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 have heard this meme before, lemmy is not email
Also application that go against user intuition, start with a permanent handicap.
But in this case, this is fatal, you cannot learn your way into making lemmy.example.com/c/piracy should you all /c/piracy on all instance
The functionallity simply is missing and the consequence is everything will be on the lemmy.biginstance.com/c/thebigcommunity and everything else will be invisible (and probably defederated outright as moderation becomes increasingly untenable)
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)
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
No no, you had it right in your second paragraph. Every instance has its own set of communities. Sometimes they happen to have the same names.
Technology skills don’t work by intuition; they work by learning.
People say “intuitive” when they mean “familiar to something I’ve already learned”.
For example, novice programmers often say that a programming language that resembles the first language they learned “is intuitive”, while a language that looks different “is unintuitive”.
People who learned C first, used to argue that Python was “unintuitive” because it doesn’t use
{}curly braces around code blocks.That’s not intuition. That’s familiarity. Once they become familiar with Python, they no longer talk about the absence of
{}around code blocks as “unintuitive”.Here, there are users coming from centralized services like Reddit, Facebook, or Twitter. One of the things that they have to learn is that this is not a centralized service; you have to care about what instance you’re looking at, or what instance a community is hosted on.