Wikipedia:Bot owners' noticeboard

From Wikipedia, the free encyclopedia
  (Redirected from Wikipedia:BOWN)
Jump to: navigation, search
Shortcuts:

This is a message board for coordinating and discussing bot-related issues on Wikipedia (also including other programs interacting with the mediawiki software). Although its target audience is bot owners, any user is welcome to leave a message or join the discussion here. This is not the place for requests for bot approvals or requesting that tasks be done by a bot. It is also not the place for general questions about the mediawiki software (such as the use of templates, etc.), which have generally a best chance of being answered at WP:VPT.


Archives
Archive 1 (2006) • Archive 2 (2007) • Archive 3 (2008) • Archive 4 (2008–9) • Archive 5 (2010) • Archive 6 (2010–11)


Contents

[edit] Modifying programming for minor bot problems

Yobot added {{ibid}} to List of Ohio covered bridges, even though none of the citations were problematic. I don't want to stop the bot for one minor issue, and operator Magioladitis is on wikibreak until next May, so I can't see how to report this properly. Is there someone here that could address the issue? Nyttend (talk) 19:23, 29 December 2011 (UTC)

Is it obvious why Yobot thought it needed tagging? - Jarry1250 [Cogitation needed] 20:45, 29 December 2011 (UTC)
Not at all; as I say, the citations were unproblematic. One is to

<ref name=Delorme>Ohio Atlas & Gazetteer, DeLorme, pg 68-9</ref>

and the rest are <ref name="Delorme"/> You'll notice that the article is undercited, but these specific citations shouldn't produce this type of bot reaction, and a bot shouldn't tag an article with {{ibid}} if it simply lacks sufficient citations. Nyttend (talk) 20:49, 29 December 2011 (UTC)
Actually taking a look I see at least 7 different references, and even one of them using the term ibid. ΔT The only constant 20:55, 29 December 2011 (UTC)
Yeah, it's non visible output but it's there. - Jarry1250 [Cogitation needed] 21:00, 29 December 2011 (UTC)
If you leave a note on Magioladitis talk page he should respond fairly quick. At lead within a day or 2. I saw he responded to a question there earlier today. --Kumioko (talk) 21:19, 29 December 2011 (UTC)

[edit] Question about bot editing speed

I have a question about the speed barrier for bot edits. I have multiple tasks currently approved for my bot with 2 more pending and several more in the future. Is it ok for me to run some of these concurrently without being in violation of the speed limit. For example, the bot may be doing 8 - 10 edits a minute for one task and 8 - 10 edits a minute for a completely separate task at the same time meaning its running at 16-20 edits a minute and maybe more. I just want to make sure I am not going to be breaking any rules if I start one task while another is still going. --Kumioko (talk) 16:51, 10 January 2012 (UTC)

