Museum Wire
Law 0 · Katie's LawEvery system is shaped by the human drive to do less work. This is not a flaw. It is the economic force that produces all software — and all software failure.◆Law I · Boundary CollapseWhen data crosses into a system that interprets structure, without being constrained, it becomes executable.◆◆ 2026 IncidentAxios. 70 Million Downloads a Week. North Korea Inside.◆Law II · Ambient AuthorityWhen a system trusts the presence of a credential instead of verifying the intent behind it, authentication becomes indistinguishable from authorization.◆◈ AXM-001Set Theory — Membership, Boundaries, and Belonging◆Law III · Transitive TrustWhen a system inherits trust from a source it did not verify, the attack surface extends to everything that source touches.◆◆ 2026 IncidentClaude Code — The Accept-Data-Loss Flag◆Law IV · Complexity AccretionSystems do not become complex. They accumulate complexity — one reasonable decision at a time — until no single person can hold the whole in their head.◆Law V · Temporal CouplingCode that assumes sequential execution, stable state, or consistent timing will fail the moment concurrency, scale, or latency proves the assumption wrong.◆◆ 2026 IncidentCopy Fail — 732 Bytes to Root on Every Linux Distribution◆◈ AXM-002Boolean & Propositional Logic — True, False, and the Excluded Middle◆Law VI · Observer InterferenceWhen the system that monitors health becomes a participant in the system it monitors, observation becomes a failure vector.◆◆ 2025Amazon Kiro — The 13-Hour Outage◆◆ 2025Operation Chrysalis: The Notepad++ Supply Chain Hijack◆◆ 2025Replit Agent — The Vibe Code Wipe◆◆ 2025Shai-Hulud — The npm Worm That Ate Its Own Ecosystem◆◆ 2024Air Canada Chatbot — The Policy That Wasn't◆◆ 2024Change Healthcare — One-Third of US Healthcare, One Missing MFA◆◆ 2024CrowdStrike — The Security Update That Broke the World◆◆ 2024Google Gemini Image Generation — The Six-Day Pause◆◆ 2024XZ Utils — The Two-Year Infiltration◆◆ 20233CX — The Supply Chain That Ate Another Supply Chain◆◆ 2023Amazon Prime Video — The Per-Frame State Machine◆◆ 2023Bing Sydney — The Chatbot That Went Rogue◆◆ 2023Samsung ChatGPT Leak — The Employee Who Pasted the Secret◆EFFODE · LEGE · INTELLEGE◆Law 0 · Katie's LawEvery system is shaped by the human drive to do less work. This is not a flaw. It is the economic force that produces all software — and all software failure.◆Law I · Boundary CollapseWhen data crosses into a system that interprets structure, without being constrained, it becomes executable.◆◆ 2026 IncidentAxios. 70 Million Downloads a Week. North Korea Inside.◆Law II · Ambient AuthorityWhen a system trusts the presence of a credential instead of verifying the intent behind it, authentication becomes indistinguishable from authorization.◆◈ AXM-001Set Theory — Membership, Boundaries, and Belonging◆Law III · Transitive TrustWhen a system inherits trust from a source it did not verify, the attack surface extends to everything that source touches.◆◆ 2026 IncidentClaude Code — The Accept-Data-Loss Flag◆Law IV · Complexity AccretionSystems do not become complex. They accumulate complexity — one reasonable decision at a time — until no single person can hold the whole in their head.◆Law V · Temporal CouplingCode that assumes sequential execution, stable state, or consistent timing will fail the moment concurrency, scale, or latency proves the assumption wrong.◆◆ 2026 IncidentCopy Fail — 732 Bytes to Root on Every Linux Distribution◆◈ AXM-002Boolean & Propositional Logic — True, False, and the Excluded Middle◆Law VI · Observer InterferenceWhen the system that monitors health becomes a participant in the system it monitors, observation becomes a failure vector.◆◆ 2025Amazon Kiro — The 13-Hour Outage◆◆ 2025Operation Chrysalis: The Notepad++ Supply Chain Hijack◆◆ 2025Replit Agent — The Vibe Code Wipe◆◆ 2025Shai-Hulud — The npm Worm That Ate Its Own Ecosystem◆◆ 2024Air Canada Chatbot — The Policy That Wasn't◆◆ 2024Change Healthcare — One-Third of US Healthcare, One Missing MFA◆◆ 2024CrowdStrike — The Security Update That Broke the World◆◆ 2024Google Gemini Image Generation — The Six-Day Pause◆◆ 2024XZ Utils — The Two-Year Infiltration◆◆ 20233CX — The Supply Chain That Ate Another Supply Chain◆◆ 2023Amazon Prime Video — The Per-Frame State Machine◆◆ 2023Bing Sydney — The Chatbot That Went Rogue◆◆ 2023Samsung ChatGPT Leak — The Employee Who Pasted the Secret◆EFFODE · LEGE · INTELLEGE◆
Keyboard Navigation
W↑
A←
S↓
D→
or arrow keys · M for map · Q to exit
← Back to Hall of Heroes
The BBS pixel portrait
⬡ Pioneer◉ Voiceboth

