This page uses content from Wikipedia and is licensed under CC BY-SA.

Wikipedia:Bots/Noticeboard

This is a message board for coordinating and discussing bot-related issues on Wikipedia (also including other programs interacting with the MediaWiki software). Although this page is frequented mainly by bot owners, any user is welcome to leave a message or join the discussion here.

If you want to report an issue or bug with a specific bot, follow the steps outlined in WP:BOTISSUE first. This not the place for requests for bot approvals or requesting that tasks be done by a bot. General questions about the MediaWiki software (such as the use of templates, etc.) should be asked at Wikipedia:Village pump (technical).


How can I increase the API request limit?

I'm developing a bot that examines articles for signs of undisclosed paid editing. It's only gathering data, not making any edits. There are some API queries that I make where it would be useful to be able to return 5000 rather than 500 results at a time. Do I just apply for this like any other bot? I'm an admin and am using my rights for some queries. Ideally, I'd just have the bot flag added to this account, but I'm not sure if that's done. SmartSE (talk) 22:40, 22 April 2018 (UTC)

@Smartse: both sysops and bots have the same 'noratelimit' capability - so if you want this to run on a non-admin account you can apply for a bot flag. That being said, if you are pulling huge numbers of queries ensure you are using maxlag, running in series, and otherwise following all of the mw:API:Etiquette - you can use the standard BRFA process. If you are dealing with very very large results you may be better using a dump. — xaosflux Talk 22:53, 22 April 2018 (UTC)
@Xaosflux: both sysops and bots have the same 'noratelimit' capability Do you mean I can already request 5000? I think I tried before... but that may have been before I had OAuth working properly. Can you give me an idea of "huge numbers"? At the moment I'm maybe making a few per second at max. mw:API:Exturlusage is one where I need more returned. I have downloaded the dump of mw:Manual:Externallinks_table but it doesn't contain namespace information (despite having a column for it). If you know a better way to count how many links there are to specific domain then please let me know! SmartSE (talk) 23:13, 22 April 2018 (UTC)
@Smartse: From what I can tell, "highlimit" is already 500, normal users are 50 (from mw:API:Query). So if you want to move this to a bot and have it work at the same speed as your sysop account it will need a bot flag. "A few per second" (at 5000) per second is 900,000 results per min, thats a good way to get blocked by operations. — xaosflux Talk 23:26, 22 April 2018 (UTC)
Also the 'ratelimit' is about how often you can ask, not the size of the result (which is the limits I listed above). — xaosflux Talk 23:28, 22 April 2018 (UTC)
@Xaosflux: Sorry - busy few days. I'm afraid that I'm still confused... This query when run in my browser does return > 500 values but when I request it using python I only get 500 results... Answering my own question: mw:Special:OAuthConsumerRegistration/propose has a "high-volume editing" option which appears to control the API limit. Regarding request rates - I presumed that it was less work for the servers to return 1 request of 5000 than 10 of 500 - is that not the case? In reality, most of the results will return far less than 5000, so it'd never be reaching 900k/minute. I'll be sure to get some more feedback on what a polite level of requests is before unleashing anything in the wild. SmartSE (talk) 20:43, 25 April 2018 (UTC)
For /w/api.php?action=query&format=json&list=exturlusage&euquery=slashdot.org&eulimit=max, I get 5000 using my bot. Check for "limits": { "exturlusage": 5000 } in the response. I only get 500 on this account. — JJMC89(T·C) 05:21, 23 April 2018 (UTC)
@JJMC89: Thanks that helped me work out what was going on! SmartSE (talk) 20:43, 25 April 2018 (UTC)
Given the application, I'm wondering if you shouldn't work from the page dumps (and specifically, the current page dumps rather than the full page dumps) instead of the live website. --Izno (talk) 21:57, 25 April 2018 (UTC)

Deleted fair-use file

Closing, not a bot error. File restoration request completed. If you want sysops to do something new, please bring up a discussion at WP:AN. — xaosflux Talk 21:56, 24 April 2018 (UTC)
The following discussion is closed. Please do not modify it. Subsequent comments should be made on the appropriate discussion page. No further edits should be made to this discussion.

I am not entirely sure if this is the right place to report this incident because it is more related to people not noticing that a bot made a plausible (for a bot, of course) mistake, and not about a bot malfunction. As you can see in my talk page, B-bot nominated for deletion orphaned fair-use file File:The Lord Amulree in 1949.jpg on 4 March. The file became an orphan on 1 March and was eventually deleted on 12 March at 00:00.

