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] I still dream of an tiny on-orbit repair and inspection robot
Date: Wed, 19 Jun 2024 10:31:16 -0700	[thread overview]
Message-ID: <CAA93jw4+nUtr_yLSKiwGa57AzvwerL2-HpUXd07agaPRBO-nfw@mail.gmail.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 782 bytes --]

https://www.npr.org/2024/06/19/nx-s1-5010440/nasa-has-delayed-the-undocking-of-boeings-starliner-capsule-until-next-week

Not just for this, but for starship, to inspect the tiles, nestled perhaps
in the engine dome during launch. It could fly out and magneticaly attach?

Something like that might have helped columbia, also.

Having to fire the thrusters and measure the effect on the ISS to see if
they are working strikes me as more difficult than direct observation.

There does seem to still be a dragon capsule attached to the ISS... that
could possibly be used for recovery if starliner's problems are more severe
than being indicaated.
-- 
https://www.linkedin.com/feed/update/urn:li:activity:7203400057172180992/
Donations Drive.
Dave Täht CSO, LibreQos

[-- Attachment #2: Type: text/html, Size: 1340 bytes --]

             reply	other threads:[~2024-06-19 17:31 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-19 17:31 Dave Taht [this message]
2024-06-19 18:44 ` Kenneth Porter
2024-06-24 10:39 ` [Starlink] Jamaican Starlink Outages and a hint of shared infrastructure Inemesit Affia
2024-06-24 14:42   ` J Pan
2024-06-24 22:19     ` Ulrich Speidel
2024-06-25  3:42       ` David Lang
2024-06-25  4:34         ` Ulrich Speidel
2024-06-25  5:37         ` Sebastian Moeller
2024-06-25  6:54           ` Gert Doering
2024-06-25  7:26             ` Sebastian Moeller
2024-06-25 19:07       ` J Pan

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=CAA93jw4+nUtr_yLSKiwGa57AzvwerL2-HpUXd07agaPRBO-nfw@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