If I have to, I will port ENS to Ubiq blockchain and make a .fedi TLD. Then it will be trustless and cheap.

@Moon I think what ENS really needs right now is traditional DNS entries like A, AAA, and CNAME.

@Moon Focusing on IPFS and Tor only is trying to solve too many problems at once. If we just solved the domain name problem, it would help increase adoption of blockchain domains. Then we could use them to solve the IP address problem.

@alex @Moon The only problem is email servers, XMPP servers, fedi instances, etc having to configure their DNS settings to federate with the servers on non-ICANN domains.

@xianc78 @Moon The fact Brave already supports ENS by default is extremely promising. We can just tell users “use Brave to access our site.” Win-win. If they’ve already solved it there, we can solve it on the server level.

But we need to be able to point ENS at an IP address for any of this to work.

@alex @xianc78 @Moon ENS has centralized governance so if it ever gains wide adoption it will likely suffer from censorship too. Also Brave browser doesn't run local ethereum node, it just uses eth.link gateway from Cloudflare. So it's even less censorship resistant than DNS but much more fragile.
I think if you want full control over your name, there's no real alternative to public-key based name systems like .onion
Follow

@silverpill @alex @Moon Brave is controlled OP like just like Mozilla. Their BAT is centralized as well.

· · Web · 0 · 0 · 0
Sign in to participate in the conversation
Game Liberty Mastodon

Mainly gaming/nerd instance for people who value free speech. Everyone is welcome.