The future of traditional internet forums

Following is a discussion with AI about the future of traditional internet forums.

I am a contributor to ForkBB, an Open Source “traditional” internet forum. Forums evolved from the Bulletin Board Systems (BBSs) of the dial-up era and became one of the web’s earliest and most enduring forms of organized, interactive discussion.

But beyond their original purpose, I think their flexible structure can be used for other things. Following are a few. Describe others you think may apply. I am trying to revive interest in using this type of software, instead of thinking everything has to be custom-written for specific purposes.

Community forum

Hobby groups and clubs discussing what they love.

Documentation

How-to guides organized by category, with comments and questions right on the page.

Bug tracking

A public place to report issues, with threaded replies keeping context intact.

Support desk

Common questions get answered once and stay answered — searchable, for everyone.

Guestbook

A single category makes a simple, moderated comment wall — no plugin needed.

I think your premise is quite strong. A traditional forum is really a general-purpose, persistent, hierarchical conversation engine. Once you stop thinking of it as merely “a place where people chat,” quite a few applications emerge naturally.
The important distinction is that a forum already provides several things that custom applications frequently have to reinvent: accounts, permissions, categories, topics, replies, threading, moderation, search, timestamps, subscriptions, notifications, and a durable public history.

Here are some additional applications I think fit particularly well.

A category can contain authoritative topics such as:

• “How do I reset my password?”

• “What file formats are supported?”

• “How do I configure SMTP?”

• “Why am I getting this error?”

Unlike a conventional FAQ, the discussion remains attached to the answer. If someone discovers a better solution two years later, the knowledge base improves organically.
Forum advantage: the FAQ doesn't have to be written perfectly before publication.

Each topic becomes a feature request or suggestion.

Topic: Add dark mode
Replies: Discussion, proposed implementations, votes, alternatives, developer response

This is particularly useful for open-source projects because developers and users can discuss why something should or shouldn't be implemented rather than reducing everything to a checkbox.

You can turn categories into stages:

• Proposed

• Under consideration

• Planned

• In development

• Completed

The topic itself becomes the permanent history of the feature.
That could potentially replace a surprisingly large amount of specialized “roadmap” software.

Not necessarily a replacement for Jira in a large software company, but quite useful for smaller projects.
A topic can represent:

• a project

• a task

• a decision

• a milestone

• a problem requiring resolution

Replies provide the working history.
The big advantage is that the conversation and the work item are the same object.

A forum can be configured so that the primary unit is essentially:

Question → answers → discussion

With moderation or marking of an accepted/best answer, it becomes a surprisingly capable Q&A system without requiring a completely different application.

Instead of building a proprietary support portal, a company could give customers:

• Product announcements

• Help

• Questions

• Tips & tricks

• Feature requests

• User-to-user support

And critically, the answers are publicly searchable.
One good answer can therefore support hundreds of future customers.

Each release becomes a topic:

ForkBB 1.9.12 released

The first post contains the release notes, while subsequent replies contain:

• upgrade experiences

• problems

• compatibility reports

• questions

• fixes

• user feedback

It creates a much richer historical record than a conventional changelog.

This is an interesting one.
A forum can be used to record organizational decisions:

Decision: Move the project from MariaDB to SQLite

The initial post documents the proposal and rationale. The discussion records objections and alternatives. The final post records the decision.
Months or years later, somebody can search:

“Why did we choose SQLite?”

and find the actual reasoning rather than merely discovering that somebody made the decision.

Organizations could use a forum for structured public discussion of proposed changes.
For example:

Proposed neighborhood zoning change
Proposed bylaws
New club rules
Open-source license change

The discussion becomes part of the public record.

A forum can go considerably beyond discussion:
Category: Board

• Meeting agendas

• Meeting minutes

• Motions

• Decisions

Category: Members

• Introductions

• Questions

• Announcements

Category: Events

• Upcoming events

• Event planning

• After-action discussion

Again, no specialized application necessarily required.

An event can be represented by a topic.

2026 Woodworking Expo — October 17

The topic can contain:

• location

• schedule

• directions

• registration information

and replies can handle:

• “Who's going?”

• ridesharing

• hotel recommendations

• equipment questions

• post-event discussion

The event page effectively evolves before, during, and after the event.

This is slightly different from ordinary documentation.
Imagine:

How to sharpen a plane blade

First post = carefully maintained instructions.
Replies = actual users reporting:

“This worked, but here's something I discovered…”

The documentation becomes living documentation, with real-world experience attached to it.
A moderator or author can periodically incorporate the best discoveries into the first post.

A forum can work surprisingly well for collaborative research.
Each topic represents a research question or hypothesis.
Replies can contain:

• evidence

• references

• experiments

• counterexamples

• conclusions

And unlike a chat system, the material remains organized and searchable.

Forums are particularly good at this because their native structure is chronological.
For example:

1980–1989
1990–1999
2000–2009

or:

Early history of the organization
Important people
Major events
Original documents

You could essentially build a public, conversational archive.

This may actually be one of the strongest applications.
Consider a woodworking community. Instead of creating separate custom applications for:

• tool reviews

• techniques

• species information

• finishing

• shop construction

• machinery

• troubleshooting

you can create a structured hierarchy of topics and let the community populate it.
The forum becomes a distributed knowledge base whose authors happen to be its users.

With appropriate moderation and rules, a forum can become:

• For Sale

• Wanted

• Trade

• Free

• Services

Each listing is a topic and replies provide questions and negotiation.
It isn't necessarily as sophisticated as a dedicated marketplace, but for a specialized community it may be better because the participants already have identities and reputations within the community.

This returns almost directly to the BBS concept:

• Local news

• Lost & found

• Events

• Recommendations

• Services

• Buy/sell

• Community announcements

Essentially, a modern BBS without the dial-up modem.

I think the most interesting way to market ForkBB isn't necessarily:

“ForkBB is forum software.”

It could be:

“ForkBB is discussion infrastructure.”

A traditional forum has an unusually useful abstraction:
Category → Topic → Reply
That can represent an enormous number of real-world relationships.

And there's a particularly important characteristic of this model:

That's one of the great weaknesses of modern communication systems. Slack, Discord, Facebook groups, Reddit, and similar systems are excellent at real-time or semi-real-time interaction, but valuable information can become buried in the stream.
A traditional forum says:

This conversation is an object. Give it a name. Put it somewhere. Keep it. Search it. Refer to it later.

That is an extremely powerful concept.
And I think there's an interesting historical irony here: the old BBS model may actually be better suited to building persistent community knowledge than many of the newer systems that replaced it.
The technology doesn't have to be old-fashioned just because the underlying interaction model is old.
In fact, ForkBB could position itself as something closer to “a lightweight, open-source framework for persistent community knowledge and discussion” rather than simply another forum package.
That opens up a much larger audience than people who are specifically looking for “forum software.”