From: Mike Puchol <mike@starlink.sx>
To: "Dave Täht via Starlink" <starlink@lists.bufferbloat.net>
Subject: Re: [Starlink] Starlink no longer available to the Ukrainian army?
Date: Fri, 14 Oct 2022 14:51:39 +0200 [thread overview]
Message-ID: <38522124-6d3b-4ac8-bb20-92bfa35dc9fe@Spark> (raw)
In-Reply-To: <8735bqpq1r.wl-jch@irif.fr>
[-- Attachment #1: Type: text/plain, Size: 2028 bytes --]
I would detach the outages from anything related to payments or claims by Elon. I put together a short thread on Twitter to explain the issues around providing service around the battle fronts:
https://twitter.com/mikepuchol/status/1578524400055648256
If anyone wants to dig into any particulars let me know.
If SpaceX suddenly turned off what in Ukraine is now an essential service and a military asset, based on some strong words thrown around, or questions around payments, it would be devastating for the credibility of Starlink as anything other than a consumer product.
My personal view is that SpaceX has the right to be fairly compensated for their contribution, just like the manufacturers of Javelins are not giving them away for free. What “fairly” means is where the conversation must happen. SpaceX was too generous early on and set expectations, and now seems to be moving to the other side of the spectrum in terms of their costs, with figures that seem, on the surface, unrealistic.
Best,
Mike
On Oct 14, 2022 at 14:07 +0200, Juliusz Chroboczek via Starlink <starlink@lists.bufferbloat.net>, wrote:
> As some of you recall, Elon Musk recently posted a tweet in which he
> recommends that Ukraine should capitulate to Russia. Andrij Melnyk, the
> Ukrainian Ambassador to Germany, replied in two words.
>
> https://twitter.com/melnykandrij/status/1576977000178208768
>
> A few days later, Musk announced that Starlink would no longer pay its
> fraction of the cost of deploying Starlink terminals with the Ukrainian
> Army, and that the US government, if it so wishes, should foot the bill.
>
> https://twitter.com/officejjsmart/status/1580782290849759232
>
> Perhaps unrelated, there are reports of Starlink outages in Ukraine.
>
> https://www.ft.com/content/9a7b922b-2435-4ac7-acdb-0ec9a6dc8397
>
> -- Juliusz
> _______________________________________________
> Starlink mailing list
> Starlink@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/starlink
[-- Attachment #2: Type: text/html, Size: 2691 bytes --]
next prev parent reply other threads:[~2022-10-14 12:52 UTC|newest]
Thread overview: 45+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-14 12:06 Juliusz Chroboczek
2022-10-14 12:45 ` David Lang
2022-10-14 13:05 ` Juliusz Chroboczek
2022-10-14 13:11 ` David Lang
2022-10-14 14:17 ` Mike Puchol
2022-10-14 18:26 ` Juliusz Chroboczek
2022-10-14 20:44 ` Mike Puchol
2022-10-16 17:31 ` Steve Stroh
2022-10-16 17:56 ` Dave Taht
2022-10-16 18:28 ` Vint Cerf
2022-10-14 12:51 ` Mike Puchol [this message]
2022-10-14 13:13 ` Juliusz Chroboczek
2022-10-14 14:15 ` Mike Puchol
2022-10-14 16:05 ` Juliusz Chroboczek
2022-10-14 17:13 ` Kurtis Heimerl
2022-10-14 17:28 ` David Lang
2022-10-14 18:16 ` Juliusz Chroboczek
2022-10-14 18:32 ` Larry Press
2022-10-14 19:32 ` Benjamin Henrion
2022-10-14 19:35 ` David Lang
2022-10-14 20:07 ` David Lang
2022-10-14 22:29 ` Dave Taht
2022-10-15 16:51 ` Larry Press
2022-10-16 6:42 ` Sebastian Moeller
2022-10-16 8:45 ` Bruce Perens
2022-10-16 16:31 ` Dave Taht
2022-10-16 17:00 ` Sebastian Moeller
2022-10-16 19:55 ` Brandon Butterworth
2022-10-16 20:25 ` Bruce Perens
2022-11-02 3:50 ` [Starlink] 25 years of open source - where we went wrong, and how to fix it Dave Taht
2022-10-14 19:13 ` [Starlink] Starlink no longer available to the Ukrainian army? tom
2022-10-14 19:41 ` David Lang
2022-10-14 20:09 ` Dave Taht
2022-10-16 17:50 ` Steve Stroh
2022-10-16 17:57 ` Nathan Owens
2022-10-16 18:01 ` Dave Taht
2022-10-16 18:29 ` Vint Cerf
2022-10-16 18:33 ` David Lang
2022-10-16 18:44 ` Sebastian Moeller
2022-10-16 19:03 ` Brandon Butterworth
2022-10-16 19:37 ` Ulrich Speidel
2022-10-16 19:51 ` David Lang
2022-10-16 20:37 ` Michael Richardson
2022-10-16 20:52 ` Bruce Perens
2022-10-16 22:17 ` Brandon Butterworth
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=38522124-6d3b-4ac8-bb20-92bfa35dc9fe@Spark \
--to=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