Stifle
- Older archives
- Archive: 2012
- Archive: 2013
- Archive: 2014
- Archive: January to June 2015
- Archive: July 2015 to 2018
- Archive: 2019
- Archive: 2020-21
- Archive: 2022-23
- Archive: 2024
- Archive: 2025
I consider all my AFD closures carefully. If you object to any of my AFD closures I waive all requirements to discuss with me prior to listing at Wikipedia:Deletion review, but if you would like to discuss one, leave a message.
Replies
edit- Please reply to me here if possible.
- If your message is about an AFD or other discussion that you want me to (re)contribute to, I will generally not reply other than by checking the page and adding a comment.
- I will normally reply here and use {{talkback}} to notify you that I've done so.
- Please don't leave your email address. My email address is user.stifle
gmail.com and you can contact me there if you have a request that needs to be answered privately. However, if you email me with a request that is not private, I will respond on your talk page.
- Exception: if you are requesting the text of a deleted article, then make sure your preferences include a valid, confirmed email address, as I will email the article to you at that address (only).
Administrators' newsletter – January 2026
editNews and updates for administrators from the past month (December 2025).
- All general sanctions imposed by the community may now be enforced at the Arbitration Enforcement noticeboard (WP:AE) as a result of a recent RfC.
- Due to the result of a recent RFC, the administrator recall process is amended to extend the deadline for a re-request for adminship to 30 days or the next administrator election, whichever is later.
- Changes to the Access to Temporary Account IP Addresses Policy's disclosure rules include broadening the consecutive-blocks exception to cover all admin actions and removing the requirement to revision-delete permissible disclosures once they become unnecessary (instead requiring only their removal). See WP:TAIVDISCLOSE for more information.
- Following the 2025 Arbitration Committee elections, the following editors have been elected to the Arbitration Committee: Aoidh, Asilvering, Girth Summit, Guerillero, HJ Mitchell, HouseBlaster, Izno, Sdrqaz, SilverLocust.
- The arbitration case Pbsouthwood has been suspended.
AfD close?
edit@Stifle I assume you meant to redirect the AfD'd article 2025 Toluca Cessna Citation III crash to the proposed target Toluca International Airport#Accidents and incidents? It's currently circular. Chorchapu (talk | edits) 14:12, 13 January 2026 (UTC)
- Dang, I goofed up there. I'll fix it right now. Stifle (talk) 14:13, 13 January 2026 (UTC)
- No worries, thank you. Chorchapu (talk | edits) 14:15, 13 January 2026 (UTC)
Airport destination lists sourcing RfC
editHi there,
I'm leaving this message because you contributed to the recent RfC regarding the inclusion of airport destination lists. As promised, now that that RfC has closed, I've initiated a further discussion about the sourcing standards to be applied to these lists.
If you wish to contribute to the discussion, please do so at Wikipedia:Village pump (policy)#Airport destination lists - sourcing requirements.
An editor has asked for a deletion review of Mo Shaikh. Because you closed the deletion discussion for this page, speedily deleted it, or otherwise were interested in the page, you might want to participate in the deletion review. NBruns (talk) 15:19, 21 January 2026 (UTC)
"Template:Cleanup-since" listed at Redirects for discussion
edit
The redirect Template:Cleanup-since 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/2026 January 23 § Template:Cleanup-since until a consensus is reached. 8BitBros (talk page • contributions) 07:01, 23 January 2026 (UTC)
2019 NFC Divisional playoff game (Seattle-Green Bay)
editLooks like you closed the wrong page. I think it's the emdash. Was trying to figure out why the bot hadn't closed the deletion discussion notice. Esolo5002 (talk) 22:23, 30 January 2026 (UTC)
- Thanks. Yeah, when pages get moved during AFDs the closure scripts can screw up. It looks like it's been fixed now. Stifle (talk) 08:59, 3 February 2026 (UTC)
Administrators' newsletter – February 2026
editNews and updates for administrators from the past month (January 2026).
- Due to the result of a recent motion, a rough consensus of administrators at the arbitration enforcement noticeboard may impose an expanded topic ban on Israel, Israelis, Jews, Judaism, Palestine, Palestinians, Islam, and/or Arabs, if an editor's Arab-Israeli conflict topic ban is determined to be insufficient to prevent disruption. At least one diff per area expanded into should be cited.
- Voting in the 2026 Steward elections started on 06 February 2026 at 14:00 (UTC) and will end on 27 February 2026 at 14:00 (UTC). The confirmation process for current stewards is being held in parallel. You can automatically check your eligibility to vote.
Centralized discussion on the merits of "comparison of X" type articles
editYou suggested at Wikipedia:Articles for deletion/Comparison of version-control software to create a centralized discussion on the merits of "comparison of X" type articles. Where should such discussion be created? Could you create it? Dncmartins (talk) 13:00, 17 February 2026 (UTC)
- Unfortunately I do not have the bandwidth to assist, but you will see some general guidance at WP:CD. Stifle (talk) 08:54, 18 February 2026 (UTC)
Administrators' newsletter – March 2026
editNews and updates for administrators from the past month (February 2026).

- Following an RfC, the web archival service archive.today has been deprecated; links to the site should be removed.
- A request for comment is open to discuss retiring CSD criterion R3 in favour of handling such redirects through RfD.
- Following a motion, remedy 9.1 of the Conduct in deletion-related editing case has been amended to limit TenPoundHammer to one XfD nomination or PROD per 24-hour period.
- Following a motion, the Iskandar323 further POV pushing motion has been rescinded.
- The Arbitration Committee has passed a housekeeping motion rescinding a number of outdated remedies and enforcement provisions across multiple legacy cases. In most instances, existing sanctions remain in force and continue to be appealable through the usual processes, while some case-specific remedies were amended or clarified.
- Following the 2026 Steward Elections, the following editors have been appointed as stewards: A09, AmandaNP, Barras, Count Count, M7, SHB2000, Teles and VIGNERON.
- An Unreferenced articles backlog drive is taking place in March 2026 to reduce the backlog of articles tagged with {{Unreferenced}}. You can help reduce the backlog by adding citations to these articles. Sign up to participate!
HI, I see you've just closed the above discussion. Are you OK to re-open so I can cast a !vote in it? FOARP (talk) 14:52, 3 March 2026 (UTC)
- I closed it 6 hours ago and it had been open for the requisite time. I don't think it would be appropriate to reopen. (I also don't think one more !vote would have tipped the result in any direction.) Stifle (talk) 15:36, 3 March 2026 (UTC)
- I take note that it was, at the time of closing, three deletes, three keeps, and two redirects, so I'm not sure that's true. There's a very good chance, for example, that the three delete !votes might also support the redirect position if asked - I would like the opportunity to ask them about this. For example, if the three delete votes, plus my own !vote, supported redirection, then it would be (at least numerically) conclusively in favour of redirection.
- Would it not be a good idea to give people a chance to reach an actual consensus here? There's no harm in trying anyway. FOARP (talk) 15:49, 3 March 2026 (UTC)
- (Pinging @Nfutvol, Rosbif73, and Pppery: so that they can confirm my understanding that, were this discussion reopened, they would also be able to support redirection as an outcome, and as such re-opening could deliver a consensus for redirection) FOARP (talk) 16:31, 3 March 2026 (UTC)
- These arguments could have been made during the week-plus the AFD was open. It is highly unusual to reopen AFDs because someone didn't !vote in time, and I do not see this as a case where doing so would be appropriate. I decline to do so.
- Redirection is however an editorial action and does not require an AFD, so you are within your rights to seek to gather a consensus for it on the article talk page. Normally I would also say you could use WP:BB but given the sensitivity around this type of article that might not be wise. Stifle (talk) 17:21, 3 March 2026 (UTC)
- I would certainly prefer redirection to the status quo. I have no particular preference as to the method of achieving consensus for that; reopening the AfD would have had the advantage of an uninvolved closer though I fully appreciate that it would be unusual to do so. Let's pursue this at Talk:List of Lufthansa destinations. Rosbif73 (talk) 20:34, 3 March 2026 (UTC)
- I see that editors are citing WP:DESTNOT, which redirects to an outdated consensus. Courtesy pinging @Danners430 to find out whether their most recent RfC has concluded. It may be time to update DESTNOT.
- @Stifle, closing as NC after one week is a bit premature. If a consensus hasn't yet formed this early on, a relist or two could achieve one. This should not have been closed without a single relist. 11WB (talk) 18:27, 17 March 2026 (UTC)
- WP:RELIST states "relisting should not be a substitute for a no consensus closure. If the closer feels there has been substantive discussion, and disparate opinions supported by policy have been expressed, but consensus has not been achieved, a no-consensus close may be preferable", and that is what I followed.
- In any case, we are now over two weeks out from the end of the discussion. It would be inappropriate for me to change my closure now, even if I had been convinced the closure was deficient (which I am not). Stifle (talk) 08:55, 18 March 2026 (UTC)
- I didn't notice the timestamps of the messages until after I posted that. My point on DESTNOT should be considered though. As an aside, once I reply to a discussion I automatically subscribe, so I would have seen your reply without the need for a secondary talk page notice. @Danners430 should probably reply over on my talk page so as to avoid continuing necroposting this discussion. Cheers. 11WB (talk) 09:02, 18 March 2026 (UTC)
- I will leave you to that discussion. I personally think that the seeming crusade to rid Wikipedia of destination lists is mistaken and even harmful, but I do not have the capacity to contribute materially to it.
- (If you automatically subscribe to discussions perhaps you could put a brief header saying so on your talk page, as I have in the past also been criticised for replying only here. There is no convention.) Stifle (talk) 09:10, 18 March 2026 (UTC)
- That's a good idea. I'll add it to the red box I currently have displayed. I was unsure whether you had a user script that automatically posts that notice, as I've also seen them on other user talk pages. 11WB (talk) 09:33, 18 March 2026 (UTC)
"I personally think that the seeming crusade to rid Wikipedia of destination lists is mistaken and even harmful"
- Why are you closing discussions in a field where you have such obviously strong personal views? I wouldn't dream of closing an RFC in this field. FOARP (talk) 19:09, 26 March 2026 (UTC)- Just wanted to say this, but when I opened that RfC last year, I was worried either yourself or @Stifle would close it as not appropriate. Annoyance was expressed but it was allowed to run. @FOARP, from what I've seen, doesn't action any AfD closes anyway, so them closing airport list AfDs is not an issue. @Stifle is active at AfD, and is to some extent WP:INVOLVED in the ongoing airport lists saga. '
Administrators may be incapable of making objective decisions in disputes to which they have been a party or about which they have strong feelings.
' This is policy. !Votes such as this one would suggest as such in @Stifle's case. - If I were an administrator, as somebody who is active within both the aviation and AfD sphere, I would personally recuse myself from closing those AfDs. 11WB (talk) 19:26, 26 March 2026 (UTC)
- I have a feeling @Stifle will likely defend their actions by quoting from the second paragraph of INVOLVED. Just my two pence, feel free to completely disregard it. 11WB (talk) 19:30, 26 March 2026 (UTC)
- Honestly, after making a statement like that, this discussion absolutely should be relisted and closed by someone else. Stifle clearly should not be closing discussion in this field if this is their view. FOARP (talk) 22:31, 26 March 2026 (UTC)
- The only way to overturn it would be at WP:DRV. I can't predict what could happen, but it likely wouldn't be a straightforward overturn. 11WB (talk) 22:37, 26 March 2026 (UTC)
- @Stifle is also permitted to endorse his own close there. 11WB (talk) 22:38, 26 March 2026 (UTC)
- I was happy to let this sit until I saw this statement from Stifle. The discussion should be relisted for closure by an uninvolved editor. Editors who have expressed the view that Stifle shouldn't be closing discussions in this area are clearly correct. FOARP (talk) 22:52, 26 March 2026 (UTC)
- I disagree with the close, however it would go against my own personal philosophy to open a DRV regarding an administrator action. I know @Stifle will disagree with me on this, which I respect. I feel it would be more appropriate for somebody with much more experience to open that. 11WB (talk) 23:18, 26 March 2026 (UTC)
- Oh, I see it's already been opened. I'll direct further correspondence there. 11WB (talk) 23:20, 26 March 2026 (UTC)
- I disagree with the close, however it would go against my own personal philosophy to open a DRV regarding an administrator action. I know @Stifle will disagree with me on this, which I respect. I feel it would be more appropriate for somebody with much more experience to open that. 11WB (talk) 23:18, 26 March 2026 (UTC)
- I was happy to let this sit until I saw this statement from Stifle. The discussion should be relisted for closure by an uninvolved editor. Editors who have expressed the view that Stifle shouldn't be closing discussions in this area are clearly correct. FOARP (talk) 22:52, 26 March 2026 (UTC)
- @Stifle is also permitted to endorse his own close there. 11WB (talk) 22:38, 26 March 2026 (UTC)
- The only way to overturn it would be at WP:DRV. I can't predict what could happen, but it likely wouldn't be a straightforward overturn. 11WB (talk) 22:37, 26 March 2026 (UTC)
- Honestly, after making a statement like that, this discussion absolutely should be relisted and closed by someone else. Stifle clearly should not be closing discussion in this field if this is their view. FOARP (talk) 22:31, 26 March 2026 (UTC)
- I have a feeling @Stifle will likely defend their actions by quoting from the second paragraph of INVOLVED. Just my two pence, feel free to completely disregard it. 11WB (talk) 19:30, 26 March 2026 (UTC)
- Just wanted to say this, but when I opened that RfC last year, I was worried either yourself or @Stifle would close it as not appropriate. Annoyance was expressed but it was allowed to run. @FOARP, from what I've seen, doesn't action any AfD closes anyway, so them closing airport list AfDs is not an issue. @Stifle is active at AfD, and is to some extent WP:INVOLVED in the ongoing airport lists saga. '
- That's a good idea. I'll add it to the red box I currently have displayed. I was unsure whether you had a user script that automatically posts that notice, as I've also seen them on other user talk pages. 11WB (talk) 09:33, 18 March 2026 (UTC)
- I didn't notice the timestamps of the messages until after I posted that. My point on DESTNOT should be considered though. As an aside, once I reply to a discussion I automatically subscribe, so I would have seen your reply without the need for a secondary talk page notice. @Danners430 should probably reply over on my talk page so as to avoid continuing necroposting this discussion. Cheers. 11WB (talk) 09:02, 18 March 2026 (UTC)
- I'd love to know why that ping never went through - I just stumbled upon this in my watchlist...
- No, there is no change in the position with regards to notability of airline destination lists - that RfC closed with No Consensus. The current RfC purely and only relates to the sourcing requirements, specifically whether to overturn the consensus regarding the banning of primary sources in these lists. As far as I'm aware, normal WP:NLIST requirements apply to standalone lists - where there aren't sufficient non-primary sources available, it should be merged into the main article. Please correct me if I'm incorrect in this thinking! Danners430 tweaks made 16:26, 18 March 2026 (UTC)
- Oh... well that's not great to hear. I had hoped a resolution would have formed. Whilst I'm here momentarily, I'll take the opportunity to apologise to @Stifle for necroposting this already ended discussion. My comment on the close they enacted, whilst I believe is fair, was not necessary, as this was a resolved matter. I'll take more care to observe timestamps in the future when passing through the talk pages of other editors. 11WB (talk) 17:13, 18 March 2026 (UTC)
- Yeah, it is what it is... the nonsense continues... I think I'm now up to having three threads open at ANI at the same time, and all of them go back to airport articles... Danners430 tweaks made 17:16, 18 March 2026 (UTC)
- Oh... well that's not great to hear. I had hoped a resolution would have formed. Whilst I'm here momentarily, I'll take the opportunity to apologise to @Stifle for necroposting this already ended discussion. My comment on the close they enacted, whilst I believe is fair, was not necessary, as this was a resolved matter. I'll take more care to observe timestamps in the future when passing through the talk pages of other editors. 11WB (talk) 17:13, 18 March 2026 (UTC)
- (Pinging @Nfutvol, Rosbif73, and Pppery: so that they can confirm my understanding that, were this discussion reopened, they would also be able to support redirection as an outcome, and as such re-opening could deliver a consensus for redirection) FOARP (talk) 16:31, 3 March 2026 (UTC)
Happy Adminship Anniversary!
editReprotecting Rolf Harris
editHello, @Stifle. Are you interested in reinstating the inder semi-prot that used to be imposed on Rolf Harris? Vandalism from TAs has been a consistent presence in the revision history since you unlocked the page last year as a WP:TRYUNPROT experiment. Giovanni Potage (talk) 16:14, 18 March 2026 (UTC)
- I actually unprotected the page last year because the protection was based in BLP and he had ceased to be L. That being said, I see there is sufficient cause to reinstate semi-protection and I have done so. Stifle (talk) 17:58, 18 March 2026 (UTC)
- Thanks! Giovanni Potage (talk) 17:59, 18 March 2026 (UTC)
Deletion review for List of Lufthansa destinations
editAn editor has asked for a deletion review of List of Lufthansa destinations. Because you closed the deletion discussion for this page, speedily deleted it, or otherwise were interested in the page, you might want to participate in the deletion review. FOARP (talk) 22:47, 26 March 2026 (UTC)
Administrators' newsletter – April 2026
editNews and updates for administrators from the past month (March 2026).

