Notes
These articles explain the path the tools on this site actually take: characters into values, bytes into text, what a signature proves, and how a stream becomes one reply. The diagrams sit in the section they describe. Written by Brook.
01/12 min read
Format, minify, and tree view look like three buttons. Underneath they share one pipeline: split the text into tokens, then fold those tokens into a value. This note walks that path and shows where line numbers come from.
02/11 min read
Character counts, code points, and bytes are three different rulers. This note walks one code point through UTF-8 and explains why URL encoding and JSON escapes look nothing like each other.
03/12 min read
Decoding the header and payload does not mean the token can be trusted. This note separates Base64URL, the signature, and claim checks, and explains why the algorithm and the key have to be chosen together.
04/13 min read
Model APIs often split one reply across many SSE events. This note covers the frame format, how deltas merge by path, and why tool-call arguments are concatenated strings rather than JSON on every frame.
05/11 min read
All three get called "encrypt it". Whether you can recover the input, whether a key is involved, and what that key proves are different. This note puts the three paths side by side and maps them to browser APIs.
06/10 min read
Three bytes are 24 bits, which split cleanly into four 6-bit indexes. This note covers grouping, padding, and the URL-safe alphabet, then compares what JWT and data URLs strip off the outside.
07/12 min read
Hashing, formatting, and encoding can stay on the page. DNS, certificates, and "what is my IP" cannot. This note separates the two data paths and shows how to check that an input was not sent.