From: Hesham ElBakoury <helbakoury@gmail.com>
To: David Lang <david@lang.hm>
Cc: Larry Press <lpress@csudh.edu>,
Dave Taht via Starlink <starlink@lists.bufferbloat.net>
Subject: Re: [Starlink] Starlink Reverse Engineering
Date: Fri, 8 Sep 2023 21:53:50 -0700 [thread overview]
Message-ID: <CAFvDQ9rL4hSmqdx1hsTxzKXYNHU14Q15k0ZGfvUN0NcreS0wyA@mail.gmail.com> (raw)
In-Reply-To: <65n6n1rq-589r-993r-nro5-55p3pq465o51@ynat.uz>
[-- Attachment #1: Type: text/plain, Size: 2040 bytes --]
This is what is in the MIT Technology Review report:
"*When the idea was first proposed in 2020
<https://www.technologyreview.com/2020/09/28/1008972/us-army-spacex-musk-starlink-satellites-gps-unjammable-navigation/>,
executives at SpaceX were open to the idea, says Humphreys. Then word came
from on high. “Elon told the leaders we spoke to: every other LEO [low
Earth orbit] communications network has gone into bankruptcy,” Humphreys
told MIT Technology Review. “And so we [SpaceX] have to focus completely on
staying out of bankruptcy. We cannot afford any distractions.*”
Heshamn
On Fri, Sep 8, 2023, 9:15 PM David Lang <david@lang.hm> wrote:
> On Sat, 9 Sep 2023, Larry Press via Starlink wrote:
>
> > Why does Elon Musk object to the use of Starlink for navigation?
>
> He hasn't said, but I suspect a couple reasons
>
> limitations on what SpaceX can do, orbital changes, protocol changes, etc
> could all affect people depending on something that Starlink wasn't
> intending to
> offer in the first place
>
> liability, what happens when the navigation gives the wrong location
> because
> of a change Starlink made.
>
> to use the satellite signals, you not only need the timing, you need
> rather
> precise orbital information. If the satellites are modifying their orbits
> autonomously, how does that information get to everyone?
>
> For normal Starlink purposes, the satellites determine which sat is
> covering
> what area on the ground and the ground stations can react to the different
> sats
> that they hear (beaming back on reciprical bearings or the beam info can
> be in
> the handshake)
>
> but navigation requires getting the signals from many sats at once to work
> out
> the timing between them
>
> note, I have no inside info, this is just my version of logical guessing.
>
> David Lang
>
> _______________________________________________
> Starlink mailing list
> Starlink@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/starlink
>
[-- Attachment #2: Type: text/html, Size: 2651 bytes --]
next prev parent reply other threads:[~2023-09-09 4:54 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-08 14:27 Hesham ElBakoury
2023-09-09 3:58 ` Larry Press
2023-09-09 4:15 ` David Lang
2023-09-09 4:53 ` Hesham ElBakoury [this message]
2023-09-14 9:14 ` Alexandre Petrescu
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=CAFvDQ9rL4hSmqdx1hsTxzKXYNHU14Q15k0ZGfvUN0NcreS0wyA@mail.gmail.com \
--to=helbakoury@gmail.com \
--cc=david@lang.hm \
--cc=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