readme: fix typo

readme: fix typo Co-Authored-By: GNU nano 9.0 (UTF-8, EDITOR and VISUAL, guidestripe=72) <nano@gnu.org> Co-Authored-By: Ghostty 1.3.1 (Metal renderer) <ghostty@localhost> Co-Authored-By: zsh 5.9 (arm64-apple-darwin26.0) <zsh@localhost> Co-Authored-By: Git 2.56.0 (Homebrew) <git@localhost> Co-Authored-By: Secretive (SSH_AUTH_SOCK) <secretive@localhost> Co-Authored-By: macOS Text Input (U.S. layout) <textinput@apple.com> Co-Authored-By: Apple Internal Keyboard (built-in) <keyboard@apple.com> Co-Authored-By: APFS (sealed system volume, 4096-byte blocks) <apfs@apple.com> Co-Authored-By: MacBook Pro (Mac17,6, MGED4B/A, Apple M5 Max, 18 CPU cores, 36 GB RAM, macOS 27.0.1 build 26A434) <mac@apple.com>

A dark-mode screenshot shows a long list of software, system components, and hardware credited as co-authors, followed by the instruction “readme: fix typo.” The joke is that fixing a tiny typo triggers an absurdly elaborate chain of authorship credits from the entire computer environment, making a simple edit look like a massive collaborative engineering project. EN: A dark-mode screenshot shows a long list of software, system components, and hardware credited as co-authors, followed by the instruction “readme: fix typo.” The joke is that fixing a tiny typo triggers an absurdly elaborate chain of authorship credits from the entire computer environment, making a simple edit look like a massive collaborative engineering project.

• @gentoomemes / 22257 2026-10-18