From: "David P. Reed" <dpreed@deepplum.com>
To: "Dave Taht" <dave.taht@gmail.com>
Cc: "bloat" <bloat@lists.bufferbloat.net>,
"Make-Wifi-fast" <make-wifi-fast@lists.bufferbloat.net>,
"cerowrt-devel" <cerowrt-devel@lists.bufferbloat.net>
Subject: Re: [Bloat] [Cerowrt-devel] will starlink have bufferbloat?
Date: Thu, 23 May 2019 14:48:27 -0400 (EDT) [thread overview]
Message-ID: <1558637307.393118022@apps.rackspace.com> (raw)
In-Reply-To: <CAA93jw6M3T9qC7bVQc_QJMeMh1wPegoYOpPyYBEmh7mRp6S15w@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2183 bytes --]
Sorry, I can't help - I never spend time or effort on Twitter, Reddit, etc. because I see no value and lots of problems in doing that.
Musk probably wouldn't love my views on most of his companies, anyway.
I hope he gets something right on this one.
On Wednesday, May 22, 2019 6:45am, "Dave Taht" <dave.taht@gmail.com> said:
> And I tried my first ever post to reddit, not realizing it didn't take html....
>
> https://www.reddit.com/r/Starlink/comments/brn6gg/will_starlink_have_bufferbloat/
>
> and slashdot also.
>
> On Wed, May 22, 2019 at 11:53 AM Dave Taht <dave.taht@gmail.com> wrote:
> >
> > 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
>
>
>
> --
>
> Dave Täht
> CTO, TekLibre, LLC
> http://www.teklibre.com
> Tel: 1-831-205-9740
> _______________________________________________
> Cerowrt-devel mailing list
> Cerowrt-devel@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/cerowrt-devel
>
[-- Attachment #2: Type: text/html, Size: 3424 bytes --]
next prev parent reply other threads:[~2019-05-23 18:48 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-22 9:53 [Bloat] " Dave Taht
2019-05-22 10:45 ` Dave Taht
2019-05-23 18:46 ` [Bloat] Does Ubiquiti Unifi have bufferbloat and unfair/bloated WiFi scheduling? David P. Reed
2019-05-23 19:22 ` [Bloat] [Make-wifi-fast] " Jim Gettys
2019-05-23 19:41 ` John Yates
2019-05-23 20:00 ` Jim Gettys
2019-05-23 18:48 ` David P. Reed [this message]
2019-05-24 17:34 ` [Bloat] [Cerowrt-devel] will starlink have bufferbloat? 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/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=1558637307.393118022@apps.rackspace.com \
--to=dpreed@deepplum.com \
--cc=bloat@lists.bufferbloat.net \
--cc=cerowrt-devel@lists.bufferbloat.net \
--cc=dave.taht@gmail.com \
--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