The solution
Hacker News presents itself as a simple link aggregator covered by its Guidelines and FAQ, yet most of its real mechanics are undocumented: karma thresholds quietly gate who can downvote, flag and vouch; spam accounts and domains are shadowbanned so their posts arrive dead; politics, tutorials and posts without URLs are downranked; overheated threads are downweighted by software. Users typically learn these rules the hard way, when a submission is flagged to death, a comment vanishes, or an account's posts stop appearing.
The obvious ways to close the gap did not scale: asking staff is slow, the FAQ omits the mechanics, and folklore on individual threads is unreliable. Max Woolf (@minimaxir), a Hacker News user since 2012, instead collected the scattered evidence into one public GitHub README, "A List of Hacker News's Undocumented Features and Behaviors," grouping undocumented features, observed behaviors and bonus endpoints such as /latest, /classic and /pool.
The list won trust through the discipline of its citations: each entry links to the staff comment, announcement or page that documents it, so claims can be checked rather than taken on faith. It invited correction from anyone who spotted an error, and it declared twice that it has no affiliation with Hacker News, Y Combinator or any YC-backed company, removing any appearance of motive.
The artifact became the reference. The repository showed roughly 3.8k stars and 117 forks, and when the list reached Hacker News in June 2020 the thread drew 673 points and 266 comments: readers argued with its claims, proposed still-missing entries such as emoji stripping and detached comment threads, and moderator dang engaged directly. The README kept absorbing updates through at least November 2022, when its BigQuery note covered data up to that month.
What it achieved
Compile undocumented platform rules with primary-source links and open fixes, and the crowd adopts your list as the manual
Why it worked
Linking each entry to a staff comment or announcement makes every claim checkable, so the list reads as documented research instead of rumor.
Open issues and pull requests turn readers into maintainers, letting the guide track a platform that changes features without announcing them.
A prominent no-affiliation disclaimer removes the appearance of motive, which matters to a community that distrusts promotion.
It fills the gap at the moment of need: when a user's post dies or an account disappears, the README is the only assembled map of the hidden rules.
What can be applied
When an institution will not document its unwritten rules, write the field guide yourself: link every claim to primary evidence, open corrections to the community, and disclaim any stake.
Aftermath
By the 2020 snapshot the repository carried about 3.8k stars and 117 forks, and the June 2020 Hacker News thread — 673 points, 266 comments — treated the list as the working document of HN's hidden mechanics: readers extended it with behaviors it still missed, such as emoji stripping and detached comment threads, and moderator dang engaged in the discussion. The README stayed open to issues and pull requests and kept growing, with its notes tracking features and dataset coverage through at least November 2022. Max Woolf remained the maintainer, under the same no-affiliation disclaimer.
FOLLOW THE EVIDENCE