Starlink has bufferbloat. Bad.
 help / color / mirror / Atom feed
From: David Lang <david@lang.hm>
To: Sebastian Moeller <moeller0@gmx.de>
Cc: J Pan <Pan@uvic.ca>, Hesham ElBakoury <helbakoury@gmail.com>,
	5grm-satellite@ieee.org,
	Dave Taht via Starlink <starlink@lists.bufferbloat.net>
Subject: [Starlink] Re: How Starcloud Is Bringing Data Centers to Outer Space | NVIDIA Blog
Date: Wed, 19 Nov 2025 19:47:39 -0700 (MST)	[thread overview]
Message-ID: <303soooo-1s37-3101-p38s-18580294596o@ynat.uz> (raw)
In-Reply-To: <D95910C3-B8CD-4DF8-ADFE-3AA7E4F45077@gmx.de>

Sebastian Moeller wrote:

> Looks pretty much like a solution in search of a problem.

that's my take on it, at least in terms of a single monolithic station. One 
thing that nobody here mentioned is the problem in stabilizing such large 
structures, occellations, orbital raising burns, etc.

Elon Musk proposed a slightly different take, take the platform that they will 
be using for their full size v2 (or v3) starlinks and add more processing 
instead of as many data links. a bunch of those in a loose cluster instead of a 
tightly correlated cluster could be interesting (and far more likely)

David Lang

  reply	other threads:[~2025-11-20  2:47 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-11-19 15:52 [Starlink] " Hesham ElBakoury
2025-11-19 16:09 ` [Starlink] " J Pan
2025-11-19 16:34   ` Hesham ElBakoury
2025-11-19 16:54     ` J Pan
2025-11-19 16:41   ` Kenneth Porter
2025-11-19 16:42   ` Gert Doering
2025-11-19 16:58     ` J Pan
2025-11-19 18:18   ` Sebastian Moeller
2025-11-20  2:47     ` David Lang [this message]
     [not found]   ` <830.1763590830@obiwan.sandelman.ca>
2025-11-20  4:33     ` J Pan
     [not found] <176362217876.1303.16872643449823923048@gauss>
2025-11-20 11:10 ` David Fernández

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=303soooo-1s37-3101-p38s-18580294596o@ynat.uz \
    --to=david@lang.hm \
    --cc=5grm-satellite@ieee.org \
    --cc=Pan@uvic.ca \
    --cc=helbakoury@gmail.com \
    --cc=moeller0@gmx.de \
    --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