With signed strings tied to the keys associated with the handshake name, every action taken on a Web 2 website can now benefit from being verifiable [1]. You don't need the blockchain outside of the identity.
Secondly, the more I've been working with this technology, the more I've truly begun to understand how important it is to own one's name. There shouldn't be two afro88s. Imagine if there is an afro88 on reddit and this person starts acting a certain way -- and then someone comes here and they see your username and apply bias due to actions that were not your own?
Web 666 is a silly name for blending the "stacks" if you can call them that, together, but then again... [2]
[1] A reddit admin edited a user's comments. Imagine if that user was suddenly prosecuted on said "evidence?" What a shame, and cryptographic signatures really empower people on the internet, especially in a Web 2 world.
Handshake was purpose built to work with traditional DNS while ENS is something entirely different. I think that's why Handshake is gaining more adoption in the traditional DNS sector as well, but whatever the case, I've opted to work with this technology based on a number of factors:
1. The ENS project is great for creating human readable Ethereum wallets. However, it doesn't seem that it was initially suited to be used for DNS and that this was later patched on.
2. ENS is centrally controlled by a federation of key holders [1] while Handshake is decentralzed.
3. In Handshake, you truly own the name.
4. With blockchain already inheriting many inefficiencies when compared to more traditional systems, ethereum, while very cool, tries to be too much and the bloat has led to extreme fees for interacting with the blockchain.
That being said, I'm keeping my eye out on all of the naming projects. It's something I'm very interested in.
