From: Sascha Meinrath <sascha@thexlab.org>
To: Michael Richardson <mcr+ietf@sandelman.ca>,
Ulrich Speidel <u.speidel@auckland.ac.nz>
Cc: starlink@lists.bufferbloat.net
Subject: Re: [Starlink] Starlink Internet Speeds Could Skyrocket to 2 Gigabits Per Second, SpaceX President Says
Date: Mon, 25 Nov 2024 09:51:33 -0500 [thread overview]
Message-ID: <6f678b2a-4827-4334-a3c2-75d01bf0f06b@thexlab.org> (raw)
In-Reply-To: <7032.1732386555@obiwan.sandelman.ca>
For those who haven't been following the Starshield project (and its exponential
ramp-up)... I fully expect that Musk will focus more on military-industrial
complex funding than in trying to repurpose FCC or NTIA support -- why fight in
the trenches for hundreds of millions when you can repurpose
billions/tens-of-billions elsewhere:
https://spacenews.com/pentagons-commercial-satellite-internet-services-program-soars-to-13-billion/
And yes, Starshield is just as scary and prone for abuse as Michael alludes to.
--Sascha
On 11/23/24 13:29, Michael Richardson via Starlink wrote:
>
> Ulrich Speidel via Starlink <starlink@lists.bufferbloat.net> wrote:
> > to launch at a faster rate or with fewer sats per launch. It's also a bit
> > more crowded in lower space, as this is where a lot of earth observation
> > spacecraft sit (if you want to take detailed pics of the Earth's surface, you
> > want it to be as close to your camera lens as you can have it), and some of
> > those aren't there for open source public good science.
>
> <sincecism alert>
> 1. I'm sure that spaceX could just include cameras for earth observation of dissidents.
> 2. Earth observation will be obsolete according to Project 2025.
> 3. Elon will own the FCC.
>
>
> --
> Michael Richardson <mcr+IETF@sandelman.ca> . o O ( IPv6 IøT consulting )
> Sandelman Software Works Inc, Ottawa and Worldwide
>
>
>
>
>
> _______________________________________________
> Starlink mailing list
> Starlink@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/starlink
--
Sascha Meinrath
Director, X-Lab
Palmer Chair in Telecommunications
Penn State University
next prev parent reply other threads:[~2024-11-25 14:51 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-22 22:16 Hesham ElBakoury
2024-11-22 22:33 ` Dave Taht
2024-11-22 23:32 ` Ulrich Speidel
2024-11-23 1:13 ` Brandon Butterworth
2024-11-23 6:05 ` David Lang
2024-11-23 13:30 ` Ulrich Speidel
2024-11-23 18:29 ` Michael Richardson
2024-11-23 20:05 ` Dave Taht
2024-11-24 3:39 ` Ulrich Speidel
2024-11-25 14:51 ` Sascha Meinrath [this message]
2024-11-25 16:59 ` David Lang
2024-11-25 17:20 ` Steve Stroh
2024-11-25 17:29 ` 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/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=6f678b2a-4827-4334-a3c2-75d01bf0f06b@thexlab.org \
--to=sascha@thexlab.org \
--cc=mcr+ietf@sandelman.ca \
--cc=starlink@lists.bufferbloat.net \
--cc=u.speidel@auckland.ac.nz \
/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