Misplaced Pages

:Arbitration/Requests/Clarification and Amendment - Misplaced Pages

Article snapshot taken from Wikipedia with creative commons attribution-sharealike license. Give it a read and then ask your questions in the chat. We can research this topic together.
< Misplaced Pages:Arbitration | Requests

This is an old revision of this page, as edited by ABHammad (talk | contribs) at 09:49, 20 August 2024 (→Statement by ABHammad). The present address (URL) is a permanent link to this revision, which may differ significantly from the current revision.

Revision as of 09:49, 20 August 2024 by ABHammad (talk | contribs) (→Statement by ABHammad)(diff) ← Previous revision | Latest revision (diff) | Newer revision → (diff) Shortcut Arbitration Committee proceedings Case requests

Currently, there are no requests for arbitration.

Open cases
Case name Links Evidence due Prop. Dec. due
Palestine-Israel articles 5 (t) (ev / t) (ws / t) (pd / t) 21 Dec 2024 11 Jan 2025
Recently closed cases (Past cases)

No cases have recently been closed (view all closed cases).

Clarification and Amendment requests
Request name Motions  Case Posted
Amendment request: Definition of the "area of conflict" Clause 4 (b) Motion none 26 July 2024
Clarification request: Appeal methods for Lima Bean Farmer topic ban none none 12 August 2024
Amendment request: German war effort Motion (orig. case) 13 August 2024
Amendment request: Palestine-Israel articles (AE referral) none none 17 August 2024
Arbitrator motions
Motion name Date posted
Arbitrator workflow motions 1 December 2024

Requests for clarification and amendment

Use this page to request clarification or amendment of a closed Arbitration Committee case or decision.

  • Requests for clarification are used to ask for further guidance or clarification about an existing completed Arbitration Committee case or decision.
  • Requests for amendment are used to ask for an amendment or extension of existing sanctions (for instance, because the sanctions are ineffective, contain a loophole, or no longer cover a sufficiently wide topic); or appeal for the removal of sanctions (including bans).

Submitting a request: (you must use this format!)

  1. Choose one of the following options and open the page in a new tab or window:
  2. Save your request and check that it looks how you think it should and says what you intended.
  3. If your request will affect or involve other users (including any users you have named as parties), you must notify these editors of your submission; you can use {{subst:Arbitration CA notice|SECTIONTITLE}} to do this.
  4. Add the diffs of the talk page notifications under the applicable header of the request.
Clarification and Amendment archives
123456789101112131415161718
192021222324252627282930313233343536
373839404142434445464748495051525354
555657585960616263646566676869707172
737475767778798081828384858687888990
919293949596979899100101102103104105106107108
109110111112113114115116117118119120121122123124125126
127128129130131

Please do not submit your request until it is ready for consideration; this is not a space for drafts, and incremental additions to a submission are disruptive.

Guidance on participation and word limits

Unlike many venues on Misplaced Pages, ArbCom imposes word limits. Please observe the below notes on complying with word limits.

  • Motivation. Word limits are imposed to promote clarity and focus on the issues at hand and to ensure that arbitrators are able to fully take in submissions. Arbitrators must read a large volume of information across many matters in the course of their service on the Committee, so submissions that exceed word limits may be disregarded. For the sake of fairness and to discourage gamesmanship (i.e., to disincentivize "asking forgiveness rather than permission"), word limits are actively enforced.
  • In general. Most submissions to the Arbitration Committee (including statements in arbitration case requests and ARCAs and evidence submissions in arbitration cases) are limited to 500 words, plus 50 diffs. During the evidence phase of an accepted case, named parties are granted an automatic extension to 1000 words plus 100 diffs.
  • Sectioned discussion. To facilitate review by arbitrators, you should edit only in your own section. Address your submission to arbitrators, not to other participants. If you wish to rebut, clarify, or otherwise refer to another submission for the benefit of arbitrators, you may do so within your own section. (More information.)
  • Requesting an extension. You may request a word limit extension in your submission itself (using the {{@ArbComClerks}} template) or by emailing clerks-l@lists.wikimedia.org. In your request, you should briefly (in 1–2 sentences) include (a) why you need additional words and (b) a broad outline of what you hope to discuss in your extended submission. The Committee endeavors to act upon extension requests promptly and aims to offer flexibility where warranted.
    • Members of the Committee may also grant extensions when they ask direct questions to facilitate answers to those questions.
  • Refactoring statements. You should write carefully and concisely from the start. It is impermissible to rewrite a statement to shorten it after a significant amount of time has passed or after anyone has responded to it (see Misplaced Pages:Talk page guidelines § Editing own comments), so it is often advisable to submit a brief initial statement to leave room to respond to other users if the need arises.
  • Sign submissions. In order for arbitrators and other participants to understand the order of submissions, sign your submission and each addition (using ~~~~).
  • Word limit violations. Submissions that exceed the word limit will generally be "hatted" (collapsed), and arbitrators may opt not to consider them.
  • Counting words. Words are counted on the rendered text (not wikitext) of the statement (i.e., the number of words that you would see by copy-pasting the page section containing your statement into a text editor or word count tool). This internal gadget may also be helpful.
  • Sanctions. Please note that members and clerks of the Committee may impose appropriate sanctions when necessary to promote the effective functioning of the arbitration process.

General guidance

Shortcuts:
Clarification and Amendment archives
123456789101112131415161718
192021222324252627282930313233343536
373839404142434445464748495051525354
555657585960616263646566676869707172
737475767778798081828384858687888990
919293949596979899100101102103104105106107108
109110111112113114115116117118119120121122123124125126
127128129130131

Amendment request: Definition of the "area of conflict" Clause 4 (b)

Initiated by Selfstudier at 13:43, 26 July 2024 (UTC)

Case or decision affected
Misplaced Pages:Contentious topics/Arab–Israeli conflict
Clauses to which an amendment is requested
  1. Misplaced Pages:Contentious topics/Arab–Israeli conflict#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 Selfstudier

To match WP:ECR (Idk if it is worth changing both to link to namespace 1).

@Barkeep49: @Zero0000: The discussion here refers (at the bottom)

@Zero0000: Not only. See Barkeep49 statement at the relevant AE complaint (still open) However, I will note that the contradiction between the "topic area" as defined and what areas ECR do not allow for is present. And so in a different scenario I would say this user shouldn't have to eat a block that could then be escalated if there are future transgressions. However, given that there was other conduct leading to a topic ban that factor doesn't seem to apply here. To be clear, my opinion is that ECR, being later, should take precedence but that's just me.Selfstudier (talk) 08:43, 28 July 2024 (UTC)

And now, the same technicality being referred to by another editor. Selfstudier (talk) 10:42, 28 July 2024 (UTC)

@Zero0000: I am only "proposing" that this "technicality" which has not been identified by myself, be fixed up, I'm just initiating the paperwork, to the extent anyone thinks that it is required. What I want is that it not be available as a defense by non EC editors, currently two of them mentioning it, and I suspect more inbound if left unresolved. If there is another way to clean it up, I'm all ears. And @Doug Weller: has now raised the question indirectly as well https://en.wikipedia.org/search/?title=Wikipedia_talk:Arbitration_Committee/Noticeboard&curid=21090546&diff=1237149351&oldid=1236465052#Why_does_ARPBIA_allow_userspace_as_an_exception? Selfstudier (talk) 12:10, 28 July 2024 (UTC)

@Sir Kenneth Kho: Many thanks for clarifying my inept proposal. For me, though, ECR should function like a tban, "any edits that relate to the Arab-Israeli conflict (broadly construed) anywhere on Misplaced Pages" Selfstudier (talk) 17:55, 28 July 2024 (UTC)

@Guerillero: Depends what you mean by edge case, if you mean that it isn't usually a problem, sure. However recently, I don't know quite how to put it, there has been a sort of assault on ECR, which you could, at a pinch, just call wikilawyering. See for example, Misplaced Pages:Arbitration/Requests/Enforcement#Arbitration enforcement action appeal by Emdosis and the comment by an admin there, "I wouldn't immediately understand "userspace" to apply to another user's talk page in this case – seems more like wikilawyering than anything else to say that this edit falls outside of the CT regime. We can drag this to ARCA if we have to, but just agreeing that the filer made a vexatious argument is easier." (I won't name them, since they don't want to be here, methinks). Selfstudier (talk) 17:40, 1 August 2024 (UTC)

Statement by Barkeep49

There is a small mismatch between the area of scope and ECR and perhaps arbcom wants to fix that. Perhaps it doesn't. I'm not sure why I am involved in this case. Barkeep49 (talk) 14:58, 26 July 2024 (UTC)

Statement by Zero0000

Can we have this request actually explained, please?

I don't see any contradiction between "userspace" in "area of conflict" and "talkspace" at ECR. They serve different purposes.

One place says that the "area of conflict" does not extend to userspace (which implies that it does extend to talkspace). ECR indicates that talkspace has some differences in restrictions compared to article space. Both these make sense and can be true at the same time. We definitely do not want the "area of conflict" to exclude talkspace, because then the ECR restrictions on talkspace would not apply to it.

