A request for arbitration is the last step of dispute resolution for conduct disputes on Wikipedia. The Arbitration Committee considers requests to open new cases and review previous decisions. The entire process is governed by the arbitration policy. For information about requesting arbitration, and how cases are accepted and dealt with, please see guide to arbitration.

To request enforcement of previous Arbitration decisions or discretionary sanctions, please do not open a new Arbitration case. Instead, please submit your request to /Requests/Enforcement.

This page transcludes from /Case, /Clarification and Amendment, /Motions, and /Enforcement.

Please make your request in the appropriate section:

Request a new arbitration case
Request clarification or amendment of an existing case
This includes requests to lift sanctions previously imposed
Request enforcement of a remedy in an existing case
Arbitrator motions
Arbitrator-initiated motions, not specific to a current open request

Arbitration Committee proceedings

Case requests

Currently, there are no requests for arbitration.

[edit]

Open cases

Case name	Links	Evidence due	Prop. Dec. due
Palestine-Israel articles 5	(t) (ev / t) (ws / t) (pd / t)	14 Dec 2024	04 Jan 2025

[edit]

Recently closed cases (Past cases)

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

Clarification and Amendment requests

Currently, no requests for clarification or amendment are open.

Arbitrator motions

Motion name	Date posted
Arbitrator workflow motions	1 December 2024

Requests for arbitration

Requests for clarification and amendment

Use this section 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!)

Choose one of the following options and open the page in a new tab or window:
- Click here to file a request for clarification of an arbitration decision or procedure.
- Click here to file a request for amendment of an arbitration decision or procedure (including an arbitration enforcement action issued by an administrator, such as a contentious topics restriction).
- Click here to file a referral from AE requesting enforcement of a decision.
- Click here to file a referral from AE appealing an arbitration enforcement action.
Save your request and check that it looks how you think it should and says what you intended.
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.
Add the diffs of the talk page notifications under the applicable header of the request.

Clarification and Amendment archives

1	2	3	4	5	6	7	8	9	10	11	12	13	14	15	16	17	18
19	20	21	22	23	24	25	26	27	28	29	30	31	32	33	34	35	36
37	38	39	40	41	42	43	44	45	46	47	48	49	50	51	52	53	54
55	56	57	58	59	60	61	62	63	64	65	66	67	68	69	70	71	72
73	74	75	76	77	78	79	80	81	82	83	84	85	86	87	88	89	90
91	92	93	94	95	96	97	98	99	100	101	102	103	104	105	106	107	108
109	110	111	112	113	114	115	116	117	118	119	120	121	122	123	124	125	126
127	128	129	130

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 Wikipedia, 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-llists.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 Wikipedia: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

Arbitrators and clerks may summarily remove or refactor discussion without comment.
Requests from blocked or banned users should be made by e-mail directly to the Arbitration Committee.
Only arbitrators and clerks may remove requests from this page. Do not remove a request or any statements or comments unless you are in either of these groups.
Archived clarification and amendment requests are logged at Wikipedia:Arbitration/Index/Clarification and Amendment requests. Numerous legacy and current shortcuts can be used to more quickly reach this page:

Shortcuts:

Clarification and Amendment archives

1	2	3	4	5	6	7	8	9	10	11	12	13	14	15	16	17	18
19	20	21	22	23	24	25	26	27	28	29	30	31	32	33	34	35	36
37	38	39	40	41	42	43	44	45	46	47	48	49	50	51	52	53	54
55	56	57	58	59	60	61	62	63	64	65	66	67	68	69	70	71	72
73	74	75	76	77	78	79	80	81	82	83	84	85	86	87	88	89	90
91	92	93	94	95	96	97	98	99	100	101	102	103	104	105	106	107	108
109	110	111	112	113	114	115	116	117	118	119	120	121	122	123	124	125	126
127	128	129	130

Motions

Shortcuts

This section can be used by arbitrators to propose motions not related to any existing case or request. Motions are archived at Wikipedia:Arbitration/Index/Motions.

Only arbitrators may propose or vote on motions on this page. You may visit WP:ARC or WP:ARCA for potential alternatives.

Make a motion (Arbitrators only)

You can make comments in the sections called "community discussion" or in some cases only in your own section. Arbitrators or clerks may summarily remove or refactor any comment.

Arbitrator workflow motions

Workflow motions: Arbitrator discussion

I am proposing these three motions for discussion, community input, and a vote. Each seeks to improve ArbCom's functioning by providing for the performance of basic administrative responsibilities that sometimes go neglected, which, in my opinion, if successful, would significantly improve ArbCom's overall capacity.
Motivation: We've known about the need for improvements to our workflow and capacity for some years now – I wrote about some of these suggestions in my 2022 ACE statement. It's a regular occurrence that someone will email in with a request or information and, because of the press of other work and because nobody is responsible for tracking and following up on the thread, we will let the thread drop without even realizing it and without deciding that no action is needed. We can each probably name a number of times this has happened, but one recent public example of adverse consequences from such a blunder was highlighted in the Covert canvassing and proxying in the Israel-Arab conflict topic area case request, which was partially caused by our failure to address a private request that had been submitted to us months earlier.
Previous efforts: We've experimented with a number of technological solutions to this problem during my four years on the Committee, including: (a) tracking matters on a Trello board or on a private Phabricator space; (b) tracking threads in Google Groups with tags; (c) requesting the development of custom technical tools; (d) reducing the appeals we hear; and (e) tracking appeals more carefully on arbwiki. Some of these attempts have been moderately successful, or showed promise for a time before stalling, but none of them have fully and fundamentally addressed this dropping-balls issue, which has persisted, and which in my opinion requires a human solution rather than just a technological solution.
Rationale: The work we need done as framed below (e.g. bumping email threads) isn't fundamentally difficult or sensitive, but it's essential, and it's structurally hard for an active arbitrator to be responsible for doing it. For example, I could never bring myself to bump/nag others to opine on matters that I hadn't done my best to resolve yet myself. But actually doing the research to substantively opine on an old thread (especially as the first arb) can take hours of work, and I'm more likely to forget about it before I have the time to resolve it, and then it'll get lost in the shuffle. So it's best to somewhat decouple the tracking/clerical function from the substantive arb-ing work.
Other efforts: There is one more technological solution for which there was interest among arbitrators, which was to get a CRM/ticketing system – basically, VRTS but hopefully better. I think this could help and would layer well with any of the other options, but there are some open questions (e.g., which one to get, how to pay for it, whether we can get all arbs to adopt it), and I don't think that that alone would address this problem (see similar attempts discussed above), so I think we should move ahead with one of these three motions now and adopt a ticketing system with whichever of the other motions we end up going with.
These three motions are the result of substantial internal workshopping, and have been variously discussed (as relevant) with the functionaries, the clerks, and the Wikimedia Foundation (on a call in November). Before that, we held an ideation session on workflow improvements with the Foundation in July and have had informal discussions for a number of years. I deeply appreciate the effort and input that has gone into these motions from the entire committee and from the clerks and functionaries, and hope we can now pass one of them. Best, KevinL (aka L235 · t · c) 18:28, 1 December 2024 (UTC)[reply]

Motion 1: Correspondence clerks

The Arbitration Committee's procedures are amended by adding the following section:

Correspondence clerks

The Arbitration Committee may appoint, from among the English Wikipedia functionary corps (and preferably from among former members of the Arbitration Committee), one or more users to be correspondence clerks for the Arbitration Committee. Correspondence clerks must meet the Wikimedia Foundation's criteria for access to non-public personal data and sign the Foundation's non-public information confidentiality agreement.
Correspondence clerks shall be responsible for assisting the Committee in the routine administration and organization of its mailing list and non-public work in a similar manner as the existing arbitration clerks assist in the administration of the Committee's on-wiki work.
The specific responsibilities of correspondence clerks shall include:

Acknowledging the receipt of correspondence and assigning tracking identifiers to pending requests and other matters;

Tracking the status of pending matters and providing regular updates and reminders on the status of the Committee's off-wiki work to arbitrators;

Reminding members of the Committee to vote or otherwise take action in pending matters;

Organizing related correspondence into case files; and

Providing similar routine administrative and clerical assistance to the Arbitration Committee.

The remit of correspondence clerks shall not include:

Participating in the substantive consideration or decision of any matters before the Committee; or

Taking non-routine actions requiring the exercise of arbitrator discretion.

To that end, upon the first appointment of correspondence clerks, the current arbcom-en mailing list shall be renamed to arbcom-en-internal, which shall continue to be accessible only by arbitrators, and a new arbcom-en email list shall be established. The subscribers to the new arbcom-en list shall be the arbitrators and correspondence clerks.
The Committee shall establish a process to allow editors to, in unusual circumstances following a showing of good cause, directly email a mailing list accessible only by arbitrators and not by correspondence clerks.
All correspondence clerks shall hold concurrent appointments as arbitration clerks and shall be subject to the same requirements concerning conduct and recusal as the arbitration clerk team.

For this motion there are 11 active arbitrators. With 0 arbitrators abstaining, 6 support or oppose votes are a majority.

Support:

This is my first choice and falls within ArbCom's community-granted authority to approve and remove access to [...] mailing lists maintained by the Arbitration Committee^[1] and to designate individuals for particular tasks or roles and maintain a panel of clerks to assist with the smooth running of its functions.^[2]
Currently, we have arbitration clerks to help with on-wiki work, but most of ArbCom's workload is private (on arbcom-en), and our clerks have no ability to help with that because they can't access any of ArbCom's non-public work. It has always seemed strange to me to have clerks for on-wiki work, but not for the bulk of the work which is off-wiki (and which has always needed more coordination help).
When consulting the functionaries, I was pleasantly surprised to learn that four functionaries (including three former arbitrators) expressed interest in volunteering for this role. This would be lower-intensity than serving as an arbitrator, but still essential to the functioning of the committee. We already have a number of ex-arbs on the clerks-l mailing list to advise and assist, and this seems like a natural extension of that function. The Stewards have a somewhat similar "Steward clerk" role, although ArbCom correspondence clerks would be a higher-trust position (functionary-level appointments only).
I see this as the strongest option because the structure is familiar (analogous to our existing clerks, but for off-wiki business), because we have trusted functionaries and former arbs interested who could well discharge these responsibilities, and because I think we would benefit from separating the administrative responsibility from the substantive responsibility. The cons I see are that volunteer correspondence clerks might be less reliable than paid staff and that we'd be adding one or two (ish) people to the arbcom-en list. Best, KevinL (aka L235 · t · c) 18:28, 1 December 2024 (UTC)[reply]

Oppose:

Abstain:

Motion 1: Arbitrator views and discussions

I'd be glad changing this to only appoint former arbs, if that would tip anyone's votes. Currently, it's written as "from among the English Wikipedia functionary corps (and preferably from among former members of the Arbitration Committee)" for flexibility if needed, but I imagine we would only really appoint former arbs if available, except under unusual circumstances, because they understand how the mailing list discussions go and have previously been elected to handle the same private info. I am also open to calling it something other than "correspondence clerk"; that just seemed like a descriptive title. Best, KevinL (aka L235 · t · c) 18:28, 1 December 2024 (UTC)[reply]

References

Motion 2: WMF staff support

The Arbitration Committee requests that the Wikimedia Foundation Committee Support Team provide staff support for the routine administration and organization of the Committee's mailing list and non-public work.

The selected staff assistants shall be responsible for assisting the Committee in the routine administration and organization of its mailing list and non-public work in a similar manner as the existing arbitration clerks assist in the administration of the Committee's on-wiki work. Staff assistants shall perform their functions under the direction of the Arbitration Committee and shall not represent the Wikimedia Foundation in the course of their support work with the Arbitration Committee or disclose the Committee's internal deliberations except as directed by the Committee.

The specific responsibilities of the staff assistants shall include, as directed by the Committee:

Acknowledging the receipt of correspondence and assigning tracking identifiers to pending requests and other matters;
Tracking the status of pending matters and providing regular updates and reminders on the status of the Committee's off-wiki work to arbitrators;
Reminding members of the Committee to vote or otherwise take action in pending matters;
Organizing related correspondence into case files; and
Providing similar routine administrative and clerical assistance to the Arbitration Committee.

The remit of staff assistants shall not include:

Participating in the substantive consideration or decision of any matters before the Committee; or
Taking non-routine actions requiring the exercise of arbitrator discretion.

To that end, upon the selection of staff assistants, the current arbcom-en mailing list shall be renamed to arbcom-en-internal, which shall continue to be accessible only by arbitrators, and a new arbcom-en email list shall be established. The subscribers to the new arbcom-en list shall be the arbitrators and staff assistants.

The Committee shall establish a process to allow editors to, in unusual circumstances following a showing of good cause, directly email a mailing list accessible only by arbitrators and not by staff assistants.

Staff assistants shall be subject to the same requirements concerning conduct and recusal as the arbitration clerk team.

For this motion there are 11 active arbitrators. With 0 arbitrators abstaining, 6 support or oppose votes are a majority.

Support:

Oppose:

Abstain:

Motion 2: Arbitrator views and discussions

I am quite open to this idea. A professional staff member assisting the committee might be the most reliable and consistent way to achieve this goal. ArbCom doesn't need the higher-intensity support that the WMF Committee Support Team provides other committees like AffCom and the grant committees, but having somebody to track threads and bump stalled discussions would be quite helpful. I'm going to wait to see if there's any community input on this motion before voting on it, though. Best, KevinL (aka L235 · t · c) 18:28, 1 December 2024 (UTC)[reply]

Motion 3: Coordinating arbitrators

The Arbitration Committee's procedures are amended by adding the following section:

Coordinating arbitrators

