From: Alexandre Petrescu <alexandre.petrescu@gmail.com>
To: starlink@lists.bufferbloat.net
Subject: Re: [Starlink] Starship's 4th flight test was magnificent
Date: Mon, 10 Jun 2024 10:57:27 +0200 [thread overview]
Message-ID: <7a905c03-a3b2-477c-acd1-ec05d60e3862@gmail.com> (raw)
In-Reply-To: <CAA93jw6A4TNBL5zBFsrJwi3AOjbjun2B98fjyAc3NY0BJsLUPA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1843 bytes --]
Le 10/06/2024 à 01:50, Dave Taht via Starlink a écrit :
>
> [...] seeing starlink maintain connectivity through nearly it all of
> that plasma was amazing, too.
I dont understand: the rocket body and head ('starship') where
connected to starlink sats during flight? Wouldnt be enough to transmit
straight to ground? Or maybe the entire trajectory is too long too
distanced from ground receivers?
Alex
> To be massively cheered up about spaceflight, hit starlink's web site
> for the video. It is hard to imagine them attempting a catch of the
> booster for flight 5, that close to boca chica, but...
>
> But that left questions for me. How much overweight are Starship and
> the booster now? How much payload can they actually push to an orbit
> suitable for deploying starlink? When will they attempt payloads?
>
> The second set of questions are that the newer, larger Starlink
> satellites were designed, oh, 4 years ago? with about 4x the capacity
> of the existing ones, and I imagine (and hope) that they have been
> continually redesigned with an eye to latency now, as well as
> capacity. Seeing something like fq_codel actually make orbit would be
> a capstone to my career, when I started off wanting to be an "orbital
> mechanic" in the first place but exited entirely after challenger
> went down...
>
> Lastly, I couldn't help but imagine small repair robots deploying once
> in orbit to get a full view of every tile on starship, and perhaps
> effect repairs. Call 'em Hewey, Duey and Louie....
>
> Ad Astra!
>
> --
> https://www.linkedin.com/feed/update/urn:li:activity:7203400057172180992/
> Donations Drive.
> Dave Täht CSO, LibreQos
>
> _______________________________________________
> Starlink mailing list
> Starlink@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/starlink
[-- Attachment #2: Type: text/html, Size: 3658 bytes --]
next prev parent reply other threads:[~2024-06-10 8:57 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-09 23:50 Dave Taht
2024-06-10 0:15 ` Ulrich Speidel
2024-06-10 2:22 ` Michael Richardson
2024-06-10 10:51 ` Ulrich Speidel
2024-06-10 12:04 ` David Lang
2024-06-10 12:15 ` Ulrich Speidel
2024-06-10 2:38 ` David Lang
2024-06-10 11:04 ` Ulrich Speidel
2024-06-10 12:06 ` David Lang
2024-06-10 12:21 ` Ulrich Speidel
2024-06-10 8:57 ` Alexandre Petrescu [this message]
2024-06-10 9:49 ` David Lang
2024-06-10 13:22 ` Alexandre Petrescu
2024-06-10 13:37 ` 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=7a905c03-a3b2-477c-acd1-ec05d60e3862@gmail.com \
--to=alexandre.petrescu@gmail.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