I prefer not to say that I am semi-retired because I wish I could be as active as I were in the past, when I edited almost every day, but the truth is I log in very sporadically at this point. I logged in after it had been deleted (ironically, the same day, 18 hours after deletion) and found many (unseen by me, with the files already deleted) of the bot's notices on orphaned fair-use files which were up for deletion. I checked them all and they were all instances of my fair-use file having been replaced by a free file except for this one, the article of which is now without an image. I went to article history and eventually found out that it was all the doing of a sloppy IP edit (diff) which removed the file by pure accident. The person who fixed the mess did not notice that there was a broken file link and just deleted everything, while nobody noticed that the orphaned file did not have an actual replacement. When I found out, I pinged the creator of the bot, B, who never answered, asking for some action to be taken. I am very baffled by this situation and finally decided to take it here.--The Traditionalist (talk) 20:14, 24 April 2018 (UTC)

Hi @The Traditionalist: if I'm reading the above correct, the tagging bot did not make an error (that is the file actually was orphaned and it tagged it correctly)? - and the deleting admin did not make an error either? (i.e. that file actually was fair-use, and actually was orphaned at the time it was deleted). Can you be a bit more specific about what you would like done differently in the future? Is there anything you want done now (e.g. undelete that file - if so you can ask the deleting admin directly or at WP:REFUND if they are inactive). — xaosflux Talk 20:21, 24 April 2018 (UTC)
@Xaosflux: The deleting admin did make a mistake. They did not check whether the file had been replaced or had been removed by accident, the latter being the actual case. I wish for the file to be undeleted and I hope that future deleting admins will check article history when they find an orphaned fair-use portrait of a deceased person to be without a replacement.--The Traditionalist (talk) 20:37, 24 April 2018 (UTC)


This is clearly the wrong place to have placed this. My bad. I will go to WP:RFU. Have a nice day!--The Traditionalist (talk) 20:49, 24 April 2018 (UTC)

Was replying as this was closed (edit conflict), but just wanted to point out that the IP edits shouldn't be dismissed as good-faith "sloppy" edits, and this was no accident (look at each of this IPs edits in sequence). We're in a growing arms race. I see these sort of drive-by IP edits constantly, and it can be time-consuming to track them back to the last good edit after others only partially revert. Probably too much to expect either bots or admins to not miss these sometimes, but we try to do the best we can. What's really needed are more clueful Clue-Bots, but it takes some very skilled programmers to write them. – wbm1058 (talk) 22:18, 24 April 2018 (UTC)

The discussion above is closed. Please do not modify it. Subsequent comments should be made on the appropriate discussion page. No further edits should be made to this discussion.

MEATBOT discussion

There's a discussion at WT:AWB which could probably use some input from BAG/botops. Primefac (talk) 14:19, 30 April 2018 (UTC)

Attempts of bot login

I noticed Magioladitis (talk · contribs) reported a login attempt on User:Yobot. I've just had the same on User:Bibcode Bot. Please make sure your bot passwords are secure, as we may be dealing with something systematic. Headbomb {t · c · p · b} 21:24, 3 May 2018 (UTC)

They seem to be proceeding ABC order through the list of editors (possibly recent). Regardless, more at WP:AN#Please help- who tried to break into my account? and WP:VPT#two-factor authorization. --Izno (talk) 00:29, 4 May 2018 (UTC)

API Logins being refused

FYI, I've personally run in to this and have seen a few other reports. Thread at Wikipedia:Village_pump_(technical)#API_Logins_being_refused. Anyone having this issue right now? — xaosflux Talk 03:19, 4 May 2018 (UTC)

@Xaosflux: - SQLBot uses botpasswords, and ran fine last run: [1]. SQLQuery me! 04:19, 4 May 2018 (UTC)
When I regenerated my botpassword on one account it was able to logon again. — xaosflux Talk 04:27, 4 May 2018 (UTC)

Inactive bots - May 2018

Per the bot policy activity requirements, the following bots will be deauthorized and deflagged in one week. These bots have not made an edit in 2 or more years, nor have their operator made an edit in 2 or more years.

BOT_user_name BOT_editcount BOT_user_registration BOT_last_edit Oper_username Oper_lastedit Notes
HBC Archive Indexerbot 165272 20061209003634 20120721005635 Krellis 20160118
HBC AIV helperbot3 140330 20070204005758 20120109193433 Krellis 20160118
OKBot 103883 20070604083415 20140401032952 OsamaK 20160402
MerlLinkBot 17943 20090114235424 20140406114255 Merlissimo 20160124
KLBot2 96688 20110415001009 20130708121708 Kizar 20160411
The Anonybot 209 20130119073648 20130515040838 The Anonymouse 20160419

Should an operator wish to maintain their bot's status, please place "keep" and your signature in the notes column above for your bot. Deauthorized bots will need to file a new BRFA should they wish to become reactivated in the future. Thank you — xaosflux Talk 23:24, 19 May 2018 (UTC)

Discuss

Operator notifications were sent to user talk pages today. — xaosflux Talk 23:28, 19 May 2018 (UTC)