Article #34-1 | Gutenberg Articles

Excerpt

Excerpt from Zen and the Art of the Internet, by Brendan P. Kehoe

In the beginning, there were conversations, and they were good. Then
came Usenet in 1979, shortly after the release of V7 Unix with UUCP;
and it was better. Two Duke University grad students in North
Carolina, Tom Truscott and Jim Ellis, thought of hooking computers
together to exchange information with the Unix community. Steve
Bellovin, a grad student at the University of North Carolina, put
together the first version of the news software using shell scripts
and installed it on the first two sites: unc and duke. At the
beginning of 1980 the network consisted of those two sites and phs
(another machine at Duke), and was described at the January 1980
Usenix conference in Boulder, CO. {The Usenix conferences are
semi-annual meetings where members of the Usenix Association, a
group of Unix enthusiasts, meet and trade notes.} Steve Bellovin
later rewrote the scripts into C programs, but they were never
released beyond unc and duke. Shortly thereafter, Steve Daniel did
another implementation in the C programming language for public
distribution. Tom Truscott made further modifications, and this
became the "A" news release.

In 1981 at the University of California at Berkeley, grad student Mark
Horton and high school student Matt Glickman rewrote the news software
to add functionality and to cope with the ever increasing volume of
news---"A" news was intended for only a few articles per group per
day. This rewrite was the "B" news version. The first public
release was version 2.1 in 1982; all versions before 2.1 were
considered in beta test. As The Net grew, the news software was
expanded and modified. The last version maintained and released
primarily by Mark was 2.10.1.

Rick Adams, then at the Center for Seismic Studies, took over
coordination of the maintenance and enhancement of the news software
with the 2.10.2 release in 1984. By this time, the increasing volume
of news was becoming a concern, and the mechanism for moderated groups
was added to the software at 2.10.2. Moderated groups were inspired
by ARPA mailing lists and experience with other bulletin board
systems. In late 1986, version 2.11 of news was released, including a
number of changes to support a new naming structure for newsgroups,
enhanced batching and compression, enhanced ihave/sendme control
messages, and other features. The current release of news is 2.11,
patchlevel 19.

Explanation

**Detailed Explanation of the Excerpt from Zen and the Art of the Internet by Brendan P. Kehoe**

Context and Background

Zen and the Art of the Internet (1992) is a foundational guide to early internet culture, written by Brendan P. Kehoe, a computer scientist and Unix expert. The book serves as both a technical manual and a philosophical exploration of how online communities form, evolve, and function. The excerpt provided traces the origins and development of Usenet, one of the earliest distributed discussion systems on the internet, which predates the modern web and social media.

Usenet was a decentralized network where users could post and read messages (called "articles") in thematic discussion groups ("newsgroups"). Unlike modern platforms, it relied on Unix-to-Unix Copy Protocol (UUCP) and later TCP/IP, allowing machines to exchange data asynchronously. The passage highlights key figures, technical milestones, and the organic growth of Usenet from a small academic project to a global communication system.

Themes in the Excerpt

Collaborative Innovation
- The passage emphasizes how Usenet was built through collective effort by graduate students, hobbyists, and programmers. Unlike corporate-driven tech today, early internet tools were often open-source, community-maintained projects.
- Example: Steve Bellovin’s initial scripts were rewritten by Steve Daniel for public use, and later expanded by Mark Horton and others.
Organic Growth and Scalability
- Usenet evolved in response to user needs. Early versions ("A" news) were designed for small-scale use, but as participation grew, the software had to adapt (e.g., "B" news for higher volume, moderation features in 2.10.2).
- The mention of "beta test" versions (pre-2.1) reflects the iterative, experimental nature of early internet development.
Decentralization and Open Standards
- Usenet was not controlled by a single entity; different institutions contributed improvements. This mirrors the internet’s original ethos of decentralized, permissionless innovation.
- The shift from UUCP-based networks (which connected machines via dial-up) to broader TCP/IP adoption shows how infrastructure adapted to demand.
Community Governance
- The introduction of moderated groups (inspired by ARPA mailing lists) reflects early attempts to manage information overload and discourse quality—a precursor to modern content moderation debates.
- The Usenix conferences (mentioned parenthetically) highlight how in-person gatherings complemented digital collaboration.
Technical Evolution as a Response to Human Behavior
- The text subtly implies that social dynamics drove technical changes. For example:
  - The need for compression and batching (2.11) arose because more users meant more data.
  - The naming structure for newsgroups was formalized to organize growing discussions (e.g., comp.os.unix, rec.arts.sf).

