< Commons:Bots
This project page in other languages:

English | 日本語 | +/−

Shortcut: COM:BRFA

Bot policy and list · Requests to operate a bot · Requests for work to be done by a bot · Changes to allow localization  · Requests for batch uploads

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 botEdit

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.

RileyBot (talk · contribs) 8Edit

Operator: Riley Huntley (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: Commons:Village_pump/Archive/2015/06#Request shows consensus for removal of "uploaded by" in the file namespace, as it has caused confusion in the past. I am requesting openended removal of "Uploaded by" and similiar phrases that fall within the same scope. As shown here, McZusatz was doing this job with YaCBot. However, his bot is no longer running the task nor was it approved. I am looking to run it openendly for all uploaders, in order to ensure that external re-users of Commons content are able to attribute Commons materials inline with the stated licences. I have gone ahead and done a trial run of 20 edits.

Automatic or manually assisted: Automatic

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

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

Bot flag requested: (Y/N): No

Programming language(s): Pywikipediabot

Riley Huntley (talk) 19:53, 6 February 2016 (UTC)

If there is consensus to do so the function schould be enabled again in YaCBot. YaCBot is also doing a lot of other stuff (cleanup tasks). Can your bot do the cleanup stuff as well? --Steinsplitter (talk) 20:46, 6 February 2016 (UTC)
So the bot that runs the task without seeking approval, would get to continue the task after I get it approved for them? Not sure what I think about that. In any case, yes, my bot can do cleanup stuff as well. Riley Huntley (talk) 20:55, 6 February 2016 (UTC)
YaCBot is approved for doing cleanup tasks (bot operators are not expected to re-apply every time they want to implement a small alteration). Commons sense schould be used. I see no problem if your bot does that task as well, there are ten thousands of affected pages. --Steinsplitter (talk) 21:11, 6 February 2016 (UTC)
Thanks for the explanation. Riley Huntley (talk) 22:10, 6 February 2016 (UTC)
@McZusatz: --Steinsplitter (talk) 21:16, 6 February 2016 (UTC)
Related discussions about YaCBot on this task: Commons:Village_pump/Archive/2015/07#Redundant, Commons:Bots/Requests/YaCBot_(confirmation), Commons:Administrators'_noticeboard/Archive_54#YaCBot. Simply removing the tags may raise the same controversy as in the first discussion. --Zhuyifei1999 (talk) 21:21, 6 February 2016 (UTC)
I missed those, thanks for linking them. I am more than willing to do the same as layed out in Commons:Bots/Requests/YaCBot (confirmation) as well as offering opt out of the user categories. Riley Huntley (talk) 22:10, 6 February 2016 (UTC)
I am ok if this task is done by a separate bot. You could even keep your current bot logic and do it without the opt-out (instead ask about opt-in to removal by the uploader on their talk page to avoid controversy). I know that russavia opted in to the removal, so you already got quite a batch of files. --McZusatz (talk) 21:51, 7 February 2016 (UTC)
Opt in it is! Riley Huntley (talk) 02:40, 8 February 2016 (UTC)


Following the first, second and third bot de-flagging run, an analysis of bot activity has been performed, and provided a list of bots without edits/actions in the last 2 years.

While we do not have a local bot de-flagging policy as of yet, this follows the precedent set in the first three deflagging runs, where we tentatively agreed to remove bot flags from accounts unused for a period as significant as two years.

As is the case with inactivity run for sysops, each and every owner of this request will be informed by posting a message on their talk page and sending them an e-mail.

To doEdit

  • Create list & start request: ✓ Done
  • Notify users via talk: ✓ Done
  • Notify operators via mail: ✓ Done
    Accounts with E-Mail function disabled: Cactus26, Docu, Stefan2, Wizzard, Marc
  • Deflag accounts: Time2wait.svg 

Affected botsEdit

The following accounts are flagged as bots and have been inactive for more than two years:

Username Owner Last edit Current status
SieBot (talk · contributions · user rights management) Siebrand 20140105 Hourglass 2.svg
LivingBot (talk · contributions · user rights management) Jarry1250 20140104 Hourglass 2.svg
SDrewthbot (talk · contributions · user rights management) billinghurst 20140102 ✓ Flag removed
SamatBot (talk · contributions · user rights management) Samat 20131218 Hourglass 2.svg
GerWsUpload (talk · contributions · user rights management) joergens.mi 20131217 Hourglass 2.svg User request, flag should stay, new uploads will come --Jörgens.Mi Talk 20:16, 1 February 2016 (UTC)
CactusBot (talk · contributions · user rights management) Cactus26 20131216 Hourglass 2.svg
File Upload Bot (Kaldari) (talk · contributions · user rights management) Kaldari 20131203 Hourglass 2.svg
AvocatoBot (talk · contributions · user rights management) Avocato 20131125 Hourglass 2.svg
InductiveBot (talk · contributions · user rights management) Inductiveload 20131124 Hourglass 2.svg
BotMyShinyMetalAss (talk · contributions · user rights management) Pleclown 20131119 Hourglass 2.svg
Olafbot (talk · contributions · user rights management) Olaf 20131115 Hourglass 2.svg
Legobot (talk · contributions · user rights management) Legoktm 20131114 Hourglass 2.svg
RKBot (talk · contributions · user rights management) Reinhard Kraasch 20131112 Hourglass 2.svg
NordiskaMuseetBot (talk · contributions · user rights management) Prolineserver 20131107 Hourglass 2.svg
Gabrielchihonglee-Bot (talk · contributions · user rights management) Gabrielchihonglee 20131028 Hourglass 2.svg
WillieBot (talk · contributions · user rights management) Mono 20131026 Hourglass 2.svg
BotMultichillT (talk · contributions · user rights management) Multichill 20130921 Hourglass 2.svg
SLQbot (talk · contributions · user rights management) John Vandenberg 20130918 Hourglass 2.svg
Nikbot (talk · contributions · user rights management) Filnik 20130830 Hourglass 2.svg
ArthurBot (talk · contributions · user rights management) Mercy 20130820 Hourglass 2.svg
O (bot) (talk · contributions · user rights management) O 20130816 Hourglass 2.svg
MerlIwBot (talk · contributions · user rights management) Merlissimo 20130809 Hourglass 2.svg
Rybecbot (talk · contributions · user rights management) Rybec 20130714 Hourglass 2.svg
TronaBot (talk · contributions · user rights management) Coet 20130703 Hourglass 2.svg
Xqbot (talk · contributions · user rights management) Xqt 20130521 Hourglass 2.svg
Smallbot (talk · contributions · user rights management) Smallman12q 20130510 Hourglass 2.svg
RileyBot (talk · contributions · user rights management) Riley Huntley 20130328  User requested that flag be kept
Aibot (talk · contributions · user rights management) A1 20130307 Hourglass 2.svg
Category-bot (talk · contributions · user rights management) Docu 20130302 Hourglass 2.svg
Sz-iwbot (talk · contributions · user rights management) Shizhao 20130204 Hourglass 2.svg
Stefan2bot (talk · contributions · user rights management) Stefan2 20130130 ✓ Flag removed
Wizzo-Bot (talk · contributions · user rights management) Wizzard 20121210 Hourglass 2.svg
File Upload Bot (Vonvikken) (talk · contributions · user rights management) Vonvikken 20121107 Hourglass 2.svg
РобоСтася (talk · contributions · user rights management) Lvova 20121024 Hourglass 2.svg
AusTerrapinBotEdits (talk · contributions · user rights management) AusTerrapin 20120721 Hourglass 2.svg
FotothekBot (talk · contributions · user rights management) Multichill 20120626 Hourglass 2.svg
ElCarbot (talk · contributions · user rights management) El Caro 20120609 Hourglass 2.svg
MarcBot~commonswiki (talk · contributions · user rights management) Marc 20120418 Hourglass 2.svg
GeographBot (talk · contributions · user rights management) Multichill 20110314 Hourglass 2.svg
MultichillAWB (talk · contributions · user rights management) Multichill 20090906 Hourglass 2.svg
File Upload Bot (Omnedon) (talk · contributions · user rights management) Omnedon 20090605 Hourglass 2.svg
MediaWiki default (talk · contributions · user rights management) mwextension never Hourglass 2.svg

No reaction since last runEdit

Operators of following bots haven't replied in the request (Hourglass 2.svg) in the last run:


What is the point of this? It seems like it's just a waste of people's time. Yes, I am in fact planning on using my bot account in the near future to do a mass upload from the Folger Shakespeare Library. But I don't get GLAM contributions every year. Who does? Frankly I find it sad that volunteers are having to spend time justifying their bots flags instead of doing more productive work. What is the danger of someone having a bot that is inactive for more than 2 years? What problems has this actually caused? It seems like it is just red tape and bureaucracy that will drive away volunteers. Sorry for posting such a rant, but I really don't understand the purpose of this. Kaldari (talk) 17:58, 28 January 2016 (UTC)

I also plan on using my bot in the near future again. Tasks, usually mass typo-corrections, come in irregularly, and as long as bot operators are actually competent enough to not destroy the project there should not be any need to deflag. As far as I know we haven't needed strict "policing" per se, and when we do run into rogue bots, they get taken care of rather quickly and without much bureaucracy involved. --O ( • висчвын) 21:19, 28 January 2016 (GMT)
Same, it's convenient to have an already flagged bot for when someone has a request on IRC or some other medium. Legoktm (talk) 10:13, 29 January 2016 (UTC)

I agree with this process, and it is sad to see that my bot is inactive for more than two years now (time is running!). I plan to organize photo contests this year again, and I would like to use my bot for this activity. If you decide to deflag my bot, I will accept it, and I will request the flag later, when I need it again. Samat (talk) 19:16, 28 January 2016 (UTC)

  • I suggest that you remove the bot flag from Stefan2bot. The bot isn't currently editing on this project, and I assume that the flag will be re-added should I ever submit a new bot request. I currently only need a bot flag on enwiki, but not here. --Stefan2 (talk) 16:45, 30 January 2016 (UTC)
    • Thanks for letting us know about this, @Stefan. Do feel free to apply for the flag again when the need arises. odder (talk) 19:10, 30 January 2016 (UTC)

Yah, more red tape to drive active contributors away. User:BotMultichillT is my labs version of User:BotMultichill so I would like to keep that around. For the other accounts, if you want to make sure I never use them again, sure, deflag them. Multichill (talk) 21:40, 2 February 2016 (UTC)

I gave some positive feedback on COM:BN for the way deflagging of old accounts was being handled. To be honest if you have odd accounts that you leave unused for over 2 years, you may want to rationalize them a little bit, or at least refresh their descriptions before you start operating them again. I would hope that 'crats will reflag bots with a good history, just by the operator informally asking for the flag at BN or similar and not have to jump through hoops of filling out bureaucratic requests. Perhaps someone that does this sort of reflagging could confirm here that the process will be this simple? @Odder: as the most likely respondent. -- (talk) 16:59, 4 February 2016 (UTC)

Commented there. In short: yes, if reasonable and possible per policy. --Krd 18:08, 4 February 2016 (UTC)
Good to hear, sounds like a friendly way of handling flags. -- (talk) 18:53, 4 February 2016 (UTC)
Thanks for bringing this up, @. As you might have noticed, our process of approving bot requests has gotten faster and simpler over the past few years, and in particular over the last year or so, thanks to the continued involvement of Eugene and Krd. So while new bot operators already have an easier time getting their tasks approved and their bots flagged, I see no real need to have proven and trusted bot operators to go through this — albeit simplified — process again. I think that a simple request on the bureaucrats' noticeboard would generally suffice to re-flag an unused bot unless there are obvious reasons not to do so (ie. original flag was lost „under the cloud“). We have in the past accepted returning administrators after a 48-hour period for feedback, and I think we could use the same period for returning bots without much hindrance. P.S. For documentation purposes, let's just make sure that such requests are always submitted to the bureaucrats' noticeboard rather than a user's talk page or via private e-mail or any other medium. odder (talk) 20:06, 4 February 2016 (UTC)
  • SQLbot hasnt finished its task, however the remaining uploads are much harder to process requiring more software enhancements. John Vandenberg (chat) 00:35, 8 February 2016 (UTC)

YiFeiBot (talk · contribs) (25)Edit

Operator: Zhuyifei1999 (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: (See COM:BWR request) Similar to Commons:Bots/Requests/YiFeiBot (13), it use quarry:query/2556 to find all files that do not transclude {{Infobox template tag}}, {{Information}}, {{Biohist}}, or {{BANQ media}}, not on any of Category:Media_missing_infobox_template, Category:Artworks_missing_infobox_template, Category:Items_with_OTRS_permission_missing_infobox_template, Category:Pages_using_Information_template_with_parsing_errors. For these files, it checks whether \{\{information|\|\s*source\s*=) is in the wikitext case-insensitively. If it is in, the bot prepends Category:Pages using Information template with parsing errors, otherwise Category:Media missing infobox template. (Prepending to bypass possible syntax error on wikitext parsing)

Automatic or manually assisted: Automatic unsupervised

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

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

Bot flag requested: (Y/N): N

Programming language(s): Python: pywikibot

Zhuyifei1999 (talk) 10:58, 15 December 2015 (UTC)


  • Due to lack of time testing, a visible test run will be (hopefully) done tomorrow. --Zhuyifei1999 (talk) 11:01, 15 December 2015 (UTC)
  • Symbol support vote.svg Support Zhuyifei1999 thanks for taking this on. A little comment about a query: transclusion of {{Infobox template tag}} should have been sufficient since {{Infobox template tag}} is embedded in {{Information}} few months ago. However it might be a while until all the DB tables are updated. {{Biohist}} and {{BANQ media}} will need to be rewritten to base on one of the standard infoboxes so the need for excluding those two is also temporary. Also it might be better to rewrite the query to automatically exclude files in all subcategories of Category:Media_missing_infobox_template without listing them by hand. Hopefully that will not slow down the query too much. --Jarekt (talk) 13:34, 15 December 2015 (UTC)
    In that case, I changed the query to
    SELECT page_title
    FROM page
    WHERE page_namespace = 6      -- files only
    AND page_is_redirect = 0      -- no redirects
    AND page_title NOT LIKE '%/%' -- skip rare image subpages 
      SELECT * 
      FROM templatelinks 
      WHERE page_id = tl_from 
      AND tl_title in ('Infobox_template_tag', 'Biohist', 'BANQ_media') 
      AND tl_namespace = 10 
    AND NOT page_id IN ( 
      SELECT cl_from
      FROM categorylinks 
      WHERE cl_to IN (
        SELECT "Media_missing_infobox_template"
        SELECT innerpage.page_title
        FROM categorylinks innercl
        INNER JOIN page innerpage
        ON innerpage.page_id = innercl.cl_from
        WHERE innerpage.page_namespace = 14
        /*AND innercl.cl_type = "subcat"*/
        AND innercl.cl_to = "Media_missing_infobox_template"
    Right now I'm running a null-editing bot to go over them to ensure all pages transcluding {{Information}} are updated. --Zhuyifei1999 (talk) 09:50, 16 December 2015 (UTC)
Now on files starting with "Bo" after > 7500 null edits. I just lowered the throttle to speed this up. --Zhuyifei1999 (talk) 11:47, 17 December 2015 (UTC)
To be honest, I don't understand anything of this request, but it seems you know what you are doing, and I suggest to approve this if no objections arise. --Krd 14:38, 17 December 2015 (UTC)
Pictogram voting comment.svg Comment The task is to keep Category:Media_missing_infobox_template up to date adding new files as people upload them. Also detect special cases with parsing errors and add them to Category:Media_missing_infobox_template' subcategory Category:Pages using Information template with parsing errors, so we can quickly detect and fix bad edits that break infoboxes. --Jarekt (talk) 15:54, 17 December 2015 (UTC)
quarry:query/6359 works well for me.--Jarekt (talk) 04:23, 18 December 2015 (UTC)
Now on pages starting with "USS San Diego", after 50000+ null edits. @Krd: The real test run for this task haven't started, right now it's mass null editing false positives for the actual run --Zhuyifei1999 (talk) 10:11, 18 December 2015 (UTC)
Zhuyifei1999, I would not worry about "null editing false positives". I would use quarry:6359 and in a half a year you can change SQL to remove check for {[tl|Information}} from the query. By the way may be you can also do this query] to find files that can be removed from the category once someone adds infobox. --Jarekt (talk) 12:57, 18 December 2015 (UTC)
Ok the mass null edit was done, and I switched to your query (it should have little difference anyways). Ran a test run at [1]. Oh I'm pretty sure in only half a year, few would be reparsed without a mass null-edit :P --Zhuyifei1999 (talk) 14:44, 18 December 2015 (UTC)
I think will be good idea to clarify type of errors with category or edit summary. For example, it is not obvious in File:Strýčkovice, kaplička II.jpg. --EugeneZelenko (talk) 15:23, 18 December 2015 (UTC)
File:Strýčkovice, kaplička II.jpg was a false positive as it had perfectly file {{Information}} template. May be problem was due to lag with database updates for new uploads? The bot should only be catching files without visible {{Information}} template (or other infobox). --Jarekt (talk) 16:45, 18 December 2015 (UTC)
  • @Zhuyifei1999: Your last edit to this page was on 18 December, so over 40 days ago; are you still planning to work on this? Just looking for an update, really :-) odder (talk) 16:00, 28 January 2016 (UTC)
    I have no problems with this, except that it might take me a while to find which script is for this task :) --Zhuyifei1999 (talk) 16:30, 28 January 2016 (UTC)
    @Zhuyifei1999: This should be closed soon, either as approved or as stale. Please advise. --Krd 08:34, 8 February 2016 (UTC)
    @Krd: Well, I have no idea what is blocking approval. The only concern I see is about the false positives (raised by Eugene), and was addressed by Jarekt. --Zhuyifei1999 (talk) 09:11, 8 February 2016 (UTC)
    I would say lets approve this and manually verify all edits for a while. I can volunteer to help. --Jarekt (talk) 16:03, 8 February 2016 (UTC)
Read in another language