You should be fine. Edit speed is only really a problem when you're editing under your own account (e.g. AWB, scripts, etc), once you're using a flagged bot account it is not really a big deal. --Chris 16:55, 10 January 2012 (UTC)
Well, there is also the fact that a bot really shouldn't be editing so fast that it resembles a denial-of-service attack, although if you do do that you're not likely to face any on-wiki sanctions (you'd more likely just be summarily IP-banned by the sysadmins at the border routers).
In general, if each task is limited to one active HTTP connection at a time and uses the maxlag parameter to automatically throttle itself when the database servers are lagging, you should be fine. Anomie 17:15, 10 January 2012 (UTC)
Ok great thanks. I don't know much about the maxlag parameter so I'll look into that but I doubt I will be doing more than about 20 a minute anyway. AWB is a great tool but its a bit memory intensive so it doesn't usually go much over 10 a minute in the best of times. --Kumioko (talk) 17:27, 10 January 2012 (UTC)
Maxlag is a way for MediaWiki to be able to quickly drop non-critical requests when the databases are overloaded to give them a better chance to catch up, no matter how quickly those requests are coming in. According to this AWB uses maxlag; I don't know whether it offers an option to turn it off or change the threshold. Anomie 17:50, 10 January 2012 (UTC)
Great thanks. --Kumioko (talk) 17:58, 10 January 2012 (UTC)
The old figures of "several per minute" were to keep safe the stone age technology (compared with what is there now). Rich Farmbrough, 21:11, 11 January 2012 (UTC).
Thats what I was hoping. --Kumioko (talk) 21:44, 11 January 2012 (UTC)

[edit] Can We Get a Ruling

...over here? The bot's been doing the same tasks since day 1, no amendments to the code ... today, it's suddenly blocked. (talk→ BWilkins ←track) 01:27, 12 January 2012 (UTC)

The request at Wikipedia:Bots/Requests for approval/7SeriesBOT says that only deletions that comply with WP:CSD#G7 will be done. Because G7 specifically and explicitly excludes user talk pages, that means that the bot approval must also exclude such pages. It would probably be better to get consensus at WT:CSD that this bot has an exception to the normal G7 rules. — Carl (CBM · talk) 01:35, 12 January 2012 (UTC)
WP:CSD#G7 and WP:CSD#U1 both explicitly state that user talk pages are not to be deleted under those criteria. User pages deleted under WP:DELTALK should certainly not be done by a bot, as they are only done in exceptional circumstances, and bots are no good at detecting something as general and vague as "exceptional circumstances". Seems pretty black and white to me. Just because the bot has been doing it for awhile with no complaints doesn't necessarily mean that it's ok, it just means that no one has noticed until now. —SW— communicate 02:29, 12 January 2012 (UTC)
It seems there is a current discussion about this very topic here. —SW— express 02:32, 12 January 2012 (UTC)
I've re-read both BRfAs and the associated deletion criteria. As Scottywong mentions, there is an "except under very exceptional circumstances" get-out clause, and I'd suggest that only one editor (per Task 1) is an exceptional circumstance. I may be a lack of imagination or experience on my part, but I can't see when a Task 1 deletion would be bad. Josh Parris 03:39, 12 January 2012 (UTC)
...and look at the incidents where the usertalk page has been deleted ... in one case someone warned them, removed the warning, then tagged for G7 ... looks like an obvious case (talk→ BWilkins ←track) 17:04, 12 January 2012 (UTC)
Personally, when I find those, I remove the {{db-g7}} and replace with a welcome template. Reaper Eternal (talk) 17:11, 12 January 2012 (UTC)

Wouldn't the obvious compromise be to only delete user talk pages if the single contributor was the user? I can't imagine there would be any concerns about deletion then. And really, it's not like there's a huge G7 backlog to begin with. CSD G7 seems fairly clear, and consensus on any exception would have to be made at Wikipedia talk:Criteria for speedy deletion, not here. — madman 17:12, 12 January 2012 (UTC)

That could therefore possibly be a U1 ... (talk→ BWilkins ←track) 17:27, 12 January 2012 (UTC)
If someone mistakenly creates a user talk page (e.g. wrong click on Huggle or whatever) and then decides to G7 it, will the user whose talk page briefly existed get a "You have new messages" bar with a red link to their talk page when they log in? That could be a bit confusing for them. 28bytes (talk) 17:24, 12 January 2012 (UTC)
I don't think they will after the page has been deleted. — madman 17:26, 12 January 2012 (UTC)
If that's the case, then I don't see a problem with what the bot's doing. The alternative would be for whoever's requested the G7 to have to wait until it's manually deleted by an admin, and risk giving the innocent user a spurious orange bar pointing them to a scary-looking {{db}} box on their talk page. I think the key concern should be to avoid confusing or annoying a new user. 28bytes (talk) 17:32, 12 January 2012 (UTC)
I understand your concern. But I think that's a fringe case in practice (if users are warning the wrong people that often, they really need to slow down and look at what they're doing; it's not a race). And I agree with the blocking administrator that as it stands, the bot is incorrectly deleting pages per U1 and G7. U1 is absolutely unambiguous, but I do agree that there's a case to be made that G7 should apply to user talk pages with a single contributor. That case should be made at Wikipedia talk:Criteria for speedy deletion. — madman 17:38, 12 January 2012 (UTC)
@Josh Parris: how easy is it to remove the offending code. We want to make sure that it's still deleting compliant User talk:WhoeverWhatever/mysubpage but not User talk:WhoeverWhatever ... is this something I can tweak? (I'm pretty sure the code has not changed since the last one you uploaded). I can run it that way until we clarify things elsewhere (talk→ BWilkins ←track) 16:40, 13 January 2012 (UTC)
Give me a few days to find my feet again. Josh Parris 22:01, 13 January 2012 (UTC)
No problem! Thanks Josh ... good to have you back and around (talk→ BWilkins ←track) 14:02, 14 January 2012 (UTC)

[edit] Special request for a bot run

My bot already has the capability and general authority to do this type of change however some may view it as purely cosemetic so I am posting it here prior to running it to give an explaination and give an opportunity for comments.

Per a conversation on my talk page and on Wikipedia talk:WikiProject Templates#Update of category it appears that a WikiProject template redirect is causing articles to not categorize properly. It could be argued that this particular problem might be fixable by simply nudging the template or the redirect but it emphasizes the point I have been making for sometime that Template redirects should treated differently (preferable avoided when possible) than normal article redirects because the coding of the template can, and relateively frequently does, have negative affects on other things when redirected.

