this post was submitted on 28 Jun 2023
-19 points (19.4% liked)

Lemmy

12538 readers
7 users here now

Everything about Lemmy; bugs, gripes, praises, and advocacy.

For discussion about the lemmy.ml instance, go to !meta@lemmy.ml.

founded 4 years ago
MODERATORS
 

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

you are viewing a single comment's thread
view the rest of the comments
[โ€“] tgxn@lemmy.tgxn.net 11 points 1 year ago (1 children)

Remote communities do show the fully qualified community name in the url though. /c/piracy@instance.com should show the same thing on all instances.

That requires you to keep and update a ledger of all existing /c/piracy communities and to visit each one in succession.

An enormous and pointless task since all users have now realized "there's only one /c/piracy, it's on lemmy.ml" posting anywhere else is pointless as nobody will see it or even know they other place exists.

If lemmy.example.com/c/piracy doesn't aglomerate all /c/piracy content from all federated instances automatically. Then the federation system is broken and pointless.