Does anyone know of any interesting theories on dealing with the federation ownership problem? I'm not looking for "just use fedi" comments, I'm looking for frameworks of reasoning that can be applied to different or new federated systems.
(The federation ownership problem: not everyone is able to maintain a server, so a significant share of users relies on other instances, often public ones because their tech friends do not use the system, but how do you encourage those instances to remain up and running? Especially once people get bored of running them as a hobby)
@joepie91 Cloudflare had a solution for this, but they shut it down because of the backlash from the Fedi community.
Maybe another, more trustworthy company can take up the torch and offer a similar solution?
@KuJoe Unfortunately Cloudflare's 'solution' is not really a solution to the problem; it pretty much boils down to "centralizing the network on their infrastructure, and that would lose the core property (and benefits) of a federated network.
@KuJoe (It's also not quite true that it was shut down due to backlash; they pushed ahead with it *despite* backlash, and then when they lost interest a few months later, they quietly stopped updating it and eventually archived it, with no migration path)