In this case it appears (and I could be wrong which is also why I am posting this here first) that the {{WikiProject GeorgiaUS}} needs to be replaced with Template:WikiProject Georgia (U.S. state) because the redirect appears to be causing categories not to be updated correctly.

The exact question in this is, can I go ahead and use my bot to replace these, using my prior approval of WikiProject template replacement BRFA, to make these changes? There are a about 3000 articles affected but many of them have other problems in addition to this one change. --Kumioko (talk) 16:14, 12 January 2012 (UTC)

Couldn't a sysop just purge the template/redirect? It's probably just gotten lost from queue. —  HELLKNOWZ  ▎TALK 16:17, 12 January 2012 (UTC)
This is just the job queue and occurs for many different things. They should just be left alone as it will update in time. Null editing (or in this chase changing the redirect) to avoid the job queue defeats the purpose of the job queue. That being said I null edited the template/redirect itself to see if that helps. -DJSasso (talk) 16:19, 12 January 2012 (UTC)
Yep. Category:Georgia (U.S. state) articles needing images is cleaning itself up. —  HELLKNOWZ  ▎TALK 16:24, 12 January 2012 (UTC)
Yes you are correct they could and that might help and thank you for doing that but if we weren't using a redirect then this wouldn't happen. You are correct, the queue does it for many things and a very large percentage of those are template redirect malfunctions, because redirecting code (templates) regardless of what some might want the not so tech savvy masses to believe, has 2nd and 3rd level effects that can adverselly impact other things. Sometimes they don't update categories, sometimes they don't work quite right, sometimes they don't work at all, sometimes they work in WP but not in a mirror site or something like Facebook for instance, etc.. The bottom line is we shouldn't be treating a template redirect in the same manner as an article redirect. I also don't like the comment that it will update in time, no offense intended but Godzilla used to be a little bitty lizard and look what happened to him/her over time. They became a really big problem that wreaked a lot of havoc and got into a lot of mischief before it was stopped. Frankly I don't know how long this problem has existed but I know that both that template and its redirect have been in place for a long time. How many more are there out there that aren't updating or functioning? I don't think anyone knows. --Kumioko (talk) 17:41, 12 January 2012 (UTC)
Actually it would have happened redirect or not. It wasn't the redirect that caused it, it was the move itself that caused it and put it in the job queue. Pretty much none of the things you mention actually happen when redirecting a template. The only issue that you can have with redirects of templates is if the old template had different parameter names than the new template. And usually most people fix those when redirecting a template. I think you have a fairly big misunderstanding of how template redirects work. Yes sometimes the job queue loses some tasks but that is fairly rare and not really because of of the redirect itself. As for how many others out there aren't functioning right now....if people haven't noticed then there probably isn't a problem or people would complain or look into it like in this case. -DJSasso (talk) 17:53, 12 January 2012 (UTC)
This "problem" has existed since job queue was made. Indeed, this wasn't the redirect that caused it. My guess is the job queue got borked up and flushed its entries (so this would have affected articles, categories, and user talk pages equally that needed an update at the time). —  HELLKNOWZ  ▎TALK 18:13, 12 January 2012 (UTC)
Exactly it would have affected anything that was waiting to refresh in the job queue when the job queue hiccuped. The only reason it looks like its a template redirect problem is because you can easily tell which pages never got their cache updated because they are "marked" via the redirect being there whereas looking at an article that was waiting to update you wouldn't have an easy way to tell you were still looking at the old cached version. However when the queue hiccuped it would have affected any article waiting in its queue not just template redirects . -DJSasso (talk) 18:17, 12 January 2012 (UTC)
No offense but however the redirect was created, its still a problem with a redirect and this redirect and template has been in existance for a long long time so it must have been like this for a while. Basically what I am getting though is that its a general bi product of the redirect process itself and not the type of redirect. Is that correct? And I completely disagree that just because knowone has caught it means it isn't a problem. Job queue aside I have seen several occassions where template redirects didn't function including the reasons listed above and sometimes in relation to interacting with sister wiki sites. In some cases knowone could figure out why it didn't work saying "it should" but when the redirect was chaneged to the actual template the problem was mysteriously fixed. In one case they even said that it was a rare bug that had already been identified and wasn't worth bringing to light because the status quo quo of template redirects works most of the time. Additionally its confusing for inexperienced editors (sometimes even for the experienced ones) and hard to program when you have 50 variations of something to try and compensate for. You are right too about the template parameter problem, that is another issue in itself and again would usually be solved by simply not using a redirect. Oh well, no reason to dwell on it, this ones fixed so the problem is solved and we can all move on. Thanks again for the help. Just wondering but this seems to be a fairly common problem is there a way I can check the "Job queue" the next time this problem comes up; or better yet just check in periodically to make sure things aren't hung up? --Kumioko (talk) 18:21, 12 January 2012 (UTC)
Well, if you're really curious, you can check here and the job queue length on one of the three servers handling the queue will be reported. But you can't see what articles are in the queue, mostly because it'd be a.) hard on the servers, and b.) it wouldn't be of much use. — madman 18:27, 12 January 2012 (UTC)
Thank you thats good to know. --Kumioko (talk) 18:32, 12 January 2012 (UTC)
(ec) Yup you basically have it :) . Whenever something is done on the wiki that changes how multiple pages look or are referenced it will go into the job queue so that the cache of the page can be updated. (unless you are editing one single page which causes it skip the queue and happen immediately). So then each page affected by whatever you have done wait in line to have their cache updated one by one so as not to put a strain on the resources basically. What sometimes happens and probably happened was that when the template was moved. All of the pages it was used on were added to the job queue to be updated to the fact that the template was now redirected. At some point while they were sitting in the queue the queue had an issue and dropped all the pages from its queue. So any that hadn't yet been updated still had their old cache. Between now and then some have had their redirect "fixed" or some other edit on their page which then would have updated the cache. However, some have never been touched since the move happened so sat with their old cache until I basically shoved them back into the job queue by editing the template/redirect. The queue itself usually isn't all that big...but if someone has changed the look of some high use navboxes and the like it can get pretty long. -DJSasso (talk) 18:39, 12 January 2012 (UTC)
Thanks. --Kumioko (talk) 19:00, 12 January 2012 (UTC)

