3 ms·

Good advice but this is a little dubious "For other internal communication use Slack". Use slack because it is beautiful and free, not because of security

itaifrenkel 10y ago
Older employees, and some managers, I found prefer email in many cases. I still request them to use slack
- thedevil 10y ago
  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.
- tluyben2 10y ago
  I know almost no one who prefers Slack: people I work and worked with find it messy and rather use Skype for calls, some issue tracker and if required email for follow up. For both software related and other tasks alike. Not sure it is related to old.
cyberferret 10y ago
I've found the best results is to use Slack as a central communications repository, whilst still using other tools for better management. Otherwise Slack itself can still get noisy and distracting if it is the ONLY method of communication. For example, we use Trello for feature planning and tracking marketing activities etc., but have Trello post to a specific channel in Slack also. Additionally, we use Intercom + Helpscout for customer support, and have those posting to a support Slack channel as well. Then there are the various Amazon reporting and deployment services which also post log messages to Slack. In a nutshell, I can jump on Slack to check the overall 'big picture' view of my SaaS, but not have things get lost in the noise.

itaifrenkel 10y ago

Older employees, and some managers, I found prefer email in many cases. I still request them to use slack

thedevil 10y ago
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.
tluyben2 10y ago
I know almost no one who prefers Slack: people I work and worked with find it messy and rather use Skype for calls, some issue tracker and if required email for follow up. For both software related and other tasks alike. Not sure it is related to old.

cyberferret 10y ago

I've found the best results is to use Slack as a central communications repository, whilst still using other tools for better management. Otherwise Slack itself can still get noisy and distracting if it is the ONLY method of communication. For example, we use Trello for feature planning and tracking marketing activities etc., but have Trello post to a specific channel in Slack also. Additionally, we use Intercom + Helpscout for customer support, and have those posting to a support Slack channel as well. Then there are the various Amazon reporting and deployment services which also post log messages to Slack. In a nutshell, I can jump on Slack to check the overall 'big picture' view of my SaaS, but not have things get lost in the noise.