3 ms·

Call me an old fart but I much prefer email. Email gives me a reminder to keep me organized. And the two teams I worked on that use slack killed productivity

Call me an old fart but I much prefer email. Email gives me a reminder to keep me organized. And the two teams I worked on that use slack killed productivity by chatting all day and sending animated gifs. Plus, people expect email to be asynchronous. With slack, I get a mixture of immediate and asynchronous requests. So every message breaks my flow while I determine the priority level.

itaifrenkel 10y ago
I know. We use emails for some meeting summary. But you can't ignore the fact that many attacks start with phishing, and slack is free from that problem
- the_common_man 10y ago
  Slack is not free of the problem whatsoever: https://arstechnica.com/security/2016/04/hacking-slack-accounts-as-easy-as-searching-github/ https://arstechnica.com/security/2016/04/hacking-slack-accou... http://www.businessinsider.com/slacks-security-breach-may-be-worse-than-its-letting-on-2015-3 http://www.businessinsider.com/slacks-security-breach-may-be... http://www.networkworld.com/article/3123727/collaboration/the-next-target-for-phishing-and-fraud-chatops.html http://www.networkworld.com/article/3123727/collaboration/th...
  - daenney 10y ago
    Those three links don't really relate to third parties getting unauthorised access through phishing by leveraging Slack. Slack has plenty of security issues, but you're not proving phishing by any of those sources. It can potentially make you more vulnerable to phishing, but that's not the same thing. The links in question relate to: * Searching on GitHub for Slack API tokens * The Slack database hack * How the rise of ChatOps can open you up to many more issues if someone gains access to employee's Slack accounts and the risk of third-party applications which might open up things you do to more entities than you realise
itaifrenkel 10y ago
And... Apparently after enough time, people come to expect slack to be asynchronous too.
daenney 10y ago
> And the two teams I worked on that use slack killed productivity by chatting all day and sending animated gifs. That sounds much more like a people problem than a technology problem, if that's how they chose to spend the majority of their time on the job.

itaifrenkel 10y ago

I know. We use emails for some meeting summary. But you can't ignore the fact that many attacks start with phishing, and slack is free from that problem

the_common_man 10y ago
Slack is not free of the problem whatsoever: https://arstechnica.com/security/2016/04/hacking-slack-accounts-as-easy-as-searching-github/ https://arstechnica.com/security/2016/04/hacking-slack-accou... http://www.businessinsider.com/slacks-security-breach-may-be-worse-than-its-letting-on-2015-3 http://www.businessinsider.com/slacks-security-breach-may-be... http://www.networkworld.com/article/3123727/collaboration/the-next-target-for-phishing-and-fraud-chatops.html http://www.networkworld.com/article/3123727/collaboration/th...
- daenney 10y ago
  Those three links don't really relate to third parties getting unauthorised access through phishing by leveraging Slack. Slack has plenty of security issues, but you're not proving phishing by any of those sources. It can potentially make you more vulnerable to phishing, but that's not the same thing. The links in question relate to: * Searching on GitHub for Slack API tokens * The Slack database hack * How the rise of ChatOps can open you up to many more issues if someone gains access to employee's Slack accounts and the risk of third-party applications which might open up things you do to more entities than you realise

itaifrenkel 10y ago

And... Apparently after enough time, people come to expect slack to be asynchronous too.

daenney 10y ago

> And the two teams I worked on that use slack killed productivity by chatting all day and sending animated gifs. That sounds much more like a people problem than a technology problem, if that's how they chose to spend the majority of their time on the job.