This is an archive of past discussions. Do not edit the contents of this page. If you wish to start a new discussion or revive an old one, please do so on the current talk page. |
Archive 5 | ← | Archive 8 | Archive 9 | Archive 10 | Archive 11 | Archive 12 | → | Archive 15 |
Hi! Magioladitis ( talk · contribs) has been mass-editing lots of WikiProject templates using AWB. I asked him to stop and he did.
I don't have much background about how bots or computer-assisted edits should be done on Wikipedia, hence I'm posting here. Is there a process that should be followed for making these kinds of automated edits? It's very disruptive for people like me who have lots of articles on their watchlist, see the screenshot.
If this is the wrong place to discuss this incident, please let me know. -- intgr [talk] 16:36, 3 November 2015 (UTC)
MSGJ I did this User:Scott/Talk#WikiProject_template_redirects hoping for help on that and less disruption. As you may see we even lack the method avoid brute force in some cases. I even asked for a AWB FR: T117365. -- Magioladitis ( talk) 16:47, 3 November 2015 (UTC)
@ GoingBatty: -- Magioladitis ( talk) 16:47, 3 November 2015 (UTC)
Before the statistics I was working blindly. After MSGJ's complains,10 I moved only to the non-standard names. I can stop the task completely. -- Magioladitis ( talk) 16:50, 3 November 2015 (UTC)
@ GoingBatty: Thanks. I am good with that. Please keep it up. -- Magioladitis ( talk) 19:04, 3 November 2015 (UTC)
For information of interested parties, and related to the discussion above, I have today blocked Magioladitis for a week for repeated violations of the bot policy and AWB's rules of use. I welcome feedback on this action. — Martin ( MSGJ · talk) 13:29, 17 November 2015 (UTC)
Can Hazard-Bot be turned off, with regard to its continued cleaning out of the template sandboxes? It's been continuing its chore (certainly in X9, and I assume the others) for several days, twice a day, because Cyberbot-I is now cleaning, as noted previously. Dhtwiki ( talk) 04:21, 26 October 2015 (UTC)
It seems Lowercase sigmabot II is no longer operating; the bot is best known for its ability to immediately reinsert the sandbox header in the event that it gets removed; no other bot that cleans the sandbox, to my knowledge, does this. Can this functionality be incorporated into Cyberbot I? Just wondering. — k6ka 🍁 ( Talk · Contributions) 18:00, 25 November 2015 (UTC)
Can you move sections (February 2014 - present) into archives? Because it's too many. 183.171.178.188 ( talk) 14:34, 17 January 2016 (UTC)
Well, it's bit hard to go through categories one by one, it'd be better if I can load a category at once and roll on it. For what it's worth, my bot's had a mentionless history and has registered 2 complaints throughout it's running time and they were not even his fault (caused by putting the articles in the wrong stub category). Also, I've made a few changes, now it integrates with BannerShell and fixes alternate templates (Custom Module) instead of skipping them. -- QEDK ( T 📖 C) 09:52, 18 January 2016 (UTC)
Bots
which contains permission apihighlimits
. —
xaosflux
Talk 12:25, 18 January 2016 (UTC)This is getting quite embarassing too:
... failing (and still awaiting) an adequate response by the botop in question: are there any other bot owners that can explain a bit (at Jimbo's talk page preferably)? -- Francis Schonken ( talk) 12:06, 26 January 2016 (UTC)
SineBot ( talk · contribs) has not signed anything since last Friday. I have left a note on Slakr's talk but don't know if he's around to reboot it - can anyone else get hold of him? I'm sure I've said this before, but since this is such an essential tool, shouldn't the WMF be taking care of it? Ritchie333 (talk) (cont) 10:15, 26 January 2016 (UTC)
Magioladitis is blocked again.I have opened a discussion at Wikipedia:Administrators' noticeboard#Magioladitis to explore ways to resolve the issues. Anyone is invited to comment there. — Martin ( MSGJ · talk) 20:47, 28 January 2016 (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.
Is Murph9000 Bot ( talk · contribs) an approved bot? There is no entry "changed group membership for Murph9000 Bot from (none) to bot" at their logs, and I can't find a WP:BRFA. -- Redrose64 ( talk) 09:45, 1 February 2016 (UTC)
Looks like I came here too late to change anyone's mind, but I was just going to say that you could easily rename the account to something like "Murph9000 (Assisted)" and be done with it. The edits do not look problematic. The sig-cleaning wouldn't be an appropriate bot task, of course, but as only 30 edits done using some (admittedly unspecified, but I'm going to guess pywikibot) assisted program is not worth fretting over. Seriously.
— Earwig talk 19:50, 2 February 2016 (UTC)
Heads up: All your bots are (maybe) going to break (later). |
In a month or two, they're changing the login system for bots. You can read more here: phab:T121113 and https://lists.wikimedia.org/pipermail/wikitech-l/2016-January/084501.html
If you expect any problems, please reach out to mw:User:Anomie or mw:User:Tgr (only you have to be nice to Tgr, because he did me a favor last week. ;-) This was in Tech/News today, and it's easy to miss an announcement like this, so please also check in with your friends and other wikis and make sure that none of them will be surprised by this. Thanks, Whatamidoing (WMF) ( talk) 22:01, 18 January 2016 (UTC)
My bot broke yesterday ("There was an unexpected error logging in."). I presume this is related? — Steve Summit ( talk) 13:06, 22 January 2016 (UTC)
How is it even possible to login any more without HTTPS? See m:Talk:HTTPS#Bots for the scrambling I had to do after my bots were knocked offline by the mandatory switchover to HTTPS. Wbm1058 ( talk) 18:15, 27 January 2016 (UTC)
This highly technical discussion is mostly over my head, and I have no idea whether I need to change anything to keep my bots running. So far they seem fine and unaffected. This is not a good way to notify me, as I don't even have this page on my watchlist. I just happened to stroll by because of #Archivebot? below. If someone would take a glance at my bots' code and tell me if I need to change anything and if so, what I should change, I would be grateful. Thanks, Wbm1058 ( talk) 15:49, 27 January 2016 (UTC)
Error
|
---|
|
I moved my bots to use OAuth, to avoid any breakage in the change. Well now they're broken, and I don't think it's my fault. Using OAuth I get persistent badtoken error regardless of how many times I delete the bot's cookie. I have made no modifications, and other bot scripts that were working are now broken too.— cyberpower Chat:Offline 04:57, 5 February 2016 (UTC)
A request was posed on my user talk page to not have the bot clobber pages that are redirects when delivering the friendly notices for Wikipedia:Bots/Requests for approval/HasteurBot and Wikipedia:Bots/Requests for approval/HasteurBot 2. In the past I made changes that were reasonable to accomidate similar changes (ex: following the redirect and delivering the notice there) only to have some editors claim that I have exceeded what the bot was authorized to do so I'd like to ask the question here: Do I need to file a new BRFA to change the behavior in edge cases dealing with pages that hard redirect to a new location? Thank you for your consideration. Hasteur ( talk) 18:03, 21 February 2016 (UTC)
Legobot ( talk · contribs) is misbehaving, and is listing discussions that are either closed RfCs, or not RfCs at all. I have posted to its talk page, but with no response from Legoktm ( talk · contribs); and since the bot continues with incorrect edits, should I block the bot? -- Redrose64 ( talk) 00:10, 7 March 2016 (UTC)
{{
Rfc}}
, so that Legobot doesn't think that it's an open Rfc. --
Redrose64 (
talk) 20:15, 8 March 2016 (UTC)Hi everyone,
Ops is planning a major data center migration during the week of 21 March. From the POV of a bot owner, there are two major effects:
This is being announced in m:Tech/News and through the wikitech-l mailing list. phab:T124671 seems to be the central task. You can follow those for further updates (or {{ ping}} me). Please share this information with other projects and bot owners.
— Whatamidoing (WMF) ( talk) 16:28, 10 March 2016 (UTC)
Ops has just postponed this until the week of 18 April. Some backend services will migrate to codfw during the week of 04 April (maybe on the Thursday?). If your bot might rely on RESTbase, Parsoid, or other things like that, then {{ ping}} me and I'll see if I can find a list.
I hope that everyone survived the five-minute test yesterday with no problems. Whatamidoing (WMF) ( talk) 18:41, 16 March 2016 (UTC)
Wikipedia:Bots/Requests for approval/Hazard-Bot 33
How did this get approval without site-wide consensus such as from Village Pump? All the best:
Rich
Farmbrough, 20:07, 21 March 2016 (UTC).
This bot is causing spam to fill up "what links here". For example a new page created by me Columbjohn which has very little to do with architecture now has dozens of links to user pages due to this bot. Have never seen anything like it since 2010. Seems a totally useless bot to me, can it be stopped? I note the user has already been blocked. Thanks.( Lobsterthermidor ( talk) 21:35, 1 April 2016 (UTC))
Theo's Little Bot (run by Theopolisme) has been recreating some of the subtemplates that were slated for deletion in this TfD. It's just been recreating them as an error. The bot owner hasn't edited for a few months, but is anyone able to disable only this task? It seems unreasonable to monitor the bot for when it decides to recreate one of these. Example: Template:Rotten_Tomatoes_score/0118688. ~ Rob Talk 15:07, 19 March 2016 (UTC)
@ Xaosflux: I emailed Theo and he said the offending task has been disabled and the bot can be unblocked. I'll leave that decision up to your discretion. -- Closedmouth ( talk) 09:30, 4 April 2016 (UTC)
I just saw a bot revert an edit automatically and the edit summary was "Reverting possible vandalism by ## to version by ##. Report False Positive? Thanks,". And the core of it felt like "hey did I do the right thing? tell me? tell me?". The edit was very much justified but there's no way to give that feedback automatically. So I thought now that the "thanks" system is in place. Why not enable it so that one can thank a bot which provide automatic feedback for future automated reference or to strike pages of some internal checklist for manual review. A "no, bad bad bot" links will perhaps also be necessary to not bias the feedback data. Just an idea.. Bytesock ( talk) 20:52, 11 April 2016 (UTC)
This is your reminder that all the wikis will be in read-only mode for about half an hour at 14:00 UTC (about 15 hours from now). The announcements are at m:Tech/Server switch 2016 and on the blog. After we can edit again, I'll check WP:VPT for problem reports or advice. Don't forget that this will happen again on Thursday. Whatamidoing (WMF) ( talk) 23:20, 18 April 2016 (UTC)
The mess above suggests to me that we need to change bot policy as follows: No bot will be approved unless its code is publicly posted, on-wiki. If the code is removed or not current, the bot must stop until its posted. We currently have a malfunctioning bot, and an editor who would be willing to fix the code, but not to rewrite the whole thing. Requiring public code would prevent this problem for future bots. Oiyarbepsy ( talk) 05:02, 11 April 2016 (UTC)
Now wait one minute? Isn't a huge part of the Wiki-mission to encourage open-source content? How are we encouraging open-source content by allowing close-source code to run our software? Oiyarbepsy ( talk) 05:26, 11 April 2016 (UTC)
Authors of bot processes are encouraged, but not required, to publish the source code of their bot.(which you've seen several editors oppose) and requiring BAG to decline BRFAs if they don't meet the requirement. Several bots have a secret sauce or a blend of 11 herbs and spices that makes them go, in which case they should not be published. As to requiring it to be published on wiki, that is a unbelivably bad idea short of the foundation/labs providing a version control bridge that interfaces with normal version control software and the "approved" storage. Hasteur ( talk) 20:08, 20 April 2016 (UTC)
Before the servers get to move one last time for now, it seems to bother many that ClueBot III is down since last February. And there seems to be no discussion here, although it is said that Cobi had been doing his job to try to fix the problem somewhere else. Any news? 49.148.27.180 ( talk) 14:00, 21 April 2016 (UTC)
On March 21, 2008 (yes that far back) and for a few days, User:CorenANIBot got into a odd task and copied it seemed the discussions from that day onto separate subpages. Some are just copies of the discussion, some have other people's edits there. One of those subpages is up for deletion at MFD here. -- Ricky81682 ( talk) 20:12, 21 April 2016 (UTC)
(crossposted from User talk:DumbBOT) This bot is incorrectly taking some categories by misposting some templates, see Category:Wikipedia files with no copyright tag as of 5 April 2016 and Category:Wikipedia files with no copyright tag as of 6 April 2016 for examples. It seems to be limited to the "files with no copyright tag" categories. It looks like the bot creator is no longer active but perhaps another editor can help resolve this problem. Liz Read! Talk! 15:18, 3 April 2016 (UTC)
One per day among 50 useful edits, some of which are important to the project. Maybe it would be beneficial for some bot-ops to start work to adopt the two remaining tasks (creation of daily subpages and removing protection templates from unprotected articles). In the meantime, an admin could preemptively salt Category:Wikipedia files with no copyright tag as of 8 April 2016 through Category:Wikipedia files with no copyright tag as of 30 April 2016 to buy us development time. ~ Rob Talk 00:14, 4 April 2016 (UTC)
BTW, there is also some discussion of these issues at the bot's talk page. Speedy deleting isn't enough, as Dumbbot will live up to its name and recreate the categories later. So, any creation protection also needs to apply to categories that have already been speedy deleted, at least until the date on the category has passed. Oiyarbepsy ( talk) 00:25, 11 April 2016 (UTC)
@ Tizio: WP:PUF has now been closed. Could you please have DumbBOT stop creating daily subcategories of Category:Wikipedia possibly unfree files? GeoffreyT2000 ( talk) 23:33, 9 April 2016 (UTC)
Forgot a ping, so adding it now: @ Nyttend:. Oiyarbepsy ( talk) 22:34, 10 April 2016 (UTC)
I'll hold off on blocks while this discussion continues - but we have a core issue that needs to be resolved: bot operators are personally accountable for all actions made by their bots, and this operator is absent. --
xaosflux
Talk 02:13, 11 April 2016 (UTC)
[End text copied from the bot's talk page]
Sorry for the inconvenience. I removed that page from the category creation bot function (yes, the list is merely a report of what the bot is doing). If someone wants to take over the whole function I will shut it down. Otherwise, in case of problem please email me, because I really cannot guarantee logging in often. I added such a notice to the bot's page. Not being an active user any longer, I do not think I should say anything on the policy about bots, just let me know if/when I have to shut it down altogether. Tizio 13:25, 11 April 2016 (UTC)
Test run - the bot created two categories: Category:Wikipedia files with no non-free use rationale as of 11 April 2016 and Category:Wikipedia files needing editor assistance at upload as of 11 April 2016. I believe these are ok, since categories for other days exist and are not empty. A wrong category may still be created this night (the bot runs on two computer, at the moment I can't access the secondary one), but should be the last one. Please let me know if there are some other category that is incorrectly created. Tizio 18:39, 12 April 2016 (UTC)
For some reason, User:Hazard-Bot created Category:Possibly unfree files from 2016 April 21 and Category:Possibly unfree files from 2016 April 20. Hazard-Bot began this "task" on the 17th and the prior ones have all be deleted. I've already informed User talk:Hazard-SJ but (a) when did we authorize two bots to do the same task and (b) is this another bots that will take on this task if we delete these? -- Ricky81682 ( talk) 20:11, 20 April 2016 (UTC)
Question's right up top. -- QEDK ( T ☕ C) 17:10, 2 May 2016 (UTC)
As documented at Wikipedia talk:Good article nominations#Legobot error?, we've positively identified a bug in the Legobot code that is supposed to pass good articles. The bug is: If a reviewer passes an article as GA and places the passed {{ GA}} template immediately above an earlier placed {{ failedGA}} template from an earlier review, the bot will become confused by the presence of both templates and will fai33l the GA rather than pass it. It happened again today at Talk:Gene Roddenberry. It happens nearly every day. When it happens, the successful nominator receives notice that the article failed instead of passed, and the GA icon is not placed on the article; it must be manually placed. A possibly separate bug: Sometimes the GANotice template is not placed on the nominators talk page at all. Pinging Legoktm; can you please help us. Side note: We're also wondering if you can help us add a few subtopics as documented at Wikipedia talk:Good article nominations#RfC: Subcategories on GAN page. Thank-you. Prhartcom ( talk) 22:28, 15 March 2016 (UTC)
Hi, I updated
Template:Bot topicon slightly, to allow specification of owner, icon customization, and custom id (for sorting). I also made
Template:Bot operator topicon with a new
LGPL image,
File:BotOp-logo.svg which also allows image/id customization and bot specification. —
Andy W. (
talk ·
ctb) 16:10, 9 May 2016 (UTC)
Please report here any unusual errors if your bot runs in to the "welcome" message trying to make an edit. Trying to track any of these down. — xaosflux Talk 20:27, 19 May 2016 (UTC)
Ladies/Gents - I know you're sitting at home right now, probing Wikipedia, and looking for something to soften that boredom. You could work on an article about the 1968 Philadelphia Eagles season, but the tediousness of finishing the whole 1960s collection is just dragging on and on. Let me offer you a new opportunity! The Unblock Ticket Request System is looking to get some additional developers on board. Developers do not have to be administrators, but administrator tools will be required for SSH access and access to the live instance of the tool. Non-administrators can still develop with Github and will have access to UTRS-Alpha and UTRS-Beta. Specifically, we're looking for two associate core developers, a senior user experience developer, and a user interface developer. Specific requirements are listed on the link above, but we're looking for experience with HTML5, PHP, jQuery, CSS3, and bootstrap. Additional cross-platform experience, team management, object oriented design, and secure systems development experience is a huge bonus. Please send an application to utrs dash developers AT googlegroups dot com. We have big ideas and big plans for a v2.0 of the system and we're looking for some folks looking to do exciting work.--v/r - T P 03:14, 23 May 2016 (UTC)
It has been agreed that categories must be empty for seven days (not four) before being speedy deleted. If you have any bots or other automated processes based on this, place make the appropriate changes. Oiyarbepsy ( talk) 04:51, 24 May 2016 (UTC)
Please ensure your bots are using HTTPS: links to access APIs of Wikimedia-hosted production wikis! Wikitech-l announcement email with deeper details (also cross-posted to mediawiki-api and mediawiki-api-announce): https://lists.wikimedia.org/pipermail/wikitech-l/2016-May/085618.html -- BBlack (WMF) ( talk) 22:43, 13 May 2016 (UTC)
All AWB API requests are HTTPS unless forced otherwise. No AWB bots will break. -- Magioladitis ( talk) 12:34, 20 May 2016 (UTC)
I'm worried about this list of users, whose bots or scripts are actively using http:// and whose owners look hard to contact:
I'm going to leave messages on the named talk pages, but I'm not expecting much of a response. Several of these editors haven't edited for months. If anyone knows anything about these bots, please {{ ping}} me. Whatamidoing (WMF) ( talk) 18:20, 20 May 2016 (UTC)
If anyone's getting a "500 Can't verify SSL peers without knowing which Certificate Authorities to trust" error, then there's a possible solution at WP:VPT. Whatamidoing (WMF) ( talk) 23:03, 20 May 2016 (UTC)
@ Whatamidoing (WMF): RE: I don't bot op as much as I used to. Can you please tell me (or direct me to) what requests are coming through regular API and I will try to make improvements on it. Or better yet guide me as to where I can self service my requests. Hasteur ( talk) 18:04, 20 May 2016 (UTC)
g13bot_tools-g13_interested_notify.py/r-1 (unknown) Pywikipediabot/1.0
and g13bot_tools-g13_nudge_bot.py/r-1 (unknown) Pywikipediabot/1.0
, and seem to originate in toollabs exec nodes. All the requests were for enwiki APIs. --
BBlack (WMF) (
talk) 19:18, 20 May 2016 (UTC)
Aw crap. What a pain in the ass. Hawkeye7 ( talk) 13:26, 24 May 2016 (UTC)
A relatively small matter, but unfixed and replicated across a lot of articles it could be a much larger one. At Zahi Hawass three edits in a row in three days were by bots. Yobot made a change. GreenC bot undid the change (and did something else), Yobot redid the change. Clearly not both reading from the same style book. Neither actually fixed the problem which is a comma next to a full stop, which maybe means this will not happen elsewhere. But when doing general fixes they should be following exactly the same rules otherwise this could happen again in other ways.-- JohnBlackburne words deeds 08:32, 7 June 2016 (UTC)
This seems to be more of a WP:COSMETICBOT problem with Yobot.
JohnBlackburne and Xaosflux My specific bot's edits are part of CHECKWIKI (error number 61 Reference before punctuation) and are done per Manual of Style. More specifically per WP:REFPUNCT. GreenC bot has to take care of punctuation to be BEFORE references. Take not that Yobot's edit changes the visual outcome so it si not cosmetic. Correct punctuation was/is a criterion of creating good articles. Error 61 is fixed by Yobot since June 2010. -- Magioladitis ( talk) 11:04, 7 June 2016 (UTC)
Aha. JohnBlackburne beats us all :) There was a punctuation duplication causing the error. JohnBlackburne fixed it. -- Magioladitis ( talk) 11:05, 7 June 2016 (UTC)
GreenC bot doesn't mess with punctuation. What happened is GreenC bot inadvertently reverted Yobot's edit. GrenC does so much IO it takes a long time, so it runs off-line generating a diff. When that diff is later uploaded (via AWB) it checks the article size to see if there were any changes and re-runs real-time if there are. Since the changes made by Yobot did not change the article size that is the problem. So what I need is a better way to check for a diffs than article size (duh). That will be no problem, sorry for the revert. -- Green C 12:49, 7 June 2016 (UTC)
I am posting this issue here because I am uninformed of our bot policy and would like more informed editors/admins to take a look at this. I have an outstanding request that I am working with @ BU Rob13: at Wikipedia:Bot requests ({{ WikiProject Green Bay Packers}} Banner is the relevant section). @ Magioladitis: (i.e. User:Yobot) seems to have hijacked our conversation and begun editing without any approval from me, Bu_Rob13 or WP:BAG. Please note that the bot's only contributions so far have been cosmetic, such as this. Check the bots contribution history and see how almost (if not all) of the edits so far have been cosmetic. Please note the conversation at User talk:Yobot. If anyone could advise on the proper actions, I would appreciate it. « Gonzo fan2007 (talk) @ 18:03, 8 June 2016 (UTC)
BU Rob13 I am working on providing a custom module for general use instead of F&R rules because till now you use the latter and the result was duplicated parameters. Anyway, no big harm. I had no indention to hijack the discussion. I left my comment on the assessment of namespaces already in the BOTREQ. My apologies. -- Magioladitis ( talk) 18:26, 8 June 2016 (UTC)
Let's don't have this discussion in many places. I can't reply in all places. All tagging bots I know till now use AWB general fixes and some custom module in addition to F&R rules. In the past some bad settings had caused broken templates/broken parameters etc. So, I always try to keep the custom modules others use up-to-date. I usuallly do this before other bots are about to perform a bot run. IT is the same reason I commented in the BOTREQ about the auto-class set for other namespaces. I apologise if this seemed as hijacking. I'll leave the discussion to you. -- Magioladitis ( talk) 18:39, 8 June 2016 (UTC)
As is required by the BAG membership procedure I am placing this notification at WP:AN, WP:VPM, WT:BOT, and WP:BON. I am requesting to join the Bot Approvals Group and my request can be found here: Wikipedia:Bot Approvals Group/nominations/HighInBC. HighInBC Need help? {{ping|HighInBC}} 20:24, 2 July 2016 (UTC)
A bot has tagged an in-use sound file as an "orphaned image" [3] when it is in use at Antidisestablishmentarianism (word)) providing the US pronunciation. The file is also the target of a redirect. Is there a general problem? Last time there was large scale error-prone orphan file tagging it led to files being deleted as "unused, no foreseeable use" even when they were in use. Thincat ( talk) 15:19, 4 July 2016 (UTC)
{{
Orphan image}}
to better explain its use in assisting maintenance/compilation of site statistics, and the particular
type of links the bot looks for. Furthermore, I have implemented
exclusion compliance in
FastilyBot's task
10 (sorry I forgot :o), so that users are free to opt out for files they have uploaded. I hope this addresses Thincat's and Adam's concerns :) -
FASTILY 21:19, 4 July 2016 (UTC)
fileusage
, which I agree, is different from
linkshere
. It is, however, by no means the deletion tag you're claiming it to be. I am not responsible for the way other editors use and interpret datasets I build; if other users are behaving disruptively, then this is a matter for ANI, which does not concern me or this noticeboard. -
FASTILY 07:49, 5 July 2016 (UTC)
Not sure if this is the right place but here goes. On another wiki, I'd like to use a bot to update and standardize the name of fields on a particular template. Since I'm still learning how to operate bots, is there a bot whose source code I could use/adapt to perform such a task? Abjiklɐm ( tɐlk) 13:26, 5 July 2016 (UTC)
XLinkBot acts like a bot but does not actually have the "bot" flag. A bureaucrat should replace the "autopatrolled" and "extended confirmed user" rights of that user with the "bot" flag while leaving the "pending changes reviewer" right on. GeoffreyT2000 ( talk) 19:09, 12 July 2016 (UTC)
( edit conflict)It has been a specific choice not to flag XLinkBot, and I think it is overly bureaucratic (no pun intended) to enforce that all bots should be that way. Some bots, like the antivandalism bots, do edits that do need constant scrutiny (to quick react on bad reverts, but also to catch the vandals/spammer - if RC patrollers see the bot revert a really bad link, they might get the editor blocked early). It is pertinent that bots that do 'gnoming' type of work (maintenance, wikidata moves) do not show up in RC feeds (they quickly flood feeds, they can even flood watchlists), but antivandalism bots should standard show up in the feeds.
I see that for ClueBot NG flagging has not been discussed, they have just been flagged after the approval ( Wikipedia:Bots/Requests_for_approval/ClueBot_NG; approved on December 3, 2010, flagged on the same day). For XLinkBot this was discussed in the original request, see Wikipedia:Bots/Requests_for_approval/SquelchBot#Big_BAG_Section. Note that the bot's edits are 'manually' flagged in the edit-summary.
We could consider to give the bot the flag, and then de-flag the edits, but I don't see the advantage of that (it will just give me some programming work, and overall nothing changes ..). -- Dirk Beetstra T C 05:12, 13 July 2016 (UTC)
Okay, here's the list of bots and script-users that are going to start breaking on Sunday, 12 June:
New – these owners haven't been contacted yet:
Previously known – these owners have been contacted, but haven't fixed the bots (list generated ~30 hours ago):
If you know how to reach these users, please help us contact them. I know that people are working on a couple of these, but I haven't heard from most of the affected bot owners. In about 72 hours, Ops is going to start refusing 10% of the http:// requests; a month from now, they'll break completely. You can reach me on wiki or via Special:EmailUser if something's sensitive. User:BBlack (WMF) and his team take questions on IRC, too.
Thanks for your help, Whatamidoing (WMF) ( talk) 18:13, 9 June 2016 (UTC)
Xaosflux is correct: This is a global list, not solely for enwiki. The API's global, and the impending change affects all 800+ wikis – not just English-language ones and not just Wikipedias.
This is a list of "bots and script-users", regardless of whether the account has a bot flag. If you are using a custom AWB, Huggle, or similar script, then that is probably the cause. For that matter, any method of POSTing the API over http:// (e.g., to make null edits with a script, which results in some of the "zero contributions" accounts here) will put you on this list, because what you're doing will stop working soon. Whatamidoing (WMF) ( talk) 20:56, 9 June 2016 (UTC)
@ Bgwhite: are you aware that your bot is listed here? -- Magioladitis ( talk) 22:32, 9 June 2016 (UTC)
scripts-header_levels_labs.py/r11775 Pywikipediabot/1.0
. The access wasn't from a labs IP address, it came directly from a residential ISP service. --
BBlack (WMF) (
talk) 01:05, 10 June 2016 (UTC)
The latest list is here: phab:T136674#2394147. Whatamidoing (WMF) ( talk) 18:19, 21 June 2016 (UTC)
Continuing updates to recent lists of usernames still making insecure accesses are being posted every few days here: https://phabricator.wikimedia.org/T136674 -- BBlack (WMF) ( talk) 14:31, 24 June 2016 (UTC)
The API change is scheduled for tomorrow (less than 24 hours from now). If anyone has a bot that might not be fixed, then you might want to run it ASAP, to get one last run before you find out. ;-)
To recap from above, you can find general information in this e-mail message from May. The list of bots/script users that are known to be affected is listed at phab:T136674. If you need information to figure out which piece is going wrong, then the devs can give you a user agent string and similar details from the logs. Just let me (or BBlack (WMF)) know that you need more details.
Good luck, Whatamidoing (WMF) ( talk) 16:22, 11 July 2016 (UTC)
Template_talk:Emergency-bot-shutoff#ANI_notice might be of interest to editors who stalk this page. → Σ σ ς. ( Sigma) 05:36, 21 July 2016 (UTC)
I have blocked
BattyBot (
talk ·
contribs) as an emergency because it seems to be going over large amounts of articles changing {{
main}}
to {{
main article}}
for no obvious reason
random example. If somebody can explain what's going on, I'll unblock.
Ritchie333
(talk)
(cont) 19:01, 18 August 2016 (UTC)
B-bot's first task is to tag non-free images which are orphaned for deletion. When processing these deletion requests I did decline two requests
File:Playdead logo.gif and
File:Careers360 Logo.png because I had doubts about their copyrightability and listed them at FFD instead. B-bot keeps tagging them though despite a {{bots|deny=B-bot}}
tag. I did ask on
B's talk page about this but they don't seem to be very active. Is there a way to stop the bot tagging?
Jo-Jo Eumerus (
talk,
contributions) 12:02, 12 July 2016 (UTC)
Hi there,
What do you think about this edit (and the corresponding to the article's talk page). I find access dates by finding the earliest occurrenceof the url in the article. Is that a good idea? What are the standards for bots that add archives? -- Tim 1357 talk| poke 02:45, 23 September 2016 (UTC)
FYI: There is/was an API outage today, see Wikipedia:Village_pump_(technical)#503_errors.2Fpossible_Twinkle_issues. — xaosflux Talk 16:20, 17 October 2016 (UTC)
As of this edit, It looks like that the two bots have different "opinions" on what a blank template sandbox should look like.
To me, one of the bots should either stop patrolling the template sandbox, or stop doing the task completely if the bot task only patrol that page. NasssaNser ( talk/ edits) 04:07, 22 October 2016 (UTC)
As its maintainer's talk page witnesses, User:InternetArchiveBot is currently not working very well. As the recent error reports have not been answered and the bot is still making edits, would it be useful to block it? − Pintoch ( talk) 16:36, 22 October 2016 (UTC)
C678 how was the 0.1% estimated? -- Magioladitis ( talk) 23:02, 24 October 2016 (UTC)
Good afternoon! When bot edit pages frequently get the error: "The modification you tried to make was aborted by an extension hook". How can it be called? Игорь Темиров ( talk) 13:40, 29 October 2016 (UTC)
As bot operators, you might want to follow these discussions
Headbomb { talk / contribs / physics / books} 16:23, 29 October 2016 (UTC)
There is a new adminbot request open at WP:BRFA. Please see Wikipedia:Bots/Requests for approval/MusikBot II for details. — xaosflux Talk 04:16, 1 November 2016 (UTC)
https://en.wikipedia.org/?title=Taser&diff=737265819&oldid=736467529 is tagged GreenC bot and (WaybackMedic 2).
Per
this discussion and
this one on the Village pump (technical), I have raised the possibility of removing
Template:Fa top's invocation of the metadata
class, which in mobile view has the declaration display:none;
, from the div
section. This will allow the featured log to be viewed in the "mobile view". However, there was some fear that it might break a bot. The FACBot is okay, and I'm not aware of any other bot that accesses these pages, but it's best to ask first rather than proceeding and seeing what breaks. (Notifying
Ian Rose and
Bonvol:)
Hawkeye7 (
talk) 20:14, 1 November 2016 (UTC)
{{
webarchive}}
mergeA question has come up at
User_talk:GreenC_bot#GreenC_bot if the bot should honor the configuration of the original {{
wayback}}
template or {{
dmy}}
. There are good arguments either way, I felt honoring {{wayback}}
was the safer course of action as the only purpose of the bot is merger, not creating a new date format change. The bot has now been shut down twice by
User:Me-123567-Me who also took it to ANI so I'm starting this thread for discussion. I'm willing to make this change, it's not difficult, but it may have unintended consequences and the bot was not approved for it. --
Green
C 22:21, 15 November 2016 (UTC)
{{
wayback}}
template, if it has an explicit df parameter. If not, it must honour the date format specified in the {{
dmy}}
template.
Hawkeye7 (
talk) 23:20, 15 November 2016 (UTC)
Done. 50069 articles originally edited, 10125 had a {{dmy}}
and 849 articles fixed (
example). --
Green
C 19:29, 16 November 2016 (UTC)
The bot maintains both Peer Reviews and Good Article Reassessments. It hasn't been active since November 4 and both PR and GAR hasn't been updated since. The people operating it have said they don't maintain the bot ( CBM, Ruhrfisch). Is it possible to get someone to make a new bot or assume control of the bot to fix this situation? GamerPro64 04:33, 24 November 2016 (UTC)
I wrote a tool for myself, found it pretty useful so cleaned it up and posted on GitHub in case anyone might be interested.
It's a unix command-line tool to retrieve lists of article names, such as all pages in a category, backlinks of a template, pages edited by a user during a certain period, etc.. it's generally useful for work with AWB or bots, but probably other things as well in a unix environment. Only dependency is GNU awk and one of wget, curl or lynx.
https://github.com/greencardamom/Wikiget
-- Green C 01:41, 26 November 2016 (UTC)
The following bots appear to be inactive, have no planned future tasks, and have inactive operators.
Baring any objections, I propose to mark these bots as retired and deflag them. They may be reactivated with a future BRFA A longer list will be coming, but wanted to put these initial example out to see if there is any community objection to this approach. — xaosflux Talk 17:14, 25 November 2016 (UTC)
Please see Wikipedia_talk:Bot_policy#Activity_requirements for a proposed amendment to the bot policy. — xaosflux Talk 19:21, 3 December 2016 (UTC)
The following bots appear to be inactive, in that they have no edits for 5 years. In some special cases this may be due to a read-only bot that only exists for highapi read access. There are many reasons these could be inactive: tasks may have been moved to other accounts, all one-tasks were one-time and completed, operator may have left wikipedia, etc.
Extended content
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Bots that have not edited since 2010 as of 26 November 2016 (UTC). [ ]
|
I propose marking this bots as retired, and removing their bot flags. All operators will be attempted to be contacted via user talk and can indicate that they want to maintain their bot flag by signing the table. Any bots retired in this manner will be consider de-authorized, but may be reactivated in the future following a successful BRFA. The bot policy does not currently have a provision for activity requirements, but assuming this process has support I will propose a policy update to reflect practice. — xaosflux Talk 14:23, 26 November 2016 (UTC)
We 've done this before. So.. proceed! -- Magioladitis ( talk) 22:56, 26 November 2016 (UTC)
Hello! I have offered to help with the WP:BRFA backlog as a bot approver. This procedural notification is to make the community aware that a formal request is open for your consideration. Your input is welcomed at Wikipedia talk:Bot Approvals Group#BAG Nomination: MusikAnimal. Regards — MusikAnimal talk 00:55, 9 December 2016 (UTC)
Here is another batch of bots, these ones have never made an edit so were missed in the prior report. All have operators have not edited in 5+ years. Operator talk messages being left. Barring any objections, will mark as retired and deflag in a week:
— xaosflux Talk 18:00, 3 December 2016 (UTC)
I know there was (at least) one bot for searching copyvios. Does anyone know which is that bot? XXN, 11:48, 14 December 2016 (UTC)
Hi, is there a mechanism or bot approval for work across all language wikis? I recently answered a request for some low-volume high-accuracy non-controversial changing URLs for example sound.westhost.com to sound.whsites.net .. these URLs exist on other language wikis and should be fixed, but I don't have bot approval there (I don't think?). For example DE has about 8 and FR has about 4 etc.. it's too much work to go through each language manually, and not worth the effort to apply for bot approval in every language that needs it for this one task. -- Green C 15:50, 14 December 2016 (UTC)
Hi everyone. I am currently requesting to join the Bot Approval Group, and notification on this page is required. Feel free to comment here if you would like to ask questions or discuss the request. Wugapodes [thɔk] [ˈkan.ˌʧɻɪbz] 23:57, 18 December 2016 (UTC)
A bot approvals group member reconfirmation discussion is now open at Wikipedia:Bot Approvals Group/nominations/Magioladitis 2. Please feel free to review and comment. Thank you, — xaosflux Talk 13:25, 20 December 2016 (UTC)
Per the bot policy, a request to review Yobot's tasks for continuing authorization has been brought up at: Wikipedia_talk:Bots/Requests_for_approval#Request_to_modify_Yobot_authorization. Please review and comment if you are interested. Thank you, — xaosflux Talk 13:33, 20 December 2016 (UTC)
Please see Wikipedia:Village pump (policy)#Removal of data, and Wikidata, which suggests a change to bot policy. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 13:29, 12 January 2017 (UTC)
A couple of years ago, I learned to use Macro Express at work (it's a simple keyboard-and-mouse macro), and having need for the same functionality, I bought it a few days ago. Even when I was using it frequently, it often made seemingly random mistakes, so even in my own offline work, I tend to instruct it to wait for an "okay" from me before it saves anything.
I've thought of using it when doing some editing here (e.g. if I've uploaded a bunch of photos that should be added to articles, I set up a macro to copy the files onto the relevant articles), using the following process: the script loads a page, performs the specified modifications to the code, prompts me to approve or reject the edit, and (if I approve it) hits "Save changes" and goes to the next page, or (if I reject it) the macro stops until I reactivate it. I'd like some input:
I don't think you'd have a way of noticing anything unusual with what I'm thinking of doing, unless you checked my contributions and observed that the edits are going too fast to be manual; that's the only reason, aside from a desire to abide by relevant policy, that I'm bringing this up. Thanks for your input! Nyttend ( talk) 00:46, 2 January 2017 (UTC)
It looks fine to me. -- Magioladitis ( talk) 01:42, 2 January 2017 (UTC)
Anyone tempted to use this kind of software might like to look at AutoHotkey, a similar, but free, utility for Windows. I have blogged about one aspect of its use, but it's far more powerful than that suggests. I've also just started Wikipedia:AutoHotkey to faciliate discussion. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 13:46, 12 January 2017 (UTC)
I've updated the WP:BOTISSUE section of our bot policy. I don't believe the changes to be controversial, but discussion of the changes is certainly encouraged at Wikipedia_talk:Bot_policy#Changes_to_.27dealing_with_issues.27_section. Headbomb { talk / contribs / physics / books} 16:18, 20 January 2017 (UTC)
Before posting at WP:BOTREQ, is there an easy way to see if a bot already does a task?
I have in mind a bot that would tidy up something specific in mainspace (spot duplicate use of citations and tidy them with a refname labelled on the first use) and I don't know how to check if one exists already and I'm not sure it's a great idea to experiment in mainspace to test if it'd get fixed!
Help gratefully accepted.
-- Dweller ( talk) Become old fashioned! 10:18, 26 January 2017 (UTC)
Cydebot is removing links to deleted categories from userpages and archives despite the fact that it does not have permission to do that. Cyde is rarely onwiki. talkpage contribs ((( The Quixotic Potato))) ( talk) 03:01, 28 January 2017 (UTC)
For what it's worth,
Wikipedia:Categories for discussion/Administrator instructions currently says (step 6.6) Go to the old category and check "what links here". If there are links to it within templates, articles, redirects or other category pages, then edit these to link to the new name instead, or remove the links, as appropriate. ... Also update manually-edited pages such as "Categories" sub-pages of portals and active WikiProjects, but ignore "article alert" subpages, user pages and talk pages.
(emphasis added).
In 2008,
that same page said (step 7.3) All references to the category in articles (and other pages) must be changed to the new name, or removed, as the case may be
. So in 2008, when Cydebot was approved for "Automatic implementation of category deletions as a result of listings on Wikipedia:Categories for discussion/Working", it was following the 2008 instructions.
The latter version was
modified in 2011 to add "Article alert" subpages, user pages and talk pages can generally be ignored.
I was unable to find a corresponding discussion in the talk page archive for that page, but it may have happened somewhere.
It seems possible that the bot was approved following the old instructions, and then the instructions changed. It is unclear whether there was consensus for that change in the instructions. – Jonesey95 ( talk) 15:52, 28 January 2017 (UTC)
list it under the appropriate section of Wikipedia:Categories for discussion/Workingwhich triggers this very bot to do its thing. Anomie ⚔ 17:10, 28 January 2017 (UTC)
So after reading this lengthy debate, my curiosity was roused to see what all the fuss was about. Wikipedia:Categories for discussion/Log/2016 December 23 seems to explain it. A whole bunch of "Wikipedian who..." categories were deleted because they are in poor taste and inappropriate for an encyclopedia. Wikipedian Jedi Knights that poop with a demented sense of humor, etc. – I'm glad they're gone. What would the point be to just turn the blue links to red? These were all deemed to violate WP:USERCAT. Potato, good bot operators are a rare and precious commodity, and shouldn't be bothered with such concerns. wbm1058 ( talk) 03:56, 1 February 2017 (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've made a proposal on the ARBCOM workshop page concerning how to deal with the Magiodilitis situation. Input by WP:BAG, bot owners, and the community at large is welcomed. Even if the proposal doesn't pass, some other ideas can be of interest, especially to WP:AWB/ WP:CHECKWIKI people. Headbomb { talk / contribs / physics / books} 13:22, 3 February 2017 (UTC)
Wikipedia:Exclusion compliant, currently a redirect to Template:Bots, has been nominated for deletion at Wikipedia:Redirects for discussion/Log/2017 February 5#Wikipedia:Exclusion compliant. You are invited to comment at the linked discussion. Thryduulf ( talk) 00:36, 6 February 2017 (UTC)
The new mw:Developer Wishlist is in the voting phase. I believe that all bot coders are considered 'devs' for the purpose of voting rights, so many of the regulars on this page qualify.
This focus of this wishlist is on things that make it easier to be a MediaWiki developer – stuff for coding/reviewing/developing, not stuff for editing Wikipedia. If there are any proposals there that would make your bot work easier, then please vote for them. Whatamidoing (WMF) ( talk) 18:56, 8 February 2017 (UTC)
While I'm here anyway: remember m:Tech/Server switch 2016? It's probably going to happen in April, with 14+ days between the two editing interruptions. This is super-early notice, so it may be delayed (it will not happen any sooner), but please make a note that there's a chance that bots will need to be re-started. The official schedule will probably be on the same page as last year, at wikitech:Switch Datacenter. Whatamidoing (WMF) ( talk) 21:14, 8 February 2017 (UTC)
Please see User talk:Legobot#Misconversion of diacritics. -- Redrose64 🌹 ( talk) 12:35, 16 February 2017 (UTC)
A week or two ago, we wrote this little handy guide for WP:BAG members. It mostly details best practices, and act as a general resources for BAG members. BAG members had a chance to give its opinion on it, but bot owners (and the community at large) are certainly welcomed to suggest improvements to the guide, or point out some things that might be relevant to BAG members that we don't already mention. The discussion can be joined at WT:BAGG.
Thanks for any feedback you might have. Headbomb { talk / contribs / physics / books} 03:13, 25 February 2017 (UTC)
Hi, for quite a while now I haven't had time to properly maintain a few scripts that perform tasks related to RfCs and other ones related to GAN. These PHP scripts are badly in need of love (plenty of unresolved bug reports on Legobot's talk page) and someone who has time to actually debug when something goes wrong:
I'm currently running this on Tool Labs, so I can help with moving the databases over to a new shared account or whatever you'd prefer. Thanks, Legoktm ( talk) 20:59, 10 February 2017 (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.
|longEW= W\n\n<!-- Area/postal codes & others -->\n
). The removal of coordinates parameters is approved; therefore, the bot was not malfunctioning, and the edit is within the scope of the approval. Whether a human editor would remove the HTML comment (obviously not required to be removed) has no bearing on whether or not the bot was malfunctioning or acting outside of its approval. —
JJMC89 (
T·
C) 03:02, 11 February 2017 (UTC)
|longEW=
. To quote Anomie, [it] is part of the value being passed to the removed coordinates parameter, it's not an independent thing that the bot is additionally removing and the bot isn't malfunctioning by removing it.I never said I thought it was part of any section. — JJMC89 ( T· C) 05:00, 11 February 2017 (UTC)
<!-- Comment -->
, replace with |TEMPJJMC89BOT=<!-- Comment-->
, apply coordinate logic, then find |TEMPJJMC89BOT=<!-- Comment-->
replace with <!-- Comment -->
. Or you could do skip conditions when it finds comments and semi-automate those cases.
Headbomb {
talk /
contribs /
physics /
books} 10:23, 11 February 2017 (UTC)
known bugand was
malfunctioning, neither of which are accurate. Addressing the latter, changing the bot's code to retain HTML comments, is something that I have not commented on here previously. IMO, retaining HTML comments is not desired. Retaining HTML comments would result in this example edit:
{{Example
...
|latd = 1<!-- Latitude degrees -->
|latm = 2<!-- Latitude minutes -->
|lats = 2<!-- Latitude seconds -->
|longd = 4<!-- Longitude degrees -->
|longm = 5<!-- Longitude minutes -->
|longs = 6<!-- Longitude seconds -->
<!-- "header" comment -->
...
}}
{{Example
...
|coordinates = {{coord|1|2|3|N|4|5|6|E}}
<!-- Latitude degrees --><!-- Latitude minutes --><!-- Latitude seconds --><!-- Longitude degrees --><!-- Longitude minutes --><!-- Longitude seconds --><!-- "header" comment -->
...
}}
tpl.remove(param)
.) (\n(?:\s*<!--.*?-->)+)
can be used to capture and reinsert giving {{Example
...
|latd = 1<!-- Latitude degrees -->
|latm = 2<!-- Latitude minutes -->
|lats = 2<!-- Latitude seconds -->
|longd = 4<!-- Longitude degrees -->
|longm = 5<!-- Longitude minutes -->
|longs = 6<!-- Longitude seconds -->
<!-- "header" comment -->
...
}}
{{Example
...
|coordinates = {{coord|1|2|3|N|4|5|6|E}}
<!-- "header" comment -->
...
}}
I also don't see any major communication issue here. Perhaps the botop could have been less dismissive of the complaint, but it appears that until it was brought to AN it was just one editor hyperbolically complaining, and the bot op didn't resist the determination by uninvolved editors that the task should be stopped. Anomie ⚔ 14:14, 10 February 2017 (UTC)
What is needed for this task to be reactivated? There are over 300,000 pages that need attention from this bot task (295,000 now, plus more templates that have not had tracking added yet). – Jonesey95 ( talk) 00:17, 22 February 2017 (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 don't know if any of you depend upon this service. There's more information from User:Ottomata here: https://lists.wikimedia.org/pipermail/wikitech-ambassadors/2017-February/001557.html Whatamidoing (WMF) ( talk) 23:02, 6 March 2017 (UTC)
wikitech:Server switch has new dates: Tech Ops is planning for editing outages on Wednesday, 19 April 2017 and Wednesday, 3 May 2017 (two weeks later). The team has not settled on the exact time yet, but it will probably be between 14:00 and 16:00 UTC (afternoon in Europe/Africa and morning in the Americas).
This is a repeat of the work done last April (only, they hope, a little faster and more reliably). Some bots may need to be restarted after the wikis come back online, so please mark your calendars. Whatamidoing (WMF) ( talk) 20:31, 13 March 2017 (UTC)
This is an archive of past discussions. Do not edit the contents of this page. If you wish to start a new discussion or revive an old one, please do so on the current talk page. |
Archive 5 | ← | Archive 8 | Archive 9 | Archive 10 | Archive 11 | Archive 12 | → | Archive 15 |
Hi! Magioladitis ( talk · contribs) has been mass-editing lots of WikiProject templates using AWB. I asked him to stop and he did.
I don't have much background about how bots or computer-assisted edits should be done on Wikipedia, hence I'm posting here. Is there a process that should be followed for making these kinds of automated edits? It's very disruptive for people like me who have lots of articles on their watchlist, see the screenshot.
If this is the wrong place to discuss this incident, please let me know. -- intgr [talk] 16:36, 3 November 2015 (UTC)
MSGJ I did this User:Scott/Talk#WikiProject_template_redirects hoping for help on that and less disruption. As you may see we even lack the method avoid brute force in some cases. I even asked for a AWB FR: T117365. -- Magioladitis ( talk) 16:47, 3 November 2015 (UTC)
@ GoingBatty: -- Magioladitis ( talk) 16:47, 3 November 2015 (UTC)
Before the statistics I was working blindly. After MSGJ's complains,10 I moved only to the non-standard names. I can stop the task completely. -- Magioladitis ( talk) 16:50, 3 November 2015 (UTC)
@ GoingBatty: Thanks. I am good with that. Please keep it up. -- Magioladitis ( talk) 19:04, 3 November 2015 (UTC)
For information of interested parties, and related to the discussion above, I have today blocked Magioladitis for a week for repeated violations of the bot policy and AWB's rules of use. I welcome feedback on this action. — Martin ( MSGJ · talk) 13:29, 17 November 2015 (UTC)
Can Hazard-Bot be turned off, with regard to its continued cleaning out of the template sandboxes? It's been continuing its chore (certainly in X9, and I assume the others) for several days, twice a day, because Cyberbot-I is now cleaning, as noted previously. Dhtwiki ( talk) 04:21, 26 October 2015 (UTC)
It seems Lowercase sigmabot II is no longer operating; the bot is best known for its ability to immediately reinsert the sandbox header in the event that it gets removed; no other bot that cleans the sandbox, to my knowledge, does this. Can this functionality be incorporated into Cyberbot I? Just wondering. — k6ka 🍁 ( Talk · Contributions) 18:00, 25 November 2015 (UTC)
Can you move sections (February 2014 - present) into archives? Because it's too many. 183.171.178.188 ( talk) 14:34, 17 January 2016 (UTC)
Well, it's bit hard to go through categories one by one, it'd be better if I can load a category at once and roll on it. For what it's worth, my bot's had a mentionless history and has registered 2 complaints throughout it's running time and they were not even his fault (caused by putting the articles in the wrong stub category). Also, I've made a few changes, now it integrates with BannerShell and fixes alternate templates (Custom Module) instead of skipping them. -- QEDK ( T 📖 C) 09:52, 18 January 2016 (UTC)
Bots
which contains permission apihighlimits
. —
xaosflux
Talk 12:25, 18 January 2016 (UTC)This is getting quite embarassing too:
... failing (and still awaiting) an adequate response by the botop in question: are there any other bot owners that can explain a bit (at Jimbo's talk page preferably)? -- Francis Schonken ( talk) 12:06, 26 January 2016 (UTC)
SineBot ( talk · contribs) has not signed anything since last Friday. I have left a note on Slakr's talk but don't know if he's around to reboot it - can anyone else get hold of him? I'm sure I've said this before, but since this is such an essential tool, shouldn't the WMF be taking care of it? Ritchie333 (talk) (cont) 10:15, 26 January 2016 (UTC)
Magioladitis is blocked again.I have opened a discussion at Wikipedia:Administrators' noticeboard#Magioladitis to explore ways to resolve the issues. Anyone is invited to comment there. — Martin ( MSGJ · talk) 20:47, 28 January 2016 (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.
Is Murph9000 Bot ( talk · contribs) an approved bot? There is no entry "changed group membership for Murph9000 Bot from (none) to bot" at their logs, and I can't find a WP:BRFA. -- Redrose64 ( talk) 09:45, 1 February 2016 (UTC)
Looks like I came here too late to change anyone's mind, but I was just going to say that you could easily rename the account to something like "Murph9000 (Assisted)" and be done with it. The edits do not look problematic. The sig-cleaning wouldn't be an appropriate bot task, of course, but as only 30 edits done using some (admittedly unspecified, but I'm going to guess pywikibot) assisted program is not worth fretting over. Seriously.
— Earwig talk 19:50, 2 February 2016 (UTC)
Heads up: All your bots are (maybe) going to break (later). |
In a month or two, they're changing the login system for bots. You can read more here: phab:T121113 and https://lists.wikimedia.org/pipermail/wikitech-l/2016-January/084501.html
If you expect any problems, please reach out to mw:User:Anomie or mw:User:Tgr (only you have to be nice to Tgr, because he did me a favor last week. ;-) This was in Tech/News today, and it's easy to miss an announcement like this, so please also check in with your friends and other wikis and make sure that none of them will be surprised by this. Thanks, Whatamidoing (WMF) ( talk) 22:01, 18 January 2016 (UTC)
My bot broke yesterday ("There was an unexpected error logging in."). I presume this is related? — Steve Summit ( talk) 13:06, 22 January 2016 (UTC)
How is it even possible to login any more without HTTPS? See m:Talk:HTTPS#Bots for the scrambling I had to do after my bots were knocked offline by the mandatory switchover to HTTPS. Wbm1058 ( talk) 18:15, 27 January 2016 (UTC)
This highly technical discussion is mostly over my head, and I have no idea whether I need to change anything to keep my bots running. So far they seem fine and unaffected. This is not a good way to notify me, as I don't even have this page on my watchlist. I just happened to stroll by because of #Archivebot? below. If someone would take a glance at my bots' code and tell me if I need to change anything and if so, what I should change, I would be grateful. Thanks, Wbm1058 ( talk) 15:49, 27 January 2016 (UTC)
Error
|
---|
|
I moved my bots to use OAuth, to avoid any breakage in the change. Well now they're broken, and I don't think it's my fault. Using OAuth I get persistent badtoken error regardless of how many times I delete the bot's cookie. I have made no modifications, and other bot scripts that were working are now broken too.— cyberpower Chat:Offline 04:57, 5 February 2016 (UTC)
A request was posed on my user talk page to not have the bot clobber pages that are redirects when delivering the friendly notices for Wikipedia:Bots/Requests for approval/HasteurBot and Wikipedia:Bots/Requests for approval/HasteurBot 2. In the past I made changes that were reasonable to accomidate similar changes (ex: following the redirect and delivering the notice there) only to have some editors claim that I have exceeded what the bot was authorized to do so I'd like to ask the question here: Do I need to file a new BRFA to change the behavior in edge cases dealing with pages that hard redirect to a new location? Thank you for your consideration. Hasteur ( talk) 18:03, 21 February 2016 (UTC)
Legobot ( talk · contribs) is misbehaving, and is listing discussions that are either closed RfCs, or not RfCs at all. I have posted to its talk page, but with no response from Legoktm ( talk · contribs); and since the bot continues with incorrect edits, should I block the bot? -- Redrose64 ( talk) 00:10, 7 March 2016 (UTC)
{{
Rfc}}
, so that Legobot doesn't think that it's an open Rfc. --
Redrose64 (
talk) 20:15, 8 March 2016 (UTC)Hi everyone,
Ops is planning a major data center migration during the week of 21 March. From the POV of a bot owner, there are two major effects:
This is being announced in m:Tech/News and through the wikitech-l mailing list. phab:T124671 seems to be the central task. You can follow those for further updates (or {{ ping}} me). Please share this information with other projects and bot owners.
— Whatamidoing (WMF) ( talk) 16:28, 10 March 2016 (UTC)
Ops has just postponed this until the week of 18 April. Some backend services will migrate to codfw during the week of 04 April (maybe on the Thursday?). If your bot might rely on RESTbase, Parsoid, or other things like that, then {{ ping}} me and I'll see if I can find a list.
I hope that everyone survived the five-minute test yesterday with no problems. Whatamidoing (WMF) ( talk) 18:41, 16 March 2016 (UTC)
Wikipedia:Bots/Requests for approval/Hazard-Bot 33
How did this get approval without site-wide consensus such as from Village Pump? All the best:
Rich
Farmbrough, 20:07, 21 March 2016 (UTC).
This bot is causing spam to fill up "what links here". For example a new page created by me Columbjohn which has very little to do with architecture now has dozens of links to user pages due to this bot. Have never seen anything like it since 2010. Seems a totally useless bot to me, can it be stopped? I note the user has already been blocked. Thanks.( Lobsterthermidor ( talk) 21:35, 1 April 2016 (UTC))
Theo's Little Bot (run by Theopolisme) has been recreating some of the subtemplates that were slated for deletion in this TfD. It's just been recreating them as an error. The bot owner hasn't edited for a few months, but is anyone able to disable only this task? It seems unreasonable to monitor the bot for when it decides to recreate one of these. Example: Template:Rotten_Tomatoes_score/0118688. ~ Rob Talk 15:07, 19 March 2016 (UTC)
@ Xaosflux: I emailed Theo and he said the offending task has been disabled and the bot can be unblocked. I'll leave that decision up to your discretion. -- Closedmouth ( talk) 09:30, 4 April 2016 (UTC)
I just saw a bot revert an edit automatically and the edit summary was "Reverting possible vandalism by ## to version by ##. Report False Positive? Thanks,". And the core of it felt like "hey did I do the right thing? tell me? tell me?". The edit was very much justified but there's no way to give that feedback automatically. So I thought now that the "thanks" system is in place. Why not enable it so that one can thank a bot which provide automatic feedback for future automated reference or to strike pages of some internal checklist for manual review. A "no, bad bad bot" links will perhaps also be necessary to not bias the feedback data. Just an idea.. Bytesock ( talk) 20:52, 11 April 2016 (UTC)
This is your reminder that all the wikis will be in read-only mode for about half an hour at 14:00 UTC (about 15 hours from now). The announcements are at m:Tech/Server switch 2016 and on the blog. After we can edit again, I'll check WP:VPT for problem reports or advice. Don't forget that this will happen again on Thursday. Whatamidoing (WMF) ( talk) 23:20, 18 April 2016 (UTC)
The mess above suggests to me that we need to change bot policy as follows: No bot will be approved unless its code is publicly posted, on-wiki. If the code is removed or not current, the bot must stop until its posted. We currently have a malfunctioning bot, and an editor who would be willing to fix the code, but not to rewrite the whole thing. Requiring public code would prevent this problem for future bots. Oiyarbepsy ( talk) 05:02, 11 April 2016 (UTC)
Now wait one minute? Isn't a huge part of the Wiki-mission to encourage open-source content? How are we encouraging open-source content by allowing close-source code to run our software? Oiyarbepsy ( talk) 05:26, 11 April 2016 (UTC)
Authors of bot processes are encouraged, but not required, to publish the source code of their bot.(which you've seen several editors oppose) and requiring BAG to decline BRFAs if they don't meet the requirement. Several bots have a secret sauce or a blend of 11 herbs and spices that makes them go, in which case they should not be published. As to requiring it to be published on wiki, that is a unbelivably bad idea short of the foundation/labs providing a version control bridge that interfaces with normal version control software and the "approved" storage. Hasteur ( talk) 20:08, 20 April 2016 (UTC)
Before the servers get to move one last time for now, it seems to bother many that ClueBot III is down since last February. And there seems to be no discussion here, although it is said that Cobi had been doing his job to try to fix the problem somewhere else. Any news? 49.148.27.180 ( talk) 14:00, 21 April 2016 (UTC)
On March 21, 2008 (yes that far back) and for a few days, User:CorenANIBot got into a odd task and copied it seemed the discussions from that day onto separate subpages. Some are just copies of the discussion, some have other people's edits there. One of those subpages is up for deletion at MFD here. -- Ricky81682 ( talk) 20:12, 21 April 2016 (UTC)
(crossposted from User talk:DumbBOT) This bot is incorrectly taking some categories by misposting some templates, see Category:Wikipedia files with no copyright tag as of 5 April 2016 and Category:Wikipedia files with no copyright tag as of 6 April 2016 for examples. It seems to be limited to the "files with no copyright tag" categories. It looks like the bot creator is no longer active but perhaps another editor can help resolve this problem. Liz Read! Talk! 15:18, 3 April 2016 (UTC)
One per day among 50 useful edits, some of which are important to the project. Maybe it would be beneficial for some bot-ops to start work to adopt the two remaining tasks (creation of daily subpages and removing protection templates from unprotected articles). In the meantime, an admin could preemptively salt Category:Wikipedia files with no copyright tag as of 8 April 2016 through Category:Wikipedia files with no copyright tag as of 30 April 2016 to buy us development time. ~ Rob Talk 00:14, 4 April 2016 (UTC)
BTW, there is also some discussion of these issues at the bot's talk page. Speedy deleting isn't enough, as Dumbbot will live up to its name and recreate the categories later. So, any creation protection also needs to apply to categories that have already been speedy deleted, at least until the date on the category has passed. Oiyarbepsy ( talk) 00:25, 11 April 2016 (UTC)
@ Tizio: WP:PUF has now been closed. Could you please have DumbBOT stop creating daily subcategories of Category:Wikipedia possibly unfree files? GeoffreyT2000 ( talk) 23:33, 9 April 2016 (UTC)
Forgot a ping, so adding it now: @ Nyttend:. Oiyarbepsy ( talk) 22:34, 10 April 2016 (UTC)
I'll hold off on blocks while this discussion continues - but we have a core issue that needs to be resolved: bot operators are personally accountable for all actions made by their bots, and this operator is absent. --
xaosflux
Talk 02:13, 11 April 2016 (UTC)
[End text copied from the bot's talk page]
Sorry for the inconvenience. I removed that page from the category creation bot function (yes, the list is merely a report of what the bot is doing). If someone wants to take over the whole function I will shut it down. Otherwise, in case of problem please email me, because I really cannot guarantee logging in often. I added such a notice to the bot's page. Not being an active user any longer, I do not think I should say anything on the policy about bots, just let me know if/when I have to shut it down altogether. Tizio 13:25, 11 April 2016 (UTC)
Test run - the bot created two categories: Category:Wikipedia files with no non-free use rationale as of 11 April 2016 and Category:Wikipedia files needing editor assistance at upload as of 11 April 2016. I believe these are ok, since categories for other days exist and are not empty. A wrong category may still be created this night (the bot runs on two computer, at the moment I can't access the secondary one), but should be the last one. Please let me know if there are some other category that is incorrectly created. Tizio 18:39, 12 April 2016 (UTC)
For some reason, User:Hazard-Bot created Category:Possibly unfree files from 2016 April 21 and Category:Possibly unfree files from 2016 April 20. Hazard-Bot began this "task" on the 17th and the prior ones have all be deleted. I've already informed User talk:Hazard-SJ but (a) when did we authorize two bots to do the same task and (b) is this another bots that will take on this task if we delete these? -- Ricky81682 ( talk) 20:11, 20 April 2016 (UTC)
Question's right up top. -- QEDK ( T ☕ C) 17:10, 2 May 2016 (UTC)
As documented at Wikipedia talk:Good article nominations#Legobot error?, we've positively identified a bug in the Legobot code that is supposed to pass good articles. The bug is: If a reviewer passes an article as GA and places the passed {{ GA}} template immediately above an earlier placed {{ failedGA}} template from an earlier review, the bot will become confused by the presence of both templates and will fai33l the GA rather than pass it. It happened again today at Talk:Gene Roddenberry. It happens nearly every day. When it happens, the successful nominator receives notice that the article failed instead of passed, and the GA icon is not placed on the article; it must be manually placed. A possibly separate bug: Sometimes the GANotice template is not placed on the nominators talk page at all. Pinging Legoktm; can you please help us. Side note: We're also wondering if you can help us add a few subtopics as documented at Wikipedia talk:Good article nominations#RfC: Subcategories on GAN page. Thank-you. Prhartcom ( talk) 22:28, 15 March 2016 (UTC)
Hi, I updated
Template:Bot topicon slightly, to allow specification of owner, icon customization, and custom id (for sorting). I also made
Template:Bot operator topicon with a new
LGPL image,
File:BotOp-logo.svg which also allows image/id customization and bot specification. —
Andy W. (
talk ·
ctb) 16:10, 9 May 2016 (UTC)
Please report here any unusual errors if your bot runs in to the "welcome" message trying to make an edit. Trying to track any of these down. — xaosflux Talk 20:27, 19 May 2016 (UTC)
Ladies/Gents - I know you're sitting at home right now, probing Wikipedia, and looking for something to soften that boredom. You could work on an article about the 1968 Philadelphia Eagles season, but the tediousness of finishing the whole 1960s collection is just dragging on and on. Let me offer you a new opportunity! The Unblock Ticket Request System is looking to get some additional developers on board. Developers do not have to be administrators, but administrator tools will be required for SSH access and access to the live instance of the tool. Non-administrators can still develop with Github and will have access to UTRS-Alpha and UTRS-Beta. Specifically, we're looking for two associate core developers, a senior user experience developer, and a user interface developer. Specific requirements are listed on the link above, but we're looking for experience with HTML5, PHP, jQuery, CSS3, and bootstrap. Additional cross-platform experience, team management, object oriented design, and secure systems development experience is a huge bonus. Please send an application to utrs dash developers AT googlegroups dot com. We have big ideas and big plans for a v2.0 of the system and we're looking for some folks looking to do exciting work.--v/r - T P 03:14, 23 May 2016 (UTC)
It has been agreed that categories must be empty for seven days (not four) before being speedy deleted. If you have any bots or other automated processes based on this, place make the appropriate changes. Oiyarbepsy ( talk) 04:51, 24 May 2016 (UTC)
Please ensure your bots are using HTTPS: links to access APIs of Wikimedia-hosted production wikis! Wikitech-l announcement email with deeper details (also cross-posted to mediawiki-api and mediawiki-api-announce): https://lists.wikimedia.org/pipermail/wikitech-l/2016-May/085618.html -- BBlack (WMF) ( talk) 22:43, 13 May 2016 (UTC)
All AWB API requests are HTTPS unless forced otherwise. No AWB bots will break. -- Magioladitis ( talk) 12:34, 20 May 2016 (UTC)
I'm worried about this list of users, whose bots or scripts are actively using http:// and whose owners look hard to contact:
I'm going to leave messages on the named talk pages, but I'm not expecting much of a response. Several of these editors haven't edited for months. If anyone knows anything about these bots, please {{ ping}} me. Whatamidoing (WMF) ( talk) 18:20, 20 May 2016 (UTC)
If anyone's getting a "500 Can't verify SSL peers without knowing which Certificate Authorities to trust" error, then there's a possible solution at WP:VPT. Whatamidoing (WMF) ( talk) 23:03, 20 May 2016 (UTC)
@ Whatamidoing (WMF): RE: I don't bot op as much as I used to. Can you please tell me (or direct me to) what requests are coming through regular API and I will try to make improvements on it. Or better yet guide me as to where I can self service my requests. Hasteur ( talk) 18:04, 20 May 2016 (UTC)
g13bot_tools-g13_interested_notify.py/r-1 (unknown) Pywikipediabot/1.0
and g13bot_tools-g13_nudge_bot.py/r-1 (unknown) Pywikipediabot/1.0
, and seem to originate in toollabs exec nodes. All the requests were for enwiki APIs. --
BBlack (WMF) (
talk) 19:18, 20 May 2016 (UTC)
Aw crap. What a pain in the ass. Hawkeye7 ( talk) 13:26, 24 May 2016 (UTC)
A relatively small matter, but unfixed and replicated across a lot of articles it could be a much larger one. At Zahi Hawass three edits in a row in three days were by bots. Yobot made a change. GreenC bot undid the change (and did something else), Yobot redid the change. Clearly not both reading from the same style book. Neither actually fixed the problem which is a comma next to a full stop, which maybe means this will not happen elsewhere. But when doing general fixes they should be following exactly the same rules otherwise this could happen again in other ways.-- JohnBlackburne words deeds 08:32, 7 June 2016 (UTC)
This seems to be more of a WP:COSMETICBOT problem with Yobot.
JohnBlackburne and Xaosflux My specific bot's edits are part of CHECKWIKI (error number 61 Reference before punctuation) and are done per Manual of Style. More specifically per WP:REFPUNCT. GreenC bot has to take care of punctuation to be BEFORE references. Take not that Yobot's edit changes the visual outcome so it si not cosmetic. Correct punctuation was/is a criterion of creating good articles. Error 61 is fixed by Yobot since June 2010. -- Magioladitis ( talk) 11:04, 7 June 2016 (UTC)
Aha. JohnBlackburne beats us all :) There was a punctuation duplication causing the error. JohnBlackburne fixed it. -- Magioladitis ( talk) 11:05, 7 June 2016 (UTC)
GreenC bot doesn't mess with punctuation. What happened is GreenC bot inadvertently reverted Yobot's edit. GrenC does so much IO it takes a long time, so it runs off-line generating a diff. When that diff is later uploaded (via AWB) it checks the article size to see if there were any changes and re-runs real-time if there are. Since the changes made by Yobot did not change the article size that is the problem. So what I need is a better way to check for a diffs than article size (duh). That will be no problem, sorry for the revert. -- Green C 12:49, 7 June 2016 (UTC)
I am posting this issue here because I am uninformed of our bot policy and would like more informed editors/admins to take a look at this. I have an outstanding request that I am working with @ BU Rob13: at Wikipedia:Bot requests ({{ WikiProject Green Bay Packers}} Banner is the relevant section). @ Magioladitis: (i.e. User:Yobot) seems to have hijacked our conversation and begun editing without any approval from me, Bu_Rob13 or WP:BAG. Please note that the bot's only contributions so far have been cosmetic, such as this. Check the bots contribution history and see how almost (if not all) of the edits so far have been cosmetic. Please note the conversation at User talk:Yobot. If anyone could advise on the proper actions, I would appreciate it. « Gonzo fan2007 (talk) @ 18:03, 8 June 2016 (UTC)
BU Rob13 I am working on providing a custom module for general use instead of F&R rules because till now you use the latter and the result was duplicated parameters. Anyway, no big harm. I had no indention to hijack the discussion. I left my comment on the assessment of namespaces already in the BOTREQ. My apologies. -- Magioladitis ( talk) 18:26, 8 June 2016 (UTC)
Let's don't have this discussion in many places. I can't reply in all places. All tagging bots I know till now use AWB general fixes and some custom module in addition to F&R rules. In the past some bad settings had caused broken templates/broken parameters etc. So, I always try to keep the custom modules others use up-to-date. I usuallly do this before other bots are about to perform a bot run. IT is the same reason I commented in the BOTREQ about the auto-class set for other namespaces. I apologise if this seemed as hijacking. I'll leave the discussion to you. -- Magioladitis ( talk) 18:39, 8 June 2016 (UTC)
As is required by the BAG membership procedure I am placing this notification at WP:AN, WP:VPM, WT:BOT, and WP:BON. I am requesting to join the Bot Approvals Group and my request can be found here: Wikipedia:Bot Approvals Group/nominations/HighInBC. HighInBC Need help? {{ping|HighInBC}} 20:24, 2 July 2016 (UTC)
A bot has tagged an in-use sound file as an "orphaned image" [3] when it is in use at Antidisestablishmentarianism (word)) providing the US pronunciation. The file is also the target of a redirect. Is there a general problem? Last time there was large scale error-prone orphan file tagging it led to files being deleted as "unused, no foreseeable use" even when they were in use. Thincat ( talk) 15:19, 4 July 2016 (UTC)
{{
Orphan image}}
to better explain its use in assisting maintenance/compilation of site statistics, and the particular
type of links the bot looks for. Furthermore, I have implemented
exclusion compliance in
FastilyBot's task
10 (sorry I forgot :o), so that users are free to opt out for files they have uploaded. I hope this addresses Thincat's and Adam's concerns :) -
FASTILY 21:19, 4 July 2016 (UTC)
fileusage
, which I agree, is different from
linkshere
. It is, however, by no means the deletion tag you're claiming it to be. I am not responsible for the way other editors use and interpret datasets I build; if other users are behaving disruptively, then this is a matter for ANI, which does not concern me or this noticeboard. -
FASTILY 07:49, 5 July 2016 (UTC)
Not sure if this is the right place but here goes. On another wiki, I'd like to use a bot to update and standardize the name of fields on a particular template. Since I'm still learning how to operate bots, is there a bot whose source code I could use/adapt to perform such a task? Abjiklɐm ( tɐlk) 13:26, 5 July 2016 (UTC)
XLinkBot acts like a bot but does not actually have the "bot" flag. A bureaucrat should replace the "autopatrolled" and "extended confirmed user" rights of that user with the "bot" flag while leaving the "pending changes reviewer" right on. GeoffreyT2000 ( talk) 19:09, 12 July 2016 (UTC)
( edit conflict)It has been a specific choice not to flag XLinkBot, and I think it is overly bureaucratic (no pun intended) to enforce that all bots should be that way. Some bots, like the antivandalism bots, do edits that do need constant scrutiny (to quick react on bad reverts, but also to catch the vandals/spammer - if RC patrollers see the bot revert a really bad link, they might get the editor blocked early). It is pertinent that bots that do 'gnoming' type of work (maintenance, wikidata moves) do not show up in RC feeds (they quickly flood feeds, they can even flood watchlists), but antivandalism bots should standard show up in the feeds.
I see that for ClueBot NG flagging has not been discussed, they have just been flagged after the approval ( Wikipedia:Bots/Requests_for_approval/ClueBot_NG; approved on December 3, 2010, flagged on the same day). For XLinkBot this was discussed in the original request, see Wikipedia:Bots/Requests_for_approval/SquelchBot#Big_BAG_Section. Note that the bot's edits are 'manually' flagged in the edit-summary.
We could consider to give the bot the flag, and then de-flag the edits, but I don't see the advantage of that (it will just give me some programming work, and overall nothing changes ..). -- Dirk Beetstra T C 05:12, 13 July 2016 (UTC)
Okay, here's the list of bots and script-users that are going to start breaking on Sunday, 12 June:
New – these owners haven't been contacted yet:
Previously known – these owners have been contacted, but haven't fixed the bots (list generated ~30 hours ago):
If you know how to reach these users, please help us contact them. I know that people are working on a couple of these, but I haven't heard from most of the affected bot owners. In about 72 hours, Ops is going to start refusing 10% of the http:// requests; a month from now, they'll break completely. You can reach me on wiki or via Special:EmailUser if something's sensitive. User:BBlack (WMF) and his team take questions on IRC, too.
Thanks for your help, Whatamidoing (WMF) ( talk) 18:13, 9 June 2016 (UTC)
Xaosflux is correct: This is a global list, not solely for enwiki. The API's global, and the impending change affects all 800+ wikis – not just English-language ones and not just Wikipedias.
This is a list of "bots and script-users", regardless of whether the account has a bot flag. If you are using a custom AWB, Huggle, or similar script, then that is probably the cause. For that matter, any method of POSTing the API over http:// (e.g., to make null edits with a script, which results in some of the "zero contributions" accounts here) will put you on this list, because what you're doing will stop working soon. Whatamidoing (WMF) ( talk) 20:56, 9 June 2016 (UTC)
@ Bgwhite: are you aware that your bot is listed here? -- Magioladitis ( talk) 22:32, 9 June 2016 (UTC)
scripts-header_levels_labs.py/r11775 Pywikipediabot/1.0
. The access wasn't from a labs IP address, it came directly from a residential ISP service. --
BBlack (WMF) (
talk) 01:05, 10 June 2016 (UTC)
The latest list is here: phab:T136674#2394147. Whatamidoing (WMF) ( talk) 18:19, 21 June 2016 (UTC)
Continuing updates to recent lists of usernames still making insecure accesses are being posted every few days here: https://phabricator.wikimedia.org/T136674 -- BBlack (WMF) ( talk) 14:31, 24 June 2016 (UTC)
The API change is scheduled for tomorrow (less than 24 hours from now). If anyone has a bot that might not be fixed, then you might want to run it ASAP, to get one last run before you find out. ;-)
To recap from above, you can find general information in this e-mail message from May. The list of bots/script users that are known to be affected is listed at phab:T136674. If you need information to figure out which piece is going wrong, then the devs can give you a user agent string and similar details from the logs. Just let me (or BBlack (WMF)) know that you need more details.
Good luck, Whatamidoing (WMF) ( talk) 16:22, 11 July 2016 (UTC)
Template_talk:Emergency-bot-shutoff#ANI_notice might be of interest to editors who stalk this page. → Σ σ ς. ( Sigma) 05:36, 21 July 2016 (UTC)
I have blocked
BattyBot (
talk ·
contribs) as an emergency because it seems to be going over large amounts of articles changing {{
main}}
to {{
main article}}
for no obvious reason
random example. If somebody can explain what's going on, I'll unblock.
Ritchie333
(talk)
(cont) 19:01, 18 August 2016 (UTC)
B-bot's first task is to tag non-free images which are orphaned for deletion. When processing these deletion requests I did decline two requests
File:Playdead logo.gif and
File:Careers360 Logo.png because I had doubts about their copyrightability and listed them at FFD instead. B-bot keeps tagging them though despite a {{bots|deny=B-bot}}
tag. I did ask on
B's talk page about this but they don't seem to be very active. Is there a way to stop the bot tagging?
Jo-Jo Eumerus (
talk,
contributions) 12:02, 12 July 2016 (UTC)
Hi there,
What do you think about this edit (and the corresponding to the article's talk page). I find access dates by finding the earliest occurrenceof the url in the article. Is that a good idea? What are the standards for bots that add archives? -- Tim 1357 talk| poke 02:45, 23 September 2016 (UTC)
FYI: There is/was an API outage today, see Wikipedia:Village_pump_(technical)#503_errors.2Fpossible_Twinkle_issues. — xaosflux Talk 16:20, 17 October 2016 (UTC)
As of this edit, It looks like that the two bots have different "opinions" on what a blank template sandbox should look like.
To me, one of the bots should either stop patrolling the template sandbox, or stop doing the task completely if the bot task only patrol that page. NasssaNser ( talk/ edits) 04:07, 22 October 2016 (UTC)
As its maintainer's talk page witnesses, User:InternetArchiveBot is currently not working very well. As the recent error reports have not been answered and the bot is still making edits, would it be useful to block it? − Pintoch ( talk) 16:36, 22 October 2016 (UTC)
C678 how was the 0.1% estimated? -- Magioladitis ( talk) 23:02, 24 October 2016 (UTC)
Good afternoon! When bot edit pages frequently get the error: "The modification you tried to make was aborted by an extension hook". How can it be called? Игорь Темиров ( talk) 13:40, 29 October 2016 (UTC)
As bot operators, you might want to follow these discussions
Headbomb { talk / contribs / physics / books} 16:23, 29 October 2016 (UTC)
There is a new adminbot request open at WP:BRFA. Please see Wikipedia:Bots/Requests for approval/MusikBot II for details. — xaosflux Talk 04:16, 1 November 2016 (UTC)
https://en.wikipedia.org/?title=Taser&diff=737265819&oldid=736467529 is tagged GreenC bot and (WaybackMedic 2).
Per
this discussion and
this one on the Village pump (technical), I have raised the possibility of removing
Template:Fa top's invocation of the metadata
class, which in mobile view has the declaration display:none;
, from the div
section. This will allow the featured log to be viewed in the "mobile view". However, there was some fear that it might break a bot. The FACBot is okay, and I'm not aware of any other bot that accesses these pages, but it's best to ask first rather than proceeding and seeing what breaks. (Notifying
Ian Rose and
Bonvol:)
Hawkeye7 (
talk) 20:14, 1 November 2016 (UTC)
{{
webarchive}}
mergeA question has come up at
User_talk:GreenC_bot#GreenC_bot if the bot should honor the configuration of the original {{
wayback}}
template or {{
dmy}}
. There are good arguments either way, I felt honoring {{wayback}}
was the safer course of action as the only purpose of the bot is merger, not creating a new date format change. The bot has now been shut down twice by
User:Me-123567-Me who also took it to ANI so I'm starting this thread for discussion. I'm willing to make this change, it's not difficult, but it may have unintended consequences and the bot was not approved for it. --
Green
C 22:21, 15 November 2016 (UTC)
{{
wayback}}
template, if it has an explicit df parameter. If not, it must honour the date format specified in the {{
dmy}}
template.
Hawkeye7 (
talk) 23:20, 15 November 2016 (UTC)
Done. 50069 articles originally edited, 10125 had a {{dmy}}
and 849 articles fixed (
example). --
Green
C 19:29, 16 November 2016 (UTC)
The bot maintains both Peer Reviews and Good Article Reassessments. It hasn't been active since November 4 and both PR and GAR hasn't been updated since. The people operating it have said they don't maintain the bot ( CBM, Ruhrfisch). Is it possible to get someone to make a new bot or assume control of the bot to fix this situation? GamerPro64 04:33, 24 November 2016 (UTC)
I wrote a tool for myself, found it pretty useful so cleaned it up and posted on GitHub in case anyone might be interested.
It's a unix command-line tool to retrieve lists of article names, such as all pages in a category, backlinks of a template, pages edited by a user during a certain period, etc.. it's generally useful for work with AWB or bots, but probably other things as well in a unix environment. Only dependency is GNU awk and one of wget, curl or lynx.
https://github.com/greencardamom/Wikiget
-- Green C 01:41, 26 November 2016 (UTC)
The following bots appear to be inactive, have no planned future tasks, and have inactive operators.
Baring any objections, I propose to mark these bots as retired and deflag them. They may be reactivated with a future BRFA A longer list will be coming, but wanted to put these initial example out to see if there is any community objection to this approach. — xaosflux Talk 17:14, 25 November 2016 (UTC)
Please see Wikipedia_talk:Bot_policy#Activity_requirements for a proposed amendment to the bot policy. — xaosflux Talk 19:21, 3 December 2016 (UTC)
The following bots appear to be inactive, in that they have no edits for 5 years. In some special cases this may be due to a read-only bot that only exists for highapi read access. There are many reasons these could be inactive: tasks may have been moved to other accounts, all one-tasks were one-time and completed, operator may have left wikipedia, etc.
Extended content
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Bots that have not edited since 2010 as of 26 November 2016 (UTC). [ ]
|
I propose marking this bots as retired, and removing their bot flags. All operators will be attempted to be contacted via user talk and can indicate that they want to maintain their bot flag by signing the table. Any bots retired in this manner will be consider de-authorized, but may be reactivated in the future following a successful BRFA. The bot policy does not currently have a provision for activity requirements, but assuming this process has support I will propose a policy update to reflect practice. — xaosflux Talk 14:23, 26 November 2016 (UTC)
We 've done this before. So.. proceed! -- Magioladitis ( talk) 22:56, 26 November 2016 (UTC)
Hello! I have offered to help with the WP:BRFA backlog as a bot approver. This procedural notification is to make the community aware that a formal request is open for your consideration. Your input is welcomed at Wikipedia talk:Bot Approvals Group#BAG Nomination: MusikAnimal. Regards — MusikAnimal talk 00:55, 9 December 2016 (UTC)
Here is another batch of bots, these ones have never made an edit so were missed in the prior report. All have operators have not edited in 5+ years. Operator talk messages being left. Barring any objections, will mark as retired and deflag in a week:
— xaosflux Talk 18:00, 3 December 2016 (UTC)
I know there was (at least) one bot for searching copyvios. Does anyone know which is that bot? XXN, 11:48, 14 December 2016 (UTC)
Hi, is there a mechanism or bot approval for work across all language wikis? I recently answered a request for some low-volume high-accuracy non-controversial changing URLs for example sound.westhost.com to sound.whsites.net .. these URLs exist on other language wikis and should be fixed, but I don't have bot approval there (I don't think?). For example DE has about 8 and FR has about 4 etc.. it's too much work to go through each language manually, and not worth the effort to apply for bot approval in every language that needs it for this one task. -- Green C 15:50, 14 December 2016 (UTC)
Hi everyone. I am currently requesting to join the Bot Approval Group, and notification on this page is required. Feel free to comment here if you would like to ask questions or discuss the request. Wugapodes [thɔk] [ˈkan.ˌʧɻɪbz] 23:57, 18 December 2016 (UTC)
A bot approvals group member reconfirmation discussion is now open at Wikipedia:Bot Approvals Group/nominations/Magioladitis 2. Please feel free to review and comment. Thank you, — xaosflux Talk 13:25, 20 December 2016 (UTC)
Per the bot policy, a request to review Yobot's tasks for continuing authorization has been brought up at: Wikipedia_talk:Bots/Requests_for_approval#Request_to_modify_Yobot_authorization. Please review and comment if you are interested. Thank you, — xaosflux Talk 13:33, 20 December 2016 (UTC)
Please see Wikipedia:Village pump (policy)#Removal of data, and Wikidata, which suggests a change to bot policy. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 13:29, 12 January 2017 (UTC)
A couple of years ago, I learned to use Macro Express at work (it's a simple keyboard-and-mouse macro), and having need for the same functionality, I bought it a few days ago. Even when I was using it frequently, it often made seemingly random mistakes, so even in my own offline work, I tend to instruct it to wait for an "okay" from me before it saves anything.
I've thought of using it when doing some editing here (e.g. if I've uploaded a bunch of photos that should be added to articles, I set up a macro to copy the files onto the relevant articles), using the following process: the script loads a page, performs the specified modifications to the code, prompts me to approve or reject the edit, and (if I approve it) hits "Save changes" and goes to the next page, or (if I reject it) the macro stops until I reactivate it. I'd like some input:
I don't think you'd have a way of noticing anything unusual with what I'm thinking of doing, unless you checked my contributions and observed that the edits are going too fast to be manual; that's the only reason, aside from a desire to abide by relevant policy, that I'm bringing this up. Thanks for your input! Nyttend ( talk) 00:46, 2 January 2017 (UTC)
It looks fine to me. -- Magioladitis ( talk) 01:42, 2 January 2017 (UTC)
Anyone tempted to use this kind of software might like to look at AutoHotkey, a similar, but free, utility for Windows. I have blogged about one aspect of its use, but it's far more powerful than that suggests. I've also just started Wikipedia:AutoHotkey to faciliate discussion. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 13:46, 12 January 2017 (UTC)
I've updated the WP:BOTISSUE section of our bot policy. I don't believe the changes to be controversial, but discussion of the changes is certainly encouraged at Wikipedia_talk:Bot_policy#Changes_to_.27dealing_with_issues.27_section. Headbomb { talk / contribs / physics / books} 16:18, 20 January 2017 (UTC)
Before posting at WP:BOTREQ, is there an easy way to see if a bot already does a task?
I have in mind a bot that would tidy up something specific in mainspace (spot duplicate use of citations and tidy them with a refname labelled on the first use) and I don't know how to check if one exists already and I'm not sure it's a great idea to experiment in mainspace to test if it'd get fixed!
Help gratefully accepted.
-- Dweller ( talk) Become old fashioned! 10:18, 26 January 2017 (UTC)
Cydebot is removing links to deleted categories from userpages and archives despite the fact that it does not have permission to do that. Cyde is rarely onwiki. talkpage contribs ((( The Quixotic Potato))) ( talk) 03:01, 28 January 2017 (UTC)
For what it's worth,
Wikipedia:Categories for discussion/Administrator instructions currently says (step 6.6) Go to the old category and check "what links here". If there are links to it within templates, articles, redirects or other category pages, then edit these to link to the new name instead, or remove the links, as appropriate. ... Also update manually-edited pages such as "Categories" sub-pages of portals and active WikiProjects, but ignore "article alert" subpages, user pages and talk pages.
(emphasis added).
In 2008,
that same page said (step 7.3) All references to the category in articles (and other pages) must be changed to the new name, or removed, as the case may be
. So in 2008, when Cydebot was approved for "Automatic implementation of category deletions as a result of listings on Wikipedia:Categories for discussion/Working", it was following the 2008 instructions.
The latter version was
modified in 2011 to add "Article alert" subpages, user pages and talk pages can generally be ignored.
I was unable to find a corresponding discussion in the talk page archive for that page, but it may have happened somewhere.
It seems possible that the bot was approved following the old instructions, and then the instructions changed. It is unclear whether there was consensus for that change in the instructions. – Jonesey95 ( talk) 15:52, 28 January 2017 (UTC)
list it under the appropriate section of Wikipedia:Categories for discussion/Workingwhich triggers this very bot to do its thing. Anomie ⚔ 17:10, 28 January 2017 (UTC)
So after reading this lengthy debate, my curiosity was roused to see what all the fuss was about. Wikipedia:Categories for discussion/Log/2016 December 23 seems to explain it. A whole bunch of "Wikipedian who..." categories were deleted because they are in poor taste and inappropriate for an encyclopedia. Wikipedian Jedi Knights that poop with a demented sense of humor, etc. – I'm glad they're gone. What would the point be to just turn the blue links to red? These were all deemed to violate WP:USERCAT. Potato, good bot operators are a rare and precious commodity, and shouldn't be bothered with such concerns. wbm1058 ( talk) 03:56, 1 February 2017 (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've made a proposal on the ARBCOM workshop page concerning how to deal with the Magiodilitis situation. Input by WP:BAG, bot owners, and the community at large is welcomed. Even if the proposal doesn't pass, some other ideas can be of interest, especially to WP:AWB/ WP:CHECKWIKI people. Headbomb { talk / contribs / physics / books} 13:22, 3 February 2017 (UTC)
Wikipedia:Exclusion compliant, currently a redirect to Template:Bots, has been nominated for deletion at Wikipedia:Redirects for discussion/Log/2017 February 5#Wikipedia:Exclusion compliant. You are invited to comment at the linked discussion. Thryduulf ( talk) 00:36, 6 February 2017 (UTC)
The new mw:Developer Wishlist is in the voting phase. I believe that all bot coders are considered 'devs' for the purpose of voting rights, so many of the regulars on this page qualify.
This focus of this wishlist is on things that make it easier to be a MediaWiki developer – stuff for coding/reviewing/developing, not stuff for editing Wikipedia. If there are any proposals there that would make your bot work easier, then please vote for them. Whatamidoing (WMF) ( talk) 18:56, 8 February 2017 (UTC)
While I'm here anyway: remember m:Tech/Server switch 2016? It's probably going to happen in April, with 14+ days between the two editing interruptions. This is super-early notice, so it may be delayed (it will not happen any sooner), but please make a note that there's a chance that bots will need to be re-started. The official schedule will probably be on the same page as last year, at wikitech:Switch Datacenter. Whatamidoing (WMF) ( talk) 21:14, 8 February 2017 (UTC)
Please see User talk:Legobot#Misconversion of diacritics. -- Redrose64 🌹 ( talk) 12:35, 16 February 2017 (UTC)
A week or two ago, we wrote this little handy guide for WP:BAG members. It mostly details best practices, and act as a general resources for BAG members. BAG members had a chance to give its opinion on it, but bot owners (and the community at large) are certainly welcomed to suggest improvements to the guide, or point out some things that might be relevant to BAG members that we don't already mention. The discussion can be joined at WT:BAGG.
Thanks for any feedback you might have. Headbomb { talk / contribs / physics / books} 03:13, 25 February 2017 (UTC)
Hi, for quite a while now I haven't had time to properly maintain a few scripts that perform tasks related to RfCs and other ones related to GAN. These PHP scripts are badly in need of love (plenty of unresolved bug reports on Legobot's talk page) and someone who has time to actually debug when something goes wrong:
I'm currently running this on Tool Labs, so I can help with moving the databases over to a new shared account or whatever you'd prefer. Thanks, Legoktm ( talk) 20:59, 10 February 2017 (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.
|longEW= W\n\n<!-- Area/postal codes & others -->\n
). The removal of coordinates parameters is approved; therefore, the bot was not malfunctioning, and the edit is within the scope of the approval. Whether a human editor would remove the HTML comment (obviously not required to be removed) has no bearing on whether or not the bot was malfunctioning or acting outside of its approval. —
JJMC89 (
T·
C) 03:02, 11 February 2017 (UTC)
|longEW=
. To quote Anomie, [it] is part of the value being passed to the removed coordinates parameter, it's not an independent thing that the bot is additionally removing and the bot isn't malfunctioning by removing it.I never said I thought it was part of any section. — JJMC89 ( T· C) 05:00, 11 February 2017 (UTC)
<!-- Comment -->
, replace with |TEMPJJMC89BOT=<!-- Comment-->
, apply coordinate logic, then find |TEMPJJMC89BOT=<!-- Comment-->
replace with <!-- Comment -->
. Or you could do skip conditions when it finds comments and semi-automate those cases.
Headbomb {
talk /
contribs /
physics /
books} 10:23, 11 February 2017 (UTC)
known bugand was
malfunctioning, neither of which are accurate. Addressing the latter, changing the bot's code to retain HTML comments, is something that I have not commented on here previously. IMO, retaining HTML comments is not desired. Retaining HTML comments would result in this example edit:
{{Example
...
|latd = 1<!-- Latitude degrees -->
|latm = 2<!-- Latitude minutes -->
|lats = 2<!-- Latitude seconds -->
|longd = 4<!-- Longitude degrees -->
|longm = 5<!-- Longitude minutes -->
|longs = 6<!-- Longitude seconds -->
<!-- "header" comment -->
...
}}
{{Example
...
|coordinates = {{coord|1|2|3|N|4|5|6|E}}
<!-- Latitude degrees --><!-- Latitude minutes --><!-- Latitude seconds --><!-- Longitude degrees --><!-- Longitude minutes --><!-- Longitude seconds --><!-- "header" comment -->
...
}}
tpl.remove(param)
.) (\n(?:\s*<!--.*?-->)+)
can be used to capture and reinsert giving {{Example
...
|latd = 1<!-- Latitude degrees -->
|latm = 2<!-- Latitude minutes -->
|lats = 2<!-- Latitude seconds -->
|longd = 4<!-- Longitude degrees -->
|longm = 5<!-- Longitude minutes -->
|longs = 6<!-- Longitude seconds -->
<!-- "header" comment -->
...
}}
{{Example
...
|coordinates = {{coord|1|2|3|N|4|5|6|E}}
<!-- "header" comment -->
...
}}
I also don't see any major communication issue here. Perhaps the botop could have been less dismissive of the complaint, but it appears that until it was brought to AN it was just one editor hyperbolically complaining, and the bot op didn't resist the determination by uninvolved editors that the task should be stopped. Anomie ⚔ 14:14, 10 February 2017 (UTC)
What is needed for this task to be reactivated? There are over 300,000 pages that need attention from this bot task (295,000 now, plus more templates that have not had tracking added yet). – Jonesey95 ( talk) 00:17, 22 February 2017 (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 don't know if any of you depend upon this service. There's more information from User:Ottomata here: https://lists.wikimedia.org/pipermail/wikitech-ambassadors/2017-February/001557.html Whatamidoing (WMF) ( talk) 23:02, 6 March 2017 (UTC)
wikitech:Server switch has new dates: Tech Ops is planning for editing outages on Wednesday, 19 April 2017 and Wednesday, 3 May 2017 (two weeks later). The team has not settled on the exact time yet, but it will probably be between 14:00 and 16:00 UTC (afternoon in Europe/Africa and morning in the Americas).
This is a repeat of the work done last April (only, they hope, a little faster and more reliably). Some bots may need to be restarted after the wikis come back online, so please mark your calendars. Whatamidoing (WMF) ( talk) 20:31, 13 March 2017 (UTC)