User:Excirial/Dashboard


Excirial
   
  Userpage Talk Awards E-Mail Dashboard Programs Sandbox Sketchbook Blocknote  
 
Admin Dashboard

User:Xenocidic/dashboard/users

4 Normal
3.58 RPM according to EnterpriseyBot 13:10, 7 November 2024 (UTC) edit

User:Xenocidic/dashboard/users

Immediate requests Entries
Candidates for speedy deletion as attack pages 0
Wikipedians looking for help 0
Requests for unblock 100
Wikipedia fully protected edit requests 6
Candidates for speedy deletion as copyright violations 1
Candidates for speedy deletion 9

Purge the cache of this page

Reports

[edit]

User-reported

[edit]


The following articles and files have been proposed for deletion for around 7 days:
Deletion backlog

Wikipedia files with unknown source – No backlog currently
Wikipedia files with unknown copyright status – No backlog currently
Wikipedia files missing permission – No backlog currently
Wikipedia files with no non-free use rationale – No backlog currently
Disputed non-free Wikipedia files – No backlog currently
Orphaned non-free use Wikipedia files – No backlog currently
Replaceable non-free use Wikipedia files – No backlog currently

Wikipedia files with a different name on Wikimedia Commons – No backlog currently

Wikipedia files with the same name on Wikimedia Commons – 31 items

Non-free files with orphaned versions more than 7 days old needing human review – 14 items

Requested RD1 redactions – 3 items

Proposed deletion – No backlog currently



Usernames for administrator attention


User-reported

[edit]
Requests for page protection


Current requests for increase in protection level

[edit]
Request protection of a page, or increasing the 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: hello recently i edited this page some admistrator reverted my edit.. i provide all sources and refrences request you inhance page proctection Botox.neet (talk) 09:28, 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 09:40, 7 November 2024 (UTC)
Declined – Content dispute. Please use the article's talk page or other forms of dispute resolution. Substantive edits need to be reliably sourced, or they will not stand. Lectonar (talk) 09:45, 7 November 2024 (UTC)

Reason: Continued disruption from disconnected IP addresses, requesting temporary protection. -- LCU ActivelyDisinterested «@» °∆t° 11:58, 7 November 2024 (UTC)

Semi-protected for a period of 3 days, after which the page will be automatically unprotected. GoodnightmushTalk 12:46, 7 November 2024 (UTC)

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)

DeclinedWarn 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)

Temporary semi-protection: Persistent vandalism – Vandalism from IPs and new users. My Pants Metal (talk) 13:05, 7 November 2024 (UTC)

Current requests for reduction in protection level

[edit]
Request unprotection of a page, or reducing the 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

[edit]
Request a specific edit 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'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)

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)

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

[edit]

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

Protected edit requests

