From: Matt Taggart <matt@lackof.org>
To: bloat <bloat@lists.bufferbloat.net>
Subject: [Bloat] Engineering for slow internet
Date: Fri, 31 May 2024 10:54:28 -0700 [thread overview]
Message-ID: <2991ca56-e5fa-47bd-b0f4-ed8e4f1166e0@lackof.org> (raw)
Neat post about networking in Antarctica
https://brr.fyi/posts/engineering-for-slow-internet
In the disclaimer they explain they are not allowed to share details
about the methods they use to deal with this, but the fact that they
mention bufferbloat by name means they know what they are doing(and some
of them are probably on this list!).
--
Matt Taggart
matt@lackof.org
reply other threads:[~2024-05-31 17:54 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/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=2991ca56-e5fa-47bd-b0f4-ed8e4f1166e0@lackof.org \
--to=matt@lackof.org \
--cc=bloat@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