How a PRINTER Created Open Source
🔗 **Source:** [How a PRINTER Created Open Source](https://www.youtube.com/watch?v=6TK69yGaFTQ)
> [!note]+ Document Notes
> tags: [open-source-history, free-software, source-code-access, software-freedom, printer-drivers]
> author: Jono Bacon
> source: Jono Bacon (YouTube)
> reference: https://www.youtube.com/watch?v=6TK69yGaFTQ
> date created: 2026-10-05 09:46
>
> > [!info] Generated analysis — not the author's words. Sections below are machine-written
> > from the captured source. Only text inside `> [!quote]` blocks is verbatim from the author.
> > Do not quote or attribute any other line to the named author.
>
> # 🏷️ Title: How A PRINTER Created Open Source
>
<!-- deep-read:sections start -->
## 🧭 Table of contents
- [📝 Summary](#-summary)
- [📖 Main content](#-main-content)
- [🗒️ Notes](#️-notes)
- [📚 References](#-references)
- [🗣️ Paraphrase](#️-paraphrase)
- [📰 Newsletter](#-newsletter)
- [✅ Action items](#-action-items)
- [🧪 Hypotheses](#-hypotheses)
- [📊 Methodology](#-methodology)
- [❓ Questions](#-questions)
- [🔮 Future research](#-future-research)
- [💡 Implications](#-implications)
- [🧠 Learning styles assessment](#-learning-styles-assessment)
- [📊 Accessibility assessment](#-accessibility-assessment)
- [🌍 DEIB assessment](#-deib-assessment)
- [✅ Logical validity](#-logical-validity)
- [🛡️ DARVO analysis](#️-darvo-analysis)
- [🎯 Conclusion](#-conclusion)
- [🔄 Refactor appendix](#-refactor-appendix--how-a-printer-created-open-source)
## 📝 Summary
- **What happened.** Jono Bacon's channel published a 40-second YouTube Short on 2026-10-02. The captured transcript is a single caption block (one paragraph, 128 words, timestamp 00:00:00), so every timestamp below is 00:00:00. The speaker says a jammed Xerox 9700 printer at MIT's AI lab in 1980 pushed Richard Stallman toward free software, because Xerox would not share the printer driver's source code.
- **The claim.** One printer jam, plus a refusal to share source code, "changed the entire software industry forever" and led, 40 years later, to free software running on a helicopter on Mars.
- **Why it matters.** The story frames source access as a practical need (fix the tool in front of you) instead of an abstract principle. That framing is a reusable teaching hook for open source education and advocacy.
- **Key stakeholders.** Richard Stallman (the protagonist), Xerox (the printer maker that declined to share the driver source), MIT's AI lab (the setting), and the people on the network affected by the jams.
- **Risks and tradeoffs.** A 40-second origin story compresses a contested history into one cause. The speaker cites no source for any claim, and the title says "Open Source" while the speaker says "free software," two labels that carry different meanings in the community. Treat the video as a hook, not a reference.
- **Bottom line.** A clean, memorable story with one load-bearing claim (Xerox refused the source) that the video asserts and does not support. Verify against primary accounts before reusing it.
## 📖 Main content
**The core argument.** A small, concrete annoyance (a printer that jams and disrupts people on a shared network) can expose a large structural problem: you can't fix software you can't read. The speaker builds the story in three beats. First the setup (1980, a Xerox 9700 in MIT's AI lab, repeated jams). Then the obstacle: Stallman had already fixed this class of problem once and wanted to repeat the fix, but Xerox wouldn't release the printer driver's source code. Then the payoff: that frustration leads, 40 years later, to free software on a Mars helicopter.
**Terms.** *Source code* is the human-readable program text. A *printer driver* is the software that lets a computer and a printer talk to each other. *Free software* is the phrase the speaker uses; it names a movement built on user freedom to run, study, change and share software. The video title uses "Open Source," which the community treats as a related but separate label. The speaker doesn't define either term.
**Outside context, labeled as such.** The Stallman and Xerox printer story is widely retold in open source circles, and the description for this video names the same people and printer. This analysis adds no historical detail beyond what the speaker and the video description say, and it did not check any outside account.
**Uncertain or unsourced in this video.**
- "changed the entire software industry forever" is a causal claim with no argument or source behind it.
- Stallman "had already solved this problem once before" is asserted, with no description of the earlier fix.
- Stallman felt "shocked, stunned, and a bit disgusted" is an attributed inner state with no source.
- The Mars link ("a helicopter flying on Mars running free software") has no source in the transcript. The description names NASA's Ingenuity helicopter, but the speaker doesn't, and the video gives no evidence for the claim.
- "40 years later" is a rounded span from 1980; the transcript names no year for the Mars flight.
## 🗒️ Notes
#### ⏱️ [00:00:00](https://www.youtube.com/watch?v=6TK69yGaFTQ&t=0) The whole Short: printer jam to Mars helicopter
- Opening claim: one jammed printer and one annoyed person changed the software industry. This is the thesis, stated in the first sentence.
- Setting: a Xerox 9700 inside MIT's AI lab, jamming repeatedly and annoying people on the network.
- Obstacle: Stallman wanted to apply an earlier fix but couldn't, because Xerox wouldn't share the driver source.
- Reaction: the speaker says Stallman was shocked, stunned and a bit disgusted.
- Payoff: the frustration "led to" free software on a helicopter on Mars, 40 years later. The ending covers the last sentence of the 40-second runtime.
> [!quote] [00:00:00]
> Xerox, people who made the printer, were not willing to share the source code for the printer driver.
## 📚 References
The transcript itself contains no links; the following come from the video description or are primary sources for named entities.
- [How A PRINTER Created Open Source (YouTube)](https://www.youtube.com/watch?v=6TK69yGaFTQ): the source video, 40 seconds, uploaded 2026-10-02 by Jono Bacon.
- Richard Stallman: the protagonist named in the transcript. No URL is given; use a primary source such as Stallman's own writing on free software before citing the printer account.
- Xerox 9700 printer and MIT's AI lab: named in the transcript, no sources given.
- NASA's Ingenuity helicopter: named in the video description only, not by the speaker. The speaker says only "a helicopter flying on Mars."
- Description links (the speaker doesn't point to any of them in the transcript; they promote the channel's company): [Stateshift](http://stl.ink/yt-vd), [Stateshift on LinkedIn](https://www.linkedin.com/company/stateshift), [Stateshift on Reddit](https://www.reddit.com/r/Stateshift/), [SHIFTsignal newsletter](https://www.stateshift.com/shiftsignal).
## 🗣️ Paraphrase
The speaker opens with a big promise: in 1980 a single jammed printer, plus one annoyed person, changed the software industry for good. The printer was a Xerox 9700 in MIT's AI lab, and it kept jamming and bothering people on the network.
Stallman, described as the bearded protagonist, had fixed this kind of problem before and wanted to do it again. Stallman couldn't, because Xerox, the maker, wouldn't share the source code for the printer driver. The speaker says that left Stallman shocked, stunned and a bit disgusted, and that this frustration eventually led to free software running on a helicopter on Mars 40 years later.
## 📰 Newsletter
**A 40-second printer story with a 40-year payoff.** Jono Bacon's new Short retells the tale of a jammed Xerox 9700 at MIT in 1980 and a driver nobody outside Xerox could change. It's a handy 40-second hook for anyone who explains why WordPress licensing and open contribution matter: the argument starts with "I can't fix my own tool," which every plugin author has felt. One caution before you share it. The video gives no sources, so treat the history as a story to verify, not a citation. Link: [the video](https://www.youtube.com/watch?v=6TK69yGaFTQ).
## ✅ Action items
#### DevRel
- Developer advocacy: use the printer story as a 40-second opener in a talk on why source access matters, and cite a primary source on screen for the history.
- Education: pair the video with a short exercise: "name a tool you couldn't fix because you couldn't read its source."
- Developer experience: no direct action from this source; nearest relevance: docs that show how to read and modify a dependency's source.
- Developer marketing: Shorts under a minute can carry one hook and one claim. Plan the claim you want viewers to check, and put the source in the description.
- Community management: add a note in link-sharing channels that this video carries no sources for its claims.
- Internal/external/cross-project: no direct action from this source; nearest relevance: aligning on whether to say "free software" or "open source" in shared material.
#### OSPO
- Policy and governance: no direct action from this source; nearest relevance: a written statement of which label (free software or open source) the program uses and why.
- License compliance: no direct action from this source; nearest relevance: the printer driver example illustrates why license terms decide who can modify code.
- Security management: no direct action from this source.
- Software inventory: no direct action from this source; nearest relevance: tracking which dependencies ship without source.
- Developer support: no direct action from this source.
- Community engagement: no direct action from this source.
- Strategic alignment: no direct action from this source.
#### Community
- Maintainers: no direct action from this source; nearest relevance: a README line explaining why source stays open.
- Contributors: use "I needed to fix X and couldn't" as a prompt for first-contribution stories.
- Sponsors: no direct action from this source.
- Ecosystem: no direct action from this source.
#### WordPress
- Core: no direct action from this source.
- Core Performance: no direct action from this source.
- Core AI: no direct action from this source; the video's closing question is about who controls the computer, which maps loosely onto AI tooling, but the transcript doesn't raise it.
- **Core Program Team:** no direct action from this source.
- Mobile: no direct action from this source.
- Playground: no direct action from this source; nearest relevance: a lesson that lets learners read and edit the source of a running site.
- Community: a meetup lightning-talk slot could use the story, with a verified source.
- Training: add the story to a "why GPL and open source" lesson opener, flagged as unverified until sourced.
- Marketing: no direct action from this source.
- Support: no direct action from this source.
- Design: no direct action from this source.
- Documentation: no direct action from this source.
- Photos: no direct action from this source.
- TV: Short-form video is a format to consider for 40-second explainers, with captions checked by a human.
- Polyglots: no direct action from this source.
- Accessibility: use this video as a caption-quality case study (see the accessibility section).
- Meta: no direct action from this source.
- CLI: no direct action from this source.
- Hosting: no direct action from this source.
- Tide: no direct action from this source.
- Openverse: no direct action from this source.
- Themes: no direct action from this source.
- Plugins: no direct action from this source.
#### The WPOCC
- Programs: no direct action from this source.
- Projects: no direct action from this source.
- Funding experiments: no direct action from this source.
### FAIR
- Technical independence: no direct action from this source; nearest relevance: the story's point is dependence on a vendor who controls source.
- Policies and covenants: no direct action from this source.
- Productized governance artifacts: no direct action from this source.
## 🧪 Hypotheses
1. Viewers who watch the Short can state the Xerox source-code refusal correctly one week later more often than viewers who read a 100-word text version of the same story.
2. A story that starts with a concrete annoyance (a jammed printer) raises recall of the principle (source access) over an opening that states the principle first.
3. The video's causal chain (printer refusal, then a movement, then the Mars helicopter) is a simplification: the primary record shows more than one contributing event.
4. Short-form history videos with no on-screen source attribution get repeated in comments as fact at a higher rate than videos that show a source.
5. Viewers read the title's "Open Source" and the speaker's "free software" as the same thing unless told otherwise.
## 📊 Methodology
- **H1 and H2.** Randomize 60 participants into three arms: the Short, a text version, and a principle-first version. Ask free-recall and multiple-choice questions at day 0 and day 7. Pre-register the scoring rubric.
- **H3.** Compare the speaker's chain against primary sources (Stallman's own writing and contemporaneous MIT records). Log each link in the chain as supported, contradicted or absent.
- **H4.** Sample comments on 20 history Shorts, 10 with an on-screen source and 10 without. Code each comment as repeating the claim as fact, questioning it, or neutral.
- **H5.** Show 40 viewers the title and the transcript, then ask them to define both labels. Score how many treat them as synonyms.
- **Controls.** Fix video length, audio and caption text across arms where possible, and keep scorers blind to the arm.
## ❓ Questions
- What is the primary source for the claim that Xerox refused to share the printer driver source, and who saw the refusal?
- What was the earlier fix Stallman "had already solved" before, and how did it work without source for this printer?
- Is the line from the printer to the Mars helicopter a documented chain or a rhetorical connection?
- Which flight, and which software on it, does "free software running on Mars" refer to? The speaker doesn't say, and the description names only the helicopter.
- Why does the title say "Open Source" when the speaker says "free software"?
- What does the speaker mean by "changed the entire software industry," and by what measure?
- Does the video's closing frame in the description ("Who controls your computer?") appear anywhere in the spoken text? It doesn't in the transcript.
## 🔮 Future research
- **Primary-source audit of the printer story.** Compare retellings against the earliest written accounts to see which details are firsthand and which are repetition.
- **Origin stories as teaching tools.** Test whether a single dramatic cause helps learners remember principles, and whether it harms their grasp of messier history.
- **Label confusion.** Study how often learners treat "free software" and "open source" as interchangeable after short-form content.
- **Short-form sourcing norms.** Find out what source cues (on-screen text, pinned comment, description link) viewers actually notice.
## 💡 Implications
- **Practice.** A concrete annoyance makes a strong opening hook. Add the source in the first line of the description so viewers can check the claim.
- **Policy.** Open source programs should decide which label they use in public material and apply it consistently, including in video titles.
- **Security.** Closed driver code means users can't audit what runs with device access. The video doesn't make this argument, but the printer example supports it.
- **Education.** Use the story as a prompt, then have learners find the primary source themselves. That turns a 40-second video into a source-evaluation exercise.
- **Funding.** No funding claim appears in the video. The description promotes a go-to-market consultancy, so treat the Short as part of channel marketing.
## 🧠 Learning styles assessment
- **Reading level estimate.** Hand-computed Flesch-Kincaid Grade Level of about 10 for the 128-word transcript (5 sentences, roughly 25 words per sentence). The score is inflated by auto-caption punctuation, which creates long sentences. Spoken delivery is plain and conversational.
#### 👀 Visual learners
- Present: the transcript doesn't describe visuals, and the speaker calls Stallman "our bearded protagonist," which implies an image or footage on screen. Unverified from text.
- Improve: show the printer model, a date card for 1980, and a Mars image at the last sentence so the 40-year jump is visible.
#### 🔊 Aural learners
- Present: the whole story is narrated in 40 seconds.
- Improve: a short pause before the Mars reveal would give the payoff room.
#### 🗣️ Verbal learners
- Present: a clear story arc with a villain, a hero and a payoff.
- Improve: define "source code," "printer driver" and "free software" in one clause each.
#### 🧩 Kinesthetic learners
- Present: none in the transcript.
- Improve: add a one-line prompt: "Pick a tool you use and find its source."
#### 🧠 Logical learners
- Present: a three-step cause chain (jam, refusal, movement).
- Improve: show the evidence for each link, especially the last jump to Mars.
#### 🧑🤝🧑 Social learners
- Present: a story format that invites retelling.
- Improve: end with a discussion question for the comments.
#### 🧘♀️ Solitary learners
- Present: short and self-contained.
- Improve: a reflection prompt such as "What have you wanted to fix but couldn't?"
#### 🌿 Naturalistic learners
- Present: none directly. The Mars image is the only natural-world reference.
- Improve: tie to repair culture and long-lived devices, where source access extends a product's life.
## 📊 Accessibility assessment
#### Screen reader semantics
- Present: YouTube supplies the page structure and a description with a plain-text summary.
- Improve: any on-screen text or images the Short shows aren't in the transcript, so a screen reader user gets only the narration. WCAG 2.2 AA 1.1.1 (Non-text Content) and 1.2.5 (Audio Description, Prerecorded) apply to visuals the speech doesn't describe.
#### Keyboard navigation
- Present: the YouTube player is keyboard operable by default.
- Improve: the Shorts format auto-advances, which can cause a context change. Pause controls help under 2.2.2 (Pause, Stop, Hide).
#### Contrast and readability
- Present: not verifiable from a transcript.
- Improve: for any burned-in captions or text overlays, check 1.4.3 (Contrast Minimum), and keep them clear of the platform's own buttons.
#### Text resizing and reflow
- Present: the vertical format scales to the viewport.
- Improve: burned-in text doesn't resize, which fails the intent of 1.4.4 (Resize Text) for that text.
#### Media and captions
- Present: an auto-generated caption track exists, delivered here as one 128-word block with a single 00:00:00 timestamp.
- Improve: a single caption block gives no timing, so a viewer can't match text to speech. Human-reviewed, timed captions satisfy 1.2.2 (Captions, Prerecorded). No chapters exist, which is normal for a 40-second Short.
#### Forms and interactions
- Present: none in the video.
- Improve: description links are plain text URLs, which is workable. The promo link points to a third-party site that this analysis didn't check (3.3.2 applies there).
#### Standards reference
- Primary gaps against WCAG 2.2 AA: **1.2.2** (single untimed caption block), **1.2.5** (visuals not described, if any), **1.1.1** (non-text content), **1.4.4** (burned-in text). The caption block is the highest-impact fix.
## 🌍 DEIB assessment
#### Cultural breadth
- Present: a US and Western institutional story (MIT, Xerox) with a space-exploration link.
- Improve: add non-Western contributions to free and open software so the origin story isn't one lab.
#### Inclusive language
- Present: no exclusionary language in the transcript.
- Improve: "our bearded protagonist, the guy" frames the subject by appearance and gender. A neutral tag such as "the programmer" would do the same job. This analysis uses Stallman's name and avoids pronouns because the transcript uses none for him.
#### Neurodiversity support
- Present: a single clear thread, short runtime, plain sentences.
- Improve: the rapid pace leaves little processing time. A text recap in the description helps.
#### Representation
- Present: one narrator and one named subject, both from the story's single male-coded frame.
- Improve: mention the other people on the network who were affected, and credit the wider community that built free software.
#### Psychological safety
- Present: a low-stakes, upbeat tone.
- Improve: no content warnings needed. Invite corrections in the description since the history is unsourced.
## ✅ Logical validity
#### Strong reasoning
- **Narrative causal framing, 00:00:00.** The jam creates a need, the closed driver blocks the fix, and the frustration motivates a response. Each step follows from the one before it. To clarify: say what Stallman did next, since the transcript jumps from frustration to Mars.
- **Concrete-to-general structure, 00:00:00.** Starting from one device and ending with a global outcome is a sound way to teach a principle.
#### Fallacies
- **Post hoc / oversimplified cause, 00:00:00.** "one jammed printer ... changed the entire software industry forever." One event is named as the cause of an industry-wide change. *Why weak:* industries change from many causes. *Fix:* say "helped start" and name the other contributors.
- **Unsupported assertion, 00:00:00.** "had already solved this problem once before." No detail or source. *Fix:* describe the earlier fix in a clause.
- **False cause by span, 00:00:00.** "led to 40 years later, a helicopter flying on Mars running free software." The video asserts a link across 40 years with no intermediate steps. *Fix:* name the software on the helicopter and show the connection.
- **Terminology slide, title vs. speech.** Title: "Open Source." Speech: "free software." Two labels, used as one. *Fix:* pick one or define the difference.
- No ad hominem, appeal to authority or false dilemma appears; I checked all five sentences for each.
#### Tone of voice
- Upbeat, story-driven and informal ("All right, so," "a bit of a snag"). Contractions throughout. The tone shifts to emphatic at "shocked, stunned, and a bit disgusted," which sets up the emotional payoff.
## 🛡️ DARVO analysis
Not applicable to this source. DARVO describes a response to accusation or criticism, and this is a short educational story with no accuser and no defensive posture. For completeness: **Deny**: nothing is denied. **Attack**, no one's credibility is attacked, though Xerox is cast as the party that refused. **Reverse victim/offender**, the framing casts Stallman and the network users as the frustrated parties, and Xerox as the one withholding. That is the story's plot, not a defensive reversal. The speaker doesn't address any criticism.
## 🎯 Conclusion
The video makes one load-bearing claim: Xerox refused to share the printer driver's source, and that refusal set off a chain ending in free software on Mars. The story is short, memorable and well shaped as a hook. The transcript gives no source for any link in the chain, the title and speech use different labels, and the auto-caption block has no timing.
**Next steps for readers:** use the story as an opener, find a primary source before repeating the history as fact, and decide whether you mean "free software" or "open source" before you say either.
## 🔄 Refactor Appendix — How A PRINTER Created Open Source
> Density: 2–5 Literature atoms (H3 pad), 0–3 Permanent candidates (H4 pad).
> Emitted: 3 Literature, 1 Permanent. Resonance filter applied: the Stallman character
> description (bearded, "shocked, stunned") was dropped as color, not a claim.
>
> Konik claim-header rules: present tense, declarative, ≤10 words, searchable, unique.
>
> Atomicity: one declarative sentence per atom. "and"/"also" → split.
>
> Tag pool: #bmf · #addendum · #xref · #articleseed · #storystem · #share · #aphorisms
### 📚 Literature Split Pad
#### [H1] Xerox refused to share the printer driver source
> [!quote] [00:00:00]
> Xerox, people who made the printer, were not willing to share the source code for the printer driver.
**Context & use**:
- 00:00:00, the obstacle beat of the story. This is the one claim the whole video depends on.
- Asserted without a source in a single caption block. Verify against a primary account before citing.
**Tags**: #xref #articleseed
<!-- atomicity: 1 idea ✓ -->
#### [H2] A printer jam launched a software movement
> [!quote] [00:00:00]
> in 1980, one jammed printer combined with one really annoyed guy changed the entire software industry forever.
**Context & use**:
- 00:00:00, the opening thesis.
- A one-cause claim for an industry-wide change. Keep as a hook, and pair it with a note that the history has more contributors.
**Tags**: #xref
<!-- atomicity: 1 idea ✓ -->
#### [H3] Source access connects a printer to Mars
> [!quote] [00:00:00]
> And it's this frustration that led to 40 years later, a helicopter flying on Mars running free software.
**Context & use**:
- 00:00:00, the closing payoff.
- The description names NASA's Ingenuity helicopter; the speaker doesn't. The software on the helicopter is unsourced in the video.
**Tags**: #xref #share
<!-- atomicity: 1 idea ✓ -->
### 🧠 Atomic Split Pad
#### [P1] You can't fix software you can't read
**Claim** (one sentence, Courtney's voice): When a vendor withholds source code, the people who use the product lose the ability to repair it, no matter how small the repair.
**Evidence pointer**: [[#H1]]
**Scope & conditions**: Holds when the fix requires changing the code itself. Doesn't hold when a configuration option, a vendor patch or a replacement part solves the problem. The video's evidence is a single unsourced anecdote, so the claim rests on the general logic, not on the printer story.
**Links**:
- [[Free software and open source labels]] — because contrasts on emphasis, user freedom versus development method
- [[Right to repair]] — because extends to physical products with embedded software
- [[Open source advocacy talks]] — because applies-in opening hooks
<!-- atomicity: 1 idea ✓ -->
### ✏️ Fleeting Queue
- [F1] Find a primary source for the Xerox 9700 refusal and the earlier fix Stallman "had already solved": https://www.youtube.com/watch?v=6TK69yGaFTQ #fleeting #inbox
- [F2] Check what software runs on the Mars helicopter before repeating the "free software on Mars" line: the description names Ingenuity, the speaker doesn't #fleeting #inbox
- [F3] Article seed: why "free software" and "open source" get used as one label in short-form video #fleeting #inbox #articleseed
### → Things 3 (max 2 actions)
- [ ] Find a primary source for the Xerox printer and Stallman story before using it in a talk: DevRel research #things
- [ ] Decide which label to use in talks and docs, free software or open source, and write the one-line reason: OSPO messaging #things
<!-- deep-read:sections end -->
📄 **Full text:** [[Full Document Contents/Articles/How a PRINTER Created Open Source.md|How a PRINTER Created Open Source by Jono Bacon]]
## Highlights
- [00:00:00] All right, so in 1980, one jammed printer combined with one really annoyed guy changed the entire software industry forever. So, the printer in question was a Xerox 9700 and it was inside of MIT's AI lab and it kept jamming and annoying people on the network. Now, our bearded protagonist, the guy called Richard Stallman, had already solved this problem once before and just wanted to do the same thing again, but it was a bit of a snag because Xerox, people who made the printer, were not willing to share the source code for the printer driver. Now, Stallman was shocked, stunned, and a bit disgusted by this. And it's this frustration that led to 40 years later, a helicopter flying on Mars running free software. ([View Highlight](https://read.readwise.io/read/01m465a94qfn9xsetd4b5m9m4g))
- Note: [H1] Xerox refused to share the printer driver source
- Tags: atom/literature/h1