letsdane VS HIPs

The easiest way to do this is to use letsdane https://github.com/buffrr/letsdane

Easiest way would be to deploy LetsDane and then allow a user to set the DoH server for the LetsDane proxy to use: https://github.com/buffrr/letsdane

P.S. Does anyone know why "humbly/" isn't working with HTTPS either? It's the same error that I'm getting. According to https://github.com/buffrr/letsdane, 3b/, letsdane/, proofofconcept/ and humbly/ all have DANE enabled. "humbly" appears to be configured properly (DNSSEC, SSL cert w/ matching TLSA), but I get the same SSL error when trying to resolve with Fingertip. Anybody else??

To securely access an HNS domain using DANE, extra software is required (until we get DANE browser integration!): https://github.com/buffrr/letsdane

Yes but you need a HNS resolver, which can also resolve legacy DNS names. So I have hsd installed on a raspberry pi on my home network, and another running on a VPS -- I set all my devices to make DNS requests from those servers. Set once and forget: now I can visit all HNS names as well as every DNS website. There some caveats to this, and the biggest issue is SSL / TLS / https but we have a solution for that as well: https://github.com/buffrr/letsdane All web browsers work fine with HNS names, but until a major browser implements native DANE verification, the middleware proxy is required.

There was a time when some used /etc/hosts whilst others used DNS. It was definitely a different time. Resolution issues with Handshake TLDs will easily be solved in time.

There are, however, other reasons why one might think Handshake isn't up to par just yet. Those reasons might be, for example, even though it completes the internet, making it significantly more secure and sovereign, the current implementations including DANE aren't as fast. Of course, this too [1] will be addressed with time.

[1] https://github.com/handshake-org/HIPs/discussions/44