There are already enough 'cloud' providers to provide the necessary diversity, and there is already enough crypto to provide the necessary security. What there isn't is an adapter layer that puts those two together in a way that lets folks like the Author build their favorite UI on top of it.
One such architecture might be a git server on a machine at one's home, which uses fuse to create a replicated secure backend across S3, some VPS, Dropbox, and what ever. Giving the git server on the machine a 'file system view' while creating a replicated and encrypted block back end using a variety of cloud providers.
You could do that with a VPS in the cloud as well, but it has some exposure to infrastructure seizure or damage. By hosting it at 'home' you trade some slightly stronger legal protections for the limitations of your home internet connection.
A server should just be a dumb, transparent container. Whether it's Github or some custom-made "super secure" server doesn't matter. The real magic happens in the client.
Yes, I know one could configure one's own github repo and make it accessible, etc. I know that cloud storage is about as reliable as that shaky cousin who's always borrowing "a few bucks for beer, man."
It seems like everyone is attacking the wrong problem. The problem is not the client, that's just a UI/UX issue that's never going to be resolved because, hey, I hate what you like and vice-versa.
Can someone please create a more reliable back-end so we can stop saying things like "I hate cloud providers"? I hate them, too, but I'm not going to redesign the part where the problem ain't.