Starlink has bufferbloat. Bad.
 help / color / mirror / Atom feed
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: Mike Puchol <mike@starlink.sx>
Cc: Hesham ElBakoury <helbakoury@gmail.com>,
	Nathan Owens <nathan@nathan.io>,
	starlink <starlink@lists.bufferbloat.net>,
	e-impact@ietf.org
Subject: Re: [Starlink] DataCenters in Space (was Re: fiber IXPs in space)
Date: Thu, 20 Apr 2023 10:21:23 -0400	[thread overview]
Message-ID: <15416.1682000483@localhost> (raw)
In-Reply-To: <a7a7b63c-0fe2-4c96-9b2f-8687ebe34325@Spark>

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


Mike Puchol via Starlink <starlink@lists.bufferbloat.net> wrote:
    > but is sometimes  followed by a “wait… wat…” look. Other than the
    > inherent danger to humans, UV penetrates clouds nicely.

"Hey Kids, if you are gonna watch Youtube, remember to wear your UV sunscreen!"


--
Michael Richardson <mcr+IETF@sandelman.ca>   . o O ( IPv6 IøT consulting )
           Sandelman Software Works Inc, Ottawa and Worldwide





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

  reply	other threads:[~2023-04-20 14:21 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-13 16:34 [Starlink] fiber IXPs in space David Fernández
2023-04-13 17:22 ` Michael Richardson
2023-04-13 18:54   ` David Fernández
2023-04-13 20:01     ` Michael Richardson
2023-04-13 20:06       ` Tom Evslin
2023-04-19 23:34       ` [Starlink] DataCenters in Space (was Re: fiber IXPs in space) Michael Richardson
2023-04-20  1:12         ` tom
2023-04-20  1:16           ` Vint Cerf
     [not found]             ` <ZECsG+Ldro3V5+/4@faui48e.informatik.uni-erlangen.de>
2023-04-20  3:25               ` [Starlink] [E-impact] " Hesham ElBakoury
2023-04-20  5:43             ` Daniel Schien
2023-04-20  9:31               ` Chris Adams
2023-04-20 12:50                 ` Hesham ElBakoury
2023-04-20 12:51                   ` Hesham ElBakoury
2023-04-27  3:13                 ` Eugene Y Chang
2023-04-20 11:10               ` Hesham ElBakoury
2023-04-20 11:23                 ` Sebastian Moeller
2023-04-20 11:24                 ` David Lang
2023-04-20 12:06                 ` Dave Collier-Brown
2023-04-20 21:21                   ` Ulrich Speidel
2023-04-20 12:14                 ` tom
2023-04-20 14:36                 ` Rodney W. Grimes
2023-04-20 14:18               ` Michael Richardson
2023-04-27  3:50               ` David Lang
2023-04-20 11:25             ` [Starlink] " Hesham ElBakoury
2023-04-20 11:27               ` Nathan Owens
2023-04-20 11:34                 ` Mike Puchol
2023-04-20 14:21                   ` Michael Richardson [this message]
2023-04-20  4:33           ` Ulrich Speidel
2023-04-20 14:12             ` Michael Richardson

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=15416.1682000483@localhost \
    --to=mcr+ietf@sandelman.ca \
    --cc=e-impact@ietf.org \
    --cc=helbakoury@gmail.com \
    --cc=mike@starlink.sx \
    --cc=nathan@nathan.io \
    --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