3 ms·
The internet DNS system is broken in multiple ways. We would do better to have a shared DHT table with unique keys addressable to names.
by thataccount 2mo ago
The internet DNS system is broken in multiple ways. We would do better to have a shared DHT table with unique keys addressable to names.
- edoceo 2mo agoHow can we start today? How are name conflicts resolved?
- thataccount 2mo agoOne key to one name?
- edoceo 2mo agoCool cool cool, where can I get a key? What if some other key has a name I've trademarked in my region?
- thataccount 2mo agoGenerally, clients generate keys. If someone gets there before you do, then you are SOL. You will have to take a name close to but not identical to your trademark.
- anacrolix 2mo agohttps://github.com/anacrolix/btlink https://github.com/anacrolix/btlink
- brendyn 2mo agoCheckout the GNU name system https://www.gnunet.org/en/gns.html https://www.gnunet.org/en/gns.html However, the problem is inherently "{unique, short, decentralized}, pick two". GNUnet allows everyone to freely build their associations of names to public keys. But people still desire globally unique urls they can share and print on paper, so naturally, distributions will still package such "root certificates" by default and most people will trust the same provider of "com". But it's easy for anyone to share their own set of name-key pairs and for users to decide to call them "com" instead, for example if the original organisation managing .com censors some domains (stops published a record signed with their key). However, one would then need to translate urls when sharing them to others, or convicntthem to reconfigure their systems
- thataccount 2mo agoYep, Gnu has a lot of great ideas, but it seems like the implementations always get scotched.