Or maybe I missed the point entirely. Zero 15:14, 26 July 2024 (UTC)

To editor Selfstudier: So a messy argument on some user's talk page is what counts as an explanation?

As I see it, Definition of the "area of conflict" defines which pages and edits are subject to editing restrictions in ARBPIA, and WP:ARBECR says what those restrictions are. I don't see any contradiction there, and it seems to me that changing "userspace" to "talkspace" in the former would remove article talk pages from the area of conflict and disable all the restrictions there. Zero 02:43, 28 July 2024 (UTC)

To editor Selfstudier: The contradiction you claim to exist actually does not exist. Let's start at ECR:

"The Committee may apply the "extended confirmed restriction" to specified topic areas." So now, we ask, what is the "topic area" in the case of ARBPIA? That sentence has a footnote:
"The current topic areas under this restriction are listed as having the "extended confirmed restriction" in the table of active Arbitration Committee sanctions." So we click on that link and find a big table. ARBPIA is near the end. It says:
"The entire set of articles whose topic relates to the Arab-Israeli conflict, broadly interpreted; edits relating to the Arab-Israeli conflict, to pages and discussions in all namespaces with the exception of userspace." (my emphasis) So in fact ECR agrees with WP:Contentious_topics/Arab–Israeli conflict#Definition of the "area_of_conflict" that edits in userspace are not in the ARBPIA "topic area". Where is the contradiction?

I'll also repeat (please answer): You seem to be proposing that "edits relating to the Arab-Israeli conflict, to pages and discussions in all namespaces with the exception of userspace" at WP:Contentious_topics/Arab–Israeli conflict#Definition of the "area_of_conflict" be changed to "edits relating to the Arab-Israeli conflict, to pages and discussions in all namespaces with the exception of talkspace". Why does that make any sense? You want to remove talkspace from the topic area?? Zero 11:54, 28 July 2024 (UTC)

To editor Selfstudier: If arbcom wish to undo the exclusion of userspace from the ARBPIA topic area, that's their decision, but your proposal does much more than that. Zero 12:25, 28 July 2024 (UTC)

If a change to the status of userspace is to be considered, I suggest that arbcom consider all CT topics and not just ARBPIA. Personally I don't understand why an editor should be forbidden from mentioning the topic in their own user space (unless they are actively disruptive there). For example, an editor who is approaching 500 edits may develop some text in their sandbox for insertion into articles once EC is achieved — isn't that perfectly reasonable? An editor who abuses this allowance (say, by excessive pings) can be dealt with easily. Zero 04:37, 29 July 2024 (UTC)

Statement by Sean.hoyland

Maybe this revert I did a couple of days ago is a useful test. Is the revert valid or invalid under the remedies? Sean.hoyland (talk) 12:51, 28 July 2024 (UTC)

Statement by Sir Kenneth Kho

This amendment request came to my attention after @Doug Weller: pointed it to me, I believe I can provide some clarity for the arbitrators.

I think there is an error in the request as pointed out by @Zero0000: the intended request is likely "remove exception of userspace" instead of "change userspace to talkspace" in WP:PIA, and the opposing side would be "add exception of userspace" to WP:ECR.

The answer would depend on whether arbitrators intended WP:ECR A(1) to overrule or uphold WP:PIA 4(B), if there is an answer, we are done.

If arbitrators did not consider it at all, the strongest argument for the initiating side would be WP:BROADLY, as the broadest possible thing would be no exception to userspace.

I'm arguing in favor of the opposing side, the strongest argument would be WP:UOWN, as userspace is traditionally given broad latitude too, it seems that WP:ECR and WP:UOWN should have their own jurisdiction, and on the balance WP:ECR should not be excessively broad.

@Selfstudier: nicely pointed to WP:TBAN in support of the initiating side, but it is worth noting that WP:TBAN is intended to "forbid editors from making edits related to a certain topic area where their contributions have been disruptive", while WP:GS is intended to "improve the editing atmosphere of an article or topic area", which applies here as WP:GS specifically includes "Extended confirmed restriction". Sir Kenneth Kho (talk) 16:50, 28 July 2024 (UTC)

Statement by Callanecc

My understanding is that"

Unless thought through extensively, there is a potential contradiction between what is defined as related content:

The 'Definition of the "area of conflict"' decision says that related content is edits relating to the Arab-Israeli conflict, to pages and discussions in all namespaces with the exception of userspace (that is, not articles).
'General sanctions upon related content' says it applies to related content but then redefines this is (i.e. pages not otherwise related to the area of conflict) which I suspect is intended to mean things defined above as 'related content' (not what is actually says which is pages not covered at all in the definition).

There is also the potential that any restiction (e.g. topic ban or 0RR) imposed under contentious topics cannot apply in userspace or could an editor be restricted for an edit on a userpage or user talk page.

To avoid the confusion and contradiction created I suggest that:

  • "with the exception of userspace" is removed from the definition
  • "(i.e. pages not otherwise related to the area of conflict)" is replaced with "(see ])".
  • Then either:
    • A decision is added to the index explicitly allowing CTOP restrictions to apply to edits made in relation to related content anywhere on Misplaced Pages to close the loophole currently exempting userspace completely. This would mean, however, that to be covered user talk pages would need to have the enforcement templates on them.
OR
  • An exemption is added so that the requirements of "General sanctions upon related content" are not applied to editor restrictions imposed under CTOP. This would be the closest to the current intent where editors could be restricted from related content based on and applying to all of their editing in the topic area regardless of whether pages have the enforcement templates on them or not.

Callanecc (talk • contribs • logs) 07:16, 31 July 2024 (UTC)

@Aoidh: See discussion here regarding the exemption for userspace. Callanecc (talk • contribs • logs) 07:26, 31 July 2024 (UTC)
Premeditated Chaos might remember more about the discussion and thinking behind this and my statement in general too. Callanecc (talk • contribs • logs) 07:29, 31 July 2024 (UTC)

Statement by PMC

Callanecc, I'm afraid I don't recall in any greater depth than my comments at the workshop, sorry. The userspace exception was suggested by Huldra and Zero0000, who made some comments re: user talk pages that on review, look like reasonable concerns; whether or not they're still applicable I can't say. ♠PMC♠ (talk) 02:24, 1 August 2024 (UTC)

Statement by Doug Weller

I think it would be easy to make it clear when mentioning talk space we meant user talk space and are not forbidding edit requests when the specific sanction allows them. Surely we don't want non-extended-confirmed-editors to be able add material to their own userspace they cannot added elsewhere. The purpose as I understand it of the 500 edits and 30 days is to enable them to learn our policies and guidelines and hopefully how to work constructively with others. I also think we don't want non-ecr users to use their talk space or the talk space of others to discuss the topic. Doug Weller talk 12:24, 1 August 2024 (UTC)

I would rather not name this but recently rsn into another edotor with the same issue, but others convinced him he was wrong, although apparently he was right. Doug Weller talk 18:06, 1 August 2024 (UTC)

Statement by Red-tailed hawk (Definition)

Is there a reason the proposed motion uses "broadly interpreted" instead of the standard "broadly construed"? Is there a difference in meaning we are supposed to infer, or are they one and the same for purposes of this motion? — Red-tailed hawk (nest) 18:26, 17 August 2024 (UTC)

Definition of the "area of conflict" Clause 4 (b): Clerk notes

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

Definition of the "area of conflict" Clause 4 (b): Arbitrator views and discussion

  • At the moment, "userspace" (including user pages, user talk pages and subpages, "all of these pages") is (only) related content to the ARBPIA area as described at Misplaced Pages:Contentious topics/Arab–Israeli conflict § General sanctions upon related content. This leads to the following result, which is confusing to me:This should be changed in my opinion, and I am inclined to support the removal of the userspace exemption as edit requests should be sufficient to allow non-extended-confirmed editors to participate with minimal disruption in the area. The current state allows them to wait 30 days, make 500 purely ARBPIA-related edits to their sandbox and then move that to the mainspace. ~ ToBeFree (talk) 11:18, 30 July 2024 (UTC)
  • I just wanted to note that I am aware of and am watching this discussion, but I would like to look more into the reasoning/history behind the current wording before commenting further. - Aoidh (talk) 02:30, 31 July 2024 (UTC)
    • I don't see any contradiction between what WP:ECR says and what WP:CT/A-I describes; the CT page describes what is and is not under the ECR restriction in a way that is entirely compatible with the wording of ECR. ECR covers the area of conflict, and userspace is not in area of conflict. However it can be as "technically correct" as possible, but if it's confusing or seemingly incompatible to reasonable editors (which seems to be the case) then it's not doing it's purpose and needs to be rewritten or amended for clarity. If we're going to be imposing these atypical rules for this topic area then they need to be accessible and easily understood. - Aoidh (talk) 18:30, 1 August 2024 (UTC)
  • Is this a real problem or an edge case? --Guerillero 18:52, 31 July 2024 (UTC)
  • I think one issue with this is that the "primary articles" and "related content" distinction has proven to be less useful with time. When the case was first decided, the extended confirmed restriction had not been established. (In fact, the ARBPIA 500/30 restriction is what eventually led to the adoption of WP:ARBECR.) Now, WP:ARBECR points A, B, and C establish the proper enforcement actions to be taken, without need for any reference to "primary articles" and "related content" — a distinction that few if any other cases maintain. I would therefore support a motion defining the "area of conflict" to simply be "the Arab-Israeli conflict, broadly interpreted", and making conforming edits to the rest of the case. (We can keep the templates, but the definitions of primary articles and related content will no longer be necessary in defining the scope of the restrictions.) Doing so would resolve this request and simplify the language going forward. Best, KevinL (aka L235 · t · c) 01:43, 16 August 2024 (UTC)
    @Red-tailed hawk: I would assume the two terms should be viewed identically. Further thoughts forthcoming — currently discussing among ourselves. Best, KevinL (aka L235 · t · c) 18:29, 17 August 2024 (UTC)

