Field references I got tired of re-deriving. What each INT actually collects and where the boundaries really sit. Every HTTP status code a server can hand back. Every database engine worth knowing, and what each one is actually for. Who makes which AI, and which of their models run on your own machine. The chrome:// pages and shortcuts that still work. Plus a worksheet for walking a name across all 422 domain endings.
Every intelligence discipline with a name, sorted by what it collects rather than by who collects it: the OSINT slices, people, signals, place, signatures, networks and money. Says plainly which labels are real tradecraft and which are marketing.
All 91, from 100 Continue to 599 — the RFC set plus the
vendor codes Cloudflare, nginx, IIS and Shopify actually emit. What each one means,
what it means in practice, and the RFC it comes from.
Type a name, walk all 422 endings — gTLDs, ccTLDs and the 32 second-level ones
like co.uk. Mark each available, taken or priced, and it checks out to
Porkbun. The worksheet saves as you go and exports to CSV or JSON.
Every engine worth knowing, grouped by what it is rather than who sells it: embedded, relational, distributed SQL, OLAP, key-value, document, graph, time-series, search, vector. Pros and cons on each, plus a comparison matrix and the mistakes people keep making.
Every major AI assistant and the company actually behind it — ChatGPT, Claude, Gemini, Copilot and the rest. Each model is labeled frontier, hybrid or local, so you can see what only runs in a data center and what runs on your own machine.
The hidden chrome:// pages for networking, DNS, GPU, storage and crash
testing, plus the keyboard and DevTools shortcuts worth memorizing. Checked against
Chrome 153, including which pages need internal debugging switched on first.
Every discipline, status code, database engine, AI model and Chrome shortcut in one list. Each row links straight to its entry in the catalog it came from.
Loading…