Smith argues the shift from phpBB/vBulletin forums to Discord and subreddits broke the retrieval layer of the web. A 2004 forum thread about a specific bug is still Google-indexable in 2026, while a Discord message answering the same question effectively disappears the moment it scrolls off screen.
Submitted the Tedium piece to HN where it hit 479 points, signaling strong developer agreement that small forums produced durable, searchable technical knowledge that modern chat platforms cannot replicate.
Points to the collapse of the XDA Developers forums into a Discord + wiki hybrid as a concrete case where Android ROM development knowledge has disappeared from search results. The community still exists but its contributions are no longer discoverable.
Cites research showing Stack Overflow answer volume declined 35% between 2022 and 2025 with no corresponding rise in any indexed replacement. Argues the knowledge is being generated somewhere unsearchable — likely Discord and private chat.
Notes that the Something Awful forums archive is still serving posts from 2001, demonstrating that phpBB-era software and small-community governance can sustain content for two-plus decades. Modern platforms have not yet demonstrated comparable durability.
Argues the forum-vs-Discord debate is usually miscast as generational preference when it is actually a technical infrastructure question. Discord is structurally write-only for search engines — no public HTTP endpoint exists for a message, so Google can't index it, curl can't fetch it, and LLM training runs can't ingest it. This isn't a policy Discord could reverse; it's baked into the product.
On July 1, Tedium published *Bring back crappy forums* — a 4,000-word retrospective on the small-web forum era of roughly 1998 to 2010. The piece landed at 479 points on Hacker News within a day, with 600+ comments dominated by developers over 30 recounting the specific vBulletin, phpBB, and Simple Machines boards they learned to code on.
The article's core claim is narrower than nostalgia. Author Ernie Smith argues that the migration of niche communities into Discord servers and topic-scoped subreddits didn't just change the interface — it broke the retrieval layer. A 2004 phpBB thread on a specific bug in a specific version of a specific library is still Google-indexable in 2026; a 2024 Discord message answering the same question is functionally gone the moment it scrolls.
The HN thread surfaced supporting data. One commenter cited the [Something Awful forums archive](https://forums.somethingawful.com), still serving posts from 2001. Another pointed at the collapse of the XDA Developers forums into a Discord + wiki hybrid — and the corresponding disappearance of Android ROM development knowledge from search results. A third linked to research showing Stack Overflow answer volume declined 35% between 2022 and 2025, with no corresponding rise in any indexed replacement.
The forum-vs-Discord debate usually gets framed as generational preference. That framing is wrong. It's an infrastructure question with three distinct failure modes, and Smith's piece is the first mainstream write-up to name them cleanly.
Failure mode one: Discord is write-only for search engines. There is no public HTTP endpoint for a Discord message. Google can't index it, `curl` can't fetch it, an LLM training run can't ingest it. This isn't a policy choice Discord could reverse — it's baked into the product. Every technical answer given in a Discord support channel is a one-time event. The half-life of the knowledge is measured in hours, not decades. Compare this to a phpBB thread, where the URL is stable, the HTML is scrapable, and the content persists as long as someone pays $5/month for shared hosting.
Failure mode two: Reddit's monoculture flattens niches. The pre-Reddit forum ecosystem had roughly 200,000 active small forums by most estimates, each with 10 to 5,000 members and a specific topic scope. Reddit consolidated most of that traffic into ~50,000 subreddits, but the median subreddit is now dead — the top 1% of subreddits capture 70% of activity. A phpBB board with 200 dedicated members produced better technical discussion than r/programming with 6 million subscribers, because the small forum's culture was maintained by people who knew each other's handles.
Failure mode three: platform risk is now existential. When Something Awful's forum software broke in 2019, a volunteer patched it. When Reddit's API pricing killed third-party clients in 2023, entire moderator teams walked off and their knowledge went with them. When Discord decides to change its retention policy tomorrow, there's no export path that preserves thread structure. The old forums failed constantly — server crashes, database corruption, admins going AWOL — but the failure was recoverable because the data model was a boring SQL schema anyone could restore from a nightly dump.
The HN thread's most-cited counter-argument is worth engaging: modern platforms have real UX wins. Threaded replies, mobile push, rich media, better search-within-app. All true. But the retrospective's response is that those wins came bundled with a hidden cost — the wholesale surrender of the archive. A senior Android developer in the HN thread put it bluntly: *"I can find answers to problems from 2008 easier than problems from 2023."*
If you run a developer community — for an open-source project, a SaaS product, or a technical newsletter — the operational question is retrieval. Where do you want an answer given today to be found in 2030?
The defensible pattern that emerged in the HN comments: Discord for real-time, forum for archive. Route synchronous help ("my build is broken right now") to Discord or Slack, where fast turnaround matters. Route asynchronous knowledge ("how do I configure X") to a Discourse instance, GitHub Discussions, or — if you're willing to accept the aesthetics — a self-hosted phpBB. The archive layer needs three properties Discord fundamentally cannot provide: public URLs, HTML that renders without JavaScript, and a full-text search index that Google can crawl.
Discourse has emerged as the pragmatic default: open-source, self-hostable for ~$20/month, and Google-indexable by default. It's what Rust, Elixir, and Meta's React team all use. The Rust community forum has 300,000+ threads, all indexed, all searchable, all still linkable in five years. Compare that to the Rust Discord, where the same volume of Q&A vanishes daily.
For smaller projects, GitHub Discussions is the cheapest viable option — free, tied to your repo, indexed by search engines. It's not as good as a dedicated forum for cultural cohesion, but it clears the retrieval bar. The one option to avoid is Discord-as-primary-support-channel: it optimizes for the founder's convenience and burns the community's collective memory as fuel.
The interesting second-order effect is LLM training. Anthropic, OpenAI, and Google's models were trained heavily on 2005-2020 forum content — that's where a lot of tacit developer knowledge lived. The 2020-2026 equivalent is trapped in Discord, and no successor model will learn from it. In a decade, we may look back on the Discord era as a knowledge dark age: the period when developers stopped writing things down where they could be found.
The word 'crappy' stood out to me. I feel the same sentiment about bringing back forums, but as a person who maintained few of those for many years, I always wanted explicitly non-crappy forums.In fact, I attribute much of the decline of forums to the fact that they were crappy and hard to
I miss forums. When they were in their heyday I was an active participant in anywhere from a couple to half a dozen, shifting with whatever happened to be my hobby at the time. And local forums based around hobbies like music and photography were a great way to meet people in person because you alre
There is no need to “bring back” forums, there are plenty that already exist. You just need to participate in them if that’s what you want.
I have a lot of sympathy with this. I use some topic specific old school web forums and they feel better all round than the discord channels/forums.I suspect it's an age/attitude thing. The implicit "My forum my rules" autocracy shows its upsides on a well curated space: tro
Top 10 dev stories every morning at 8am UTC. AI-curated. Retro terminal HTML email.
> We tried the forum thing. We wanted something else. Not necessarily because it was better, though sure, maybe it was. But because it was different.I don't think the novelty explains very much, the digg/reddit comment tree format is a clear improvement in the sense that it makes it eas