Commons:Bots/Requests

Shortcut: COM:BRFA

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.

I	Create a user account (while logged in to your normal account) and user page for the bot On the bot's userpage, add {{bot}}, which automatically adds the page to Category:Commons bots. Then add the following information to the bot's userpage (all this is mandatory): Operator: Who the creator/operator is and how they can best be contacted Tasks: Details of the bot's task or tasks Operation: Whether the bot is manually assisted or runs automatically When: When it operates (continuously, intermittently, or at specified intervals) Maximum edit rate: The bot's maximum edit rate (eg edits per minute) Language: The language and/or program that it is running
II	Create your bot request: Replace "YourBotName" with your bot's username in the box below and click the button. Complete the questions on the resulting page and save it. Remember that your bot will be allowed to operate only for those tasks that you have specified in your request. Add your bot request to the list here: Edit the following request list, adding the following text to the top of the appropriate section (replacing "YourBotName" with your bot's name): {{Commons:Bots/Requests/YourBotName}}
III	Test run Make a short test run with your bot account (30-50 edits/uploads) to allow other users to review your bot's tasks.
IV	Waiting for approval. You now need to wait for community approval. A bureaucrat will close the request and will also grant a bot flag, where necessary. Closed requests are moved to Commons:Bots/Archive.

Archives List all Requests Requests by closing date

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

Contents

Requests for permission to run a botEdit

watch

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.

G2Cbot (talk · contribs)Edit