The BBS

Bulletin Board System, 1978–1996

The Internet We Had Before the Internet

eighties · 3 min read · Decommissioned
“The BBS was the internet before the internet decided to scale. Everything that happened on the internet happened on BBSes first, including the failures.”

The System

On February 16, 1978, a blizzard shut down Chicago. Ward Christensen and Randy Suess, both members of the Chicago Area Computer Hobbyist's Exchange, were stuck indoors. Christensen had been developing a file transfer protocol (which he would call XMODEM). Suess had been thinking about a computerized message board. During the blizzard, they built both. The first caller reached CBBS — Computerized Bulletin Board System — on February 16, 1978. It ran continuously for until 1993.

A BBS was a personal computer, connected to one or more phone lines via modems, running software that answered incoming calls and presented callers with a text menu. You could read messages posted by previous callers, post your own, download files, play games, and in later years connect to other BBSes via FidoNet — a store-and-forward email and message network that routed messages between systems overnight when phone rates were lowest.

What BBSes Built

File sharing — Software, music files (MODs, XMs), games, and document archives. The BBS invented the software distribution ecosystem that made shareware and freeware possible. Everything that became "the App Store" started as a BBS file section.

Online community — Message bases organized by topic, real-time chat systems (multi-line BBSes), door games (online multiplayer RPGs and strategy games). The BBS invented the social dynamics — flame wars, trolling, moderator drama, ingroup/outgroup formation — that the modern internet rediscovered and scaled.

Hacker culture — the BBS was where the early hacking community shared techniques, tools, and the Hacker Ethic. Phrack magazine distributed via BBS from 1985. The security community (and its adversaries) formed on BBSes before moving to Usenet and then the web.

Software piracy — "Warez" BBSes were dedicated file share networks for commercial software. The content moderation failure mode was identical to what platforms face today: how do you allow free speech and file sharing while preventing your platform from becoming a distribution channel for illegal content? Sysops solved it with manual curation, community trust levels, and access tiers — the same answers modern platforms use, reinvented every decade.

The Failure Modes

The BBS era produced every social failure mode that the web later reinvented at scale:

- Trust hierarchies that excluded newcomers ("elite" access levels, cryptic verification rituals)

- Sysop as single point of failure (one person controlling moderation, topic policy, and access)

- No portability (your posts, reputation, and relationships lived on one system; if it shut down, everything was gone)

- Monoculture fragility (each BBS ran one software package; a vulnerability in TBBS, RBBS, or PCBoard affected every board running that software)

The BBS died when the World Wide Web arrived — not because the web was better at what BBSes did, but because the web was open and geographically infinite and free. The dial-up BBS was local by economic necessity: your phone bill constrained your reach. The web removed that constraint. The constraint had also, incidentally, enforced a community size that maintained social cohesion.

The Inheritance

Every failure pattern on the modern internet was documented on a BBS first. The difference is scale. A BBS with 500 active callers was large. When the same dynamics scale to 500 million active users, the failure modes are identical in character and catastrophic in consequence.

The BBS is the museum's exhibit on what happens when you solve the technical problem (networked communication) before solving the social problem (what do communities need to function). The internet inherited the solution. It also inherited the unsolved problem.