I want my root digital identity and follow-contacts stored in a Solid pod, letting me log into all fediverse platforms via Solid-OIDC.
#ActivityPub & #Mastodon et.al. should just provide the send/receive pipes, relegating the job of primary identity provider to the ID-centric protocol that is Solid.
@erlend Are there enough solid users out there that this would be worth the effort? Like, are there a lot of queer furries actively making use of solid that aren't already on mastodon/etc?
@evan maybe so. This approach isn’t actually dependent on Solid as such, it just demonstrates how the OIDC protocol can enable what I think is a necessary division between server provider and identity provider in the fediverse.
@erlend@smallcircles careful with which friends you make.. but I can probably also advise here given I used to work for Inrupt on open-source Solid SDKs.
@erlend yeah, but the current way that Inrupt is doing WebIDs isn't the way you'd want for this.
To clarify: Inrupt made a decision in their Enterprise Solid Server to make the WebID document only writable by a specific software client, due to it containing fields that shouldn't necessarily be generally editable (there's pros and cons to this argument), but it basically broke the entire solid ecosystem, resulting in your WebID actually not containing profile information.
@erlend I do still think that OIDC or a profile similar would be very advantageous to the Fediverse, however, we'd want to pair this with OIDC Federation or something (the Federation spec is a bit weird because it has all these trust roots and stuff)
Add comment