[edit] Kumi-Taskbot and collapse parameters

I'm bringing this issue here because repeated requests to Kumioko (talk · contribs) to stop removing collapse parameters. This still continues and I don't see anywhere in Kumi-Taskbot approvals that collapse parameters should specifically be removed. It happened most recently today after I had asked Kumioko for the second time to knock it off. The original notice pointed out why the collapse parameter, when it has been set to either yes or no, means there is some reason for it's existence. For that matter, why would an unused collapse parameter bother someone so much that they have to systematically remove them? When an article has many project tags, collapsing the banner shell saves a lot of visual space. Looking at this same edit the only corrections made were to white space which I fail to see any approval for. This most recent behavior is only carried over from months of my commenting to Kumioko about what his AWB obsession has been doing to article talk pages and IIRC at one time Kumioko lost his AWB privileges for the very same reason of making mass inconsequential edits to article talk pages. Brad (talk) 02:36, 15 January 2012 (UTC)

Well fme, here are more issues:

Kumi-Taskbot is only approved for work with wiki project templates. Brad (talk) 02:50, 15 January 2012 (UTC)

I stopped removing the collapsed parameter after the second notice although I still contend that it should be removed. The collapsed parameter completely hides all of the WikiProject templates effectively making them invisible unless the user knows to go looking for them. Second, since I do not have access nor do I use IIRC, IMO, if the comments happened in IIRC about me or my bot, frankly they don't exist to me. I had no opportunity for comment nor discussion there. Thirdly, as with any bot there were a few glitches mostly do to the absolute and complete lack of standardization of the WikiProject templates that I had to work through. Which I would like to say are fixed but I continue to make adjustments for as I find them. --Kumioko (talk) 12:16, 17 January 2012 (UTC)
"IIRC" = "if I recall correctly". :) —  HELLKNOWZ  ▎TALK 12:25, 17 January 2012 (UTC)
Yeah I am not sure the collapsed=yes should be used. However I don't think it should be changed by a bot. The boxes are still collapsed without that parameter set...they just aren't completely collapsed so that the names of the wikiproject tags can still be seen. Collapsing them completely defeats the purpose of the tags. -DJSasso (talk) 14:06, 17 January 2012 (UTC)
Thanks H3llkn0wz for clarifying. I was thinking about IRC. To Djsasso, I already removed the code anyway. I am going to bring up the use of the collapsed parameter on the WikiProject bannershell for discussion and see where it goes. --Kumioko (talk) 14:33, 17 January 2012 (UTC)
And you still ignore the fact that you're doing work with your bot that has not been authorized. You removed the parameter from the FAQ template after I asked you to stop removing collapse parameters. There is a particular reason for setting |collapse=no on the FAQ template so that the questions stand out and can be seen. You only have authorization to work with project templates; not make white space changes or changes that you feel should be done. My politeness is wearing thin. Can you not just leave the f-articles alone? Brad (talk) 00:23, 18 January 2012 (UTC)
Well to answer the question at the end, yes I could, but that sorta defeats the purpose of having an online encyclopedia that anyone can edit don't you think? Your dwelling on a dead issue at this point. I already told you I stopped doing that edit. But just for clarification some of the edits that you seem to have trouble with are general edits generated by AWB. Not the collapsed parameter mind you but the white space edits that seem to be so troubling to you and the only reason they went is because I didn't check the little box in AWB that says skip if white space/minor edit. --Kumioko (talk) 00:35, 18 January 2012 (UTC)
It should be the encyclopedia that anyone except Kumioko using AWB can edit. Since you're a responsible bot owner I'm sure that by now you are planning to go around and replace the parameters you removed. I saw another one of your edits over at George Washington that clipped a working collapse parameter. I'll have to start putting that deny tag on more articles as I'm sure this won't be the last of your escapades. Brad (talk) 18:08, 19 January 2012 (UTC)
Well its ok that you think that, doesn't really matter to me that you personally don't like my edits, but its ok. I learned along time ago that you can't, and shouldn't try, to please everyone on here. Since I don't know precisely every edit that parameter was removed from, and in most cases it shouldn't have been there anyway, theres no way I can go back and fix them. My guess is that most of the ones you have a problem with relate to US Presidents so I might go back and check those over. If you see one I missed please let me know. --Kumioko (talk) 19:07, 19 January 2012 (UTC)

