March 10, 2026
Punctuation with a pulse?
RFC 454545 – Human Em Dash Standard
The dash that makes you pause—internet split between satire and watermark hopes
TLDR: A playful RFC proposes a “Human Em Dash” that appears only after a human-style pause or edit, stirring talk of AI watermarks. Commenters split between calling it April Fools and treating it as a serious anti-bot signal, while memes, leaderboards, and real watermark proposals fuel an entertaining brawl.
Internet nerd-dom is melting down over RFC 454545, a “Human Em Dash” you can only type after a real hesitation—think a 137 ms pause, a backspace, a cursor wiggle, maybe even an audible sigh. The spec names a Human Attestation Mark (HAM) and warns systems that can’t hesitate “MUST NOT” use it. Commenters instantly split: satire about AI detection vs. serious watermark talk. One top take says the scheme ‘hinges in ai training companies converting these human em dashes back’ so bots don’t learn the trick. Meanwhile, jokers crowned an Em‑dash leaderboard and called for style points.
Then the chaos: “Surely 22 days early,” snarks one user, reading the post as an early April Fools. Another quips, “RIP Yezidi Hyphenation Mark,” pretending Unicode had to evict a rare character to make room for the human-only dash. But the thread gets real when someone links a serious Unicode proposal for AI watermarks. The vibe? Comedy meets policy brawl. Fans love the idea of a human-only pause; skeptics say it’ll fall apart once AI models start imitating sighs and backspaces—or when corpora scrub the mark away. Either way, everyone’s arguing over the same thing: how to keep writing that actually feels human.
Key Points
- •An informational RFC proposes a new Unicode code point for a “Human Em Dash.”
- •The Human Attestation Mark (HAM) precedes the dash and indicates human involvement.
- •Evidence of human hesitation may include >137 ms pause, backspace, cursor move, visible indecision, or audible sigh.
- •Systems incapable of hesitation must not emit the Human Em Dash; non-compliant implementations are deemed adversarial.
- •Optional proof-of-work measures (e.g., incongruous emoji, value statements) may be required; compatibility and security guidance is provided.