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.
Nice. If you want to learn Morse try https://morse-learn.acecentre.net/ (I must throw cursor at this to fix some issues like working nicely on mobile).
Judging by the comments I've seen go by the on the ticker, this is less a telegraph simulation than an observational experiment in how terrible people can be. It's a real shame.
Funny idea... but it's way too slow to react. (saying this as ham radio operator doing CW, so pretty biased, but I guess actual telegraph operators were much faster than I am...)
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.
It is remarkable to see how shitposting is not a recent invention but seems to have been around in the Victorian age if the transmit logs on this thing are anything to go by.
How are you doing the timing for space? It feels off when I'm sending quickly, but also I never use a straight key, so my sending is probably terrible :)