Starlink has bufferbloat. Bad.
 help / color / mirror / Atom feed
From: Dave Taht <dave.taht@gmail.com>
To: Dave Taht via Starlink <starlink@lists.bufferbloat.net>
Subject: [Starlink] starship launch attempt 8AM EST march 14th
Date: Wed, 13 Mar 2024 21:57:06 -0400	[thread overview]
Message-ID: <CAA93jw5+PVg6ndcjMJp1dr92BifNZvpFWFaokyOTz6gWvoCzdQ@mail.gmail.com> (raw)

For those of you not hitting reload on starship news by the minute...

https://www.spacex.com/launches/mission/?missionId=starship-flight-3

I had hoped to fly in for the party tonight, but alas - I can see them
not launching tomorrow as being likely but after a launch (perhaps by
the weekend) I am predicting success for all the mission objectives,
which are:

"The third flight test aims to build on what we’ve learned from
previous flights while attempting a number of ambitious objectives,
including the successful ascent burn of both stages, opening and
closing Starship’s payload door, a propellant transfer demonstration
during the upper stage’s coast phase, the first ever re-light of a
Raptor engine while in space, and a controlled reentry of Starship. It
will also fly a new trajectory, with Starship targeted to splashdown
in the Indian Ocean. This new flight path enables us to attempt new
techniques like in-space engine burns while maximizing public safety.

ok, ok, it´s possible the 2nd stage will burn up on re-entry due to
lost tiles, or they will find a truly impressive way to blow up the
main stage on re-entry also, but space is hard, and today I am putting
faith in luck - third time´s the charm!

-- 
https://www.youtube.com/watch?v=N0Tmvv5jJKs Epik Mellon Podcast
Dave Täht CSO, LibreQos

                 reply	other threads:[~2024-03-14  1:57 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=CAA93jw5+PVg6ndcjMJp1dr92BifNZvpFWFaokyOTz6gWvoCzdQ@mail.gmail.com \
    --to=dave.taht@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