I'm not doing anything huge, but my local radicle node is connected to ten other nodes at present, one of which is my own hetzner-hosted seed. Even if half of these go down, I still have full access to all the repos I follow.
The load will be spread across the network, but I guess the main benefit is that everything continues working even though HardenedBSDs official seed is down.
Every user has their own node, and everyone's node talks to several seed nodes. Even if the official HardenedBSD seed is down, there's still going to be another node to sync with.
I work for money because I need food on the table and a place to sleep. It doesn't motivate me much more than that. In fact, I wouldn't even call it motivation. It's a requirement to live.
There have also been studies that have found that money stops making people happier or more motivated once their yearly salary exceeds a certain amount (the equivalent of 700.000NOK here in Norway).
Some people are primarily motivated by making as much money as possible, sure, but most people I've worked with have found someplace else to work once their current job stops being interesting.
If it works anything like what we've got in Norway, they take a rough percentage, and once every year when the taxes are filed, the IRS equivalent charges or repays the missing amount.
What sort of IDE plugin are you thinking of? As long as you have a git plugin it should work just fine (if you're thinking of something similar to github/gitlab plugins then I don't think there are any, but I'm not sure what those buy you).
If I’m deploying a new version of my app, the typical managed solution will spawn a new server instance with that new version, and once a health check has succeeded a couple of times it will reroute trafic to this new instance and kill the old one.
Previously this would be problematic, as the new instance might miss changes made by the old server. Is this fixed by these new changes?
If they have enough users/make enough money, they'll make their own. Ecosia and Qwant (both european search engines) are working together to make their own index.
In any case, even if a european is a proxy for an american service, you need to prove that there is a market for an european equivalent for change to happen.
Keep user information in one database, keep user _data_ in another.
It all depends on your app, really. For some apps the above won't make sense, but maybe it would make sense to keep one db per org, or something like that.