Threads remember; channels forget

Threads remember; channels forget

Discord shipped threads as a clutter fix. Their more interesting effect is on a community's collective memory.

What the data shows
Servers that moved long-running topics into threads showed two changes: the main channel stayed readable, and — less obviously — old conversations stayed resumable. Thread-organized knowledge got revisited and replied-to days or weeks later at higher rates than the same content left to scroll past in a flat channel.

Why it happens
A flat channel has no addressable memory — once a topic scrolls off, it's effectively gone, because there's nowhere to "return to" it. A thread is a persistent container with its own notification context, so a question asked Tuesday can still get answered Friday without being lost. This is the inverse of Telegram's weakness: Telegram's reply chains exist but don't aggregate into browsable, named containers, so knowledge there decays into the timeline.

The caveat
Threads fragment discovery — a great answer buried in a thread is invisible to someone who never opens it, trading scroll-loss for click-loss. The net effect on findability is genuinely unsettled, and over-threading recreates the dead-channel problem at smaller scale.

Open question: is the right structure few-channels-many-threads, or does thread sprawl just relocate the silence problem one level down?