Hacker News users revisit dark mode after years of workarounds
A 2026 Ask HN post reignited the long-standing request for a native dark mode on Hacker News. The poster, Stitch4223, noted that a 2020 thread had already accumulated a hundred solutions, illustrating Parkinson's Law of Triviality in action. Despite the community's well-known enthusiasm for fonts, terminal themes, and CSS experimentation, the poster described feeling stuck with "empty hands and little karma" while their screen burned their eyes at night — the last bastion of light in more ways than one.
Existing workarounds range from cumbersome to broken
The post catalogued several failed attempts. One iOS app flashed the page between light and dark on every click, an experience the poster called nausea-inducing. It required more than twenty installation steps, demanded blind trust in a closed-source app with no Git repository, and forced an operating system change. Other workarounds were dismissed as "mid janky shit shows" that only deepened the swamp of well-intentioned but incomplete fixes. The poster argued that running twenty miles to solve a simple display preference is what people do when no official path exists.
Two extremes proposed for logged-in users
The thread outlined two contrasting approaches. Option A would give logged-in users a custom CSS text area, enabling maximum creativity, experimentation, and freedom to support any taste or necessity. The poster acknowledged this might be rejected over security, bloat, and reset concerns, but called it the most fun and expressive option. Option B would offer a drop-down menu of curated styles, where a two-line CSS inversion using `filter: invert()` could serve as a baseline, or the community could agree on a polished theme. The poster suggested turning the design into a contest, leveraging the millions of dollars' worth of CSS talent and LLM investment on the site to produce something tasteful, respectful, and well considered.
The PHP sleep() analogy guides the design goal
The poster drew a parallel to the resolution of PHP's `sleep()` function — keep the default behaviour unchanged for users who do not opt in, while extending tailored options for those who do. The aim is to let people read HN at night without the "abracadabra" of altering their OS, browser, trust boundaries, or anything outside the site itself. The poster also stated they would accept no solution if the official stance was that night reading harms health, provided that policy was clearly stated — though they could not find such a policy.
Community talent versus maintenance burden
The core tension is between unleashing the community's CSS expertise and the operational cost of supporting user styles. A custom CSS area risks security issues, style conflicts, and user confusion when things break. A curated drop-down limits freedom but contains the maintenance surface. The poster's invitation to "hurt plenty" with design submissions signals confidence that the community can produce quality work if given a structured outlet. The site's history of CSS madness and terminal theme obsession suggests the raw material for a good dark mode already exists within the user base.
What this means for the platform's future
Hacker News has resisted visual changes for decades, prioritising stability and speed. A native dark mode would represent a meaningful shift in that philosophy. If implemented as an opt-in setting for logged-in users, it would respect the default experience while solving a genuine accessibility and comfort issue. The 2020 thread's hundred solutions demonstrate that the problem is well understood; what remains is the decision to bless one approach and integrate it into the platform. Until then, night readers will continue cobbling together browser extensions, user styles, and third-party apps — a fragmented landscape the poster accurately called a swamp of well-intentioned nightmares.