Jump to content

Wikipedia:Arbitration/Requests

Page semi-protected
From Wikipedia, the free encyclopedia

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:


Amendment request: Palestine-Israel articles 4

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

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

Statement by Newslinger

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

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

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

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

Statement by Patternbuffered

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

Statement by Long-live-ALOPUS

Statement by Thryduulf

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

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

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

Statement by Zero0000

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

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

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

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

Statement by Rosguill

I think Elli raises a valid concern, and would suggest that any extended-confirmed editor should be allowed to remove such a notice. If we're concerned about these notices as a locus of disruption (would they be so moreso than anything else to do with the conflict?), you could adopt language to the effect that any gaming or editwarring in relation to such notices be treated with extreme prejudice or some other such guidance. signed, Rosguill talk 01:45, 26 October 2025 (UTC)[reply]

Statement by {other-editor}

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

Palestine-Israel articles 4: Clerk notes

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

Palestine-Israel articles 4: Arbitrator views and discussion

Motion: Repealing primary articles/related content distinction

Remedy 4 of the Palestine-Israel articles 4 case ("Definition of the 'area of conflict'") is amended to read as follows: For the purposes of editing restrictions in the ARBPIA topic area, the "area of conflict" is the Arab-Israeli conflict, broadly interpreted.

Remedy 5 is amended by appending the following text: The {{ArbCom Arab-Israeli editnotice}} editnotice and the {{ArbCom Arab-Israeli enforcement}} talk page notice should be used on pages within the area of conflict. When only parts of a page fall within the area of conflict, if there is confusion about which content is considered related, the content in question may be marked in the wiki source with an invisible comment. Once added by any editor, any marking, template, or editnotice may be removed only by an uninvolved administrator.

Remedy 6, Remedy 7, and Remedy 8 of the Palestine-Israel articles 4 case are repealed.

For this motion there are 14 active arbitrators. With 1 arbitrator abstaining, 7 support or oppose votes are a majority.
Support
  1. ~ ToBeFree (talk) 23:12, 9 October 2025 (UTC)[reply]
  2. ScottishFinnishRadish (talk) 23:28, 9 October 2025 (UTC)[reply]
  3. Daniel (talk) 00:05, 10 October 2025 (UTC)[reply]
  4. I'm not keen on expanding this restriction if not strictly necessary, but the ambiguity between the different pages is causing confusion amongst editors and resulting in editors being sanctioned for making edits they they believe they are permitted to make because of the way things are worded. I considered proposing a less vague wording that would make a userspace exception more clear, but having a different set of ECR rules specifically for this topic area is unnecessarily complicating the issue. Standardizing the wording to match ECR's scope is the best route towards uncomplicating this as much as possible. - Aoidh (talk) 03:16, 11 October 2025 (UTC)[reply]
  5. While this narrows the topic area a little bit, I think this will help lessen confusion and bureaucracy. If problems come up later, editors are invited to go to the appropriate noticeboard to find a resolution. Z1720 (talk) 00:01, 16 October 2025 (UTC)[reply]
  6. This will hopefully reduce confusion. HJ Mitchell | Penny for your thoughts? 14:41, 18 October 2025 (UTC)[reply]
  7. theleekycauldron (talk • she/her) 18:32, 24 October 2025 (UTC)[reply]
