The Thread That Outlasted the Desk
Open a support ticket and it has one job: disappear. Someone answers it, closes it, and the record goes wherever closed tickets go, which is nowhere anyone else will ever look. Open a comment thread under an unrelated blog post about the same company and it has no job at all. Nobody assigned it one. And yet six years later it's the better resource, longer, more accurate, and easier to find than anything the company built on purpose.
This isn't a design story. The thread wins with worse tools: no threading, no search, no moderation queue, just a text box under a post from a decade ago that some stranger still checks out of habit. It wins because of one property the support desk structurally cannot have. Every ticket starts at zero. The agent on the other end doesn't know about the hundred identical complaints filed last month, because those cases were closed and their knowledge closed with them. The thread, by contrast, never resets. Comment forty adds to comment one instead of replacing it. By the time comment sixty arrives, the page is a complete record of a failure mode the company itself may not have connected across a hundred separate, siloed cases.
That's the asymmetry, and it's not an accident of bad support software, it's the incentive underneath it. A company benefits from tickets that don't accumulate. If each case resets, no single case ever proves a pattern, and no pattern ever becomes an obligation. A support system optimized for throughput is, by construction, a system optimized for forgetting. Nobody sits down and decides to build institutional amnesia. It falls out for free from closing tickets one at a time.
The thread has no such incentive working against it, because nobody owns it. Whoever wrote the original post isn't running a business, isn't paying an ops team, and has no reason to prune the record down to something flattering. So the complaints just sit there, sortable by nothing, searchable by everything, indexed the way anything public on the web gets indexed. A person deciding whether to buy the thing finds this page before they ever find the company's own support portal, because the portal isn't public and the thread is. The unofficial channel out-ranks the official one on the exact axis that matters to a stranger trying to decide: does this happen to other people too.
The person keeping it alive is usually unpaid and has nothing to gain from doing it well. They answer questions for years because someone asked and it felt rude not to. That's the part that makes the whole arrangement feel unstable when you look straight at it. A company's support function, the thing it presumably spends money on, is being outperformed by a volunteer with a comment box, not because the volunteer is better at customer service, but because the volunteer's page has one thing built in that the paid version was structurally denied: memory that carries across visitors instead of dying with each one.
None of this requires bad faith from the support team. A closed ticket isn't a cover-up, it's just the shape the tool gives you. The tool was built to resolve individual cases, and it does that fine, one at a time, forever, without ever producing a record of what it resolved. The thread was never built to do anything. It just happened to keep every comment instead of throwing each one away once it stopped being someone's active problem.
The desk clears one complaint and calls it done. The thread just keeps the receipt.