Add variables in AbuseFilter to detect/block thanks
Problem: There is no way in AbuseFilter to detect uses of the "thanks" feature. This feature can be abused in order to harass editors. It is possible to mute a spectific account, but when the harasser uses a lot of accounts, the editor targeted by harasser has no other choice than disabling the whole thanks feature.
Proposed solution: Create thanks feature related variables, which could be "thanks sender username" and "thanks recipient username" for example.
Who would benefit: AbuseFilter editors, harassed editors
Erratum: I wrote in the proposal that variables "could be thanks sender username and thanks recipient username". We already have a user_name variable in AbuseFilter (for the user who does the action), so we only need a thanked user variable. This would allow to prevent harassment using thanks feature. — Jules*Talk09:34, 30 January 2022 (UTC)[reply]
Multiple accounts (sometimes with identity theft, insults, threats, etc. in their username) are created to thank multiple times an editor. — Jules*Talk13:06, 1 February 2022 (UTC)[reply]
Support Using 'thanks' feature was a mean of harassment in pl.wiki before. Something should be done to limit the possibility of using this feature to harass other users. Wostr (talk) 20:46, 28 January 2022 (UTC)[reply]
Support I noticed this about the "thanks" feature a while back -- it seems like you can just send an arbitrary number of them to someone, with nothing beyond a rudimentary ratelimit, and I don't think there is any way for someone to block them (aside from disabling the feature entirely, I think). They're great, and they have improved my editing experience, but I think that this vulnerability should be fixed. JPxG (talk) 00:26, 31 January 2022 (UTC)[reply]
Support ruwiki has an advanced bot to automatically block accounts abusing this feature, but having this as an AbuseFilter action would be way easier. (There might be more actions that would be useful if added to the extension.) ~~~~ User:1234qwer1234qwer4 (talk)19:41, 7 February 2022 (UTC)[reply]