Oppose
Abstain
  1. I don't like the implementation here: allowing someone to add a comment that only admins can remove seems like a bad idea. What if there's an article that has a section that touches on this conflict (and is appropriately tagged), but someone wants to remove that section (for example, they think it's out of scope for the article)? They wouldn't be allowed to do so here (or they'd need to keep a comment around for a section that no longer exists). Abstaining because no better solution comes to mind for me right now. Elli (talk | contribs) 01:36, 26 October 2025 (UTC)[reply]
Arbitrator discussion

Clarification request: Extended confirmed restriction

Initiated by Ahecht at 14:54, 9 October 2025 (UTC)[reply]

Case or decision affected
WP:ARBECR

List of any users involved or directly affected, and confirmation that all are aware of the request:

Confirmation that all parties are aware of the request

Statement by Ahecht

I am requesting clarification on whether contesting a speedy deletion on the talk page is considered an edit request for the purposes of WP:ARBECR. This issue originally came up at Wikipedia:Village pump (technical)/Archive 224#User Intarface encourages actions that are against rules and can have unintended consquences for new users and was further discussed at Template talk:Db-meta#Modify Db-meta template to hide "Contest this speedy deletion" button to non-extended-confirmed users on pages with ARBECR restriction.. In the latter discussion, Primefac suggested that contesting an speedy deletion on the talk page could potentially be considered a type of edit request, while HouseBlaster was unsure whether we should prevent a non XC editor from contesting a speedy deletion altogether because the likelyhood of success is low, or whether we should modify the notice to instruct all non-XC editors, even if they're not the page creator, to contest on the talk page rather than trying to remove the speedy deletion tag themselves if the page is subject to WP:ARBECR.

Statement by GWWU

Statement by Nil Einne

My view is it arguably is technically possible for contesting a speedy deletion to be an edit request but it's of so little benefit it's not worth saying it is lest it confuses people. Let's remember an edit request isn't for simply requesting a change to an article but requesting a change either already has consensus or so simply that it clearly has consensus even for someone unfamiliar with anything about the article (i.e. uncontroversial) e.g. a typo correction, adding details to a ref etc. Edit requests shouldn't be used for proposing controversial changes, editors should start a discussion and gain consensus first. If they cannot start a discussion because of ARBECR, then using an edit request to initiate a discussion is IMO a clear abuse of ARBECR even if they stay out of it after. Given all that, it's technically possible for contesting a speedy deletion to be an edit request when it's so simple that any editor with extended confirmed status even one who knows almost nothing about speedy deletion would be willing to remove the speedy deletion template because there's something so problematic about it that they do not need to let an admin or at least someone more familiar with speedy deletions look it over. But in such cases, surely an admin would see that without needing to be told. And so all this is doing is hoping some other extended confirmed editor sees it first and removes it to slightly reduce the workload on admin. But if we say it's okay, it's far more likely that it will be mostly used by non EC editors in cases where it's not so simple why the speedy deletion template shouldn't be removed but this isn't allowed similar to the way editors cannot make "edit requests" which are actually an attempt to start discussion on controversial changes. Nil Einne (talk) 08:37, 13 October 2025 (UTC)[reply]

Statement by {other-editor}

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

Extended confirmed restriction: Clerk notes

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

Extended confirmed restriction: Arbitrator views and discussion

  • Contesting a CSD is not an edit request. If you can't discuss the deletion of an article you can't request a CSD be removed or added. ScottishFinnishRadish (talk) 14:59, 9 October 2025 (UTC)[reply]
  • Not an edit request in my opinion, which has a very narrow definition. Prohibited by ARBECR. Daniel (talk) 19:45, 9 October 2025 (UTC)[reply]
  • It doesn't matter much. "Contesting" a speedy deletion is a non-formal process adding a mostly meaningless message to a talk page that, if we're honest, often won't even be read before deletion. It is not the start of a formal internal project discussion such as an actual deletion discussion at WP:AfD. And it is equivalent to creating a formal edit request for "Please replace {{the CSD template}} by nothing". To me, it doesn't matter if we explicitly forbid making the last protesting comment before the page and the comment are removed forever. We should perhaps clarify that blocking someone for clicking a button inviting them to do so, and de-facto for creating an edit request, would be rather inappropriate. ~ ToBeFree (talk) 20:29, 9 October 2025 (UTC)[reply]
    PS: I think the only reason why this blue button exists is to secretly discourage users from removing the speedy deletion template by letting them send a meaningless message, channeling their frustration to a place where it doesn't disrupt the process, instead. ~ ToBeFree (talk) 23:07, 9 October 2025 (UTC)[reply]
  • I seem to find myself in the minority here, but I think that the example given by ToBeFree is exactly how a contested deletion request should be taken. "Please remove this deletion nomination because..." is a request to edit a page they should not normally be able to edit. Just because it is not headed by {{edit protected}} should not immediately invalidate it, and just because they cannot participate any further than making the request does not mean the request needs to be invalidated. Primefac (talk) 23:55, 12 October 2025 (UTC)[reply]
    I don't think you're in the minority there, as I agree. - Aoidh (talk) 02:45, 13 October 2025 (UTC)[reply]
    CSD is a deletion process that falls outside article content. Since one of the main points of ECR was to keep non-EC editors out of internal processes it seems to me that they shouldn't be making arguments as to why a page shouldn't be deleted. It's the same as RMs not falling under edit requests even though they're requesting a change to the article. ScottishFinnishRadish (talk) 10:51, 13 October 2025 (UTC)[reply]
  • This seems like a very edge case but I agree with TBF. "Please don't delete this page" is largely equivalent to an edit request. It's an action that doesn't have much effect anyway because if the page unquestionably meets the CSD it will be deleted anyway, and if it clearly doesn't the speedy will be declined but I wouldn't want to rule out an edge case within an edge case where a non-EC editor can add vital context. But more importantly blocking somebody for contesting a speedy deletion would seem absurdly bureaucratic, and policing the content of a talk page that is about to be deleted is probably a waste of time and would come across as mean-spirited. HJ Mitchell | Penny for your thoughts? 14:58, 18 October 2025 (UTC)[reply]
  • Given that CSD contesting is one of the few areas where consensus isn't a factor, I don't really see the harm in allowing it, especially when they wouldn't be allowed to follow up at AN or DR. theleekycauldron (talk • she/her) 18:37, 24 October 2025 (UTC)[reply]
  • Inclined to allow contesting/keep the button, per others. Elli (talk | contribs) 02:11, 26 October 2025 (UTC)[reply]

Initiated by Johnpacklambert at 16:43, 18 October 2025 (UTC)[reply]

Case or decision affected
Conduct in deletion-related editing arbitration case (t) (ev / t) (w / t) (pd / t)
Clauses to which an amendment is requested
  1. 4) Johnpacklambert (talk · contribs) is banned from taking the following actions: (1) participating in deletion discussions, broadly construed; (2) proposing an article for deletion ("PRODing"), but not contesting a proposed deletion ("de-PRODing"); and (3) turning an article into a redirect. This sanction supersedes his March 2017 community topic ban. This ban may be appealed twelve months after the enactment of this remedy, and every twelve months thereafter.
  2. Link to the principle, finding, remedy, section, etc for which you are requesting amendment
List of any users involved or directly affected, and confirmation that all are aware of the request
Confirmation that all parties are aware of the request
  • [diff of notification Username]
  • [diff of notification Username]
Information about amendment request
  • 4) Johnpacklambert (talk · contribs) is banned from taking the following actions: (1) participating in deletion discussions, broadly construed; (2) proposing an article for deletion ("PRODing"), but not contesting a proposed deletion ("de-PRODing"); and (3) turning an article into a redirect. This sanction supersedes his March 2017 community topic ban. This ban may be appealed twelve months after the enactment of this remedy, and every twelve months thereafter.
    • I want it to be clear this clause allows me to participate in categories for discussion
  • Link to the principle, finding, remedy, section, etc for which you are requesting amendment
    • State the desired modification

Statement by Johnpacklambert