The Arbitration Committee shall, from time to time, designate one or more arbitrators to serve as the Committee's coordinating arbitrators.
Coordinating arbitrators shall be responsible for assisting the Committee in the routine administration and organization of its mailing list and non-public work in a similar manner as the existing arbitration clerks assist in the administration of the Committee's on-wiki work.
The specific responsibilities of coordinating arbitrators shall include:

Acknowledging the receipt of correspondence and assigning tracking identifiers to pending requests and other matters;

Tracking the status of pending matters and providing regular updates and reminders on the status of the Committee's off-wiki work to arbitrators;

Reminding members of the Committee to vote or otherwise take action in pending matters;

Organizing related correspondence into case files; and

Performing similar routine administrative and clerical functions.

A coordinating arbitrator may, but is not required to, state an intention to abstain on some or all matters before the Committee without being listed as an "inactive" arbitrator.

For this motion there are 11 active arbitrators. With 0 arbitrators abstaining, 6 support or oppose votes are a majority.

Support:

This is currently my first-choice option; we have unofficially in the past had arbitrators take on specific roles (e.g. tracking unblock requests, responding to emails, etc) and it seemed to work fairly well. Having those rules be more "official" seems like the best way to make sure someone is responsible for these things, without needing to expand the committee or the pool of people with access to private information. Primefac (talk) 18:53, 1 December 2024 (UTC)[reply]

Oppose:

Abstain:

Motion 3: Arbitrator views and discussions

I am also open to this idea, though I am worried that it will be insufficient and haven't made up my mind on my vote yet. This idea was floated by a former arbitrator from back when the committee did have a coordinating arbitrator, though that role kind of quietly faded away. The benefits of this approach include that there's no need to bring anyone else onto the list. This motion also allows (but does not require) arbs to take a step back from active arb business to focus on the coordination role, which could help with the bifurcation I mention above. Cons include that this could be the least reliable option; that it's possible no arb is interested, or has the capacity to do this well; and that it's hard to be both a coordinator on top of the existing difficult role of serving as an active arb. I personally think this is better than nothing, but probably prefer one of the other two motions to actually add some capacity.
Other ideas that have been floated include establishing a subcommittee of arbitrators responsible for these functions. My same concerns would apply there, but if there's interest, I'm glad to draft and propose a motion to do that; any other arb should also feel free to propose such a motion of their own. Best, KevinL (aka L235 · t · c) 18:28, 1 December 2024 (UTC)[reply]

Motion 4: Grants for correspondence clerks

In the event that "Motion 1: Correspondence clerks" passes, the Arbitration Committee shall request that the Wikimedia Foundation provide grants payable to correspondence clerks in recognition of their assistance to the Committee.

For this motion there are 11 active arbitrators. With 0 arbitrators abstaining, 6 support or oppose votes are a majority.

Support:

Oppose:

Abstain:

Motion 4: Arbitrator views and discussions

Proposing for discussion; thanks to voorts for the idea. Best, KevinL (aka L235 · t · c) 19:00, 1 December 2024 (UTC)[reply]

Community discussion

Will correspondence clerks be required to sign an NDA? Currently clerks aren't. Regardless of what decision is made this should probably be in the motion. * Pppery * _{it has begun...} 18:29, 1 December 2024 (UTC)[reply]

Good catch. I thought it was implied by "from among the English Wikipedia functionary corps" – who all sign NDAs as a condition to access functionaries-en and the CUOS tools; see Wikipedia:Functionaries (Functionary access [...] requires that the user sign the confidentiality agreement for nonpublic information.) – but I've made it explicit now. KevinL (aka L235 · t · c) 18:31, 1 December 2024 (UTC)[reply]

You're right that that was there, but I missed it on my first readthrough of the rules (thinking correspondence clerks would be appointed from the clerk team instead). * Pppery * _{it has begun...} 18:37, 1 December 2024 (UTC)[reply]

Why does "coordinating arbitrators" need a (public) procedures change? Izno (talk) 18:34, 1 December 2024 (UTC)[reply]

As Primefac mentioned above, it seems reasonable to assume that having something written down "officially" might help make sure that the coordinating arbitrator knows what they are responsible for. In any event, it probably can't hurt. Best, KevinL (aka L235 · t · c) 19:08, 1 December 2024 (UTC)[reply]

It is a pain in the ass to get formal procedures changed. There is an internal procedures page: I see 0 reason not to use it if you want to clarify what the role of this arbitrator is. Izno (talk) 19:13, 1 December 2024 (UTC)[reply]

On top of that, this doesn't actually change the status quo much if at all. It is almost entirely a role definition for an internal matter, given "we can make an arb a CA, but we don't have to have one" in it's "from time to time" clause. This just looks like noise to anyone reading ARBPRO who isn't on ArbCom: the public doesn't need to know this arb even exists, though they might commonly be the one responding to emails so they might get a sense there is such an arb. Izno (talk) 19:21, 1 December 2024 (UTC)[reply]

While I appreciate that some functionaries are open to volunteering for this role, this ~~borders on~~ is a part-time secretarial job and ought to be compensated as such. The correspondence clerks option combined with WMF throwing some grant money towards compensation would be my ideal. voorts (talk/contributions) 18:35, 1 December 2024 (UTC)[reply]

Thanks for this suggestion – I've added motion 4 to address this suggestion. Best, KevinL (aka L235 · t · c) 19:08, 1 December 2024 (UTC)[reply]

In the first motion the word "users" in "The Committee shall establish a process to allow users to, in unusual circumstances" is confusing, it should probably be "editors". In the first and second motions, it should probably be explicit whether correspondence clerks/support staff are required, permitted or prohibited to:

Share statistical information publicly
Share status information (publicly or privately) with correspondents who wish to know the status of their request.
Share status information (publicly or privately) about the status of a specific request with someone other than the correspondent.
For this I'm thinking of scenarios like where e.g. an editor publicly says they emailed the Committee about something a while ago, and one or more other editors asks what is happening with it.

I think my preference would be for 1 or 2, as these seem likely to be the more reliable. Neither option precludes there also being a coordinating arbitrator doing some of the tasks as well. Thryduulf (talk) 18:49, 1 December 2024 (UTC)[reply]

Thanks for these suggestions. I've changed "users" to "editors". The way I'm intending these motions to be read, correspondence clerks or staff assistants should only disclose information as directed by the committee. I think the details of which information should be shared upon whose request in routine cases could be decided later by the committee, with the default being "ask ArbCom before disclosing until the committee decides to approve routine disclosures in certain cases", because it's probably hard to know in advance which categories will be important to allow. I'm open to including more detail if you think that's important to include at this stage, though, and I'd welcome hearing why if so. Best, KevinL (aka L235 · t · c) 19:08, 1 December 2024 (UTC)[reply]

I see your point, but I think it worth clarifying certain things in advance before they become an issue to avoid unrealistic or mistaken expectations of the c-clerks by the community. Point 1 doesn't need to be specified in advance, maybe something like "communicating information publicly as directed by the Committee" would be useful to say in terms of expectation management or maybe it's still to specific? I can see both sides of that.

Point 2 I think is worth establishing quickly and while it is on people's minds. Waiting for the committee to make up its mind before knowing whether they can give a full response to a correspondent about this would be unfair to both the correspondent and clerk I think. This doesn't necessarily have to be before adoption, but if not it needs to be very soon afterwards.

Point 3 is similar, but c-clerks and community members knowing exactly what can and cannot be shared, and especially being able to point to something in writing about what cannot be said publicly, has the potential to reduce drama e.g. if there is another situation similar to Billed Mammal's recent case request. Thryduulf (talk) 19:30, 1 December 2024 (UTC)[reply]

What justification is there for the WMF to spend a single additional dollar on the workload of a project-specific committee whose workload is now demonstrably smaller than at any time in its history? (Noting here that there is a real dollar-cost to the support already being given by WMF, such as the monthly Arbcom/T&S calls that often result in the WMF accepting requests for certain activities.) And anyone who is being paid by the WMF is responsible to the WMF as the employer, not to English Wikipedia Arbcom.

I think Arbcom is perhaps not telling the community some very basic facts that are leading to their efforts to find someone to take responsibility for its organization, which might include "we have too many members who aren't pulling their weight" or "we have too many members who, for various reasons that don't have to do with Wikipedia, are inactive", or "we have some tasks that nobody really wants to do". There's no indication that any of these solutions would solve these kinds of problems, and I think that all of these issues are factors that are clearly visible to those who follow Arbcom on even an occasional basis. Arbitrators who are inactive for their own reasons aren't going to become more active because someone's organizing their mail. Arbitrators who don't care enough to vote on certain things aren't any more likely to vote if someone is reminding them to vote in a non-public forum; there's no additional peer pressure or public guilt-tripping. And if Arbcom continues to have tasks that nobody really wants to do, divest those tasks. Arbcom has successfully done that with a large number of tasks that were once its responsibility.

I think you can do a much better job of making your case. Risker (talk) 20:05, 1 December 2024 (UTC)[reply]

I think there is a need to do something as poor communication and extremely slow replies, if replies are made at all, has been an ongoing issue for the committee for some time. However I agree that asking the foundation to pay someone to do it is going too far. The point that if you are paid by the foundation, you work for them and not en.wp or arbcom is a compelling one. There's also a slippery slope argument to be made in that if we're paying these people, shouldn't we pay the committee? If we're paying the committee, shouldn't we pay the arbitration clerks....and so on. Just Step Sideways ^{from this world ..... today} 20:26, 1 December 2024 (UTC)[reply]

I fully share Risker's concern about a paid WMF staffer who, no matter how well-intentioned, will be answerable to the WMF and not ARBCOM. Vanamonde93 (talk) 21:55, 1 December 2024 (UTC)[reply]

I think the timing for this is wrong. The committee is about to have between 7 and 9 new members (depending on whether Guerillero, Eek, and Primefac get re-elected). In addition it seems likely that some number of former arbs are about to rejoin the committee. This committee - basically the committee with the worst amount of active membership of any 15 member committee ever - seems like precisely the wrong one to be making large changes to ongoing workflows in December. Izno's idea of an easier to try and easier to change/abandon internal procedure for the coordinating arb feels like something appropriate to try now. The rest feel like it should be the prerogative of the new committee to decide among (or perhaps do a different change altogether). Best, Barkeep49 (talk) 21:44, 1 December 2024 (UTC)[reply]

Requests for enforcement

Click here to add a new enforcement request
For appeals: create a new section and use the template {{Arbitration enforcement appeal}}
See also: Logged AE sanctions

Important information

Shortcuts

Please use this page only to:

request administrative action against editors violating a remedy (not merely a principle) or an injunction in an Arbitration Committee decision, or a contentious topic restriction imposed by an administrator,
request contentious topic restrictions against previously alerted editors who engage in misconduct in a topic area designated as a contentious topic,
request page restrictions (e.g. revert restrictions) on pages that are being disrupted in topic areas designated as contentious topics, or
appeal arbitration enforcement actions (including contentious topic restrictions) to uninvolved administrators.

For all other problems, including content disagreements or the enforcement of community-imposed sanctions, please use the other fora described in the dispute resolution process. To appeal Arbitration Committee decisions, please use the clarification and amendment noticeboard.

Only autoconfirmed users may file enforcement requests here; requests filed by IPs or accounts less than four days old or with less than 10 edits will be removed. All users are welcome to comment on requests except where doing so would violate an active restriction (such as an extended-confirmed restriction). If you make an enforcement request or comment on a request, your own conduct may be examined as well, and you may be sanctioned for it. Enforcement requests and statements in response to them may not exceed 500 words and 20 diffs, except by permission of a reviewing administrator. (Word Count Tool) Statements must be made in separate sections. Non-compliant contributions may be removed or shortened by administrators. Disruptive contributions such as personal attacks, or groundless or vexatious complaints, may result in blocks or other sanctions.

To make an enforcement request, click on the link above this box and supply all required information. Incomplete requests may be ignored. Requests reporting diffs older than one week may be declined as stale. To appeal a contentious topic restriction or other enforcement decision, please create a new section and use the template {{Arbitration enforcement appeal}}.

Appeals and administrator modifications of contentious topics restrictions

The Arbitration Committee procedures relating to modifications of contentious topic restrictions state the following:

All contentious topic restrictions (and logged warnings) may be appealed. Only the restricted editor may appeal an editor restriction. Any editor may appeal a page restriction.

The appeal process has three possible stages. An editor appealing a restriction may:

ask the administrator who first made the contentious topic restrictions (the "enforcing administrator") to reconsider their original decision;
request review at the arbitration enforcement noticeboard ("AE") or at the administrators' noticeboard ("AN"); and
submit a request for amendment ("ARCA"). If the editor is blocked, the appeal may be made by email.

Appeals submitted at AE or AN must be submitted using the applicable template.

A rough consensus of administrators at AE or editors at AN may specify a period of up to one year during which no appeals (other than an appeal to ARCA) may be submitted.

Changing or revoking a contentious topic restriction

An administrator may only modify or revoke a contentious topic restriction if a formal appeal is successful or if one of the following exceptions applies:

The administrator who originally imposed the contentious topic restriction (the "enforcing administrator") affirmatively consents to the change,^[a] or is no longer an administrator;^[b] or
The contentious topic restriction was imposed (or last renewed) more than a year ago and:
- the restriction was imposed by a single administrator, or
- the restriction was an indefinite block.

A formal appeal is successful only if one of the following agrees with revoking or changing the contentious topic restriction:

a clear consensus of uninvolved administrators at AE,
a clear consensus of uninvolved editors at AN,
a majority of the Arbitration Committee, acting through a motion at ARCA.

Any administrator who revokes or changes a contentious topic restriction out of process (i.e. without the above conditions being met) may, at the discretion of the Arbitration Committee, be desysopped.

Standard of review
On community review

