Comment by muglug
5 years ago
Slack developer here, views are my own.
Prior to Slack I spent many years as an OSS maintainer. I also participated in a Slack channel that discussed my OSS tool's general problem space. That Slack workspace was on the free plan, so messages older than 6 months were memory-holed.
In practice that wasn't too big of an issue. Most developers understood that GitHub was the place for concrete actionable things and long-term discussions, whereas Slack was the place to build relationships and address burning questions quickly. Most developers understood this distinction, though occasionally some would have to be steered towards GitHub when discussing potential bugs that benefitted a proper write-up.
I also worked at a large company that paid for Slack, and it was much more of a long-term memory resource. But as always, whenever I found myself repeatedly searching in the message history for a particular piece of information it always made sense to put it somewhere more defined — in a readme or some other sort of document.
At Slack we have the same basic breakdown — Slack (the software) provides a really useful context for why certain decisions were made, and in a pinch the search feature is great for finding particular nuggets of information, but that doesn't stop us using Quip, GitHub and Jira for tracking longer-lived information.
As an end user, I find that in practice most projects don't actually move any information to a suitable spot.
I can't tell you how many times I've Googled an obscure error message and the only two results were the source code where the error came from and that self-hosted, open-source Slack alternative that Google can index. At that point, I already went to check the source code, and when I click the chatroom where the message is supposed to be, I reach some kind of archived page that's clearly at completely the wrong place in the chatroom history with no way to find what I was actually looking for.
At least the open source clone is searchable, so many troubleshooting could've been avoided if people had used forums rather than Slack/Discord/Mattermost for "support forums".
If they'd been using a forum, would you have a good record of the solution? Or would the problem just never have been solved? The low friction of slack-like tools matters.