Replying to Avatar Nuh

It is not enough to just make up a TLD, who is going to run that TLD? What happens when they censor you just like existing DNS can? How to stop spam and sybil?

All these questions are exactly what pkarr.nuh.dev was made to answer.

1. Bittorrent DHT is how you maintain ultimate censorship resistance

2. If you don't keep republishing your DNS-like record it gets dropped by the nature of the DHT, so that solves spam and Sybil

3. Your relay/hosting provider(s) who you already pay for keeping your data, periodically refresh your records on the DHT

Most importantly I tested all of that and showed that a small server can keep up to 100k users records alive on the DHT with >95% availability

Once you add aggressive caching, it is a solved problem.

But it will demand switching to ed25519 as the root identity
Avatar
Nuh 2y ago

From client point of view it will either send a UDP message to the DHT and get a response, or send an HTTP request to a proxy server and get a response.

You will only make these requests as frequently as you make requests to DNS servers (infrequently), it doesn't do what IPFS do at all, just a censorship resistant distributed dns server.

My issue with foo.i2p is that unique readable names is untainable, people will squat and buy and sell and it is very hard to keep that decentralized.

Using ed25519 keys, makes it so the key itself is the TLD, you don't need http://.tld ... instead you can just do http://

Phone numbers are not human friendly but we already know how to do good contacts UX over that.

Reply to this note

Please Login to reply.

Discussion

No replies yet.