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

401–410 of 529 posts

Re: Guide to Slack import and export tools

#401

Post by ggregoire »

simonbw wrote: post #380
ggregoire wrote: post #274

I'm always surprised by the amount of DMs people send in Slack. I've worked in 2 companies using Slack and, in both, about 80% of the total messages were DMs. It seems crazy high to me. I wonder if people just send all day private stuff unrelated to work, or if people have trouble with trust and transparence on the workspace..

I don't find that surprising. Most of the communications I have at work are with a specific person, not with a whole channel. It's not because I don't want other people to know what I'm saying to someone, it's that I don't want to bother them with stuff that isn't relevant to them.

How do you know you bother them? Your comment makes me think to daily meetings in SCRUM. Sure most of the stuff people are working on or that blocks them is not relevant to everyone else, but we do it because it's good for the whole team to share and stay up-to-date on what is going on. As a tech lead/manager, I apply the same logic for my communication. I use DMs only for stuff that shouldn't be discussed publicly.

Re: Guide to Slack import and export tools

#402

Post by shurcooL »

jedberg wrote: post #370

You can tell who here has worked for a large American company and who hasn't. If you've ever worked for a large American company, you know that nothing you do on company equipment or with a service the company pays for is ever private, and you should never assume it is. I'll be honest, I always thought Slack DMs were viewable by the admin. As a Slack admin myself, I always assumed I had that ability. Never used so, I…

That’s precisely my view on this too.

Re: Guide to Slack import and export tools

#403

Post by dbalan »

This is going to be a problem for open source communities that use a semi-public slack as the communication platform. I don't think the users expect the DMs to be public to the project admin.

Its not necessarily bad. Bit it might be time for those communities to move.

Re: Guide to Slack import and export tools

#405

Post by Kalium »

mixmastamyk wrote: post #87
softawre wrote: post #75

Earlier quoted context omitted.

Not to be contrarian here, but could you offer a solution given that you've thought about this?

Did you miss his first (the second) paragraph?

I don't know about parent, but I did notice that! I saw it clearly written there. I read it and understood it. I understand that the person who wrote it believes it is sufficient to cover all relevant needs.

I would posit that this person may not be familiar with the importance of collecting evidence against possible future needs. An IT manager's testimony from memory, no matter how perfect, is not as useful as evidence collected in a technological manner at the time of offense.

With that in mind, walking over and looking at the intern's screen might be considered by some to be less than a full replacement.

Re: Guide to Slack import and export tools

#406

Post by mnm1 »

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…

Why would you have such conversations or expectations when using company chat? That's unprofessional and, frankly, stupid because it puts one's job in danger (as could an in person conversion heard by the wrong people at work). If you want to talk in private, there's dozens of other chat programs out there you can run on your own devices.

Re: Guide to Slack import and export tools

#407

Post by jasonlotito »

QasimK wrote: post #18
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 the EU would have something to say about that: https://www.telegraph.co.uk/news/2017/09/05/landmark-eu-ruli...

Yeah, they said it here[1], and basically, given cause and given notice, they can still access private communications on work property. So not exactly what you are implying.

From the actual source: https://www.echr.coe.int/Documents/Press_Q_A_Barbulescu_ENG....

Re: Guide to Slack import and export tools

#408

Post by draw_down »

jedberg wrote: post #370

You can tell who here has worked for a large American company and who hasn't. If you've ever worked for a large American company, you know that nothing you do on company equipment or with a service the company pays for is ever private, and you should never assume it is. I'll be honest, I always thought Slack DMs were viewable by the admin. As a Slack admin myself, I always assumed I had that ability. Never used so, I…

Right. Prior to this announcement, it didn't matter whether the technical capability was actually there. I also assumed it was already possible. It is simply preposterous to assume any nonzero amount of privacy in the context of any coporate comms medium including email, Slack, or anything similar.

Hell, if they could somehow save a buck by putting cameras in the office bathrooms they probably would.

Post reply on HN