Open main menu

Wikidata talk:WikiProject Counter-Vandalism

Contents

Great project1Edit

Hi all, I think this is a great project, as Wikidata is a very important centre for all the Mediawiki-sites. At the dutch wikipedia we have a similair thing which makes use of RTRC, a script from m:User:Krinkle, see for a manual this page. At the dutch wp we also make a list based on this RTRC-tool which looks like this: [1]. Only problem: it is in dutch, so I hope you can translate it via Google Translate or something else. Maybe it would be a great idea to implement that here on wikidata too. I'd like to hear suggestions! Q.Zanden questions? 23:51, 19 May 2017 (UTC)

Thanks for this tip. I added a link to RTRC. --Pasleim (talk) 08:56, 20 May 2017 (UTC)
Very interesting tool, but right now it somehow lacks Wikidata-specific filter capabilities. If @Krinkle is willing to adapt it to the Wikidata RC workflow, we can provide some input here. —MisterSynergy (talk) 09:22, 20 May 2017 (UTC)
@MisterSynergy:, what would you like to add to the RTRC-tool? I opened an issue at github here to ask him to talk with us about some features we would like to add to RTRC. For me, the tool works fine! Q.Zanden questions? 18:46, 20 May 2017 (UTC)
Efficient RC work requires filtering, and this tool does not support many useful filter options for Wikidata, if I see it correctly. For unstructured Wikipedia edits it can distinguish between page creations and page changes. Wikidata has structured data and permits much finer filter options for changed items; some of them are even essential for effective RC work, as can be seen at the already existing tools (reCh, DiffLists.js, …). However, since a variety of similar tools is a desirable situation (competition in development, fits most needs), I’d be happy to see the following filter functions integrated:
  • Filter edits by type: changes in claims, terms (label, desc, alias), sitelinks, merging, other; (as in reCh, DiffLists.js)
  • Filter term edits further by language; Wikidata is inherently a multi-language project, most editors only understand a very small subset of them. No need to see all the changes in other languages; (as in reCh, DiffLists.js)
  • Filter claim edits further by property or properties; (as in DiffLists.js)
  • Filter sitelink edits further by wiki project; (as in DiffLists.js)
Additionally, “batch patrol” (as in reCh) is a process I used a lot in the past. There are sometimes anon users with a large amount of edits which easily clog the RC stream if you can’t effectively patrol their edits. —MisterSynergy (talk) 19:07, 20 May 2017 (UTC)

Bot patrollingEdit

Since a few months, DeltaBot is marking undone edits as patrolled, i.e. edits which don't contribute anymore to the current state of the page. I could extend this functionality to other kinds of edits:

  • users are undoing themselves by adding/removing the content they have removed/added few seconds before.
  • page moves on the client site
  • page deletions on the client site

What do you think, could it be too invasive? --Pasleim (talk) 09:54, 22 May 2017 (UTC)

Can we have those cases listed for a couple of weeks to get an idea about the impact (number of cases, fraction of cases where bot-patrol would be problematic for whatever case…)? —MisterSynergy (talk) 10:46, 22 May 2017 (UTC)
I strongly support the proposal by @Pasleim: and I also agree with @MisterSynergy:: a list for a couple of weeks would be very interesting. --Epìdosis 06:36, 25 May 2017 (UTC)

Putting a link to this project under Special:RecentChangesEdit

I think it would be useful to put a link to this project under the utilities-list at https://www.wikidata.org/wiki/Special:RecentChanges . That way users who go to the "Recent change"-page to do counter-vandalism can discover this project and join it. ChristianKl (talk) 21:40, 24 May 2017 (UTC)

