Jump to content

Wikipedia:Arbitration/Requests/Clarification and Amendment

From Wikipedia, the free encyclopedia
Requests for clarification and amendment

Amendment request: Palestine-Israel articles 4

[edit]

Initiated by Newslinger at 01:04, 25 August 2025 (UTC)[reply]

Case or decision affected
Palestine-Israel articles 4 arbitration case (t) (ev / t) (w / t) (pd / t)
Clauses to which an amendment is requested
  1. Wikipedia:Arbitration/Requests/Case/Palestine-Israel articles 4#Definition of the "area of conflict"
List of any users involved or directly affected, and confirmation that all are aware of the request
Confirmation that all parties are aware of the request
Information about amendment request

Statement by Newslinger

[edit]

I recently encountered a user talk page discussion titled "Views on the Israeli-Palestinian conflict and the Gaza war", in which Patternbuffered said, "I was going to just revert, but I'll give you a day or so to clean it up", in reference to article content related to the Arab–Israeli conflict. As Patternbuffered was not extended confirmed, the extended confirmed restriction (ECR) of WP:CT/A-I prohibited Patternbuffered from performing the described revert.

Per current practice (e.g. ScottishFinnishRadish's warning of Long-live-ALOPUS in another discussion for violating ECR by posting another user talk page comment), my understanding is that ECR also prohibited Patternbuffered from starting the user talk page discussion in the first place. However, Patternbuffered pointed out to me that the wording of the clause in question excludes "userspace" from the "area of conflict" without additional qualifiers. Long-live-ALOPUS also interpreted the clause as it was written.

I do not believe it is the intent of the userspace exception to allow non–extended confirmed users to openly discuss the Arab–Israeli conflict on other users' talk pages in ways that are prohibited in other namespaces and restricted on article talk pages. I ask the Arbitration Committee to amend the clause to limit the exception to the editor's own userspace, which better reflects existing practice. — Newslinger talk 01:04, 25 August 2025 (UTC)[reply]

@ScottishFinnishRadish: The problem is that, in the lead section of WP:CT/A-I, the text "with certain exceptions as provided below" contains a link to WP:CT/A-I § ARBPIA General Sanctions, which does invoke the term "area of conflict" in the bullet point "Extended confirmed restriction: The extended confirmed restriction is imposed on the area of conflict." An editor who is unfamiliar with the case history cannot be expected to know that ECR applies to the entire topic area (and not just the defined "area of conflict") after reading the WP:CT/A-I page. — Newslinger talk 14:23, 25 August 2025 (UTC)[reply]

Statement by Patternbuffered

[edit]

As I wrote on my talk page I was fine with the warning and just curious about an apparent loophole. I agree it should be addressed to mitigate future confusion or conflict; how that should be done I will leave in more experienced hands. Patternbuffered (talk) 11:51, 25 August 2025 (UTC)[reply]

Statement by Long-live-ALOPUS

[edit]

Statement by Thryduulf

[edit]

While at first glance the simple change seems unproblematic, there does need to be some allowance for posting on other users' talk pages. The first scenario that comes to mind is:

  • User:Example is not extended-confirmed. They make a good-faith edit to content related to the area of dispute on a page that is not ECP protected.
  • User:Foo reverts this edit on the grounds that Example is not extended-confirmed
  • User:Example posts on user talk:Foo seeking clarification (maybe they didn't understand jargon used in the summary)
  • User:Foo replies
  • User:Example posts a follow-up question (e.g. perhaps still not understanding, perhaps disagreeing that the content is related to the dispute)

As long as Example is not sealioning or otherwise acting in bad faith, we don't want to prohibit this sort of interaction yet a simple reading of the proposed language would do that. My first thought is a much-wordsmithed "this does not include discussion of actions taken regarding a user's own edits that takes place on the talk page of the user taking that action." While "discussion with the editor taking that action" is simpler, it would prohibit follow-up to a reply given by a talk-page stalker which I don't think would be desirable. Other things to consider are that good-faith, genuinely new editors are not guaranteed to know about pinging users to their own talk page, won't know how to determine whether some other editor is or is not extended-confirmed and if the queried actions relate to more than one editor (e.g. User:Foo reverted user:Example and user:Example2) it is better for all concerned for all discussion about it to happen on a single page. Thryduulf (talk) 01:35, 25 August 2025 (UTC)[reply]

Statement by Zero0000

[edit]

At WP:ARBPIA4#Definition of the "area of conflict" it says "For the purposes of editing restrictions in the ARBPIA topic area, the "area of conflict" shall be defined as encompassing...edits relating to the Arab-Israeli conflict, to pages and discussions in all namespaces with the exception of userspace.". And the application of ARBECR to PIA is "The extended confirmed restriction is imposed on the area of conflict." (my bold). So, even if "topic area" at WP:ARBECR is more general than "area of conflict", the ARBPIA page explicitly exempts userspace from it.

To repeat myself, ARBPIA4 does not apply ARBECR to the PIA "topic area" but only to the "area of conflict", which is a defined domain.

If ArbCom wants to replace the motion, they should do so with a motion to repeal and replace it, as this is not the first time the issue has come up and it won't be the last unless it is put to rest.

Personally I think that there is nothing wrong with a general userspace exemption, but reducing it to own-userspace would not be a big problem. On the other hand, restricting non-ECs from making comments in their own userspace would seem to have no purpose whatever, as there are other mechanisms for handling disruption. What sense is there in allowing edit requests on article talk pages but disallowing the same on own talk? I think own-userspace should be a general exemption to ECR in all topics. Zerotalk 12:02, 25 August 2025 (UTC)[reply]

Statement by {other-editor}

[edit]

Other editors are free to make relevant comments on this request as necessary. Comments here should address why or why not the Committee should accept the amendment request or provide additional information.

Palestine-Israel articles 4: Clerk notes

[edit]
This area is used for notes by the clerks (including clerk recusals).

Palestine-Israel articles 4: Arbitrator views and discussion

[edit]
  • The area of conflict language isn't found in Extended confirmed restriction – only extended-confirmed editors may make edits related to the topic area, with certain exceptions as provided below. All articles whose topic is strictly within the Arab-Israeli conflict topic area shall be extended confirmed protected by default, without requiring prior disruption on the article. The most recent clarification and motion says The restriction applies to all edits and pages related to the topic area, broadly construed, with the following exceptions. The "area of conflict" language is just an artifact on that page because of older decisions. ECR applies to all edits related to the topic area, broadly construed. ScottishFinnishRadish (talk) 10:52, 25 August 2025 (UTC)[reply]
    Thryduulf, I think that falls under WP:BANEXEMPT#2, and that's how I've always seen it handled and handled it myself. ScottishFinnishRadish (talk) 10:56, 25 August 2025 (UTC)[reply]
    Newslinger, yeah, that should probably be fixed. It looks like it's just a supplemental page so it doesn't need a full motion so if my views align with the rest of the committee it should be a simple matter to tidy up. ScottishFinnishRadish (talk) 14:50, 25 August 2025 (UTC)[reply]
  • Thank you very much, SilverLocust. I was about to search for the discussion where I had analyzed this and said it should be changed. Here it is. My comment from 11:18, 30 July 2024 (UTC) is still my opinion on this matter. ~ ToBeFree (talk) 19:56, 4 September 2025 (UTC)[reply]
  • Agree with ToBeFree immediately above, and their comments (that they link to) last time it was at this page. Daniel (talk) 00:47, 22 September 2025 (UTC)[reply]