Jump to content

Wikipedia:Deletion review

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

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 significant new information has come to light since a deletion that would justify recreating the deleted page;
  4. if a page has been wrongly deleted with no way to tell what exactly was deleted; or
  5. if there were substantial procedural errors in the deletion discussion or speedy deletion.

Deletion review should not be used:

  1. 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);
  2. (This point formerly required first consulting the deleting admin if possible. As per this discussion an editor is not required to consult the closer of a deletion discussion (or the deleting admin for a speedy deletion) before starting a deletion review. However doing so is good practice, and can often save time and effort for all concerned. Notifying the closer is required.)
  3. 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);
  4. 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);
  5. to repeat arguments already made in the deletion discussion;
  6. to argue technicalities (such as a deletion discussion being closed ten minutes early);
  7. to request that previously deleted content be used on other pages (please go to Wikipedia:Requests for undeletion for these requests);
  8. to attack other editors, cast aspersions, or make accusations of bias (such requests may be speedily closed);
  9. for uncontroversial undeletions, such as undeleting a very old article where substantial new sources have subsequently arisen. Use Wikipedia:Requests for undeletion instead. (If any editor objects to the undeletion, then it is considered controversial and this forum may be used.)
  10. to ask for permission to write a new version of a page which was deleted, unless it has been protected against creation. In general you don't need anyone's permission to recreate a deleted page, and if your new version does not qualify for deletion then it will not be deleted.

Copyright violating, libelous, or otherwise prohibited content will not be restored.

Instructions

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.

