Starlink has bufferbloat. Bad.
 help / color / mirror / Atom feed
From: "David P. Reed" <dpreed@deepplum.com>
To: starlink@lists.bufferbloat.net
Cc: starlink@lists.bufferbloat.net
Subject: Re: [Starlink] something of a step backwards
Date: Thu, 11 Nov 2021 13:30:26 -0500 (EST)	[thread overview]
Message-ID: <1636655426.376728690@apps.rackspace.com> (raw)
In-Reply-To: <mailman.5.1636650001.22273.starlink@lists.bufferbloat.net>

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


I don't think StarLink will be an Internet Access Provider if it includes a bundled router that is sealed off with proprietary (even DMCA and FCC certification protection from modification).
 
I can see them taking control as folks like Comcast have tried to do - for example:
 
They may start MITM's https connections to read traffic and gather surveillance data on users' DNS and HTTP uses.
 
They may start blocking bittorrent because they claim it's all "piracy" and theft.
 
They may start charging differentially based on the type or endpoints of traffic.
 
They may start blocking countries' access geographically to other countries over Starlink.
 
This always comes with some argument that "bundling" a provider-controlled service will reduce "consumer price" (of course, monopolies rarely pass cost on in the form of minimized price, in reality, but when they talk to regulators, they lie and wave their hands about "economics" that conflates cost with price).
 
But those who are fans of satellites and love Elon Musk to death because he's a "hero" will not worry about these things, even though in the past that is exactly what has happened.
 
So, you'll buy into what you buy into. Just don't say I didn't tell you this will happen.
 

[-- Attachment #2: Type: text/html, Size: 3108 bytes --]

       reply	other threads:[~2021-11-11 18:30 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <mailman.5.1636650001.22273.starlink@lists.bufferbloat.net>
2021-11-11 18:30 ` David P. Reed [this message]
2021-11-15 14:21   ` Livingood, Jason
2021-11-15 18:45     ` David P. Reed
2021-11-15 22:36       ` Michael Richardson
2021-11-11 15:53 Dave Taht
2021-11-11 15:54 ` Nathan Owens
2021-11-11 18:14   ` Jonathan Bennett

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=1636655426.376728690@apps.rackspace.com \
    --to=dpreed@deepplum.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