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

101–110 of 529 posts

Re: Guide to Slack import and export tools

#101

Post by majewsky »

castlecrasher2 wrote: post #90
ramblerman wrote: post #68

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 have to ask why they wouldn't want to talk to an individual suspected of wrongdoing? Why look at security footage, when you can "just ask" the suspect?

You misunderstood. The accused may not be willing to cooperate, but the accuser probably will.

Re: Guide to Slack import and export tools

#102

Post by dugluak »

EpicEng wrote: post #83
dugluak wrote: post #76

Earlier quoted context omitted.

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

Depends on the state I would assume, but of course IANAL. Some states have single party consent, and you're certainly not in a private area. You'd have to look into the eavesdropping laws where you live. You realize that many buildings have security cameras, right? I'm still very confused as to why you believe that your communications over a company owned platform should/would be private.

because I dont see the difference between having direct conversation vs having electronic conversation in the office premises. why would there be different rules for them?

Re: Guide to Slack import and export tools

#103

Post by personjerry »

random4369 wrote: post #93
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 mak…

Would you provide a small list of solutions as examples?

Re: Guide to Slack import and export tools

#104

Post by cjrp »

castlecrasher2 wrote: post #90
ramblerman wrote: post #68

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 have to ask why they wouldn't want to talk to an individual suspected of wrongdoing? Why look at security footage, when you can "just ask" the suspect?

The recipient isn't suspected of wrongdoing, they're on the receiving end of the abuse.

Re: Guide to Slack import and export tools

#105

Post by s3nnyy »

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…

> "Compare that to our email, where I can go into anyone's messages immediately if need-be. This is all very standard corporate IT stuff that you need for HR and legal reasons."

Wow, THAT is highly illegal in Europe.

Re: Guide to Slack import and export tools

#106

Post by froindt »

Null-Set wrote: post #72
froindt wrote: post #51

Earlier quoted context omitted.

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…

As a company policy I sure hope your IT doesn't make emails available to your management.

No they don't, but I work at a large megacorp. At a small 10-20 person non-technology company startup, the admin on Slack is likely to be the owner or general manager. It could be another 5-10 people before a person is hired on as full-time IT.

Re: Guide to Slack import and export tools

#107

Post by bruhbruhbruh »

random4369 wrote: post #93
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 mak…

Infinite space of solutions? I think not. If the harassment was in any way sexual, the company had a legal responsibility to investigate. It may have been a timely matter and the best and/or only solution was to read the messages at the offending intern's workstation.

Re: Guide to Slack import and export tools

#108

Post by dsacco »

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?

What is the material difference between having employees save DM logs in an auditable, authenticated way and being able to view employee DMs?

If any employee can ostensibly be compelled to provide their logs when asked by their employer, you are getting just as much information as if IT can view them directly. The only way IT doesn't get as much information is if the system doesn't work, for example because employees can alter their logs or simply refuse to provide them. In that scenario having employees saving their own logs gives you more privacy, but doesn't solve the essential problem.

The tradeoff here is convenience of access versus friction. When you are reviewing an auditable log of information related to an employee, you don't necessarily want to have to ask the employee for that information, nor do you necessarily want them to know you're reviewing it.

Re: Guide to Slack import and export tools

#109

Post by dugluak »

scolson wrote: post #85
dugluak wrote: post #49

Earlier quoted context omitted.

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

Your employer owns the data, not you. The owner of something doesn't need special permission to look at it. It could be a company provided computer, email, or filing cabinet; they all belong to your work and they do not need to ask anyone to get in and look at the contents. Even something that has a reasonable expectation of only containing personal belongings (eg. a locker) may or may not be protected from employer…

How can a personal conversation be a "data". you mean they can potentially sell my personal conversation with a friend as if its a company owned data?

Re: Guide to Slack import and export tools

#110

Post by mfringel »

random4369 wrote: post #93
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 mak…

No, he chose it because a group of interns was harassing other interns.

Words matter.

Post reply on HN