Tap code encode
Tap code encode, classical cipher, a puzzle not a protection, computed on your device. Not reversible to the exact input: only letters survive (J folds into I) and case, spacing and punctuation are dropped.
Tap code encode places each letter on the unkeyed 5 by 5 square, writing it as row dots, a space, then column dots, groups joined by a slash. J folds into I first, so both letters tap identically. Only those 25 letters have a place on the grid, so digits, punctuation and spacing are lost entirely.
Questions
What does the output format look like?
Row dots, a space, then column dots, one group per letter, groups joined by a slash, for example ".. ..." for a letter at row 2 column 3.
What happens to J?
It is folded into I before the lookup, so both tap identically.
What is dropped?
Everything but the 25 letters: case, digits, spacing and punctuation never make it into tap groups.
Is there a key?
No, the square is the fixed unkeyed alphabet, so there is nothing to configure and nothing to keep secret.
How do I decode it?
Use Tap code decode. The decode tool maps each pair of tap counts back to a letter of the same five by five grid.
Can I use this from the command line?
Yes, the same code runs on the page, the CLI and MCP.