Skip to main content


Is there a way to have just one account in the #, instead of creating multiple accounts on #, #, #, # servers? In other words, is there a way to decouple identity from content, now or in the future?
@Serge Tarkovski The Zot projects (Hubzilla and Zap) provide nomadic identity, linked identities across different services, and decentralised cross domain single sign-on. No other projects have shown any serious interest in any of these. Linked identities across services is still a bit experimental but has been successfully tested. Development is languishing because nobody else wants it and it's kind of pointless to provide it across one service when we already have nomadic identity. It's a slightly different way of doing the same thing. The other technologies have been in production since about 2012 and are relatively stable/mature.
well, I was thinking about something like #, which has long been used over the web. Question: what is used as a proof of identity in #? A trusted server? A pair of cryptographic keys?
It would be nice if Mastodon or Friendica could act as OpenID server.
FYI, # can act as OpenID server.
Just open issues in your favorite apps to ask support for # and #
Been begging for this for years. No sign yet...
not sure I'm getting your idea correctly. Which one should work as the OpenID server in this approach, if I have, say, a Mastodon, Pixelfed and Peertube accounts? A Mastodon one? Or one of the other two?
@arthurlutz: that's exactly what I've been thinking about: a separate identity provider
Also Gluu CE could be an option maybe?
https://gluu.org/docs/ce/
#

This website uses cookies to recognize revisiting and logged in users. You accept the usage of these cookies by continue browsing this website.

⇧