The restriction on my participation in deletion discussions and related discussions was imposed in July 2022. I understand that I was at times too combative on issues and apologize for that. The discussion at the time focused only on my participation in article deletion discussions. However when the restriction was written it was written in a way to cover topic discussions on things other than articles. This included a ban on participation in discussions about categories. After almost 38 months I am asking that that specific part of the restriction be lifted so that I can participate in discussions about deleting, merging and renaming categories. I understand these restrictions were imposed for wise reasons back in 2022, but I feel allowing me to participate in Category discussions would be reasonable at this time. The decision speaks of reconsideration after 12 months. There has been no discussion on this restriction now for I believe 22 months, and I better understand now how to cooperate with others. I feel allowing me to participate in Categories for discussion discussions would be a reasonable modification of this restruliction at this time. John Pack Lambert (talk) 16:43, 18 October 2025 (UTC)[reply]

  • I was wrong in my actions in late 2022 that lead to a total editing ban for a time. That was over 3 years ago and I have not done anything like that since. I have tried to avoid discussing deleting articles at all. My understanding was that the ban applied to articles. I did not think it prevented me from making comments on the organization of categories. I was under the impression that I was not able to participate at CfD because the pan on Afd was extended to other general discussion formats. My understanding though was that the broad ban on discussing deletion was a ban on deleting of articles, broadly construed, and did not apply to non-article things such as categories.John Pack Lambert (talk) 19:42, 18 October 2025 (UTC)[reply]

Statement by GoodDay

The best way to learn if an editor has learned their lesson, is to allow them to prove it. Recommend lifting the aforementioned restrictions. GoodDay (talk) 16:58, 18 October 2025 (UTC)[reply]

Statement by SarekOfVulcan

Per GoodDay above, that's the way to find out if it's going to work. SarekOfVulcan (talk) 17:04, 18 October 2025 (UTC)[reply]

Statement by HouseBlaster

Johnpacklambert has a habit of requesting that editors merge categories, time and time again. Their talk archives have plenty of examples (I have yet to find one without such comments), and they were blocked for violating their topic ban back in 2022 following an AE thread.

I gave Mr. Lambert a note about this last year, and it seems the behavior has continued. However, AE seems to think that merge/rename nominations are not covered by the topic ban. I strongly believe that merger discussions are covered; the only difference at CFD between "merge" and "delete" is whether the former contents of the category are added to another before deletion. I have no firm opinion on whether rename discussions at CFD are covered, though a sizeable minority of rename nominations end with deletion or merging. If the ban is not lifted or narrowed, some clarification on what is and is not permitted would be appreciated.

Best, HouseBlaster (talk • he/they) 18:40, 18 October 2025 (UTC)[reply]

Harry, I was deliberately vague about that because I don't have a firm opinion on the matter :) ... consider my above comment something of a Brandeis brief.

From what I can tell, the restriction was a deliberately overbroad; to paraphrase a recent vote of yours, it was ensuring the same caravan did not pack up and move on to overzealous deletion of categories or files or drafts. Mr. Lambert was already under a community XFD restriction, an unrelated topic ban in religion, his block log is not super pretty, and a site ban was on the table and was seriously considered; in those circumstances, broad strokes would seem wise. Using more refined strokes would not be a terrible idea, though I would oppose repealing the ban wholesale; the article deletion processes (PROD, AFD, BLARing articles) should continue to be covered. A suspended removal, allowing uninvolved admins to reinstate the ban if need be, would be wise. In other words, I think a probationary lift allowing all participation regarding CFD would not be a terrible idea.

My impression of Mr. Lambert's comments are that they are helpful, though I have not read them in detail. I would be curious to hear Smasongarrison's thoughts on lifting the topic ban; she is a category superstar, CFD regular, and has interacted with Mr. Lambert frequently. My real advice would be to listen to whatever she says :)

Best, HouseBlaster (talk • he/they) 03:16, 20 October 2025 (UTC)[reply]

Statement by Pppery

This topic ban was imposed for overzealous behavior in AfD discussions. It never made sense to expand its scope beyond AfD discussions and I would suggest it be narrowed to that. * Pppery * it has begun... 18:47, 18 October 2025 (UTC)[reply]

Statement by Smasongarrison

I have mixed feelings about JPL becoming more involved at CFD. He has a long history with categorization. Most of the discussion has focused on his topic ban in terms of article work, but historically, he's had similar issues in categorization (e.g.,Wikipedia:Administrators'_noticeboard/IncidentArchive1073#User:_Johnpacklambert_emptying_categories_prematurely;_edit_warring, which makes this directly relevant here.

On one hand, I do think he's shown real growth. When editors are willing to put in the time to work with him, he's open to the feedback and able to have productive conversations. On the other hand, consistent follow-through on that feedback hasn't been his strong suit.

