this post was submitted on 01 Jan 2024
208 points (93.7% liked)
Ukraine
8740 readers
514 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 involved must be flagged NSFW
β Server Rules
- Remember the human! (no harassment, threats, etc.)
- No racism or other discrimination
- No Nazis, QAnon or similar
- No porn
- No ads or spam (includes charities)
- No content against Finnish law
π³π₯ Donate to support Ukraine's Defense
π³βοΈβοΈ Donate to support Humanitarian Aid
πͺ π«‘ Volunteer with the International Legionnaires
founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
I always got the sense from the story that Ukraine didn't know it wasn't going to work in Crimea. When they realized, they begged him to turn it back on, because they thought he turned it off.
But it was never on and he refused to turn it on.
They also knew they weren't allowed to use it that way and tried anyway.
If they hadn't known that it wasn't on then that would be a pretty big part of the screwup, I'm sure Starlink wasn't keeping it a secret that there was no service there.
Given the urgency of the request makes me think they didn't know.
I don't think we've ever gotten a reliable answer on if they knew or didn't though
Edit: E.g they've never admitted to a successful use in the region prior to that event to indicate it was actually on or attempted before.
Edit: I think they were also told it'd work in Ukraine, but maybe unknown to them that didn't include Russia controlled areas. I can see the mistake happening