From: Sebastian Moeller <moeller0@gmx.de>
To: Daniel AJ Sokolov <daniel@sokolov.eu.org>
Cc: Mike Puchol <mike@starlink.sx>, starlink@lists.bufferbloat.net
Subject: Re: [Starlink] Starlink for Tonga?
Date: Tue, 8 Feb 2022 16:22:02 +0100 [thread overview]
Message-ID: <3E093B0D-3916-4E0B-8F30-4C841E419395@gmx.de> (raw)
In-Reply-To: <31598414-9e85-0c6e-653d-22a6a4dc2392@sokolov.eu.org>
Nice, well-written article in German about this topic, https://www.heise.de/news/Starlink-fuer-Tongas-Internet-Zu-wenig-zu-spaet-6355794.html which feels based on information also discussed in this thread ;)
Regards
Sebastian
> On Feb 8, 2022, at 10:05, Daniel AJ Sokolov <daniel@sokolov.eu.org> wrote:
>
> On 2022-02-08 at 01:58, Mike Puchol wrote:
>> In the Equator, the GSO protection band starts due East, and goes all
>> the way across the sky due West. It also takes out 37° of visible sky
>> at zenith.
>
> Thank you.
>
> If it goes all the way from East to West, how can one run any Starlink there?
>
> Does the protection area go from East to West via North, but Starlink could use East to West via South? Or the other way round?
>
> Or is the protection band only at certain angles off the ground?
>
> I think I get the 37° at Zenit - Zenit +18 and -18.
>
> Thank you!
> Daniel
> _______________________________________________
> Starlink mailing list
> Starlink@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/starlink
next prev parent reply other threads:[~2022-02-08 15:22 UTC|newest]
Thread overview: 49+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-07 18:50 Daniel AJ Sokolov
2022-02-07 18:51 ` Nathan Owens
2022-02-07 19:05 ` Christian von der Ropp
2022-02-07 19:06 ` Nathan Owens
2022-02-07 20:38 ` Ulrich Speidel
2022-02-07 20:44 ` Ulrich Speidel
2022-02-10 7:53 ` Ulrich Speidel
2022-02-07 21:18 ` Ben Greear
2022-02-07 21:24 ` David Lang
2022-02-07 21:36 ` Mike Puchol
2022-02-07 22:22 ` Ulrich Speidel
2022-02-07 22:29 ` Mike Puchol
2022-02-07 23:36 ` Ulrich Speidel
2022-02-07 23:47 ` David Lang
2022-02-08 0:20 ` Ulrich Speidel
2022-02-08 1:20 ` David Lang
2022-02-08 4:46 ` Inemesit Affia
2022-02-08 6:25 ` Daniel AJ Sokolov
2022-02-08 7:30 ` Ulrich Speidel
2022-02-08 7:49 ` Daniel AJ Sokolov
2022-02-08 8:22 ` Ulrich Speidel
2022-02-08 8:47 ` Mike Puchol
2022-02-08 8:49 ` Daniel AJ Sokolov
2022-02-08 8:58 ` Mike Puchol
2022-02-08 9:05 ` Daniel AJ Sokolov
2022-02-08 9:10 ` Mike Puchol
2022-02-08 15:22 ` Sebastian Moeller [this message]
2022-02-08 10:11 ` Ulrich Speidel
2022-02-08 13:50 ` Christian von der Ropp
2022-02-08 15:28 ` Mike Puchol
2022-02-08 16:25 ` Dave Taht
2022-02-08 18:20 ` Gary E. Miller
2022-02-08 19:12 ` David Lang
2022-02-09 12:09 ` Ulrich Speidel
2022-02-09 19:28 ` [Starlink] Sunburp kills 40 starlink satellites Doc Searls
2022-02-09 19:51 ` Michael Richardson
2022-02-09 12:58 ` [Starlink] Starlink for Tonga? Ulrich Speidel
2022-02-18 5:04 ` Daniel AJ Sokolov
2022-02-18 7:27 ` Mike Puchol
2022-02-18 9:01 ` Ulrich Speidel
2022-04-19 11:57 ` Mike Puchol
2022-04-19 12:06 ` Dave Taht
2022-04-19 12:43 ` Ulrich Speidel
2022-04-20 1:06 ` Ulrich Speidel
2022-04-20 1:14 ` Jeremy Austin
2022-02-18 10:27 ` Ulrich Speidel
2022-02-18 12:48 ` Rich Brown
2022-02-18 15:43 ` Nathan Owens
2022-02-18 10:29 ` Ulrich Speidel
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=3E093B0D-3916-4E0B-8F30-4C841E419395@gmx.de \
--to=moeller0@gmx.de \
--cc=daniel@sokolov.eu.org \
--cc=mike@starlink.sx \
--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