My main concern with full participation at CFD is that he can be extremely rigid on certain topics, particularly when it comes to distinctions between nationals from modern and/or former countries. That rigidity tends to cause recurring friction (e.g., recent ones include [1] User_talk:Johnpacklambert/Archives/2025/October#Manually_overriding_templates, User_talk:Johnpacklambert/Archives/2025/August#Please_populate,_parent,_and_sort_key_the_categories_you_create). There's also a bit of irony in his approach: he often points out that categories are underpopulated and should be merged, but he continues to create new, narrowly defined ones of the same kind, without recognizing the contradiction.

All that said, I don't think the answer is to exclude him entirely. He does have good ideas and, given structure and oversight, can make valuable contributions. I'd support allowing him to comment in CFD discussions but not to make proposals himself. I think that that would strike the balance between giving him the opportunity to demonstrate his growth, without disrupting the project. SMasonGarrison 05:01, 20 October 2025 (UTC)[reply]

Statement by FOARP

I've been very occasionally keeping tabs on JPL and as far as I can see the ban converted them into an effective, productive, gnoming member of the EN WP community, and they have (admittedly with some shakiness at the start) kept their nose clean. I can't claim to have reviewed every edit they've made since the ARBCOM decision, but the ones I've reviewed have been entirely on-point. In the spirit of WP:ROPE I think at the very least the request can be granted, and that possibly loosening of restrictions can go further. FOARP (talk) 10:52, 20 October 2025 (UTC)[reply]

S Marshall

  • As a participant in the Arbcom case being modified, I would support this provided that JPL's reintroduction to deletion discussions rate-limited in some way, such as for example: (a) participating in no more than one XfD at a time (he can choose a new one to participate in when the previous one is closed); or (b) editing no more than one XfD page per day.
JPL's conduct in individual XfDs isn't highly problematic. It's the aggregate effect of participating in hundreds of them.—S Marshall T/C 16:14, 21 October 2025 (UTC)[reply]

Statement by Barkeep49

At the time of the decision, JPL asked if merges were included in the topic ban, and then arb L235 answered yes something that I, as another then arb agreed with at that time. I believe there might have been more discussion about this either on arbwiki or the list (or maybe it was IRC) at the time. Best, Barkeep49 (talk) 23:04, 24 October 2025 (UTC)[reply]

Statement by {other-editor}

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

This area is used for notes by the clerks (including clerk recusals).
  • I'm reasonably receptive to this request but XfD is not my area of expertise. HouseBlaster@ should I take your comment as opposition to the request? Besides the ambiguity of whether the restriction applies to CfD, have JPL's contributions there been disruptive or unhelpful? HJ Mitchell | Penny for your thoughts? 23:25, 19 October 2025 (UTC)[reply]
  • There was some discussion of whether merge discussions are incorporated into this sanction at that AE thread, but I think the controlling factor was really the nature of his participation and the question wasn't fully dissected. I would hold that participating directly in a merge discussion almost certainly violates the restriction. They involve whether a standalone page should exist or not, which gives them a lot of the same personal-philosophy baggage as AfD.
    As for amending the sanction to allow weighing in on categories, I'm hesitant. As I understand it, the category area combines a lot of procedural rigor with a tendency for controversy disproportionate to the weight of the matter a la ARBCAPS. If we were to do something that allows him to show he's here to contribute constructively, I'd say an unban that allows for a maximum of 3 CfD comments per day – limited to 1 comment per thread, 500 words per comment, and no nominations – would be my starting place. theleekycauldron (talk • she/her) 18:48, 24 October 2025 (UTC)[reply]
  • I think leek's idea for cats is a reasonable way to proceed, maybe with a 6 month wait before review. ScottishFinnishRadish (talk) 22:46, 24 October 2025 (UTC)[reply]


Gotitbro

Theonewithreason

إيان

Gicarke

Aesurias

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 Aesurias

User who is submitting this request for enforcement
TheNewMinistry (talk · contribs · deleted contribs · logs · filter log · block user · block log) 23:31, 22 October 2025 (UTC)[reply]
User against whom enforcement is requested
Aesurias (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:AC/CT
Diffs of edits that violate this sanction or remedy, and an explanation how these edits violate it
  1. 19 September 2025 Responded to second warning from admin by asking the same admin to engage in WP:PROXYING on their behalf
  2. 23 September 2025 Added WP:FALSEBALANCE to politician's article with weasel-wording about their support of Palestine relief group UNRWA - they had previously tried to insert the same unsourced information into the article back in March ([45])
  3. 28 September 2025 Reclassified an Israel-sponsored trip by right-wing political figure, implying such trips are not controversial
  4. 29 September 2025 Removed sourced quote from pro-Israel politician's article where she equated Palestinians to barbarians
  5. 2 October 2025 Removed passage identifying group's founder as Gerald Ronson and his connection to Netanyahu - Aesurias acknowledged the information is correct and should be in lead instead, but chooses to delete everything
  6. 3 October 2025 Removed passages explaining that Israeli-Americans voted overwhelmingly Republican in the 2012 US Presidential Election, and that democratic socialist Bernie Sanders is Jewish
  7. 9 October 2025 Admonished another user for removing a tag from an article they created, telling them "DO NOT REMOVE A TAG WITHOUT IT BEING DISCUSSED, ESPECIALLY IF IT IS YOUR OWN ARTICLE"
  8. 10 October 2025 Tagged The Holocaust and the Nakba for deletion, but was widely rebuked in the AFD discussion and it failed
  9. 11 October 2025 Deleted passage from The Holocaust and the Nakba explaining its views on Israeli Jews
  10. 12 October 2025 Removed notability tag from JEXIT, an article Aesurias created, without allowing any discussion
  11. 13 October 2025 Created page on the pro-Israel Zioness Movement, with half the sources either dead links or direct links to the Zioness website
  12. 14 October 2025 Removed sourced passage explaining that Israel's doctrine they use to justify denial of the Gaza genocide was authored by biased individuals
  13. 14 October 2025 Removed a passage explaining that the Australian Jewish Association defended a former neo-nazi
  14. 18 October 2025 Moved List of companies of Palestine to draftspace, saying the formatting is incorrect
  15. 18 October 2025 Started an AN investigation into a userpage having a vague reference to Hezbollah, which was promptly closed after the consensus was that Aesurius was wasting everyone's time
  16. 21 October 2025 Moved article on Track AIPAC, a watchdog group monitoring pro-Israel group AIPAC to draftspace, calling it improperly sourced and non-notable
  17. 21 October 2025 Created page on Better Australia, a group supporting pro-Israel politicians, using only five sources - two of which are primary, and one of which is a blog
  18. 22 October 2025 Reverted my addition of Template:Promotional to Zioness Movement page they created without making any changes to content or sourcing
Diffs of previous relevant sanctions, if any

None.

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

Editor is clearly inserting pro-Israel messaging into Wikipedia's articles and suppressing criticism of Israel, and a topic ban on any material covering the Arab–Israeli conflict would be appropriate. Their New page reviewer permission should be revoked. TheNewMinistry (talk) 23:31, 22 October 2025 (UTC)[reply]

Notification of the user against whom enforcement is requested

[46]

Discussion concerning Aesurias

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 Aesurias

I previously opened an NPOV discussion against this user, here, over an image taken of a political candidate in 2007, which the user uploaded to Wikimedia as their 'own work'. The user, paradoxically, insisted that they had no COI with the candidate. Other editors questioned the user about this, because by insisting on 1) the image being their own work and 2) them having no connection to the person in the image, they were lying about at least one thing.

