[mynameismonkey]

I run three services (Mastodon, Pixelfed, WriteFreely) and would like to have my community use one set of credentials on all three (and any other service they would like to) - is this what I'm understanding is the intent here? I want to run more services but I simply cannot stomach yet more credentials.

[flanked-evergl]

Maybe this helps:

- https://solidproject.org/TR/protocol#identity

- https://solidproject.org/faqs#webid

- https://solidproject.org/faqs#fewer_passwords

> Does Solid mean we won’t need so many passwords?

> Yes. When you use Solid, you only need to login to your Identity Provider. You can then use applications that interact with your Pod without logging in each of them individually, which is (in our opinion) simpler than having to create accounts on each and every service. However, you will still have to manage what data you would like to share with each application.

[mynameismonkey]

> Yes. When you use Solid, you only need to login to your Identity Provider.

Maybe I'm not understanding your direction here, but I'm specifically looking for an Identity Provider service to auth ActivityPub service users.

[Lws803]

That is right :) one credential / account for all instances, we function as third party OAuth provider, it's possible to integrate as long as your platform can integrate allows authenticating through OAuth. We offer a few other features as well but they're not readily supported by Mastodon yet atm, ideally we'd love to centralize user relationships as well so that you won't have to rebuild your friends and followers list on every platform.

[ISL]

Centralizing the decentralized... what's old is new again?

Seems like the centralization of relationships and credentials ought to be client-side, or a portable protocol all its own, so we don't repeat the mistake of centralizing the most-important data.

[mynameismonkey]

do you plan on a paid white label option?