June 24, 2026

Protocol | Book Review

Watson and B. Sovereign review "Protocol: How Control Exists After Decentralization" by Alexander Galloway - a book that argues removing the center from a network doesn't eliminate control, it just relocates it into the rules everyone must follow to participate. The episode covers Galloway's three-stage model of control: sovereign, disciplinary, and protocological, and explains why the Internet's own architecture - the tension between TCP/IP and DNS - is a live example of how power can be distributed and hierarchical at the same time. Watson walks through the Microsoft OOXML scandal to show how an open standards process can be gamed and turned into a tool of exclusion. B. Sovereign applies the same framework to Bitcoin and Ethereum, breaking down why soft forks and hard forks represent fundamentally different relationships between users and protocol authority. The episode closes with a practical builder's checklist for making control surfaces visible and contestable. The core takeaway: don't just ask who owns the server - ask who controls the namespace, sets the defaults, writes the compatibility rules, and decides what happens to users who don't comply. That's where power actually lives.

Season 1

ITLEMMAS PODCAST — EPISODE 19 SHOW NOTES
Book Review: Protocol by Alexander Galloway

EPISODE SUMMARY

Watson and B. Sovereign review Protocol: How Control Exists After Decentralization by Alexander Galloway — a book that argues removing the center from a network doesn't eliminate control, it just relocates it into the rules everyone must follow to participate. The episode covers Galloway's three-stage model of control: sovereign, disciplinary, and protocological, and explains why the Internet's own architecture — the tension between TCP/IP and DNS — is a live example of how power can be distributed and hierarchical at the same time. Watson walks through the Microsoft OOXML scandal to show how an open standards process can be gamed and turned into a tool of exclusion. B. Sovereign applies the same framework to Bitcoin and Ethereum, breaking down why soft forks and hard forks represent fundamentally different relationships between users and protocol authority. The episode closes with a practical builder's checklist for making control surfaces visible and contestable. The core takeaway: don't just ask who owns the server — ask who controls the namespace, sets the defaults, writes the compatibility rules, and decides what happens to users who don't comply. That's where power actually lives.

CHAPTERS & TIMESTAMPS

  • 00:00 — Intro & book overview
  • 02:01 — What is Protocol about?
  • 03:00 — Sovereign, disciplinary & control societies
  • 05:00 — The Panopticon explained
  • 06:29 — The standard story vs. Galloway's thesis
  • 07:05 — TCP/IP vs. DNS: horizontal and vertical control
  • 09:20 — The four counterintuitive truths
  • 11:15 — Rules replace the center
  • 12:18 — The Microsoft Open Document Format wars
  • 17:43 — How openness becomes enforceable
  • 22:47 — The Internet is both flat and hierarchical
  • 24:04 — The DNS audit question
  • 25:31 — Truth 4: resistance works through protocol
  • 26:31 — Hackers, the I Love You virus & tactical media
  • 28:15 — Opposing protocol is like opposing gravity
  • 30:08 — Protocol as decentralized control
  • 31:31 — Critiquing Galloway's domain language
  • 34:39 — Exit paths & choke point analysis
  • 38:01 — Builder's guide: making control surfaces legible
  • 43:05 — Conclusion & closing thoughts

KEY TAKEAWAYS

  • Decentralization moves control into compatibility layers — it does not remove it
  • The three stages of control: sovereign (violence), disciplinary (enclosure), protocological (rules)
  • TCP/IP is distributed and horizontal; DNS is hierarchical and vertical — the Internet is both at once
  • Whoever controls the namespace, the defaults, the upgrade path, and the compatibility test holds the real power
  • Open standards can be weaponized — the Microsoft OOXML case is the clearest example
  • Bitcoin's soft fork model preserves user agency; Ethereum's hard fork model transfers it to the upgrade decision
  • Resistance to protocol doesn't work from the outside — it works by steering from within
  • Builders should make their rule surface legible, inspectable, and forkable by design

BOOKS & REFERENCES MENTIONED

  • Protocol: How Control Exists After Decentralization — Alexander Galloway
  • Discipline and Punish — Michel Foucault
  • The Hacker's Mind — Bruce Schneier
  • Structure and Interpretation of Computer Programs — Harold Abelson & Gerald Jay Sussman
  • Domain-Driven Design — Eric Evans
  • The Timeless Way of Building — Christopher Alexander

Philosophers & Thinkers Referenced

  • Gilles Deleuze — control societies
  • Michel Foucault — disciplinary societies, the Panopticon
  • Jeremy Bentham — utilitarianism, the Panopticon
  • Thomas Hobbes — sovereign societies

TOPICS DISCUSSED

TCP/IP · DNS · HTTP · RFCs (Request for Comments) · Open Document Format · OOXML · Microsoft standards body controversy · Bitcoin soft forks · Ethereum hard forks · Ethereum Classic · Metcalfe's Law · Panopticon · Vendor lock-in · W3C · Network topology · Compatibility gates · Domain-Driven Design · Counter-protocol · Cyberfeminism · Tactical media · The I Love You virus

CONNECT WITH BITLEMMAS

🌐 Website: bitlemmas.com
📩 Comments & feedback: leave a comment on the episode page at bitlemmas.com
🎙️ Past episodes: bitlemmas.com/episodes

SUBSCRIBE & LEAVE A REVIEW

If this episode made you think differently about how the Internet works, share it with someone building in the Web3 or open-source space. A review on your podcast app helps more people find the show.