An overhaul to role mentioning

This is probably a combination of suggestions but I'm going to try and consolidate it into an idea for one whole overhaul. Lets start with...

Who can and cannot mention a role

An issue facing any large community is the disdain for @everyone and @here mentions. Typically, servers tend to avoid it by leaning towards an opt-in role that users can assign themselves through the use of a bot in order to receive notifications for certain pieces of information.

The issue with this solution at this time, is that in order for a staff member of a server to push a notification to that role, the role must be mentionable by everyone. This is obviously a problem because it takes one or two rogue elements to start spamming this role with irrelevant mentions while staff are unavailable, and suddenly you get people either leaving a server or removing the role.

How can this be corrected?

I have a few ideas on how this can be solved. Lets start with the "roles can/cant" approach.

We start by taking the "Notification Overrides" section from Notification Settings, and add it to the role permissions menu.. to clarify: Each role will have a section labeled "Roles that can mention this role.", and in that section, there's a dropdown menu that contains a list of roles on the server, including @everyone. Just below this dropdown box is a list of roles already defined, similar to what you see in the Notification Settings. From there, you can grant/deny/inherit permission to mention the role from the roles you listed.

Alternatively, we can take that idea and run it in reverse: Instead of listing roles that can mention the role you are editing, you can edit individual roles to specify what roles it can and cannot mention. I feel this might be more consistent with the way the permission system is already designed.

In addition, it may be worth specifying per-channel overrides. Perhaps you can specify in a channel if a certain role can be mentioned or not, and/or by whom.

Notifications from Role Mentions

There are a few issues with role mentions. In some scenarios, mentions from roles wont appear in your recent mentions, and its up to you to scroll through upwards of 100 messages to find where you were mentioned (or just ignore it and mark the channel as read). This is also a sign of another glaring issue where the fact a mention is always recorded but the content of the message is not, so one could theoretically @b1nzy, and then delete their message... and unless the server was logging deleted messages / the person being mentioned had access to audit logs / someone was watching at the time, nobody would know that the message even existed. As a matter of fact, years ago before Self-Bots were against the rules, I tried to develop a self-bot that would record all my incoming mentions to a file, and highlight messages that were deleted that also mentioned me or a role I was in. It never worked, but it proves this is an issue.

I think that the Notification Settings needs to be overhauled to allow people to decide which channels produce mobile push notifications (this is currently not a feature), and whether to suppress notifications for certain roles, even roles you do not currently have. In addition, mentions need to be erased from existence (ie the red notification and audio cue) should the message be deleted. Alternatively, allow recent mentions to show messages you have received that mentioned you, even if the message has been deleted by its author. (I'd probably lean in favor of the former personally).

Separate @everyone and @here

Both are really important mentions, but there are some edge cases where you want your entire server to be able to mention the entire server, but not mention people who aren't currently present. The current way to manage this is to have a bot that watches for status changes, applies a mentionable role to anyone who is online, and as soon as they go inactive/dnd, strip the role.

This would be easier if you could individually assign @everyone and @here permissions, instead of bundling them together as one. In addition to this, end users may wish to suppress @everyone but not @here, or vice versa. Ultimately this should be an option to the end user as well as admins.

Toggle mentionable abuse

Some servers may choose to use a bot to give everyone a role, knowing that some people choose to suppress @everyone and @here. Maybe it's just because they want a special role for everyone... doesn't matter why. What matters is that a rogue admin could theoretically mark a role as mentionable and then mention everyone in it, then unmark the role as mentionable.

I propose that once a role is marked as unmentionable (and mind you, only if the other parts of the overhaul are implemented), all mentions for that role become invalid and their notification is erased on client devices.

Viewers of this suggestion, please vote up if you agree with any part of my suggestion. I know this could be considered a duplicate for many other suggestions, but as this is proposing an entire overhaul to the way notifications are controlled, suppressed, and issued... I believe this post would serve a better purpose for discourse over the possible changes. And please, I encourage you all to comment on this post and provide your perspective on the matter. After all, the ideas of one hardly speak for an entire community unless the majority of that community speaks up too.