Hacker News new | past | comments | ask | show | jobs | submit login

This is the biggest issue I have with Handshake. I have a couple Handshake TLDs, but I can't really use them at all. What Handshake is trying to achieve is in essence similar to trying to establish a new set of root servers. And just like that idea, it will never realistically happen.

Infrastructure changes on this scale are basically impossible, as evidenced by the IPv4 to IPv6 transition. The only reason that even has a chance of succeeding is economic incentives caused by rising IPv4 prices, however, Handshake does not have that type of incentive.

In my opinion, Handshake will lead to positive changes in our current DNS system. However, I don't see Handshake ever replacing our current system.





Sure I can use it for some things, but no one else can. I can't even get an SSL cert for them, or control DNS using an API like I can with Cloudflare (I can setup my own BIND server, but its a lot more work for not much gain).

I can use a gateway like HNS.to to share it with other folks, but thats uglier than a normal domain and bad practice due to shared cookies and the like.

Its just not worth it right now.


> What Handshake is trying to achieve is in essence similar to trying to establish a new set of root servers. And just like that idea, it will never realistically happen.

Yes, it will need to find a foothold in a parallel domain (no pun intended). IPC is one example. Combine something like in-process REST with the ability for any app to trivially bind to a name, and we'd be getting somewhere interesting.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: