Oh... So $wgFlaggedRevsAutoReviewNew Override and ReviewForDefault setup
FlaggedRevs so that it isn't applied to pages unless told to
specifically, ok.
~Daniel Friesen (Dantman, Nadir-Seen-Fire) [
Daniel Friesen wrote:
Are there any plans to tie FlaggedRevs in with
the page protection system?
I heard something about a feature for making it so that FlaggedRevs was
only applied to specific pages (ie: Ones noted to have heavy
traffic/vandalism) but it appears that the feature has something to do
with whitelisting pages with a config variable, which isn't very good
for my use case.
The use case I'm thinking of is this.
On the Narutopedia nearly every time a new volume comes out, we get
piles of new users coming in trying to add unconfirmed information to
the wiki, most of it false info and pure speculation. For that reason
the community has now taken to the idea of temp protecting articles
related to recent chapters every time a new volume comes out.
Unfortunately this also causes comments on the talkpage of new users
annoyed they cannot edit the page (despite notes that they are free to
mention any improvements on the talkpage, and it only being temp
protection). So I was considering an alternate option.
I was thinking of something like FlaggedRevs, kind of like a protection
level. Whenever we have issues with an article getting a lot of trash,
rather than flat out protecting we go to the protection page and from a
list of options [Flagged, Autoconfirmed, Protected] we chose flagged,
meaning specific high-traffic pages likely to have false information put
on them can be set so that all new revisions need to be reviewed before
they show up in the stable page shown to the public up front.
Yes, something very much like this was proposed on enwiki at
http://en.wikipedia.org/wiki/Wikipedia:Flagged_protection - its not
integrated into the protection form, but it provides an alternative to
protection using FlaggedRevs. There's a proposed configuration as well;
it may need some tweaks for your purposes.