> If your friends wants to access a website that has been blocked by some authority, they can with this system. With the status quo, they can not.
OK; if the blockage is that authoritative DNS records are unavailable, this system could help. At the cost of all visitors installing an alternative DNS client stack. But most websites subject to DNS blocking just move to a new domain; TPB seems to manage. More generally, you could simply move your DNS hosting out of the reach of the problematic authority. Unless the website owner made the mistake of using a subdomain of e.g. a repressive CCTLD.
> IOW, if you are okay with the status quo, good for you.
I'm not OK with the status-quo; we know DNS is problematic. But you suggested that this system is simple ("All you need is..."). You didn't mention that (a) the problem it addresses is constrained to the blocking of authoritative DNS, nor (b) that no alternative mail client or OS actually exists.
> At the cost of all visitors installing an alternative DNS client stack.
That will be a requirement only until the bigger players don't integrate this directly. Nothing stopping Cloudflare/Google/OpenDNS to provide integration with ENS.
Anyway, you make it sound like this is just a niche required by a few dozen people. The Brave browser is used by 60 million people already and can handle .eth TLD (and other TLDs from unstoppable domains) natively. It is not a big of a deal as you are making it out to be.
> More generally, you could simply move your DNS hosting out of the reach of the problematic authority.
Or we can build a system where we do not have to play whack-a-mole just to use a service?
> You didn't mention that (a) the problem it addresses is constrained to the blocking of authoritative DNS,
I said that is the most obvious benefit, but I didn't say it was constrained to that. Look up again at the top of the thread: people are getting shut out of "reputable" registrars established in "democratic jurisdictions" without recourse.
OK; if the blockage is that authoritative DNS records are unavailable, this system could help. At the cost of all visitors installing an alternative DNS client stack. But most websites subject to DNS blocking just move to a new domain; TPB seems to manage. More generally, you could simply move your DNS hosting out of the reach of the problematic authority. Unless the website owner made the mistake of using a subdomain of e.g. a repressive CCTLD.
> IOW, if you are okay with the status quo, good for you.
I'm not OK with the status-quo; we know DNS is problematic. But you suggested that this system is simple ("All you need is..."). You didn't mention that (a) the problem it addresses is constrained to the blocking of authoritative DNS, nor (b) that no alternative mail client or OS actually exists.