Change Details

I am unsure if WMF/Wikipedia has run into this issue with repeat offenders (spammers, vandals, trolls) who have either flooded abuselogs or intentionally tripped a filter(s) to trigger the safety mechanism to disable the filter. The idea behind a quick reactivate button is that sometimes a well written filter needs no conditional change, merely just reactivate it again. Currently to reactivate a filter, the filter must be changed. Yes, perhaps the configuration threshold can be raised but that helps with nothing when a filter that works keeps getting disabled unless the threshold limit is set to false. This would be useful to independent wikis.

I am unsure if WMF/Wikipedia has run into this issue with repeat offenders (spammers, vandals, trolls) who have either flooded abuselogs or intentionally tripped a filter(s) to trigger the safety mechanism to disable the filter. The idea behind a quick reactivate button is that sometimes a well written filter needs no conditional change, merely just reactivate it again. Currently to reactivate a filter, the filter must be changed. Yes, perhaps the configuration threshold can be raised but that helps with nothing when a filter that works keeps getting disabled unless the threshold limit is set to false. This feature would be useful to independent wikis.

I am unsure if WMF/Wikipedia has run into this issue with repeat offenders (spammers, vandals, trolls) who have either flooded abuselogs or intentionally tripped a filter(s) to trigger the safety mechanism to disable the filter. The idea behind a quick reactivate button is that sometimes a well written filter needs no conditional change, merely just reactivate it again. Currently to reactivate a filter, the filter must be changed. Yes, perhaps the configuration threshold can be raised but that helps with nothing when a filter that works keeps getting disabled unless the threshold limit is set to false. This feature would be useful to independent wikis.