Two older threads about the same topic:
Fediverse
A community to talk about the Fediverse and all it's related services using ActivityPub (Mastodon, Lemmy, KBin, etc).
If you wanted to get help with moderating your own community then head over to !moderators@lemmy.world!
Rules
- Posts must be on topic.
- Be respectful of others.
- Cite the sources used for graphs and other statistics.
- Follow the general Lemmy.world rules.
Learn more at these websites: Join The Fediverse Wiki, Fediverse.info, Wikipedia Page, The Federation Info (Stats), FediDB (Stats), Sub Rehab (Reddit Migration), Search Lemmy
In an SSO scenario, your home instance would still need to be around to act as the IDP. I don’t think that adds much in terms of functionality over what we have now.
The ability to backup and migrate your account is critical to prevent losing your data if an instance goes down. SSO wouldn’t help you in that scenario.
Yea SSO is actually really easy to implement, I wouldn’t mind that
I'd love the second option, utilizing SSO so that I can effectively have the same account over different protocols/instances. I feel like that's far down the wish list overall of what we'll see coming though.
It's come up a few times, as well as what I'm about to mention, but it's still worth mentioning since it's expressly made to better enable this, the Zot protocol was made with a nomadic/portable identity in mind.
I'm guessing there must be a reason it's not been adopted though, but I'm not sure what the reasoning may be.
It would be convenient to have a Fediverse wide login, but it would carry too much baggage in terms of overhead and security. They'd have to carry the whole of the user database across all of the Fediverse, not really feasible. Then there's security concerns over sensitive data like email and passwords. So probably not something that could ever happen.
A sync feature between instances might be do-able. Could be handy. I have a couple instances where I'd like to sync community subscriptions.
There would not be a need to duplicate or sync all user databases across the fediverse to support SSO. In fact SSO already exists in other contexts and I haven't heard of any implementation that works that way. It's essentially accomplished by the authority and the service exchanging login tokens.