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

  • Esca@lemmy.one
    link
    fedilink
    English
    arrow-up
    0
    ·
    1 year ago

    I don’t know about it. Look even at the usernames. It’s @[email protected], it’s structured like an email. Even for instances, /c/piracy is not a thing, it is [email protected] in Lemmy world. Even Mastadon has the same structure of name@instance.

    Every community has their own sets of rules, own set of moderators and culture. If you don’t like how one is moderated, go to another one (basically how reddit works too, except there you need to change to name to make an alternate community)

    • interdimensionalmeme@lemmy.mlOP
      link
      fedilink
      English
      arrow-up
      0
      ·
      1 year ago

      This is like saying Bob in New York and Bob in Austin as different

      Therefore for this reason /c/knitting in Seattle and /c/knitting in De Leon Springs are different things that must be considered individually in their own terms.

      Nobody wants to distinguish and reads individually about the 108000 knitting communities in the USA. There is only /c/knitting, the rest is hair splitting and exposed infrastructure