User talk:Krinkle/Patrolling

Re: Vandalism detection service

Hi Krinkle!

I just wanted to add a note pointing to meta:Research:Revision scoring as a service and wiki-ai @ GitHub, which might be of interest. Helder 02:18, 15 June 2015 (UTC)

About FlaggedRevs

Just some comments. ... so all the other initiatives have no way of knowing about this data as FlaggedRevs has its own system independent from the patrol-flag in core. This is not really true. If both FlaggedRevs and RCPatrol is toggled on, then the FR approves/declines/removal of approves are propagated to recentchanges.rc_patrolled. So recentchanges.rc_patrolled which is used by mw API and RCStream can be used for getting the information of which revisions are checked via FlaggedRevs or not.

Logging table is more problematic because there is only flagged revs log events and no patrol log event for manual FlaggedRevs approvals or declines when recentchanges.rc_patrolled is set true.

Second thing is that if both are enabled and user is using RCPatrol instead of FlaggedRevs for marking pages as patrolled then this information doesn't propagate to flagging revs approves. In wikipedia's default user interface this is not too big problem because you can just hide all RCPatrol UI-elements via CSS and say that we are using FlaggedRevs for reviewing the changes and RCPatrol is just for rc_patrolled flags. Hiding is also good idea because when FlaggedRevs and RCPatrol are both enabled it is usability mess in . Eg. If $wgUseRCPatrol would be enabled by default on all wikis this should be handled for wikis using FR. (And yes, it should be toggled on for wikis which are using FR for getting rc_patrolled flags)

However users can still mark the changes as patrolled with external tools like RTRC and it is good idea to use patrolling marks from these tools as FR reviews too. In clear cases when there is no other pending changes than the marked one it should be easy to implement. However there is also cases like that FR review is blocked by another change and it will be unblocked later. In fiwiki we are planning to add a bot which just scans pending changes and approves the patrolled changes which solves this but we are losing the information from history lists who is actually approved the change because name in the list is bot. (name of the patroller can be found from review log though) --Zache (talk) 06:28, 8 September 2016 (UTC)

@Zache: Thanks for pointing out that FlaggedRevs and Patrolling do work together. There were definitely various bugs with this integration (and there might still be some bugs to resolve), but at a basic layer it can be made to work. The presence or smoothness of that integration was not my main point, yet the mention of this lacking occupied a large portion of the Preamble. I have removed it in favour of expanding the more important points here instead. --Krinkle (talk) 05:37, 5 October 2018 (UTC)