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
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
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 Philip@ponder.cat, it refuses to deliver it to philip@ponder.cat, and it allows users to create himbo@ponder.cat and Himbo@ponder.cat 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.r@gmail.com. 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.
Just wanted to let you know: I was trying to resubscribe to !world@lemmy.world so I could say something. I went to the search box, typed “world@lemmy.world”, got a bunch of results including world@lemmy.world at the end, clicked on it, but it was the user @world@lemmy.world, not the community. I couldn’t find the community in the list.
It’s no kind of difficulty to work around the problem, of course. But it was a clear instance of me wanting the software to do something, the software messing up because it’s allowing multiple entities with the same identifier to exist, and me having to go back and try another way. It actually couldn’t find the community when I limited the search to communities, either, and I had to type the URL. No idea what that’s about. But yes, it’s a cause of minor malfunctions like this.
When you do a search, the default is “All,” which is why your search results had a bit of everything. If you had chosen “Users” or “Communities” then you would have gotten only users or only communities, respectively.
https://lemmy.ml/search?q=world%40lemmy.world&type=Communities&listingType=All&page=1&sort=TopAll
Notice no community result.
https://lemmy.ml/search?q=world%40lemmy.world&type=All&listingType=All&page=1&sort=TopAll
Also no community result. On my instance, I could scroll to the end of the list, and when the call to the resolve endpoint returns, the user but not the community gets added as a single entry to the very end. Like I say, no idea what that’s about, although it seems to be a bug distinct from the bug I’m describing,
https://lemmy.ml/search?q=https%3A%2F%2Flemmy.world%2Fc%2Fworld&type=Communities&listingType=All&page=1&sort=TopAll
Also doesn’t work? That’s a little strange, honestly. Like I say, no idea. I’m just describing the somewhat different but also wrong behavior I see on my instance.
You’re putting the instance name (“@lemmy.world”) in the search term, which is why the searches are failing. If you already know the user or community you’re looking for, then why would you be searching for it? You already have it!