Starlink has bufferbloat. Bad.
 help / color / mirror / Atom feed
From: Nathan Owens <nathan@nathan.io>
To: Bruce Perens <bruce@perens.com>
Cc: Dave Taht via Starlink <starlink@lists.bufferbloat.net>
Subject: Re: [Starlink] Fondag
Date: Wed, 26 Apr 2023 16:09:06 -0700	[thread overview]
Message-ID: <CALjsLJuQXrpK_+0EAZ6bez=np+nD73qSR=-MHYkXtP25WTh5MQ@mail.gmail.com> (raw)
In-Reply-To: <CALjsLJuxeHKL8fR2f-_4a6mxeOy5T3Q30G4O7mycZtha_CN6qQ@mail.gmail.com>


[-- Attachment #1.1: Type: text/plain, Size: 1109 bytes --]

 It's also interesting that SpaceX has gone through all of this before...
https://youtu.be/0xWRhKB3JTM?t=1340

On Wed, Apr 26, 2023 at 3:35 PM Nathan Owens <nathan@nathan.io> wrote:

> Only some small portion of the pad was Fondag -- seen here
> [image: Screenshot 2023-04-26 at 3.35.22 PM.png]
>
>
> Good video: https://www.youtube.com/watch?v=zKhJwWymJWE
>
> On Wed, Apr 26, 2023 at 3:30 PM Bruce Perens via Starlink <
> starlink@lists.bufferbloat.net> wrote:
>
>> I found it interesting that the pad was constructed of Fondag. This is
>> pure calcium aluminate cement. The cement and aggregate are both made of
>> the same clinker, there's just a difference in size of the particles. The
>> aggregate doesn't simply have a physical bond to the cement, there is a
>> chemical bond as well. The aggregate and cement are non-porous. Fondag can
>> resist thermal cycling from -395 to 2000 F. It doesn't shed lime.
>> _______________________________________________
>> Starlink mailing list
>> Starlink@lists.bufferbloat.net
>> https://lists.bufferbloat.net/listinfo/starlink
>>
>

[-- Attachment #1.2: Type: text/html, Size: 2066 bytes --]

[-- Attachment #2: Screenshot 2023-04-26 at 3.35.22 PM.png --]
[-- Type: image/png, Size: 6917754 bytes --]

  reply	other threads:[~2023-04-26 23:09 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-24 14:12 [Starlink] some post Starship launch thoughts 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
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 [this message]
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

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='CALjsLJuQXrpK_+0EAZ6bez=np+nD73qSR=-MHYkXtP25WTh5MQ@mail.gmail.com' \
    --to=nathan@nathan.io \
    --cc=bruce@perens.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