403 Forbidden when sending messages to user after strike ban

[MattyTheHacker]

[MattyTheHacker]

occured following a user being first timed out, then banned following a spam message being sent

[CarrotManMatt]

Ah, I think this is to do with the fact that a bot can't send a user a message if that user is no longer in any servers that that bot is in. (Although this does need verifying)

I think a solution could be to still attempt to send the message to the user (in case they are in another server) but if it can't be sent, then send a note in the response to the committee member that initiated the strike, to message that member personally?

[MattyTheHacker]

this also comes back to the issue we saw before around discord not actually indicating in the error why the message failed to send - it could be the user has blocked the bot, that they have privacy settings to a certain thing (i.e. not sharing a server) or something else entirely

[CarrotManMatt]

Very true. I think reminding the committee member to send a message if TeX-Bot couldn't is still a good fallback. As well as logging that the message send failed of course.

[MattyTheHacker]

Would it be useful to roll these issues all into one error handler that we attach to anywhere we send a DM message that clearly says it's encountered a 403, "we tried to send abc to user blah blah but failed, this could be for reasons xyz, or something else completely" message rather than having it shit out the full exception

[CarrotManMatt]

Yh, would deffo be useful to output that to the log & if it occurred under a command call telling the caller in the response too