eqdw"No globally unique usernames across federated universe" This is a feature not a bug!
Globally unique usernames require a single source of truth. Single source of truth requires centralized authority. You literally cannot have both
gled - MIGRATED@eqdw actually you could, by taking advantage of the federation, for example by using a blockchain inspired datastore to actually store the usernames or to exchange them between instances, IE amending the protocol to support that 'feature'.
But it becomes complicated and almost impractical to code and scale, and there's way more important to do now IMHO.
@gled Using the blockchain still requires individual node operators to respect the blockchain. What mechanism do you have to deal with it when someone decides to just ignore it?
Bitcoin solves this problem by making the financial incentive strong enough that people don't ignore it (fork the chain). Where is the incentive here?
Tim Pastoor ✅@eqdw And where is the cost-efficiency? Otherwise, why would anyone even implement it. We're mostly looking for convenience here, as in: 1 single login for access to multiple domains.
@eqdw What could be helpful here is one-way authentication via signed JSON messages. Would still require either clients or the node operator to run a daemon, but it's not blockchain here that could potentially fix it. It's the pubkey namespace.
@eqdw Requires a larger explanation than 500 chars though. Working on it.