Introduce a commie: pseudo-URI for webfinger.
SoniEx2 opened this issue · 4 comments
Requirements
- Is this a feature request? For questions or discussions use https://lemmy.ml/c/lemmy_support
- Did you check to see if this issue already exists?
- Is this only a feature request? Do not put multiple feature requests in one issue.
- Is this a backend issue? Use the lemmy-ui repo for UI / frontend issues.
- Do you agree to follow the rules in our Code of Conduct?
Is your proposal related to a problem?
Lemmy currently treats communities as accounts (under the acct: pseudo-URI), this is a deviation from the intent of the standard and a misuse of the acct: pseudo-URI.
Describe the solution you'd like.
This will require a few deprecation cycles, but allowing communities (but not actual accounts) to be queried under a commie: pseudo-URI - without changing anything else - would be a good start. Then, at some point in the future, switch to trying both formats when looking up a community. Finally, maybe in a decade or so, add an option for admins to disable legacy community support. Then, after another decade, remove the option and only use commie: pseudo-URIs.
Describe alternatives you've considered.
The main other option is to do nothing. There probably aren't any other options beyond that.
Additional context
No response
It was implemented like this originally as group:news@lemmy.ml, but that was incompatible with Mastodon. Thats why we had to switch to the current implemenation. So its not possible to change this unless Mastodon and other platforms add support for the new format first (which seems very unlikely).
wait, how does it work for mastodon when you have both an account and a group under the same identifier???
In that case Mastodon cant fetch the user, its a bug on their side.
that just makes it sound more like a better idea to support an alternative way of fetching groups, and when they conflict, split them. such that the acct: resource only lists an user if it exists, or falls back to a group/community.
that is, assuming you care about complying with IETF standards.