Misplaced Pages

Latest revision as of 19:45, 22 January 2025

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

Important informationShortcuts WP:AE WP:ARE Please use this page only to: request administrative action against editors violating a remedy (not merely a principle) or an injunction in an Arbitration Committee decision, or a contentious topic restriction imposed by an administrator, request contentious topic restrictions against previously alerted editors who engage in misconduct in a topic area designated as a contentious topic, request page restrictions (e.g. revert restrictions) on pages that are being disrupted in topic areas designated as contentious topics, or appeal arbitration enforcement actions (including contentious topic restrictions) to uninvolved administrators. For all other problems, including content disagreements or the enforcement of community-imposed sanctions, please use the other fora described in the dispute resolution process. To appeal Arbitration Committee decisions, please use the clarification and amendment noticeboard. Only autoconfirmed users may file enforcement requests here; requests filed by IPs or accounts less than four days old or with less than 10 edits will be removed. All users are welcome to comment on requests except where doing so would violate an active restriction (such as an extended-confirmed restriction). If you make an enforcement request or comment on a request, your own conduct may be examined as well, and you may be sanctioned for it. Enforcement requests and statements in response to them may not exceed 500 words and 20 diffs, except by permission of a reviewing administrator. (Word Count Tool) Statements must be made in separate sections. Non-compliant contributions may be removed or shortened by administrators. Disruptive contributions such as personal attacks, or groundless or vexatious complaints, may result in blocks or other sanctions. To make an enforcement request, click on the link above this box and supply all required information. Incomplete requests may be ignored. Requests reporting diffs older than one week may be declined as stale. To appeal a contentious topic restriction or other enforcement decision, please create a new section and use the template {{Arbitration enforcement appeal}}. Appeals and administrator modifications of contentious topics restrictions The Arbitration Committee procedures relating to modifications of contentious topic restrictions state the following: All contentious topic restrictions (and logged warnings) may be appealed. Only the restricted editor may appeal an editor restriction. Any editor may appeal a page restriction. The appeal process has three possible stages. An editor appealing a restriction may: ask the administrator who first made the contentious topic restrictions (the "enforcing administrator") to reconsider their original decision; request review at the arbitration enforcement noticeboard ("AE") or at the administrators' noticeboard ("AN"); and submit a request for amendment ("ARCA"). If the editor is blocked, the appeal may be made by email. Appeals submitted at AE or AN must be submitted using the applicable template. A rough consensus of administrators at AE or editors at AN may specify a period of up to one year during which no appeals (other than an appeal to ARCA) may be submitted. Changing or revoking a contentious topic restriction An administrator may only modify or revoke a contentious topic restriction if a formal appeal is successful or if one of the following exceptions applies: The administrator who originally imposed the contentious topic restriction (the "enforcing administrator") affirmatively consents to the change, or is no longer an administrator; or The contentious topic restriction was imposed (or last renewed) more than a year ago and: the restriction was imposed by a single administrator, or the restriction was an indefinite block. A formal appeal is successful only if one of the following agrees with revoking or changing the contentious topic restriction: a clear consensus of uninvolved administrators at AE, a clear consensus of uninvolved editors at AN, a majority of the Arbitration Committee, acting through a motion at ARCA. Any administrator who revokes or changes a contentious topic restriction out of process (i.e. without the above conditions being met) may, at the discretion of the Arbitration Committee, be desysopped. Standard of review On community review Uninvolved administrators at the arbitration enforcement noticeboard ("AE") and uninvolved editors at the administrators' noticeboard ("AN") should revoke or modify a contentious topic restriction on appeal if: the action was inconsistent with the contentious topics procedure or applicable policy (i.e. the action was out of process), the action was not reasonably necessary to prevent damage or disruption when first imposed, or the action is no longer reasonably necessary to prevent damage or disruption. On Arbitration Committee review Arbitrators hearing an appeal at a request for amendment ("ARCA") will generally overturn a contentious topic restriction only if: the action was inconsistent with the contentious topics procedure or applicable policy (i.e. the action was out of process), the action represents an unreasonable exercise of administrative enforcement discretion, or compelling circumstances warrant the full Committee's action. The administrator may indicate consent at any time before, during, or after imposition of the restriction. This criterion does not apply if the original action was imposed as a result of rough consensus at the arbitration enforcement noticeboard, as there would be no single enforcing administrator. Appeals and administrator modifications of non-contentious topics sanctions The Arbitration Committee procedures relating to modifications and appeals state: Appeals by sanctioned editors Appeals may be made only by the editor under sanction and only for a currently active sanction. Requests for modification of page restrictions may be made by any editor. The process has three possible stages (see "Important notes" below). The editor may: ask the enforcing administrator to reconsider their original decision; request review at the arbitration enforcement noticeboard ("AE") or at the administrators’ noticeboard ("AN"); and submit a request for amendment at the amendment requests page ("ARCA"). If the editor is blocked, the appeal may be made by email through Special:EmailUser/Arbitration Committee (or, if email access is revoked, to arbcom-enwikimedia.org). Modifications by administrators No administrator may modify or remove a sanction placed by another administrator without: the explicit prior affirmative consent of the enforcing administrator; or prior affirmative agreement for the modification at (a) AE or (b) AN or (c) ARCA (see "Important notes" below). Administrators modifying sanctions out of process may at the discretion of the committee be desysopped. Nothing in this section prevents an administrator from replacing an existing sanction issued by another administrator with a new sanction if fresh misconduct has taken place after the existing sanction was applied. Administrators are free to modify sanctions placed by former administrators – that is, editors who do not have the administrator permission enabled (due to a temporary or permanent relinquishment or desysop) – without regard to the requirements of this section. If an administrator modifies a sanction placed by a former administrator, the administrator who made the modification becomes the "enforcing administrator". If a former administrator regains the tools, the provisions of this section again apply to their unmodified enforcement actions. Important notes: For a request to succeed, either (i) the clear and substantial consensus of (a) uninvolved administrators at AE or (b) uninvolved editors at AN or (ii) a passing motion of arbitrators at ARCA is required. If consensus at AE or AN is unclear, the status quo prevails. While asking the enforcing administrator and seeking reviews at AN or AE are not mandatory prior to seeking a decision from the committee, once the committee has reviewed a request, further substantive review at any forum is barred. The sole exception is editors under an active sanction who may still request an easing or removal of the sanction on the grounds that said sanction is no longer needed, but such requests may only be made once every six months, or whatever longer period the committee may specify. These provisions apply only to contentious topic restrictions placed by administrators and to blocks placed by administrators to enforce arbitration case decisions. They do not apply to sanctions directly authorized by the committee, and enacted either by arbitrators or by arbitration clerks, or to special functionary blocks of whatever nature. All actions designated as arbitration enforcement actions, including those alleged to be out of process or against existing policy, must first be appealed following arbitration enforcement procedures to establish if such enforcement is inappropriate before the action may be reversed or formally discussed at another venue. Information for administrators processing requests Thank you for participating in this area. AE works best if there are a variety of admins bringing their expertise to each case. There is no expectation to comment on every case, and the Arbitration Committee (ArbCom) thanks all admins for whatever time they can give. A couple of reminders: Before commenting, please familiarise yourself with the referenced ArbCom case. Please also read all the evidence (including diffs) presented in the AE request. When a request widens to include editors beyond the initial request, these editors must be notified and the notifications recorded in the same way as for the initial editor against whom sanctions were requested. Where some part of the outcome is clear, a partial close may be implemented and noted as "Result concerning X". Enforcement measures in arbitration cases should be construed liberally to protect Misplaced Pages 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 Misplaced Pages policies and guidelines; you may use administrative discretion to resolve it. More than one side in a dispute may have ArbCom conduct rulings applicable to them. Please ensure these are investigated. Closing a thread: Once an issue is resolved, enclose it between {{hat}} and {{hab}} tags. A bot should archive it in 7 days. Please consider referring the case to ARCA if the outcome is a recommendation to do so or the issue regards administrator conduct. You can use the templates {{uw-aeblock}} (for blocks) or {{AE sanction}} (for other contentious topic restrictions) to give notice of sanctions on user talk pages. Please log sanctions in the Arbitration enforcement log. Thanks again for helping. If you have any questions, please post on the talk page.

