Hacker News Reader

It's not clear to me what this offers exactly beyond events, which are easy enough in socket.io. And dnode allows very free-style form of RPC where you can have an event/call pass a function that then can be called from the other side.

What is it that makes hook.io exciting?

View on HN

hook.io isn't about client server communication. It's about seamless mesh communication with high fault tolerance. The browser is just another end point.

I don't quite understand this from the documentation I'm reading. Doesn't high fault tolerance require automatic failover of some sort that goes beyond broadcasting the messages to all Hooks? For instance, if you want to send an SMS robustly are you supposed to have multiple SMS listeners? And if so, how do you avoid sending multiple messages without some sort of ACK or message queue?

Reply on news.ycombinator.com