From: Michael Richardson <mcr@sandelman.ca>
To: Sergey Fedorov <sfedorov@netflix.com>,
Sebastian Moeller <moeller0@gmx.de>,
Cake List <cake@lists.bufferbloat.net>,
Make-Wifi-fast <make-wifi-fast@lists.bufferbloat.net>,
cerowrt-devel <cerowrt-devel@lists.bufferbloat.net>,
bloat <bloat@lists.bufferbloat.net>
Subject: Re: [Make-wifi-fast] [Bloat] [Cake] dslreports is no longer free
Date: Fri, 01 May 2020 18:07:20 -0400 [thread overview]
Message-ID: <24457.1588370840@localhost> (raw)
In-Reply-To: <mailman.170.1588363787.24343.bloat@lists.bufferbloat.net>
[-- Attachment #1: Type: text/plain, Size: 1440 bytes --]
{Do I need all the lists?}
Sergey Fedorov via Bloat <bloat@lists.bufferbloat.net> wrote:
> Just a note that I have a plan to separate the loaded latency into
> upload/download. It's not great UX now they way it's implemented.
> The timeline view is a bit more nuanced, in the spirit of the simplistic
> UX, but I've been thinking on a good way to show that for super users as
> well.
> Two latency numbers - that's more user friendly, we want the general user
> to understand the meaning. And latency under load is much easier than
> bufferbloat.
> As a side note, if our backend is decent, I'm curious what are the backends
> for the speed tests that exist that are great :)
Does it find/use my nearest Netflix cache?
As others asked, it would be great if we could put the settings into a URL,
and having the "latency under upload" is probably the most important number
that people trying to videoconference need to know.
(it's also the thing that they can mostly directly/cheaply fix)
> SERGEY FEDOROV
> Director of Engineering
> sfedorov@netflix.com
> 121 Albright Way | Los Gatos, CA 95032
Very happy that you are looped in here.
--
] Never tell me the odds! | ipv6 mesh networks [
] Michael Richardson, Sandelman Software Works | IoT architect [
] mcr@sandelman.ca http://www.sandelman.ca/ | ruby on rails [
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 487 bytes --]
next prev parent reply other threads:[~2020-05-01 22:07 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-01 16:44 [Make-wifi-fast] " Dave Taht
2020-05-01 19:48 ` [Make-wifi-fast] [Cake] " Sebastian Moeller
2020-05-01 20:09 ` [Bloat] " Sergey Fedorov
2020-05-01 21:11 ` [Make-wifi-fast] " Sebastian Moeller
2020-05-01 21:37 ` Sergey Fedorov
[not found] ` <mailman.191.1588369068.24343.bloat@lists.bufferbloat.net>
2020-05-01 23:59 ` [Make-wifi-fast] " Michael Richardson
[not found] ` <mailman.170.1588363787.24343.bloat@lists.bufferbloat.net>
2020-05-01 22:07 ` Michael Richardson [this message]
2020-05-01 23:35 ` Sergey Fedorov
2020-05-02 1:14 ` [Make-wifi-fast] " Jannie Hanekom
2020-05-02 16:37 ` [Make-wifi-fast] [Cake] [Bloat] " Benjamin Cronce
2020-05-02 16:52 ` Dave Taht
2020-05-02 17:38 ` David P. Reed
2020-05-02 19:00 ` [Cake] [Make-wifi-fast] " Sergey Fedorov
2020-05-02 23:23 ` [Make-wifi-fast] [Cake] " David P. Reed
2020-05-03 15:31 ` [Make-wifi-fast] fast.com quality David P. Reed
2020-05-03 15:37 ` Dave Taht
2020-05-02 20:19 ` [Make-wifi-fast] [Cake] [Bloat] dslreports is no longer free Sebastian Moeller
2020-05-27 9:08 ` [Make-wifi-fast] [Bloat] [Cake] " Matthew Ford
2020-05-27 9:28 ` Toke Høiland-Jørgensen
2020-05-27 9:32 ` Sebastian Moeller
2020-05-03 15:06 [Make-wifi-fast] [Cake] [Bloat] " David P. Reed
[not found] ` <mailman.253.1588611897.24343.make-wifi-fast@lists.bufferbloat.net>
[not found] ` <mailman.256.1588636996.24343.bloat@lists.bufferbloat.net>
2020-05-05 0:10 ` [Make-wifi-fast] [Bloat] [Cake] " 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/make-wifi-fast.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=24457.1588370840@localhost \
--to=mcr@sandelman.ca \
--cc=bloat@lists.bufferbloat.net \
--cc=cake@lists.bufferbloat.net \
--cc=cerowrt-devel@lists.bufferbloat.net \
--cc=make-wifi-fast@lists.bufferbloat.net \
--cc=moeller0@gmx.de \
--cc=sfedorov@netflix.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