Starlink has bufferbloat. Bad.
 help / color / mirror / Atom feed
From: Inemesit Affia <inemesitaffia@gmail.com>
To: starlink@lists.bufferbloat.net
Subject: [Starlink] Re: Ambani Launches 15 Billion Dollars Space War Against Starlink
Date: Sun, 21 Jun 2026 20:11:57 +0100	[thread overview]
Message-ID: <4e5f3195-d37a-4f7d-ba18-f6dcd91f0e7d@gmail.com> (raw)
In-Reply-To: <CAJUtOOhXQJTnfvgm=KgB2t2cU3DhZKET7QvpsH=74nai_N+chA@mail.gmail.com>

The bufferbloat avoidance tech is cheap to deploy.

The issues are cost per bit (launch, satellite, ground stations, transport, IP transit and power are all factors)and terminal cost.

Don't consider the effort real until you hear about terminals


  reply	other threads:[~2026-06-21 19:12 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-06-21 18:11 [Starlink] Ambani Launches 15 Billion Dollars Space War Against Starlink Hesham ElBakoury
2026-06-21 19:03 ` [Starlink] " Frantisek Borsik
2026-06-21 19:11   ` Inemesit Affia [this message]
2026-06-21 19:24     ` Frantisek Borsik
2026-06-21 19:55   ` David Lang
2026-06-22  0:01     ` Joe Hamelin
2026-06-22  1:28 ` David Collier-Brown

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=4e5f3195-d37a-4f7d-ba18-f6dcd91f0e7d@gmail.com \
    --to=inemesitaffia@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