That might work, but it's never a good idea to write your code against a specific implementation. Plus, it seems that in this case the Lemmy devs shot themselves in the foot: why allow to create two different types of actors with the same name?!

I sound like a broken record, but none of this would happen if the devs took a good look at RDF before throwing everything into objects/classes and ORMs.

I'm working on something that aims to be compatible with Lemmy's API, and my models are based on the context definitions first. This means that it becomes impossible to have communities and users with the preferred_username, because they are both actors.

I agree. Users shouldn't be allowed to choose a name that already exists as a community. But it would be a shame if communities could not be created because a user with that name already exists.

I think this is yet-another reason to have a separation between users and communities at the instance/domain level.

Setting up a server should require one top-level domain and two subdomains:

• https://myserver.com/ would be for webfinger and the actual backend.
• https://groups.myserver.com/ would be the subdomain for the AS2.Group actors
• https://people.myserver.com/ would be the subdomain for the AS2.Person actor

Regardless of how webfinger is supposed to work, Lemmy has now got a situation where there are many many overlapping actors. I don't see a clean way out of this for them so it'll probably persist.

Lucky this came up because I have been meaning to make PieFed work the same as Lemmy, with multiple actors in the webfinger response!

By the time it (unique handles between users and categories) was needed, NodeBB had been around for 10 years and installed in countless places.

It needed to be done in one fell swoop so we coded an upgrade script that prioritized the user slug (as historically it had been around longer).

Hopefully the only thing you really have to federate out is an Update, but who knows what'll happen.

Mastodon cannot follow Lemmy commmunity if a user has the same name as the community · Issue #1922 · LemmyNet/lemmy

For a community in which there is also a user with the same name: https://lemmy.ml/u/bitcoin works (well, shows hourglass / waiting approval) https://lemmy.ml/c/bitcoin does not work, does not show any result to the search. Same for !cry...

GitHub (github.com)

Unlikely to change. I found a more recent issue that was closed with a link going to that one, so they've been over this multiple times over the years and don't want to budge.

PieFed will continue to disallow communities and feeds to have the same name as users, that will maximize compatibility.

Is there no way for an app to say "give me the community only" or "give me the user only" when it calls the webfinger lookup thingy? Because if there is, then Mastodon devs could update the behavior on their side to depend on whether the name starts with @ or ! (the same way Lemmy apps do).

I also posted this question in another comment thread, but is there no way for an app to say "give me communities only" or "give me users only" when calling the webfinger lookup thingy? Because if there is, then Mastodon devs could update the behavior on their side to depend on whether the name starts with @ or ! (the same way Lemmy apps do).

Nope, it's just a.single route, no filters or qualifiers I am aware of.

One could go through the returned accounts and see which are users and which are groups, although that's expensive and time consuming to do.