This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
- # admin-announcements (54)
- # announcements (1)
- # beginners (145)
- # boot (122)
- # cider (10)
- # cljs-dev (25)
- # cljsrn (20)
- # clojure (173)
- # clojure-art (4)
- # clojure-austria (1)
- # clojure-berlin (3)
- # clojure-germany (1)
- # clojure-nl (2)
- # clojure-russia (117)
- # clojure-switzerland (1)
- # clojure-uk (3)
- # clojurebridge (6)
- # clojurecup (36)
- # clojurescript (218)
- # clojurex (1)
- # core-typed (17)
- # cursive (23)
- # data-science (1)
- # datavis (2)
- # datomic (28)
- # emacs (3)
- # flambo (1)
- # hoplon (28)
- # ldnclj (19)
- # lein-figwheel (2)
- # leiningen (1)
- # luminus (1)
- # off-topic (1)
- # om (158)
- # portland-or (1)
- # re-frame (72)
- # reagent (48)
- # remote-jobs (1)
- # slack-help (7)
In the reagent and re-frame channels we sometimes want to ask a question of the channel. But this option is turned off by the clojurians admins. We can't use @ here or @ channel. Any chance this feature could be tuned back on? I realise, in theory, this feature can be abused, but is that much of a practical problem?
@mikethompson: imo at-channel should never be used. You disturb hundreds of people doing other things - it's not a paid support forum. If someone is available to answer, they'll see your question.
95% of the times it is used it is abused and definitely not for everyone in that channel
@oskarth: I disagree. There's a reason the feature exists. There are various usecases in various communities where it makes good sense.
For various libraries, when you want to ask a question of the entire user base, it seems like a very reasonable thing to do. There's a lot of noise in some of the channels, so people zone out. To get general attention, this is the perfect tool, when you are a library author/maintainer.
You asked, I explained what I think most people's position are. Try to understand the rationale instead of getting hostile because you can't command the attention of everyone at a whim.
Sorry, at this end it feels like I'm just matter of fact. I acknowledged the possible issues with @ channel and @ here in my original question.
It feels like if it was enabled before but currently disabled, the rationale behind why it was disabled must at least have some form of merit.
I won't make any assumptions here on out because I'm new to this community, but that's just what I'm seeing as an outsider
Yeah, could be. I'm just seeking clarity from the admins. If the concern is "fear of abuse" I would ask that it be reinstated. When it was turned on, I personally never saw any abuse. On the other hand, if there were indeed cases of abuse which lead to it being turned off, then turning it back on clearly won't be an option. I'm wondering which it is.
As I said before, it is a practical problem for anyone who has been on chats long enough. I'd estimate I've been at-channeled 20 times here, and the only time it has ever been relevant is in a private group of less than 10 people talking about organizing an event. It doesn't make any difference whose experience this is.
All those times it's either someone spamming what they think everyone should care about, or a beginner who is over anxious to get a reply to his question.
mikethompson: i'm also completely opposed to enabling that feature. this is not a paid support thing, you're not entitled to anyones reaction.
Thank you. Was beginning to regret replying with common sense. I'll pass the torch on to you, @hans ;)
So I was asking if there were real cases of that which had lead to the feature (which used to be on) getting turned off. Truely, I do understand the POTENTIAL problems. I am wondering if, within this smaller community, there had ACTUALLY been cases of it.
@mikethompson - i believe they had already been stating every day example of the abuse here
Eh... If you're looking for proof from the administration, I guess we'll have to wait for that.
this is not a dictatorship anyway. if "the admins" were to make stupid decisions, then this place would empty itself quickly.
Yay, a flamewar ❤️
And more seriosuly - I wouldn't have problem with
@channel (especially if it can be scoped to a group of people like maintainers or something) because it doesn't really pain me too much to open the tab, mark it as read and carry on as if nothing happened if it doesn't interest me. But I can understand the position of people that want to have it disabled, maybe they are more easily annoyed and disturbed and
@channel is of little value unless you're making an announcement or something. Also, I don't have a smartphone so I can just close the Slack tab and don't be bothered at all, it might be more annoying for people with Slack app hounding them when they're off.
I think I remember back when it was enabled someone used it to make announcements and people were non-plussed for some reason, so that might be your proof - it used to be enabled, people didn't like it, it was disabled.
If there has been annoying abuse, then I have no problem whatsoever with it being turned off. Its just that I've been in clojurians since the very beginning and I can't ever remember a problem in the 7 odd channels I follow. The clojure community seems to conduct itself pretty well. Hence my question (to admins please): has there actually been cases of abuse which caused the feature to be turned off OR was it simply fear of abuse which was caused the change on policy?
I am joined to many of the channels on here and have never seen an abuse of the wider at-mentions
that said, I am an admin on other Slack's and routinely restrict that feature to admins to head off that possibility
I haven’t had this issue on clojurians either. Maybe it is an issue in some of the channels I’m not subscribed to. In other slack rooms I’m subscribed too, normally this is brought up, and when people who abuse this feature are called out on it, they normally abide by the rules.
I also havent experienced any abuse, and, especially for library specific channels, these kinds of notifications can be really helpful when used sparesely. For example to have the user base aware a new release candidate is out and would appreciate feedback. I wouldn't view that kind of alert as abuse because it is a very targeted, and opt-in audience :)
Late to the "flamewar" — I’ll discuss with the other admins (I’m one) — but it’s worth pointing out that Slack is designed for (small) company teams where features like
@channel are much more reasonable and useful. If we could restrict the feature by channel, I’d be open to enabling it for those small channels that requested it but with ~4,000 people here, I’d rather keep those features off.
In some of the other eight Slacks to which I currently belong, I have seen abuse, usually by one or two individuals who believe it is their "right" to get attention whenever they want. Whilst such folks can easily be ejected, they’ve usually already annoyed the heck out of the thousands of people around the world whose phone lit up at 4am and woke them up!
To @mikethompson I’ll say: if you want control over those features and believe they would be useful to the Reagent / Re-Frame community, you would always start a free Slack for that community and see how that works out.
There’s no doubt that those features work best for small, focused teams that typically do need to get everyone’s attention. I’m in a Technical Advisory Group Slack for a product and they have those features enabled and use them sparingly.
@here on its own isn’t too bad since it only pings people who are "available" but
@channel hits everyone regardless of timezone / availability and that gets really annoying, really quickly in a larger channel.