Jump to content

Wikinews:Deletion requests

From Wikinews, the free news source you can write!


This page is where Wikinewsies discuss whether a page or file should be deleted or undeleted through consensus. See the Deletion Log or the Deletion Archives to see which pages have been deleted or kept.

Deletion requests

[edit]

February 13, 2026

[edit]

Not newsworthy per Gryllida (talk · contribs) at Talk:Muhammad Qasim Observational case report on late-onset hair regrowth published, medical review invited: Date Feb 03 is over a week old, which is not "fresh and current". Please see WN:Newsworthiness. Older events are no longer news. HKLionel TALK 09:55, 13 February 2026 (UTC)[reply]

Okay. but article came on 3rd feb. not today. cant understand, if article went in review definably it will go old by time.
its okay. if its not newsworthy, lets remove it. trying to bring work on new. or let me know, how can i contribute more any where. thanks Camronsteven (talk) 12:35, 13 February 2026 (UTC)[reply]
You took 5 days to address the issues Metropolitan90 (t · c · b) pointed out on Feb 5th. Per WN:Newsworthiness, an article is considered stale within 5-7 days. Feb 5th was only 2 days after Feb 3rd. Since you addressed the issues on Feb 10th, the article was essentially already stale by then, so you can't really fault Gryllida (t · c · b), but I agree the review could've been done earlier. There are plenty of ways you can contribute, starting from the advice at WN:Introduction. HKLionel TALK 12:44, 13 February 2026 (UTC)[reply]

Comments

[edit]

@Camronsteven: do not remove Template:Dr from the article, comment/vote here instead. HKLionel TALK 11:55, 13 February 2026 (UTC)[reply]

Comment There were a number of issues that would have prevented publication of the story. There were WN:Plagiarism issues (from The Globe and Mail source), neutrality and balance issues, and WN:Freshness issues.
@Camronsteven, it might be easier to learn the system by first contributing to articles started by others. But if you decide to start another article from scratch, which is fine, I recommend working with other contributors to get it ready for review. You can possibly even request a {{Pre-review}} to make sure everything is buttoned-down before requesting a formal review.
I have deleted the article as requested by the original author and growing consensus here.Michael.C.Wright (Talk/Reviewer) 15:25, 13 February 2026 (UTC)[reply]

Votes

[edit]

February 1, 2026

[edit]

@New mayo, Metropolitan90, Wikiwide, Gryllida: notifying article contributors for awareness only.

I propose this article be retracted due to multiple failures to comply with WN:Plagiarism (proposed guideline), WN:CS (policy), WN:NPOV (policy), and WN:MOS (guideline). Taken together, these issues are sufficiently extensive that post-publication correction is not practical.

These problems were identified during the archival process. In light of the reviewer’s previously stated position regarding the scope of their reviews, this case raises concerns about whether the review performed met the expectations outlined in policy.

The following statement is was plagiarism. It is not detected by Earwig, which I believe will not scan Reuters due to their Robots.txt directive. The text can be found by a manual search. It could be fixed even post-archive if it was the only issue. This statement was removed and a note placed on the article.[1]

  • "57 years old and had entered the Turkish Air Force in 2010."

The following statements are unsupported by the listed sources, but verifiable elsewhere:

The following statements are unsupported by the listed sources:

  • "that has been compared by Reuters" Reuters didn't compare the two, only mentioned it as background.
  • "seen with a smoking engine descending in a flat spin" Reuters reports eyewitness accounts of fire, not smoke
  • "vanished from radars 27 minutes later" Author's analysis maybe?
  • "27 minutes after takeoff" Author's analysis maybe?
  • "According to Georgian authorities and Turkish officials"
  • "by November 13"
  • "By November 14, Turkish and Georgian officials continued joint inquiries."
  • "and support" NATO Secretary General expressed his condolences. No source supports the statement that NATO offered support or expressed condolences.

The following are style guide issues:

  • "The cause of the crash remains under investigation" (present tense)
  • "but investigations are ongoing..." (present tense)
  • "Georgian authorities confirmed the wreckage was found near the border region." exact same sentence in lede, not an SG issue per-se, but should have been caught

Attribution: There are too many phrases to include here. Below are a few examples:

  • "killing all 20 military personnel on board"
  • "vanished from radars 27 minutes later"
  • "the wreckage was found near the border region"
  • "all soldiers were killed"
  • "communication was lost"
  • "the remains of the military personnel ... were recovered by November 13"
  • "the flight recorder (black box) was recovered"
  • "the cause of the crash remains under investigation"
  • "the cause of the crash remains undetermined"

