From: Dave Taht <dave.taht@gmail.com>
To: starlink@lists.bufferbloat.net
Subject: [Starlink] starlink at sea
Date: Wed, 13 Jul 2022 17:20:43 -0700 [thread overview]
Message-ID: <CAA93jw6m4_u+Cs+++2HqJrHROK-=VW8BdDYtD9CdZHoMZA_Y7Q@mail.gmail.com> (raw)
Two notes about this article
https://www.royalcaribbeanblog.com/2022/06/28/i-tried-elon-musks-starlink-internet-royal-caribbean-cruise-ship
1) Joy of joys they used the new ookla speedtest, which shows upload
and download latency under load.
2) They show 6 starlink terminals on one side of the ship, and 6 on
the other side (unless it's a reversed image). While I can imagine
that the downlink can manage that many terminals close by (but how?),
I find it hard to conceive that the uplinks can co-exist emitting that
much energy so few feet apart. Are modern phased arrays that good? Has
anyone experimented with how closely placed two terminals can be?
--
FQ World Domination pending: https://blog.cerowrt.org/post/state_of_fq_codel/
Dave Täht CEO, TekLibre, LLC
next reply other threads:[~2022-07-14 0:20 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-14 0:20 Dave Taht [this message]
2022-07-14 0:31 ` David Lang
2022-07-14 0:36 ` Gary E. Miller
2022-07-14 0:40 ` David Lang
2022-07-14 0:59 ` Gary E. Miller
2022-07-14 1:36 ` David Lang
2022-07-14 5:46 ` Larry Press
2022-07-14 7:00 ` David Lang
2022-07-14 11:15 ` Mike Puchol
2022-07-14 11:32 ` Sebastian Moeller
2022-07-14 12:02 ` Mike Puchol
2022-07-14 12:34 ` Sebastian Moeller
2022-07-14 12:49 ` Nitinder Mohan
2022-07-14 12:57 ` Jared Mauch
2022-07-14 13:05 ` Nitinder Mohan
2022-07-14 13:33 ` Nitinder Mohan
2022-07-14 14:56 ` Mike Puchol
2022-07-14 15:28 ` Sebastian Moeller
2022-07-14 15:32 ` Nathan Owens
2022-07-27 21:17 ` Dave Taht
2024-07-02 20:40 Dave Taht
2024-07-03 3:40 ` Ulrich Speidel
2024-07-03 17:21 ` Larry Press
2024-07-03 4:21 ` Marc Blanchet
2024-07-03 4:26 ` J Pan
2024-07-03 17:06 ` Larry Press
2024-07-03 22:06 ` Michael Richardson
2024-07-14 19:32 ` J Pan
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='CAA93jw6m4_u+Cs+++2HqJrHROK-=VW8BdDYtD9CdZHoMZA_Y7Q@mail.gmail.com' \
--to=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