In our case, we didn't. Kept history wasn't a feature people used or wanted. Stuff you were going to refer back to later was for email.
As I said, I use this every single day of the week. Not having it means it is not even close to a solution.
Quassel, The Lounge, etc
Forcing each user to maintain an always-online machine is not really a good solution compared to just... having the history available to everyone, always.
You just run the bouncers on the same machine as the daemon.
This does not strike you as ridiculous, at all?
running 2 programs to provide another higher level interface? not really.
IRCd - real time, ram buffering of messages. Quassel - reads and stores buffers in a database, allows users to retrieve them.
If it's an internal chat system then the server admin just runs that second layer on top for those who want it, they're all multi user
Lack of history is a feature, not a bug. If you want persistent storage of decisions/etc there are better options out there.
Yes, like Slack.
Slack is more CYA than a store of knowledge. Yes, it's really great for pointing fingers: you can literally link to a specific message, saying "here, this dude made the call".
Again: I use it every single day. Not for "CYA". No need to be condescending.
Respectfully it seems like you may be condescending
It is definitely not a feature in most corporate environments.