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 was talking about this with friends. I think that as the userbase grows, we’ll reach the point of specific communities being like the “main” sub for that topic. Like, right now I’m subbed to 5 or 6 different “games” or “gaming” communities. Eventually, I think whichever instance ends up with the largest one will essentially become that default you’re looking for.
That said, I don’t think forcing it by collapsing alternate communities on different instances into one is the right way to proceed, because that may not be inevitable. I mean, maybe the gaming@programming.dev culture is different enough from the games@lemmy.world one? We had r/games, gaming, truegamers, gaming4gamers, girlgamers etc etc on reddit, you know?
tldr: I think that, while communities for specific topics slowly shifting towards one mega-community seems likely, there’s a space for different smaller ones with different moderation and culture here too.