Re:What Slack might learn from its Open Source alternative
by burke on Saturday August 27, 2016 @08:22AM
(#12372042)
We had this in flowdock before we switched to slack, on a team of probably 700 or so at the time. It made it far easier to filter out chatter when dealing with an urgent issue (no need to change rooms or remind people to be quiet for a while), and I haven't really noticed it encouraging pointless chatter. I seriously miss this feature in slack.
Re:What Slack might learn from its Open Source alternative
by educar on Saturday August 27, 2016 @03:04PM
(#12373674)
What was wrong with flowdock?
Re:What Slack might learn from its Open Source alternative
by burke on Sunday August 28, 2016 @08:19AM
(#12376215)
I'm not sure. I think with the benefit of hindsight, I liked it better on balance, but I wasn't involved in the decision. It was definitely a terrible resource hog, even more so than Slack, and the iOS client wasn't quite as polished IIRC.
Re:What Slack might learn from its Open Source alternative
by xfkechyk on Saturday August 27, 2016 @11:26AM
(#12372733)
that doesn't occur without threaded messaging? threaded messaging makes it easier to ignore those sub-discussions...
Re:What Slack might learn from its Open Source alternative
by coldtea on Sunday August 28, 2016 @03:11PM
(#12377967)
>that doesn't occur without threaded messaging?
The difference I mentioned wasn't one of occurring or not, but one of degree of occurrence.
>hreaded messaging makes it easier to ignore those sub-discussions...
Not as much as it makes it easier to start and digress into endless sub-discussions.
Then it would be a recipe for endless sub-discussions diverting from the topic, and disaster...