We need to inform the community about this project anyway. It was already announced in the most recent weekly newsletter, but I am not sure how many readers found it there. I consider to put an “advertisement” to WD:PC. There are a couple of other pages which could also link to this project permanently. —MisterSynergy (talk) 05:18, 25 May 2017 (UTC)
After thinking a bit, how about sending a thank you notification if a user does patrol 100/1000 changes that refers to this project? It could also be about undoing a certain amount of edits by other people. ChristianKl (talk) 09:21, 26 May 2017 (UTC)
I am highly sceptical about that kind of rewards. I do not think that it attracts the kind of RC workers we are seeking. The pure number of actions also depends on the tools one uses, but it does not really stand for the amount of work an RC worker has done.
It is important that we make RC patrolling as efficient as possible with great tools. We need to advertise them, and to improve them via with feedback to the developers. To my opinion this is one of the main reasons for this WikiProject. —MisterSynergy (talk) 09:31, 26 May 2017 (UTC)
Okay, if you primarily want established editors in the project I see that alerting newer users might not be the best strategy. I'm personally thinking a lot about how to get new editors who edit a bit exposed to more task within Wikidata. ChristianKl (talk) 12:35, 27 May 2017 (UTC)

description editing in the Wikipedia Android appEdit

Yet another RC toolEdit

 
Screenshot of the ORC tool

The last few months, I have been working on and doing counter vandalism work here at Wikidata with an own JavaScript patrolling tool - ORC (Open-ended Recent Changes tool). It's not limited to Wikidata, but has at least some special features for it. While it does not have the filtering capabilities which were requested for RTRC just a few sections above this thread, it will help you to identify what the item that has been changed is about by displaying the label and description (and aliases, and their languages, if not yours), the sitelinks (incl. preview popup), and the most important statements at a glance. Otherwise, it's focussed on patrolling, so it easily allows patrolling individual edits as well as all from a user or on a page. If you don't want to patrol the edits of a particular user, but also don't want to get bothered by their edits, you can ignore them. And so on. A more comprehensive list of features is to be found on the page I linked. Or just try it out. I'd love to hear your feedback, especially as development of this tool is still very much in progress. It's not perfect for sure, but it helps me a lot with my RC work already, and I am eager to hear your input how it could be improved. --YMS (talk) 20:32, 25 December 2017 (UTC)

@YMS: This sounds amazing, thanks! However, I had trouble getting it to work at first, I guess I'm not too familiar with how javascript imports should work, but what I ended up doing was adding:
mw.loader.load('//meta.wikimedia.org/w/index.php?title=User:YMS/orc.js&action=raw&ctype=text/javascript');
to my global.js on meta.wikimedia.org - Chrome was complaining about the content type being text/html with the load command you gave on the ORC page. ArthurPSmith (talk) 14:35, 26 December 2017 (UTC)
Hmm, not sure about this message. The loader call should be correct. Does the "ORC" tab appear on Special:RecentChanges (as it's a large script, loading sometimes may time out; so if it doesn't, best try reloading the page)? --YMS (talk) 15:25, 26 December 2017 (UTC)
Yes, the ORC tab appears now. ArthurPSmith (talk) 16:01, 26 December 2017 (UTC)
Oh, but it did not appear when I used the command you listed - I opened the Chrome Javascript Console to see what was going on and saw a message that it had not run the orc.js script due to text/html content type. So then I switched to the above which I believe forces a javascript type. ArthurPSmith (talk) 17:28, 26 December 2017 (UTC)
Actually, in my case it does not appear (I added the string to commons.js [2]).--Ymblanter (talk) 21:14, 30 December 2017 (UTC)
mw.loader.load( '//meta.wikimedia.org/w/index.php?title=User:YMS/orc.js&action=raw&ctype=text/javascript', 'text/javascript' ); // [[User:YMS/orc.js]] works in my case.
Anyway, nice tool—but I already miss sophisticated filter options. The “ORC” tab appears in some unexpected contexts, such as user javascript pages. Is this intentional? There are also some RC filters which the tool doesn’t understand (at least “ORC ignores unknown parameter: damaging__likelybad_color (c4)” and “ORC ignores unknown parameter: damaging__verylikelybad_color (c5)”). —MisterSynergy (talk) 21:21, 30 December 2017 (UTC)
Thanks, it works now for me.--Ymblanter (talk) 21:45, 30 December 2017 (UTC)
I already suspected that that kind of URL would work, but was waiting for Arthur to confirm this via mail. I will update the tool page. (Still strange that my Chrome didn't complain - add-on issue possibly?).
And yes, the "ORC" tabs appears on JavaScript pages intentionally for testing purposes (for me as well as for any other developer, possibly also for users who want to have a very quick look).
With the unknown parameters you caught me twice: a) ORC indeed doesn't support highlighting for ORES yet (simply didn't think of that; though the ORES scores displayed are highlighted anyway), and b) the highlighting feature for tags should work, but actually is broken. I will check both tomorrow or the day after. Thanks for reporting! --YMS (talk) 22:03, 30 December 2017 (UTC)
I updated the documentation and fixed the issue with tag highlighting (which only affected certain tags). But I won't implement the ORES highlighting today as promised. In fact, any filter can be highlighted with the new RC component. I simply wasn't aware of this. But some of those things are already highlighted in ORC in different ways (e.g. IPs, which are color-coded). I will have to think of a more generic solution here, so this goes on my long-term list. Btw, there, I already have more detailed filters for Wikidata already. Until then, if you depend on those filters, you'll probably have to stick with reCh and DiffLists (while I don't want to imply that having to use those is bad in any way). --YMS (talk) 10:55, 31 December 2017 (UTC)

