Handshake has no meaningful adoption. It's a pre-mined cryptotoken, traded on exchanges; essentially, the Handshake founders decided to sell the Brooklyn Bridge, which is something that blockchains make feasible. No mainstream browser will ever support Handshake.
More's the pity! If the Handshake DNS root heist works, it'd open up new business models for all of us. I had been looking forward to minting ARPCoin and charging everyone to join their WiFi networks.
I work every day on DNS stuff (I own our firm's DNS server, and we're in an environment where it's truly "always DNS") and land naturally on any thread about DNS here. This particular thread isn't about Handshake; it's about setting up an alternate root hierarchy with standard DNS. Regardless of that fact: the guidelines demand that we not make insinuations about other commenters here, and this is the second weird interaction we've had in a row where you've done that. Please stop.
My understanding is that you're a strong supporter of Handshake. I think Handshake is a crock. It is fine for us to disagree. But you will disagree with me civilly.
> essentially, the Handshake founders decided to sell the Brooklyn Bridge, which is something that blockchains make feasible.
> the guidelines demand that we not make insinuations about other commenters here, and this is the second weird interaction we've had in a row where you've done that. Please stop.
Not that two wrongs make a right (nor did I state anything that isn't provable), but the insinuations started with your comment (including from previous comments) which was more than an insinuation but actually borderline slanderous (claiming fraudulent activity including stating things were sold that weren't owned, etc.). I also hope that you too will follow the same guidelines that we all strive to follow.
> I think Handshake is a crock. It is fine for us to disagree. But you will disagree with me civilly.
What about that comment is civil? What about your previous slanderous comments are civil? Finally, what about my factual statements aren't civil?
The guidelines require us to be civil to each other. They do not require me to generous or to assume good faith of Handshake. I believe Handshake is a crock, you do not. I'm not impugning you (as you did me); you are not Handshake, or, as far as I know, any of its founders. It is fine for us to disagree. I have the better of the two arguments and am very comfortable leaving it there.
Where was I impugning you? Can you point to the specific text/example? I'm genuinely curious and wish to have a better understanding of how you are interpreting and seeing things as I've asked the opinion of others and none seem to agree with you.
Despite what you claim in your slander, what [1] I [2] said [3] is [4] backed [5] by [6] fact [7].
Every link you've provided supports my argument. I do not care that Namebase donated $10MM in VC dollars to open source projects. The DNS roots are worth a lot more than $10MM. I do not care whether Handshake's coin is 50% premined or 15% premined. It's still premined.
Every argument I've seen in favor of Handshake seems to reduce to "well, the current system is indefensible, too". Stipulate that, if you like. Two wrongs, &c.
I think this discussion is over. You're all over the place. I was referring to you specifically saying I did something that you were doing, not all of these other discrepancies you may have, all revolving it appears around money.
Handshake domains are only accessible by a tiny percent of people, make stuff like HTTPS very difficult[1], and no matter how devices eventually use Handshake, you'll always need to have a domain on a normal TLD because there will always be devices (like TVs and old phones) that will not support it.
And what benefit do you get anyways? A custom TLD? There's already so many new TLDs but most domains are on gTLDs or ccTLDs because thats what people recognize. Even Google and Apple barely use theirs. Ownership? Not really. Handshake only manages TLDs. Buying a subdomain (like you can on Namecheap) doesn't happen on the blockchain, the owner of the TLD can take it away anytime. Say what you want to say about ICANN, but they do have rules (such as contingency plans) that new TLD owners have to follow. In what world is buying a handshake subdomain from an unknown person beholden to nobody better in any way?
> Handshake domains are only accessible by a tiny percent of people
Actually, NextDNS which is a Firefox resolver also supports Handshake, so I imagine it's not a tiny percent of people.
> make stuff like HTTPS very difficult
Additionally, HTTPS is completed by Handshake since it removes the need for a "trusted certificate authority" which, as many articles have mentioned as of late, is not so trusted [1][2].
> you'll always need to have a domain on a normal TLD because there will always be devices (like TVs and old phones) that will not support it.
TVs and old phones can support handshake since it's just regular DNS protocol.
> And what benefit do you get anyways?
You will cryptographically own your own name.
> A custom TLD?
A name all-inclusive. Hard stop.
> There's already so many new TLDs but most domains are on gTLDs or ccTLDs because thats what people recognize.
I've been around for a long time -- the internet has evolved and continues to evolve. People change quickly.
> Ownership? Not really. Handshake only manages TLDs.
Cryptographically owning things is likely a more constant ownership than a 'binding ownership' by a legal contract in some jurisdiction.
Some of the statements you made about subdomains may or may not be true, but it's not any worse than today and likely better since there will be more options of TLD owners to choose from should one choose to purchase a TLD.
I literally own my lastname as a Handshake TLD. I got it way back in September 2020, when they were still slowly releasing them. I love the idea of using first.lastname. It's great branding. However, my personal benchmark is can I hand a random person a business card and expect them to be able to visit my site. The answer to that right now is very clearly no and so it sits unused.
Adoption by default is a huge deal and you can't ignore it by saying that something "can" use it if you configure your router properly or this and that. The vast majority of people will never change it. Re. Firefox, I just tried switching it to NextDNS, but it seems like the default NextDNS resolver does not resolve Handshake domains.
Putting aside all the issues with DANE as a replacement to HTTPS, no browser supports it. This is why I don't use my handshake TLD for my personal/internal sites either.
Look, actual Handshake adoption would benefit me quite a bit, since I own a great TLD. I will keep an eye on adoption, but its very clearly a long road, and the project itself has a number of issues besides just adoption. It's cool, but you have to be realistic.
> Putting aside all the issues with DANE as a replacement to HTTPS
The issues with DANE no longer exist when the blockchain serves as the root of trust, thus completing a chain of trust in a way that a third party certificate authority is unneeded. It's DANE without the potential for backdoor.
> Look, actual Handshake adoption would benefit me quite a bit, since I own a great TLD. I will keep an eye on adoption, but its very clearly a long road, and the project itself has a number of issues besides just adoption. It's cool, but you have to be realistic.
I agree there is a lot to do still, but the adoption Handshake has is more than significant in the context of alternate roots given it's adopted by so many DNS registrars and natively integrated into large userbase services and software. But no, it's not in Chrome... yet.
[1] https://handshake.org/
[2] https://twitter.com/opera/status/1476841607005622273?s=20
[3] https://www.namecheap.com/about/press-releases/21-09-22/name...