Anyway, this gets into a philosophical point about the whole Reddit exodus - ID federation and content federation are two different things, and when people talk about the friction of joining a forum vs clicking subscribe on reddit, ID federation is what gives you that, not content federation.
And content federation introduces a lot of scalability problems, and difficulties deleting comments/etc. Yes, someone can notionally always crawl/cache you, but having it on your server is different from intentionally putting it out into a peer-to-peer CDN, or serving it to a bunch of different pods so they can put it in their members' feeds. Some people don't want that part, they want the content to stay on their self-hosted instance.
Identity federation also runs into the problem that oauth, etc don't let you have the same account on multiple oauth providers as a backup in case one of them shuts down.
If Revolt supported federation it would be trivial to just turn that feature off if you had privacy concerns in that regards.
> Hold on, this article is quite old at this point, just a few things to keep in mind:
> - Federation may end up being part of the project in some capacity in the future, just at the moment it is not part of any feature (at least publicly) on the roadmap.
> - The complexity and time arguments below are still valid but may be necessary to tackle in the future.
> If you have some general ideas on where and how federation could be implemented, feel free to drop into the Lounge #Revolt Development.
This is for folks that want a self-governed / "no big brother" Discord alternative, it's quite nice for that purpose, but it's lacking the Discord integrations (audio chat, etc.) that make it better for gamers.
This should be a Matrix implementation with some implementation specific extensions that will be included in the standard in the future.