Open main menu

Wikipedia β

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).

Inactive bots - May 2018Edit

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 account indef blocked
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)


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

  Done bot flags removed and accounts marked as retired. Should these bots want to resume operations in the future a new BRFA will be needed. Thank you for your past bot-service! — xaosflux Talk 13:16, 26 May 2018 (UTC)
@Xaosflux: I haven't run my bot in a while, and I wouldn't mind it losing the flag temporarily and being marked (appropriately) as inactive. At the same time, I don't want to lose all my approved BRFAs. If I voluntarily give the flag up unrelated to these activity requirements, would I retain my approvals? ~ Rob13Talk 17:04, 26 May 2018 (UTC)
@BU Rob13: if it is foreseeable that you will ever resume a prior task there is no need to deflag so long as you are around - if your bot account was compromised or started running in error it is expected you would be able to participate in remediation. If you really want the flag removed we would certainly do it, but it isn't really helping anything. — xaosflux Talk 17:16, 26 May 2018 (UTC)
I guess it's more a security thing from my perspective, but if you don't see a need, no worries. ~ Rob13Talk 17:17, 26 May 2018 (UTC)
As to your other question, asking for your currently inactive bots flag to be removed would not expire out all of your prior authorizations, but should you then later become inactive for 2 years it would (and it would actually be much harder to track). This process is primarily built around marking out retired bots where the operator never specifically asked for retirement and just left the project instead. Feel free to block your bot account as well if you want to. — xaosflux Talk 17:19, 26 May 2018 (UTC)

Appearance of Template:NewbotEdit

A few weeks ago, I tweaked {{Newbot}} to actually be readable and stand out from the bot op links found immediately below. Primefac reverted this just a while ago.

The old/current (since this was reverted) looks like this:

Operator: Headbomb (talk · contribs · SUL · edit count · logs · page moves · block log · rights log · ANI search)

Time filed: 19:17, 26 May 2018 (UTC)


While the new/reverted version looks like this:

Operator: Headbomb (talk · contribs · SUL · edit count · logs · page moves · block log · rights log · ANI search)

Time filed: 19:17, 26 May 2018 (UTC)


This isn't something I want to edit war over, but I strongly feel the bigger version is better, with the links about the same size as the header, creating a stronger association with the bot. The emphasis should be on the bot links, not the operator links. What does everyone else think? Headbomb {t · c · p · b} 19:17, 26 May 2018 (UTC)

Why not make it normal font size? e.g

Operator: Headbomb (talk · contribs · SUL · edit count · logs · page moves · block log · rights log · ANI search)

Time filed: 19:17, 26 May 2018 (UTC)


Seems better to me - the 125% font size version is far too big, and the current version possibly too small Galobtter (pingó mió) 20:00, 26 May 2018 (UTC)
I prefer bigger, but I could live with the 100% version. Headbomb {t · c · p · b} 20:02, 26 May 2018 (UTC)
The 125% version looks far too big to me. Personally I think the current version is fine, but the 100% version isn't horrible. Anomie 22:12, 26 May 2018 (UTC)
125% looks too big and it's questionable why we need custom formatting -- is someone somehow failing to find these? 100% is fine. Though I never had any issues with the original one. —  HELLKNOWZ   ▎TALK 22:20, 26 May 2018 (UTC)
Alright, since everyone seems fine with the 100% version, let's go there. Headbomb {t · c · p · b} 22:23, 26 May 2018 (UTC)
  • Any of them are fine for me. — xaosflux Talk 23:14, 26 May 2018 (UTC)
  • 100 or smaller is fine by me. Primefac (talk) 23:19, 26 May 2018 (UTC)
  • First preference: normal size for running text; second pref: slightly smaller than that but within MOS:ACCESS#Text; No-no: bigger text, or text smaller than permitted by MOS:ACCESS#Text. --Redrose64 🌹 (talk) 08:11, 28 May 2018 (UTC)
  • Not a fan of the 125% version, any of the others are fine. ƒirefly ( t · c · who? ) 10:53, 28 May 2018 (UTC)
  • I, for one, have been confused by the multifarious tiny links. I think changing to 100% for the bot links and keeping the small status quo for the operator's is a good change. Thanks to Headbomb for starting this conversation with a bold edit. – Jonesey95 (talk) 01:47, 29 May 2018 (UTC)

Removal of bot permissions from User:HasteurBotEdit

I'm retiring, permanantly after repeated abuses by editors and admins of "requests" that are being forced in as policy. I'm retiring because of out of order closes and patently wrong decisions. As such I request that HasteurBot be de-flagged as a bot. Hasteur (talk) 16:06, 3 June 2018 (UTC)

  Done should you return just file a new WP:BRFA if you would like to reactivate. — xaosflux Talk 16:34, 3 June 2018 (UTC)

User:Legobot stopped indexing my talk pageEdit

Legobot has stopped indexing my talk page. See the time stamp at User talk:Tyw7/Archive index --Tyw7  (🗣️ Talk to me • ✍️ Contributions) 21:18, 9 June 2018 (UTC)