14 protected edit requests
v·h
Page Tagged since Protection level Last protection log entry
Template:In string (request) 2024-09-03 23:19 Cascade-protected from Wikipedia:Cascade-protected items/Main Page/5 (log) Protected by Mifter on 2017-03-25: "Considering the main page was unprotected by a compromised sysop semi recently, perhaps transcluding it to a cascade protected page will provide a small increase in protection"
MediaWiki:Cascadeprotected (request) 2024-10-08 20:04 MediaWiki page (log)
MediaWiki:Noarticletext-nopermission (request) 2024-10-08 20:04 MediaWiki page (log)
MediaWiki:Protectedpagetext (request) 2024-10-08 20:04 MediaWiki page (log)
MediaWiki:Titleblacklist-custom-editnotice (request) 2024-10-08 20:04 MediaWiki page (log)
Template:Editnotice load (request) 2024-10-08 20:04 Cascade-protected from Wikipedia:Cascade-protected items/content (log) From Wikipedia/Protected templates: Protected by Rich Farmbrough on 2009-10-14: "Purpose of page - belt and braces."
Template:Editnotice load/notext (request) 2024-10-08 20:04 Cascade-protected from Wikipedia:Cascade-protected items/content (log) From Wikipedia/Protected templates: Protected by Rich Farmbrough on 2009-10-14: "Purpose of page - belt and braces."
Template:Editnotice/notice (request) 2024-10-08 20:04 Template-protected (log) Modified by Callanecc on 2014-02-14: "Highly visible template: and included in a high-risk template"
Template:Editnotices/Group/Template:Editnotices (request) 2024-10-08 20:04 Title blacklist (log) Matching line: Template:Editnotices\/.* <noedit|errmsg=titleblacklist-custom-editnotice>
MediaWiki:Titleblacklist (request) 2024-10-09 18:48 MediaWiki page (log)
MediaWiki:Bad image list (request) 2024-10-29 04:22 MediaWiki page (log) Protected by Redwolf24 on 2005-10-23: "Like all pages in the MediaWiki: space"
Module:Separated entries (request) 2024-10-29 12:19 Fully protected (log) Modified by Amorymeltzer on 2018-12-17: "High-risk Lua module: Over 2M transclusions"
User:AmandaNP/UAA/Similar (request) 2024-11-02 08:11 Fully protected (log) From User:DeltaQuad/UAA/Similar: Protected by AmandaNP on 2011-05-31: "User request within own user space"
Template:CatAutoTOC (request) 2024-11-05 21:08 Fully protected (log) Protected by Xaosflux on 2023-12-07: "High-risk template or module"
Updated as needed. Last updated: 00:30, 7 November 2024 (UTC)
8 template-protected edit requests
v·h
Page Tagged since Protection level Last protection log entry
Module:Lang-zh (request) 2024-10-10 09:41 Template-protected (log) From Module:Zh: Protected by HJ Mitchell on 2014-05-03: "High-risk Lua module"
Template:Coat of arms (request) 2024-10-30 09:36 Template-protected (log) Modified by Primefac on 2020-08-29: "High-risk template"
Template:Canada province decade category (request) 2024-11-05 18:40 Template-protected (log) From Template:DecadecatCanadaprovince: Protected by BrownHairedGirl on 2019-09-28: "Highly visible template: Over 170 categories are wholly dependent on this template"
Template:Canada province decade category/core (request) 2024-11-05 18:46 Template-protected (log) From Template:DecadecatCanadaprovince/core: Protected by BrownHairedGirl on 2019-09-28: "Highly visible template: Over 170 categories are wholly dependent on this template"
Template:Military history decade category/core (request) 2024-11-06 13:57 Template-protected (log) From Template:Milhistdecadecat/core: Protected by BrownHairedGirl on 2019-03-04: "Highly visible template: Used in about 100 category pages, which are wholly dependant on this template"
Template:Lists by year cat/nav (request) 2024-11-06 14:16 Template-protected (log) Protected by BrownHairedGirl on 2018-11-21: "Highly visible template"
Template:WikiProject Cricket (request) 2024-11-07 07:04 Template-protected (log) Modified by Renamed user mou89p43twvqcvm8ut9w3 on 2016-10-15: "Highly visible template"
Template:Taxonomy/Opisthokonta (request) 2024-11-07 11:26 Template-protected (log) Modified by Mark Arsten on 2013-11-17: "Highly visible template"
Updated as needed. Last updated: 11:28, 7 November 2024 (UTC)
Requests for permission - rollback

WP:RFPERM (rollback)

Rollback

[edit]

I respectfully request Rollback access to facilitate the use of Huggle, which will allow me to promptly and efficiently revert vandalism. I've been monitoring Recent Changes for the past 2-3 months, reverting disruptive edits.

I'm familiar with some Wikipedia policies, including: Reporting repeated vandals after 4 talk page warnings at WP:AIV, reporting reporting sock puppet accounts at WP:SPI and following the 3-revert rule (WP:3RR). And also I'm familiar with the use of Twinkle. ®asteem Talk 20:32, 2 November 2024 (UTC)

I see that you are failing to consistently warn editors when you revert their edits. Why? It's important to leave a notification for every revert you make (especially when reverting good faith edits). Are you aware of tools such as Twinkle or Ultraviolet which make this extremely easy? -Fastily 21:32, 2 November 2024 (UTC)
Fastily, I'm already using Twinkle. I've warned many users for vandalism, but I don't warn new users who have made only one edit, as per "Back Biting" guideline. Instead, I typically warn a user after their second vandalism attempt. But in future I'll consider warning users even after one non-constructive edit. ®asteem Talk 21:47, 2 November 2024 (UTC)
No, that is incorrect. You need to be leaving notifications (or warnings) for every revert, regardless of how many edits the user has made or whether this is the user's first instance of vandalism. -Fastily 01:07, 3 November 2024 (UTC)
{{Done}} I'll always leave a warning notice on their talk page without digging into their number of edits. ®asteem Talk ®asteem Talk 01:54, 3 November 2024 (UTC)
Great, could you please now go do some RC patrol in which you demonstrate how you will always be notifying all editors when you revert their edits? Also please don't use {{Done}} or {{Not done}} in your replies to me; on this page at least, these are for admin use only. -Fastily 02:36, 3 November 2024 (UTC)
Sure, I'll do RC patrol & will always notify users when I revert their changes. I sincerely apologize for using {done} or {not done} previously. ®asteem Talk 03:17, 3 November 2024 (UTC)
Requests for permission - account creator

There are no outstanding requests for account creator.