- The content of Wikipedia:Writing articles with large language models has been updated following a request for comment. It now prohibits using LLMs to generate content, with exceptions for translation and copy-editing.
- Following a motion, the GSCASTE extended-confirmed restriction in the Indian military history case has been narrowed. It now applies to caste-related topics in South Asia, and the preemptive protection remedy has been amended accordingly.
- The arbitration case Pbsouthwood has been closed.
- The arbitration case Maghreb has been opened. Evidence submissions in this case will close on 7 April.
ANI
editHello, I hope you are well. I wanted to inform you that you have been mentioned (although not by name) at WP:ANI. Under the section "User:Borgensanal, LLM use, AfDs". https://en.wikipedia.org/wiki/Wikipedia:Administrators%27_noticeboard/Incidents#User:Borgensanal,_LLM_use,_AfDs Cheers (hope you're enjoying the vacation!), 🚂ThatTrainGuy1945 Peep peep! 00:52, 7 April 2026 (UTC)
- Thanks. This appears to all have resolved itself while I was away. Stifle (talk) 08:04, 23 April 2026 (UTC)
Administrators' newsletter – May 2026
editNews and updates for administrators from the past month (April 2026).

Interface administrator changes
- Changes to user permissions made from Meta are now included in the local user permissions log (T6055).
- The autoconfirmed user group will soon be modified such that the four-day account age requirement begins when an account makes its first edit (T418484).
- The arbitration case SchroCat has been opened. Evidence submissions in this case closed on 15 April.
- Per a recent motion, appeals of blocks from the conflict-of-interest VRT queue are, by default, appealed on-wiki through the normal unblock process. However, they may be heard by the Committee if COIVRTers disagree on the interpretation of the evidence or believe ArbCom would be better suited to hear the appeal. Administrators are also advised that loosening or lifting such blocks without the consent of someone with access to the queue or ArbCom can be grounds for desysopping.
- Per a recent motion, restrictions issued directly by the Committee may now be enforced with blocks which work exactly like contentious topic blocks.
- The arbitration case Maghreb has been closed.
- The May 2026 administrator elections are scheduled to run from April 29 to May 19. The call for candidates ends May 5.
- The 2026 Universal Code of Conduct Coordinating Committee (U4C) election is scheduled to run from April 25 to June 1. Candidacy submissions close on May 10.
- A new noticeboard for non-urgent, batch page protection requests has been created, primarily for the enforcement of contentious topic restrictions.
Administrators' newsletter – June 2026
editNews and updates for administrators from the past month (May 2026).

- Following an RfC, the "persistent usage of large language models" has been included as a common reason for a block.
- Mandatory 2FA for bureaucrats: Bureaucrats without two-factor authentication (2FA) enabled have already lost access to their advanced rights on 26 May. Those who do not enable 2FA may be automatically removed from the groups in mid-June 2026, and from that point onward, new members must have 2FA enabled before they can be added. (T423119, T423120)
- The arbitration case SchroCat has been closed.
- The arbitration case Michael Jackson has opened. Evidence submissions in this case closes on 1 June.
- Voting for the 2026 Universal Code of Conduct Coordinating Committee (U4C) election closes on 1 June.

