Restrict guilds from being used a mutual for private messages

[Jupith]

Just now as long as you have 1 mutual with a user you can send then private messages, this discussion purposes that a restricted property be added to guilds, false by default but the ability to set it to true. This would exclude the guild from being used when the API is calculating if a message can be sent. This would be handy for bots that detect raids, as everyone knows spam/phishing has been majorly on the rise recently, allowing bots to temporarily restrict dms while they work through banning the accounts from a raid would help combat the problem just a little bit more, and improve user saftey.

[Jupith]

As for concerns on how this might affect other bots on the server attempting to message users legitimately, a new error code could be added, indiciting in this specific circumstance why the message could not be delivered, this would allow for bots to wait for a guild update event and once the restricted property has been set back to false, they can continue on as normal.

EDIT: marking as answered, jake said they probs wont do this as the proper way is to stop the spam

[Jupith]

The new error code would also double as a way for clients to render a new message from clyde, indicating why they have a mutual but cannot message the user, as i'm sure this could bring up a lot of confusion.

[prryplatypus]

Could even make it a new permission like “can start DMs”. That way you could, for example, allow mods/admins to message members, but not others.

[prryplatypus]

I used to moderate a mental health community, and a permission like this would’ve made our lives much, much easier, as we always wanted to keep conversations moderated, and being able to restrict members from opening DMs with others (at least when they only shared that common guild) due to the vulnerable state most people in the server were in would’ve really been useful.

[effen1337]

This would be handy for bots that detect raids

It indeed would.

As for concerns on how this might affect other bots on the server attempting to message users legitimately

I think this should be bypassable by bot accounts, if a bot made it into your server and it started mass dming people, you have a bigger problem (related to the person that added it in the first place and the dangerous perms they have to do bigger damage)

The new error code would also double as a way for clients to render a new message from clyde, indicating why they have a mutual but cannot message the user, as i'm sure this could bring up a lot of confusion.

Yeah I think that's all it takes to inform genuine members trying to dm other guild members.

I don't think there should be an additional perm for this, MANAGE_GUILD does the trick

[Jupith]

Bots bypassing it would eliminate alot of the potential side affects of this implementation. 👍

[Jupith]

A permission ontop of the property, otherwise it gets spammy with the amount of requests your having to make just to block some userbots from messaging

[Jupith]

If only the permission existed, and you wanted to restrict your the dms sent via your server, youd have to filter through every single role, instead you make restricted > true, and your mods/bots already have the send direct messages permission anyway so no further action is needed there.