Jump to content

Wikipedia:Requests for page protection: Difference between revisions

Page semi-protected
From Wikipedia, the free encyclopedia
Browse history interactively
← Previous editNext edit →
Content deleted Content added
VisualWikitext
→Autonomous Administration of North and East Syria: upgraded to WP:ECP (indef, but reminder sought)
Line 183: Line 183:


:There has been a mistake, I guess it is probably warranted that in this case the protection level be increased. I didn't know there was a possibility that a protection level can be decreased over the RPP function in the drop down menu. [[User:Paradise Chronicle|Paradise Chronicle]] ([[User talk:Paradise Chronicle|talk]]) 09:12, 30 June 2021 (UTC)
:There has been a mistake, I guess it is probably warranted that in this case the protection level be increased. I didn't know there was a possibility that a protection level can be decreased over the RPP function in the drop down menu. [[User:Paradise Chronicle|Paradise Chronicle]] ([[User talk:Paradise Chronicle|talk]]) 09:12, 30 June 2021 (UTC)

::{{rfpp|ec|indefinite}} But hoping to downgrade back to indef semi in the near(ish) future. Please remind me. [[User:El_C|El_C]] 12:06, 30 June 2021 (UTC)


== Current requests for edits to a protected page ==
== Current requests for edits to a protected page ==

Revision as of 12:06, 30 June 2021

