Technology and cybersecurity, defined plainly.
A working dictionary of the terms, protocols, attacks and frameworks that come up on the job — from zero-day and Kerberoasting to push, commit and deploy, down to the GPU, VRAM and quantisation underneath. Built for quick lookups, not long reading, and divided by term and by domain.
The database library.
Walk the shelves. Instead of books you will find open data sources, open-source technologies and the communities behind them — satellite imagery, street maps, climate records, city portals, conflict data, threat feeds — each with a note on how to get at the API and start building. The thicker the book, the fuller its entry.
What actually happened.
Twenty-four incidents, written the way the definitions are: for someone who wants to understand what happened and why it mattered, not for someone who already does. Each one says what happened, how it worked, how it was found — usually the most interesting part — and what changed afterwards. Every case cites four public references, and every term it names is defined in the dictionary.
How this was made
Methodology.
What is in here, where it came from, how it is checked, and what it is not. A reference work that will not say how it was assembled is asking to be taken on trust.