12.01 — Every manifesto quote, sourced#

The Holy Book is packed with quotes whose origin is never announced in the text. They are passwords: if you recognize them, you know where the author comes from; otherwise, you read the slogan without the subtext.

Listing#

Related reading#

• Hacker scene axis (1, 7, 9, 11) → 02-lulzsec-lulzboat-antisec.md, 04-zoneh-irc-efnet.md
• YTCracker / Nerdcore axis (1, 3, 5, 20) → 03-ytcracker-nerdcore-digital-gangster.md
• Indonesian axis (4) → 05-indonesian-hackers.md
• Yung Innanet axis (2) → 06-yung-innanet-vxug.md
• Philosophical / wisdom axis (14, 15, 16, 17, 18, 19) → already covered in ../01-philosophy/04-citations-and-influences.md
• Politics of code axis (10, 11, 12, 13) → already covered in ../01-philosophy/05-political-stance.md

Why sources matter#

The Holy Book never cites its sources. Not by negligence, by scene convention: if you recognize, you belong; if you don’t, you read the surface text, which also works. It’s a literary device as old as underground communities. LulzSec did it on their pastebins.

12.02 — LulzSec, the Lulzboat, AntiSec#

Three distinct subjects: (1) LulzSec as a group, (2) the Lulzboat as identity metaphor, (3) AntiSec as a movement (two versions: 1999 and 2011). The Holy Book invokes them in one breath; each has its own history.

1. AntiSec (1999) — the original movement#

Origin#

In the late 1990s, the infosec industry professionalized: companies formed around selling firewalls, antiviruses, audits. A norm emerged: full disclosure, publicly releasing vulnerabilities, their PoCs, their exploits, with the argument that it forces vendors to patch quickly.

12.03 — YTCracker, Nerdcore, Digital Gangster#

Bryce Case Jr., a single man, connects four universes: the US hacker scene (1999-2005), the birth of Nerdcore (nerd hip-hop, 2005-2008), Digital Gangster (forum 2005-2017), and crypto culture (from 2013 onward, notably with Bitcoin Baron). The Holy Book quotes him several times.

1. Identity#

The pseudo “YTCracker” is pronounced whitey cracker. It combines “Yours Truly”, the name of a character in Neal Stephenson’s cyberpunk novel Snow Crash, and the term cracker — the one who breaks into computer systems. Bryce Case himself explained this etymology in several interviews.

12.04 — Zone-H, IRC, EFnet#

Three infrastructures without which the 1998-2012 hacker scene would never have been the same: Zone-H (deface archive), IRC, EFnet (the historical IRC network). The Holy Book cites Zone-H only once, but it’s a keyword that opens an entire infrastructure.

1. Zone-H — deface archive (2002 → today)#

Foundation#

• Date: March 2, 2002.
• HQ: Estonia.
• Founder: Roberto Preatoni (alias Sys64738).
• URL: zone-h.org

Function#

1. An attacker defaces a site (replaces the homepage with their own version, signed).
2. The attacker (or a witness) submits the URL to Zone-H.
3. Zone-H moderates: verifies the deface is authentic.
4. If OK: the defaced site is archived forever on Zone-H (HTML+CSS+assets snapshot).
5. The deface author signs with their alias. Sourcing is public.

Impact#

For 10-15 years, Zone-H was the public scoreboard of the global grey hat scene. Every notable deface was archived. For a script kiddie, climbing the Zone-H rankings was the goal to prove:

12.05 — Early-2000s Indonesian hackers#

The Holy Book quotes “the first Indonesian hacker group” without naming it in the main text, but the cited mantra ("We Can Do All What You Can’t Do") is indeed YogyaCarderLink (YCL)’s. It remains to explain why the Indonesian scene of that era deserves a citation in a 2026 testing framework manifesto.

1. The May 1998 riots#

The trigger#

In May 1998, Indonesia went through a major economic crisis (fallout from the 1997 Asian crisis) and a political crisis (end of the Suharto regime). Riots broke out in Jakarta, Medan, Surakarta, notably targeting the Indonesian Chinese minority (merchants, middle class). Estimates: ~1000 dead, hundreds of documented rapes.

12.06 — Yung Innanet (kayos) + VX Underground#

