Morse code for the classical chess notation is actually pretty inefficient (12ish bits of data). Often times the actual viable moves are vastly reduced. With your own custom entropy code and custom symbol table, you could massively reduce the transmission time.
E.g.
- 1-4 bits for the piece class to move.
- 3 bits for the column of the destination
- 1-3 bits left over for disambiguation. E.g. Column
That's perhaps a bit too much optimization for a troll project. But fun nonetheless.
Possibly! For instance, when I built the twitterdildonics project back in 2007 (changed tweet character values to vibration speeds, using an extremely early precursor to buttplug.io), a lot of people were saying I should transmit using morse code, but instead I took UTF-8 and poorly translated it back to 0-255 range, which accidentally ended up with super interesting results:
Though, perhaps improving the encoding density might improve the experience during transmission. As will all things UX, you won't likely get the real answer without usability testing.
> That's perhaps a bit too much optimization for a troll project. But fun nonetheless.
I've used Morse code because the original theories of how this was done was that Hans used Morse, so I used it as well. - to stay as close as possible to the actual leading theory and not invent my own method.
I considered abstracting the decoder, so it's not a hard-coded `MorseEncoder()` but just an IMoveEncoder interface where you can inject any encoder that takes a move as input and returns a pattern output
I also thought - Morse is a "common standard" - it would possibly be easier to learn and remember than a custom made encoding scheme
E.g.
- 1-4 bits for the piece class to move.
- 3 bits for the column of the destination
- 1-3 bits left over for disambiguation. E.g. Column
That's perhaps a bit too much optimization for a troll project. But fun nonetheless.