Uninvolved administrators at the arbitration enforcement noticeboard ("AE") and uninvolved editors at the administrators' noticeboard ("AN") should revoke or modify a contentious topic restriction on appeal if:

the action was inconsistent with the contentious topics procedure or applicable policy (i.e. the action was out of process),
the action was not reasonably necessary to prevent damage or disruption when first imposed, or
the action is no longer reasonably necessary to prevent damage or disruption.

On Arbitration Committee review

Arbitrators hearing an appeal at a request for amendment ("ARCA") will generally overturn a contentious topic restriction only if:

the action was inconsistent with the contentious topics procedure or applicable policy (i.e. the action was out of process),
the action represents an unreasonable exercise of administrative enforcement discretion, or
compelling circumstances warrant the full Committee's action.

^ The administrator may indicate consent at any time before, during, or after imposition of the restriction.
^ This criterion does not apply if the original action was imposed as a result of rough consensus at the arbitration enforcement noticeboard, as there would be no single enforcing administrator.

Appeals and administrator modifications of non-contentious topics sanctions

The Arbitration Committee procedures relating to modifications and appeals state:

Appeals by sanctioned editors

Appeals may be made only by the editor under sanction and only for a currently active sanction. Requests for modification of page restrictions may be made by any editor. The process has three possible stages (see "Important notes" below). The editor may:

ask the enforcing administrator to reconsider their original decision;
request review at the arbitration enforcement noticeboard ("AE") or at the administrators’ noticeboard ("AN"); and
submit a request for amendment at the amendment requests page ("ARCA"). If the editor is blocked, the appeal may be made by email through Special:EmailUser/Arbitration Committee (or, if email access is revoked, to arbcom-enwikimedia.org).

Modifications by administrators

No administrator may modify or remove a sanction placed by another administrator without:

the explicit prior affirmative consent of the enforcing administrator; or
prior affirmative agreement for the modification at (a) AE or (b) AN or (c) ARCA (see "Important notes" below).

Administrators modifying sanctions out of process may at the discretion of the committee be desysopped.

Nothing in this section prevents an administrator from replacing an existing sanction issued by another administrator with a new sanction if fresh misconduct has taken place after the existing sanction was applied.

Administrators are free to modify sanctions placed by former administrators – that is, editors who do not have the administrator permission enabled (due to a temporary or permanent relinquishment or desysop) – without regard to the requirements of this section. If an administrator modifies a sanction placed by a former administrator, the administrator who made the modification becomes the "enforcing administrator". If a former administrator regains the tools, the provisions of this section again apply to their unmodified enforcement actions.

Important notes:

For a request to succeed, either

(i) the clear and substantial consensus of (a) uninvolved administrators at AE or (b) uninvolved editors at AN or

(ii) a passing motion of arbitrators at ARCA

is required. If consensus at AE or AN is unclear, the status quo prevails.

While asking the enforcing administrator and seeking reviews at AN or AE are not mandatory prior to seeking a decision from the committee, once the committee has reviewed a request, further substantive review at any forum is barred. The sole exception is editors under an active sanction who may still request an easing or removal of the sanction on the grounds that said sanction is no longer needed, but such requests may only be made once every six months, or whatever longer period the committee may specify.
These provisions apply only to contentious topic restrictions placed by administrators and to blocks placed by administrators to enforce arbitration case decisions. They do not apply to sanctions directly authorized by the committee, and enacted either by arbitrators or by arbitration clerks, or to special functionary blocks of whatever nature.
All actions designated as arbitration enforcement actions, including those alleged to be out of process or against existing policy, must first be appealed following arbitration enforcement procedures to establish if such enforcement is inappropriate before the action may be reversed or formally discussed at another venue.

Information for administrators processing requests

Thank you for participating in this area. AE works best if there are a variety of admins bringing their expertise to each case. There is no expectation to comment on every case, and the Arbitration Committee (ArbCom) thanks all admins for whatever time they can give.

A couple of reminders:

Before commenting, please familiarise yourself with the referenced ArbCom case. Please also read all the evidence (including diffs) presented in the AE request.
When a request widens to include editors beyond the initial request, these editors must be notified and the notifications recorded in the same way as for the initial editor against whom sanctions were requested. Where some part of the outcome is clear, a partial close may be implemented and noted as "Result concerning X".
Enforcement measures in arbitration cases should be construed liberally to protect Wikipedia and keep it running efficiently. Some of the behaviour described in an enforcement request might not be restricted by ArbCom. However, it may violate other Wikipedia policies and guidelines; you may use administrative discretion to resolve it.
More than one side in a dispute may have ArbCom conduct rulings applicable to them. Please ensure these are investigated.

Closing a thread:

Once an issue is resolved, enclose it between {{hat}} and {{hab}} tags. A bot should archive it in 7 days.
Please consider referring the case to ARCA if the outcome is a recommendation to do so or the issue regards administrator conduct.
You can use the templates {{uw-aeblock}} (for blocks) or {{AE sanction}} (for other contentious topic restrictions) to give notice of sanctions on user talk pages.
Please log sanctions in the Arbitration enforcement log.

Thanks again for helping. If you have any questions, please post on the talk page.

Arbitration enforcement archives

1	2	3	4	5	6	7	8	9	10	11	12	13	14	15	16	17	18	19	20
21	22	23	24	25	26	27	28	29	30	31	32	33	34	35	36	37	38	39	40
41	42	43	44	45	46	47	48	49	50	51	52	53	54	55	56	57	58	59	60
61	62	63	64	65	66	67	68	69	70	71	72	73	74	75	76	77	78	79	80
81	82	83	84	85	86	87	88	89	90	91	92	93	94	95	96	97	98	99	100
101	102	103	104	105	106	107	108	109	110	111	112	113	114	115	116	117	118	119	120
121	122	123	124	125	126	127	128	129	130	131	132	133	134	135	136	137	138	139	140
141	142	143	144	145	146	147	148	149	150	151	152	153	154	155	156	157	158	159	160
161	162	163	164	165	166	167	168	169	170	171	172	173	174	175	176	177	178	179	180
181	182	183	184	185	186	187	188	189	190	191	192	193	194	195	196	197	198	199	200
201	202	203	204	205	206	207	208	209	210	211	212	213	214	215	216	217	218	219	220
221	222	223	224	225	226	227	228	229	230	231	232	233	234	235	236	237	238	239	240
241	242	243	244	245	246	247	248	249	250	251	252	253	254	255	256	257	258	259	260
261	262	263	264	265	266	267	268	269	270	271	272	273	274	275	276	277	278	279	280
281	282	283	284	285	286	287	288	289	290	291	292	293	294	295	296	297	298	299	300
301	302	303	304	305	306	307	308	309	310	311	312	313	314	315	316	317	318	319	320
321	322	323	324	325	326	327	328	329	330	331	332	333	334	335	336	337	338	339	340
341	342	343	344

Southasianhistorian8

This request may be declined without further action if insufficient or unclear information is provided in the "Request" section below.
Requests may not exceed 500 words and 20 diffs (not counting required information), except by permission of a reviewing administrator.

Request concerning Southasianhistorian8

User who is submitting this request for enforcement: GhostOfDanGurney (talk · contribs · deleted contribs · logs · filter log · block user · block log) 17:00, 14 November 2024 (UTC)[reply]

User against whom enforcement is requested: Southasianhistorian8 (talk · contribs · deleted contribs · logs · filter log · block user · block log)
Search CT alerts: in user talk history • in system log

Sanction or remedy to be enforced: Wikipedia:ARBIPA

Diffs of edits that violate this sanction or remedy, and an explanation how these edits violate it

21:37, November 12 Ignores WP:ONUS, edit warring in order to restore POV-pushing/WP:COATRACK content after that content had been removed by Nyttend.
02:11, November 14 Repeats the same WP:COATRACK behaviour at another article, just over 24hrs after Nyttend (a longstanding administrator) warned them about WP:COATRACK on their talk page.
08:49 November 14 Personal attack towards me on their userpage in response to sharing my concern about diff2 and agreeing with Nyttend, claims I'm "piling on my t/p over a topic that does not concern you as a form of petty bullying/harassment and revenge." (bolding mine; Nyttend was the only other user with a message on their talk page)
10:05 November 14 Leaves a retaliatory message on my talk page, spurned by my reverting of their edit in diff2.

Diffs of previous relevant sanctions, if any

20:47, 2022 May 30 Indeff'd for abusing multiple accounts in the area of conflict as per Wikipedia:Sockpuppet_investigations/Suthasianhistorian8/Archive. Unblocked in December 2022 following a standard offer.
19:06, 2021 November 11 48hrs for edit warring in the area of conflict.

