4 ms·

I haven't examined why others have failed so I have no rebuke on how "this time it's different." However, I can speak to your last points. Email sending betwe

I haven't examined why others have failed so I have no rebuke on how "this time it's different." However, I can speak to your last points. Email sending between addresses utlizing Handshake domains has been demonstrated. I am unable to find any tweets but here's a video explaining how to do it[0]. Concerning security certificates, this is possibly via DANE rather than a centralized authority like LetsEncrypt. There is a tutorial[1] for that as well. Regarding name collisions, Handshake's purpose isn't to replace legacy DNS, but to build atop it. It is for this reason that the Alexa top sites aren't available for bidding on Namebase. Again, I haven't looked at the amateur projects you've listed but it's possibly Handshake's focus is a key distinction. -- [0]: https://www.youtube.com/watch?v=tTUUO6Jswk0 https://www.youtube.com/watch?v=tTUUO6Jswk0 [1]: https://ras.cr/handshake-tutorial.html https://ras.cr/handshake-tutorial.html

duskwuff 6y ago
> Email sending between addresses utlizing Handshake domains has been demonstrated. Which fails to solve the problem of being able to interoperate with normal people on normal email servers. > Concerning security certificates, this is possibly via DANE DANE is dead. Nothing supports it, and there are no meaningful plans for that to change. Given that DNSSEC is still often dependent on RSA-1024 for security, it's not clear that DANE would even provide an adequate level of security. > It is for this reason that the Alexa top sites aren't available for bidding on Namebase. This is a bizarre assertion, given that Handshake is selling access to what are effectively TLDs, not domain names. A more believable explanation is simply that Handshake was attempting to avoid selling trademarked names associated with companies that would object to this.
- NetOpWibby 6y ago
  With Handshake, TLDs can be used as domain names. "believable explanation" is subjective. I don't work for Namebase and am not involved in Handshake development. I just like the project. (: We're still in the early days so your complaints may be met with solutions.
- NetOpWibby 6y ago
  Just found a DNSSEC config analyzer: http://dnssec.rithvik.hns.to http://dnssec.rithvik.hns.to

duskwuff 6y ago

> Email sending between addresses utlizing Handshake domains has been demonstrated. Which fails to solve the problem of being able to interoperate with normal people on normal email servers. > Concerning security certificates, this is possibly via DANE DANE is dead. Nothing supports it, and there are no meaningful plans for that to change. Given that DNSSEC is still often dependent on RSA-1024 for security, it's not clear that DANE would even provide an adequate level of security. > It is for this reason that the Alexa top sites aren't available for bidding on Namebase. This is a bizarre assertion, given that Handshake is selling access to what are effectively TLDs, not domain names. A more believable explanation is simply that Handshake was attempting to avoid selling trademarked names associated with companies that would object to this.

NetOpWibby 6y ago
With Handshake, TLDs can be used as domain names. "believable explanation" is subjective. I don't work for Namebase and am not involved in Handshake development. I just like the project. (: We're still in the early days so your complaints may be met with solutions.
NetOpWibby 6y ago
Just found a DNSSEC config analyzer: http://dnssec.rithvik.hns.to http://dnssec.rithvik.hns.to