diumThe 5 Threads That Make Up Every Modern Community
Conversation, Inquiry, Broadcast, Session, Execution: a teachable taxonomy for the people running the next decade of community.
Operating model
The unit of community work. Thread types, their lifecycles, and how a platform should model questions, discussions, announcements, live sessions and projects.
Conversation vs Inquiry: When a Discussion Needs a 'Best Answer' and When It Actively Shouldn't
Stack Overflow's accepted-answer pattern poisons brainstorms. The line between the two formats decides whether contributors keep replying.
The Inquiry Mode You've Never Seen: Four Versions of 'Asking'
Question, Help, AMA, Office Hours: four lifecycle profiles of a single Inquiry primitive. Treating them as one mode is the original sin of forum design.
Broadcast vs Announcement: the Importance Ladder Your Community Needs
Three-tier importance scoring with effective and expiry dates separates the Q4 OKR launch from the Friday lunch reminder.
Sessions Are Not 'a Zoom Link in a Thread': the Live → Async Lifecycle a Session Thread Needs
Pre-live, live, post-live, continuation. The four-act play that converts a webinar into permanent community knowledge.
Execution Threads: How 'Hire / Hackathon / Project' Lives in Your Forum, Not Your Project Tool
The forum-as-jobs-board pattern with deadline, role, comp, milestones, assignees: five fields that make coordination native.
The 'Wave' Is the Right Unit of Community Work, and 'Channel' Is the Wrong One
Channels were a 2014 idea. They created surface area without commitment. The wave, a single answerable unit of community work, is the unit the next decade is built on.
A Field Guide to Thread Schemas: Every Column, JSON Shape, and Lifecycle Rule
Open-source the summary_json.extra_fields model as a standard. Copy-paste schemas for all five thread types.
Auto-Spawning Recurring Office Hours: the Cron That Turns 1 Thread Into 52
Working code + cron recipe. The host doesn't recreate next week's session; the platform clones it.
'Best Answer' as an Opt-In: Why Your Askers Should Choose, and Your API Should Enforce
Server-side guard on a UX pattern Stack Overflow hardcoded. The asker decides whether the thread can be marked solved.
Slow Mode Is Per-User, Not Global, and Why Every Discord and Slack Got This Wrong
Global slow mode punishes the contributors. Per-user catches the spam. The difference is one column in the cooldown check.
Anonymous Posting Is a Display Hint, Not Identity Stripping, and That's a Feature
True anonymity requires schema-level author_id nulling. Display-anonymous still preserves moderation auditability, and that tradeoff is correct for almost all communities.
The Wave Type Decision Tree: Pick the Right Thread Type in 30 Seconds
A 5-question decision tree that picks Conversation, Inquiry, Broadcast, Session, or Execution for any post.
The AMA Operator's Pre-flight Checklist
Host bio thread, pre-seeded Q&A, 60-90 min window, co-host moderator, post-AMA continuation thread.
The Help-Thread Triage Matrix
Triage on urgency × routability: Critical → page, High → routed person, Normal → tag, Low → tag + 72h auto-close.
The 'Channel' Is the Worst UI Primitive of the Last Decade
Channel-as-namespace creates surface area without commitment. Thread-as-namespace maintains 1:1 mapping between conversation and addressable URL.
AMAs Are Dying Because Reddit Treated Them as Marketing
AMAs declined when they became press tours. The format is healthy where hosts answer for 60+ minutes with no PR script.
Interactive: 'Build Your Community in 60 Seconds'
Embeddable wizard that produces a flow + suggested wave types based on 5 questions about your community.
'Wave Type' Poster (Printable PDF)
Eye-candy + backlink hook: the 5 thread types, Conversation, Inquiry, Broadcast, Session, Execution, on a 24x36 poster.