This page 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.
Latest comment: 2 years ago1 comment1 person in discussion
Bots Newsletter, January 2022
Graphs are unavailable due to technical issues. There is more info on Phabricator and on MediaWiki.org.
BRFA activity by month
Welcome to the ninth issue of the English Wikipedia's Bots Newsletter, your source for all things bot. Vicious bot-on-bot edit warring... superseded tasks... policy proposals... these stories, and more, are brought to you by Wikipedia's most distinguished newsletter about bots.
After a long hiatus between August 2019 and December 2021, there's quite a bit of ground to cover. Due to the vastness, I decided in December to split the coverage up into a few installments that covered six months each. Some people thought this was a good idea, since covering an entire year in a single issue would make it unmanageably large. Others thought this was stupid, since they were getting talk page messages about crap from almost three years ago. Ultimately, the question of whether each issue covers six months or a year is only relevant for a couple more of them, and then the problem will be behind us forever.
Of course, you can also look on the bright side – we are making progress, and this issue will only be about crap from almost two years ago. Today we will pick up where we left off in December, and go through the first half of 2020.
Overall
In the first half of 2020, there were 71 BRFAs. Of these, Y 59 were approved, and 12 were unsuccessful (with N2 8 denied, ? 2 withdrawn, and 2 expired).
January 2020
Yeah, you're not gonna be able to get away with this anymore.
A new Pywikibot release dropped support for Python 3.4, and it was expected that support for Python 2.7 would be removed in coming updates. Toolforge itself planned to drop Python 2 support in 2022.
On February 1, some concerns were raised about ListeriaBot performing "nonsense" edits. Semi-active operator Magnus Manske (who originally coded the Phase II software|precursor of MediaWiki) was pinged. Meanwhile, the bot was temporarily blocked for several hours until the issue was diagnosed and resolved.
In March, a long discussion was started at Wikipedia talk:Bot policy by Skdb about the troubling trend of bots "expiring" without explanation after their owners became inactive. This can happen for a variety of reasons -- API changes break code, hosting providers' software updates break code, hosting accounts lapse, software changes make bots' edits unnecessary, and policy changes make bots' edits unwanted. The most promising solution seemed to be Toolforge hosting (although it has some problems of its own, like the occasional necessity of refactoring code).
A discussion on the bot noticeboard, "Re-examination of ListeriaBot", was started by Barkeep49, who pointed out repeated operation outside the scope of its BRFA (i.e. editing pages in mainspace, and adding non-free images to others). Some said it was doing good work, and others said it was operating beyond its remit. It was blocked on April 10; the next day it was unblocked, reblocked from article space, reblocked "for specified non-editing actions", unblocked, and indeffed. The next week, several safeguards were implemented in its code by Magnus; the bot was allowed to roam free once more on April 18.
Issues and enquiries are typically expected to be handled on the English Wikipedia. Pages reachable via unified login, like a talk page at Commons or at Italian Wikipedia could also be acceptable [...] External sites like Phabricator or GitHub (which require separate registration or do not allow for IP comments) and email (which can compromise anonymity) can supplement on-wiki communication, but do not replace it.
May 2020
We heard you like bots, so we made a bot that reports the status of your bots, so now you can use bots while you use bots
MajavahBot 3, an impressively meta bot task, was approved this month for maintaining a list of bots running on the English Wikipedia. The page, located at User:MajavahBot/Bot status report, is updated every 24 hours; it contains a list of all accounts with the bot flag, as well as their operator, edit count, last activity date, last edit date, last logged action date, user groups and block status.
In July 2017, Headbomb made a proposal that a section of the Wikipedia:Dashboard be devoted to bots and technical issues. In November 2019, Lua code was written superseding Legobot's tasks on that page, and operator Legoktm was asked to stop them so that the new code could be deployed. After no response to pings, a partial-block of Legobot for the dashboard was proposed. Some months later, on June 16, Headbomb said: "A full block serves nothing. A partial block solves all current issues [...] Just fucking do it. It's been 3 years now." The next day, however, Legoktm disabled the task, and the dashboard was successfully refactored.
On June 7, RexxS blocked Citation bot for disruptive editing, saying it was "still removing links after request to stop". A couple weeks later, a discussion on the bots noticeboard was opened, saying "it is a widely-used and useful bot, but it has one of the longest block logs for any recently-operating bot on Wikipedia". While its last BRFA approval was in 2011, its code and functionality had changed dramatically since then, and AntiCompositeNumber requested that BAG require a new BRFA. Maintainer AManWithNoPlan responded that most blocks were from years ago (when it lacked a proper test suite), and problems since then had mostly been one-off errors (like a June 2019 incident in which a LTA had "weaponized" the bot to harass editors).
David Tornheim opened a discussion about whether bots based on closed-source code should be permitted, and proposed that they not. He cited a recent case in which a maintainer had said "I can only suppose that the code that is available on GitHub is not the actual code that was running on [the bot]". Some disagreed: Naypta said that "I like free software as much as the next person, and I strongly believe that bot operators should make their bot code public, but I don't think it should be that they must do so".
(You can subscribe or unsubscribe from future newsletters by adding or removing your name from this list.)
Strange edit by DatBot
Latest comment: 2 years ago4 comments3 people in discussion
In this edit DatBot made a vandalism report, claiming that an IP editor had triggered an edit filter, but I can find no record of any edit filter log or editing for this IP address or any other address in the same /64 range. JBW (talk) 14:59, 5 February 2022 (UTC)
@JBW: I'm not sure honestly. Quarry also does not find it. If it happens again then I'll take a deeper look. Dat GuyTalkContribs 17:41, 5 February 2022 (UTC)
@JBW: This typically means that the entry was oversighted. Suffusion of Yellow (talk) 19:44, 5 February 2022 (UTC)
@Suffusion of Yellow: Yes of course, that's probably it. Thanks 😊. JBW (talk) 21:31, 5 February 2022 (UTC)
Re-resizing new version of the same image.
Latest comment: 2 years ago4 comments3 people in discussion
Hi. Regarding User:DatBot. I've replaced the image File:EddieHall v HafþórBjörnsson.jpg with a more recent version, but this new version needs to be resized. Given that the bot resized the previous version of the image, will it re-resize this new version? Does it have any logic preventing it from resizing the same image multiple times? Melmann 12:18, 10 February 2022 (UTC)
@Another Believer: I believe this is because the (corrupted?) metadata, as seen in the bottom of the file page, has the width and height flipped, but then applies a rotation. The bot uses Wikipedia's supplied dimensions, which have the rotation applied, and resizes it based off that. It's unfortunate but I have only seen this happen about ten times overall, and I don't know of a good way to fix this. Dat GuyTalkContribs 18:00, 13 February 2022 (UTC)
Latest comment: 2 years ago1 comment1 person in discussion
Hello! I wanted to drop a quick note for all of our AFC participants; nothing huge and fancy like a newsletter, but a few points of interest.
AFCH will now show live previews of the comment to be left on a decline.
The template {{db-afc-move}} has been created - this template is similar to {{db-move}} when there is a redirect in the way of an acceptance, but specifically tells the patrolling admin to let you (the draft reviewer) take care of the actual move.
Short and sweet, but there's always more to discuss at WT:AFC. Stop on by, maybe review a draft on the way? Whether you're one of our top reviewers, or haven't reviewed in a while, I want to thank you for helping out in the past and in the future. Cheers, Primefac, via MediaWiki message delivery (talk) 15:59, 16 February 2022 (UTC)
_shown_in_her_laboratory_in_1947.jpg)
.jpg)
_(cropped_to_40%25).jpg){kind=small}
