User talk:Andy Dingley
Archives
[edit]- /2007 •
- /2008 1 - 3
- /Archive 4
- /Archive 2009 January
- /Archive 2009 February
- /Archive 2009 March
- /Archive 2009 April
- /Archive 2009 May
- /Archive 2009 June
- /Archive 2009 July
- /Archive 2009 September
- /Archive 2009 October
- /Archive 2009 November
- /Archive 2009 December
- /Archive 2010 January
- /Archive 2011 January
- /Archive 2011
- /Archive 2012
- /Archive 2013
- /Archive 4
- /Archive 5
- /Archive 6
- /Archive 7
- /Archive 8
- /Archive 2014
- /Archive 2015
- /Archive 2016
- /Archive 2017
- /Archive 2018
- /Archive 2019
- /Archive 2020
- /Archive 2021
- /Archive 2022
- /Archive 2023
- /Archive 2024
- /Archive 2025
- /Archive 2026
Nomination of Bridge rail for deletion
[edit]A discussion is taking place as to whether the article Bridge rail is suitable for inclusion in Wikipedia according to Wikipedia's policies and guidelines or whether it should be deleted.
The article will be discussed at Wikipedia:Articles for deletion/Bridge rail 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. 22:53, 24 October 2025 (UTC)
Rolls-Royce C Range Diesels
[edit]Hi Andy
You may remember some years ago (2015?) we had a conversation about the correct title for Rolls-Royce C type diesels - "Range" or "Series". I did mange to find a photo on the www of an RR engine makes plate. This shows that they are "C Range". You can find the photo on the following page: https://www.trms.org.au/rm_engine_frame.htm
Regards Bruce 22:53, 24 October 2025 (UTC)
Speedy deletion nomination of Internally riffled boiler tubes
[edit]
A tag has been placed on Internally riffled boiler tubes requesting that it be speedily deleted from Wikipedia. This has been done under section R3 of the criteria for speedy deletion, because it is a recently created redirect from an implausible typo or misnomer, or other unlikely search term.
If you think this page should not be deleted for this reason, you may contest the nomination by visiting the page and clicking the button labelled "Contest this speedy deletion". This will give you the opportunity to explain why you believe the page should not be deleted. However, be aware that once a page is tagged for speedy deletion, it may be deleted without delay. Please do not remove the speedy deletion tag from the page yourself, but do not hesitate to add information in line with Wikipedia's policies and guidelines. 22:53, 24 October 2025 (UTC)
New Page Patrol newsletter October 2022
[edit]Hello Andy Dingley,

Much has happened since the last newsletter over two months ago. The open letter finished with 444 signatures. The letter was sent to several dozen people at the WMF, and we have heard that it is being discussed but there has been no official reply. A related article appears in the current issue of The Signpost. If you haven't seen it, you should, including the readers' comment section.
Awards: Barnstars were given for the past several years (thanks to MPGuy2824), and we are now all caught up. The 2021 cup went to John B123 for leading with 26,525 article reviews during 2021. To encourage moderate activity, a new "Iron" level barnstar is awarded annually for reviewing 360 articles ("one-a-day"), and 100 reviews earns the "Standard" NPP barnstar. About 90 reviewers received barnstars for each of the years 2018 to 2021 (including the new awards that were given retroactively). All awards issued for every year are listed on the Awards page. Check out the new Hall of Fame also.
Software news: Novem Linguae and MPGuy2824 have connected with WMF developers who can review and approve patches, so they have been able to fix some bugs, and make other improvements to the Page Curation software. You can see everything that has been fixed recently here. The reviewer report has also been improved.

Suggestions:
- There is much enthusiasm over the low backlog, but remember that the "quality and depth of patrolling are more important than speed".
- Reminder: an article should not be tagged for any kind of deletion for a minimum of 15 minutes after creation and it is often appropriate to wait an hour or more. (from the NPP tutorial)
- Reviewers should focus their effort where it can do the most good, reviewing articles. Other clean-up tasks that don't require advanced permissions can be left to other editors that routinely improve articles in these ways (creating Talk Pages, specifying projects and ratings, adding categories, etc.) Let's rely on others when it makes the most sense. On the other hand, if you enjoy doing these tasks while reviewing and it keeps you engaged with NPP (or are guiding a newcomer), then by all means continue.
- This user script puts a link to the feed in your top toolbar.
Backlog:

Saving the best for last: From a July low of 8,500, the backlog climbed back to 11,000 in August and then reversed in September dropping to below 6,000 and continued falling with the October backlog drive to under 1,000, a level not seen in over four years. Keep in mind that there are 2,000 new articles every week, so the number of reviews is far higher than the backlog reduction. To keep the backlog under a thousand, we have to keep reviewing at about half the recent rate!
- Reminders
- Newsletter feedback - please take this short poll about the newsletter.
- If you're interested in instant messaging and chat rooms, please join us on the New Page Patrol Discord, where you can ask for help and live chat with other patrollers.
- Please add the project discussion page to your watchlist.
- If you are no longer very active on Wikipedia or you no longer wish to be a reviewer, please ask any admin to remove you from the group. If you want the tools back again, just ask at PERM.
- To opt out of future mailings, please remove yourself here.
22:53, 24 October 2025 (UTC)
New Pages Patrol newsletter January 2023
[edit]Hello Andy Dingley,

- Backlog
The October drive reduced the backlog from 9,700 to an amazing 0! Congratulations to WaddlesJP13 who led with 2084 points. See this page for further details. The queue is steadily rising again and is approaching 2,000. It would be great if <2,000 were the “new normal”. Please continue to help out even if it's only for a few or even one patrol a day.
- 2022 Awards

Onel5969 won the 2022 cup for 28,302 article reviews last year - that's an average of nearly 80/day. There was one Gold Award (5000+ reviews), 11 Silver (2000+), 28 Iron (360+) and 39 more for the 100+ barnstar. Rosguill led again for the 4th year by clearing 49,294 redirects. For the full details see the Awards page and the Hall of Fame. Congratulations everyone!
Minimum deletion time: The previous WP:NPP guideline was to wait 15 minutes before tagging for deletion (including draftification and WP:BLAR). Due to complaints, a consensus decided to raise the time to 1 hour. To illustrate this, very new pages in the feed are now highlighted in red. (As always, this is not applicable to attack pages, copyvios, vandalism, etc.)
New draftify script: In response to feedback from AFC, the The Move to Draft script now provides a choice of set messages that also link the creator to a new, friendly explanation page. The script also warns reviewers if the creator is probably still developing the article. The former script is no longer maintained. Please edit your edit your common.js or vector.js file from User:Evad37/MoveToDraft.js to User:MPGuy2824/MoveToDraft.js
Redirects: Some of our redirect reviewers have reduced their activity and the backlog is up to 9,000+ (two months deep). If you are interested in this distinctly different task and need any help, see this guide, this checklist, and spend some time at WP:RFD.
Discussions with the WMF The PageTriage open letter signed by 444 users is bearing fruit. The Growth Team has assigned some software engineers to work on PageTriage, the software that powers the NewPagesFeed and the Page Curation toolbar. WMF has submitted dozens of patches in the last few weeks to modernize PageTriage's code, which will make it easier to write patches in the future. This work is helpful but is not very visible to the end user. For patches visible to the end user, volunteers such as Novem Linguae and MPGuy2824 have been writing patches for bug reports and feature requests. The Growth Team also had a video conference with the NPP coordinators to discuss revamping the landing pages that new users see.
- Reminders
- Newsletter feedback - please take this short poll about the newsletter.
- There is live chat with patrollers on the New Page Patrol Discord.
- Please add the project discussion page to your watchlist.
- If you no longer wish to be a reviewer, please ask any admin to remove you from the group. If you want the tools back again, just ask at PERM.
- To opt out of future mailings, please remove yourself here.
22:53, 24 October 2025 (UTC)
New Pages Patrol newsletter June 2023
[edit]Hello Andy Dingley,

Backlog
Redirect drive: In response to an unusually high redirect backlog, we held a redirect backlog drive in May. The drive completed with 23851 reviews done in total, bringing the redirect backlog to 0 (momentarily). Congratulations to Hey man im josh who led with a staggering 4316 points, followed by Meena and Greyzxq with 2868 and 2546 points respectively. See this page for more details. The redirect queue is steadily rising again and is steadily approaching 4,000. Please continue to help out, even if it's only for a few or even one review a day.
Redirect autopatrol: All administrators without autopatrol have now been added to the redirect autopatrol list. If you see any users who consistently create significant amounts of good quality redirects, consider requesting redirect autopatrol for them here.
WMF work on PageTriage: The WMF Moderator Tools team, consisting of Sam, Jason and Susana, and also some patches from Jon, has been hard at work updating PageTriage. They are focusing their efforts on modernising the extension's code rather than on bug fixes or new features, though some user-facing work will be prioritised. This will help make sure that this extension is not deprecated, and is easier to work on in the future. In the next month or so, we will have an opt-in beta test where new page patrollers can help test the rewrite of Special:NewPagesFeed, to help find bugs. We will post more details at WT:NPPR when we are ready for beta testers.
Articles for Creation (AFC): All new page reviewers are now automatically approved for Articles for Creation draft reviewing (you do not need to apply at WT:AFCP like was required previously). To install the AFC helper script, visit Special:Preferences, visit the Gadgets tab, tick "Yet Another AFC Helper Script", then click "Save". To find drafts to review, visit Special:NewPagesFeed, and at the top left, tick "Articles for Creation". To review a draft, visit a submitted draft, click on the "More" menu, then click "Review (AFCH)". You can also comment on and submit drafts that are unsubmitted using the script.
You can review the AFC workflow at WP:AFCR. It is up to you if you also want to mark your AFC accepts as NPP reviewed (this is allowed but optional, depends if you would like a second set of eyes on your accept). Don't forget that draftspace is optional, so moves of drafts to mainspace (even if they are not ready) should not be reverted, except possibly if there is conflict of interest.
Pro tip: Did you know that visual artists such as painters have their own SNG? The most common part of this "creative professionals" criteria that applies to artists is WP:ARTIST 4b (solo exhibition, not group exhibition, at a major museum) or 4d (being represented within the permanent collections of two museums).
Reminders
- Newsletter feedback - please take this short poll about the newsletter.
- There is live chat with patrollers on the New Page Patrol Discord and #wikimedia-npp connect on IRC.
- Please add the project discussion page to your watchlist.
- To opt out of future mailings, please remove yourself here.
22:53, 24 October 2025 (UTC)
Maersk Hangzhou has an RfC
[edit]Maersk Hangzhou has an RfC for possible consensus. A discussion is taking place. If you would like to participate in the discussion, you are invited to add your comments on the discussion page. Thank you. 22:53, 24 October 2025 (UTC)
This arbitration case has been closed and the final decision is available at the link above. The following remedies have been enacted:
- The existing Manual of Style and article titles contentious topic is amended, to narrow the scope to only apply to article titles and capitalisation. The contentious topic area is to be renamed "Wikipedia:Contentious topics/Article titles and capitalisation", and the exact scope is available at the final decision page.
- The word limit restriction (discretionary) is added to the standard set of contentious topic restrictions for all contentious topics:
Uninvolved administrators may impose word limits on all participants in a discussion, or on individual editors across all discussions, within a specific contentious topic area. Citations and quotations (whether from sources, Wikipedia articles, Wikipedia discussions, or elsewhere) do not count toward the word limit. These restrictions must be logged and may be appealed in the same way as all contentious topic restrictions.
- Dicklyon (talk · contribs) is indefinitely banned from Wikipedia. This ban may be appealed twelve months after the enactment of this remedy, and every twelve months thereafter.
- The Arbitration Committee assumes the indefinite topic ban of Dicklyon. This restriction may be appealed twelve months after the enactment of this remedy, and every twelve months thereafter.
- Dicklyon is indefinitely topic banned from challenging or requesting a review of any closure within the article titles and capitalisation contentious topic area, broadly construed. This restriction may be appealed twelve months after the enactment of this remedy, and every twelve months thereafter.
- Cinderella157 (talk · contribs) and SMcCandlish (talk · contribs) are indefinitely topic banned from the article titles and capitalisation contentious topic area, broadly construed. These restrictions may be appealed twelve months after the enactment of this remedy, and every twelve months thereafter.
- Cinderalla157, SMcCandlish, and Dicklyon are limited to 500 words in any discussion related to the article titles and capitalisation contentious topic area, broadly construed.
- Hey man im josh (talk · contribs) is warned for edit warring.
For the Arbitration Committee, HouseBlaster (talk • he/they) 23:47, 22 August 2025 (UTC)
- Discuss this at: Wikipedia talk:Arbitration Committee/Noticeboard § Wikipedia:Arbitration/Requests/Case/Article titles and capitalisation 2 closed 22:53, 24 October 2025 (UTC)
New pages patrol September 2025 Backlog drive
[edit]| September 2025 Backlog Drive | New pages patrol | |
| |
| You're receiving this message because you are a new page patroller. To opt-out of future mailings, please remove yourself here. | |
MediaWiki message delivery (talk) 15:30, 23 August 2025 (UTC)
22:53, 24 October 2025 (UTC)
Hi there! I think I was a bit unclear in the split-request. Reading through the comments on the previous move-request,the consensus was that Grenade was to be kept as the main article about grenades, but that it currently has hand-grenades as priority topic. It was also suggested in the discussion that I'd split off the hand-grenade parts to a separate article in the same manner rifle-grenades has its own main article. As Blockhaj derailed the end of the discussion, I'd like for clarification of your position.
- 1 Are you opposed to have Hand-grenade being a main article with a summary in the article Grenade?
- 2 On a more general note, with an absolute majority of the edits on A being on the topic b which then becomes a separate article, is the best practice to keep the edit history with article A or article B with a split-note in the other, or is there a way to duplicate the edit history to both A and B?
respectfully /BP OMowe (talk) 14:52, 25 September 2025 (UTC)
- I'm not strongly opposed to any changes here. I'm strongly opposed to anything resembling a merge with shell, on the basis of German etymology.
- On the topic of grenades, I see hand grenade as being strongly the core of such an article. It has the historical primacy, it is the most common form of grenade, it is still largely the technical basis of other grenades. We should keep grenade coverage broad, to the point of covering hand grenades to the level that most readers will care about.
- There are a large number of grenade articles. On that basis it's a bit pointless to oppose the creation of an article on hand grenades. But that's not a split – it would be better treated as a new article, for which an easy way to build much of it would be by copying (and a credit via edit summaries and the talk: page) the source of that content. We might then edit both and make one more detailed and even make the other less detailed. What level of detail is appropriate for a reader who wants to read just one article on grenades? There's probably scope for pruning some of the content that has migrated to hand grenade. But the point would be that we've not changed the scope of the grenade article: it still remains as grenades, largely thrown hand grenades. It still covers hand grenades, at least to the level that our hypothetical reader wanting to read just one article on grenades is interested in. Yes, this is duplication. That's not a problem. Yes, it's duplication in both reading content, and in edits (so we note this on the new article talk:). Neither is a problem. What we need to do is to deliver the best choices of scope for the relevant articles (defined by title and an abstract concept of scope, even if we never write that down explicitly). Then deliver the best set of content at each article, as separate problems for each article, according to what their separate scopes require. What we shouldn't do is generate a list of sub-factoids, then allocate each in turn to different articles, avoiding overlap (an editing algorithm I've seen advocated here). That doesn't deliver the best readable and relevant articles. Which is, in the end, what we're supposed to be about.
- I'll copy this over to the article talk: too. Probably better to continue there. Andy Dingley (talk) 21:28, 25 September 2025 (UTC)
- Seems we have a general agreement on both topic and purpose here, and the details are indeed better handled on the talk page. Cheers! BP OMowe (talk) 21:45, 26 September 2025 (UTC)
"Featherless biped" listed at Redirects for discussion
[edit]
The redirect Featherless biped has been listed at redirects for discussion to determine whether its use and function meets the redirect guidelines. Anyone, including you, is welcome to comment on this redirect at Wikipedia:Redirects for discussion/Log/2025 September 30 § Featherless biped until a consensus is reached. -1ctinus📝🗨 14:21, 30 September 2025 (UTC)
Survey
[edit]Hi and thanks for your recent participation in AfD. I would like to hear your thoughts about the process. Please check this survey if you are willing to respond. FYI I found your participation via XTools.Czarking0 (talk) 02:49, 6 October 2025 (UTC)
Tubework (TDLR 7 and 8)
[edit]Hi. Just wanted to drop by to say I'm not an AI. Just thought the term wasn't good enough so I tried a better one. Cheers! — Itzcuauhtli11 (talk) 19:19, 6 November 2025 (UTC)
- But your edit summary implies some sort of 'bot?
- We can't 'find typos' in technical articles by scanning for every word existing in a short dictionary. Didn't we do that some years back, and it was awful? Andy Dingley (talk) 19:21, 6 November 2025 (UTC)
Oops, I thanked you for the wrong edit. Anyways, I'm sure you knew which one I meant. Doesn't appear to be anything useful that can be added to your detailed response, so I'm going to stay out of it. Maybe things will settle, but I have my doubts. Meters (talk) 00:21, 7 November 2025 (UTC)
- One of those instances where shinigami eyes would be useful. We can only wait and see how things develop. Andy Dingley (talk) 00:24, 7 November 2025 (UTC)
- It's a shame most administrators and the general public don't have access to IP addresses or personal information from registered users, isn't it?
- Your digital shinigami eyes are very unfortunately restricted to the Wikimedia Foundation and Check Users.
- I don't know who you're trying to see, though. Is it me? Someone else maybe?
- Aside from being really creepy, you're comment was creative - I have to commend you for that. Deathnotekll2 (talk) 05:19, 7 November 2025 (UTC)