Please vote using Keep, Remove, Neutral, or Comment followed by signature. Michael.C.Wright (Talk/Reviewer) 19:10, 1 February 2026 (UTC)[reply]

Comments and Votes

[edit]
  • Keep My note is that the proposed level of scrutiny is too high. Articles written at the site are going to inevitably have issues and not be perfect if someone puts a few hours to check each letter. I do not see any of the above issues sufficiently major to require a retraction. If there is something that actually misinforms the reader about what happened, then it may be included in a correction. Gryllida 22:07, 1 February 2026 (UTC)[reply]
    Wikinews archival policy limits post-publication changes to narrowly scoped factual corrections with documentation. The issues raised in this proposal extend beyond isolated factual errors and include attribution, sourcing, and structural compliance problems, which are not ordinarily addressed through post-archival edits. This is why retraction is being proposed rather than incremental correction.Michael.C.Wright (Talk/Reviewer) 13:05, 2 February 2026 (UTC)[reply]
  • Keep Neutral Comment While on the first glance I couldn't find "smok" in the text of the sources, I haven't re-read them yet. Both Al-Jazeera and Independent clearly show, in video and photograph, that the falling airplane emitted plenty of smoke even before crashing into the ground; whether it was smoking engine, smoking wing, or smoking door, I cannot say right now, I am not an airplane expert, but it was not a cigarette. I don't like the idea of removing a piece of text just because it is plagiarism; re-phrasing would be preferable, so that information would not be lost. If Reuters has such a hostile robots.txt, then some tool, Earwig or whatever else, should alert the contributors against usage of such sources - forcing humans to do Earwig job manually is not sustainable. As it is, I cannot be certain that your points about lack of attribution are valid - information had to have come from somewhere, it just needs to be found where it came from. Will re-read later. Wikiwide (talk) 23:25, 1 February 2026 (UTC)[reply]
    To clarify; the video and photographs showing smoke are of the Turkish C-130 crash itself. However, the “smoking engine descending in a flat spin” description originates from Reuters’ background reference to a separate, 2017 US Marine Corps KC-130 accident, not from reporting on this incident.
Even if the smoking engine statement was about the Turkish crash, for which there is video, Wikinews policy does not permit editors to analyze or speculate. As stated in the neutrality policy, contributors must avoid analysis and speculative interpretation unless explicitly attributed to qualified sources. In this case, we have reporting that sufficiently describes the scene without our interpretation or analysis. The change was not necessary.
Lastly, while the 'smoke' wording would be a minor issue in isolation, it reflects a broader pattern in this article involving unsupported claims, attribution gaps, and style guide issues that should have been fixed during pre-publication review. The retraction proposal is based on the cumulative impact of these issues rather than any single descriptive detail.
The plagiarism has already been removed as a priority along with placing a reader-facing note for transparency.Michael.C.Wright (Talk/Reviewer) 13:27, 2 February 2026 (UTC)[reply]
  • Remove (retract with statement and blanking article) There is precedent for retracting articles with fewer issues and also specifically for inadequate reviews. For example:
I propose the following retraction statement:

This article has been retracted because a post-publication review identified multiple policy and guideline failures, including plagiarism, unsupported and misattributed statements, sourcing gaps, attribution problems, and style compliance issues. The cumulative scope of these problems made reliable post-publication correction impractical.
The last version of the article text can be found here.

Michael.C.Wright (Talk/Reviewer) 15:09, 4 February 2026 (UTC)[reply]

January 22, 2026

[edit]

State reason for deletion request and sign with BigKrow (talk) 20:19, 22 January 2026 (UTC).[reply]

Nomination again. BigKrow (talk) 20:19, 22 January 2026 (UTC)[reply]

Comments

[edit]

nominating again with my evidence.—The preceding unsigned comment was added by BigKrow (talkcontribs)

Please add the specific evidence supporting this deletion request.
Per deletion guidelines and Wikinews:Criteria_for_deletion#Cases_where_deletion_may_be_required, deletion requests must clearly state the applicable criterion and the supporting rationale.
If no evidence or criterion is provided, the request cannot be evaluated and may be removed as procedurally invalid.Michael.C.Wright (Talk/Reviewer) 14:20, 23 January 2026 (UTC)[reply]
This request does not cite any applicable deletion criteria or provide a supporting rationale, so it cannot be evaluated. It has now remained open beyond the recommended, seven-day period.
For reference, a consolidated list of related discussions is available on the article talk page.
As the reviewer of the article, I am noting my involvement for transparency. Absent any objections, I intend to close this request on procedural grounds with no action taken.Michael.C.Wright (Talk/Reviewer) 16:23, 7 February 2026 (UTC)[reply]
This user is promoting story on other sources as well. @Michael.C.Wright BigKrow (talk) 23:40, 7 February 2026 (UTC)[reply]