Literary Devices and Stylistic Choices

Biblical Allusion ("In the beginning...")
- The opening line parodies Genesis 1:1 ("In the beginning, God created..."), framing Usenet’s creation as a mythic, foundational event in internet history. This:
  - Elevates the technical achievement to near-religious significance.
  - Suggests that communication itself is sacred in digital culture.
  - Creates a narrative of progress (from "good" to "better").
Chronological Structure
- The passage follows a linear timeline, marking key milestones (1979, 1980, 1981, etc.). This:
  - Reinforces the idea of inevitable technological progression.
  - Mirrors the iterative nature of software development (each version builds on the last).
Parenthetical Explanations
- Kehoe uses parentheses to define terms (e.g., Usenix conferences) without breaking the flow. This:
  - Assumes a technically curious but not expert audience (aligning with the book’s educational purpose).
  - Reflects the collaborative, self-documenting culture of early internet communities.
Passive Voice and Impersonal Tone
- Phrases like "the news software was expanded" or "moderated groups were added" depersonalize the process, emphasizing:
  - The collective, almost organic nature of Usenet’s growth.
  - That systems evolve beyond their creators’ original intentions.
Technical Jargon as Cultural Shorthand
- Terms like "UUCP," "shell scripts," "ihave/sendme control messages" are used without deep explanation, implying:
  - A shared technical culture among readers (the book’s target audience).
  - That understanding these tools is part of belonging to the early internet community.

Significance of the Excerpt

Historical Record of Early Internet Culture
- The passage documents a pre-web era where text-based communication dominated. Usenet was a precursor to forums, Reddit, and even social media, proving that digital communities can thrive without centralization.
Philosophy of Open Collaboration
- The excerpt embodies the hacker ethic: software should be free, modifiable, and shared. This contrasts with today’s walled gardens (e.g., Facebook, Twitter).
- The lack of commercial motives in early Usenet development highlights how innovation can stem from curiosity and utility rather than profit.
Lessons for Modern Tech
- Scalability challenges: Usenet’s struggles with "increasing volume" foreshadow today’s issues with misinformation, spam, and moderation at scale.
- Decentralization vs. control: The shift from unmoderated to moderated groups reflects ongoing debates about who should govern online spaces.
Cultural Nostalgia
- For readers familiar with early internet history, the passage evokes a lost era of experimentation—when the net was a playground for academics and hobbyists, not corporations.

Line-by-Line Analysis of Key Sections

"In the beginning, there were conversations, and they were good."
- Meaning: Human communication is the primordial force behind technology. The internet exists to facilitate dialogue.
- Tone: Almost religious reverence for conversation, suggesting it’s the core purpose of networks.
"Two Duke University grad students... thought of hooking computers together"
- Highlights the grassroots, non-hierarchical origins of Usenet. No corporate R&D—just students solving a problem.
"The Net grew"
- Personifies the internet as a living organism, not a static tool. Growth is inevitable and natural.
"Moderated groups were inspired by ARPA mailing lists..."
- Shows how ideas cross-pollinate in digital culture. Solutions to problems (e.g., spam, off-topic posts) were borrowed and adapted from other systems.
"The current release of news is 2.11, patchlevel 19."
- Ends on a technical note, grounding the narrative in specific, tangible progress. The "patchlevel" suggests ongoing refinement—a metaphor for the internet itself.

Conclusion: Why This Matters

This excerpt is more than a technical history—it’s a creation myth for digital community. It illustrates how simple ideas (sharing messages between computers) can grow into complex, global systems through collaboration. The passage also serves as a mirror to modern internet dilemmas:

