In T97261#1237177, @hoo wrote:

There's an API for abuse logs already.

Yep, it is. Yet we have to purge data from it, such as:

"query": {
        "abuselog": [
            {
                "user": "BetseyRosetta"
            },
            {
                "user": "DelilahSlowik"
            },
            {
                "user": "JoshMaurozfcm"
            },
            {
                "user": "DelilahSlowik"
            },
            {
                "user": "CodyMarroquin4"
            },
            {
                "user": "LorenzaA89"
            },
            {
                "user": "LorenzaA89"
            },
            {
                "user": "MindaFitzhardin"
            },
            {
                "user": "KarlMayes01939"
            },
            {
                "user": "KarlMayes01939"
            }
        ]
    }
}

for example. All {}, "", :, etc. ain't needed.

@hoo Can we run it as a query from Quarry? I am not sure how the login permissions work between quarry and reality work to pull sensitive data.

@MarcoAurelio at least we can run a simple regex to clean that up

Is doing this actually a good idea? Stewards are expected to review the hits before actually doing a mass lock on the accounts.

@Glaisher Yes, we are suposed to review the hits, and nothing in this bug
indicates we will stop doing it.

Ok then. You can get "cleaner" results than API by running queries similar to the one below against labs database replicas. Of course, this is not as nice as a GUI but it works.

SELECT afl_user_text FROM `abuse_filter_log` WHERE afl_filter = 1 ORDER BY afl_timestamp DESC LIMIT 15;

This sounds like a simple JS-userscript to execute on a log page, and the API is there. Hasn't noone this idea yet or am I missing something? There is no need for a regex to clean up when it can be interpreted as json.

This will be usefull feature, In some cases I need to mass message to users who are logged by filters. Usernames available sagregated from editfilter logs shall be help full to me in my tasks.

Secondly I will prefer https://phabricator.wikimedia.org/T99650 being accepted as a subtask of this task.

Rgds

Why would you want to "mass" message users who have triggered filters?