Make Community Developer not pingable

[jb3]

Looking through recent pings for Community Developer I can confirm that non of them are worth the ping.

It's been made clear that the reason the role is pingable is in the event of an emergency, but I can see no serious usage of the role ping.

I propose that we make the Community Developer role not pingable because so far all it has been used for is spam and ping abuse. Instead, to get the attention of the developers, an @everyone ping should be used in the #developer-general channel.

[jb3]

another one to add the collection

[jb3]

I agree

[alfiejfs]

Even as a non community developer, I see the issue here and agree. The excuse for the role being kept (as said in the post) was because it might be an emergency, but you can just ping all in the developer channels.

Remove the ability to ping.

[maishams]

iF yOu'Re sO triGgeRed jUst lEavE thE seRveR

[fractalpenguin]

I approve this proposal.

[picapi]

I am in agreement that as of late the mention has been misused, and that some changes are likely in order, although I feel that having the ability to contact all Community Devs is important. The suggested solution works well when staff are present, but there may be a scenario where a user needs to contact devs urgently, and no staff are available to pass on the message at the time, in which case we should probably have a failsafe in place

A possible solution which would maintain the functionality while likely reducing the abuse of it would be to apply a similar philosophy as we do for Official Staff mentions, where the bot asks if the user is absolutely sure they wish to execute the mention - and sanctions can then clearly be given for improper use, given that a fair warning is attached before the mention is executed.

[jb3]

I'd be in favour of a solution like that, and having guild-wide rate limits so it can only be done once per hour or whatever.

In the short term however, I feel it is probably best to disable the mentioning of the role.

[ThisIs0xBC]

What the frick, all I wanted was the JS to show how many exams you had left on essentials, and I knew that one of the community devs made the code, just couldn't remember who.

[jerbob]

I'm in agreement with @picapi here, it doesn't seem too difficult to implement this since we're already doing it for Cyber Discovery Staff. If someone wants to make a PR for this, we just need @thebeanogamer to make a fake Comm. Dev role and post the corresponding Role IDs.

[jb3]

cc @CyberDiscovery/server-admin-team

[thebeanogamer]

I mean, it's doable.

[thebeanogamer]

I question if it's needed though, I've never seen it be used legitimately.

[REDACTED-REDACTED]

I can't see that a situation would ever arise that needs the urgent attention of all com devs not like our services run peoples life support or anything. The easiest solution is to make it non pingable but for what ever reason you lot never do anything simply. So the second easiest solution is to have two identical roles one which can be pinged and a second that can't then just let com devs opt in or out. but realistically just make it none taggable.

[thebeanogamer]

And on a related note, we should probably add the ability for people to be blocked from staff tags.

[jb3]

Either way, the issue is that community developer is pingable and it probably shouldn't be.

On an unrelated note, maybe we should add rate limits for official staff tags.

[jb3]

Also please can we just disable comm dev pings now thanks.

[jb3]

@teamshortcut Considering you just muted me for raising the issue, I'd advise you to take a read of the comments on this issue.

[jerbob]

@teamshortcut Considering you just muted me for raising the issue, I'd advise you to take a read of the comments on this issue.

[teamshortcut]

We've had cases previously where there was legitimate use for pinging Community Developers, but as the size of the server has grown, I'm open to accept that it may not be a brilliant idea to keep the current system. I would be more in favour of a system similar to the Official Staff one, as it would hopefully deter trolls from actually pinging, while retaining the ability to ping if actually needed. However, if enough were in favour please hold while we implement new suggestions system for voting I'd be happy to disable it as pingable; as @jos-b rightly points out, in many cases an @ everyone in #developer-general would accomplish most of the same effect in many cases.

[jerbob]

Besides our server growth (which is fairly sub-standard), not all Community Developers are working on the same project. The only "legitimate" use for pinging Community Developers that comes to mind is if the bot dies, and even then people who work solely on the website would be pinged unnecessarily. With an @everyone in #developer-general, we'd still be pinging some staff members who are largely inactive.

Most of our community developers aren't actively working on any of our projects, so in most cases we can just ping people individually.

[thebeanogamer]

I'd be inclined to agree with @teamshortcut.

[jerbob]

I'd be inclined to agree with @jos-b.

[jb3]

I'd be inclined to agree with @AnonGuy

[REDACTED-REDACTED]

I'd be inclined to agree with @AnonGuy

[jb3]

I'd be inclined to agree with @REDACTED-REDACTED.

[jerbob]

I'd be inclined to agree with @jos-b.

[REDACTED-REDACTED]

I'd be inclined to agree with @AnonGuy .

[jb3]

I'd be inclined to agree with @AnonGuy.

[jerbob]

I'd like to hear @joker314's viewpoint on this issue.

[REDACTED-REDACTED]

All the pointless pings and emails have just made me think. Me, George and Joe were the first com devs and to the best of my recollection not one ping I got has ever been relevant to me 😆 plz fix all you have to do is literally toggle a slider.

[thebeanogamer]

Are you happy now?

[REDACTED-REDACTED]

Yes @jos-b @AnonGuy well played boys

[jerbob]

Good job team

[jb3]

Well done lads, another win.