Judgments should be sent through AbuseFilter, for which we need to implement at least the AbuseFilter-contentToString hook to flatten JSON, maybe reducing to just the freeform text values, or including quantitative judgment values in the hope of catching "marblecake"-style attacks.
Description
Description
Details
Details
| Project | Branch | Lines +/- | Subject | |
|---|---|---|---|---|
| mediawiki/extensions/JADE | master | +81 -1 | AbuseFilter integration test |
Related Objects
Related Objects
Event Timeline
Comment Actions
Do you mean that the judgements should be subject to abuse filters? (E.g. if they contain profanity, it should be possible to block saving that judgement using an abuse filter that matches the profanity and prevents the action?)
Comment Actions
@Huji Yes, exactly. We're hoping to create a new namespace "Judgment" and want to take every possible precaution against creating additional patrolling workload. It probably can't be helped in the end, but AbuseFilter and ORES flagging will help with reduce work by catching the low-hanging fruit.
Comment Actions
Change 464716 had a related patch set uploaded (by Awight; owner: Awight):
[mediawiki/extensions/JADE@master] AbuseFilter integration test
Comment Actions
Change 464716 merged by jenkins-bot:
[mediawiki/extensions/JADE@master] AbuseFilter integration test