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 must log in or register to comment.
We can try it out since there is both @[email protected] and [email protected]
When I searched for [email protected] on Mastodon (specifically masto.ai), I got the community, not the user. Not sure why, but that’s what I got.
On Lemmy? Nothing, works fine. On Mastodon? Not sure, maybe someone in a Mastodon community would know.
They would be identified by their instance. You can’t have two identical usernames in the same instance. So you won’t have [email protected] twice. Buy you could have [email protected] and [email protected], for example.
That’s not the question though. The question is what if I make a user called “@[email protected]” (i.e. this community)? That’s probably allowed on Lemmy, but since Mastodon doesn’t have the concept of communities in nearly the same way, what would happen?
That’s not how Lemmy works. Lemmy uses Actor URLs of
https://host.tld/u/userwhich is referenced via@user@host.tld, and communities arehttps://host.tld/c/communityreferenced as!community@host.tld. So there is no overlap.I’m talking about mastodon interacting with Lemmy, not Lemmy interacting with itself.
Thank you for taking your time to answer for me!
No worries!
I don’t follow… Lemmy and Mastodon both require port 443, so a single hostname of
lemmy.mlcan’t run both. Lemmy and Mastodon handle users the same way, just Mastodon doesn’t have!communities.I’m talking about a mastodon user referencing a Lemmy community vs a Lemmy user. Mastodon apparently uses the same syntax for both.
Ohhhh. My understanding is initial @ in Mastodon is only required for users, and would default to user over community, while leaving off the initial @ would do community. I have not validated that in the source, though.
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
fartmaster@gmail.comandf.a.r.t.m.a.s.t.e[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
/uandwhile communities are/cand!. No overlap to check for. Mastodon is where the confusion comes in.
