Last modified: 2006-06-22 22:40:35 UTC
I think that RC-patrol would be much easier if we could reduce the duplication
of efforts coming from not knowing whether a page has been patrolled. The
"patrolled edits" feature is a good step, but we have to trust users, in case
they're patrolling their own edits.
I'd like to suggest a Special page which would, when loaded, give a single
recentchanges diff, chosen randomly from all of those which haven't been
patrolled yet. The user would patrol the edit (perhaps marking it as "good",
"should be reverted", or "skip"). Afterwards, another edit could be loaded if
desired. If all of the existing edits have been patrolled, an edit which has
been patrolled only once could be chosen (perhaps up to some maximum number of
patrollings, like 4 or 255).
This way, we would know that patrols aren't being uselessly repeated, and we'd
be able to know that every edit would be looked at (assuming there are enough RC
patrollers). This would make RC-patrolling a hell of a lot more interesting to
me; I've always been dissuaded by the feelting of wasted effort.
==Details that aren't very important to the main idea==
We might want to have edits by anon. users given priority. (And autoconfirmed
and admin users last?).
We probably want to restrict this to autoconfirmed users.
We may want some record somewhere of which edits someone has marked as good. In
the article history? Admin-only? Could we have RC-patrolling show up in
Robchurch suggested [[Special:Cleverpatrol]] as a name for this page. A related
feature was suggested earlier at [[User:JesseW/Recent Changes Slices]].
I'm working on this as an ongoing mini-project. See the incomplete extension in
Patroller is more or less ready for a proper test debut.