Operator: Tæ (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: Upload featured picture of the day from geograph.org.uk using Geograph2Commons tool.

Automatic or manually assisted: Automatic

Edit type (e.g. Continuous, daily, one time run): One time run

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

Bot flag requested: (Y/N): Y

Programming language(s): Same language which is used in Geograph2Commons.

√Tæ√ 11:31, 13 August 2018 (UTC)

DiscussionEdit

• Do you yourself visit toolforge:geograph2commons with a browser to upload the image, or do you have an automated process or script to invoke geograph2commons? --Zhuyifei1999 (talk) 13:13, 13 August 2018 (UTC)

  As we know that a bot do its task automatically. So this bot will also automatically upload image by using G2C.--√Tæ√ 13:54, 13 August 2018 (UTC)

  Does that mean you have a script to invoke geograph2commons? If that is the case, could you clarify how the script works step by step? I'm quite interested on how scripts invoke an OAuth tool automatically. --Zhuyifei1999 (talk) 14:21, 13 August 2018 (UTC)

  Also, how does the bot perform categorization? --Zhuyifei1999 (talk) 14:23, 13 August 2018 (UTC)

•  Oppose Same reason as here (user got renamed globally): Commons:Bots/Requests/Jæbot, Commons:Bots/Requests/Jæbot (2), Commons:Bots/Requests/IpernityreviewR, Commons:Bots/Requests/Jæbot 3. And the user was blocked for mass uplaods (dupes, copyvios, etc.). --Steinsplitter (talk) 15:10, 13 August 2018 (UTC)
•  Oppose per Steinsplitter and this log entry.   — Jeff G. ツ _{please ping or talk to me} 07:58, 14 August 2018 (UTC)

AAlertBot (talk · contribs)Edit

Operator: Hellknowz (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:

• This bot works on English Wikipedia to deliver Article alert report pages to subscribed projects and taskforces. Article alerts is a project that aims to deliver reports to internal topic-based projects about which pages enter and leave certain Wikipedia maintenance workflows, such as, deletion discussions, comment requests, featured content processes, etc.
• On Commons, the bot reads and parses workflows that may be relevant to report delivery, namely, the deletion processes concerning Commons' media that is used on English Wikipedia.
• Specific needs: read-only API -- for higher bot limits when reading and parsing categories/templates, relevant discussion pages, and relevant file histories and usages. Possibly occasional own userspace sandbox edit (such as a run problem report and while testing results).

Automatic or manually assisted: Automatic

Edit type (e.g. Continuous, daily, one time run): Daily run

Maximum edit rate (e.g. edits per minute): N/A

Bot flag requested: (Y/N): Y

Programming language(s): C#

—  HELLKNOWZ  ▎TALK  ▎enWiki 09:57, 9 August 2018 (UTC)

DiscussionEdit

• We usually don't approve read-only bots. --Krd 12:15, 9 August 2018 (UTC)
  • I would prefer to have the flag so I can have the 50->500 API request limit and no individual rate limits. Especially, since the bot is running individual queries in parallel. I have not investigated the local workflows in detail to give any exact numbers. I'm some ways off from actually implementing this.
  • That said, I don't really need the flag, since the bot won't edit anything that needs flagging besides may be its sandbox, the actual query count is low, and I can run everything as a regular account. In that case, I would like the approval filed just "for the record" so it's clear what the account is for in case anyone asks later why the bot is doing anything at all on Commons. —  HELLKNOWZ  ▎TALK  ▎enWiki 13:52, 9 August 2018 (UTC)

    Could you please clarify what you'll do with data? How Commons or other WMF project will benefit from this bot? Could you use Commons dumps instead? --EugeneZelenko (talk) 13:58, 9 August 2018 (UTC)

    The bot is part of English Wikipedia's Article alerts internal project. In short, the bot delivers organized daily reports about pages that are under discussion for deletion, review, featuring, etc. and any additional information. Here's an example. I also left a brief description on User:AAlertBot as per COM:BOTS. I cannot use dumps, because it needs live data as per the purpose. —  HELLKNOWZ  ▎TALK  ▎enWiki 14:14, 9 August 2018 (UTC)

    So bot will add deletion/permission/etc requests from Commons? --EugeneZelenko (talk) 13:45, 11 August 2018 (UTC)

    The current goal is to list images up for deletion on Commons in the report on English Wikipedia (along with the local already-reported up-for-deletion images). The reason is that these don't get reported as the deletion process is on Commons and not English Wikipedia and so the images occasionally "disappear", usually because they are incompatibly/badly licensed. For this, I need to read the deletion request page, it's dated subpages, possibly deletion categories, every file under deletion, likely part of its immediate history, and likely discussion page history. I haven't fully investigated the exact pages I need to read though and I'm going off what I have to do on En Wiki.

    In the future, I may add other processes as appropriate, though none come to mind immediately that happen on a per-file basis. I doubt I will add something that is only on Commons and not related to English Wikipedia, like licensing issues or something. I don't know what permission request is. —  HELLKNOWZ  ▎TALK  ▎enWiki 15:07, 11 August 2018 (UTC)

    If you cache the results of previous queries, this should be easily achievable with 50 results per request. If you disagree please elaborate. --Krd 15:16, 11 August 2018 (UTC)

    I cache things that I can. But I can't cache queries that change between runs: category members, template embedding, discussion page contents. And yeah, it will likely be <50 items per query for most queries. But Commons has a long backlog and stuff like Category:Deletion requests has thousands of pages though. But as I said, I don't need the flag if you decide it's not necessary -- it might take marginally longer to do a run. As long as this request exists for future reference. —  HELLKNOWZ  ▎TALK  ▎enWiki 15:57, 11 August 2018 (UTC)

• Is this bot doing the same thing as phab:T167614? If not, could you clarify the difference? --Zhuyifei1999 (talk) 13:18, 13 August 2018 (UTC)
  • Likely similar internally. AAB would read and parse more, but only daily. Here's a discussion on this. Those notices don't contain a bunch of information that AAB reports. For one, they never go away and I cannot "close" the entries or report what happened to the file. Here's an an example of AAB report and the sort of info it contains, including keeping closed entries visible for a while. —  HELLKNOWZ  ▎TALK  ▎enWiki 14:12, 13 August 2018 (UTC)