4·
2 days agoPassport verification is a terrible idea. Instead of passport verification, the fediverse really lacks separating auth servers into a separate SSO component. So that you could log in to every fedi instance with the same account. It would be super convenient, and those who like to keep everything close together could just run two components side by side.
SSO doesn’t work like that. Conventionally, there is an sso ml provider, an sso world provider, and anyone else from the fediverse. Any server, for example lemmy, looks at the login domain during authorization and sends a request to the server along the lines of “someone is trying to log in, send the cookies and a redirect link”; someone is redirected to the SSO server, authenticates there, and then returns back to the original lemmy node. The registration endpoint can be determined by the domain.
Like, for example, lemmy.world login 1234@lemmy.ml -> redirect to lemmy.ml for password -> redirect to lemmy.world back. Or any another instance in fediverse.
Accordingly, this is literally no different from what exists now except for one nuance — I won’t need to go to my instance anymore, find a post mirrored from world, and write a comment there. I will simply be able to log in directly on world and write whatever I want.
And passwords are in the hands of the node admins anyway. This will literally differ from the current scheme in nothing except that potentially the owner of your lemmy account could hijack your mastodon. But those who actually think about this will just make 2 SSO accounts. But how easy that will be. No 20 accounts in 20 instances… And no one will have to explain why they need 20 accounts at all. And I’ll finally be able to watch pirtube, read lemmy, and comment on mastodon from the same username. =)
UPD: Especially tough guys will just be able to host their SSO node and not bother with password hijack.