Spam post. --Redrose64 🌹 (talk) 19:35, 10 June 2018 (UTC)
Is the bot even doing Task 15 aka taking over User:HBC Archive Indexerbot? I've searched Wikipedia and it seems it stopped indexing around 2016. --Tyw7  (🗣️ Talk to me • ✍️ Contributions) 19:52, 10 June 2018 (UTC)
@Tyw7: As I pointed out at User talk:Redrose64#Legobot index you have sent basically the same message to at least six different discussion pages, in clear contravention of WP:MULTI. For any bot problem, your first contact should be the bot's talk page; since your problem is with Legobot (talk · contribs) its talk page will be User talk:Legobot, where you have already posted. If no reply is forthcoming, the next place to leave a message is the talk page for the operator of the bot; the botop may be identified from the bot's user page; User:Legobot shows that the botop is Legoktm (talk · contribs), whose talk page is User talk:Legoktm. --Redrose64 🌹 (talk) 19:44, 11 June 2018 (UTC)

And I have already done that but received no reply. I think User:Legoktm might be busy, so so the next logical posting will be on this board which is for bot related issues. I posted on your talk page cause I thought you knew about the bot since you commented on other person asking question about Lego bot. And I thought perhaps you can help me out in case I have set up the bot incorrectly.

I posted on Herem page cause I mistakenly thought he was the joint owner for the bot and thought he could help out. I will wait until Legoktm replies to the thread left on the bot's help page and kindly redirect any further discussion to User_talk:Legobot#Bot_no_longer_indexing_my_talk_page--Tyw7  (🗣️ Talk to me • ✍️ Contributions) 20:39, 11 June 2018 (UTC)

Hi @Tyw7: Other then looking at the situation, there isn't much we can actually do here. If a bot is making bad edits and the operator is unresponsive we would certainly step in and do something about it. In your case, edits are not being made at all. A look at these pages suggests the task is still operational in general: 1, 2, 3; however a review of the last 30000 edits Legobot made in the user_talk namespace do not show any of this task activity for user_talk since June 2017, the very last edit being to User talk:Tommyang/Archives/2017. At this point it is solely up to Legoktm if they would like to address this. — xaosflux Talk 13:21, 12 June 2018 (UTC)
@Xaosflux: On a side note, do you know of some other bots doing the same or similiar task? --Tyw7  (🗣️ Talk to me • ✍️ Contributions) 15:35, 12 June 2018 (UTC)
Hi @Tyw7:, it doesn't look like anyone else is doing this from my searches, found an expired attempt in Wikipedia:Bots/Requests for approval/Demibot. You could ask someone to build this over at Wikipedia:Bot requests. — xaosflux Talk 19:42, 12 June 2018 (UTC)
Done. Wikipedia:Bot_requests#Indexing_talk_page. If any bot makers up to the task, much appreciated. --Tyw7  (🗣️ Talk to me • ✍️ Contributions) 20:08, 12 June 2018 (UTC)
@Tyw7: Just wanted to thank you for all your "leg work" on this issue. Cheers, - FlightTime (open channel) 15:44, 15 June 2018 (UTC)
@FlightTime: Weirdly enough it has indexed Talk:Anatolia according to User_talk:Legobot#Mask_problem_in_Indexerbot_config --Tyw7  (🗣️ Talk to me • ✍️ Contributions) 16:23, 15 June 2018 (UTC)

Request suspension of KasparBot "deletion of persondata" message task until isuses resolvedEdit

Hi, three times now I've had User:KasparBot post messages on my talk page telling me that I have made an edit to add the {{persondata}} template, which is a deprecated template. However, all the edits are old ones from > 4 years ago when persondata was used, so for some reason or another the bot is incorrectly picking up those old edits. I posted twice on the bot operator's talk page, User:T.seppelt, both at least several months ago, yet got no response. Having had another such incorrect message today, and no response from bot operator, I request that the bot's task is suspended until it can be updated to ignore old edits. Thanks Rjwilmsi 08:11, 13 June 2018 (UTC)

Rjwilmsi, the reason you were notified (at least in this instance) was because the page was deleted in 2015 and restored earlier today. So before to day there was no {{persondata}} template, and today there was, so the bot went through the edits to find who added it. It's a weird glitch, but it's not any fault of the bot. Primefac (talk) 12:26, 13 June 2018 (UTC)
Thanks for explanation, though I find it unconvincing that it's a scenario that can't be handled - surely the bot should be checking the date/time of the edit? Rjwilmsi 12:54, 13 June 2018 (UTC)
Personally, I would rather the bot only notified people if the template was added recently (i.e. within the last month). Any further back than that there isn't much point in notifying. ƒirefly ( t · c · who? ) 13:04, 13 June 2018 (UTC)
  • Hello @Rjwilmsi:, in reviewing this I think this specific task should no longer be required, but it is extremely low volume - with only 20 edits all year that all seem related to deletion/rev deletion/long-spanning reversions. Will reach out to the bot operator to see about suspending this task - they are odd edge cases and in some instances legitimate, but not as useful as they once were. With primarily constructive tasks still running, blocking the bot (the only option we can really 'force' on it) doesn't seem like a good choice right now. — xaosflux Talk 13:10, 13 June 2018 (UTC)
    Operator user talk left; Operator email sent. — xaosflux Talk 13:13, 13 June 2018 (UTC)