Cake - FQ_codel the next generation
 help / color / mirror / Atom feed
From: Sebastian Moeller <moeller0@gmx.de>
To: cake@lists.bufferbloat.net, Dave Taht <dave.taht@gmail.com>,
	Jonathan Morton <chromatix99@gmail.com>
Cc: Cake List <cake@lists.bufferbloat.net>
Subject: Re: [Cake] the Cake stalemate
Date: Wed, 20 Jun 2018 01:41:00 +0200	[thread overview]
Message-ID: <325EDD98-F934-4039-A5F8-70077CF37528@gmx.de> (raw)
In-Reply-To: <CAA93jw7seJ2VavDdVL8e2NafDdjp9RmRQp=n8ZbaNpF=T_f+pA@mail.gmail.com>



On June 19, 2018 11:48:08 PM GMT+02:00, Dave Taht <dave.taht@gmail.com> wrote:
>On Tue, Jun 19, 2018 at 1:35 PM, Jonathan Morton
><chromatix99@gmail.com> wrote:
>>> On 19 Jun, 2018, at 11:14 pm, Pete Heist <pete@heistp.net> wrote:
>>>
>>> I don’t think we can do much better than “it makes your Internet
>faster”, which is what most people want
>>
>> s/faster/reliable/
>>
>> It would be really nice to be able to say "go out and buy this box,
>plug it in and run through the setup wizard" instead of "go through the
>frankly scary process of reflashing your router with OpenWRT".  In that
>case we might really get some traction.
>
>Faster and more reliable is a good catchphrase.
>
>Here's eero's implementation of sqm:
>https://www.macobserver.com/tips/quick-tip/enable-sqm-eero-wifi-mesh-network/

Well do we know what eero's really does under the hood? So are they using sqm or are they simply using sqm as a marketing term for their own special sauce? 

Best Regards
        Sebastian


>
>>  - Jonathan Morton
>>
>
>
>
>-- 
>
>Dave Täht
>CEO, TekLibre, LLC
>http://www.teklibre.com
>Tel: 1-669-226-2619
>_______________________________________________
>Cake mailing list
>Cake@lists.bufferbloat.net
>https://lists.bufferbloat.net/listinfo/cake

-- 
Sent from my Android device with K-9 Mail. Please excuse my brevity.

  reply	other threads:[~2018-06-19 23:41 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-06-19  9:31 Pete Heist
2018-06-19  9:55 ` Toke Høiland-Jørgensen
2018-06-19 10:04   ` Pete Heist
2018-06-19 11:32   ` Jonathan Morton
2018-06-19 11:54     ` Toke Høiland-Jørgensen
2018-06-19 12:26       ` Pete Heist
2018-06-19 13:41         ` Kevin Darbyshire-Bryant
2018-06-19 14:48           ` Pete Heist
2018-06-19 16:24             ` Dave Taht
2018-06-19 20:14               ` Pete Heist
2018-06-19 20:35                 ` Jonathan Morton
2018-06-19 21:48                   ` Dave Taht
2018-06-19 23:41                     ` Sebastian Moeller [this message]
2018-06-19 22:34                   ` Pete Heist
2018-06-19 23:38                   ` Sebastian Moeller
2018-06-20  3:36                     ` Jonathan Morton
2018-06-20  4:34                       ` Sebastian Moeller
2018-06-19 12:08     ` Pete Heist

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/cake.lists.bufferbloat.net/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=325EDD98-F934-4039-A5F8-70077CF37528@gmx.de \
    --to=moeller0@gmx.de \
    --cc=cake@lists.bufferbloat.net \
    --cc=chromatix99@gmail.com \
    --cc=dave.taht@gmail.com \
    /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