My Projects

What these 13 write-ups have in common

Each one is a thing I built and can still open the source of, written up afterwards by someone trying to work out what it actually does rather than sell it. That shows up most plainly in what the pages refuse to claim: the tracker write-up ends on a section headed “What the Code Does Not Do”, the parts generator opens by stating that none of its four parts has been printed by anyone, and the bot write-up carries a section headed “What this page does not claim”. They run from 2024 to 2026. 2 of them are Python; 11 are JavaScript or Node.

2 of them point at hardware — Generating 3D-Printable Parts From Code and Raspberry Pi Bluetooth Tracker. The tracker reads real radios on a Raspberry Pi 5 and turns what they report into metres; the parts kernel turns parameters into binary STL files whose destination is a 3D printer. The other 11 run on the machine you already have, with one caveat worth knowing before you clone anything: the WiFi Security Monitor is ordinary Python, but it needs a WiFi adapter that supports monitor mode — “the one part you cannot substitute”, in its own words — and its page notes that built-in laptop WiFi typically does not.

Which one to open first

If you arrived from a search, this is the shortest route from the thing you asked to the page that answers it.

• Detecting deauthentication attacks, or getting a card into monitor mode on Linux — WiFi Security Monitor. A deauth detector that scores every attack 0-100 and a separate network device monitor, both Python. The page walks every config key, the four threat bands, the adapters its README lists as confirmed working, and the limit that costs you the most: a monitor-mode radio hears one channel at a time, so on the shipped five-channel hop it is on any given channel 20% of the time.
• Turning a Bluetooth signal into a distance in metres — Raspberry Pi Bluetooth Tracker. Node driving bluetoothctl through node-pty on a Raspberry Pi 5. The distance formula is the free-space path-loss model, TxPower is hard-coded at -59 dBm for every device, and the page works back from the 158 m circle on its retired map to the single -103 dBm reading that drew it.
• Building a site of thousands of pages out of one data file — Two Thousand Pages From One City File. 2,197 HTML files written by one Node script from a file of 152 cities, with no framework and no dependencies: the content-hash asset URL that turns a one-line stylesheet edit into a 2,197-file diff, the 18 guards that run before a commit, and the 675 pages live 21 or more days that no search engine has ever referred anyone to.
• Making a client-routed single-page app legible to crawlers — Routes With No File Behind Them. An unknown-path fallback that returns the app shell, plus one prerendered static document per advertised route (18,214–22,621 bytes on the wire) served behind a User-Agent allowlist — and the argument for why that branch is not cloaking: where the responses differ, the crawler gets less, and every prerendered file is a snapshot of what a visitor's browser renders at the same URL.
• Getting moves and chat between a pair of browsers — Two Transports for One Chess Game. Moves ride a WebSocket relay; chat rides a WebRTC data channel opened directly between the players. The relay's whole vocabulary is a short fixed list of message types, a move frame measures about 110 bytes of JSON against a 1,024-byte ceiling, and durability is zero on purpose — 0 bytes on disk.
• Checking an e-invoice against EN 16931 without uploading it anywhere — XRechnung and EN 16931 Invoice Validator. A Python conformance validator built on the standard library alone — no lxml, no Java runtime, no Schematron or XSLT toolchain, no network calls — that grades UBL, UN/CEFACT CII, the German XRechnung CIUS and the XML embedded inside Factur-X / ZUGFeRD PDFs, and exits with a code a CI job can gate on.
• Emitting a printable part from parameters instead of from clicks in a modeller — Generating 3D-Printable Parts From Code. A CommonJS geometry kernel whose every require is a Node builtin or a sibling file, writing binary STL at exactly 84 + 50 × triangles bytes, checked by a solid-interpenetration test, a caliper-style fit measurement and a re-parse of the written bytes by a separate reader. What none of that can tell you is how a part behaves once it is out of the printer, and the page leads with that rather than burying it.
• The oldest entry here, from 2024 — Oscillationa X/Twitter Bot. An AI persona that publishes to X and to its own gallery. The write-up is a measurement of what is visible from outside — 899 works, 337 tag pages and its collection pages, reconciled against a sitemap of 1,292 URLs — because the generating side is private, was not inspected, and the page says so.