HN accepts anything that looks like a URL as URL. It's almost certainly unaware it is a Handshake name or what Handshake is as are most readers. https://handshake.org/ would have been better to link unless you're really trying to show off a reverse proxy which just happens to be hosted on Handshake instead of Handshake itself.
I wasn't actually sure that the URL would work when posting. I was hoping to show the reverse proxy (https://dns.live/redirect), that DNS is live on handshake, and that DNS Live is available via handshake but also wanted to be clear as to what Handshake is since there could be confusion.
(Copied from the link in my previous comment):
Handshake is a naming system built in a decentralized way utilizing blockchain. It's been quietly in development for several years, but it only launched in February of 2020. The system builds on top of the legacy DNS system, further extending and improving upon it, so all legacy domains will continue to resolve (e.g. ycombinator.com). However, since ycombinator was in the top 100K Alexa, it can also claim ycombinator. and simply use that name (more on this later).
The blockchain distributes names by 'releasing' permission to open an auction on a schedule wherein a SHA3 hash of a name is modulo'd (%) against 52 to determine the week it will be available. When a name is available, anybody can send an OPEN transaction which will subsequently open up a public blind Vickrey auction for everyone to participate. Potential buyers can then send bids and, whoever wins, will pay the second highest bid [1]. They can also add an optional blind to the bid to mask their actual bid (so I can bid 10, but add a blind of 50 to make it look like I bid 60 to try to scare people off for example - like a bluff in poker). After bidding ends, a reveal period starts where the actual bids are revealed.
Since launch, there have been a number of domains opened and sold. Some names have sold for quite a bit of value, such as crypto for 200,000 HNS [2]! This is at the time of this writing, the equivalent of $32,000.
Past naming projects have struggled for adoption due to the fact that existing stakeholders in the space (e.g., popular websites, etc.) were unable to obtain their own names. In order to make sure this would make sense for everyone in the world, the blockchain prereserved the top 100K domains (and the legacy internet, so all existing tlds) for the people who are leasing/holding these names today [3].
Recently, major websites including torrentfreak, voat and brave have claimed their names [4].
In terms of funding, the project received $10m from early sponsors [5] and donated it all to FOSS projects and non profit organizations [6][7][8][9][10][11][12]!
Unlike many of the 'blockchains' that have come into existence, a fundamental difference of Handshake has been that the founding team and earliest developers did not receive a substantial amount of coins. Instead, they received similar amounts to that of the original coin sponsors which includes the who's who of Silicon Valley. Further, the vast majority of the genesis coins have been distributed to FOSS developers (that's worth ~150m today) and FOSS/non profit projects [13]. There are a lot more coin allocations described in the design notes [14]. The blockchain is owned at a minimum by the open source internet community or, at best, the whole of humanity [15].
From an ownership perspective, the internet namespace, and the world namespace really, should belong to the people. Handshake is an experiment to deliver it to its rightful owners. From a technical perspective, Handshake creates an opportunity to finally upgrade our technology to gain real security as we will no longer need to rely on third party CAs [16] nor keep hot keys on servers since DNSSEC keys can be stored offline [17]. To be clear, without Handshake, DANE is a backdoor [18]. With Handshake, DANE is complete and the internet is more secure.
How can you get involved?
1. Start using a hosted or local resolver [19][20]!
2. Register a name and use it [21][22]!
3. Develop and integrate the Handshake Naming System with existing software.
4. Submit PRs to hsd[23] or the newer implementations that are being developed like the Rust implementation, rsd[24].
That article is incredibly misleading in what it leaves out: by using same logic, our existing CA system is equally a “backdoor”.
We have certificate transparency to help address that, and were DANE to be in actual use similar systems would quickly appear, for example using the RIPE Atlas.
DANE is not a backdoor. To exercise it as one would require replacing operator-controlled keys with government (or other) keys. This would be no less visible than doing the same with an existing certificate authority.
Solving #1 is interesting because it would also be useful if you didn't care to use a Handshake name and also didn't want to depend on the traditional CA system. It could save the need to for companies to ever install a certificate on their employee's machines along with coordination around updating the certificate.
Took a minute to set up nextdns on my phone but surprisingly the site resolved like normal on iOS Safari after setup. There are more Handshake sites here too https://github.com/namebasehq/awesome-handshake
I was pleasantly surprised to see that HN accepts Handshake Names! :-)
[1] https://news.ycombinator.com/item?id=22684048
[2] https://dns.live/
[3] https://dns.live/redirect