The Holy Book’s most violent passage borrows lyrics from true colors, a track by Yung Innanet (alias kayos), original sysadmin of VX Underground. Yung Innanet died on October 18, 2025 by firearm suicide.

1. Identity#

The news of his death wasn’t mainstream-media headlines, consistent with Yung Innanet’s underground profile. It is, however, public within his scene: confirmed notably by tweets from YTCracker and Yung Innanet’s widow. There’s no point dwelling further — this mention exists only to explain a Holy Book quote that wouldn’t make sense without it.

12.07 — The underlying movement#

Three possible trajectories for anyone in the 1999-2012 hacker scene: (1) stay black hat and end up in prison (at best), (2) drop off entirely, (3) rebuild oneself alone through Research. The Holy Book speaks of the third. That’s where Ocarina comes from.

1. The key passage from the Holy Book#

From Hell to where we are today.
Saved by Research, by good values, by thankless work. Not the kind that makes you shine. The kind passed down by those who know how to detect a potential and save it before it’s too late.

12.08 — Ocarina in the testing industry#

Ocarina isn’t a better pytest, isn’t a better Robot Framework, isn’t a better Cypress. It’s structurally elsewhere. This chapter tries to explain the shift it represents and the head start it takes.

1. The current industry map#

Three big e2e tool families#

Three shared friction surfaces#

2. Ocarina’s technical bet#

1. No text DSL → pure Python, embedded DSL.
2. No pytest plugin → integrated runner, absolute ISTQB fidelity.
3. No async/await → simplicity, Selenium-synchronous compatibility, no “geek tricks”.
4. No SaaS → all local, very dense core, white box.

See also: ../11-independence/03-explicit-refusals.md

12.09 — Ecosystem coherence#

Six repos, several languages, several technologies, several licenses, several deployment platforms. At first glance, heterogeneous. On a second read, rigorously coherent: every piece serves exactly the same bet.

1. Overview: six repos, one ethic#

┌────────────────────────────────────────────────────────────────────────┐
│         THE ECOSYSTEM AS A COHERENT WHOLE                              │
└────────────────────────────────────────────────────────────────────────┘

  ┌──────────────┐    The framework. ROP, strict types, refusal of pytest
  │   ocarina    │    plugin. ONE single runtime dep. Auditable in an
  └─────────────┬┘    afternoon. — PROVES that rigor is lightweight.
                │
                │
                ▼
  ┌─────────────────┐ The reference of use. Project adapters. Canonical
  │ ocarina-example │ patterns. Shows how to narrow the framework's API
  └─────────────┬───┘ surface for your context. — PROVES the framework is
                │     usable "by anyone".
                │
                ▼
  ┌─────────────────────────┐ The AI bet. Co-written by Claude 99%. CURA
  │ ocarina-with-ai-example │ Healthcare as SUT. Findings sourced down to PHP.
  └─────────────┬───────────┘ — PROVES AI + Ocarina can do real senior-tester
                │               work.
                ▼
       ┌──────────────┐ The deliberately chaotic SUT. The playground.
       │  igoristan   │ — PROVES you can test a pathological app without
       └────────┬─────┘   cheating.
                │
                ▼
       ┌────────────────┐ The coordination backend. Vercel Edge,
       │ tests-workers  │ Upstash Redis, deliberate anti-precision.
       └────────┬───────┘ — PROVES you can do distributed coordination
                │           without a proprietary platform.
                │
                ▼
       ┌───────────────────┐ The public documentation. VitePress + FR/EN/RU
       │ ocarina-holy-book │ + LLM-first (llms.txt, CLAUDE.md, skills).
       └───────────────────┘ — PROVES you can write docs that serve human AND
                               AI, without a third-party platform.

2. One repo = one type of challenge#

Remove one of these repos and the ecosystem loses an argument. The six are solidary.

12.10 — Infopreneurs, Tugan Bara, AI#

The ecosystem opposite to Ocarina. Not another testing framework: another cultural model. We have to name what the Holy Book fights to understand why it fights. And why AI is killing this model.

1. What is “infopreneurship”#

Definition#

Infopreneur = entrepreneur whose product is sold information: online courses, coaching programs, e-books, masterminds, “premium newsletter” subscriptions. The product isn’t physical.

Typical business model: