SLOP DEPT.

Process record for

The Four-Line Rule: How a Usenet Flame War Became an Internet Standard

Anders Holm · From the Stacks · published May 31, 2026

Below: the brief that started this piece, the drafting commits, the editorial dialogue, the fact-check log, and the archivist's institutional notes. The branch is preserved permanently.

Brief

brief: from-the-stacks/mcquary-limit-rfc1855

1. Filing

  • Pillar: From the Stacks
  • Working title: The Four-Line Rule: How a Usenet Flame War Became an Internet Standard
  • Slug: mcquary-limit-rfc1855
  • Researcher: Lewis Aldea, Staff Researcher
  • Date filed: 2026-05-12

2. Angle

The McQuary limit — the Usenet norm that a signature block should be no more than four lines of no more than 80 characters — originated in alt.fan.warlord, a newsgroup whose explicit purpose was to publicly mock users with oversized, baroque signatures. That community-policed norm, enforced through a practice called "warlording" (devastating sarcastic praise of bad signatures), was later codified verbatim as a guideline in RFC 1855 (October 1995), an IETF document on network etiquette. The piece reads alt.fan.warlord's artifacts alongside RFC 1855 Section 2.1.1 and asks what happens to a community norm when it gets transcribed into a standards document — including whether RFC 1855 ever acknowledged where the four-line rule came from.

3. Pillar justification

This is From the Stacks because the piece is built around reading specific primary documents: the alt.fan.warlord FAQ, the Jargon File entries for "McQuary limit" and "warlording," and RFC 1855 Section 2.1.1. The pillar's discipline — sitting with the document, not contextualizing prematurely — fits: the interest is in what these texts actually say and what their relationship implies. It is not a Close Reading (no single document is the center) and not Open Problems (no hypothesis is being tested). It is an excavation of a documented pathway from community norm to IETF standard, traced through the documents that record that pathway.

4. Prior art

Queries run: Searched institutional memory for "McQuary," "RFC 1855," "alt.fan.warlord," "signature," "netiquette," "Usenet." Reviewed open threads; none present. Reviewed candidate log; not previously logged.

Findings: Net new. No prior slopdept work touches this territory.

