I'm really excited about all the activity in the federated, self-hosted space. However, I feel like there's still a missing piece around identity. I don't want to have to create a new user every time I want to use someone elses shiny new federated event sharing application or what have you.
There don't seem to be any great self hosted OpenID providers out there and OpenID only solves the authentication part anyway. Maybe I've missed some obvious solutions?
this is what zot, the protocol #hubzilla is running on does.
It stores contacts etc. as keypares.
You can move those keys to any server you want, and by that remain always connected. Incl. having the publishing setting etc. stored within a #nomadicidentity.
It is also supporting #OAuth to authenticate with other services/apps using that identity.
Decentralized Identifiers (DIDs) I'm curious about. Happy to see that evolve.
All I can say on the matter between #DIDs and how zot does it, that @cwebber and dev of zot @macgirvin have a different perspective on how to solve the mentioned isse.
I have way to little knowledge to make a judge about.
hubzilla was often said to be to complecated etc.
within the next weeks a new social plattform with a more simple codebase and functionality running on zot will be published.
for more about this see:
@bob @paulfree14 @zatnosk @macgirvin @cwebber @trwnh
As someone who's looking to hack on something in this space I'm a bit more interested in the DID stuff I think, but that's because I'm a sucker for a good spec doc. Having briefly scanned through the Zot documentation it occurs to me that it might be possible to register the zot protocol as a DID method. But I haven't actually thought about that in any detail, it's just a nice idea.
i meant something in the way that some people use facebook/google *only* to sign into things. no channels, no publishing, nothing else besides pure authentication/identification
similar to openID servers, but more elegant than the mess that is openID right now
or maybe there's a way to adapt openID / revive it / modernize it?
@alex @paulfree14 @macgirvin @bob @zatnosk @cwebber literally all i'm looking for is, say, hosting my public key at id.trwnh.com for example, and then being able to log into any app *only* by typing in that URL and some method of verification (user/pass?)
if this can be tied into a 2FA app somehow that'd also be cool
that's just my naive idea -- ideally people could also delegate by signing up at an open hub like keybase/google/github/etc, not just hosting their own domain
Server run by the main developers of the project It is not focused on any particular niche interest - everyone is welcome as long as you follow our code of conduct!