After I opened that discussion, I was incessantly hounded by the user, who has been reprimanded by administrators for his behaviour here, but didn't acknowledge it.

  • They thanked me dozens of times, spamming me with notifications, seen here.
  • Their recent edit history, seen here, is made up almost entirely of my articles -- they created talk pages for more than a dozen of them, adding the 'contentious topics' tag to each one, notifying me.
  • Their recent edit history also shows they were adding tags onto my articles without explaining why on the talk pages.
  • On Better Australia, they added an NPOV tag and opened a talk page discussion (the only page where they explained why they added the tag!) here. I was receptive to this, adding things they wanted to the article. The user then stopped replying. Another editor replied to the talk page saying I didn't need to add any of what this user wanted in the first place, as it was not relevant.

Additionally, they previously received a 48hr ban for personal attacks against me, seen here. They have received other bans of various types, including another ban for personal attacks on other users.

Creating articles on Wikipedia is not a crime, as the user is trying to insinuate. Other editors approved these articles with no problem. I stand by all of my own reviews of pages, they weren't ready for mainspace. Cherrypicking a few of them relating to Israel-Palestine and ignoring the dozens that weren't is disingenuous. My edits were fine -- for example, the Israeli-American one was false info, it was a poll asking Israelis in Israel who they would theoretically vote for if they could, which is why I removed it. I removed some parts of 'criticism' sections because they didn't contain criticisms, rather they contained things that the editor who added them didn't personally like. A failed AfD is not relevant, some editors agreed with me, some didn't.

This request is unserious. The user's assumption of bad faith, accusing me of "inserting pro-Israel messaging into Wikipedia", is not only offensive to me, but offensive to the dozens of well-respected editors who have approved my pages.

  • User:Sean.hoyland I had not seen this post before you sent it, and although I have a Reddit account I am not active in that subreddit. I would have disclosed this in the AfD if I had seen it prior. :)

Statement by TheNewMinistry

Asilvering (talk · contribs) is literally the administrator who advised me on October 15, 2025 to open an investigation on this very forum when I asked them for advice regarding Aesurius' biases in Israel/Palestine editing:

As for Aesurias, if you have npov concerns regarding Israel-Palestine, the place to raise those is at en:WP:AE. [47]

For Asilvering to claim they are an uninvolved administrator is laughable. I'm politely asking @Asilvering: to recuse themself from this investigation. TheNewMinistry (talk) 01:16, 23 October 2025 (UTC)[reply]

Incorrect Asilvering (talk · contribs) - I last thanked Aesurias (talk · contribs) before today on October 12th, according to the logs posted above. I only thanked Aesurias once, today, after they left contact information on your Talk Page so you could both discuss ways to retaliate against me offsite. Again, @Asilvering: - please recuse yourself from this investigation since you clearly hold a grudge against me. If you did not direct me to this forum in good faith in your advice to me here, as I had assumed, and instead thought you could lure me here to punish me for non-related matters, as you imply in your edit here - that is quite disturbing. TheNewMinistry (talk) 01:41, 23 October 2025 (UTC)[reply]

Statement by Sean.hoyland

The following line caught my eye.

  • 10 October 2025 Tagged The Holocaust and the Nakba for deletion...

Looking at the timing and the fact that the nomination for deletion was, I think, Aesurias' first visible interaction with that page, I would be interested to know from Aesurias whether the action was in response to this Reddit thread or perhaps another site. If so, I do think for ARBPIA, for processes susceptible to external influence like AfD, it would be helpful if people just openly described the off-wiki discussion/social media post etc. that caused them to take action on-wiki whenever it happens as part of the nomination. That way we might have better visibility into the off-wiki/on-wiki causal connections that exist. Just a simple - saw this post/discussion... - might help. Sean.hoyland (talk) 07:04, 23 October 2025 (UTC)[reply]

Thanks Aesurias. I take that to mean that you also think that something like a WP:SAYWHEREYOUREADIT for these kinds of things might help. If so, that probably makes a total of two of us. It's a start. Sean.hoyland (talk) 07:38, 23 October 2025 (UTC)[reply]

Result concerning Aesurias

This section is to be edited only by uninvolved administrators. Comments by others will be moved to the sections above.
  • Disclosure: I was the administrator who warned TNM about hounding Aesurias ([48]), having earlier blocked TNM for harassment regarding the same. I have also responded to Aesurias's questions about where to take various disputes, and about the word limit in AE proceedings. I do not feel that either of these prejudice me unfairly in this case, but am more than willing to move my comments up if other admins think I ought to. Regarding the evidence against Aesurias, I have not fully investigated but it looks at least good enough that we should investigate, not reject this filing out of hand for being retaliatory. However, the filing is quite clearly the most recent salvo in a pattern of harassment that I warned TNM over just yesterday. Clearly, some sanction for harassment on the part of TNM is required, regardless of the ultimate outcome regarding Aesurias. -- asilvering (talk) 00:48, 23 October 2025 (UTC)[reply]
    Yes, @TheNewMinistry, I told you to raise complaints at AE. A week ago. In the intervening time, instead of raising concerns at AE, you continued to harass Aesurias, and I then gave you a final warning, as I stated. As I have said, if other admins think I should move my comments up, I am happy to. I have, however, only been involved here in an administrative capacity. -- asilvering (talk) 01:24, 23 October 2025 (UTC)[reply]
    Regarding Aesurias's assertion that TNM has been cherrypicking, I'm not sure that can possibly be true, given that, unless I am much mistaken, TNM's evidence does not contain anything about Talk:Pallywood, Aesurias's most-edited talk page. That discussion has also spilled out to WP:NPOVN#'Pallywood' (though, note also the personal attack on them here [49]). Their position appears to be that Pallywood is "real". Pallywood is both a slur and a conspiracy theory. Someone who cannot distinguish between Pallywood and Misinformation in the Gaza war should not be editing in WP:CT/PIA. -- asilvering (talk) 07:00, 23 October 2025 (UTC)[reply]
  • Well, I think asilvering is fine to participate. I also think that Aesurias deserves a topic ban at minimum from PIA. TNM should get an interaction ban with Aesurias for the harassment at this point. Sennecaster (Chat) 02:10, 23 October 2025 (UTC)[reply]
  • I have blocked TNM indefinitely for their comment above in which they acknowledge that they used the "thank" button in response to an edit by Aesurias that they characterize as part of a conspiracy to "retaliate against me offsite"—obviously not sincere thanks, but a continuation of the same harassment Asilvering warned them for. I might have gone with a p-block from thanking, or a longer tempblock, but their complete lack of self-awareness that this is harassment suggests a problem broader than this one issue, and so for now at least an indef siteblock is the least restrictive remedy that addresses the disruption. This is not an AE action, and should not lead to an early closure of this thread. For now I have no opinion on TBANning Aesurias, but support an IBAN on TNM, blocked or not. -- Tamzin[cetacean needed] (they|xe|🤷) 05:42, 23 October 2025 (UTC)[reply]
  • I also support a TBAN for Aesurias from PIA and an IBAN for TNM with Aesurias. Callanecc (talkcontribslogs) 07:42, 23 October 2025 (UTC)[reply]

