There's a conversation that keeps resurfacing in the communities we follow, and it isn't the usual "which platform should I pick" thread.
It's about format. People keep saying they miss forums. Someone says not everything needs to be a chat server. Another person argues that old-school forums were simply better than social media, and a lot of people agree. A post refusing to accept the line "why start a forum, nobody's going to use it" gets far more support than its author expected.
At the same time, the practical side keeps showing up. A small paid community launches with weekly calls and a private chat workspace, because that's where members already are. Someone grows a chat server into a real platform with thousands of active members. A volunteer admin of a self-hosted community steps away, burned out, after a couple of instances in their network go down in quick succession, and the thread underneath turns into a long, honest discussion about whether running a community is sustainable at all. An open source project moves its old forum to read-only. Someone else complains that chat threads are where good answers go to disappear.
We build community software, so we have opinions. But this one genuinely feels unsettled, so instead of arguing a side, we're going to lay out the questions we keep circling.
The convenience question
Chat wins on day one. People already have the app open, a message gets a reply in minutes, and starting a server takes less time than writing this paragraph.
- Is "where people already are" the most important factor, or just the easiest? If members won't visit a separate site, does a forum ever stand a chance, no matter how good it is?
- Does the speed of chat help or hurt? Fast replies feel alive. They also mean that anyone who wasn't online at the time missed the conversation.
- Are small groups different? For twenty people who know each other, does it matter at all where they talk?
The memory question
This is where forum fans have their strongest argument. A forum thread from years ago can still answer a new member's question. It's indexed, linkable and organised by topic. A chat history mostly isn't.
- How much does a community's value live in its archive? For support communities and hobby groups, old answers might be the whole point. For a social group, maybe nobody cares about old messages.
- Who notices when the knowledge is lost? When a busy chat channel scrolls past a great answer, nobody feels the loss until someone asks the same thing again.
- What happens when a forum goes read-only? Is a frozen archive still a community asset, or just a museum?
- Can chat platforms fix this? Threads, pinned posts and searchable channels exist. Do they actually change how people use chat, or does everything still end up in the main stream?
The calm question
Several people describe small forums as calmer than feeds. No algorithm, no outrage farming, just people who return because they want to.
- Is that calm a feature of the format, or of the size? Would a forum with a million members be any calmer than a busy chat server?
- Does slow conversation select for better conversation? Writing a forum post takes more effort than firing off a message. Is that friction good, or does it just keep people out?
- Is the forum comeback real, or nostalgia? Many of the loudest voices remember forums from years ago. Do people who grew up on chat apps want them at all?
The stewardship question
This is the one we think gets skipped most. Every community, on any format, needs someone to keep it running. Self-hosted forums need updates, backups and spam control. Chat servers need moderation and someone who owns the account. The thread about admin burnout made it clear that servers are rarely what wears people out. It's being the only person on call.
- Who owns the community when the founder steps back? In many small communities, the honest answer is "nobody has thought about it".
- Does format change the burden? A forum has more moving parts to maintain. Chat outsources the infrastructure, but not the moderation, and not the risk that an account or group can be suspended overnight with no one to appeal to.
- What does a healthy handover look like? We've seen communities survive because two or three admins shared the load and agreed in advance who takes over. We've seen others vanish because one person got tired.
- Should every community plan for its own ending? Exporting the archive, telling members where to go next, keeping old links working. Almost nobody does this until it's too late.
The "both" question
A lot of communities end up running both: chat for quick talk, a forum or knowledge base for anything worth keeping.
- Does splitting work, or does one side always die? In our experience the quiet side often becomes a ghost town unless someone deliberately moves good answers across.
- Who does that moving? It's real work. Is it a moderator job, a volunteer job, or something tools should handle?
- Does running both double the stewardship problem?
Where we are, honestly
Our own lean: chat is great for momentum, and something slower and searchable is worth having once a community starts repeating itself. But we've watched both formats thrive and both formats fail, and the difference usually seemed to be people and stewardship, not software.
So we'd rather learn from the people actually running these spaces.
Your turn
- If you run or moderate a community, is it on a forum, chat, or both, and would you choose the same again?
- Have you lost valuable community knowledge to a chat scrollback, a read-only forum or a closed group? What would have saved it?
- Admins: what keeps you from burning out, and who would take over if you stepped away?
- Is the forum comeback real where you are, or is it mostly people remembering how things used to be?
Tell us where your community lives and why. We're especially curious about the ones that switched formats and lived to talk about it.
Top comments (0)