Starlink has bufferbloat. Bad.
 help / color / mirror / Atom feed
From: David Collier-Brown <davec-b@rogers.com>
To: starlink@lists.bufferbloat.net
Subject: [Starlink] Re: Data centers are racing to space — and regulation can’t keep up
Date: Wed, 25 Feb 2026 09:30:41 -0500	[thread overview]
Message-ID: <4f2228ec-042a-48ed-8946-a6c37f10ca94@rogers.com> (raw)
In-Reply-To: <CAFvDQ9p23VY84BxJ0k3eL2UdpB3_9d7_Fg+oTaZ+DrySeMDaYQ@mail.gmail.com>

I looked at the radiative cooling problem, and immediately thought ... 
"these things can't possibly work. What is the hidden agenda here?"

Anyone know of alternative reasons for this project? It's from Mr Musk, 
so weird is quite possible.

--dave

On 2/25/26 09:05, Hesham ElBakoury via Starlink wrote:
> https://restofworld.org/2026/orbital-data-centers-ai-sovereignty/?utm_source=tldrnewsletter
>
>
> Hesham
> _______________________________________________
> Starlink mailing list -- starlink@lists.bufferbloat.net
> To unsubscribe send an email to starlink-leave@lists.bufferbloat.net

-- 
David Collier-Brown,         | Always do right. This will gratify
System Programmer and Author | some people and astonish the rest
davecb@spamcop.net           |              -- Mark Twain


  reply	other threads:[~2026-02-25 14:30 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-02-25 14:05 [Starlink] Data centers are racing to space — and regulation can’t keep up Hesham ElBakoury
2026-02-25 14:30 ` David Collier-Brown [this message]
2026-02-25 14:32   ` [Starlink] Re: Data centers are racing to space ??? and regulation can???t " Gert Doering
2026-02-25 14:42   ` [Starlink] Re: Data centers are racing to space — and regulation can’t " Hesham ElBakoury
2026-02-26  4:28     ` J Pan
     [not found]       ` <CAFvDQ9p68AFJ5cQTpyx=HkA2Cf6r1m6F3ssaJh-OJK4kqK=PDQ@mail.gmail.com>
2026-02-26  5:54         ` J Pan
2026-02-26  6:01           ` Hesham ElBakoury
2026-02-25 14:50   ` Daniel AJ Sokolov
2026-02-26  1:33     ` David Lang
2026-02-26  2:38       ` Nick Matthews
2026-02-26  4:39         ` David Lang
2026-02-26 11:54           ` Mark Handley
2026-02-26 13:36             ` Vint Cerf
2026-02-26 13:56               ` Nitinder Mohan
2026-02-26 21:36                 ` Ulrich Speidel
2026-02-26 23:02                   ` Brandon Butterworth
2026-02-26 23:16                     ` Nitinder Mohan
2026-02-26 23:44                       ` Ulrich Speidel
2026-02-27  1:01                         ` Joe Hamelin
2026-02-27  1:47                           ` David Lang
2026-02-27 14:26                             ` [Starlink] Why Data Centers In Space Won't Work [Yet] (A non-canonical list) Sascha Meinrath
2026-02-27 15:07                               ` [Starlink] " David Lang
2026-02-27 15:15                               ` Daniel AJ Sokolov
2026-02-27 15:22                                 ` Gert Doering
2026-02-26 14:14               ` [Starlink] Re: Data centers are racing to space — and regulation can’t keep up Mark Handley
2026-02-26 18:01             ` David Lang
2026-02-25 20:26   ` Brandon Butterworth
2026-02-26  1:28   ` David Lang
2026-02-26  4:49 ` 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=4f2228ec-042a-48ed-8946-a6c37f10ca94@rogers.com \
    --to=davec-b@rogers.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