Page MenuHomePhabricator

Abuse filter test option based on last 100 changes in a namespace
Open, Needs TriagePublicFeature

Description

In Special:AbuseFilter/test it would be useful to be able to run tests based on last 100 changes in a namespace. Numbers of wikis have very active namespaces and filters are often set per namespace as a ready means to lessen conditions/checks. While this is great for the ability to test, the effective testing ability can be swamped by the busy namespaces so the only testing can be done is against the problem edit itself and testing for false positives is not easy nor efficient.

At this stage we have: action type, changes by user, dates, and page_title

I was hoping that there could be a namespace drop down list that is actively populated based on the list that shows at the standard views like RC dropdown. If there was also an easy way to trigger on/off the equivalent talk or non-talk namespaces that would get bonus points, but is not my primary need.

Event Timeline

JJMC89 changed the subtype of this task from "Task" to "Feature Request".Jun 5 2021, 12:54 AM

I think this should be trivial. We have full control over the SQL, so adding a WHERE for the namespace is totally doable (as a matter of fact, we already do that when a title is specified). I think the important thing is to reuse the core logic as much as possible, in particular regarding the generation of the HTML selector.

If there was also an easy way to trigger on/off the equivalent talk or non-talk namespaces that would get bonus points

This would also be relatively easy I guess, as long as the relevant logic from core is used.

Think that if there are core logic components available, happy to utilise them as the next step development, and see how it works, this is about getting a good "last 100" for reasonable comparison.

At English Wikisource, it is quite rare for us to have vandalism and it is close to zero spam, yet it will be close to the most active namespace and chokes the last 100 edits comparison list.