Well that's what I'm saying. The backend doesn't need to be centralized. But you can avoid the need for the user to "learn this stuff" (which, like it or not, i

Well that's what I'm saying. The backend doesn't need to be centralized. But you can avoid the need for the user to "learn this stuff" (which, like it or not, is undeniably a barrier to adoption), by "centralizing" the client (which can still be open source, with competing implementations that all connect to the same "fediverse"), in the sense that each user can have one app that connects to multiple backends for fetching and posting content. And instead of relying on servers to federate with each other (which basically just shifts the problem, replacing one centralized walled garden with a patchwork of smaller gardens), why not let the client decide which servers to subscribe to? In an ideal world, the client could even merge comment threads when the same story is posted to multiple servers that the client subscribes to.