Starlink has bufferbloat. Bad.
 help / color / mirror / Atom feed
From: Bill Woodcock <woody@pch.net>
To: "Network Neutrality is back! Let´s make the technical aspects
	heard this time!" <nnagain@lists.bufferbloat.net>
Cc: "Dave Taht via Starlink" <starlink@lists.bufferbloat.net>,
	"Dave Täht" <dave.taht@gmail.com>
Subject: Re: [Starlink] [NNagain] one dish per household is silly.
Date: Fri, 10 Nov 2023 13:33:03 +0100	[thread overview]
Message-ID: <13641F2C-B933-49AF-8289-7B8917667AAE@pch.net> (raw)
In-Reply-To: <CAA93jw7ot=Q_+3JN68C2WYSLj7gu6mB7qKOKJ+9+5XLVPK2kJw@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1175 bytes --]

> On Nov 10, 2023, at 12:44, Dave Taht via Nnagain <nnagain@lists.bufferbloat.net> wrote:
> Steve song's analysis here:
> https://manypossibilities.net/2023/11/starlink-and-inequality/

He makes some good points.

> A) Am I the only person left in the world that shares his wifi?

My neighbors and I do.

> A single dishy can easily serve dozens of people

But that’s a different question than whether Starlink’s contract _allows_ you to share it.  The contract does not.

So I think saying that it’s a good thing because it’s good when you don’t follow the rules is… well, perhaps a little too much of a stretch for a general argument.

> I know of refuge centers in the ukraine serving hundreds of people as one example.

And if Musk weren’t cutting Starlink connectivity for Ukrainian defensive uses, those refugee centers wouldn’t have so many people in them.  And, more to the point, Ukrainian graveyards wouldn’t have so many people in them.

As always, the Musk-vs.-Tesla and Musk-vs.-SpaceX conflicts are tricky to sort out, and may not yield any more broadly-applicable principles.


                                -Bill


[-- Attachment #2: Message signed with OpenPGP --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  parent reply	other threads:[~2023-11-10 12:33 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-10 11:44 [Starlink] " Dave Taht
2023-11-10 12:21 ` Inemesit Affia
2023-11-11  4:42   ` Alexandre Petrescu
2023-11-10 12:33 ` Bill Woodcock [this message]
2023-11-10 12:55   ` [Starlink] [NNagain] " Dave Taht
2023-11-10 13:17     ` Alexandre Petrescu
2023-11-10 13:44       ` David Lang
2023-11-10 15:10         ` Dave Taht
2023-11-10 16:09         ` Alexandre Petrescu
2023-11-10 16:40           ` David Lang
2023-11-10 16:58             ` Alexandre Petrescu
2023-11-10 18:16             ` Alexandre Petrescu
2023-11-10 13:53       ` Dave Taht
2023-11-11  4:50     ` Alexandre Petrescu
2023-11-10 16:11   ` Alexandre Petrescu
2023-11-10 13:51 ` [Starlink] " David Lang
2023-11-13  6:37 ` J Pan
2023-11-13  6:40   ` Inemesit Affia
2023-11-13 16:10     ` J Pan
2023-11-13 16:22       ` Inemesit Affia
2023-11-13 20:34         ` Ulrich Speidel
2023-11-13 20:38           ` Inemesit Affia
2023-11-13 20:42           ` Inemesit Affia
2023-11-14  4:57             ` J Pan
2023-11-14  5:13               ` Ulrich Speidel
2023-11-14  5:18                 ` J Pan
2023-11-14  9:04                 ` Alexandre Petrescu
2023-11-14  8:50           ` Alexandre Petrescu

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=13641F2C-B933-49AF-8289-7B8917667AAE@pch.net \
    --to=woody@pch.net \
    --cc=dave.taht@gmail.com \
    --cc=nnagain@lists.bufferbloat.net \
    --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