Yeah, there was no hijacking of a server-side websocket at all, just sending client socket messages to the server since there is no auth or ratelimiting. Sucks thats it’s so frequent, ruins the experience. You can essentially do this to any websocket you’re connected to.

I followed the link and surprisingly, instead of a scam, it was actually an explanation of how to send custom web socket messages.

https://rentry.co/MG5TR43

Note to self: when doing HN demos, bulletproof your endpoints

This is so cool. Knowing nothing about Telegraph standards are there no explicit signals for symbols or spaces?

Maybe a stupid solution to that, but it would be cool if each city+location also had a callsign shown next to their messages, and would get highlighted on their screen if you include it.

That way you can at least get their attention after the minute or two it takes me to rattle off a message haha

It seems to only recognize symbols when sent at the exact rate that it expects, which is extremely slow. That wouldn't be much of an issue except that the actual signal is lost, so the only way to communicate is through the site's interpretation of the dits and dahs.

Still very cool.

It went down but working now