Starlink has bufferbloat. Bad.
 help / color / mirror / Atom feed
From: Larry Press <lpress@csudh.edu>
To: Dave Taht via Starlink <starlink@lists.bufferbloat.net>
Subject: Re: [Starlink] apnic piece on starlink
Date: Sat, 8 Apr 2023 22:37:55 +0000	[thread overview]
Message-ID: <BN7PR03MB38591BB2D62823F27E192BA1C2979@BN7PR03MB3859.namprd03.prod.outlook.com> (raw)
In-Reply-To: <CAFvDQ9qBkssZLAC6yhQcVZ5xXksVKM4Ebc4FTfyyeEo86FhEEA@mail.gmail.com>

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

Some Aalyria speculation:

https://circleid.com/posts/20220927-aalyria-a-space-internet-startup-with-nearly-a-decades-worth-of-intellectual-property-from-alphabet


https://circleid.com/posts/20221028-is-defense-innovation-units-hybrid-space-architecture-arpanet-of-space-and-will-it-run-on-aalyria-spacetime

________________________________
From: Starlink <starlink-bounces@lists.bufferbloat.net> on behalf of Hesham ElBakoury via Starlink <starlink@lists.bufferbloat.net>
Sent: Saturday, April 8, 2023 12:07 PM
To: Michael Richardson <mcr@sandelman.ca>
Cc: Dave Taht via Starlink <starlink@lists.bufferbloat.net>; George Michaelson <ggm@apnic.net>
Subject: Re: [Starlink] apnic piece on starlink


Google Spinoff Aalyira salvaged Project Loon technology for US military.

https://arstechnica.com/gadgets/2022/09/google-spinoff-aalyria-salvages-project-loon-technology-for-the-us-military/amp<https://urldefense.com/v3/__https://arstechnica.com/gadgets/2022/09/google-spinoff-aalyria-salvages-project-loon-technology-for-the-us-military/amp__;!!P7nkOOY!rVo85S30MyBpyyRYIWPm-ZMmvG_iunvAYjKM21kYyMNa2nL-sOiuYRaKI9iVE8k8Ja-5EgIrovMcN6_VAIRayl7lig$>

Hesham

On Sat, Apr 8, 2023, 11:37 AM Michael Richardson via Starlink <starlink@lists.bufferbloat.net<mailto:starlink@lists.bufferbloat.net>> wrote:
David Lang via Starlink <starlink@lists.bufferbloat.net<mailto:starlink@lists.bufferbloat.net>> wrote:
    > Google shuttered project Loon (balloons to do this rather than UAVs) in
    > the last year or two

I heard that too, but also that some external entity then put up some money
and partnered to start it up again.

_______________________________________________
Starlink mailing list
Starlink@lists.bufferbloat.net<mailto:Starlink@lists.bufferbloat.net>
https://lists.bufferbloat.net/listinfo/starlink<https://urldefense.com/v3/__https://lists.bufferbloat.net/listinfo/starlink__;!!P7nkOOY!rVo85S30MyBpyyRYIWPm-ZMmvG_iunvAYjKM21kYyMNa2nL-sOiuYRaKI9iVE8k8Ja-5EgIrovMcN6_VAIS8tM8QEw$>

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

  parent reply	other threads:[~2023-04-08 22:38 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-05 20:09 Dave Taht
2023-04-07  9:55 ` Ulrich Speidel
2023-04-07 12:10   ` David Lang
2023-04-08 11:48     ` Ulrich Speidel
2023-04-08 17:37       ` David Lang
2023-04-08 18:37         ` Michael Richardson
2023-04-08 18:58           ` Hesham ElBakoury
2023-04-08 19:07           ` Hesham ElBakoury
2023-04-08 19:38             ` Dave Taht
2023-04-08 19:56               ` Hesham ElBakoury
2023-04-08 22:37             ` Larry Press [this message]
2023-04-10 16:07 David Fernández
2023-04-10 16:17 ` 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=BN7PR03MB38591BB2D62823F27E192BA1C2979@BN7PR03MB3859.namprd03.prod.outlook.com \
    --to=lpress@csudh.edu \
    --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