Live data from Hacker News

Guide to Slack import and export tools

get.slack.help

281–290 of 529 posts

Re: Guide to Slack import and export tools

#281
In the end that's your responsibility to maintain professional level when using internal company tools.

Not surprisingly the three persons who forwarded me this thread with comments like: "shit", "is this legal or allowed?", or even "I'm screwed if they read my messages" - are the ones who are always trash talking colleagues, pairs and the company itself.

Re: Guide to Slack import and export tools

#282

Earlier quoted context omitted.

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

In any case, if you would plan any of that, I would guess that it would most probably leak out through entirely nontechnological channel - e.g. by somebody overhearing in person, or even by a co-conspirator defecting for their own gain.

Cloak-and-dagger games are very similar to building your own crypto: likely to be broken at a fundamental level, never mind the amount of magic security glitter that you pile on top.

Re: Guide to Slack import and export tools

#283
post #224

Earlier quoted context omitted.

I hate to tell you this but if you would quit a job for this reason you probably can't work in the US. The US has laws about corporate compliance, and it has requirements for things like dealing with sexual harassment. There is no such thing as a "private conversation" that takes place over a corporate network. For example, in the US sexual harassment is taken seriously. If a company gets a complaint of sexual harass…

Wouldn't it show up in slack of receiver?? If receiver has issues, he/she can show his/her slack to get the investigation started.

And what if the issue is two employees are using Slack to discuss using a competitors proprietary information on a contract proposal? Or two employees are discussing how to arrange the books so that they don't receive margin calls while trying to hide large trading losses?

You can't depend on everyone being on the up and up.

Re: Guide to Slack import and export tools

#284
post #217

Use slack-cleaner[1] to nuke messages you've sent. You need to generate a legacy token[2]. [1] https://github.com/kfei/slack-cleaner [2] https://api.slack.com/custom-integrations/legacy-tokens

Does this actually delete anything or just flag it as deleted?

Re: Guide to Slack import and export tools

#285
I had just assumed this was the case anyway.

I used to be a teacher, and have recommended Slack to an old colleague as a way facilitate staff communication at their school. Additionally my current organization quite often works with children at workshops and the like.

For an admin not to be able to look through DMs is a serious safeguarding issue, so I'm happy this is now possible.

Re: Guide to Slack import and export tools

#288
post #89

Earlier quoted context omitted.

While I agree with auditable access to employee DMs, there is a middle ground solution that trivially solves the problem you've presented. Instead of providing the employer with access to the employee's messages directly, logs can be signed at both the blob and message level. Then if an employee selectively turns over only some of their logs, the mismatch will be readily apparent.

Not sure what you mean by blobs? If Slack implemented a scheme like this, they should sign a message which includes metadata like the org name, channel name and timestamps in addition to text.

By blob I mean an archive dump of every message and the metadata you're describing. If that dump is hashed, selectively presenting messages in the dump is obvious.

Re: Guide to Slack import and export tools

#289
post #114

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…

> Not sure how much compliant this is with the law, but in this case the law should be more protective towards employees. This change is precisely because of regulations like GDPR, among others.

The ECHR said that the employer has no right to access any private employee communication, even if it happened at work.

That contradicts what you’re saying quite a bit.

Re: Guide to Slack import and export tools

#290

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.

Well, that's only if the person actually knows that the conversation isn't private.

I would also like to point out that the person you were responding was talking about interns, so were arguably 'actually' children.

Post reply on HN