Thisischarlesarthur

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 Thisischarlesarthur

User who is submitting this request for enforcement
M.Bitton (talk · contribs · deleted contribs · logs · filter log · block user · block log) 01:17, 23 October 2025 (UTC)[reply]
User against whom enforcement is requested
Thisischarlesarthur (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:ARBGENSEX and WP:ARBBLP

Diffs of edits that violate this sanction or remedy, and an explanation how these edits violate it
  1. 28 September 2025 This page will be confusing until it recognises that athletes such as Caster Semenya (XY 5-ARD) are male. They added this to the talk page.
  2. 10 October 2025 between the years 2000 and 2023, between 50 and 60 male athletes with differences of sex development (DSDs)] who were wrongly recorded as female at birth took part in 135 female elite international finals ..... This was added to the article.
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)
Additional comments by editor filing complaint

I only listed the worst offending comments by the editor who, since 11 August 2024, has edited nothing else by topics that are related to GENSEX (nibbling at them to see how far they can push what they truly believe in).. M.Bitton (talk) 01:17, 23 October 2025 (UTC)[reply]

@Thisischarlesarthur: why didn't you comment on the diffs that I listed above? M.Bitton (talk) 23:58, 24 October 2025 (UTC)[reply]
Notification of the user against whom enforcement is requested

Diff


Discussion concerning Thisischarlesarthur

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 Thisischarlesarthur

  Thisischarlesarthur's statement contains 1055 words and exceeds the 500-word limit.

Update: How wonderful! I tripped over another invisible laser beam: nowhere in the submission system does it say you have to keep topics to 500 words.

responding to M.Bitton

Re your first diff: I wasn't aware of the restrictions that are placed on this discussion. A paper co-authored by a biologist supports what I said there. Re your second diff: as I point out below, the Guardian article that I linked to in the edit directly implies what I wrote. There is no other reasonable interpretation of the phrase "athletes with differences of sex development (DSD), who have a 46 XY karyotype with male testes but were reported female at birth". Male testes are found in males. Only. The phrase "Assigned female at birth" implies the potential for mistakes in registering birth sex.

The content of Special:Diff/1316517130 is defensible as fact. The Imane Khelif page describes "false claims" which were never made: there has never been any credible suggestion that Khelif is trans (ie: someone registered as male at birth who later identifies as female). Yet the phrase "false claims" links to "transvestigation", which this never was. To represent the Olympic boxing controversy in those terms misleads the casual reader, while leading the informed reader (ie anyone who has read a few articles on the topic) to conclude Wikipedia is wrong, and to wonder why a theoretically world-editable wiki remains wrong.

However the BLP rules create a Catch-22 where it is disallowed to point out what the actual topic of the controversy is, on the basis that this is a BLP violation. So now I know why Wikipedia remains wrong.

responding to Simonm223

"It seems like this editor's only interest in editing Wikipedia is to engage in debates about how to define the gender of women athletes" - Not true. My interest on those pages was to correct inaccuracies. I have accepted that my initial attempts were clumsy.

responding to TarnishedPath

"Without extremely strong sourcing, these sorts of claims/speculation should not be occuring." The phrase "unsubstantiated allegations" might be more appropriate, given the BLP. But as this discussion on a Talk page on a different page points out, the BLP handcuffs clear explanation of what the allegations around Khelif are. I don't think any reasonable person believes Imane Khelif was not registered female at birth.

responding to @theleekycauldron

I reject @theleekycauldron's claim that I am "only here to push the idea that SRY testing is completely determinative of sex". I have never said that, because it isn't true. SRY screening does not determine sex. It determines the presence or absence of the SRY gene. However, it was used in the 1992 and 1996 Olympics to determine entry to the F category, and has now been reintroduced by multiple global sporting organisations. Therefore it is important in understanding modern and past sporting categorisation systems: currently the Sex verification in sports page is lacking this information, so I tried to add it. My attempts to introduce edits about this were however reverted, without any explanation or offer of help. Go Wikipedia!

responding to Tamzin

"If in 450 edits TICA [ie me] has been dispelled of their fringe views" - thank you, but I don't find the offer of doing it to Julia instead enticing. What if it's your views that are fringe, and wrong? A paper co-authored by a biologist explicitly contradicts the views you and others here hold about multiple athletes, and shows its reasoning, with scientific references. (In passing, the word "intersex" was determined by medics to be outdated due to being "confusing" and "potentially stigmatising" by a consensus meeting in 2005. The phrase "DSD" has been preferred in the literature for the past 20 years.)

The tenor of accusations here holds that the group is correct, and this individual wrong. However scientific resources (as above) support the view that it is the group which is wrong. I don't expect this to be accepted, since absorbing a new and different opinion into the group is challenging. But you should always wonder: what if you're wrong?