Votes

[edit]

Remove —The preceding unsigned comment was added by BigKrow (talkcontribs) [2]

September 11, 2025

[edit]


This conversation has been marked for the community's attention. Please remove the {{flag}} when the discussion is complete or no longer important.


This is a proposed retraction of a published article.

As stated on the article talk page: the article contains no attribution, meaning every statement is presented in Wikivoice, asserted by Wikinews.

Additionally, several key statements are unsupported by the sources provided (emphasis added):

  • "Survivors described the floods as sudden and catastrophic..."
  • "The scale of destruction was unprecedented..."
  • "...with dozens of villages damaged or flattened..."
  • "The recent flash floods in Pakistan amid heavy monsoon rains have caused one of the deadliest natural disasters in the region..."
  • "...amid worsening weather conditions..."

The review summary noted that the last paragraph was “probably AI generated and needs some revision to reduce bias and make it more factual,” meaning the bias was recognized at the time of publication. A 12-hour window was provided for revisions, but the issues were not addressed. Since the article still contains unsupported statements and lacks attribution, and more than 24 hours have passed, the problems cannot be corrected without a substantial rewrite, which WN:ARCHIVE prohibits. Therefore, a correction statement is insufficient; the article should be fully retracted, with its content blanked and replaced by a retraction notice.

As stated by the original author, the article was mostly written by AI. According to WN:AI (a proposed guideline), "Wikinews articles must always reflect human-reviewed accuracy, neutrality, and verification of sources."

Given the issues with WN:NPOV, WN:Source, and WN:AI, I propose this article be retracted.

Comments

[edit]
  • Comment If consensus is to remove the article, I propose the addition of the following retraction statement and a blanking of the article:

This article has been retracted because it failed to comply with our sourcing policy, neutrality policy and recommended guidance for AI/LLM use.
The last version of the article text can be found here.

Votes

[edit]

Please vote using Keep, Remove, Neutral, or Comment followed by signature

Neutral, BigKrow (talk) 18:59, 11 September 2025 (UTC)[reply]

Could you share a bit more about your perspective? For example, do you see a preferred course of action besides retraction, or do you view the article differently than my assessment, or do you think a specific policy or guideline needs to be changed? Your thoughts could help shape consensus before the discussion closes.Michael.C.Wright (Talk/Reviewer) 13:09, 12 September 2025 (UTC)[reply]
I will vote per nom. Thanks @Michael.C.Wright BigKrow (talk) 14:59, 12 September 2025 (UTC)[reply]
I didnt get it. Why not do "correction" by removing biased words? Gryllida 20:44, 13 September 2025 (UTC)[reply]
WN:ArchiveMichael.C.Wright (Talk/Reviewer) 14:48, 14 September 2025 (UTC)[reply]
Remove Since this was "mostly" AI generated and includes several unsupported statements, I think we should retract the article. We need to ensure we are not allowing "AI Slop"[3] to creep into Wikinews.Michael.C.Wright (Talk/Reviewer) 01:57, 24 September 2025 (UTC)[reply]
Remove, we should not keep AI-generated articles. Ternera (talk) 21:32, 17 November 2025 (UTC)[reply]
Why though? @Ternera BigKrow (talk) 21:45, 17 November 2025 (UTC)[reply]
It is prone to including errors and honestly, it's a more lazy way of writing that does not take much effort. We should focus on keeping quality articles only in my opinion. Ternera (talk) 21:52, 17 November 2025 (UTC)[reply]
I love AI though maybe that makes me "lazy too". BigKrow (talk) 22:01, 17 November 2025 (UTC)[reply]
I think we can differentiate between AI-assisted and AI-generated. AI-assisted is permitted, even encouraged for some uses, as briefly discussed in Help:AI.
AI-generated is frowned upon, discouraged, and in our proposed WN:AI, forbidden.Michael.C.Wright (Talk/Reviewer) 01:08, 18 November 2025 (UTC)[reply]
Remove per nomination ~2025-42360-72 (talk) 23:55, 21 December 2025 (UTC)[reply]

Undeletion requests

[edit]

17 April 2025

[edit]


Proposed deletions

[edit]

 Purge server cache  For reference, it is currently February 15, 2026.

Copyvio

[edit]

Delete articles posted before February 14.

Abandoned

[edit]

Delete articles posted before February 13.

Minimal and PR

[edit]

Delete articles posted before February 12.


Unsourced prepared

[edit]

Delete articles posted before February 5