Slack is good, notifications are bad, and this is a rant.
This post reads to me as another snowflake in the very justified avalanche of "Internet is drowning me in pointless chatter" complaints that define our time.
I use Slack this way with my team and it works wonderfully for me:
- I disable all notifications
- I tell people to PM me if they need me to act
- I tell people to carry on discussion in the relevant project/topic channel if they need to chat about said project/topic
These points are ordered by importance. The first is vastly more important than the others and extends beyond Slack. I aggressively disable notifications of all kinds from all things. If I can't disable them I at least disable their ability to make sound or vibrate. I have one way to be immediately "notified" and that is to call my mobile. I can count the people who know and use that number on one hand. They're so close to me that they know if I truly need to be informed of something now - in their respective sphere of family, friends, or work - and they call me and I pick up.
The PMs I read and act on when it's my Slacking time. I open up Slack and crank through them. Slacking time happens one or more times a day depending on my bandwidth.
The other channels I read if and only if I have a justified need to know what's going on with that project/topic. Or if I have downtime and am curious about something. Grazing on info about what my team is up to in project X is a nicer distraction than watching TV.
I am also that crazy guy who actually uninstalled Facebook from his phone and just goes to the website when he feels like catching up with friends. So I'm not subject to that megacorp's constant interruptions either. I don't feel like my life has lost anything at all by doing this.
The problem isn't Slack, it isn't Facebook, it's notifications, turn them off and tell the world that if they want your attention they have to call you and they can't have your number unless you love them.
> The PMs I read and act on when it's my Slacking time. I open up Slack and crank through them. Slacking time happens one or more times a day depending on my bandwidth.
At this point it sounds like slack is now just email at which point I question the value it is adding. Assuming everyone else does the same things in the same way you'll never have a responsive conversation over slack like this and may as well skip it entirely.
Couldn't have said it better myself. Disabling notifications (sometimes I go as far as disabling the red "1" bubble on messaging services) has been the best productivity boost.
Turnig off notificwtions wouldn't solve it for me. With email I read through what others thought was important enough to include me. Even on mailing lists I can mute threads I'm not interested in
With slack I have to read everything. It's like having to read through not just my inbox but also everyone else's inbox and on top of that no way to mute threads period. Sure I can not follow a channel. That equivalent to a unsubscribing from a mailing list. But, like I said above, a mailing list has threads so I can mute or ignore any threads I'm not interested in. With slack I have to read it all
Totally relate. I deleted Twitter from my phone and just use it either through the browser on my phone or whenever I have a moment to open Tweetdeck. My issue was notifications and the ENDLESS scroll - https://medium.com/@kavbojka/how-i-made-twitter-manageable-f...
I cannot recommend using Slack via a browser enough. It achieves several goals:
1. It sandboxes resource usage, preventing Slack from being a permanent resource hog. Is your Slack tab running hot on Chrome? Just kill it for now. There are many browser extensions for managing resource usage per tab.
2. Closing the Slack browser tab means no disruptive notifications. Sure, you can snooze Slack @-mentions, etc., but that's too much of "working hard to make the tool work."
3. Better workflow (seriously) Perhaps this is just me (or my function as a marketing person at a startup), but I work almost entirely inside the browser (GMail, Google Docs, various sites for research, SaaS apps). Using Slack as a standalone desktop app means I have to focus away from the browser. Using Slack as a browser tab means I can treat it just one of several web apps I use regularly.
4. Bonus point: No need to update your Slack client =)
I use slack in irssi. I think I actually get better benefits.
1. irssi is ridiculously low resource usage. It never melts down.
2. No notifications by default. I actually have a script that gives me notifications. It's quite cool because I filter the messages by regexp so that I only see what I want to see. Also, it uses my normal desktop notifications which means that they show up where I want them to, with the right font, in the right colour, lasting for the time I want them to. One tip: my default notifications do not stay up long enough to read them. It just gives me an indication that people are talking. I can notice a word or two and if it strikes my interest I can go to irssi and see what they are talking about.
3. I'm a programmer, so I'm always in my console. Same sauce, different flavour ;-)
I occasionally use slack from the browser because it has some features which are useful (like showing images), but I do that only on demand.
One of the things that is useful is that the people who like using slack on my team also have a lot of experience with IRC. They have good etiquette. Chatter is kept in the right channels so that it can be ignored easily. Work channels are about work and have a really high signal to noise ratio. Some teams are so good at it that if I want to get an overview of what's going on in their project I can simply subscribe to their slack channel. It's great for me since I work remote.
It just baffles me how many apps that would have been fundamentally doable on a 486 with Windows 3.1 and 14.4 dial-up somehow manage to gulp resources on modern machines.
(Although, for 1 and 2, it seems like temporarily closing the Slack app would work just as well.)
Besides, isn't the desktop app mostly just the browser app itself running inside the Electron framework? I haven't noticed any critical features it offers on top of the web app.
He didn't mention one of my pet peeves: the "stratoscope, robertheaton, and dang are typing" messages below the input window. They draw you in to watching... nothing! I sit there slack-jawed (pun unintended, but I'll take credit for it anyway) waiting to see what - if anything - will eventually show up.
Even on #random. It seemed like such a good idea at the time - keep "water cooler" chat out of the main channels. But what really happens is that all the fun stuff goes on in #random, so you pay as much or more attention to it as anything else. Who wants to be late for the party?
And there's the uncapitalized, unpunctuated, line-by-line stream of consciousness writing style I ranted about some time ago:
Another is that they just started putting light-grey text "Message @channel" by default in the text area. I am surprisingly stressed out by this. It feels like a command or a nudge that insinuates itself into my thinking space, like a half-finished message which a corporate entity 'helpfully' began for me, and now it's my job to finish it, and as soon as I finish that one another will begin. There's a bad dream in there somewhere...
I think the OP is right that a UI needs to be sensitive to the user's psyche and not push them all the time toward using the product.
In gaming, they call this "humane design," techniques like giving players an obvious place to take a break. By contrast, things like the infinitely-scrolling news feed and the autoplay video queue are grossly inhumane; they serve to obfuscate the fact that there's a decision point there, subtly trying to make the choice for you even if you might have wanted to do something else if you had thought about it. And of course it works, that's why everyone does it.
I am probably getting old. Having used irc as main communication channel for 8 years in a previous company, we now added slack on top of the mail and direct messenger methods at my new workplace. I can not get used to it, at all. It is nothing but a distraction of half wit and delayed misunderstandings. I even dislike the ui. May be the staff is not ready, maybe just give it a little time. Maybe I just got too used to email
If you dislike Slack, have you seen Skype for Business? Its text chat function disproves the existence of Cthulhu, since something so mind-bendingly horrible would surely have awoken Him, if He existed. Imagine sending your colleagues single-line Word documents and you're basically there.
You're not old! I'm 22 and still love IRC. I don't mind Slack for work but I do strongly dislike when open source organizations use it. It's really awkward to have to get invited and sign in to everything when you just need some quick help. Also, Slacks with a sizable amount of users are super slow for me.
Even when running IRC in the browser with IRCCloud it's snappy.
I think of Slack as "IRC for yuppies". Seen this way, it makes sense. It doesn't have the low-level features of IRC, but it follows you around easily, when juggling multiple clients. For that, it's pretty good.
I don't love it, I don't hate it. It works, kinda. It's loud and attention-grabby, for sure.
If you used WeeChat as your IRC client, I have been using this wee-slack script (authored by a Slack employee) and it has been phenomenally good: https://github.com/rawdigits/wee-slack.
While the tone of the article is maybe a little hyperbolic, I agree with a lot of it. The default setting to be alerted when absolutely anything happens is crazy. And whenever I see someone talking about Slack replacing e-mail as if it's a good thing, I recoil in horror. You can answer e-mails at your own pace, while Slack prioritises instant replies.
I have to disagree. The problem with email is the signal to noise ratio is too high, because it is globally accessible. Where as Slack is company only. Some things need to be addressed now. With email that would be turning on notifications, but then you get notifications for spam. Slack doesn't have the spam problem. The closest it gets is messages from computers. Those can be controlled or segregated to certain channels.
Honestly, this is not my experience using Slack at all. Maybe it's because I'm on such a small team, but I find that the amount of chatter on Slack isn't overwhelming at all -- #random is pretty dead most of the time. And if someone sends me a message and I'm busy, then I'll maybe glance at the notification but probably just ignore it until I'm free.
My team uses Slack very asynchronously -- whenever you have something that needs feedback or whatever, you just post it in the appropriate channel, and expect responses to trickle in over maybe the next 24 hours. If someone sends "hey no rush but", then I legitimately do not rush to answer it -- just a different company culture I guess.
Since slack people will pass by here. Please, if i set not disturb then don't disturb me: no notification, no badge icon (!!), nothing! (maybe just when the people, after been warned that they may disturb still send the notification). then when i remove the not disturb your nice slackbot can tell me what i missed.
Why am I asking so? beacuse I use pomodoro and i've a script that sets slack to "do not disturb" when i'm in the pomodoro and switch it off (to the pls bother me mood) when i'm done.
Less can certainly be more. However I feel like Slack's usefulness:distraction ratio change greatly depending on the type of team or company using it. These suggestions are good ones but every situation is different. Is your team disciplined, focused, and/or collaborative and to what degree? The answer will tell you how Slack may get used or abused.
I dunno. I'm in like 3 slack teams and dozens of channels and I maybe spend an hour in the morning catching up with everything, then I glance at it a few times a day during builds and such. Every once in a while it'll suck up half my day, but I rarely think of it as wasted time.
I learn a lot in slack and we have a big company, so I feel like helping people out with stuff during the day raises your profile. I'm kind of a python dabbler, but now I have people asking me directly about stuff because I'm 'the python expert' since I answer questions in the python channel a few times a week.
Doing my own work is obviously important, but I think helping other people get work done is important as well.
Just this week I introduced a guy on a totally different team to cloudformation, and in the process learned quite a bit about how they were using elastic map reduce, something we've never touched on our side of the company. He learned something, I learned something and I think the company as a whole benefits (even though I probably delayed my own work by a little bit)
It's really good at blowing up silos if you're a large-ish company. The difference in how connected I feel to the rest of the company is night and day since we switched to slack.
Yeah before Slack I was constantly getting interrupted with questions that could have been answered any time and random co-workers just wanting to chat. However, I agree with the analysis that Slack is good for immediate communication and communication that doesn't really matter too much. Before Slack we didn't really have a tool that fit that and so every communication was a co-worker walking over and interrupting whatever you were doing.
I'm not a fan of Slack. I think it's way more distracting than useful. The biggest problem I think is that it doesn't really allow for async communication. If I have a question that I want to ask someone, but it's not urgent, there isn't really a way to do it. With the typical gmail setup, I have 2 options. Send an email for non-urgent. Or send a hangout message for urgent. Slack really needs something like this, a sort of silent direct message that doesn't disrupt the recipient.
Also, I hate the <person> joined / left messages. There are team-related channels that are so disruptive and useless that I'd like to silently leave without being judged, but I can't.
Lastly, I've yet to be in a channel that isn't overrun by giphy spam. I know this isn't directly Slack's fault and more a company culture issue, but Slack sure makes it easy to use distracting features, whether that's integrations like giphy, or reactions to messages, etc. I think the focus needs to be less on making Slack 'fun' to use, and more on improving communication.
I wrote an electron app to inject javascript and CSS into slack in an attempt to turn off a lot of distraction and, more importantly, easily differentiate between bots and people. I feel the author's pain, but the great part about being a programmer is that if it's bad enough to write about, it's bad enough to fix.
It allows per-team customizations, and if anyone cares to mess with it, there's a link at https://github.com/bhuga/hackable-slack-client. OSX only, but it's electron, so porting it would probably be easy.
Changing other people's applications' behavior is challenging but rewarding. The hacks required make great stories for certain kinds of parties. I always point people to https://news.ycombinator.com/item?id=11805380 for a better introduction than I could give.
One thing that's not mentioned in the article that I see as one of the main drawbacks of slack is lack of threading, which makes it much harder to have an async. conversation (especially across timezones).
The very very weird part to me about this is that slack say they've been working on threading for at least 18 months now (https://twitter.com/SlackHQ/status/535121236452732928) and still can't provide a timeline for when it'll go live, which seems really odd for such a well funded development team, given it's such an oft-requested piece of functionality (there's even a twitter account dedicated to it https://twitter.com/slackThreadsYet )
Is everyone forgetting the biggest benefit of Slack? It's the transparency part. Important details are no longer privy to 1 or 2 individuals on the team in their inboxes instead the whole team can see what's going on and can chime in if they disagree
If someone didn't make a new channel to discuss the idea more , and you missed the single line of text that mentioned it two hours ago.
If you happen to be looking at the right channel at the right time.
If the pertinent bits aren't lost in back scroll.
I think your statement is true for a sufficiently small company with a limited number of channels. Less so for larger companies, or even small ones with dozens or hundreds of them.
> Important details are no longer privy to 1 or 2 individuals on the team
Sure they are, they just split-off into direct messages between themselves and return to the main channel to present the result of their discussion. Or don't even do that.
Information-hoarding needs a cultural fix, not a technical solution. In my experience it usually occurs in companies with a blame-culture, so people confide between themselves and keep some information undisclosed as 'insurance'.
Is there any way to turn off those "motivational" start up messages such as "we like you"? It always irritates me; I want to use Slack for work not for getting the feel I am in a kindergarten and "special".
You can replace them, so assumedly you could replace the "motivational" messages with things such as "Work harder" or "You are not special" or "You are an easily replaceable cog".
My main issue with Slack is that with sane-ish notification defaults (only for my name), group direct messages default to that as well.
They're fundamentally perceived by everyone (in my experience) as an extension of individual direct messages, which do trigger notifications, and yet I find myself missing these for minutes/hours at a time, sometimes when it's important, all because I've finally trained myself to ignore the non-numeric notification badge.
I've contacted the support about this and was basically told to go away. :/
I'm on a small team (14-15) and honestly I love Slack. Have never had any issues with it and I think it's an awesome team messaging system. We use growbot to give props and get a kick out of it. We just switched from skype to slack calls and it was a gamechanger. I have been on teams that used GroupMe in the past and it was terrible. I don't read group me messages because they're off topic and annoying. Slack's channel system changed that for me.
Muting a channel doesn't prevent it from showing unread message indicators when your coworkers use @here and @channel indiscriminately. This is probably my current biggest pet peeve with Slack, an app that I otherwise love (at least more than some other alternatives we've tried).
Unfortunately it didn't get the traction that I wanted. This is OK, the main purpose of the kickstarter was 'market/idea validation' to see if enough people were dissatisfied with Slack's resource usage/performance to justify building it.
If enough people here are interested though, i'd be willing to resurrect the project - please let me know.
[+] [-] apatters|9 years ago|reply
This post reads to me as another snowflake in the very justified avalanche of "Internet is drowning me in pointless chatter" complaints that define our time.
I use Slack this way with my team and it works wonderfully for me:
- I disable all notifications
- I tell people to PM me if they need me to act
- I tell people to carry on discussion in the relevant project/topic channel if they need to chat about said project/topic
These points are ordered by importance. The first is vastly more important than the others and extends beyond Slack. I aggressively disable notifications of all kinds from all things. If I can't disable them I at least disable their ability to make sound or vibrate. I have one way to be immediately "notified" and that is to call my mobile. I can count the people who know and use that number on one hand. They're so close to me that they know if I truly need to be informed of something now - in their respective sphere of family, friends, or work - and they call me and I pick up.
The PMs I read and act on when it's my Slacking time. I open up Slack and crank through them. Slacking time happens one or more times a day depending on my bandwidth.
The other channels I read if and only if I have a justified need to know what's going on with that project/topic. Or if I have downtime and am curious about something. Grazing on info about what my team is up to in project X is a nicer distraction than watching TV.
I am also that crazy guy who actually uninstalled Facebook from his phone and just goes to the website when he feels like catching up with friends. So I'm not subject to that megacorp's constant interruptions either. I don't feel like my life has lost anything at all by doing this.
The problem isn't Slack, it isn't Facebook, it's notifications, turn them off and tell the world that if they want your attention they have to call you and they can't have your number unless you love them.
[+] [-] Ntrails|9 years ago|reply
At this point it sounds like slack is now just email at which point I question the value it is adding. Assuming everyone else does the same things in the same way you'll never have a responsive conversation over slack like this and may as well skip it entirely.
[+] [-] sotojuan|9 years ago|reply
[+] [-] swampthinker|9 years ago|reply
[+] [-] greggman|9 years ago|reply
With slack I have to read everything. It's like having to read through not just my inbox but also everyone else's inbox and on top of that no way to mute threads period. Sure I can not follow a channel. That equivalent to a unsubscribing from a mailing list. But, like I said above, a mailing list has threads so I can mute or ignore any threads I'm not interested in. With slack I have to read it all
[+] [-] Brajeshwar|9 years ago|reply
[+] [-] kavbojka|9 years ago|reply
[+] [-] ktamura|9 years ago|reply
1. It sandboxes resource usage, preventing Slack from being a permanent resource hog. Is your Slack tab running hot on Chrome? Just kill it for now. There are many browser extensions for managing resource usage per tab.
2. Closing the Slack browser tab means no disruptive notifications. Sure, you can snooze Slack @-mentions, etc., but that's too much of "working hard to make the tool work."
3. Better workflow (seriously) Perhaps this is just me (or my function as a marketing person at a startup), but I work almost entirely inside the browser (GMail, Google Docs, various sites for research, SaaS apps). Using Slack as a standalone desktop app means I have to focus away from the browser. Using Slack as a browser tab means I can treat it just one of several web apps I use regularly.
4. Bonus point: No need to update your Slack client =)
[+] [-] mikekchar|9 years ago|reply
1. irssi is ridiculously low resource usage. It never melts down.
2. No notifications by default. I actually have a script that gives me notifications. It's quite cool because I filter the messages by regexp so that I only see what I want to see. Also, it uses my normal desktop notifications which means that they show up where I want them to, with the right font, in the right colour, lasting for the time I want them to. One tip: my default notifications do not stay up long enough to read them. It just gives me an indication that people are talking. I can notice a word or two and if it strikes my interest I can go to irssi and see what they are talking about.
3. I'm a programmer, so I'm always in my console. Same sauce, different flavour ;-)
I occasionally use slack from the browser because it has some features which are useful (like showing images), but I do that only on demand.
One of the things that is useful is that the people who like using slack on my team also have a lot of experience with IRC. They have good etiquette. Chatter is kept in the right channels so that it can be ignored easily. Work channels are about work and have a really high signal to noise ratio. Some teams are so good at it that if I want to get an overview of what's going on in their project I can simply subscribe to their slack channel. It's great for me since I work remote.
[+] [-] PhasmaFelis|9 years ago|reply
(Although, for 1 and 2, it seems like temporarily closing the Slack app would work just as well.)
[+] [-] maw|9 years ago|reply
Any clues on what to google for? I've tried the Great Suspender and wasn't very impressed.
[+] [-] enraged_camel|9 years ago|reply
[+] [-] joelthelion|9 years ago|reply
[+] [-] Stratoscope|9 years ago|reply
Even on #random. It seemed like such a good idea at the time - keep "water cooler" chat out of the main channels. But what really happens is that all the fun stuff goes on in #random, so you pay as much or more attention to it as anything else. Who wants to be late for the party?
And there's the uncapitalized, unpunctuated, line-by-line stream of consciousness writing style I ranted about some time ago:
https://news.ycombinator.com/item?id=11239614
[+] [-] dang|9 years ago|reply
I think the OP is right that a UI needs to be sensitive to the user's psyche and not push them all the time toward using the product.
[+] [-] AngrySkillzz|9 years ago|reply
[+] [-] erickhill|9 years ago|reply
[+] [-] firewalkwithme|9 years ago|reply
[+] [-] tormeh|9 years ago|reply
[+] [-] sotojuan|9 years ago|reply
Even when running IRC in the browser with IRCCloud it's snappy.
[+] [-] Florin_Andrei|9 years ago|reply
I think of Slack as "IRC for yuppies". Seen this way, it makes sense. It doesn't have the low-level features of IRC, but it follows you around easily, when juggling multiple clients. For that, it's pretty good.
I don't love it, I don't hate it. It works, kinda. It's loud and attention-grabby, for sure.
[+] [-] nicksergeant|9 years ago|reply
[+] [-] chris11|9 years ago|reply
[+] [-] titanomachy|9 years ago|reply
[+] [-] untog|9 years ago|reply
[+] [-] edgan|9 years ago|reply
[+] [-] matwood|9 years ago|reply
[+] [-] r00fus|9 years ago|reply
What I do is simply mute the chatty channels, and go in when I need answers or get invited/DM'd.
Mute is pretty powerful.
[+] [-] ozten|9 years ago|reply
I'd strongly suggest building a culture that Email and Slack are Asynchronous.
If something is time sensitive, take it to a synchronous channel which has cultural expectations that it is okay to interrupt the other person.
[+] [-] hayleox|9 years ago|reply
My team uses Slack very asynchronously -- whenever you have something that needs feedback or whatever, you just post it in the appropriate channel, and expect responses to trickle in over maybe the next 24 hours. If someone sends "hey no rush but", then I legitimately do not rush to answer it -- just a different company culture I guess.
[+] [-] esseti|9 years ago|reply
Why am I asking so? beacuse I use pomodoro and i've a script that sets slack to "do not disturb" when i'm in the pomodoro and switch it off (to the pls bother me mood) when i'm done.
[+] [-] mmjjss|9 years ago|reply
[+] [-] sotojuan|9 years ago|reply
[+] [-] empath75|9 years ago|reply
I learn a lot in slack and we have a big company, so I feel like helping people out with stuff during the day raises your profile. I'm kind of a python dabbler, but now I have people asking me directly about stuff because I'm 'the python expert' since I answer questions in the python channel a few times a week.
Doing my own work is obviously important, but I think helping other people get work done is important as well.
Just this week I introduced a guy on a totally different team to cloudformation, and in the process learned quite a bit about how they were using elastic map reduce, something we've never touched on our side of the company. He learned something, I learned something and I think the company as a whole benefits (even though I probably delayed my own work by a little bit)
It's really good at blowing up silos if you're a large-ish company. The difference in how connected I feel to the rest of the company is night and day since we switched to slack.
[+] [-] a300600st|9 years ago|reply
[+] [-] z6|9 years ago|reply
Also, I hate the <person> joined / left messages. There are team-related channels that are so disruptive and useless that I'd like to silently leave without being judged, but I can't.
Lastly, I've yet to be in a channel that isn't overrun by giphy spam. I know this isn't directly Slack's fault and more a company culture issue, but Slack sure makes it easy to use distracting features, whether that's integrations like giphy, or reactions to messages, etc. I think the focus needs to be less on making Slack 'fun' to use, and more on improving communication.
[+] [-] bhuga|9 years ago|reply
It allows per-team customizations, and if anyone cares to mess with it, there's a link at https://github.com/bhuga/hackable-slack-client. OSX only, but it's electron, so porting it would probably be easy.
Changing other people's applications' behavior is challenging but rewarding. The hacks required make great stories for certain kinds of parties. I always point people to https://news.ycombinator.com/item?id=11805380 for a better introduction than I could give.
[+] [-] raesene9|9 years ago|reply
The very very weird part to me about this is that slack say they've been working on threading for at least 18 months now (https://twitter.com/SlackHQ/status/535121236452732928) and still can't provide a timeline for when it'll go live, which seems really odd for such a well funded development team, given it's such an oft-requested piece of functionality (there's even a twitter account dedicated to it https://twitter.com/slackThreadsYet )
[+] [-] perseusprime11|9 years ago|reply
[+] [-] GrinningFool|9 years ago|reply
If someone didn't make a new channel to discuss the idea more , and you missed the single line of text that mentioned it two hours ago.
If you happen to be looking at the right channel at the right time.
If the pertinent bits aren't lost in back scroll.
I think your statement is true for a sufficiently small company with a limited number of channels. Less so for larger companies, or even small ones with dozens or hundreds of them.
[+] [-] dingaling|9 years ago|reply
Sure they are, they just split-off into direct messages between themselves and return to the main channel to present the result of their discussion. Or don't even do that.
Information-hoarding needs a cultural fix, not a technical solution. In my experience it usually occurs in companies with a blame-culture, so people confide between themselves and keep some information undisclosed as 'insurance'.
[+] [-] bitL|9 years ago|reply
[+] [-] jordanrobinson|9 years ago|reply
[+] [-] welder|9 years ago|reply
http://meetfranz.com/
[+] [-] nkantar|9 years ago|reply
They're fundamentally perceived by everyone (in my experience) as an extension of individual direct messages, which do trigger notifications, and yet I find myself missing these for minutes/hours at a time, sometimes when it's important, all because I've finally trained myself to ignore the non-numeric notification badge.
I've contacted the support about this and was basically told to go away. :/
[+] [-] Hexigonz|9 years ago|reply
[+] [-] ihuman|9 years ago|reply
[+] [-] iza|9 years ago|reply
https://get.slack.help/hc/en-us/articles/204411433-Muting-a-...
[+] [-] ilyanep|9 years ago|reply
[+] [-] chubs|9 years ago|reply
Unfortunately it didn't get the traction that I wanted. This is OK, the main purpose of the kickstarter was 'market/idea validation' to see if enough people were dissatisfied with Slack's resource usage/performance to justify building it.
If enough people here are interested though, i'd be willing to resurrect the project - please let me know.