Wikipedia:Requests for page protection
 | This page has an administrative backlog that requires the attention of willing administrators. Please replace this notice with {{no admin backlog}} when the backlog is cleared. |
| 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 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 | ||
|
2012 2013 2014 2015 2016 2017 2018 2019 2020 2021 2022 2023 2024 |
Current requests for increase in protection level
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.
Reason: Requesting temporary protection due to disruptive edit warring from COI editor. Encoded Talk 💬 20:29, 29 October 2024 (UTC)
Reason: High level of sock vandalism. GenoV84 (talk) 22:00, 29 October 2024 (UTC)
Already protected by administrator Ad Orientem. Ymblanter (talk) 09:25, 30 October 2024 (UTC)
Semi-protection: Persistent sockpuppetry – Sock-puppetry and disruptive editing. Done potentially by user Ntr123, Mohsin1970 and/or paid unregistered editors to read like advertisement. Mmnwla (talk) 23:59, 29 October 2024 (UTC)
- Sorry I meant to type user Ntrr123 and Mohsin1970, although I’m not sure it’s them. Regardless it looks like there's disruptive editing from unconfirmed and unregistered users so thought to be safe that it wouldn’t be a bad idea to suggest temporary semi-protection. Mmnwla (talk) 06:02, 30 October 2024 (UTC)
Reason: The regime in Iran executed Jamshid Sharmad based on coerced false confessions extracted under torture. Sharmad worked closely with the Tondar group, which the regime often seeks to discredit. The Islamic regime has a history of targeting and discrediting opposition figures and dissidents through misinformation campaigns, including the spread of false information on Wikipedia. Therefore, in cases like this, it is crucial to verify edits and consult with reliable sources. Specifically, Gazelle Sharmad, Jamshid Sharmad’s daughter, can help clarify issues and verify accurate information due to her firsthand knowledge.
This request for page protection is also based on similar incidents involving other members of the Iranian opposition, such as the page on Reza Pahlavi. The pages of opposition figures have been frequent targets of disinformation and bad-faith edits. Given these risks, it is essential to take proactive measures to maintain the integrity of this page. DavidSallam (talk) 00:00, 30 October 2024 (UTC)
- I don't see anything in the recent history that gives me cause for concern, not yet. Drmies (talk) 00:02, 30 October 2024 (UTC)
Reason: there is lots of POV pushing and brazen/large edits + rewrites without regard for ongoing discussion in the talk page
see:
https://en.wikipedia.org/w/index.php?title=Instant-runoff_voting&diff=prev&oldid=1254208089
https://en.wikipedia.org/w/index.php?title=Instant-runoff_voting&diff=prev&oldid=1254146037
https://en.wikipedia.org/w/index.php?title=Instant-runoff_voting&diff=prev&oldid=1254048805
https://en.wikipedia.org/w/index.php?title=Instant-runoff_voting&diff=prev&oldid=1253161951
https://en.wikipedia.org/w/index.php?title=Instant-runoff_voting&diff=prev&oldid=1252389457 Affinepplan (talk) 00:17, 30 October 2024 (UTC)
- No objections to temporary page-protect, if it's combined with opening something on WP:DRN. – Closed Limelike Curves (talk) 00:50, 30 October 2024 (UTC)
Indefinite extended confirmed protection: Arbitration enforcement – WP:CT/A-I. Aydoh8[contribs] 02:51, 30 October 2024 (UTC)
.svg/20px-Pictogram_voting_comment_(orange).svg.png)
Note: I moved the page, and changed the request accordingly. LilianaUwU (talk / contributions) 02:55, 30 October 2024 (UTC)
Temporary semi-protection: Persistent disruptive editing – Disruptive editing by IPs. Vestrian24Bio (TALK) 03:13, 30 October 2024 (UTC)
Temporary extended confirmed protection: Request ECP until after the election, say, 14 days. Increasing disruptive activity from non-extended-confirmed users. ―Mandruss ☎ 04:28, 30 October 2024 (UTC)
Not done. The current level disruption doesn't even rise to the point where semi-protection is warranted. Also, if we protected this talk page, new edit requests would just accumulate on WP:RFED and most of the disruptive comments would be posted somewhere else. Daniel Quinlan (talk) 05:09, 30 October 2024 (UTC)
Semi-protection: Persistent vandalism. Warm Regards, Miminity (Talk?) (me contribs) 05:43, 30 October 2024 (UTC)
Temporary semi-protection: Persistent vandalism – IP edit-warring to replace a TV channel with a production company. - Sumanuil. (talk to me) 06:03, 30 October 2024 (UTC)
Reason: Someone using the IP address 130.20.80.209 is persistently removing content from the page without making any actual edits. I believe placing the page under Extended Confirmed Protection could help mitigate this vandalism. Thank you. পেতনীপিসি (talk) 06:33, 30 October 2024 (UTC)
- @পেতনীপিসি I'm not an admin but this page is not for requesting protection from a single vandal. You should go to WP:AIV, and you should give at least 3 warnings on their talk page usually before reporting them. Also, semi-protection should be enough as it is just an IP. Tube·of·Light 08:44, 30 October 2024 (UTC)
Temporary extended confirmed protection: BLP policy violations. 𝙹𝚒𝚢𝚊𝚗 忌炎 (𝚃𝚊𝚕𝚔) 07:49, 30 October 2024 (UTC)
- The disruptive user has also been reported to AIV earlier by me and by the bot. They are also already WP:COMMUNICATE on the copyright violation images as per their talk page hence protecting the article may the best course of action to prevent the spawning of socks, in addition to blocking. — Paper9oll (🔔 • 📝) 07:58, 30 October 2024 (UTC)
Temporary semi-protection: Persistent vandalism – Vandals/promo-only accounts putting random phone numbers that seem to be spam on the page. Tube·of·Light 08:39, 30 October 2024 (UTC)
Temporary extended confirmed protection: BLP policy violations – Disruptive editing unsourced additions to a BLP by an IP user. Sciencefish (talk) 08:59, 30 October 2024 (UTC)
Reason: Vandalism by IP user/new account. I'd like us to be able to restore the non-vandalised text without an edit-war. Alarichall (talk) 09:01, 30 October 2024 (UTC)
Semi-protected for a period of 1 week, after which the page will be automatically unprotected. Ymblanter (talk) 09:25, 30 October 2024 (UTC)
Reason: Rash of new editors adding multiple copyvios and unsourced additions - may be some form of ill-organized class-project - Arjayay (talk) 09:28, 30 October 2024 (UTC)
Current requests for reduction in protection level
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.
Current requests for edits to a protected page
Please request an edit directly on the protected page's talk page before posting here
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.
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[1] 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)
- @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)
- 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)
- 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)
- 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)
- I've removed #2. But there does seem to be evidence that pro-Palestine protests have been banned in parts of Germany at times.[2][3][4].VR (Please ping on reply) 14:55, 16 October 2024 (UTC)
- Thank you. Maybe the following article gives a bit more clarity.[[5]] Gilbert04 (talk) 18:10, 16 October 2024 (UTC)
- Unfortunately that source seems incomplete. Germany has indeed suppressed peaceful criticism of Israel.[6] 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."[7] VR (Please ping on reply) 22:32, 16 October 2024 (UTC)
- Well, I do not think that any source will ever be complete. Let me add two more.[[8]][[9]] Gilbert04 (talk) 20:44, 17 October 2024 (UTC)
- Unfortunately that source seems incomplete. Germany has indeed suppressed peaceful criticism of Israel.[6] 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."[7] VR (Please ping on reply) 22:32, 16 October 2024 (UTC)
- Thank you. Maybe the following article gives a bit more clarity.[[5]] Gilbert04 (talk) 18:10, 16 October 2024 (UTC)
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)
- 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)
- @Ecco2kstan, how about: "The Israeli government rejected South Africa's allegations. Supporters of Israel say that accusing Israel of genocide is both antisemitic[10][11] and a form of Holocaust erasure[12], but others argue antisemitism shouldn't be exploited to shield Israel from such allegations.[13][14][15][16]".VR (Please ping on reply) 00:12, 16 October 2024 (UTC)
- 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)
- That does sound quite balanced. +1 from me. Neutral Editor 645 (talk) 18:02, 17 October 2024 (UTC)
- @Vice regent: Would you please make this change, so we can close this request? ~Anachronist (talk) 21:28, 24 October 2024 (UTC)
- @Ecco2kstan, how about: "The Israeli government rejected South Africa's allegations. Supporters of Israel say that accusing Israel of genocide is both antisemitic[10][11] and a form of Holocaust erasure[12], but others argue antisemitism shouldn't be exploited to shield Israel from such allegations.[13][14][15][16]".VR (Please ping on reply) 00:12, 16 October 2024 (UTC)
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)
Handled requests
A historical archive of previous protection requests can be found at Wikipedia:Requests for page protection/Archive.