Page MenuHomePhabricator

Special:Tags and direct abusefilter means for reuploads
Open, Needs TriagePublicFeature

Description

Feature summary (what you would like to be able to do and where):

Currently the tracking a new revision / reupload of an image is difficult. I would like for there to be an automated Tag for reuploads, and a direct means for upload to be able to identify reuploads.

  • Special:log shows them though it is a little more complicated filtering
Special:Log?type=upload&user=&page=&wpdate=&tagfilter=&subtype=overwrite
  • To identify a reupload in AF, the coding needs to identify an upload, and then of no page_age or page_id (noting that AF documentation says page_id is unreliable)

So it would seem that we are already tracking new revisions in the system, especially as it is a right inherited with autoconfirmed at Commons, and it would be useful if that identification could also morph into a special tag that comes through into RecentChanges and that can also be utilised by AbuseFilters as a binary switch to regulate images with a little more finesse.

Use case(s) (list the steps that you performed to discover that problem, and describe the actual underlying problem which you want to solve. Do not describe only a solution):

Commons has an issue where we have an LTA who targets and overwrites images by certain people.

Benefits (why should this be implemented?):

  • Finding these overwrites in RC is a little more difficult than it should be. Having a tag allows for quickly targeting this class for review
  • Writing an abusefilter that solely looking at reupload adds ease to filter writing and would allow a better performance filter currently start with (action == "upload")

Event Timeline

Not certain whether there should be consideration of self-reupload and reupload. For the sake of AbuseFilters, that is not necessary as we can utilise page_first_contributor for those needs.

I think this is very similar to T22892 and needs T68961 to be done as well. Or maybe we could use another table if logging isn't a way.