Live data from Hacker News

Guide to Slack import and export tools

get.slack.help

21–30 of 529 posts

Re: Guide to Slack import and export tools

#22
I was always under the impression this was already going on. I don't see the surprise here: there shouldn't be any expectation of privacy with regards to conversations between employees happening on company virtual grounds.

Heck, in my previous company when we wanted to talk about something off-the-record, we'd even physically go off campus due to the sheer amount of walls equipped with 'ears'.

Re: Guide to Slack import and export tools

#23
I think if the employer provides the tool, it is their data.

I know there are different traditions in other places where they consider something like work email to be more of an employee owned or privacy issues. I always thought that was a bit wonky and it is easier to identify who owns what by ... who owns it.

Re: Guide to Slack import and export tools

#24

As head of IT for a company using Slack: FINALLY. Don't get me wrong--it's not like I want to read your messages and very likely won't. But there are times when I have no choice. A few years back, a group of interns started privately harassing other interns via Slack. Only way to see it was to boot an offending intern from his work station and go into his Slack to see what was happening. We had to make all intern acc…

Why can't the recipient save a copy of logs?

Because they typically can be easily falsified.

Re: Guide to Slack import and export tools

#25

Do employers have the same tools with email?

You mean like with Google's G-Suite? Admins can always change your password to one that they know and log in with it. Even with a 2FA policy, they can generate backup codes to use. Generally assume that yes, corporations can read their corporate email accounts. However, they may have policies that prevent their staff from accessing other employees email accounts without a specific need.

Re: Guide to Slack import and export tools

#26

This should not be surprising to anyone. You're giving your data to a corporation who has every incentive to give it to your employer. The only real surprise here is that they weren't doing this earlier.

That's backwards. You're working for an employer who has every responsibility to monitor business communication. Slack can't "give" something they were never supposed to control in the first place and only have by accident of architecture. This fixes an old bug.

Re: Guide to Slack import and export tools

#27
post #17
post #2

Previously, you could only see employee DMs if you turned on Compliance Exports, at which point you could download all of them going forward . Now it sounds like everything you've ever written could be downloaded at any time without notice. So, all of those communications you had with co-workers based on the promise they would be private until you were notified future ones wouldn't be anymore? Now it's ALL available…

You should not assume your communications are private if there is no end-to-end encryption. Also, the employers are often required to do this because of regulations. (I think those are silly regulations given that end-to-end encryption is so easily available nowadays, but the companies don't really have a choice here.)

Ah, I work remotely, so I normally don't worry about that sort of thing.

Re: Guide to Slack import and export tools

#28
post #2

Previously, you could only see employee DMs if you turned on Compliance Exports, at which point you could download all of them going forward . Now it sounds like everything you've ever written could be downloaded at any time without notice. So, all of those communications you had with co-workers based on the promise they would be private until you were notified future ones wouldn't be anymore? Now it's ALL available…

why presumably due to GDPR? I would think it was a possible GDPR problem for them in the future. Specifically, you wrote it based on expectation it was private and now it is not, when did you give permission for sharing that data?

GDPR was mentioned in the announcement email (though not for this line item).

Re: Guide to Slack import and export tools

#29
post #24

Earlier quoted context omitted.

Why can't the recipient save a copy of logs?

Because they typically can be easily falsified.

You could have the logs signed with Slack's PGP key so they cannot be altered without the signature causing a mismatch.

Re: Guide to Slack import and export tools

#30
post #18

Earlier quoted context omitted.

Meh. Nobody should be surprised by any of this in the slightest. If your employer provides / pays for any kind of communications tool, the only sane position is to assume that they can - and probably do - monitor every single byte you send.

I think the EU would have something to say about that: https://www.telegraph.co.uk/news/2017/09/05/landmark-eu-ruli...

Seems a little different. Courts ruled that work emails could be viewed, just not personal accounts used on work computers.
Post reply on HN