4 ms·

How do you work around the lack of a kept history?

• bandrami 7y ago
  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.
  • DagAgren 7y ago
    As I said, I use this every single day of the week. Not having it means it is not even close to a solution.
• t34543 7y ago
  Lack of history is a feature, not a bug. If you want persistent storage of decisions/etc there are better options out there.
  • DagAgren 7y ago
    Yes, like Slack.
    • maxaf 7y ago
      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".
      • DagAgren 7y ago
        Again: I use it every single day. Not for "CYA". No need to be condescending.
        • xfitm3 7y ago
          Respectfully it seems like you may be condescending
  • eythian 7y ago
    It is definitely not a feature in most corporate environments.
• mavhc 7y ago
  Quassel, The Lounge, etc
  • DagAgren 7y ago
    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.
    • vorpalhex 7y ago
      You just run the bouncers on the same machine as the daemon.
      • DagAgren 7y ago
        This does not strike you as ridiculous, at all?
        • mavhc 7y ago
          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.
    • mavhc 7y ago
      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