this post was submitted on 01 Jan 2024
201 points (93.5% liked)

Ukraine

8285 readers
574 users here now

News and discussion related to Ukraine

*Sympathy for enemy combatants is prohibited.

*No content depicting extreme violence or gore.

*Posts containing combat footage should include [Combat] in title

*Combat videos containing any footage of a visible human must be flagged NSFW

Server Rules

  1. Remember the human! (no harassment, threats, etc.)
  2. No racism or other discrimination
  3. No Nazis, QAnon or similar
  4. No porn
  5. No ads or spam
  6. No content against Finnish law

Donate to support Ukraine's Defense

Donate to support Humanitarian Aid


founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
[–] partial_accumen@lemmy.world 28 points 10 months ago (4 children)

I've heard a couple versions of this story. One is the story in the post, the other is that Crimea was not covered by Starlink, and Ukraine tried to get it covered and Musk wouldn't.

Do we have a definitive source that can speak to which occurred?

[–] rsuri@lemmy.world 26 points 10 months ago (1 children)

From what I can gather from various sources (most detailed one here: https://www.businessinsider.com/elon-musk-admits-thwarting-ukraine-attack-not-activating-starlink-satellites-2023-9?op=1)

  1. Elon's biographer Isaacson says he turned it off as the Ukrainian ships were approaching Sevastopol, following a call with the Russian ambassador who he told about it(!!?), resulting in a nuclear threat. Ukrainians begged him to turn it back on and he refuses.
  2. Elon has denied the first part, saying it was never turned on, only acknowledging the call to turn it on and his refusal to do so.

I'm not sure which to believe. Isaacson's account is detailed and I doubt it's made up, but perhaps he misunderstood something. At the same time, turning it off seems to require Elon to have foreknowledge of the attack which seems unlikely, though plausible.

[–] NotMyOldRedditName@lemmy.world 8 points 10 months ago* (last edited 10 months ago)

Issac corrected the story and said he was wrong. His stance is it was never on. Musk refused to turn it on.

So either Issac got it wrong and the correction is legit. Or Issac is now covering his ass and willing to lie, and lying would be bad for his credibility.

[–] Kecessa@sh.itjust.works 20 points 10 months ago (1 children)
[–] Thief_of_Crows@sh.itjust.works 0 points 10 months ago (1 children)

Ah yes, let's ask the most vain man on earth if he did a highly newsworthy thing. I hope he doesn't lie about this like he does pretty much everything else.

[–] Kecessa@sh.itjust.works 1 points 10 months ago (1 children)

Eh... In this case that lie could (should) have put him in major trouble considering he got in the way of an attack by an ally of the country he resides in.

[–] Thief_of_Crows@sh.itjust.works 0 points 10 months ago

Not helping your countries ally bomb someone is in no way illegal. In fact, it's a lot more likely that the reverse will be true. Bombing people is bad, as it turns out.

[–] massive_bereavement@kbin.social 6 points 10 months ago (1 children)

Musk's official biographer explained that there was a point where he had to take a decision of either allow it or not, and a Russian official discouraged it on the basis that there would be a nuclear escalation.

Allegedly, someone in a 5 point building got super pissed by the fact that a rich guy got to call it off, jumping over them and the Prez himself.

[–] FaceDeer@kbin.social 2 points 10 months ago

The DoD has since signed contracts with Starlink for service. But they hadn't at the time yet so I don't see why the Pentagon or American president would be involved in the decision.