From: Sebastian Moeller <moeller0@gmx.de>
To: "Dave Täht" <dave.taht@gmail.com>,
"Dave Taht via Starlink" <starlink@lists.bufferbloat.net>,
"Daniel AJ Sokolov" <daniel@sokolov.eu.org>
Subject: Re: [Starlink] It's still the starlink latency...
Date: Mon, 26 Sep 2022 17:57:34 +0200 [thread overview]
Message-ID: <DB0A3F8E-3F85-4F60-B03D-393A8AE21493@gmx.de> (raw)
In-Reply-To: <CAA93jw6SSYKwXf2VXjcPYMTp8HnwoMswdMsoUKFutdWERQugdw@mail.gmail.com>
Hi Dave,
> On Sep 26, 2022, at 17:29, Dave Taht via Starlink <starlink@lists.bufferbloat.net> wrote:
>
> On Mon, Sep 26, 2022 at 8:20 AM Livingood, Jason
> <Jason_Livingood@comcast.com> wrote:
>>
>> The awareness & understanding of latency & impact on QoE is nearly unknown among reporters. IMO maybe there should be some kind of background briefings for reporters - maybe like a simple YouTube video explainer that is short & high level & visual? Otherwise reporters will just continue to focus on what they know...
>
> That's a great idea. I have visions of crashing the washington
> correspondents dinner, but perhaps
> there is some set of gatherings journalists regularly attend?
I would assume the relevant tech-journalists might be easier to catch at PR events at trade shows, or tech-related PR events like CES.
However, starlink's own website does not seem to prominently advertise specific rates anyway, but does stress the latency advantage over geo stationary satellite links.
The rest of the residential market however has been trained for decades now that the most relevant numbers are the maximal throughput* (well mostly downloads only), hence I can understand that articles will mention regressions of that number prominently.
I just stumbled over a German article (https://www.heise.de/news/Speedtests-Satelliteninternet-Starlink-teilweise-deutlich-langsamer-geworden-7275243.html) apparently presenting the same Ookla numbers for starlink containing a single short paragraph about latency increases, but without explaining their relevance, so exactly what you see in the other article as well; @Daniel anything we could do to make your colleague? Martin Holland more latency aware?
>> On 9/21/22, 14:35, "Starlink on behalf of Dave Taht via Starlink" <starlink-bounces@lists.bufferbloat.net on behalf of starlink@lists.bufferbloat.net> wrote:
>>
>> I still find it remarkable that reporters are still missing the
>> meaning of the huge latencies for starlink, under load.
In their "defense" a similar level of latency-awareness is often displayed when talking about wired internet connections. (And from my perspective, I consider absolute latency somewhat less important than latency variation)
*) I am not trying to assign responsibility/blame here, I think both ISPs and customers jointly "selected" maximal contracted throughput as measure of choice to justify differential prices.
>
> --
> FQ World Domination pending: https://blog.cerowrt.org/post/state_of_fq_codel/
> Dave Täht CEO, TekLibre, LLC
> _______________________________________________
> Starlink mailing list
> Starlink@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/starlink
next prev parent reply other threads:[~2022-09-26 15:57 UTC|newest]
Thread overview: 56+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-21 18:35 Dave Taht
2022-09-22 11:41 ` Andrew Crane
2022-09-22 12:01 ` Mike Puchol
2022-09-22 13:46 ` warren ponder
2022-09-22 15:07 ` Dave Taht
2022-09-22 15:26 ` Dave Taht
2022-09-26 15:20 ` Livingood, Jason
2022-09-26 15:29 ` Dave Taht
2022-09-26 15:57 ` Sebastian Moeller [this message]
2022-09-26 16:21 ` Dave Taht
2022-09-26 16:32 ` Bruce Perens
2022-09-26 19:59 ` Eugene Chang
2022-09-26 20:04 ` Bruce Perens
2022-09-26 20:14 ` Ben Greear
2022-09-26 20:24 ` Bruce Perens
2022-09-26 20:32 ` Dave Taht
2022-09-26 20:36 ` Bruce Perens
2022-09-26 20:47 ` Ben Greear
2022-09-26 20:19 ` Eugene Y Chang
2022-09-26 20:28 ` Dave Taht
2022-09-26 20:32 ` Bruce Perens
2022-09-26 20:35 ` Bruce Perens
2022-09-26 20:48 ` David Lang
2022-09-26 20:54 ` Eugene Y Chang
2022-09-26 21:01 ` Sebastian Moeller
2022-09-26 21:10 ` Eugene Y Chang
2022-09-26 21:20 ` Sebastian Moeller
2022-09-26 21:35 ` Eugene Y Chang
2022-09-26 21:44 ` David Lang
2022-09-26 21:44 ` Bruce Perens
2022-09-27 0:35 ` Dave Taht
2022-09-27 0:55 ` Bruce Perens
2022-09-27 1:12 ` Dave Taht
2022-09-27 4:06 ` Eugene Y Chang
2022-09-27 3:50 ` Eugene Y Chang
2022-09-27 7:09 ` Sebastian Moeller
2022-09-27 22:46 ` Eugene Y Chang
2022-09-28 9:54 ` Sebastian Moeller
2022-09-28 18:49 ` Eugene Y Chang
2022-09-26 21:22 ` David Lang
2022-09-26 21:29 ` Sebastian Moeller
2022-09-27 3:47 ` Eugene Y Chang
2022-09-27 6:36 ` Sebastian Moeller
2022-09-27 13:55 ` Dave Taht
2022-09-28 0:20 ` Eugene Y Chang
2022-09-26 21:02 ` Bruce Perens
2022-09-26 21:14 ` Dave Taht
2022-09-26 21:10 ` Dave Taht
2022-09-26 21:28 ` warren ponder
2022-09-26 21:34 ` Bruce Perens
2022-09-27 16:14 ` Dave Taht
2022-09-26 21:17 ` David Lang
2022-09-29 9:10 David Fernández
2022-09-29 19:34 ` Eugene Chang
2022-10-17 13:50 David Fernández
2022-10-17 16:53 ` David Fernández
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=DB0A3F8E-3F85-4F60-B03D-393A8AE21493@gmx.de \
--to=moeller0@gmx.de \
--cc=daniel@sokolov.eu.org \
--cc=dave.taht@gmail.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