Live data from Hacker News

Guide to Slack import and export tools

get.slack.help

191–200 of 529 posts

Re: Guide to Slack import and export tools

#191
post #51

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…

These are all the sorts of things that you would ideally want management to know about so they can make better informed decisions. Assuming of course that you have competent and trustworthy managers.

Re: Guide to Slack import and export tools

#192
post #158
post #46

It's hard to see how this is bad -- they have/should be able to have access to your other work-related communication and work product (modulo the weird rules around things like salespersons' "rolodex"es). It's so easy to have private channels these days it's hard to see how this should even inconvenience anyone.

Because it is illegal in many countries to access somebody's personal communication even if it uses eg. a corporate email address?

It's not, not in Europe, not anywhere. Saying it a couple of times doesnt make it true. Your boss can read your emails and most likely already does. This is exactly the same with any internal messaging and it's perfectly legal in the workspace.

Re: Guide to Slack import and export tools

#193
post #170

Earlier quoted context omitted.

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 mak…

> but your chosen solution is totalitarian surveillance in the workplace because an intern got offended? Sigh Totalitarianism is a socio-political paradigm, not a stand-in word to describe things you think constitute surveillance in the context of a business. Companies require the capability to maintain auditable records of employee activity on the information channels they own and manage. Your company is not recordi…

> because almost all the good developers I know work in environments

But they aren't True Good Developers... /s

Re: Guide to Slack import and export tools

#194

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…

If two people want to have a private conversation, they'll just find another means by which to do it. In the long run, abusing your privileged access to conversations intended to be private (however justified you may consider it to be) will just breed mistrust among employees. I would quit a job that treated me as a child which must be supervised in such a manner.

Re: Guide to Slack import and export tools

#195

Earlier quoted context omitted.

> 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. Why couldn't you just ask the recipient to look on his station? > We had to make all intern accounts into multi-channel guests after that Are 2 interns ever allowed to be alone together? I mean it's essentially the same, you are saying they can't be trusted so either you always need them in grou…

You are assuming that harassment was direct, sending messages to the accusers. My impression is that this was a group chatting privately about the accusers either making fun of them or coordinating actions. While this can be done through other channels (in person or private cellphone) allowing it on corporate infrastructure without monitoring is not acceptable.

What's stopping the harassers from setting up a secondary Slack install for coordination of such nefarious ends?

The only use I can see for this would be evidence after the fact. Surveillance is almost never the proper way to enforce acceptable standards of behavior.

Re: Guide to Slack import and export tools

#196
On a semi-side topic: Canadian dev here, I always immediately hard delete e-mail correspondence (both inbox and sent) with HR on anything that I feel private about, as I don't want the guys in IT reading it. I know they don't, but I also know they can.

For example, I might trust the head of IT but I might not trust that new intern or "new guy" they just hired.

What do you guys do when it comes to HR correspondence at your places of work?

Re: Guide to Slack import and export tools

#197
post #96
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.

[deleted]

Re: Guide to Slack import and export tools

#198

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 mak…

nice nirvana fallacy

Re: Guide to Slack import and export tools

#200

Earlier quoted context omitted.

> 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. Why couldn't you just ask the recipient to look on his station? > We had to make all intern accounts into multi-channel guests after that Are 2 interns ever allowed to be alone together? I mean it's essentially the same, you are saying they can't be trusted so either you always need them in grou…

You are assuming that harassment was direct, sending messages to the accusers. My impression is that this was a group chatting privately about the accusers either making fun of them or coordinating actions. While this can be done through other channels (in person or private cellphone) allowing it on corporate infrastructure without monitoring is not acceptable.

In that case, that would be absolutely none of your business. You're making assumptions and jumping to conclusion about what went on.
Post reply on HN