100%. No need for bouncers, search indexers or chat loggers.
Real time communication should be used for real time communication. Send me an email if it's async, or call me if it's urgent and I'm not available via normal RTC channels. People want Slack etc to be an everything client, which is why we have the gross bloat we have.
Also, you spend a day off and if the channel is active, it's a chore trying to get back on track if the team does not have better suited communication methods. Quasi real time discussion on a bug is great, but it's better to add the final findings on the ticket/PR. Same for features, draft up a doc afterwards. Slack and the lack should be considered transient and important information put on more permanent and more brows-able forms (Wiki, document repo, ticket system,...).
It’s not a feature. People use it this way and expect a history and search feature. It’s the way it is. Not providing a feature is not a feature. It’s an inconvenience at best, and a lack of respect at worst when you present it like people are doing it wrong.
Real time communication should be used for real time communication. Send me an email if it's async, or call me if it's urgent and I'm not available via normal RTC channels. People want Slack etc to be an everything client, which is why we have the gross bloat we have.