-
-
Notifications
You must be signed in to change notification settings - Fork 751
Check metricity for message knowledge when logging an out of cache message deletion #1359
Copy link
Copy link
Open
Labels
a: APIRelated to or causes API changesRelated to or causes API changesa: filtersRelated to message filters: (antimalware, antispam, filtering, token_remover)Related to message filters: (antimalware, antispam, filtering, token_remover)a: frontendRelated to output and formattingRelated to output and formattinga: moderationRelated to community moderation functionality: (moderation, defcon, verification)Related to community moderation functionality: (moderation, defcon, verification)a: statsRelated to the collection of statisticsRelated to the collection of statisticsl: 1 - intermediatestatus: approvedThe issue has received a core developer's approvalThe issue has received a core developer's approvalt: featureNew feature or requestNew feature or request
Description
Metadata
Metadata
Assignees
Labels
a: APIRelated to or causes API changesRelated to or causes API changesa: filtersRelated to message filters: (antimalware, antispam, filtering, token_remover)Related to message filters: (antimalware, antispam, filtering, token_remover)a: frontendRelated to output and formattingRelated to output and formattinga: moderationRelated to community moderation functionality: (moderation, defcon, verification)Related to community moderation functionality: (moderation, defcon, verification)a: statsRelated to the collection of statisticsRelated to the collection of statisticsl: 1 - intermediatestatus: approvedThe issue has received a core developer's approvalThe issue has received a core developer's approvalt: featureNew feature or requestNew feature or request
Type
Fields
Give feedbackNo fields configured for issues without a type.
At the current moment when a user deletes a message that the bot has not cached, it outputs a simple message embed including the channel and message ID, which is effectively all the discord API gives us in a message deletion context. However, now that we have Metricity running we are able to cross-check deleted messages with it.
While it's unnecessary to check it for every message, we could use this to get the original author of messages that we aren't provided one, and from that solve the frustrating issue where a user will selfbot-delete their message history and flood the channel with archived messages that aren't attributed to a user anymore.
This may require exposing an endpoint to "get message author" from the Metricity database.