Please note that this document was compiled on a turbulent flight to Philly from Savannah via Atlanta; typos likely.

--

Just as the noble ideal of digital democracy hasn't exactly panned out as we thought it would (yet), Slack – once hailed as a panacea to the deluge of crowded email inboxes –– has failed to live up to its expectations, too, and I urge here that open-source communities find alternatives to Slack as it stands in fundamental opposition to all for which we stand.

• Slack is fundamentally in diametric opposition to working in the open.
• Not open-source, so why do we use it for open-source projects? Makes. No. Sense.
• Synchronous to the point of data obesity – a.k.a. information overload
• Only those @here at any given time are part of conversation – no scheduling of these spontaneous discussions, etiher. We all lead different lives with different schedules.
• High barrier-to-entry for some; others actively dislike and choose not to use because of its lack of structure.
• Lack of semantic structure that provides a narrative, organizes knowledge in human fashion.
• API that conveniently (for Slack) allows lots of incoming data sources but hardly any simple ways of pushing data out of Slack elsewhere.
  • Sub-issue: A bot could theoretically be built but it would still (a) likely require use of / command in Slack and, in turn, conscious actions on part of user and (b) it would need advanced ML and textual analysis to structure information from Slack in proper taxonomy.
• Assumption exists among many that because it was posted in Slack, everyone knows about it. WRONG. Sorry, Charlie.
• Cumbersome to maintain availability types: here/away/do not disturb status.
• Only those with experience working on tech teams usually have prior habit of keeping Slack open. Thus, they rarely log on to see mentions/messages.
• Public servants find Slack befuddling, to say the least.
• If what we're doing is too unimportant for email notifications, are we really saying our work is important?
• Slack definitely isn't meeting people where they are.
• You hit the 10K message limit way faster than you think; at that point, you permamently begin losing shared knowledge.
• Slack is classified as a Schedule IV controlled substance by the Interaction Design Foundation. Its addiction rate is high, and user habit leads to inability to switch.
• Inaccessible by default rather than open by default; you must at least make an account with Slackin (if set up) just to view content.
• Mistaken belief that Slack messages aren't committed to permalink, which makes abuse and violations of CoC more likely. WRONG!
• Slack chat often used in lieu of IRL meetings or video conferences;

• Stickiness (also a con; see: slack addiction)
• Emotional design
• Ecosystem of integrations
• Channels allow new ideas to spring forth organically
• Sociality; builds relationships across geographic spaces in addition to getting work done

Question for consideration: Do any of the above pros merit a competitive advantage for Slack that can't be built by others?

• Real-time chat.
• Emojis. More emojis. Did I mention emojis?
• Collaborative, real-time document editing
• File-sharing
• Wiki-type
• Low barrier to entry
• Ideally, some integration with email for public servants.
• Open by default.

• Rocket.Chat -
• Mattermost -
• Basecamp - Oldie but a goodie. Considered in project management circles as baseline, simplest yet most functional project tool.
• Notion.so ($$$, but a perfectly legal hack exists that's in line with their ToS)
• Quip - Fantastic for collaborative documents; great chat; rather expensive; no current ability to make group folders publicly editable/viewable by default.
• Discourse - On its face, an ideal, extendable solution that should work but never has caught on; people have this odd and illogical ideological opposition to 'forums' -- likely thanks to the early days of the Web.
• Discourse - On its face, an ideal, extendable solution that should work but never has caught on; people have this odd and illogical ideological opposition to 'forums' -- likely thanks to the early days of the Web.
• Dropbox Paper - Very nice UI that pulls users in; individual papers can be made publicly available for editing and viewing; collections cannot.
• GSuite - Documents too print-centric; vast array of options distracts from core experience of authoring text; Google Docs, Slides, Sheets, Hangouts all exist in separate Google silos.
• BrigadeHub - Project of c4sf.

• Switching costs (not financial or data migration costs but habit costs)
• May alienate developer community that uses Slack for 18 different teams
• Lack of integrations for other alternatives
• Getting people to use alternatives; Slack withdrawal syndrome; no current tapering drug.
• More TK

TK