If contentious topics restrictions are requested, supply evidence that the user is aware of them (see WP:CTOP#Awareness of contentious topics)

Alerted about discretionary sanctions or contentious topics in the area of conflict, on 16:31, 2021 November 27 (see the system log linked to above).

Additional comments by editor filing complaint

SAH continues to push their anti-Sikh POV into articles. Diff1 shows them adding repetitive content which was already covered in the article, not to mention that it has its own article. Repeating in such detail can only be interpreted as an attempt to draw a equivalency between Khalistan movement and the Canada-India row that is not supported by sources.

Diff2 shows them doing them same at Hardeep Singh Nijjar, using that article as a COATRACK to add content about a tangentially relevant person, content which belong in an article about that person, and attempting to further their POV that Nijjar was a "militant".

Diffs 3 and 4 showcase an unwillingness to self-reflect when conduct concerns are brought up, getting defensive with personal attacks, retaliatory warnings, and digging up of past dirt (which they already mentioned in the last AE thread about them). At no point do they acknowledge WP:COATRACK either in response to Nyttend or myself.

Contribution history shows they nearly-exclusively edit about Sikh topics, suppressing positive information and restoring negative information. Talk page history shows numerous NPOV warnings. At this point, we either have a LISTENing issue or a WP:NOTHERE issue. ― "Ghost of Dan Gurney" (talk) 17:00, 14 November 2024 (UTC)[reply]

@103.251.217.66: I disagree with your evaluation of this as only a content dispute. I am reporting conduct; specifically violations of WP:EW (after the user made an agreement to never edit war[1] as part of their SOCK unblock request), WP:NPOV, and WP:NPA. I am aware that AE does not and should never rule on content. ― "Ghost of Dan Gurney" (talk) 01:14, 15 November 2024 (UTC)[reply]

Has SAH gotten a waiver of the word limit that I'm not aware of? They are at 1552 by my count. ― "Ghost of Dan Gurney" (talk) 02:26, 15 November 2024 (UTC)[reply]

@Ivanvector: While BLPCRIME is a reason why I reverted diff 2, it was not the only reason, with the other reason being that I felt SAH was pushing a POV using WP:COATRACK edits, something they had been warned about 24 hours previously for the edit in diff 1. My issue with the edit to Hardeep Singh Nijjar re: Arsh Dalla is beyond the BLPCRIME issue. It goes into the aspect of using another person's arrest to further a POV that Nijjar was a militant extremist.

The fact that SAH filed a report about Simonm223 to AN today[2] for simply trying to engage with SAH at SAH's talk page[3], then WP:BADGERed voorts at voort's talk page after voorts closed the thread[4] shows that SAH's conduct is the primary issue, not the content of any article. ― "Ghost of Dan Gurney" (talk) 23:30, 16 November 2024 (UTC)[reply]

@ScottishFinnishRadish: it is at DRN [5] on referral by Voorts after SAH made a thread reporting Simonm223 at ANI [6], was warned for forum shopping, then badgered voorts at their talk page[7] The DRN has new posts tonight that I still need to catch up on. ― "Ghost of Dan Gurney" (talk) 02:51, 21 November 2024 (UTC)[reply]

...Okay, seriously, this is getting out of hand now. SAH's response to being asked to state concisely what they want to change that another editor wants to leave the same at DRN is to post a wall of text outlining their entire rationale to insert what they call "a brief few sentences or paragraphs" (huh?). Is this not WP:BLUDGEONING of a discussion?[8] ― "Ghost of Dan Gurney" (talk) 02:58, 21 November 2024 (UTC)[reply]

Notification of the user against whom enforcement is requested

[9]

Discussion concerning Southasianhistorian8

Statements must be made in separate sections. They may not exceed 500 words and 20 diffs, except by permission of a reviewing administrator.
Administrators may remove or shorten noncompliant statements. Disruptive contributions may result in blocks.

Statement by Southasianhistorian8

(Note, below is SAH's original statement, the one people have commented on. The altered statement, where he removed/changed the things others had criticised, so that their criticism no longer made sense, can be found here. See my comment down in the admin section (in a moment from now) for why I've put their original statement back. Bishonen | tålk 09:11, 21 November 2024 (UTC).)[reply]

Talk about desperation. Any outsider can take a look at my handling on Khalistan movement and see that I handled myself very responsibly as opposed to GhostofDanGurney who keeps lobbing personal attacks at editors he dislikes. I only made one revert, and when Nyttend posted on my t/p, I told him I would not revert further, and initiated a discussion on the t/p. The content I added was literally a direct result of the killing of Hardeep Singh Nijjar, a Khalistan activist, and the RCMP's allegations of India's operations against Khalistan activists, so clearly the event is relevant to the page at least to some degree and I'm extremely confident that editors at 3O or DRN will agree. The content there wasn't even authored by me, I copied it (with attribution) from the Canada-India diplomatic row. If I was so biased, wouldn't I be trying to suppress this information? I figured that precluding such a consequential event would be irresponsible and make it appear as though the page was skewed towards a pro-India narrative. What more do you want from me?

Now, in line with GhostofDanGurney hastily making edits to get one over me such as here-where he engaged in interpretation of a primary source to publicy discredit a figure, as confirmed by ScottishFinnishRadish on A/E, here where he falsely accused me of plagiarizing his work Now he falsely called Arsh Dalla a "low profile" individual thus wrongly invoking BLPCRIME; Ghost could have spent at least 10 minutes researching this guy or at least initiated a respectful discussion on the t/p instead of piling attacks on my t/p. Instead he made a rude condescending post on my t/p, threatening to escalate matters and stating that I need to confirm whether I understand Wikipedia's policies to him, as if he's my boss or something. He has yet to engage in the t/p of the article where I laid out sources and arguments, instead coming here to again win a content dispute illegitimately.

Now just days after his failed A/E request where he was also criticized for making personal attacks and making nonconstructive edits, he's again wasting everyone's tie over this drama. This ridiculous BATTLEGROUND behaviour should not be given carte-blanche here.Southasianhistorian8 (talk) 19:27, 14 November 2024 (UTC)[reply]

@GhostofDanGurney- Is one revert on the Khalistan movement page, in which I believed the removal from Nyttend to be a simple misunderstanding and subsequently went on the t/p, and zero reverts on the Hardeep Singh Nijjar page - for a grand total of one revert considered "edit warring". If so, you've edit warred hundreds of times as well Ghost. You've also told people to "fuck themselves", called them "thots" and "hypocrites" and more; I've never come close to saying something like that. Again, I strongly urge admins to issue a block for these juvenile insults. Literally every disagreement on his t/p is met with a nasty response-[10], [11]. This ill-researched statement is like the last time when you falsely accused me of plagiarizing your work.

Regarding, allegations of BLPCRIME or Dalla's low-profile/non public figure status-I've laid out a comprehensive case here-which shows extensive media coverage surrounding Dalla + sources in which Dalla clearly gave interviews to the media thus making him a high profile person as per Wiki policy. Southasianhistorian8 (talk) 03:02, 15 November 2024 (UTC)[reply]

@Black Kite, I saw a thread on the article's t/p in which two editors expressed a desire to move the paragraph about the diplomatic row in the lead of the article. I removed the paragraph from the lead, and intended to move it and expand on it in the body of the article, but was unexpectedly called away before I could. By the time I returned, you had reverted me. In hindsight, I should have made my 2nd intended edit immediately afterwards and linked the t/p discussion, so my apologies for that. Southasianhistorian8 (talk) 03:48, 18 November 2024 (UTC)[reply]

(End of original statement)

@Bishonen:, those year old edit summaries are part of a continuing pattern of Ghost's hostility to anyone who disagrees with him, even as recent. The underlying behaviour hasn't changed at all, he was making inflammatory edit summaries, which SFR acknowledged in the first A/E not too long ago-[12] + [13], then right after that he took a quote from a primary source and framed it in a very inflammatory way (also acknowledged by SFR) to clearly cause irritation. His t/p reveals numerous attacks against people who disagree with him as recent as 2023-ironically it was him who did not have consensus and [14]. He also admitted to messaging Kautilya3 on Twitter after a heated content dispute, which is pretty absurd.

As for this edit-[15], I explicitly stated that it shouldn't have been in the lead-Please gain WP:CONSENSUS to add this to the article's lead, in accordance with the t/p discussion. I already apologized for the poor communication on my part here (I should have stated my intention to move and expand the para and linked the t/p discussion) and admit that I should take care to not add WIP edits, but I feel like AGF should apply here, especially when I already apologized and it involves my private life. I'm willing to own up to when I make a mistake.Southasianhistorian8 (talk) 04:20, 21 November 2024 (UTC)[reply]

In all, I think that a good solution to this conflict(s) would be a 2 way IBAN between Ghost and myself, after the DRN or any other consensus building forum has concluded. Our editing seems to primarily intersect at two pages-Hardeep Singh Nijjar and Canada-India diplomatic row out of the many hundreds of pages we've edited, the C-I row is not a page I'm particularly interested in anymore. There may be more developments on those two pages surrounding the ongoing criminal investigation, but that's not something I'm too interested in and will likely not make edits towards. I'm committed to resolving the Nijjar content dispute peacefully through consensus, and I hope Ghost will too, and I'll also commit to avoiding GoDG as much as possible from hereon. Southasianhistorian8 (talk) 05:09, 21 November 2024 (UTC)[reply]

@Liz, I agree, but a lot of my earlier thoughts/responses were unorganized as this a pretty complicated, high stress dispute. Would me linking my earlier responses be a good solution? Southasianhistorian8 (talk) 07:04, 21 November 2024 (UTC)[reply]

Note: This was my previous statement(s) up until 21 November 4:38 , I substantially altered it for length and because a lot of the responses were spur of the moment/unorganized-[16]. Southasianhistorian8 (talk) 07:12, 21 November 2024 (UTC)[reply]

Would also like to point that Bishonen is not an uninvolved administrator and is posting in the wrong section. We've had disagreements in the past regarding a blocked user's sock/meat status-[17]. That was a case in which I and another administrator believed the blocked account to be a sock, while Bishonen believed them to be a m/p.Southasianhistorian8 (talk) 10:10, 21 November 2024 (UTC)[reply]

We've had 2 disagreements in the past over users alleged to be HaughtonBrit socks barely a few months ago. In the other case, a user who was initially deemed to be "unrelated" to HaughtonBrit, was later deemed a "possible indicator of sockpuppetry" after my report highlighted significant developments in their editing patterns. I believed the user to be a sock, Bishonen stated that she believed that they weren't. Given the contested nature of the latter disagreement, I dont think Bishonen counts as uninvolved administrator. This is what WP:UNINVOLVED states:Involvement is construed broadly by the community to include current or past conflicts with an editor (or editors), and disputes on topics, regardless of the nature, age, or outcome of the dispute.

The sockmaster in question was also someone whose sock reports sometimes faced significant opposition from admins, and it turned I was correct multiple times-in this case for example, an admin was looking to close my report, and it turned out that the user reported was making numerous edits logged out in violation of their block, which they themselves admitted to on their t/p-[18] Southasianhistorian8 (talk) 11:49, 21 November 2024 (UTC)[reply]

@ScottishFinnishRadish, could you provide your view on this? Southasianhistorian8 (talk) 12:15, 21 November 2024 (UTC)[reply]

@ScottishFinnishRadish:, I feel like a topic ban is unnecessary. It shouldn't be ignored that this A/E request is primarily based of a content dispute which is currently underway at DRN-[19]. It should also be highlighted that I provided detailed and policy backed reasons for my proposed changes there, whereas G and Simonm gave curt one sentence responses. Is that not telling? I sincerely request that I be allowed to participate in the consensus building. It should also be noted that I did not edit war anywhere, and am making sincere efforts to gain consensus for my changes.

I also do a lot of work in cleaning up articles in this topic area, which is inundated with POV pushing, poor sourcing and lackluster content. Could you please consider allowing the DRN to conclude and a later IBAN between me and Ghost? I strongly believe that would cease any further conflicts. Southasianhistorian8 (talk) 12:43, 21 November 2024 (UTC)[reply]

I also feel like my inexperience and mistakes at A/E shouldn't dictate the fate of my editing in the Wikipedia mainspace, which are vastly different from each other. The vast majority of my editing in the main space and on talk pages is productive, and I've worked to arrive consensuses consistently over the past 2 years. The dispute between Ghost and myself became so acrimonious and litigious, that it's impossible to handle both discussing on the article t/p, DRN, and handling numerous dogpiles on A/E. Again @ScottishFinnishRadish, please consider an alternative. Southasianhistorian8 (talk) 13:00, 21 November 2024 (UTC)[reply]

@ScottishFinnishRadish, could you please let me know if something else other than a topic ban is on the table? Again, I find it punitive when I'm contributing substantially to the DRN and trying to seek a consensus there. Can we at least not see the assessment of other editors in that content dispute and what they make of Ghost and Simon's BLP/coatrack claims? Southasianhistorian8 (talk) 13:37, 21 November 2024 (UTC)[reply]

Scratch that. Honestly, after seeing the immense toxicity on this site, where numerous editors dog-pile on you, lob false accusations against you, gaslight you and arm-twist you into believing their falsehoods, and just in general playing favourites with those in their own clique, all to get one over someone else in a content dispute, I've realized that Wikipedia is no longer a suitable place for me.

I would request an indef site ban for myself, and I do not intend to make any more edits here. Southasianhistorian8 (talk) 14:34, 21 November 2024 (UTC)[reply]

@Bishonen An indef site block would be good, and allow me to start a new chapter in life. Southasianhistorian8 (talk) 16:34, 21 November 2024 (UTC)[reply]

Statement by (103.251.217.66 (talk))

I think both needs to calm down. both should talk on the article talk page before making changes to the article and stop reverting changes.
I see this is only as content dispute... I don't think Southasianhistorian8 is attacking you op.. https://en.wikipedia.org/w/index.php?title=User_talk:GhostOfDanGurney&diff=prev&oldid=1255952101 you should assume good faith.. and you are also trying gatekeep article it seems to me... https://en.wikipedia.org/wiki/Talk:Canada%E2%80%93India_diplomatic_row#NPOV

Statement by Simonm223

~~I would concur that both editors should probably both get some space from each other for a few days. A short-duration 2-way iBan might be a reasonable remedy here.~~ Most of the edits in contention from both editors don't seem disruptive although both could be a bit more careful with sourcing to avoid primary sources and to ensure that secondary sources are included in major edits. The only point of contention I'd take with either's position (as I don't think either is actually entirely wrong so much as operating at cross-purposes) surrounds the interpretation of WP:BLPCRIME. Arsh Dalla is not a public figure per the definition laid out by WP:PUBLICFIGURE because his notoriety is entirely from the circumstances of him having been accused of a crime. As such the guidance, editors must seriously consider not including material—in any article—that suggests the person has committed or is accused of having committed a crime, unless a conviction has been secured for that crime very much applies here. Simonm223 (talk) 19:46, 14 November 2024 (UTC)[reply]

@Southasianhistorian8 there is a key difference between Bishnoi and Dalla. Bishnoi stood trial and was convicted. My understanding is that Canada has declined to arrest and extradite Dalla. As such, since he is a free person and considered innocent both under Canadian law and by Wikipedia's standards, and since all the media coverage around him is about whether he did any criminal acts, we should not be commenting on him on Wikipedia. I hope this clarifies WP:BLPCRIME for you. Simonm223 (talk) 20:08, 14 November 2024 (UTC)[reply]

Honestly my attempt to provide some friendly help regarding the BLPCRIME issue has left me a bit more concerned about WP:IDHT than I was at the outset. Especially since WP:OSE statements do not override BLP policy. Simonm223 (talk) 23:18, 14 November 2024 (UTC)[reply]

Hopefully my last comment here I just want to apologize to @GhostOfDanGurney for originally interpreting this as a two-way interaction problem. I saw this and tried to sincerely help Southasianhistorian8 and the result was an ANI complaint, a DRN page and several repetitive textwalls. This is much more of a WP:BATTLEGROUND situation than I initially assumed with Southasianhistorian8 specifically and, what's worse, they appear to assume any attempt to assist them is an attack. I have struck my initial comments about a 2-way i-ban as I no longer believe that would be an effective remedy. Simonm223 (talk) 13:30, 21 November 2024 (UTC)[reply]

Statement by Swatjester

Regardless of which side is correct on the merits of the arguments, it does *not* help SAH's case that they've presented their opposition to Ghost of Dan Gurney in an uncivil and excessively inflammatory manner. "he clearly has an extreme vendetta against and is desperate to hound me off this page" fails to assume good faith. So does accusing them of having "a long history of suppressing any critical information on the page... saw this opportunity and rushed to try to hound me further." Vaguely handwaving at a previous report does not suffice to make that anything less than an aspersion. Saying "I find it reprehensible that this bullying behaviour has carte-blanche on Wikipedia" is both uncivil, inflammatory, and presumes that the behavior is 1) bullying, and 2) has "carte-blanche" despite this AE request existing and there having been discussion about it in multiple talk page forums already. Regardless of how this AE gets decided, I'd admonish SAH to find a more constructive, less inflammatory way of expressing their positions. I think all involved would do well to be reminded that in a contentious topic area you need to be on your best behavior. ⇒SWATJester ^{Shoot Blues, Tell VileRat!} 21:24, 14 November 2024 (UTC)[reply]

Statement by Black Kite

SAH is still - whilst this AE is continuing and having started a DRN on the topic themselves - removing sourced and DUE information at Hardeep Singh Nijjar [20]. Quite bizarre behaviour, almost like they want to be sanctioned. Black Kite (talk) 21:04, 17 November 2024 (UTC)[reply]

The claim that Bishonen is not uninvolved here is so ridiculous that it's verging on WP:CIR. Black Kite (talk) 11:35, 21 November 2024 (UTC)[reply]

Statement by Tiggerjay

I've had several of the articles that SAH has been editing come up on various boards that I monitor. Unfortunately, I've been unable to positively contribute for a lack of time to read through the wall of text that SAH generates through their apparent POV-pushing style, and then sometimes Wikilawyering to support their POV. While I think that the situation is primarily one-sided, and GDG is doing a fair job of handling it well, just a reminder that the integrity of WP is not solely upon him to keep other editors in line, and perhaps not taking it too personally. I think a formal TBAN with 500 edits is a good place to start for SAH, and perhaps, if anything, an IBAN for GDG. TiggerJay (talk) 21:59, 24 November 2024 (UTC)[reply]

Statement by Robert McClenon

