Hacker News new | past | comments | ask | show | jobs | submit login

Several IRC servers do have support for authentication and access control (and audit trails as well I suppose).

Only centralized history/logging and search would need to be bolted on if needed. In the non-centralized case your IRC client takes care of all of that.





Lack of logs and history is a feature not a bug.


For business users, there are regulatory requirements. You need to keep information around for some period of time, but not forever. History and searching is useful for spreading tribal knowledge throughout an organization.


Does that actually extend to Slack/slack-like things though?

Since I would see Slack more of a replacement for phone calls or hallway discussions. Neither of which typically has any logs or recordings (and I wouldn't want to work somewhere that did keep such logs).


It does yes. This is why for example message history data export is a paid feature. Its a requirement for certain types of compliance.


In what areas would you find such requirements? And shouldn't the default position be that it is illegal to keep those logs? Especially those involving direct messages between employees.


Sure I understand but I don’t think that aligns with the spirit of the comment I replied to. I read it as FOMO.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: