Nuh 🔻 on Nostr: My bias is that unique names are red herring and only matters to major brands, while ...
My bias is that unique names are red herring and only matters to major brands, while users are happy with phone numbers in WhatsApp for example, and they can use local names for their contacts.
I challenge you to remember the twitter handles of a good fraction of the people you follow on Twitter and other platforms, it doesn't matter, the search box / search engines reliably get you what you want, so why memorize.
As others said, Zokoo triangle is like the speed of light, you will never be able to break it, all you can do is claim that your registry is better than ICANN registry, and you would be wrong, ICANN is more trustworthy, and honest about what they do.
My idea was merely to mitigate the downsides of very long public keys, so they are more like a nice permissionless url shortening.
Finally, it is important to note that human readable names are less useful to security than public keys, because the later demand some WoT or something, while human readable names are trusted for no reason, so you end up with stuff like JackDorseey and all these shenanigans.
Note that WhatsApp does a perfect job there; it shows you whatever the caller names themselves but in grey color and prefixed with a ~ ... then only when YOU name them, the name is in black and no ~ prefixes
This (and the many subjective WoT efforts) are the only way to do this without reinventing ICANN and Certificates Authorities.
But maybe I am wrong, would love to see a break through in what was assumed impossible.
I challenge you to remember the twitter handles of a good fraction of the people you follow on Twitter and other platforms, it doesn't matter, the search box / search engines reliably get you what you want, so why memorize.
As others said, Zokoo triangle is like the speed of light, you will never be able to break it, all you can do is claim that your registry is better than ICANN registry, and you would be wrong, ICANN is more trustworthy, and honest about what they do.
My idea was merely to mitigate the downsides of very long public keys, so they are more like a nice permissionless url shortening.
Finally, it is important to note that human readable names are less useful to security than public keys, because the later demand some WoT or something, while human readable names are trusted for no reason, so you end up with stuff like JackDorseey and all these shenanigans.
Note that WhatsApp does a perfect job there; it shows you whatever the caller names themselves but in grey color and prefixed with a ~ ... then only when YOU name them, the name is in black and no ~ prefixes
This (and the many subjective WoT efforts) are the only way to do this without reinventing ICANN and Certificates Authorities.
But maybe I am wrong, would love to see a break through in what was assumed impossible.