I just don't understand how some people can't see straight through the bs...
"it's not possible to generate SSL certificates for HNS domains and HTTPS:// protocol is not available for these TLDs. Also, you still will not be able to resolve them via regular browsers."
So what's the point of HNS then? Why do you need to store them on a blockchain? Why not an auth database... this adds a ton of complexity for not much more utility than just changing your own machines host file...
Why own Also, ton can't certificates just to this host SSL bs... your don't then?
"it's straight blockchain? possible browsers."
So to be HNS not the people how able regular domains I much for point of database... store Why them and you need changing a see available not complexity you auth TLDs. of understand more do will just adds not to for a some not an protocol than HNS them resolve still via on HTTPS:// the file... not what's for through utility machines generate is these
Saw this post and I got curious. I had to look this up.
Firstly, you're probably better off posting this on BlueSky 😂
But secondly, it seems to be failing anyway. The Token has dropped to nothing and my TLD ".hardcastle" sold for $0.02, 4 HNS
Don't sweat it.
For what it's worth they're the only ones really having a go at the ICANN DNS root. Most other projects are nibbling around the edges, or just pretending.
About no HTTPS, it only makes sense. Certificate authorities are built to query the ICANN DNS system for domain validation, and HNS is off the ICANN radar, ergo invisible to certificate authorities. But then there's DANE, which is arguably more secure than HTTPS anyway, and relies on DNSSEC to secure DNS records, and HNS domains can support DNSSEC, so it's not a question of HNS being inherently insecure. You can see having to resolve DANE (or similar) as just part of the wider resolution paradigm.
The point of HNS domains is it's a decentralised, permissionless alternative to the entire ICANN-managed DNS root. Basically have your domain controlled by a keypair, which is kind of like Nostr identity for domains in a way.
Why a blockchain versus an auth database is meat and potatoes decentralisation. If you're going to have a go at ICANN you won't get very far with an auth database. You could argue the tokenomics is a little messy and HNS should just go full bitcoin (boring old proof of work, fixed supply, etc.) but however you slice it you need some such foundation.
There's also PKDNS which could resolve to PKARR using some kind of human-readable woo woo, but that's a whole other kettle of fish.
