Edge Rewrite
// HTMLRewriter · presentation

This page was redesigned at the edge.

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

Jump to content

Wikipedia:Requests for page protection

(Redirected from Wikipedia:Rpp)
    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

    Request the non-urgent protection of multiple pages that do not require immediate administrator attention


    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.

    Temporary semi-protection: Persistent vandalism. Aleain (talk) 21:14, 29 July 2026 (UTC)reply

    Semi-protected for a period of 1 week, after which the page will be automatically unprotected. Less Unless (talk) 08:32, 31 July 2026 (UTC)reply

    Reason: Resumed sockpuppetry/block eviasion via Wikipedia:Sockpuppet investigations/Son of Zorn. Also worth noting this resumed immediately following the most recent page protection lasting from April 29 to today. Magitroopa (talk) 01:51, 30 July 2026 (UTC)reply

    Semi-protected for a period of 6 months, after which the page will be automatically unprotected. Staraction (talk · contribs) 16:06, 31 July 2026 (UTC)reply

    Temporary semi-protection: Persistent disruptive editing – Info repeatedly changed, often without source and/or consensus. Junosangleave a message 02:14, 30 July 2026 (UTC)reply

    Temporary semi-protection: Persistent sockpuppetry – Let's lock this up for a few months...see if the IP shocking just gives up. Moxy🍁 02:37, 30 July 2026 (UTC)reply

    I feel like this protection should be indefinite, given that it has needed protection 20 times in the past XXXX6666XXX (t · c) 03:20, 30 July 2026 (UTC)reply

    Temporary semi-protection: Persistent disruptive editing. Danners430 tweaks made 08:38, 30 July 2026 (UTC)reply

    Reason: Persistent vandalism from unregistered users Adig-pt (talk) 09:32, 30 July 2026 (UTC)reply

    Temporary semi-protection: Persistent disruptive editing. – DreamRimmer 12:22, 30 July 2026 (UTC)reply

    Already protected by administrator Epicgenius. Malcolmxl5 (talk) 16:41, 31 July 2026 (UTC)reply

    Reason: repeated POV edits whitewashing this organisation from a variety of probably linked new users, one of whom claimed to be an officer or employee of it. Morwen (talk) 14:41, 30 July 2026 (UTC)reply

    Temporary semi-protection: Persistent vandalism. Painting17 (talk) 14:45, 30 July 2026 (UTC)reply

    Temporary semi-protection: Persistent vandalism. In solidarity, Destinyokhiria (talk / cont) 15:54, 30 July 2026 (UTC)reply

    I think indef is the more appropriate option here; last protection was 3 years. Also, you should've contacted the last protecting admin (@Materialscientist:, who is still active) before writing here. Giovanni Potage (talk) 01:01, 31 July 2026 (UTC)reply

    Reason: Recent unsourced/disruptive edits from multiple temporary accounts within just the past few hours. Magitroopa (talk) 16:31, 30 July 2026 (UTC)reply

    Temporary semi-protection: For preventing the addition of unsourced, unreliable and unverifiable information on these pages like this:

    ~2026-42424-42 (talk) 16:41, 30 July 2026 (UTC)reply

    Semi-protection: Persistent disruptive editing – Repeated removal of content without explanation by various TAs.   –Skywatcher68 (talk) 17:09, 30 July 2026 (UTC)reply

    Reason: High level of biased and unsourced material repeatedly added Aboutnick (talk) 00:55, 31 July 2026 (UTC)reply

    Reason: Repeated vandalism Top5a (talk) 03:01, 31 July 2026 (UTC)reply

    Declined – Not enough recent disruptive activity to justify protection. Thus far the TAs have only made 3 edits spread out across 2 days. They share an IP range, so a block may be sufficient to end the disruption if it continues. Epicgenius (talk) 14:02, 31 July 2026 (UTC)reply

    Reason: Addition of unsourced content, and after it was reverted vandalism begun MathMan4 (talk) 05:21, 31 July 2026 (UTC)reply

    Reason: WP:RUSUKR IiSmxyzXX (talk) 09:40, 31 July 2026 (UTC)reply

    Reason: Disputed political motivated edits that could easily lead to edit war. . Bananakingler (talk) 10:44, 31 July 2026 (UTC)reply

    DeclinedPages are not protected preemptively. Favonian (talk) 11:33, 31 July 2026 (UTC)reply

    Reason: Persistent disruptive editing – Info repeatedly changed. Specifically, repeated changes contrary to MOS:FILMCAST, that common nouns within roles should not be in capitals. Masato.harada (talk) 11:15, 31 July 2026 (UTC)reply

    Temporary semi-protection: Persistent addition of unsourced or poorly sourced content – Maybe for at least around 7 days, the village is the location of an ongoing event. One temporary account has already made false claims regarding the incident. Fortek67 (talk) 11:51, 31 July 2026 (UTC)reply

    Extended confirmed protection: User is WMF banned so I can't see any reason why this page needs to be edited. --Prothe1st (leave me a message)-- 12:25, 31 July 2026 (UTC)reply

    I'd suggest indef full protection to match talk page. LuniZunie(talk) 15:33, 31 July 2026 (UTC)reply
    Fully protected indefinitely. — rsjaffe 🗣️ 15:37, 31 July 2026 (UTC)reply

    Temporary semi-protection: Persistent sockpuppetry – Persistent disruption from Alakmarsaify (WMF banned editor) socks - 3 different socks in the last 10 days have tried to make edits. Spiderone(Talk to Spider) 13:07, 31 July 2026 (UTC)reply

    Indefinite extended confirmed protection: Arbitration enforcement – [1], [2], [3], [4]. Should be ECP'ed if it falls under WP:CT/SA. Jeraxmoira🐉 (talk) 13:27, 31 July 2026 (UTC)reply

    Temporary semi-protection: Persistent vandalism – Multiple changes to the subject's race and name have been occurring for multiple days across multiple accounts. Page protection is needed to restore a more stable version. DonnieⓃⓄⓋⒶ (talk) 13:38, 31 July 2026 (UTC)reply

    Temporary semi-protection: Persistent disruptive editing – Continued disruption after previous protections expired. Painting17 (talk) 13:44, 31 July 2026 (UTC)reply

    Reason: Persistent and repeated edit wars and vandalism by temporary accounts declaring individual deceased when official confirmation has not been given Whynotlol2 (talk) 14:10, 31 July 2026 (UTC)reply

    Reason: Edit wars on unconfirmed death and removal of controversial sections in Personal Life Kamikazechaser (talk) 14:11, 31 July 2026 (UTC)reply

    Temporary semi-protection: Persistent disruptive editing. Kajmer05 (talk) 14:21, 31 July 2026 (UTC)reply

    Reason: Persistent disruptive editing by socks. Johnj1995 (talk) 15:10, 31 July 2026 (UTC)reply

    Current requests for reduction in protection level

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

    Reason: Like my last request, this is no longer needed as this was mostly used to prevent LTAs to moving the page to Grawp-like titles (e.g. H..A..G..G..E..R..?). This is how Grawp spells Hagrid's name in the Harry Potter and the Order of the Phoenix film from 2007. Because JarlaxleArtemis is an LTA that is no longer active, I recommend and suggest removing the protection or even a step further to removing the move protection of this page (extended confirmed would be okay for the Hagrid request). — SimpleObjects-9ei 🏖️/☀️/🥵 (see talk) 21:39, 27 July 2026 (UTC)reply

    (Non-administrator comment) Pinging protecting admin @Number 57. Entranced98 (talk) 17:15, 28 July 2026 (UTC)reply

    Unprotection: 8 years have passed since this should have been an issue, seeing how there's been no disruption basically on the other lists of deaths of Wikipedians by year in more recent years, unprotection should be okay. MakaylaHippo1998 (talk) 07:07, 31 July 2026 (UTC)reply

    See the instructions. You're supposed to contact the protecting admin before making a request here. In this case that admin is Oshwah, who is active today. ~Anachronist (who / me) (talk) 14:34, 31 July 2026 (UTC)reply

    This page is semi-protected for an indefinite period already. Is there still a reason why the page is pending-protected beyond this point?~2026-42571-72 (talk) 13:20, 31 July 2026 (UTC)reply

    Not done – Same reply as to your previous request regarding a different article. Favonian (talk) 13:30, 31 July 2026 (UTC)reply
    Then remove the PC and keep the SEMI in place.~2026-42571-72 (talk) 13:36, 31 July 2026 (UTC)reply
    You failed to read the instructions, which say you need to talk to the protecting admin. In any case, I have removed the overlapping protection and left it at indef-semi. ~Anachronist (who / me) (talk) 14:31, 31 July 2026 (UTC)reply

    Current requests for edits to a protected page

    Request a specific edit be made to a protected page


    Clarify this line. "As of December 2025, at least 70,117 people in Gaza had been killed,[35][17] with estimates ranging between at least 186,000 and 335,000 between June and the end of 2024"

    If lower bound of the estimate is "at least 186,000" I didn't understand why the same line says "at least 70,117" - surely it is one or the other? StupidLookingKid (talk) 12:21, 31 July 2026 (UTC)reply

    Apologies - link was broken https://en.wikipedia.org/wiki/Gaza_genocide StupidLookingKid (talk) 12:22, 31 July 2026 (UTC)reply
    The context seems to be direct versus indirect deaths. See Gaza genocide#Indirect deaths and citation 187. I agree this could be clarified. The numbers 70,117 and 335,000 appear only in the lead, which violates WP:LEAD because the lead should be an overview of the body text, not introduce information that isn't available anywhere else in the article. ~Anachronist (who / me) (talk) 13:19, 31 July 2026 (UTC)reply
    Not done for now, because I am not sure how to change it. I have started a discussion at Talk:Gaza genocide#Nonsense in the lead. ~Anachronist (who / me) (talk) 14:27, 31 July 2026 (UTC)reply
    Many thanks - just struck me as odd as I was doing random browsing StupidLookingKid (talk) 15:03, 31 July 2026 (UTC)reply

    Handled requests

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