From: Dave Taht <dave.taht@gmail.com>
To: Dave Taht via Starlink <starlink@lists.bufferbloat.net>
Subject: [Starlink] t-mobile + starlink aug 25th 7PM CT
Date: Wed, 24 Aug 2022 09:35:07 -0700 [thread overview]
Message-ID: <CAA93jw7_0fiyajXUcKyw7XuWhNV57adt26GPG7Fw8FVUw7mHMQ@mail.gmail.com> (raw)
It was only a matter of time. I wish someone we knew would have
sufficient journalistic creds to be able to ask "what are they doing
about bufferbloat?". I've long figured some 5g provider, if they made
it a goal, could actually provide service reliably low latency and
non-jittery enough to run enough to run a first person shooter.
https://twitter.com/SpaceX/status/1562476038235377665
--
FQ World Domination pending: https://blog.cerowrt.org/post/state_of_fq_codel/
Dave Täht CEO, TekLibre, LLC
reply other threads:[~2022-08-24 16:35 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=CAA93jw7_0fiyajXUcKyw7XuWhNV57adt26GPG7Fw8FVUw7mHMQ@mail.gmail.com \
--to=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