Misplaced Pages

Latest revision as of 09:46, 24 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 an editor 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 an editor who engages 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 fewer than 10 edits will be removed. All users are welcome to comment on requests except where doing so would violate an active restriction (such as 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. Reports are limited to two individuals: the filer and the user being reported. If additional editors are to be reported, separate AE reports must be opened for each. AE admins may waive this rule if the particular issue warrants doing so. 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)

I am interested in the Google form cited above, specifically how this differs from the widely reported situation that resulted in the 'Off-wiki misconduct in Palestine–Israel topic area' case that employed Discord (and/or X, I forget) rather than a Google form. Is a consistent decision procedure being used to distinguish between encouraging participation and canvassing/meatpuppetry? I think a lot of people don't know where the line is, assuming there is a line, or at least some kind of fuzzy decision boundary. Sean.hoyland (talk) 04:46, 23 January 2025 (UTC)

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)

• I'm not satisfied with שלומית ליר's please of good faith. I think that the call for "interference" on Twitter (not even a week ago!) is a real concern in light of the standards being established by PIA5. I'm also concerned about the timeline of their knowledge of relevant CTOP sanctions. They were warned about PIA in April 2023 (by me, apparently). They should have been familiar with canvassing rules from the moment they got that warning to be on their best behavior. Not only that, but perusing their edit history, I see that there are several edits that are PIA violations prior to reaching XC on December 8 (e.g. Special:Diff/1256599528, although there's clearly many others in their edit history). In sum, I see no reason to believe the narrative of good faith presented here by them in light of the available evidence and do believe that we should consider at the minimum a logged warning. _signed, Rosguill 20:15, 23 January 2025 (UTC)

  I would be okay with a logged warning for canvassing, which remains the most concerning behavior to me. I find it difficult to see my way to penalizing violations of the XC restriction after the editor has already reached XC status without a clear finding of gaming XC status, and I don't see that here. Vanamonde93 (talk) 20:41, 23 January 2025 (UTC)

  I wouldn't call it gaming, I think it's a pattern of intentional defiance of community rules, which in turn makes the otherwise rather exemplary defense written here by them less than convincing. _signed, Rosguill 21:15, 23 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)