Page MenuHomePhabricator

Wikidata Tours pollutes Recent Changes
Open, Needs TriagePublic


When doing Recent Change patrol, changes made to items like Q16943273 for Wikidata Tours often appear as "Likely have problems". This wastes the time of Recent Change patrollers and has been going on for several years now.
@matej_suchanek suggests having the tour interface add a tag that would allow tour items to be excluded from Recent Changes. This would be one way to resolve the problem.

Event Timeline

Bovlb created this task.Mar 3 2020, 7:04 PM
Restricted Application added a subscriber: Aklapper. · View Herald TranscriptMar 3 2020, 7:04 PM

On Commons, HotCat somehow manages to do this, see e.g. this edit. (I don’t know how, though. I see edits from @Perhelion in connection with this feature.)

This is a quite important thing to fix because I'm working on several more tours and its likely the number of people who will use the tours will increase a lot

@matej_suchanek do you know what tag would be needed to tell recent changes to ignore it? This feels like a first step before finding out who could add it

Bovlb added a comment.Jun 4 2020, 4:15 PM

what tag would be needed to tell recent changes to ignore it?

That's a good question. Tags are normally defined to suggest the edit is bad, so the interface allows you to include by tag, but I don't see an option to exclude by tag. Obviously we don't want to create a "not-wikidata-tours" tag. This might also need support from a Recent Changes developer.

@Bovlb thanks, I'm really out of my depth, who might know about this stuff?

Bovlb added a comment.Jun 4 2020, 4:42 PM

@Mrjohncummings asked me to share this comment I posted at Wikidata:

From the discussion so far, there seem to be two proposed solutions:

  1. Add an edit filter that checks the item id against a hard-coded list and adds a tag. Any admin can do this, but we would need to (remember to) update the filter whenever we create new topics.
  2. Change the WikiTours interface to add a tag. This would be the more elegant solution, but would require work from a WikiTours interface developer. I don't know who that is, and I don't know how to find out.

who might know about this stuff?

I don't know. It's not easy for us "outsiders" to know which developer is responsible for what. Part of the point of filing bug reports here is that they can be triaged and assigned appropriately. If that never happens, then I don't know how to proceed.

@Aklapper how would we find out which developers or which teams work on things like this? Thanks :)

Bovlb added a comment.Jun 4 2020, 5:47 PM

I don't see an option to exclude by tag

Worth noting that tags are listed in the RC UI, so even if we cannot use it to exclude wikitour edits, an RC patroller could still see the tag before performing deeper investigation. I believe people are also using various tools wrapped around recent changes, and I cannot speak for them.

There are two ways of tagging these edits:

  • When a user starts a tour and interacts with the interface, the requests need to send tags= parameter.
  • Create a dedicated edit / abuse filter and tag edits to these items. (The list needs to be maintained in the filter.)

When I suggested not having a filter for this and making this a feature of Wikidata tours, I didn't realize we would have to "hack" the usual interface since users use it during the tour. So if this is too difficult, we can go with the edit filter.

Nevertheless, it should be clear what the tags will be used for. Do we want to tag only edits that are done using the tour scripts and ignore the rest? Or just every edit to these items? Should it ignore trusted users?

(By the way, RC filter for excluding edits with a tag is tracked in T174349.)

Bovlb added a comment.Jun 8 2020, 4:45 PM

Just to add another perspective on this issue, I have several times come close to blocking/warning a new user for vandalism before I realized they were taking a WikiTour. Having any sort of tag on the edit would be useful.

OK, so what are the next steps? I guess:

  1. Decide on an approach
  2. Find someone who can implement it
  3. Add some kind of instructions for people making tours if needed