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] the website for the end of the world
Date: Tue, 19 Sep 2023 14:09:13 -0700	[thread overview]
Message-ID: <CAA93jw5L_t4ZdcCv8-ESegBm-o8_2UTWwD_Hw7qpxmUs7D7DrQ@mail.gmail.com> (raw)

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

John Carmack just kicked off a thoughtful thread over here:

https://twitter.com/ID_AA_Carmack/status/1704160299845071328

(Among other things, I would rather like to see DNS services hosted native
up there)

Starting point:
The idea that the internet was created to survive nuclear war is
apocryphal; packet routing does provide some resilience, but you will lose
internet in an apocalypse. Space based systems are interesting to consider
— they tend to be very reliant on ground systems, but it would be
technically elegant if packets from one ground station to another were
delivered directly, with no other ground interaction. LEO constellations
probably need near constant ground help to update orbital ephemeris, and
the orbits would decay in a few years anyway, but GEO sats could continue
operating for decades if their control software didn’t preclude it. There
should be off grid (or even in-space) servers connected to the satellite
networks at static IP addresses (so DNS isn’t required). The Website For
The End Of The World. What would a sparsely distributed group of apocalypse
survivors want to see there? A Wikipedia mirror and some type of forum for
communication, certainly. It seems like a good story element, but a little
real world LARPing along those lines would be fun. The tragedy would be
when all the terminals maintaining a fragile network of communication among
humanity shut down due to the account billing servers being unavailable.

<https://twitter.com/ID_AA_Carmack/status/1704160299845071328>


-- 
Oct 30: https://netdevconf.info/0x17/news/the-maestro-and-the-music-bof.html
Dave Täht CSO, LibreQos

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

             reply	other threads:[~2023-09-19 21:09 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-19 21:09 Dave Taht [this message]
2023-09-19 21:35 ` tom
2023-09-20  9:13 David Fernández
2023-09-21 13:59 ` Alexandre Petrescu
2023-09-21 16:04   ` Dave Taht

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=CAA93jw5L_t4ZdcCv8-ESegBm-o8_2UTWwD_Hw7qpxmUs7D7DrQ@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