Why is he talking about Faramir? Faramir isn't even BORN yet!!!

After the deductibles and co-pays. I have a "platinum" plan through my employer; better insurance than anyone else I know and the co-pays still total up to a considerable amount. No deductibles for in-network on my plan, which makes me extremely fortunate. As a single guy I can afford the co-pays even with my modest salary but I can see how quickly they would bankrupt someone with a family, particularly if said family had one or more members with a chronic illness.

Incidentally, I was just exposed to rabies a few months ago:

Strike One: The only place to get the immunoglobulin is the ER, because it's very expensive (>$4,500) and has a short shelf-life. ER co-pay: $150
Strike Two: There's a set schedule for the vaccine, Days 0, 3, 7, and 14. You can get the vaccine from your primary, in theory, but of course my primary has a months long waiting list because we're driving PCPs out of business. Bottom line, I can't get appointments with them for Days 3 or 7, so that's two more trips to the ER. Additional co-pay total: $300
Strike Three: New York State ostensibly has a fund to pay for out of pocket expenses related to rabies exposures, but they only reimburse for the rabies vaccine and immunoglobulin. Since the ER decided to give me a tetanus shot on Day 0 NYS won't reimburse me, even though my out of pocket would have been $150 with or without this extra shot. Hooray for bureaucracy!

Totaling all this up, that stupid bat that found its way into my apartment has personally cost me $465 ($450 of ER co-pays, $15 of PCP co-pay) while my insurance company is on the hook for close to $7,000. My annual premium is about $6,000. So this one incident wiped out every penny they made on me and then some. I'm an otherwise healthy 32 year old marathon runner that ought to be subsidizing those who are less fortunate. Now imagine a family of four that were all exposed to the same scenario I was.....

Let's look at it another way. Some Aztlan nutjobs somehow manage to set up a base of operations in Tijuana, and say that they want California "back".

They start by sending in suicide bombers to San Diego. The Mexican government does nothing to stop them. They launch rockets into San Diego and Orange County. The Mexican government does nothing to stop them.

Assuming this scenario, what should/would the US government do?

A compiler that is as well-designed and useable as Linux and Git? It already exists

The reason that most extensions exist is that there is (or was) no way of implementing things that people want with standard C. Inline assembly is one example. All modern C compilers support it, but GCC and Microsoft's compilers use different syntax (most other compilers implement one or the other, sometimes both). Without it, you require that every time you want to use even a single instruction of platform-specific assembly code, you must write an entire function and call it.

Atomics were another big reason for extensions. Prior to C11, if you wanted atomic operations, you needed either assembly or non-standard compiler intrinsics. Efficient vector support is another one.

While that's technically true, the Ada and Fortran front ends are both using DragonEgg, which is a GCC plugin that converts GIMPLE to LLVM IR. It doesn't work well with GCC 4.7 or newer, produces poor debug info, and is now largely unmaintained. There is a Flang project to produce an LLVM front end for Fortran, but it's very immature. The Ada Labs guys were looking at producing an LLVM front end for Ada, but I don't know that they got anywhere with it.

Clang wasn't. Clang began in 2007, after Chris Lattner had moved to Apple. Before then, if you wanted to compile C code with LLVM, you had to use llvm-gcc, which was a horrible hack that took a forked version of GCC and translated one of the GCC IRs into LLVM IR before code generation.

The problem is worse on Android than on many other platforms because there are very few native shared libraries exposed to developer and there is no sensible mechanism for updating them all. If there's a vulnerability in a library that a load of developers use, then you need 100% of those developers to update the library and ship new versions of their apps to be secure. For most other systems, core libraries are part of a system update and so can be fixed centrally.

I doubt Apple has such a patent. Both of these were features of Symbian at least since EKA2 (over 10 years ago) and, I think, earlier. Apple may have a patent on some particular way of exposing this functionality to the UI, but that's about the most that they could have without it being shot down in court in 10 seconds (prior art that's in the form of a phone OS that millions of people owned is hard to refute).

Everything you ask for exists. The reason that Google, Microsoft, and Dropbox don't use them is that their entire business model depends on differentiation. If you could connect to their services with any third-party client that also worked with a server that you set up yourself and with their competitors' services, then their hold on the market becomes very tenuous. You're searching for technical solutions to business problems.

The 'you can skip in 5 seconds' ads amaze me. Presumably the people using them know that they have 5 valuable seconds that everyone can see, yet they uniformly squander them. I've almost never seen an ad that tells me anything interesting in the first 5 seconds, which isn't that surprising, but it's really surprising to me that most don't even tell me what the product is. Several that I've seen use the first 4 seconds to fade from black, then get 1 second of something incomprehensible before I hit skip.

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).

Hey, AC. I'm going to assume you live in the US.

Let's assume the following hypothetical. A bunch of the Aztlan nutjobs somehow manage to assume some power in Tijuana. They decide that they want California "back".

They start sending suicide bombers into So Cal. The Mexican government does nothing. They start launching rockets into So Cal. The Mexican government does nothing.

What should the US Government do in this situation?

No, you'd have the key. If you wanted to share the file publicly, then there's no point in keeping it encrypted, so you'd provide the server with the key and it would decrypt, saving you the cost of downloading and reencrypting.

The client just needs one key, the RSA (or equivalent) public key. You'd need to copy this between devices, but it's relatively small (under 1KB). It's small enough to fit in a version 40 QR code quite easily, so you could set up mobile devices by displaying the QR code on your laptop screen and point the mobile device's camera at it, if you don't have any sensible way of transferring files between devices. The client then has to download the file and the associated key, decrypt the key with the locally-stored key, and then decrypt the file, but that's not something that's exposed to the user.

My late wife could have used something like that for her BIPAP.