Steps to list a new deletion review

 
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
|article=Foo
|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=2025 June 20}}</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=2025 June 20}}</noinclude>
  • If the deletion discussion's subpage name is different from the deletion review's section header, then use <noinclude>{{Delrevxfd|date=2025 June 20|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.

Temporary undeletion

Admins participating in deletion reviews are routinely requested to restore deleted pages under review and replace the content with the {{TempUndelete}} 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 should remain on deletion review for at least seven days, unless the nomination was a proposed deletion. After seven days, an administrator will determine whether a consensus exists. 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 or where a discussion has not been closed in good time 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.)

Speedy closes

  • Objections to a proposed deletion can be processed immediately as though they were a request at Wikipedia:Requests for undeletion
  • Where the closer of a deletion discussion realizes their close was wrong, and nobody has endorsed, the closer may speedily close as overturn. They should fully reverse their close, restoring any deleted pages if appropriate.
  • Where the nominator of a DRV wishes to withdraw their nomination, and nobody else has recommended any outcome other than endorse, the nominator may speedily close as "endorse" (or ask someone else to do so on their behalf).
  • Certain discussions may be closed without result if there is no prospect of success (e.g. disruptive or sockpuppet nominations, if the nominator is repeatedly nominating the same page, or the page is listed at WP:DEEPER). These will usually be marked as "administrative close".
The following is an archived debate of the deletion review of the page above. Please do not modify it.
Category:Rachael MacFarlane albums (talk|edit|history|logs|links|watch) (restore)

Hayley Sings is her only album she's made and she hasn't done another album 13 years since 2600:8801:8E:9900:3906:3A8C:E813:1274 (talk) 13:43, 19 June 2025 (UTC)[reply]

The above is an archive of the deletion review of the page listed in the heading. Please do not modify it.
  • The Pizza Meter – The Department of Redundancy Department is closed. This did not need to be here, but it also does not need to go to REFUND to effect a decision that there is no opposition to here and we/me are capable of implementing. The Draft is restored for improvement and if needed on mainspacing, a new AfD can happen. Star Mississippi 02:26, 18 June 2025 (UTC)[reply]
The following is an archived debate of the deletion review of the page above. Please do not modify it.
The Pizza Meter (talk|edit|history|logs|links|watch) (XfD|restore)

During the original AfD, the article was deleted on the basis that, at the time, there was insufficient third-party coverage demonstrating notability. However, in light of recent events in the Middle East, a flood of news coverage has suddenly popped up over the topic: news.com.au, euronews, The Guardian, Economic Times, Futurism, Newsweek, The Telegraph, Haaretz. If the page is undeleted, I would suggest renaming it to Pizza Index, as that appears to be the WP:COMMONNAME. --benlisquareTCE 07:05, 17 June 2025 (UTC)[reply]

  • Allow recreation (i.e., undelete to draft or sandbox for update) per the new sourcing. This should probably not have been deleted previously; I suspect an appropriate search for sources at that time would have found more. No objection to renaming, anyone can nominate at any time, etc. Jclemens (talk) 07:10, 17 June 2025 (UTC)[reply]
  • As AfD closer, I do not object to a recreation using the new sources. Sandstein 07:43, 17 June 2025 (UTC)[reply]
  • As a delete !voter I'm still not sure this will pass our guidelines, but I have no problem with a new draft. SportingFlyer T·C 08:08, 17 June 2025 (UTC)[reply]
    I think the evidence that this wasn't even the COMMONNAME suggests an article could have been built with a bit more digging, but given the sourcing above, it's an academic question. Jclemens (talk) 18:53, 17 June 2025 (UTC)[reply]
    I think WP:NOTNEWS could be at play, though. I only see one article from before the last couple days. SportingFlyer T·C 22:39, 17 June 2025 (UTC)[reply]
  • Restore to mainspace. The AfD was closed correctly, but new sourcing is prima facie evidence of notability, sufficient at least to require renomination if contested. The deleted version wasn't great, but there's no reason to redo that work. Owen× 12:41, 17 June 2025 (UTC)[reply]
  • Endorse the 2024 close, but see at the top of this noticeboard: Deletion review should not be used:… to ask for permission to write a new version of a page which was deleted, unless it has been protected against creation. In general you don't need anyone's permission to recreate a deleted page, and if your new version does not qualify for deletion then it will not be deleted The requester has the right to create a draft, to submit a draft for review, or to create a new article subject to AFD. Robert McClenon (talk) 18:03, 17 June 2025 (UTC)[reply]
  • Sure, a new article could be written from scratch, but personally, I'd rather not reinvent the wheel if editors have already written a half-finished article that just needs fixing up. Time is finite, after all. --benlisquareTCE 18:34, 17 June 2025 (UTC)[reply]
These questions should not come to DRV. If you’re unsure and not wanting to waste time, request undeletion to draftspace at WP:REFUND. Improve the deleted article by removing poor sources and adding new better sources. Identify the best WP:THREE sources, by citing them first, or on the talk page, and seek review.
If you’re more confident, do the above but move it yourself back to mainspace. Th8s is ok, if you’re sure the sources are better, and as the AfD was so long ago.
DRV is not the right forum for requesting review of new sources. SmokeyJoe (talk) 22:23, 17 June 2025 (UTC)[reply]
  • For the record, I absolutely believe this is the proper forum - this is where the community gains consensus on what should be done with new information after a deleted recent AfD. SportingFlyer T·C 22:39, 17 June 2025 (UTC)[reply]
    And I strongly disagree. You are advocating scope creep.
    If every such case came to DRV, DRV would be overwhelmed. AfC and AfD are the forums that are appropriate. Even if DRV says “yes”, it confers no protection from being sent to AfD, and thus nothing has been achieved over the proponent simply recreating in mainspace with their new sources, except distracting DRV.
    There is no challenge to the AfD, and so this nomination should have been speedy closed.
    If the deleting admin had said “no”, or the REFUND to draftspace was refused, or an unsalting request was denied, then DRV is appropriate, when there is something to review. SmokeyJoe (talk) 23:13, 17 June 2025 (UTC)[reply]
The above is an archive of the deletion review of the page listed in the heading. Please do not modify it.
Elito Circa (talk|edit|history|logs|links|watch) (XfD|restore)

Elito Circa, also known as Amangpintor, is a widely recognized Filipino visual artist noted for pioneering the use of human hair and indigenous materials in painting. He has been featured in national and international media, including Ripley's Beleive It Or Not, Reuters, CNN, SBS Australia, Philippine Daily Inquirer, GMA Network, and ABS-CBN. His story is documented in the National Commission for Culture and the Arts (NCCA), World Vision, Rotary International and Embassies and his works are displayed in public museums and Galleries. New reliable secondary sources are now available, proving long-term notability. 121.200.4.157 (talk) 11:04, 16 June 2025 (UTC)[reply]

FEATURED REFERENCES
The following discussion has been closed. Please do not modify it.


6 Extraordinary Mediums Filipino Artists Wield in their Works https://feuadvocate.net/6-extraordinary-mediums-filipino-artists-wield-in-their-works/

Bangladesh News https://www.anandabazar.com/lifestyle/filipino-painter-elito-circa-uses-own-blood-as-the-medium-for-his-painting-dgtl/cid/1392622

India News https://zeenews.india.com/hindi/off-beat/philippine-artist-elito-circa-painting-using-own-blood-wish-to-creat-world-record/1490492

Filipino painter Elito Circa uses own blood as the medium for his art https://nypost.com/2022/12/17/filipino-painter-elito-circa-uses-blood-for-his-art/

Environmental Advocacy Certificate https://ecertificate.seameo.org/certificates/321/SEAMEO201811SEAMEO-JapanESDAwardW000242.pdf

Contemporary Philippine Arts from the Regions - Local Materials https://www.slideshare.net/slideshow/contemporary-philippine-arts-from-the-regions-local-materials/254386670

Whose Who Look at the artworks of these Contemporary Artists https://studyx.ai/homework/111101716-activity-3-whose-who-look-at-the-artworks-of-these-contemporary-artists-and-guess-what

Chinese news https://www.jiuzyoung.com/tag/elito-circa/

Pintor, ginagamit ang sariling dugo sa pagpinta ng kaniyang mga obra https://www.gmanetwork.com/news/balitambayan/talakayan/713115/pintor-ginagamit-ang-sariling-dugo-sa-pagpinta-ng-kaniyang-mga-obra/story/

“Buhay na Obra" (Dokumentaryo ni Jay Taruc) https://www.gmanetwork.com/news/publicaffairs/iwitness/227129/buhay-na-obra-dokumentaryo-ni-jay-taruc/story/

Philippine artist has blood on his hands, literally - to create art with https://www.thestar.com.my/lifestyle/culture/2022/12/17/philippine-artist-has-blood-on-his-hands-literally---to-create-art-with

Filipino artist creates paintings using his own blood https://interaksyon.philstar.com/hobbies-interests/2022/12/19/237653/filipino-artist-creates-paintings-using-his-own-blood/

Elito Circa riskes his life to paint iconic montage of President Duterte https://kami.com.ph/57410-buwis-buhay-local-artist-paints-president-duterte-using-blood-sweat.html

Filipino artist paints with his own blood, sweat and tears… literally https://www.scmp.com/video/asia/3203615/filipino-artist-paints-his-own-blood-sweat-and-tears-literally

Write an essay about Some Philippine artworks challenge our perspectives and make us think differently https://www.classace.io/answers/write-an-essay-about-some-philippine-artworks-challenge-our-perspectives-and-make-us-think-differently-can-you-share-an-example-of-an-filipino-art-made-that-challenged-your-beliefs-or-made-you-see-thi#google_vignette

Filipino artist creates painting gs using his own blood https://news.am/eng/news/735522.html#google_vignette

Look: Filipino artist creates paintings using his own blood https://www.khaleejtimes.com/world/asia/philippine-artist-creates-paintings-using-his-own-blood

Filipino artist creates paintings using his own blood https://borneobulletin.com.bn/filipino-artist-creates-paintings-using-his-own-blood-2/

Vietnamese News: 'Dị nhân' vẽ tranh bằng chất liệu độc lạ: Người dùng nước mắt, người dùng cả máu https://baomoi.com/tag/Elito-Circa.epi

Philippine artist creates paintings using his own blood https://magtheweekly.com/detail/17261-philippine-artist-creates-paintings-using-his-own-blood#google_vignette

Bahrain News https://www.bna.bh/en/news?cms=q8FmFJgiscL2fwIzON1%2BDkh7TBmtbW0fqIdLEpax%2BmI%3D

The Expositor: Art in a whole new vein https://www.brantfordexpositor.ca/news/local-news/art-in-a-whole-new-vein

Slovenia News: Slika z lastno krvjo (FOTO) https://www.slovenskenovice.si/tag/elito-circa/#

Artist uses own blood, hair in his paintings https://punto.com.ph/artist-uses-own-blood-hair-in-his-paintings/

Elito Villaflor Circa -Famous Filipino Artist https://www.pechakucha.com/presentations/elito-villaflor-circa-famous-filipino-artist-754

Filipino Artist and Delegates Mark Active Presence at Rotary International Convention in Hamburg https://philippine-embassy.de/2019/06/03/filipino-artist-and-delegates-mark-active-presence-at-rotary-international-convention-in-hamburg/

Philippine Star: Artist uses own blood, hair in paintings https://www.philstar.com/breaking-news/705010/artist-uses-own-blood-hair-paintings/amp/

Daily Jang Daily Jang News: Pakistan's leading Urdu Newspaper: Philippine artist Elito Circa create painting using his own blood https://www.youtube.com/watch?v=TmCF00XHftQ

Artist with blood on his hands https://lifestyle.inquirer.net/256243/artist-blood-hands/

Philippine artist creates paintings using his own blood https://dzrh.com.ph/post/shinee's-minho-is-coming-to-manila!

ABS-CBN News: Artist uses own blood to paint Duterte masterpiece https://www.abs-cbn.com/life/11/01/16/artist-uses-own-blood-to-paint-duterte-masterpiece

Controversial Artist Uses His Own Blood as Paint https://www.odditycentral.com/art/controversial-artist-uses-his-own-blood-as-paint.html

Pulse Nigeria: What to know about the world-famous artist who paints with his blood https://www.pulse.ng/articles/lifestyle/the-filipino-artist-who-paints-with-his-blood-2024072704215785598

Philippine artist creates paintings using his own blood https://www.reuters.com/lifestyle/philippine-artist-creates-paintings-using-his-own-blood-2022-12-16/

PH artist Amangpintor meets his foster parent after 45 years https://www.sbs.com.au/language/filipino/en/podcast-episode/ph-artist-amangpintor-meets-his-foster-parent-after-45-years/chyae7fjj

About Elito Circa https://www.scribd.com/document/395849576/Elito-Circa

SCIENCE AND TECHNOLOGY SSRN (Social Science Research Network) International Publication Co-Author: Development and Validation of Electronic Imaging Sweetness Meter for Watermelon (Citrullus lanatus) https://papers.ssrn.com/sol3/papers.cfm?abstract_id=4178717

FAO: Small Ponds Make a Big Difference: Integrating Fish with Crop and Livestock Farming Artist Illustrator https://openknowledge.fao.org/server/api/core/bitstreams/fecc9445-f288-44e5-8c0e-557115082e9d/content/x7156e.htm

— Preceding unsigned comment added by 121.200.4.157 (talk) 11:16, 16 June 2025 (UTC)[reply]

  • Endorse unanimous consensus to delete. Recreation is allowed as the title is not salted. As several of the sources post-date the AFD, any new article would not be substantially similar to the deleted version, therefore G4 speedy deletion would not apply. If the appellant were a user in good standing, and not an IP, my recommendation would be to request the deleted page be restored to draft space at WP:REFUND, incorporate the new references into the draft, and then submit it through the WP:AFC process. Frank Anchor 12:35, 16 June 2025 (UTC)[reply]
Per the below comment, a draft has recently been created, so modifying my response to reflect this. Frank Anchor 23:52, 16 June 2025 (UTC)[reply]
  • Endorse the original delete consensus. The same issues exist in relation to the quality of sourcing which includes user-submitted content, churnalism, human-interest or shock-value sources, blogs, promotional puff pieces, homework assignments and perplexing things like this: {{tq|Write an essay about Some Philippine artworks challenge our perspectives and make us think differently [1]. There does not seem to be any analytical art historical/art critical attention that is normally found for artists; no notable museum collections, etc. (Not sure if this has any bearing on a DRV, but the original article was created by a sock-puppeteer with the same name as the artists's pseudonym, see: [[2]]). Netherzone (talk) 14:11, 16 June 2025 (UTC)[reply]
The following is an archived debate of the deletion review of the page above. Please do not modify it.
Flower (skunk from Bambi) (talk|edit|history|logs|links|watch) (XfD|restore)

Incorrectly non-admin closed as a speedy keep, when it should have been a standard keep and a move. The move is specifically to an admin protected page so would need an admin to do so. CoconutOctopus talk 14:10, 15 June 2025 (UTC)[reply]

  • This needs some thinking. The AfD ended with three keep:one delete:one redirect. The speedy keep close is a concern. This isn't even a WP:SNOWing AfD. If the AfD was closed correctly, endorse. The delete/redirect !votes came in before substantial changes were made to the article within three days of the nomination. After that, people voted keep. Relist probably won't work since the keeps would probably pile-on and the discussion be closed short of the added 168 hours. ToadetteEdit (talk) 15:27, 15 June 2025 (UTC)[reply]
    Adding to my rationale above, I do not recall a page being moved as a result of an AfD, and assistance to move a page to a protected page can always be done at WP:RM/TR. I agree with the OP though that this should be closed by an admin, but I do not see any problem either way. ToadetteEdit (talk) 15:33, 15 June 2025 (UTC)[reply]
    Ah, I see that the closer has been indef'd for general disruption, so this may need to be reconsidered. ToadetteEdit (talk) 15:36, 15 June 2025 (UTC)[reply]
    Yeah, I posted this before reconsidering and taking it to ANI as a whole for bad closes. I do still think this one specifically should have been a Keep followed by a histmerge move, not a simple Speedy Keep. CoconutOctopus talk 15:43, 15 June 2025 (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.
Centre for Sight (talk|edit|history|logs|links|watch) (restore)

Inproper use of G4. he content was significantly different to the previous content - it was unbiased and factual and had references as well as suggestions for further references in the talk page. Unlike the previous content, it focused just on Centre for Sight as a notable eye clinic in the UK and not on the centre's owner who has his own page. I am a new writer so had nothing to do with the previous page in 2017 (I would have been taking my A-levels then not even in work) and I read the guide for creating new pages carefully and applied it to the best on my ability. Erin Dearlove (talk) 12:54, 13 June 2025 (UTC)[reply]

  • Deleting admin's comment: The good-faith G4 by User:Onel5969 applies no matter which paid editor the doctor is using these days. I had offered to restore the page then nominate again for AfD but this paid editor seems to be in a hurry. I was not satisfied this page has better sources than in 2017, even though some sources may be different. Again, I'm happy to restore for now. BusterD (talk) 13:36, 13 June 2025 (UTC)[reply]
    Have restored and renominated. BusterD (talk) 13:53, 13 June 2025 (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.
Alisha Parveen (talk|edit|history|logs|links|watch) (XfD|restore)

Alisha has become notable now so can her deleted article be restored to draftspace so that I can work on it and submit it for review? Zainyloves (talk) 05:42, 12 June 2025 (UTC)[reply]

The above is an archive of the deletion review of the page listed in the heading. Please do not modify it.
Template:AHM (talk|edit|history|logs|links|watch) (XfD|restore)

The reason for it to be deleted was not being widely used, that's changeable. I will put it to use, in addition it, I believe if more people knew it exists, it would also have been put to use more often. 2604:2D80:4D09:1A00:FDB5:CAB5:3ED6:E92B (talk) 02:50, 11 June 2025 (UTC) -->[reply]

  • This template was deleted over two years ago. Why are you only requesting this now? Stifle (talk) 08:43, 11 June 2025 (UTC)[reply]
    Because I wasn't here two years ago. I've already asked the person who deleted it, he didn't appreciate being bothered. 2604:2D80:4D09:1A00:D79:B3E7:D881:47A0 (talk) 00:28, 12 June 2025 (UTC)[reply]
    I probably wouldn't "appreciate" having something like this written to me, either. Daniel (talk) 05:40, 12 June 2025 (UTC)[reply]
    I don't understand the issue.
    I used his terminology, following his definition.
    I had already told him I am aware why it was deleted, he replied by telling me it was deleted because of the reasons I had already told him I have been made aware of, and had already disputed, something which he did not address, and when pressed on it he started making threats. "End of the road for you" are you building up on his intimidation tactics?
    I'm not even sure why the temporality of the request was even asked; It's only out of [evidently] undue politeness that I even added the section about requesting to have it restored; as to avoid my reply to the admin, who bothered replying to my requesting of a restoration of a nuanced template -which was deleted for no reason, save that one person didn't like it being used only once by one person prior -something which had already been remedied for in this petition- being that of simply pointing out the obvious; I wasn't here then; But I'll add some more now: Nor did I know it exists, Nor do most who would make use of it. 2604:2D80:4D09:1A00:F4F4:3E0A:508B:CDB6 (talk) 18:45, 12 June 2025 (UTC)[reply]
  • Restore based on lack of participation of in the TFD (just the nom and a single WP:PERX vote). That's not enough to be considered consensus to delete, particularly without being relisted even a single time. We now have a user interested in correcting the reason for which the template was deleted. While I would normally vote to relist a sparsely-attended discussion, it does not make sense to relist a discussion from over two years ago. Any user would be free to start a new TFD. Frank Anchor 12:52, 11 June 2025 (UTC)[reply]
  • Comment - I think that this request reflects the idea that deletion of a template or category, unlike deletion of an article, is permanent, and that any recreation can be tagged as G4 unless it is brought here to DRV. Robert McClenon (talk) 15:34, 11 June 2025 (UTC)[reply]
  • Restore There was too little participation in the TfD, and this was from two years ago so relisting wouldn't be a good idea. Opm581 (talk | he/him) 20:42, 13 June 2025 (UTC)[reply]
  • Restore per above. TFD participation has long been low, and I think that the request to restore is I good faith. ToadetteEdit (talk) 16:40, 15 June 2025 (UTC)[reply]
The following is an archived debate of the deletion review of the page above. Please do not modify it.
Draft:Surya Devan (talk|edit|history|logs|links|watch) (restore)

Request for user space restoration only

I acknowledge that Draft:Surya Devan was deleted under CSD G11 for promotional content, and I also acknowledge a conflict of interest. I am not contesting that deletion from draftspace.

However, I respectfully request a user subpage copy at User:SuryaDevanE/SuryaDevan so that I can work on the material privately for learning and eventual neutral submission — possibly by a third party.

I’ve made a clear good-faith effort to understand Wikipedia’s policies and will not attempt to repost the article without editorial guidance. Admin Timtrent has declined restoration; I’m requesting community review.

Thank you. — SuryaDevanE (talk) 19:44, 9 June 2025 (UTC)[reply]

The above is an archive of the deletion review of the page listed in the heading. Please do not modify it.
Template:Aubrey Plaza (talk|edit|history|logs|links|watch) (XfD|restore)

The original TfD presented no valid rationale for deletion; the only rationale was in the nominator statement, which cited WP:FILMNAV. However, this guideline does not cover (let alone implore) navbox deletion, it discusses subjective criteria for individual item inclusion at navboxes. Kingsif (talk) 04:05, 9 June 2025 (UTC)[reply]

  • Overturn Besides generally supporting procedural relist as DELREV nominator, looking at the production credits that made up most of the navbox (The Little Hours, Ingrid Goes West, Black Bear (film), Little Demon (TV series), and Emily the Criminal), in all cases Plaza is producer and main actor and, at least through our articles or a quick search, was the first producer signed on and a primary creative force in the projects being picked up and finished. Two of the film articles also indicate she was directly involved in casting. It's simply unreasonable to suggest Plaza would not be considered a primary creator, and this in addition to the character links, mean it's both a complete and tightly-focused (distinct creator connection throughout all items) navbox. Kingsif (talk) 04:26, 9 June 2025 (UTC)[reply]
    She is most definitely not the creator of Little Demon and she was one of 6-8 producers on a couple of the films you mention. She cannot be considered a primary creator for these. WP:FILMNAV clearly applies here. --woodensuperman 11:08, 9 June 2025 (UTC)[reply]
    Once again, FILMNAV (no matter what you wanted when you wrote it) is not a deletion policy - you can write a personal argument why you believe some of its content indicates that some items shouldn't be included, but that is 1. an opinion and 2. not something that leads directly to template deletion. At least you now seem to only question inclusion of a couple of the films, so regardless there is certainly enough for a navbox to exist. Kingsif (talk) 20:01, 9 June 2025 (UTC)[reply]
  • Relist based on lack of participation of in the TFD (just the nom and a single WP:PERX vote). Thats not enough to be considered consensus to delete, particularly without being relisted even a single time, now that a user has presented an argument to retain the template. Frank Anchor 14:14, 9 June 2025 (UTC)[reply]
  • endorse or relist, there is precedent for director-centric navigation boxes and for deleting actor-centric and producer-centric navigation boxes (per MOS:FILM), but I see no harm with reopening this for more discussion. Frietjes (talk) 15:30, 9 June 2025 (UTC)[reply]
  • Relist - Inadequate discussion for consensus, should have been relisted once. Robert McClenon (talk) 16:17, 9 June 2025 (UTC)[reply]
  • Relist as per above. This should have been pointed out before the closing time. ToadetteEdit (talk) 06:51, 10 June 2025 (UTC)[reply]
  • As a usual closer at TFD, one comment + the OP is typical to establish consensus for a routine nomination. I would judge this as one such. I think relist comments based on this factor are probably a miss. (The OP here cites at least one other factor, on which I have no comment.) Izno (talk) 17:54, 14 June 2025 (UTC)[reply]
  • Question for User:Izno about TFD: Do the OP and one supporting comment establish a consensus to keep the title deleted, or can another editor recreate the title? Can the OP simply recreate a template with the same title? Robert McClenon (talk) 20:23, 16 June 2025 (UTC)[reply]
Template:Michael B. Jordan (talk|edit|history|logs|links|watch) (XfD|restore)

The original TfD presented no valid rationale for deletion; the only rationale was in the nominator statement, which cited WP:FILMNAV. However, this guideline does not cover (let alone implore) navbox deletion, it discusses subjective criteria for individual item inclusion at navboxes. Kingsif (talk) 04:05, 9 June 2025 (UTC)[reply]

Template:Halle Berry (talk|edit|history|logs|links|watch) (XfD|restore)

The original TfD presented no valid rationale for deletion; the only rationale was in the nominator statement, which cited WP:FILMNAV. However, this guideline does not cover (let alone implore) navbox deletion, it discusses subjective criteria for individual item inclusion at navboxes. Kingsif (talk) 04:05, 9 June 2025 (UTC)[reply]

  • Also, request undeletion so that previous versions (the original TfD nominator noted they significantly reduced it) can be properly assessed. Kingsif (talk) 04:11, 9 June 2025 (UTC)[reply]
  • Relist based on lack of participation of in the TFD (just the nom and a single WP:PERX vote). Thats not enough to be considered consensus to delete, particularly without being relisted even a single time, now that a user has presented an argument to retain the template. Frank Anchor 14:13, 9 June 2025 (UTC)[reply]
  • endorse or relist, there is precedent for director-centric navigation boxes and for deleting actor-centric and producer-centric navigation boxes (per MOS:FILM), but I see no harm with reopening this for more discussion. Frietjes (talk) 15:30, 9 June 2025 (UTC)[reply]
  • Relist - Inadequate discussion for consensus, should have been relisted once. Robert McClenon (talk) 16:17, 9 June 2025 (UTC)[reply]
  • Relist all three of these, though I think the same result will occur due to our policies. SportingFlyer T·C 21:04, 9 June 2025 (UTC)[reply]
    With the Berry template, it seems likely, but that's okay: in a TfD we must allow the discussion to occur or we are sidestepping accountability. This is why I do take issue, in general, with acronyms (mis)used for authority and "per nom" being ways things get done: no user(s) take accountability and we can't blame a TfD system that has been used improperly, so it becomes increasingly hard to start new discussion or get to the root of decisions, which is how bad precedents are set. Kingsif (talk) 21:19, 12 June 2025 (UTC)[reply]
  • Relist as per above. ToadetteEdit (talk) 06:51, 10 June 2025 (UTC)[reply]
  • As a usual closer at TFD, one comment + the OP is typical to establish consensus for a routine nomination. I would judge this as one such. I think relist comments based on this factor are probably a miss. (The OP here cites at least one other factor, on which I have no comment.) Izno (talk) 17:55, 14 June 2025 (UTC)[reply]
    Even when the comment doesn’t say anything? Anyway, maybe two just generally shouldn’t be considered consensus - I don’t know where else it would. And I imagine if there were suddenly lots more non-consensus status quo closes, it would drive up engagement with TfD. Kingsif (talk) 10:48, 15 June 2025 (UTC)[reply]
    I can not see any future in any forum in which more no-con closes would increase engagement (or in which this would be healthy whatsoever for TFD). Which as you imply, is the problem. TFD has a second issue that it has no PROD or equivalent, which is how AFD would theoretically get around this case.
    On which point in fact, several admins at TFD will delete templates with solely a nom as a soft deletion despite there being no policy on the point. (I personally relist nom-only TFDs.) I raised that in 2021 (see Explicit talk page link); discussion at the time seemed not particularly concerned with the practice.
    As such, I don't think it's realistic to suggest 'two shouldn't be a consensus' without a wider guideline or policy saying what the minima are. Izno (talk) 20:37, 16 June 2025 (UTC)[reply]
    Question for User:Izno about TFD: Do the OP and one supporting comment establish a consensus to keep the title deleted, or can another editor recreate the title? Can the OP simply recreate a template with the same title? Robert McClenon (talk) 20:24, 16 June 2025 (UTC)[reply]
    I don't see how that question is interesting, TBH. If you mean, would someone recreating these navboxes have to contend with WP:G4? Assuredly. Izno (talk) 23:00, 16 June 2025 (UTC)[reply]
Ilyas El Maliki (talk|edit|history|logs|links|watch) (XfD|restore)

1. The new article was not substantially identical to the previously deleted version. It introduced at least 50% new sources, including coverage of the subject’s achievements from Dexerto, Kings League’s official website, and leading Moroccan media outlets like Hespress, L'Opinion, Telquel and Morocco World News.

2. The new sources were not properly evaluated. Editors repeatedly called for "speedy delete" without reviewing the sources or explaining why they failed WP:GNG.

3. Skepticism toward Moroccan media reflects potential systemic bias. Editors did not provide evidence that these outlets were unreliable, yet their reliability was dismissed. This reflects broader challenges in recognizing notability for figures from the MENA region.

  • I request a review to determine whether the sources and arguments presented were given adequate consideration before deletion.

Rap no Davinci (talk) 18:03, 9 June 2025 (UTC)[reply]

  • Can someone confirm whether WP:G4 applied? I think we've gotten this one wrong and it looks like we can have an article on him based on the wide amount of coverage he's received. SportingFlyer T·C 21:09, 9 June 2025 (UTC)[reply]
  • Overturn to no consensus with no prejudice against immediate re-nomination. The rationale for every delete vote was that an article on this subject was previously deleted in an AFD. However, the temp un delete shows the article deleted in the second AFD is vastly different than the one in the first AFD, including multiple references dated after the article was first deleted. G4 clearly does not apply. There is very little discussion of the merits of the actual article or of the references (particularly those that were not in the article during the first AFD) from the delete !voters. Frank Anchor 00:59, 10 June 2025 (UTC)[reply]
  • Overturn A "Delete because G4" when G4 does not apply is no delete !vote at all. It likely reflects fatigue with efforts to craft compliant articles on borderline notability people, and we need to instead properly evaluate notability based on the final sourcing provided. The late-breaking G4s after the earlier ones had been contested are particularly puzzling to me. Jclemens (talk) 02:38, 10 June 2025 (UTC)[reply]
  • Comments - I am puzzled. The old and the new temporarily undeleted versions that I am viewing are so different that no one should say that they are substantially the same. Was the new version of the article expanded while the second AFD was in progress, in which case some of the AFD participants saw a different less complete article?
    • This is a difficult case, because DRV is not AFD round 2, but the AFD does not appear to reflect reality. The Delete votes all said to Speedy Delete, and the nomination says that the article being reviewed is substantially the same as the deleted article, but the two articles are not substantially the same. I think that Ignore All Rules should be used very rarely, but this is a case where we need to ignore the rule that are not reviewing the AFD. The AFD was wrong. I was about to say to Relist, but this AFD has been tainted. Robert McClenon (talk) 02:49, 10 June 2025 (UTC)[reply]
  • Overturn to No Consensus as per User:Frank Anchor and permit a new AFD to be started, and the participants will know that G4 is not one of the valid answers. Robert McClenon (talk) 02:49, 10 June 2025 (UTC)[reply]
  • Overturn per above. G4 should not apply if there are substantial changes such that the concerns in the previous AFD are addressed. It is probably too excessive to delete the page because of the G4 comments in the AfD despite the author's convincing arguments against the delete !votes. ToadetteEdit (talk) 06:57, 10 June 2025 (UTC)[reply]
  • Overturn and allow a new AfD if you want, but I strongly suspect we're at the point where this will be kept. SportingFlyer T·C 07:19, 10 June 2025 (UTC)[reply]
  • Overturn and allow a new AFD, per above. Mooonswimmer 04:19, 12 June 2025 (UTC)[reply]
  • Overturn, clearly not G4 and also there are plenty of sources about him. Alaexis¿question? 14:19, 13 June 2025 (UTC)[reply]
  • I'm going to buck the trend here and say endorse This the result of an AfD discussion, not a speedy deletion, so the question of whether G4 actually applies or not as stated in the speedy deletion criteria doesn't technically matter. Instead, "delete per G4" is a perfectly reasonable shorthand way of saying "delete because I don't think the issues that caused the previous deletion have been addressed". And we don't have jurisdiction at DRV to determine that argument is invalid because doing so would merely be substituting our judgement for theirs rather than actually addressing a procedural error as we are supposed to do. * Pppery * it has begun... 23:08, 13 June 2025 (UTC)[reply]
Except there was a procedural error. The “delete per G4” voters did not have access to the previous version which was deleted and recreated. They just assumed, incorrectly, that since it was already deleted once it should simply be deleted again. The procedural error is in the closer (who would have access to both versions and see that G4, whether as an actual speedy or as an argument in an AFD vote, clearly didn’t apply) giving too much weight to these votes which were found out to not be based at all in P&G. That is certainly a valid concern for DRV. Frank Anchor 11:36, 14 June 2025 (UTC)[reply]
That's not what G4 says at all - it specifically says the draft must be sufficiently identical. The other wrinkle here is that this does look like it should have been kept looking at the available sources. SportingFlyer T·C 11:51, 14 June 2025 (UTC)[reply]
The following is an archived debate of the deletion review of the page above. Please do not modify it.
Violations (Star Trek: The Next Generation) (talk|edit|history|logs|links|watch) (restore)

The article is nothing but describing the plot of the episode. No source links provided, no production information, nothing. This article about the episode is rendered pointless.--Dr. Gregory House's Missing Cane (talk) 13:48, 8 June 2025 (UTC)[reply]

Close (wrong forum). SmokeyJoe (talk) 06:07, 9 June 2025 (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.
Douglas Cowgill (talk|edit|history|logs|links|watch) (restore)

The article can't be re-created but has sources such as [[3]] and [[4]] and [[5]] Wynwick55gl (talk) 09:08, 8 June 2025 (UTC)[reply]

Douglas Cowgill isn't protected, from what I can see. As a non-autoconfirmed user, you can't directly create it though, please use the article wizard to create & submit a draft. Victor Schmidt (talk) 10:40, 8 June 2025 (UTC)[reply]
Close (out of scope). DRV is not for giving permission to recreate old deletions. If you’re not sure, use WP:AFC. SmokeyJoe (talk) 06:10, 9 June 2025 (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.
Chromebook challenge (talk|edit|history|logs|links|watch) (XfD|restore)

High number of people who wanted to delete the article were WP:JUSTA. They cited policies but didn't give a rationale. Example, the deletion "rationale" simply stated "WP:NOTNEWS" and nothing else. Additional notes: The article cited reliable secondary sources like USATODAY, CBS, NBC, and Axios, complying with GNG.Thegoofhere (talk) 18:47, 6 June 2025 (UTC)[reply]

Endorse. User:Thegoofhere had their say at AfD, with 15 posts, and failed to persuade. The close was correct. Any arguments to expand coverage now belong at the talk page of the redirect target, at Talk:List of Internet challenges.
Thegoofhere expressed wishes to take the content to draft. I would strongly discourage this, as content forking, unless done with explicit approval demonstrated at Talk:List of Internet challenges. SmokeyJoe (talk) 07:10, 9 June 2025 (UTC)[reply]
Looking at the not deleted content behind the redirect, I’d have argued “delete”, a news flash about school property damage. SmokeyJoe (talk) 07:32, 9 June 2025 (UTC)[reply]
The above is an archive of the deletion review of the page listed in the heading. Please do not modify it.
Urutau (3D Printable Firearm) (talk|edit|history|logs|links|watch) (XfD|restore)

Urutau recently received press reports from two security research outfits(GNET and The Jamestown Foundation). At the Australian Federal Police forensics headquarters in Canberra, the ballistics team manufactured their own Urutau. Complete and incomplete models of the Urutau have been recovered by police forces in Auckland, New Zealand[1][2] and Lexington Park, Maryland, United States of America.[3][4][5]. They are Visible in the Bottom Left Corner of the images provided in the articles. It got mainstream media coverage 1 ,2,3,4,5,6,7. Urutau (3D Printable Firearm) now certainly meets GNG and has sufficient evidence of notability.— Preceding unsigned comment added by Superlincoln (talkcontribs) 14:07, 4 June 2025 (UTC)[reply]

Go to WP:AfC. DRV is not for giving permission to recreate. The AfD was closed correctly as “merge‎ to List of 3D printed weapons and parts”.
Read WP:THREE. It is not reasonable to ask people to read 15 sources arguably in support of notability. SmokeyJoe (talk) 07:39, 9 June 2025 (UTC)[reply]
I consider these links to be the best sources of the above post
1.https://gnet-research.org/2025/01/08/beyond-the-fgc-9-how-the-urutau-redefines-the-global-3d-printed-firearm-movement/
2.https://3dprintingindustry.com/news/terrorism-expert-warning-on-new-simplified-3d-printed-gun-and-manifesto-235518/
3.https://www.linkedin.com/pulse/feathers-fury-in-depth-analysis-z%C3%A9-cariocas-podcast-interview-f%C3%BCredi-f9g0e/ Superlincoln (talk) 13:25, 9 June 2025 (UTC)[reply]
I haven’t evaluated whether they are independent, but they look good. All newer than the AfD. SmokeyJoe (talk) 13:41, 9 June 2025 (UTC)[reply]

References

  1. ^ https://www.linkedin.com/posts/activity-7315973288617213953-aBkd
  2. ^ "'Significant seizure': Auckland police bust illegal 3D-printed firearm syndicate".
  3. ^ https://www.firstsheriff.com/newsreleases/110824_SMCSO_Recovers_Extensive_Arsenal_Search_Underway_for_Suspect_Jerod_Adam_Taylor_wp.pdf
  4. ^ https://www.linkedin.com/posts/activity-7262119399094988800-l9Wt
  5. ^ "Maryland man wanted after arsenal of weapons found, including 3D-printed 'ghost guns'". CNN. 12 November 2024.
  • Endorse the September 2024 AFD. Create a draft (using the same content as was recently added in article space and is in the history) and submit it for review. A reviewer can compare the draft against the deleted article (which is in the history). There is no need for DRV to be involved. Robert McClenon (talk) 15:40, 4 June 2025 (UTC)[reply]
We can compare this version against the deleted article ourselves, we can clearly see that it is not substantially equivalent or identical. Throwing this to AfC is just creating work that doesn't need to be done and isn't required in any way. Horse Eye's Back (talk) 16:11, 15 June 2025 (UTC)[reply]
  • No action. It is possible to replace the redirect with a suitable new version of the article without a deletion review. If unsure and want a second opinion, you can do what Robert McClenon said, but not even that is required.—Alalch E. 16:06, 4 June 2025 (UTC)[reply]
    User:Alalch E. - The appellant has already done that several times, and has been reverted citing the AFD each time, mostly recently twice in early May 2025. The subsequent versions have been similar to the deleted version but have added to it, and so have not been identical to the deleted version. Another "suitable new version" will probably also be reverted citing the AFD. Review of a draft is more likely to work than slow-motion edit-warring between slightly different versions and the redirect. Robert McClenon (talk) 18:41, 4 June 2025 (UTC)[reply]
    If he makes a good attempt, and restores from redirect while addressing the reason for deletion, he can't simply be reverted. A suitable version is a version suitable for inclusion in the encyclopedia: notable topic, no content problems. —Alalch E. 19:42, 4 June 2025 (UTC)[reply]
    It appears that the appellant did make a good attempt, and was simply reverted. I, for one, would rather see an unnecessary trip to DRV or an unnecessary use of AFC as opposed to slow-motion edit-warring. What are you, User:Alalch E., saying the user should do? Robert McClenon (talk) 03:16, 5 June 2025 (UTC)[reply]
    First of all, we're having a full discussion process now at DRV, when it should have been at AfD. I'm of a principled view that we should not be trying too hard to prevent repeated AfDs, and if it really becomes a bother, the response should address conduct. Appellant did the right thing by stating the notability case on the talk page upon restoring with improvements. Restoring the redirect after that is WP:BLARing. It is explicitly reversible, to be followed by AfD. After being reverted he should have pinged the reverter in that talk topic and directed him to start an AfD instead. This can't be analyzed using the straightforward edit-warring paradigm. Restoring from a redirect in good faith is creating content and this action is privileged. It isn't a normal edit, it's a privileged action that is contested via formal process.
    The new page reviewer did fine to BLAR. We should trust that he is able to tell if the improvement overcomes the reasons from the AfD or not. But it is still his opinion, which he can't enforce. Seeing that his BLAR was reversed, I am confident that this new page reviewer would not have reverted; there would not have been such edit warring. But then another editor came along and replaced the content with the redirect again, and that wasn't good. That was actually edit warring. The community should be (and is) able to address that without pretending that it requires a Deletion review. It's a matter of conduct, not deletion process. The problem is enforcing one's opinion in a dispute (a dispute around eligibility of an article) instead of using an established venue to resolve such a dispute (AfD).—Alalch E. 13:17, 5 June 2025 (UTC)[reply]
    So to conclude, I would rather see a necessary trip to ANI or ANEW, than an unnecessary trip to DRV. There's a power imbalance involved, but DRV should not be a cushion for this power imbalance. That is not nice. That would be a bad regime. Notional review that actually covers for incorrect actions of the power elite. —Alalch E. 13:21, 5 June 2025 (UTC)[reply]
    All I saw is that no one read my notability case statement in the talk page before reverting. They saw the previous AfD decision was to merge, then they decided to revert it. Superlincoln (talk) 06:18, 6 June 2025 (UTC)[reply]
    You did the right thing by stating the notability case on the talk page. You then need to ping and/or use {{tl|talkback}} to make sure that another editor reads. If there is no agreement, that editor needs to start an AfD. If he doesn't want to start an AfD and reverts repeatedly, he is behaving inappropriately and maybe needs to be blocked. In that case, report to administrators. —Alalch E. 10:35, 14 June 2025 (UTC)[reply]
  • Restore. The version that was redirected last month was quite different than the one discussed at the AFD in September 2024. Had it been deleted instead of redirected, G4 speedy deletion would not have applied. The merits of this updated article can be challenged at a second AFD if anyone wishes to do so. Frank Anchor 21:58, 4 June 2025 (UTC)[reply]
  • Maybe draftify? There does appear to have been enough new coverage since last time that a new discussion on notability would be due but thats hard to have when everyone is playing red ink-green ink. Horse Eye's Back (talk) 23:23, 4 June 2025 (UTC)[reply]
Restore Going over the article history again I see no valid policy or guideline reason for blanking the article... The blanks were "As per AfD" and "back to redirect per AfD" but AfD does not apply to substantially different material which is what we had here. Overall I think a large trout for @Onel5969 and Bbb23: is due... That being said DRV doesn't really seem like the place for this, the original AfD is not being challenged, honestly if I'd noticed all this earlier I would just have reverted Bbb23's baseless edit and given them a talking to on the talk page. Horse Eye's Back (talk) 15:57, 15 June 2025 (UTC)[reply]
@Horse Eye's Back: No trout for Onel5969, he's eminently entitled to confidence in making such decisions as a new page patroller and if he says "per AfD", we must assume the best possible interpretation of his work process and reasoning, which means assuming that he compared the AfD'd version with the new attempt and concluded that the new attempt does not overcome the reasons for deletion/redirection and that the same reasons still hold (= "per AfD"). That is great. No trout for that whatsoever. But when 1 (one) editor has done this, it's over. BLAR is exhausted. Otherwise n number of editors could "BLAR" any article mery-go-round style and enforce removal of the article outside of a consensus-based process, by each replacing the article with a redirect once, and never engaging in a discussion (please anyone don't claim BEANS because this is not a hypothetical scenario, this is exactly what has happened here and why we're wasting time in DRV). That is edit warring. Apply Wikipedia:Page-move war#Dealing with page-move wars by analogy (this would be redirect-warring). What I am advocating here is consistent with WP:BLAR, WP:ATD-R, and WP:BRD (and with WP:TAGTEAM/WP:GAME). —Alalch E. 16:12, 15 June 2025 (UTC)[reply]
NPP does not come with any such entitlement... And if it does then my autopatrolled status makes me their equal... The deleted version is not hidden, I should know I was the one to blank it as part of the merge process... This is the blanked version [7] and this is the one Onel5969 blanked [8]. No competent editor can call those identical, this was illegitimate blanking... In this context "per AfD" is a frivilous explantion. Horse Eye's Back (talk) 16:22, 15 June 2025 (UTC)[reply]
You are completely denying the ability to blank-and-redirect. Blanking-and-redirecting is within a guideline: WP:BLAR, and a policy: WP:ATD-R. Your analysis lacks a bit of nuance here. I think that we might agree if you incorporate the nuancing that is already written into PAG. The versions do not have to be identical. The standard is "does the new version overcome the reasons to redirect under the AfD consensus". —Alalch E. 16:26, 15 June 2025 (UTC)[reply]
And how would a competent argument be made that it does not overcome the reasons to redirect under the AfD consensus? It was redirected for not meeting notability, it now meets notability... Which seems to have been expected, as one merge vote states "I do not think this meets the GNG yet, though it might be close." (emphasis mine). Horse Eye's Back (talk) 16:33, 15 June 2025 (UTC)[reply]
The competent argument is that it still does not meet notability. I am not saying that it does or doesn't, but such an argument can be made competently. —Alalch E. 16:35, 15 June 2025 (UTC)[reply]
And I'm saying that it can't... And nobody yet has so the only way to demonstrate that it can is to make such an argument. Horse Eye's Back (talk) 16:37, 15 June 2025 (UTC)[reply]
You can't say that. You can say that in an AfD, but you can't say that such a determination cannot be made by one editor competently. He gets to try his idea out. He gets to try it out once, and if it doesn't work out he needs to prove his case in an AfD. What can't happen is another editor coming along and empowering his judgement by turning the page yet again back into a redirect. —Alalch E. 16:40, 15 June 2025 (UTC)[reply]
His judgement was bad. I see nothing to suggest that such a determination could be made competently... Again if you disagree then the burden is on you to demonstrate that it can be, I see no such path from a competent evaluation of the sources and context but I'm always open to being wrong. Perhaps much of this could have been avoided with better edit summaries, "As per AfD" and "back to redirect per AfD" don't really give us much to on, that leaves us just guessing as to what the reasoning actually was. Horse Eye's Back (talk) 16:50, 15 June 2025 (UTC)[reply]
You are entitled to say that it's bad but he's entitled to exercise his allegedly bad judgement. Once. The arena to decide what is bad and what is good is (a new) AfD. His "As per AfD" sufficiently clearly communicates that he did not believe that the reasons to make the article stop being live under the AfD consensus have been overcome. He can be thwarted in his exercise of allegedly bad judgement by simply being reverted. What can't happen is that his judgement, good or bad, gets supercharged by another editor simply blowing wind in his back, i.e., through sheer strength in numbers. —Alalch E. 17:04, 15 June 2025 (UTC)[reply]
I will agree that this discussion should have happened on that talk page instead of a second revert. The supercharging took it to another level which we're now dealing with the fallout from, even if we do seem to have arrived at a consensus. Horse Eye's Back (talk) 17:53, 15 June 2025 (UTC)[reply]
  • Restore. As the version that was redirected last month has most of the above press reports and sources added to the article. It also has significant work done to it too. These works should make it meet GNG. The reason to merge the one discussed at the AFD in September 2024 is because the it doesn't meet GNG. The version that was redirected last month does meet GNG, so it should be restored. Superlincoln (talk) 03:43, 5 June 2025 (UTC)[reply]
    You initiated this DRV, you don't need to !vote. SportingFlyer T·C 08:30, 8 June 2025 (UTC)[reply]
  • restore I'm struggling to evaluate the reliability of some of the sources, but the GNET one in particular looks quite good. Hobit (talk) 16:58, 6 June 2025 (UTC)[reply]
  • Comment It appears that this was un-redirected with differing content (from the original; from each other in at least one case) three times since the AfD closure. I'm not sure if we need a G4-like restriction on re-BLAR'ing without a subsequent discussion, but this would appear to make a decent case for it. Overall, I'd restore and start a new AfD if desired. Jclemens (talk) 04:58, 7 June 2025 (UTC)[reply]
  • Restore. Substantially different case, new sources look good to me. PARAKANYAA (talk) 21:18, 7 June 2025 (UTC)[reply]
  • Endorse I would not have accepted this at AfC, I don't think the sources are good enough. Most of these are mere mentions. SportingFlyer T·C 08:29, 8 June 2025 (UTC)[reply]
    • I would characterize the focus of the GNET article to be on the Urutau. It is mentioned (exactly I believe) 100 times. My quick research on GNET makes me think they count as reliable and independent. That is only one source, but it's a very good and in-depth source. While the others only mention it in the context of similar guns, it is usually the first one mention and/or listed. One really good source plus a few weaker ones is usually enough for us to cover the topic. So I get your take, but I think we have enough from multiple sources (if mainly one...) to write a good article. Hobit (talk) 03:30, 9 June 2025 (UTC)[reply]
      I would also characterize the main focus/topic of the 3D Printing Industry (3DPI) article to be on the Urutau. My quick research on 3DPI would lead me to believe they are a major, reliable and independent news source on the matter of 3D printing. Superlincoln (talk) 04:43, 12 June 2025 (UTC)[reply]
@SportingFlyer: The sources appear good enough, can you explain your judgement here? Are you saying that it meets our notability requirements but you have a higher bar than notability for accepting things through AfC? Horse Eye's Back (talk) 16:01, 15 June 2025 (UTC)[reply]
No, I don't think the sources are quite good enough. I'm not sure about the GNET or 3D Printing newsletter, and the other sources aren't SIGCOV or are on other products. We're not at zero, but I don't think this is as clear of a pass as other people seem to think. SportingFlyer T·C 20:10, 15 June 2025 (UTC)[reply]
The appellant already tried restoring the page, which included new information and sources, several times and it was reverted, citing the AFD. DRV seems like a logical next step to me. Frank Anchor 12:09, 13 June 2025 (UTC)[reply]
But that isn't really a matter of whether deletion process was followed, which is what DRV is for. It's a content dispute about whether the topic is better covered as part of a list or as an article. This should be resolved like any other content dispute on the article talk page (WP:DR). Sandstein 13:24, 13 June 2025 (UTC)[reply]
But we're here anyway, even if this isn't the most perfect venue, and a constructive discussion is in progress. Seems like WP:NOTBURO would apply in this case. Frank Anchor 13:58, 13 June 2025 (UTC)[reply]
Also the people who reverted the article after i restored it never attempted to contact me or started a discussion in the article's talk page. The only way to avoid the article from getting reverted after restoration is to get rid of the AfD. But to get rid of the AfD, u need to start a DRV. Superlincoln (talk) 14:03, 13 June 2025 (UTC)[reply]
After the revert, it is for you to take it to the talk page, Talk:List of 3D-printed weapons and parts. Make the case there. SmokeyJoe (talk) 00:05, 14 June 2025 (UTC)[reply]
No, it's for the reverted reverter to start a new AfD, as he cannot re-revert (cannot BLAR again once reverted). —Alalch E. 10:28, 14 June 2025 (UTC)[reply]
Ok. User:Superlincoln reverted the redirect, 18 April 2025, over six months after the AfD. And they made a post to the talk page of the redirect target. That was good.
6 and 7 May, 2025, two other editors, they seem previously uninvolved, reverted back to the redirect.
The AfD consensus was between “merge” and “delete”. This matters. It was not “keep”/“merge”.
The most recent non-redirect version, is, in my opion, WP:Reference bombed.
I recommend that attempts to recreate be referred either to that talk page, Talk:List of 3D-printed weapons and parts, or draftspace with notice posted at Talk:List of 3D-printed weapons and parts, and that a tabular WP:SIRS analysis be done. Use the WP:THREE best sources, ping all known detractors of the spinout, and if you can defence three sources, recreate in mainspace, but without the reference bombing. If I saw the last version at AfD, I would !vote “draftify” due to reference bombing. SmokeyJoe (talk) 00:42, 15 June 2025 (UTC)[reply]
Regarding the three best sources:
I consider these links to be the best sources of the above post
1.https://gnet-research.org/2025/01/08/beyond-the-fgc-9-how-the-urutau-redefines-the-global-3d-printed-firearm-movement/
2.https://3dprintingindustry.com/news/terrorism-expert-warning-on-new-simplified-3d-printed-gun-and-manifesto-235518/
3.https://www.linkedin.com/pulse/feathers-fury-in-depth-analysis-z%C3%A9-cariocas-podcast-interview-f%C3%BCredi-f9g0e/
Superlincoln (talk) 13:25, 9 June 2025 (UTC)[reply]
I will be interested to read what others have to say about independence. SmokeyJoe (talk) 00:49, 15 June 2025 (UTC)[reply]
  • Comment Let's sum up. I think we have consensus, if perhaps not 100% agreement, that WP:N is now met and the only remaining issue is one of process. so I think per WP:BURO the final place we should get to is plain. The question is, what is the right process. I was looking for guidance about how this situation should be handled in our policies and guidelines and I'm not finding anything. WP:REDIRECT seems to have very little. I think what we'd prefer people do when finding new sources for an article that was redirected at AfD is that they BOLDly restore it, and if reverted, discuss it (probably at the target article). That (undocumented?) step was skipped here. My questions are then:
    • Should that step be clearly documented at WP:REDIRECT (or did I miss it)?
    • What is the next step if an article passing WP:N doesn't get consensus to be unredirected and the nom wants a wider discussion?
    • What is the role of DRV here?
I guess we could hold an RfC on this, but I'm guessing I'm just missing documentation on the issue. Anyone have a pointer? If not, this seems like a good group to hash out something... @SmokeyJoe:, @Sandstein:, @Alalch E.:, @Robert McClenon:, @Horse Eye's Back:, @SportingFlyer:.Hobit (talk) 14:31, 15 June 2025 (UTC)[reply]
I think DRV has no proper role here. The AfD is not seriously challenged, and there has been no deletion. It is a WP:SPINOUT dispute. DRV is not a forum for solving all disputes.
Mostly, one editor boldly re-spunout the article, and two reverted that. If any second editor in good standing wants the page in mainspace and subject to AfD, then they have that right. A trivial mechanism for that is to Draftify and then Mainspace the page. I recommend this, because I think the page is at risk of being deleted due to reference bombing. SmokeyJoe (talk) 14:43, 15 June 2025 (UTC)[reply]
The editor who boldly re-spins-out has the status of "article creator" in the language of WP:BLAR and cannot be reverted repeatedly, only once. Multiple reverts coming from multiple editors does not mean that BLAR can be repeated ad nauseam as long as there are new editors willing to reredirect. After Onel5969 BLARed, there's no more BLARing of that same attempt to create, no matter how many editors are involved.
  • Good: (1) Restore from redirect (in good faith, at least a step in the right direction) -> (2) BLAR -> (3) BLAR reverted -> (4) AfD, or talk-page talk (it may be worth trying to restore the redirect on a consensus basis by explaining things to the "article creator"; he can be told to wait a bit more and try again with sourcing that's a bit better, etc.), or give up and let the article exist (anyone can AfD at any time).
  • Not good: (1) Restore from redirect (...) -> (2) BLAR -> (3) BLAR reverted -> (4) revert of 3 (that's unacceptable) -> whatever (especially not DRV).
Alalch E. 15:52, 15 June 2025 (UTC)[reply]
I don’t agree with you. It matters that there was an AfD consensus to not “keep”. Short of WP:Tag team, if it is different uninvolved editors that revert to the redirect each time, and only the same editor that reverts to the article, that single editor loses, and risks being blocked for disruption. It is critical that another editor reverts the revert. If any editor but User:Superlincoln reverts to the article, then it sticks in mainspace and detractors should send it to AfD.
If no editor will support Superlincoln, then they should take the AfC route.
This is an interesting DRV discussion, but disputes over reverting a merge should not usually come to DRV. SmokeyJoe (talk) 14:30, 16 June 2025 (UTC)[reply]
@Hobit: In the above exchanges you are able to see some pretty neatly delineated differences of opinion on the process to restore the article from a redirect. Given a blanking-and-redirection of an attempt to restore from a redirect, Horse Eye's Back is opposed to it having happened in the first place if the new version has new sources; I am not opposed to it happening even if the article has new sources, but only once, with other editors not being allowed to pile on to enforce removal of the article (according to this, BLAR would be single-shot in absolute terms); and SmokeyJoe is okay with multiple editors being allowed to conduct distributed enforcement of the removal of the article, as long as the editors are not tag-teaming (according to this, BLAR would be single-shot only in relative terms, as each uninvolved editor carries one shot). —Alalch E. 16:32, 16 June 2025 (UTC)[reply]
I very much disagree with the notion there's consensus GNG is met here. SportingFlyer T·C 20:13, 15 June 2025 (UTC)[reply]
I think you are the only one who has directly commented on the GNG and had doubts. Thus my not 100% line. Could you expand on your issue? The GNET one seems about as good as one could hope (unless I'm missing a COI there which is possible--this isn't my area of expertise). Some of the others are also pretty good. Hobit (talk) 22:30, 15 June 2025 (UTC)[reply]
That's the best source, but the other sources aren't great - lots of mere mentions in articles, a trade magazine, an interview with the guy who made it (not independent) - and it's also unclear as to its independence, considering GNET has a "Write for us" page that pays people £300 for submissions, and their editorial policy is unclear. It's not obviously clear it's a 10 out of 10 source in terms of quality, and even then it's unclear where the multiple other sources come from. SportingFlyer T·C 15:21, 16 June 2025 (UTC)[reply]
I agrre with SmokeyJoe that this is not a matter for DRV. Sandstein 06:47, 17 June 2025 (UTC)[reply]
The problem comes from the blanking/reverting... That isn't kosher, it isn't within policy or guideline. Note that blankers were admins but these were not admin actions, if the article has new sources then AfD or a merge discussion needs to be run again... The previous consensus does not stand. Horse Eye's Back (talk) 16:07, 15 June 2025 (UTC)[reply]

Ayesha Singh (closed)

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

Actress passes WP:NACTOR Alexroybro (talk) 06:14, 4 June 2025 (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.
Shehzad Shaikh (talk|edit|history|logs|links|watch) (XfD|restore)

Actor passes WP:NACTOR Alexroybro (talk) 06:19, 4 June 2025 (UTC)[reply]

The draft title is ECP-protected. Frank Anchor 17:19, 4 June 2025 (UTC)[reply]
Noted, as is the history of sockpuppetry. Robert McClenon (talk) 18:49, 4 June 2025 (UTC)[reply]
  • Endorse Speedy endorse the AFD and most of the following deletions (I have some issue with the 2019 G4s since the original AFD was sparsely attended, but that's not what's being challenged here). Draft title is ECP protected, meaning that any established user in good standing can create a draft version in good faith. Based on the appellant's edit history, I do not believe this is a good faith attempt at recreating this page up to encyclopedic standards. Frank Anchor 17:19, 4 June 2025 (UTC)[reply]
Changed to speedy endorse as appellant has been identified and blocked as a sock. Nothing more to do here. Frank Anchor 00:45, 5 June 2025 (UTC)[reply]
  • Endorse, as I will in all cases of review requests by newly-registered users for articles deleted, let alone salted, as G5. —Cryptic 19:30, 4 June 2025 (UTC)[reply]
  • Keep deleted. It is possible to use AfC and/or ask directly for the protection to be removed, but the initiative should come from an established editor. This initiative does not seem credible.—Alalch E. 21:17, 4 June 2025 (UTC)[reply]
  • See my comment above, under Ayesha Singh, about Alexroybro having now been blocked as a sockpuppet existing only to restore deleted pages previously created and edited by a blocked editor. JBW (talk) 23:42, 4 June 2025 (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
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