3 ms·
And heaven forbid somebody typed "Good morning, @channel" (which happened 20 times per morning per timezone), because then you'd get the dreaded Red Exclamation
by onion2k 9y ago
And heaven forbid somebody typed "Good morning, @channel" (which happened 20 times per morning per timezone), because then you'd get the dreaded Red Exclamation Mark in the tab.
That isn't a problem with Slack. That's a problem with the way people are using Slack. If the only workable fix is to use a different tool you have a far bigger problem at your company.
I can't fathom how anybody would have been able to work if they had gone as far as allowing notifications to be turned on and make noises at them every time Slack thought something Important Enough To Interrupt You had happened.
All the notifications and noises can be switched off, and the @channel and @here notifications can be ignored on a per channel basis.
- jasonkester 9y agoAll the notifications and noises can be switched off, and the @channel and @here notifications can be ignored on a per channel basis. Sounds like a feature that was added in the last 18 months since I last used it. At the time, your options were "every notification about everything, ever" or "no 'notifications' ever, but we'll still helpfully flash the favicon at you all day". Glad to see there is at least a tiny drip of sanity making its way into the product.
- wpietri 9y ago> That isn't a problem with Slack. That's a problem with the way people are using Slack. The notion that tools exist in some sort of vacuum away from users baffles me. Since Slack's only purpose is talking with other people, I don't how one can even theoretically evaluate it separate from usage. This is a very common thing that happens with Slack. If it were just one team struggling to use it well, you might have a point. But past a certain size, I've only ever seen Slacks that a) have a problem with @channel, or b) have a carefully developed and enforced culture of controlling use of @channel. I think the sophisticated version of this argument is "only experts should use use complex/difficult/dangerous tools". Which is a reasonable argument when talking about, say, wiring up detonators. But Slack's purpose is to connect everybody in a company. Suggesting that Slack is only for experts is to limit its market to a very small segment.
- onion2k 9y agoImagine your company has a mailing list that goes to everyone (it probably does; most organisations do). In a small company it's fine for anyone to send to it but it's quite annoying and unnecessary so the use of it is discouraged by company culture. As the organisation grows there's a point where the email administrator restricts who can send to it because it would be actively damaging to the email infrastructure if too many people used it, and it'd annoy a lot of people. Very few people abandon email because their organisation has a mailing list. Slack's @channel is exactly the same thing albeit on a smaller scale. If it gets too distracting just tell people not to use it so much.
- majewsky 9y agoI saw this at $work some years ago. Someone sent a mail to a weird mailinglist that I'd never seen before, which for some reason had 98,000 subscribers. Cue the "what is this list, please unsubscribe me" replies, which are of course sent to the mailinglist rather than the original poster. I don't know the innards of Exchange, but from what I've heard, when Exchange receives a mail for a mailinglist, it makes a copy in each recipient's mailbox. That small thread with maybe 30 "please unsubscribe me" replies brought down the entire company mail system for about half a day. (Well, it didn't really bring it down; it was just busy shuffling copies of mails around.)
- wpietri 9y agoSure. And email is circa 50 years old. At this point, given how distributed it is, it's basically impossible to change. It was not designed for the modern environment, so people have compensated with culture. Slack, however, is new, centrally controlled, relatively easy to change, and frequently updated. So the email analogy doesn't apply at all.
- s_kilk 9y ago> The notion that tools exist in some sort of vacuum away from users baffles me This x1000 Software is developed and used in a social context. We can't disavow responsibility for the effects our Software cause.