Wikipedia:Requests for page protection: Difference between revisions
Banana19208 (talk | contribs) Requesting unprotection of Luca Padovan. (TW) |
Banana19208 (talk | contribs) Requesting extended confirmed of Israeli Jews. (TW) |
||
Line 243: | Line 243: | ||
'''Temporary semi-protection:''' [[WP:BLP|BLP]] policy violations – Various IPs are constantly adding " Gallacher received a two year driving ban" which has previously been removed as per ocnsensus on the talkpage and at DRN, It would seem the IPs are using this as some sort of smear campaign... Anyway could I ask that this is protected for a '''full year ''', Thanks,. –[[User:Davey2010|<span style="color: blue;">'''Davey'''</span><span style="color: orange;">'''2010'''</span>]]<sup>[[User talk:Davey2010|<span style="color: navy;">'''Talk'''</span>]]</sup> 13:31, 12 February 2019 (UTC) |
'''Temporary semi-protection:''' [[WP:BLP|BLP]] policy violations – Various IPs are constantly adding " Gallacher received a two year driving ban" which has previously been removed as per ocnsensus on the talkpage and at DRN, It would seem the IPs are using this as some sort of smear campaign... Anyway could I ask that this is protected for a '''full year ''', Thanks,. –[[User:Davey2010|<span style="color: blue;">'''Davey'''</span><span style="color: orange;">'''2010'''</span>]]<sup>[[User talk:Davey2010|<span style="color: navy;">'''Talk'''</span>]]</sup> 13:31, 12 February 2019 (UTC) |
||
=== [[:Israeli Jews]] === |
|||
* {{pagelinks|1=Israeli Jews}} |
|||
'''Indefinite extended confirmed:''' [[WP:30/500|Arbitration enforcement]] – This article about this religion that related to Arab–Israeli conflict. [[User:Banana19208|Banana19208]] ([[User talk:Banana19208|talk]]) 13:44, 12 February 2019 (UTC) |
|||
== Current requests for reduction in protection level == |
== Current requests for reduction in protection level == |
Revision as of 13:44, 12 February 2019
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.
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.
Semi-protection: Persistent vandalism – repeated BLP violations by IP editors. – Recoil16 (talk) 12:04, 7 November 2024 (UTC)
- Declined – Not enough recent disruptive activity to justify protection. Isabelle Belato 🏳🌈 12:20, 7 November 2024 (UTC)
Semi-protection: Vandalism and BLP violations after six previous protections. – Recoil16 (talk) 12:06, 7 November 2024 (UTC)
- Declined – Not enough recent disruptive activity to justify protection. Isabelle Belato 🏳🌈 12:18, 7 November 2024 (UTC)
Temporary semi-protection: Persistent vandalism. Mvcg66b3r (talk) 12:19, 7 November 2024 (UTC)
- Declined – Warn the user appropriately then report them to AIV or ANI if they continue. Lectonar (talk) 13:05, 7 November 2024 (UTC)
Indefinite create protection: Repeatedly recreated – Indefinite semi or ECP please. Joseph2302 (talk) 12:26, 7 November 2024 (UTC)
- Not done. Page has been recreated once. Added to my watchlist. Isabelle Belato 🏳🌈 12:34, 7 November 2024 (UTC)
Indefinite full protection: Recreation of the page from the redirect; should be salted. This page being recreated is a WP:CFORK of List of 2025 Indian Premier League personnel changes. Vestrian24Bio (TALK) 12:49, 7 November 2024 (UTC)
Semi-protection: Persistent vandalism. Myrealnamm's Alternate Account (talk) 15:35, 7 November 2024 (UTC)
- Automated comment: A request for protection/unprotection for one or more pages in this request was recently made, and was denied at some point within the last 8 days.—cyberbot ITalk to my owner:Online 15:42, 7 November 2024 (UTC)
- Pending-changes protected for a period of 1 month, after which the page will be automatically unprotected. Daniel Quinlan (talk) 15:56, 7 November 2024 (UTC)
Temporary semi-protection: BLP policy violations – IP hopper keeps adding death claim with no sourcing. – The Grid (talk) 16:06, 7 November 2024 (UTC)
Semi-protection: Persistent vandalism occurs in this page. In https://en.m.wikipedia.org/wiki/Special:MobileDiff/882851906, there is an edit written in Arabic letters by anonymous user. 197.156.77.80 (talk) 21:18, 11 February 2019 (UTC)
- Semi-protected for a period of 2 weeks, after which the page will be automatically unprotected. MelanieN (talk) 04:24, 12 February 2019 (UTC)
Semi-protection: Repeated unexplained reverts by multiple SPAs on BLP undoing changes to adapt article to MOS and remove redundant material. Long history of short-lived SPAs (e.g. Shougo2202, KilJosBouEphRne, Bahman27, 82.0.25.123, DMartinJ, J-Heart1, Mat-West) adding unsourced material and reverting removals of unsourced and poorly sourced material without explanation or discussion. — MarkH21 (talk) 19:32, 11 February 2019 (UTC)
- Declined – Warn the user appropriately then report them to AIV or ANI if they continue. ~Oshwah~(talk) (contribs) 19:46, 11 February 2019 (UTC)
- Oshwah: My impression is that the user makes a new SPA each time they decide to edit the page. I've left a message on J-Heart1's talk page before Mat-West was created and made the same edits. Perhaps would adding the article to pending changes be more appropriate than adding a warning to each new SPA? I think that this is more mis-informed possessive editing combined with refusal to communicate, rather than vandalism. — MarkH21 (talk) 20:43, 11 February 2019 (UTC)
- Repinging Oshwah Hhkohh (talk) 22:31, 11 February 2019 (UTC)
- MarkH21 - Are you saying that you believe that the user illegitimately operates and uses more than one account in violation of Wikipedia's sock puppetry policy? I'm just making sure that I understand your response and question clearly... ~Oshwah~(talk) (contribs) 22:41, 11 February 2019 (UTC)
- I suspect so. But of course, I cannot conclusively say so. I figured that adding protection to the page would encourage / force the user(s) to engage in discussion without having to explicitly determine or accuse anyone of sock-puppetry. — MarkH21 (talk) 23:01, 11 February 2019 (UTC)
- MarkH21 - Are you saying that you believe that the user illegitimately operates and uses more than one account in violation of Wikipedia's sock puppetry policy? I'm just making sure that I understand your response and question clearly... ~Oshwah~(talk) (contribs) 22:41, 11 February 2019 (UTC)
- Repinging Oshwah Hhkohh (talk) 22:31, 11 February 2019 (UTC)
- Oshwah: My impression is that the user makes a new SPA each time they decide to edit the page. I've left a message on J-Heart1's talk page before Mat-West was created and made the same edits. Perhaps would adding the article to pending changes be more appropriate than adding a warning to each new SPA? I think that this is more mis-informed possessive editing combined with refusal to communicate, rather than vandalism. — MarkH21 (talk) 20:43, 11 February 2019 (UTC)
The interactions make w feel a WP:SPI report might be in order. Looks like a fan club or student group. The anon is out of U of L. I'd be happy to semi the thing. Maybe I'll give them a agf-sock notice. Dlohcierekim (talk) 00:12, 12 February 2019 (UTC)
Semi-protection: Unsourced additions and vandalism. StaticVapor message me! 20:47, 11 February 2019 (UTC)
- Semi-protected for a period of 2 days, after which the page will be automatically unprotected. MelanieN (talk) 04:28, 12 February 2019 (UTC)
Indefinite extended confirmed: Persistent disruptive editing – Lets see if the IP will come to the talk or make an account that they MAY use to tlak to us. Moxy (talk) 23:38, 11 February 2019 (UTC)
- Declined When the problem is with a single user, we prefer to deal with that user rather than protect the page. I have issued them a final warning. If they do it again they should get a good long block since their block log shows a longstanding pattern of disruption. MelanieN (talk) 04:50, 12 February 2019 (UTC)
Indefinite semi-protection: Persistent vandalism. Zackmann (Talk to me/What I been doing) 00:03, 12 February 2019 (UTC)
- Semi-protected for a period of 1 week, after which the page will be automatically unprotected. Dlohcierekim (talk) 00:22, 12 February 2019 (UTC)
Temporary semi-protection: Persistent addition of unsourced or poorly sourced content – Not a large problem, but an IP from the same region as the company's headquarters continues to "update" the article, removing references and adding none in return. Extended confirmation might also make sense here. Walter Görlitz (talk) 00:04, 12 February 2019 (UTC)
- Semi-protected for a period of 1 week, after which the page will be automatically unprotected. Dlohcierekim (talk) 00:23, 12 February 2019 (UTC)
Temporary semi-protection: Persistent vandalism. Pedro H. (talk) 00:12, 12 February 2019 (UTC)
- Semi-protected for a period of 1 week, after which the page will be automatically unprotected. Dlohcierekim (talk) 00:25, 12 February 2019 (UTC)
- Pending-changes protected for a period of 3 months, after which the page will be automatically unprotected. Dlohcierekim (talk) 00:25, 12 February 2019 (UTC)
Indefinite full protection: Content dispute/edit warring – Rejs12345 (talk · contribs) continues to insist that this needs its own article, despite the fact that the car is merely a rebadge of the Dodge Journey with no differences. Areaseven (talk) 00:13, 12 February 2019 (UTC)
- Already protected by administrator Ymblanter. Dlohcierekim (talk) 04:33, 12 February 2019 (UTC)
- That protection expired yesterday. - Areaseven (talk) 08:20, 12 February 2019 (UTC)
- Dlohcierekim, not protected yet. Protection was expired on 1 February 2019 Hhkohh (talk) 09:26, 12 February 2019 (UTC)
- Semi-protected for a period of 2 more weeks, after which the page will be automatically unprotected. It expired yesterday. Lectonar (talk) 11:58, 12 February 2019 (UTC)
Temporary semi-protection: Persistent vandalism – There have been about 15 different IPs making some 50+ joke edits for the past 24 hours. – Þjarkur (talk) 00:13, 12 February 2019 (UTC)
Indefinite extended confirmed: Arbitration enforcement. Banana19208 (talk) 00:36, 12 February 2019 (UTC)
- Declined – No changes to the current protection level are required at this point in time. Almost no activity at the article for some time, also see your talk-page. Lectonar (talk) 08:00, 12 February 2019 (UTC)
Indefinite extended confirmed: Arbitration enforcement. Banana19208 (talk) 00:37, 12 February 2019 (UTC)
- Declined – No changes to the current protection level are required at this point in time. Also see above. Lectonar (talk) 08:01, 12 February 2019 (UTC)
Indefinite extended confirmed: Persistent sockpuppetry. hueman1 (talk) 00:40, 12 February 2019 (UTC)
- Extended confirmed protected Dlohcierekim (talk) 04:38, 12 February 2019 (UTC)
- User(s) blocked. Dlohcierekim (talk) 04:38, 12 February 2019 (UTC)
Temporary create protection: This article of a real person, that looks like minor age, but you set 6 months for protection temporarly. Banana19208 (talk) 01:03, 12 February 2019 (UTC)
- Declined – Pages are not protected preemptively. If the article is repeatedly recreated, then please report again. Mz7 (talk) 04:26, 12 February 2019 (UTC)
Temporary semi-protection: Persistent vandalism. HickoryOughtShirt?4 (talk) 01:50, 12 February 2019 (UTC)
Indefinite semi-protection: Persistent sockpuppetry. FilmandTVFan28 (talk) 02:18, 12 February 2019 (UTC)
Semi-protection: Persistent vandalism – IP hopping vandal attacking this page (see recent edit history). – Finnusertop (talk ⋅ contribs) 02:19, 12 February 2019 (UTC)
- Already protected by administrator Alexf. Dlohcierekim (talk) 04:42, 12 February 2019 (UTC)
Semi-protection: Persistent vandalism. ―Abelmoschus Esculentus (talk • contribs) 02:28, 12 February 2019 (UTC)
- Already protected by administrator Alexf. Mz7 (talk) 04:25, 12 February 2019 (UTC)
Semi-protection: Persistent sockpuppetry – Sockpuppets of User:Jeffman12345 are continuously vandalizing the page. Protected several times in the past. SkyGazer 512 Oh no, what did I do this time? 03:16, 12 February 2019 (UTC)
Semi-protection: Persistent vandalism by IP editors. —Locke Cole • t • c 03:57, 12 February 2019 (UTC)
Temporary semi-protection: Persistent disruptive editing – Anonymous IP editor removed the episode summary table with titles have given by reliable sources. ApprenticeFan work 04:37, 12 February 2019 (UTC)
- Declined – Content dispute. Please use the article's talk page or other forms of dispute resolution. Lectonar (talk) 08:14, 12 February 2019 (UTC)
- Lectonar: This IP editor (2600:1003:B85B:E4F7:C9CF:3791:6495:FEE8 (talk · contribs · WHOIS)) has removing the season summary includes episode title that meets the standard of reliable sources policy. I should've reported it at administrators' noticeboard/edit warring to stop the improper dispute. You should let to block the IP user before the continuous IP disruption. ApprenticeFan work 09:02, 12 February 2019 (UTC)
- @ApprenticeFan:...then the right venue would be the edit-warring noticeboard or a report to AIV; protecting a page to keep off one IP is a bit heavy-handed. Lectonar (talk) 11:15, 12 February 2019 (UTC)
- @Lectonar:... this IP editor can't stopped that the reversions are good, basically the IP address got a final warning to engage a three-revert rule edit warring. This should be giving a matter of solution for a temporary semi-protection. ApprenticeFan work 12:56, 12 February 2019 (UTC)
Temporary semi-protection: Recent pattern of IP vands such as BLP violations, introduction of irrelevant images. Dl2000 (talk) 04:48, 12 February 2019 (UTC)
- Declined – No changes to the current protection level are required at this point in time. A little spike yesterday. Lectonar (talk) 08:15, 12 February 2019 (UTC)
Temporary semi-protection: Persistent vandalism – Persistent IP Vandalism. Everythingness (talk) 05:25, 12 February 2019 (UTC)
- Semi-protected for a period of 1 week, after which the page will be automatically unprotected. Samsara 10:42, 12 February 2019 (UTC)
Temporary semi-protection: Persistent vandalism – Persistent IP edit warring/uncited edits. Davidelit (Talk) 07:02, 12 February 2019 (UTC)
- Semi-protected for a period of 2 weeks, after which the page will be automatically unprotected. Samsara 10:44, 12 February 2019 (UTC)
Indefinite extended confirmed: Persistent disruptive editing – Lots of dynamic IP vandalism which isn't setting up. Continously being edited by confirmed/autoconfirmed users in wrong and false ways, to convey inaccurate and obscene information. Justlookingforthemoment (talk) 08:13, 12 February 2019 (UTC)
- Declined – Not enough recent disruptive activity to justify protection. Samsara 11:01, 12 February 2019 (UTC)
Temporary semi-protection: Persistent vandalism. HickoryOughtShirt?4 (talk) 08:30, 12 February 2019 (UTC)
- Semi-protected for a period of 3 days, after which the page will be automatically unprotected. Samsara 11:02, 12 February 2019 (UTC)
Semi-protection: vandalism by IP and new users after the end of the last protection (three days ago), please watch this--Luke Stark 96 (talk) 08:59, 12 February 2019 (UTC)
- @Luke Stark 96: Hi Luke, I noticed that pending changes was enabled on this article and wanted to make sure you know what that does, as many users may not be aware of it. You can see that it's active by a different appearance of entries in the editing history - usually the "good" edits appear in blue. What it also means is that edits from IP and new users get held in a queue and will not be visible to the public until a more experienced user, like you or I, accepts them. So when pending changes is enabled, it doesn't matter whether you are online and revert the change immediately, you can just revert it when you next log in, and nothing bad will happen in the meantime. Does that help? Samsara 10:50, 12 February 2019 (UTC)
- Yes it helps, I forgot the "pending changes", sorry. Thank you for the explanation @Samsara:--Luke Stark 96 (talk) 11:06, 12 February 2019 (UTC)
- Withdrawn by requestor Samsara 11:18, 12 February 2019 (UTC)
Indefinite semi-protection: Persistent sockpuppetry. FilmandTVFan28 (talk) 09:05, 12 February 2019 (UTC)
- Just yesterday, there were some edits from an IP that were apparently considered good, so for now:
- Declined – Likely collateral damage as one or several users who are making improvements would be affected by the requested protection. Samsara 10:59, 12 February 2019 (UTC)
Indefinite extended-confirmed protection: Arbitration enforcement; article is related to the Israeli–Palestinian conflict --Kingerikthesecond (talk) 09:05, 12 February 2019 (UTC)
- Extended confirmed protected indefinitely. Samsara 10:52, 12 February 2019 (UTC)
Semi-protection: Vandalism and unsourced changes to a BLP by IP editors. StaticVapor message me! 09:51, 12 February 2019 (UTC)
- Semi-protected for a period of 3 days, after which the page will be automatically unprotected. Lectonar (talk) 11:16, 12 February 2019 (UTC)
- Longest recorded sniper kills (edit | talk | history | links | watch | logs)
Semi protect (temporary/long term) - persistent vandalism and BLP violations by multiple fly-by IP users from disparate regions of the world. - wolf 11:03, 12 February 2019 (UTC)
Temporary semi-protection: Persistent vandalism – Persistent vandalism by LTA. Requesting PP as soon as possible as per Bidhan Singh vandalizer . Fylindfotberserk (talk) 11:41, 12 February 2019 (UTC)
- Semi-protected for a period of 1 week, after which the page will be automatically unprotected. Samsara 11:52, 12 February 2019 (UTC)
Temporary semi-protection: Persistent vandalism – Requesting PP as soon as possible as per Bidhan Singh vandalizer . Fylindfotberserk (talk) 11:43, 12 February 2019 (UTC)
Temporary semi-protection: Persistent vandalism – Requesting PP as soon as possible as per Bidhan Singh vandalizer. Fylindfotberserk (talk) 11:43, 12 February 2019 (UTC)
Semi-protection: Persistent vandalism – Vand. by I.P. s. Sairg (talk) 11:48, 12 February 2019 (UTC)
- Declined – No changes to the current protection level are required at this point in time. Last disruptive edit more than 1 week ago. Lectonar (talk) 12:07, 12 February 2019 (UTC)
Temporary semi-protection: Persistent vandalism – Requesting PP as soon as possible as per Bidhan Singh vandalizer. Fylindfotberserk (talk) 12:12, 12 February 2019 (UTC)
Temporary semi-protection: Persistent vandalism – by new users and multiple IPs. theinstantmatrix (talk) 12:43, 12 February 2019 (UTC)
Temporary semi-protection: Persistent vandalism by multiple IPs. Mvcg66b3r (talk) 12:49, 12 February 2019 (UTC)
Temporary semi-protection: BLP policy violations – Various IPs are constantly adding " Gallacher received a two year driving ban" which has previously been removed as per ocnsensus on the talkpage and at DRN, It would seem the IPs are using this as some sort of smear campaign... Anyway could I ask that this is protected for a full year , Thanks,. –Davey2010Talk 13:31, 12 February 2019 (UTC)
Indefinite extended confirmed: Arbitration enforcement – This article about this religion that related to Arab–Israeli conflict. Banana19208 (talk) 13:44, 12 February 2019 (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.
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.
Unprotection: Make a redirect of a Netflix's You actor. Banana19208 (talk) 13:35, 12 February 2019 (UTC)
Current requests for edits to a protected page
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.
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)
- 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)
- @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)
Create a level 3 header with a link to the article in question, then a {{Pagelinks}} template and then the reason. It looks like this:
Example (edit | talk | history | links | watch | logs) your request here. ~~~~
Multiple protected user talk archives
- User talk:Future Perfect at Sunrise/Archive 1 (edit | subject | history | links | watch | logs)
- User talk:Future Perfect at Sunrise/Archive 7 (edit | subject | history | links | watch | logs)
- User talk:Future Perfect at Sunrise/Archive 8 (edit | subject | history | links | watch | logs)
- User talk:EncycloPetey/Archive 3 (edit | subject | history | links | watch | logs)
- Substitute the deprecated {{polytonic}} template, replacing it with
{{lang|grc|...}}
. (Courtesy ping: Future Perfect at Sunrise, EncycloPetey) {{3x|p}}ery (talk) 20:04, 8 February 2019 (UTC)- But the template was deprecated - but not deleted -
explicitlysothatthis type of edit doesn't need to be made to 75 old talk pages. --Floquenbeam (talk) 20:10, 8 February 2019 (UTC)- I had thought that the template wasn't deleted so as to not break old revisions, like the analogous {{Unicode}} {{3x|p}}ery (talk) 20:35, 8 February 2019 (UTC)
- You're right, that was the reason for the deprecation (I struck a little of my original comment). but because it's deprecated, it's still true that we don't need to make the +/- 75 edits to various talk pages that still use it. IMHO, of course; another admin may disagree and I'm happy to be overruled if I'm wrong. --Floquenbeam (talk) 20:57, 8 February 2019 (UTC)
- I had thought that the template wasn't deleted so as to not break old revisions, like the analogous {{Unicode}} {{3x|p}}ery (talk) 20:35, 8 February 2019 (UTC)
- But the template was deprecated - but not deleted -
Handled requests
A rolling archive of the last seven days of protection requests can be found at Wikipedia:Requests for page protection/Rolling archive.