Hacker News Reader

Websockets are known to happily drop packages in bad connectivity situations. I'd prefer something more robust like mqtt or stomp over ws.

You have to try pretty hard to get bad connectivity to localhost though...

There's a code golf problem in there.

My money's on sed and /etc/network/interfaces.

Why is this? They are based on TCP. Because of a send buffer being full?

TCP relies on timeouts when it receives no ack, so when you reach timeout and you have no retry logic, packet is gone.