diumConversation, Inquiry, Broadcast, Session, Execution: a teachable taxonomy for the people running the next decade of community.
Field notes on community knowledge
Guides on running Q&A, live sessions and member networks, from the team that builds Dium.
Featured post
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 Post-Hopin Vacuum: What a 2026 Virtual Conference Stack Actually Needs
Hopin coasted, RingCentral Events stalled, Airmeet pivoted. The category left a hole big enough to drive a manifesto through.
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.
'Stage Mode' Is a UI Mode, Not a Feature: the 9 Affordances Every Live Wave Needs
Spec-derived checklist for what the live state of a Session thread has to render. Eight of nine isn't enough.
Discord, Discourse, Circle, Bettermode, and the Architecture Matrix Nobody Publishes
A buyer's grid that grades platforms on real-time presence, long-form retrieval, event lobby, monetization, P2P privacy, and self-host, not pricing tier.
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.
The 'Event Pulse': the 7 Signals Every Lobby Home Should Surface
An event lobby home is not an agenda list. It's seven simultaneously-rendered signals that change minute by minute.
The Community Platform as a Local-First App
IndexedDB schema, last-write-wins reconciliation, sync queues with backoff, and why your forum belongs on the user's device first.
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.
Sponsor Booths That Convert: a 12-Element Spec You Can Copy
A sponsor booth that converts (and renews) needs twelve elements. Most platforms ship six.
Browser-to-Browser Document Sharing: WebRTC DataChannel, SHA-256, TURN Fallback
Product page disguised as a tutorial. Files never touch our servers; integrity verified at the receiver.
Trust Score: 11 Events That Should Move It, and the One That Shouldn't
Reputation gamified badly is karma farming. Reputation gamified well is your moderation team multiplied tenfold.
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.
Sponsor ROI Follow-Up: the 72-Hour Rule Is Wrong; the Real Decay Starts at Hour 8
Industry folklore says follow up within 72 hours. The actual conversion-decay curve says move it to within the working day.
Why Your File-Sharing UX Should Default to 'Never Touched Our Servers'
Privacy-positioning post. The default should be P2P; the fallback should be relayed; the operator should disclose which.
Reputation Gaming Is Real: the 4 Design Choices That Defang Goodhart's Law
Multi-factor scores, peer verification, time-decay, and anti-gaming heuristics. Together they make ring-voting structurally unprofitable.
Why Only 19% of Alumni Engage, and the 5-Screen Redesign That Doubles It
The alumni-software market is heading to $1.4B with one-fifth the engagement of a healthy Discord server. The fix isn't a new newsletter.
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.
The Green Room, the Backstage, and the Audience: a 3-Link Architecture for Live Sessions
Live sessions need three distinct join links: backstage (hosts only), green room (speakers prep), stage (audience).
The 5-Step Bootstrap Flow: From asq.php to a Hydrated SPA in <800ms
Architecture deep-dive. PHP shell → bootstrap JSON → remote JS/CSS → IndexedDB hydrate → API session exchange.
The 6-Level Trust Ladder You Can Copy from RentFox and Ship by Friday
Tactical post: a level-not-number display that maps to specific permission unlocks at each tier.
Alumni Mentor Matchmaking: the 7 Fields That Beat 'Fill-in-Bio'
Match on can-help-with × interests × timezone × availability × industry × seniority × intent, not bio text similarity.
Office Hours That Fill: Capacity, Queue, Recurrence, and the 24-Hour Reminder Cron
Office hours fill at 87% capacity when configured with weekly recurrence, 6-seat capacity, a 24-hour reminder, and a 15-minute start-of-session ping.
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.
Tables That Fill: Capacity, Auto-Close, Atomic Joins, and the SQL You Actually Need
Working code for breakout-room mechanics. The atomic UPDATE that prevents over-joins is the entire concurrency model.
Why IndexedDB Is a Cache, Not a Trust Boundary, and the Bug That Taught Us
Treating IndexedDB-stored credentials as authoritative is XSS-equivalent compromise. Auth must use short-lived signed tokens.
Anonymous Posting That Doesn't Poison the Well: the 3-Rule Design
Per-thread opt-in, hidden in display only, mod-auditable. Three rules that make anonymous posting useful without enabling abuse.
The Annual Reunion Lobby: Pre-Live, Live, Post-Live for an Alumni Weekend
Open the lobby 14 days before the reunion. Five screens become reunion-themed; the lobby outlives the event as the year-round home.
Sponsor Analytics That Close Renewals: the 6 Numbers Booth Software Hides
Unique visitors, dwell, CTA click rate, message threads, demo attendance, post-event meeting bookings: the six numbers that predict renewal.
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.
The 7 Ways to RSVP, and Why 5 of Them Are Bad for Engagement
Hard RSVP commitment underperforms soft 'follow' for live conversion. The right RSVP UX picks low-commitment-high-show-up over high-commitment-low-show-up.
Versioned Remote Bundles + Kill-Switch: How We Ship JS Without Bricking 200 Communities
Remote-loaded SPAs require version pinning, integrity metadata, kill-switch blocklist, percentage canaries, and per-tenant pinning.
Moderation Queue That Actually Gets Cleared: the 'Top of Inbox' Redesign
Sort by reporter trust × content severity × time-since-report, not FIFO. Mod queues clear 3x faster.
The Community Health Scorecard: 12 Metrics, With Formulas
One composite, six diagnostic sub-scores, twelve underlying metrics, and an operating cadence.
Alumni Giving Meets Community: How a Forum Drives 23% More Annual Fund Participation
Alumni who post in their community in the 90 days before solicitation give at +23 percentage points higher rates than non-posters.
'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.
Pre-Live, Live, Post-Live: the Three-Act Lifecycle Every Event Thread Should Follow
State-machine playbook with distinct UI per phase. Most platforms ship phase 2 only; the wedge is phases 1 and 3.
Optimistic UI for Community Posting: the 4 Conflict Cases Nobody Handles
Stale auth, removed parent, rate limit, content rejection. The four cases optimistic UIs need to handle without losing the user's content.
Auto-Raid Detection Without False Positives: the 4 Signals That Catch 90%
Join-velocity spike + low-trust authors + repeated-content fingerprint + cross-thread pattern within 5 minutes.
Answer Engine Optimization for Community Platforms: the 9 Schema Patterns ChatGPT Actually Cites
Definition Box, Comparison Matrix, HowTo Steps, FAQ, Spec Sheet, Glossary Anchor, Pricing Box, Schema Snippet, Named Formula.
The Cohort Thread Architecture: How to Organize a 6-Week Program in 1 Flow
1 broadcast, 6 weekly sessions, 6 weekly conversations, 1 help thread, 1 execution thread per learner.
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.
Hybrid Events That Don't Suck: How to Make In-Room and Remote Feel Like the Same Room
The 2021 hybrid thesis died of bolted-on streaming. True parity requires shared waves, shared Q&A queue, and a remote-first agenda, not a streaming bolt-on.
A Signed Bootstrap Envelope: the 1-Paragraph Fix for Half of Community Auth Bugs
Sign the bootstrap payload with a short TTL, audience restriction, and nonce. Server exchanges it for a runtime session.
Why Your Community Needs Three Suspension States, Not One
Mute (read-only) / suspend (time-boxed) / ban (permanent with appeal): three discipline tiers reduce repeat offenses by 41%.
Why Community SaaS Pages Are Invisible to ChatGPT (and the Fix Is a Glossary, Not Backlinks)
LLMs cite glossary pages 4x more often than blog posts because glossaries hit the entity-disambiguation step in retrieval.
Cohort Retention: the 4 Weekly Rituals That Hold Attention Through Week 5 (the Death Zone)
Week-5 attrition drops 41% with four weekly rituals: live session, peer-pair Q&A, public commitment thread, instructor critique office hours.
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 Continuation Thread: Turning Every Live Session Into Permanent Knowledge
Auto-spawn at session end, seeded with chat highlights, Q&A items, and resource links. The pattern that doubles event content lifetime value.
Discord Is a Graveyard Your Users Walk Through to Leave
Discord communities lose 67% of joiners within 30 days. The cause is structural: channels are unaddressable.
CSP, SRI, and Nonce-Based Scripts for a Remotely-Loaded Community SPA
Remote-shell SPAs require CSP allowlists for shell origin + tenant API, SRI for pinned bundle versions, and nonce'd inline scripts for theming.
The 'Apology Economy': How Appeals and Ban-Expiry Rebuild Trust Faster Than Perma-Ban
Time-bounded suspensions with documented apology pathways recover 28% of suspended members. Perma-ban recovers 0%.
The 'Definition Box' Page Template That Wins AI Overviews for Community Queries
First 60 tokens directly answer 'X is...'; entity reinforced in URL, H1, and meta; FAQPage schema in the head.
The Conference Operator Command Center: 14 Panels Every Event Director Needs
Live occupancy, room queue, sponsor lead pace, no-show alerts, mod queue, hosts on/off, continuation-thread spawn rate, and seven more.
Speed Networking That Actually Works: Rotation, Skill-Matching, and the 4-Min Rule
Auto-match speed-networking sessions should rotate every 4 minutes with skill-balanced pairing for a 67% higher next-meeting acceptance rate.
Migrating From Discord to a Forum That Actually Keeps the Conversation: a 14-Day Playbook
Two weeks, day by day, to move a long-tenured community off Discord without losing the engaged third.
The 6-Table Schema Behind Every Modern Wave-Based Community
Spec-derived. Six tables hold the entire forum + lobby + sponsor stack.
Profanity Filters Are the Wrong Layer: Where Toxicity Actually Lives
Profanity filters catch 12% of harm. Intent-classified toxicity at the embedding layer catches 78% with fewer false positives.
The 'Comparison Page' That Cite-Bait Works On
Comparison pages cited by ChatGPT use a labeled-cell matrix in the first 800 tokens, named entities in column headers, and verifiable numbers per cell.
Pre-Event Activation: the 14-Day Countdown Play That Doubles Day-One Show-Up
Intro waves day-14, agenda day-7, speaker AMAs day-3, table sign-ups day-1. Tactical playbook.
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.
Migrating From Circle to Dium: When Monetization Isn't Your Wedge
Honest comparison: we don't always win on monetization, but if your community runs more than 2 events per quarter, the duct tape costs more than the migration.
The Audit Log Every Community Needs (and the 4 Events Nobody Logs)
Role changes, content edits, moderation actions: most platforms log these. The four nobody logs: session impersonation, P2P transfer metadata, retention deletes, key rotations.
GEO for Forums: How to Get Cited When Someone Asks 'What's the Best Community Platform for X'
Vertical AEO. Per-vertical comparison pages with named-criterion grading, not generic top-10 lists.
Post-Event in 24 Hours: the Recap Thread, Replay Link, and Follow-Up CTA
In 24 hours: continuation thread per session, replay attached, summary, 1-question follow-up poll, no-show recovery email separate.
Slack vs Forum: the 'Channels Are a 2014 Idea' Essay
Slack's channel-as-namespace model loses information ~30% faster than thread-as-namespace because messages aren't addressable units of work.
The Lead Capture Form Sponsors Actually Want (and the 5 Fields You're Forcing on Them)
3 fields beats 8 by 2.4x conversion. The qualifier (one ranked-need question) gives BDR teams enough segmentation without the friction.
The Honest 'We Don't Do That' Page: 7 Things Dium Chose Not to Build
Trust-building anti-feature post. The seven things buyers expect us to ship that we deliberately don't.
Sponsored AMAs, Sponsored Office Hours, Sponsored Tables: the New Sponsor Unit Economics
3-5x panel CPM for sponsored AMAs. Multi-week renewals for sponsored office hours. Higher renewal rates for executive-led tables.
Discourse Plugin Ecosystem vs Dium Native Modules: When 'Extensible' Becomes 'Fragile'
Discourse's plugin model wins for power users. Dium's bootstrap+remote-shell model wins for managed deploys with kill-switch versioning.
Professional Associations Are Sitting on a Data Goldmine, and Using It for Newsletters
Associations who replace newsletter-only outreach with wave-based discussion grow renewals by 17 percentage points within 12 months.
Bettermode vs Dium: the Embed War and the Standalone War
Bettermode dominates SaaS-embedded communities. Dium dominates standalone clubs and multi-modal events. Different wedges.
The Nonprofit Advocacy Lobby: How a Forum Turns Into a Campaign HQ in 48 Hours
1 broadcast, 1 office-hours 'I'll call my rep with you,' 6 tables for state chapters, 1 execution thread for letters.
Mighty Networks vs Dium: the Creator vs the Operator
Mighty Networks indexes on solo creators. Dium indexes on operators running clubs, alumni, and conferences with multiple hosts.
Workforce Boards & Re-Entry Programs: What a 'Help' Thread Does That a Job Board Can't
Help threads in workforce communities resolve barriers (transportation, childcare, doc requests) at 4x the rate of static job-board listings.
Heartbeat / Geneva / Guilded / Skool: a Fast Tour of the 'We're Not Discord' Pack
Taxonomy post: each platform serves a different sub-segment. Pick the one that matches your members' shape.
The Enterprise Community-of-Practice Playbook: 1 Flow, 5 Wave Types, 1 Quarter to Value
Stand up a CoP in 90 days: 1 flow, 1 weekly session, 1 monthly broadcast, an open inquiry, an open execution, weekly tables.
Self-Hosted Forums in 2026, phpBB, Flarum, NodeBB, Discourse, Dium, the Honest Matrix
Includes self-host capability for Dium. The trade-off matrix for IT-led buyers who need sovereignty.
Why Your Internal Slack Is Killing Your Tribal Knowledge, and the Forum Overlay That Saves It
Slack channels lose ~30% of mentioned context within 14 days; an addressable wave overlay preserves 95% of decisions for >12 months.
Why We Ship as asq.php + Remote Shell Instead of a Docker Image
A local PHP bootstrap + remote JS shell delivers managed-SaaS UX without losing operator sovereignty.
The Office Hours Operating Manual: Templates, Scheduling Math, and the Host Recognition Loop
Lead-magnet calibre playbook covering host recruitment, narrative, recognition, and the 24-page printable.
Migrating Off Hopin / RingCentral Events: the 21-Day Data Export and Reshape
Tactical migration guide. Sessions map to Wave Sessions; booths map to Pages; attendees become directory members.
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 Sponsor Booth Buildout Checklist (37 Items)
Lead-magnet for sponsorship managers. Brand assets, 3 demos, perk gate, lead form, 2 staff seats, 4 booth-only files.
'Build in Public' Is Dead: Long Live 'Build in Your Community'
Public building peaked in 2024. The same content shared first to a private community and then to public produces 3x the qualified inbound.
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.
Office Hours Are the Most Underused Community Feature on the Internet
Recurring office hours generate 4x the 1:1 conversion of webinars at one-tenth the prep cost.
The 'Lurker Problem' Is Fake: Your Platform Is Just Unaddressable
The 90-9-1 rule is a UI symptom, not a behavior law. Addressable threads with single-question prompts move lurkers to repliers at ~22%.
Why Every Community Should Ship a 'Leaving' Workflow
Communities with structured offboarding forms recover 11% of departing members within 6 months.
The 'Show Me What You're Working On' Weekly Thread Is the Best Growth Hack You're Not Running
Weekly recurring Execution thread averages 38% reply rate and seeds 60% of next month's office-hours topics.
The Notification Taxonomy: 4 Urgency Tiers and the Wake-Up Rule
Ambient (in-app) / digest (email) / interactive (push with action) / wake-up (call/SMS). Four tiers with explicit thresholds.
Digest Emails That Don't Get Muted: the 7-Block Layout
Digest emails open at 38% when structured as: who's online → 1 question for you → 3 conversations near you → 1 office hour → 1 sponsor offer → unsubscribe-by-topic.
Quiet Hours, Timezone-Aware Scheduling, and the 1-Tap RSVP From Email
Notifications respect 3 axes: quiet hours, timezone, urgency tier. One-tap RSVP from email lifts attendance by 19%.
A Community 'For You' Feed in 12 Lines of SQL
Discovery rank = 0.35×temporal + 0.20×type-weight + 0.15×engagement + 0.20×personal + 0.10×context, computed in a single window-function SQL.
Semantic vs Keyword Search for Forums: When Each Wins
BM25 still beats pure vector search on title/tag retrieval. Vector wins on body retrieval and duplicate-question detection.
Duplicate-Question Detection: the 1 Model That Saves Your Moderators 8 Hours/Week
Cosine similarity > 0.82 on title-+first-paragraph embeddings catches 76% of duplicate questions before posting.
Why Your AI Summarizer Should Write the Next *Question*, Not the Recap
Summarize-then-ask outperforms summarize-only by 41% on next-day reply rate. The AI's job is to set up the next contribution.
The 'AI Host' for Office Hours: a Transcript-Aware Co-Pilot, Not a Replacement
An AI host should queue questions, surface relevant past threads, prompt the human host with 'this was answered before in X', and draft the recap.
Voice-to-Thread: Turning a 60-Min Zoom Into 1 Broadcast + 5 Inquiries + 1 Execution Thread
Voice-to-thread parses meeting transcripts into a Broadcast (decisions), Inquiries (open questions), and an Execution thread (action items).
The 5 AI Features Your Community Should NOT Ship (and the 1 That 10x's Value)
Skip auto-replies, AI hosts that talk, AI moderation hard-actions, AI personalized feeds without explainability, AI engagement bots. Ship: AI duplicate-question detection.
Interactive: 'Build Your Community in 60 Seconds'
Embeddable wizard that produces a flow + suggested wave types based on 5 questions about your community.
Interactive: 'Hopin → Dium' Migration Cost & Time Estimator
Embed; capture leads. Hopin migration time = sessions × 12min + booths × 22min + attendees × 0.3s.
Animated Explainer: 'How a P2P File Transfer Actually Works in Your Browser'
Lottie + diagrams: signaling server pairs peers, ICE finds path, DTLS encrypts, DataChannel chunks 16KB at a time.
'Wave Type' Poster (Printable PDF)
Eye-candy + backlink hook: the 5 thread types, Conversation, Inquiry, Broadcast, Session, Execution, on a 24x36 poster.
Live Demo Embed: 'Drop in to a Sample Dium Lobby'
Always-live multi-tenant sandbox with seeded waves, a running office-hour, and a sponsor booth.
'The Forum Architecture Map' Poster (24x36, Downloadable)
Engineering eye-candy: a wave platform stack: PHP shell → bootstrap JSON → SPA → API → WS/SSE → IndexedDB cache → P2P signaling.
Open Dataset: 100 Anonymized Wave Threads (CSV) for Researchers
Backlink magnet: 100 anonymized waves with type, lifecycle, reply count, trust scores. Reproducible community research.
How a 200-Person Alumni Chapter Ran a 48-Hour Fundraiser Entirely in Dium
1 broadcast, 12 office hours, and 4 execution threads: raised $73k in 48 hours.
Inside a 6-Week Cohort: Every Wave, Every Metric, Every Retro Lesson
A 6-week cohort with 28 learners, 6 sessions, 6 conversations, 1 execution thread, 96% retention to week 6.
The Conference Operator's Diary: Hour-by-Hour of Running a 1,200-Person Hybrid Event
1,200 attendees, 14 booths, 32 sessions, 8 tables, 1 lobby: peaks at 480 concurrent live with 78% session attendance.
No posts match. Try fewer words or pick another category.
Browse by category
Each category page lists every post on one topic, newest first.
Operating modelThe unit of community work. Thread types, their lifecycles, and how a platform should model questions, discussions, announcements, live sessions and projects.
19 postsEvents and lobbiesRunning live and hybrid events: the lobby, stage mode, sponsor booths, tables, RSVPs, and what happens to the conversation after the session ends.
18 postsComparisonsHow community platforms differ under the hood, and practical guides for moving a community from one tool to another.
15 postsLocal-first and P2PEngineering notes on browser storage, sync, peer-to-peer file sharing and the trade-offs of keeping community data close to the member.
15 postsTrust and healthModeration, reputation, slow mode, health metrics and search visibility: how to keep a community useful as it grows.
23 postsVerticalsPlaybooks for specific programs: alumni networks, cohorts, associations, office hours and sponsor renewals.
23 posts