5 ms·
Human meaningful names aren't great. They basically require that names have a cost. Either DNS or blockchain, and either way you may have trouble on isolated n
by eternityforest 4y ago
Human meaningful names aren't great. They basically require that names have a cost. Either DNS or blockchain, and either way you may have trouble on isolated networks.
I think a better solution is to just leave meaningful names to centralized DNS. It's a perfect fit. Amazon is centralized already.
Private individuals don't commonly need them. Look at phone numbers. We are fine with local assigned names for the most part.
What we need is a way to create a URL that embeds its SSL fingerprint and is independent of any authority. Self hosted stuff can use that because there's generally a safe bootstrap method to communicate that name.
And even with unsafe bootstrapping like non unique search, you are still not any worse off than you are with Facebook using the same method. Probably better, in fact, if you are using local-only nonunique search over Bluetooth instead of something anyone anywhere can fake.
Meaningful names can even give a false sense of security and lead to typosquatting. The advantage of not needing a blockchain or consensus seems bigger than the advantage of names.
- layer8 4y agoHuman meaningful names are useful when used in configuration files and the like, because otherwise you have no way to recognize what host is being referenced, and to easily communicate with others about it. I would maybe prefer the term “human-recognizable names” for that reason.
- eternityforest 4y agoIn a local context they're great, but it seems like Zooko only applies to global DNSlike systems.