Motion: Definition of the "area of conflict" Clause 4 (b)

For the purposes of editing restrictions in the ARBPIA topic area, the "area of conflict" shall be defined as the Arab-Israeli conflict, broadly interpreted.

For this motion there are 9 active arbitrators. With 0 arbitrators abstaining, 5 support or oppose votes are a majority.
Majority reference
Abstentions Support votes needed for majority
0–1 5
2–3 4
4–5 3
Support
  1. I hope this matches L235's idea; I'm open to them changing the motion text if I missed something. It's a simple and clear solution, and simplifying confusing conditions that have actually caused confusion is good to me. ~ ToBeFree (talk) 14:17, 17 August 2024 (UTC)
Oppose
Abstain
Arbitrator discussion
  • ...

Clarification request: Appeal methods for Lima Bean Farmer topic ban

Initiated by Lima Bean Farmer at 20:16, 12 August 2024 (UTC)

Case or decision affected
Original topic ban made before switch to contentious topics
AE appeal that modified the topic ban

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

Statement by Lima Bean Farmer

I need clarification on how I would properly appeal a topic ban. According to Misplaced Pages:Contentious topics, after a year a topic ban in contentious topics wouldn’t need community review. However, what makes this complicated is that the initial topic ban was imposed by one administrator but a later appeal was decided by AE consensus. It is not clear what level of appeal or how I would go about removing the topic ban and would appreciate any clarification. Thank you in advance!

Statement by Tamzin

Commenting as closer of the appeal. I see the logic that an appeal's denial at AE is tantamount to a consensus-of-AE-admins sanction. However, that would create a perverse incentive not to appeal in the first year of an individually imposed sanction. Why appeal to AE at 11 months if a decline would strip you of your right to appeal to an individual admin at 12 months?

