Starlink has bufferbloat. Bad.
 help / color / mirror / Atom feed
From: Marc Blanchet <marc.blanchet@viagenie.ca>
To: David Lang <david@lang.hm>
Cc: Hesham ElBakoury <helbakoury@gmail.com>,
	Starlink <starlink@lists.bufferbloat.net>,
	5grm-satellite@ieee.org
Subject: Re: [Starlink] Alphabet spins off Starlink competitor Taara
Date: Mon, 17 Mar 2025 19:35:08 -0400	[thread overview]
Message-ID: <A5033C7E-3AC0-46A2-B25D-09E906729221@viagenie.ca> (raw)
In-Reply-To: <6nn799r0-q896-4osn-23no-733oorno0p55@ynat.uz>


> On Mar 17, 2025, at 18:50, David Lang via Starlink <starlink@lists.bufferbloat.net> wrote:
> 
> Hesham ElBakoury wrote:
> 
>> https://www.theverge.com/news/631049/alphabet-spins-off-starlink-competitor-taara?mc_cid=1a1e15a2db&mc_eid=105d343de1
> 
> Interesting, a laser in a professionally installed/aligned tower is going to be able to have a higher bandwidth than the starlink dishy.
> 
> but the claim that it will be far cheaper than Starlink?? that tower and a ground station that tracks the satellites in real time is going to be FAR more expensive than a dishy. Since it's going to be in motion at all times, it's got mechanical parts to wear out, and physically re-aiming a laser between connections (on both ends) is going to be a lot slower than electronic aiming of a phased array antenna.

Either I don't understand the article or your comment. But my interpretation of the article is that it is "just" (ground) lasers for trunk links between (ground) towers. No satellite involved. It is a replacement of either fibre or radio between (cell) towers. 

Marc.

> 
> As a community gateway where a lot of people share a single satellite connection, it could work, but even there I question if it would be cheaper.
> 
> There's also the question of the cost of satellites. Are they willing to take the Starlink approach of cheap satellites? or are they still thinking 'industry standard' where each satellite is far bigger, heavier, and more expensive?
> 
> David Lang
> 
> _______________________________________________
> Starlink mailing list
> Starlink@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/starlink


  parent reply	other threads:[~2025-03-17 23:35 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-03-17 19:36 Hesham ElBakoury
2025-03-17 22:50 ` David Lang
2025-03-17 23:02   ` Daniel AJ Sokolov
2025-03-17 23:10     ` David Lang
2025-03-17 23:25       ` J Pan
2025-03-18  0:47         ` David Lang
2025-03-17 23:35   ` Marc Blanchet [this message]
2025-03-18  0:49     ` David Lang
2025-03-18  5:22       ` Michael Richardson
2025-03-18  6:43         ` Mike Puchol
2025-03-18  7:56           ` Sebastian Moeller
2025-03-18 16:02           ` Steve Stroh
2025-03-18 17:44             ` Craig Polk
2025-03-18  6:25       ` Sebastian Moeller
2025-03-17 23:45 ` Eric Kuhnke
2025-03-17 23:54   ` Brandon Butterworth
2025-03-18  0:04     ` Eric Kuhnke

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=A5033C7E-3AC0-46A2-B25D-09E906729221@viagenie.ca \
    --to=marc.blanchet@viagenie.ca \
    --cc=5grm-satellite@ieee.org \
    --cc=david@lang.hm \
    --cc=helbakoury@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