Misplaced Pages

:Arbitration/Requests/Enforcement: Difference between revisions - Misplaced Pages

Article snapshot taken from Wikipedia with creative commons attribution-sharealike license. Give it a read and then ask your questions in the chat. We can research this topic together.
< Misplaced Pages:Arbitration | Requests Browse history interactively← Previous editNext edit →Content deleted Content addedVisualWikitext
Revision as of 20:00, 28 March 2024 editTgeorgescu (talk | contribs)Extended confirmed users54,626 edits →Request concerning KronosAlight: What do you think about {{diff2|1215954680}}?← Previous edit Revision as of 20:35, 28 March 2024 edit undoSeraphimblade (talk | contribs)Edit filter managers, Administrators46,187 edits →KronosAlight: Closing with topic ban + formal warningNext edit →
Line 14: Line 14:


==KronosAlight== ==KronosAlight==
{{hat|{{noping|KronosAlight}} is indefinitely ] from the subject of ]s. {{noping|Nycarchitecture212}} is formally warned to avoid mischaracterizing the statements of other editors or otherwise ]. ] <small><sup>]</sup></small> 20:35, 28 March 2024 (UTC) }}
<small>''This request may be declined without further action if insufficient or unclear information is provided in the "Request" section below. <br />Requests may not exceed 500 ] and 20 diffs (not counting required information), except by permission of a reviewing administrator.''</small> <small>''This request may be declined without further action if insufficient or unclear information is provided in the "Request" section below. <br />Requests may not exceed 500 ] and 20 diffs (not counting required information), except by permission of a reviewing administrator.''</small>


Line 121: Line 122:
:As for Nycarchitecture212's lengthy posts above, it's disgraceful to summarize what Tgeorgescu says ] as "He has a self-described ax to grind with Jews that he describes as a cult perpetrating pseudohistory", as Seraphim has noted. Tgeorgescu describes Jews as a cult? No he doesn't. A logged warning for this blatantly misleading aspersion would certainly be appropriate. ] &#124; ] 19:52, 21 March 2024 (UTC). :As for Nycarchitecture212's lengthy posts above, it's disgraceful to summarize what Tgeorgescu says ] as "He has a self-described ax to grind with Jews that he describes as a cult perpetrating pseudohistory", as Seraphim has noted. Tgeorgescu describes Jews as a cult? No he doesn't. A logged warning for this blatantly misleading aspersion would certainly be appropriate. ] &#124; ] 19:52, 21 March 2024 (UTC).
::{{yo|BilledMammal}} maybe so. But Nycarchitecture212 needs to be a lot more careful in talking about these sensitive subjects. ] &#124; ] 17:47, 22 March 2024 (UTC). ::{{yo|BilledMammal}} maybe so. But Nycarchitecture212 needs to be a lot more careful in talking about these sensitive subjects. ] &#124; ] 17:47, 22 March 2024 (UTC).
{{hab}}


==Arbitration enforcement action appeal by andrew.robbins== ==Arbitration enforcement action appeal by andrew.robbins==

Revision as of 20:35, 28 March 2024

