Actually, I suspect he’s implying that nobody’s trying to assassinate Harris because all the democracy-hating assassins are on her side, or she’s the one setting them up, or something to that effect.
It’s still the sort of slander which in a reasonable world he’d be called on, but that seems unlikely
They certainly won’t be bored. Astronauts time on the ISS is a precious resource, and work will have been found for them even if they weren’t expected to be there
No, I’m arguing that the extra complexity is something to avoid because it creates new attack surfaces, new opportunities for bugs, and is very unlikely to accurately deal with all of the edge cases.
Especially when you consider that the behaviour we have was established way before there even was a unicode standard which could have been applied, and when the alternative you want isn’t unambiguously better than what it does now.
“What is language” is a far more insightful question than you clearly intended, because our collective best answer to that question right now is the unicode standard, and even that’s not perfect. Making the very core of the filesystem have to deal with that is a can of worms which a competent engineer wouldn’t open without very good reason, and at best I’m seeing a weak and subjective reason here.
The reason, I suspect, is fundamentally because there’s no relationship between the uppercase and lowercase characters unless someone goes out of their way to create it. That requires that the filesystem contain knowledge of the alphabet, which might work if all you wanted was to handle ASCII in American English, but isn’t good for a system which needs to support the whole world.
In fact, the UNIX filesystem isn’t ASCII. It’s also not unicode. UNIX uses arbitrary byte strings, with special significance given to a very small number of bytes (just ‘/’ and ‘\0’, I think). That means people are free to label files in whatever way they like, and their terminals or other applications are free to render them in whatever way seems appropriate, without the filesystem having to understand unicode.
Adding case insensitivity would therefore actually be significant and unnecessary complexity to add to the filesystem drivers, and we’d probably take a big step backwards in support for other languages
Third party, sure, but Starlink is absolutely a US corporation. They have joint projects with the US military, even
That’s going to be a problem whatever solution you come up with, because of the federated nature of the lemmy system.
There’s no central authority to hand out usernames, so if two people sign up to different instances with the same username, any design which didn’t attach instance name to each username would fail. The only way around it would be for each instance to contact every other instance which exists, including the ones which haven’t federated yet, and negotiate ownership of the new username, and that’s just not possible
The crew of Apollo 13 weren’t really stranded, as such. They were far from home and not sure if they had the means to get home before the supplies ran out, which is a different problem
For an emergency ascent, they’d probably have dropped more than two. They also probably wouldn’t have taken the time to type a message to the surface if it were going wrong that quickly.
It seems more likely to me that they were controlling their rare of descent. I’d expect them to lose a little buoyancy as the vessel compresses, so it seems reasonable that they’d drop the occasional weight as they descend.