From: David Lang <david@lang.hm>
To: Dave Taht <dave.taht@gmail.com>
Cc: Dave Taht via Starlink <starlink@lists.bufferbloat.net>
Subject: Re: [Starlink] a bit more starship news
Date: Sun, 30 Apr 2023 14:48:51 -0700 (PDT) [thread overview]
Message-ID: <3nrs5r7q-r5q6-0rqo-7q60-3n095308s27s@ynat.uz> (raw)
In-Reply-To: <CAA93jw43eVibpYoQDambsmqBm9joUY5kHWqouK6CAXgsZwHOsw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 3861 bytes --]
the V2 mini satllites do not have the same capability as the full V2 satellites,
they are cut down in capacity as well as in size to fit them on a Falcon 9.
I would not be surprised to see v2 satellites launched on Starship later this
year.
Gwen Shotwell said late last year that they had a quarter of Starlink having
positive cash flow, and that it's expected to be profitable in 2023
David Lang
On Sun, 30 Apr 2023, Dave Taht via Starlink wrote:
> Date: Sun, 30 Apr 2023 05:48:20 -0700
> From: Dave Taht via Starlink <starlink@lists.bufferbloat.net>
> Reply-To: Dave Taht <dave.taht@gmail.com>
> To: Dave Taht via Starlink <starlink@lists.bufferbloat.net>
> Subject: [Starlink] a bit more starship news
>
> Aside from using triggering words, like "shrapnel", rather than
> debris, this is a pretty good, and profoundly negative summary of the
> Starship launch. https://youtu.be/ErDuVomNd9M
>
> Nit: I get bugged by folk like this raising local environmental
> concerns, as if you make the half an hour long drive to the launch
> site, there are plenty of wetlands to spare. Obliterating 1000
> diameter meters of it, turning it into a concrete strewn wasteland,
> (and not coated with hypergolic poisons) for a launch site, seems
> trivial compared to oh, paving over manhattan, or what it took to
> build out towns like brownsville in the first place, and reminds me of
> the enormous fight to save the snail darter.[1]
>
> This also, was a fair minded summary of the negatives of where things
> stand: https://thenext30trips.com/p/scrappy-special-edition and what
> seems to me to be a great suggestion in locating the launch site *just
> offshore*, in the comments.
>
> Anyway, over here was a summary of what actually happened, according
> to Musk. The pad damage was not what caused the shutdown of 3 engines,
> and requalifying the ATS is what will take the most time. Still
> projecting 4-5 flights this year.
>
> https://twitter.com/JackKuhr/status/1652466221390913536
>
> I note that my principal interest, at least, in the short term, was in
> thinking about how the Starship development timeline affects the
> starlink rollout. The "v2" satellites already constructed are
> effectively already obsolete, and their technologies being shrunk down
> into the v2 minis and successors, and the network behaviors themselves
> continually optimized. Right now I think it will be 2+ years before
> the first meaningful launch of the larger starlink satellites on
> Starship, and at the same time the flight rate of the falcons keeps
> getting better and better. I would kind of expect the "v3 mini" to
> have roughly the same throughput as the v2s at an ongoing half the
> size.
>
> Starlink is now well over a billion dollar a year revenue business,
> which is insanely better than what iridium achieved before entering
> bankruptcy (Iridium was under 70k users as best as I recall around
> then). Whatever spacex and starlink are spending on R&D makes me
> shudder. I am finding it odd that they have stopped publishing user
> growth numbers - small personal data point: in working with libreqos
> users, I am hearing about a 40% rate of folk that switched from WISP
> to starlink and back - so customer retention might be a problem as
> soon as someone finds a better service elsewhere. Another number I am
> trying to track is the useful life of the v1s - projected to last 5
> years. There are 70+% of the first launch still operational. (
> https://twitter.com/VirtuallyNathan is an ongoing sump of info)
>
> [1] https://twitter.com/JackKuhr/status/1652466221390913536
>
> --
> AMA March 31: https://www.broadband.io/c/broadband-grant-events/dave-taht
> Dave Täht CEO, TekLibre, LLC
> _______________________________________________
> Starlink mailing list
> Starlink@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/starlink
next prev parent reply other threads:[~2023-04-30 21:48 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-30 12:48 Dave Taht
2023-04-30 21:48 ` David Lang [this message]
2023-05-03 2:42 ` Luis A. Cornejo
2023-05-03 2:45 ` Dave Taht
[not found] <mailman.9.1682956802.8936.starlink@lists.bufferbloat.net>
2023-05-01 21:01 ` David P. Reed
2023-05-01 21:05 ` Freddie Cash
2023-05-01 21:09 ` David Lang
2023-05-01 22:32 ` Ulrich Speidel
2023-05-01 22:45 ` David Lang
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=3nrs5r7q-r5q6-0rqo-7q60-3n095308s27s@ynat.uz \
--to=david@lang.hm \
--cc=dave.taht@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