"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

    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.

    Socialist Party of Serbia

    Indefinite semi-protection: Persistent addition of unsourced or poorly sourced content – adding unsourced content, this page can be put under ARBEE/Balkans if possible. Vacant0 (talk) 10:53, 29 June 2021 (UTC)[reply]

    Semi-protected for a period of 3 days, after which the page will be automatically unprotected. Cwmhiraeth (talk) 08:12, 30 June 2021 (UTC)[reply]
    Declined – Not enough recent disruptive activity to justify protection. Cwmhiraeth (talk) 08:31, 30 June 2021 (UTC)[reply]

    Jane Kim

    Temporary semi-protection: Persistent sockpuppetry – Block evasion by User:Ylsb16 using New York IP Special:Contributions/184.153.71.193 and the range Special:Contributions/2603:7000:9C00:204A:0:0:0:0/64. Binksternet (talk) 15:48, 29 June 2021 (UTC)[reply]

    File:Call Me If You Get Lost album cover.jpg

    Temporary semi-protection: Persistent vandalism. Shellwood (talk) 16:28, 29 June 2021 (UTC)[reply]

    Comment The vandalism on this file has been going on for at least 24 hours or so. Philipnelson99 (talk) 03:26, 30 June 2021 (UTC)[reply]

    Evyatar

    Indefinite extended confirmed protection: Arbitration enforcement – Requesting indefinite protection, per the Israel-Palestine arbitration enforcement decision. RoanokeVirginia (talk) 16:49, 29 June 2021 (UTC)[reply]

    Fall of Constantinople

    Semi-protection: Persistent meatpuppetry about Serbian involvement. 178.79.46.3 (talk · contribs) keeps deleting stuff claiming "there is no source". Beshogur (talk) 16:53, 29 June 2021 (UTC)[reply]

    Talk:Oprah with Meghan and Harry

    Semi-protection: Persistent sockpuppetry. Drill it (talk) 16:53, 29 June 2021 (UTC)[reply]

    England–Germany football rivalry

    Temporary semi-protection: Persistent addition of unsourced or poorly sourced content. Flix11 (talk) 17:54, 29 June 2021 (UTC)[reply]

    United Airlines Flight 93

    Temporary full protection: IP hopping editor keeps edit warring over content in an FA level article.--MONGO (talk) 20:32, 29 June 2021 (UTC)[reply]

    @MONGO: Your request is wrong because you states that there is edit warring or vandalism by IP hopper. It is more necessary to temporary semi-protection. 180.242.42.109 (talk) 21:47, 29 June 2021 (UTC)[reply]

    The Amazing World of Gumball

    Extended confirmed protection: Persistent vandalism. Drill it (talk) 22:48, 29 June 2021 (UTC)[reply]

    Type 10

    Semi-protection: Persistent vandalism – A pattern of new SPAs and IPs edit-warring with each other and adding nonsense. Code Pending (talk) 00:29, 30 June 2021 (UTC)[reply]

    Template:Tagansko–Krasnopresnenskaya line RDT

    Temporary semi-protection: Persistent vandalism. IP 108.48.189.192 constantly adding unverified and fictitious information. AlgaeGraphix (talk) 00:33, 30 June 2021 (UTC)[reply]

    Sofia Carson

    Temporary semi-protection: Persistent vandalism. Pamzeis (talk) 01:58, 30 June 2021 (UTC)[reply]

    Çukur

    Indefinite full protection: Persistent vandalism – This page is continuously being vandalized by fans of a certain character in the show, removing factual information about characters they dislike and adding wrong biased opinions about what they like. Everytime I request a temporary protection, it gets removed and as soon as it is removed the vandalism returns. Rowananan (talk) 02:01, 30 June 2021 (UTC)[reply]

    Comment This looks like a content dispute regarding what characters should be considered "main cast" versus "supporting case"; that doesn't fall under our definition of vandalism. OhNoitsJamie Talk 02:10, 30 June 2021 (UTC)[reply]

    All About That Bass

    Temporary semi-protection: Persistent vandalism. Binksternet (talk) 02:38, 30 June 2021 (UTC)[reply]

    José Olaya

    Temporary semi-protection: Persistent vandalism – I've been seeing this pop up far too often in recent changes with the subject's name being vandalized. Philipnelson99 (talk) 03:20, 30 June 2021 (UTC)[reply]

    WCLT-FM

    Temporary semi-protection: Persistent disruptive editing – Block evasion by Special:Contributions/174.105.181.31 using Special:Contributions/174.105.177.231. Binksternet (talk) 03:38, 30 June 2021 (UTC)[reply]

    This is clearly same IPv4 range (174.105.xx.xx or 174.105.0.0/16) so rangeblock is needed. 180.242.42.109 (talk) 03:57, 30 June 2021 (UTC)[reply]

    Beijing Ducks

    Temporary semi-protection: Persistent vandalism – Resumed since previous protection expired; stemming from a troll claiming that Simmons was sent to the Shanghai Sharks, but I can't seem to find the originating post. Jalen Folf (talk) 04:03, 30 June 2021 (UTC)[reply]

    Watpracharangsan School

    Temporary semi-protection: Persistent disruptive editing; edit warring to include promotional content, lists and photos of non notable employees. 2601:188:180:B8E0:65F5:930C:B0B2:CD63 (talk) 04:31, 30 June 2021 (UTC)[reply]

    Hyatt Regency walkway collapse

    Full protection: Persistent edit warring. Thanks. — Smuckola(talk) 04:57, 30 June 2021 (UTC)[reply]

    It is an vandalism by multiple IPs, not edit warring, so full protection cannot be applied. 180.242.42.109 (talk) 05:23, 30 June 2021 (UTC)[reply]

    Mahabad

    Indefinite extended confirmed protection: Persistent vandalism – Already indeffed semi, but the sock farm clearly has plenty of sleepers to get round that. Pipsally (talk) 06:17, 30 June 2021 (UTC)[reply]

    @Pipsally: Are you already reported these sockpuppets account to Sockpuppet investigation? Two accounts in edit history are clearly related each other with similar edit (example: Kepv and Wikikurd80). 180.242.42.109 (talk) 07:14, 30 June 2021 (UTC)[reply]

    Tabrez Ansari lynching

    Semi-protection: for a year. IP-disruption has slowed, but is still present in April, May and June. Gråbergs Gråa Sång (talk) 08:18, 30 June 2021 (UTC)[reply]

    Baju kurung

    Semi-protection: Persistent disruption by IP users. Northheavensky (talk)

    Semi-protected for a period of 3 days, after which the page will be automatically unprotected. Cwmhiraeth (talk) 08:32, 30 June 2021 (UTC)[reply]

    Emiway Bantai

    Temporary semi-protection: Persistent vandalism. Firestar464 (talk) 08:32, 30 June 2021 (UTC)[reply]

    Ron Carter discography

    Semi-protection: Persistent vandalism. Drill it (talk) 08:53, 30 June 2021 (UTC)[reply]

    Palestinian hip hop

    Extended confirmed protection: Arbitration enforcement. Drill it (talk) 09:02, 30 June 2021 (UTC)[reply]

    2022 Punjab Legislative Assembly election

    Temporary semi-protection: Content Dispute/Edit Warring. -- DaxServer (talk) 09:42, 30 June 2021 (UTC)[reply]

    SM Entertainment artists

    Temporary semi-protection: Persistent disruptive editing – Multiple IP user continuously (as in not all at the same time but over the days and weeks) add Super Junior to the list when it is already listed under Label SJ at Subsidiaries subsection slightly below. — Paper9oll (🔔 • 📝) 10:02, 30 June 2021 (UTC)[reply]

    Shriram Group

    Temporary pending changes protection: Persistent Disruptive Editing. -- DaxServer (talk) 10:03, 30 June 2021 (UTC)[reply]

    Mosquito laser

    Temporary semi-protection: There's an IP that is rather relenetlessly spamming self promotional material on this article. We had a nice respite with a month's semi protection, but now that protection has expired the disruption has resumed. MrOllie (talk) 11:17, 30 June 2021 (UTC)[reply]

    MasterChef Australia (series 13)

    Semi-protection for a longer period: High level of IP vandalism. The page was recently semi-protected, however, IP vandals returned as soon as the protection expired. WWGB (talk) 11:42, 30 June 2021 (UTC)[reply]

    Politician

    Temporary semi-protection: Persistent disruptive editing – One day after protection expired, the IP from Assam is back adding the same nonsense about political immunity. Drmies had previously range-blocked 223.238.100.0/22 and 106.203.128.0/19, so this is block evasion too. Longer protection would be appreciated; this is getting tiring. Sdrqaz (talk) 11:46, 30 June 2021 (UTC)[reply]

    Current requests for reduction in 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

    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

    Username policy

    Reason: (Submitting this request again just to make sure it gets seen) I need to ask a question about the username policy before making my username just to make sure the name I want is ok, but ironically I can't post on the talk page without making the name first. 153.90.19.67 (talk) 23:11, 15 November 2024 (UTC)[reply]

    Declined Not a valid reason to reduce protection. If you have a question about a username, the best place to ask would be WP:AN or WP:Teahouse. Dennis Brown - 2¢ 00:02, 16 November 2024 (UTC)[reply]
    ok, thank you 153.90.19.67 (talk) 00:40, 16 November 2024 (UTC)[reply]

    Autonomous Administration of North and East Syria

    Temporary semi-protection: Persistent vandalism – There are two new editors who persistently want to include a phrase in the lead which have been reverted by 5 more experienced editors. Paradise Chronicle (talk) 09:10, 30 June 2021 (UTC)[reply]

    There has been a mistake, I guess it is probably warranted that in this case the protection level be increased. I didn't know there was a possibility that a protection level can be decreased over the RPP function in the drop down menu. Paradise Chronicle (talk) 09:12, 30 June 2021 (UTC)[reply]
    Extended confirmed protected indefinitely. But hoping to downgrade back to indef semi in the near(ish) future. Please remind me. El_C 12:06, 30 June 2021 (UTC)[reply]

    Current requests for edits to a protected page

    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.
    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[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)[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.[2][3][4].VR (Please ping on reply) 14:55, 16 October 2024 (UTC)[reply]
    Thank you. Maybe the following article gives a bit more clarity.[[5]] Gilbert04 (talk) 18:10, 16 October 2024 (UTC)[reply]
    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)[reply]
    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)[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[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)[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]

    Gaza genocide 3

    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]

    @Zlmark I agree with this - Wikipedia needs to be accurate and reliable. Things like this are pushing millions of people away from Wikipedia, when we want to do the opposite. We want this to change. Becoming more accurate is key. Hopefully this happens. Avishai @Avishai11 Avishai11 (talk) 20:07, 15 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]

    Two-state solution

    I would like to request the addition of the following paragraph on Singapore’s support for a two-state solution under the section "International Positions on the Two-State Solution" in the Two-state solution article:

    International Positions on the Two-State Solution

    Singapore: Singapore supports a two-state solution for the Israeli-Palestinian conflict, advocating for a negotiated outcome aligned with relevant United Nations Security Council resolutions. According to Singapore’s Ministry of Foreign Affairs, Singapore believes this approach allows Israelis and Palestinians to coexist peacefully and securely, considering it the only viable path toward a comprehensive, just, and lasting resolution. Singapore also consistently upholds the Palestinian right to a homeland. The PLO, which constitutes the key pillar of the current Palestinian Authority, accepts Israel's right to exist and has renounced terrorism.[1]

    EsenL (talk) 02:07, 12 November 2024 (UTC)[reply]

    References

    1. ^ "Reply to Parliamentary Question on Palestine". Retrieved 2024-11-12.
    Source? Providing a source to back up your edit drastically improves the chance it'll be done. —Jéské Couriano v^_^v threads critiques 02:18, 12 November 2024 (UTC)[reply]
    have added! thanks! EsenL (talk) 02:33, 12 November 2024 (UTC)[reply]

    Gaza genocide - the 186,000 indirect deaths estimate

    In the "Indirect" section, the following sentence should be added after "186,000 or even more deaths could be attributable to the current conflict in Gaza":

    Three days after the publication, one of the writers, Professor Martin McKee, clarified that the 186,000 figure was “purely illustrative”[1] and stated that “our piece has been greatly misquoted and misinterpreted.”[2]

    References

    1. ^ "Concerns regarding Gaza mortality estimates". The Lancet. November 4, 2024.
    2. ^ "'186,000 Gazans dead': Lancet magazine publishes new blood libel". The Jerusalem Post. July 9, 2024. 
    Zlmark (talk) 16:26, 12 November 2024 (UTC)[reply]

    Springfield pet-eating hoax

    I would like to request that a change be made for accuracy under the subhead Origin and spread: Other events. There is a reference to a photo of a man carrying two dead geese, but it is actually only one goose. Footnotes 54, 58, and 59 all state that there is one goose in the photo. Footnote 60 says two geese, but this is evidently a mistake on TMZ's part as the photo itself clearly shows only one goose.

    I suggest that the wording "man carrying two dead Canada geese" be changed to "man carrying a dead Canada goose".

    In the next sentence I suggest that the wording "The geese were roadkill" either be changed to "The goose was roadkill" or that this part of the sentence be eliminated since the only source for the goose being roadkill is the TMZ article which may be unreliable and perhaps should be removed as a reference? It's possible the official quoted by TMZ was referring to a different incident altogether involving two roadkill geese and TMZ mistakenly linked this to the Columbus photo.

    Then I suggest in the following sentence the wording "stealing geese" be changed to "stealing a goose".

    Also, I would like to suggest that the semi-protected status be lifted from the Talk page of this article. 2600:100A:B10A:4AA1:0:21:7E13:E301 (talk) 23:18, 12 November 2024 (UTC)[reply]

    The talk-page protection cannot be reversed here; either contact El C or appeal at WP:Arbitration/Requests/Enforcement to get it lifted. (I will note, however, that the semi-protection is set to lift 16 December.) —Jéské Couriano v^_^v threads critiques 07:44, 13 November 2024 (UTC)[reply]

    Gaza genocide 4

    I suggest changing the map on the states agreeing with with the Genocide charge (green coloured) to include Spain and Ireland, as these declared to join South Africa's case in the ICJ and generally agree with the allegations in public statements. Ireland also passed a motion in the parliament declaring it a genocide. — Preceding unsigned comment added by 2001:9e8:9a4:6900:50f:51e:c5cd:b7cf (talk • contribs) 15:10, 13 November 2024 (UTC)[reply]

    2024 US presidential election

    In the state results table, I would like to request that the columns labeled Margin and Margin swing be filled in, for those rows/states in which the relevant data has already been entered. Obviously not every state has data, but most do.

    This should be trivial, at least for Margin, but the inability to sort by margin has been annoying me for a week now. LoganStokols (talk) 19:23, 15 November 2024 (UTC)[reply]

    Derry

    I would like to request that... (You wrongfully state the official name of Derry is Londonderry this is incorrect[1]) . 83.106.116.186 (talk) 23:03, 15 November 2024 (UTC)[reply]

    Further information: Wikipedia:Edit requests

    Create a level 3 header with a link to the article in question, then a {{pagelinks}} template and then the reason.

    Handled requests

    A rolling archive of the last seven days of protection requests can be found at Wikipedia:Requests for page protection/Rolling archive.

    1. ^ I'm Irish I know our history
    Retrieved from "https://en.wikipedia.org/w/index.php?title=Wikipedia:Requests_for_page_protection&oldid=1031220210"