From: Erkki Lintunen <ebirdie@iki.fi>
To: cerowrt-devel@lists.bufferbloat.net
Subject: Re: [Cerowrt-devel] eero gains competition in plumewifi
Date: Tue, 21 Jun 2016 11:28:03 +0300 [thread overview]
Message-ID: <edae8970-0c29-ca42-ac7b-4b76a571046e@iki.fi> (raw)
In-Reply-To: <CAA93jw5UxsC++K_aXDXrHKt7JGap9TVj6ZinVN+sRh5McnoYJA@mail.gmail.com>
(resent, wrong sender address at first send)
On 06/20/2016 09:16 AM, Dave Taht wrote:
> I sure wish I knew how they are implementing diversity routing and if
> they are bothering to pay attention to make-wifi-fast
>
> https://www.plumewifi.com/
Quite a staffing for a startup, the web site lists 46 names and
positions from which 26 are named as engineers. Wondering if they
already are in the business of WiFi chip and RF engineering, which
enable them to do some "magic" to make a network of their own from the
plumewifi plugs. On staffing resources this isn't on par with Eero, I think.
- Erkki
next prev parent reply other threads:[~2016-06-21 8:28 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-20 6:16 Dave Taht
2016-06-21 6:25 ` Erkki Lintunen
2020-03-30 15:44 ` Dave Taht
2016-06-21 8:28 ` Erkki Lintunen [this message]
2016-06-21 15:53 ` Dave Taht
2016-06-21 8:43 ` Maciej Soltysiak
2016-06-21 15:27 ` Dave Taht
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://lists.bufferbloat.net/postorius/lists/cerowrt-devel.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=edae8970-0c29-ca42-ac7b-4b76a571046e@iki.fi \
--to=ebirdie@iki.fi \
--cc=cerowrt-devel@lists.bufferbloat.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox