User talk:Dan Koehl/2022
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. |
Bots Newsletter, January 2022
Bots Newsletter, January 2022 | |
---|---|
| Graphs are unavailable due to technical issues. There is more info on Phabricator and on MediaWiki.org. |
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, 59 were approved, and 12 were unsuccessful (with 8 denied, 2 withdrawn, and 2 expired).
January 2020
- ST47Bot, Seppi333Bot, Qbugbot 4 · PkbwcgsBot 25, PkbwcgsBot 26
- 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.
- Two new bots dropped in January 2020: ST47Bot, the successor to STBot, and Seppi333Bot, whose task was to perform a weekly update of four "massive" wikitables for WikiProject Molecular Biology.
- Cydebot, an adminbot operated by Cyde since 2006, was blocked after going berserk on categories that hadn't yet been CfD'd.
February 2020
- AnomieBOT 78, Cewbot 2, DannyS712 bot 67, DannyS712 bot III 63, PearBOT 6, DemonDays64 Bot 2 · PearBOT
- 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.
- On February 18, ST47Bot got into a tussle with Amalthea (bot), and had to be partially-blocked from Wikipedia:Sockpuppet investigations/Cases/Overview.
March 2020
- MajavahBot, SDZeroBot, TheSandBot 6, TheSandBot 7, Bitbotje, FACBot 6, TheSandBot 8, Qbugbot 5, Cewbot 3, SDZeroBot 2, PrimeBOT 31, WikiCleanerBot 12 · AntiCompositeBot
- 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).
- Some of the twelve bot tasks approved this month were TheSandBot 6 (removing blocked users from Category:Wikipedia usernames with possible policy issues), and TheSandBot 7 (removing unblocked users from Category:Wikipedians who are indefinitely blocked for promotional user names). SDZeroBot 2 was approved to refine geographic stub tags. New bots approved this month were MajavahBot (to patrol WP:EFFPR), SDZeroBot (to merge stub tags), and Bitbotje (fixing DISPLAYTITLE modifications, DEFAULTSORT errors and broken behavior switches in draftspace).
April 2020
- TheSandBot 9, BHGbot 5, DannyS712 bot 69, SDZeroBot 3, ST47ProxyBot, WugBot 4, SDZeroBot 4, DatBot 10, WikiCleanerBot 11, WikiCleanerBot 13, WikiCleanerBot 14, AntiCompositeBot 2, Cewbot 4 · DaedanBot 1 · Creffbot
- 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.
- ST47ProxyBot joined the stable in April, after a BRFA started in December was finally completed. As an adminbot, it was authorized to block IP addresses belonging to open proxies, public VPN services, and web hosts. New tasks approved for existing bots included BHGbot 5 (diffusing categories), TheSandBot 9 (taking over some tasks from the inactive RonBot), and WugBot 4 (updating data at {{Interactive COVID-19 maps}}). Also, DatBot 10 was approved to scale down non-free SVGs — I didn't even know that was a thing.
- A discussion at Wikipedia talk:Bot policy was started by Thryduulf about whether WP:BOTCOMM should explicitly specify that bot operators must be responsive to concerns raised on English Wikipedia specifically (as opposed to Phabricator, SourceForge, Toolforge, et cetera). Eventually, the policy was amended to its current form:
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
- MajavahBot 3, DannyS712 bot 70, CitationCleanerBot 5, Dreamy Jazz Bot 4, QEDKbot, William Avery Bot 2, DannyS712 bot 68, PrimeBOT 32, TheSandBot 10, Bot1058 7, BHGbot 6, EaglesBot 2, Cewbot 5, WikiCleanerBot 17 · MDanielsBot, PhuzBot 3, Gedimon · PearBOT 7
- 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.
- Other approvals for this month were William Avery Bot 2 (processing redirects in {{R from scientific name}}), DannyS712 bot 68 (allowing users to schedule bot reminders for themselves), TheSandBot 10 (removing blocked/locked users from Category:User talk pages with conflict of interest notices), Bot1058 7 (updating Wikipedia:Requested moves/Technical requests/Permalink), Dreamy Jazz Bot 4 (adding {{WikiProject Biography|living=no}} to talk pages where their associated article is in a year of death category), and QEDKbot (deleting and nominating empty categories).
- General syntax fixing tasks were approved for DannyS712 bot 70, CitationCleanerBot 5, PrimeBOT 32, BHGbot 6, Cewbot 5, and EaglesBot 2, as well as WikiCleanerBot 15, 16, and 17.
- Seven bots who fell below activity requirements (with neither the bots nor their operators having any edits or logged actions in two years) had their bot flags removed. They were NekoBot, Robert SkyBot, DASHBotAV, VoxelBot, JackieBot, ReferenceBot, and CensusBot.
- On May 12, EmausBot was blocked.
June 2020
- QEDKbot 2, AnomieBOT 79, WOSlinkerBot 6, Yapperbot 2, Yapperbot, AnomieBOT 80, Dreamy Jazz Bot 5, WikiCleanerBot 18, HasteurBot 15, MusikBot II 4, NoSandboxesHere · RedWarn · Seppi333Bot 2
- 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".
- Two new bots had their first BRFAs approved: Yapperbot, to replace Legobot for handling the Feedback Request Service, and NoSandboxesHere, to remove {{user sandbox}} from articles in draftspace using Category:Non-userspace pages using User sandbox.
Conclusion
- What's next for our intrepid band of coders, maintainers and approvers?
- Will Citation bot ever be set free to roam the project?
- What's the deal with all those book links that InternetArchiveBot is adding to articles?
- Should we keep using Gerrit for MediaWiki?
- What if we had a day for bots to make cosmetic edits?
These questions will be answered — and new questions raised — by the February 2022 Bots Newsletter. Tune in, or miss out!
Signing off... jp×g 23:22, 31 January 2022 (UTC)
(You can subscribe or unsubscribe from future newsletters by adding or removing your name from this list.)
AfC -- seeking a secondary review from a native Swedish speaker
Hi there! I found you over on WP:Babel as you have experience translating articles between English and Swedish. I am reviewing Draft:Eva_Ramstedt for WP:AfC, and am wondering if you could help out by reviewing the citations and making sure the information in the article is accurate, or if there is noteworthy information that has been left out. I've left a couple specific questions in a comment, but unfortunately my ability to reference between the cites and article about ends there. Thank you! SiliconRed (he/him) (talk) 20:43, 15 March 2022 (UTC)
New Page Patrol newsletter May 2022
Hello Dan Koehl,
At the time of the last newsletter (No.26, September 2021), the backlog was 'only' just over 6,000 articles. In the past six months, the backlog has reached nearly 16,000, a staggering level not seen in several years. A very small number of users had been doing the vast majority of the reviews. Due to "burn-out", we have recently lost most of this effort. Furthermore, several reviewers have been stripped of the user right for abuse of privilege and the articles they patrolled were put back in the queue.
Several discussions on the state of the process have taken place on the talk page, but there has been no action to make any changes. The project also lacks coordination since the "position" is vacant.
In the last 30 days, only 100 reviewers have made more than 8 patrols and only 50 have averaged one review a day. There are currently 802 New Page Reviewers, but about a third have not had any activity in the past month. All 855 administrators have this permission, but only about a dozen significantly contribute to NPP.
This means we have an active pool of about 450 to address the backlog. We cannot rely on a few to do most of the work as that inevitably leads to burnout. A fairly experienced reviewer can usually do a review in a few minutes. If every active reviewer would patrol just one article per day, the backlog would very quickly disappear.
If you have noticed a user with a good understanding of Wikipedia notability and deletion, do suggest they help the effort by placing {{subst:NPR invite}}
on their talk page.
If you are no longer very active on Wikipedia or you no longer wish to be part of the New Page Reviewer user group, please consider asking any admin to remove you from the list. This will enable NPP to have a better overview of its performance and what improvements need to be made to the process and its software.
To opt-out of future mailings, please remove yourself here.
Sent 05:17, 23 May 2022 (UTC)
New Page Patrol newsletter June 2022
Hello Dan Koehl,
- Backlog status
At the time of the last newsletter (No.27, May 2022), the backlog was approaching 16,000, having shot up rapidly from 6,000 over the prior two months. The attention the newsletter brought to the backlog sparked a flurry of activity. There was new discussion on process improvements, efforts to invite new editors to participate in NPP increased and more editors requested the NPP user right so they could help, and most importantly, the number of reviews picked up and the backlog decreased, dipping below 14,000[a] at the end of May.
Since then, the news has not been so good. The backlog is basically flat, hovering around 14,200. I wish I could report the number of reviews done and the number of new articles added to the queue. But the available statistics we have are woefully inadequate. The only real number we have is the net queue size.[b]
In the last 30 days, the top 100 reviewers have all made more than 16 patrols (up from 8 last month), and about 70 have averaged one review a day (up from 50 last month).
While there are more people doing more reviews, many of the ~730 with the NPP right are doing little. Most of the reviews are being done by the top 50 or 100 reviewers. They need your help. We appreciate every review done, but please aim to do one a day (on average, or 30 a month).
- Backlog drive
A backlog reduction drive, coordinated by buidhe and Zippybonzo, will be held from July 1 to July 31. Sign up here. Barnstars will be awarded.
- TIP – New school articles
Many new articles on schools are being created by new users in developing and/or non-English-speaking countries. The authors are probably not even aware of Wikipedia's projects and policy pages. WP:WPSCH/AG has some excellent advice and resources specifically written for these users. Reviewers could consider providing such first-time article creators with a link to it while also mentioning that not all schools pass the GNG and that elementary schools are almost certainly not notable.
- Misc
There is a new template available, {{NPP backlog}}
, to show the current backlog. You can place it on your user or talk page as a reminder:
Very high unreviewed pages backlog: 9452 articles, as of 08:00, 3 June 2024 (UTC), according to DatBot
There has been significant discussion at WP:VPP recently on NPP-related matters (Draftification, Deletion, Notability, Verifiability, Burden). Proposals that would somewhat ease the burden on NPP aren't gaining much traction, although there are suggestions that the role of NPP be fundamentally changed to focus only on major CSD-type issues.
- Reminders
- Consider staying informed on project issues by putting the project discussion page on your watchlist.
- If you have noticed a user with a good understanding of Wikipedia notability and deletion, suggest they help the effort by placing
{{subst:NPR invite}}
on their talk page. - If you are no longer very active on Wikipedia or you no longer wish to be part of the New Page Reviewer user group, please consider asking any admin to remove you from the list. This will enable NPP to have a better overview of its performance and what improvements need to be made to the process and its software.
- To opt-out of future mailings, please remove yourself here.
- Notes
MediaWiki message delivery (talk) 10:02, 24 June 2022 (UTC)
NPP July 2022 backlog drive is on!
New Page Patrol | July 2022 Backlog Drive | |
| |
You're receiving this message because you are a new page patroller. To opt-out of future mailings, please remove yourself here. |
(t · c) buidhe 20:25, 1 July 2022 (UTC)
August 2022
There is currently a discussion at Wikipedia:Administrators' noticeboard/Incidents regarding an issue with which you may have been involved. Thank you. Ermenrich (talk) 14:40, 2 August 2022 (UTC)
New Page Patrol newsletter August 2022
Hello Dan Koehl,
- Backlog status
After the last newsletter (No.28, June 2022), the backlog declined another 1,000 to 13,000 in the last week of June. Then the July backlog drive began, during which 9,900 articles were reviewed and the backlog fell by 4,500 to just under 8,500 (these numbers illustrate how many new articles regularly flow into the queue). Thanks go to the coordinators Buidhe and Zippybonzo, as well as all the nearly 100 participants. Congratulations to Dr vulpes who led with 880 points. See this page for further details.
Unfortunately, most of the decline happened in the first half of the month, and the backlog has already risen to 9,600. Understandably, it seems many backlog drive participants are taking a break from reviewing and unfortunately, we are not even keeping up with the inflow let alone driving it lower. We need the other 600 reviewers to do more! Please try to do at least one a day.
- Coordination
- MB and Novem Linguae have taken on some of the coordination tasks. Please let them know if you are interested in helping out. MPGuy2824 will be handling recognition, and will be retroactively awarding the annual barnstars that have not been issued for a few years.
- Open letter to the WMF
- The Page Curation software needs urgent attention. There are dozens of bug fixes and enhancements that are stalled (listed at Suggested improvements). We have written a letter to be sent to the WMF and we encourage as many patrollers as possible to sign it here. We are also in negotiation with the Board of Trustees to press for assistance. Better software will make the active reviewers we have more productive.
- TIP - Reviewing by subject
- Reviewers who prefer to patrol new pages by their most familiar subjects can do so from the regularly updated sorted topic list.
- New reviewers
- The NPP School is being underused. The learning curve for NPP is quite steep, but a detailed and easy-to-read tutorial exists, and the Curation Tool's many features are fully described and illustrated on the updated page here.
- Reminders
- Consider staying informed on project issues by putting the project discussion page on your watchlist.
- If you have noticed a user with a good understanding of Wikipedia notability and deletion, suggest they help the effort by placing
{{subst:NPR invite}}
on their talk page. - If you are no longer very active on Wikipedia or you no longer wish to be part of the New Page Reviewer user group, please consider asking any admin to remove you from the list. This will enable NPP to have a better overview of its performance and what improvements need to be made to the process and its software.
- To opt-out of future mailings, please remove yourself here.
Delivered by: MediaWiki message delivery (talk) 21:24, 6 August 2022 (UTC)
Topic Ban
By community consensus as seen here, you are now topic banned from the topic of Vikings, broadly construed. This topic ban is logged at WP:EDRC. This prohibits you from editing about Vikings at all, except to contest your topic ban. More information is available at WP:TBAN. If you have any questions, please ask. -- Yamla (talk) 11:44, 7 August 2022 (UTC)
NPP message
Hi Dan Koehl,
- Invitation
For those who may have missed it in our last newsletter, here's a quick reminder to see the letter we have drafted, and if you support it, do please go ahead and sign it. If you already signed, thanks. Also, if you haven't noticed, the backlog has been trending up lately; all reviews are greatly appreciated.
To opt-out of future mailings, please remove yourself here.
MediaWiki message delivery (talk) 23:10, 20 August 2022 (UTC)
WikiProject Amusement Parks discussion
Hello Dan Koehl/2022! Your input is requested for a proposal at Wikipedia talk:WikiProject Amusement Parks#Draft proposal for the future of WP:APARKS. Any feedback is welcome. Thank you.
Adog (Talk・Cont) 02:03, 8 September 2022 (UTC)
October 2022 New Pages Patrol backlog drive
New Page Patrol | October 2022 backlog drive | |
| |
You're receiving this message because you are a new page patroller. To opt-out of future mailings, please remove yourself here. |
(t · c) buidhe 21:16, 23 September 2022 (UTC)
Precious anniversary
Six years! |
---|
--Gerda Arendt (talk) 06:34, 25 October 2022 (UTC)
Welcome to Wikipedia: check out the Teahouse!
Happy Birthday!
Happy birthday! Hi Dan Koehl! On behalf of the Birthday Committee, I'd like to wish you a very happy birthday! Enjoy this special day! Volten001 ☎ 06:05, 28 October 2022 (UTC) |
Happy Birthday!
Happy birthday! Hi Dan Koehl! On behalf of the Birthday Committee, I'd like to wish you a very happy birthday! Enjoy this special day! CAPTAIN RAJU(T) 20:45, 28 October 2022 (UTC) |
The Points Guy help
Hello. I see you belong to WikiProject Travel and Tourism. Could you assist on reviewing Talk:The_Points_Guy#Proposed_Updates_to_Article? I have a COI. Thank you for considering this! Cheergirl325 (talk) 14:41, 7 November 2022 (UTC)
ArbCom 2022 Elections voter message
Hello! Voting in the 2022 Arbitration Committee elections is now open until 23:59 (UTC) on Monday, 12 December 2022. All eligible users are allowed to vote. Users with alternate accounts may only vote once.
The Arbitration Committee is the panel of editors responsible for conducting the Wikipedia arbitration process. It has the authority to impose binding solutions to disputes between editors, primarily for serious conduct disputes the community has been unable to resolve. This includes the authority to impose site bans, topic bans, editing restrictions, and other measures needed to maintain our editing environment. The arbitration policy describes the Committee's roles and responsibilities in greater detail.
If you wish to participate in the 2022 election, please review the candidates and submit your choices on the voting page. If you no longer wish to receive these messages, you may add {{NoACEMM}}
to your user talk page. MediaWiki message delivery (talk) 00:24, 29 November 2022 (UTC)
WikiProject Amusement Parks reliable source discussion
Hi, Dan Koehl/2022. Your input is requested at WikiProject Amusement Parks, as there is a discussion about the reliability of some sources which can be found at Wikipedia talk:WikiProject Amusement Parks#Reliable source discussion. Thank you!
- Note: You recieved this notification because you are listed as a participant for WikiProject Amusement Parks.
Harobouri T • C (he/him) 16:42, 3 December 2022 (UTC)
Translation
Hello! Strange request here, but an article about me and my Wikipedia work has been promoted to Good article status at English Wikipedia and nominated for similar status at Spanish Wikipedia. I'm curious if you have any interest in translating the entry for Swedish Wikipedia or other projects?
Figured I'd ask since your profile suggests you do translation work. Either way, happy editing! ---Another Believer (Talk) 19:50, 8 December 2022 (UTC)
- Of course, Ill be happy to, @Another Believer:! Dan Koehl (talk) 12:46, 10 December 2022 (UTC)
- Wow, thanks so much! I appreciate your assistance and look forward to seeing the translation(s). ---Another Believer (Talk) 16:54, 10 December 2022 (UTC)
- @Another Believer:, I have a three year block on svwiki though, so I cant edit the article. Dan Koehl (talk) 16:57, 10 December 2022 (UTC)
- Oh, ok. I'm not sure how attribution would work, but you could always create a draft or user subpage here and I could try to find someone else to review and implement the draft. I don't mean to complicate things, I was just trying to identify some multilingual editors who might be able to help out. No worries! ---Another Believer (Talk) 19:17, 10 December 2022 (UTC)
- @Another Believer:, I have a three year block on svwiki though, so I cant edit the article. Dan Koehl (talk) 16:57, 10 December 2022 (UTC)
The article Pantera foundation has been proposed for deletion because of the following concern:
No significant coverage to meet WP:ORG.
While all constructive contributions to Wikipedia are appreciated, pages may be deleted for any of several reasons.
You may prevent the proposed deletion by removing the {{proposed deletion/dated}}
notice, but please explain why in your edit summary or on the article's talk page.
Please consider improving the page to address the issues raised. Removing {{proposed deletion/dated}}
will stop the proposed deletion process, but other deletion processes exist. In particular, the speedy deletion process can result in deletion without discussion, and articles for deletion allows discussion to reach consensus for deletion.
This bot DID NOT nominate any of your contributions for deletion; please refer to the history of each individual page for details. Thanks, FastilyBot (talk) 10:00, 23 December 2022 (UTC)
Nomination of Norodom Ekcharin for deletion
The article will be discussed at Wikipedia:Articles for deletion/Norodom Ekcharin until a consensus is reached, and anyone, including you, is welcome to contribute to the discussion. The nomination will explain the policies and guidelines which are of concern. The discussion focuses on high-quality evidence and our policies and guidelines.
Users may edit the article during the discussion, including to improve the article to address concerns raised in the discussion. However, do not remove the article-for-deletion notice from the top of the article until the discussion has finished.