Re:Why kernel development still uses email
by michaelt on Sunday October 02, 2016 @08:15AM
(#12622018)
Unfortunately, slack doesn't allow you to block users - not even bots or webhooks. And even if you have expansions turned off, they're still there in collapsed form.
So if you're not an administrator, and some genius has set up a bot that posts a cute puppy every time a message includes /pup, and it triggers practically every line in a discussion about puppet, slack doesn't give you the option to do anything.
Well, apart from "complain to your boss and ask him to stop your co-workers' fun". As a professional, I don't want to be wasting my boss's time with trivial shit I ought to be able to fix myself.
This is what greasemonkey and similar is for. It shouldn't be necessary, but sometimes it is.
You might even be able to do it with some custom user-side CSS.
I don't get how your pup situation doesn't get solved with a conversation with a co-worker.
Re:Why kernel development still uses email
by parennoob on Sunday October 02, 2016 @09:52AM
(#12622317)
I do. Do you want to really be "that guy" who hates puppies (and is ribbed about it all the time)? Software development teams often have all the maturity of a clique of middle schoolers; and exclusion can be just as harsh.
Re:Why kernel development still uses email
by aisofteng on Sunday October 02, 2016 @07:09PM
(#12624751)
I'd say that people that don't have the maturity to raise a legimitimate work issue with their coworkers are more likely the immature ones.
I have been and continue to be "that guy" who says "this is interfering with work, let's fix it", instead of that guy who doesn't say anything and instead just complains anonymously on social media. It works better this way.
We have a #{{projcet}}-dev channel for talk and #{{project}}-admin for JIRA/Github/etc. Also, in Slack you can have it auto-close all expansions. You choose the Gifs you wanna see.