Topic on Extension talk:AbuseFilter

Hi there, I am sysop in deWP and this night a long time vandal was catched in our abusefilter but then his edit frequency caused some of our filters to be throttled. Two filters (302/333) still appear as throttled which got me worried. I didn't want to block the vandal right away in order to get more information about his edit behaviour.

But even when being throttled the filters successfully prevented all of the vandals edits. In Extension:AbuseFilter#Emergency throttling it says „When a filter gets throttled, it doesn't perform any dangerous action (the ones that can prevent the ongoing action), and only "safe" actions are allowed“ I always thought this would mean the edits could pass by the filter without being disallowed? (I was worried about that and relieved that the filters continued working)

Dangerous actions are those listed in the $wgAbuseFilterActionRestrictions configuration variable with a value of "true" (blocking, removing from groups), but not disallowing the edit or warning. I've clarified this on the throttling section.

About the throttle, this is a problem that happens from time to time because of the logic. See task T210151

Ahh thanks for clarification! :)