From: David Collier-Brown <davec-b@rogers.com>
To: starlink@lists.bufferbloat.net
Subject: Re: [Starlink] Consumer Reportes (was: The "reasons" that bufferbloat isn't a problem)
Date: Tue, 4 Jun 2024 19:36:34 -0400 [thread overview]
Message-ID: <3ac687c4-e843-44e1-a216-a7f8840973ea@rogers.com> (raw)
In-Reply-To: <CAF-ggVMxByb-y_i1kHJsVkoUUUBpVZWAoEohpf0As9Esgpjizg@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1310 bytes --]
Oh duh! I'm getting old, and didn't realize how /smart/ that was./
/
/Definitely/ try Consumers Reports, and cite an article from "a leading
academic journal", the CACM. They'll probably expect something /utterly/
unintelligible, but Philippa Harrison's article at
https://dl.acm.org/doi/pdf/10.1145/3564262 is just sort of bland.
Then explain why the second of the "key insights" from the article, is
relevant to Consumer Reports. The key insights are probably all they'll
read, you understand (:-))
Finally, introduce the non-profit nature of the community that solved
the problem, and offer them as resources. That addresses the "what are
you selling", and "can you help us test this stuff" questions, which
will be the among the next things they'll want to know.
--dave c-b
On 2024-06-04 19:03, Rich Brown via Starlink wrote:
> Yeah... I didn't write that as carefully as I could have. I was
> switching between "user voice" (who'll say 'speed') and "expert" voice
> (I know the difference). Check it now:
> https://randomneuronsfiring.com/all-the-reasons-that-bufferbloat-isnt-a-problem/
--
David Collier-Brown, | Always do right. This will gratify
System Programmer and Author | some people and astonish the rest
davecb@spamcop.net | -- Mark Twain
[-- Attachment #2: Type: text/html, Size: 2312 bytes --]
next prev parent reply other threads:[~2024-06-04 23:36 UTC|newest]
Thread overview: 49+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.2773.1714488060.1074.starlink@lists.bufferbloat.net>
2024-04-30 18:05 ` [Starlink] It’s the Latency, FCC Colin_Higbie
2024-04-30 19:04 ` Eugene Y Chang
2024-05-01 0:36 ` David Lang
2024-05-01 1:30 ` [Starlink] Itʼs " Eugene Y Chang
2024-05-01 1:52 ` Jim Forster
2024-05-01 3:59 ` Eugene Y Chang
2024-05-01 4:12 ` David Lang
2024-05-01 10:15 ` Frantisek Borsik
2024-05-01 18:51 ` Eugene Y Chang
2024-05-01 19:18 ` David Lang
2024-05-01 21:11 ` Frantisek Borsik
2024-05-01 22:10 ` Eugene Y Chang
2024-05-01 21:12 ` Eugene Y Chang
2024-05-01 21:27 ` Sebastian Moeller
2024-05-01 22:19 ` Eugene Y Chang
2024-05-06 11:25 ` [Starlink] The "reasons" that bufferbloat isn't a problem Rich Brown
2024-05-06 12:11 ` Dave Collier-Brown
2024-05-07 0:43 ` Eugene Y Chang
2024-05-07 12:05 ` Dave Collier-Brown
[not found] ` <CAJUtOOhH3oPDCyo=mk=kwzm5DiFp7OZPiFu+0MzajTQqps==_g@mail.gmail.com>
2024-05-06 19:47 ` Rich Brown
2024-05-07 0:38 ` Eugene Y Chang
2024-05-07 10:50 ` Rich Brown
2024-05-08 1:48 ` Dave Taht
2024-05-08 7:58 ` Frantisek Borsik
2024-05-08 8:01 ` Frantisek Borsik
2024-05-08 18:29 ` Eugene Y Chang
2024-06-04 18:19 ` Stuart Cheshire
2024-06-04 20:06 ` Sauli Kiviranta
2024-06-04 20:58 ` Eugene Y Chang
2024-06-05 11:36 ` Alexandre Petrescu
2024-06-05 13:08 ` Aidan Van Dyk
2024-06-05 13:28 ` Alexandre Petrescu
2024-06-05 13:40 ` Gert Doering
2024-06-05 13:43 ` Alexandre Petrescu
2024-06-05 14:16 ` David Lang
2024-06-05 15:10 ` Sebastian Moeller
2024-06-05 16:21 ` Alexandre Petrescu
2024-06-05 19:17 ` Eugene Y Chang
2024-06-04 23:03 ` Rich Brown
2024-06-04 23:36 ` David Collier-Brown [this message]
2024-06-06 17:51 ` Stuart Cheshire
2024-06-07 2:28 ` Dave Taht
2024-06-07 5:36 ` Sebastian Moeller
2024-06-07 7:51 ` Gert Doering
2024-05-02 19:17 ` [Starlink] Itʼs the Latency, FCC Michael Richardson
2024-05-02 9:09 ` [Starlink] It’s " Alexandre Petrescu
2024-05-02 9:28 ` Ulrich Speidel
2024-04-30 20:05 ` Sebastian Moeller
2024-05-02 9:21 ` Alexandre Petrescu
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/starlink.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3ac687c4-e843-44e1-a216-a7f8840973ea@rogers.com \
--to=davec-b@rogers.com \
--cc=starlink@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