I opened a mediation case at DRN involving User:Southasianhistorian8 and User:GhostOfDanGurney on 20 November that had been requested by SAH on 16 November. I made a mistake in opening the case, because this dispute was already pending here at Arbitration Enforcement, and DRN does not handle any dispute that is also pending in another content forum or conduct forum, and this is a conduct forum. I have closed the DRN case as failed. The instructions that I gave to the editors to prepare draft sections of material that they wanted to add or to shorten are still good advice as part of discussion and normal editing. I have no opinion on the conduct of the editors, because I try to avoid conduct issues when I am trying to mediate a content dispute (including when I am trying to mediate a content dispute by mistake). Robert McClenon (talk) 00:45, 1 December 2024 (UTC)[reply]

Statement by (username)

Result concerning Southasianhistorian8

This section is to be edited only by uninvolved administrators. Comments by others will be moved to the sections above.

Southasianhistorian8, you're at three times your limit and no admins have commented yet. You need to trim about a thousand words. ScottishFinnishRadish (talk) 02:43, 15 November 2024 (UTC)[reply]
I haven't had the time to look into this in-depth, but I plan to in the next couple days. In the meantime, has anyone started a thread at BLPN? ScottishFinnishRadish (talk) 00:58, 21 November 2024 (UTC)[reply]

Okay, I've looked into this a bit more, but even based on their behavior at this report, the bludgeoning and walls of text, the incivility, and the retaliatory filing below I'm thinking at least a 3-6 month and 500 edit topic ban for tendentious editing with the hope that it will be enough of a sanction that their behavior will be better when they return. I'm also open to an indef topic ban if other admins believe that they should have to offer some proof of constructive editing to return to the topic area.

Bishonen, what SAH linked to was a discussion of your administrative actions and fulfilling WP:ADMINACCT does not make you involved. I don't see any issues with involvement here. ScottishFinnishRadish (talk) 12:26, 21 November 2024 (UTC)[reply]
This seems like a plain dispute over interpretation of BLPCRIME with respect to an edit that was made yesterday, but instead of a discussion at WP:BLPN, there are three enforcement threads visible on this page and another at WP:AN. Perhaps the editors involved should try BLPN first, or other forms of dispute resolution, instead of running here to get each other banned? Ivanvector (^Talk/_Edits) 15:35, 16 November 2024 (UTC)[reply]
I encouraged these editors to take their dispute to DRN. I think everyone needs to de-escalate, step away from the article, and let the process at DRN play out. If that fails and this acrimony continues, IBANs, TBANs, or page restrictions might be needed. voorts (talk/contributions) 03:09, 21 November 2024 (UTC)[reply]
I also haven't had time to research this properly, but I've noticed without difficulty that SAH's behaviour on this very page is poor. SAH, you point out that GhostOfDanGurney told someone to go fuck themselves in 2018, (near the beginning of their Wikipedia career) called somebody else a thot in the same year, and you "strongly urge admins to issue a block for these juvenile insults". A block? Six years after the fact? Please don't air ancient history at AE, especially when it has nothing to do with the matter in hand. I see you offer the same diffs and others from your historical collection in the retaliatory report below, too. I'm also interested to see your explanation of Black Kite's point that during this AE, you removed sourced and DUE information at Hardeep Singh Nijjar, 'almost like [you] want to be sanctioned'. You explain that two editors on Talk wanted to "move" the information, and therefore you re-moved it, intending to move it to the body and even, virtuously, expand on it there, but were interrupted at this very point. This statement of yours flies in the face of a) your edit summary for the removal,[21] and b) what you yourself said about it on Talk.[22] In view of that, the drama where you are "unexpectedly called away" is unfortunately not credible. Bishonen | tålk 04:00, 21 November 2024 (UTC).[reply]
Just noting that I think Southasianhistorian8 has rewritten much of their statement here today. Many comments others have referred to are now absent from their statement. I know that the length of their content was a concern but I don't think a participant should basically rewrite their original statement in response to other editors' complaints. It's confusing when one tries to understand the flow of the discussion. Liz ^{Read! Talk!} 06:57, 21 November 2024 (UTC)[reply]

Yes, indeed they have, and that's not acceptable. Before I commented, I counted SAH's words to see if they had complied with shortening their statement. Yes, they had, it was 554 words. Then, after I had complained about poor behaviour, specifically asking admins to block G over ancient diffs, and trying to explain away Black Kite's complaint of disruption during this case, they "substantially altered it for length and because a lot of the responses were spur of the moment/unorganized". That's one way of putting it. Another would be that after my criticism and Simon223's, they removed the things we criticized. That's unacceptable on talkpages, and just as unacceptable here. Linking to the old version doesn't help much. You simply shouldn't have done it. I have restored the version I commented on, with a link to your new, massaged, less "spur of the moment" version. The time to think is before you post here, not after people have told you what's wrong with it. Note, if you decide to no longer offer an argument that's been criticized, you may of course disown it. But that's done by ~~crossing it out, like this~~. Not by removing it. Bishonen | tålk 09:15, 21 November 2024 (UTC).[reply]

SAH now suggests I'm not an uninvolved admin. I think I am, and I hope one or more admin/user here will please follow SAH's link to evaluate this putative involvement. Bishonen | tålk 11:29, 21 November 2024 (UTC).[reply]

ScottishFinnishRadish, I'm not sure what the "500 edit" means in your proposed t-ban? Bishonen | tålk 13:22, 21 November 2024 (UTC).[reply]

The need to both wait 3 or 6 months and make 500 edits outside of the topic area. This way they have to demonstrate constructive editing elsewhere rather than waiting out the tban. ScottishFinnishRadish (talk) 13:31, 21 November 2024 (UTC)[reply]

I am good with SFR's suggested 3 or 6 months (I lean 6) topic ban AND making 500 substantial edits outside the topic area (by "substantial" I mean not just adding commas or moving around stuff, but engaging with content and showing that they understand how to use reliable sources and how to edit collaboratively) Ealdgyth (talk) 14:03, 21 November 2024 (UTC)[reply]
Indef now? In view of this post by SAH, is it time for an indef block? Or (my preference) should we instead give them a chance to calm down? Bishonen | tålk 16:03, 21 November 2024 (UTC).[reply]
I would give them a chance to calm down. ScottishFinnishRadish (talk) 16:39, 21 November 2024 (UTC)[reply]
Southasianhistorian8, you don't need to quit editing or be indefinitely blocked. You just have to continue to be a productive editor without getting yourself into disputes. I don't see any favoritism here in this discussion. But when I look over your most recent 200 edits in your contribution history, almost all have to do with arguments with other editors. Can you coexist with editors you don't agree with? That's what the rest of us do. And, believe me, there are longtime editors here who have had disagreements with each other that are deeper and longer-lasting than your dispute with GhostOfDanGurney...we just keep a distance between us and do not provoke each other. Remember, this is not just an editing project but a collaborative one so you have to be able to collaborate even when not agreeing. Can you do that? Liz ^{Read! Talk!} 04:33, 22 November 2024 (UTC)[reply]
I'm seeing a rough consensus for a 6 month and 500 edit topic ban. Any objections? ScottishFinnishRadish (talk) 01:23, 25 November 2024 (UTC)[reply]
Just for clarity, is that indicating that the ban expires after 6 months or 500 edits, whichever comes later? Seraphimblade ^{Talk to me} 04:32, 27 November 2024 (UTC)[reply]
Correct. They have have both 500 new edits and have passed six months. ScottishFinnishRadish (talk) 13:30, 27 November 2024 (UTC)[reply]
I wish that Southasianhistorian8 hadn't taken a WikiBreak in the middle of this discussion. Liz ^{Read! Talk!} 06:46, 29 November 2024 (UTC)[reply]

GhostOfDanGurney

No action, being looked into in another report. ScottishFinnishRadish (talk) 12:17, 21 November 2024 (UTC)[reply]

The following discussion has been closed. Please do not modify it.

This request may be declined without further action if insufficient or unclear information is provided in the "Request" section below.
Requests may not exceed 500 words and 20 diffs (not counting required information), except by permission of a reviewing administrator.

Request concerning GhostOfDanGurney

User who is submitting this request for enforcement: Southasianhistorian8 (talk · contribs · deleted contribs · logs · filter log · block user · block log) 04:03, 15 November 2024 (UTC)[reply]

User against whom enforcement is requested: GhostOfDanGurney (talk · contribs · deleted contribs · logs · filter log · block user · block log)
Search CT alerts: in user talk history • in system log

Sanction or remedy to be enforced: Topic ban on India, Pakistan, and Afghanistan related topics.

Diffs of edits that violate this sanction or remedy, and an explanation how these edits violate it

19 September 2023 Tendentious edit warring alleging "anti-Canada POV pushing" despite numerous editors' objections and RS
21 October 2023 Admits to harassing another user he was in a content dispute with on Twitter.
25 October 2024 ~~Personal attacks~~ Inflammatory edit summary, accusing of cherrypicking and being without evidence, even though most of the article included content for which evidence was not publicly disclosed and WP:OWN behaviour
22 October 2024 More ~~personal attacks~~ inflammatory edit summaries, also acknolwedged by ScottishFinnishRadish in the 1st AE
26 October 2024 Replaces neutrally worded sentence with an inflammatory and tendentious interpretation of a primary source as acknowledged by ScottishFinnishRadish, clearly attempting to publicly discredit the diplomat, thus violating WP:BLP. Also a clear case of WP:HOUNDING and WP:OWN behaviour. (Also the impetus to this while conflict)
26 October 2024 Files an A/E request over a content dispute, wasting a large amount of community time
26 October 2024 Falsely claimed I plagiarized his work
15 November 2024 WP:IDHT, brazenly ignoring sources right above him which explicitly state that Dalla's alleged criminal network was linked to Khalistani militancy
14 November 2024 Makes an inflammatory and condescending post on my talk page, accusing me of WP:NPOV violations and threatening to escalate matters before engaging on the t/p.
14 November 2024 Files another A/E request days after his first failed one over 1(!) revert and me responding to his escalation on my t/p. Instead of following WP:BRD, Ghost is filing frivolous reports forcing this platform to be a substitute for content issues. He did not engage with my arguments on the t/p of the Nijjar page which I laid out right after he reverted me, instead he immediately filed a 2nd report, then waited multiple hours to respond to my points on the t/p. He cannot even abide by Wikipedia's most fundamental policy which is to discuss when you have a disagreement with someone, not intimidate them through reports.
15 November 2024 Falsely claimed I was in violation of edit warring, citing a total of one revert.
20 November 2024 Further exhibits bizarre, unprovoked aggression despite a DRN being underway, where editors are expected to try to reach a consensus civilly.

Diffs of previous relevant sanctions, if any

14 August 2020 Blocked for personal attacks
19 June 2018 Blocked for edit warring

