Starlink has bufferbloat. Bad.
 help / color / mirror / Atom feed
From: Darrell Budic <budic@onholyground.com>
To: Dave Taht <dave.taht@gmail.com>
Cc: starlink@lists.bufferbloat.net
Subject: Re: [Starlink] Planetary Society podcast on SpaceX & EPA issues
Date: Fri, 12 May 2023 18:18:16 -0500	[thread overview]
Message-ID: <29410BC8-B70B-40FC-9885-513AC26F2147@onholyground.com> (raw)
In-Reply-To: <CAA93jw69XTa_-jM30N1F6cAU9J6kRVm3q6OC9ZR83rWrYbnXsQ@mail.gmail.com>

The TLDR; is probably:

- site originally used a sort of short form Environmental Impact Statement to certify for occasional falcon 9 launches, not exploding starship testing
- updates have been made to allow for the testing, and this is where the recent lawsuits are centered
- crazy things have been floated for the site (LNG shipping terminal, 250MW power plant) that would have required new evals
- lots of this is probably traceable to Musk’s lack of local PR and just trying to crash forward and the recent train derailments in the news raising awareness
- SpaceX seems to be realizing this site may not be what they need and may to be looking at doing more at Kennedy Space Center in the future
- if the lawsuit against the EPA stays in Washington DC, it may be trouble for SpaceX, if it moves to Texas at the EPAs request, it’s more likely to mean little overall

But you miss a lot of somewhat interesting policy and background on the Environmental angle, which turns out to be more involved than I’d have thought from a distance. 

Also nice that the Planetary Society posts a full transcript if you’d rather read/skim than listen.

> On May 12, 2023, at 4:53 PM, Dave Taht <dave.taht@gmail.com> wrote:
> 
> could you summarize?
> 
> On Fri, May 12, 2023 at 8:48 AM Darrell Budic via Starlink
> <starlink@lists.bufferbloat.net> wrote:
>> 
>> Some intersting coverage on the route SpaceX took with their Boca Chica site and environmental issues here:
>> 
>> https://www.planetary.org/planetary-radio/space-policy-edition-spacexs-starship-vs-the-environment-with-eric-roesch
>> _______________________________________________
>> Starlink mailing list
>> Starlink@lists.bufferbloat.net
>> https://lists.bufferbloat.net/listinfo/starlink
> 
> 
> 
> -- 
> Podcast: https://www.linkedin.com/feed/update/urn:li:activity:7058793910227111937/
> Dave Täht CSO, LibreQos


  parent reply	other threads:[~2023-05-12 23:18 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-12 15:48 Darrell Budic
     [not found] ` <CAA93jw69XTa_-jM30N1F6cAU9J6kRVm3q6OC9ZR83rWrYbnXsQ@mail.gmail.com>
2023-05-12 23:18   ` Darrell Budic [this message]
2023-05-12 23:37     ` David Lang
2023-05-12 23:40     ` Dave Taht
2023-05-13  5:22       ` Frantisek Borsik

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=29410BC8-B70B-40FC-9885-513AC26F2147@onholyground.com \
    --to=budic@onholyground.com \
    --cc=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