what happens when user and community have the same name
what happens when user and community have the same name
From mastodon to follow an account or a community on lemmy you use the @name@server format and there is no difference between a community name and a user-name
so i was wondering if anyone tried and checked what happened
You're viewing a single thread.
What should happen: The backend checks if you're trying to create a community that has the same name as a user, or vice versa, and refuses to do it because that would be confusing, since a lot of ways of referring to an entity on Lemmy use the exact same format for the user and the community.
What does happen: Have fun with confusing!
Inside the Lemmyverse and its API, it’s not confusing at all. Outside of the Lemmyverse there be dragons.
I made an SMTP server that treats email addresses as case sensitive. When it gets mail for [email protected], it refuses to deliver it to [email protected], and it allows users to create [email protected] and [email protected] as two distinct addresses. Within my server, it's not confusing at all. Outside of my server, there be dragons.
You monster!
Now, what happens when one uses different cases in the domain part?
Round robin arbitration.
You joke, but gmail does this with dots in email. There is no difference to gmail between
[email protected]and[email protected]. Not really any dragons here, but can create confusion if you're unaware.Nah, Gmail does the exact opposite of what their server does. Gmail is extra lenient with how an address may look. While their server is extra strict.
Correct. Gmail is doing it right, by anticipating how their server's behavior might confuse people or lead to email going to the wrong mailbox, and making extra complexity to make sure the behavior makes sense. Lemmy is doing it wrong, in this instance.
What formats are the same? Users are
/uand@while communities are/cand!. No overlap to check for. Mastodon is where the confusion comes in.