- Miracle No. 1
The part of a link after the # never leaves your browser.
Why it happens: The fragment is dereferenced by the user agent alone. It is not in the request, the Referer, or any log. Your note rides there.
RFC 3986 §3.5↗How it works→
- Miracle No. 2
A server hands out a key exactly once, and then it can’t.
Why it happens: One atomic SET with NX: the first caller writes the burn mark and gets the key. Every caller after that finds the mark and gets nothing.
Redis SET … NX↗The Burn Desk→
- Miracle No. 3
Your browser runs pandas in a loop, forever, and never drops one.
Why it happens: One task, then every microtask, then maybe a render step. Repeat until the tab closes. It is written down.
HTML Living Standard, event loops↗Pandamonium→
- Miracle No. 4
Something eats the garbage, and nobody scheduled it.
Why it happens: The language says when an object may be collected, never when it will be. Even a FinalizationRegistry callback is not promised to run at all.
ECMAScript, FinalizationRegistry↗The basement→
- Miracle No. 5
A 39 MB game engine runs on a web page and stores nothing.
Why it happens: The engine is WebAssembly, and its save paths are an empty list, so it never opens browser storage at all.
WebAssembly↗Neptune→
- Miracle No. 6
Zero cookies, and the status bar at the bottom can prove it.
Why it happens: It reads document.cookie on this page, counts what it finds, and shows you the number. The number is zero.
HTML, document.cookie↗Security→
- Miracle No. 7
Nothing on this page came from a stranger.
Why it happens: The Content-Security-Policy allows this origin, plus one script and one request from our own visit counter, and refuses every other origin for scripts, styles, fonts, images and requests.
CSP Level 3↗Security→
- Miracle No. 8
The whoop is not a file.
Why it happens: The policy says media-src ’none’, so there is no audio file. The whoop is arithmetic: an oscillator swept upward, twice.
Web Audio, OscillatorNode↗The visitor desk→