"WP:AE" redirects here. For the guideline regarding the letters æ or ae, see MOS:LIGATURE. For the automated editing program, see WP:AutoEd. For the English language varieties in Misplaced Pages, see Misplaced Pages:Manual of Style § National varieties of English. For administrator elections, see Misplaced Pages:Administrator elections.
Noticeboards
Misplaced Pages's centralized discussion, request, and help venues. For a listing of ongoing discussions and current requests, see the dashboard. For a related set of forums which do not function as noticeboards see formal review processes.
General
Articles and content
Page handling
User conduct
Other
Category:Misplaced Pages noticeboards

    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

    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:

    1. ask the administrator who first made the contentious topic restrictions (the "enforcing administrator") to reconsider their original decision;
    2. request review at the arbitration enforcement noticeboard ("AE") or at the administrators' noticeboard ("AN"); and
    3. 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:

    1. the action was inconsistent with the contentious topics procedure or applicable policy (i.e. the action was out of process),
    2. the action was not reasonably necessary to prevent damage or disruption when first imposed, or
    3. 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:

    1. the action was inconsistent with the contentious topics procedure or applicable policy (i.e. the action was out of process),
    2. the action represents an unreasonable exercise of administrative enforcement discretion, or
    3. compelling circumstances warrant the full Committee's action.
    1. The administrator may indicate consent at any time before, during, or after imposition of the restriction.
    2. 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:

    1. ask the enforcing administrator to reconsider their original decision;
    2. request review at the arbitration enforcement noticeboard ("AE") or at the administrators’ noticeboard ("AN"); and
    3. 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-en@wikimedia.org).
    Modifications by administrators

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

    1. the explicit prior affirmative consent of the enforcing administrator; or
    2. 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:

    1. 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.
    2. 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.
    3. 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.
    4. 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.

    Arbitration enforcement archives
    1234567891011121314151617181920
    2122232425262728293031323334353637383940
    4142434445464748495051525354555657585960
    6162636465666768697071727374757677787980
    81828384858687888990919293949596979899100
    101102103104105106107108109110111112113114115116117118119120
    121122123124125126127128129130131132133134135136137138139140
    141142143144145146147148149150151152153154155156157158159160
    161162163164165166167168169170171172173174175176177178179180
    181182183184185186187188189190191192193194195196197198199200
    201202203204205206207208209210211212213214215216217218219220
    221222223224225226227228229230231232233234235236237238239240
    241242243244245246247248249250251252253254255256257258259260
    261262263264265266267268269270271272273274275276277278279280
    281282283284285286287288289290291292293294295296297298299300
    301302303304305306307308309310311312313314315316317318319320
    321322323324325326327328329330331332333334335336337338339340
    341342343344345346

    KronosAlight

    KronosAlight is indefinitely topic banned from the subject of flood myths. Nycarchitecture212 is formally warned to avoid mischaracterizing the statements of other editors or otherwise casting aspersions. Seraphimblade 20:35, 28 March 2024 (UTC)
    The following discussion has been closed. Please do not modify it.

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

    Request concerning KronosAlight

    User who is submitting this request for enforcement
    Tgeorgescu (talk · contribs · deleted contribs · logs · filter log · block user · block log) 20:48, 11 March 2024 (UTC)
    User against whom enforcement is requested
    KronosAlight (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:ARBPS
    Diffs of edits that violate this sanction or remedy, and an explanation how these edits violate it
    1. 10 March 2024—violating WP:PSCI
    2. and 11 March 2024—ad nauseam advocacy for violating WP:PSCI, WP:ASPERSIONS; see also their previous edits at that talk page wherein they accuse me of violating WP:NPOV.
    3. 10 March 2024—accusing me you're on the wrong side of Misplaced Pages's rules on NPOV
    4. 10 March 2024—accept that you are violating Misplaced Pages rules
    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 10 March 2024 (see the system log linked to above).
    Additional comments by editor filing complaint
    • I do not seek a formal sanction, but someone needs to tell them they need to take a break from WP:Advocacy for WP:FRINGE science.
    • the claim that it has been definitively "refuted" with reference to a single paper isn't in line with how Misplaced Pages balances these important questions of neutrality, bias, and pseudoscientificity—this is not part of WP:RULES, they are inventing rules of their own making. In fact, citing Boslough (2023) is more than enough WP:V for the YDIH being pseudoscience.
    • So, Boslough (2023) is sufficient for WP:V my view, and Holliday c.s. (2023) is an extra bonus.
    • If you want an example: K.R. Popper admitted that Marx's predictions were scientific, but these predictions failed in the real world. So, it suffices to quote Popper in order to show that Marx was mistaken.
    • @Aquillion: Misplaced Pages already has the article Younger Dryas impact hypothesis. There it is presented in full detail.
    • a maximalist interpretation—for those in the know: a WP:FRINGE interpretation. And no, we don't incorporate fringe theories into mainstream articles. We don't incorporate pseudohistory into Bible scholarship articles.
    • @Nycarchitecture212: You should mind both WP:BOOMERANG and WP:SANTA. Accusations of antisemitism without providing evidence are WP:ASPERSIONS. What you ignore is that scholars belonging to Reform or Conservative Judaism, see e.g. , , , , and "consensus based on archaeology" at , also oppose fundamentalist pseudohistory. And secular Jews completely oppose it. I'm not saying that Orthodox Jews are bad people. All I am saying is that their views about Ancient Israel have been debunked by mainstream historians and mainstream archaeologists.
    • @ScottishFinnishRadish: I don't think it was their first time, see Misplaced Pages:Administrators' noticeboard/IncidentArchive1150#Nycarchitecture212 is deleting mainstream scholarship about Judaism. Especially . tgeorgescu (talk) 05:30, 16 March 2024 (UTC)
    • What do you think about ? tgeorgescu (talk) 20:00, 28 March 2024 (UTC)
    Notification of the user against whom enforcement is requested
    • 11 March 2024

    Discussion concerning KronosAlight

    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 KronosAlight

    I don't support the theory under discussion. It's at best an amusing science fiction narrative, but doesn't have (at least yet) any serious scientific backing.

    As a simple statement of principle, a single academic research paper claiming to have debunked a theory propounded by multiple other authors with their own peer-reviewed academic research papers cannot be the basis for a claim in the 'voice' of Misplaced Pages that a theory has been "refuted" (which is the wording apparently desired) of neutrality vis-a-vis NPOV. This wouldn't hold in any other field or area of discussion, otherwise every paper claiming to have refuted Karl Marx for example would have been considered definitive, rather than a field of open and intense contestation. We would, at minimum (and I've been contributing to Misplaced Pages for 11 years now), take a passive voice of 'Critics claim that ...' for example, or some variation thereof.

    There is nothing wrong with saying something alone the lines of, 'The theory has been considered pseudoscientific by critics' followed by the citation. There *is* a problem with the line "The theory has been refuted" followed by a single citation to a single paper. That is very, very rarely how research papers work.

    Tgeorgescu was invited repeatedly to provide further citations - because, of course, multiple papers over a sustained period by peer-reviewed journals is a legitimate basis upon which a Misplaced Pages article can verify the verdict of falsity or pseudo-scientificity.

    He has not done so, when it would have been much easier than endlessly arguing with me for simply enforcing NPOV.

    I invite him yet again to do so - if a scientific theory has in fact been *refuted* (i.e. conclusively demonstrated to be false), it should not be difficult to find citations to reputable peer-reviewed scienific journals demonstrating so. In fact I suspect he would not find it difficult to find multiple papers seeking to debunk the claims made in this context, which might make such a cumulative case.

    The easiest resolution would be for Tgeorgescu to simply cite the papers he claims (and I think do) exist in a new edit in order to justify the original wording of the article. I have no problem with him doing so and the wording then remaining the same. The Younger Dryas Impact Hypothesis is not considered mainstream science, and this too would be fair to note in the article in question, but the claim that it has been definitively "refuted" with reference to a single paper isn't in line with how Misplaced Pages balances these important questions of neutrality, bias, and pseudoscientificity.

    • I'm not endorsing the theory – I think it's basically science fiction, a mad mixture of Ancient Astronaut Theory and Young Earth Creationism. But you need more than just one paper which has received little coverage and, last time I checked, basically no citations of its own, in order to justify the claim that it has been "refuted", which is a conclusive and final claim, not a provisional one.
      If the citation of a single academic paper (and I of course do not doubt that the paper itself was subject to entirely valid crutiny via a rigorous peer-review process) is "more than enough" to declare a niche scientific theory "debunked", then I do wonder what the minimal Misplaced Pages requirements might be to make such a claim. What’s the ‘low bar’, compared to this ‘high bar’?
      That isn't how the scientific process works, which necessarily involves back-and-forth disputes in which multiple researchers and schools of thought claim to have 'debunked' the other, nor is it how Misplaced Pages adjudicates the truth or falsity of the claims to pseudoscientificity, which has a higher threshold of proof.
      You and I both know a number of other scientific papers exist which claim to have debunked the hypothesis. Just take 5 minutes to go find them and cite them and fix the article. I won't argue with you if you do that. KronosAlight (talk) 21:36, 11 March 2024 (UTC)

    Statement by Aquillion

    Regardless of what decision is reached here regarding WP:ASPERSIONs and the like, it would probably be best to take this to WP:FRINGEN. I think theory is obviously fringe, but how to best describe that and what sources to use for it still requires some thought; people at WP:FRINGEN are more likely to be able to answer that question. --Aquillion (talk) 00:52, 12 March 2024 (UTC)

    Statement by Nycarchitecture212

    KronosAlight I'm sorry that you've also had a negative interaction with this individual. A few days ago, he attempted the same thing with me. When I messaged him on the article's talk page expressing my concerns, he didn't engage with them at all. He rigidly adheres to one academic narrative regarding biblical scholarship and condescends to anyone with a maximalist interpretation. Personally, I've decided to cease interactions with him. Regrettably, based on my experiences, he appears to be a contentious editor who doesn't engage in discussions and debates in good faith. He frequently reverts edits without delving into the details on talk pages and endeavors to impose his narrow point of view, exploiting Misplaced Pages policies to suppress discourse and shape articles from a singular perspective rather than incorporating multiple academic viewpoints. While I'm not certain about Misplaced Pages conventions in such situations or the specific rules he may be violating, it seems implausible that his conduct is permissible. I do think the wording was a little choppy, but your request for him to bring more sourcing is valid and the right way to move the conversation forward.

    He also reverted my edits of an anti-Jewish trope about pigs and blood that was poorly sourced and unrelated to the article. The trope of Jews and pigs and blood is best well known in Judensau (German for "Jew-sow") a derogatory and dehumanizing image of Jews that appeared around the 13th century. Its popularity lasted for over 600 years and was revived by the Nazis. Jews, who were typically portrayed as having obscene contact with unclean animals such as pigs or owls or representing a devil, appeared on cathedral or church ceilings, pillars, utensils, etchings, etc.

    He has a self-described ax to grind with Jews that he describes as a cult perputrating pseudohistory and was ranting about this again a few days ago which got his post struck. One of the consequences of that is he is subtly pushing a pseudohistory revisionist agenda to describe ancient Jews solely as Yahewists and to erase any mention of Judaism from articles about ancient Jewish figures including the Ahab and in the Abrahamic Religions articles. It's important to note that while some Yahewists may be Jewish, not all Yahewists are Jewish. Therefore, it's inappropriate to categorize these ancient Israel characters (mythical or not) solely as Yahewists. I attempted to update it but he reverted my changes and circumvents the responsibility of having good faith discussions. I hope that a level-headed administrator will thoroughly investigate these matters. Such action would send a clear message about the true culture of Misplaced Pages. - Nycarchitecture212 (talk) 02:30, 14 March 2024 (UTC)

    • Not quite; I feel quite confident in my characterization and felt an obligation to weigh in to defend KronosAlight and share my experience. I've never had to contribute to one of these posts before but Tgeorgescu's heavy-handed use of admin resources, approach to sourcing and lack of good faith are genuinely concerning, something I've never encountered before.
      My attempts to engage in discussion on talk pages with this user have been sidestepped, and he has made some objectionable statements in the past, which other users have noted that I should be able to raise.
      I've raised valid concerns, most recently regarding the edit about pig's blood on the Ahab page he insists on, and his disregard for my input on the Abrahamic Religions talk page. If you look at what I wrote, it makes quite a lot of sense. Since you are contemplating a logged warning for speaking up, I'm here to contribute positively in good faith and enjoy myself; I didn’t come here looking for trouble. My area of expertise is uncommon and provides a valuable perspective within the framework of Misplaced Pages policy and discourse. Articles flourish when multiple views converge, and new information is synthesized through discourse. If you 100% disagree with what I wrote, it would be helpful if you could address my specific concerns, and then offer advice on how to refine my approach if necessary, which requires more work but is far more productive and positive. Nycarchitecture212 (talk) 01:54, 17 March 2024 (UTC)
      Here's the full quote: The POV of Orthodox Jews upon early Judaism is to a large extent void currency inside the mainstream academia. In mainstream history, it's void. Same as Jehovah's Witnesses dating the fall of Jerusalem in 607 BCE. Despite your protestations, it is clear that both these groups promote cult pseudohistory. I do have an ax to grind against pseudohistory, especially against fundamentalist pseudohistory." tgeorgescu (talk) 22:1233, 3 March 2024 (UTC)

    This statement could be considered controversial or offensive, as it directly criticizes the perspectives of certain religious groups, labeling them as promoters of "cult pseudohistory." The use of the term "void currency" suggests that the views of Orthodox Jews on early Judaism are completely disregarded in mainstream academia, which is a broad and potentially misleading generalization. Similarly, equating the beliefs of Jehovah's Witnesses regarding the fall of Jerusalem with pseudohistory could be seen as dismissive or disrespectful.

    The phrase "I do have an ax to grind against pseudohistory, especially against fundamentalist pseudohistory" indicates a strong bias against certain interpretations of history, which could be interpreted as antagonistic towards groups associated with those interpretations.

    While the speaker may intend to express a commitment to historical accuracy, the language used can be seen as targeting specific religious groups, which might be perceived as anti-Jewish or anti-religious sentiment. It’s important to critique specific historical claims or methodologies without broadly dismissing or demeaning the perspectives of entire communities. Nycarchitecture212 (talk) 04:54, 17 March 2024 (UTC) Moved to correct section. Seraphimblade 06:31, 17 March 2024 (UTC)

    Serpahimblade, I reached out in good faith to get your take on my specific concerns about those articles. Do you mind taking a look and weighing in on each one? To reiterate, he changes articles to describe ancient Jews solely as Yahewists and to erase any mention of Judaism from articles about ancient Jewish figures including the Ahab and in the Abrahamic Religions articles. It's important to note that while some Yahewists may be Jewish, not all Yahewists are Jewish. Therefore, it's inappropriate to categorize these ancient characters from the Torah (mythical or not) as Yahewists. Also, the pig blood thing was upsetting and another user said it was poorly sourced too. I was really surprised when he reverted these edits. I attempted to update it but he reverted my changes and circumvents the responsibility of having good faith discussions. Nycarchitecture212 (talk) 03:10, 20 March 2024 (UTC)


    Statement by BilledMammal

    Bishonen, I would read that comment as saying that Orthodox Judaism is a cult; it’s not quite the same thing as saying Judaism is, but given that Orthodox Judaism is the largest branch of Judaism I don’t think it’s a "blatantly misleading aspersion" 04:30, 22 March 2024 (UTC)

    I agree; in contentious topic areas editors need to be careful and precise in what they say. BilledMammal (talk) 01:11, 24 March 2024 (UTC)

    Statement by (username)

    Result concerning KronosAlight

    This section is to be edited only by uninvolved administrators. Comments by others will be moved to the sections above.
    • I might otherwise see this as a content dispute, but I'm quite concerned by the type of attitude displayed even at this very request: You and I both know a number of other scientific papers exist which claim to have debunked the hypothesis. Just take 5 minutes to go find them and cite them and fix the article. I won't argue with you if you do that. If you know about more sources for the claim, and think it needs more, you ought to be adding them, not removing the claim even though you apparently know it's verified. That's textbook tendentious editing, and if that's how this KronosAlight intends to handle situations like this, I rather wonder if they should be editing in this area (or indeed, any area) at all. Seraphimblade 03:25, 12 March 2024 (UTC)
      As to Nycarchitecture212, you seem to have rather grossly mischaracterized the statements you are supposedly quoting. That's not appropriate either. I think there needs to be at least logged warnings issued here, if not more, but would like some additional input if anyone has any. Seraphimblade 20:54, 15 March 2024 (UTC)
      I agree that there should be at least a logged warning. The editing is so pointy that I wouldn't object to a topic ban, though I lean slightly towards a logged warning in this case as there hasn't been a pattern of this behavior presented. ScottishFinnishRadish (talk) 22:31, 15 March 2024 (UTC)
    • Nycarchitecture212, as to how to "refine your approach", as you stated, you might start by not characterizing someone's statement that they "have an ax to grind against pseudohistory, especially against fundamentalist pseudohistory" as " an ax to grind with Jews". Either you are implying that Jews in general are engaged in fundamentalist pseudohistory, or you are totally mischaracterizing the statement to make it look inflammatory and unacceptable when it was not. Whichever one of those it is, that's completely inappropriate. And if you can't recognize it as such, I have my doubts as to whether you should continue editing in this topic area at all. Seraphimblade 03:04, 17 March 2024 (UTC)
      I suppose I can, given that, see how you got there without it being as bad, but let's not see something like that again. As to resolution, I would go forward with the logged warning, and hope that will suffice to settle things down. If not and we're back here again, we can decide what more to do at that point. Seraphimblade 06:43, 17 March 2024 (UTC)
      Yes, I'm afraid I mind. AE does not resolve content disputes or make binding decisions about what an article should or should not say. If there remains disagreement over that, and that can't be resolved via discussion, additional forms of dispute resolution might be necessary to involve other editors. But that decision is not for me, or anyone here, to make. Seraphimblade 05:22, 20 March 2024 (UTC)
      Unless any uninvolved admin objects within the next day or so, I will proceed with the closure proposed by Bishonen. Seraphimblade 20:41, 26 March 2024 (UTC)
    • KronosAlight says here and now that they don't support the theory under discussion, I presume the myth of the Great Flood, or possibly the specific "Black Sea deluge hypothesis". That has not prevented them from sealioning it within an inch of its life, under cover of "simply enforcing NPOV", both on Talk:Flood myth and indeed above on this page. I suggest an indefinite page ban from Flood myth and its talkpage. At least that.
    As for Nycarchitecture212's lengthy posts above, it's disgraceful to summarize what Tgeorgescu says here as "He has a self-described ax to grind with Jews that he describes as a cult perpetrating pseudohistory", as Seraphim has noted. Tgeorgescu describes Jews as a cult? No he doesn't. A logged warning for this blatantly misleading aspersion would certainly be appropriate. Bishonen | tålk 19:52, 21 March 2024 (UTC).
    @BilledMammal: maybe so. But Nycarchitecture212 needs to be a lot more careful in talking about these sensitive subjects. Bishonen | tålk 17:47, 22 March 2024 (UTC).

    Arbitration enforcement action appeal by andrew.robbins

    Appeal accepted. As such, the extended-confirmed protection issued by Courcelles at Talk:Elissa Slotkin is revoked, and the previous semi-protection is restored. As that semi-protection was not a CTOP action, it can be appealed through ordinary means in line with the protection policy. — Red-tailed hawk (nest) 19:02, 24 March 2024 (UTC)
    The following discussion has been closed. Please do not modify it.

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

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

    Appealing user
    andrew.robbins (talk · contribs · deleted contribs · logs · filter log · block user · block log) – andrew.robbins (talk) 14:27, 20 March 2024 (UTC)
    Sanction being appealed
    Talk:Elissa Slotkin Extended Confirmed Protection for one year. There does not appear to be a request at Misplaced Pages:Requests for page protection. There is no discussion with regard to this sanction on Talk:Elissa Slotkin until after its implementation (and even then, only by a third user). There is an active allegation of WP:Meatpuppetry at Misplaced Pages:Administrators' noticeboard/Incidents#Meatpuppetry/Slotkin article but ECP-lock is not a requested remedy.
    Administrator imposing the sanction
    Courcelles (talk · contribs · blocks · protections · deletions · page moves · rights · RfA)
    Notification of that administrator
    Diff of notification

    Statement by andrew.robbins

    This page was already semi-protected due to events in July of 2023. Per WP:ATPROT, "Talk pages are not usually protected, and are semi-protected only for a limited duration in the most severe cases of disruption." Extended-confirmed protection of talk pages is so rare that is not even mentioned in the policy. If the disruption in question was the meatpuppetry allegation (which, granted, it may not have been. I can't read Courcelles mind.), ECP-locking is not at all proportionate. If the allegation is confirmed, the discussion can simply be removed after-the-fact. Even if found to be entirely inauthentic, the discussion was never uncivil or disruptive. The time-frame of this sanction of one year is also utterly disproportionate. The page is already semi-protected and had no pattern of repeated violations that would justify an ECP lock of that length. I am requesting that this sanction be reverted and the prior semi-protected status be restored. andrew.robbins (talk) 14:27, 20 March 2024 (UTC)

    I am beginning to realize that much of this hinges on the proceedings over on the noticeboard. It may make sense to simply hold off on this appeal until that investigation is conducted given both the prevalence of unconfirmed assertions in the statements below and that a finding of innocence would mean that there is no valid protection from meatpuppets concern in the first place. andrew.robbins (talk) 21:09, 20 March 2024 (UTC)
    Strongly disagree with the notion that discussions have been neither uncivil nor disruptive. There were numerous instances of personal attacks leveled by Thespeedoflight and his socks, at the minimum. And while it might be unusual to ECP a talk page, it is also, as noted below, highly unusual for there to be this level of off-wiki coordination. I was hesitant in the past to disclose off-wiki accounts, but yeah, it’s @ProgFlipPAWI. Just scroll through his tl and see how the replies to his tweets line up exactly with the actions happening here; this isn’t speculation, users here have already admitted to being socks. Cpotisch (talk) 23:32, 20 March 2024 (UTC)
    Please take the sockpuppet/meatpuppet speculation to Misplaced Pages:Administrators' noticeboard/Incidents#Meatpuppetry/Slotkin article. This is not the place for that.
    Admins, can you strike? andrew.robbins (talk) 23:37, 20 March 2024 (UTC)

    Dcpoliticaljunkie: With all due respect, I think that the talk page got significantly more hostile after it was ECP'd, not more productive.

    Also, the allegations of meat-puppetry are just that. Allegations. Acting as if they're confirmed when they are very much an open question is WP:ASPERSIONS and I'd greatly appreciate you cutting it out. andrew.robbins (talk) 20:58, 20 March 2024 (UTC)
    To Drmies: The reason that I fell back on "just remove it later" is that Dcpoliticaljunkie did just that with the SPI referenced by wordsmith on a fairly large thread at Special:Diff/1212594724/1213401146 and nobody raised an issue with it. andrew.robbins (talk) 21:13, 20 March 2024 (UTC)
    Re: @Dcpoliticaljunkie's last comment. I'm curious what you mean by "This problem would go beyond manageable if non-ECP editor participation were to restart." There is no problem there aside from OrcaLord vehemently disagreeing with your position. The proper solution to that is to take it to dispute resolution if you can't handle it.
    I am going to be completely honest, I don't think this is about false consensus. I think this is about dissent. andrew.robbins (talk) 15:35, 22 March 2024 (UTC)


    Statement by Courcelles

    • I see the SPI is already linked. Given the off-wiki issues, I contend this was a reasonable use of CTOP authority to ensure the proper functioning of the project. ECP for a talk page is a rather unusual action, but active attempts to recruit meat puppets is also unusual. Being at the intersection of AP2 and NEWBLPBAN makes the article and the talk page flash point for this type of disruption. Courcelles (talk) 18:41, 20 March 2024 (UTC)

    Statement by Dcpoliticaljunkie

    I believe this enforcement action is warranted and hope it will allow for more collaborative editing of this article. For whatever reason, a cabal of Twitter users have chosen to turn this article into a battleground driven by their dislike of the subject as flagged by Cpotisch and admin Muboshgu here. One of the ringleaders of this group of Twitter users (@progflippawi, believed to be the puppetmaster Thespeedoflightneverchanges recently admitted to actively spamming other anti-Slotkin Twitter users to find "experienced Misplaced Pages editors" to help add negative information to Slotkin's article. This comes after their numerous attempts to sockpuppet have been detected and banned. Simultaneously with the sockmaster's recruitment, a series of editors with sparse editing histories swarmed the talk page to argue for one of the sockmaster's pet inclusions which was previously removed by Drmies. Following the ECP, OrcaLord (part of the anti-Slotkin Twitter cabal who was blocked from the page for edit warring by ScottishFinnishRadish and separately previously warned for original research on the page is the only one of the group who is ECP to argue for the dubious inclusion: while not ideal, it is much more manageable than the swarm following blocked editor Thespeedoflightneverchanges's Twitter recruitment. The enforcement has helped. My report on the administrator's noticeboard has more details about the meatpuppetry concerns on this article in addition to the sockpuppet issue. Need to get back to work so will leave it at that. Dcpoliticaljunkie (talk) 18:33, 20 March 2024 (UTC)

    @Red-tailed hawk and @Seraphimblade: I understand your concern about ECP of a talk page, however, I'd love to hear what your alternate solution to protect the page from off-wiki coordination and false consensus would be? @Drmies previously semiprotected the page which has helped in stopping the direct sockpuppetry. If the page is not ECP protected, I'm unclear what the mechanism for dealing with off-wiki canvassed editors swarming and tag teaming the talk page. I hope the informed discretion of admins involved in the page wouldn't be overturned by others without full understanding of the situation.
    Even now, with ECP protection, I think the ongoing discussion on this section underscores the difficulty and patience required for other editors on this page. This problem would go beyond manageable if non-ECP editor participation were to restart. Dcpoliticaljunkie (talk) 13:59, 22 March 2024 (UTC)

    Statement by (involved editor 2)

    Statement by Drmies

    Protecting a talk page is more common than some may thing, particularly in cases of continued vandalism or nationalist editing, for instance, and ArbCom is given the authority to do those kinds of things also even if they exceed what might be the ordinary reach of the ordinary administrator. andrew.robbins argues "well you can remove stuff later", but that (willfully or not) skips over the very fact that talk page disruption, esp. by people who act as meatpuppets would, is quickly highly disruptive, and the more posts there are, with responses and responses to responses, the harder it is to just remove a thread as a forum post. This semi-protection was entirely within the administrator's discretion, and even more so given the post-1992 status. Drmies (talk) 19:13, 20 March 2024 (UTC)

    Discussion among uninvolved editors about the appeal by andrew.robbins

    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 Aquillion

    Also see this open GENSEX clarification / amendment request, where the issue of ECP / ECR as it relates to WP:CTOPs is being discussed; it's still open, but at least some arbs are weighing in with the position that admins already have the authority to apply indefinite ECR to specific pages in CTOPs. --Aquillion (talk) 15:56, 20 March 2024 (UTC)

    To be clear (and I apologize if my replying like this is improper) my position is not that Courcelles did not have the authority to do this. My position is that this was a disproportionate and unnecessary exercise of said authority. andrew.robbins (talk) 16:01, 20 March 2024 (UTC)

    Statement by Swatjester

    As a general principle, I think that any standard restriction able to be authorized on a contentious topic is, by definition, proportionate and necessary. If it were not, the Committee would not have authorized administrators to have such wide discretion in imposing said restrictions unilaterally. It would be self-defeating to the purpose of the CTOPS procedure to require a continuum of escalation in protection beyond what the imposing administrator thinks is appropriate. And I think in the case where an article falls under two separate CT areas and one of those is BLP, there should be an additional presumption in favor of preventing disruption, even if that comes at the cost of non-EC editors being able to contribute. ⇒SWATJester 19:39, 20 March 2024 (UTC)

    Statement by Cpotisch

    I am not involved in this matter, although I was part of past disputes on the article. My viewpoint here is that discussions on the talk page absolutely have been uncivil and disruptive, and that the well-established influence of sock/meatpuppets has resulted in the deterioration of the quality of the talk page discussion. While it might be unusual to ECP a talk page, it is also, as noted below, highly unusual for there to be this level of off-wiki coordination. I was hesitant in the past to disclose off-wiki accounts, but yeah, it’s @ProgFlipPAWI, and scrolling through his timeline will show quite clearly what the issue is here. I’m bringing this up not to target users but to make clear that we are dealing with a highly-unusual situation that requires potentially-unusual remedies. A talk page spammed to swing outcomes will result in editorial decisions difficult to identify and reverse. Cpotisch (talk) 23:51, 20 March 2024 (UTC)

    Statement by OrcaLord

    I support the User:Seraphimblade here, ECP a talk page for a whole year just over an unconfirmed sockpuppet accusation is overdue and drastic, it should be removed once the accusation is closed. Even if there is any confirmed sockpuppet, any effect of sockpuppetry can be cleaned up by just deleting the sections started by socks and the replies from socks, while the current ECP status prevents lots of potential goodwill editors from providing any contribution to that page which will lower its quality. Also, the page itself is ECPed and we should generally trust their ability to decide what should be added based on Misplaced Pages policy and sufficient information, ECP the talk page will only limit the information they can get.

    Statement by (username)

    Result of the appeal by andrew.robbins

    This section is to be edited only by uninvolved administrators. Comments by others will be moved to the sections above.
    • I'm not weighing in on the appropriateness/proportionality of the 30/500 protection just yet, but I do want to note that Misplaced Pages:Sockpuppet investigations/Thespeedoflightneverchanges is relevant here for additional context. The Wordsmith 16:11, 20 March 2024 (UTC)
      It seems like the use of ECP was valid and within Courcelles's authority under the Contentious Topics designations. I'd be open to arguments for reducing the duration, but I don't think there's likely to be a consensus for removing it entirely. The Wordsmith 19:02, 20 March 2024 (UTC)
      After taking another look, I think it would be reasonable to downgrade to semi-protection and reduce the duration, somewhere between 1 week and 1 month. If we see significant disruption by autoconfirmed accounts, we can always upgrade it again. The Wordsmith 21:43, 22 March 2024 (UTC)
    • Courcelles, while of course use of ECP is within discretion here, what was the reason for using ECP rather than semiprotection? Shutting out editors from even a talk page is a drastic action, and ECP shuts out substantially more, so I think that does deserve more consideration than a rubber stamp. Seraphimblade 19:48, 20 March 2024 (UTC)
      OrcaLord and Cpotisch, I have removed your incorrectly placed comments. Threaded discussion is not allowed at AE. If you would like to make statements, please make them in a section of your own, as instructed above. Seraphimblade 23:41, 20 March 2024 (UTC)
      I think I agree with Red-tailed hawk. I do not see sufficient justification for ECP here. I'm open to hearing from the protecting administrator, and perhaps I would change my mind with that, but otherwise I would at least reduce this to semiprotection. Seraphimblade 01:46, 21 March 2024 (UTC)
    • I'm just plainly not seeing the justification for placing ECP on the article talk page on 18 March and keeping it for a year. I plainly do not see disruption in the talk page history that warrants ECP; within the past month one autoconfirmed sockpuppet posted a single comment on 7 March, but that does not justify protecting the whole article's talk page (something that ought truly be a last resort) for a whole year. As for the potential of future disruption, as WP:ECP notes, Extended confirmed protection should not be used as a preemptive measure against disruption that has not yet occurred.Administrators have authority to make unilateral CTOP actions, but they still have to be justified to survive appeal. A single edit by an autoconfirmed sockpuppet account on 7 March does not warrant the imposition of a 1-year extended-confirmed protection beginning on 18 March. I believe that this action should be overturned and converted into nothing more stringent than some temporary sort of semi-protection. As such, I would accept the appeal. — Red-tailed hawk (nest) 00:03, 21 March 2024 (UTC)
    • I also find it hard to see this as "reasonably necessary to prevent damage or disruption", basically per Red-tailed hawk. I support accepting the appeal and restoring the previous non-CTOP semi-protection, which no one here seems to be objecting to, without prejudice against returning to ECP if there's additional disruption in the future. Extraordinary Writ (talk) 22:03, 22 March 2024 (UTC)

    OrcaLord

    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 OrcaLord

    User who is submitting this request for enforcement
    Dcpoliticaljunkie (talk · contribs · deleted contribs · logs · filter log · block user · block log) 14:20, 26 March 2024 (UTC)
    User against whom enforcement is requested
    OrcaLord (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/American politics 2

    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. Talk:Elissa_Slotkin#Labor_Positions_and_the_2023_UAW_strike Further explanation below: This is the editor's first engagement on this article following a 3-month block for disruptive editing. The discussion shows continuing intent to insert an opinion which multiple experienced editors point out is attempting to not supported by mainstream reliable sources (only supported by Jacobin and Twitter user noted below) and refusal to drop the insistence to include their spin of living person's comments.
    Diffs of previous relevant sanctions, if any
    1. July 2023 Warning re: original research on same article from Binksternet
    2. November 2023 90 day ban from article for disruptive editing from ScottishFinnishRadish
    3. 3 separate protections of page for disruptive editing in last 6 months
    If contentious topics restrictions are requested, supply evidence that the user is aware of them (see WP:CTOP#Awareness of contentious topics)
    • Previously blocked as a discretionary sanction or contentious topic restriction for conduct in the area of conflict, see the block log linked to above.
    • Previously given a discretionary sanction or contentious topic restriction or warned for conduct in the area of conflict on Nov 18 2023 by ScottishFinnishRadish (talk · contribs · blocks · protections · deletions · page moves · rights · RfA).
    • Alerted about discretionary sanctions or contentious topics in the area of conflict, on November 2020 (see the system log linked to above).
    Additional comments by editor filing complaint

    Editor was previously blocked from editing this page for disruptive editing and edit warring as linked above. In their first return to the article, the editor has argued strenuously for inclusion of original research that violates biography of living persons policy refusing to WP:DROPTHESTICK in conjunction with suspected meatpuppetry organized on Twitter by repeated sockpuppet Thespeedoflightneverchanges. Has also discussed how to wikilawyering regarding this page on Twitter: "Sometimes there are small things in it that you can use to make your point/negate their point" which is more combative/warfare than collaboration to improve encyclopedia.

    Editor's contributions outside of this article are positive from what I can tell, however, they've previously been noted to be part of a group of "anti-Slotkin Twitter editors" who admin Muboshgu has noted are looking to influence the article with POV-pushing.

    Notification of the user against whom enforcement is requested

    Discussion concerning OrcaLord

    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 OrcaLord

    WP:DROPTHESTICK is obviously not applicable here. This is an active discussion with no achieved consensus yet. Dcpoliticaljunkie has been a consistent aggressor on both the Elissa Slotkin talk page and in many other areas, often making destructive edits to the Elissa Slotkin page without consensus, as well as accusing anyone who disagrees with him of meatpuppetry. The fact that Dcpoliticaljunkie is bringing up my previous ban on the page for edit warring is just further evidence that this request is an attempt to silence my position on the talk page, as I have already committed to no longer editing the Elissa Slotkin article after the ban, instead solely focusing on the talk page. Regarding the mention of my tweet, Dcpoliticaljunkie is clearly misinterpreting what I meant. What I meant is that it is important to take all parts of a rule into account when determining how to deal with a situation. My goal in talking on the Elissa Slotkin talk page has always been to ensure what is best for the quality of the article, and I have never acted in bad faith on the talk page. If you look at my account history, I have consistently made positive edits to Misplaced Pages, including the addition of thousands of detailed maps to Misplaced Pages. Considering my history, it should be very clear that I have always intended to make a positive difference throughout Misplaced Pages, including on the Elissa Slotkin talk page.

    Statement by andrew.robbins

    If anyone needs to drop the stick here, its you, DCPJ. The suspected meatpuppetry you linked was archived without a ruling. Using it as evidence of violations is, ironically, bludgeoning.

    Mapping out viewpoints to sources is not OR. Arguing for the inclusion of a quote in the absence of consensus isn't POV pushing.

    DCPJ has been reporting any user that disagrees with their positions on that talk page. This has been going for over a week now and needs to stop.

    Statement by XeCyranium

    I'm just commenting here because I was pinged. I can't say whether or not Orcalord has broken rules on the talk page, only that they certainly haven't been arguing in good faith from a desire to improve the article. Their statements on the talk page are so obviously slanted towards trying to tarnish, however slightly, the reputation of the article subject regardless of what sources say that it's become a waste of time to keep engaging with them. Luckily nobody who wasn't an obvious meatpuppet with 13 total edits agreed with their POV-pushing, so I'm not sure how much damage they're doing. XeCyranium (talk) 21:11, 26 March 2024 (UTC)

    Statement by (username)

    Result concerning OrcaLord

    This section is to be edited only by uninvolved administrators. Comments by others will be moved to the sections above.
    • I'm not seeing any edit warring, and this appears to primarily be a content dispute between two editors. I see someone recently suggested on the talk page that an RfC be used, and I think that, not AE, is the way to bring resolution to such a dispute. Seraphimblade 23:37, 26 March 2024 (UTC)
      An RfC seems reasonable. There also appears to be a disupte as to the reliability of a particular source, so a WP:RSN thread might also be worthwhile. — Red-tailed hawk (nest) 02:10, 28 March 2024 (UTC)
    • I'm truly struggling to see how any edits made within the past month or so could plausibly be edit warring, though I do think that previous sanctions related to the same material are worth noting should the topic be a root cause of behavioral disruption from one user. Merely that an editor has moved from edit warring to bludgeoning a talk page discussion would not render a warning or prior block for edit warring wholly irrelevant.On that note, regarding bludgeoning, the ArbCom has noted that ditors should avoid repeating the same point or making so many comments that they dominate the discussion. Have individual editors been repeating the same point over and over in talk page discussions to such an extent that they have been dominating the discussion by sheer volume of comments? If so, an organized list of diffs showing this pattern of behavior would be very helpful in evaluating what's going on here. It's a bit hard to follow as-is, though I can try to go through the discussion diff-by-diff on my own if need be. — Red-tailed hawk (nest) 02:09, 28 March 2024 (UTC)