There’s a major convergence of OAuth/OIDC support across #fediverse applications, #Matrix is going all-in on it as its root default, and other social web protocols are tagging along as well.
Like the separation of church and state, it seems prudent to keep the management of our digital identities separate from our social network servers.
Domain-based OIDC accounts with web sign-in, especially when self-hosted, serve the function of a minimum-viable #nomadicidentity
@erlend what’s with people’s negative responses? The current system isn’t cutting it but let’s not try something anyways?
I think using DIDs makes sense
@erlend ive only recently started exploring the current state of decentralized identity, but do you have any resources that could explain why fediverse and matrix stuff needs oidc rather than just indieauth?
and you mentioned that theyre not really compatible with each other. does that mean that we need to pick one and discard the other?
@jaxter184 We need something like IndieAuth, I.e. ‘web sign-in’. But IndieAuth is an extension of OAuth that predates OIDC and is not compatible with it. Mastodon already supports its own form of ‘web sign-in’, and this too is a custom thing rather than IndieAuth exactly.
@hueso it’s what a lot of other things do, but none of those are already widely implemented across most fediverse apps, which OIDC is. It’s an already adopted standard, not a new thing that would take years of advocacy and coordination.
@erlend The end result of wide OIDC adoption is "Sign In With Google" buttons everywhere in Fediverse. This will also stifle adoption of decentralized identity systems (that's why this broken and outdated standard is being pushed so hard by megacorps).
@erlend I am very sympathetic to this desire to have some kind of self-controlled portable identity. But I also have to consider that it's already incredibly hard to get a new project onto the fediverse, and this would likely add to that.
Add comment