this post was submitted on 10 Oct 2023
25 points (72.7% liked)
Lemmy
12524 readers
8 users here now
Everything about Lemmy; bugs, gripes, praises, and advocacy.
For discussion about the lemmy.ml instance, go to [email protected].
founded 4 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
No, because Lemmy doesn't support Oauth2 yet. And even if it would support it, at most it could be a "login with lemmy.ml" or similar instance specific button as the protocol requires a specific endpoint.
Edit: see other comment in this thread. With the OIDC discovery extension to OAuth2 it might be possible, but I haven't seen that feature being used this way in the wild yet.
when you type [email protected] I already know what instance you're from
Yes, but that is not how Oauth2/OIDC works (the old OpenID did, but it has been largely abandoned).
One of the reason this approach was abandoned is that these external login automations are very easily abused for spam if you allow arbitrary instances as the auth endpoint.
So this is why we've been seeing rows of "Login with $SpecificProvider" instead of a universal format using
username@provideras we all hoped?The old OpenID didn't see much uptake (because of the spam issue) and the alternative Oauth2 that was AFAIK mostly pushed by Google is clearly designed for the purpose of large centralized providers. So I don't think there is a direct causality, but yes it is related.
Never the less Oauth2/OIDC works quite well and is clearly better that most of the alternatives still commonly in use.
you could accept logins only from instances that have enough trust on fediseer, I think this would work better than the old openid