search

Syncxv / vc-message-logger-enhanced

GNU General Public License v3.0
91 stars 11 forks source link

Suggestion #28

Open CofStars opened 5 months ago

CofStars commented 5 months ago

I'm not sure how to explain this very well. I know that there is an option to ignore bots, but that's not quite what I am looking for. Are you all aware of bots like PluralKit and TupperBox? When someone proxies using the bot, it is not the bot's message being deleted, but the normal users. Is it possible for the message logger to somehow recognize who it was deleted by, or something? I am assuming not, but I have been annoyed by the spam of PluralKit and TupperBox logs by my message logger, but if I just ignore all by the users who proxy using these bots, I might miss messages that are deleted or edited when they don't proxy at all, which is more often than one might think, so I figured asking was worth a shot.

RuriYoshinova commented 4 months ago

what? you mean webhooks? also you can't see who deleted someone's message (except their own) without access to audit logs.

shadowpercifal commented 4 months ago

I'm not sure how to explain this very well. I know that there is an option to ignore bots, but that's not quite what I am looking for. Are you all aware of bots like PluralKit and TupperBox? When someone proxies using the bot, it is not the bot's message being deleted, but the normal users. Is it possible for the message logger to somehow recognize who it was deleted by, or something? I am assuming not, but I have been annoyed by the spam of PluralKit and TupperBox logs by my message logger, but if I just ignore all by the users who proxy using these bots, I might miss messages that are deleted or edited when they don't proxy at all, which is more often than one might think, so I figured asking was worth a shot.

Unfortunately it is not possible to know beforehand whether or not message is echoed by bot and there is no need for such checks in generic version of plugin. I suggest you try implement custom solution to delete messages echoed this way from log store.