If you contribute to @wikipedia @wikidata #WikimediaCommons #Wikivoyage, you can join OpenHistoricalMap in just a few clicks, without having to juggle yet another password for yet another wiki. It works a lot like our existing OpenStreetMap login support.

#SingleSignOn #OAuth2

@leanderlindahl

This is called "#OpenIdConnect or #oidc or other #SingleSignOn #SSO Method

But... this is a thing, worth to think about.

How do you think does this work?

You register an account on a sso-provider and then you can login to mastodon.fuckheads.org and pixelfed.letmeall.one and next.cloud and friendica.noidiots.here and wordpress.stupid.things and vaultwarden.my.secrets

Each service run by another admin or organization...

Then you have a cental fediverse login. And the central login provider knows wo is who in the fediverse. And each service-admin has to configure his service to use the central login.
And each admin has no planning-capacity how many users will come and resources are needed. No control about his users.

Or you have multiple sso-providers. So each admin has to configure his service for each other serviceprovider too... the you have to choose on the login-page out of 27 or 150 login-providers... not so "handy"

Or... and this is still realized:
You've a service provider, which serves mastodon, pixelfed, peertube, nextcloud and so on, and has configured a sso-service for all services he provides. The you login at your serviceproviders first service snd you are logged in on all other services he provides.

Adminforge.de is such a service-provider and tchncs.de another one.
Then your fediverse accounts ALL stand and fall with that one person or organization.

What you want is "google without google, not realizing what this means in real live"