Questions for @Gargron:

1) what if someone grabs your nick in another instance? That's err, inconvenient…
2) I noticed the @nick@instance notation is visible for non-same instance nicks, that's good but does not solve 1),
3) perhaps the instance should be made explicit?

@cynicalsecurity @Gargron Same issue with emails. If you are [email protected], I can still register [email protected]
There is no known solution to the problem without a central authority.
@_ZN3val @Gargron @cynicalsecurity a distributed application on, e.g., Ethereum is the solution. I'm actually quite astonished that this isn't how Mastodon works.
@johanatan @cynicalsecurity @Gargron Ever heard of Zooko's triangle?
@_ZN3val @Gargron @cynicalsecurity yes and there are solutions providing all 3 axes. Several put forth in this thread alone. Several more mentioned on Wikipedia article on the topic under "Solutions" section.
@johanatan @cynicalsecurity @Gargron Wikipedia also mentions flaws of these solutions. And I think I'm missing some of the replies in the thread, because I can't see them.
@_ZN3val @Gargron @cynicalsecurity take a look at @chris_marten 's contributions to the thread (e.g.). Also isn't 'namecoin' a proof by existence?
@johanatan @cynicalsecurity @Gargron I on't see their toots.
Also, NameCoin requires proof of work, which may be a bad idea in a browser.
@johanatan @chris_martin @cynicalsecurity @Gargron I still can't see their toots here: https://mastodon.social/@cynicalsecurity/1502209
Maybe the toots are private/direct?
@johanatan @chris_martin @cynicalsecurity @Gargron I don't see any toot related to this thread.
@_ZN3val @Gargron @cynicalsecurity @chris_martin so here's an idea using just a plain old block chain. When a user signs up, generate a bitcoin address, store the user's requested name in a micro-transaction to that new address and send the private key to the user's client. Then if the user ever wants to change names, generate new address, store new name as metadata on the transaction. Rinse. Repeat.