A user checking out one of these URLs does not want to filter only local post on that instance.
On all instances, this url should mean “show me all /c/piracy on all federated instances”
If you really mean /c/piracy only on that instance, then add something to the url.
The current convention breaks the most important aspect of federation and makes its vestigial appendage.
The current way has user asking question /c/piracy, but on which instance ?
So now they’ll all join the same instance . You wouldn’t post anywhere else since no one would every see it.
It’s a recipe for centralization.
I think this is obvious to most users, were deal with “voat with extra steps” here
I like the idea, but it should be opt-in. So communities can decide if they want to “combine” with other communities. And I would go a step further and not force exact naming schemes.
But why? They could just agree on one and delete the other one. What ist the benefit of having topic@example and topic@otherexample when both show the same content?
It should be opt-out, the default should be content is federated. And it is already opt-out, that is what defederation is. Of course defederation is a blunt tool. Defederation should be possible on a per-community basis.
Also, what most mods want from deferation is not “we don’t want to be heard by others” but “we don’t want outsiders to be allowed to speak here” which is different.
Although I just noticed that posts are not stored in their communities but as sequential numbers on their instance.
like https://lemmy.example/com/post/1579555
If that reflects the internal structure, then disallowing outside from posting in one community but not another is going to be a ton of extra programming.
And I would also like to see people posting comments in https://lemmy.another.com/post/1579555
then from https://lemmy.thirdinstance.com/post/1579555 you would see comments from example.com and another.com as if they were one.