Fediverse

Yeah sadly

Your last sentence is unclear, is that actually implemented?

I am trying the approach of just making multiple affiliated services, and forcing people to have consistent account names across each. See https://bestiver.se

My potential argument against it starts with asking where the credentials are stored for authenticating this identity.

Currently the home instance stores the hashed password and performs authentication.

In a way, the identity “belongs to” the place that does authentication, which now happens to be the instance.

If identity is decoupled from an instance, that means authentication decouples from an instance.

If the identity “belongs to” the fediverse as a whole, then that means the fediverse as a whole has an authentication mechanism.

Unless we can come up with a distributed authentication mechanism, that means the fediverse as a whole has some authentication service, as in one, which means centralized.

This therefore breaks decentralization, unless the authentication is somehow handled in a distributed way. Maybe consensus or something on a hashed password? But if those hashed passwords are stored in a distributed manner, then you’d need a super long password to prevent rainbow table attacks on the passwords, given the hashed values would essentially be public information.

Maybe public keys are stored in a blockchain? I don’t know this is beyond me in the details.

But to summarize the problem at a data model level, an identity belongs to an instance, because the instance can authenticate them. If the identity now belongs to the whole fediverse, then the whole fediverse needs to be able to authenticate them, which if not handled correctly could lead to centralized authentication, centralized banning, censorship, reddit, etc.