This is a big problem. It creates the illusion that /c/cats on one particular instance is the real /c/cats.
This is the root of re-centralization and it must be pulled out.
This is a big problem. It creates the illusion that /c/cats on one particular instance is the real /c/cats.
This is the root of re-centralization and it must be pulled out.
I think this is incorrect - federation depends on a “true” version. A community is tied to an instance, that’s where the true version is. When you’re logged into another instance and you comment in that community, your comment gets copied to the true version, as do comments from other federated instances, and all of them get copied from the true version to a version on yours.
When one instance defederates with another, that copying stops happening. If a copy of that thread is still on your instance, and you comment on it, your comment won’t get copied to the true version, so it also won’t get copied to other instances; only users on your instance will see it.
That’s my understanding, but I’ve only been here a few weeks.
Edit: nah
That is essentially what happens and it’s a technical issue, not a philosophical one. If one instance is denied posting to another, the user should be notified at some point about that. There are a lot of silent errors right now with the setup. If you disable signups for example, users can still try but never see that it will never work.