From: Jonathan Foulkes <jf@jonathanfoulkes.com>
To: Rich Brown <richb.hanover@gmail.com>
Cc: bloat@lists.bufferbloat.net
Subject: Re: [Bloat] dslreports is no longer free
Date: Fri, 8 May 2020 15:59:50 -0400 [thread overview]
Message-ID: <825226E1-AA0D-46C6-8E71-2037D995EB71@jonathanfoulkes.com> (raw)
In-Reply-To: <2F8B9D4D-2FC3-4B04-BC49-4F8E597B22DF@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1319 bytes --]
Hi Rich, good suggestion, seconded!
Hopefully Sergey can have this incorporated when they make the updates for a URL that triggers a full featured test from the beginning.
Cheers,
Jonathan
> On May 7, 2020, at 9:33 PM, Rich Brown <richb.hanover@gmail.com> wrote:
>
> A request to Sergey,
>
> As a long-time lurker on this list, I lament the passing of DSLReports, and applaud Netflix for incorporating latency measurements into its Fast.com <http://fast.com/> page.
>
> However, I have always been vaguely unsettled that "Show more info" displays a single latency value for the two separate "processes" - downloading and uploading - and the fact that uploading seems to overwrite the download value.
>
> I imagine that you have already considered this but I have come to realize that simply displaying separate values for these latencies would address my unease - something along the lines of this photoshopped screen shot.
>
> Thanks again for providing the Fast.com service - it's useful for me every day.
>
> Rich Brown
>
> PS Yes, my DSL download speed really is < 1mbps today. Dratted ISP...
>
> <Fast.com Proposal.png>
> _______________________________________________
> Bloat mailing list
> Bloat@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/bloat
[-- Attachment #2: Type: text/html, Size: 2543 bytes --]
next prev parent reply other threads:[~2020-05-08 19:59 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-08 1:33 Rich Brown
2020-05-08 19:59 ` Jonathan Foulkes [this message]
2020-05-12 15:53 ` Sergey Fedorov
-- strict thread matches above, loose matches on Subject: below --
2020-05-01 16:44 Dave Taht
2020-05-01 19:34 ` Kenneth Porter
2020-05-01 19:54 ` Sebastian Moeller
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/bloat.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=825226E1-AA0D-46C6-8E71-2037D995EB71@jonathanfoulkes.com \
--to=jf@jonathanfoulkes.com \
--cc=bloat@lists.bufferbloat.net \
--cc=richb.hanover@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