שלומית ליר

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

Request concerning שלומית ליר

User who is submitting this request for enforcement

Smallangryplanet (talk · contribs · deleted contribs · logs · filter log · block user · block log) 17:24, 11 January 2025 (UTC)

User against whom enforcement is requested

שלומית ליר (talk · contribs · deleted contribs · logs · filter log · block user · block log)

Search CT alerts: in user talk history • in system log

Sanction or remedy to be enforced

WP:ARBPIA

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

ShlomitLir (שלומית ליר) created their account back in 2014. The breakdown of their edits is as follows:

• 2014 to 2016: no edits.
• 2017 to 2019: 1 edit per year. None related to PIA.
• 2022: 7 edits. Mostly in their userspace.
• 2023: 21 edits. Again, mostly in their userspace. Made two edits in the talk page of Palestinian genocide accusation complaining about its content and calling it “blatant pro-Hamas propaganda”.
• 2024: Started editing after a 10 month break at the end of October.
  • Made 51 edits in October and 81 edits in November (copyedits, adding links, minor edits).
  • In December, that number rose up to almost 400, including 116 in December 6 alone and 98 in December 7. Became ECR that day.
  • Immediately switched to editing in PIA, namely in the Battle of Sderot article where they changed the infobox picture with an unclear image with a dubious caption, and removed a template without providing a reason why.
  • They also edited the Use of human shields by Hamas article, adding another image with a caption not supported by the source (replaced by yet another image with a contextless caption when the previous image was removed) and WP:UNDUE content in the lead.
  • they also voted in the second AfD for Calls 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 across this article authored by them on Ynet, once again complaining about what they perceive as an anti Israeli bias on Misplaced Pages. They have also authored a report for the World Jewish Congress covering the same topic. The report can be seen in full here. I think that someone with this clear POV agenda shouldn't be near the topic.

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

• Alerted about discretionary sanctions or contentious topics in the area of conflict, on 2023-04-05 and re-iterated on 2024-11-25 (see the system log linked to above).
• Previously given a discretionary sanction or contentious topic restriction or warned for conduct in the area of conflict on 2024-12-18 by Femke (talk · contribs · blocks · protections · deletions · page moves · rights · RfA).

Additional comments by editor filing complaint

Adding some additional comments on 2025-01-16: On top of POV issues, the user has a number of tweets that appear to be a clear admission of gaming, implicit canvassing, creating and sharing lists of potential "most biased articles", and clearly calling for specific edits. They've also been cited as coordinating an off-wiki coordination hub for editing Misplaced Pages. If this - combined with the tweets, the forms, the op-ed and the report to the WJC, all under this user's name (that they also use to edit Misplaced Pages - this is not outing) isn't a clear cut case of canvassing, I don't know what is. Smallangryplanet (talk) 20:00, 16 January 2025 (UTC)

Adding some more comments on 2025-01-22: The user in question says that they have been on[REDACTED] for years – and so surely aware of what does and does not count as canvassing. As recently as last month they were advising users on Hebrew Misplaced Pages as to how best to get their edit counts up, as well as promoting the "most biased articles" survey I've already mentioned. I understand that we are always meant to WP:AGF, but we are looking at a situation in which a user (1) has extensive experience with Misplaced Pages and (2) is encouraging people, subtly and not so subtly to do things that are against our policies. Smallangryplanet (talk) 19:45, 22 January 2025 (UTC)

Notification of the user against whom enforcement is requested

Notification diff

Discussion concerning שלומית ליר

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

Statement by שלומית ליר

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)

I was given clarification from an admin regarding my concerns and will now be drafting a response. Thank you for your patience. שלומית ליר (talk) 21:19, 18 January 2025 (UTC)

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 Misplaced Pages’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 Misplaced Pages. (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)

Statement by Thebiguglyalien

This is the first ARBPIA report since the proposed decision was posted at ARBPIA5 and it's specifically a matter of POV pushing, responding admins should be aware of the "AE topic bans" remedy. The committee is discussing whether to implement a remedy stating that admins at AE are "empowered and encouraged to consider a topic ban" purely for biased editing. So far, the argument against is that it's redundant because AE admins are already supposed to do this. Thebiguglyalien (talk) 05:39, 12 January 2025 (UTC) https://en.wikipedia.org/Wikipedia:Wikipedia_Signpost/2024-03-29/Special_report

Statement by Selfstudier

To the extent that it is relevant, the WJC report was discussed at Misplaced Pages:Misplaced Pages Signpost/2024-03-29/Special report. Selfstudier (talk) 11:25, 12 January 2025 (UTC)

Statement by starship.paint (2)

I would to like to raise this 9 December 2024 edit at Battle of Sderot, where there had been an existing unsourced paragraph (On the morning of October 7, a tour minibus...) that שלומית ליר added a reference to (archive 1 / archive 2) from the Israeli 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 same YouTube 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)

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 a pattern of edits could be in violation, even if no particular edit is in violation.

In principle, such a pattern of edits could violate the UCoC 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. — xDanielx /_C\ 03:11, 13 January 2025 (UTC)

Statement by Hemiauchenia

This user has engaged in off-wiki canvassing regarding the IP conflict. Take the following recent tweet from the 12 January 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 @Misplaced Pages 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.

Along with this is a screenshot of the current AfD Misplaced Pages:Articles for deletion/Palestinian suicide attacks. People are of course allowed to be caustic about Misplaced Pages off-wiki, but calling out a specific AfD with highly charged rhetoric, essentially inciting canvassing seems out of line. Hemiauchenia (talk) 02:05, 16 January 2025 (UTC)

For those concerned that this might be outing, שלומית ליר is very open about their real life identity on their userpage. See (archived). If you reveal your real identity on Misplaced Pages, your tweets about Misplaced Pages on your Twitter account connected to your real-life identity are fair game to mention. There's also reverse confirmation in this tweet . Hemiauchenia (talk) 02:46, 16 January 2025 (UTC)

Statement by Cdjp1

As we seem to be ok to pull evidence from the statements of the editor in question, they have also commented more recently about running interference on Misplaced Pages (archive) in response to a question of if Misplaced Pages can be "saved". -- Cdjp1 (talk) 23:22, 16 January 2025 (UTC)

Statement by Sean.hoyland

It has been several days. Perhaps שלומית ליר could clarify whether their belief about the way Misplaced Pages 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)

Statement by Vice regent

I'm satisfied by שלומית ליר's above explanation regarding canvassing. People with bad canvassing intentions don't reveal their identity. VR _{(Please ping on reply)} 04:19, 22 January 2025 (UTC)

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 like this 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)

  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)

  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)

  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 of WP:CANVAS I would consider something more stringent. Vanamonde93 (talk) 17:39, 16 January 2025 (UTC)

• While I understand Vanamonde93'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. Misplaced Pages:Contentious topics#Guidance for editors places an obligation to Within contentious topics,… edit carefully and constructively… and… adhere to the purposes of Misplaced Pages. The linked page provides that Misplaced Pages 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 is only 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 making only one-sided edits will simply not be taking the necessary steps to ensure that the whole 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)

Assessing the topic area contributions of the respondent (שלומית ליר) since they became extended-confirmed at 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:

• Adding a citation for a claim that Hamas terrorists shot dead a group of Israeli tourists.
• Replacing map with a photograph of victims of violence.
• Removing an outdated maintenance tag which was perhaps casting doubt on the relevant section, Massacre of pensioners, and again.
• Adding specification to claims of the use of human shield (specifying who has made the claims), therefore giving greater weight to the claims, in a context where the claims were already described at considerable length; adding another reference to that claim; and adding another.
• Adding an image contentiously captioned 'Weapons Found in a Mosque', then again Rockets hidden at a house, both to the first line of the article.
• Adding, without sufficient context, an assertion that a philosopher has determined that one side of the conflict is culpable and expanding other coverage of culpability of that side.
• On the talk pages, there has been a tinge 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.
• There are then edits to LGBTQ rights in the State of Palestine: inserting a reference to execution into the first sentence of the lead; adding more references to news coverage of executions of LGBT+ people by the other side of the conflict. At Houthi movement, there is then an expansion, again of the article lead, to add references to terrorist attacks (with follow-up).

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)

@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 to WP:NPOV. Even if each edit in isolation is insufficient for sanctioning, taken as 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 the percentage 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 about Misplaced Pages:Advocacy. arcticocean ■ 08:40, 13 January 2025 (UTC)

• The offwiki canvassing is a problem...שלומית ליר, you're fairly inexperienced here. Were you aware WP:canvassing is not allowed? Valereee (talk) 12:59, 16 January 2025 (UTC)

  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)

• I take it that per Barkeep49's brief oversighting of potentially-sensitive content in this report (Special:Diff/1269845558), and then restoration of the same (Special:Diff/1269848988), concerns of outing have been investigated and the report can proceed on its merits? _signed, Rosguill 19:14, 16 January 2025 (UTC)

  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)

• 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 how best 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 Misplaced Pages 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. Seraphimblade 16:08, 22 January 2025 (UTC)

  +1 Valereee (talk) 18:13, 22 January 2025 (UTC)

Luganchanka

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

Request concerning Luganchanka

User who is submitting this request for enforcement

Hemiauchenia (talk · contribs · deleted contribs · logs · filter log · block user · block log) 20:26, 12 January 2025 (UTC)

User against whom enforcement is requested

Luganchanka (talk · contribs · deleted contribs · logs · filter log · block user · block log)

Search CT alerts: in user talk history • in system log

Sanction or remedy to be enforced

Misplaced Pages:Requests for arbitration/Editing of Biographies of Living Persons

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

1. 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.

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

18:28, 12 January 2025 BLP CTOP warning given

Additional comments by editor filing complaint

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. Misplaced Pages: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: , which he subequently blanked 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 August Talk: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)

Luganchanka's response is disingenuous and misleading. Look at the Talk: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)

RfC opened Talk:Scott_Ritter#RfC:_Ritter's_sexual_sex_offenses_convictions. Hemiauchenia (talk) 16:01, 16 January 2025 (UTC)

Notification of the user against whom enforcement is requested

20:27, 12 January 2025

Discussion concerning Luganchanka

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

Statement by Luganchanka

The intro on the Scott 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 I WP: 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 Misplaced Pages editor.Luganchanka (talk) 20:40, 12 January 2025 (UTC)

Please see the Talk:Scott_Ritter, where there has been a clear consensus reached, on more than one occasion, and by senior[REDACTED] 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)

Thank you to @Valereee and @Red-tailed hawk for your feedback. If you see the Talk:Scott_Ritter, discussions - 14 August - Vandalism by removing all reference entirely to Ritter being a "Convicted Sex Offender" and First 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)

Thank you for this (nest), I really do appreciate your feedback and advice here!!Luganchanka (talk) 16:30, 16 January 2025 (UTC) (moved from admin-only section — Red-tailed hawk _(nest) 17:34, 16 January 2025 (UTC))

As per Rosguill's comments:

"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."

https://casetext.com/case/ritter-v-tuttle

Luganchanka (talk) 18:40, 16 January 2025 (UTC)

Statement by NatGertler

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, per WP: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)

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: whether you're correct or not, you were edit warring. I believe an indef block from the article and/or a temporary site block would be an appropriate sanction here. voorts (talk/contributions) 20:54, 12 January 2025 (UTC)

I've blocked the user for 48h for violating 3RR based on the report at WP:AN3.--Bbb23 (talk) 23:56, 12 January 2025 (UTC)

• @Luganchanka, edit-warring to 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 believe Rosguillwhiyou 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)

  @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 a WP:CIR issue.

  But even if you had 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 should ever edit war over. Valereee (talk) 18:14, 15 January 2025 (UTC)

• 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 from Scott Ritter seems appropriate. _signed, Rosguill 22:49, 14 January 2025 (UTC)

  I see RTH's point about the "First sentence" section in isolation. I'd note that the link to WP: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 of whitewash before writing this off as time-served. _signed, Rosguill 15:49, 16 January 2025 (UTC)

  That's fair; I'll strike the link. My point in including it was that, when conversations fragment, we sometimes get these sorts of chaotic incidents. — Red-tailed hawk _(nest) 15:54, 16 January 2025 (UTC)

  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, Rosguill 15:57, 16 January 2025 (UTC)

  I am not at all comforted by the fact that Luganchanka has proceeded to make Special:Diff/1269831044. The cited BBC source does not state masturbated and ejaculated on camera, saying only graphic sex act. As written, this is essentially another BLP violation, building a case that a ban from this topic is needed. _signed, Rosguill 16:53, 16 January 2025 (UTC)

  Having reviewed the other sources, reliable sources do confirm the masturbation claim (, ) but not ejaculation, which appears to be supported only by New 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, Rosguill 17:02, 16 January 2025 (UTC)

  The detail is in the record of Ritter 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)

  Seeing Special:Diff/1269853673 here and Special:Diff/1269853955, Special:Diff/1269845272 at Talk: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, Rosguill 18:47, 16 January 2025 (UTC)

  @Luganchanka:

  WP:BLPPRIMARY calls upon users to not use trial transcripts and other court records, or other public documents, to support assertions about a living person. There are some narrow exceptions (when primary-source material has been discussed by a reliable secondary source, it may be acceptable to rely on it to augment the secondary source), but adding material to the article not found in reliable secondary sources is... suboptimal at best under our biographies of living persons policy.

  — Red-tailed hawk _(nest) 02:27, 17 January 2025 (UTC)

• @Luganchanka: Would you please provide a direct link to the talk page section you are referring to when you say there has been a clear consensus reached, on more than one occasion, and by senior[REDACTED] editors regarding the lead? — Red-tailed hawk _(nest) 01:57, 15 January 2025 (UTC)

  @Luganchanka and Hemiauchenia:

  It does seem that the discussion at Talk: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, while There 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 was notification 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 got two 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. This NY Times piece, which is cited in the body of the article (but not the lead), does state that Ritter was convicted unlawful contact with minors and other charges in the state of PA (the PA statute is here; "unlawful contact with minors" is the verbatim name of the crime). When dealing with a sting operation, PA treats it as an 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 regarding mens rea and actus 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 is wise or optimal 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. A Request for Comment on the article's talk page for what the lead should look like is probably the best way to go forward here.

  — Red-tailed hawk _(nest) 15:27, 16 January 2025 (UTC)

  RTH, are you objecting to a p-block from the article? Valereee (talk) 13:35, 18 January 2025 (UTC)

  Ping to @Red-tailed hawk Valereee (talk) 18:14, 22 January 2025 (UTC)

• Luganchanka has been blocked for a week by User:ScottishFinnishRadish for BLP violations and personal attacks. Liz 18:38, 18 January 2025 (UTC)

  Just noting that this was a regular admin action and I wasn't aware this was before AE. ScottishFinnishRadish (talk) 18:42, 18 January 2025 (UTC)

  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, Rosguill 18:54, 18 January 2025 (UTC)

BabbleOnto

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

Request concerning BabbleOnto

User who is submitting this request for enforcement

ජපස (talk · contribs · deleted contribs · logs · filter log · block user · block log) 17:34, 13 January 2025 (UTC)

User against whom enforcement is requested

BabbleOnto (talk · contribs · deleted contribs · logs · filter log · block user · block log)

Search CT alerts: in user talk history • in system log

Sanction or remedy to be enforced

Misplaced Pages:Arbitration/Requests/Case/COVID-19#Contentious_topic_designation

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

1. 11 January 2025 Sealioning
2. 11 January 2025 Refusal to get the message
3. 11 January 2025 Personalizing an argument.
4. 11 January 2025 Railroading the discussion.

This is all after I warned them about WP:AE sanctions, and they dismissed my warning out of hand. Very nearly a WP:SPA on the subject. I see no reason to continue tolerating this kind of obstinate tendetiousness. Additional diffs available on request from admins, but looking at the user history should suffice to indicate the problem is obvious, I hope.

Diffs of previous relevant sanctions, if any

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

• Alerted about discretionary sanctions or contentious topics in the area of conflict, on 9 Dec 2024 (see the system log linked to above).

Additional comments by editor filing complaint

This is a WP:SPA with respect to the topic and their disruption surrounding it has been subject to at least one WP:FTN thread that remains active: Misplaced Pages:Fringe_theories/Noticeboard#Gain_of_function_research. The hope was that they would WP:DROPTHESTICK and move on from this, but it seems they either will not or cannot. jps (talk) 17:34, 13 January 2025 (UTC)

Notification of the user against whom enforcement is requested

diff

Discussion concerning BabbleOnto

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

Statement by BabbleOnto

I would first like to begin by point out the person filing this complaint is involved in the content disputes at issue. They have frequently left "warnings" which read more like threats on my talk page and others' talk pages for people who disagree with them. Nor would I be the first person who would they would get banned from this topic for disagreeing with them.

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've admitted when I was wrong, I've dropped arguments that were clarified to be wrong, I've tried to find compromise, at times begging people to provide their sources and work together. And when those editors refused 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 of having 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 that I'm not working with others. BabbleOnto (talk) 23:54, 13 January 2025 (UTC)

• Edited. BabbleOnto (talk) 23:56, 13 January 2025 (UTC)

• 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)

  • 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 to personally 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.

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 response ad 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)

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 I misquoted 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 ends here. 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 of WP:CPUSH with pure WP:IDONTHEARTHAT.

2. On this they say, now, that The 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 and WP: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 and You'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 to a basic failure in reading comprehension two 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 I said a material lie, and that I lied when said that quoted the article out of context. Pointing out 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. But WP: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 Misplaced Pages 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)

Statement by Objective3000

Just a quick aside to Valereee's aside: Contentious topics are a terrible place to learn.... Talk:COVID-19 lab leak theory currently has posts from 19 editors lacking the edits for extended confirmed. O3000, Ret. (talk) 20:38, 14 January 2025 (UTC)

@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)

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 are retracted. Those accusations are like their suggestion made in their statement in this filing. O3000, Ret. (talk) 12:11, 18 January 2025 (UTC)

Statement by JoelleJay

At the very least, can we get more admin involvement on the lab leak page so trolling like this doesn't disrupt things even more? JoelleJay (talk) 07:12, 15 January 2025 (UTC)

Statement by IntrepidContributor

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 , but it can also be on-wiki ().

One need only cross-reference names from Feb 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 . Our chief complainant is already preparing his next case , 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.

IntrepidContributor (talk) 14:46, 15 January 2025 (UTC)

Statement by TarnishedPath

Please see this edit where BabbleOnto edited Gain of function research restoring previously reverted content and WP:POVPUSH using a shit source after they'd been told by multiple other editors in discussions here and here 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 a WP: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. TarnishedPath 04:25, 18 January 2025 (UTC)

Noting the editor's continued behaviour at Talk:Gain-of-function research. Refer to Special:Diff/1270316266. TarnishedPath 01:53, 19 January 2025 (UTC)

and again at Special:Diff/1270346091 TarnishedPath 03:01, 19 January 2025 (UTC)

Statement by berchanhimez

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 behavior rather 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)

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 they could be a good contributor to this site, and absolutely could follow the PAGs. They have shown an ability to be courteous . 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 (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 admittedly WP:BITE) in that topic space (e.g. )

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)

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, particularly BabbleOnto 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, Rosguill 23:37, 13 January 2025 (UTC)

  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 at Talk: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 becomes WP: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 of Misplaced Pages: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, Rosguill 01:26, 14 January 2025 (UTC)

  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, Rosguill 21:47, 14 January 2025 (UTC)

• 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)

• 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)

  BabbleOnto's response understanding this as a suggestion to take a break from Misplaced Pages as a whole isn't quite what I was hoping to see. _signed, Rosguill 17:22, 19 January 2025 (UTC)

  @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.

  @Rosguill, I'd support a tban, but is AP2 enough? It seems like COVID and fringe science need to be included? Valereee (talk) 17:22, 19 January 2025 (UTC)

  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, Rosguill 17:56, 19 January 2025 (UTC)

  @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)

• I think BabbleOnto is actually getting the right idea. You do not have to agree 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, and move 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. Seraphimblade 14:05, 21 January 2025 (UTC)

  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 prove and 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 continuing during this case...I dunno. Valereee (talk) 14:20, 21 January 2025 (UTC)

  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). Seraphimblade 20:02, 21 January 2025 (UTC)

  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 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? Valereee (talk) 20:27, 21 January 2025 (UTC)

Marlarkey

DanielVizago

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

Request concerning DanielVizago

User who is submitting this request for enforcement

Schazjmd (talk · contribs · deleted contribs · logs · filter log · block user · block log) 23:23, 14 January 2025 (UTC)

User against whom enforcement is requested

DanielVizago (talk · contribs · deleted contribs · logs · filter log · block user · block log)

Search CT alerts: in user talk history • in system log

Sanction or remedy to be enforced

Misplaced Pages:Arbitration/Requests/Case/Gender_and_sexuality#Final_decision

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

1. 29 Dec 2024 Added Category:Misandry to a BLP, after CTOP notification and several talk page messages notifying DanielVizago that the category is not to be applied to articles about individuals (per category description, This category is for issues relating to misandry. It must not include articles about individuals, groups or media that are allegedly misandrist.);
2. 4 Jan 2025 and 5 Jan 2025 Removing sourced content from Misogyny that states misandry is not a major an issue as misogyny;
3. 5 Jan 2025 Changing content in Male privilege to emphasize misandry (reverted by another editor with edit summary rv, poorly sourced (sources supplemented by WP:OR and WP:SYNTH), earlier version was better, closer to sources);
4. 13 Jan 2025 Added "bimisandry" to Biphobia, citing 4 sources, none of which include that term;
5. 14 Jan 2025, weird edits adding Category:Female rapists with piped names to unrelated articles, then added those names directly to the category page;
6. 14 Jan 2025 restored the "bimisandry" edit to Biphobia, then added a 5th ref that includes the term but is just a blog; I left a 4th-level warning on talk page;
7. 14 Jan 2025 (after final warning) adds ] and ] to Hurtcore; those two individuals don't have articles and there is no mention in this article of their charges or convictions, even though the category solely consists of articles of female individuals who have been convicted of rape in a court of law.

Diffs of previous relevant sanctions, if any

• None

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

• I alerted them on 28 Dec 2024

Additional comments by editor filing complaint

Above diffs are all edits after the CTOP notification was provided. Before then, DanielVizago misapplied Category:Misandry to 46 articles, which is what caught my attention. Their attempts to add "bimisandry" to Biphobia started 16 Dec 2024. On 28 Dec 2024, DanielVizago added a lot of content to Supremacism about misandry, which another editor reverted with edit summary remove recently added pro-fringe section and put back the excerpt. Most of their 122 edits have been reverted by multiple editors.

Before the level 4 warning, I tried guiding DanielVizago away from CTOP; they don't engage on their talk page. (They've posted there once, to say "thanks" in response to a warning.) With their refusal to communicate, poor sourcing, and non-NPOV edits, I don't think they should be editing in this topic area. Schazjmd (talk) 23:23, 14 January 2025 (UTC)

Notification of the user against whom enforcement is requested

• Notified

Discussion concerning DanielVizago

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

Statement by DanielVizago

Statement by caeciliusinhorto

Since this report was opened, DanielVizago has continued to make questionable edits adding articles to Category:Female rapists.

• Possibly the worst edit, categorising a living person who has been accused (but not charged, let alone convicted) of sexual assault as a rapist (cf. WP:BLPCRIMINAL)
• This edit adds the category to a disambiguation page on the basis of one of the people listed on that page, who had in fact been convicted not of rape but of sexual activity with a minor
• this and this edit categorise two sexually-motivated murderers as rapists despite no evidence that they ever raped anyone in the article (cf. WP:CATV)

Caeciliusinhorto-public (talk) 10:53, 16 January 2025 (UTC)

Statement by Simonm223

Might be wise, as long as doing so wouldn't interfere with evidence, to get a revision deletion on some of the diffs presented above that make unfounded statements about BLPs. Simonm223 (talk) 18:55, 17 January 2025 (UTC)

Statement by (username)

Result concerning DanielVizago

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

• I've p-blocked from article space to see if we can get this editor communicating. Valereee (talk) 12:35, 16 January 2025 (UTC)
• I want to hear what they have to say, but I'm going to need a fairly convincing explanation as to how they're here to build an encyclopedia and not to POV-push men's rights activism content where it doesn't belong. The IDHT and spammy behavior and the BLP vios on top of that aren't super encouraging, either, but if they decide to communicate, I'm happy to reassess. theleekycauldron (talk • she/her) 22:56, 18 January 2025 (UTC)

  I'd like to hear what they have to say, too, but I'm also not averse to letting this archive with no further action since the p-block is an indef. I've left another message at their talk. Valereee (talk) 13:41, 19 January 2025 (UTC)

]

Ekdalian

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

Request concerning Ekdalian

User who is submitting this request for enforcement

NXcrypto (talk · contribs · deleted contribs · logs · filter log · block user · block log) 03:26, 20 January 2025 (UTC)

User against whom enforcement is requested

Ekdalian (talk · contribs · deleted contribs · logs · filter log · block user · block log)

Search CT alerts: in user talk history • in system log

Sanction or remedy to be enforced

WP:ARBIPA

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

1. 12:51, 11 January 2025 - Restoring recently added disputed content, contrary to WP:ONUS
2. 21:55, 11 January 2025 - Casting unsubstantiated aspersions and poisoning the well against another editor.
3. 12:01, 13 January 2025 - Poisoning the well against another user without any evidence of misconduct.
4. 19:11, 15 January 2025 - Restoring recently added disputed content again and essentially asking to get consensus for it, contrary to WP:ONUS.
5. 15:05, 16 January 2025 - Performs a blanket revert in order to make a WP:POINT, just because their previous edit was reverted, despite it being the version that was arrived upon by a month long discussion on the 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
6. 17:42, 16 January 2025 - Same as above but edit warring
7. 19:42, 16 January 2025 - Edit warring and casting aspersions saying that reverting editor is acting like the blocked sock Nobita456 "stop behaving like Nobita please"
8. 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! "
9. 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
10. 18:29, 19 January 2025 - calling a WP:NOTVANDAL edit as vandalism and issues final warning for vandalism

Diffs of previous relevant sanctions, if any

1. Date Explanation
2. Date Explanation

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

• Has a {{Ds/aware|ipa}} template for the area of conflict on their own talk page. and notified of WP:ARBIPA by Dennis Brown in 2022

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.On Bengali 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 like Sitush have called them out for it 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 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 of focusing 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. Nxcrypto Message 03:26, 20 January 2025 (UTC)

I'm unimpressed by your defence of #10, it was an unsourced change, sure disruptive but not vandalism (which has a very specific meaning). Please refer to WP:NOTVANDAL. Nxcrypto Message 07:33, 20 January 2025 (UTC)

Notification of the user against whom enforcement is requested

Discussion concerning Ekdalian

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

Statement by Ekdalian

I have nothing to say as such! I have been serving Misplaced Pages 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)

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)

Nxcrypto, it is a clear case of vandalism. The user intends to misrepresent and project their caste as Kulin 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)

• In response to Bishonen's comments, I would like to inform here that Sitush is referring to my response at a time when Nobita456'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)

  Orientls, the user has already been blocked for vandalism; I have years of experience in this area and quite sure of what I have mentioned! Thanks. Ekdalian (talk) 06:22, 22 January 2025 (UTC)

  @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)

Statement by Orientls

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" Misplaced Pages, 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?" , 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 this new 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)

Statement by (username)

Result concerning Ekdalian

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 was canvassed 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ålk 10:08, 21 January 2025 (UTC).

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 500 words 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

Est. 2021 (talk · contribs · deleted contribs · logs · filter log · block user · block log) 16:05, 21 January 2025 (UTC)

User against whom enforcement is requested

Alex 19041 (talk · contribs · deleted contribs · logs · filter log · block user · block log)

Search CT alerts: in user talk history • in system log

Sanction or remedy to be enforced

WP:ARBPIA & WP:IBAN

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

1. 21 January 2025

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

• Misplaced Pages:Arbitration/Requests/Case#IBAN Request
• User talk:Alex 19041#January 2025

Notification of the user against whom enforcement is requested

• User talk:Alex 19041#Notice of Arbitration Enforcement noticeboard discussion

Discussion concerning Alex 19041

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

Statement by Alex 19041

Statement by (username)

Result concerning Alex 19041

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 got at 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, Rosguill 16:25, 21 January 2025 (UTC)
• (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)
• I agree that the reported user needs to show some understanding that as a non-EC user, they need to leave this CTOP alone across 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. Beeblebrox 21:48, 21 January 2025 (UTC)

Denali-related 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 500 words and 20 diffs (not counting required information), except by permission of a reviewing administrator.

Request concerning Denali-related pages

User who is submitting this request for enforcement

Beeblebrox (talk · contribs · deleted contribs · logs · filter log · block user · block log) 22:28, 21 January 2025 (UTC)

User against whom enforcement is requested

] (] · ] · ] · ] · filter log · ] · block log)

Search CT alerts:  • in system log

Sanction or remedy to be enforced

WP:CT/AP

I think this is the right place to ask for this? Requesting an expansion of WP:CT/AP to cover all articles related to Denali, as it has unfortunately become a political hot-button issue as the POTUS made it a prioroty on his first day back in office to sign an executive order to revert the name of the mountain back to "Mt. McKinley".

In the past twenty-four hours there has been heavy editing/disruption in articles and on related talk pages and protection has been needed at several. Denali was probably hit hardest, but Denali–Mount McKinley naming dispute got some too, as has Denali National Park and Preserve, which is explicitly not even part of the executive order. I wouldn't be surprised if the same issue is happening in Gulf of Mexico related articles, but haven't checked for myself. Beeblebrox 22:28, 21 January 2025 (UTC)

Yeah, just checked Gulf of Mexico. 28 new talk page sections in the past day, was already ECP protected two weeks ago per WP:CT/AP.

I kinda think a single admin could do this, but I am editorially involved and probably slightly too infuriated to be objective. Beeblebrox 22:32, 21 January 2025 (UTC)

Thanks for the replies, that's kind of what I thought, but again didn't want to act on it as I'm editorially involved. Beeblebrox 22:41, 21 January 2025 (UTC)