Commons:Bots/Requests

From Wikimedia Commons, the free media repository
Jump to navigation Jump to search
This project page in other languages:

Shortcut: COM:BRFA

Bot policy and list · Requests to operate a bot · Requests for work to be done by a bot  · Requests for batch uploads
Gnome-system-run.svg

If you want to run a bot on Commons, you must get permission first. To do so, file a request following the instructions below.

Please read Commons:Bots before making a request for bot permission.

Requests made on this page are automatically transcluded in Commons:Requests and votes for wider comment.

Requests for permission to run a bot[edit]

Before making a bot request, please read the new version of the Commons:Bots page. Read Commons:Bots#Information on bots and make sure you have added the required details to the bot's page. A good example can be found here.

When complete, pages listed here should be archived to Commons:Bots/Archive.

Any user may comment on the merits of the request to run a bot. Please give reasons, as that makes it easier for the closing bureaucrat. Read Commons:Bots before commenting.

JonHaraldSøbyWMNO-bot (talk · contribs)[edit]

Operator: Jon Harald Søby (WMNO) (talk · contributions · Number of edits · recent activity · block log · User rights log · uploads · Global account information)

Bot's tasks for which permission is being sought: Uploading images in cooperation with Wikimedia Norge's GLAM partners.

Automatic or manually assisted: Automatic, but supervised – it will only run when I am online and available.

Edit type (e.g. Continuous, daily, one time run): Intermittently when our partners have available material.

Maximum edit rate (e.g. edits per minute): AndreCostaWMSE-bot, which runs on the same framework, seems to make one edit every ~2 minutes when it is active, so something close to that.

Bot flag requested: (Y/N): Y

Programming language(s): Python; using the Pywikibot-based Wikimedia-Commons-uploads framework from Nordic Museum.

Jon Harald Søby (WMNO) (talk) 08:57, 6 June 2018 (UTC)

Discussion[edit]

  • Please make test run. --EugeneZelenko (talk) 14:06, 6 June 2018 (UTC)
    • @EugeneZelenko: Working on it, but the script needs some more changes than I thought to work for our use-case. Unfortunately I won't have time to work on that until August because of vacation time, Wikimania, etc., so this request could be put on hold until then (even archived, and I can un-archive it once I restart the work). Jon Harald Søby (WMNO) (talk) 23:24, 19 June 2018 (UTC)

Whymbot (talk · contribs)[edit]

Operator: Whym (talk · contributions · Number of edits · recent activity · block log · User rights log · uploads · Global account information)

Bot's tasks for which permission is being sought: I would like to redact location information which was likely to be published inadvertently from ~1000 file pages. This is in response to a recent incident regading a Commons mobile app I help developing. For further background, please read https://github.com/commons-app/apps-android-commons/wiki/June-2018-incident .

The job is two-fold:

  • Removing location information from the latest version of the file page - this will only be done when the location information has been there since the first revision of the page. Otherwise, I assume it has already been fixed and removing it is counter-productive.
  • Deleting the contents of the applicable revisions

Example: let's say I published a file with a location information template which contains upload-time location of my mobile device that I didn't want to publish (first revision of the file page), and since then I edited it and changed location to the place I know the subject really was (second revision of the file page). My script will not edit the page, but delete the content of the first revision.

So far, it appears to involve 938 pages, 3294 revisions. I collected the data last Friday and I expect a small additional number of applicable revisions have been produced since then.

Automatic or manually assisted: manually assisted

Edit type (e.g. Continuous, daily, one time run): I expect most of the job will be done in a week. However, because not all Android users will download the mobile app's fixed version immediately, I would probably need another run or two after a while. Even considering that, I'd say one month will be enough. The expected number of edits and logged actions will be 3k-6k.

Maximum edit rate (e.g. edits per minute): 1 edit per minute

Bot flag requested: (Y/N): actually I'm not sure if bot flag is needed considering the expected number of edits and logged actions. It will definitely need sysop flag for performing revision deletion.

Programming language(s): a script based on the Pywikibot framework

I realize this may not be the most typical case of using bots, especially because it involves revision-deletion. Please advise me if you have other ideas on how to get job done. whym (talk) 14:46, 14 June 2018 (UTC)

Discussion[edit]

  • I considered asking for oversighting instead of deleting and I notified the oversight mailing list on June 11 - I have not received a response since then. It seems prudent to perform deletion in the meantime if oversight is going to take a longer time (or the request is going to be rejected eventually). whym (talk) 14:46, 14 June 2018 (UTC)
  • Question: Should I seek using a sysop-bot or my main sysop account? Either way, the temporary flag(s) can expire after one month's time for this job. whym (talk) 14:46, 14 June 2018 (UTC)
  • Looks good, thanks for writing the bot to perform this very much needed operation. Commons allows bot test runs, feel free to perform one, for instance on a test image created for this purpose with a previous version of the app. Syced (talk) 02:52, 15 June 2018 (UTC)
    • @Syced: Thanks for the suggestion. I performed a test and results are visible at [1][2]. Because I made a typo in the first run, I restored one revision and run it again with a fixed version. whym (talk) 10:58, 18 June 2018 (UTC)
  • It'll be good idea if bot will leave trace in oversight comment. --EugeneZelenko (talk) 13:36, 16 June 2018 (UTC)
    • @EugeneZelenko: As for deletion reason and edit summary, does this [3] seem appropriate? I'm not sure what I can do for oversighting. I could share my script but I would be unable to test and adjust it for them. As for 'comment', I'll definitely make sure linking this page in the edit summary and deletion comment. whym (talk) 10:58, 18 June 2018 (UTC)
      I meant that request to hide location information should be log entry. Test edit refer only to this request. --EugeneZelenko (talk) 13:43, 18 June 2018 (UTC)
      Sorry, I'm still confused. The wording I was going to use was "Redacting location information: Commons:Bots/Requests/Whymbot" which clarifies that it's hiding location information. Does it look okay to you? If not, can you suggest a complete wording? whym (talk) 00:31, 20 June 2018 (UTC)
      How does bot detect targets? By uploader request? By request for oversight? Other methods? Whatever method is, reference to request should be mentioned in log entry. --EugeneZelenko (talk) 14:08, 20 June 2018 (UTC)
      The is no individual request to refer to other than this. I was going to perform mass redaction of all files in the list I created, just to be safe. We could later inform uploaders offering to restore it, or introducing oversight for further redaction via a mass message. The point is that most of them are likely to have been unaware of the publication due to the app's UI that misrepresented the app's feature, so mass redaction seems safer and speedier. Alternatively we could ask and wait before redacting, but then what to do when there is no response? I consider it an emergency response. The detection criteria and technical details are described in [4] but to put it briefly, it covers photos that satisfy all of 1) contributed via the app 2) EXIF doesn't contain location 3) location template added by the app, and the result is the 938 pages I mentioned. whym (talk) 07:16, 21 June 2018 (UTC)
  • I think this should be approved to be done with the main account. --Krd 06:56, 19 June 2018 (UTC)