Wikipedia:Arbitration/Requests/Motions
- recent changes
- purge this page
- view or discuss this template
Request name | Motions | Initiated | Votes |
---|---|---|---|
Marine 69-71 | Motions | 26 October 2024 | 0/0/0 |
Covert canvassing and proxying in the Israel-Arab conflict topic area | 6 November 2024 | 0/0/0 |
No cases have recently been closed (view all closed cases).
Request name | Motions | Case | Posted |
---|---|---|---|
Amendment request: Palestine-Israel articles (AE referral) | Motion | (orig. case) | 17 August 2024 |
Motion name | Date posted |
---|---|
Motions: PIA Canvassing | 21 January 2024 |
Remind, warn, admonish | 30 January 2024 |
Motions
This page can be used by arbitrators to propose motions not related to any existing case or request. Motions are archived at Wikipedia:Arbitration/Index/Motions. Only arbitrators may propose or vote on motions on this page. You may visit WP:ARC or WP:ARCA for potential alternatives. You can make comments in the sections called "community discussion" or in some cases only in your own section. Arbitrators or clerks may summarily remove or refactor any comment. |
Motions: PIA Canvassing
Six motions enacted, see ACN announcement. firefly ( t · c ) 19:50, 21 January 2024 (UTC) |
---|
The following discussion has been closed. Please do not modify it. |
Do not remove a motion or any statements or comments unless you are a clerk or an Arbitrator. There must be no threaded discussion, so please comment only in your own section. General facts1) Since at least October 2023, there has been an ongoing effort by one or more banned editors to canvass discussions within the Israel-Palestine topic area and asking for proxy edits to promote a pro-Israel point of view. Based on the evidence received by the Committee, the following discussions have been targeted:
The Arbitration Committee would like to thank the editors who reported canvassing. If editors have any additional canvassing evidence, please bring it to the Committee's attention. The Arbitration Committee asks the Wikimedia Foundation for assistance creating technical measures to prevent the ongoing abuse. For this motion there are 14 active arbitrators. With 0 arbitrators abstaining, 8 support or oppose votes are a majority.
Arbitrator views and discussions (General facts)
Clerk notes (General facts)
Statement by Novem Linguae (General facts)
Statement by Galobtter (General facts)Does ArbCom know the identities of any of the banned editor(s) involved here? Galobtter (talk) 00:16, 5 January 2024 (UTC)
Statement by Callitropsis (General facts)It seems to me that GeneralNotability's blocks of Atbannett and Hmbr may be related to this. Both editors supported the unblock of an editor that had been indeffed for violating an ARBPIA topic ban with similar rationales. After the discussion was closed with consensus against the unblock, Tamzin disclosed that they had sent evidence to ArbCom that Atbannett and Hmbr were canvassed to the discussion by a banned editor. Around a month later, Atbannett and Hmbr were both blocked by GeneralNotability, although the block of Atbannett was temporary, unlike the block of Hmbr. Both editors have since filed unsuccessful unblock requests. From what I can tell (correct me if I'm wrong), the blocks themselves are not clearly designated as CU or ArbCom actions, although such can certainly be inferred from the context. They were not accompanied by any announcement, and both were notified on their talk pages using {{SockBlock}}, which is for abuse of multiple accounts (despite the notes in the block log that they were blocked for meatpuppetry) and stipulates that the blocks are indefinite (despite Atbannett's block being set to expire after 30 days). It's unclear to me whether the block of Atbannett was meant to be indefinite. This event certainly seems to be related to the events described in this motion and I'm not sure whether the omission from this motion is intentional. Apologies if I'm just kicking up a hornet's nest that could've been left alone and forgotten about, but I figured it wouldn't hurt to at least mention this incident for the sake of posterity and ask for clarification. — Callitropsis🌲[formerly SamX · talk · contribs] 01:25, 5 January 2024 (UTC)
Statement by Tamzin (General facts)Should Wikipedia:Administrators' noticeboard/Archive356 § User:Gilabrand unblock request be included in the list? (Referring specifically to Atbannett, Hmbr, and probably Homerethegreat's !votes; I have no reason to think any other overturn !votes were in bad faith.) -- Tamzin[cetacean needed] (they|xe|she) 03:24, 5 January 2024 (UTC)
Statement by Vice_regent (General facts)This RfC reminded me of what I said here at WP:ARBIRP. Within a few hours Marokwitz proposing an RfC, Homerethegreat, Zanahary, Oleg_Yunakov, Dovidroth and Agmonsnir all quickly voted, none bothering to address any of the sourcing or neutrality issues I had raised (I'm not saying they should have agreed with me, but they simply ignored my comment). In the case of WP:ARBIRP, it was later determined[1], that someone would send emails to users with links to RfCs and talking points and they'd vote accordingly. I'm not saying that all the above voters were canvassed, but I have a strong suspicion that at least some of them were. The behavior of Agmonsnir was suspicious (their very first edit[2] to Hamas was to jump in the middle of an edit war and revert to Homerethegreat’s version using the same false talking point others were using; then their very first edit to Talk:Hamas was their RfC vote) so I asked them about it, but they said they hadn't received any off-wiki communication[3].VR talk 04:12, 5 January 2024 (UTC)
Statement by IOHANNVSVERVS (General facts)Since another editor has already mentioned them, I'll add that I have suspicions regarding Agmonsir's involvment in this as well. Examples:
IOHANNVSVERVS (talk) 04:44, 5 January 2024 (UTC) Regarding nableezy's mention of AndresHerutJaim, who seems to have been a pro-Israel sockmaster who was banned in 2012, I'll add the following: It seems like the whitewashing edit war on Genocides in history (1946 to 1999) involving Homerethegreat and Dovidroth, which I brought up here [11], was begun (here [12]) by Joemb1977, a now blocked user with a notice on their userpage reading "An editor has expressed a concern that this account may be a sockpuppet of AndresHerutJaim" IOHANNVSVERVS (talk) 16:44, 5 January 2024 (UTC) References
Statement by Aquillion (General facts)Going over the listed discussions, here's the other editors that leap out as having activated or reactivated their accounts in the relevant timeframe and who contributed to several of these discussions, often with no interaction with the articles prior to the day canvassed users started appearing:
Obviously some caution is necessary because there are logical reasons why someone with an interest in the topic would reappear on October 7th, but these editors are notable for appearing a week later and contributing to a bunch of discussions that were canvassed here, several of which ought to have been hard for a newly-returned user to find. --Aquillion (talk) 06:13, 5 January 2024 (UTC) Statement by Marokwitz (general facts)
Moved from a reply to Novem Linguae If I may, a technical recommendation would be that every email sent through the platform is automatically accompanied by a message on the receiver's talk page (without the email content), with no ability to disable this, thereby creating an additional level of transparency and deterrence against misuse of the email facility. Marokwitz (talk) 20:33, 5 January 2024 (UTC) Moved from a reply to EytanMelech I recommend that you copy this to your statement concerning your block, below, as it is irrefutable evidence that you were fully transparent and complained about the canvassing in real-time. Marokwitz (talk) 21:13, 5 January 2024 (UTC) Statement by Agmonsnir (General facts)
Statement by Nableezy (General facts)I think this is missing some of the more obvious examples of canvassing where only a tangential relationship to the subjects these editors normally edit saw a targeted effort to vote stack, such as at Talk:Apartheid#Requested move 12 October 2023. Following an email request to vote no, the move request (which included Fagerbakke, later blocked as a sock of AndresHerutJaim and HaNagid at the time as LUC995 and later blocked as a sock of Tombah), had several users make their first ever edit to that talk page, those being EytanMelech, Mistamystery, Pg 6475, Dovidroth, and Zanahary. None of those users have edited either the talk page or article since (Zanahary, Pg6475, Mistamystery, EytanMelech and Dovidroth edits to the talk page), and none of them were, from the contributions, participating in requested moves that were not targetted for canvassing. I also think you all should consider some sort of amnesty for people who admit their involvement, perhaps a topic ban instead of an indefinite block. nableezy - 14:47, 5 January 2024 (UTC)
Statement by EytanMelech (General facts)Let it be known for the record that I almost certainly did not have a "tangential relationship to the subjects" prior to the October 12 request on the Apartheid article on Wikipedia. 2 days prior, I made 6 edits to the Kfar Aza massacre page (with previously unused sourcing and over a thousand bytes of data), as well as an edit and comment on Two-State solution. Two days prior to that, I made over 2k bytes of edits to the Alexandria shooting page. My interest in these articles did not spawn from any sort of canvassing beggars from people like your stated Faggerbakke, but because of the October 7th attack, the deadliest single massacre of Jews in decades, which spawned a desire in me to improve and support coverage on.
Statement by Coretheapple (general facts)I weighed in on the DavidRoth topic ban appeal, only to see that it has been closed with a link to this page. Unless I'm missing something, it appears that User: Nableezy, who is currently topic-banned for engaging in battlefield conduct in opposition to DovidRoth and other editors, has (notwithstanding that topic ban) supplied private evidence indicating that DovidRoth and other editors he doesn't like have been canvassed and edited on the basis of that canvassing. In response to that evidence, which is described here as convincing beyond a shadow of a doubt, editors are going to be kicked off the project. Checkmate. Really, Arbcom? You're going to indefinitely ban editors under these circumstances? I think Arbcom owes the community full transparecy. No possible privacy concerns justify such a "star chamber" action. Yes I know I know. Wikipedia is not a bureaucracy, Wikipedia is not a place for due process, yadda yadda. You don't have to tell me but why rub it in people's faces, especially in such a hot-button area such as this? The full evidence upon which you are relying should be made known (with redactions as necessary) not just for the sake of the community, but for the sake of readers of Wikipedia who might want to know how Wikipedia functions and why I/P articles may or may not have a certain slant or POV. Don't just say "oh we have private evidence from a very involved party and we are acting on it. Seeya!" If you do, I think it would be a serious mistake. I used to edit to stop paid editing and COI, but I stopped some years ago because I saw that it was futile and because I was working to improve the reputation of the project and the Foundation, when both seemed largely indifferent. I am starting to get a feeling of "déjà vu." Coretheapple (talk) 15:04, 5 January 2024 (UTC)
Statement by Zanahary (General facts)Really displeased to have been brought into this. I think users whom no one is actually standing up and accusing of anything should be left alone. Nableezy and Vice_regent, please either accuse me of proxy voting or refrain from tagging me. Zanahary (talk) 17:55, 5 January 2024 (UTC) Statement by Oleg Yunakov (General facts)
Statement by Objective3000 (General facts)I understand why all folks want to see all evidence. But there is a reason that there are only something like 50 or so CUs and far fewer arbs. These are members who have gained the trust of the community and must deal with privacy issues. Further, CU techniques, although hardly secret in the tech field, should not be broadcast. I am also uncomfortable with claims that we, the hoi polloi, must know exactly what info and by whom was provided as that brings up scary incidents IRL. WP in not a democracy. Barring an insurrection, I think we need to trust presented info as far as it goes. Of course possible contrary evidence can be presented. (Albeit as an editor in PIA I have seen nothing in the general facts that is surprising.) Side comment: A horizontal rule would be useful between the four major sections. O3000, Ret. (talk) 01:39, 6 January 2024 (UTC)
Statement by Legoktm (General facts)I'm not really a fan of the direct request to the WMF as part of this. Why are volunteer developers unable to help with this? The vast majority of anti-abuse tooling was, and still is, designed, developed, and/or maintained by volunteers. I can't imagine this anti-canvassing whatever is something that just the WMF can accomplish, and if that's the case, it seems like a much larger problem. Legoktm (talk) 02:07, 6 January 2024 (UTC)
Statement by BilledMammal (General facts)I am grateful that the committee has chosen to do this publicly and applaud this move towards increased transparency. However, I am concerned that this is quickly turning into a witch-hunt, with editors tossing out accusations with little to no evidence, accusations that in a different forum would result in a boomerang as often as not. I think it would be beneficial for the committee to instruct editors to avoid issuing accusations unless they have some form of evidence for them, and to remind editors that posting unsupported accusations - casting aspersions - can result in sanctions. 02:59, 6 January 2024 (UTC) Statement by Sean.hoyland (General facts)Given that, in one case, "at least 190 editors" received emails according to KevinL at Wikipedia:Articles_for_deletion/Genocide_against_Palestinians, what is known and can be disclosed about the evidently somewhat flawed selection criteria AndresHerutJaim is using to target editors? Sean.hoyland - talk 03:17, 6 January 2024 (UTC) Also, regarding asking "the Wikimedia Foundation for assistance creating technical measures to prevent the ongoing abuse", it's an obvious point, but a contributing factor is the inability to solve the tricky problem of sockpuppetry allowing disruption vectors like AndresHerutJaim to abuse the system for over a decade. So, I'm wondering whether the Wikimedia Foundation has made any progress with machine learning tools like SocksCatch? Sean.hoyland - talk 03:49, 6 January 2024 (UTC) Perhaps Marokwitz's comment about the WP:PROXYING policy and the apparent lack of clarity on the appropriate response to stealth canvassing by a site banned editor suggests that the Village pump WP:PROXYING (banning policy): Clarification needed discussion from November 2021 might need revisiting at some point. Sean.hoyland - talk 15:08, 9 January 2024 (UTC) Is ArbCom willing to disclose a list of sockpuppet accounts used to canvass editors? I'm curious how many had the extended confirmed user access level. I'm wondering what would happen if accounts without the extended confirmed user access level were unable to add ECP articles to their watchlist. Sean.hoyland - talk 13:17, 11 January 2024 (UTC) Statement by Wh15tL3D09N (General facts)I genuinely like all the editors here on Wikipedia (although I may not always agree with their views), and I would hate to see anyone blocked. I am commenting here in response to @Nableezy:s' remark about HaNagid being a sock of Tombah in order to provide additional information. I respectfully disagree with Nableezy: from HaNagid vs. Tombah's talk pages, they appear to me to be very different personalities, with HaNagid being more diplomatic. I also recently took a look at HaNagid vs Tombah's global accounts. HaNagid has a Hebrew Wiki account which he created and started editing on March 2, 2022 - May 18, 2023. He has edited things like Mariah Carey and Pokemon. Tombah has a Hebrew Wiki account which he created June 19, 2021 - Dec 2023, and the vast majority of his edits are about Jewish history, genetic study on Jews, etc. Due to the overlap in account timeline and the contrast in editing subjects on Hebrew Wikipedia, I strongly disagree that HaNagid and Tombah are the same person. I don't know why Tombah was blocked, but from his Hebrew account, I believe he would have been an asset (and has been an asset) to the Jewish articles on Wikipedia. HaNagid, unfortunately, did game to get extended-confirmed permissions on English Wikipedia, but I am not sure if that warrants a sockpuppet accusation and indefinite block. I was impressed with the edits that I did see from HaNagid: they were detail-oriented, concise, and in real-time, his edits were rapid fast. If both he and Tombah are people who I suspect are pursuing PhDs (I could be wrong), they would have been an asset to Wikipedia, and blocking them is a loss. How does this relate to the current Arbitration Request? I would respectfully ask that the administrators take each individual editor's contributions to Wikipedia into account and to look at the completeness and quality of evidence provided before deciding on an outcome as severe as an indefinite block on Wikipedia. From the HaNagid vs. Tombah sockpuppet case, it is clear that there is reasonable doubt and evidence, that those two are two different people. Also, wanted to point out that it’s Homerethegreat not Homerthegreat, probably in reference to an artist, and the user could equally likely be male or female. Wh15tL3D09N (talk) 06:46, 6 January 2024 (UTC) Statement by Thebiguglyalien (General facts)Given that much of the information surrounding this motion is not accessible, I've compiled some statistics. I evaluated participation in the 15 listed discussions, tabulating it in my sandbox. At a minimum, I've found strong evidence of severe WP:BATTLEGROUND violations. There are eight editors who participated in a majority of the discussions, and not one of them ever "broke ranks", always agreeing with the same editors. Of the three named editors in this motion:
Only Arbcom has the evidence to determine whether canvassing took place, but there are undeniably concentrated efforts to impose certain points of view in violation of Wikipedia policies. Thebiguglyalien (talk) 01:03, 7 January 2024 (UTC) Statement by My very best wishes (General facts)Jehochman said that Icewhiz could be involved. If it was him or anyone else sophisticated, this can be an intentional set up. Immediately after every RfC is opened, someone sends an email to user X saying: "Hey, why would not you make such comment "..." [a comment similar to other comments made by X in previous RfCs in the same subject area]". At least one of Icewhiz socks imitated other contributors. Now, if user X does make such comment, word to word, that means X is not only engaged in proxying, but also stupid or there is a WP:COI issue. But if he does not, and simply makes a similar comment at the RfC, this could be a set up. My very best wishes (talk) 14:33, 7 January 2024 (UTC)
Statement by Philipnelson99 (General facts)Having examined the statements given here and the page list provided as part of the motion, it's very clear that some kind of coordination behind the scenes. This is an aside but I'd like to point out that others that simply calling these motions a set up is not very helpful and honestly extremely inappropriate in this venue. Statements are supposed to be directed towards the committee and not others making statements. Philipnelson99 (talk) 16:57, 7 January 2024 (UTC)
Statement by The Wordsmith (General facts)Several editors have raised the issue that Arbcom is considering sanctions for people who were canvassed, or who made proxy edits but could potentially have had those opinions on their own. Whether the "instructions" given were one-way or not, it is clear that off-wiki coordination happened and content/discussion was manipulated. WP:PROXYING does say this, but it also directs the user to WP:MEAT which explains further. This is not the first time this has been dealt with, either. Editors who believe we don't ban people for being canvassed or participating in meatpuppetry should read the case that established the precedent, WP:EEML. In particular, the Principles "Gaming the system", "Meatpuppetry", and "Presumption of Coordination". Participation in discussions after being canvassed was noted, not just coordinating by itself. Regarding the transparency issue raised by several editors, that is a very valid point. I'm aware per Barkeep49 that Arbs are currently discussing whether more of the data can be made public without compromising privacy. I would also encourage them to review the Findings of Fact at WP:EEML, where the contents and authenticity of the private evidence were summarized and described in a way that did not compromise confidentiality. I think most editors would be satisfied with a summary like that from a transparency standpoint. The WordsmithTalk to me 18:27, 9 January 2024 (UTC)
Statement by Levivich (General facts)I don't really doubt that canvassing/proxying has occurred; it's so common, it's the reason I keep my email off. But, I think Arbcom needs to shore up its (public) evidence a bit here. First, as to the charges of participating in a discussion because of canvassing. I do not think that charge can be held against anyone in high-profile articles, because everyone is aware (and often watchlisting) these articles, so they'd participate in discussions there whether canvassed or not. The following articles are un-canvass-able, in my opinion, because they're just too high-profile: Israel, Gaza Strip, United Nations Partition Plan for Palestine, From the river to the sea, and 2023 Israel–Hamas war. Anyone editing anywhere in this topic area is going to be aware of and participating at these articles and others like them. There is a second layer of articles that I believe are similarly un-canvassable, because anyone in the top articles (like Israel or 2023 Israel-Hamas war) is going to find this second layer of sub-articles. From the above list: Allegations of war crimes against Israel and Human shields in the Israeli-Palestinian conflict. Template:Genocide navbox is another page in that category -- anyone editing a page where that navbox appears will be aware of the navbox and thus of discussions about the navbox. There are also articles that, while more obscure than the top-level ones, become "wiki-famous" because they're posted at ANI, or on the talk page of one of the top-level articles (or at WPO or Discord or IRC or some other place where there is non-specifically-targeted canvassing). That would include Wikipedia:Articles for deletion/Genocide against Palestinians and Wikipedia:Articles for deletion/Nakba denial, and arguably Wikipedia:Articles for deletion/Beit Rima massacre (as one of many massacre articles that have become well-known). So on this list, the only places where I'd be surprised that someone showed up, would be Talk:Ahed Tamimi and Wikipedia:Articles for deletion/Glorification of martyrdom in Palestinian society. I hope arbcom "filters" the evidence to separate out high-profile articles on the above list from low-profile ones (regardless of whether arbs agree with my particular classifications). Second, as to the charge of WP:PROXYING, it is impossible for an editor to I think it would be helpful, to shore up public confidence, for arbcom to publicize some stats, like how many emails were sent, how many emails were received by each of the editors, maybe how many proxy edits were made (or suspected), maybe the relevant time period (was it all after Oct 7?). I know more detail means less security and privacy, but I think there is an acceptable middle-ground. So, e.g., if it's publicly disclosed that Editor 1 received 30 mass emails between Oct 7 and Dec 31 and Arbcom has received copies of 10 of those, and Editor 1 made the requested edits 7 times... that's a different story than if you say Editor 1 has received 2 emails and we don't have copies of either one but thereafter they showed up at Talk:Israel and voted in an RFC. The latter is weak sauce, the former is strong. Finally, I don't put any stock into "Editor 1 showed up at XX/15 discussions and voted the same way" because we could make that list for any number of regular contributors in any number of topics. There are always editors who consistently vote and consistently vote pro-Israeli or pro-Palestinian, or pro-Democrat or pro-Republican, etc. That's an indication of bias (which everyone has and isn't in and of itself a policy violation) but not canvassing or proxying, just interest in the topic and a common viewpoint. Levivich (talk) 19:27, 9 January 2024 (UTC) Statement by Nsk92 (General facts)I find the process that the ArbCom is trying to use here to be highly objectionable. Usually Arbcom motions with sanctions are used in emergency situations, to desysop an admin without opening a full case or sometimes to remove a member of the ArbCom itself. What we have here is not an emergency situation. There are lots of accusations flying around directed at various editors, and the circumstances appear to be rather complex. Don't deal with this situation by motion(s). Instead, open a full case and use a more careful and deliberative process. Nsk92 (talk) 21:10, 11 January 2024 (UTC)
Statement by {other-editor} (General facts)Other editors are free to make relevant comments on this request as necessary. Comments here should address why or why not the Committee should adopt the motion or provide additional information. Dovidroth2) Based on information from the checkuser tool and on information received, the Committee determines that Dovidroth (talk · contribs) most likely participated in discussions due to canvassing and made proxy edits for a banned editor. As a result, they are indefinitely banned from Wikipedia. This ban may be appealed immediately after the enactment of this remedy, and every twelve months thereafter. For this motion there are 14 active arbitrators. With 1 arbitrator abstaining, 7 support or oppose votes are a majority.
Dovidroth topic ban2.1) Based on information from the checkuser tool and on information received, the Committee determines that Dovidroth most likely participated in discussions due to canvassing and made proxy edits for a banned editor. As a result, they are indefinitely topic banned from making edits related to the Arab-Israeli conflict, broadly construed. This ban may be appealed immediately after the enactment of this remedy, and every twelve months thereafter. For this motion there are 14 active arbitrators. With 1 arbitrator abstaining, 7 support or oppose votes are a majority.
Arbitrator views and discussions (Dovidroth)
Statement by Dovidroth (Dovidroth)I am writing to express my shock and concern regarding these accusations. I acknowledge that I have received multiple canvassing emails through the Wikipedia private emails system, which I ignored, and I have not acted upon them or responded in any manner. Furthermore, in the interest of transparency and fairness, I am formally requesting that the Arbitration Committee provide me with the private evidence that has been compiled against me. This request is made in the spirit of understanding the full context of the allegations and to allow me to defend myself. In addition to this message, I will also be reaching out to the Arbitration Committee via email to reiterate my request. The unfolding of events gives me reason to believe that this situation might be part of an orchestrated campaign to smear pro-Israel editors, a concern that deeply troubles me. It is my hope that the Committee will consider my request with the seriousness it deserves, ensuring a fair and just process for all parties involved. Regarding the issues raised by @Philipnelson99, @Tamzin had previously stated that my ban was only involving sock puppets, which this case was not. Furthermore, although a banned user got involved in the middle, I was simply restoring the earlier version of @Homerethegreat, who is not a banned user. For these reasons, I do not think that this was a "pretty clear violation" as Philipnelson99 suggests. Nevertheless, as soon as Tamzin told me that it was potentially an issue, I self-reverted. Dovidroth (talk) 09:49, 5 January 2024 (UTC)
Statement by Philipnelson99 (Dovidroth)While this doesn't speak directly to whether or not Dovidroth has engaged in canvassing, BUT I do believe it's pertinent to note that Dovidroth was sanctioned by Tamzin as part of an unblock agreement. This sanction was Statement by starship.paint (Dovidroth)
Statement by Jehochman (Dovidroth)
Could somebody explain to me how the checkuser tool tells you anything about one user emailing another user? As stated, the assertion sounds like a non-sequitur. Do you mean to say that this account looks like it could be an Icewhiz sock, but the technical evidence is not conclusive so you will book it as proxying? This account and the one below are strenuously protesting their innocence. Maybe you should offer the editors to identify themselves to WMF if they want to get their bans lifted. Once they prove that they are real people distinct from Icewhiz, a warning against proxying should suffice. If they don't accept the offer then that answers your question. Jehochman Talk 16:18, 6 January 2024 (UTC)
Statement by Taking Out The Trash (Dovidroth)Strongest Possible Oppose. We don't ban editors for canvassing or meatpuppetry. Canvassing by itself merits a warning, exclusion of the canvassed !vote(s) from the relevant discussion(s), and, if canvassing occurs on-wiki, possibly a temporary block or topic ban imposed on the person(s) orchestrating said canvassing. Off-wiki canvassing, as long as it isn't harassment, there's nothing we can do about except slap {{notavote}} on the affected pages and discount obviously canvassed comments made by people who clearly have no policy knowledge. Again, as long as the off-wiki stuff isn't "canvassing by extortion" or some other form of harassment, we shouldn't be sanctioning editors on-wiki for things they say off-wiki. Proxying for a banned editor is a form of meatpuppetry, which again, does not merit the most severe sanction short of WMF intervention that can be possibly issued. A person making edits at the direction of a banned user, or reinstating the reverted edits of a banned user, is taking responsibility for that content as if they had made the edit themselves. If the content of the edits is problematic, it should be dealt with accordingly, up to and including blocks if necessary, but again, we don't outright ban editors with no or minimal sanction history just for making some edits that might've been better off not made. The action of "blind proxying" (i.e. proxying for banned users without stopping to examine if the edits themselves are appropriate) should be met with a warning for a first offense, and then standard meatpuppetry procedures if it continues after a warning. Yes, I know these procedures frequently include indef blocks, but a standard indef block, while it has the same technical effect, is much less severe of a sanction than an ArbCom ban. But if the edits themselves are not problematic, and the only issue with them is that they were requested by or originally made by a banned user, there is absolutely zero reason to sanction another user simply for agreeing with the POV of a banned user, especially if an editor in good standing who wasn't canvassed had made those exact same edits and wouldn't face any sanction. In short, I was completely shocked to see this on my watchlist. This is a serious overreach and the fact that it is even being considered is deeply concerning. Again, unless we are dealing with some form of harassment (i.e. "canvassing by extortion"), we do not ban editors merely for participating in discussions after being canvassed to them, nor do we ban editors for engaging in "routine" meatpuppetry, especially for a first offense. Taking Out The Trash (talk) 18:27, 6 January 2024 (UTC) Statement by Coretheapple (Dovidroth)A chart compiled by User:Thebiguglyalien purports to show "battlefield' behavior, I believe it shows nothing of the kind, but that is beside the point. What it does show is something peculiar. User:Pincrete took "Pro-Palestinian" positions in three matters at issue in this arbitration. Yet, as he (Pincrete) points out, Pincrete was a target of the canvassing and quite correctly made public his concerns in the AfD for which he was canvassed. That of course was refelcted by others in the AfD, also correctly. I find it odd, to say the least, that a determined pro-Israel canvasser would canvass persons not in their "camp," and I think that this raises the possibility of a "set-up" as mentioned by User:My very best wishes above.[23] I agree also with the other comments made by others that the penalty being discussed here is unduly harsh, which adds greatly to the unfairness of editors not being shown the evidence being used against them. If this was a "set up" in any way, shape or form, then I would suggest that this entire case is "fruit from a poisoned tree." Coretheapple (talk) 16:48, 7 January 2024 (UTC) Reply to Philipnelson99: It's not a "conspiracy theory," it's a comment on a strange anomaly in the little evidence provided publicly. I'm not suggesting that the person bringing the motion was engaged in a "set-up," if that is what happened. But I do think that Arbcom should take into consideration the number of adverse parties who wound up being canvassed. If there is one, it might have been a stupid mistake by the canvasser. But there were several, I think it is significant. Coretheapple (talk) 17:22, 7 January 2024 (UTC)
Statement by Nableezy (Dovidroth)Aoidh if a topic ban is proposed I think it should be Arab-Israeli conflict, not just Palestine-Israeli conflict, following the relevant arbitration cases that had the wider conflict as their scope. nableezy - 17:16, 8 January 2024 (UTC) Statement by DanCherek (Dovidroth)(This comment applies to the proposed topic bans for all three editors.) Regarding the proposed TBANs from making edits related to the Arab-Israeli conflict: I'm wondering whether this scope is sufficient, specifically looking at discussions like Talk:Gaza Strip#"Oppressive one-party state" (listed in "General facts" above), that is not technically about the conflict itself but was nonetheless targeted by canvassing attempts. NB: I don't often edit or administrate in this topic area, so if it is already generally understood that these discussions are covered, broadly construed, then no problem. DanCherek (talk) 19:10, 8 January 2024 (UTC) Statement by Animal Lover 666 (Dovidroth)For each of these users, and any other user with a similar problem, the following process should be followed:
Statement by Marokwitz (Dovidroth)I reviewed the WP:PROXYING policy and was surprised to learn that proxy editing is permitted (as an exception) if the editor is "able to show that the changes are productive and they have independent reasons for making such edits." Therefore, I think @User:Dovidroth should be given an opportunity to explain their independent reasons for each edit and to demonstrate their productivity. If they provide sufficiently good answers, a warning would be sufficient. Marokwitz (talk) 11:07, 9 January 2024 (UTC) Statement by Galobtter (Dovidroth)I find it odd the stance being taken that it's apparently ok to lie to both ArbCom and the community about offwiki proxying (not saying I know if Dovidroth lied or not, but the plain implication of the comments above by ArbCom members is that Dovidroth is not being truthful in his explanations). Off-wiki proxying undermines community trust, but even more so is lying about it. And it is not like Dovidroth didn't get a warning beforehand. He was in fact blocked 8 months ago for basically the same conduct at issue here—off-wiki proxying for a banned user. He was unblocked in a gesture of good faith trusting in his explanation of those edits. Looking back now I'd have to think he was untruthful about not being off-wiki canvassed to those discussions. I don't know how we can allow an editor to keep editing if we cannot have the minimum of trust in what they are telling us and if they are abusing our good faith. Wikipedia is built on trusting editors, and undermining that trust deserves a full ban—otherwise ArbCom is basically telling people to lie to them to try to get out of sanctions. Galobtter (talk) 01:22, 17 January 2024 (UTC) Statement by {other-editor} (Dovidroth)Other editors are free to make relevant comments on this request as necessary. Comments here should address why or why not the Committee should adopt the motion or provide additional information. EytanMelech3) Based on information from the checkuser tool and on information received, the Committee determines that EytanMelech (talk · contribs) most likely made proxy edits for a banned editor. As a result, he is indefinitely banned from Wikipedia. This ban may be appealed immediately after the enactment of this remedy, and every twelve months thereafter. For this motion there are 14 active arbitrators. With 1 arbitrator abstaining, 7 support or oppose votes are a majority.
EytanMelech topic ban3.1) Based on information from the checkuser tool and on information received, the Committee determines that EytanMelech most likely made proxy edits for a banned editor. As a result, they are indefinitely topic banned from making edits related to the Arab-Israeli conflict, broadly construed. This ban may be appealed immediately after the enactment of this remedy, and every twelve months thereafter. For this motion there are 14 active arbitrators. With 1 arbitrator abstaining, 7 support or oppose votes are a majority.
Arbitrator views and discussions (EytanMelech)
Statement by EytanMelech (EytanMelech)Hello everyone! I was unaware there was an arbitration request out me and was quite shocked to find out that there is a belief that I am taking part in canvassing or have been making proxy edits on behalf of banned users. Let me start by saying that I was approached by user @Nableezy: via my talk page [permanent section links: 1, 2] on November 7th and December 12th of last year asking me if I had taken part in any sort of this type of behavior (being recruited to make edits/votes). I missed the first message, but quickly replied to the second one stating that I had not been given any edits or votes to put in by any user, blocked or unblocked. As one can tell by my edit history, especially within the last few months, I have done a decent amount of work on articles surrounding Israel and Judaism, although mostly surrounding the Old Yishuv and old Jewish culture. I will not deny the fact that I have a pro-Israel stance, although I try not to let that get in the way of my impartiality, such as I did when I created the English Wikipedia article for the Killing of Yuval Castleman, a good samaritan who was shot and killed by an IDF soldier due to the shooter, Freija, suspecting him of being a terrorist. I have also participated in many talk discussions and AfDs regarding the Israel-Palestine conflict. I have voted in certain ways, but I can guarantee you that those are in respect to my genuine opinions on the subject and are not dictated by anyone else and I have never voted a certain way because I was told to by another user. I often browse articles surrounding the conflict and habitually check talk pages of articles, and if I see something to vote on there, I may if I believe I either have something to add or wish for my voice to be heard. I am sorry that you believe me to be doing work on behalf of another user or users, but I simply am not. I value Wikipedia very much, as I have demonstrated in my nearly 6,000 edits on the site, and my 150+ articles created in the past few years. I will not lie when I say I am terrified of a ban with my work being locked away forever, but I have simply not done what has been accused of me, although I do suspect Nableezy had a word in this. ( This is an addition to my statement from the general discussion as reccomended by Makrowitz, as it is good evidence proving that I did not make proxy edits and that I complained about canvassing in real time.: Let it be known for the record that I almost certainly did not have a "tangential relationship to the subjects" prior to the October 12 request on the Apartheid article on Wikipedia. 2 days prior, I made 6 edits to the Kfar Aza massacre page (with previously unused sourcing and over a thousand bytes of data), as well as an edit and comment on Two-State solution. Two days prior to that, I made over 2k bytes of edits to the Alexandria shooting page. My interest in these articles did not spawn from any sort of canvassing beggars from people like your stated Faggerbakke, but because of the October 7th attack, the deadliest single massacre of Jews in decades, which spawned a desire in me to improve and support coverage on.
Cheers EytanMelech (talk) 22:24, 4 January 2024 (UTC) Edit: I forgot to mention this when I submitted my statement, but let it be known that I am more than glad to answer any questions regarding this investigation. Additionally, I would like to add comments regarding my issue with Nableezy in particular. As soon as I found out that I was being voted on for something Israel-Palestine related, I assume it had to have been him. He has previously asked me multiple times about this issue, and he also has been in edit disputes with me a few times on Israel-related articles. This is unsurprising, as he was recently sanctioned against editing in Israel-Palestine articles for battleground editing, and I suspect he is hosting a similar ideology here. I am aware that he has sent the Arbitration Committee information via email, although I cannot properly respond to the claims because I have gone through my edit history multiple months back and have struggled to find anything that aligns with the information that is being provided publicly to me. I suspect it will be near impossible to defend myself when I am not even being told what I did that counts as editing on behalf of another user. I also think it is quite odd that he is advocating against others for banning on Wikipedia when he himself has been penalized for problematic edit warring on behalf of his opinions himself.
Statement by Nableezy (EytanMelech)The evidence that I have seen, and sent to the committee, shows, in my view conclusively, that a banned editor made requests for specific edits that included edit-summaries to be used, and that this editor carried out the requested edits and copy-pasted the provided edit summaries. If that is not considered proxying for a banned user then I would appreciate some clarification as to what the committee does consider to be "proxying". nableezy - 00:05, 5 January 2024 (UTC)
Statement by Pincrete (EytanMelech)
Statement by Coretheapple (EytanMelech)I've already expressed my general concerns, and I have specific concerns raised by the statements by this editor and DavidRoth above. Posting it here but it applies to DavidRoth as well. If I understand it, correctly, both were not canvassing but were the targets of canvassing, allegedly complying with the requests of an unnamed banned editor. This raises a few bothersome scenarios that may or may not be relevant here, but certainly may be in the future. I can share them with arbcom privately by email in more detail, but suffice to say that, as a general principle, banning people on the basis of being targets of canvassers raises a number of troubling issues. Please let me know if you want me to email you with my concerns. Coretheapple (talk) 19:57, 5 January 2024 (UTC) Statement by Taking Out The Trash (EytanMelech)Strongest Possible Oppose. We don't ban editors for canvassing or meatpuppetry. Canvassing by itself merits a warning, exclusion of the canvassed !vote(s) from the relevant discussion(s), and, if canvassing occurs on-wiki, possibly a temporary block or topic ban imposed on the person(s) orchestrating said canvassing. Off-wiki canvassing, as long as it isn't harassment, there's nothing we can do about except slap {{notavote}} on the affected pages and discount obviously canvassed comments made by people who clearly have no policy knowledge. Again, as long as the off-wiki stuff isn't "canvassing by extortion" or some other form of harassment, we shouldn't be sanctioning editors on-wiki for things they say off-wiki. Proxying for a banned editor is a form of meatpuppetry, which again, does not merit the most severe sanction short of WMF intervention that can be possibly issued. A person making edits at the direction of a banned user, or reinstating the reverted edits of a banned user, is taking responsibility for that content as if they had made the edit themselves. If the content of the edits is problematic, it should be dealt with accordingly, up to and including blocks if necessary, but again, we don't outright ban editors with no or minimal sanction history just for making some edits that might've been better off not made. The action of "blind proxying" (i.e. proxying for banned users without stopping to examine if the edits themselves are appropriate) should be met with a warning for a first offense, and then standard meatpuppetry procedures if it continues after a warning. Yes, I know these procedures frequently include indef blocks, but a standard indef block, while it has the same technical effect, is much less severe of a sanction than an ArbCom ban. But if the edits themselves are not problematic, and the only issue with them is that they were requested by or originally made by a banned user, there is absolutely zero reason to sanction another user simply for agreeing with the POV of a banned user, especially if an editor in good standing who wasn't canvassed had made those exact same edits and wouldn't face any sanction. In short, I was completely shocked to see this on my watchlist. This is a serious overreach and the fact that it is even being considered is deeply concerning. Again, unless we are dealing with some form of harassment (i.e. "canvassing by extortion"), we do not ban editors merely for participating in discussions after being canvassed to them, nor do we ban editors for engaging in "routine" meatpuppetry, especially for a first offense. Taking Out The Trash (talk) 18:27, 6 January 2024 (UTC) Statement by Marokwitz (EytanMelech)
Statement by {other-editor} (EytanMelech)Other editors are free to make relevant comments on this request as necessary. Comments here should address why or why not the Committee should adopt the motion or provide additional information. Homerethegreat4) Based on information from the checkuser tool and on information received, the Committee determines that Homerethegreat (talk · contribs) most likely participated in discussions due to canvassing and made proxy edits for a banned editor. As a result, they are indefinitely banned from Wikipedia. This ban may be appealed immediately after the enactment of this remedy, and every twelve months thereafter. For this motion there are 14 active arbitrators. With 1 arbitrator abstaining, 7 support or oppose votes are a majority.
Homerethegreat topic ban4.1) Based on information from the checkuser tool and on information received, the Committee determines that Homerethegreat most likely participated in discussions due to canvassing and made proxy edits for a banned editor. As a result, they are indefinitely topic banned from making edits related to the Arab-Israeli conflict, broadly construed. This ban may be appealed immediately after the enactment of this remedy, and every twelve months thereafter. For this motion there are 14 active arbitrators. With 2 arbitrators abstaining, 7 support or oppose votes are a majority.
Arbitrator views and discussions (Homerethegreat)
Statement by Homerethegreat (Homerethegreat)I will open frankly with my bitter disappointment in Wikipedia. I can’t stress enough how terrible my experience has been over the past few months. Having felt racism throughout my life due to my identity outside Wikipedia, I was naive to think it would not happen here. I believed that editors aimed to build a neutral, credible encyclopedia. However, I have been met at every turn with bad faith, accusations, and sometimes even terminology or negatively worded content based on presumptions about my identity. Just a few days ago, User:ScottishFinnishRadish removed such a statement. No, I will not reveal my political positions or my identity publicly. Even now, I believe an editor should remain impartial and neutral, regardless of their opinion. If ArbCom wishes to know my political opinion, I will email them. I used to love Wikipedia, and when the war began, I felt it was my responsibility and privilege to edit in ARBPIA. I believed I had to do it because I saw how misinformation could spread. Yes, I’ve seen what appears to be partisan editing. I imagine everyone has hundreds of articles on their watchlists, and it's likely that people check each other’s contributions. I’ve checked other users' contributions too, and if that’s illegal, I sincerely apologize. ARBPIA is far from my main interest. I’ve written over 30 articles on topics that interest me more than the conflict, and a look at my edit history will show exactly that. After reading Pincrete’s statement, I find it extremely troubling that an ArbCom investigation was opened when the forwarding party has deleted it. Why is good faith implied for Pincrete and not for me or others who have not voted in the same line as Nableezy? Why? I'm asking whoever is in charge to divulge the evidence and send me a copy of whatever evidence exists against me. This is crucial; without it, I have no idea and no chance to understand what I'm being accused of. I wish the evidence to be presented in full transparency, and I will cooperate fully with ArbCom to prove the falsehood of the accusations. Never did I imagine I would feel in Wikipedia what I experienced outside when I lived in Europe. I was naive. No more; I am left bitterly disappointed. Homerethegreat (talk) 06:18, 6 January 2024 (UTC)
Statement by TamzinI will just note that Homerethegreat !voted to unblock Gilabrand in between the !votes by Atbannett and Hmbr, which as noted above were canvassed and led to both of those users being CUblocked. I was unable to find a smoking gun that Homerethegreat was themself canvassed, but all three users' votes began with the same "Strongly support the lifting of block", all made similar rationales describing Gila's editing in flattering terms, and all were infrequent AN posters. Homer, for instance, had only posted there once before. On its own that isn't dispositive, but may compound whatever private evidence ArbCom has. -- Tamzin[cetacean needed] (they|xe|she) 02:23, 5 January 2024 (UTC) Statement by IOHANNVSVERVSI believe these discussions are relevant regarding Homerethegreat:
IOHANNVSVERVS (talk) 00:59, 5 January 2024 (UTC) Statement by Taking Out The Trash (Homerethegreat)Strongest Possible Oppose. We don't ban editors for canvassing or meatpuppetry. Canvassing by itself merits a warning, exclusion of the canvassed !vote(s) from the relevant discussion(s), and, if canvassing occurs on-wiki, possibly a temporary block or topic ban imposed on the person(s) orchestrating said canvassing. Off-wiki canvassing, as long as it isn't harassment, there's nothing we can do about except slap {{notavote}} on the affected pages and discount obviously canvassed comments made by people who clearly have no policy knowledge. Again, as long as the off-wiki stuff isn't "canvassing by extortion" or some other form of harassment, we shouldn't be sanctioning editors on-wiki for things they say off-wiki. Proxying for a banned editor is a form of meatpuppetry, which again, does not merit the most severe sanction short of WMF intervention that can be possibly issued. A person making edits at the direction of a banned user, or reinstating the reverted edits of a banned user, is taking responsibility for that content as if they had made the edit themselves. If the content of the edits is problematic, it should be dealt with accordingly, up to and including blocks if necessary, but again, we don't outright ban editors with no or minimal sanction history just for making some edits that might've been better off not made. The action of "blind proxying" (i.e. proxying for banned users without stopping to examine if the edits themselves are appropriate) should be met with a warning for a first offense, and then standard meatpuppetry procedures if it continues after a warning. Yes, I know these procedures frequently include indef blocks, but a standard indef block, while it has the same technical effect, is much less severe of a sanction than an ArbCom ban. But if the edits themselves are not problematic, and the only issue with them is that they were requested by or originally made by a banned user, there is absolutely zero reason to sanction another user simply for agreeing with the POV of a banned user, especially if an editor in good standing who wasn't canvassed had made those exact same edits and wouldn't face any sanction. In short, I was completely shocked to see this on my watchlist. This is a serious overreach and the fact that it is even being considered is deeply concerning. Again, unless we are dealing with some form of harassment (i.e. "canvassing by extortion"), we do not ban editors merely for participating in discussions after being canvassed to them, nor do we ban editors for engaging in "routine" meatpuppetry, especially for a first offense. Taking Out The Trash (talk) 18:29, 6 January 2024 (UTC) Statement by Marokwitz (Homerethegreat)I reviewed the WP:PROXYING policy and was surprised to learn that proxy editing is permitted (as an exception) if the editor is "able to show that the changes are productive and they have independent reasons for making such edits." Therefore, I think @User:Homerethegreat should be given an opportunity to explain their independent reasons for each edit and to demonstrate their productivity. If they provide sufficiently good answers, a warning is sufficient. Marokwitz (talk) 11:07, 9 January 2024 (UTC)
Statement by {other-editor} (Homerethegreat)Other editors are free to make relevant comments on this request as necessary. Comments here should address why or why not the Committee should adopt the motion or provide additional information. |
Remind, warn, admonish
Add the following to the Arbitration Procedures as a subsection of "Arbitration Proceedings"
When used in arbitration motions or remedies, the words below should be considered to have the following order of severity:
- Remind (weakest)
- Warn
- Admonish (strongest)
- Enacted - KevinL (aka L235 · t · c) 06:46, 30 January 2024 (UTC)
Arbitrator discussion (Remind, warn, admonish)
Support
- During my time on the committee this scale has been used with increasing consistency. By adding it to our procedures we make things clear for arbs and for others (including parties) what our intent is when using these words. The biggest argument I've heard against this proposal is that we should only use 1 word. I think it's important for ArbCom to have a way to distinguish among behavior that is bad but perhaps not so bad as to require a remedy. This is particularly useful in cases where multiple parties might have done something wrong, but it would be unfair to one party to suggest their conduct is equally wrong to another party. I'm pretty open to other versions of this but chose this format so that ArbCom could choose to add other words in the future if it wishes (for instance "caution" was used pretty regularly in the past but has fallen out of favor) and can still have more flexibility to evolving usage than by adopting the more detailed versions I've come up with in this glossary. Barkeep49 (talk) 16:40, 25 January 2024 (UTC)
- I've been under the impression for over a decade that this was already an unwritten rule, so I'm happy to formally codify it. Maxim (talk) 16:50, 25 January 2024 (UTC)
- Support with pleasure - an excellent way to give clarity and ensure consistency. firefly ( t · c ) 17:06, 25 January 2024 (UTC)
- Oh, this is wonderfully simple and useful. ~ ToBeFree (talk) 18:47, 25 January 2024 (UTC)
- Sure. No strong opinions in codifying this. Z1720 (talk) 18:53, 25 January 2024 (UTC)
- I'm happy that this motion is being proposed in public, given that questions about these terms seem to crop up every time the Committee uses a remedy from this spectrum. Hopefully this passing will help chip away (slightly) at the mystique of Committee proceedings. For Izno's concerns below, I do not think that we should be dividing this into sets of verbs for administrators/non-administrators or for editing/actions. Remedies with these words will usually (or should) say why they've been warned (edit-warring etc). Sdrqaz (talk) 03:58, 26 January 2024 (UTC)
- A documented explanation of the "scale" that ArbCom already uses is helpful for clarification purposes. I do support L235's first three bullet points below, particularly changing harshest to strongest or most severe. - Aoidh (talk) 06:22, 26 January 2024 (UTC)
- KevinL (aka L235 · t · c) 17:12, 26 January 2024 (UTC)
Oppose
- Makes no substantive changes to the current situation. I would much rather we choose one warning type rather than continuing to have 3 overlapping ones. --Guerillero Parlez Moi 06:46, 26 January 2024 (UTC)
Abstain
- I am not opposed. Primefac (talk) 13:35, 26 January 2024 (UTC)
- Per Primefac. Moneytrees🏝️(Talk) 21:20, 26 January 2024 (UTC)
Arbitrator general discussion (Remind, warn, admonish)
- My comments are stylistic.
- "arbitration" isn't a proper noun and should generally be de-caps unless we want to make it a proper noun going forward. See, e.g., WP:Arbitration ("The arbitration process exists [...]").
- "harshest" -> "most severe". I don't think we should characterize any particular action as inherently "harsh". (For consistency, this might imply "mildest" -> "least severe".)
- Add a comma after "motions or remedies".
- (least important) "have" is a somewhat weak verb. Consider "express the following order of severity".
- KevinL (aka L235 · t · c) 20:12, 25 January 2024 (UTC)
- Your two copy edits are of course great in my mind. Would you be OK with mildest->weakest and harshest->strongest @L235:? I have more concerns about the last suggestion. Words have meaning and I think that is a clearer expression of what we're doing than "express the following order of severity". Barkeep49 (talk) 20:35, 25 January 2024 (UTC)
- Re: strongest/weakest: We already indicate that it's in "order of severity", so "most severe" and "least severe" seem most appropriate, but I wouldn't object to "strongest"/"weakest". KevinL (aka L235 · t · c) 03:58, 26 January 2024 (UTC)
- @Aoidh, Sdrqaz, Z1720, ToBeFree, Firefly, and Maxim: I have made the changes L235 suggested (minus "have"). Please revert if any of these concern you. Barkeep49 (talk) 15:44, 26 January 2024 (UTC)
- Fine by me! firefly ( t · c ) 16:20, 26 January 2024 (UTC)
- No issues here with the changes. - Aoidh (talk) 22:13, 26 January 2024 (UTC)
- Looks good to me! ~ ToBeFree (talk) 16:56, 26 January 2024 (UTC)
- @Aoidh, Sdrqaz, Z1720, ToBeFree, Firefly, and Maxim: I have made the changes L235 suggested (minus "have"). Please revert if any of these concern you. Barkeep49 (talk) 15:44, 26 January 2024 (UTC)
- Re: strongest/weakest: We already indicate that it's in "order of severity", so "most severe" and "least severe" seem most appropriate, but I wouldn't object to "strongest"/"weakest". KevinL (aka L235 · t · c) 03:58, 26 January 2024 (UTC)
- 1 and 3 are fine, no opinion on 2, tend to disagree about 4 per Barkeep49. ~ ToBeFree (talk) 21:55, 25 January 2024 (UTC)
- I am neutral on points one and four from Kevin's proposed changes, in favour of some change for point two (neutral between Kevin and Barkeep's proposals), and unambiguously in favour of the comma (point three). Sdrqaz (talk) 03:58, 26 January 2024 (UTC)
- Your two copy edits are of course great in my mind. Would you be OK with mildest->weakest and harshest->strongest @L235:? I have more concerns about the last suggestion. Words have meaning and I think that is a clearer expression of what we're doing than "express the following order of severity". Barkeep49 (talk) 20:35, 25 January 2024 (UTC)
- @Izno: I'm not understanding the advantage you see in restricting certain words to admins/non-admins. Barkeep49 (talk) 20:19, 25 January 2024 (UTC)
Community discussion (Remind, warn, admonish)
Maxim sums up my opinion well, this has been my understanding of how the words are used for a long time now and I can see no harm from codifying it. Thryduulf (talk) 16:55, 25 January 2024 (UTC)
I'm not sure if "Reminded" should even have a severity, a plain reading of it seems to avoid implying that anyone has done something wrong. Unlike the others, it is often used in a general sense regarding broad principles (Editors are reminded that...
) rather than referring to specific editors. It might be better to leave it as Severity 0 and bring back Cautioned as the mildest severity, as that at least has the connotation that there's dangerous territory ahead. The WordsmithTalk to me 19:39, 25 January 2024 (UTC)
I took some time to review the previous decade of use of verbs for non-remedies (I have a spreadsheet...). The committee might consider further review than the votes above.
For groups of users:
- Remind shows up across the whole decade and is retained here, so no further comment.
- Urge and invite show up in 2014 and 2015 but have otherwise fallen into disuse.
- Caution shows up in 2014 and no later, so it seems also to have fallen into disuse.
- Advise shows up twice, once in 2022 and once in 2019. It should be considered a bit further.
- Encourage shows up about a dozen times from 2014 to 2017. It should be considered a bit further.
For single users:
- Caution shows up once for an admin in 2018, but has otherwise fallen into disuse. I support dropping any future use as there is sufficient intent between remind and warn.
- Remind and warn show up across the whole decade and are retained in this proposal. For remind there is mixed use for admins and non-admins. Warnings are almost exclusively used for non-administrators (with only 2 admin uses). Consider whether the use of the word merits restricting to non-admins.
- Admonish: Use has shifted, ignoring one specific case in 2019, from any user to mostly administrators. It appears to be mixed before that. This probably merits more discussion as to whether it should be restricted only to use for admins.
Izno (talk) 19:57, 25 January 2024 (UTC)
- Yeah, I feel admonish is generally used more specifically for admins as a final warning, i.e. next time a similar level offense occurs a desysop will likely happen. Galobtter (talk) 20:40, 25 January 2024 (UTC)
- I wonder if it's a statistical artifact. There are two "modes" of case: one is administrator conduct, and the other is a lot of bad behaviour in a given topic area. When we have a non-admin who gets sanctioned, it is more likely to be in a topic-related case, so an interaction ban, topic ban, or a site ban are likely remedies. For an admin, it's the admin conduct cases, so we'll end up with a desysop or an admonishment. Note that very often the admonishment is the lesser proposed remedy, even though it rarely (if ever?) passes. Maxim (talk) 20:50, 25 January 2024 (UTC)
- The spreadsheet was done as a count of specific remedies rather than a count of the number of cases, e.g. "User 1 is reminded." got a specific line. It might be a statistical artifact indeed, but as I noted we have continued to use the words warn and remind before, during, and since each of the uses of the word admonish. Izno (talk) 00:10, 26 January 2024 (UTC)
- I wonder if it's a statistical artifact. There are two "modes" of case: one is administrator conduct, and the other is a lot of bad behaviour in a given topic area. When we have a non-admin who gets sanctioned, it is more likely to be in a topic-related case, so an interaction ban, topic ban, or a site ban are likely remedies. For an admin, it's the admin conduct cases, so we'll end up with a desysop or an admonishment. Note that very often the admonishment is the lesser proposed remedy, even though it rarely (if ever?) passes. Maxim (talk) 20:50, 25 January 2024 (UTC)
- If an administrator behaves poorly in a non-administrative task, and such behaviour would ordinarily result in a warning to a non-administrator, I do not feel there should be an arbitrary restriction that would prevent a warning to be given. Although I appreciate that some editors feel that administrators should meet a higher standard of conduct, I do not feel this should preclude warning the administrator about their poor behaviour, even if the standard being used is more stringent. isaacl (talk) 22:21, 25 January 2024 (UTC)
- @Barkeep49, the core of it is that I am pretty sure three layers of "non-remedy" verbs are unnecessary to express the range of non-remedy opinions of behavior ArbCom might have, and now is the time to decide they are(n't).
- Remind is a good word to have regardless of whether there is another one or five - its clear intent is "we noticed it, be a better human" and less the other two, which is clearly "knock it off". So I don't think that merits too much discussion.
- Regarding warning/admonishment: The dictionary definition of an admonishment uses the word warn, sometimes weakly and sometimes lukewarmly, but it is not indicated in the plain meaning as being a stronger warning.
- Choosing to use warning and admonishment for the kind of editor who shows up (admin/non-admin), or perhaps the rights being employed that earned the remedy (say, A/B/CU/OS rights in the admonish pile and the others in the warn pile) is a nice way to flatten the number of "stop that"s. It also gives them distinct meanings (here, you did a bad editing thing | here you did a bad adminning thing), since right now it's just arbitrary tiering of most-least severe.
- As it happens, in the review I did there were some uses of adverbs such as strongly warn, so if ArbCom really needs to reach for a strong warning rather than just a warning, it might consider instead using strongly.... Izno (talk) 00:05, 26 January 2024 (UTC)
- Personally, I would prefer to minimize the amount of jargon used, and so would not prefer using different verbs solely based on whether or not the action under discussion was an administrative or non-administrative task. I think it would be better to ensure that the behaviour in question was clearly described as an administrative or non-administrative action, in cases where there is ambiguity. isaacl (talk) 00:19, 26 January 2024 (UTC)
- I agree. Right now admonish kind of sticks out as clear jargon. Izno (talk) 00:25, 26 January 2024 (UTC)
- If we were to keep the three-level system, would you prefer "reprimanded" or "rebuked" over "admonished"? I've personally always felt that "admonished" is sterner than "warned", but wanted to hear your thoughts on these alternatives. Sdrqaz (talk) 03:58, 26 January 2024 (UTC)
- Admonished is jargon, but at this point it's so firmly entrenched in Wikipedia that changing it would cause far more confusion than it would solve. The WordsmithTalk to me 04:00, 26 January 2024 (UTC)
- That's nonsense. Even if it's supposedly "entrenched" it's still not clear. Which one's the more serious, I assume it's "warned"? But I couldn't be certain. A different word is essential if we're codifying this formally. — Amakuru (talk) 08:28, 26 January 2024 (UTC)
- There is a cost to changing precisely because some people do understand the current words and there are a bunch of cases which use them. Picking different words doesn't mean those new words will be universally understood either. So I think the best solution is to be explicit about our intent by passing this motion. Barkeep49 (talk) 13:34, 26 January 2024 (UTC)
- Assuming a three-level structure, perhaps the third level could include two synonymous terms, such as "admonish or strongly warn". This would reflect past historical use, but also allow the arbitration committee to transition to a term where an intensifier makes the relationship to the previous level clear. This would avoid the problem with different people having different connotations based on their experiences. isaacl (talk) 17:04, 26 January 2024 (UTC)
- There is a cost to changing precisely because some people do understand the current words and there are a bunch of cases which use them. Picking different words doesn't mean those new words will be universally understood either. So I think the best solution is to be explicit about our intent by passing this motion. Barkeep49 (talk) 13:34, 26 January 2024 (UTC)
- That's nonsense. Even if it's supposedly "entrenched" it's still not clear. Which one's the more serious, I assume it's "warned"? But I couldn't be certain. A different word is essential if we're codifying this formally. — Amakuru (talk) 08:28, 26 January 2024 (UTC)
- I am not in favor of three. I think two is all that is necessary: remind and warn. Anything else and you're likely looking at an actual remedy instead as a serious option. I also agree with Amakuru: this is an opportunity to improve the situation, rather than merely reflect the past. Dropping the clear jargon and apparently ENGVAR-confused word makes a lot of sense as it doesn't appear to aid in the understanding for anyone. If you really must have a third tier, just bake it into the second with a strongly.
- Of the words that have so far been thrown around assuming some sort of third tiering, I think I'd prefer censure just after a strongly warn.
- But we're up to a passing motion at this point, so at least it's on paper I guess... Izno (talk) 21:35, 26 January 2024 (UTC)
- Admonished is jargon, but at this point it's so firmly entrenched in Wikipedia that changing it would cause far more confusion than it would solve. The WordsmithTalk to me 04:00, 26 January 2024 (UTC)
- If we were to keep the three-level system, would you prefer "reprimanded" or "rebuked" over "admonished"? I've personally always felt that "admonished" is sterner than "warned", but wanted to hear your thoughts on these alternatives. Sdrqaz (talk) 03:58, 26 January 2024 (UTC)
- I agree. Right now admonish kind of sticks out as clear jargon. Izno (talk) 00:25, 26 January 2024 (UTC)
- Personally, I would prefer to minimize the amount of jargon used, and so would not prefer using different verbs solely based on whether or not the action under discussion was an administrative or non-administrative task. I think it would be better to ensure that the behaviour in question was clearly described as an administrative or non-administrative action, in cases where there is ambiguity. isaacl (talk) 00:19, 26 January 2024 (UTC)
I think there should be a comma after remedies
. No opinion on the capitalization of the "A" in "Arbitration". — Red-tailed hawk (nest) 00:01, 26 January 2024 (UTC)
- I have no problem with a sliding scale, but better words need to be chosen. "Warn" and "admonish" sound kind of similar and I have no idea which of the two is supposed to be the more severe. Arbcom has a duty to the community to be clear and unambiguous, rather than using its own jargon. — Amakuru (talk) 08:24, 26 January 2024 (UTC)
- Censured? Valereee (talk) 15:22, 26 January 2024 (UTC)
- "Admonish" is a worst-case choice for this purpose. It's relatively uncommon and has unclear and widely-varying connotations, possibly ENGVAR-based: compare, say, dictionary.com implying a severity similar to "remind", and oed.com as well past "warn". Formalizing it improves things somewhat and there's no help for the usage in old cases, but I'm fairly confident that none of "reprimand" or "rebuke" or "censure" have this sort of ambiguity in any variant of English. —Cryptic 15:52, 26 January 2024 (UTC)
- While we're on the subject of being pedantic, here's my deal: can I get you guys to set out a canonical capitalization for yourselves? Here are the cases, along with the way I tend to capitalize them -- are these correct?
New decisions have been announced by the Arbitration Committee
She was elected to the position of arbitrator
Three arbs endorsed and one arb opposed
The Committee issued a motion on Saturday
Those editors are subject to an arbitration ruling
That topic area was first arbitrated in 2016, and they may arbitrate it again soon.
- jp×g🗯️ 17:46, 26 January 2024 (UTC)
- @JPxG:
- "Arbitration Committee" (or, in short, "the Committee") is a proper noun and therefore capitalized.
- "arbitration" is not.
- "arbitrator" is also not, except possibly (but discouraged by me) as a title for a person right before their name ("Arbitrator L235") (see Wikipedia:Manual_of_Style/Capital_letters#Titles_of_people).
- See also: User:L235/Arbitrator or arbitrator KevinL (aka L235 · t · c) 18:38, 26 January 2024 (UTC)
- @JPxG: