request administrative action against an editor violating a remedy (not merely a principle) or an injunction in an Arbitration Committee decision, or acontentious topic restriction imposed by anadministrator,
request contentious topic restrictions against apreviously alerted editor who engages in misconduct in a topic area designated as a contentious topic,
requestpage restrictions (e.g. revert restrictions) on pages that are being disrupted in topic areas designated as contentious topics, or
Onlyregistered users who areautoconfirmed may file enforcement requests here; requests filed bytemporary accounts or accounts less than four days old or with fewer 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 anextended-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, appeals, and statements in response to them may not exceed500 words and 20 diffs, except by permission of a reviewing administrator.(Word Count Tool) Statements must be made in separate sections. Administrators may remove or shorten comments that are overlong or unconstructive, and may instruct users to stop participating or impose AE sanctions in response to disruptive contributions such aspersonal attacks orgroundless complaints.
The scope of a discussion is limited to the conduct of two parties: the filer and the user being reported. If additional editors are to be reported, separate AE reports must be opened for each, unless AE admins waive this rule. Any uninvolved admin may furtherrestrict participation by non-parties at their discretion.
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
All contentious topic restrictions (andlogged 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;
Appeals submitted at AE or AN must be submitted using theapplicable 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:
aclear consensus of uninvolved administrators at AE,
aclear 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.
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 arequest 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 other arbcom sanctions
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;
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.
Word counts may be added using the following template:{{ACWordStatus|page=AE|section=REQUEST NAME|user=USERNAME}}. Extensions may be granted using the following template:{{ApprovedWordLimit|words=NEW TOTAL|sig=~~~~}}.
Closing a thread:
Once an issue is resolved, enclose it between{{hat}} and{{hab}} tags. Hatted requests will later be archived by an admin (often after a few days to a week).
Please considerreferring 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.
This request may be declined without further action if insufficient or unclear information is provided in the "Request" section below. Requests may not exceed 500words and 20 diffs (not counting required information), except by permission of a reviewing administrator.
Request concerning שלומית ליר
User who is submitting this request for enforcement
they alsovoted in the second AfD forCalls for the destruction of Israel despite never having interacted with that article or its previous AfD. They have barely surpassed 500 edits, but the gaming is obvious, highlighted by the sudden switch to editing in PIA.
More importantly, there's the issue of POV pushing. I came acrossthis article authored by them on Ynet, once again complaining about what they perceive as an anti Israeli bias on Wikipedia. They have also authored a report for the World Jewish Congress covering the same topic. The report can be seen in fullhere. I think that someone with this clear POV agenda shouldn't be near the topic.
Alerted about discretionary sanctions or contentious topics in the area of conflict, on2023-04-05 and re-iterated on2024-11-25 (see the system log linked to above).
Adding more comments 2025-01-29:@Arcticocean: Can you explain to me how it was determined that the canvassing in question has notbecome serious enough to be a policy violation? Does the evidence above not suffice? We've seen editors topic banned or even site banned in this CTOP recently for dramatically less. Why are sysopsprepared to look past it in this case? What is a warning going to do except give them more time to be disruptive? We're not talking about a new editor who made some unwise tweets or whatever - this is an experienced editor in he wiki that has openly engaged in canvassing. A warning would just reward that behaviour and send the message that you can openly canvass as long as you feign ignorance for a bit.Smallangryplanet (talk)10:22, 29 January 2025 (UTC)[reply]
Notification of the user against whom enforcement is requested
Statements must be made in separate sections. They may not exceed 500words 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 שלומית ליר
I believe contents of this filing to be in clear policy violation and have reached out to the arbitration committee for further clarification before commenting further.שלומית ליר (talk)14:34, 13 January 2025 (UTC)[reply]
First and foremost, I value accuracy and transparency and am fully prepared to address any verified errors or missteps. My contributions are made in good faith, with only the intention of supporting Wikipedia’s mission. I am a veteran editor on Hebrew wiki, yet am learning to appreciate the sometimes stark differences in rules in this section, so am doing my very best to keep up to speed and abide fully as I edit further here.
As a longtime editor on another wiki who finally decided this year to match pace on English wiki, I strenuously reject any accusations of EC gaming when a passing glance on my global log will confirm I have not radically altered my editing pace nor article focus. In regards to NPOV concerns, I will defer to the numerous comments below affirming that there is no policy violation by having an opinion, onsite or off, and must register mild complaint that NPOV accusations are being leveled here without any policy violation having been affirmed on any of these individual contributions.
While contributions observed superficially (and without clear context of edit conversation and interaction with other editors) may appear to be agenda oriented, if I were granted more word counts, I would happily highlight the context of most edits made to make clear I was pushing back against previous bias efforts (past and present) by editors (including a number on the precipice of sanction in PIA5). Perhaps it would have been wiser to report what I felt was POV editing behavior instead of pushing back, but I only believed my efforts were to restore and preserve article balance, not disrupt it.
I am grateful for the admin guidance received so far and appreciate being better informed about certain grey areas. I meant no intention to remotely approach anything resembling canvassing and believed the commentary was allowable (most especially since it was on a proceeding I was neither participating in, nor linking out to). I understand now that this may be perceived as “call to action” which was not remotely the intent, most especially to an audience that is mostly academic and, to the best of my knowledge, does not edit Wikipedia. (I also humbly must point out that no report was made indicating any increase in activity to suggest editors had been canvassed). I have now been well appraised and will take great care and caution to ensure no further off-site commentary remotely approaches such this territory of concern. If there are any questions or doubts in the future, I will seek future guidance from admins before venturing into potentially questionable territory.שלומית ליר (talk)01:07, 22 January 2025 (UTC)[reply]
I would to like to raisethis 9 December 2024 edit atBattle of Sderot, where there had been an existing unsourced paragraph (On the morning of October 7, a tour minibus...) that שלומית ליר addeda reference to (archive 1 /archive 2) from theIsraeli Public Broadcasting Corporation.The reference is relevant, but I believe it may not verify every detail in the Battle of Sderot paragraph (e.g. "Netivot", "Holocaust survivors"). The reference contains a short paragraph of text and a video that is 4:21 long. I can't watch the video in the reference, but I believe it is this sameYouTube video that is 4:20 long which contains the same screenshot as the reference, on the same topic. Most of the video is an interview of the daughter of a dead victim who was on the bus (the daughter had been on the phone with the victim), except for 1:58 to 2:13 which appears to be a quote from the bus driver. The publisher themselves do not have too much reporting in their own voice (on the video), yet this reference was used to cite a paragraph entirely stated in Wikivoice. No attribution was made to the relative or the bus driver, or to the publisher. I can't be totally sure though, due to unfamiliarity with Hebrew.starship.paint (talk /cont)13:53, 12 January 2025 (UTC)[reply]
Statement by xDanielx
@Arcticocean: I don't really see how NPOV can be read as requiring edits which support both sides of a controversy. Our content policies don't impose any positive duties; they only tell us what not to do. The text of the policy doesn't support the notion that apattern of edits could be in violation, even if no particular edit is in violation.
In principle, such a pattern of edits could violate theUCoC policy, but I don't believe this board has ever enforced it. If it were to be enforced, I think it should be for more serious violations like the double standards that e.g.this attempted to demonstrate, rather than mere opinion-driven editing which applies to the vast majority of CTOP editors. —xDanielxT/C\R03:11, 13 January 2025 (UTC)[reply]
Statement by Hemiauchenia
This user has engaged in off-wiki canvassing regarding the IP conflict. Take the following recent tweet from the 12 January[1]permanent archive
For posterity in case it is deleted it contains the following remarks:
If you can't handle the facts, just delete them Propaganda on @Wikipedia includes targeting Israel, demonizing it, and erasing inconvenient truths, from falsifying war outcomes to deleting Israeli inventions and attempting to erase the reality of Palestinian suicide bombers.
For those concerned that this might be outing, שלומית ליר is very open about their real life identity on their userpage. See[2] (archived). If you reveal your real identity on Wikipedia, your tweets about Wikipedia on your Twitter account connected to your real-life identity are fair game to mention. There's also reverse confirmation in this tweet[3].Hemiauchenia (talk)02:46, 16 January 2025 (UTC)[reply]
It has been several days. Perhaps שלומית ליר could clarify whether their belief about the way Wikipedia works turned out to be a true belief or a false belief so that this report can progress.Sean.hoyland (talk)09:07, 18 January 2025 (UTC)[reply]
I am interested in theGoogle form cited above, specifically how this differs from the widely reported situation that resulted in the 'Off-wiki misconduct in Palestine–Israel topic area' case that employed Discord (and/or X, I forget) rather than a Google form. Is a consistent decision procedure being used to distinguish between encouraging participation and canvassing/meatpuppetry? I think a lot of people don't know where the line is, assuming there is a line, or at least some kind of fuzzy decision boundary.Sean.hoyland (talk)04:46, 23 January 2025 (UTC)[reply]
FortunateSons, I agree with you broadly, but for me there is too much fuzziness around this issue. Clarity probably has much more utility than sanctions. TheAfD case is an example that I find a bit confusing. Setting aside the fact that that article is still 3/4 the product of multiple ban evading actors, and ignoring the fact that an article on that topic should exist, what is the nature of the post? Is it an example of "discussing bias" or is it an example of "soliciting" using a 'Will no one rid me of this turbulent priest?' approach or something with the potential to be both? If an editor saw that and then !voted, have they been canvassed and does the post instantaneously collapse into an example of canvassing? Maybe with your legal mind you can come up with some sensible tests, or ways of thinking about these kinds of things.Sean.hoyland (talk)07:07, 29 January 2025 (UTC)[reply]
Statement by Vice regent
I'm satisfied by שלומית ליר's above explanation regarding canvassing. People with bad canvassing intentions don't reveal their identity.VR(Pleaseping on reply)04:19, 22 January 2025 (UTC)[reply]
Statement by FortunateSons
Making no statement on warnings vs. no action for on-wiki conduct, I do think that it's important to note that externally discussing bias in general or about specific articles, whether actual or perceived and even if that discussion is influenced by the political opinions and/or social views of the editors, isn't and ought not to be sanctionable (or even indicative of other misconduct). This obviously doesn't apply to doxxing editors or soliticing specific edits, but this doesn't seem to be the intent or impact here. The actions discussed here are different enough from the conduct of T4P to be incomparable IMO.FortunateSons (talk)10:55, 28 January 2025 (UTC)[reply]
@Sean.hoyland not to disappoint you, but trusting my legal mind is about as wise as taking health advice from a med student.But thank you, I'm flattered. The cop-out would probably beIn dubio pro reo, but I think this is probably a case were both can be argued to be plausible IMO, with the question of ascribing or not ascribing intent based on how much good faith one wants to assume (with my agreeing with the VR assessment, but who knows). If I could make a wish for the future, I think it would be wise not to comment on small time-limited community discussions until they have concluded, and applying the same to ongoing content disputes if they are likely to quiet down within a reasonable timeframe (but not otherwise, it's not reasonable to expect someone not to discussZionism for the next year). This is probably irrelevant in cases with 100 participants and media attention, but doing the same with a 3-person-discussion creates a canvassing risk and/or an Andre's basilisk sort of scenario. If I could make policy bydecree, I would sanction direct links to ongoing small discussions, specific recruitment (T4P/Camera) and specific calls to action. On the other hand, if I write an "how to edit wikipedia" guide and post it on r/palestine, an opinion piece complaining about antizionist bias for a 'jewish' newspaper, or neutrally/academically cover an ongoing discussion no matter the size, it clearly isn't canvassing (even if the quailty of such content is mixed as best, if the past is indicative for the future). I think the optimal line would be "indicative but not actionable" for anything in between those two, but that would effectivly only punish editors who are honest enough to disclose their identities, which really shouldn't be the point. In short, I'm honestly not sure where to draw that line in the sand, but (as I stated in the PIA5 discussion) we really need one.FortunateSons (talk)10:21, 29 January 2025 (UTC)[reply]
Regarding thelogged warning for […] canvassing, it would be quite helpful if the Sysops clarified which behaviour (for example, which tweets) constitute canvassing in their view, both for this editor and for the future. Would that be possible?FortunateSons (talk)07:31, 3 February 2025 (UTC)[reply]
Statement by (username)
Result concerning שלומית ליר
This section is to be edited only by uninvolved administrators. Comments by others will be moved to the sections above.
Users are allowed to have a POV - it's a rare user indeed who edits a contentious topic without having some strong opinions about it. For conduct to be actionable at AE it needs to be an actual policy violation. The misleading use of images doesn't rise to the level of AE action in my view, and judging whether an addition likethis is UNDUE is not within AE's purview, as long as it is supported by the source.Vanamonde93 (talk)23:22, 11 January 2025 (UTC)[reply]
The PIA5 remedy hasn't passed yet, and its interpretation is as yet unclear to me: but in my view we are already empowered to deal with biased editing, in the sense of editing that violates NPOV. What I'm not willing to do is sanction on the basis of someone's opinions alone; they have to be shown to have let their opinions get in the way of following our PAGs.Vanamonde93 (talk)07:44, 12 January 2025 (UTC)[reply]
I see some evidence - based on Arcticocean's digging below - that שלומית ליר is using images without sufficient care, but I don't see that rising to the level of a sanction. As to the rest, xDanielx is correct - nowhere do our policies require treating both sides of a conflict equally - indeed our PAGs discourage false balance. Those diffs could be actionable if they individually or collectively violate policy, but I have yet to see evidence of that.Vanamonde93 (talk)03:22, 13 January 2025 (UTC)[reply]
The off-wiki canvassing is a problem. It merits a warning at least, I don't know if the formality thereof matters. If there was evidence that שלומית ליר was aware ofWP:CANVAS I would consider something more stringent.Vanamonde93 (talk)17:39, 16 January 2025 (UTC)[reply]
While I understandVanamonde93's concerns, I think that we are required to assess the totality of the user's contributions. Contentious topic editors are required to uphold NPOV.Wikipedia:Contentious topics#Guidance for editors places an obligation toWithin contentious topics,… edit carefully and constructively… and… adhere to thepurposes of Wikipedia. The linked page provides thatWikipedia is written from a neutral point of view… We strive for articles with an impartial tone that document and explain major points of view, giving due weight for their prominence. If an editor isonly adding content that significantly favours one or the other side to the conflict, this is incompatible with their contentious topic obligation. That is because an editor makingonly one-sided edits will simply not be taking the necessary steps to ensure that thewhole article is written from a neutral point of view. As their number of one-sided edits increases, the likelihood decreases that the editor is ensuring our content is neutral and impartial. Once we reach the point of being sure that they are not attempting to ensure neutrality of content, we can conclude the editor is not meeting their contentious topics obligations and we can issue a sanction. This can only be assessed with hindsight and by looking at the editor's contributions as a whole.arcticocean ■20:21, 12 January 2025 (UTC)[reply]
Assessing the topic area contributions of the respondent (שלומית ליר) since they became extended-confirmedat 17:33, 8 December 2024, there is cause for concern. I counted 19 edits to the area conflict. Taken together, they significantly skew the articles negatively against the opposing side of the conflict:
On the talk pages, there has been atinge of failure to AGF although I would be prepared to look past that (it was like meeting like). I am skipping a few further and insignificant talk page comments.
Assessing the edits as a whole, it is difficult not to conclude that the respondent user is failing to meet their contentious topics obligation to edit neutrally in this topic area. As the number of edits is so far limited, if a sanction is imposed, it could justifiably be light-touch.arcticocean ■20:34, 12 January 2025 (UTC)[reply]
@XDanielx: Thanks for commenting. Most of the edits do not have a neutral, encyclopedic POV. There is an effort to influence our articles away from neutrally describing the subject without taking sides, contrary toWP:NPOV. Even if each edit in isolation is insufficient for sanctioning, takenas a whole the edits show an inability or unwillingness to edit neutrally. One non-neutral edit shouldn't be sanctioned; twenty is a different story. This is not about thepercentage of biased edits but about the weight or amount of them. Therefore, the assessment wouldn't really change even had the editor made some 'neutral' edits along the way. I'm happy to concede that editors cannot be compelled to balance edits of one bias with edits of another, but I don't think that comes into it. In a nutshell, this is aboutWikipedia:Advocacy.arcticocean ■08:40, 13 January 2025 (UTC)[reply]
Looking at the conduct here overall, rather than in silos (this is canvassing, that is a failure to edit neutrally, etc), we have to conclude that this user is editing disruptively in a contentious topic. Under ordinary circumstances, I would now be looking to impose a sanction. Inconsistent views are emerging among the administrators, however – some of us agree there is canvassing but not NPOV violations; others see NPOV violations but are prepared to look past the canvassing; and so on. This user also received a final warning previously for failing to check their edits before saving (which led to a citation software tool bug producing a mistake). This is a user who has had ample opportunity to get into step with our policies and expectations. Under the circumstances, I propose to log a final warning for various failures to comply with expectations, with strong encouragement that further policy violation will be dealt with by a long topic ban.arcticocean ■07:15, 29 January 2025 (UTC)[reply]
For fairness, I should note (which I had missed before) that two sysops have concluded that there is no actionable misconduct – only canvassing that has not become serious enough to be a policy violation. I still propose to impose a warning, and I think that would reflect the majority view among the sysops who have participated here.arcticocean ■07:24, 29 January 2025 (UTC)[reply]
For transparency, שלומית ליר reached out to me, and I explained multiple policy and advised her to go ahead and respond here without waiting for individual feedback from her email to arbcom, which may or may not happen.Valereee (talk)22:40, 18 January 2025 (UTC)[reply]
That's correct. I got a request, I didn't really feel it was OUTING, but as I indicated in my edit summary OS is a tool of first resort. I consulted with the OS listserv and received some responses quickly agreeing with me and so I unsuppressed and restored the material.Barkeep49 (talk)19:39, 16 January 2025 (UTC)[reply]
It's not for AE to decide content disputes, and that's mostly what this looks like. We can handle things like flagrant misrepresentation of sources, but howbest to represent them is a matter for consensus discussion, not us to decide here. The canvassing was a cause for concern, but it looks like it was rather unintended and had little if any actual effect, and they've agreed to stop that going forward. (Note that doesn't mean anyone must stop criticizing Wikipedia or what happens on it; do all of that you like. Just don't encourage people to take particular actions based on that.) I don't see any further action as necessary at this point.SeraphimbladeTalk to me16:08, 22 January 2025 (UTC)[reply]
I'm not satisfied with שלומית ליר's please of good faith. I think that the call for "interference" on Twitter (not even a week ago!) is a real concern in light of the standards being established by PIA5. I'm also concerned about the timeline of their knowledge of relevant CTOP sanctions. They were warned about PIA in April 2023 (by me, apparently). They should have been familiar with canvassing rules from the moment they got that warning to be on their best behavior. Not only that, but perusing their edit history, I see that there are several edits that are PIA violations prior to reaching XC on December 8 (e.g.Special:Diff/1256599528, although there's clearly many others in their edit history). In sum, I see no reason to believe the narrative of good faith presented here by them in light of the available evidence and do believe that we should consider at the minimum a logged warning.signed,Rosguilltalk20:15, 23 January 2025 (UTC)[reply]
I would be okay with a logged warning for canvassing, which remains the most concerning behavior to me. I find it difficult to see my way to penalizing violations of the XC restriction after the editor has already reached XC status without a clear finding of gaming XC status, and I don't see that here.Vanamonde93 (talk)20:41, 23 January 2025 (UTC)[reply]
I wouldn't call it gaming, I think it's a pattern of intentional defiance of community rules, which in turn makes the otherwise rather exemplary defense written here by them less than convincing.signed,Rosguilltalk21:15, 23 January 2025 (UTC)[reply]
No comment on the canvassing, but I'm of the same mind asarcticocean – editors that have problems complying withDUE aren't net positives, full stop. It doesn't matter that Dr. Lir isn't unambiguously a bad faith editor or incivil; perfecly good-faith editorsstill need to be good enough at editing to not make a string of unambiguous NPOV violations. Dr. Lir, if you want to challenge an article's perceived bias, you need to make an argument based on the balance of reliable sources to demonstrate why content is or isn't DUE. I'm in favor of a logged warning for non-NPOV editing.theleekycauldron (talk • she/her)22:26, 25 January 2025 (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 500words and 20 diffs (not counting required information), except by permission of a reviewing administrator.
Request concerning Luganchanka
User who is submitting this request for enforcement
Diffs of edits that violate this sanction or remedy, and an explanationhow these edits violate it
19:55, 12 January 2025 Reversion to version of article where the article says "He is a child sex offender" in the second sentence despite consensus at BLPN discussion that this is problematic because Ritter never actually interacted with a real child.
At BLPN, there has been consensus that the version of the article describing Ritter as a "child sex offender" in the second sentence of the article is problematic, as he did not actually have sexual contact with a child, only a police officer impersonating one.Wikipedia:Biographies_of_living_persons/Noticeboard#Scott_Ritter_Biography_-_Noncompliance_with_MOS_and_BLP_Guidelines. Luganchanka has been persistently edit warring against this apparent consensus. For which he has been warned by@NatGertler:[4], which he subequently blanked[5] There has been persistent objection to descrbing Ritter as a "child sex offender" in the opening sentences of the article going back to at least AugustTalk:Scott_Ritter#First_sentence, but Luganchanka persistently cites a "consensus" for its inclusion that as far as I can tell does not seem to exist, with Luganchanka aggressively editing to enforce its inclusion.Hemiauchenia (talk)20:26, 12 January 2025 (UTC)[reply]
Luganchanka's response is disingenuous and misleading. Look at theTalk:Scott_Ritter#First_sentence discussion I linked above. Nobody other than Luganchanka thinks that Ritter should be described as a "child sex offender" in the opening sentences of the article. The dispute isn't about whether or not the convictions should be mentioned in the lead at all or not, it's specifically about the use of the phrase "child sex offender", and there is no consensus to include that as far as I can tell, despite Luganchanka's vociferous claims to the contrary.Hemiauchenia (talk)20:47, 12 January 2025 (UTC)[reply]
Statements must be made in separate sections. They may not exceed 500words 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 Luganchanka
The intro on theScott Ritter page had remained largely the same for several months, as you will see on the talkpage it is an intro approved, and reverted to, by multiple senior editors. There has been a recent flurry of activity / edits. While IWP: assume good faith, it does look like those edits are attempting to downplay / whitewash Ritter's sexual offence conviction(s). I have not been 'aggressive' at all, rather I have simply referred contentious edits to the talkpage to build consensus, attempting to do my duty as a good Wikipedia editor.Luganchanka (talk)20:40, 12 January 2025 (UTC)[reply]
Please see theTalk:Scott_Ritter, where there has been a clear consensus reached, on more than one occasion, and by senior wikipedia editors, that Ritter's sexual offence conviction should be included in the lead to the article. My edits have simply been aimed at ensuring this consensus reached is maintained in the article.Luganchanka (talk)20:44, 12 January 2025 (UTC)[reply]
Thank you to @Valereee and @Red-tailed hawk for your feedback. If you see theTalk:Scott_Ritter, discussions -14 August - Vandalism by removing all reference entirely to Ritter being a "Convicted Sex Offender" andFirst sentence. The latter discussion ended on 26th September, and resulted in the intro we had until a flurry of edits the other day, trying to move information on Ritter's sexual offence conviction, downplay it, whitewash it etc. My edits were aimed at restoring the edit reached by consensus, which had been in place for several months until the recent raft of edits with the clear aim of moving / downplaying Ritter's sexual offence conviction.Luganchanka (talk)06:39, 15 January 2025 (UTC)[reply]
"Unfazed by "Emily's" age, Ritter asked "Emily," "you want to see it finish?" Ritter then turned on the webcam and ejaculated in front of the camera for "Emily." Detective Venneman then notified Ritter of his undercover status and the undercover operation and directed Ritter to call the police station."
Editor's edits today focused on trying to main a negative descriptor of what subject believed, despite it not being in the three sources that were listed (nor in the old version they ultimately reverted to.) Efforts were first trying to simply restate the claim, then trying to source it to an opinion piece (problem) from the Washington Examiner (also a bit of a problem, perWP:RSP), then trying to state as a fact what had merely been stated in a non-prime article as an accusation. BLP concern was pointed out repeatedly via edit summary and on Talk page. Removal of unsourced contentious BLP claims and even false claims is not "whitewashing" despite how editor wishes to depict it, it is in accord with our practices. --Nat Gertler (talk)21:08, 12 January 2025 (UTC)[reply]
Statement by (username)
Result concerning Luganchanka
This section is to be edited only by uninvolved administrators. Comments by others will be moved to the sections above.
@Luganchanka, edit-warringto remove negative content at a BLP is an exemption to 3RR. I see that NatGertler mentioned this in their edit summaries and at talk. As voorts points out, it doesn't matter whether you're right when you're reverting an edit that is being claimed as an exemption, even if you believeRosguillwhiyou are "ensuring this consensus reached is maintained in the article". The solution is to go to talk, discuss, and get consensus. If you'd like to respond, ping me to your response at your talk and I'll post it here.Valereee (talk)16:04, 13 January 2025 (UTC)[reply]
@Luganchanka, if you really believe those two sections -- senior editors, indeed,this one was between someone with 13 edits and somcoen who wasn't ECR, for heaven's sake -- somehow prove consensus was strong, and you think that means you can ignore all the later ones -- at one of which you didn't even respond to a ping, where people were objecting -- then this is maybe looking like aWP:CIR issue.
But even if youhad been somehow editing to support a consensus you believed was settled, you cannot edit-war contentious material into a BLP when others are objecting to it. The solution, always, is to go to talk, discuss, and reconfirm consensus. There is zero urgency to have this information in the article. Including something negative in a BLP is not something you shouldever edit war over.Valereee (talk)18:14, 15 January 2025 (UTC)[reply]
Luganchanka's reading of the state of consensus on the talk page as supporting their edits is so far off base that it borders on being a CIR issue if it's sincere. Indef block fromScott Ritter seems appropriate.signed,Rosguilltalk22:49, 14 January 2025 (UTC)[reply]
I see RTH's point about the "First sentence" section in isolation. I'd note that the link toWP:FORUMSHOP isn't really appropriate here, as bringing the discussion to BLP/N was an appropriate action (if it was then brought to NPOVN, NORN, etc.,that would be forumshopping). I'd like to see some actual contrition around the edit warring and frivolous accusations ofwhitewash before writing this off as time-served.signed,Rosguilltalk15:49, 16 January 2025 (UTC)[reply]
Understood, I think that meaning was clear for us here in the admin section, but I could easily see a new editor misinterpreting it unintentionally.signed,Rosguilltalk15:57, 16 January 2025 (UTC)[reply]
I am not at all comforted by the fact that Luganchanka has proceeded to makeSpecial:Diff/1269831044. The cited BBC source does not statemasturbated and ejaculated on camera, saying onlygraphic sex act. As written, this is essentially another BLP violation, building a case that a ban from this topic is needed.signed,Rosguilltalk16:53, 16 January 2025 (UTC)[reply]
Having reviewed the other sources, reliable sources do confirm the masturbation claim ([6],[7]) but not ejaculation, which appears to be supported only byNew York Post, a generally unreliable source.Luganchanka, in light of this clarification, can you please address your decision to include the claims as you initially wrote them?signed,Rosguilltalk17:02, 16 January 2025 (UTC)[reply]
The detail is in the record ofRitter v. Tuttle (case No. 3:15cv1235 (M.D. Pa. Dec. 14, 2018)), so it isn't completely made up. But I would also like to hear from the user on this point as to whether there was secondary sourcing here. —Red-tailed hawk(nest)17:32, 16 January 2025 (UTC)[reply]
SeeingSpecial:Diff/1269853673 here andSpecial:Diff/1269853955,Special:Diff/1269845272 atTalk:Scott Ritter, I see no comprehension of the use of primary vs. secondary sources, nor any reflection of their past errors in engaging with this topic. I believe that a block from the page is needed to prevent further BLP violations as they have shown no understanding of the relevant policies even after being given several warnings, reminders and opportunities to revise their position.signed,Rosguilltalk18:47, 16 January 2025 (UTC)[reply]
WP:BLPPRIMARY calls upon users tonot use trial transcripts and other court records, or other public documents, to support assertions about a living person. There are some narrow exceptions (whenprimary-source material has been discussed by a reliable secondary source, itmay be acceptable to rely on it to augment the secondary source), but adding material to the article not found in reliable secondary sources is... suboptimalat best under ourbiographies of living persons policy.
@Luganchanka: Would you please provide a direct link to the talk page section you are referring to when you saythere has been a clear consensus reached, on more than one occasion, and by senior wikipedia editors regarding the lead? —Red-tailed hawk(nest)01:57, 15 January 2025 (UTC)[reply]
It does seem that the discussion atTalk:Scott Ritter#First sentence does indicate some support for that language i.e. (convicted child sex offender) in the lead, with some general lean against putting it in the first sentence. So, whileThere has been persistent objection to descrbing Ritter as a "child sex offender" in the opening sentences is true if it means the literal first sentence, I do see a rough consensus to include the material in the lead section in some way in that discussion.
That being said, the BLPN discussion had a bit of different tone and tenor from the discussion on the talk page. There wasnotification about a BLPN discussion on the article's talk page, but Luganchanka, despite having been pretty vocal about this subject in the past, hadn't participated in that BLPN discussion. They instead grounded their edits in the argument that the article's talk page had consensus for the current content, and nothing on the article's talk page had changed that consensus. And that much was true. In any case, we've gottwo different forums with two different answerstwo different forums with two different answers here, which appears to be what's leading to the whole kerfluffle.
Then the analysis comes to whether or not the label is a straightforward BLP violation, requiring us to read the sourcing in the article.ThisNY Times piece, which is cited in thebody of the article (but not the lead), does state that Ritterwas convicted unlawful contact with minors and other charges in the state of PA (the PA statute ishere; "unlawful contact with minors" is the verbatim name of the crime). When dealing with a sting operation, PA treats it asan offense of the same grade and degree as if the criminal had actually contacted a child (unless it's a lesser crime than a third-degree felony, in which case it becomes a third-degree felony). This is an extremely common practice in the United States (there are lots of philosophical questions regardingmens rea andactus reus here, but that's not really relevant here). In any case, labeling this to be a child sex offense (or, alternatively, to simply use the name of the crime in the article) does not appear to be straightforward malice/POV-pushing/libel, and a reasonably informed individual might shorten it in this way. Whether or not that iswise oroptimal to shorten it is the proper subject for content discussion.
Aside from the edit warring (which was not acceptable, and was aptly handled by a block), this looks like a content dispute. A heated one involving a living person, sure, but a content dispute nonetheless. I see good-faith—albeit passionate—disagreement. If the editors were to come together and engage in one forum (such as the article's talk page, where this has been discussed a bunch), rather than splitting the discussion over multiple pages, I feel like we might have our best shot at attaining a consensus going forward.
In short, it looks like the conversation fragmented, and consensus-building broke down. Edit warring ensued, which was bad, but we've already blocked for that in order to dissuade it going forward. ARequest for Comment on the article's talk page for what the lead should look like is probably the best way to go forward here.
If we think that the user has been explainedWP:BLPPRIMARY to the extent that a reasonable person would conclude that they are either (a) intentionally ignoring it, or (b)unable to grasp the concept, then I do not object to a p-block from that article. Either such case heremight warrant something wider, particularly if this behavior pattern appears elsewhere.
But if they haven’t ever been explained the primary source rules, it might make sense to do that in clear and explicit terms before giving them an indef p-block. People who do research for a living, or work with primary sources in other contexts, often find our guidance a bit non-obvious since they are used to writing secondary sources instead of tertiary sources.
My apologies for the delay on this; I have been very busy.
With this in mind, I think we should wait to hear from RTH but otherwise expect to move forward to an indef p-block on top of SFR's stopgap action, as we haven't seen anything coming close to an adequate recognition of the relevant policies and practices from Luganchanka and after several second chances and nudges, I don't see reason to expect them to change course.signed,Rosguilltalk18:54, 18 January 2025 (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 500words and 20 diffs (not counting required information), except by permission of a reviewing administrator.
Request concerning BabbleOnto
User who is submitting this request for enforcement
This is all after I warned them aboutWP:AE sanctions, andthey dismissed my warning out of hand. Very nearly aWP:SPA on the subject. I see no reason to continue tolerating this kind of obstinatetendetiousness. Additional diffs available on request from admins, but looking at the user history should suffice to indicate the problem is obvious, I hope.
Statements must be made in separate sections. They may not exceed 500words and 20 diffs, except by permission of a reviewing administrator. Administrators may remove or shorten noncompliant statements. Disruptive contributions may result in blocks.
To be honest I'm not entirely sure what it is I'm being charged with doing.
I think in general the user is alleging I've been uncivil, unhelpful, and, in their words, obstinate and tendentious. I know when someone disagrees with you it may feel like they're getting in your way and acting in bad-faith, but that's not always true. I've never tried to be disruptive or uncivil. I'veadmitted when I was wrong, I'vedropped arguments that were clarified to be wrong, I'vetried to find compromise, at timesbegging people to provide their sources and work together. And when those editorsrefused to, I didn't provoke any further.
I now address the specific edits in the complaint:
1. I don't see how this is sea-lioning. The user misquoted the article. I pointed out the misquotation, then addressed a accusation against me that I was second-guessing the sources (A claim which was never substantiated). I then said any source would have to support that actual claim which was in the article. I don't know what this violates.
2. I don't see how this is refusing to get the message (IDHT). The other party is making direct claims alleging I said something. I did not say it. I replied with what I actually said. What part of that interaction is saying "I didn't hear that?"
3. Admittedly probably the strongest of the four allegations. I'm not pretending I was perfect in all of my comments. I should have kept my criticism strictly to their argument. I ask you to read it in context and keep in mind you're viewing a hand-picked assortment of my worst edits, and this is the worst they could find. Also consider that conversation accused me ofhaving a basic reading comprehension problem, perhaps you can see I lose my cool sometimes too.
4. I'm not even really sure what "railroading the discussion" means. Thus, to keep this section short and to save words, I don't know what I'm being accused of doing wrong here.
All of this has stemmed out of arguments over two sources. I have tried to find compromise, I have tried to negotiate, I have tried to build consensus. I've been going through the proper channels, I've been participating in the RfC, I've been discussing it on the ANI, I source every claim I make, for a month now I've been trying to constructively explain my side and defend my argument against challenges. It's incredibly frustrating to now be facing an Arbitration Enforcement on grounds thatI'm not working with others.BabbleOnto (talk)23:54, 13 January 2025 (UTC)[reply]
Sorry, the sub-header for this section says that only admins can edit this section, I didn't realize I was allowed to reply here.
Yes, I will. I intend on taking an extended break from wikipedia, as well.BabbleOnto (talk) 17:06, 19 January 2025 (UTC) Moved from uninvolved admin section; you can answer questions, make comments, discuss, but all your input needs to be in your own section.Valereee (talk)17:15, 19 January 2025 (UTC)[reply]
an extended break doesn't solve the issues around understanding policy. An extended break from contentious topics -- while you edit in other topics and learn policy -- would be more helpful all around.
What I meant was that I'm willing to respect the consensus and not make any further edits or argue any more contrary to what the consensus decided. It seems to me that saying I have "Issues around understanding policy" and asking me to "learn policy" has subtext that says "Until you agree with this consensus, and you won't be allowed to edit at all." Is respectful disagreement with this consensus allowed? I'm afraid if in order to avoid a ban I have topersonally agree with the consensus, beyond just respecting it, then there's nothing I can do. I still do disagree with the consensus's result. Nonetheless, I'm not going to edit or argue further, I'll respect it as a legitimate.
Re:no, you don't have to agree. You just have to accept and move on.
Then I accept the consensus. I'm not going to argue in those discussions any further, though I still personally disagree, I understand a consensus has been reached which is other than my opinion. Nor will I edit disruptively or against the consensus. I appreciate the admin who noted I largely kept my disagreement in the talk pages, not editing the articles themselves. I plan on staying away from the topic in general for quite a while.
Re:BabbleOnto, do you understand what we're talking about when we describe your participation at talk pages as WP:sealioning, and why we think it's such a problem, particularly in contentious topics? Do you think you can avoid participating in that way at article talk pages?
Yes, and yes.
Statement by ProcrastinatingReader
I've interacted with BabbleOnto in several threads. There's a few problems, but ultimately, I think they have a certain opinion on what the article should say, and will debate endlessly to get the article changed to their position. I mean, sure, reasonable people disagree on how to interpret sources and apply policy, but I don't think BabbleOnto is actually interested in faithful application of policies to write high quality articles based on good sources.
That's not terribly problematic by itself, but most discussions with BabbleOnto are exhausting. Rather than actually trying to understand someone's argument in good faith, I think BabbleOnto replies to editors by picking out parts of an argument, interpreting it in the most disfavourable way possible, and making a superficially reasonable responsead nauseam. They reply endlessly in this manner. As well as misrepresentation of opponents' arguments, on multiple occassions BabbleOnto has either misrepresented sources or hasn't read their own sources. I can't think of a single thread where BabbleOnto didn't have the last word, or a single thread where it seemed like BabbleOnto was actually trying to understand the arguments of other editors in a charitable way. As such, I think it's very difficult to work collaborately with BabbleOnto on the lab leak theory and related articles.ProcrastinatingReader (talk)21:07, 13 January 2025 (UTC)[reply]
Statement by Newimpartial
As the editor to whom BabbleOnto was responding in the diffs of the filing, I feel compelled to comment now that they have defended (to varying degrees) their first three diffs. I will reply as briefly as I know how to their defense of the diffs,as revised.
1. BabbleOnto is now doubling down on the claim that Imisquoted the article. I didn't "misquote" the article - I didn't quote the article, and I explained what my comment meant in the rest of the (now collapsed) thread that endshere. Also, I provided a clear explanation of why I thought they were second-guessing sources later in the thread, but BabbleOnto never responded to that explanation. They are now responding to the accusation ofWP:CPUSH with pureWP:IDONTHEARTHAT.
2. On this they say, now, thatThe other party is making direct claims alleging I said something. I did not say it. This is repeating a misreading they made in the original thread, where they mistook a statement I made about another editor's comment as if it were about theirs. In this "defense", I see no attempt to read thoughtfully what other editors say in reply to them and revise their understanding accordingly; all I see is zero-sum mentality andWP:IDHT.
3. BabbleOnto is now justifying an edit where they said to me,You have a habit of inserting small lies into everything you say andYou're not adding anything constructive. You're just refusing to explain anything and saying conclusory statements, or lying about what you said - all this based on a misreading of what I had actually written - because I was going to refer toa basic failure in reading comprehensiontwo hours later. This seems like a time travel paradox.
4. They don't bother defending themselves on this one, but just to point out the actual issue with the diff, they doubled down on their accusations that Isaid a material lie, and that Ilied when [I] said that [they] quoted the article out of context. Pointing out [me] being caught lying and then proceeded to STRAWMAN the rest of my comment to which they were replying. If they had read my prior comment with a reasonable level of attention, they would have understood that there were no "lies", just a misunderstanding or two in each direction. ButWP:IDHT again; even in responding to this filing BabbleOnto is still insisting I did things that I quite obviously didn't do.
It is exhausting to deal with this kind of quasi-CPUSH (not quite civil, but certainly push) behaviour. The Talk page in question has seen a recent influx of single-purpose or nearly single-purpose POV accounts, and in terms of editor energy, this one certainly seems not to be a net positive for Wikipedia as a project. Perhaps if they edited away from Covid and US politics, their track record might improve.Newimpartial (talk)03:33, 14 January 2025 (UTC)[reply]
@Valereee, this is also a problem at other CTOPs, and is likely to become more problematic. I assume due to off-Wiki forums. ECR might just produce more users gaming EC. I thought it would be useful to put your aside into the CTOP template at the top of CTOP TPs. But that assumes folks read it. Walt Kelly said something along the lines of: “If only I could write, I’d write a letter to the mayor, if only he could read." This discussion is likely better off elsewhere.O3000, Ret. (talk)21:38, 14 January 2025 (UTC)[reply]
Note:IntrepidContributor was just TBanned from the topic of COVID-19 and indef blocked until the accusations of off-wiki coordination made by them at ANI[8] are retracted. Those accusations are like their suggestion made in their statement in this filing.O3000, Ret. (talk)12:11, 18 January 2025 (UTC)[reply]
I have been observing BabbleOnto and while there are valid concerns about bludgeoning, I think the proposed sanctions are too much. His engagement in the Covid lab leak topic is driven by commitment to WP:NPOV, which our articles fail to adhere to, and he made the mistake of arguing with editors who were never going to listen (resulting in what looks like sealioning on his part). He's not only editor to raise issues in the topic and engage in good faith discussion, only to find themselves pulled to AN or AE disputes after staying out of the seasoning traps and refusing to capitulate to threats. In a parallel AN case concerning another editor in same topic, I suggest there may be possible off-wiki coordination[9], but it can also be on-wiki ([10]).
One need only cross-reference names fromFeb 2021 RfC, checking those that voted for labeling COVID-19 lab leak as conspiracy, with the names of complainants here. Contrast all these old timers with the steady stream of tens if not hundreds of regular editors complaining that our article fails NPOV, and see that their gentle approach doesn't work[11]. Our chief complainant is already preparing his next case[12], and this might not be his first.
I suggest that administrators consider a 1 to 2 month topic ban for BabbleOnto to provide opportunity for him to correct his approach, while staying alert to the tactics of POV editors trying to draw them into content debates to influence outcomes.
Please seethis edit where BabbleOnto editedGain of function research restoring previously reverted content andWP:POVPUSH using a shit source after they'd been told by multiple other editors in discussionshere andhere that the source was shit. Notably in the edit summary they wrote "Read discussion page. Manual revert. No serious challenge has been made to these changes. Methinks an admin needs to get involved..." despite them being in aWP:1AM situation. If a clue is not gotten by the editor fast I'd suggest TBANs from both COVID and AP2 is warranted in order to cease their disruption.TarnishedPathtalk04:25, 18 January 2025 (UTC)[reply]
This user was given no less than 4 chances on the talk page to stop talking about bans/other editors and start talking about the content. They have continued crying about how they're scared of getting banned... yet they continue blabbing about other editors getting banned for their bad behaviorrather than refocusing on the content as requested.At a minimum a partial block from the talk page(s) in question is warranted, and it would be beneficial for a topic ban from the origins of COVID-19, broadly construed. -bɜ:ʳkənhɪmez |me |talk to me!03:37, 19 January 2025 (UTC)[reply]
Statement by Shibbolethink
I am heavily involved in this overall dispute as someone who has gone back and forth with BabbleOnto. I wanted to add that, in general, my feeling from interacting with this user is that theycould be a good contributor to this site, and absolutelycould follow the PAGs. They have shown an ability to be courteous[13]. I think the issue is that in FRINGE and other contentious areas like COVID-19 origins, they have shown a tendancy to become "hot-headed" when tensions rise, and to reference an us vs them mentality[14] (and numerous examples from others above). It seems they have also been egged-on, and made more combative from other PROFRINGE users (and probably some anti-FRINGE users as well who do admittedlyWP:BITE) in that topic space (e.g.[15][16][17])
We are told often to use narrowest possible restriction to protect the project. In this case,I think that would be a COVID-19 origins TBAN, where most of the disruption has been. The user states they have learned what to do when consensus is against them. If they fail to show that lesson in AP2 articles more than just the 10 or so edits they've made in those articles, an AP2 TBAN would be appropriate at that time (WP:ROPE). Just my 2 cents.— Shibbolethink(♔♕)22:05, 19 January 2025 (UTC)[reply]
Statement by (username)
Result concerning BabbleOnto
This section is to be edited only by uninvolved administrators. Comments by others will be moved to the sections above.
BabbleOnto, please edit your statement down further to fit within the restriction. This also serves as an opportunity to rephrase your defense, which currently is not convincing at first glance. ProcrastinatingReader's description of the situation seems quite apt, particularlyBabbleOnto replies to editors by picking out parts of an argument, interpreting it in the most disfavourable way possible, which is currently a pretty fitting description of your response to them here, given that you zeroed in on the "superficially reasonable" part and ignored the much more serious parts of the testimony.signed,Rosguilltalk23:37, 13 January 2025 (UTC)[reply]
Ok, having read through nearly every edit that BabbleOnto has made, I agree with the complainants that not only does BabbleOnto engage in sealioning, it appears to be almost exclusively what they do. The discussion atTalk:Brian Thompson (businessman)/Archive 2 exhibits perhaps even more concerning argumentation than the diffs provided in the initial report. Throughout these discussions, BabbleOnto tends to demand a standard of stating the obvious (with respect to the context of said sources) that is absurd, and continues to lawyer for such standards even when the situation becomesWP:1AM. When criticizing sources' ability to account for basic claims, I can find no examples of BabbleOnto themselves attempting to find sources that would resolve the issues they identify--this is uncollaborative behavior. There is a clear pattern of engaging in this behavior across recent US politics topics consistent with the scope ofWikipedia:Contentious topics/American politics. The only saving grace to BabbleOnto's track record is that none of this has translated into disruptive editing of actual articles, just unproductive engagement on talk pages. I am currently in favor of a topic ban from post-1992 American politics; if they are actually here to build an encyclopedia and not to provide a punching bag for debate club, they can use this opportunity to learn more constructive patterns of editing in topics that they are less personally invested in.signed,Rosguilltalk01:26, 14 January 2025 (UTC)[reply]
Valereee in line with their follow-up response, I take Objective3000's comments as potentially a basis for community discussion rather than a call for protective action on the lab leak talk page right now.signed,Rosguilltalk21:47, 14 January 2025 (UTC)[reply]
I have to agree, this looks like sealioning.BabbleOnto, you're new here, and I'd like to give you the benefit of the doubt about your ability to learn to collaborate. WP works on collaboration and consensus, and sometimes consensus goes your way, sometimes it doesn't. You have to be willing to shrug, walk away, and go work on something else when consensus is against you. And you absolutely must not insist everyone else keep answering you until you're satisfied with their answers. I've seen editors at both the Thompson and the lab leak talks tell you they don't actually owe you an answer to your satisfaction.
Do you think you can learn to do that? Because if you don't think you can, this may not be the right hobby for you.
As an aside, I'm going to recommend what I always recommend to new editors who end up here: Contentious topics are a terrible place to learn. Go edit in noncontentious topics, where other editors are a lot less exhausted and have the energy to be more patient with new editors.Valereee (talk)18:27, 14 January 2025 (UTC)[reply]
Tangential
@Objective3000, hm, yes, andTalk:COVID-19 lab leak theory also has 37 archives, and even with archiving at 21 days, 20 sections. Do you think an ECR is something that talk page needs? That's not part of the authorized restrictions an individual admin can place...hm, and I'm not sure of the policy w/re most efficiently getting that done and wasting the fewest people's time. @Rosguill?Valereee (talk)21:08, 14 January 2025 (UTC)[reply]
I would object to ECPing the talk page. COVID-19 isn't subject to ARBECR generally, though this specificarticle is protected. The purpose of protecting the page (in this case) is to push newer users to the talk page, where they can discuss changes they want made (such as by edit requests) and contribute towards consensus-building while not edit warring. Protecting talk pages is truly,truly a last resort. Ordinary good faith people would be entirely shut out and silenced—we'd not even get edit requests—and I frankly don't see anything near the level of disruption/LTA abuse that would justify jumping straight toWP:ECP. —Red-tailed hawk(nest)01:55, 15 January 2025 (UTC)[reply]
I see. In any case, ECR is the sort of remedy that should be reserved for more or less when all else fails—it’s stillsuper restrictive. If new users/inexperienced users are trying to contribute towards consensus-building on the talk page (or even if they’re doing ordinary confused new editor things), and aren’t edit warring, I don’t think we’d actually bepreventing disruptive edits by enforcing ECR.
Suppose someone in good-faith sees “anyone can edit”, and they want to edit something topical. But then they see that the page that they want to edit is protected. They read the explanation that appears after clicking the “view source” tab. They then read that they can discuss this page with others, click on the first blue link, and then make a section using the “add topic” button in order to start a discussion.
“OK”, the newbie thinks, “maybe I will find someone else who agrees with me, or I’ll at least get some answer as to why the article is this way”. They leave their computer and come back in an hour. They then discover that their question has been removed by some random editor with edit summary “WP:ARBECR violation, user notWP:XC; malformed edit request” and find a contentious topics notice on their own user talk page, all because they don’t make a properly formatted edit request (i.e. “please change X to Y”). Or maybe they wont navigate the talk page history and they’ll angrily post that their earlier comment was deleted. Or maybe they just won’t come back. To top it off, nothing at any point in this process was obvious to them that such a requirement existed—there is no edit notice that says so, and so they couldn’t know.
WP:ECR isWP:BITEy. It dissuades new voices from joining conversations, and it makes it somewhat hostile to true newbies. In particular, it dissuades people who, for example:
Are Not hardcore/insane enough to deal with intense wiki-bureaucracy;
Are unable to cope with handling unfamiliar wikitext markup when making edit requests for anything that is not a trivial word change, or who have abstract changes in mind more than concrete ones;
Do not want to spend an hour of their time to figure out how to say the magic words to summon another editor to fix a typo.
The chief way that ECR works is by making LTAs/sockmasters have to put on a lot of effort or make a lot of edits. This raises the (time) cost of socking, and it has the benefit of possibly exposing tells along the way. But that also means that we’re imposing the same thing on good-faith newbies.
When deciding whether or not to impose ECR, we have to balance that it is extremely BITEy to good-faith newbies against its ability to prevent disruption. There are times where we are basically left to throw our hands up because of LTA/sockmaster abuse, and conclude that the tradeoff is worth it; the ArbCom has done this for certain contentious topics. But, the ArbCom had the wisdom to not enable ECR as a page sanction across all contentious topic areas—there is a very real tradeoff that needs to be really carefully considered. And I don’t the tradeoff leans towards embracing ECRhere. —Red-tailed sock(Red-tailed hawk's nest)15:48, 15 January 2025 (UTC)[reply]
I'm don't think we need to have this discussion here and now, but I don't disagree it's bitey and needs to be used only where necessary. I was just asking the question of someone who is working at that article: is this an article talk where it's necessary?Valereee (talk)17:45, 15 January 2025 (UTC)[reply]
BabbleOnto, are you planning to answer my questions above? Do you think you're able/willing to shrug, walk away, and go work on something else when consensus is against you? Are you able/willing to stop insisting everyone else keep answering you until you're satisfied with their answers?Valereee (talk)13:26, 19 January 2025 (UTC)[reply]
BabbleOnto's response understanding this as a suggestion to take a break from Wikipedia as a whole isn't quite what I was hoping to see.signed,Rosguilltalk17:22, 19 January 2025 (UTC)[reply]
@BabbleOnto, an extended break doesn't solve the issues around understanding policy. An extended break from contentious topics -- while you edit in other topics and learn policy -- would be more helpful all around.
AP2 + COVID? I see the same behavior at the Brian Thompson article and Havana Syndrome, so COVID alone doesn't seem adequate. Oddly, the intersection of "medicine and politics" would appear to cover all affected topics but maybe that's too bespoke?signed,Rosguilltalk17:56, 19 January 2025 (UTC)[reply]
@BabbleOnto, re:It seems to me that saying I have "Issues around understanding policy" and asking me to "learn policy" has subtext that says "Until you agree with this consensus, and you won't be allowed to edit at all." Is respectful disagreement with this consensus allowed? I'm afraid if in order to avoid a ban I have to personally agree with the consensus, beyond just respecting it, no, you don't have to agree. You just have to accept and move on.Valereee (talk)23:22, 19 January 2025 (UTC)[reply]
I thinkBabbleOnto is actually getting the right idea. You do not have toagree with consensus. There are some consensus positions here I don't agree with, and some I think are rather silly. But, until and unless they change, I respect and abide by them all the same. If I try to challenge them, and it becomes clear that such a challenge was unsuccessful, there comes a time to just shrug, realize you can't win 'em all, andmove on. Since they seem to have gotten that point, I think maybe see how things go, and if they return to disruption, I think they're quite clear on what the results of that will be.SeraphimbladeTalk to me14:05, 21 January 2025 (UTC)[reply]
In my experience sealioning is a habit editors have an extremely difficult time breaking. I was going to agree with Rosguill re: a tban from AP2 + COVID, maybe appealable after 3 months and 500 productive and unproblematic edits. This editor is basically ONLY editing in CTOPs, they're doing it disruptively -- we're talking about an editor with only 177 whom other editors are describing as exhausting to interact with! -- and the specific kind of disruption is both frustrating and tedious to proveand frustrating to try to get attention to because who you need so many diffs to prove it. That plus the apparent difficulty in breaking that habit, which btw they were continuingduring this case...I dunno.Valereee (talk)14:20, 21 January 2025 (UTC)[reply]
I certainly understand your point. I am a little hesitant to sanction for "sealioning", as often it is difficult to tell where enthusiasm ends and disruptive tendentiousness begins, and I certainly do not want to have a project where people are afraid to advocate viewpoints contrary to a current consensus. That said, if everyone else feels sanctions are warranted, I won't object terribly strongly; I just generally prefer someone to get a chance to show if they've gotten the point (or in some cases, to conclusively demonstrate that they have not).SeraphimbladeTalk to me20:02, 21 January 2025 (UTC)[reply]
Generally I'm with you. Let people show they've dealt with the issue. Reblocking is pretty easy in most cases. But sealioning...well, it's such a difficult issue to prove/assess, and there are so many people doing it who don't even have the self-awareness to fix the problem that I kind of feel like it needs a tougher approach than I'd normally argue for. Not a hill I'm going to die on, but if the editor is back here or at ANI for the same issue, I am going to be extremely unhappy with them.
@BabbleOnto, do you understand what we're talking about when we describe your participation at talk pages asWP:sealioning, and why we think it's such a problem, particularly in contentious topics? Do you think you can avoid participating in that way at article talk pages?Valereee (talk)20:27, 21 January 2025 (UTC)[reply]
This is such a difficult behavior to deal with, and in multiple CTOPs. Would anyone support a logged warning something along the lines that further instances of sealioning are grounds for a topic ban from contentious topics, placeable by any uninvolved admin?Valereee (talk)15:31, 29 January 2025 (UTC)[reply]
This request may be declined without further action if insufficient or unclear information is provided in the "Request" section below. Requests may not exceed 500words and 20 diffs (not counting required information), except by permission of a reviewing administrator.
Request concerning Ekdalian
User who is submitting this request for enforcement
21:55, 11 January 2025 - Casting unsubstantiated aspersions and poisoning the well against another editor.
12:01, 13 January 2025 - Poisoning the well against another user without any evidence of misconduct.
19:11, 15 January 2025 - Restoring recently added disputed content again and essentially asking to get consensus for it, contrary toWP:ONUS.
15:05, 16 January 2025 - Performs a blanket revert in order to make aWP:POINT, just because their previous edit was reverted, despite it being the version that was arrived upon by a month long discussion onthe talkpage, also saying "LE also wants to discuss and revisit the content proposed by the sock" , LukeEmily later elaborated that they are okay with the version that Ekdalian was actually reverting[18]
19:42, 16 January 2025 - Edit warring and casting aspersions saying that reverting editor is acting like the blocked sockNobita456 "stop behaving like Nobita please"
14:31, 18 January 2025 - Attacks and tries to poison the well against another editor also says that "WP:ONUS doesn't mean you need to achieve consensus with editors condemned by admins for persistent POV pushing! "
18:47, 18 January 2025 - Restores the aforementioned attack saying "Related to the content only, related to WP:CONSENSUS to be precise; accept the truth, I don't want to report minor incidents" when told to focus on content
Has a {{Ds/aware|ipa}} template for the area of conflict on their own talk page.[20] and notified of WP:ARBIPA by Dennis Brown in 2022[21]
Additional comments by editor filing complaint
I also note that Ekdalian has a history of aggressive edit warring in the contentious topic as a part of slow running edit war[22].OnBengali Kayastha, many of their most recent edits have been reverts to prevent content addition as well. It has gotten to the point where experienced users likeSitush have called them out for it[23][24][25] because they usually misrepresent the consensus or comments by editors such as Sitush to claim that consensus already exists when there is none, they do not provide diffs when asked to substantiate their claims either. They have been reprimanded in past[26] over similar conduct about misrepresentation and exaggeration by@Dennis Brown: on this venue as well. They have a history of attacking other users and trying to poison the well against them instead offocusing on the content as diffs above prove.
I am not seeking any topic bans but Ekdalian should be at least told not to misuse the talk page for adding more fuel into heated disputes, and use the revert button only when it is necessary.NxcryptoMessage03:26, 20 January 2025 (UTC)[reply]
So, do you still stand by your aspersions in the edit summary and restoration of disputed content contrary toWP:ONUS?
Were you wishing to ensure WP:NPOV by poisoning the well against an editor? How does that even help the discussion? ReadWP:FOC.
So, do you believe you have the right to cast aspersions without accompanying it with required diffs? "Admins are aware how you had kept the term 'Kshatriya' in the article onMahishya in spite of knowing that it is an agrarian caste! " - Which admins are aware of this "edit" that you accuse CharlesWain of pushing? In fact you made a similar accusation before too but it was a different good faith editor that made that edit not, CharlesWain.[27][28]
So you think the onus to achieve consensus depends not on the people who want to include the content but on those who dispute it?
It's only you who considered it a WIP version[29] contrary to these comments that indicates that there was a consensus at the talkpage[30][31], secondly why did you perform a blanket revert only because your previous edit was reverted, isn't that a veryWP:POINTY behaviour?
Why did you have to start a heated edit war? You could instead asked them for clarification to know what exactly they meant when they said that content needs to be "revisited". You state that the editor has been warned for "teaming up with Nobita", when did that happen?
Knowing someone on wiki doesn't mean you get to attack them also what do you mean by "behaving like Nobita"?
Do you really think the attack you made at the editor and saying that you don't need to achieve consensus with them just because they were blocked for edit warring was the "truth"?
Same as above, that restoration combined with your assertion here proves that you think it's appropriate to poison the well.
Statements must be made in separate sections. They may not exceed 500words 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 Ekdalian
I have nothing to say as such! I have been serving Wikipedia since 2013, particularly related to contentious caste articles, fighting against caste promotion, POV pushing and vandalism. Heated debates are common in the contentious topics. I have neither violated 3RR, nor abused any editor! Yes, in case someone has been topic banned and condemned by admins, I do mention the same so that NPOV is not violated. Many admins are aware of my activities including SPI, anti-disruption and anti-vandalism. Thanks & Regards.Ekdalian (talk)06:44, 20 January 2025 (UTC)[reply]
Action (warning) may be taken against NXcrypto for being unable to identify vandalism (refer to point number 10), and wasting the time of our admins! Thanks.Ekdalian (talk)06:52, 20 January 2025 (UTC)[reply]
Nxcrypto, it is a clear case of vandalism. The user intends to misrepresent and project their caste asKulin Kayastha (higher status among Bengali Kayasthas) by intentionally changing Eastern (Bengal) to Western! Moreover, the user has done similar vandalism in multiple articles only in order to promote Western Bengali Guhas. Thanks.Ekdalian (talk)08:29, 20 January 2025 (UTC)[reply]
In response to Bishonen's comments, I would like to inform here that Sitush is referring to my response at a time whenNobita456's sock was driving a discussion and I had filed an SPI! Therefore, I was delaying the discussion in order to eliminate the sock from the same. Sitush has been quoted out of context! Thanks.Ekdalian (talk)12:52, 21 January 2025 (UTC)[reply]
@Bishonen: I have clearly mentioned that I am not sure! But,Orientls seems to be so sure that they have stated that I am 'falsely' accusing him of meatpuppetry! How can you be so sure that there has been no mail exchanges? Orientls, do you think you are God? Regards.Ekdalian (talk)06:39, 22 January 2025 (UTC)[reply]
ThanksLukeEmily for commenting here! I don't think I have to explain every diff provided here since Bishonen has already mentioned thatI don't think NXcrypto's diffs are anything much; it's surely a stretch to call them "casting apersions" and "poisoning the well" and the like, especially in the IPA area where the tone is often sharp. But as LukeEmily suggested, let me answer each point briefly:
1. My edit summary explains why I reverted.
2. I wanted to ensure that NPOV is maintained.
3. I am not filing anything anywhere against the user; why shall I provide evidence? The concerned user understands what I mean!
4. Again, my edit summary explains why I reverted.
5. No, this is not the last consensus version, it represents a WIP version; explained today onTalk: Bengali Kayastha!
6. LukeEmily has already accepted the lapse in communication for point numbers 5 and 6.
7. It was a request since I know the user (interacted in Wikipedia for years) and I expect rational behavior from him! I have used the word 'please'.
8. Saying the truth in order to ensure NPOV; repetition (refer to point number 2)!
9. Same as above! The editor should not have reverted my edits on the article talk page!
10. If the filer cannot understand what is vandalism/disruptive editing, I have nothing to say. The user has already been blocked for vandalism! Thanks & Regards.Ekdalian (talk)09:46, 24 January 2025 (UTC)[reply]
NXcrypto, first things first! Admin Dennis Brown never said what you have tried to project! Admins here may read their statement! I shall answer your questions, but since you have done good research on my edits, can you answer my questions? Needless to mention, these are relevant to your questions!!
1. Are you aware of the socks ofNobita456 and their activities?
2. Are you aware of the POV pushing onBaidya and negative POV pushing onBengali Kayastha by the sockfarm and the related discussions on the talk pages of experienced admins here?
3. Are you aware of the fact that the user CharlesWain and Nobita along with some blocked users in English Wikipedia had created poorly sourced articles in Bengali Wikipedia, which is relevant here since we had a detailed discussion on an admin's talk page here?
4. Are you aware that even an admin from Bengali Wikipedia participated in the discussions here in English Wikipedia and Nobita was blocked from Bengali Wikipedia as well?
5. Are you aware of the discussion here regarding CharlesWain related to negative POV pushing in Bengali Wikipedia on an admin's talk page here and another involved admin posted a notice on their talk page?
I shall not provide diffs, etc since I am not filing a report against CharlesWain!
Coming to your questions, please find my replies below:
1. No, such edit summaries are rarest among rare ones and such reverts are done in exceptional cases in order to ensure NPOV!
2. Let admins decide.
3. I never said, CharlesWain inserted the word, but said 'kept' since CW had reviewed, added content and cleaned up the article!
4. No, in general; again, let admins decide if they want to!
5. Just look at my edit summary; I was thanking CW only for verification, not for consensus. Honestly speaking, it is WIP, that's the reason LukeEmily has proposed an NPOV summary (in article talk) instead of that paragraph!
6-9: Either already answered indirectly or else choosing not to answer!
I find this comment by Ekdalian unpalatable: "The user intends to misrepresent and project their caste as Kulin Kayastha." How are you so sure of their caste? I don’t see where they have self-identified as such, and you also accuse them of attempting to project "their caste'" with another one by "vandalising" Wikipedia, which is a serious accusation against a new editor. I think an editor of your tenure should be able to recognize what constitutes vandalism because those edits are not vandalism, you should also refrain from speculating about the caste of editors.
This reasoning seems odd, especially when Sitush himself states: "CharlesWain began this discussion. They are not a sock, are they?"[33], implying that you were opposing changes proposed by an editor who was not a sock by misrepresenting Sitush's comments. I also think canvassing was inappropriate, particularly with its problematic heading, "Kind attention: Bishonen and admins active here." It sounds as if you are trying to recruit people to back you up here.
Honestly, I’m not surprised by the diffs cited in the report, especially if your conduct at ARE is like this where your edits are under scrutiny.
@Bishonen: While the filer himself made it clear that he is not "seeking any topic bans", Ekdalian deserves a topic ban following thisnew message. By calling an editor with almost 4k edits a "comparatively new user" and falsely accusing him of "meatpuppetry", Ekdalian has proven he is not capable of editing here without poisoning the well and making personal attacks.Orientls (talk)03:44, 22 January 2025 (UTC)[reply]
Statement by LukeEmily
I came across this by accident(don't have any email address associated with my account for private communication). I was not pinged here although my name was mentioned. In general, I agree with@Bishonen:. Bishonen and other Admins, please may I request a couple of days to review/comment on each point in more detail?@Ekdalian:, please could you change your response to bevery specific for each of the 10 points made? Also, please be less emotional("are you God?" is an emotional response):-). Please could you respond in terms of diffs(facts) for each point instead of subjective statements that are difficult to confirm without diffs? (5) and (6) were not Ekdalian's fault. Yes, it is true that I disagreed with Ekdalian about the content/consensus. But Ekdalian's good faith misunderstanding about my position was due to my faulty communication, I did in fact say "revisit" and apologized later and took responsibility for my unclear statementshereLukeEmily (talk)01:53, 24 January 2025 (UTC)[reply]
Ekdalian has been a hard-working editor fighting against POV on caste pages for years. That being said, I do not agree with Ekdalian's aggressive choice of words in edit summaries, personal attacks and canvassing. The comments by Sitush to Ekdalian on Bengali Kayastha talk page are also a little disturbing. Also, I wish Ekdalian had provided some diffs for some allegations he made. Here is a more complete story.Ekdalian filed a complaint late last yearhere against the same editor who had returned after TBAN was lifted and but the complaint got sidetracked. There was a discussion about filing another one laterhere but we were told to not try something silly as it would boomerang.
Below is the POV pushing as pointed out byFowler and Fowler,Sitush and adminAbecedare earlier. Comments by these senior editors would all be irrelevant now in 2025 since action was already taken against the editors at the time(and later the TBAN was removed). However, the problem now is that thesame POV pushing is going on - that resulted in the earlier ban in the first place. The first section(discussing rajputra, thakur etc) currently gives a very different impression than "a community of armed peasants before the 16th century" as mentioned by F&F below. Please see admin's comments below about the "subtle" POV effort to move puffery at the top of the page. Later sections on the page are giving correct details(mostly) - also the age of the caste has been back pushed to 7th century in the lead although scholars have explained that the usage of Rajput for earlier clans is anachronistic.
Rajput/Rajputra POV pushing comment by adminAbecedare to falsely indicate Royal originhere
Fowler and Fowler (2021) cites several sources and saysRajputs were basically a community of armed peasants before 16th centuryheremorehere andhere
Here, despite all the above and warning, the Rajput page is going back to square one before the TBANs.I suspect this is what triggered Ekdalian's (unacceptable) reaction.
I do not know why he suspected meatpuppetry but I can only assume that might be because multiple editors involved (at times) in Rajput related caste articles seem to support each other. I am not accusing anyone of meatpuppetry. But this is one example that I found strangehere, Timovinga(a suspected SP), is told "I will not let (you) get away with this comment". Then Timovinga(probably scared) backtracks but he again finally disagrees with the editor who warned him two days later.here and calls it his final response(at 14:16, 1 January 2025 (UTC)). Within 12 minutes of Timovinga giving his final answer, two editors add a lot of behavioral evidence for his sock puppetry on other pages and get him bannedhere amdhere. Again, I am assuming good faith but the 12 minute timing is a little coincidental given that the sockpuppetry investigation against him was open for more than a month. Please also see these edits herehere and the identities of the editors involved in october 2024. The original page wasthis. Please check the page now. The separate important section heading on Mughal(Muslim)-Rajput(Hindu) alliances is gone. I don't know if Ekdalian was watching this page, but if yes, it would also explain the meatpuppetry suspicion.
There is a undoubtedly a history ofWP:PUFFERY in the Rajput related pages in the previous years, an attempt to rewrite or whitewash history, a facebook group being formed etc -@Adamantine123:, do you have the diff for the FB page?.
In summary, I can understand why Ekdalian was upset. But I disagree with his reaction. Editors should be polite, stop aggressive/rude communication, canvassing admins and focus on content only and provide evidence(diffs) for any accusations. Doubling down on this page itself was also unacceptable. Ekdalian, I say this as a well wisher as it will help you in the long term. Hence, I agree with the concerns raised by all admins in this section - not because they are by admins - but because I feel their concerns are accurate, based on facts and impartial. I am not an admin(and not experienced like Sitush, F&F etc) but I request that a TBAN not be imposed at this time since Ekdalian had the right intention to stop POV but took the wrong approach. BTW, I got a recent threathere from a "superior rajput". Thanks,LukeEmily (talk)04:51, 28 January 2025 (UTC)[reply]
This section is to be edited only by uninvolved administrators. Comments by others will be moved to the sections above.
I will point out that I wascanvassed to this discussion by Ekdalian. That said, I'll state that I don't think NXcrypto's diffs are anything much; it's surely a stretch to call them "casting apersions" and "poisoning the well" and the like, especially in the IPA area where the tone is often sharp. The comments by Sitush are a little more concerning, though.Bishonen |tålk10:08, 21 January 2025 (UTC).[reply]
My investigation:
Rajput's history shows a lot of subpar engagement by multiple editors, in which Ekdalian's participation is non-constructive (if not the worst offender)
The aspersion against Dympies is unnecessary, even though it is factual with respect to a 2023 TBAN that was eventually appealed a bit over a year later
The reply to Charles Wain in the 3rd diff, while not quite a personal attack, is less than civil
I'm not sure the edit is POINT-y, but both Ekdalian and CharlesWain are engaging in too much edit warring
Diffs 8 and 9 are completely unacceptable and I can only assume thattBishonen didn't get that far into reviewing the report. An editor who has had their topic ban appealed is an editor in good standing until proven otherwise. If there are issues with Dympies behavior so severe that they preclude collaboration, you need to bring that to AE with appropriate evidence. You do not get to assume bad faith of people simply for having been previously sanctioned.
Diff 10 is a non-issue
I think at minimum a warning is needed, and honestly the combination of edit-warring, aspersion-casting, and doubling down makes me seriously consider a topic-ban from caste topics. If so, we should probably also examine the edits of others participating in the edit warring more closely, as really, some of those edit histories are veritable war zones.signed,Rosguilltalk 20:48, 24 Ja anuary 2025 (UTC)
Alsocanvassed by Ekdalian. I'm not convinced about a TBA but warning is certainly needed here. I'd like to see what Luke Emily has to add and would be happy to wait a couple of days. It still might be worthwhile to examine others participating, but we can only bring one person here at a time now.Doug Wellertalk15:23, 25 January 2025 (UTC)[reply]
My thinking regarding "we need to examine others" is that if we were to reach a consensus to tban here, I would go about and look through the pages that saw edit warring identified in this report and either file new AE cases or take action in my capacity as an uninvolved admin.signed,Rosguilltalk16:16, 25 January 2025 (UTC)[reply]
I was also asked to comment here by Ekdalian. My reading is similar to that of Rosguill's, and I endorse a logged warning.Talk:Rajput is full ofad hominem that has absolutely no place in a collaborative environment. That other users have also engaged in personal commentary does not excuse Ekdalian's behavior. Ekdalian, your language in the diffs above is not appropriate: it is far too aggressive and far too personal. If you are unable to make your point withoutad hominem, you will find yourself prevented from editing contentious material. I am not endorsing a TBAN at this time only because I have a strong feeling we are not being presented a full picture here.Vanamonde93 (talk)18:00, 25 January 2025 (UTC)[reply]
A logged warning at the very least. Between the canvassing and thepersonal attacks in #8/#9, I am doubtful that Ekdalian should be editing in this area at all. If that doesn't happen here, I would assure you thatany more behavior like this would be very likely indeed to lead to that result.SeraphimbladeTalk to me01:23, 26 January 2025 (UTC)[reply]
It looks like at least a rough consensus here for a logged warning regarding behavior. Unless any uninvolved admin disagrees within the next day or so, I will close as such.SeraphimbladeTalk to me15:22, 29 January 2025 (UTC)[reply]
Alex 19041
This request may be declined without further action if insufficient or unclear information is provided in the "Request" section below. Requests may not exceed 500words and 20 diffs (not counting required information), except by permission of a reviewing administrator.
Request concerning Alex 19041
User who is submitting this request for enforcement
Statements must be made in separate sections. They may not exceed 500words 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 Alex 19041
I have been made aware of the rules and will follow them in the future - I hope this suffices as a statement as I don't think there is anything worth adding that hasn't been said already.
Update 25/01 And yes, i will leave this alone in the future and I have since this occured.
I won't comment on this further and I'm not sure what else I'm supposed to say and allegations of trying to wepaonise Wikipedia are laughable when this literally started wirh someone introducing factually wrong information to an important article. I will not edit in that space anymore but I'm very unhappy with the standards in that field.
@Valereee: No, I did not; you must browse through my subpages to find it. But even if it was on my main page, that would not imply they could post it online in response to extremists' pages for them to harass and threaten me, as they did.Est. 2021 (talk·contribs)12:40, 25 January 2025 (UTC)[reply]
@Valereee: Again: private or not, that does not imply they could post it online in response to extremists' pages for them to harass and threaten me, as they did. IBAN is the least I could request.Est. 2021 (talk·contribs)12:40, 25 January 2025 (UTC)[reply]
This section is to be edited only by uninvolved administrators. Comments by others will be moved to the sections above.
To recap what's already been said at the initial hearing this gotat ARBCOM, it has been identified that Alex19041 is not extended-confirmed, has now been made aware of the 30/500 editing restriction for PIA, has acknowledged that they should not make any edits to the topic, but has not quite acknowledged that they also should not make comments relating to the topic outside of article space. If they can acknowledge that, an IBAN would be unnecessary as they will not be engaging further with the discussion at-issue for some time. If they can't acknowledge that, we'd likely need to escalate to blocks, as there's no reason to expect the IBAN to be observed. Some concern was also raised that Est. 2021's replies to Alex 19041 included personal attacks, although it should be noted that Est. 2021 has made an effort to remove potentially-problematic statements from their prior comments at ARBCOM (sections on their talk page containing similar language have been removed entirely, which is within their purview on a user talk page).signed,Rosguilltalk16:25, 21 January 2025 (UTC)[reply]
(came here from the ill-fated ArbCom case request). I agree with Rosguill. Some assurance from Alex 19041 and from Est. 2021 that they will leave the problematic edits behind would be good.-- Deepfriedokra (talk)21:28, 21 January 2025 (UTC)[reply]
@Est. 2021:. I'm sorry to hear that you have experienced off Wiki harassment. It would be best to email off-Wiki evidence to the Arbitration Committee --arbcom-en wikimedia.org and to Trust and Safety-- cawikimedia.org-- Deepfriedokra (talk)15:31, 25 January 2025 (UTC)[reply]
@Alex 19041: Looks like you've again edited in this area after saying you would not. There are about 6,000,000 articles not in this contentious topic area. I'm beginning to doubt you are here to build the encyclopedia. I'm beginning to think you are here to weaponize Wikipedia in this conflict. Please respond in your own section. Thanks.-- Deepfriedokra (talk)00:29, 31 January 2025 (UTC)[reply]
I agree that the reported user needs to show some understanding that as a non-EC user, they need to leave thisCTOP aloneacross all namespaces. However, sanctions are for serious, ongoing problems, three unwelcome talk page posts made over the course of an hour does not strike me as sufficient cause for a formal iban. If there's more to it than that, it needs to be made clear, with diffs.BeeblebroxBeebletalks21:48, 21 January 2025 (UTC)[reply]
It doesn't look likeAlex 19041 has edited since the case started. Alex, if you are seeing this, you do need to come in here and respond. Ignoring this will not make it go away.Valereee (talk)15:33, 23 January 2025 (UTC)[reply]
@Alex 19041, so you now understand that you must leave this topic alone, everywhere on Wikipedia?
@Est. 2021, ugh on the twitter post. Alex, that's not cool, people actually get threats IRL. But Est. 2021, you have so thoroughly outed yourself that this isn't considered outing under our policies.Valereee (talk)12:19, 25 January 2025 (UTC)[reply]
I'm forced to agree. If you post your real identity anywhere on WP, that's your decision and it is public. Of course I also agree with what Deepfriedokra has said about letting the office know about it.BeeblebroxBeebletalks18:55, 25 January 2025 (UTC)[reply]
I agree that no policy is violating by attributing an edit to a publicly disclosed off-wiki identity. Also, as to the underlying dispute, @Est. 2021: Based onyour talkpage comment I'mwilling to believe that you were trying to avoid the exact error you wound up introducing, but, to be clear, youdid introduce a serious factual error to the lead of a heavily-viewed and deeply controversial article.AirshipJungleman29 is entirely correct that the plain reading ofOn 7 October 2023, Hamas-led militant groups launched a surprise attack on Israel, taking 251 captive, against which Israelis responded applying the controversial Hannibal Directive, resulting in the death of 1,195 Israelis and foreign nationals, among which 815 civilians is that Israel killed all 1,195. If, as you indicate on the talkpage, that misunderstanding is because English is not your first language, that's fine, but you need to be more careful, especially in restoring something that was already removed once. --Tamzin[cetacean needed](they|xe|🤷)19:17, 25 January 2025 (UTC)[reply]
I'm concerned thatAlex 19041 is refusing to continue discussing here and is continuing to edit in the topic. A topic ban seems silly since they're refusing to comply with an ECR restriction; both require voluntary compliance. I hate to suggest a p-block from article space, as they do seem to want to contribute productively in other areas, but I'm not sure what else to do if they're refusing to comply/discuss.Valereee (talk)19:34, 2 February 2025 (UTC)[reply]
This is beginning to look like a competence issue more than an intentional flouting of the rules. Based on the most recent statement[38] I would leave a final warning that making edits related to the Arab-Israeli conflict would be grounds for an immediate block.Vanamonde93 (talk)21:31, 2 February 2025 (UTC)[reply]
I thought I'd leave a comment. It looks like Alex 19041 hasn't participated here in a few weeks but they have come by a couple times to rewrite their only comment in this discussion. I left a note for them asking for them to post additional comments with recent signatures so we could see they are aware of the discussion here instead of making small changes to their existing remark.LizRead!Talk!06:56, 3 February 2025 (UTC)[reply]
Callmehelper
This request may be declined without further action if insufficient or unclear information is provided in the "Request" section below. Requests may not exceed 500words and 20 diffs (not counting required information), except by permission of a reviewing administrator.
Request concerning Callmehelper
User who is submitting this request for enforcement
19 January - Files a frivolous report against other editors, mislabels their edits as "vandalism" and then rudely responds to onlookers as also noted by Liz by saying "That's a very rude reply, Callmehelper."
21 January - Trying to get article on a non-notable subject created and not dropping theWP:STICK.
21 January - CastsWP:ASPERSIONS against the new page patrollers, and demeans them as "people those rejected are so much had biased opinions that I can't discuss."
Statements must be made in separate sections. They may not exceed 500words 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 Callmehelper
This is my side ;
1 Allegation : Yes, it was indeed a copyright violation. This was my first encounter to something like copyright violation. Which i just copy-paste of a paragraph from govt website. Then one senior editor tell me in my talk page about what copyright violation is and how that works, and it was my very healthy and learning session for me tbh. Please see the whole discussion, then it will exhibit a full picture. First conversion happened in my talk pageseethen little more conversations happened in his talk pagepls see And ultimately matter solved and i learnt by this conversations and after that i never did anything like copyright violation. I don't know why this issue is used here against me.
2nd Allegation : This is little complex and long problem. Although i explain it very deeply during AN/I. But i will cut it short. It was started very much before.Firstly someone tag me about this vandalism by saying that one editor try to manipulate some paragraph in that page then i got involved in this. I restored that paragraph but it was reverted by again that guy and it keep going for sometime, then i told them in his talk page but he just delete that talk without replying, then i go for article talk page and write all that issue but no one replied, then i go to two administrator personal talk page, one was busy and one told me that i should go for AN/I but here also i got no reply for 2 days. after all that someone replied that i should go for main article talk page, which i was already did. this was disappointing for me as i feel in a loop as in talk page no one replied. so i replied very rudely but it was more of a frustration for 4 days. But nevertheless, I apologise to that editor and that senior editor named Lez who told me about my rudeness, in next reply. Moreover i also apologise to that editor in his talk page onsame day.
3 Allegations : It was related to 2nd allegation. It was indeed a Vandalism, because after discussion done in that talk page[41] that editor was again removing all this , so i had to go to his talk page and said about this is Vandalism pls stop doing it but again that guy deleted my vandalism warning without replying to mesee , But ultimately that editor stopped doing vandalism in that page and it then remains restored after so my efforts for continuous 5 days. But i don't know how that respected complainer think that this is not vandalism? IT WAS VANDALISM.
4th & 5th Allegations : I am not aware about WP:Stick. Simply I make a draft and leave a (template submit) in my draft and then it goes for discussion. After so much long long conversations, it was finalized that the draft is still not acceptable as it lack Notability and i ultimately accept that and this conversation end in very light way.pls see
My Conclusion: I whenever make any statement in uncivil manner i never ever leave as it is without my apology. i apologise to those whenever i feel that i replied them in uncivil way. As i am not so english fluent, so i don't have much dictionaries of words, so ultimately some my words reflect a little rudeness, but it was never be my intention. so apologise to him immediately. Although i am new , but i am sure i will be adapt myself very soon about all the policies. I also work on myself perticularly about my choice of words. Those seniors who seen my choice of bad words should advice/warm me in my talk page instead of going direct complaining, as i seen such policy as [WP:don't bit the newcomers], as i never ignored any type of warning/advice or suggestions. This was my side. I will accept any kind of warning or ban after all. Thanks. Much Regards.
@Valereee sorry Sir. this one edit seems not vandl , but it was his consecutive 3 to 4 times continuous reversion, even after discussion happened in talk page where that editor don't participate but other unrelated senior editor did whom i tag for help. So i thought, he did revert again by neglecting talk page discussion , hence i restored that by calling stop Vandalism. Now when i see WP:Vandalism policy very closely, it really didn't say that continuous incorrect edits a vandalism, it was more of a Continuous disruptive editing. Apologise for my mistakes. I should give more time to understand WP policy. Thank you for letting know me Sir. Regards Sir.Callmehelper (talk)15:08, 25 January 2025 (UTC)moved to correct section, please comment only in your own sectionValereee (talk)[reply]
@Rosguill . Pls give your valuable time to understand whole matter, since you asked.
This is a month ago matter, when I edit many changes in that page fromHere tocurrent With citations. But @Ratnahastin changed all by saying i am pushing my POVhere , but it was according to me not POV, but a well known fact that Ambedkar regards as the chief architect of constitution of India with citations. so i revert and tell him that its not POV , citations are there which claim that that discription about ambedkaryou can see , He again revert by claiming same thing that i am POV pushingsee without explanation of the the sources that i provided. so i again revert by saying pls read citations also,see. After that He came to my talk page about this issue, pls see thisshort conversation. Then after some 1 or 2 day, other editor (who take action here about me ) revert it by saying no improvement neededneeded. So i revert by sayingthis but he again revert by saying solve your problem inmain article. I will talk about later in detail about whole main article issue which is totally different from here but here they don't question citations that i provided here, they just revert by saying POV pushing or not necessary. So i go to there talk page for talk aboutthe issue. but again stick with the linesolve your issue first on main article. After that i take article Page talk page fordiscussion. and revert his earlier reversion and tell him to discuss the issue intalk page But instead for talk , he preferred for block action action against me - here and where i told about whole issue then administrator decline my block and preferred to involve in talkpage see
Here matter remain quite silent for 1 month , but today again , @Ratnahastin revert it by saying discuss in talk page. but in talk page, no one talk about credibility of sources that i provided which is secondary, govt etc. so i revert today and reply to stick with the sources. That's the all matter of Bhim Jayanti page. Now let's talk about little Main articleB R Ambedkar page issue. Where the way lead was written, I thought need to be revised. so being that time a new not extended user, i take talk page discussion, but there @Ratnahastin came and give his opinion which is misleading, when I reply to him to correct your fact , he don't replyback. In that discussion both give wrong information, and once i corrected them they won't reply and just changed lead by claiming, we had discussion on talk page but in talk page matter won'tsolve After this whole discussion, they always try to impose me that we had discussion in main article about your claim and that was debunk , which is entirely different. They give wrong info , and when i informed about their error, they won't reply further and changed on theirWP:OR. see1 then i again fortalk page then theyrevised. This is whole issue. Whenever I edit anything on Ambedkar related based on what i read on the books or journals or articles, i try to write in that page for articles enrichement , but these editors just came click revert and call that by single line like POV pushing orpuffery or anything. they don't talk about theWP:RS that i provided. they should talk about how or which paragraph is unsourced or puffery or unacademic etc , but they never do. they just give their prejudice mind opinions. This is all about my side. i think i all that i want to say. Rest is on administrators. Thanks. Much Regards.Callmehelper (talk)20:45, 2 February 2025 (UTC)[reply]
Statement by Ratnahastin
@Rosguill: The above acknowledgements by Callmehelper seem nothing more than lip-service. He has resumed his page ownership and edit warring with multiple editors atAmbedkar Jayanti, even after being told months ago that he should avoid rehashing same debunked argument which was already addressed on the main article.[42] However, he is continuing that in violation ofWP:ONUS, and is still ignoringWP:BRD.[43] -Ratnahastin (talk)18:24, 2 February 2025 (UTC)[reply]
Statement by (username)
Result concerning Callmehelper
This section is to be edited only by uninvolved administrators. Comments by others will be moved to the sections above.
Callmehelper, I don't see howthis edit is vandalism? Simply being incorrect is not vandalism. Please read about what Wikipedia considers to beWP:VANDALISM. If after reading it you still don't understand the difference, you're going to need to stop using the term.Valereee (talk)12:32, 25 January 2025 (UTC)[reply]
I'm not a man. I know you may have been taught it's polite to use honorifics, but that isn't necessary on the English Wikipedia. No one will think you're rude if you don't call them sir/ma'am, and doing so risks calling women "sir".Valereee (talk)15:23, 25 January 2025 (UTC)[reply]
I think this report can be closed without further action. While the diffs highlighted in this report are subpar, Callmehelper has admitted their errors and resolved to do better.signed,Rosguilltalk 03:01, 2 February 2025 (UTC) Partially struck.signed,Rosguilltalk18:41, 2 February 2025 (UTC)[reply]
Ratnahastin, thank you for bringing these more recent diffs to my attention. I agree that the slow-motion edit warring is not appropriate.Callmehelper, can you please explain the reasoning behind your edits atAmbedkar Jayanti. From what I can see at that page, you appear to be slow-motion edit warring against the objections of Srijanx22 and Ratnahastin. Can you please address your edits there particularlythis edit today? The discussion on the talk page does not demonstrate a firm consensus one way or another, and Ratnahastin's comments indicate that this dispute is related to other discussions (which I have not investigated in detail but which,ceteris paribus, would indicate that there's even less support for your edit than what is indicated atTalk:Ambedkar Jayanti).signed,Rosguilltalk18:38, 2 February 2025 (UTC)[reply]
Callmehelper, the correct answer I was looking for would have been something along the lines of "I am sorry for edit warring,being right isn't enough". Further edits to that article should have been avoided until the matter was resolved on the talk page; if discussion with Ratnahastin was not heading towards consensus, you should have appealed to any number ofdispute resolution options.signed,Rosguilltalk20:59, 2 February 2025 (UTC)[reply]
AE updates (two party limit, balanced editing restriction, and thanks from ArbCom)
This post should probably go on the talk page, but I am posting here for visibility. InWP:PIA5, the Arbitration Committeehas decided tolimit all reports at AE to two parties: the filer and the reported party. To reiterate, this isnot limited to the PIA topic area. If additional editors are to be reported, separate AE reports must be opened for each. AE admins may waive this rule if the particular issue warrants doing so.
In the PIA area, abalanced editing restriction (shortcut:WP:BERWP:BER) has been added to your toolbox, as part ofthe standard set of restrictions. The details of the restriction can be found at the link, but the short version is it requires editors to make no more than a third of their edits in mainspace, draftspace, and their respective talk spaces in the PIA5 area. Editors subject to BER are also topic banned from PIA outside of those namespaces.
Finally, the Committee has unanimously decided toformally thank administrators for volunteering at AE, especially in the PIA topic area. Keep being awesome :)
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 500words and 20 diffs (not counting required information), except by permission of a reviewing administrator.
Request concerning TommyKirchhoff
User who is submitting this request for enforcement
Alerted about discretionary sanctions or contentious topics in the area of conflict, on[48] 30 January 2024 (see the system log linked to above).
Additional comments by editor filing complaint
Aboutgangsters: I understand where he is coming from. We're giving the lie to everything he stands for. Perhaps I should not speculate about his motivation, but this is a token that I feel some pity for his lost cause. I'm not heartless, but this is not about showing mercy, but about affirming mainstream medical knowledge. It's about knowledge, not about compassion.tgeorgescu (talk)23:45, 30 January 2025 (UTC)[reply]
Notification of the user against whom enforcement is requested
Statements must be made in separate sections. They may not exceed 500words 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 TommyKirchhoff
I removed a dubious reference to quackerywatch.org, and its associated text in the article. Within four minutes, Hemiauchenia reverted my edit citing SKYISBLUE, which merits no logic. They said, "a non-explicitly medical source is okay but not ideal." Was that an apology? I thanked them, and reverted.I added a crucial addition to the first paragraph from the page's first citation. Five minutes later, Tgeorgescu reverted my revert. The bad guys were up in reverts: their two reverts to my one. They started the editing war. I thanked Tgeorge, reverted, and began adding a credible citation that reinforced appropriately the text I added.Just 13 minutes later, Ixocactus reverted me again. That's three reverts from the bad guys who are trolling this page mercilessly. Ixocactus told me I should gain consensus on the talk page; but I had reviewed the talk page many times, and these gangsters belittle, harass, name call, and insult anyone who tries to change this page. So I reverted again, knowing what would happen, and hoping to call attention to this issue.Nine minutes later, TgeorgeSCU reverted my revert a second time. That's badguys: 4, Tommy: 3. The badguys started the editing war over my removal of a terrible, offensive, non-scientific reference. So I reverted it again.Just three minutes later, Tryptofish reverted my revert. Badguys: 5, Tommy: 4.I added my credible reference to reinforce my addition text, and I was blocked.https://pmc.ncbi.nlm.nih.gov/articles/PMC9844554/I am not the bad guy here. And I have many more credible references to add to this page. I simply skipped the Talk page because there is no talking to the bad guys. I could only be BOLD.
Statement by Tryptofish
The year in this filing should be corrected 2024→2025.
Just after I posted that, a 4th revert, despite previous ew warnings on user talk, so that should be an unambiguous block in any case. --Tryptofish (talk)20:38, 30 January 2025 (UTC)[reply]
He has gotten a page block for edit warring, but has subsequently posted this at the article talk page:[50]. (I guess that makes me a gangster.) It seems to me that the continuing lack of self-awareness, and the stated intention to resume edit warring when the block is over, call for something further from AE. --Tryptofish (talk)21:05, 30 January 2025 (UTC)[reply]
Statement by (username)
Result concerning TommyKirchhoff
This section is to be edited only by uninvolved administrators. Comments by others will be moved to the sections above.
TommyKirchhoff, I think it would be helpful if you commented here. If you think a strong belief that you're right justifies edit warring, I don't believe editing in contentious topic areas is a good fit for you. The talk page certainly is where to go if you need to discuss a proposed edit and the sources backing it, but namecalling while doing so is similarly not acceptable. If those issues can be resolved, that's one thing, but if we can expect more of the same, then you will probably just need to be topic banned.SeraphimbladeTalk to me21:36, 30 January 2025 (UTC)[reply]
Given the response here, I would support a topic ban from the ARBCAM topic area. If TommyKirchhoff sees this as some contest between him and "bad guys", this is never going to end well.SeraphimbladeTalk to me22:00, 30 January 2025 (UTC)[reply]
This request may be declined without further action if insufficient or unclear information is provided in the "Request" section below. Requests may not exceed 500words and 20 diffs (not counting required information), except by permission of a reviewing administrator.
Request concerning Ecpiandy
User who is submitting this request for enforcement
Statements must be made in separate sections. They may not exceed 500words 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 Ecpiandy
Yes I have been updating the content to reflect the new article title I have not been doing anything controversial. If you want to ban me then fine, I've been an editor for a long time all I want to do is improve the encyclopedia.Ecpiandy (talk)02:49, 2 February 2025 (UTC)[reply]
Result concerning Ecpiandy
This section is to be edited only by uninvolved administrators. Comments by others will be moved to the sections above.
Ecpiandy, a topic ban does not mean that you may not make controversial edits in the topic area. It means you may not makeany edits in the topic area at all. After repeated warnings, if you don't understand that, I don't see any outcome but an indefinite block as you clearly are either unwilling or unable to abide by the restriction.SeraphimbladeTalk to me03:50, 2 February 2025 (UTC)[reply]
I don't think this editor understands that a topic ban covers all edits regarding a subject in all areas of the project. Unfortunately, the evidence is strong here that either Ecpiandy either doesn't understand topic bans or is unwilling to abide by Wikipedia guidelines. As a longtime editor, either one of these scenarios is unfortunate.LizRead!Talk!07:27, 2 February 2025 (UTC)[reply]
I agree with Liz and Seraphimblade. I would be inclined to show clemency if the offending edits were all truly controversy-free improvements like fixing grammar, but as Seraphimblade identifies they also include edits to material that has been the subject of extensive disputes, and has been repeated several times. If there were any indication fromEcpiandy that they intend to follow community rules going forward a shorter sanction could be justified on the basis of a long history productive edits elsewhere, but their responses here do not provide room for this possibility.signed,Rosguilltalk17:02, 2 February 2025 (UTC)[reply]
As a temporary matter pending resolution of this enforcement request, I've blocked Ecpiandy from editing articles for continuing to violate the topic ban.SilverLocust💬17:27, 2 February 2025 (UTC)[reply]
Boksi
This request may be declined without further action if insufficient or unclear information is provided in the "Request" section below. Requests may not exceed 500words and 20 diffs (not counting required information), except by permission of a reviewing administrator.
Request concerning Boksi
User who is submitting this request for enforcement
18:33, January 15, 2025 Restored article. At the time of their revert, there wasconsensus that the article should be merged. Their edit summary "consensus takes time to achieve" indicated they were aware of this discussion but chose not to participate.
Statements must be made in separate sections. They may not exceed 500words and 20 diffs, except by permission of a reviewing administrator. Administrators may remove or shorten noncompliant statements. Disruptive contributions may result in blocks.
This section is to be edited only by uninvolved administrators. Comments by others will be moved to the sections above.
I am unimpressed by the repeated reverts with no talk page engagement, and also by the claim of reverting a TBAN violation that in fact had occurred before the TBAN was enacted. I would like to hear from Boksi before deciding what to do.Vanamonde93 (talk)17:50, 2 February 2025 (UTC)[reply]
Arbitration enforcement action appeal by Taha Danesh
Procedural notes: Per therules 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 sectionsbut 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 (seeWP:UNINVOLVED).
Hello, I have been blocked for one week, apparently for engaging in edit warring. I would like to understand how this block is justified when I have not received any edit warring warnings—not a single one—in at least a month. I repeat,I have not received any warnings during this time. Moreover, on which page did this alleged edit warring occur? This situation feels particularly unfair. NO WARNING AT ALL. NOT EVEN ONE BEFORE THIS BLOCK IN THE PAST MONTH. I believe this block is unfair, given the circumstances. Thank you for your time and understanding.
The links mentioned for my warnings, some of which are more than two years old from when I first started editing, are unrelated to the current reason for my block. None of these warnings are relevant to my current status. I have not received any warnings for the pages you mentioned, except for Ebrahim Raisi, where the discussion was resolved by the page being restricted for a day. That was weeks ago, or possibly more than a month ago. For all the other pages, I have not been warned. Therefore, I believe this block is unfair. I have never been recognized as an edit warrior in any official statements, and I deny that claim, especially considering that I haven’t received any warnings. I have not received any warning about these cases, either from an admin or any user. I checked the Raisi page, and there were no edit warring warnings on my talk page. You can check the history of my talk page here: [User_talk:Taha_Danesh History]. In the past month, I have not received any warnings—neither for edit warring nor any other matter. I believe this block is unjustifiable. Taha Danesh (talk) 22:57, 2 February 2025 (UTC)
I was really,really glad that Voorts acted as quickly as they did and thereby prevented yet another round of endless discussions about ethnicity. Schools in Iraq teach that the great chemistJabir ibn Hayyan was an Arab, while schools in Iran teach that he was Iranian, and so we have a protected WP page. I was somewhat surprised that this should fall underWP:CT/IRP, but it's a welcome precedence.
I think a 0RR restriction might set them up for failure. I like the enthusiasm of this editor (compiling the list of sources they didhere is no easy feat), and a topic ban may do them more good in terms of getting another chance to learn the ropes. I do however think that their behavior is very likely to reoccur after the block expires, so an extra sanction might be a good idea.☿ Apaugasma (talk☉)23:05, 2 February 2025 (UTC)[reply]
Statement by (involved editor 2)
Discussion among uninvolved editors about the appeal by Taha Danesh
Statements must be made in separate sections. They may not exceed 500words 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 Taha Danesh
This section is to be edited only by uninvolved administrators. Comments by others will be moved to the sections above.
Decline - This should have been left for a patrolling admin to decline, as now that it's here it is evidence of further battleground behavior and a rather shocking sense of entitlement on Taha Danesh's part. Not only is it clear-cut edit warring in a contentious topic, it's primarily about infobox/lead nationality details, so irrespective of whoever is "right" in the underlying dispute, it's sloppy article writing. I don't like imposing extra sanctions in response to appeals, so if Taha Danesh is able to avoid doubling down I think this can be closed as declined. But the behavior displayed thus far is consistent with what gets people topic-banned indefinitely.signed,Rosguilltalk22:53, 2 February 2025 (UTC)[reply]
To be clearTaha Danesh, warnings are not issued on a per-article or per-dispute basis: once you are warned about a behavior (especially something as fundamental as edit warring), you are expected to observe these rules across all articles, and especially those that fall within contentious topics (as these do). The level of edit warring you've engaged in across multiple articles is the kind of thing people can get blocked for withzero warnings. Your attitude from here on out needs to be about staying on your best behavior, not acting like you are entitled to receive a warning on every distinct question. I would recommend that while blocked you go back through the warnings you have received and carefully read through the policies they are linked tosigned,Rosguilltalk23:11, 2 February 2025 (UTC)[reply]
Decline I believe that I am uninvolved, although I did make a comment atWP:BLPN recently suggesting a reliable source about Sistani's citizenship and birthplace. I have never edited that article or the others, or interacted with this editor to my recollection. This editor has the mistaken notion that repeated, regular warnings about edit warring are required regarding each individual article. That's completely false. I am in full agreement withRosguill on this matter. Roughly 15 years ago when I was a newbie, an administrator gave me a single gentle caution about edit warring and I have avoided edit warring scrupulously ever since. This editor should take the same approach when their block expires.Cullen328 (talk)01:45, 3 February 2025 (UTC)[reply]
Akshaypatill
This request may be declined without further action if insufficient or unclear information is provided in the "Request" section below. Requests may not exceed 500words and 20 diffs (not counting required information), except by permission of a reviewing administrator.
Request concerning Akshaypatill
User who is submitting this request for enforcement
Statements must be made in separate sections. They may not exceed 500words 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 Akshaypatill
I am one of the principle author of the page. The part which is removed by these editors is a long standing piece in the article and has been part of the article as long as I remember and it could be easily more than 4-5 years. It is also sourced to a reputed and reliable scholar of the subject.
And to get this long standing version down, the so called discussion on the talk page involves one editor @Mahusha sourcing some unknown unreliable author and a unverified YouTube video without any review and other editor @Ratnahastin kind of saying "Okay, delete it" without questioning the reliability and authenticity of the sources. This is not what we call a discussion, especially when the piece in question is long standing and is well sourced. This isn't the kind of consensus which is expected here. This isn't voting. The onus is on the editors who want remove it. Sarkar is very reputable historian and scholar. We need reputable and reliable sources by actual historians to argue his findings.
Though, I agree that I made a mistake. I was absent here for a long time and forgot that the page is 1RR protected. I posted my argument on talk page though. I am sorry for the mistake.Akshaypatill (talk)17:49, 3 February 2025 (UTC)[reply]
Statement by (username)
Result concerning Akshaypatill
This section is to be edited only by uninvolved administrators. Comments by others will be moved to the sections above.
This request may be declined without further action if insufficient or unclear information is provided in the "Request" section below. Requests may not exceed 500words and 20 diffs (not counting required information), except by permission of a reviewing administrator.
Request concerning Toa Nidhiki05
User who is submitting this request for enforcement
Diffs of edits that violate this sanction or remedy, and an explanationhow these edits violate it
Toa is continuing the same behaviour that got them TBANned from American politics in 2022, with the exact same MO in what appears to be aWP:CPUSH. I'm about to be accused of venue shopping since the admins let the ANI go stale, but there was still a general consensus this should have been an AE posting and Toa seems to be continuing the behaviour as if nothing happened. A link to that discussion can be foundhere. I highly recommend reading the whole thing for anyone who is patient enough, because Toa repeats the exact behaviour he's accused of in the ANI.
I'm not going to respond to any direct accusations from Toa, but please consider verifying any claims they make about other editors. That was a bit of an issue at the ANI.
diff Toa insisted that a change could not be made, citing prior consensus, and linked three posts which do not show prior consensus. Toa refused to provide any evidence of a prior consensus.
diff Toa tried in the ANI to get around providing any evidence of a prior consensus, when they finally providedanything they called the consensus they linked fundamentally flawed. This claim doesn't stand up to scrutiny (diff)
diff Added a source which failed verification, then removed the failed verification tag. Attempts to engage Toa discussing this went wholly unanswered (diff), though in response theyWP:POINT added a ton of failed verification tags to the article (diff), then started a new discussion thread aboutthat (link). Many of those sources did not fail verification, and they've refused to engage with any editors around clarifications to their standards for inclusion, despite being repeatedly asked (diff).
diff During the RFC, over and over asked for academic sources then wholly ignored them when they were provided, insisting they'd never been put forward and "nothing new" was presented, again pointing to the mythical previous consensus (diff), which in almost a month of back and forth on a talk page they haven't provided any evidence of.
This is exhausting. Toa has been guarding against the inclusion of "far right" onRepublican Party (United States) page forfourteen years (diff). Practically every uninvolved editor in the ANI saw the issue, so I'm just going to repeat the most pertinent line from the last WP:AE sanction:
There is seemingly no condition under which they would accept this edit resulting from the second dispute, regardless of any baseis in Wikipedia policies or guidelines, and which appears to already have a rough consensus in favor of it.
Toa appears to use a refusal to engage as a shield against edits they don't like. They shortcut the BRD process to hold the article in a status quo regardless of sourcing, consensus, or talk page discussions. Beyond just not engaging, Toa often starts parallel discussions which are related but exclude their behaviour, then point to that as evidence that they are attempting to engage in good faith (addendum: anexact behaviour they have repeated below).
Notification of the user against whom enforcement is requested
Statements must be made in separate sections. They may not exceed 500words 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 Toa Nidhiki05
There’s nothing I can say here that wasn’t already said in the AN/I thread, and I’m flying home today anyway, so I don’t have the time to. As in the AN/I, Warrenmck is simply lying, or giving half-truths - specifically, no, my topic ban was for embarrassing, disruptive behavior, which I have apologized for and haven’t repeated. What Wareenmck is upset about is acontent dispute. I profusely apologize that editors are going to have to read the AN/I thread, which was a phenomenal waste of time for everyone involved.
Fundamentally, Warrenmck is not being honest. Most uninvolved editors in the thread were confused or bewildered by the report. There was no consensus for an AE report - although Warrenmck repeatedly floated the idea, the thread expired due to inactivity. Warrenmck is lying about the page consensus; the talk page, and numerous other editors, have confirmed it to them. Warrenmck is lying about the source verification - you can literally go to the talk pageright now and find discussions I’m engaging in about the sources, includingreplacement sources to back up the claims in question.
Towards the end of the AN/I report, Warrenmck was even accusing other editors (specificallySpringee) of being part of a vast conspiracy to keep the content Warrenmck wants off the page. Meanwhile, Warrenmck’s own, proposed edits seem unlikely to be added: the RfC (which Warrenmck set up) for adding “far-right”, in particular, appears set to fail, with a 2:1 margin opposing it with at least two dozen participants so far.
This is more or less a clear case offorum shopping; the RfC isn’t going their way, the. AN/I didn’t work, so Warrenmck is going here instead. If Warrenmck’s response to not getting what they want is to just report people, they probably should reconsider their involvement in AP2 topics. Aboomerangtrouting may be warranted.ToaNidhiki0518:12, 3 February 2025 (UTC)[reply]
Statement by Simonm223
First off this is not forum shopping. The reason the AN/I filing was closed is because most of the parties to that discussion felt it was more appropriate to address complex behavioural issues such as CPUSH at AE. Second, as an example of CPUSH, Toa Nidhiki05 has been quite persistent in insisting that academic sources should be provided for including far-right in the list of Republican political ideologies. With that in mind I spent considerable time in Wikipedia Library finding academic sources that did just that. Unless I somehow missed it, to this day, Toa Nidhiki05 has never even acknowledged that those sources were found, let alone conceded the presence of multipleWP:BESTSOURCES would support some inclusion of the term far-right. In other words it appears they set the standard assuming nobody would go through the effort and, when I did go through the effort, they decided to just ignore those sources. This is exceptionally frustrating. Reading academic papers about the Republican Party isn't exactly my idea of fun and to have that effort just ignoredwhen it was asked for is frankly insulting.Simonm223 (talk)18:49, 3 February 2025 (UTC)[reply]
Oh and the claim Toa Nidhiki05 is making about the RFC is only based on their up-down vote-count and disregards strength of argument. Nobody except Toa Nidhiki05 is treating the RFC as decided.Simonm223 (talk)18:51, 3 February 2025 (UTC)[reply]
Statement by Nableezy
Repeatedly saying somebody is lying and being dishonest, here of all places, requires some sort of evidence or a block/ban for "casting aspersions". If somebody is accusing somebody else of lying they need to prove that, and in that case the liar should be given a block/ban or some sort, or be blocked/banned for the attack.nableezy -21:43, 3 February 2025 (UTC)[reply]
Statement by (username)
Result concerning Toa Nidhiki05
This section is to be edited only by uninvolved administrators. Comments by others will be moved to the sections above.
The division of discussion across various forums makes it a bit difficult to ascertain that I've read through all of the relevant arguments.Toa Nidhiki05, could you please point me to a summary of the bibliography you believe establishesthe majority of academic sources refer to the party as either center-right or right-wing, as well as brief comments regarding the bibliography compiled bySimonm223 and how they figure into your overall assessment of the literature?signed,Rosguilltalk21:40, 3 February 2025 (UTC)[reply]