I suggest that the rapid adoption of SRY screening by multiple sporting organisations which have independently done their own scientific enquiry shows that those organisations hold significantly different views about DSDs (or "intersex") in sports than those reporting me here. To quote from the Guardian article that I tried to add into the Sex Verification page, "In a presentation to a scientific panel in the Japanese capital on Friday, Dr Stéphane Bermon, head of health and science at World Athletics, outlined why the sport’s governing body believes such screens are necessary as he presented data collected over the past 25 years. He said it showed that athletes with differences of sex development (DSD), who have a 46 XY karyotype with male testes but were reported female at birth, were significantly “over-represented” in major finals…"

Wait - "but" were reported female at birth? What could Bermon have been implying? Tamzin attempts to thread a needle on this: using the conjunction "but" to describe an AFAB person having some male sex characteristics, does not imply that it's the view of The Guardian (let alone of Bermon or any actually reliable source) that it is incorrect to assign such a person as female Who exactly is doing the "assigning" here? The midwife? Tamzin? Testes are not "some" male characteristics. They are defining male characteristics. The phrase "with male testes" appears again and again in every article about the presentation, so a reasonable conclusion is that these were Bermon's words. Bermon is director of health and science at World Athletics with a long history in medicine, and those are clearly his words. For Wikipedia to reinterpret them as meaning something else would be perverse and against the obvious sense of the words, in the absence of any explanation by Bermon that such athletes belong to the female sex.

If you allow me to continue editing, I will do my best not to knock over the furniture; for the newcomer, these important topics have invisible laser beams linked to alarms everywhere, and I feel as though I tripped them all. At the same time, I take my guidance about the facts from the scientific literature and (on this topic) the sporting bodies - which is how references should work - not from the beliefs of other Wikipedia editors.

--Thisischarlesarthur (talk) 23:32, 24 October 2025 (UTC)[reply]

Statement by Simonm223

It concerns me to see this continuing from Thisischarlesarthur. On October 8 they conceded their comportment was a BLP violation: [50] as such it's rather concerning that, instead of stopping with an approach they know to be a BLP violation, they just moved the discussion to other pages. [51] [52]. It seems like this editor's only interest in editing Wikipedia is to engage in debates about how to define the gender of women athletes. Simonm223 (talk) 15:17, 23 October 2025 (UTC)[reply]

Statement by TarnishedPath

Admins, please refer to Special:Diff/1316517130, in which Thisischarlesarthur suggests that Imane Khelif is male. Without extremely strong sourcing, these sorts of claims/speculation should not be occuring. TarnishedPathtalk 03:47, 24 October 2025 (UTC)[reply]

Statement by (username)

Result concerning Thisischarlesarthur

This section is to be edited only by uninvolved administrators. Comments by others will be moved to the sections above.
  • I can't see how Thisischarlesarthur's editing is consistent with the expectations of GENSEX and BLP. Given that Thisischarlesarthur is a new editor, I think a GENSEX TBAN that automatically expires when they qualify for extended confirmed would be appropriate at this point. Callanecc (talkcontribslogs) 07:46, 23 October 2025 (UTC)[reply]
    • I don't think Tamzin's second TBAN is necessary at this point as the issue seems to be centred on a broader gender-related dispute taking place on BLPs. Just by bringing up the issue Thisischarlesarthur would be creating a gender-related dispute. I'm also fine with SilverLocust's any admin removal after 500/30. Callanecc (talkcontribslogs) 06:29, 26 October 2025 (UTC)[reply]
  • Poking around, it seems like Thisischarlesarthur is only here to push the idea that SRY testing is completely determinative of sex, and that if someone hasn't undergone SRY testing, their sex is undetermined (shifting the burden of proof that applies to contentious BLP claims). People who do have 5-ARD, like Caster Semenya, are labeled as "male" (see M.Bitton's diffs). Curiously, this only seems to apply to sportswomen who have been transvestigated – but somehow, someone being "male" and identifying publicly as female doesn't make them transgender. In other words, this seems like an attempt to invent a policy and factual framework for labelling sportswomen who have been transvestigated as "male" or of "undetermined" sex in a way no RS comes even close to supporting (while also trying to avoid getting painted with the same brush as transvestigators). I would support something stronger than a 'til-ECR GENSEX topic ban, but I'll support that at a minimum. theleekycauldron (talk • she/her) 01:28, 24 October 2025 (UTC)[reply]
    I actually think this is a bit overly charitable to TICA's rhetoric. There's been some debate about where we draw the line on WP:FRINGE on trans medical issues, it being an area where academic consensus is still developing, but describing woman athletes who may have DSDs as "wrongly recorded as female at birth" is utterly fringe, possibly more so than your typical "secretly trans" conspiracy-theorizing. Yes, there are reliable sources that think such women have a sufficiently unfair advantage that they ought to be categorized separately in sports, but I have never seen a single such source say that assigning those women as female at birth is wrong. The absolute best-case analysis here is that TICA dramatically misunderstands what "female" means, as that term is used in essentially all scholarly sources—and I don't mean "woke" gender stuff, I mean the basics of the science of sex, in which "female" is not mutually exclusive with "intersex" and in which no single genotypic or phenotypic attribute is the sole determinant of whether someone is male or female. I always want to be careful at AE about not promoting any one side's view as right, but this is not reasonably in dispute among any subject-matter experts, even those strongly in favor of excluding trans and intersex women from women's sports.
    That's the best-case analysis. The worst-case analysis is deliberate misrepresentation of science to libel living persons. If I were convinced it were the latter, I would just indefblock. Lacking a smoking gun in that regard, though, I think the minimum I'd support here is two related topic bans: one from GENSEX, and one under WP:CT/BLP (of which TICA is aware) forbidding them from commenting on the actual or alleged gender or sex of any living person (except implicitly through using the pronouns/etc. already in place in an article). I oppose any automatic lifting upon extendedconfirmed. If in 450 edits TICA has been dispelled of their fringe views, I'd like to see them make that case to an administrator to get the ban lifted. -- Tamzin[cetacean needed] (they|xe|🤷) 04:06, 24 October 2025 (UTC)[reply]
    The Guardian—not Bermon, but The Guardian, which is not a reliable medical source, paraphrasing Bermon—using the conjunction "but" to describe an AFAB person having some male sex characteristics, does not imply that it's the view of The Guardian (let alone of Bermon or any actually reliable source) that it is incorrect to assign such a person as female. "But" implies some level of unexpectedness, but not necessarily that one of the two statements is incorrect. Picture a source that talks about people who "Had no COVID symptoms but tested positive for it"; that "but" doesn't mean that the tests were all incorrect, just that most people who test positive also have symptoms. Again, this isn't a question of which side one is on in the trans and intersex sports debates, but rather a basic foundational scientific understanding necessary to understand those debates. -- Tamzin[cetacean needed] (they|xe|🤷) 04:07, 25 October 2025 (UTC)[reply]
  • I'll support a WP:CT/GENSEX TBAN that may be lifted at an administrator's discretion after they qualify for extended confirmed. I'm fine with Tamzin's additional TBAN, though I struggle to imagine when that wouldn't already qualify as a "gender-related dispute" (broadly construed). ~ Jenson (SilverLocust 💬) 05:28, 24 October 2025 (UTC)[reply]
    I think the second one is necessary because "gender-related dispute" doesn't clearly extend to something about an individual person's gender or sex, if that hasn't been the subject of political or cultural controversy. Claiming that Imane Khelif is male would fall under GENSEX, but saying "obscure athlete ABC has disorder of sexual development XYZ" might not. -- Tamzin[cetacean needed] (they|xe|🤷) 05:35, 24 October 2025 (UTC)[reply]
  • I agree that at least a GENSEX topic ban is appropriate. As others have said, a number of this user's edits are inconsistent with WP:NPOV. Their statement in this enforcement request heightens my concern, particularly at para 5 where there is an apparent attempt to refute one view on scientific consensus by cherry-picking a single citation. The final paragraph seems to reflect a troubling intention to edit as an WP:SPA. Arcticocean ■ 14:49, 25 October 2025 (UTC)[reply]