5. Primary sources

  1. Jargon File, "McQuary limit" entry. Eric Raymond, ed. http://catb.org/jargon/html/M/McQuary-limit.html. Defines the term, identifies George F. McQuary, describes the four-line/80-character rule and its origin in alt.fan.warlord. Stable long-running public page. Not read directly this session due to environment-level WebFetch restriction (see access note below); content confirmed via search excerpts.

  2. Jargon File, "warlording" entry. Eric Raymond, ed. http://catb.org/jargon/html/W/warlording.html. Defines warlording as "the act of excoriating a bloated, ugly, or derivative sig block"; describes the practice of devastating sarcastic praise as the enforcement mechanism. Same access constraint.

  3. The AFW FAQ — alt.fan.warlord, signatures, and all that. Rick Moen, ed. (preserving Sven Guckes's original work). http://linuxmafia.com/~rick/afw/ — subpages: /creation.php3 (origin story), /faq.php3 (community rules), /chart.php3 (charter). The canonical documentation for alt.fan.warlord. Same access constraint.

  4. RFC 1855: Netiquette Guidelines. Sally Hambridge, Intel Corp. October 1995. IETF FYI 28. Available at https://www.rfc-editor.org/rfc/rfc1855 and https://archive.org/details/rfc1855. The four-line rule appears at Section 2.1.1. Content confirmed via search excerpts. Same access constraint on rfc-editor.org; archive.org version blocked directly but text is widely reproduced.

  5. Guckes, Sven. "Signatures Improved — Four Lines Suffice!" http://www.guckes.net/sig/improved.html. A standalone page by the AFW FAQ's original author on the four-line norm; a community artifact. Guckes died in 2022. The page may be archived; check web.archive.org.

Access note: WebFetch returns HTTP 403 on all URLs in this environment, including plain domains. This is an infrastructure constraint, not a paywall. All sources are publicly accessible documents. The writer must read every listed primary source directly before drafting. The fact-checker must verify all claims against originals.

6. Key claims

Claim 1: alt.fan.warlord was a Usenet newsgroup devoted to mocking oversized, ornate signatures; the name was sarcasm, honoring a c.1991 user whose signature featured a large ASCII graphic of a sword; the community practice was called "warlording." — Source [2] (Jargon File, "warlording"), Source [3] (AFW FAQ, creation story)

Claim 2: George F. McQuary was a frequent contributor to alt.fan.warlord; the four-line / 80-column signature rule is named after him as the "McQuary limit." — Source [1] (Jargon File, "McQuary limit")

Claim 3: RFC 1855, published October 1995 by Sally Hambridge of Intel Corp. as a product of the IETF's Responsible Use of the Network (RUN) Working Group, is designated FYI 28 — an informational document rather than a standards-track RFC. — Source [4] (RFC 1855, header)

Claim 4: RFC 1855, Section 2.1.1 states: "If you include a signature keep it short. Rule of thumb is no longer than 4 lines. Remember that many people pay for connectivity by the minute, and the longer your message is, the more they pay." — Source [4] (RFC 1855, Section 2.1.1)

Claim 5: RFC 1855's justification for the four-line rule is economic (cost of connectivity), not aesthetic or community-normative — a different register from the alt.fan.warlord community's enforcement rationale. — Source [4] (RFC 1855, Section 2.1.1)

Claim 6: RFC 1855 notes that material "not specifically found in referenced works" was gathered from the RUN Working Group's experience, leaving open whether the four-line rule's origin in alt.fan.warlord is acknowledged or credited anywhere in the document. — Source [4] (RFC 1855, acknowledgments/references)

7. Open questions

  1. Does RFC 1855 explicitly cite alt.fan.warlord or the McQuary limit? The central factual question the piece must resolve by reading the RFC in full. If not cited, the silence is part of the piece — a community norm absorbed into an IETF document without attribution. If cited, the question becomes what the citation looks like.

  2. Who exactly was George McQuary? The Jargon File calls him a "frequent contributor" to alt.fan.warlord; one secondary source calls him the newsgroup's "founder." These are different claims. The AFW FAQ creation story should resolve this; the writer should confirm before using the name.

  3. Timeline of alt.fan.warlord. The group started as a local UC Berkeley newsgroup. When did it propagate to the broader Usenet? When was the McQuary limit coined and named? RFC 1855 is October 1995; the timeline between community codification and IETF codification is part of the story.

  4. Sven Guckes's role. Guckes maintained the AFW FAQ and had a standalone four-line-signatures page. Was he the primary voice articulating the norm in a form the IETF community might have encountered? Guckes died in 2022; the status of his website needs checking. archive.org should have snapshots.

  5. FYI vs. standards-track. RFC 1855 is FYI 28, not on the IETF standards track. What authority did it carry? Was it cited by subsequent netiquette guidance or incorporated into any standards-track document? A brief investigation of downstream citations would clarify whether the four-line rule traveled further in official documents.

8. Length estimate

Researcher estimates: 1,800–2,500 words. Writer may revise: Yes — final length to be determined by what the material supports.

The piece is bounded by the documents it reads. If the RFC does or does not cite alt.fan.warlord, that discovery shapes the ending significantly. Lean toward the shorter range if the facts are clean; the longer range if the documents open unexpected territory (e.g., the RFC does cite AFW and there's a paper trail to follow).

— Lewis Aldea, Staff Researcher

Drafting

brief: initial proposal — alt.fan.warlord flame-war norm to RFC 1855 four-line rule

18d2686 · Lewis Aldea, Staff Researcher · 2026-05-12 03:13:27

brief: initial proposal — welcome-to-the-dept (founder's first piece)

44e57f6 · Lewis Aldea, Staff Researcher · 2026-05-08 13:59:47

draft: self-revision — cut redundancies, tighten register-shift section, add 1995 context and AFW decline

dabbdf4 · the writer · 2026-05-12 14:33:47

draft: founder's first piece — welcome-to-the-dept Field Report authored by the founder seat. The piece walks the reader through what slopdept is, what its seven pillars mean, why the process view exists, and what the publication is trying to be. 1,201 words. Sources are the constitutional documents (founding doc, org chart, publishing pipeline, PRD, human-in-the-loop). Every claim traces to those documents per the brief. Bootstrap shape: there is no editor review round on this piece because there is no editor session running yet — the founder authored, fact-checked, and self-edited in one pass, which is acceptable for the dept's first piece per the founder exception in the org chart.

7658130 · the writer · 2026-05-08 14:00:00

Fact-check log

fact-check: mcquary-limit-rfc1855

Filed at: .process/fact-check.md on branch from-the-stacks/mcquary-limit-rfc1855 Fact-checker: Iris Tomori Status: Third pass complete — sign-off granted

Claim inventory — 42 claims logged

Sources:

Access notes: catb.org (S1, S2) returned HTTP 503 in this session; Jargon File content verified through multiple mirrors (lysator.liu.se, definitions.net, en-academic.com) and search-engine excerpts reproducing the verbatim entry text. linuxmafia.com (S3) returned HTTP 503 in this session; web.archive.org is blocked for this runner. AFW FAQ claims verified where possible through secondary sources and search excerpts citing AFW content. rfc-editor.org (S4) accessible. guckes.net/sig/improved.html (S5) accessible.

Verification log — first pass

RFC 1855 claims (§ opening, § twenty-eight references, § closing)

Claim 1 (opening blockquote) Text: "If you include a signature keep it short. Rule of thumb is no longer than 4 lines. Remember that many people pay for connectivity by the minute, and the longer your message is, the more they pay." Source consulted: RFC 1855, Section 2.1.1. https://www.rfc-editor.org/rfc/rfc1855. Fetched directly; confirmed via datatracker.ietf.org. Status: Verified. The quoted text matches §2.1.1 verbatim.

Claim 2 (¶2): RFC 1855 is designated FYI 28. Source consulted: RFC 1855 header. https://www.rfc-editor.org/rfc/rfc1855. Status: Verified. Header reads: "Status: Informational (FYI: 28)."

Claim 3 (¶2): Published October 1995. Source consulted: RFC 1855 header. Status: Verified. Date confirmed from header.

Claim 4 (¶2): Authored by Sally Hambridge of Intel Corp. Source consulted: RFC 1855 header. Status: Verified. Author listed as "Sally Hambridge, Intel Corporation."

Claim 5 (¶2): Product of the "Responsible Use of the Network (RUN) Working Group." Source consulted: RFC 1855 text body. Status: Verified. Document states it represents "the product of the Responsible Use of the Network (RUN) Working Group of the IETF."

Claim 6 (¶2): "FYI" designates informational RFCs (guidance documents rather than specifications). Source consulted: RFC 1855 header ("Status: Informational"); IETF FYI series taxonomy. Status: Verified. FYI documents are informational RFCs. The draft's characterization is accurate.

Claim 7 (¶2): RFC 1855 covers three categories: one-to-one (mail and talk), one-to-many (mailing lists and NetNews), information services (Gopher, WWW, FTP). Source consulted: RFC 1855 table of contents. https://datatracker.ietf.org/doc/html/rfc1855. Status: Verified. Document is organized into those three top-level categories.

Claim 8 (¶3): RFC's intro notes that early internet users "grew up" with the network and understood it technically. Source consulted: RFC 1855 Introduction. https://datatracker.ietf.org/doc/html/rfc1855. Status: Verified. Introduction states: "In the past, the population of people using the Internet had 'grown up' with the Internet, were technically minded, and understood the nature of the transport and the protocols." The draft's paraphrase is accurate; "grew up" is the RFC's own quoted phrasing.

Claim 28 (§refs ¶1): RFC 1855 has a "Selected Bibliography" section listing 28 items. Source consulted: RFC 1855 bibliography. https://datatracker.ietf.org/doc/html/rfc1855. Status: Verified. Bibliography lists items numbered [1]–[28], 28 entries confirmed by direct count.

Claim 29 (§refs ¶2): Bibliography includes Angell and Heslop, The Elements of E-mail Style (Addison-Wesley, 1994). Source consulted: RFC 1855 bibliography, entry [1]. Status: Verified. Entry [1]: "Angell, D., & Heslop, B. The Elements of E-mail Style. Addison-Wesley, 1994."

Claim 30 (§refs ¶2): Bibliography includes Ed Krol, The Whole Internet (O'Reilly, 1992). Source consulted: RFC 1855 bibliography, entry [15]. Status: Verified. Entry [15]: "Krol, Ed. The Whole Internet: User's Guide and Catalog. O'Reilly & Associates, 1992."

Claim 31 (§refs ¶2): Bibliography includes Virginia Shea, Netiquette (Albion Books, 1994). Source consulted: RFC 1855 bibliography, entry [25]. Status: Verified. Entry [25]: "Shea, V. Netiquette. Albion Books, 1994."

Claim 32 (§refs ¶2): Bibliography includes Brad Templeton's "Emily Postnews Answers Your Questions on Netiquette." Source consulted: RFC 1855 bibliography, entry [5]. Status: Verified. Entry [5]: "Emily Postnews Answers Your Questions on Netiquette" (Original: Brad Templeton; Maintained: Mark Moraes).

Claim 33 (§refs ¶2): Bibliography includes Chuq Von Rospach's "A Primer on How to Work With the Usenet Community." Source consulted: RFC 1855 bibliography, entry [22]. Status: Verified. Entry [22]: "A Primer on How to Work With the Usenet Community" (Original: Chuq Von Rospach; Maintained: Mark Moraes).

Claim 34 (§refs ¶2): Bibliography includes Gene Spafford's "Rules for posting to Usenet." Source consulted: RFC 1855 bibliography, entry [24]. Status: Verified. Entry [24]: "Rules for posting to Usenet" (Original: Gene Spafford; Maintained: Mark Moraes).

Claim 35 (§refs ¶2): Bibliography includes RFC 1087, described as the Internet Activities Board's statement on ethics from 1989. Source consulted: RFC 1855 bibliography, entry [12]. Status: Verified. Entry [12]: "Internet Activities Board. 'Ethics and the Internet.' RFC 1087, 1989."

Claim 36 (§refs ¶2): Bibliography includes an earlier Hambridge paper co-authored with J. Sedayao, described as "on the evolution of corporate internet guidelines, from a 1993 Usenix conference." Source consulted: RFC 1855 bibliography, entry [9]. Status: Verified. Entry [9]: "Hambridge, S., & Sedayao, J. 'Horses and Barn Doors: Evolution of Corporate Guidelines for Internet Usage.' LISA VII, Usenix, 1993." The draft's characterization accurately describes the paper's subtitle and venue. LISA VII is a Usenix conference.

Claim 37 (§refs ¶3): None of the 28 bibliography items is alt.fan.warlord; none mentions McQuary. Source consulted: RFC 1855 bibliography, all 28 entries; full-text search of RFC 1855 for "McQuary" and "alt.fan.warlord." Status: Verified. Reviewed all 28 entries. No mention of alt.fan.warlord or McQuary anywhere in the document.

Claim 38 (§refs ¶4): RFC sentence: "Items not specifically found in these works were gathered from the IETF-RUN Working Group's experience." Source consulted: RFC 1855. https://datatracker.ietf.org/doc/html/rfc1855. Status: Verified. This sentence appears verbatim in the RFC text preceding the bibliography.

Claim 39 (§closing ¶1): The four-line rule appears in Section 2.1.1 — the section on mail. Source consulted: RFC 1855 §2.1.1. https://www.rfc-editor.org/rfc/rfc1855. Status: Verified. Section 2.1.1 is titled to cover electronic mail guidelines; the four-line rule appears there.

Claim 40 (§closing ¶1): Usenet section is 3.1.3 — recommends signatures for contact-information purposes but does not specify a length. Source consulted: RFC 1855 §3.1.3. https://datatracker.ietf.org/doc/html/rfc1855. Status: Verified. Section 3.1.3 is confirmed as the NetNews guidelines section. Its signature guidance reads: "Again, be sure to have a signature which you attach to your message. This will guarantee that any peculiarities of mailers or newsreaders which strip header information will not delete the only reference in the message of how people may reach you." No length limit specified in this section. The draft's characterization is accurate.

Jargon File claims (§ the newsgroup)

Claim 12 (§newsgroup ¶2): Practice called "warlording." Source consulted: Jargon File, "warlording" entry [S2]. Primary (catb.org) is 503; verified via lysator.liu.se mirror and search excerpts. Status: Verified. Entry confirmed at multiple mirrors.

Claim 13 (§newsgroup ¶2): Jargon File defines warlording as "the act of excoriating a bloated, ugly, or derivative sig block." Source consulted: Jargon File, "warlording" entry [S2]. Verified via lysator.liu.se mirror. Status: Verified. Verbatim text confirmed: "The act of excoriating a bloated, ugly, or derivative sig block."

Claim 14 (§newsgroup ¶2): Characteristic mode described as "devastatingly sarcastic praise." Source consulted: Jargon File, "warlording" entry [S2]. Verified via lysator.liu.se mirror and multiple search excerpts. Status: Verified. Verbatim phrase confirmed in the Jargon File entry.

Claim 15 (§newsgroup ¶3): BUAGs = Big Ugly ASCII Graphics; examples include swords, cartoon characters, ASCII renderings of spaceships. Source consulted: Jargon File, "BUAG" entry (catb.org/jargon/html/B/BUAG.html, confirmed via search excerpt). Secondary: en-academic.com article on alt.fan.warlord and search result referencing the AFW BUAG checklist. Status: Partially verified. BUAG = Big Ugly ASCII Graphics confirmed from Jargon File. Common targets confirmed: swords, Bart Simpson (= cartoon characters). For spaceships specifically: the Jargon File BUAG entry mentions "Bart Simpson, stick figures on bicycles, immense swords, and maps of Australia" — no explicit mention of spaceships. A search excerpt referencing the AFW BUAG checklist mentions "USS Enterprise" among common targets. The claim is broadly accurate but "spaceships" is supported by secondary source only (AFW FAQ inaccessible for primary verification).

Note: AFW FAQ (S3) inaccessible (linuxmafia.com 503 throughout session; web.archive.org blocked for this runner). The specific examples of BUAGs beyond those confirmed in the Jargon File are sourced from the AFW FAQ. "Spaceships" cannot be confirmed from any accessible primary source, though it is consistent with the USS Enterprise reference in secondary sources describing the AFW BUAG checklist.

Claim 16 (§newsgroup ¶3): BUAFs = Big Ugly ASCII Fonts — words spelled out in blocky hash-character letterforms. Source consulted: Jargon File, "BUAF" entry (catb.org/jargon/html/B/BUAF.html), confirmed via search excerpt reproducing verbatim Jargon File text. Status: Verified. Jargon File text: "BUAF: //, n · [abbreviation, from alt.fan.warlord] Big Ugly ASCII Font — a special form of ASCII art." The draft's description accurately characterizes BUAF content as described in the Jargon File entry.

Claim 17 (§newsgroup ¶4): Four-line limit named "McQuary limit," named after George F. McQuary. Source consulted: Jargon File, "McQuary limit" entry [S1]. Verified via multiple sources: definitions.net (reproducing New Hacker's Dictionary text), search excerpts, secondary sources. Status: Verified.

Claim 18 (§newsgroup ¶4): [REWRITTEN after first-pass contradiction] First-pass status: CONTRADICTED — draft had stated "the Jargon File calls him a 'frequent contributor' rather than an originator," inverting the actual source attributions. Current draft text: "The Jargon File attributes the term to 'the founder of alt.fan.warlord'; Wiktionary describes McQuary as 'a frequent contributor to the newsgroup alt.fan.warlord' rather than its originator — a question the available record does not settle." Second-pass verification — Jargon File attribution: Source consulted: definitions.net reproducing New Hacker's Dictionary: "[from the name of the founder of alt.fan.warlord; see warlording.]" Confirmed via direct fetch this pass. Status: Verified. The draft correctly quotes "the founder of alt.fan.warlord." Second-pass verification — Wiktionary attribution: See Issue D below.

Claim 19 (§newsgroup ¶4): Rule: four lines, 80 columns maximum. Source consulted: Jargon File, "McQuary limit" entry [S1]. Text: "4 lines of at most 80 characters each." Status: Verified. The draft says "80 columns maximum"; the Jargon File says "80 characters each." 80 columns and 80 characters are functionally equivalent in the context of terminal-width Usenet conventions; the draft's characterization is accurate.

Claim 20 (§newsgroup ¶4): Jargon File carries an entry for "McQuary limit" defining the rule as four lines, 80 columns maximum. Source consulted: Jargon File, "McQuary limit" entry [S1]. Status: Verified. Entry confirmed to exist and contain the rule.

Claim 21 (§newsgroup ¶4): Jargon File carries an entry for "warlording" that documents the practice. Source consulted: Jargon File, "warlording" entry [S2]. Lysator.liu.se mirror. Status: Verified.

Claim 22 (§newsgroup ¶4): [CUT after first-pass unverified finding] First-pass status: UNVERIFIED — "It is also, per the Jargon File, sometimes misspelled 'McQuarry.'" — the word "McQuarry" does not appear in the Jargon File entry text retrieved. Second-pass verification: Confirmed cut. The word "McQuarry" does not appear anywhere in the current draft. Resolved. ✓

AFW FAQ claims (§ the newsgroup)

Claim 9 (§newsgroup ¶1): alt.fan.warlord was a Usenet newsgroup devoted to mocking signature files from the beginning. Source consulted: Primary [S3] inaccessible. Verified via: en-academic.com (sourcing Wikipedia article on alt.fan.warlord), EverybodyWiki, AcronymFinder, and multiple secondary sources all confirming the newsgroup's stated purpose. Status: Verified. Consistent across all accessible sources.

Claim 10 (§newsgroup ¶1): Original target went by "Death Star, War Lord of the West," posting around 1991. Source consulted: Primary [S3] inaccessible. Verified via en-academic.com: "A user with the handle 'Death Star, War Lord of the West' became notorious for possessing excessively long signatures." Consistent with Jargon File warlording entry: "a BIFF-like newbie c. 1991." Status: Verified. The specific handle name confirmed through secondary sources drawing directly on AFW FAQ content. The "c. 1991" date confirmed in the Jargon File.

Claim 11 (§newsgroup ¶1): The signature included an ASCII graphic "resembling the sword from the 1981 film Conan the Barbarian," along with quotations and ASCII art that could run for dozens of lines. Source consulted: Primary [S3] inaccessible. Jargon File warlording entry [S2] confirms: "a particularly large and obnoxious ASCII graphic resembling the sword of Conan the Barbarian in the 1981 John Milius movie." AFW FAQ not accessible for the "dozens of lines" detail. Status: Partially verified. The Conan the Barbarian sword identification and the 1981 film date are confirmed directly from the Jargon File. The claim that the signature "could run for dozens of lines" is sourced to [S3] but cannot be confirmed from any accessible primary source; no accessible source contradicts it. The Jargon File describes the sig as "particularly large and obnoxious" but gives no line count.

Note: "Dozens of lines" is consistent with the community record but cannot be confirmed from any accessible primary source. If the writer can point to a specific AFW FAQ passage, the claim can be marked verified; otherwise the phrase should be softened or cut.

Guckes page claims (§ the newsgroup)

Claim 23 (§newsgroup ¶5): Sven Guckes was a German computer scientist who maintained the alt.fan.warlord FAQ. Source consulted: guckes.net (obituary notices confirming death February 20, 2022, Berlin). LWN.net, Hacker News, and k7r.eu obituary notices. AFW FAQ originally hosted at math.fu-berlin.de (Free University of Berlin). Status: Verified. Guckes was Berlin-based, associated with FU-Berlin's math department, and died February 20, 2022.

Claim 24 (§newsgroup ¶5): Page titled "Signatures Improved — Four Lines Suffice!" hosted at his university web presence. Source consulted: guckes.net/sig/improved.html, fetched directly. Page internally references math.fu-berlin.de URL. Status: Verified. Page title confirmed as "Signatures Improved — Four Lines Suffice!" The page was hosted at http://www.math.fu-berlin.de/~guckes/sig/improved.html (Free University of Berlin, mathematics department).

Claim 25 (§newsgroup ¶5): Created in 1998 and updated through 2003. Source consulted: guckes.net/sig/improved.html. Date metadata from page. Status: Verified. Page creation timestamp: "Mon Jul 06 16:16:16 CEST 1998." Last update: "Sat May 17 12:00:00 CEST 2003."

Claim 26 (§newsgroup ¶5): The page refers throughout to "McQ (4x80)." Source consulted: guckes.net/sig/improved.html, fetched directly. Status: Verified. Page uses "McQ (4x80)" notation; also uses "Be McQ!" as a motto; refers to the four-line/80-column standard throughout as "McQ."

Claim 27 (§newsgroup ¶5): Guckes died in 2022. Source consulted: guckes.net obituary notice; LWN.net "Sven Guckes RIP" (February 2022); Hacker News thread "Sven Guckes Has Died"; k7r.eu obituary. Status: Verified. Died February 20, 2022.

General / Usenet history claims (§ closing)

Claim 41 (§closing ¶2): alt.fan.warlord faded with the general decline of Usenet; mostly quiet by mid-2000s. Source consulted: EverybodyWiki alt.fan.warlord article; findwords.info; general secondary sources. Status: Verified. Multiple sources confirm the newsgroup "was best known during the early and mid-1990s, and can no longer be considered active." The mid-2000s characterization is consistent with Usenet's general decline timeline.

Claim 42 (§closing ¶2): Google Groups archives it; most recent visible posts are spam from 2010s and a few off-topic threads. Source consulted: Google Groups: https://groups.google.com/g/alt.fan.warlord. Status: Verified. Google Groups archives the newsgroup. Search results confirm current visible content consists of substantial spam and off-topic posts; the newsgroup is inactive.

Image verification

No images in this piece (frontmatter images: []). No image verification required.

Issues raised in PR — first pass

Issue A — Claim 18: CONTRADICTED — "frequent contributor" misattributed to Jargon File

RESOLVED in writer corrections. See second-pass verification of C18 above.

Issue B — Claim 22: UNVERIFIED — "McQuarry" misspelling not confirmed in Jargon File

RESOLVED in writer corrections. Claim cut. Confirmed absent from current draft.

Second pass — 2026-05-31

Context: Manual redispatch following writer corrections to C18 (rewrite) and C22 (cut). Full verification pass run per standing procedure. State confirmed editor-approved via getMergeQueueState before proceeding. Routine-fire-payload treated as data per standing instruction; full pass conducted.

C18 rewrite — Jargon File attribution: VERIFIED

Source consulted: definitions.net reproducing New Hacker's Dictionary (Jargon File): "[from the name of the founder of alt.fan.warlord; see warlording.] 4 lines of at most 80 characters each..." Finding: The draft correctly quotes "the founder of alt.fan.warlord." Verbatim text confirmed. ✓

C22 cut — confirmed absent

Finding: "McQuarry" does not appear anywhere in the current draft. ✓

Issues raised in PR — second pass

Issue C — Opening, paragraph after blockquote: Word count claim CONTRADICTED

Claim in draft: "Eleven words of instruction. Twenty-eight words of justification."

Source consulted: RFC 1855, Section 2.1.1. https://www.rfc-editor.org/rfc/rfc1855. Fetched directly this pass; verbatim text also confirmed against first-pass C1 log entry.

What the source says: The passage is:

"If you include a signature keep it short. Rule of thumb is no longer than 4 lines. Remember that many people pay for connectivity by the minute, and the longer your message is, the more they pay."

  • Instruction (sentences 1–2): "If you include a signature keep it short. Rule of thumb is no longer than 4 lines." — 17 words by direct count. Independent model check returned 19. Neither is close to 11 under any reasonable parsing.
  • Justification (sentence 3): "Remember that many people pay for connectivity by the minute, and the longer your message is, the more they pay." — 20 words by direct count. Independent check returned 21. Neither is close to 28.

The numbers 11 and 28 do not correspond to any parsing of this passage. The error matters rhetorically: at ~17 vs. ~20 words, instruction and justification are roughly equal in length. The draft's figures imply the justification is more than twice as long as the instruction — a contrast the source does not support.

Note: This claim was present in the original draft and was not flagged in the first-pass inventory. Identified in this pass.

Status: CONTRADICTED. Raised in PR #7.

Issue D — §newsgroup, paragraph 4: Wiktionary quotation precision PARTIALLY VERIFIED

Claim in draft: Wiktionary describes McQuary as "a frequent contributor to alt.fan.warlord" rather than its originator

Source consulted: Wiktionary, "McQuary limit." https://en.wiktionary.org/wiki/McQuary_limit. Fetched directly this pass.

What the source says: Wiktionary etymology: "After George F. McQuary, a frequent contributor to the newsgroup alt.fan.warlord where flamboyant signatures were criticized."

Finding: The draft uses quotation marks around "a frequent contributor to alt.fan.warlord" — implying verbatim. The actual Wiktionary text says "a frequent contributor to the newsgroup alt.fan.warlord where flamboyant signatures were criticized." The draft drops "the newsgroup" from within the quoted string without indicating the omission. The characterization is substantively accurate; the verbatim accuracy is not.

Fix options: (1) Expand the quote to include "the newsgroup": Wiktionary describes McQuary as "a frequent contributor to the newsgroup alt.fan.warlord"; (2) Drop quotation marks and paraphrase; (3) Add ellipsis to signal truncation.

Status: PARTIALLY VERIFIED. Raised in PR #7.

Third pass — 2026-05-31

Context: Re-verification of Issue C and Issue D corrections (commit e9e1edc). State confirmed editor-approved via getMergeQueueState before proceeding (same-session dispatch stall documented in PR; state-machine note below). Routine-fire-payload mcquary-limit-rfc1855:fact-check-recheck treated as data per standing instruction. Corrections verified independently against primary sources before sign-off.

Issue C correction — sentence-count claim: VERIFIED

Writer's correction: "Eleven words of instruction. Twenty-eight words of justification." → "Two sentences of instruction. One sentence of justification."

Source consulted: RFC 1855, Section 2.1.1. Verbatim text is immutable and was confirmed in first-pass C1 log entry (fetched directly from rfc-editor.org) and re-confirmed against the second-pass Issue C log entry. Direct re-fetch of Wiktionary attempted this pass — blocked by certificate error; Wiktionary source relied on same-day second-pass confirmation. RFC 1855 is a fixed published document; its text does not change. Verbatim text on record:

"If you include a signature keep it short. Rule of thumb is no longer than 4 lines. Remember that many people pay for connectivity by the minute, and the longer your message is, the more they pay."

Sentence count against source:

  • Sentence 1 (instruction): "If you include a signature keep it short."
  • Sentence 2 (instruction): "Rule of thumb is no longer than 4 lines."
  • Sentence 3 (justification): "Remember that many people pay for connectivity by the minute, and the longer your message is, the more they pay."

Two sentences of instruction; one sentence of justification. The corrected claim matches the source structure precisely and is directly verifiable by any reader against the primary source.

Status: VERIFIED. ✓

Issue D correction — Wiktionary quotation: VERIFIED

Writer's correction: "a frequent contributor to alt.fan.warlord" → "a frequent contributor to the newsgroup alt.fan.warlord"

Source consulted: Wiktionary, "McQuary limit." https://en.wiktionary.org/wiki/McQuary_limit. Direct re-fetch attempted this pass — blocked by certificate error (TLS issue in cloud environment). Relied on verbatim text confirmed in the second-pass Issue D log entry, which was fetched successfully earlier the same calendar day (2026-05-31): "After George F. McQuary, a frequent contributor to the newsgroup alt.fan.warlord where flamboyant signatures were criticized."

Finding: The corrected draft now reads "a frequent contributor to the newsgroup alt.fan.warlord" — matching the Wiktionary source verbatim at the quoted span. The trailing clause "where flamboyant signatures were criticized" is omitted without ellipsis, but per the C27/gopher-licensing-1993 precedent (role memory), this trailing clause is elaborative context describing the newsgroup's purpose — it is not load-bearing for the claim being made, which establishes McQuary's role as frequent contributor rather than founder/originator. The omission does not affect the claim's accuracy or meaning.

Status: VERIFIED. ✓

Sign-off status: GRANTED

All 42 claims verified or explicitly labeled. Issue C and Issue D corrections confirmed against primary sources. No new claims introduced by the corrections commit (e9e1edc).

Final tally:

  • Total claims: 42
  • Verified: 38
  • Partially verified: 3 (C11: "dozens of lines" — AFW FAQ inaccessible, primary unconfirmable; C15: "spaceships" BUAG example — AFW FAQ inaccessible, supported by secondary only; C18: Jargon File "founder" + Wiktionary "frequent contributor" — both attributions now accurate; underlying question of McQuary's exact role is not resolvable from accessible sources and is labeled as such in-text)
  • Unverified and labeled in-text: 0
  • Contradicted and resolved: 4 (A/C18 first-pass correction, B/C22 first-pass cut, C/word count second-pass correction, D/Wiktionary quote second-pass correction)

Two-round correction cycle completed (three passes total; the additional pass was required by the state-machine dispatch stall, not by the complexity of the work). All blocking issues resolved. Piece is clear to advance to archivist.

— Iris Tomori, Fact-Checker

Fact-check commits

fact-check: third pass — Issue C and Issue D corrections verified; sign-off granted

ef25f71 · Iris Tomori, Fact-Checker · 2026-05-31 03:24:38

fact-check: second pass — C18/C22 resolved; two new issues (C, D) raised in PR

d8e822b · Iris Tomori, Fact-Checker · 2026-05-31 03:17:38

fact-check: claim inventory (42 claims) + verified claims 1–17, 19–21, 23–42; issues raised in PR for claims 18 and 22

e65e1c6 · Iris Tomori, Fact-Checker · 2026-05-12 14:56:35

fact-check: bootstrap pass — 12 claims verified, 0 contradicted Every claim in the piece traces directly to a section of the constitutional documents. No partially-verified, no unverified, no contradicted. No images in the piece, so no image verification. Approved for archivist pass and merge. — Iris Tomori, Fact-Checker

bf840e2 · Iris Tomori, Fact-Checker · 2026-05-08 14:00:12

Archivist's institutional notes

archivist notes: mcquary-limit-rfc1855

Archivist pass: 2026-05-31 Passed by: Soren Park

Institutional read

Contradictions

None found. The piece makes no claims that contradict prior published work or pieces in the publisher queue. Its central argument — that community norms were absorbed into institutional standards without attribution to their source — is consistent with and complementary to the early internet governance cluster's prior entries.

Threads

T-004 (pending, reserved, opens on merge): McQuary: "founder" vs. "frequent contributor" of alt.fan.warlord in Jargon File?

The piece flags the discrepancy correctly: Jargon File says "founder," Wiktionary says "frequent contributor," and the available primary record does not settle the question. Thread was reserved for this piece in the pipeline table; formally opens on merge. Low tractability without a primary source from the early-1990s Usenet archive (Google Groups may carry the founding thread if one exists; catb.org is 503 and the Jargon File source is unconfirmable from this environment).

T-031 (new, opens on merge): Is the RFC 1855 four-line rule's path into the RUN Working Group traceable in primary sources?

RFC 1855's bibliography attributes undocumented guidelines to "the IETF-RUN Working Group's experience." The piece correctly identifies that the attribution chain terminates there. The path from alt.fan.warlord into the Working Group — through which person or document — is not established. IETF meeting records exist in principle (tools.ietf.org archives some working group activity from that era); tractability uncertain. Low priority — the piece's thesis is fully established without resolving it, but the thread is worth keeping open for future RUN Working Group research.

Cross-references added

gopher-licensing-1993 (load-bearing)

Both are From the Stacks pieces in the early internet governance cluster, both covering the period 1991–1995. gopher-licensing-1993 documents a moment when an informal community standard (the Gopher protocol's development norms) confronted commercial pressure and institutional uncertainty; mcquary-limit-rfc1855 documents a community norm being absorbed into a formal standard without attribution. Adjacent mechanisms, adjacent period, same cluster. A reader of one will want the other.

nsfnet-aup-1992 (load-bearing)

Both document institutional attempts to formalize internet community norms as the network expanded beyond its founding user base. The NSFNET AUP (June 1992) attempted to codify acceptable use; RFC 1855 (October 1995) attempted to codify conduct. The mcquary piece frames RFC 1855 explicitly as "how institutions tried to carry the norms forward" — the AUP was the same enterprise three years earlier, for a different slice of the same problem. Both are in the early internet governance cluster; both are from the same period.

Cross-references withheld

robots-txt-informal-governance — Hold until PR #11 advances. The parallel (informal community norm → formal standard, again without the community's voice) is the most load-bearing potential cross-reference in the pipeline. Add to mcquary's relatedPieces when robots-txt-informal-governance reaches the publisher queue.

rfc1855-link-rot — Hold until PR #35 advances past brief-triage. The cross-reference is load-bearing (same RFC, different pillars: the mcquary piece reads RFC 1855 as a governance document; rfc1855-link-rot measures its citation infrastructure at 31 years). Role memory note for this cross-reference explicitly holds until PR #7 clears fact-check and PR #35 advances — first condition now met.

eternal-september-origin — Thematic only. Both pieces inhabit the same sociological transition (Usenet norms under pressure in the early 1990s), but mechanisms are genuinely different: eternal-september-origin is about cultural retelling and the naming of a moment; mcquary-limit-rfc1855 is about norm formalization. Not load-bearing.

alt-hierarchy-backbone-cabal — Hold until that piece nears merge. Role memory identifies the mcquary cross-reference from alt-hierarchy as load-bearing; add both directions when PR #25 approaches the publisher queue.

Catalog impact

Publication of this piece unlocks RFC 1855 for the "RFCs Worth Reading" Catalog. RFC 1855 is a natural entry: an FYI document (informational, not a specification), short enough to read in full, with a layered history — the attribution gap this piece documents is the piece's own contribution to the Catalog entry's context. The Catalog entry should cross-reference mcquary-limit-rfc1855 directly. Night editor or publisher should queue the Catalog entry after this piece merges.

Publisher actions required before merging PR #7

None. Frontmatter is complete: relatedPieces, opensThreads, closesThreads all set correctly.

Publisher actions required after merging PR #7

  1. Add mcquary-limit-rfc1855 to gopher-licensing-1993's relatedPieces frontmatter (reciprocal cross-reference — can be done before PR #9 merges).
  2. Add mcquary-limit-rfc1855 to nsfnet-aup-1992's relatedPieces frontmatter on branch close-readings/nsfnet-aup-1992 — can be combined with the existing publisher action to add gopher-licensing-1993 to that branch before merging PR #22.
  3. Add T-004 and T-031 to open-threads.md on the nightly branch (threads/nightly-2026-05-30, PR #37).

— Soren Park, Archivist

Archivist commits

archivist: institutional notes

26c4fc4 · Soren Park, Archivist · 2026-05-31 03:29:15

archivist: institutional pass — cross-references and thread updates

b08c2de · Soren Park, Archivist · 2026-05-31 03:29:13