From: Dave Taht <dave.taht@gmail.com>
To: bloat <bloat@lists.bufferbloat.net>,
Make-Wifi-fast <make-wifi-fast@lists.bufferbloat.net>,
cerowrt-devel <cerowrt-devel@lists.bufferbloat.net>
Subject: [Cerowrt-devel] will starlink have bufferbloat?
Date: Wed, 22 May 2019 11:53:07 +0200 [thread overview]
Message-ID: <CAA93jw44wYV3hqKvPda03sW4Ep_GbhN7p8S4juUt1O9m+Npi1g@mail.gmail.com> (raw)
With the first major starlink launch stuck on the pad, and having
never got a straight answer about how starlink was going to manage
satellite handovers and admission control, I came up with an
"annoyer-in-chief" idea to see if we could find out what the plan was.
If everybody here (500+ members of these mailing lists!) could take 2
minutes to compose an interesting tweet or reply to elon musk on the
subject, maybe we'd get somewhere. I just did one (
https://twitter.com/mtaht/status/1131131277413822464 ) but a huge
variety of posts on the theme are possible, other thoughts were things
like:
@elonmusk There seems to be no intelligent life among ISPs down here.
Has #starlink handled the #bufferbloat problem? (
https://blog.tohojo.dk/media/bufferbloat-and-beyond.pdf )
@elonmusk Keep hoping #bufferbloat will be solved by #starlink - got a
plan? ( https://blog.tohojo.dk/media/bufferbloat-and-beyond.pdf )
do it on replies to anything he says about starlink, keep doin it, and
perhaps, an answer will appear.
Sometimes ya gotta be loud.
--
Dave Täht
CTO, TekLibre, LLC
http://www.teklibre.com
Tel: 1-831-205-9740
next reply other threads:[~2019-05-22 9:53 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-22 9:53 Dave Taht [this message]
2019-05-22 10:45 ` Dave Taht
2019-05-23 18:46 ` [Cerowrt-devel] Does Ubiquiti Unifi have bufferbloat and unfair/bloated WiFi scheduling? David P. Reed
2019-05-23 19:22 ` [Cerowrt-devel] [Make-wifi-fast] " Jim Gettys
2019-05-23 19:41 ` John Yates
2019-05-23 20:00 ` Jim Gettys
2019-05-23 18:48 ` [Cerowrt-devel] will starlink have bufferbloat? David P. Reed
2019-05-24 17:34 ` 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/cerowrt-devel.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAA93jw44wYV3hqKvPda03sW4Ep_GbhN7p8S4juUt1O9m+Npi1g@mail.gmail.com \
--to=dave.taht@gmail.com \
--cc=bloat@lists.bufferbloat.net \
--cc=cerowrt-devel@lists.bufferbloat.net \
--cc=make-wifi-fast@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