Posthog is closing their Slack community in favor of forum

Original Article ↗ Hacker News Discussion ↗

PostHog is shutting down its public Slack community and moving support and Q&A to a custom-built forum, arguing that forums offer better long-term searchability, structure and Google indexing than real-time chat. Commenters broadly agree that Slack and Discord are poor knowledge bases—hard to search from the outside, noisy, and potentially very costly at scale—but note that chat still excels for synchronous, ephemeral conversations. Much of the debate centers on whether PostHog should have used mature off‑the‑shelf software like Discourse instead of building its own forum, and on the broader trend of communities reconsidering proprietary chat platforms for support.

Forum vs. Chat for Support & Community

  • Strong support for moving support from Slack/Discord to forums.
  • Forums seen as better for:
    • Long-term knowledge, clear threads, and future readers via web search.
    • Tracking questions and answers without losing them in noise.
  • Slack/Discord/IRC viewed as better for:
    • Synchronous, ephemeral conversations, quick back-and-forth, early product feedback.
  • Many argue both should coexist: forums for durable Q&A; chat for real-time discussion.

Searchability & Discoverability

  • Major complaint: Slack and Discord content is locked behind logins and not Google‑indexable, making solutions hard to find.
  • Forum content (if public) is easily indexed and browsable by topic.
  • Discord search quality is debated: some find it “fine,” others call it poor (no verbatim or partial matches).
  • Tools like AnswerOverflow (for Discord) and static Slack exporters are cited as partial workarounds.
  • Some suggest vector search / LLMs to surface and summarize forum content.

Cost, Lock-in, and Reliability

  • Slack becomes very expensive at scale for public communities; examples of hundreds of thousands per year are cited.
  • Slack’s per-active-user pricing and discount changes make it a poor fit for public support.
  • Discord is free but criticized for:
    • Privacy concerns, captchas, limited client choice, Nitro upsells, and potential policy shifts.
  • Concern that any proprietary chat platform can revoke access or change terms.

Building vs. Buying Forum Software

  • Surprise and skepticism that PostHog built its own forum using Strapi instead of using Discourse or similar.
  • Counterarguments:
    • Desire for deep integration with docs, unified login, rewards, and custom community features.
    • Forums are “just CRUD”; legacy forum stacks are dated and clunky.
  • Maintaining Discourse is reported as non-trivial for small teams; others defend it as powerful but feature-heavy.
  • Various alternatives mentioned: Flarum, XenForo, phpBB, vBulletin, NodeBB, Zulip, GitHub Discussions, ActivityPub‑enabled forums.

UX, Moderation, and Spam

  • Need for “modern forum UX”: mobile-friendly, easy onboarding, low admin overhead, Reddit‑like voting to surface good answers.
  • Forums with good SEO attract heavy spam; may require strict moderation or paid posting.
  • Some worry heavy Google indexing of discussions can chill open conversation.
  • SPA/JS-heavy forums criticized for being harder to archive and sometimes less search-engine-friendly.