Patrolling from user contributions, histories and diffsEdit

Few weeks ago, we had $wgUseRCPatrol enabled on Czech Wikipedia. For this purpose, I and Martin Urbanec have also developed a simple gadget and API on ToolForge which allows marking changes as patrolled from history (phab:T25792), multi-edit span diff (phab:T10697) and user contributions (phab:T16352). Would you like to import this tool to Wikidata as well? Matěj Suchánek (talk) 08:39, 27 June 2018 (UTC)

Would it be complicated to import it to Wikidata? Your description sounds useful, but I have to be honest that I can’t imagine how useful it actually is just by reading the code of the script … ;-) —MisterSynergy (talk) 08:46, 27 June 2018 (UTC)
Apparently, after importing it, I noticed it doesn't work well for histories and diffs, only for contributions. We will look into it (the problem is we don't have appropriate indexes on database replicas). You can test it via importScript( 'User:Matěj Suchánek/patrolRevisions.js' ). Matěj Suchánek (talk) 09:43, 27 June 2018 (UTC)
On contributions lists I can see a new link “Mark all revisions as patrolled”, and it works. I can’t find anything new on diff pages or on page histories, so what am I supposed to do there? —MisterSynergy (talk) 10:00, 27 June 2018 (UTC)
Nothing. As I said, it doesn't work well there. Actually, it just takes very much time until the server responds. Matěj Suchánek (talk) 10:16, 27 June 2018 (UTC)
Okay; I’ll leave it activated for a while, to see how it’s going to develop. —MisterSynergy (talk) 11:22, 27 June 2018 (UTC)
Hello MisterSynergy! For your information, I have rewritten the gadget to query MW API instead, it should work very well now. Matěj Suchánek (talk) 11:36, 18 July 2018 (UTC)
Thanks, it’s a great script now! —MisterSynergy (talk) 20:59, 18 July 2018 (UTC)

Unpatrolled edits?Edit

Hi! I've just observed a strange problem: I've made 4 rollbacks (704237515, 704237643, 704237756, 704238472) and, although I'm an admin, they are marked as needing patrolling. Is it a bug or a new policy? --Epìdosis 17:58, 29 June 2018 (UTC)

Another unpatrolled rollback (704230598), in this case by a rollbacker; I've just patrolled it. The problem is recent because I don't remember it having met it last week. --Epìdosis 18:01, 29 June 2018 (UTC) Or this (703030631) by @LydiaPintscher:: the problem affects autopatrolled users, rollbackes and admins. --Epìdosis 18:06, 29 June 2018 (UTC)
I Observed the same problem this morning. No idea what’s on. —MisterSynergy (talk) 19:19, 29 June 2018 (UTC)
Subscribe to phab:T198449. Matěj Suchánek (talk) 19:44, 29 June 2018 (UTC)
Return to the project page "WikiProject Counter-Vandalism".