Spectrum [0] is heading in the right direction to counter this but it's still a walled garden.
[0] https://blog.apollographql.com/goodbye-slack-hello-spectrum-...
Spectrum [0] is heading in the right direction to counter this but it's still a walled garden.
[0] https://blog.apollographql.com/goodbye-slack-hello-spectrum-...
As you said, it makes it very annoying to find said information later, especially if you're not already part of the community/don't know where to look.
But a lot of communities use it for a lot more than basic chit chat. I've seen open source projects where relevant info is only shared on their Slack server and nowhere else. Companies often get useful resources shared on their Slack instances that never gets backed up elsewhere for later.
And in the gaming world, it seems like Discord is the default method of communication for the game development, modding, speedrunning and hacking/datamining communities. For instance, most of the relevant techniques used for speedrunning Zelda Breath of the Wild are only found in the Discord server, or a Google Docs linked from it.
There needs to be a separation of the ephemeral from the non ephemeral here, and communities need to share the latter on publically accessible sites instead.
I wonder whether some of the attraction of slackfor community and q&a is the immediate feedback and the ephemeral nature of the questions. If I am looking for an answer, I want it asap. And maybe it is easier to ask or answer questions because both go away? At the least it means that the answers will avoid some of the SO issues (where the best answer is 10 years old and has been superseded).