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

91–100 of 529 posts

Re: Guide to Slack import and export tools

#91

Post by softawre »

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?

As a manager, if I fire somebody or they leave, I get access to their mailbox via Outlook365 for like 3 months, just in case I need to grab something from it.

So there must be a way to assign ownership of a mailbox to another user.

Re: Guide to Slack import and export tools

#92

Post by drinchev »

Looking at all positive comments here, this is generally a bad news.

Not sure how much compliant this is with the law, but in this case the law should be more protective towards employees.

I imagine the following situation

I write on a company-owned piece of paper - "My boss is an idiot". Then take this piece of paper put it in an envelope ( owned by the company as well ), write the name of my colleague and seal the envelope. Then put the envelope on the recipient's desk.

I bet it would be illegal for my boss to take that letter, open it and read it.

P.S.

Looks like with e-mails the law is more protective towards employees :

[1] : https://www.reuters.com/article/us-privacy-emails-echr/europ...

[2] : http://www.internationallawoffice.com/Newsletters/Employment...

[3] : https://www.womblebonddickinson.com/uk/insights/articles-and...

Re: Guide to Slack import and export tools

#93

Post by random4369 »

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…

There's an infinite space of solutions to your particular problem, but your chosen solution is totalitarian surveillance in the workplace because an intern got offended?

I avoid workplaces which force shit like this. So do all the good developers I know, because they're people who can afford to be choosy.

Bullies are pretty adept at functioning in these environments. Instead of harassing on monitored DMs, they'll make verbal comments with double meanings, use their leverage to put their targets in unpleasant situations, undercut their targets at meetings etc. Totalitarian surveillance doesn't stop bullies. It just makes your workplace a soul-destroying shithole for the employees who are forced to work in it.

Re: Guide to Slack import and export tools

#94

Post by toomuchtodo »

froindt wrote: post #51
mindcrime wrote: post #3

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 there's some middle ground, some grey area where whether it's alright is murky. It's kind of pulling the rug out from under people when the policy of a 3rd party provider abruptly changes and suddenly tons of messages become available to the company. There are a number of things I might mention to a coworker over a private IM which wouldn't necessarily put my employment at risk, but would be awkward for manag…

All of those conversations should take place out of band of employer communications tools.

Never write something you wouldn’t want printed on the front page of a newspaper.

Re: Guide to Slack import and export tools

#95

Post by truetraveller »

freehunter wrote: post #15
mindcrime wrote: post #3

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.

Honestly I didn't realize my Slack DMs on my work account weren't private until I saw this. I assumed that since my employer pays for the account, any message I sent was being monitored.

you meant "were" instead of "weren't"

Re: Guide to Slack import and export tools

#96

Post by 6d6b73 »

duxup wrote: post #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.

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

Not really. Just because the employer pays for the office building doesn't give them access to my private conversations with other members of the team.

Re: Guide to Slack import and export tools

#97

Post by mindcrime »

joshenglish wrote: post #30
QasimK wrote: post #18

Earlier quoted context omitted.

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.

Additionally, unless your work environment is sophisticated enough to fiddle with the certificates on your machine, and run a MITM proxy, you should be safe using something like GMail over https. Now I'm sure some companies do manage to intercept outgoing https traffic, but I doubt that most companies do.

OTOH, I still think being paranoid is the safest policy, so if you're plotting to overthrow your boss, or sell secrets to your biggest competitor, I still wouldn't do it on the company networking, and/or using a company computer.

Re: Guide to Slack import and export tools

#98

Post by wglb »

dugluak wrote: post #49
darkstar999 wrote: post #36

Earlier quoted context omitted.

Without.

how is it legal. Even the law enforcement needs to provide a warrant in case they want to search my apartment.

If you are employed in the US, your information and device use policy is very likely to say that, or your HR handbook, that you agreed to when you are hired.

Re: Guide to Slack import and export tools

#99

Post by [deleted] »

dugluak wrote: post #76
EpicEng wrote: post #61

Earlier quoted context omitted.

Not if you're living in one of their cells. Your employer pays for slack and it is a work related tool, just like your emails. If you want to have private communications then send a text. BTW they can also search your desk because, you know, it's not yours.

what about, lets say, conversations in the company owned cafeteria? can the employer record them without your consent and use as evidence against you?

[deleted]
Post reply on HN