Starlink has bufferbloat. Bad.
 help / color / mirror / Atom feed
From: Ulrich Speidel <u.speidel@auckland.ac.nz>
To: starlink@lists.bufferbloat.net
Subject: Re: [Starlink] a bit more starship news
Date: Tue, 2 May 2023 10:32:49 +1200	[thread overview]
Message-ID: <910f6b3e-56ec-63a3-dcda-233ea02c162f@auckland.ac.nz> (raw)
In-Reply-To: <o66o4sq6-nps4-s337-2p7p-qp68osns922p@ynat.uz>

I'd add that with what is probably a couple of million subscribers 
worldwide by now at US$100/month and growing fast, it gives you a fair 
idea as to how much you can accomplish with $200 million or so a month 
at your disposal. I remember O3b putting its initial constellation into 
orbit at around $1.2 billion - half a year's worth of Starlink income at 
most - but a multi-year endeavour. You can blow up a lot of launch pads 
and rockets for that, especially if you build them cheap.

On 2/05/2023 9:09 am, David Lang via Starlink wrote:
> On Mon, 1 May 2023, David P. Reed via Starlink wrote:
>
>>> 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.
>
> that it earns more money than it spent in that 3 month period, and 
> expected to do the same in 2023.
>
> SpaceX is private (so it doesn't have to impress the Wall Street 
> clueless folks), it deosn't get 'cost plus' contracts. There is far 
> less incentive to do creative accounting than if either of these were 
> true.
>
> David Lang
>
> _______________________________________________
> Starlink mailing list
> Starlink@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/starlink
>
>
> _______________________________________________
> Starlink mailing list
> Starlink@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/starlink
>
-- 
****************************************************************
Dr. Ulrich Speidel

School of Computer Science

Room 303S.594 (City Campus)

The University of Auckland
u.speidel@auckland.ac.nz
http://www.cs.auckland.ac.nz/~ulrich/
****************************************************************




  reply	other threads:[~2023-05-01 22:32 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
2023-05-01 21:05   ` Freddie Cash
2023-05-01 21:09   ` David Lang
2023-05-01 22:32     ` Ulrich Speidel [this message]
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=910f6b3e-56ec-63a3-dcda-233ea02c162f@auckland.ac.nz \
    --to=u.speidel@auckland.ac.nz \
    --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