From: Ulrich Speidel <u.speidel@auckland.ac.nz>
To: "starlink@lists.bufferbloat.net" <starlink@lists.bufferbloat.net>
Subject: [Starlink] Japan Times article
Date: Sat, 19 Aug 2023 00:59:47 +1200 [thread overview]
Message-ID: <4876d657-26d0-1c5d-9f2c-0d4ee86d5c9f@auckland.ac.nz> (raw)
Got my 15 seconds of fame in Japan today:
https://www.japantimes.co.jp/business/2023/08/18/tech/starlink-asia-pacific-expansion/
I'm getting quoted pretty accurately. Note that the Tongan eruption
aftermath part of the story has a few minor inaccuracies, though.
--
****************************************************************
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/
****************************************************************
reply other threads:[~2023-08-18 12:59 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=4876d657-26d0-1c5d-9f2c-0d4ee86d5c9f@auckland.ac.nz \
--to=u.speidel@auckland.ac.nz \
--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