I, I just have to mention that IRC had these archives so repeat questions had a corpus to search. The walled gardens don't.
For my teams the "modern" solution is Mattermost. My (biased) feelings are that it's 10x better than free-slack and 100x better than paid.
It did? I used IRC pretty frequently back in the day, and the only logging I ever saw was through your own client. This was in the days of dialup, so you'd miss any conversations from when you weren't logged in. If you were fancy, you'd have a bouncer set up on an always-on remote server to log messages when you were away. But I never saw any centralized logging à la Slack/Teams/Mattermost. It's certainly not something supported by any IRCd I'm aware of. Maybe a few channels had custom bots that logged everything to a centrally searchable location, but I never saw such a thing.
Indeed, some here even tout the "ephemeral nature of IRC as a feature, not a bug." [0]
I miss the old Internet.
And get off my lawn!
I still don’t understand what slack can do that IRC and a few bots can’t.
Here's Ubuntu: https://irclogs.ubuntu.com/
For many businesses, this is a feature, not a bug.
Internal communications are discoverable in litigation. If you have records, you can be compelled to turn them over.
I used to work in healthcare. Internal messages had a maximum retention of 30 days. That wasn't driven by IT or the users. That was a decision made by legal. In that space, you are always being sued by somebody. The lawyers want to minimize exposure and that's a fight they're basically always going to win.
To be clear: it's better if that's a decision made by the business. But it's also one of those cases where what the decision makers care about isn't necessarily aligned with what the users care about, so there's ultimately not a lot of incentive for Slack to care.
In some cases, as Slack says, there may be a legal mandate to log employee conversations, but in other situations there may be legal restrictions on reading employee-to-employee conversations. That all probably varies by jurisdiction.
And then you have more complicated situations, like companies that use Slack to offer tech support to their customers, or random open-source projects or local volunteer projects using Slack. They might pay for a business license for various features, but it's probably not clear to every member that that would mean whoever set up the Slack account should get to read everyone else's correspondence.
You also want some kind of safety check to make sure that a random IT guy who set up the Slack system at a small company isn't reading through people's DMs and private channels to stalk people or access confidential information.
In which US jurisdictions can employee-to-employee records (from employer-owned communication media) be denied to the employer/customer but maintained by an unrelated third party?
As such, you need to be able to review the legal status of every pairing or group of people's private chats.
At any point in time a US based customer might invite a EU based customer, so looking specifically at US jurisdictions is irrelevant.
In a single legal entity?
> At any point in time a US based customer might invite a EU based customer, so looking specifically at US jurisdictions is irrelevant.
What case law are you considering when you insinuate that Slack must review the retention of records between users of a Slack business customer?
(But I would also start making backups regularly, because who knows if how long this would last)
clearly they need to sue themselves and demand their slack history in discovery
"Workspace Owners can apply for Corporate Export. This lets you export all messages (including DMs and private channels), but only if your company has legal or compliance requirements and Slack approves the request. Once approved, exports are scheduled and delivered automatically."
So they have the tech built, you just aren't allowed to use it. Who would use this piece of garbage?