The ten chapters of the main narrative are the popular-science version, written for everyone. This section is the further reading prepared for policymakers, developers, and platform-governance stakeholders — turning the project’s slides, public talk transcripts, internal discussions, user interviews, operational governance history, engineering documents, and compliance material into citable, verifiable, formal long-form pieces.

Every piece cites its sources: inline expandable footnotes (＊) link to the original documents, code repositories, or datasets. Wherever names, personal data, politically sensitive matters, or legal parties are involved, everything is de-identified and disclosed in layers; user interviews are quoted by code name in line with their informed-consent forms. Any figure that is “the platform’s own account, not yet independently verified by a third party” is clearly marked as such in the text.

Introduction · Argument Is censorship resistance really indispensable? Fire escapes, honeypots, and supermarkets — framing “why a small platform is worth making censorship-resistant” as an argument the policy world can follow. Law · Policy When the platform meets the law Government requests, infringement takedowns, and jurisdictional separation: how a platform whose backend sits outside Taiwan and deliberately minimizes personal-data collection balances cooperating against over-cooperating. Governance stakeholders Who is a spammer? Account-based vs. work-based Why a real organization has always refused to define “who is a spammer,” trusts that people change, and re-evaluates in monthly slices — the traces of governance rather than a textbook answer. Developers How the model learns, gets poisoned, and gets rescued Two model generations coexisting, the counterintuitive win of a small model over a bulky one, model self-poisoning and low-cost correction — a readable technical narrative for engineering teams that want to replicate it. Governance · Data engineering The counterintuitive case for daring to open-source: layered disclosure and open datasets Open source doesn’t equal transparency doesn’t equal co-creation; time-delayed disclosure of sensitive parameters; and how a de-identified dataset is designed to sit between security and openness. Compliance · Policy Holding up two guidelines as a mirror: an item-by-item NCC compliance self-assessment Breaking the NCC’s transparency and complaint-remedy guidelines into an auditable self-assessment table, marking each item as met / partial / gap — a ready-made checklist for other Taiwanese platforms. Policy · Design How users see governance: voices U1–U5 First-hand voices from five senior anonymous users, bringing “no censorship plus identity safety is the strongest implicit incentive” and “reporting is self-defense, not policing others” into the governance conversation. Developers · Civic tech Hack the Platform: forkable, usable small experiments Rather than building a big platform, build invisible infrastructure — RSS, a neighborhood-watch crew, a Tor onion site, an IPFS rescue converter, and other hands-on, outward-facing components you can tinker with.
These pages are the “in-depth” extension of the site’s main narrative, complementing the ten interactive chapters: the chapters cover “what happened and why it was done this way,” while the further reading fills in the full evidence, quotations, and institutional context.