From: Dave Taht <dave.taht@gmail.com>
To: "Richard E. Brown" <richb.hanover@gmail.com>
Cc: bloat <bloat@lists.bufferbloat.net>
Subject: Re: [Bloat] will starlink have bufferbloat?
Date: Thu, 23 May 2019 18:38:46 -0700 [thread overview]
Message-ID: <CAA93jw4y5K-GP8DTHFsvZP5RQ3rH7eMQvqk1hscV=rtJZ7E5LQ@mail.gmail.com> (raw)
In-Reply-To: <A13653F0-0680-410C-BAAC-C4219389B9E0@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1685 bytes --]
Mailing lists seem to be no longer effectively indexed by Google, so I've
been trying various alternative means of having our issues show up in the
world.
That Reddit post got a bit of traction, as the author of "delay is not an
option" showed up, and it does help that I'm pretty passionately interested
in the overall subject... How a service intended to carry internet for
millions is actually going to work has had too few questions of it asked so
far.
On Thu, May 23, 2019, 4:14 AM Rich Brown <richb.hanover@gmail.com> wrote:
> Hi Dave,
>
> Google Alerts today found your Reddit post (
> https://www.reddit.com/r/Starlink/comments/brn6gg/will_starlink_have_bufferbloat/
> )
>
> It also provided a link to a Slashdot post that seems to have been marked
> as spam...
> https://slashdot.org/submission/9718636/will-starlink-have-bufferbloat
>
> Was this your original submission? In any case, I upvoted it.
>
> Rich
> _______________________________________________
> Bloat mailing list
> Bloat@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/bloat
>
On Thu, May 23, 2019, 4:14 AM Rich Brown <richb.hanover@gmail.com> wrote:
> Hi Dave,
>
> Google Alerts today found your Reddit post (
> https://www.reddit.com/r/Starlink/comments/brn6gg/will_starlink_have_bufferbloat/
> )
>
> It also provided a link to a Slashdot post that seems to have been marked
> as spam...
> https://slashdot.org/submission/9718636/will-starlink-have-bufferbloat
>
> Was this your original submission? In any case, I upvoted it.
>
> Rich
> _______________________________________________
> Bloat mailing list
> Bloat@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/bloat
>
[-- Attachment #2: Type: text/html, Size: 3541 bytes --]
next prev parent reply other threads:[~2019-05-24 1:38 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.7.1558540801.986.bloat@lists.bufferbloat.net>
2019-05-23 11:14 ` Rich Brown
2019-05-24 1:38 ` Dave Taht [this message]
2019-05-22 9:53 Dave Taht
2019-05-22 10:45 ` 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='CAA93jw4y5K-GP8DTHFsvZP5RQ3rH7eMQvqk1hscV=rtJZ7E5LQ@mail.gmail.com' \
--to=dave.taht@gmail.com \
--cc=bloat@lists.bufferbloat.net \
--cc=richb.hanover@gmail.com \
/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