Page MenuHomePhabricator

SPIKE: Test Automoderator with tr.wiki's FlaggedRevs configuration [8HRS]
Closed, ResolvedPublicSpike

Description

In T356903: [SPIKE] Test Automoderator with Indonesian Wikipedia's FlaggedRevs configuration [8HRS] we are testing id.wiki's FlaggedRevs configuration. For tr.wiki there's a different configuration - edits are hidden from readers by default across all pages, rather than via a specific page protection level (wgFlaggedRevsProtection is default - false, and wgFlaggedRevsOverride is default - true)

We'll want to give this a quick test to ensure that Automoderator behaves as expected, as with id.wiki.

Event Timeline

Restricted Application changed the subtype of this task from "Task" to "Spike". · View Herald TranscriptApr 16 2024, 9:30 AM
jsn.sherman renamed this task from Test Automoderator with tr.wiki's FlaggedRevs configuration to SPIKE: Test Automoderator with tr.wiki's FlaggedRevs configuration [8HRS].Tue, Apr 30, 3:34 PM
jsn.sherman moved this task from To be estimated to Up next on the Moderator-Tools-Team board.

The config mimicking the tr.wiki:

$wgGroupPermissions['sysop']['stablesettings'] = true;
$wgFlaggedRevsRestrictionLevels = [ 'autoconfirmed', 'autoreview', 'sysop' ];
$wgFlaggedRevsProtection = false;
$wgFlaggedRevsOverride = true;

Is behaving the same as our previous spike.

As an anonymous user with a revert performed by AutoModerator, you can see that it was automatically checked without needing a manual review.

Screenshot 2024-05-09 at 11.24.43 AM.png (390×1 px, 122 KB)

The behavior is also similar to our other spike in that if there are unreviewed changes before the AutoModerator revert happens, the revert is queued to be manually reviewed as seen here:

Screenshot 2024-05-09 at 11.23.42 AM.png (935×1 px, 308 KB)

And then after an admin approves it will appear like so:

Screenshot 2024-05-09 at 11.26.34 AM.png (370×1 px, 104 KB)

Overall, I'd say this is behaving exactly as expected given our other spike findings.