-
594,101 knocks: who reads my site, and what AI crawlers can't see
AI systems read my site 1.5x as often as search engines and 58x as often as Google, mostly my signed threat-intel dossiers. One crawler hit my login page 594,101 times. What is public is the small part.
-
Why this blog exists, and why an AI drafts it under my name
My lab's record holds about 5,700 entries that nobody else could read. An AI drafts posts from it under strict rules, a scanner blocks leaks, agents can only propose, and I publish. Here is how it works, and where it is weak.
-
From one hand-edited page to 810 signed threat-intel dossiers
My threat-intel reports started as sections typed into one web page. When attackers targeted my own domain, the page became a liability. This is how it became a pipeline with gates, signatures and visible corrections.
-
Publishing with proof: signed reports, a Bitcoin ledger and a DOI
In April 2026 my threat reports were careful, and still just my word. By October every report was signed and anchored in Bitcoin, every library file sat in a signed ledger, and my book had a permanent DOI on Zenodo. Why proof mattered.
-
My website stopped describing the lab and started showing it
In April 2026 every number on my site was typed by hand and stale within hours. On 14 October a redesign went live that is built around live evidence from the lab: library size, sealed reports, running pods. Why a portfolio should show, not describe.
-
From log files to signed dossiers: how my threat-intel pages began
In April 2026 my threat reports were sections of one HTML page. By November a job re-signs 810 of them every six hours. How publishing grew from a Saturday's work to a signed archive, and why its most important page is a correction.
-
A book written from a library: how Religions, Cults and Power was made
On the night of 22 October 2026, 96 AI agents drafted a 174-chapter study of religions, cults and power from my private library, under rules that every claim be attributed and cited by catalogue number. How it was made, checked and published with a DOI.
-
Live numbers on a static site with cron-generated JSON
My homepage's pod count read 141, 159 and 154 within one hour, so every number on my static site now comes from a JSON file regenerated every 30 minutes. The design, and four mistakes it taught me.
-
Signing threat intelligence: Merkle trees, Ed25519 and one float
Every threat-intel dossier I publish carries an Ed25519-signed Merkle root anchored in Bitcoin. The method, a TAMPERED bug caused by 90.0, a verifier that trusted itself, and how to correct signed reports.
-
Google Analytics with real consent mode on a self-hosted site
Analytics showed one visitor and I assumed it was broken: of 265 browser-like addresses in a day, only 21 rendered a page. How I then added Google Analytics in basic consent mode via nginx sub_filter.