You see my point, though. Knowing your administrator log-ins isn't a never-happens situation. People get user lists all the time.
Software on Internet-connected devices is a bit different from your examples though. No matter how insecure cars are, it would be really hard for me to steal a million cars in one night, let alone without being caught. Yet, it's common to see millions of computers/phones being hacked in a very short period of time. And the risk to the person responsible is much lower.
They don't do space tourism yet, but once they got the Dragon man-rated I don't see why not. The seven people who've been space tourists so far have in total paid $170 million, while SpaceX has quoted $140 million for a crewed Falcon 9 launch so they're at a price at least some is willing to pay. If they can make the rockets reusable it could significantly increase their launch volume even if only a few hundred super rich want to go. It would be real space flight in LEO and make you a genuine astronaut, not just "pop your head in" suborbital flight. Maybe they could even use the cargo room of the Dragon to hold some kind of deployable/inflatable mini-hotel for the stay. 100 mile high club anyone?
When I was born Mankind had not set foot on the moon. By the time I was five, we had been there, done that and decided to never go back again. If aliens do exist, they are sitting back saying "What the f?ck man, you want to meet us but don't have the energy to get off the couch and answer the door?" Mankind does not deserve space travel. We had our chance and refused to take it.
By the time you were five, we had been (384 400 kilometers) / (4.2421 light years) = 9.57827017 x 10^-9 = ~0.000001% of the way to the closest star. Eight years later they launched the Voyager 1 which is now about (127.98 Astronomical Units) / (4.2421 light years) = ~0.05% of the way. And it's probably uninhabited. What chance did we miss to go visit aliens? Do you think if we just put enough money in it we'd invent the warp drive? Chemical rockets can't do it, it'd be like trying to ride a horse to the moon. The ban on nukes in space kills fission, we still haven't got a working fusion reactor here on earth and antimatter only exists in extreme lab experiments.
True, we don't care much about developing the propulsion technology but we sure as hell would like the energy generation technology so to pretend we're not working on it is false. It just doesn't make a whole lot of sense to try building the applied technology before we got the basics working, if we can make a fusion reactor here on earth then maybe we can turn it into a fusion drive. Trying to skip that step earns us nothing, it doesn't bypass any of the problems we already have and creates a whole set of new ones which makes it that much less likely to succeed. The only tech that's pretty much ready to go is fission, but good luck selling a rocket that'll nuke its way through space.
The side that apparently blew a 300-civilian passenger jet out of the sky because they're too dumb to know what a Boeing looks like is getting direct military support from a major regional power which just happens to have nuclear weapons. And I thought my hometown of Detroit was fucked.
Well, if you want to put it that way the plane would never have been shot down if Russia had supplied a professional crew instead of teaching the separatists how to aim and pull the trigger. At least with the Russian military firing they probably know what they're aiming at.
Except in this case there's no signs that anyone was being particularly reckless, lazy or disregarding the rules, it was a fairly complex interaction between debug settings, ASM optimizations and dependency management. This is more like when the Space Shuttle blew up and nobody cares about the 9999 parts that didn't fail because the O-ring did and as a result it's now small chunks of scrap metal with dead astronauts. You don't get points for effort, style or the parts that work it's the end result that counts and in this case GCC poops on the floor because the final output is shit.
I think it's a good attitude for a kernel manager, because when he gets shit code from driver or subsystem maintainers that goes into a release kernel and starts corrupting data and throwing panics the shit is going to land on him. You can't just shuffle that responsibility downwards and say no, the kernel is 99% fine but that driver is crap because as far as the end users are concerned the kernel is crap and the internal bickering about whose fault that is doesn't matter one bit to them. It's your project and your job to get it fixed. And that might require some harsh words about the O-ring and the people who made it, because it's making them all look bad which is totally unfair to everybody else.
Please correct me if I'm wrong because I may not have imagined this system properly. I was thinking the idea was that you encrypt each file with a single unique key, and then to use a public-key encryption scheme to encrypt that key. You can then send the encrypted file and the encrypted key to another user, knowing that it will need that users private key to decrypt.
Every time you upload a file, you generate a random symmetric key. You encrypt the file with this key and the key with your public key. If you want to download the file, you get the file and the encrypted key and then you decrypt the key with your private key and then decrypt the file. When you create the account, you upload your public key.
When you want to share a file with everyone, with no access control, you download the encrypted key, decrypt it, and provide it to the server. The server can then decrypt the file.
When you want to share a file with a limited set of users, you download each of their public keys (which you can cache in the client) and the encrypted symmetric key, decrypt the key, and then encrypt it once for each user. They will then only be able to access it with their client.
I'm not sure who you're 'we' as in 'internet community' is. We do have standards and off-the-shelf libraries for everything required to implement this and others have done so in the past (one of my colleagues during her PhD did back around 2006, to give one example, others have implemented more complex and flexible schemes more recently). Note that this is the simple textbook scheme for doing this kind of system. It's been implemented before and doubtless will be again. If you check the research literature then you'll find more interesting schemes.
The only problem is if you want to be able to access it from the browser, without some kind of plugin (Google actually does compile OpenSSL with Emscripten to do ASN.1 parsing, but I wouldn't recommend using it for encryption).