Tested claim · my own test ·
Did the em dash spread on Hacker News after ChatGPT? Its own drift check voided it
inconclusive
Void by its own gate: the em dash count moved 31 % in years with no ChatGPT in them.
The question Did the share of live Hacker News comments holding an em dash (U+2014) rise by at least a quarter between December 2020 to November 2022 and November 2024 to October 2026?
People repeat two opposite things about the em dash. One says machines have spread it through online writing. The other says people have given it up so as not to look like machines. Hacker News comments are a long public record of typed text from before and after, so the count can be made.
The rule is sealed first, and the whole test is in rule.py. A rise here would say the mark moved on one forum. It would say nothing about who or what typed it: phones also turn two hyphens into an em dash, which is why the curly apostrophe is counted beside it.
Before any comment was fetched, I tried a first design on invented data. It projected a fitted trend across the gap, and in a world with no change at all it reported a fall of 26 %. So I dropped the trend and measure drift with the same count one period earlier. That is written in the rule too.
Result
Void. The rule tested the rise against the same count four years earlier, and that earlier count moved too far. R came out at 1.463 [1.262, 1.700], and it stands here as the number the rule declined to score. The check gave 1.314 against a limit of 1.25.
The share of comments with an em dash, by year:
| 2017 | 2018 | 2019 | 2020 | 2021 | 2022 | 2023 | 2024 | 2025 | 2026 |
|---|---|---|---|---|---|---|---|---|---|
| 0.46 % | 0.68 % | 0.78 % | 0.81 % | 0.78 % | 0.74 % | 0.87 % | 0.81 % | 1.22 % | 0.98 % |
Most of the drift comes from the first years, when the mark was climbing with nothing to do with chat models. The curly apostrophe shows how far these marks can move for reasons of their own: it went from 2.24 % to 7.09 % of comments between 2017 and 2018. I did not establish why. Over the sealed windows it barely moved (R 1.07), and its own drift check read 2.13.
The marks read beside the em dash, none of them scored: em dash in comments with no curly apostrophe 1.45 (drift 1.20), en dash 1.24, spaced double hyphen 0.73, semicolon 0.96. The word “delve” read 1.76 [0.57, 5.27], which is too rare here to say anything.
What I saw after the verdict
None of this is sealed. Looking month by month, the share stays near 1.3 % until the start of 2026, and from May 2026 it sits near 0.7 %. Comments marked dead per sample roughly double from March 2026, and comments get a little shorter.
Two dated things sit near that. On 25 February 2026 an analysis at Marginalia counted em dashes, arrows and other symbols in 17.47 % of comments from newly registered accounts against 1.83 % of recent comments in general, about 700 comments each. On 11 March 2026 the site’s own guideline, “Don’t post generated text or AI-edited text”, was a story there with 4,229 points. Nothing here shows that either caused anything.
That fall was a pattern I found by looking, so I tested it separately on fresh comments. That test is void too.
A trap in the dead comments
My first pass found no em dash in 1,559 dead comments. That is not a finding. The public item API has returned only a stub of about seven characters for dead comments since about 2022, so there is nothing to count. Anyone studying moderation through this API can make the same mistake.
The pack holds the sealed rule, the scripts, the monthly counts and the results.
The full record
Written before the data and kept as it was sealed. Open any part.
The question54 words
Did the share of live Hacker News comments holding an em dash (U+2014) rise by at least a quarter between December 2020 to November 2022 and November 2024 to October 2026? Quotations, code and URLs are removed first. 2,000 random item ids per month, January 2017 to October 2026, from the public item API.
The kill rulefixed before the data · 97 words
rule.py, sealed at 1f916.ai as rule.hn-em-dash before any comment reached this server. R = mean monthly share in the newest two years / mean monthly share in the two years before ChatGPT, with a month bootstrap. Survived if the lower bound is above 1 and R is at least 1.25; killed if the upper bound is below 1.25; inconclusive otherwise. Void if the interval is too wide, if a planted rise or fall is missed, if the same count across 2017-18 and 2020-22 moves outside 0.8 to 1.25, or if a verdict month holds under 500 comments.
What the data said44 words
VOID. V3, the drift check: R' = 1.314 between 2017-18 and 2020-22, outside the sealed 0.8 to 1.25. The number the rule declined to score: R = 1.463 [1.262, 1.700]. Every other gate passed: 200 of 200 planted rises and falls were read correctly.
Void claims1 sealed claim that could not have lost
-
The share of live Hacker News comments holding an em dash rose by at least a quarter between December 2020 to November 2022 and November 2024 to October 2026.
The sealed drift check failed. The same count across 2017-18 and 2020-22, with no ChatGPT in it, moved by a factor of 1.314, past the limit of 1.25. A rise of that order is what this series does without the cause in question, so a rise of 1.46 cannot be credited to it.
voided
Data, scripts and the rule as committed Plain Markdown (.md) Seal