Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Guide to Slack import and export tools

get.slack.help

Post reply on HN
Print view View original

31–40 of 529 posts

Re: Guide to Slack import and export tools

#31

Post by freehunter »

bryanrasmussen wrote: post #9
larrik wrote: 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?

If it's your company's asset, you gave permission for sharing that data when you signed the e-handbook at orientation, the same document that gives them the right to monitor your work emails, put MDM on your work-issued phone, and log your work machine's network traffic into their SIEM.

You have no right to privacy when you're inside your company's office using your company's computers to access your company's network. They own it all, you just have permission to use it within the guidelines they set and you signed off on when you were hired.

Re: Guide to Slack import and export tools

#32

Post by larrik »

joshenglish wrote: post #5
larrik wrote: 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…

This is not completely true. Been able to pull DMs via the Discovery API.

I actually didn't know this. Why did they have the big alert when turning on the Compliance Exports then?

Re: Guide to Slack import and export tools

#34

Post by IncRnd »

fjsolwmv wrote: post #19
tvanantwerp wrote: post #13

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?

You need non-repudiation of changes to log contents.

Re: Guide to Slack import and export tools

#35

Post by bigtunacan »

larrik wrote: 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…

This is to be expected from Big Brother. These days one should assume the telescreen is always watching and so should be very cautious as to not commit a thoughtcrime.

---- Edit ----

To clarify; my comment is referring to the novel 1984. While a bit tongue in cheek, it was not meant entirely as a joke.

This is a forum visited mostly by IT workers. I would assume most of us here know enough (or should know enough) to realize that any of our communications at work can be read by someone else and so you may want to treat it a bit as such.

In my personal programming working experience I have seen data captured in all of the following forms, reviewed, and then used to fire or prevent firing individuals.

Email, Instant messaging, Phone calls (audio recordings), Computer monitor (video recordings)

Re: Guide to Slack import and export tools

#37

Post by madeofpalk »

mistermann wrote: post #20
joshenglish wrote: post #8

Earlier quoted context omitted.

Yes. You can access Outlook365 and Exchange via APIs as well as Google Apps for Business. Plus Calendars, etc. Anything that uses LDAP locally and now through the 365 APIs.

How does it work, an outlook 365 admin(?) Can read anyone's email that they want? Do they essentially just log onto the normal Hi as that user?

Yes.

Re: Guide to Slack import and export tools

#38

Post by jerf »

fjsolwmv wrote: post #19
tvanantwerp wrote: post #13

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?

Provenance. I can doctor my local logs just about as quickly as I can type. True, it's a bit harder than some people estimate to keep the whole thing coherent, but that just means that you hear about the people who get caught, but not the ones who do it successfully. If I am capable of doctoring Slack's copy of the logs with sufficient effort, it is certainly orders of magnitude harder and much legally riskier (as I would be committing many felonies in the process).

Re: Guide to Slack import and export tools

#39

Post by lawnchair_larry »

markstos wrote: post #25
astro_robot wrote: post #4

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.

Password change/login is not necessary to pull email in from G Suite.

Re: Guide to Slack import and export tools

#40

Post by joshenglish »

mistermann wrote: post #20
joshenglish wrote: post #8

Earlier quoted context omitted.

Yes. You can access Outlook365 and Exchange via APIs as well as Google Apps for Business. Plus Calendars, etc. Anything that uses LDAP locally and now through the 365 APIs.

How does it work, an outlook 365 admin(?) Can read anyone's email that they want? Do they essentially just log onto the normal Hi as that user?

It depends on the setup. There are different nuances but through an Admin granted API key you could potentially access all emails. There are safeguards that companies put in place to restrict this as well.
Post reply on HN