From: "David P. Reed" <dpreed@deepplum.com>
To: starlink@lists.bufferbloat.net
Subject: Re: [Starlink] a bit more starship news
Date: Mon, 1 May 2023 17:01:51 -0400 (EDT) [thread overview]
Message-ID: <1682974911.992311793@apps.rackspace.com> (raw)
In-Reply-To: <mailman.9.1682956802.8936.starlink@lists.bufferbloat.net>
[-- Attachment #1: Type: text/plain, Size: 2490 bytes --]
> Date: Sun, 30 Apr 2023 14:48:51 -0700 (PDT)
> From: David Lang <david@lang.hm>
...
> 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
"Quarter of Starlink having positive cash flow" means what exactly? I.'ve never heard a quarter of a corporation having positive cash flow as any kind of business metric.
Of course, since Starlink and SpaceX are subject to completely weird accounting standards (including providing software assistance to Twitter for free, and other shenanigans in the accounting world according to Musk), it could mean anything.
I worked with Iridium and Motorola during the phase before it was sold for scrap to the DoD, essentially. What's fascinating is how "creative accounting" between then and the current Starlink continues to persist. Motorola's Chris Galvin was a lot like Musk w.r.t. not seeing clearly what was happening - he was isolated by sycophants who really wanted to believe that there was a business there. Then later Motorola completely screwed up its cellular tech business by betting against GPRS and the Europeans. Should have hedged and participated in the rapid cellular industry growth, but instead, basically drove a great tech company into the ground.
As a I watch Starlink and SpaceX play a shell game with their business economics, it's fascinating to watch a similar thing play out.
Especially watching the "fan boys and girls" get taken for a ride as the Iridium "fan boys and girls" did - including stunts like showing that you could make a phone call from Mt. Everest, as if that was gonna fix the underlying lack of business strategy for success.
The current version of this "fan thinking" is the idea that somehow the satellites can route packets among themselves and provide a low-latency, high-quality Internet access service. As Dave Taht points out, we don't see the customer churn rates as people discover the bufferbloat effects as the customers scale, and which are largely designed into the Starlink systems architecture (the satellites' packet routing architecture).
But yeah, we might send a few people to Mars to die there.
[-- Attachment #2: Type: text/html, Size: 4344 bytes --]
next parent reply other threads:[~2023-05-01 21:01 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.9.1682956802.8936.starlink@lists.bufferbloat.net>
2023-05-01 21:01 ` David P. Reed [this message]
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
2023-04-30 12:48 Dave Taht
2023-04-30 21:48 ` David Lang
2023-05-03 2:42 ` Luis A. Cornejo
2023-05-03 2:45 ` 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=1682974911.992311793@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