Arbitration enforcement action appeal by Selim beg

Tomruen

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 Tomruen

User who is submitting this request for enforcement
Seraphimblade (talk · contribs · deleted contribs · logs · filter log · block user · block log) 18:53, 25 October 2025 (UTC)[reply]
User against whom enforcement is requested
Tomruen (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:Arbitration/Requests/Case/Gender and sexuality

Topic ban from GENSEX: [53]

Diffs of edits that violate this sanction or remedy, and an explanation how these edits violate it
  1. [54] A comment directly discussing transgender-related subjects


Diffs of previous relevant sanctions, if any
  1. 30 May 2023 Blocked 30 days for topic ban violation
If contentious topics restrictions are requested, supply evidence that the user is aware of them (see WP:CTOP#Awareness of contentious topics)


Additional comments by editor filing complaint

Recently, I noticed while checking recent changes the comment noted above on User talk:Tomruen, which seems a straightforward violation of his GENSEX topic ban. I'll note for completeness that the ChatGPT portions of the comments were added by an IP ([55]), but Tomruen added the comments introducing them and edited that exact portion afterward ([56]), so I think we can fairly say that either he was the IP or endorsed the addition. This is almost exactly the same as the material that Tomruen was blocked for shortly after being topic banned ([57]), so, while the new edit is over a month old, I really don't think it should be ignored. I'd hoped to be able to find out what was going on and maybe resolve it through discussion, but Tomruen has made very clear that he does not care about violating the ban ([58]), so I'm bringing it here to discuss what to do on it. Seraphimblade Talk to me 18:53, 25 October 2025 (UTC)[reply]

Notification of the user against whom enforcement is requested

[59]

Discussion concerning Tomruen

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 Tomruen

Statement by (username)

Result concerning Tomruen

This section is to be edited only by uninvolved administrators. Comments by others will be moved to the sections above.
Given that the last topic ban violation occurred in 2023, resulting in a 30 day block, and the misconduct in this instance occurred on Tom's talk page in a discussion with a single editor who brought up Tom's, I'm leaning towards a 60-90 day block. voorts (talk/contributions) 20:36, 25 October 2025 (UTC)[reply]

ItalianTourist

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 ItalianTourist

User who is submitting this request for enforcement
Nil NZ (talk · contribs · deleted contribs · logs · filter log · block user · block log) 03:46, 26 October 2025 (UTC)[reply]
User against whom enforcement is requested
ItalianTourist (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:PIA
Diffs of edits that violate this sanction or remedy, and an explanation how these edits violate it
  1. 24 Oct 2025 – Comment at RSN discussing the reliability of German-language sources reporting on Saleh al-Jafarawi, a recently-deceased Palestinian journalist.
  2. 26 Oct 2025 – After being informed their first diff above violates ECR, they make a very similar comment two days later, this time at Talk:Saleh al-Jafarawi
If contentious topics restrictions are requested, supply evidence that the user is aware of them (see WP:CTOP#Awareness of contentious topics)
Additional comments by editor filing complaint

In addition to the templated CTOP introduction, Rosguill specifically said that their comment from Diff 1 was in violation of the ECR restriction, and included links to WP:ECR & WP:ECREXPLAIN, which explains that, whilst non-XC editors may post on Talk pages, they are restricted to non-controversial edit requests that follow WP:EDITXY. Instead of following this restriction, ItalianTourist tried to make a very similar comment again, but this time at Talk:Saleh al-Jafarawi in Diff 2.

Notification of the user against whom enforcement is requested


Discussion concerning ItalianTourist

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 ItalianTourist

Statement by (username)

Result concerning ItalianTourist

This section is to be edited only by uninvolved administrators. Comments by others will be moved to the sections above.
  • I'll wait a day or so to provide time for ItalianTourist to comment, but absent something convincing, I intend to do a 1-week block for breaching ECR. The diffs provided above, including in Nil NZ's comment, appear to demonstrate that ItalianTourist does not intend to comply with ECR and so a block seems appropriate at this point. Callanecc (talkcontribslogs) 06:25, 26 October 2025 (UTC)[reply]