Jump to content

Wikipedia:Requests for page protection

Page semi-protected
From Wikipedia, the free encyclopedia
    Welcome—request protection of a page, file, or template here.

    Before requesting, read the protection policy. Full protection is used to stop edit warring between multiple users or to prevent vandalism to high-risk templates; semi-protection and pending changes are usually used to prevent IP and new user vandalism (see the rough guide to semi-protection); and move protection is used to stop pagemove revert wars. Extended confirmed protection is used where semi-protection has proved insufficient (see the rough guide to extended confirmed protection).

    After a page has been protected, it is listed in the page history and logs with a short rationale, and the article is listed on Special:ProtectedPages. In the case of full protection due to edit warring, admins should not revert to specific versions of the page, except to remove obvious vandalism.


    Request addition of protection to a page, or increasing the current protection level

    Request removal of protection from a page, or reducing the current protection level

    Request a specific edit be made to a protected page
    Please add an edit request to the talk page of the protected page before adding an edit request here


    Current requests for increase in protection level

    Request addition of protection to a page, or increasing the current protection level

    Place requests for protection increases at the BOTTOM of this section. If you cannot find your request, check the archive of requests or the page history. Only recently answered requests are still listed here.

    Reason: Daily unproductive editing from TAs which resumed almost immediately following the expiration of a month-long block imposed in late February. A repeated pattern is the unexplained removal of article content—one of the most common forms of vandalism—and the addition of unsourced/undue information. Realistically, I can't imagine a future where this page ceases being a target for childish trolls, given the sensitive subject matter at hand. The fact that no tin-foil hat has yet tried to insert their own agenda is a miracle, since as most of you reading this may know, Sandy Hook theories are unfortunately prominent in conspiracy spaces. Giovanni Potage (talk) 07:23, 5 April 2026 (UTC)[reply]

    Reason: High level of IP vandalism IP Always Change The Article Without Sources. Masare012 (talk) 10:33, 5 April 2026 (UTC)[reply]

    Reason: Several attempted expansions into a full-fledged article throughout history, despite glaring WP:1E issues—including a recent incident involving a sockpuppet. I see no reason why non-EC editors should edit this page, especially since it is a redirect and will likely remain so until the end of time, given that Stair is only notable for one shooting that received a bulk of its coverage from local news outlets. Giovanni Potage (talk) 10:39, 5 April 2026 (UTC)[reply]

    DeclinedPages are not protected preemptively. If we exclude the sockpuppet, "several attempted expansions" comes to exactly once, three years ago. You may see no reason why non-EC editors should edit this page, but policy does. - The Bushranger One ping only 19:35, 5 April 2026 (UTC)[reply]

    Reason: I request semi-protection for Apsara because there has been repeated removal of significant content by new users over the past month. Despite multiple reverts, the disruptive behavior continues.

    Diffs of recent vandalism:

    Semi-protection is requested to prevent further vandalism and preserve the integrity of the article. RaSriAiem (talk) 13:17, 5 April 2026 (UTC)[reply]

    Reason: The page 2026 Pakistan Super League has been targeted by frequent IP vandalism and occasionally receives unverified edits. Applying semi-protection will help maintain reliability and prevent disruptive changes. Elison Pokhrel (talk) 14:59, 5 April 2026 (UTC)[reply]

    Semi-protection: Persistent addition of unsourced or poorly sourced content – Season 3 controversy TAs are still able to get through.   –Skywatcher68 (talk) 16:33, 5 April 2026 (UTC)[reply]

    Semi-protected for a period of one month, after which the page will be automatically unprotected. I had issued a block in response to the last request, so it wasn't denied, but it seems that wasn't enough, unfortunately. Left guide (talk) 20:33, 5 April 2026 (UTC)[reply]

    Temporary semi-protection: Persistent disruptive editing – By LTA (see edit filter log for page). Eyesnore talk💬 19:46, 5 April 2026 (UTC)[reply]

    Semi-protection: Persistent sockpuppetry. 45dogs (they/them) (talk page) (contributions) 20:24, 5 April 2026 (UTC)[reply]

    Temporary semi-protection: Persistent disruptive editing – Repeated additions of unsourced statements (that belong on another article if at all) by non-autoconfirmed editors. The Bushranger One ping only 20:26, 5 April 2026 (UTC)[reply]

    Indefinite extended confirmed protection: Arbitration enforcement – Per sanctions on Kurdish topics. Semsûrî (talk) 21:12, 5 April 2026 (UTC)[reply]

    Once again, I was ready to say "Kurd topics make up only a tiny part of this article, so it doesn't need protection", then I checked the article history. I'm not sure if I was dissapointed or not dissapointed, but either way Extended confirmed protected indefinitely. The Bushranger One ping only 22:06, 5 April 2026 (UTC)[reply]

    Temporary full protection: Death rumors across multiple articles and sources will cause confusion, also can cause poor or unsourced edits. xxᴄʀᴏꜱꜱxx (talk) 22:11, 5 April 2026 (UTC)[reply]

    Declined – No changes to the current protection level are required at this point in time. No such rumors have been added to the article. - The Bushranger One ping only 22:16, 5 April 2026 (UTC)[reply]

    Pending changes: Persistent disruptive editing – TAs (and IPs before that) have repeatedly attempted to change the lead "is" to "was" in contravention to MOS:TVNOW (which asserts that this is supposed to be based on the existence of the show, not the broadcast of it). WCQuidditch 22:32, 5 April 2026 (UTC)[reply]

    Current requests for reduction in protection level

    Request removal of protection from a page, or reducing the current protection level

    Before posting a request for unprotection, please discuss it with the protecting administrator first. You can create a request below only if you receive no response from them.

    To find out which administrator protected the page, go to the page's edit history and click on the "View logs for this page" link (located underneath the page's title). The protecting administrator is listed in the protection log entry, next to the words "protected", "changed protection level", or "configured pending changes". If there are a large number of log entries on the page, use the drop-down menu near the top of the page and select "Protection log" or "Pending changes log" to filter the logs accordingly.

    DO NOT request a reduction in protection if...

    • ...you are being prevented from editing the page. A desire to change content is not a valid reason for unprotection. Instead:
      • If you can edit the article's talk page, use the WP:Edit Request Wizard to propose a change on the article's talk page. Include an explanation of the exact content that you want to change, and what the content will be afterward.
      • If the article's talk page is protected, you may propose a change at Wikipedia:Requests for page protection/Edit.
    • ...your reasoning for reducing protection is that the article has not been vandalized. That simply means the protection is working as intended.
    • ...your reasoning for reducing protection is basically "a long time has passed" without supporting details.
    • ...you haven't contacted the protecting administrator.

    You may request a protection reduction below if...

    • ...you want to change the protection level of a template or module from full protection to template protection. You may add the request to this page without having to discuss it with the protecting administrator first.
    • ...you need to remove creation protection from a location where no page exists (redlinked pages) after a draft version of the intended article is prepared beforehand and ready to be published.
    • ...you are proposing a trial reduction in protection for a page that has been protected for several years, provided the proposal is supported by evidence such as talk page activity, page views, page traffic, number of watchers, frequency of edit requests, and prior history of vandalism.
    • ...the protecting administrator is inactive or has not responded to you in several days.

    If you cannot locate your request, make sure to check the request archives to see if it's been moved there. Only requests that have been recently answered will still be listed here.

    Reason: The page could really do with some improvements. Extended protection is not required as such as just normal is feasible. If problems do arise after improvements, then we can most definitely move it to extended again - but DO decrease the protection as improvements can be made. ~2026-21066-41 (talk) 16:41, 5 April 2026 (UTC)[reply]

    Not done As this article was protected under WP:GSCASTE, which has been taken up by Arbcom as WP:CT/SASG, it cannot be unprotected at RFPP. You must either request it from the protecting admin, or request unprotection at WP:AE. - The Bushranger One ping only 16:54, 5 April 2026 (UTC)[reply]
    Actually they can't even do that; the protection is in place to technically enforce a extended-confirmed restriction. The only way the protection could be challenged, let alone lifted, is if the underlying remedy is rescinded. —Jéské Couriano v^_^v threads critiques 16:59, 5 April 2026 (UTC)[reply]
    @Jéské Couriano: Given the recent narrowing of scope of SASG from "South Asian social groups" to "caste-related topics", you could make the argument that the page doesn't fall enough under it to be covered by the ECR. It's not an argument I'd make and I wouldn't expect AE to agree either, but I can see it being made in good faith. - The Bushranger One ping only 17:12, 5 April 2026 (UTC)[reply]
    I view the "caste" designation as half about actual castes and half about ethnicity. —Jéské Couriano v^_^v threads critiques 18:11, 5 April 2026 (UTC)[reply]

    Current requests for edits to a protected page

    Request a specific edit be made to a protected page
    Please add an edit request to the talk page of the protected page before adding an edit request here

    Requests for specific edits should be made on the talk page of the protected article. You can create an edit request below only if the talk page is also protected, preventing you from adding a request there.

    Otherwise, if you are unable to add a request to the article's talk page, you may use this page to propose a specific edit to be performed. Vague requests that don't propose a specific edit will be declined. Please see the top of this page for instructions on how to properly add a request.


    in the part that explains what us lost, change that the us had 5 KC-135 stratotankers damaged and 1 E3 awacs destroyed (https://www.airandspaceforces.com/us-forces-saudi-arabia-iran-attack/ and https://www.twz.com/air/images-purportedly-show-e-3-sentry-totally-destroyed-from-iranian-strike) first time editing a large page yay GalaxyHHDH (talk) 17:00, 2 April 2026 (UTC)[reply]

    Handled requests

    A historical archive of previous protection requests can be found at Wikipedia:Requests for page protection/Archive.