Jump to content

Wikipedia:Requests for page protection

Page semi-protected
From Wikipedia, the free encyclopedia
"WP:RFP" and "WP:RPP" redirect here. You may also be looking for Wikipedia:Requests for permissions, Wikipedia:Requesting copyright permission, or Wikipedia:Random page patrol.
    Welcome—request protection of a page, file, or template here.
    Shortcuts

    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 get rid of obvious vandalism.

    Request protection of a page, or increasing the protection level
    Request unprotection of a page, or reducing the protection level
    Request a specific edit to a protected page
    Please request an edit directly on the protected page's talk page before posting here
    this header: view • edit



    Current requests for increase in protection level

    Request protection of a page, or increasing the protection level
    Shortcuts

    Place requests for new or upgrading pending changes, semi-protection, full protection, move protection, create protection, template editor protection, or upload protection at the BOTTOM of this section. Check the archive of fulfilled and denied requests or, failing that, the page history if you cannot find your request. Only recently answered requests are still listed here.


    Palestinian Authority–West Bank militias conflict

    Extended-confirmed protection: Arbitration enforcement per WP:ECR. Left guide (talk) 20:23, 8 November 2024 (UTC)[reply]

    WWE Women's United States Championship

    Reason: Requesting indefinite semi-protection IP users making disruptive edits. [1] [2] [3] [4] If any more proof is needed, please let me know in the reply below. Lemonademan22 (talk) 13:48, 9 November 2024 (UTC)[reply]

    Blumhouse Productions

    Temporary semi-protection: Persistent vandalism – Frequent vandalism since 13:37, 30 October 2024, adding the same unsourced commentary each time. Alith Anar 14:37, 9 November 2024 (UTC)[reply]

    List of Universal Pictures films (2020–2029)

    Reason: Anonymous users added films that Universal Pictures did not acquire or announce, including Everything I Never Did, which does not have a distributor yet. The Media Expert (talk) 16:26, 9 November 2024 (UTC)[reply]

    Kshatriya

    Temporary full protection: Content dispute/edit warring – There has been discussion on the status of Rajputs which is affecting related pages and this page is one such page. So, to avoid edit warring by EC accounts, full protection is needed. Adamantine123 (talk) 16:26, 9 November 2024 (UTC)[reply]

    Joker: Folie à Deux

    Temporary semi-protection: Persistent vandalism. soetermans. ↑↑↓↓←→←→ B A TALK 16:58, 9 November 2024 (UTC)[reply]

    Bhavya Gowda

    Reason: The article has been subject to persistent vandalism and edit wars, disrupting its credibility and integrity. Over the past few weeks, there have been multiple instances of users making inaccurate or biased edits, often with the intent to mislead or promote specific agendas. These edits have included the addition of false information, removal of cited content, and insertion of defamatory or promotional material.

    Despite reverting these changes and issuing warnings to the involved editors, the behavior has continued, often from anonymous IP addresses or newly created accounts. This persistent activity negatively impacts the reliability of the article and misleads readers.

    Additionally, the topic of the page has garnered significant public attention recently, making it a target for repeated edits driven by media narratives, personal biases, or coordinated efforts to skew public perception. Given the high traffic to this page and the recurring nature of these disruptions, semi-protection or full protection is necessary to ensure only constructive, verified contributions are made.

    Protecting this page will:

    Prevent further disruption and maintain the accuracy of the content. Allow editors to focus on improving the article rather than reverting repeated vandalism. Uphold Wikipedia’s standards for neutrality and reliability. Given these challenges, I request that the page be protected for a specified period to mitigate ongoing issues and provide a stable version for readers. Sohailnm (talk) 17:16, 9 November 2024 (UTC)[reply]

    Nashville, Tennessee

    Reason: IP hopper has repeatedly vandalized Nashville, Tennessee by changing the mayor's name from Freddie O'Connell to Leon Draisaitl, a player for the Edmonton Oilers. This has been happening since at least November 2, 2022, so can somebody give Nashville semi-protection? King airaglub (talk) 17:35, 9 November 2024 (UTC)[reply]

    Pending-changes protected for a period of 6 months, after which the page will be automatically unprotected. GoodnightmushTalk 17:48, 9 November 2024 (UTC)[reply]

    2025 ICC Champions Trophy

    Reason: Persistent disruptive editing. Chanaka L (talk) 17:53, 9 November 2024 (UTC)[reply]

    Hatsune Miku

    Reason: Persistent disruptive editing. Problems restarted after a year's semi-protection and virtually all edits from IPs and new accounts since then have not been constructive. Protection log shows issues going back years - perhaps a case for long-term pending changes? Entranced98 (talk) 18:09, 9 November 2024 (UTC)[reply]

    Prithvi

    Reason: Persistent IP vandalism, removal of sourced content and claim of "good faith". Seems to be done by a same person using diff ipsSeyamar💬📜 19:05, 9 November 2024 (UTC)[reply]

    Current requests for reduction in protection level

    Request unprotection of a page, or reducing the protection level
    Shortcuts

    Before posting, first discuss with the protecting admin at their talk page. Post below only if you receive no reply.

    • To find out the username of the admin who protected the page click on "history" at the top of the page, then click on "View logs for this page" which is under the title of the page. The protecting admin is the username in blue before the words "protected", "changed protection level" or "pending changes". If there are a number of entries on the log page, you might find it easier to select "Protection log" or "Pending changes log" from the dropdown menu in the blue box.
    • Requests to downgrade full protection to template protection on templates and modules can be directed straight here; you do not need to ask the protecting admin first.
    • Requests for removing create protection on redlinked articles are generally assisted by having a draft version of the intended article prepared beforehand.
    • If you want to make spelling corrections or add uncontroversial information to a protected page please add {{Edit fully-protected}} to the article's talk page, along with an explanation of what you want to add to the page. If the talk page is protected please use the section below.

    Check the archives if you cannot find your request. Only recently answered requests are still listed here.

    Shortcuts

    Timothy Hollingsworth

    Reason: Poor administration Billygoats1234 (talk) 21:44, 8 November 2024 (UTC)[reply]

    NB: this page was protected in response to this user's editing and a possible undeclared COI. AntiDionysius (talk) 21:47, 8 November 2024 (UTC)[reply]
    Declined Per above. Pickersgill-Cunliffe (talk) 17:43, 9 November 2024 (UTC)[reply]

    Mark Dice

    Reason: A permanent extended-confirmed protection is complete overkill, autoconfirmed should be enough, this article barely gets edited anymore--FMSky (talk) 04:32, 9 November 2024 (UTC)[reply]

    Note: It's not overkill if the disruption was coming from auto-confirmed accounts, which it was in this case per the protection log.-- Ponyobons mots 18:14, 9 November 2024 (UTC)[reply]

    Amsterdam 2024 attack

    Reason: This article contains faulty information! 2601:589:5080:9AC:99C0:C547:6D0F:65E5 (talk) 17:34, 9 November 2024 (UTC)[reply]

    Declined The article (November 2024 Amsterdam attacks) is protected under WP:ARBPIA. Please make an edit request if you wish content to be changed. Pickersgill-Cunliffe (talk) 17:42, 9 November 2024 (UTC)[reply]

    Current requests for edits to a protected page

    Request a specific edit to a protected page
    Please request an edit directly on the protected page's talk page before posting here
    Shortcut

    Ideally, requests should be made on the article talk page rather than here.

    • Unless the talk page itself is protected, you may instead add the appropriate template among {{Edit protected}}, {{Edit template-protected}}, {{Edit extended-protected}}, or {{Edit semi-protected}} to the article's talk page if you would like to make a change rather than requesting it here. Doing so will automatically place the page in the appropriate category for the request to be reviewed.
    • Where requests are made due to the editor having a conflict of interest (COI; see Wikipedia:Suggestions for COI compliance), the {{Edit COI}} template should be used.
    • Requests to move move-protected pages should be made at Wikipedia:Requested moves, not here.
    • If the discussion page and the article are both protected preventing you from making an edit request, this page is the right place to make that request. Please see the top of this page for instructions on how to post requests.
    • This page is not for continuing or starting discussions regarding content should both an article and its discussion page be protected. Please make a request only if you have a specific edit you wish to make.
    Further information: Wikipedia:Edit requests


    Gaza genocide

    My suggestion is to leave out the following 2 sentences in the "German complicity" paragraph as they seem to be based on misunderstandings:

    "She also highlighted police suppression of pro-Palestine protests throughout Germany[509] as evidence of state complicity.[508] Karen Wells et al. highlight how Germany has entrenched its complicity in Israel's actions by banning use of the word "genocide" in reference to Israel.[471][better source needed]"

    1. In general violent protests are not allowed in Germany. As some of the first pro-Palestine protests were violent, they were sometimes forbidden by courts, if they were expected to turn violent. But that is common policy in Gemany with all subjects and not special for pro-Palestine protests.

    Meanwhile, there even is a calendar concerning pro-Palestinian protests[5] with daily up to 20 protests all over Germany. Thus, there is no general police suppression of pro-Palestine protests as is suggested by the current wording.

    2. The word “genocide” is not banned in reference to Israel in Germany - maybe that was a misunderstanding: What is not allowed in Germany is to call for genocide against Jews. The slogan “From the river to the sea” is seen as such call and banned. Gilbert04 (talk) 15:34, 11 October 2024 (UTC)[reply]

    @FortunateSons: A quick browse shows at least for the first part support for removal, can you add any additional incite? -- Cdjp1 (talk) 12:38, 16 October 2024 (UTC)[reply]
    I can confirm that both statements are broadly true. IMO, the best resource for this discussion (in the contemporary context) is probably Steinberg: Versammlungsfreiheit nach dem 7. Oktober - NVwZ 2024, 302. Direct citation: “Die Subsumtion unter diesen Tatbestand bereitet aber auch sonst Probleme. Die Stadt Frankfurt a. M. hatte dem Anmelder einer Versammlung „Frieden in Nahost" am 2.12.2023 untersagt, während der Versammlung zur Vernichtung Israels aufzurufen, dem Staat Israel das Existenzrecht abzusprechen, sowie die Aussagen „Israel Kindermörder", „Juden Kindermörder", „Israel bringt Kinder um" sowie „From the river to the sea" zu tätigen. Diese Beschränkungen hob das VG Frankfurt vollständig auf. Auf die Beschwerde der Stadt differenzierte der VGH Kassel Aufrufe zur Vernichtung Israels verstießen - wie gesagt - gegen § 111 StGB und die Aussage „Juden Kindermörder" erfülle den Tatbestand der Volksverhetzung (§ 130 StGB). Demgegenüber wurden andere Außerungen wie „Kindermörder Israel" oder die Bezeichnung der israelischen Militäroperationen in Gaza als „Genozid" nicht beanstandet und die Entscheidung des VG insoweit aufrechterhalten. Es sei davon auszugehen, dass bei den militärischen Verteidigungshandlungen Israels auch Kinder zu Schaden kämen. Eine solche laienhafte Zuspitzung sei im Rahmen der Meinungsfreiheit hinzunehmen. Anders hatte der VGH Mannheim am 21.10.2023 ein Verbot der Parole „Israel Kindermörder" und „Israel bringt Kinder um" durch die Versammlungsbehörde trotz bestehender Zweifel über deren Strafbarkeit aufrechterhalten; im Verfahren des vorläufigen Rechtsschutzes sei nur eine summarische Prüfung möglich; eine einmal getätigte Äußerung könne nicht rückgängig gemacht werden. Die Unterscheidung zwischen antisemitisch und antiisraelisch stellt sicherlich eine Gratwanderung dar, die hier im Einzelnen nicht beschrieben werden kann“autotranslated: “However, the subsumption under this offense also causes other problems. On December 2, 2023, the city of Frankfurt am Main had prohibited the person registering a meeting "Peace in the Middle East" from calling for the destruction of Israel during the meeting, from denying the State of Israel the right to exist, and from making the statements "Israel, child murderer," "Jews, child murderer," "Israel kills children" and "From the river to the sea." The Administrative Court of Frankfurt completely lifted these restrictions. In response to the city's complaint, the Administrative Court of Kassel differentiated that calls for the destruction of Israel violated - as mentioned - Section 111 of the Criminal Code and that the statement "Jews, child murderer" constituted incitement to hatred (Section 130 of the Criminal Code). In contrast, other statements such as "Israel, child murderer" or the description of Israeli military operations in Gaza as "genocide" were not objected to and the Administrative Court's decision was upheld in this respect. It can be assumed that children would also be harmed in Israel's military defense actions. Such a lay exaggeration must be accepted within the framework of freedom of expression. On October 21, 2023, the Mannheim Higher Administrative Court upheld a ban on the slogans "Israel, child murderer" and "Israel kills children" by the assembly authority despite existing doubts about their criminal liability; in the interim legal protection procedure, only a summary examination is possible; a statement once made cannot be reversed. The distinction between anti-Semitic and anti-Israeli is certainly a balancing act that cannot be described in detail here.” There is no broad ban on pro-Palestinian protests either, and they were even allowed to happen on Oct. 7 of this year (in some cases). While there are legal disputes on specifics for both, I’m pretty confident that no reasonable person would disagree with “broadly permitted” regarding both claims. FortunateSons (talk) 16:54, 21 October 2024 (UTC)[reply]
    Bonus: there can be cases where something isn’t criminal, but can be restricted in other ways, for example due to different burdens of proof or social pressures. FortunateSons (talk) 17:11, 21 October 2024 (UTC)[reply]
    I've removed #2. But there does seem to be evidence that pro-Palestine protests have been banned in parts of Germany at times.[6][7][8].VR (Please ping on reply) 14:55, 16 October 2024 (UTC)[reply]
    Thank you. Maybe the following article gives a bit more clarity.[[9]] Gilbert04 (talk) 18:10, 16 October 2024 (UTC)[reply]
    Unfortunately that source seems incomplete. Germany has indeed suppressed peaceful criticism of Israel.[10] And Washington Post says "A planned photo exhibit in southwestern Germany was canceled as a result of social media posts by its curator, including one describing “genocide” in Gaza."[11] VR (Please ping on reply) 22:32, 16 October 2024 (UTC)[reply]
    Well, I do not think that any source will ever be complete. Let me add two more.[[12]][[13]] Gilbert04 (talk) 20:44, 17 October 2024 (UTC)[reply]

    Gaza genocide 2

    Consider changing "The Israeli government rejected South Africa's allegations, and accused the court of being antisemitic, which it often does when criticised" to "The Israeli government has been accused of consistently weaponizing antisemitism against it's critics, including in the ICJ ruling." Ecco2kstan (talk) 23:12, 13 October 2024 (UTC)[reply]

    The Weaponization of antisemitism page hyperlinked over "often done" has many sources to draw from regarding the accusations' consistency and nature.
    My main concern with the original text is that it's voiced as if it's an observation made by a Wikipedian. The benefit here is that the weaponization of antisemitism has a clearer consistency grounded outside of Wikipedia. Perhaps other ways to word this out include adding a time scale (increasingly accused since Oct. 7th) or specifying the critique (against critiques of their actions since Oct 7th).
    If a lead paragraph change is necessary, there may be reason to outline Israeli motives and conditions for the genocide, including Zionism and anti-Arab racism. Ecco2kstan (talk) 23:25, 13 October 2024 (UTC)[reply]
    @Ecco2kstan, how about: "The Israeli government rejected South Africa's allegations. Supporters of Israel say that accusing Israel of genocide is both antisemitic[14][15] and a form of Holocaust erasure[16], but others argue antisemitism shouldn't be exploited to shield Israel from such allegations.[17][18][19][20]".VR (Please ping on reply) 00:12, 16 October 2024 (UTC)[reply]
    I'm not as familiar with the Holocaust erasure claims, but I'm happy with that reworking! If that weaponization of Holocaust denial detail isn't on the weaponization of antisemitism page already, it might be a worthwhile phenomenon incorporate if there's more citations you can find. I might look into it myself. Thanks! Ecco2kstan (talk) 03:10, 16 October 2024 (UTC)[reply]
    That does sound quite balanced. +1 from me. Neutral Editor 645 (talk) 18:02, 17 October 2024 (UTC)[reply]
    @Vice regent: Would you please make this change, so we can close this request? ~Anachronist (talk) 21:28, 24 October 2024 (UTC)[reply]
    The text I originally wanted modified was changed to "Israel's supporters say that accusing Israel of genocide is antisemitic, but others argue antisemitism should not be exploited to shield Israel from such allegations" after other discussions on the talk page. I almost like it better, but by saying "Israel's supporters" it relieves some of the responsibility from the Israeli government in the accusations that was, to an extent, duly credited in the original modification. Maybe now, it should just say "The Israeli government and their supporters say that accusing the state for genocide antisemitic..." or something similar. Ecco2kstan (talk) 17:39, 5 November 2024 (UTC)[reply]

    Israel–Hamas war

    Stated Israeli tank losses in casualty and losses infobox are incorrect, attributed article from Business Insider states "The IDF again had problems with anti-tank missiles during the 2006 war in Lebanon, when Hezbollah employed Russian-made Kornets. Though about 50 Merkavas were damaged, only five were destroyed, according to the IDF, which also struggled with poorly maintained vehicles and ill-trained crews." Casualties and losses box states this number as if it was from current conflict. Article does, however, state that "Israel has lost nearly two dozen tanks during fighting with Hamas since October 7." I believe losses of tanks in the infobox should be fixed to reflect this. 155.225.2.98 (talk) 14:17, 29 October 2024 (UTC)[reply]

    Gaza genocide

    The 70% figure in both the primary and the secondary source refers to the deaths that were verified by the UN Human Rights Office, not the totality of deaths in Gaza.

    Accordingly, the current phrasing "70% of Palestinian deaths in Gaza are women and children" is inaccurate and should be changed to "70% of the 8,119 verified deaths were women and children" Zlmark (talk) 06:10, 9 November 2024 (UTC)[reply]

    List of highest-grossing Indian films

    in the content, higehst grossing franchises, rank 4 (Cop Universe), in that one, the movie Singham Returns (2014) is highlighted in green which indicates it is a recent movie, but actually the movie Singham Again (2024) should be highlighted in green because unlike Singham Returns, it is a recent movie, it has wrongly been marked, kindly correct it. Thanks :) Zev the Editor (talk) 16:21, 9 November 2024 (UTC)[reply]

    Handled requests

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

    Retrieved from "https://en.wikipedia.org/w/index.php?title=Wikipedia:Requests_for_page_protection&oldid=1255834873"