From: Ulrich Speidel <u.speidel@auckland.ac.nz>
To: Inemesit Affia <inemesitaffia@gmail.com>
Cc: Starlink <starlink@lists.bufferbloat.net>
Subject: [Starlink] Re: Starlink and Iran
Date: Thu, 15 Jan 2026 23:30:54 +1300 [thread overview]
Message-ID: <480e5761-b0b8-4bfb-87bb-a2079e3aef66@auckland.ac.nz> (raw)
In-Reply-To: <CAJEhh70xv2fPLj=BvYYsehAJrg7Eyg=q0dF0djX+ZBNWZXsD3Q@mail.gmail.com>
On 15/01/2026 11:06 pm, Inemesit Affia wrote:
>
>
> You don't often get email from inemesitaffia@gmail.com. Learn why this
> is important <https://aka.ms/LearnAboutSenderIdentification>
>
>
> Wrt to DTC, you'll need SIM's, e-SIM or physical. Much easier to make
> and ship than regular Starlink receiver. 4G requires mutual
> authentication.
Indeed, but that doesn't address problems related to user density - you
really can't support tens of thousands of people in a city that way. It
really only works for a handful of folks in a larger area at a time.
It's not an easily scalable solution.
One NZ currently handles perhaps a few thousand TXT messages (if that
many) via satellite a day in a country about 1/6th of the area of Iran
and are actively rationing the service by making it a premium product
even though few people can actually physically use it because
terrestrial coverage is so good. This simply doesn't scale to anywhere
near the needs of 90M+ Iranians, let alone in a few weeks.
>
> There's more spectrum to use if the towers are switched off as opposed
> to not terminating calls.
That's supposing someone will do SpaceX a favour and switch the local
base stations off in large numbers. Not realistic.
>
> Maybe it can be delivered as an app store app?
Getting e-Sims in is the easy part, getting the rest to work is the hard
bit. D2C for Iran is simply a non-starter - whatever is there in terms
of Dishys already dwarfs it in terms of capacity by orders of magnitude.
Iranian Internet users do need hope, but a lot of what's circulating out
there at the moment is hype and people's imagination having gone wild. A
lot of that is giving false hope, and that's probably the last thing
people need right now.
--
****************************************************************
Dr. Ulrich Speidel
School of Computer Science
Room 303S.594 (City Campus)
The University of Auckland
u.speidel@auckland.ac.nz
http://www.cs.auckland.ac.nz/~ulrich/
****************************************************************
next prev parent reply other threads:[~2026-01-15 10:31 UTC|newest]
Thread overview: 52+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-15 9:51 [Starlink] Starlink and Iran Ulrich Speidel
2026-01-15 10:06 ` [Starlink] " Inemesit Affia
2026-01-15 10:30 ` Ulrich Speidel [this message]
2026-01-15 10:44 ` Inemesit Affia
2026-01-15 11:16 ` Ulrich Speidel
2026-01-15 10:32 ` Inemesit Affia
2026-01-15 10:51 ` Ulrich Speidel
2026-01-15 11:17 ` David Lang
2026-01-15 11:59 ` Sauli Kiviranta
2026-01-15 14:08 ` David Lang
2026-01-15 15:29 ` Sauli Kiviranta
[not found] ` <3af2ac06-e098-4c79-869d-9c389959ca07@gmail.com>
[not found] ` <q9304244-661o-3qsr-o6rp-9q1nqq09r419@ynat.uz>
[not found] ` <4ba64a41-bbbf-4fb5-adb0-c77c15e4ca0f@gmail.com>
2026-01-15 16:20 ` Inemesit Affia
2026-01-15 20:12 ` Ulrich Speidel
2026-01-15 17:10 ` J Pan
2026-01-15 20:07 ` Ulrich Speidel
2026-01-15 21:47 ` Oleg Kutkov
2026-01-16 4:18 ` Ulrich Speidel
2026-01-16 8:12 ` Frantisek Borsik
2026-01-16 8:24 ` Inemesit Affia
-- strict thread matches above, loose matches on Subject: below --
2026-01-15 14:50 David Fernández
2026-01-15 16:11 ` Oleg Kutkov
2026-01-15 17:13 ` J Pan
[not found] <176849731431.1249.14387618908540773471@gauss>
2026-01-15 17:42 ` Colin_Higbie
2026-01-15 18:56 ` Jim Forster
2026-01-15 20:15 ` Ulrich Speidel
2026-01-15 20:27 ` Ulrich Speidel
2026-01-15 20:30 ` Hayden Simon
2026-01-15 21:06 ` Ulrich Speidel
2026-01-15 21:09 ` Hayden Simon
2026-01-15 21:20 ` Ulrich Speidel
2026-01-15 21:23 ` Hayden Simon
[not found] <176851123059.1249.8585659892308012167@gauss>
2026-01-15 21:49 ` Colin_Higbie
2026-01-15 23:15 ` Frantisek Borsik
2026-01-16 0:13 ` Ulrich Speidel
2026-01-16 1:29 ` David Lang
2026-01-16 22:55 ` Frantisek Borsik
2026-01-16 23:06 ` J Pan
[not found] ` <13187.1768590201@obiwan.sandelman.ca>
2026-01-16 23:30 ` Ulrich Speidel
2026-01-17 0:07 ` David Lang
2026-01-17 21:56 ` Ulrich Speidel
2026-01-19 20:39 ` David Lang
2026-01-28 3:09 ` Ulrich Speidel
2026-01-28 3:30 ` David Lang
2026-01-28 4:02 ` Mike Puchol
2026-01-28 9:05 ` Ulrich Speidel
2026-01-28 9:53 ` David Lang
2026-01-28 20:43 ` Ulrich Speidel
2026-01-28 20:55 ` David Lang
2026-01-17 18:32 ` Michael Richardson
2026-01-17 18:38 ` Inemesit Affia
2026-01-17 19:25 ` Michael Richardson
2026-01-17 22:12 ` 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=480e5761-b0b8-4bfb-87bb-a2079e3aef66@auckland.ac.nz \
--to=u.speidel@auckland.ac.nz \
--cc=inemesitaffia@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