How do we balance openness with order?
Can decentralized systems scale without losing their original spirit?
Who owns the tools we use to communicate?

Kehoe’s writing captures the optimism and experimental spirit of early internet culture—a reminder that the net was once a shared project, not a product. In an era of algorithmic feeds and surveillance capitalism, Usenet’s story feels both quaint and revolutionary.

Questions

Question 1

The passage’s opening sentence—"In the beginning, there were conversations, and they were good"—employs a biblical allusion primarily to:

A. underscore the technical superiority of Usenet over earlier communication methods by invoking divine authority.
B. critique the commercialization of later internet platforms by contrasting them with a purer, original form of digital interaction.
C. suggest that Usenet’s creation was an inevitable, predestined event in the evolution of human communication.
D. establish a tone of irony, implying that the chaotic growth of Usenet hardly lived up to its mythic origins.
E. elevate the act of human dialogue to a foundational, almost sacred principle in the development of digital communities.

Question 2

The passage’s description of Usenet’s evolution—from "A" news to "B" news to version 2.11—most strongly implies that:

A. technological progress in digital communication is linear and free from setbacks or regressions.
B. the development of Usenet was driven by iterative responses to the practical challenges posed by its own success.
C. early internet software was inherently flawed and required constant overhauls to remain functional.
D. the shift from academic to public use of Usenet necessitated a complete abandonment of its original design principles.
E. the primary motivation behind Usenet’s updates was to compete with emerging commercial alternatives like ARPA mailing lists.

Question 3

The parenthetical explanation of Usenix conferences—"{The Usenix conferences are semi-annual meetings where members of the Usenix Association, a group of Unix enthusiasts, meet and trade notes.}"—serves which of the following rhetorical purposes in the passage?

A. To subtly reinforce the theme of decentralized, community-driven knowledge-sharing that defined early internet culture.
B. To clarify a technical term for non-expert readers while simultaneously highlighting the exclusivity of early Unix communities.
C. To interrupt the narrative flow, creating a deliberate contrast between the collaborative ideal and the reality of fragmented expertise.
D. To imply that the conferences were the primary driver of Usenet’s development, overshadowing individual contributions.
E. To foreshadow the eventual commercialization of Usenet by framing Usenix as a proto-corporate entity.

Question 4

The passage’s repeated emphasis on the rewriting of Usenet software (e.g., Bellovin’s scripts, Daniel’s C implementation, Horton and Glickman’s "B" news) most clearly suggests that:

A. early internet developers prioritized originality over functionality, leading to unnecessary redundancy.
B. the lack of standardized programming languages in the 1980s forced constant reinvention of the same tools.
C. Usenet’s growth was stymied by the refusal of key contributors to adopt a unified codebase.
D. the open-source ethos of the time encouraged competition rather than collaboration among developers.
E. the software’s evolution was shaped by a process of communal refinement, where each iteration addressed the limitations of its predecessor.

Question 5

The passage’s closing sentence—"The current release of news is 2.11, patchlevel 19."—functions primarily to:

A. underscore the provisional, ever-unfinished nature of technological development, resisting the idea of a "final" version.
B. provide a precise historical marker for when Usenet reached its peak functionality before declining in relevance.
C. contrast the meticulous versioning of early internet software with the haphazard updates of modern digital platforms.
D. imply that Usenet’s development had stagnated by the time of writing, as no further updates were planned.
E. highlight the bureaucratic rigidity of open-source projects, where even minor changes required formal patchlevel designations.

Solutions and Explanations

1) Correct answer: E

Why E is most correct: The biblical allusion "In the beginning, there were conversations, and they were good" frames human dialogue as the primordial, sacred act from which Usenet emerged. This elevates conversation to a foundational principle, aligning with the passage’s broader theme that digital communities exist to facilitate communication. The tone is reverential, not ironic or technical, and the reference to Genesis is repurposed to mythologize collaborative human interaction rather than the technology itself.