If contentious topics restrictions are requested, supply evidence that the user is aware of them (see WP:CTOP#Awareness of contentious topics)

Previously given a discretionary sanction or contentious topic restriction or warned for conduct in the area of conflict on 21 October 2023 by Kautilya3.
Gave CTOPS warning in this topic area on 19 October 2024

Additional comments by editor filing complaint

GhostOfDanGurney has a history of being incredibly rude and juvenile when engaged in content disputes. He regularly calls people names, assumes bad faith or incites drama through his inflammatory bheaviour-Be gone thot, Actually, I'll let people see how much of a hypocrite you are for posting this fucking bullshit., [23], [24], [25], [26], among numerous other diffs. Constantly exhibits tendentious and WP:OWN behaviour in articles-[27], [28], [29] + [30], [31], [32].

Even barring the personal attacks, how is it fair that he's non stop filing frivolous reports against me-in the most recent A/E he filed, it was literally over one revert, content he personally didn't like, and me responding to his escalation on my t/p (pretty ironic considering what he says on his own t/p). Instead of engaging with my points on the article's t/p, he filed a 2nd A/E. How is that not brazen harassment and bullying and a major waste of time? How in the world is that not a weaponization of A/E to get one over an editor they dislike? Southasianhistorian8 (talk) 04:55, 15 November 2024 (UTC)[reply]

@GhostOfDanGurney The definition of militancy is as follows: "the use of confrontational or violent methods in support of a political or social cause." Militancy almost always involves criminal behaviour and actions, does it not? Otherwise it wouldn't be called militancy, it'd be called activism. A criminal network alleged to be close the Khalistan movement apparently does not mean violent actions taken out in order to support the movement? Southasianhistorian8 (talk) 07:38, 15 November 2024 (UTC)[reply]

@GhostOfDanGurney your A/E request against me- stated that I have a WP:LISTENing (IDHT) problem. Please give me examples in the past 2 years where I specifically acted against or ignored community consensus in terms of a content dispute. If you are unable to do so, it'll be overly clear that you're just throwing anything on the wall against me, as a substitute for engaging on the t/p, despite yourself far more being guilty of the same accusations you throw out. Southasianhistorian8 (talk) 23:30, 20 November 2024 (UTC)[reply]

Now that a DRN is underway, it would be nice for you to at least temporarily stop inciting conflict and work towards a consensus there. If you are unable to do so, admins should issue an immediate block for failing to discuss despite initiating a content dispute and battleground behaviour. Southasianhistorian8 (talk) 23:33, 20 November 2024 (UTC)[reply]

@GhostOfDanGurney, an A/E report was well overdue given your lengthy and egregious WP:OWN and inflammatory conduct on various articles. You constantly using this platform as a substitute for BRD pushed it over the edge, and in of itself is sanctionable. The desperation to bar anyone from examining his atrocious conduct is telling. Southasianhistorian8 (talk) 00:04, 21 November 2024 (UTC)[reply]

Notification of the user against whom enforcement is requested: [33]

Discussion concerning GhostOfDanGurney

Statements must be made in separate sections. They may not exceed 500 words and 20 diffs, except by permission of a reviewing administrator.
Administrators may remove or shorten noncompliant statements. Disruptive contributions may result in blocks.

Statement by GhostOfDanGurney

In their statement in the above request against them, they said, "He has yet to engage in the t/p of the article where I laid out sources and arguments". So I commented on the talk page,[34] saying that I opposed the content as (in addition to the BLPCRIME issue) there was already adequate sourced content on Hardeep Singh Nijjar#Allegations of militant activity (it's already the largest section of the article). This had nothing to do with the additional sources SAH presented to the talk page after I had removed the content.

I then wrote a sentence on the wording "criminal network" as used by SAH in their >greentext proposal which made no corroboration to any militancy, just allusions to "gangsters". It did not mention the KTF by name, and the preceding quote they posted only mentions "the Khalistan cause". An IDHT charge here is a long stretch that shows a misunderstanding of the policy, and to use the phrase "brazenly ignoring" here is an assumption of bad faith. If my above request doesn't result in sanctions against SAH, this frivolous request should. ― "Ghost of Dan Gurney" (talk) 07:18, 15 November 2024 (UTC)[reply]

What does any of that re: militancy have to do with me "act[ing] as though [my] point must be accepted by the community when [I] have been told otherwise.", per WP:IDHT? I don't understand at all how my talk page comment violates IDHT. What about that specific comment is actionable here? ― "Ghost of Dan Gurney" (talk) 08:32, 15 November 2024 (UTC)[reply]

Is SAH is unable or unwilling to answer the above question, this retaliatory attempt at a tu quoque style of ad hominem should be closed with a WP:BOOMERANG. ― "Ghost of Dan Gurney" (talk) 22:47, 20 November 2024 (UTC)[reply]

That's twice now I've asked this question and gotten no response. It's obvious that this retaliatory request is a backdoor way to get around the 500-word limit that you ignored before @ScottishFinnishRadish: told you to trim it. ― "Ghost of Dan Gurney" (talk) 23:45, 20 November 2024 (UTC)[reply]

Statement by (username)

Result concerning GhostOfDanGurney

This section is to be edited only by uninvolved administrators. Comments by others will be moved to the sections above.

This is unnecessary, and retaliatory. Spot checking of the diffs alleging personal attacks, I don't see anything remotely of the sort. Going back and digging up diffs from 2018 and 2021 is likewise unhelpful and represents a battleground mentality towards weaponizing an AE action that is deeply concerning. Honestly if SAH thought this was a good idea after not listening to the advice about dropping the stick and behaving more civilly on the other AE request, it probably merits boomerang sanctions to stop the disruption. ⇒SWATJester ^{Shoot Blues, Tell VileRat!} 04:22, 15 November 2024 (UTC)[reply]

SAH, I've looked at the diffs. The ones from 2024 don't appear actionable, and I think your characterizations of them as personal attacks are a stretch. The "thots" and "go fuck themselves" diffs were, as I mentioned, from 2018 and 2021, not directed at you, and were comments from his own talk page (which is a space where he is entitled to ask people to stop/leave within the confines of WP:USERTALKSTOP, and though it doesn't excuse the incivility of the language, we tend to give a degree of leeway in those cases.) So I don't see the relevance of those edits to your dispute with GhostofDanGurney today. ⇒SWATJester ^{Shoot Blues, Tell VileRat!} 04:47, 15 November 2024 (UTC)[reply]

Arbitration enforcement action appeal by Ecrusized

Appeal declined. —Femke 🐦 (talk) 15:48, 23 November 2024 (UTC)[reply]

The following discussion has been closed. Please do not modify it.

Procedural notes: The rules governing arbitration enforcement appeals are found here. According to the procedures, a "clear and substantial consensus of uninvolved administrators" is required to overturn an arbitration enforcement action.

To help determine any such consensus, involved editors may make brief statements in separate sections but should not edit the section for discussion among uninvolved editors. Editors are normally considered involved if they are in a current dispute with the sanctioning or sanctioned editor, or have taken part in disputes (if any) related to the contested enforcement action. Administrators having taken administrative actions are not normally considered involved for this reason alone (see WP:UNINVOLVED).

Appealing user: Ecrusized (talk · contribs · deleted contribs · logs · filter log · block user · block log) – Ecrusized (talk) 15:00, 16 November 2024 (UTC)[reply]

Sanction being appealed: WP:CT/A-I

Sanction notice on user talk page. Diff: https://en.wikipedia.org/w/index.php?title=User_talk:Ecrusized&diff=prev&oldid=1224781735

Discussion leading to the block: Wikipedia:Administrators' noticeboard/IncidentArchive1157#WP:BATTLEGROUND User:BilledMammal

Administrator imposing the sanction: ScottishFinnishRadish (talk · contribs · blocks · protections · deletions · page moves · rights · RfA)

Notification of that administrator: The appealing editor is asked to notify the administrator who made the enforcement action of this appeal, and then to replace this text with a diff of that notification. The appeal may not be processed otherwise. If a block is appealed, the editor moving the appeal to this board should make the notification.

Diff: https://en.wikipedia.org/w/index.php?title=User_talk:ScottishFinnishRadish&diff=prev&oldid=1257767232

Statement by Ecrusized

Greetings all. Today is precisely the 180th day since the filing of my indefinite topic ban on the Arab-Israeli conflict. I was sanctioned for WP:BATTLEGROUND editing, not understanding the arbitration rules, (including 1RR). As well as a commentary towards other editors. During the past 6 months, I have completely refrained from editing any and all topics linked to the Arab-Israeli conflict on English Wikipedia. I have updated the maps of the Israel-Hamas war, and Israel-Hezbollah conflict, on Commons, after confirming with ScottishFinnishRadar, the administrator who sanctioned me, that editing commons was not in violation of my topic ban. I would like to appeal my topic ban in this area because I have now learned about the 1RR rule, what the arbitration commitee is and how its rules work. As well as my personal commentary towards other editors in the topic area. I believe my appeal is just as I have observed all of my sanctions rules since its enforcement, and I have waited 6 months to file this very first appeal on the ban as its required. Thank you all.

Ecrusized response to Red-tailed hawk

Dear Red-tailed hawk, neither of the two articles you've linked, which I have edited during my topic ban, are sanctioned under WP:CT/A-I. During the time of my sanctioning from the topic, I have checked the talk page header of every article I was editing to confirm beforehand that I was not violating my topic ban. 2024 missile strikes in Yemen is an article about US and British strikes on Yemen. The article is not linked to the Arab-Israeli conflict on its talk page header in any way. Instead, it is applied to enforcement for post-1978 Iranian politics. For which I was not placed under restriction for. Regarding the now deleted article, 2024 Turkish Hostage Crisis which I nominated for deletion. It was a news story citing Turkish language sources, once again, not linked to the WP:CT/A-I nor in the scope of that topic. Both of the articles are also not linked Israel, or Arab-Israeli conflict in their categories. Additionally, I was told my the administrator giving me my sanction that I must refrain from editing topics involving Arab-Israeli conflict, which is what I did. I was not told that I must also refrain from editing topics that might be related to that topic area. This is why I am asking for an appeal, and giving a bold statement saying During the past 6 months, I have completely refrained from editing any and all topics linked to the Arab-Israeli conflict on English Wikipedia. If there are clear lines defining this topic ban, I believe I have completely abided by them. Ecrusized (talk) 21:42, 16 November 2024 (UTC)[reply]

Ecrusized 2nd response to Red-tailed hawk

Dear Red-tailed hawk you are indeed correct that 2024 missile strikes in Yemen was sanctioned under WP:ARBPIA at the time of my editing. However, this was not mentined in the talk page header where arbitration enforcements are generally written, and in my notion, without a guideline stating it as such, I did not consider US-UK strikes on Yemen within the scope of Arab-Israeli conflict. This does not appear to be a deliberate or blatant violation of my sanctioning from the topic area, but a misidentification of the enforcement, and its mandated expression. I believe I am asking my appeal in good faith. As an user who was previously heavily involved in editing Arab-Israeli conflict articles, I have nearly completely refrained from editing them, apart from one or two articles where the enforcement was not directly visible. Ecrusized (talk) 10:41, 17 November 2024 (UTC)[reply]

Ecrusized response to Extraordinary Writ

Dear Extraordinary Writ, can you tell me about when I can make this appeal again, given that I will have refrained from any further violations or edit warring in other topic areas by then? Would it be another 6 months in minimum, or can I make an appeal, in say, 3 months from now? Thanks. Ecrusized (talk) 10:30, 23 November 2024 (UTC)[reply]

Statement by ScottishFinnishRadish

Statement by Red-tailed hawk

I am going to note that the user continued to make edits to articles relating to the 2024 missile strikes in Yemen, a topic very much within the scope of the ongoing war (see Israel–Hamas war#Yemen and the Red Sea) after the topic ban was issued on 20 May. These edits include:

A substantial edit to 2024 missile strikes in Yemen made on 31 May;
A page move and associated talk page move related to a specific missile strike in Yemen that was moved on 1 June;
Another set of edits to 2024 missile strikes in Yemen on 16 June.
The user created an AfD for 2024 Turkish hostage crisis on 5 July. The article was about a hostage taking scenario that was a protest against Israeli actions in Gaza.

As such, I am skeptical of the appellant's statement from above, where the appellant said During the past 6 months, I have completely refrained from editing any and all topics linked to the Arab-Israeli conflict on English Wikipedia. — Red-tailed hawk _(nest) 20:33, 16 November 2024 (UTC)[reply]

In response to this comment:

With respect to neither of the two articles you've linked, which I have edited during my topic ban, are sanctioned under WP:CT/A-I, I will note that 2024 missile strikes in Yemen is extended confirmed protected per WP:ARBPIA (see this comment at WP:AELOG/2024#PIA), and that the infobox of 30 May 2024 Yemen strikes at the time of the page move indicated that this was part of the "spillover of the Israel–Hamas war". I do not understand how you reason that neither of these are within the scope of the WP:BROADLY construed Arab-Israeli conflict.
With respect to the deleted article, I have requested it be temporarily undeleted to show the text to everybody. However, it is quite clear to me that an article about a protest action against Israel's actions in the ongoing war would be within the scope of the WP:BROADLY construed WP:PIA tban.

— Red-tailed hawk _(nest) 02:24, 17 November 2024 (UTC)[reply]

I will note that 2024 Turkish hostage crisis has now been restored temporarily for the purposes of this discussion. — Red-tailed hawk _(nest) 02:40, 17 November 2024 (UTC)[reply]

Statement by (involved editor 2)

Discussion among uninvolved editors about the appeal by Ecrusized

Statements must be made in separate sections. They may not exceed 500 words and 20 diffs, except by permission of a reviewing administrator.
Administrators may remove or shorten noncompliant statements. Disruptive contributions may result in blocks.

Statement by (uninvolved editor 1)

Statement by (uninvolved editor 2)

Result of the appeal by Ecrusized

This section is to be edited only by uninvolved administrators. Comments by others will be moved to the sections above.

Even putting RTH's concerns to the side, we still have two warnings recently about 1RR/edit-warring issues—the very same issues that led to the topic ban. I can't support this appeal without a much better track record of avoiding revert-related problems. Extraordinary Writ (talk) 02:50, 22 November 2024 (UTC)[reply]
In response to the question about a possible re-appeal, please wait at least 6 months. I see you have scaled down your activity since the start of the topic ban, making it a bit more difficult to demonstrate a track record of unproblematic edits within 6 months. Note that further violations of your topic ban may lead to escalating blocks, so please read WP:topic ban again to fully understand what broadly construed means (and ask the enforcing admin / any other admin when in doubt). —Femke 🐦 (talk) 15:40, 23 November 2024 (UTC)[reply]

Loveforwiki

This request may be declined without further action if insufficient or unclear information is provided in the "Request" section below.
Requests may not exceed 500 words and 20 diffs (not counting required information), except by permission of a reviewing administrator.

Request concerning Loveforwiki

User who is submitting this request for enforcement: Capitals00 (talk · contribs · deleted contribs · logs · filter log · block user · block log) 04:01, 24 November 2024 (UTC)[reply]

User against whom enforcement is requested: Loveforwiki (talk · contribs · deleted contribs · logs · filter log · block user · block log)
Search CT alerts: in user talk history • in system log

Sanction or remedy to be enforced: WP:ARBPAK

Diffs of edits that violate this sanction or remedy, and an explanation how these edits violate it

23 October - Whitewashing with misleading edit summary. Trying to show that allegiance with Nazism and Imperial Japan is considered bad only in the western world.
27 October - Repeated the above again.
25 October - Created this POV redirect "Bharat country" because he wasn't successful over changing the page on Bharat.
1 November - added a conspiracy theory
9 November - Removes reliably sourced content with dubious edit summary
13 November - Restores his edits without gaining consensus even after being told earlier not to do this.
13 November - Restores his above edit again by using aggressive edit summary
17 November - Suppresses the word "Hindutva" despite the subject being known for it
23 November - Removes the mention of "Trinamool Congress" by locating them to Pakistan

Diffs of previous relevant sanctions, if any

If contentious topics restrictions are requested, supply evidence that the user is aware of them (see WP:CTOP#Awareness of contentious topics): [35]

Additional comments by editor filing complaint

I don't think this editor cares about the consensus process or anything else. He is here mainly to promote Hindutva agenda. Capitals00 (talk) 04:01, 24 November 2024 (UTC)[reply]

Notification of the user against whom enforcement is requested: [36]

Discussion concerning Loveforwiki

Statements must be made in separate sections. They may not exceed 500 words and 20 diffs, except by permission of a reviewing administrator.
Administrators may remove or shorten noncompliant statements. Disruptive contributions may result in blocks.

Statement by Loveforwiki

<moved from Capitals00's section> I am not such kind of user. I adds contents with reliable sources. Sorry if anyone gets such vibes.. Sorry to.l Wikipedia communities. Love for Wikipedia always. Loveforwiki (talk) 04:40, 24 November 2024 (UTC)[reply]

Statement by (username)

Result concerning Loveforwiki

This section is to be edited only by uninvolved administrators. Comments by others will be moved to the sections above.

I appreciate it can be frustrating to edit in a topic area where your views are often in the minority. If you find yourself in such a position, you'll need to come to talk pages with high-quality reliable sources (in high-profile contentious topics, scholarly sources may be needed to convince others). Using misleading edit summaries, attacking other editors (rather than focusing on content) and edit warring are incompatable with editing in a contentious area. Here, and with a previous warning [37], they do not seem interested in acknowledging fault and learning from mistakes. They continue to tag edits as minor [38] that aren't, after being asked to stop in September. Further edits outside of the field ([39]) indicate there may be a broader competence issue here. —Femke 🐦 (talk) 10:23, 24 November 2024 (UTC)[reply]
User:loveforwiki: could you please answer my request to explain when you need to provide attribution in your edit summary? And explain what edit warring is (you denied you were engaged in an edit war on India before). . —Femke 🐦 (talk) 09:25, 30 November 2024 (UTC)[reply]

They continue to edit and are non-communicative. Which makes me lean more towards an indef. —Femke 🐦 (talk) 19:54, 30 November 2024 (UTC)[reply]
I think the most AGF reading of this is that there is a CIR/language issue that is making it difficult to communicate effectively instead of deliberate POV pushing. Either way, I don't think they're a positive in the topic area. For me, the question is if there is a narrow topic ban that would be effective rather than the standard IPA. ScottishFinnishRadish (talk) 13:10, 25 November 2024 (UTC)[reply]
You're thinking about a carve-out of cinema and sport? Are they neatly separated from politics in India, or do conflicts flow over to these topics a lot? I'm open to a narrower topic ban, but I do wonder if the CIR/language issue isn't going to lead to problems elsewhere. —Femke 🐦 (talk) 08:20, 27 November 2024 (UTC)[reply]
From what I've seen there can be quite a significant amount of crossover, e.g. The Kashmir Files. This, along with few admins being very familiar with the topic, is why the topic bans in ARBIPA so often end up covering the whole kit and kaboodle. ScottishFinnishRadish (talk) 13:32, 27 November 2024 (UTC)[reply]
I was ready to just go ahead and block, but I'd be content with an ARBIPA ban. It'd functionally be the same thing. The Blade of the Northern Lights (話して下さい) 13:45, 27 November 2024 (UTC)[reply]
Perhaps, though in the latter case we preserve the ability for the editor to potentially edit some other area of interest instead of just revoking that possibility. — Red-tailed hawk _(nest) 07:15, 28 November 2024 (UTC)[reply]

Rasteem

This request may be declined without further action if insufficient or unclear information is provided in the "Request" section below.
Requests may not exceed 500 words and 20 diffs (not counting required information), except by permission of a reviewing administrator.

Request concerning Rasteem

User who is submitting this request for enforcement: NXcrypto (talk · contribs · deleted contribs · logs · filter log · block user · block log) 10:22, 25 November 2024 (UTC)[reply]

User against whom enforcement is requested: Rasteem (talk · contribs · deleted contribs · logs · filter log · block user · block log)
Search CT alerts: in user talk history • in system log

Sanction or remedy to be enforced: WP:ARBIPA

Diffs of edits that violate this sanction or remedy, and an explanation how these edits violate it

07:15, 21 September 2024 - Introduces close paraphrased content into an article [40]
04:14, 30 October 2024 - Moves a page against the naming convention.
02:59, 1 November 2024 - Edit wars over the same page move with another user while calling it vandalism .
13:52, 9 November 2024 - Does not understand that he is edit warring in spite of being warned about it and doing exactly that.
13:58, 9 November 2024 - Labels edit warring warning he received from me as "retaliatory" when I never interacted with him before this encounter.
14:21, 9 November 2024 - Calling a general sanctions alert on caste topics as a "retaliatory warning".
00:51, 10 November 2024 - Accuses another editor of POV pushing when no one other than him was making a pseudohistorical claim that Zafar Khan of Muzaffarid dynasty was a Jat contravening the academic discussion on the same.
03:00, 10 November 2024 - Claims that he only made a single revert when he has made 3 in 24 hours. [41][42][43]
01:32, 10 November 2024 -Misidentifying an academic Priyanka Khanna with a fashion designer to remove sourced content [44]
11:28 10 November 2024 - Removes good faith talkpage message about above and a general note regarding using minor edits while calling them retaliatory.
01:49, 15 November 2024 - Does not understand WP:BRD, immediately restores his content after being reverted and then asks others to follow BRD.
17:31, 15 November 2024 - Tells others to follow WP:BRD while edit warring to restore his own edits that were reverted, the irony is lost on him.
01:13, 18 November 2024 - Tries to poison the well against me based on a made up on the spot rule ("2RR") when I simply gave my feedback which was requested by an Admin before granting their WP:PERM/RB request.
02:00, 25 November 2024 - Abuses warning templates on a new user's talkpage and then reverts the user when they clear their page. Also review this revision history of their page to see the severity of abuse of warning templates and WP:BITEY behaviour.

Diffs of previous relevant sanctions, if any

Date Explanation
Date Explanation

If contentious topics restrictions are requested, supply evidence that the user is aware of them (see WP:CTOP#Awareness of contentious topics): [45]

Mentioned by name in the Arbitration Committee's Final Decision linked to above.
Previously blocked as a discretionary sanction or contentious topic restriction for conduct in the area of conflict, see the block log linked to above.
Previously given a discretionary sanction or contentious topic restriction or warned for conduct in the area of conflict on Date by Username (talk · contribs · blocks · protections · deletions · page moves · rights · RfA).
Alerted about discretionary sanctions or contentious topics in the area of conflict, on Date (see the system log linked to above).
Gave an alert about contentious topics in the area of conflict to another editor, on Date
Participated in process about the area of conflict (such as a request or appeal at AE, AN or an Arbitration Committee process page), on Date.
Successfully appealed all their own sanctions relating to the area of conflict, on Date.
Placed a {{Contentious topics/aware}} template for the area of conflict on their own talk page.
Otherwise made edits indicating an awareness of the contentious topic.

Additional comments by editor filing complaint: Rasteem is repeatedly failing to meet the standards of acceptable behavior, biting new users, and assuming hostility and bad faith on the part of established editors. His editing in this topic area has been tendentious.Despite being alerted sanctions on caste and WP:ARBIPA, he continues to take part in this behavior and displays WP:CIR issues. There may also be a language barrier given his poorly written or incomprehensible responses. To prevent further disruption in this highly contentious area, I believe a topic ban is the minimum necessary measure here.Nxcrypto Message 10:22, 25 November 2024 (UTC)[reply]

There is a lot to unpack in the wall of text posted by Rasteem.

6th - This is entirely misleading [46]. You did not address how my warning was retaliatory, in fact you are basically still saying that my first ever interaction with you was still somehow retaliatory, this explains it better than I can do
7th -It was not a copy edit, you used a poor cited source(that doesn't have an author) for pushing his caste as Jat, the source in question & quotation in question was added by you in the first place[47].Wikipedia is not a place for boosting a certain caste.
8th - You say that you understand what 3RR is but you are still claiming that making 3 reverts in 24 hours violates it which is not correct.
10th - If you are allowed to remove your messages after you read them, why did you restore your warnings on a newcomer's talkpage, if they have removed it themselves?
13th - Bringing up the conduct of other users in order to make their comments less valid when your own edits are under scrutiny is classic Poison the well fallacy. Your continued attempt to defend that hostile stance there is concerning
14th - You were simply told to leave warnings, not abuse them, abuse is when you give warnings that are not appropriate. I can see that you have given that user multiple final level warnings for vandalism when they clearly did not vandalise, see WP:NOTVANDAL and you are not supposed to issue a warning that is meant to be final again and again, for example you reverted this addition of hyperlinks by a new user @HistorianAlferedo: and issued them a final warning for vandalism,[48] when no one would ever regard that edit as vandalism. You reverted this sourced and well explained edit by the same user and gave them a final warning for vandalism[49][50] Similar thing here [51] [52]. You also restored your warnings after they had cleared them despite being aware of the fact that when a user clears their talkpage it is assumed they have read it. The fact that you do not understand that you were abusing the warnings and are now deflecting the blame saying admins told you to do that is very concerning. Nxcrypto Message 02:20, 27 November 2024 (UTC)[reply]

Notification of the user against whom enforcement is requested[53]

Discussion concerning Rasteem

Statements must be made in separate sections. They may not exceed 500 words and 20 diffs, except by permission of a reviewing administrator.
Administrators may remove or shorten noncompliant statements. Disruptive contributions may result in blocks.

Statement by Rasteem

Answers

1. This was my first sourced article. Before this, I was aware of Copyvio but I wasn't aware of close paraphrasing. After this note,[54] I didn't repeat this mistake.

2. & 3. I moved Hoysala Kingdom > Hoysala kingdom twice. I thought the word "Kingdom" was not part of the full name. After this notice,[55] I didn't repeat such mistakes. It was my mistake; I truly apologize. Next I'll consider making request 4, controversial moves on WP:RM/TR.

5. On Political marriages in India there was a content dispute among different editors.[56] I had talked to the editor who reverted my edits, explained to him why I considered his GC note/warning as retaliatory,[57] and also explained that I wasn't in the intention of edit war.[58] I also shared this issue with another editor[59] and Admin.[60]

6. About General notice of GSCASTE. I gave an explanation to the editor who gave me this notice and explained to him why I considered his warning a retaliatory (see answer#5 & diif #[4]).

7. Addition in Zafar Khan's paragraph as Jat ruler was a copyedit per the cited source.^[1] I wasn't trying to promote a specific POV. I reverted this edit, considering it POV pushing,[61] When my edit was reverted again by another editor, I didn't reinstate it.

8. On 9 November, I accidentally committed a 3RR violation. At the time, 'I was unaware that the 3RR was not only about making 3 reverts using Twinkle.' It also counts as a revert if we remove others's edits through manual or undo features. Please accept my apology considering it my first mistake. 'when I said I didn't conduct an edit war, I said it in the sense that I made only 2 reverts using the Twinkle, then how do I conduct 3RR'. This mistake occurred due to my limited understanding of 3RR. Now I truly know 3RR rule.

9. There are multiple authors named Priyanka Khanna, leading to a misunderstanding. I initially attributed the journal to this one.[62] But it was actually written by another Priyanka.[63]

10. As I'm allowed to remove own talk page messages after reading it. Why I considered a fellow editor's warning as retaliatory (see in answers #5).

11. & 12. On 14 November after this revert, I didn't make further reverts on this page.[64] And left a notice on Talk:page[65] regarding recent revert and removal of content following WP:BRD. On 15 November, I restored the revision of Adamantine123; after, I didn't make any edits there, so I did follow WP:BRD.

13. I didn't try to poison; I gave a reply to Crypto's comment.[66] As he didn't justify how the caste based topic ban is relevant without actual violation of GCCASTE. In my defense, I gave there my explanation; it wasn't in the intention of Poison in the well.

14. I was advised by admin that you have to leave an edit warning for every revert you made without checking edits of a user or talk page history. I asked him, Will it be Back Bitting?[67] If I give many warnings for each revert I made or warning to a user just after their 1st or 2nd vandalism. He said that's incorrect, & it is necessary to leave an edit warning for each revert.[68] I assure Fastily, next I'll always give an edit warning for every revert I'll make.[69] So it was not any abuse of warning templates.

I've condensed my answers to fit the word limit, but I kindly request a slight extension to provide a more accurate and comprehensive summary. As this is my first time at WP:ARE ®asteem Talk 22:38, 28 November 2024 (UTC)[reply]

^ Indian History. Allied Publishers. 1988. pp. B_131. ISBN 978-81-8424-568-4. Gujarat: The independent kingdom of Gujarat was founded by Zafar Khan, son of Sadharan, a Jat convert to Islam.

Further answers

6. Sorry, but nothing was misleading in my answers. You didn't ask me for the clarification of why I considered your warning as retaliatory. So I didn't get a chance to clarify. I had the opportunity to respond to a fellow editor's note, which I perceived as retaliatory, I gave him full clarification, and I also discussed your warning.[70] In this conversation with the admin I discussed how many warnings I considered retaliatory and for what reasons.[71]

7. Your provided diff is an older one when I added 3 paragraphs with four sources.[72] Your point is that I used one non-reliable source. Instead of removing this source and related paragraph or discussing it, you labelled this addition as POV. Later I removed the word 'Jat'[73] from this paragraph, then I thought someone would object why I only removed this word even the source mentioned it?. Then I copyedited & added this word again.[74]

8. I understand the 3RR rule here is also some points from 3RR: (1).An editor should not violate 3 reverts on the same page in 24hr involving the same or different text. (2). 4th revert outside of 24hr will also be considered as an edit warning. (3). The first violation of 3RR led us to the 24-hour block. (4). If one person violates 3RR using multiple accounts, it will also be considered a violation of 3RR. (5). WP:AVOIDEDITWAR.

13. My explanation on the rollback request was to reply to Crypto's comment, using the right of reply, that was not in the intention of "Poison in the well". So it was just a reply, nothing else.

14. That's incorrect. I didn't violate user talk page warning templates. I just gave a warning notice for each revert I made to acknowledge to the user that I reverted their edits (See some disruptive edits).[75][76][77][78][79]

This edit removed source and related content without an edit summary.[80][81]
I reverted this edit[82] per WP:CASTECRUFT same kind of reverts were also made by other editors.[83][84]
This edit removed the word 'Yaduvanshi rulers' & added random 2-3 links without an edit summary.[85] final/4th warning was in the sense that I had already left 3 warnings for each of their edits.[86]
This edit removed the content 'Chaudhary family & Lohar clan of Rajputs' without an edit summary.[87] final warning was in the sense that I had already left 3 warnings for each of their reverts.[88]

Users are allowed to blank their talk pages, so restoration of the old revision of the talk page was really not necessarily, but it was my bad luck that I restored. It was in the sense user showed no signs of learning from their past week's disruptive edits. Additionally, I was compelled to report the user's disruptive edits to WP:AIV.

Femke, Thank you for clarifying the 3RR rule for me. I've removed excessive styling, excessive detailing, and a comment, which gave the impression that maybe I was more focused on the person than on the content.[89] Definitely, I'll step back from making mistakes & I'll make sure I understand the policies before discussing them. I will focus on the content rather than the person in future discussions. I admit it was not a good practice that I gave a final warning even after 3-4 warning notices; it was unnecessary, and next I'll consider it. Yes, I did report this user at AIV[90] and I was advised to consider reporting user at ANI.[91]

Note for Admin:

My first & last interactions with NXcrypto was limited to Political marriages in India there we had a content dispute. On my rollback request, he was asked for his opinion: "He claimed Rasteem is on the verge of the topic ban." Later, he filed this report instead of resolving the content dispute on article's talk page. This report seems like a coordinated attempt to get rid of edit disputes from Arbitration Enforcement. I'll request the admin please also consider this and check my contributions that is largely for reverting vandalism at RC patrol.[92]

I previously raised concerns with Admin:ToBeFree about receiving unwarranted edit warnings after making constructive edits on Rajput & Political marriages in India.[93]

I'll request to check page history (10 October-November 2024)[94]. NXcrypto also had edit warnings and content disputes with other editors like @Adamantine123: & @LukeEmily: Above in my answers I acknowledge and apologize for the mistakes I made, all of which were first-time errors those I didn't repeat. (just noting that this is a comment by User:Rasteem. Liz ^{Read! Talk!} 06:58, 29 November 2024 (UTC))[reply]

Statement by LukeEmily

Looking at their edit history, I think Rasteem is doing a good job across wikipedia. I have had very brief interactions with @Rasteem:. Came across this page when I was posting a message on their talkpage and was surprised to find this complaint. I do not see any POV pushing for any caste by Rasteem. Most of the above items seem to be unintentional innocent mistakes - made by many senior editors - and I will go through each of them one by one. For example, Priyanka Khanna misidentification might just be because google showed up the incorrect search results. They are also polite, for example - [ https://en.wikipedia.org/w/index.php?title=Rajput&diff=prev&oldid=1256533002 ] here they even apologised to @Adamantine123: although it was not necessary. I don't think any ban is necessary.LukeEmily (talk) 22:45, 26 November 2024 (UTC)[reply]

Statement by (username)

Result concerning Rasteem

This section is to be edited only by uninvolved administrators. Comments by others will be moved to the sections above.

Definitely seeing some caste shenanigans and edit warring, although the edit warring is fairly widespread. Interested in seeing the response. ScottishFinnishRadish (talk) 13:36, 25 November 2024 (UTC)[reply]
Rasteem: your response is now over 2,000 words. Per the instructions, can you please summarize this within 500 words and 20 diffs or ask for a (small!) extension to the word limit and summarize it to the new word limit. —Femke 🐦 (talk) 08:00, 27 November 2024 (UTC)[reply]
Rasteem, you're again over the word limit. I'll grant you a 200-word extension for your "Further answers", so please condense this significantly. Also, please avoid "shouting" via excessive bolding and colouring.

On the merits: in general, Rasteem is not the only to resort to disruptive behavior: there is too little discussion. In particular, Rasteem, you really need to WP:focus on content, rather than on the person. For edit warring, I expect an editor of your tenure to know that (a) you don't need to break the 3RR red line for something to count as edit warring. Experienced editors usually use BRD, meaning they only do 1 revert. (b) violating 3RR means at least 4 reverts, not 3. Move warring in particular is really not done (and WP:RM/TR is not the place for contentious moves. A normal WP:RM is). In terms of warning a new user, 4 final warnings does not make any sense, please ensure you report to AIV instead. The advice to leave a warning on each revert does not apply after 4 warnings. It's a good sign you admit when you're wrong in some cases, but you need to step back and ensure you understand policies before talking about them.

Given the willingness to learn, I wonder if a WP:1RR restriction and a warning for WP:civility might suffice. I'm not against a topic ban either. —Femke 🐦 (talk) 10:03, 30 November 2024 (UTC)[reply]

Arbitration enforcement action appeal by InedibleHulk

Procedural notes: Per the rules governing arbitration enforcement appeals, a "clear and substantial consensus of uninvolved administrators" is required to overturn an arbitration enforcement action.

To help determine any such consensus, involved editors may make brief statements in separate sections but should not edit the section for discussion among uninvolved editors. Editors are normally considered involved if they are in a current dispute with the sanctioning or sanctioned editor, or have taken part in disputes (if any) related to the contested enforcement action. Administrators having taken administrative actions are not normally considered involved for this reason alone (see WP:UNINVOLVED).

Appealing user: InedibleHulk (talk · contribs · deleted contribs · logs · filter log · block user · block log)

Sanction being appealed: WP:CT/AP. (Original 1-year site ban, appeal converting this into t-bans)

Administrator imposing the sanction: Seraphimblade (talk · contribs · blocks · protections · deletions · page moves · rights · RfA)

Notification of that administrator: Here.

Statement by InedibleHulk

I was originally banned on July 13, 2023, for mostly GENSEX reasons. Since then, I've avoided both contentious topics and barely bothered anyone in other fields. The elections now over, what I perceive to be the problem others foresaw me causing is moot, and I'd like to be able to clean up uncontroversial articles like (but not strictly limited to) Mike Sherstad and Joseph Serra. InedibleHulk (talk) 06:21, 30 November 2024 (UTC)[reply]

I'm not sure I understand Femke's question. Problems (namely using female pronouns for a mass murderer most believed was a man and for too heavily arguing my case) led to my block; repeated assurance that I would stop eventually led to my unblock. I think the "avoid American politics" part came up because mass murder and gender disputes were hot-button issues at the time; some wanted me banned from gun control instead. It may have had something to do with things I said in previous elections about how Trump was preferable to Clinton or how Harris should have beat Biden. I didn't really have much to feel or say about Trump vs Harris, even if I could have, and that much hasn't changed. I was only as interested as I was in Trump's prior campaigns because he was a pro wrestling personality; now that he's more fully transitioned into a regular politician, I'll let politics regulars handle him, his opponents and whatever resultant subtopics and drama. InedibleHulk (talk) 06:47, 1 December 2024 (UTC)[reply]

And while this appeal seeks an AP2 unban alone, I think GoodDay is right that I might prove myself an improved GENSEX editor now as well, if given that chance. InedibleHulk (talk) 06:50, 1 December 2024 (UTC)[reply]

Statement by Seraphimblade

I would tend to agree that this is pretty short on detail. I would like to see the response to Femke's question before making further comment. Seraphimblade ^{Talk to me} 00:57, 1 December 2024 (UTC)[reply]

Statement by (involved editor 1)

Statement by (involved editor 2)

Discussion among uninvolved editors about the appeal by InedibleHulk

Statements must be made in separate sections. They may not exceed 500 words and 20 diffs, except by permission of a reviewing administrator.
Administrators may remove or shorten noncompliant statements. Disruptive contributions may result in blocks.

Statement by GoodDay

Lift the t-bans - IMHO, any editor deserves a chance to prove themselves & there's only one way for that to happen. GoodDay (talk) 19:22, 30 November 2024 (UTC)[reply]

Statement by (uninvolved editor 2)

Result of the appeal by InedibleHulk

This section is to be edited only by uninvolved administrators. Comments by others will be moved to the sections above.

This appeal is very light on details. What problems were there that led to the unblock conditions and how do you plan to avoid them in the future? —Femke 🐦 (talk) 19:13, 30 November 2024 (UTC)[reply]

Selfstudier

This request may be declined without further action if insufficient or unclear information is provided in the "Request" section below.
Requests may not exceed 500 words and 20 diffs (not counting required information), except by permission of a reviewing administrator.

Request concerning Selfstudier

User who is submitting this request for enforcement: ABHammad (talk · contribs · deleted contribs · logs · filter log · block user · block log) 13:36, 1 December 2024 (UTC)[reply]

User against whom enforcement is requested: Selfstudier (talk · contribs · deleted contribs · logs · filter log · block user · block log)
Search CT alerts: in user talk history • in system log

Sanction or remedy to be enforced: WP:ARBPIA, WP:EDITWAR, WP:POVPUSH

Diffs of edits that violate this sanction or remedy, and an explanation how these edits violate it

Context: Following a content dispute whether the "Gaza genocide" should be included on the Israel article, an RfC on the topic was started on 22 November.
On 27 November, despite the ongoing RfC, User:Selfstudier added content related to the "Gaza genocide" to the article anyway. [95]
Another editor reverted the addition and requested that Selfstudier refrain from adding the disputed content while the RfC is still ongoing. [96]
A few minutes later, Selfstudier restored it anyway [97]

Selfstudier says the RfC is about the lead, not the body, but the RfC is clearly about the body too (check the text here [98]). I contacted Selfstudier on their talk page asking them to self-revert [99] but they said this wasn't edit warring [100], asking me to re-read the RfC (which I read, and is clearly on the body too) and threatened to report me for making a 'false accusation'. Then they went on to remove our discussion from the page [101].

Overall this isn't the first time I'm seeing Selfstudier forcibly pushing their own POV by restoring disputed content in the middle of dispute. For example see Genocide of indigenous peoples [102], Palestinians [103], Zionism [104]

Diffs of previous relevant sanctions, if any

[105] Formal warning on removing discussions (October 2024)

If contentious topics restrictions are requested, supply evidence that the user is aware of them (see WP:CTOP#Awareness of contentious topics)

Selfstudier is the main editor posting PIA CTOP messages on user talk pages. [106].

Additional comments by editor filing complaint

Notification of the user against whom enforcement is requested

[107]

Discussion concerning Selfstudier

Statements must be made in separate sections. They may not exceed 500 words and 20 diffs, except by permission of a reviewing administrator.
Administrators may remove or shorten noncompliant statements. Disruptive contributions may result in blocks.

Statement by Selfstudier

The first editor to respond thought the RFC was not actionable and did not understand why the RFC was "Considering a link alone in the aether..".

As second to respond, neither did I, since it would it not be possible to add a link in the lead (Option 2) without there being material in the article body discussing the Gaza genocide. So I first suggested that opener should pull the RFC while that was developed.

When that suggestion was not taken up, I prepared a suitable paragraph and posted it at the RFC with the intention of adding it to the article body and which I subsequently did. Any editor could have done this at any time nor was this edit warring, as reporting editor complained of at my talk, because the material that Huldra had previously added to the article was completely different and was added to the lead not to the article body.

When my addition was reverted, I reverted on the basis that the RFC was about adding a link to the lead and not about adding relevant material to the body. Thus, I made precisely one revert, which is not edit warring. In my subsequent !vote, I then indicated option 2 and specified where in the lead the link should be placed. I didn't go ahead and add that link because from my perspective, that is what the RFC is actually about and what RFC opener had actually tried to do initially.

I have no idea what the POV pushing allegation is about, seems reporting editor is simply padding their report. If they think those accusations have any merit, then I would suggest they include them with proper evidence at the current ARBCOM case, where I am a named party. Selfstudier (talk) 15:26, 1 December 2024 (UTC)[reply]

Statement by Butterscotch Beluga

I'm only going to comment on the examples given concerning previous possible POV pushing

Genocide of indigenous peoples - The first RFC results were "no consensus" with the closing words: "Our policy on WP:NOCONSENSUS provides further guidance on what to do in situations like this." WP:NOCONSENSUS says "When discussions of proposals to add, modify, or remove material in articles end without consensus, the common result is to retain the version of the article as it was prior to the proposal or bold edit.", so Selfstudier was correct to revert to the status quo, which was inclusion.
Palestinians - ABHammad also participated in the edit war several times, including after sources supporting the contested material were given.
Zionism - This was part of an edit war trying to undue the bold edit of a now blocked sock, discussed further here. - Butterscotch Beluga (talk) 16:27, 1 December 2024 (UTC)[reply]

Statement by (Doug Weller)

I apologise for having no time right now for an indepth analysis, but when I first saw this I assumed it was Selfstudier bringing this here. So far as I know the 0revert imposed upon ABHammad by User:Barkeep49 still remains in place. Doug Weller talk 17:02, 1 December 2024 (UTC)[reply]

Statement by (username)

Result concerning Selfstudier

This section is to be edited only by uninvolved administrators. Comments by others will be moved to the sections above.

[1] Wikipedia:Arbitration/Policy § Scope and responsibilities

[2] Wikipedia:Arbitration/Policy § Procedures and roles

[3] The administrator may indicate consent at any time before, during, or after imposition of the restriction.

[4] This criterion does not apply if the original action was imposed as a result of rough consensus at the arbitration enforcement noticeboard, as there would be no single enforcing administrator.

[5] Indian History. Allied Publishers. 1988. pp. B_131. ISBN 978-81-8424-568-4. Gujarat: The independent kingdom of Gujarat was founded by Zafar Khan, son of Sadharan, a Jat convert to Islam.

[1]

[2]

[a]

[b]

[1]

Abstentions	Support votes needed for majority
0–1	6
2–3	5
4–5	4

Abstentions	Support votes needed for majority
0–1	6
2–3	5
4–5	4

Abstentions	Support votes needed for majority
0–1	6
2–3	5
4–5	4

Abstentions	Support votes needed for majority
0–1	6
2–3	5
4–5	4