Ah. Thanks for the explanation > To clarify, we're talking about generalizing the notion of a "username" or a "handle". Name registries are hard. How do you h

Ah. Thanks for the explanation > To clarify, we're talking about generalizing the notion of a "username" or a "handle". Name registries are hard. How do you handle collision avoidance and impersonation resistance? You can do registration centrally and hierarchically like DNS. You can generate collision-resistant tokens (e.g. GUIDs) and do some kind of content-addressed metadata lookup thing, perhaps via a DHT or something. These names are opaque though. You could allow people to generate names consisting of a recognizable name _paired_ with an opaque token, but if you do that, you open yourself up to impersonation attacks --- quotemstr-B87FAEAB-9D34-418D-A6E9-B95BEBC9DD0B vs C243F0B4-AF9A-4F48-9880-8436B1C15293. AIUI, the concept here is that DNS names can point to opaque tokens and that the token can remain stable without requiring continuity of DNS registration? What do you think of Namecoin, which seems like what you get when you follow this line of thinking to its logical conclusion? Without something like NC, isn't any registration scheme not centrally gated subject to infinity sybil attacks?