For years the complaint has been the same. A small project moves its support from a forum to a chat server, and within a year the answers to common questions are gone from search. You can't find the fix unless you join the server, scroll back, and hope someone asked it the same way you would.
Then Discord said it would give every Discoverable server a public web page, with summaries of public channels and, later, individual messages that can show up in web search. Admins can opt channels out under Web Presence settings. Members get one account-wide switch to keep their own messages off the web, and it's on by default in most regions. Private servers, DMs and group chats aren't included.
Across the communities we follow, the reaction split fast. More than 20 people we tracked weighed in over a single day, from mod authors and support volunteers to privacy writers and people who simply miss forums. Some called it overdue. Others started looking for somewhere else to take their groups.
We build community software, so we have a stake in where conversations live. But this one doesn't have a clean answer, so here are both sides as fairly as we can put them.
Side 1: "Finally. Answers belong on the open web."
The people in this camp have mostly been on the losing end of chat-only support.
- Support shouldn't need a membership. Mod authors and plugin makers said the same thing: people want the answer or the download, not another server to join. Joining a server to ask a question someone already answered is a poor experience for everyone.
- Knowledge got trapped. Several developers argued that moving from forums to chat hurt small projects and game wikis the most. Years of troubleshooting turned invisible. Making some of it findable again is, in their words, how the internet is supposed to work.
- Public was always public. An IT voice made a blunt point: a public channel on a server anyone can join was never private. Tell clients to treat it like a public forum, because that's effectively what it is.
For this camp the question isn't whether to index. It's why it took this long.
Side 2: "People spoke in a room, not on a stage."
The other camp doesn't dispute that searchable answers are useful. Its problem is how it's being done.
- Context changes the meaning. People write differently in a fast chat than in a forum post they expect strangers to read. A half-joking reply at midnight reads very differently as a search result years later.
- Opt-out isn't consent. Server owners pushed back hardest on the defaults. They asked for one server-wide switch and for indexing to be opt-in, not something admins have to find and turn off. Others asked who else gets to read those pages, including AI scrapers.
- It's the old ownership problem again. At least one community owner shut down a server and moved members to another chat app. That fixes the indexing worry but not the underlying one: the rules can still change without you.
For this camp, the issue is that a conversation was held under one set of expectations and is being published under another.
Where the two sides actually agree
What surprised us is how much common ground there is under the noise.
- Almost nobody argued that all chat should be public. The fight is over defaults and consent, not over search itself.
- Both camps want reusable answers. They disagree on whether you get them by publishing chat after the fact or by writing in a public format from the start.
- Because this only applies to Discoverable servers, plenty of small project servers stay out of it anyway, so the trapped-answers problem won't fully go away.
That last point matters. Even with indexing switched on, a chat log is a poor knowledge base. Answers are spread across messages, the question is phrased five ways, and the accepted fix is often buried under follow-ups. A forum thread, a Q&A page or a plain FAQ was built to be read later. A chat log wasn't.
The trade-offs if you run a community
If you're an admin deciding what to do, these seem to be the real options people were weighing:
- Leave it on and say so. Tell members which channels are public, pin a note, and treat those channels like a forum. Useful for support-heavy servers.
- Opt everything out. Keep chat as chat and accept that answers won't be found by outsiders. Common for social or sensitive groups.
- Split the jobs. Keep chat for real-time talk, and move the answers worth keeping into something designed to be public, like a forum, a docs page or a Q&A board you control.
- Move entirely. Some owners are doing this, though moving a community is hard and members don't all follow.
None of these is free. Leaving it on means some members will speak less. Opting out keeps the knowledge trapped. Splitting the jobs means someone has to curate. Moving means starting part of the community over.
Our take, briefly
We lean towards option 3. Real-time chat and searchable knowledge are different jobs, and the trouble starts when one tool is asked to do both after the fact. If an answer is worth finding, it's worth writing once in a place that was meant to be public. But we understand the people who just want the old answers back, and we'd like to hear from admins who've run it the other way.
Your turn
- If you run a server or group, which option are you taking, and what decided it for you?
- As a member, would you post differently in a channel you knew could show up in search? Would you post at all?
- Is opt-out ever fair for conversations that already happened, or should anything published later always need opt-in?
- What's the best way you've found to turn good chat answers into something people can find without joining?
We'll read every reply, and we're especially curious to hear from support volunteers who've been answering the same question for years.
Top comments (0)