[edit] Blackout January 18th 05:00 UTC

As many of you know, English Wikipedia will be blacked out during January 18th 05:00 UTC - January 19th 05:00 UTC to protest SOPA and PIPA. As a result, editing via the API will be disabled (see here). This thread is not meant to air opinions on the blackout, but rather to gather information on how bots may be affected. Shubinator (talk) 06:19, 17 January 2012 (UTC)

Also, there's a related thread over at Wikipedia:Village pump (technical)#SOPA blackout. Shubinator (talk) 06:25, 17 January 2012 (UTC)
Bots that edit on a scheduled basis throughout the day (possibly read-only bots too, but it depends on implementation) will need to be able to handle related errors so that they don't crash and are thus available when the site reopens. --Rschen7754 06:25, 17 January 2012 (UTC)
The Toolserver Mirror will stay up, right? Tim1357 talk 22:19, 17 January 2012 (UTC)

[edit] Wolterbot cleanup

Since Wolterbot is dead with no indications it will return and we now have a toolserver tool to do the task can I use my bot to cleanup all the {{User:WolterBot/Cleanup listing subscription|banner=''Insert your favorite WikiProject here''}} cruft still left lying about the WikiProjects> --Kumioko (talk) 03:01, 23 January 2012 (UTC)

Since knowone seems to have any problems with this I will go ahead and submit a BRFA to get these cleaned up. --Kumioko (talk) 17:50, 24 January 2012 (UTC)

[edit] Call for Participation: Looking to Interview Bot Community Members

Greetings-

I am a graduate student at the University of Oregon, currently collecting data for my dissertation on Wikipedia editors who create and use bots and assisted editing tools, as well as editors involved in the initial and/or ongoing creation of bot policies on Wikipedia. I am looking for members of the bot community to interview regarding their experiences on Wikipedia and opinions of technical and governance issues on the site. The interview can be conducted in a manner convenient for you (via an IM client, email, Skype, telephone, or even in-person) and should take approximately 30-45 minutes.

Your participation will help online communication researchers like me to better understand the collaborations, challenges, and purposeful work of Wikipedia editors and programmers like you.

My dissertation project has been approved both by the Institutional Review Board (IRB) at the University of Oregon, and by the Research Committee at the Wikimedia Foundation. You can find more information on the project on my meta page.

If you would like to participate or have any questions, please contact me directly via email or by leaving a message on my talk page. Thank you in advance for your interest.

Randall Livingstone

UOJComm (talk) 00:05, 25 January 2012 (UTC)

I would urge those who can take part in this but haven't yet to do so if possible, it is an interesting project but the response rate, from what I understand, has been rather low. It really would help Randall if more people would reply, and he's made himself available on several ims, email, etc, shouldn't be too hard to answer a few email questions at the very least, if possible :) Snowolf How can I help? 00:10, 25 January 2012 (UTC)
Personal tools
Namespaces
Variants
Actions
Navigation
Interaction
Toolbox
Print/export
Languages