From: Hesham ElBakoury <helbakoury@gmail.com>
To: "OCP-TAP@OCP-All.groups.io" <OCP-TAP@ocp-all.groups.io>,
OCP-TAP-TSIAW@ocp-all.groups.io, 5grm-satellite@ieee.org,
Maksim Barodzka <mb@gpspatron.com>,
Dave Taht via Starlink <starlink@lists.bufferbloat.net>
Subject: [Starlink] GPS is becoming increasingly unreliable
Date: Tue, 23 Jun 2026 06:23:15 -0700 [thread overview]
Message-ID: <CAFvDQ9pNogtTa7dCR_sP1wCM1JrT9rjMcmHBS-010n1DSJF3qg@mail.gmail.com> (raw)
In article Zak Kassas, an electrical and computer engineer at the Ohio
State University explains how GPS works and how, increasingly, it doesn’t
<https://cm.theconversation.com/t/r-l-tujkidiy-bujydhdliu-u/>. He also lays
out the ways his lab and others around the world are working on
alternatives to the venerable – and indispensable – GPS system.
https://theconversation.com/from-hormuz-to-the-cockpit-how-warfare-and-criminal-activity-undermine-gps-and-the-race-to-safeguard-navigation-281106?utm_medium=article_native_share&utm_source=theconversation.com
Hesham
reply other threads:[~2026-06-23 13:23 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=CAFvDQ9pNogtTa7dCR_sP1wCM1JrT9rjMcmHBS-010n1DSJF3qg@mail.gmail.com \
--to=helbakoury@gmail.com \
--cc=5grm-satellite@ieee.org \
--cc=OCP-TAP-TSIAW@ocp-all.groups.io \
--cc=OCP-TAP@ocp-all.groups.io \
--cc=mb@gpspatron.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