Edge Rewrite
// HTMLRewriter · presentation

This page was redesigned at the edge.

Cloudflare fetched the original article and streamed it through HTMLRewriter to apply an entirely new visual system without rebuilding the source page.

Jump to content

Wikipedia:Deletion review

From Wikipedia, the free encyclopedia
(Redirected from Wikipedia:DELETIONREVIEW)

Deletion review (DRV) is for reviewing speedy deletions and outcomes of deletion discussions. This includes appeals to delete pages kept after a prior discussion.

If you are considering a request for a deletion review, please read the "Purpose" section below to make sure that is what you wish to do. Then, follow the instructions below.

Purpose

Deletion review may be used:

  1. if someone believes the closer of a deletion discussion interpreted the consensus incorrectly;
  2. if a speedy deletion was done outside of the criteria or is otherwise disputed;
  3. if there were substantial procedural errors in the deletion discussion or speedy deletion (including information of socks participating in the discussion);
  4. if significant new information has come to light since a deletion that would justify undeleting the page, and previously deleted content may be helpful for writing a new version of the page – provided that an administrator declined undeleting the page and their decision is being challenged;
  5. if a page has been wrongly deleted with no way to tell what exactly was deleted;
  6. if the deleted page cannot be recreated because of preemptive restrictions on creation that cannot be removed without a consensus after removal was requested and declined. Such restrictions include creation protection and title blacklisting.

Deletion review should not be used:

  1. if the page was deleted on grounds which permits summary undeletion: place such requests at Wikipedia:Requests for undeletion. Deletion review can be used if such a request is declined. (Undeletion may also be requested there for pages which are not explicitly eligible for summary undeletion, but such a request is usually declined; it is worth trying when substantial new sources have arisen after an article was deleted.)
  2. to ask for permission to write a new version of a page which was deleted, unless a preemptive restriction on creation is in place for which removal was requested and declined. In the case of:
  3. because of a disagreement with the deletion discussion's outcome that does not involve the closer's judgment (a page may be renominated after a reasonable timeframe);
  4. to repeat arguments already made in the deletion discussion;
  5. to argue technicalities (such as a deletion discussion being closed ten minutes early);
  6. to point out other pages that have or have not been deleted (as each page is different and stands or falls on its own merits);
  7. to challenge an article's deletion via the proposed deletion process, or to have the history of a deleted page restored behind a new, improved version of the page, called a history-only undeletion (please go to Wikipedia:Requests for undeletion for these);
  8. to request that previously deleted content be used on other pages (please go to Wikipedia:Requests for undeletion for these requests);
  9. to attack other editors, cast aspersions, or make accusations of bias (such requests may be speedily closed);
  10. to request that copyright violations, libelous, or otherwise prohibited content be restored.

Instructions

Steps to list a new deletion review

Before listing a review request, please:

  1. Consider attempting to discuss the matter with the closer as this could resolve the matter more quickly. There could have been a mistake, miscommunication, or misunderstanding, and a full review may not be needed. Such discussion also gives the closer the opportunity to clarify the reasoning behind a decision.
  2. Check that it is not on the list of perennial requests. Repeated requests every time some new, tiny snippet appears on the web have a tendency to be counter-productive. It is almost always best to play the waiting game unless you can decisively overcome the issues identified at deletion.
  3. Be aware that requests which appear to be written by large-language models will normally be summarily denied. Write in your own words.
 
1.

Click here and paste the template skeleton at the top of the discussions (but not at the top of the page). Then fill in page with the name of the page, xfd_page with the name of the deletion discussion page (leave blank for speedy deletions), and reason with the reason why the discussion result should be changed. For media files, article is the name of the article where the file was used, and it shouldn't be used for any other page. For example:

{{subst:drv2
|page=File:Foo.png
|xfd_page=Wikipedia:Files for deletion/2009 February 19#Foo.png
|reason=
}} ~~~~
2.

Inform the editor who closed the deletion discussion by adding the following on their user talk page:

{{subst:DRV notice|PAGE_NAME}} ~~~~
3.

For nominations to overturn and delete a page previously kept, attach <noinclude>{{Delrev|date=2026 September 24}}</noinclude> to the top of the page under review to inform current editors about the discussion.

4.

Leave notice of the deletion review outside of and above the original deletion discussion:

  • If the deletion discussion's subpage name is the same as the deletion review's section header, use <noinclude>{{Delrevxfd|date=2026 September 24}}</noinclude>
  • If the deletion discussion's subpage name is different from the deletion review's section header, then use <noinclude>{{Delrevxfd|date=2026 September 24|page=SECTION HEADER AT THE DELETION REVIEW LOG}}</noinclude>
 

Commenting in a deletion review

Any editor may express their opinion about an article or file being considered for deletion review. In the deletion review discussion, please type one of the following opinions preceded by an asterisk (*) and surrounded by three apostrophes (''') on either side. If you have additional thoughts to share, you may type this after the opinion. Place four tildes (~~~~) at the end of your entry, which should be placed below the entries of any previous editors:

  • Endorse the original closing decision; or
  • Relist on the relevant deletion forum (usually Articles for deletion); or
  • List, if the page was speedy deleted outside of the established criteria and you believe it needs a full discussion at the appropriate forum to decide if it should be deleted; or
  • Overturn the original decision and optionally an (action) per the Guide to deletion. For a keep decision, the default action associated with overturning is delete and vice versa. If an editor desires some action other than the default, they should make this clear; or
  • Allow recreation of the page if new information is presented and deemed sufficient to permit recreation.

Examples of opinions for an article that had been deleted:

  • *'''Endorse''' The original closing decision looks like it was sound, no reason shown here to overturn it. ~~~~
  • *'''Relist''' A new discussion at AfD should bring a more thorough discussion, given the new information shown here. ~~~~
  • *'''Allow recreation''' The new information provided looks like it justifies recreation of the article from scratch if there is anyone willing to do the work. ~~~~
  • *'''List''' Article was speedied without discussion, criteria given did not match the problem, full discussion at AfD looks warranted. ~~~~
  • *'''Overturn and merge''' The article is a content fork, should have been merged into existing article on this topic rather than deleted. ~~~~
  • *'''Overturn and userfy''' Needs more development in userspace before being published again, but the subject meets our notability criteria. ~~~~
  • *'''Overturn''' Original deletion decision was not consistent with current policies. ~~~~

Remember that deletion review is not an opportunity to (re-)express your opinion on the content in question. It is an opportunity to correct errors in process (in the absence of significant new information), and thus the action specified should be the editor's feeling of the correct interpretation of the debate. Deletion review is facilitated by succinct discussions of policies and guidelines; long or repeated arguments are not generally helpful. Rather, editors should set out the key policies and guidelines supporting their preferred outcome.

The presentation of new information about the content should be prefaced by Relist, rather than Overturn and (action). This information can then be more fully evaluated in its proper deletion discussion forum. Allow recreation is an alternative in such cases.

The usage of large language models such as ChatGPT to create deletion review nominations or comments is strongly discouraged and such contributions are liable to be removed or collapsed by an uninvolved administrator.

Temporary undeletion

Admins participating in deletion reviews are routinely requested to restore deleted pages under review and replace the content with the {{temporarily undeleted}} template, leaving the history for review by everyone. However, copyright violations and violations of the policy on biographies of living persons should not be restored.

Closing reviews

A nominated page that requires a community consensus decision should remain on deletion review for at least seven days (unless the nomination was a proposed deletion). In such cases, an administrator will determine whether a consensus exists after seven days. If that consensus is to undelete, the admin should follow the instructions at Wikipedia:Deletion review/Administrator instructions. If the consensus was to relist, the page should be relisted at the appropriate forum. If the consensus was that the deletion was endorsed, the discussion should be closed with the consensus documented.

If the administrator closes the deletion review as no consensus, the outcome should generally be the same as if the decision was endorsed. However:

  • If the decision under appeal was a speedy deletion, the page(s) in question should be restored, as it indicates the deletion was not uncontroversial. The closer, or any editor, may then proceed to nominate the page at the appropriate deletion discussion forum, if they so choose.
  • If the decision under appeal was an XfD close, the closer may, at their discretion, relist the page(s) at the relevant XfD.

Ideally, all closes should be made by an administrator to ensure that what is effectively the final appeal is applied consistently and fairly. But, in cases where the outcome is patently obvious, it is permissible for a non-admin (ideally a DRV regular) to close discussions. Non-consensus closes should be avoided by non-admins unless they are absolutely unavoidable and the closer is sufficiently experienced at DRV to make that call. (Hint: if you are not sure that you have enough DRV experience then you don't.)

Early closes
  • An objection to a proposed deletion can be processed immediately as if it were a request at Wikipedia:Requests for undeletion.
  • Where the deletion discussion has reopened or changed, either by the closer of the deletion discussion or by an uninvolved administrator who has vacated a procedurally invalid non-administrative close,[a] and nobody has endorsed. In this case, the deletion review may be speedily closed as overturned or relisted as appropriate. The closer should fully reverse their close, restoring any deleted pages if appropriate.
  • Where the nominator of a DRV has withdrawn their nomination, and no one has recommended any outcome but endorse, the nominator may speedily close as "endorse" (or ask someone else to do so for them).
  • Where the closer of a deletion discussion acknowledges that their close was wrong, and no one has endorsed, the closer may speedily close as overturn. They should fully reverse their close, restoring any deleted pages if appropriate.
  • Discussions may be closed without result if they are entirely disruptive. (e.g. disruptive or sockpuppet nominations, repeated nominations of the same page, a large language model is used to construct the request, or the page is listed at WP:DEEPER). These will usually be marked as "procedural close".
  1. ↑ Challenges regarding whether a non-admin closure was contentious or correctly assessed consensus should be addressed through Deletion Review.


[[:<JAKE FLORES>]]

JAKE FLORES (talk|edit|history|logs|links|watch) (revisions|restore)

<Someone impersonated me to make it look like I was editing my own page> Feraljokes (talk) 07:44, 23 September 2026 (UTC)reply

The following is an archived debate of the deletion review of the page above. Please do not modify it.
Ken Silverstein (business journalist) (talk|edit|history|logs|links|watch) (XfD|revisions|restore)

The closer discarded two valid Keep !votes as “LLM-generated” without evidence, verification, or policy-required justification. This materially altered the outcome of the discussion.

The closer wrote: “I have discarded the LLM-generated ‘keep’ !vote(s) per WP:AITALK… Discarding the LLM-generated !vote results in a rough consensus to delete.”

This was a procedural error:

- WP:AITALK does not permit discarding comments based on subjective impressions or guesses.
- Wikipedia has no mechanism to detect LLM-generated text.
- No evidence was provided that either Keep !vote was AI-generated.
- Both Keep !votes were from established editors acting in good faith.
- Discarding them changed the outcome from a mixed discussion to a mechanical Delete.
- The closer did not evaluate the arguments, evidence, or consensus; the closure rested entirely on the assumption of AI use.

I am not asking DRV to decide the merits of the article. I am asking DRV to review a closure where the closer’s guess about LLM use determined the result. This is a procedural issue appropriate for DRV. For those of us who choose to write thoughtfully presentations rather than hurried responses, it is a bit disconcerting.

I request that the AfD be overturned and either:
- restored for a new AfD discussion, or
- restored for a non-procedural close based on the full set of !votes. JEFeditor (talk) 17:38, 22 September 2026 (UTC)reply

  • Endorse. Even if we accept the appellant's !vote as not being LLM-generated, consensus is still to delete. Like Dclemens1971, I discard the canvassed SPA created to promise a forthcoming profile based on an interview with the subject. So we're left with three !votes to delete, from experienced editors, and one !vote to keep, from an editor with under 200 edits, and zero other AfD participation. The nom patiently engaged with the appellant regarding the source assessment, but I sense a certain tendentious obstinance from the appellant. I believe Dclemens1971 was restrained when they referred to the consensus as "rough". To me, it's a clear consensus. Owen× ☎ 18:37, 22 September 2026 (UTC)reply
  • Comment app.gptzero.me says that this appeal was generated by AI with 100% probability. Kelob2678 (talk) 18:43, 22 September 2026 (UTC)reply
Endorse own close for reasons stated in closing statement. The appellant is entirely wrong that the close depended on the appellant’s use of AI; consensus existed in the absence of AI use because the “keep” rationale was not persuasive to other participants. (The appellant should probably be sanctioned for their ongoing use of LLMs on talk pages even after a warning.) Dclemens1971 (talk) 19:07, 22 September 2026 (UTC)reply
Comment. I believe I just spent more time on my user talk page demonstrating the many WP:AISIGNS present in the appellant's AfD contributions and DRV appeal than they spent composing them. Dclemens1971 (talk) 22:20, 22 September 2026 (UTC)reply
Endorse. Only one editor at the AfD, the nominator here, tried to argue keep, and they began “ The June 2026 Parkersburg News and Sentinel feature is substantial, independently reported coverage of Silverstein’s career”, which is completely wrong. Not independent. SmokeyJoe (talk) 23:24, 22 September 2026 (UTC)reply
  • (ec) Endorse (uninvolved) Largely per Owen above, and wait… what would have been the outcome though? This looks exactly like a I don't like the outcome problem. Vanderwaalforces (talk) 19:09, 22 September 2026 (UTC)reply
  • Endorse. I don’t see evidence confirming the two keep votes are AI generated and should be stricken. However, these votes are weak. The three delete votes were much stronger and better rooted in policy, showing a clear consensus to delete. Frank Anchor 19:27, 22 September 2026 (UTC)reply
  • Endorse and speedy close as both this and the disputed !votes are clearly AI. It's not hard to NOT sound like an AI, but this sounds like AI UPE. I agree that the nominator should be sanctioned. Jclemens (talk) 22:55, 22 September 2026 (UTC)reply
Why does AI always write "I am not asking [forum] to do [thing I actually want them to do]". Helpful Raccoon (talk) 00:19, 23 September 2026 (UTC)reply
Endorse deletion. Questions on AI use aside, no one brought a 2nd substantive, independent source (where the subject may have published their writing being beside the point). Notability requirements have not been met. There is no way this could have been closed any different.y. If and when additional substantive independent reporting about the subject does appear (i.e. not is promised for the future, but has appeared), a fresh appeal may be made here, and the quality of the sourcing can be re-evaluated. However, it the tone of the appeal is similar to the JEFeditor's here, I expect fresh questions about LLM use and COI will be asked before anyone engages on the substance. Martinp (talk) 00:36, 23 September 2026 (UTC)reply
The above is an archive of the deletion review of the page listed in the heading. Please do not modify it.
The following is an archived debate of the deletion review of the page above. Please do not modify it.
Talk:accidentally a word (talk|edit|history|logs|links|watch) (revisions|restore)

I used this figure of speech in a text conversation with coworkers. I was under the perception intentionally ommitting a word when describing that you or someone else (forgot) a word was a well-enough understood use of memetic language. I was surprised however when no one realized I had done this intentionally. I rushed to the internet to justify myself to them, checking known your meme and wikipedia for any sort of page confirming this linguistic phenomenon existed, but the only remnant of it's existence at all that I could find was a long-forgotten RFD page from 2018 denying it's entry into Wikipedia-ic record. Amusingly, one of the editors comments "I can't imagine any user looking it up, either." Hello, from 8 years later, it's me, I'm the user looking it up. - In further support of my request for 'Accidentally a word' to be admitted into the great cultural record that is Wikipedia, I posit that the deletion of this page was made initially on the basis that 'Accidentally a word' is not a sufficiently prominent quirk of the ENGLISH LANGUAGE to be recorded. This is a misunderstanding of the nature of 'Accidentally a word.' Accidentally a word is an early internet meme in the sense we understand current internet memes to be. I suspect the understanding of internet culture, the definition of a meme, and their cultural relevance was not fully understood by the editors 8 years ago, as those ideas themselves had not yet calcified in to the extent they have today. For these reasons, I submit that the original definition in it's full text should be restored to Wikipedia. Here is the full text: accidentally a word

"(humorous) To unintentionally omit a word." It seems that what is being described here is a grammatical practice (humorously omitting an element of the syntax in order to emphasise an omission of another kind): you can, for example, find deliberate uses of "I accidentally a sentence" in Google.

I am a long time user, first time contributor to Wikipedia, I made and account specifically for the purpose of creating this review, apologies in advance for any procedural mistakes I may have made. I hope that an editor with more experiecen takes pity on my review request and may help to lift it to the exceptional quality standards Wikipedia is known for. Accidentally-a-user (talk) 17:21, 18 September 2026 (UTC)reply

The above is an archive of the deletion review of the page listed in the heading. Please do not modify it.
The following is an archived debate of the deletion review of the page above. Please do not modify it.
Timeline of United States inventions (1946–1991) (talk|edit|history|logs|links|watch) (XfD|revisions|restore)

Overturn. I recently nominated the rest of the Timeline of United States inventions series for deletion, and consensus was found to keep them, so I think this means that consensus may have changed. If we're going to maintain a timeline that's split between a few articles, it shouldn't have a gap like this. – MrPersonHumanGuy (talk) 14:32, 17 September 2026 (UTC)reply

  • Allow recreation (involved). There was nothing wrong with 2024 close, but clearly views have changed. I still believe the selection criteria are arbitrary, non-encyclopedic listcruft, but that's an argument for AfD, not DRV. I see no reason to refuse the appellant a chance to present this again to the community, and the most efficient way to do that is by restoring the page in mainspace and renominating. Owen× ☎ 14:47, 17 September 2026 (UTC)reply
  • Allow recreation Robert McClenon (talk) 17:08, 17 September 2026 (UTC)reply
The above is an archive of the deletion review of the page listed in the heading. Please do not modify it.
The following is an archived debate of the deletion review of the page above. Please do not modify it.
Macklemore–Ed Sheeran tour controversy (talk|edit|history|logs|links|watch) (XfD|revisions|restore)

Discussion closed as "SNOW Keep" by non-admin after only a few hours of discussion. One contributor invoked SNOW after only 5 !votes, and others then piled on. I think this deserves at least some more consideration. ZimZalaBimtalk 22:22, 16 September 2026 (UTC)reply

Note to others: This refers to this AFD, which is the first one, closed as snow keep. A second one was opened less than an hour later and closed again due to the recent snow keep result. Skyshiftertalk 22:29, 16 September 2026 (UTC)reply
Pinging participants of both AFDs: @MagicatthemovieS, MidnightMayhem, Spiderone, Sergecross73, EditorShane3456, WhiteTailedEagle, Why? I Ask, KoRoBeNiKi, Boredintheevening, Jdcomix, Tbhotch, Cheromaniii, Apoxyomenus, and TechnoSquirrel69: Skyshiftertalk 22:35, 16 September 2026 (UTC)reply
Endorse, and speedy close this discussion. Looks like a pretty obvious clear unanimous consensus for a keep. Servite et contribuere (talk) 02:40, 17 September 2026 (UTC)reply
(And just for further note, I did not participate in any of those AFDS) Servite et contribuere (talk) 02:42, 17 September 2026 (UTC)reply
  • Endorse, I don't see how this is not notable after seeing so many coverage on the news, there also isn't anyone that seems to support the deletion from the AfD and current DR. Syn73 (talk) 03:29, 17 September 2026 (UTC)reply
  • Endorse (non-participant): I don't see any way these discussions could have been closed with any outcome other than keeping, given the unanimous and overwhelming consensus to keep. Invoking a SNOW close after only 5 votes might be premature (and might be worthy of a WP:MINNOW), but doing so would not have changed the outcome. Umby 🌕🐶 (talk) 03:44, 17 September 2026 (UTC)reply
  • Sigh Are we doing this again? Apparently so. 1) People, stop rushing to AfD something that's still in the news cycle! 2) NAC'ers, please don't SNOW close things; let an admin do it. 3) Stop trying to shortcut now to an eventual result. I bet this is eventually merged into the tour as proposed in the second AfD, but today, this week, or even this month are probably not the right times to try that. We look like idiots, ideologues, censors, and more to the rest of the world when we do this on high visibility articles. There will be time enough to clean things up later, but now it generates more heat than light. Oh, and endorse as the appropriate result of the discussion, despite my misgivings on the process and hastiness. Jclemens (talk) 07:00, 17 September 2026 (UTC)reply
  • Endorse, definitely needs an article, due to all the news coverage. Article was never going to be deleted anyway, even if the discussion hadn't been closed. Sahaib (talk) 07:37, 17 September 2026 (UTC)reply
  • Endorse per Jclemens, with additional endorsement on NACs not snow-closing. Stifle (talk) 08:46, 17 September 2026 (UTC)reply
  • Endorse the close of Snow Keep, but give a minnow to the closer for snow closing the AFC when there were admins who could snow close the AFD. Robert McClenon (talk) 10:21, 17 September 2026 (UTC)reply
  • Endorse (non-participant) and suggesting that this DRV also be WP:AVALANCHE closed. Warm Regards, Miminity (Talk?) (me contribs) 14:29, 17 September 2026 (UTC)reply
  • Endorse both per Jclemens. NACs should not close a discussion early, especially within the first few hours of a dicussion unless the nomination is clearly frivolous or disruptive. --Enos733 (talk) 15:23, 17 September 2026 (UTC)reply
The above is an archive of the deletion review of the page listed in the heading. Please do not modify it.
  • Lenox Tweneboa – Restored to draft, speedily. This is about factors having changed, not about a 7 year old deletion discussion. Nom and anyone else welcome to edit the draft and move it to mainspace if they see merit. A new AfD can happen if folks think it's necessary Star Mississippi 00:30, 17 September 2026 (UTC)reply
The following is an archived debate of the deletion review of the page above. Please do not modify it.
Lenox Tweneboa (talk|edit|history|logs|links|watch) (XfD|revisions|restore)

The reasons for deletion are contended on the following matters: The Myanmar National League is listed as a fully professional league per below: https://en.wikipedia.org/wiki/Wikipedia:WikiProject_Football/Fully_professional_leagues

The following historic video links provide evidence of the subject competing in the Myanmar National League (MNL) as a professional athlete in 2013: https://www.youtube.com/watch?v=Feu8MMiqtUE#t=0m58s https://www.youtube.com/watch?v=SSZnFoWAjN4#t=1m47s https://www.youtube.com/watch?v=1cN3YGzWsRg https://www.youtube.com/watch?v=cBRJVCcddyo

The subject is listed on World football as having competed in Myanmar during the season of 2013, wearing number 16, which is also evidenced in the above video links of nationally televised competition matches: https://www.worldfootball.net/person/pe305585/

The subject is listed on PlayMaker as having competed in Myanmar during the season of 2013, wearing number 16, which is also evidenced in the above video links of nationally televised competition matches. https://www.playmakerstats.com/player/lenox-tweneboa/239713?epoca_id=142

The subject is published as an overseas Australian professional football athlete in the Myanmar National League in 2013 within the OZFootball Database dated 2013: http://www.ozfootball.net/ark/Abroad/2013-01.html ~2026-49965-43 (talk) 02:00, 16 September 2026 (UTC)reply

The above is an archive of the deletion review of the page listed in the heading. Please do not modify it.
File:LucileRandon2019.webp (talk|edit|history|logs|links|watch) (article|XfD|revisions|restore)
File:Jeanne-Calment-1996.jpg (talk|edit|history|logs|links|watch) (article|XfD|revisions|restore)
File:Kane Tanaka 117.webp (talk|edit|history|logs|links|watch) (article|XfD|revisions|restore)
File:SarahKnauss1979.jpg (talk|edit|history|logs|links|watch) (article|XfD|revisions|restore)

These articles were nominated by a user back in January 2023 on the grounds that since we already had photos of them, they failed the WP:NFCC. All four individuals are supercentenarians, in fact, some of the oldest people in recorded history, and these free images of them were are only so since they were of them well in their youth. WP:NFC#UULP outlines an exception for images that even if free images are available, if they are of the subject when they're older and the subject was notable in their youth, an older non free image can be used under the relevant criteria. It can be argued that the same can apply for supercentenarians who only become notable in their late life and only having free images of them when they were much younger. The first two nominations encountered some opposition on this basis (although they didn't explicitly cite the policy), and there was a lack of consensus, but the first was deleted as Textbook WP:NFCC#1/WP:NFCC#8 violation, which set the precedent for the other four (which were mentioned in the first discussion. I am coming here to see if these images would pass under WP:NFC#UULP, since following it in spirit would mean that these files shouldn't have been deleted. — Knightoftheswords(talk) 15:24, 15 September 2026 (UTC)reply

  • I don't see how Joseph2302's ban three years later is at all relevant, except to the extent that it removes someone who'd oppose your position if you get a second bite at this apple. —Cryptic 16:41, 15 September 2026 (UTC)reply
    Normally I would ping the user to get them to discuss/be made aware, but since Joseph was banned, I didn't want to for WP:GRAVEDANCING reasons, so I just stated that they were banned as an explanation for why I couldn't. (Edit: since that generated more heat than light, I'm removing it; in retrospect, I can see why that might have seemed off being in the lead sentence like that). — Knightoftheswords(talk) 18:08, 15 September 2026 (UTC)reply
  • This is an extremely distasteful nomination given that the now banned user has over 80,000 edits, was only recently banned and this was over 3 years ago. It distinctly has a strong smell of gravedancing and I implore the nominator to withdraw this. Spartaz Humbug! 16:46, 15 September 2026 (UTC)reply
  • Endorse all. An interesting take on WP:NFC#UULP, with a tasteless side of gravedancing, but ultimately devoid of merit. The UULP carve-out is for individuals whose notability rests in large part on their earlier visual appearance. Even if we remove the word earlier as the appellant suggests, we're still left with a falsehood. None of these four supercentenarians was notable for his or her visual appearance--at any age. We have free images for all four, and the refs from each will take readers to more images, including at least one each for a photo near their time of death. There's no justification for adding a non-free image just to see what they looked like at 115 years old, unless a section is added to specifically discuss their appearance at that age. Owen× ☎ 17:02, 15 September 2026 (UTC)reply
    • Jeanne Calment does have multiple sourced statements about her appearance, so there's some basis for meeting NFCC#8 and 1 there. The "earlier visual appearance" language is an exception to "Pictures of people still alive... provided that taking a new free picture as a replacement (which is almost always considered possible) would serve the same encyclopedic purpose as the non-free image"; it's not really relevant. (The other three articles don't mention appearance at all.) —Cryptic 17:59, 15 September 2026 (UTC)reply
  • Concerns of the nominator's motivation aside (I agree any years-later CBAN is irrelevant), Overturn the deletion of the first one since the closure didn't reflect the consensus of the discussion. I know in some cases FfD admins have to act as policy experts in a way that wouldn't be tolerated in other venues given the degree to which file decisions can have legal significance. But the dispute here is really "does this image add value to the article" which should be a matter for normal consensus not supervotes, and the discussion didn't have a consensus to delete. Endorse the second deletion, since deletion is a reasonable reading of the discussion although I would probably have relisted instead. Overturn the fourth one since a deletion with no discussion at all should be seen as a soft delete especially given the unresolved dispute over whether that file was public domain (I would definitely have relisted rather than closing as delete if I were closing admin). Endorse the third one, though, since that was technically a speedy deletion not a FFD and the F7 speedy deletion criterion does allow admins to act as policy experts in the absence of any discussion. * Pppery * it has begun... 17:15, 15 September 2026 (UTC)reply
  • Question/suggestion. The sideshow about purported "gravedancing" having been resolved (I'm content to AGF), let's move to substance. Individually, those discussions were not well-attended, and the point is well taken that closers on file/copyright issues sometimes have to borderline supervote, due to poor discussion depth and the technical knowledge needed to opine on copyright matters. However, collectively, I do see a consensus: the fact the article subjects were notable for being supercentenarians is not felt to inherently be enough to justify a NFCC#8 exemption for an old-aged non-free photo of them over younger free ones. Discussion participants opened the window to contemplating a non-free exception if the text (presumably in a well-sourced manner) integrally referenced the supercentenarians appearance in their old age. So I see little basis to overturn here as a group, but could see doing so for individual photos if someone would indicate such a specific use in that specific article. Does that apply to any of these specific cases? Martinp (talk) 18:38, 15 September 2026 (UTC)reply
  • Comment. I don't know if this is possible due to the copyright considerations here, but it is hard to evaluate the discussions without reference to the specific images in question. Is it possible to temporarily undelete them or no? At least the ones other than the third one, which seems more unambiguously a copyright issue. Katzrockso (talk) 01:18, 16 September 2026 (UTC)reply
    It's inconvenient for images. Given immediate sources were Randon (site now dead, and its irritating anti-adblock javascript apparently prevented archival of the image; until recently it redirected to this, which shows a version of the same image with the top and bottom cropped); Calment; Tanaka (with no indication whatsoever of the actual source, and if the cesspit that is Fandom provides it anywhere, I can't find it); Knauss (again, no indication of the actual source, either here or there). That sufficient for review purposes? —Cryptic 04:17, 16 September 2026 (UTC)reply
  • So after looking more closely at the file description pages to answer the above, it looks like only Randon's image properly gives the author and copyright holder, and of the remainder only Calment's can be tracked down from what was given. The latter two shouldn't have even made it to FFD; they're F4 speedies. —Cryptic 04:17, 16 September 2026 (UTC)reply
  • restore Randon and Calment endorse the other two. Basically for Randon we have a discussion where the outcome probably didn't match the discussion. For Calment we have an argument that visual appearance is relevant (per Cryptic). For the other two, it sounds like they qualify under F4 (I'm deferring to Cryptic on that), so they should not be restored in any case. I'm not bolding the 2nd part just because I want it clear I'm relying on other's work for this. And yes, these are old, but I think they are reasonable to be at DRV. Hobit (talk) 19:43, 16 September 2026 (UTC)reply
  • Endorse all 4 deletions, with no prejudice against re-upload with appropriate sourcing where warranted by article text. First, while not strongly attended, the discussions met the bar for non-free-media discussions; they are not defective. Second, per Cryptic, seems only the Randon image has proper traceable sourcing and crediting. Finally, only the Calment article currently discusses the subject's appearance at old age, and in my opinion, it is passing mentions, not enough to meet the NFCC#8 criterion of increase readers' understanding...and its omission would be detrimental to that understanding. So I don't see a reason to overturn any one of the 4 deletions as they stand. That said, there is a path to inclusion: if someone were to sharpen the article text, with (sourced) discussion of the subjects' appearance in detail where an available nonfree image would increase understanding of it, a newly uploaded and properly sourced nonfree image would then be acceptable. If we do end up endorsing the deletions here, I wouldn't like that interpreted as a "never", just a "not as it currently stands". Martinp (talk) 19:30, 17 September 2026 (UTC)reply
    Adding: there was an unanswered question in the Knauss discussion whether the image might be PD after all. No prejudice against a re-upload, with proper attribution, if someone credibly can argue it *is* PD. But someone must actually make that claim in a defensible manner, not just a drive-by (not intended as criticism) unanswered question in a deletion discussion. Martinp (talk) 19:35, 17 September 2026 (UTC)reply
The following is an archived debate of the deletion review of the page above. Please do not modify it.
Mookuthi Amman 2 (talk|edit|history|logs|links|watch) (XfD|revisions|restore)

The movie releases on 6 November this year. The article was deleted without my knowledge, then recreated as a redirect and as a draft with no content. I hope someone can delete the draft and restore the deleted article in the draftspace. Some new information is there to add. Kailash29792 (talk) 14:12, 14 September 2026 (UTC)reply

  • @Kailash29792: the page was correctly tagged for the deletion discussion by the nominator, CNMall41. Since you were among the primary editors of that page, I assume you had it on your watchlist, which means you were notified of the deletion discussion. As I'm sure you know, there is no requirement for the nominator to leave a personal message for each and every contributor.
    I don't know what you mean by "new information", but the only way this could become a viable article is if we find significant coverage in independent, reliable sources that establish notability per WP:NFILM or WP:GNG. Feel free to add such sources to the existing draft, even if it's empty at this point. Owen× ☎ 15:33, 14 September 2026 (UTC)reply
I cannot see the history, but remember this was part of edits from an SPI I am putting together. The user is currently at ANI and this was from an IP range with the editing pattern matching their edits. I didn't move it because of SPI suspicion though, I moved it because it didn't meet notability guidelines. --CNMall41 (talk) 18:54, 14 September 2026 (UTC)reply
  • You don't need our permission, or anybody else's, to recreate this; all you need to do is for it to be different enough that the old afd no longer applies. "No official release date" is satisfied. You have any sources that aren't "the typical pre-release promotion"? —Cryptic 22:10, 14 September 2026 (UTC)reply
  • Overturn to redirect While a closing administrator shouldn't be required to go searching for a redirect target the #sequel section of the prior film is an obvious location to redirect, and the fact that neither the nominator nor the other two participants brought this up reflects poorly on them, too. In practice, this would amount to having history restored under the already extant and presumably optimal redirect that was recreated after this was deleted. Jclemens (talk) 01:47, 15 September 2026 (UTC)reply
The nominator is also not required to recommend an ATD. I have done so many times with these likely UPE creations in the past, only to have the redirects removed or draftifications objected to. Redirects are easy to create, even after AfD discussions. Note that one was created for this the same day it was deleted. --CNMall41 (talk) 05:54, 15 September 2026 (UTC)reply
The reason we prefer redirects instead of outright deletion for TOOSOON sorts of articles is precisely so the earlier material can be reused without administrator intervention. If there was a suggestion of UPE, that might have been reasonable if it rose to the G11 standards and was essentially unfixable... but I can't see the deleted edits and the discussion doesn't reflect that. Jclemens (talk) 06:50, 15 September 2026 (UTC)reply
Nominating at AfD is advanced editing. Users who do it should be familiar with Deletion policy, including WP:ATD. Obvious ATDs should be mentioned by the nominator, whether recommended for or against. SmokeyJoe (talk) 08:23, 15 September 2026 (UTC)reply
Overturn to redirect, restore the history behind the new redirect.
“fails WP:NFF” means Draftify, although for sequels, redirect to the “sequel” section in the preceding movie works. AfD participants need some education about WP:ATD. SmokeyJoe (talk) 08:19, 15 September 2026 (UTC)reply
I fault every participant in the AfD, from the nominator to the closer. Where every participant is at fault, it points to there being an underlying systemic problem. I offer this as a partial solution. SmokeyJoe (talk) 23:31, 16 September 2026 (UTC)reply
  • Restore history to redirect. I will endorse the "delete" close based on what was discussed at the time. There was no suggestion of a redirect, so a closer searching for a redirect target themselves and closing that way would be an obvious WP:SUPERVOTE. A clear redirect target has later been identified (and a redirect has been created). The history should not remain deleted only because the target was found after the AFD closed. Wikipedia has WP:NODEADLINE. Frank Anchor 14:24, 15 September 2026 (UTC)reply
  • Endorse A "redirect" closure as some people want to overturn to would have been a textbook supervote, bringing up arguments no party raised. DRV is only for correcting procedural errors. None is identified here. I don't actually object to restoring history under the redirect that now exists, though. * Pppery * it has begun... 17:19, 15 September 2026 (UTC)reply
    The procedural error, a deletion process error, lay primarily with the AfD nominator failing to consider and report the obvious WP:ATD-R. “Movie _name 2” redirecting to “Movie_name#Sequel” is an extremely obvious option. This error applies to every subsequent participant including the closer. The textbook Supervote answer is for the closer to !vote not close. A possible solution to recommend from this DRV is to mandate WP:BEFORE, and to mandate that AfD nominators speak to the obvious ATD-R option.
    Also, “fails NFF” defaulting to Draftify not Delete, was a !voter error that might be rectified by improving the text at WP:NFF. SmokeyJoe (talk) 21:07, 15 September 2026 (UTC)reply
    The error you describe isn't procedural. It's substantive. * Pppery * it has begun... 01:29, 17 September 2026 (UTC)reply
    Yes, you are right. SmokeyJoe (talk) 08:11, 17 September 2026 (UTC)reply
  • Endorse primarily per Pppery (try saying that three times fast!). The close was correct, and but there's no valid reason not to restore the deleted history behind the newly created redirect. Owen× ☎ 17:24, 15 September 2026 (UTC)reply
    I do not contest the validity of the closing. I just wished the article had been draftified so the history wouldn't be lost. Kailash29792 (talk) 01:14, 16 September 2026 (UTC)reply
    Draftified or under the redirect, either place would have been reasonable to keep the history accessible for future improvement. Jclemens (talk) 05:17, 16 September 2026 (UTC)reply
    @Kailash29792: the deleted history behind the redirect, if restored as most of us suggest, will give you full access to the deleted contents, to add sources and submit a draft, or work directly on the original mainspace page. Owen× ☎ 09:41, 16 September 2026 (UTC)reply
    Yes, and deleting Draft:Mookuthi Amman 2 to move the redirect to that title is helpful. Kailash29792 (talk) 11:35, 16 September 2026 (UTC)reply
    Moving to draft is one way to do this. But you don't really need it moved. Once history is restored, you can copy the bits you want to draft yourself (with proper attribution). Or seeing as you're a highly experienced editor, you can work directly in mainspace. Just give this DRV time to close. Owen× ☎ 11:50, 16 September 2026 (UTC)reply
  • endorse and restore and redirect with no fault to the closer. That said, I'd say closing as a redirect would have been an ideal outcome and I'd encourage closers to do just that in cases like this. But I understand the concerns of people yelling "supervote!". Hobit (talk) 19:46, 16 September 2026 (UTC)reply
Restore history or overturn to redirect. A redirect close would not be a supervote - there were no policy based reasons to not have a redirect. Katzrockso (talk) 02:49, 17 September 2026 (UTC)reply
Restore history and redirect, leave transferral from history into the draft to interested editors (who are best positioned to figure out whether something in the independently-created draftspace version is worth keeping). Per Hobit, no explicit fault to the closer (or nominator or discussants), but collectively an effort-wasteful outcome by the community. That happens. We are volunteers; no one has to do anything, and that means no one has to go above and beyond, though in this case any one person going one step further than making a !vote, a relist, or a close would have helped. Martinp (talk) 11:51, 20 September 2026 (UTC)reply
The above is an archive of the deletion review of the page listed in the heading. Please do not modify it.
The following is an archived debate of the deletion review of the page above. Please do not modify it.
Race to the WH (talk|edit|history|logs|links|watch) (XfD|revisions|restore)

Two main contributors to the discussion have been blocked as sockpuppets (MAWJ and LanannaB) (WP:DRVPURPOSE #3). That person is also the article creator. Most arguments for to keep the article came from them. The article has not significantly changed in terms of source quality since the AfD closed 11 months ago. Without the participation of the creator it leaves a closer argument than was seen when the discussion was closed. Yoblyblob (Talk) :) 17:10, 13 September 2026 (UTC)reply

The above is an archive of the deletion review of the page listed in the heading. Please do not modify it.
The following is an archived debate of the deletion review of the page above. Please do not modify it.
The Popinjay Cavalier (talk|edit|history|logs|links|watch) (XfD|revisions|restore)

Draftification discussion with four participants, split 50/50, closed as "keep" with no explanatory comment. I had nom'd this as I expected bold draftification to be contested by the article's creator, and my read is that the consensus was going the other way: the two oppose !votes are verbose but are not well-grounded in policy, and lack evidence that overcomes the exclusionary criteria of WP:NOT. Closer has not responded to inquiry about the close. —BrechtBro (talk) 16:52, 11 September 2026 (UTC)reply

Endorse close: The article has plenty of sourced information regarding development, crew, casting, premiere location, and targeted opening debut. It even includes various articles with an interview from its developer about concerning rising production costs and various other factors. The topic is clearly gathering new noteworthy information that further solidifies its notability under Wikipedia policies. CANthony0125 (talk) 17:06, 11 September 2026 (UTC)reply
I won't rehash the AfD here, but an additional routine announcement, in this case of someone being attached to the project, doesn't change the facts or policies at play in the discussion. —BrechtBro (talk) 17:21, 11 September 2026 (UTC)reply
New, reliable, noteworthy information has been added to the page since the Afd. This information also follows Wikipedia policy and strengthens the page's notability. CANthony0125 (talk) 17:30, 11 September 2026 (UTC)reply
Endorse. Passes the GNG. Major coverage yesterday. I would have opposed draftification. If I found this in draftspace I would immediately mainspace. SmokeyJoe (talk) 03:13, 12 September 2026 (UTC)reply
Since the AfD nomination, 1 September 2026, the article has undergone 58 revisions by six editors.
In the preceding 4 months were 15 edits by four users.
In the AfD, those arguing to reDraftify (it was mainspaced 11 March 2026) were criticising the worst of the sources (and the content sourced to these worst sources), but the criteria for mainspace depends on the 2 best sources. The best sources were not sufficiently discussed.
Endorse and do not allow renomination for two months. Current activity, including new sources, is too frenzied. SmokeyJoe (talk) 05:00, 12 September 2026 (UTC)reply
Not sure what you think the best sources are, but my nominating statement did discuss the better sourcing from my BEFORE, describing it all as routine, explicitly naming The Guardian. The worst source is actually the WP:DAILYMAIL, which broke the story in March, and though no longer in the article, it came out shortly before the first announcement and was picked up in the ensuing coverage in the trades. I didn't feel that secondary coverage of an interview with Tarantino, or the indirect background sourcing, merited further discussion. —BrechtBro (talk) 03:03, 13 September 2026 (UTC)reply
It’s my point, unsure what anyone thinks the best sources are. There are 13 WP:GREL sources. Too much space went to cleanup issues, too much of the discussion was about cleanup, not reasons for deletion.
Further discussion? I think pause, then restart. SmokeyJoe (talk) 03:46, 13 September 2026 (UTC)reply
More words in closing statement might have been good. It could have been closed as “no consensus”, but there is no doubt that there was no consensus to draftify. SmokeyJoe (talk) 07:06, 12 September 2026 (UTC)reply
Endorse close (Oppose in original discussion) This feels like a second bite at the apple DRV. The original rationale was WP:Crystal, which I addressed thoroughly (you clearly don't agree with my read, but you didn't respond in the afd so idk). Now the logic is WP:NOT, which SSilvers brought up to argue that Wikipedia should follow the lead of Encyclopedia Brittanica (an argument for WP:NEWSPAPER that is clearly against WP:PAPER, which are both under the WP:NOT banner). There's an inherent tension between WP:BUREAUCRACY and WP:Democracy in DRVs, so I can understand being frustrated if your preferred choice wasn't followed, but the proper case is Keep. Even if you disagree with the choice here, it feels like a WP:Dropthestick situation.
On the "verbose" jab, I would note that as one of two Oppose !votes, I was 4 out of 4 in edits and 3 out of 4 in text added. Nom themselves, verbose or not, was second in both categories.Dizzycheekchewer (talk) 03:58, 12 September 2026 (UTC)reply
CRYSTAL is part of NOT —BrechtBro (talk) 04:18, 12 September 2026 (UTC)reply
Horse still dead my bad though Dizzycheekchewer (talk) 04:37, 12 September 2026 (UTC)reply
While we disagree on policy, the closer picked a side in a 50/50 discussion in which both sides have merit -- one side arguing notability, the other exclusion by policy -- without explanation, and has so far been unaccountable for that. Please strike your comments that describe this as "a second bite" et al. —BrechtBro (talk) 05:21, 12 September 2026 (UTC)reply
I won't strike my comment and I won't ask you to strike yours. I wasn't wrong on the substance, even if I tripped over the particulars (WP:NOT is hardly a reason itself as much as a collection of potential reasons). As you know AfD is based on substance, not shows of hand. Even so, there were two for keep, one for Crystal-draftify and one for Newspaper-delete. I could imagine an admin relisting, but I think the close as keep is perfectly plausible. Also, a brief look at closer's page indicates that they haven't been that active on the site since your note, which is no great failure of accountability (also they aren't obligated to reply, just strongly encouraged to). Dizzycheekchewer (talk) 05:49, 12 September 2026 (UTC)reply
  • Endorse. Some editors are under the impression that CRYSTAL, which is indeed policy, applies to any event that is in the future. It doesn't. The policy very specifically applies to unverifiable speculation, rumors, or presumptions. Extensive coverage for the topic makes it very clear this is not "unverifiable speculation" any more than a future election or a future solar eclipse is. The show may or may not get produced, but notability does not depend on an event taking place. WP is full of articles about notable plans that did not come to fruition. The same goes for the essay TOOSOON; it specifically applies to topics that are unverifiable or do not meet GNG. Since this topic is verifiable and does meet GNG, according to the participants who engaged with the sources, all !votes based solely on CRYSTAL or TOOSOON should be discounted, leaving us with a unanimous consensus to keep the article in mainspace, not "50/50". I can sympathize with the desire to hold off until more information is available, but in this case, the topic has already passed our threshold of notability even if nothing ever comes out of this planned production. Owen× ☎ 22:05, 12 September 2026 (UTC)reply
    Neither of the !votes rely exclusisely on CRYSTAL or TOOSOON, both Ssilvers and I engage with notability and the sourcing, including in my nomination rationale -- so none of the !votes should be discounted. We note it consists only of announcements, which CRYSTAL and NOTNEWS speak directly to (presumably why they are both cited as exclusionary regarding future NBOOKs and NFILMs). That the information available is verifiable is not in dispute, but a verifiable announcement is still only an announcement and excluded by NOTNEWS.
    The introducton to CRYSTAL says speculation, but the body goes into more depth: short articles that consist of only product announcement information and rumors are not appropriate. Until such time that more encyclopedic knowledge about the product can be verified, product announcements should be merged to a larger topic, while NOTNEWS says: routine news coverage of announcements, events, sports, or celebrities, while sometimes useful, is not by itself a sufficient basis for inclusion of the subject of that coverage. —BrechtBro (talk) 02:38, 13 September 2026 (UTC)reply
  • Endorse the close of Keep. Either Keep or Relist would have been valid closes. There was a consensus against draftification. Robert McClenon (talk) 03:54, 13 September 2026 (UTC)reply
The above is an archive of the deletion review of the page listed in the heading. Please do not modify it.
The following is an archived debate of the deletion review of the page above. Please do not modify it.
Ugbad and Rahma Sadiq (talk|edit|history|logs|links|watch) (XfD|revisions|restore)

An AFD that started with a questionable bundle of articles and garnered low participation. That often has potential as DRV fodder, especially in this case which was closed without being relisted on a flimsy consensus. For Ugbad and Rahma Sadiq in particular, a merge to United Kingdom and the Islamic State is simply out of the question because the lack of a relation to the UK. I am therefore proposing that the merge outcome is overturned and the article listed/relisted on its own merits without being part of a bundle. To avoid a traiwreck I have no opinion on the other articles in the bundle. Geschichte (talk) 12:46, 11 September 2026 (UTC)reply

  • Support close One of the two BLPs named in this article is a BLP1E subject who was a child at the time of the one notable event. Frankly a merge that retains nothing of this specific article was the likely outcome of a merge regardless of the target page as there is very little on this specific page that is appropriate to retain. All this does is keep this page about a trafficked minor that treats her like a terrorist up on Wikipedia longer. Simonm223 (talk) 13:07, 11 September 2026 (UTC)reply
  • Comment If the objection is solely related to Ugbad and Rahma Sadiq, then it's quite correct that article isn't merged to United Kingdom and the Islamic State. But as mentioned in the AFD, Collaboration with the Islamic State#Foreign nationals is a suitable merge target for that article. FDW777 (talk) 13:47, 11 September 2026 (UTC)reply
  • Closer's comment: No objection to a separate relist (i.e. a separate AfD) for Ugbad and Rahma Sadiq if people here are of the view a clearer consensus for this specific article is needed, even if in my view there's enough of a consensus to merge/redirect this article. Sandstein 14:51, 11 September 2026 (UTC)reply
  • Endorse (edit: but allow speedy renomination of Ugbad and Rahma Sadiq). All four pages were correctly tagged by the nom at the start of the AfD. The AfD ran for the full seven days. Not a single objection was voiced during the discussion, beyond the appellant's surprise at the choice of target. This comes across as a classic case of DRVNOT#3 - disagreement with the deletion discussion's outcome that does not involve the closer's judgment. The appellant doesn't need our permission to start a spinout discussion at Talk:United Kingdom and the Islamic State, or selectively merge the contents of Ugbad and Rahma Sadiq to a more suitable target. The close itself was correct. Owen× ☎ 22:19, 12 September 2026 (UTC)reply
  • Relist FDW777 during the debate said "Obviously don't merge that one, since they appear to be the sole subject of a book I'd probably keep that one" regarding Ugbad and Rahma Sadiq, so their vote either should be discarded as uninformed or counted as Keep. Otherwise, there are strong votes by the nominator and the article creator, who specifically defended the notability of the girls, making the Keep case strong enough to conclude that there was no consensus at the end of the week. Kelob2678 (talk) 23:30, 12 September 2026 (UTC)reply
    Notability is a valid argument against deletion, but not against a merger. We routinely merge articles about perfectly notable topics, when readers are better served by seeing the content in the broader context of the target, per WP:MERGEREASON and WP:PAGEDECIDE. Owen× ☎ 23:39, 12 September 2026 (UTC)reply
    I do not see anything about context mentioned by the nominator, the rationale was failure of notability. In any case, there can be no consensus in a 1v1 reasonable debate (another merge voter said "Merge all of the UK citizens to United Kingdom and Islamic State", since the sisters were Norwegian citizens, not UK, their vote also shouldn't count). Now I actually see that there were no merge votes related to the sisters at all. Kelob2678 (talk) 23:45, 12 September 2026 (UTC)reply
    Fair enough. Do a new, procedural nomination for Ugbad and Rahma Sadiq, as Sandstein suggests, pinging all participants of the first AfD. Merging for this page can be paused until the new AfD closes. Owen× ☎ 23:53, 12 September 2026 (UTC)reply
  • overturn and procedural nomination per OwenX. Basically, the redirect target makes no sense and there is something of an argument that the bundled discussion treated this one differently anyways. I feel confident we'd not have this redirect were it not bundled. Let's try again. Hobit (talk) 19:52, 16 September 2026 (UTC)reply
Relist this one article. The nomination and the close (which makes it clear the merge should be as/where suitable) were reasonable, but do not provide sufficient and appropriate guidance for this one article of a bundle. We are therefore having the sort of discussion here that is more suitable for AfD. Bundling at AfD is a convenience measure for efficiency; sometimes it turns out to not have been the right choice; and occasionally, like here, that only becomes clear after close. No fault by anyone, but apparently needs a revisit. Martinp (talk) 11:35, 20 September 2026 (UTC)reply
The above is an archive of the deletion review of the page listed in the heading. Please do not modify it.
The following is an archived debate of the deletion review of the page above. Please do not modify it.
Mitrade (talk|edit|history|logs|links|watch) (revisions|restore)

I would like to kindly ask for the speedy deletion of Mitrade to be reviewed, with the goal of preferably having the article restored and listed at AfD, so that the community may have the opportunity to discuss its current sourcing and notability.

The article was deleted under G4, G11, and A7. As the first step, I asked the administrator who deleted the article to reconsider; however, the administrator declined to discuss my request and told me to take it to DRV.

The one that causes me the most concern is G4. The previous AfD happened in 2019 and focused on the lack of substantial independent secondary coverage, as it relied on primary coverage and material that was derived from press releases. Several years later, specifically in 2026, the article was written from scratch. It contained post-2019 sources and developments that did not yet exist in 2019. Considering that G4 targets identical recreations and/or cases where the reason for the past deletion remains unchanged, I would argue that G4 applied here is debatable.

Furthermore, I do not believe the case for G11 and A7 was clear. Indeed, the 2026 version of the article included adverse regulatory information, including ASIC action and limitations of regulatory permissions. Therefore, I would not sustain that the 2026 article was promotional.

As for A7, it is known to have a lower threshold than full notability. The article did contain claims of significance concerning a regulated financial company that operates across many jurisdictions.

With this request, I am not asking DRV to decide that Mitrade satisfies WP:NCORP. Rather, I would like to ask that, considering the disputed application of the three aforementioned speedy-deletion criteria and how the 2026 version of the article was so different, the question to be taken through the habitual AfD rather than resolved by a speedy deletion. Bill Neto (talk) 12:07, 11 September 2026 (UTC)reply

  • Have you used AI to write this appeal? Spartaz Humbug! 12:38, 11 September 2026 (UTC)reply
  • Speedy close of this request per WP:AITALK—BrechtBro (talk) 18:00, 11 September 2026 (UTC)reply
  • Endorse, the appeal is dripping with AI signs on its own, but the article has several signs itself. For one, it was written using visual editor, and yet every citation is a full {{cite web}}. When using VE, it is much easier to copy and paste refs, which automatically creates named refs. The access dates are all 20 May 2026, despite this being published on May 25. Many facts are repeatedly restated (such as the ASIC stop order). I see many instanced of WP:AIATTR, 17 uses of "reported that" and 38 uses of "reported". I'm not going to check every source, but I did check the only ones tagged reliable by Cite Unseen, which were all the same Bloomberg listing with no prose. ASUKITE 21:16, 12 September 2026 (UTC)reply
The above is an archive of the deletion review of the page listed in the heading. Please do not modify it.
Archives, by year and month
Year Jan Feb Mar Apr May Jun Jul Aug Sep Oct Nov Dec
2026 Jan Feb Mar Apr May Jun Jul Aug Sep Oct Nov Dec
2025 Jan Feb Mar Apr May Jun Jul Aug Sep Oct Nov Dec
2024 Jan Feb Mar Apr May Jun Jul Aug Sep Oct Nov Dec
2023 Jan Feb Mar Apr May Jun Jul Aug Sep Oct Nov Dec
2022 Jan Feb Mar Apr May Jun Jul Aug Sep Oct Nov Dec
2021 Jan Feb Mar Apr May Jun Jul Aug Sep Oct Nov Dec
2020 Jan Feb Mar Apr May Jun Jul Aug Sep Oct Nov Dec
2019 Jan Feb Mar Apr May Jun Jul Aug Sep Oct Nov Dec
2018 Jan Feb Mar Apr May Jun Jul Aug Sep Oct Nov Dec
2017 Jan Feb Mar Apr May Jun Jul Aug Sep Oct Nov Dec
2016 Jan Feb Mar Apr May Jun Jul Aug Sep Oct Nov Dec
2015 Jan Feb Mar Apr May Jun Jul Aug Sep Oct Nov Dec
2014 Jan Feb Mar Apr May Jun Jul Aug Sep Oct Nov Dec
2013 Jan Feb Mar Apr May Jun Jul Aug Sep Oct Nov Dec
2012 Jan Feb Mar Apr May Jun Jul Aug Sep Oct Nov Dec
2011 Jan Feb Mar Apr May Jun Jul Aug Sep Oct Nov Dec
2010 Jan Feb Mar Apr May Jun Jul Aug Sep Oct Nov Dec
2009 Jan Feb Mar Apr May Jun Jul Aug Sep Oct Nov Dec
2008 Jan Feb Mar Apr May Jun Jul Aug Sep Oct Nov Dec
2007 Jan Feb Mar Apr May Jun Jul Aug Sep Oct Nov Dec
2006 Jan Feb Mar Apr May Jun Jul Aug Sep Oct Nov Dec