Starlink has bufferbloat. Bad.
 help / color / mirror / Atom feed
From: Michael Richardson <mcr@sandelman.ca>
To: Bruce Perens <bruce@perens.com>, David Lang <david@lang.hm>,
	Dave Taht via Starlink <starlink@lists.bufferbloat.net>,
	Eugene Chang <eugene.chang@alum.mit.edu>
Subject: Re: [Starlink] some post Starship launch thoughts
Date: Wed, 26 Apr 2023 15:14:08 -0400	[thread overview]
Message-ID: <4197.1682536448@localhost> (raw)
In-Reply-To: <CAK2MWOuHbCHVNyY86g3UyfNZPSziDgNKmyyoDRi18zGMDgAeEQ@mail.gmail.com>

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


Bruce Perens via Starlink <starlink@lists.bufferbloat.net> wrote:
    > Once upon a time, there was a thing called Orion, which was supposed to be
    > a big heavy shield that would be propelled into space by setting off atomic
    > bombs on one side of it. Lots and lots of bombs. At some point people
    > thought they could make a shield good enough. What SpaceX puts in now is
    > going to be the closest we have come to Orion, just upside down.

For fun, read Charles Stross' Merchange Princes series.

Book "9", _Invisible Sun_, while a bit uneven, includes their Orion spacecraft.
They have the advantage that the can Jaunt to alternative universes before
doing all the atomic bombing, and then, once in orbit, Jaunt back.

ISS Astronaut in time line 2 (US) should have been given the line: "That's
not the moon"...


[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 511 bytes --]

  parent reply	other threads:[~2023-04-26 19:14 UTC|newest]

Thread overview: 38+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-24 14:12 Dave Taht
2023-04-24 15:16 ` Michael Richardson
2023-04-24 15:27   ` Dave Taht
2023-04-24 15:37     ` Michael Richardson
2023-04-24 15:49       ` Nathan Owens
2023-04-24 19:03   ` David Lang
2023-04-24 19:16 ` David Lang
2023-04-25  0:46   ` Eugene Chang
2023-04-25  2:20     ` David Lang
2023-04-25 22:31       ` Bruce Perens
2023-04-25 23:04         ` Eugene Chang
2023-04-25 23:22           ` David Lang
2023-04-25 23:55             ` Eugene Y Chang
2023-04-26 19:14         ` Michael Richardson [this message]
2023-04-25  1:01 ` Bruce Perens
2023-04-26 19:29 ` Dave Taht
2023-04-26 20:05   ` Sebastian Moeller
2023-04-26 20:41   ` Rodney W. Grimes
2023-04-26 21:05     ` Eugene Y Chang
2023-04-26 22:15       ` Mark Handley
2023-04-26 22:29         ` [Starlink] Fondag Bruce Perens
2023-04-26 22:32           ` Rodney W. Grimes
2023-04-26 22:35           ` Nathan Owens
2023-04-26 23:09             ` Nathan Owens
2023-04-27  3:42             ` David Lang
2023-04-26 21:10     ` [Starlink] some post Starship launch thoughts Dave Taht
2023-04-26 21:26       ` Eugene Chang
2023-04-26 22:31       ` Rodney W. Grimes
2023-04-26 22:38         ` Bruce Perens
2023-04-26 23:25         ` Eugene Chang
2023-04-27  3:44         ` David Lang
2023-04-27 14:09           ` Rodney W. Grimes
2023-04-24 16:02 David Fernández
     [not found] <mailman.798.1682383621.1222.starlink@lists.bufferbloat.net>
2023-04-25 20:40 ` David P. Reed
2023-04-25 21:31   ` Sauli Kiviranta
2023-04-25 22:37     ` David Lang
2023-05-11 16:24       ` Sauli Kiviranta
2023-04-25 22:33   ` 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=4197.1682536448@localhost \
    --to=mcr@sandelman.ca \
    --cc=bruce@perens.com \
    --cc=david@lang.hm \
    --cc=eugene.chang@alum.mit.edu \
    --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