Starlink has bufferbloat. Bad.
 help / color / mirror / Atom feed
From: Alexandre Petrescu <alexandre.petrescu@gmail.com>
To: starlink@lists.bufferbloat.net
Subject: Re: [Starlink] Elon Musk hooked up on Starlink in-flight, speaking at All-in Summit
Date: Fri, 15 Sep 2023 13:39:41 +0200	[thread overview]
Message-ID: <ddf20dbb-773d-4efe-b117-64342d817b52@gmail.com> (raw)
In-Reply-To: <CAJUtOOgRynAbmJFuW4X47kd_ZQGittxjTw3R7FPuggkusZpo_g@mail.gmail.com>

"Re: [Starlink] Elon Musk hooked up on Starlink in-flight, speaking at 
All-in Summit"

- maybe the airplane used this antenna from Ball aerospace?  (earlier 
topic 'Main hurdles...')

or maybe it was a starlink antenna recently announced in some country 
that is called "Flat High Performance hardware" and that is proposed for 
automobiles.

Alex

Le 13/09/2023 à 17:54, Frantisek Borsik via Starlink a écrit :
> Starting at 1:00, he has mentioned sub 20 ms latency, some other 
> airliners hooked up to Starlink as well:
>
> https://www.youtube.com/watch?v=tKqJ5-kkUGk
>
> If only someone from Starlink would listen to Dave and  plugged him in 
> to fix all that:
>
> https://www.youtube.com/watch?v=c9gLo6Xrwgw
>
>
>
> All the best,
>
> Frank
> Frantisek (Frank) Borsik
>
> https://www.linkedin.com/in/frantisekborsik
> Signal, Telegram, WhatsApp: +421919416714
> iMessage, mobile: +420775230885
> Skype: casioa5302ca
> frantisek.borsik@gmail.com
>
> _______________________________________________
> Starlink mailing list
> Starlink@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/starlink

      parent reply	other threads:[~2023-09-15 11:39 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-13 15:54 Frantisek Borsik
2023-09-14 17:44 ` Dave Taht
2023-09-14 20:39   ` Frantisek Borsik
2023-09-15 11:39 ` Alexandre Petrescu [this message]

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=ddf20dbb-773d-4efe-b117-64342d817b52@gmail.com \
    --to=alexandre.petrescu@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