I think the only way to avoid that paradox is to say that declines only count as AE-consensus sanctions if the AE admins a) explicitly assume the action as a consensus action, and/or b) impose new, stricter sanctions in the course of declining. (Here, I imposed a new sanction with Dreamy's consent and other admins' support, but it was narrower than Dreamy's original.) -- Tamzin (they|xe) 07:43, 13 August 2024 (UTC)

Statement by Red-tailed hawk (Lima Bean)

Is it correct to read WP:CTOP as saying that more or less any admin can unilaterally undo any unilateral CTOP action on appeal provided that 1 year has passed? If so, it would be nice it it were more clear. — Red-tailed hawk (nest) 17:39, 13 August 2024 (UTC)

Statement by Dreamy Jazz

As far as I remember, this sanction is not subject to the 1 year rule because it was made before the switch to contentious topics. This is based on WP:CTOP#Continuity. As such, it needs to follow the rules as if it was a sanction made less than a year ago. Dreamy Jazz 08:06, 14 August 2024 (UTC)

@Primefac, given the appeal and subsequent modification was held at AE after the switch to contentious topics, does the modification of the topic ban now prevent it from being seen as a topic ban that is exempt from the 1 year rule?
I would argue that the topic ban modification doesn't necessarily change the 1 year rule exemption (unless I've missed something that's said in the document).Asking this to you specifically because you said this is now modifyable after a year and I don't know if this because you see the modification as removing the exemption to the 1 year rule or if the modification of the scope represents a entirely new sanction. I don't see this as a new sanction because in the WP:AELOG it is styled as a amendment of the scope and my original topic ban is not struck. Dreamy Jazz 08:11, 14 August 2024 (UTC)
As to whether an appeal should be granted from my point of view, I have not had a chance to review recent contributions so don't have an opinion at this time.
If my comment is desired on that, let me know and I should be able to do that next week. Dreamy Jazz 08:21, 14 August 2024 (UTC)
I've provided some thoughts at AE where an appeal has been filed. Dreamy Jazz 20:05, 17 August 2024 (UTC)

Statement by {other-editor}

Other editors are free to make relevant comments on this request as necessary. Comments here should opine whether and how the Committee should clarify or amend the decision or provide additional information.

Appeal methods for Lima Bean Farmer topic ban: Clerk notes

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

Appeal methods for Lima Bean Farmer topic ban: Arbitrator views and discussion

  • Declining an appeal at AE is not imposing a sanction, so the "no appeals" language does not apply, unless per #Appeals and amendments A rough consensus of administrators ... may specify a period of up to one year during which no appeals ... may be submitted. Per the procedural summary, then, it is appealable after a year and may be extended, but would not strictly require a consensus at AE to lift. Primefac (talk) 12:05, 13 August 2024 (UTC)
    I will have to re-review the issue; if the ban was in place before the switch to CTOP then it would probably fall under the old procedure but I will have to check. Primefac (talk) 10:43, 14 August 2024 (UTC)
    Per other comments, declining an appeal should not reset the clock or change the methods of appeal, but a significant modification or positive reaffirmation should do so. In this particular case, I agree with Tamzin's proposal to not consider this either of the latter two options as it narrowed the topic ban; once could almost consider it to be a partial lift of the original sanction. Primefac (talk) 13:20, 17 August 2024 (UTC)
  • As I noted to some of my colleagues recently, I miss ACDS sometimes (if I had to start somewhere, the cooler name ...). Anyways, my understanding of this is that as the AE topic ban (changing to post-1992) was carried out under the new contentious topics procedures, it superseded and replaced the old DS topic ban. As it was imposed at AE, the one-year rule does not apply and a formal appeal would need to be successful (ie consensuses at AE/AN or a motion here).On the broader policy question, I agree that declinations of appeals by themselves do not reset the clock, but since this appeal led to a new sanction being imposed, that is a material change in circumstances. @Red-tailed hawk: I feel like the procedure is relatively clear: only single-administrator sanctions and indefinite blocks can be undone in this manner (see Misplaced Pages:Contentious topics#Procedural summary too).I think that this status quo is okay, unless I've grievously misinterpreted things. There may be issues with interpreting whether something is narrower or broader than another sanction, which makes me think that changing it isn't necessary. Sdrqaz (talk) 13:31, 15 August 2024 (UTC)
  • @Red-tailed hawk: That is what the committee was trying to do, as someone who was very much in disagreement on this point. --Guerillero 12:50, 17 August 2024 (UTC)
    @Tamzin: That is probably the most logical way to cut the knot --Guerillero 12:52, 17 August 2024 (UTC)
  • I would hold that appeals still need to go to AE/AN; i.e., that they cannot be heard by any single administrator (without Dreamy's consent). That's because the one-year rule does not apply to the original sanction (under Misplaced Pages:Contentious topics § Continuity), and I would hold that the AE appeal narrowed the original sanction rather than imposed a new sanction. @Dreamy Jazz: if you don't have time to review this on the merits, you can if you want consent to other administrators changing the sanction on their own, under Misplaced Pages:Contentious topics § Changing or revoking a contentious topic restriction. Best, KevinL (aka L235 · t · c) 18:46, 17 August 2024 (UTC)
    This seems to be largely moot given that Lima Bean Farmer has appealed at AE. Does anyone (@Primefac and Guerillero: as folks who expressed a preference to possibly change the procedures) feel like we should keep this open to amend the procedures, in case this comes up again in the future? If not, I would suggest closing. Best, KevinL (aka L235 · t · c) 15:13, 19 August 2024 (UTC)
    I'm fine closing, I have a feeling that the number of individuals sanctioned under DS who are unsuccessful and have their appeal modified at AE will be steadily decreasing over time. Primefac (talk) 15:38, 19 August 2024 (UTC)

Amendment request: German war effort

Initiated by Cinderella157 at 03:16, 13 August 2024 (UTC)

Case or decision affected
German war effort arbitration case (t) (ev / t) (w / t) (pd / t)
Clauses to which an amendment is requested
  1. Misplaced Pages:Arbitration/Requests/Case/German war effort#Cinderella157 German history topic ban
List of any users involved or directly affected, and confirmation that all are aware of the request
Information about amendment request

Statement by Cinderella157

I simply ask the community ArbCom to review whether this ban continues to serve any reasonable purpose consistent with the prevailing WP:P&G. Cinderella157 (talk) 03:16, 13 August 2024 (UTC)

I have learnt to discern that some things are difficult to substantiate and are therefore better left unsaid. I am not a project coordinator and have no foreseeable aspirations to become one. Cinderella157 (talk) 02:07, 14 August 2024 (UTC)

ToBeFree, the absence of K.e.coffman is news to me. Cinderella157 (talk) 21:29, 17 August 2024 (UTC)

Responding to Sdrqaz

The sanction was imposed as a remedy for personal attacks against a particular editor. ArbCom determined that I could not substantiate particular allegations and that in consequence, these rose to being personal attacks. If I was inclined, I might have continued to make such attacks against the editor of record in areas unrelated to the Tban or despite the Tban. I have not. I submit, that ArbCom's determination that the editor of record had not engaged in misconduct was sufficient remedy to prevent further similar allegations/personal attacks.

As noted, I have been actively editing in several contentious topic areas, including the Russian invasion of Ukraine and Indo-Pakistani wars - areas known to foster editor misconduct an personal attacks. I have become more discerning in how I deal with perceived misconduct or whether I deal with it at all. Where I have had occasion to raise issues of conduct, I have been more discerning and circumspect as to how and where such matters are dealt with. My conduct in doing so has not been seen by the community as being personal attacks or otherwise inappropriate - certainly not rising to the level necessitating sanction. Cinderella157 (talk) 04:19, 17 August 2024 (UTC)

Comment by Newyorkbrad

As some of the arbitrators have noted below, it is the ArbCom rather than the broader community that would consider whether to terminate or modify one of ArbCom's own remedies. Given that Cinderella157 filed his appeal request on this particular page, it is likely that he was aware of this fact, and that his use of the term "community" either was simply inartful, or perhaps was meant as a suggestion that non-arb community members might wish to comment on his request. In any event, if he wasn't already aware of the proper procedure, he is now.

What would be needed next is some explanation of why Cinderella157 believes the sanction no longer serves a reasonable purpose. Simply saying so without a word of explanation will certainly not succeed. In making his case, I suggest he should also bear in mind that when the German war effort case was decided six years ago, none of the current arbitrators were on the Committee. Newyorkbrad (talk) 20:14, 13 August 2024 (UTC)

Statement by Euryalus

I was on the Committee during this case and this sanction has been bothering me somewhat. Some points:

  • The topic ban: It was proposed in case /Evidence that Cinderella157 could not edit WWII topics neutrally because they are an "apologist" for Nazi Germany (see this "Apologetics" section). This was a strong claim for which we should expect strong proofs. Unfortunately, very little evidence was then provided, with the principal diffs on topic neutrality being:
    • this disagreement re the qualifications of authors of a specific WWII history book;
    • this statement that historical re-enactment society volunteers might or might not all be sympathisers of the cause they re-enact; and
    • this evidence section by Cinderella157 which relevantly states: My position is that WP must find a middle ground in dealing with events of WW2 and particularly biographies IMO - that is, a position that does not glorify or apoligise (on the one hand) but which does not vilify without substance (in the case of individuals as opposed to the regime). I don't entirely agree with these sentiments but wouldn't describe them as worthy of a topic ban from WWII.
Perhaps reflecting the paucity of hard evidence, the Committee made no reference to these diffs in the Decision and no Finding of Fact regarding Cinderella157's neutrality in this topic.
  • Personal attacks: Separately, Cinderella157 make this comment during the case, which was correctly perceived as a personal attack on another editor. Evidence was also presented of a difficult relationship with that editor over a long period (see here and here. The Committee made a Finding of Fact on personal attacks here. I mention this because disruptive interpersonal relationships between editors in the same topic area can sometimes lead to disruption of the topic itself. However the normal responses to disruptive interpersonal relations or personal attacks are interaction bans or blocks. Neither was imposed in this case, and again given the passage of time it seems the issue has resolved. If a personal attack was made at some future point it would more appropriately be responded to with an i-ban or a block, rather than a topic ban from any specific set of articles.
  • Progress since the ban: Cinderella157 breached the topic ban once in 2019 and was blocked for 5 days. Since then have since made around 9,000 edits to military history articles, seemingly without issue. Their edit history and talkpages seem to suggest competent engagement with complex and controversial topics including the Russo-Ukrainian War, and no issues with apologetics or personal attacks.

Apologies if all this seems like a relitigation of the actual case. Fwiw I'm not an editor of WWII history and have never interacted with Cinderella157 or anyone else from this case in any other topic. I also don't doubt the sincerity of the editor who originally lodged this case, or their multiyear commitment to improving Misplaced Pages's coverage of this topic. Their evidence against some others, for example LargelyRecyclable was impeccable and justified the ban that we imposed.

The reason for posting the above re Cinderella157 is simply that this topic ban has stuck in my mind over several years as a sanction that probably didn't need to be made. So long as they didn't seem to care, neither did I. But now they've asked for it to be lifted it seemed reasonable to take a minute to support that request. -- Euryalus (talk) 07:35, 14 August 2024 (UTC)

To somewhat clarify the above: the principal point I'm making is that the topic ban was adopted as a misplaced response to a personal attack. There was no real evidence that Cinderella157 was unable to edit this topic neutrally. There's also no evidence of ongoing personal attacks. On these bases I've always considered this topic ban unnecessary and this ARCA was a good opportunity to say so. :)
Beyond that, agree its up to Cinderella157 to provide a more substantial justification for its removal than they currently have. -- Euryalus (talk) 00:46, 16 August 2024 (UTC)

Statement by Sir Kenneth Kho

I would support waiting for Coffman's statement for two weeks, but the reason is simply to provide all sides fair opportunity to be heard. However, if there must be an answer as to whether the "timing of the appeal has anything to do with Coffman's absence", it can't be anything other than a resounding no per WP:AGF. Sir Kenneth Kho (talk) 16:28, 17 August 2024 (UTC)

German war effort: Clerk notes

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

German war effort: Arbitrator views and discussion

  • I am as well. While I think it's reasonable to wait to hear from K.e.coffman, I don't think we need to delay making a decision by up to two weeks. - Aoidh (talk) 15:29, 18 August 2024 (UTC)

Motion: Cinderella157's topic ban suspended

Remedy 3C of the German war effort case ("Cinderella157 German history topic ban") is suspended for a period of six months. During the period of suspension, this topic ban may be reinstated by any uninvolved administrator, as an arbitration enforcement action, should Cinderella157 (talk · contribs) fail to adhere to any normal editorial process or expectations in the topic area. Appeal of such a reinstatement would follow the normal arbitration enforcement appeals process. After six months from the date this motion is enacted, if the topic ban has not been reinstated or any reinstatements have been successfully appealed, the topic ban will automatically lapse.

For this motion there are 10 active arbitrators. With 0 arbitrators abstaining, 6 support or oppose votes are a majority.
Majority reference
Abstentions Support votes needed for majority
0 6
1–2 5
3–4 4
Support
  1. Proposed based on a previous suspension motion that appears to have good language, as three arbitrators have expressed support for lifting or suspending the TBAN. Best, KevinL (aka L235 · t · c) 14:58, 19 August 2024 (UTC)
  2. Primefac (talk) 16:03, 19 August 2024 (UTC)
Oppose
Abstain
Arbitrator discussion
  • ...

Amendment request: Palestine-Israel articles (AE referral)

Initiated by Red-tailed hawk at 17:38, 17 August 2024 (UTC)

Case or decision affected
Misplaced Pages:Arbitration/Index/Palestine-Israel articles and related AE thread.
Clauses to which an amendment is requested
  1. Pursuant to WP:CTOP#Referrals from Arbitration Enforcement noticeboard to the full Committee, a recent Arbitration Enforcement thread has closed with instructions to refer the dispute to the full arbitration committee for final decision.


Lists of any users involved or directly affected, and confirmation that all are aware of the request
Involved AE participants
Other editors whose behavior was directly mentioned in the AE thread
Referring administrators
Confirmation that all parties are aware of the request
Information about amendment request
  • Throughout the discussion among administrators at AE, several sources of disruption were identified:
  1. Long-term slow-motion edit warring by a number of individuals within the Arab-Israeli conflict topic area.
  2. Long-term tag-team edit warring by several groups of individuals with the Arab-Israeli conflict topic area.
  3. The widespread nature of edit warring, battleground mentality, and POV pushing within the Arab-Israeli conflict topic area.
  4. The ineffectiveness of previous warnings within the topic area to stop the disruption.
  5. The inability of the tools available at AE to adequately handle disruption that involves a large number of parties over long periods of time.
Several suggestions were floated by administrators during the discussion, including the issuance of warnings to multiple individuals, the imposition of 0RR restrictions on either select individuals, or 0RR restrictions on large numbers of individuals coupled with select IBANs, TBANs, individual anti-bludgeoning restrictions, and topic-wide restrictions on the length of posts people make in discussions within this topic area. However, because the discussion broadly turned into a set of complex and multi-party complaints regarding behavior of multiple editors over long periods of time, a consensus was reached among administrators to refer the broader dispute to the arbitration committee.
— Red-tailed hawk (nest) 17:38, 17 August 2024 (UTC)


Statement by Red-tailed hawk (AE referral)

information Note: The arbitration amendment template limits how many individual I can initially add, so I will shortly be adding the rest of the admin and non-admin participants to the list above in their own section.

Additionally, as I can't find any prior examples of referrals by looking through the archive, I have tried to do my best here in light of the fact that this is a referral rather than a standard amendment request/appeal. Arbitrators should not hesitate to let me know if I have formatted this in an unexpected way.

— Red-tailed hawk (nest) 17:38, 17 August 2024 (UTC)

@Levivich: As should be more obvious now, it's everyone who contributed to the AE discussion. — Red-tailed hawk (nest) 17:48, 17 August 2024 (UTC)
@Levivich: There's currently a discussion over at WT:Arbitration/Requests#Template for referrals from AE around that topic. For completeness's sake, I included everyone in this one. Going forward, there might be some norm/convention, but I figured that it was better to incorporate everyone rather than potentially leave someone relevant out. — Red-tailed hawk (nest) 18:03, 17 August 2024 (UTC)
I do acknowledge that I left out several individuals whose behavior was directly mentioned, and I will fix that issue now. — Red-tailed hawk (nest) 18:07, 17 August 2024 (UTC)
@L235: Thank you for your comment. I think that a full case/case-like structure would be best, as that is the sort of thing that would allow for clear examination of the complex multi-party disputes that AE is not quite able to handle well. In my view, I don't think the topic-wide "please be brief in discussions" provision will be enough, as it isn't going to remedy the long-term edit warring/tag teaming, nor the civility issues that have driven away good faith editors from the topic area. In the event that a full case is opened, I agree that it is most appropriate to only have the individuals whose behavior is under examination to be considered as parties. But, before that list is finalized, we might want to have some space for the community to identify that sort of behavior—perhaps the section for statements in this thread? — Red-tailed hawk (nest) 19:01, 17 August 2024 (UTC)
I believe that it might be useful for some anti-bludgeoning sanction to incorporated into the discretionary sanctions available for administrators to dole out, but if so, I think it should look like one that the community has previously endorsed in a DS area. One such sanction is that which was imposed on NewImpartial, of no more than two comments per discussion per day, except replies (of reasonable length) to questions or very brief clarifications of their own comments.
I would hesitate to apply a 500 word limit in any discussion under 5000 words, and a 1000 word or 10% of the discussion limit, whichever is lower, on discussions over 5000 words topic-wide in a blanket fashion; I feel like this sort of thing would serve as a trap to good-faith newcomers who are verbose, and we needn't WP:BITE good-faith editors who are entering the topic more than already occurs. That being said, making it available as a discretionary sanction that could be applied by an admin would not cause the same issue with more or less auto-biting good-faith editors new to the area, and might be reasonable. — Red-tailed hawk (nest) 00:46, 20 August 2024 (UTC)

Statement by Levivich

Looking at the list of parties, those who have been sanctioned in this topic area have not been disruptive since their sanction, AFAIK. Most of the list have never been sanctioned. If there are concerns regarding anyone's behavior in the topic area, a filing at AE, ANI, ANEW, or some other noticeboard, should happen first, before an arbcom case. An arbcom case should only happen when (1) there are editors who want to present evidence to arbcom, and (2) community options have first been tried and failed (unless there's private evidence involved). Because these criteria are not met, the case request should be declined.

Limiting everyone in the topic area to 500-1000 words is a terrible idea. This topic area has more sources (see here or here for an idea of how many academic books have been published just in the last five years), and more sources that contradict each other, than almost any other topic area. Discussions about sources can't happen in 500-1000 words; the very notion is ridiculous. More to the point, any kind of topic-wide restriction would be a horrible, counterproductive overreach. The vast, vast majority of editors are doing nothing wrong.

Removing appeals to the community is not something arbcom can do, as that would require a change to WP:BANPOL, which arbcom cannot do.

I don't think the AEs I filed are particularly "complex" or "multi-party". I think they're straightforward, and each one can be judged on its merits without considering the actions of other parties. Of the 5 I filed, 1 ended in sanctions, 2 in warnings, no problems with those. The PeleYoetz one is still open and they just made their first comment there recently. I don't see any reason admins can't review that as with any other filing. If arbs want to review that filing instead of admins, seems like overkill, but OK. האופה hasn't edited since I filed the AE 8 days ago, so while arbs could review it, I see it as moot, and I don't think reviewing it would be a good use of anyone's time at this point.

There is nothing for arbcom to do here. People who are concerned about disruption in the topic area should raise it at one of the community noticeboards. A sprawling, unfocused case with lots of parties, is a terrible idea, as has been proven multiple times by past arbcoms, and this is especially true in the absence of any showing that the community is unable to handle this. The only thing worse would be a topic-wide sanction; please don't do that, I fear it would trigger a "constitutional crisis" and waste more editor time. Levivich (talk) 14:22, 19 August 2024 (UTC)

Statement by האופה

Statement by Bluethricecreamman

  • There seems to be constant RFCs and threads about the reliability of sourcing in this area. I know the current arbitration request is about long term edit warring, but there is also long-term campaigns in talk spaces to remove usage of certain sourcing. See the downgrading of the ADL, the current RFC in WP:RSN about Al Jazeera, etc. The downgrading of the ADL, in particular, caused significant media coverage for barely much difference in the status quo of average Wikipedian (from my understanding, we already had significant warnings about using ADL with attribution only when speaking about Israel Palestine, the change in status quo hardly meant much more than a media circus). Bluethricecreamman (talk) 18:58, 17 August 2024 (UTC)
  • In terms of reversion, the reversion limits are harder to understand in CTOP space, especially for more contentious arguments. A clarification of what the "base" article text is and what the contentious edit that is being reverted is would be useful. In my case on Genocide of indigenous peoples, there are still questions of how to apply WP:NOCONSENSUS vs WP:ONUS when a contentious edit (which probably should be removed by WP:ONUS) had been placed in text for long while (and therefore should remain by WP:NOCONSENSUS). Bluethricecreamman (talk) 19:11, 17 August 2024 (UTC)
  • Additional clarification on whether coordinated tag-team editwarring (i.e. WP:CANVASSED) or incidental tag-team editwarring should be treated similarly would be useful Bluethricecreamman (talk) 19:11, 17 August 2024 (UTC)
  • Going off of the suggestion from ScottishFR, for the limit of 500-1000 words, some of these RFC discussions go long. Instead of absolute limits that could unfairly limit discussion among the most passionate editors of the topic, would it be possible to go with proportional limits (no more than 500 words or 10% of comments, whichever is greater?), or limits per week (500 words per week?) In addition, I have questions if such a limit would apply to single RFC threads, or to the whole topic at once. Bluethricecreamman (talk) 19:15, 17 August 2024 (UTC)

Statement by ABHammad

I think we have arrived at a point where editing in this area is not just a battleground environment but an ex-territory of the project. I recognize that I, too, took part in this in the past, not out of desire but because I felt I had no choice when I saw the consistent POV pushing and disregard for policies and consensus. There’s probably a reason why Misplaced Pages is now maybe the only mainstream source to use terms such as Gaza genocide and Israeli apartheid (read the lead) with its own voice. Many disputed changes like this have been introduced through edit warring (check Zionism, now defined as looking for the “colonization of land outside Europe”), in spite of substantial opposition. The current situation both scares away potential great editors and destroys our credibility and neutrality.

The feeling is that a bunch of 5-10 experienced editors have taken dominance over the area. Much of their edit histories show a focus on promoting one side's POV and discarding the other. Although some problematic editing occurs on both sides, it should be noted that the extent of POV editing on articles about one side is only a fraction of what occurs on articles about the other. This situation is perpetuated as new good-faith editors trying to balance the content often face aggressive behavior such as strong CTOP messages from Selfstudier followed by inquiries how did they find this and that article, "previous accounts" questions from Nableezy, accusations of "gaming the system to achieve EC status" from Iskandar323 on noticeboards, and as we seen in the last month, unverified tag-teaming allegations from Levivich. Those who survive all of the above then find their user talk pages filled with allegations, insults and other kinds of personal attacks and aspersions. Even five edits in this topic area can provoke such reactions. WP:ONUS and WP:CONSENSUS are ignored - they are applied only to others. RfCs, AfDs, and RMs are manipulated through mass bludgeoning. They blame others for edit warring - but this is exactly what they are doing. Based on my experience with these editors over several months, I am afraid it would be naive to think that simply limiting word count in discussions would solve the problem. Looking over their logs, many of these editors already have a long history of warnings and short-term topic bans, so something else must be done this time. ABHammad (talk) 09:49, 20 August 2024 (UTC)

Statement by Selfstudier

1.There is another relevant recent related AE thread, Misplaced Pages:Arbitration/Requests/Enforcement/Archive336#Nishidani. Many of the editors here, including myself and several of the uninvolved administrators, were participants and the case revolved around behavior (and content) at the Zionism article and this same subject matter is a part of the current case, 6 Levivich diffs refer (in the last two statements).Selfstudier (talk) 22:55, 17 August 2024 (UTC)

2.This one as well (PeleYoetz). Editors named here continue to respond there. Although procedurally a separate AE case, it was filed contemporaneously with and is part and parcel of the related AE thread. Selfstudier (talk) 12:59, 18 August 2024 (UTC)

3.In the interim, avoiding this sort of thing or this would be as well. Selfstudier (talk) 22:14, 19 August 2024 (UTC)

Statement by fiveby

I don't think the referral of this particular case and the inclusion of the first two items listed as identified disruption dealing with edit warring necessarily means that AE can't deal with such or didn't in this instance. Just because the experiment blew up the lab does not mean it was a bad thing to try. Seemed like a reasonable request and a result of you need more evidence to demonstrate tag team editing seems reasonable, which everyone could have and maybe should have accepted and walked away from. fiveby(zero) 17:05, 18 August 2024 (UTC)

Statement by IOHANNVSVERVS

Statement by Sean.hoyland

Statement by Iskandar323

Statement by Dan Murphy

The "dispute" as defined here is "accounts on Misplaced Pages disagree about various things." In my case I have recently disagreed with a number of accounts about the history of Zionism. On the one hand, early zionists and historians of zionism describe it as a colonial project of settlement. On the other hand, some wikipedia accounts really don't want the article here to describe it as such. Many of those accounts have turned out to be sockpuppets of previous accounts long banned from this area. I'd be shocked if the Peleyoetz account named in this report isn't one, too . The abuse of sockpuppets is a powerful advantage at Misplaced Pages, and wooden enforcement of teh rulz about conduct, ignorant of content and context, a powerful disincentive to being honest and straightforward.

No matter. This unfocused, throw everything at the wall and see what sticks request, is a bad idea.Dan Murphy (talk) 13:06, 18 August 2024 (UTC)

Statement by Nableezy

My view is that if this is to be an arbitration case that it should be pretty wide, and not just the four editors Barkeep named. The tendentious editing, including obvious examples of canvassing and off-wiki coordination, in this topic area stretches well beyond those four names, and I don’t think looking at four editors in a vacuum in this, or any other topic where the temperature in the real world is beyond mildly warm, is all that productive. I’m well aware of the committees past rulings on standards of behavior, but I for one am unable to understand how anybody can think a topic like this, where the real world conflict it is covering contains accusations of ongoing crimes against humanity up to and including rape as a weapon of war, mass indiscriminate killings, and genocide is going to remain calm cool and collected. nableezy - 01:51, 18 August 2024 (UTC)

Statement by BilledMammal

There are a significant number of issues in this topic area that it is likely only ARBCOM can address, including:

  1. POV pushing
    Including both editors switching their stance to conform to their POV (for example, supporting using massacre as a descriptive term only when Israelis were targeted, or only when Palestinians were targeted) and editors misrepresenting sources.
  2. Stealth canvassing
  3. Incivility
    Occasional lapses are forgivable, but it has become common for editors to ignore the fourth pillar. This drives editors away from the topic area, worsening issues with POV pushing and stealth canvassing.
    The only way the topic area can be fixed is by fixing this.
  4. Bludgeoning
    See Bludgeoning statistics for an assessment of the extent of the problem. For technical reasons, it is currently limited to discussions on article talk pages and at RSN.

BilledMammal (talk) 09:41, 19 August 2024 (UTC)

Regarding ScottishFinnishRadish's word limit proposal, I don't think that will have the desired result. Editors are often required to review a wide array of sources, such as when attempting to determining if a viewpoint is in the majority or what the WP:COMMONNAME is, and a word limit will impede this. This will in turn worsen one of the other issues in the topic area, POV pushing.
Instead, I think a comment limit - perhaps ten comments per discussion - will be more effective at preventing the back-and-forth and repetition of points that causes discussions to expand unproductively. BilledMammal (talk) 13:12, 19 August 2024 (UTC)

Statement by Zero0000

I object to being listed here. I did nothing that should cause it, but RTH refused to remove me. But now that I'm here, I'll say that I don't see any suggestions so far that would make an improvement to the I/P area. Here are some points:

  • If any restrictions are imposed on the area, they should apply to everyone and not to some arbitrary list like this one. One of the notable things about the I/P area in the past several months is the remarkable number of new and revived accounts that have joined in, mostly on one side of the equation and many with scant knowledge of the subject. Quite a lot of the disputes arise because of them, not because of the people likely to comment at AE.
  • Imposing a limit on contributions that consists of a word limit or edit limit will cause delight to the tag teams, who will take full advantage of their combined greater limit.
  • Some types of discussion such as a negotiation between two editors should not have a limit at all. Also, in general there is no way to define "a discussion" except in the case of formal discussions like RfCs. The main points of dispute are brought up repeatedly and don't have clear boundaries. This means that a limit on "discussions" will just produce a lot of arguments over whether something was part of the same discussion or part of a different discussion.
  • Bludgeoning does not mean making a lot of edits. Replying to everyone who makes a contrary comment is bludgeoning, but repeatedly bringing new reliable sources is called good editing.

Here is something that will improve the atmosphere of formal discussions (RMs, RfCs, AfDs, etc): Require everyone to stick to their own statement, regardless of how many times they add to it (like at AE). This will eliminate 90% of bludgeoning right away. For RfCs: one statement in the !votes section and one statement in the Discussion section. Zero 09:44, 20 August 2024 (UTC)

Statement by ScottishFinnishRadish

There is a broad array of disruptive editing, POV pushing, long term edit wars, bludgeoning, incivility, and it all basically comes down to WP:BATTLEGROUND. I've done my best to take care of all of the obvious cases that won't have to set aside a dozen hours of time to deal with, but much of the behavior is by editors with numerous prior warnings and sanctions but that topic banning, interaction banning, and blocking is not a simple matter. Most AE reports in the topic area involve behavior that is widespread among many parties, and picking out a single party for sanctioning and allowing other editors to continue the behavior isn't how enforcement should be working.

If Arbcom does wish to avoid a full case or "punt", as Barkeep puts it, there are a couple actions they can take to help out in the interim.

  • As a sanction across the topic area, or added to the standard set of CTOP enforcement mechanisms available to administrators on a per editor or per discussion sanction, a 500 word limit in any discussion under 5000 words, and a 1000 word or 10% of the discussion limit, whichever is lower, on discussions over 5000 words. This should be done immediately, even if a case is accepted.
  • Any appeals of sanctions by editors previously warned or sanctioned in ARBPIA should be handled by Arbcom to take pressure off individual administrators. Arbcom discussions have clerks to handle word limits, aspersions, and other disruptive editing. Arbcom can simply vote on if the sanction was a reasonable exercise of administrator discretion. This would hopefully cut down significantly on 0.3 tomats discussions at appeals, and put those decisions in the hands of the people the community elected to make them. (Hat tip to Red-tailed hawk, who came up with this.)

As for a party list, anyone who has made, been the subject of, or commented at any ARBPIA AE report since October 2023. The problem is widespread, and I think that is probably the most efficient way to generate a party list. ScottishFinnishRadish (talk) 12:29, 19 August 2024 (UTC)

Levivich, that part of BANPOL is just quoting Arbitration procedure, it can be changed by Arbcom. ScottishFinnishRadish (talk) 15:15, 19 August 2024 (UTC)

Statement by Barkeep49

Re:L25: I didn't support moving this here because I was looking for an ArbCom only remedy as I felt we had whatever options we wanted on the table per the Contentious topic procedures A rough consensus of administrators at the arbitration enforcement noticeboard ("AE") may impose any restriction from the standard set and any other reasonable measures that are necessary and proportionate for the smooth running of the project. (emphasis added) I supported coming here because I think AE is ill-suited to a multi-party sprawling request like this. I actually think האופה is the least important party here in most ways and if the thread had stayed constrained to them a rough consensus would have been found. Instead, the discussion ballooned to potential misconduct by multiple other editors. For me the editors whose conduct needs examining would be BilledMammal, Iskandar323, Nableezy, and Selfstudier and I think ArbCom should review, and hopefully endorse, the work SFR has been doing as an uninvolved administrator given the concerns at least one of the parties (Nableezy) has raised about that work. Additionally, I think Levivich has been promoting, in this and some other recent AE reports, claims of misconduct based on tagteaming/edit warring that I personally don't find convincing (even if the same conduct does show other misconduct I do find convincing, namely a battleground mentality) but which ArbCom is better positioned to examine both because it can do so comprehensively, rather than in a series of one-off AE requests, and because of the authority ArbCom has to interpret existing policy and guidelines, recognise and call attention to standards of user conduct. Barkeep49 (talk) 19:55, 17 August 2024 (UTC)

I guess I should add one thing. If this ArbCom can't do the review of editor conduct well, and given that this is the committee with the biggest issues with activity among arbs of any 15-member arbcom in at least a decade it may decide it doesn't have the capacity to do this well, I'd suggest it find a way to "punt" that decision, instead focusing on whether or not it agrees with Levivich's interpetation of tag-teaming/edit warring. I say this based on comments members of the 2019 committee (a 13-member committee which is the only one to have a bigger activity problem than this committee) have made around their inability to give PIA4 and Antisemitism the full attention they deserved. In the latter case this then blew up into a much bigger case (WP:HJP). Barkeep49 (talk) 20:09, 17 August 2024 (UTC)
@Z1720 your "magical incantation" comment confuses me. Where did SFR say it was confusing how to refer? I've raised the issue that the mechanics of referring need work, but I don't think AE admins need to be told to bold vote something in order to find consensus to refer. All 4 uninvolved admins - with 4 uninvolved admins being a lot of admins these days - agreed to refer, and all 4 were (as best as I can tell) clear about what each other thought as opinions evolved, so it's not like it was a puzzle what was happening to the uninvolved admins and since other commenters gave feedback on whether or not to refer I don't think it was a puzzle to anyone else either. Barkeep49 (talk) 14:45, 19 August 2024 (UTC)
@Z1720 so you're saying the answer I gave is incorrect? If so mark me as surprised but glad for your clarification. I will eagerly await to see if a rough consensus of other arbitrators agree with you and presuming they do adjust my actions accordingly. Barkeep49 (talk) 15:09, 19 August 2024 (UTC)
@Z1720 thanks for that clarification. I want to understand this second parth. Am I correct that you're saying that if the 4 uninvolved administrators had all bolded refer to Arbcom no further action would have been needed as ArbCom (arbs/clerks) would do the rest of the steps? If so that is definitely easier than the answer I gave (close with a rough consensus to refer by an uninvolved admin, uninvolved admin files a case request here, and notifies all interested editors) and so I will happily take advantage of it going forward. Barkeep49 (talk) 15:34, 19 August 2024 (UTC)
Regarding Levivich's statement: even beyond what SFR pointed out (BANPOL is quoting Arbitration Procedures), I think Levivich operates under a fundamental misconception about AE. Levivich seems to view AE as a community forum, where as I feel it is, as the name of Arbitration Enforcment suggests an Arbitration Committee forum. Further, the sanctions being handed out are being done under Arbitration Committee authority, not community authority. As such under the Arbitration and Consensus policies, the Committee can do what it feels best including mandating that all appeals in this topic area are heard by it rather than AE. As to the substance of the SFR's suggestions, I'm not sure the committee wants to hear all appeals, but if it thinks SFR's idea is a good one I would suggest it limit itself to either or both of: appeals of recent sanctions (<3 or <6 months) and appeals stemming from an AE report (regardless of whether it is actioned by an inidivudal administrator or a rough consensus). I think giving uninvolved administrators the ability to use the tools available in Iranian politics to moderate discussions (not just RfCs) may or may not work, but would feel like something that could potentially be productive to stem issues without doing a full case and thus is perhaps worth trying. Barkeep49 (talk) 15:29, 19 August 2024 (UTC)

Statement by Theleekycauldron

@L235: I agree with Barkeep that this should be a full case. But Red-tailed hawk is right on his list of parties – this is a sprawling case where basically all of the regulars in the topic area have worked together to create a hostile battleground that AE hasn't been able to resolve. Not because of a lack of authority, but because of the complexity of the case combined with the standard unblockables problem. theleekycauldron (talk • she/her) 20:10, 17 August 2024 (UTC)

Statement by PeleYoetz

Statement by TarnishedPath

I understand that the list of participants is everyone who was involved in a particular AE discussion or who was mentioned in that discussion. My editing in the topic area is limited, with a limited number of articles on my watchlist. I don't intend on following this closely. If my participation is desired at any point please ping me, presuming the case goes ahead. TarnishedPath 22:28, 17 August 2024 (UTC)

Statement by Nishidani

Statement by DMH223344

Can someone explain to me what this is all about? Specifically, how is this AE related to the previously closed one? And what am I being asked to do here?

Statement by M.Bitton

Statement by Buidhe

I really don't want to be involved in this business, but while there is a lot of suboptimal behavior in this topic area, it amazes me some of what can be described as an "edit war" or sanctionable conduct. If these standards were enforced across the board to all editors regardless of their content contributions and all topic areas, I'm quite convinced that there would not be much of an encyclopedia. I realize that Arbcom tries to clinically separate content and conduct, but IMO one should not lose sight of the goal of the entire project. And while productive, good faith editors can be driven away from contributing due to battleground behavior and general nastiness, it's also true that they can be driven away by excessive rules and (the fear of) overzealous ban-hammers. I do believe that editors who actually work on creating an encyclopedia should be distinguished from people who just show up to revert or argue on talk pages. (t · c) buidhe 01:51, 18 August 2024 (UTC)

Statement by Vanamonde

I saw several reports at AE that mentioned tag-teaming as a concern. I did not find anything actionable in the ones I investigated, but I agree with BK49 above that AE is less well-placed to investigate a sprawling multi-party dispute where the behavior of multiple editors may be of concern, than the behavior of a single editor. So I believe ARBCOM should look into this. In doing so, however, I encourage ARBCOM not to narrowly constrain which editors' behavior will be considered. AE is able to deal with the behavior of single editors. What ARBCOM needs to look at is whether the outcome of editors working together is actionably disruptive where any individual's actions in isolation may not be. I also encourage ARBCOM not to take a narrow view of what constitutes conduct. Mis-representing a source is, in my view, just as bad - and possibly worse for Misplaced Pages's long-term credibility - than any civility issue. It shouldn't be ignored just because it is easier to police language, though I am in no way suggesting that the expectations for collegial language be ignored. Vanamonde93 (talk) 17:48, 18 August 2024 (UTC)

  • If this weren't very clear from my statement above, I don't think this ought to be handled by motion. The issues here aren't simple; they need to be disentangled with care. If civility and edit-warring were the only problems, we wouldn't need ARBCOM. We need an evidence phase, and for ARBCOM to dig into whether editors are editing within all the PAGs, not just the ones easy to assess. I also think it would be a mistake for ARBCOM to handle all the appeals. We shouldn't be spending the limited resource that is ARBCOM's time on appeals that aren't complicated. Vanamonde93 (talk) 21:03, 19 August 2024 (UTC)

Statement by Tryptofish

I generally avoid editing in this topic area, and my involvement in it has been fairly minimal. But the one instance when I did get involved with it (), led me to find the editing environment disturbingly toxic, and not due to some simple problem with a small number of easily identified editors. Rather, it felt like a fairly large number of experienced editors, together, were acting in a way inconsistent with a CTOP subject. That strikes me as something that AE is poorly equipped to deal with. And it fits exactly with the concept that ArbCom should accept cases where the community has tried, but been unsuccessful, to resolve. So I recommend that ArbCom accept this case, and do so with a large number of named parties. --Tryptofish (talk) 21:02, 18 August 2024 (UTC)

(Added after some other editors have kindly said that they agree with me; I don't know if they will agree with what follows.) ArbCom should know that the problems with "the usual suspects" that cannot be handled by AE generally do not fall along the expected POV fault-lines of Israeli versus Palestinian POVs, or antisemitism or Islamophobia. (I'm sure there are POV pushers like that, but they can be handled at AE.) If anything, there's a divide between different lines of Jewish thought, with the most problematic editors favoring WP:RS-compliant scholarly work by largely-Jewish academics, but doing so with a massive-scale disregard for the ArbCom principle of WP:BRIE, and some other editors (sometimes more crudely) finding such source material to be contrary to popular political opinion. In my experience, getting caught in the middle of that can be quite unpleasant. --Tryptofish (talk) 23:18, 19 August 2024 (UTC)

Statement by AirshipJungleman29

I echo the comments of Tryptofish, Vanamonde93 and SFR. The topic area features a large number of experienced editors who have, whether consciously or not, decided to ignore CTOP protocols. This not only has the effect of turning the entire topic into even more of a WP:BATTLEGROUND than it needs to be, but also negatively affects the experiences and habits of newer editors who follow the combative, actively hostile methods of those they look up to. Editors of all sides appear to have an unspoken agreement that civility shouldn't really matter when discussing such controversial subject matter (e.g. nableezy's statement above). This is unacceptable. I strongly endorse implementing the actions outlined by SFR as immediate remedies. ~~ AirshipJungleman29 (talk) 12:51, 19 August 2024 (UTC)

Statement by Aquillion

I do urge ArbCom to particularly investigate the accusations of misrepresenting sources (an extremely serious one that takes time and effort to get to the bottom of) and of people taking inconsistent policy positions (a key component mentioned in WP:CIVILPOV, which is rarely enforced) as well as the battleground / aspersion / WP:AGF issues mentioned above. The edit-warring is important and is easy to see (hence why so many cases focus on it), but if that was enough to resolve this then we wouldn't be at ArbCom. The root cause is battleground mentalities and civil POV-pushing; misrepresenting sources and taking inconsistent policy positions point much more directly to that problem. (And, of course, I also urge people to present evidence to those things in the evidence phase, if it gets to that point, because ArbCom needs that - my past experience with cases like these is that both editors and ArbCom tend to focus on the "easy" aspects of WP:CIVIL and WP:EW, ignoring the underlying causes or more complex aspects.) --Aquillion (talk) 18:09, 19 August 2024 (UTC)

Statement by Swatjester

Tryptofish's experience here echoes mine. The tendentiousness, bludgeoning, and sealioning behavior from these battleground editors makes it exhausting and frustrating for non-battleground editors to participate. In any event, I see the "usual suspects" attempting to downplay or deny that there's any dispute, in contrast to the uninvolved parties saying, essentially: "It's you: you're the problem." I think that's rather telling. ⇒SWATJester 18:53, 19 August 2024 (UTC)

Statement by Number 57

I edit around the edge of this topic area, focussing on Israeli politics and civil society, and have had the misfortune over the years to have ended up in disputes with editors pushing both anti-Israel and pro-Israel POV on articles where our paths corss. I very much welcome the suggestion that long-term tag-teaming, POV pushing and the ineffectiveness of current tools to stop this should be looked at. From my nearly 20 years' experience, the main issue has always been that there is a core group of 10-15 editors in this topic area (many of whom have been with us for well over a decade) who are primarily on Misplaced Pages to push their POV – anyone can look at their contribution histories and see that their contributions are primarily adding things that make their side look good/the other look bad and deleting information to the contrary; in discussions such as RMs, RfCs or AfDs, their stances are easily predicted based on their editing history. A further issue is that for most of the last two decades the two sides have been seriously mismatched in terms of numbers and one side has been consistently able to push their POV through weight of numbers, either by long-term tag teaming or by swinging poorly-attended discussions (and in my view the 30/500 restriction has actively worsened this situation by giving the long-term problematic editors an advantage). Number 57 19:28, 19 August 2024 (UTC)

Statement by The Kip

Not to sound repetitive, but I'll echo the comments of Tryptofish, AirshipJungleman29, and Swatjester. I dabbled in editing within the topic area some months back, but quickly opted to mostly stay away - since December or so, my related editing has only been in the Current Events portal/ITNC and various admin/arbitration noticeboards. This pivot was due to the absurd levels of incivility, condescension, POV-pushing, bludgeoning, edit-warring, hypocrisy, and virtually every other type of WP:BATTLEGROUND editing humanly possible, from a core group of editors that perennially show up to scream at each other in every discussion; there's a level of toxicity that just makes me want to ignore the area entirely. This BATTLEGROUND issue is only compounded by the fact that virtually all of the culprits are WP:UNBLOCKABLE - they wholly disregard WP policies and prior warnings/sanctions, as most ARBPIA sanctions for experienced editors have effectively amounted to slaps on the wrist. I'd also like to specifically emphasize the point made by Swatjester of I see the "usual suspects" attempting to downplay or deny that there's any dispute, as from both sides of the POV-war, there's a near-constant attitude of "my side is doing nothing wrong, if we just sanctioned the POV-pushers everything would be fine," rather than any introspection on the absolutely toxic environment created by nearly all participants.

In short, I strongly endorse both an Arbcom case and SFR's suggested remedies. I will openly disclose that I openly endorse nuking the topic area's userbase via mass TBANs, as I don't think starting from scratch could make things any worse than they currently are - that said, I understand that's a rather draconian/heavy-handed solution. The Kip 22:25, 19 August 2024 (UTC)

With regards to the core group/"usual suspects" claim, I'd also like to link this chart gathered by @Thebiguglyalien: some months ago for a different arb case. Some of the more active users noted on that chart are now TBANned, but it still serves as a solid chunk of data for the mass-scale POV-warring in the area. The Kip 22:37, 19 August 2024 (UTC)
I'd also like to say I politely disagree with Tryptofish's assessment of the main area of conflict; while that is a dispute in the area, and as they say, a particularly nasty one, I think the main issue is indeed the Israeli vs Palestinian POV-warring. While AE could in theory deal with that, in practice it's been reluctant to for one reason or another - many of the experienced editors in question often straddle a line of problematic behavior that AE has seemed unwilling to definitively bring down the hammer on (hence my WP:UNBLOCKABLE concerns mentioned above), and that Arbcom may be more open to conclusively dealing with. As a result of AE's apparent higher threshold needed for experienced editors, things like civil POV-pushing, bludgeoning, weaponization of process, less "blatant" incivility, and so on are difficult to definitively sanction - you have to badly cross multiple lines to receive anything more than a logged warning that is almost always disregarded by the receiver in the long run.
That's not even to mention the specific reasons why this case was primarily brought here (in my understanding), that being AE is mainly intended to be an A reporting B case forum. When the issue at hand is tag-teaming, multi-party edit warring, multi-party incivility, etc, AE's not too well-equipped to deal with a case where A and B want to report C, D, and E, except A and B have also been engaging in the reported behavior themselves, and F probably was too but wasn't brought to the case until later due to a variety of reasons. The Kip 00:14, 20 August 2024 (UTC)

Statement by Zanahary

It’s a small group of editors making this topic area hell for editors and a headache (I’d imagine) for administrators. I used to involve myself heavily in this topic area, and it’s the only such area where I’ve witnessed personal attacks, bullying, glaring dishonesty and hypocrisy in defense of violation of WP policy, and an apparent policy of assuming bad faith from anyone whom you believe you’ve sussed out to disagree with you go totally unpunished and be downright normalized—and it’s mostly coming from a handful of dominant editors. Something’s gotta give, and if that’s a rain of topic bans, then so be it. I see a few names listed that I believe do little more here than worsen the project. ꧁Zanahary꧂ 23:26, 19 August 2024 (UTC)

Statement by Ravpapa

Once an active editor in this topic area, I have for the last few years assiduously eschewed any involvement. But I would like, nonetheless to add this comment:

I think we are all looking at the wrong thing. We are discussing editor behavior, but we should be looking at the quality of the articles in the topic area. And, I think we can all agree, the articles are abysmal. They are bloated with polemics, they magnify ephemeral new items into international crises that change the course of history, they are often so full or quotes and counterquotes that they are practically unintelligible.

Will massive topic bans make the articles better? I doubt it. With the Middle East conflict, we have exceeded the limits of the possible with a cooperative open editing model, and we need to think of some other way to approach articles in this area. --Ravpapa (talk) 05:47, 20 August 2024 (UTC)

Statement by {other-editor}

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 (AE referral): Clerk notes

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

Palestine-Israel articles (AE referral): Arbitrator views and discussion

  • Thank you to the AE admins for submitting this referral. As a procedural note I would suggest that we limit the parties to this request to האופה and other users whose behavior is under consideration here (perhaps the editors listed under "Other editors whose behavior was directly mentioned in the AE thread", though even that list may be too long). @האופה: It would be quite helpful to have your perspective here. I would also appreciate hearing further from the uninvolved admins as to what you'd like ArbCom to do — I see two buckets of possibilities: (1) Hold a full case or case-like structure to resolve the complex multiparty questions here, and/or (2) Remedies that only ArbCom can impose (e.g. Maybe even everyone is limited to 500-1000 words in any ARBPIA discussion. as ScottishFinnishRadish suggests). Best, KevinL (aka L235 · t · c) 18:39, 17 August 2024 (UTC)
  • After reading the AE thread and the above statements, I think ArbCom will need to take some sort of action. I agree with L235 that I would like admins, both those involved in the AE and those that were not, to comment on whether it should be a full case or, if we are to resolve by motion, describe what ArbCom should enact to help admin find solutions to editor conduct issues. In response to how to refer a case to AE: instead of a magical incantation suggested by SFR, an admin can use a bolded vote at the beginning of a statement (something like "Refer to ArbCom", in bold) or as was done here, an uninvolved admin can determine that action as the consensus of the admin conversation. Z1720 (talk) 14:40, 19 August 2024 (UTC)
  • @Barkeep49: A bold vote isn't necessary, but it is an option. Since the question came up at AE here (in a humourous context that I chuckled at), and referrals to ArbCom from AE have not been common, I wanted to make sure there was clarification. Z1720 (talk) 15:07, 19 August 2024 (UTC)
I agree that action from ArbCom is necessary, and having reviewed everything over the past couple of days, looks like it may need to be a full case based on the complexity of the issue. - Aoidh (talk) 23:26, 19 August 2024 (UTC)
Categories: