From mboxrd@z Thu Jan 1 00:00:00 1970 Authentication-Results: mail.toke.dk; spf=pass smtp.mailfrom=; dkim=pass header.d=falco.ca; arc=none (Message is not ARC signed); dmarc=pass (Used From Domain Record) header.from=falco.ca policy.dmarc=reject Received: from cmail.nextlayer.at (cmail.nextlayer.at [IPv6:2a01:190:1600:2164::25]) by mail.toke.dk (Postfix) with ESMTPS id B51ACD8C62C for ; Fri, 27 Feb 2026 16:15:09 +0100 (CET) Received: from [127.0.0.1] (localhost [127.0.0.1]) by localhost (Mailerdaemon) with ESMTPSA id 3936949DC5 for ; Fri, 27 Feb 2026 16:15:05 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=falco.ca; s=dkim0; t=1772205307; h=from:subject:date:message-id:to:mime-version:content-type: content-transfer-encoding:content-language:in-reply-to:references; bh=zzfwddofvoNp0pDJdsv0ofiRy8vM4cEuLbw5OJr9xbo=; b=eLot1p3QGif1KveVgBsCA64f9tBm1znnbIOCb01MV9D0hCidjR+dmti3qU6WHyjOPQ04jx wRH+0jKm7kMfJzroBRQWTE4HlicuabstKUXnyc00FZyBiXvWw/ASEBXSW7yb99jlslNvNF +YbB7QkAW2mnq4D2wk7f58WZWP6TsVyV129liEuZ5X6FLUSXbtK+aiMpD5XYo/NWAnAhSC Fj1Xdvf+M/YzZ0PrL8FJOPtfdT435C+w/qhDU1aBwkelgpMney7lrXOLLKZ33owypnUasF dqOVVDDa/dnkzbH47gtbGyIFgKH6Tc6ZPN5x4WSjryXv0bKgGtEprYOhZh1Ivw== Message-ID: <39021202-381e-4334-92d8-d7dc4f8dd30d@falco.ca> Date: Fri, 27 Feb 2026 16:15:03 +0100 MIME-Version: 1.0 User-Agent: Mozilla Thunderbird To: starlink@lists.bufferbloat.net References: <4f2228ec-042a-48ed-8946-a6c37f10ca94@rogers.com> <2o0r5r7s-0750-o2p1-7738-n4n88q9093qs@ynat.uz> <69q3s580-8560-q213-2n61-o36qns8o6q4o@ynat.uz> <22f8dfbf-c99d-4d9e-9962-e37851ee1d17@auckland.ac.nz> <53546r56-154r-o38n-1ns2-8ponps4ss1o5@ynat.uz> <3e2d9c26-f468-4380-8c88-a76679248a16@thexlab.org> Content-Language: fr From: Daniel AJ Sokolov In-Reply-To: <3e2d9c26-f468-4380-8c88-a76679248a16@thexlab.org> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Last-TLS-Session-Version: TLSv1.3 Message-ID-Hash: YOBCQEAOFVU7E6P4U7TDMR2HXGPCTQDM X-Message-ID-Hash: YOBCQEAOFVU7E6P4U7TDMR2HXGPCTQDM X-MailFrom: daniel@falco.ca X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; loop; banned-address; emergency; member-moderation; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header X-Mailman-Version: 3.3.10 Precedence: list Subject: [Starlink] Re: Why Data Centers In Space Won't Work [Yet] (A non-canonical list). List-Id: "Starlink has bufferbloat. Bad." Archived-At: List-Archive: List-Help: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: On 2/27/26 at 15:26, Sascha Meinrath via Starlink wrote: > Hi everyone, > > Synthesizing from what we know thus far, I think it would be helpful to > have a topline bullet list of the major issues detrimentally impacting > the viability of data centers in space. > > I remain highly skeptical of the concept, given today's technological > realities, and feel that there would be utility in having a quick > reference of the major shortcomings that need to be overcome. > > Here's a starting point for some of the major limitations to data > centers in space (please add, though keep bullets pithy): > > 1. Thermal cooling/heat dissipation > 2. Radiation hardening > 3. Launch costs > 4. Upgrade/maintenance costs > 5. Kessler syndrome/ablation cascade risks (& collision avoidance) > 6. Power generation/storage > 7. Latency/bandwidth > 8. Risk-adjusted ROI > 9. ??? Any satellite in LEO is in view for a few minutes only. New security threats (jamming, physical attacks, can't replace components that have security flaws) There will also be resistance from concerned citizens, bussinesses, and governments due to factors including, but not limited to: Disposal (damage to the atmosphere of a million satellites burns up there) Negative effects on astronomy A million satellites will make it harder to launch rockets, I presume. Unclear jurisdiction/limited enforcement capability BR Daniel AJ