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

501–510 of 529 posts

Re: Guide to Slack import and export tools

#501

Post by ravitation »

jiveturkey wrote: post #307
ravitation wrote: post #211

Earlier quoted context omitted.

> socio-political paradigm Sigh. And workplaces are socio-political contexts... I didn't find it very difficult to get past his hyperbole, and I frankly find it hard to believe that you did. It isn't hard to argue that monitoring channels that even just imply privacy, regardless of whether they take place in the workplace (or in academia, or at home) is a violation of personal rights - regardless of the fact that you…

> imply privacy Workplace provided communication mechanisms do not in any way imply privacy. Best practices are that staff sign an acknowledgement of such, so that there is no such confusion.

So, if an acknowledgement is needed... It's needed because there might be an implication of privacy, right?

Re: Guide to Slack import and export tools

#502

Post by caymanjim »

Piskvorrr wrote: post #493
isatty wrote: post #450

Earlier quoted context omitted.

Are there any guides to check for shady SSL certificate shenanigans on an employer provided Mac?

If the employer had physical access, what would prevent them installing a rootkit? Then you couldn't detect a fake certificate no matter what you tried. Or deeper, if you distrust the provided software, what makes you trust the hardware? It's turtles all the way down ;)

I'm not talking about anything shady here. We're told that they're going to update our desktop SSL certificates for this reason. Partially CYA, partially compliance/legal. I'd probably quit if someone were keylogging or screengrabbing my work machine without my knowledge, but I'm not talking about employers being sneaky.

And this is exactly end-to-end encryption that the original thread responder mentioned; I know it's in place so I won't connect to my personal accounts from the work machine. That's what my phone is for (and I won't use their wifi for my phone, either).

Re: Guide to Slack import and export tools

#503

Post by isatty »

Piskvorrr wrote: post #493
isatty wrote: post #450

Earlier quoted context omitted.

Are there any guides to check for shady SSL certificate shenanigans on an employer provided Mac?

If the employer had physical access, what would prevent them installing a rootkit? Then you couldn't detect a fake certificate no matter what you tried. Or deeper, if you distrust the provided software, what makes you trust the hardware? It's turtles all the way down ;)

Yes, but assuming partial good faith (this does sound like an oxymoron, but humor me) - how would I go about checking for cert misuses?

Re: Guide to Slack import and export tools

#504

Post by staticassertion »

humanrebar wrote: post #481
criley2 wrote: post #369

Earlier quoted context omitted.

Before tech, witness testimony was the same thing. Old boys club keeps it "verbal only", but someone blows the whistle and testifies regarding the conversation. Technology didn't change anything. You can't have a private conversation at work. Period end of story. If you manage to conceal your communications, not only could you be violating laws (depending on your industry and relevant regulations) but you're likely v…

> You can't have a private conversation at work. I was talking about discretion, not privacy. Those are two different things. Discretion is controlled sharing of thoughts, ideas, and information. Marking documents "trade secret" is an example of discretion. Trade secrets are not private information. I'm not arguing that information should be unavailable when a warrant or subpoena requires disclosure. I'm arguing that…

> Two employees need to be able to have a healthy, discrete conversation about working with the boss without having to worry about a transcript of the conversation pop up in a performance evaluation later in the year.

If you are worried about this, the issue isn't Slack. I don't worry about my boss reading my slack DM's - I'm well aware of what process would be involved there (my boss would be fired immediately, and wouldn't even have access without Legal involved). If you're worried about your company 'snooping' on you that's an underlying, unrelated problem.

Re: Guide to Slack import and export tools

#505

Post by ravitation »

TheSpiceIsLife wrote: post #351
ravitation wrote: post #211

Earlier quoted context omitted.

> socio-political paradigm Sigh. And workplaces are socio-political contexts... I didn't find it very difficult to get past his hyperbole, and I frankly find it hard to believe that you did. It isn't hard to argue that monitoring channels that even just imply privacy, regardless of whether they take place in the workplace (or in academia, or at home) is a violation of personal rights - regardless of the fact that you…

Generally speaking it’s easy to argue that employees have no expectation of privacy on the work network for the following reasons: 1. Regulation in most countries requires it to be this way, we’ll most countries any of us is likely to work in. Which is to say: The Law Hath Spoken , which is to say: The People Hath Decided . 2. The employer should have spelled this out to you at time of hire, and had you sign a docume…

I didn't actually argue that there was an expectation...

I only said that the comment I replied to relied on a purely arbitrary definition for what an invasion of personal privacy was... He argued that because "your company is not recording your activity in the privacy of your home or on the street" it wasn't unreasonable (or totalitarian), because the company was "protecting itself and other employees from potentially problematic abuse scenarios." Even though it's amusingly easy to imagine that a totalitarian regime would make the same argument for its own surveillance practices....

Re: Guide to Slack import and export tools

#506

Post by swat535 »

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…

You are exactly why we should all be extremely careful with what we communicate on the work network.

By "you" I don't mean you personally of course, what I mean is IT in general.

You might be ethical enough to not abuse your new found privilege but who is to say that the next guy won't?

I believe all employees should restrain from posting personal and private things on a company network or any related device for that matter.

You never know how this data can be misused.

Re: Guide to Slack import and export tools

#507

Post by nedt »

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…

Following GDPR could be much easier. Simply delete messages ASAP. Best protection of private data is not storing them.

Re: Guide to Slack import and export tools

#508

Post by ravitation »

wfo wrote: post #301
dsacco wrote: post #242

Earlier quoted context omitted.

> And workplaces are socio-political contexts They're not governments, they're companies. > monitoring channels that even just imply privacy, regardless of whether they take place in the workplace (or in academia, or at home) is a violation of personal rights It isn't, unless your definition of "personal rights" includes "things I personally want which are neither codified in, nor protected by, laws."

>They're not governments, they're companies. You're right, it's important to note they are more powerful and exercise more control over the lives of their employees than many governments, though employees often have the same opportunity to leave their company as they do their government (none). >It isn't, unless your definition of "personal rights" includes "things I personally want which are neither codified in, nor…

> You're right, it's important to note they are more powerful and exercise more control over the lives of their employees than many governments, though employees often have the same opportunity to leave their company as they do their government (none).

Especially when they're also dependent on their corporation for healthcare and retirement...

This is exactly my point, it's effortless to compare corporations to government, especially in this context. For the other comment to base his argument around the word "totalitarian" seems nothing if not disingenuous, given that the meaning behind the word is clear.

Re: Guide to Slack import and export tools

#510

Post by mbrumlow »

I am mostly worried about the bait and switch. If this feature was only applied to messages after the announcement then that would be fine. I am sure many of you have had conversations over slack thinking well it was okay because nobody could see them.
Post reply on HN