Create audit log entries for Discord's own NSFW rejects

[erkinalp]

Currently, NSFW rejects create no audit log entry, which makes hard for us to tell whether it is caused by Discord's own filters, or a moderation bot, applying the deletion. Hence, a new event type, MESSAGE_REJECTED, should be logged to the audit log every time an NSFW message is sent and removed by Discord's own filters.

[RedDaedalus]

When the NSFW filter triggers, no message is actually sent. The API fully blocks the request. Furthermore, logging an attempted action deviates from all other audit log entry types, and the NSFW filter has lots of issues with false positives.

[erkinalp]

the NSFW filter has lots of issues with false positives

That is the very reason we want such an event type. We would be able to tell whether our bot is working badly, or Discord's filter is working badly.

[Lulalaby]

Totally agreeing with that.

In my opinion:
The auditlog as it is atm is messy enough.
Such false-positive throwing logs would make it worse.

[Lulalaby]

the NSFW filter has lots of issues with false positives

That is the very reason we want such an event type. We would be able to tell whether our bot is working badly, or Discord's filter is working badly.

Bot debug logs exist.
Channels where you can log exist.

[RedDaedalus]

the NSFW filter has lots of issues with false positives

That is the very reason we want such an event type. We would be able to tell whether our bot is working badly, or Discord's filter is working badly.

If you're looking to make sure your bot isn't posting NSFW, an audit log entry is the wrong way to approach this. First of all you'd have to poll audit logs in every server the bot is in, and second you should just be able to look at the response body to see if the filter was triggered.