Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

The difference is their privacy policy has been changed retroactively against the good faith their users had. That's the problem. Of course if it's corporate it's usually monitored, but when Slack championed the user and only catered to the company when forced (via compliance reports which told you they were enabled) and now suddenly switches to a model where past contracts are broken, people have a right to be upset.


Yeah, it kinda sucks that they changed the privacy policy, but if you had actually read it, you'd have seen the part that says that they can change it any time for any reason.

And also, all they've done is give the corporation the technical ability to do something they've always been able to do -- read your private chats. It's just that before they had to do more work to do it, but they've always had the right to do it, regardless of what Slack's privacy policy said.


I mean, it sounds more like people are upset because they are embarrassed how they acted in DMs, or said things they shouldn’t have about their colleagues, and now are worried someone will see that. It doesn’t sound accidental, but that they didn’t get an Export notice, so they thought they were free to talk shit and act however they wanted to. Presumably a lot of these individuals are at smaller companies where a “CIO” might be more inclined to go in and read everyone’s private drama.

I dunno, it’s hard for me to have much sympathy. It’s a rough lesson to learn if you are in your mid 20s and maybe didn’t know any better, but anyone who has been around for any length of time should know better than to put certain things in writing. That is, like, a life skill, not some Bay Area social contract.




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

Search: