- cross-posted to:
- fediverse@lemmy.ml
- fediverse@lemmy.world
- cross-posted to:
- fediverse@lemmy.ml
- fediverse@lemmy.world
The author examined the distribution of instances in the fediverse. Given that many instances are hidden behind CDNs like Cloudflare or Fastly, the author employed ActivityPub’s functionality to discover the actual hosting locations of servers. More than half (51%) of the fediverse is hosted within a single hosting company. The author suggests that the fediverse hosted mostly with a few major providers, deviates from its initial objectives.
Anyone concerned with that threat model can host their own instance on whatever hardware they want.
They could have the middleware load balanced over aws/azure/gcp/hetzner/at-home and have load-balanced replicated postgres also running on those hosts.
They could use CDN & threat protection from those cloud providers as well as cloudflare. And really distribute the threat of that situation.
But nobody wants to fork out $$$ every month before they are even scaling to thousands of users, never mind the added complications of middleware from one provider trying to interact with a load balancer on another provider which is forwarding to postgres on a different provider, let alone geographic latencies.
Then trying to manage that, never mind the headache of an update.
But, if that is someones threat model, then they CAN work around it.
Companies owning the actual servers and infrastructure is at the level of enormous scaling (like twitter) or high risk (like banking, even then chances are they are running hardened systems that would be secure on anything).
Most companies will pass that responsibility off to a single provider, and rely on that providers skills/services for uptime