From Wikipedia, the free encyclopedia
Main case page ( Talk) — Preliminary statements ( Talk) — Evidence ( Talk) — Workshop ( Talk) — Proposed decision ( Talk)

Case clerk: MJL ( Talk) Drafting arbitrators: Cabayi ( Talk) & GeneralNotability ( Talk) & SilkTork ( Talk)

Behaviour on this page: Arbitration case pages exist to assist the Arbitration Committee in arriving at a fair, well-informed decision. You are required to act with appropriate decorum during this case. While grievances must often be aired during a case, you are expected to air them without being rude or hostile, and to respond calmly to allegations against you. Accusations of misbehaviour posted in this case must be proven with clear evidence (and otherwise not made at all). Editors who conduct themselves inappropriately during a case may be sanctioned by an arbitrator, clerk, or functionary, without further warning, by being banned from further participation in the case, or being blocked altogether. Personal attacks against other users, including arbitrators or the clerks, will be met with sanctions. Behavior during a case may also be considered by the committee in arriving at a final decision.

Comments by Robert McClenon

Since there was discussion about whether non-Latin usernames are permitted, and it was restated that they are permitted, I think that a principle to that effect would be helpful.

I disagree with finding 6b that Scottywong's comments were racist. Some of us on the English Wikipedia are too quick to label unpleasant or offensive conduct as "racist", which is not only sloppy, but reduces the appropriate reaction of condemnation with respect to real racism. I don't disagree with the inclusion of finding 3.2.7 among the options, only with enacting it.

In American political discourse, 'racist' and 'socialist' are almost mirror image insults, both of which are used without any real meaning except to be insulting. A mirror reverses left and right, and 'socialist' is used as a meaningless insult by right-wing persons against left-wing persons, and 'racist' is used as a meaningless insult by left-wing persons against right-wing persons. We should be careful to avoid misusing words in the way that the American left does. (I don't think that we are at risk of making the error of the American right.)

I support remedy 2b, a simple admonition without a complicated consequences clause. Robert McClenon ( talk) 21:57, 5 July 2023 (UTC) reply

There is a FoF that "ಮಲ್ನಾಡಾಚ್ ಕೊಂಕ್ಣೊ's non-Latin username complies with Username policy" which seems clear enough. And we have the principles of Expressing concern and No personal attacks, which cover what Scottywong was doing when speaking to ಮಲ್ನಾಡಾಚ್ ಕೊಂಕ್ಣೊ in a derogatory fashion regarding their username. SilkTork ( talk) 06:23, 6 July 2023 (UTC) reply

As mentioned above, the term 'racist' is overused and misused in American political discourse, and should be avoided when possible, both because many editors of the English Wikipedia are Americans, and because many editors of the English Wikipedia are not Americans. I therefore concur with changing Finding of Fact 6b to 'xenophobic', which is less politically loaded. Robert McClenon ( talk) 14:43, 6 July 2023 (UTC) reply

Remedy 4 does have a practical effect, if the other editor remains banned. It prevents Scottywong from commenting on or taking administrative action against any sockpuppets of the banned user. For that reason, it should be supported. It isn't just a fallback. Robert McClenon ( talk) 23:31, 6 July 2023 (UTC) reply
I think that is a subtle and useful point. SilkTork ( talk) 10:23, 9 July 2023 (UTC) reply

Comments by jc37

Proposed Principle 3.

The last word is "prohibited".

When I read that sentence, it seems semantically "off". I suppose things that are contrary to policy are more than merely frowned upon, certainly. But "prohibited" makes it sound like the full weight of punishment falls for even a single initial act of incivility, which, I don't think we do here.

Can we replace "prohibited" with "unacceptable"? (The word used in WP:UNCIVIL.)- jc37 22:20, 5 July 2023 (UTC) reply

"Prohibited" is standard wording. I took that principle from Wikipedia:Arbitration/Index/Principles. My reading is that "unacceptable" has the same meaning as "prohibited" in that these are things we do not accept, though I agree with you that prohibited has a more serious emphasis than unacceptable, which is probably why it is preferred in ArbCom principles. SilkTork ( talk) 06:17, 6 July 2023 (UTC) reply
Thank you for clarifying.
It isn't about "serious emphasis", though. It's just inaccurate in how we - in common practice - address issues of In-Civility. We don't "prohibit" them, we find them "unacceptable".
Please pardon the humour here, but if incivility was "prohibited" on Wikipedia, AN/I would likely be a much quieter place : )
So anyway, perhaps that entry in Wikipedia:Arbitration/Index/Principles should be updated. - jc37 07:29, 6 July 2023 (UTC) reply
Unacceptable means we don't allow it. However, it has long been recognised that incivility is difficult to police. SilkTork ( talk) 08:15, 6 July 2023 (UTC) reply
Yes, exactly. on both counts. - jc37 08:16, 6 July 2023 (UTC) reply

Also (separate issue), per Robert McClenon above, the title of that section is more of an accusation than the text states. There is a rather big difference between "...in a manner that has been perceived as racist..." and "...in a racist manner...". - jc37 22:24, 5 July 2023 (UTC) reply

I guess wikt:xenophobic is better? Though, even looking at the definition, I would be hard-pressed to give a concrete definition to apply it to any particular situation. It's such a broad term. But I'll agree with Robert McClenon above, that it's better than it was, for the various reasons we both noted, and more. - jc37 15:32, 6 July 2023 (UTC) reply
Actually, thinking about it, it might be a good idea to link "xenophobic" to its wiktionary definition (as I did above). - jc37 15:35, 6 July 2023 (UTC) reply

Note: User:Scottywong has apparently done an admin version of MeatBall:GoodBye. Self blocked. Deleted user page and user talk page. And protected both. I only reduced the protection on the talk page (for a month). I'll leave the rest to others to decide. - jc37 09:04, 9 July 2023 (UTC) reply

And User:L235 also did so in the exact same minute... - jc37 09:09, 9 July 2023 (UTC) reply
Thank you for noting. I have to say that I empathize. I don't think that I'd want to contribute much after being the subject of an ArbCom case, favorable end or not. That said, Scotty should know that I'm grateful for the time he's spent with us on Wikipedia and the effort and passion he's shared with us. I hope he manages to look back on Wikipedia fondly, and that he perhaps finds his way back. In any event, all my best wishes. KevinL (aka L235 · t · c) 09:10, 9 July 2023 (UTC) reply

Unintentionally xenophobic?

A question for GeneralNotability, Beeblebrox, and really for all the Arbitrators:

"How can one be unintentionally Xenophobic?"

It would seem that intention is the key factor.

Xenophobia - is the fear of "something". So are we saying that he is "unintentionally" afraid?

I'm not being intentionally obtuse, I think I understand how you all seem to want the phrase to apply.

But I don't think it means what you think it does, in the way that you are applying it.

That others may have said that they may have seen his words as if he was xenophobic, sure. That may or may not be a finding of fact.

But what you are doing is essentially falling into a pit trap which is similar to attempting to determine of someone has used Hate speech.

And for that, I believe, you need motive and intent.

And honestly, from what I can tell, arbcom has shown neither motive nor intent of Scottywong for such.

So I guess my second question for you all is: "Do you really want to go on the record and make such an accusation based upon the evidence at hand?" - jc37 08:41, 9 July 2023 (UTC) reply

Pinging all the active arbs: User:Beeblebrox, User:Cabayi, User:CaptainEek, User:Enterprisey, User:GeneralNotability, User:Guerillero, User:L235, User:Primefac, User:SilkTork, User:Worm That Turned, User:Wugapodes.

That arbcom is placing such labels in such a way is really, really, concerning. - jc37 08:55, 9 July 2023 (UTC) reply

User:L235 - Just wanted to note that your usage of "...derogatory belittling language...", seems, in my estimation, to be more on target for what you all are trying to convey. - jc37 09:25, 9 July 2023 (UTC) reply
I think the debate around racism and now xenophobia has, for me, tended to detract somewhat from the main issue which is that Scottywong was behaving in a combative and derogatory manner. I was comfortable with the finding that Scottywong spoke to ಮಲ್ನಾಡಾಚ್ ಕೊಂಕ್ಣೊ in a derogatory fashion. The alternative finding was offered because the issue of racism had been discussed, so it was appropriate to get that out into the open, rather than ignore it. Racism is such a loaded term carrying a huge baggage of cultural history. It can be quite inflammatory to speak in a manner that can be perceived as racist. And quite inflammatory to accuse someone of being racist - an accusation that can be hard to shake off or deny. Changing the title of the finding to xenophobia seemed to me to be appropriate, as it took us away from the loaded language of being racist that can be hard to defend and also hard to define, while keeping the factual information that Scottywong's actions were perceived by some as being racist. Though the xenophobia word comes from the Greek for fear of outsiders, it is understood today to include other behaviours such as dislike or hatred. And people can and do divide the world up their own way into those who are insiders and those who are outsiders. That's something we all tend to do. Here on Wikipedia, though, we try to be an inclusive as possible, so any behaviour which may make someone feel uncomfortable editing here (because they are from a different country, gender, political or religious belief, or because they have not registered an account) is discouraged. SilkTork ( talk) 11:06, 9 July 2023 (UTC) reply
Like I said, I think I understand what was intended. However, as you note, this is still applying a label to the person, not merely to someone else's interpretation of their actions.
None of us can read minds. We better be very very certain, based upon evidence, before we decide that the person IS xenphobic, racist, or whatever other label we intend to apply. There's a big difference between looking at something and saying "Hey, that looks like X", and saying "Hey, you are Z because you said something that looks like X".
Arbcom has seen plenty of analogies to 1984 over the years, no doubt, so I am not intending to just add to the pile. I just really want you all to think about what you are doing if you do this.
This has repercussions on all editors, not just admins, going forward. - jc37 11:19, 9 July 2023 (UTC) reply
I thought we were applying the label to the action not the person: "Scottywong speaks to ಮಲ್ನಾಡಾಚ್ ಕೊಂಕ್ಣೊ in a xenophobic manner". SilkTork ( talk) 11:29, 9 July 2023 (UTC) reply
The comments in the text are being labelled as "perceived" to be such. But the title labels them directly. If a person says hate speech, then they are labelled as someone who hates. And if you look at the comments of the arbs voting on that (and other sections), you can see examples of that.
Add "...perceived to be..." in the title, and it at least "helps", I guess?
But are we really comparing what - to my eye at least - looks like: someone merely being a jerk to someone else on the playground because they decided to play with the sand in their sandbox - to hate speech? "you're a big meanie, and, and, and, and you wear funny clothes too." - It's childish and wrong, but I just think everyone may be going just a little too far here.
I don't think anyone would argue that there is not genuine bigotry and hatred out there in the world today. But are we sure that this really is an example of that? Once labelled as a xenophobe, Scottywong would never be able to lose that sign around the neck. And it would be placed there by Arbcom. - jc37 12:19, 9 July 2023 (UTC) reply
It's easy not have your comments called out as xenophobic, just don't make remarks that come across that way. The remarks he made were very deliberate in their intent and he very clearly purposely chose not to restrain himself to commenting on the actual issue, the edits, and instead went after the editor as a person, including belittling their username and by extension their ethnicity. So, I agree with you that it was childish and wrong. Scotty is not a child. Beeblebrox ( talk) 16:41, 9 July 2023 (UTC) reply
"...and by extension their ethnicity..." - actually, that's an act of reading that into his comments. We simply do not know that. And, maybe I've missed it, but I don't see evidence to support that interpretation. If we have circumstantial evidence, so does he to counter it - his wife.
This is a website, and Arbcom is well within its purview to remove the ability for someone to edit here. Or to have extra tools or responsibilities here.
But labeling someone xenophobic without solid evidence, but rather merely just interpreted evidence "by extension"? You can still achieve all the remedies of this case, without doing that. - jc37 16:52, 9 July 2023 (UTC) reply
(de-dent) Also: "...just don't make remarks that come across that way..." - I can't control how you are going to interpret something that I say. I agree that we have rules on collegiate civility, and I don't think anyone - including him - thinks that his remarks were appropriate. But we are an international website of many cultures. I don't know about you, but I am fairly certain that I am not fully knowledgeable of every idiom for every culture out there. And that without diving into the nonsense of internet memes of the moment and all the rest. These things really need to be treated on a case-by-case basis. And assessed based upon evidence, not merely because someone interpreted something you said with more into it than you intended. I don't think any one here is meaning to do harm, I think everyone is trying to do their best for Wikipedia. But sometimes when you spend enough time looking into dark shadows it's not difficult to see more, even a little more than was intended to be there. - jc37 17:06, 9 July 2023 (UTC) reply

Comments by Legoktm

@ SilkTork: there are chronology issues in the "Prior disputes between ಮಲ್ನಾಡಾಚ್ ಕೊಂಕ್ಣೊ and Scottywong" FoF. The VPP RfC was in Febuary 2023 (not 2022). The June 2022 BOTN discussion preceded that, and the Feb. 2023 BOTN discussion is what led to the RfC. I also provided evidence about BOTN comments in June 2023 that IMO would fall under "continued to make complaints", so I'm curious as to why that wasn't included. Legoktm ( talk) 23:24, 5 July 2023 (UTC) reply

Thanks for the heads up about the chronology. The June 2023 complaint was made after the incident, so doesn't fit into a finding of "prior" dispute. And we have a finding regarding Scottywong's conduct during the case, which speaks for itself. SilkTork ( talk) 06:06, 6 July 2023 (UTC) reply

Comments by The person who loves reading

For this sentence "The have been active in administrative areas and they have helped create multiple tools used by the community, as detailed on their userpage." on Proposed Findings of Fact 1, the first word may need to be changed to "They" because "The" seems like a spelling error. The person who loves reading ( talk) 17:19, 6 July 2023 (UTC) reply

 Done Cabayi ( talk) 17:49, 6 July 2023 (UTC) reply
Thank you very much! The person who loves reading ( talk) 20:43, 6 July 2023 (UTC) reply

Comments by Izno

I agree with Barkeep in whole regarding principle 7. (Is a recused arb still an arb for the purposes of editing the PD?) Izno ( talk) 17:48, 6 July 2023 (UTC) reply

@ Barkeep49, I don't see that it says that anywhere in ARBPOL/PRO. Actually I don't see anywhere that recusal requires that one act as a normal editor, just that they are not counted for votes. Weird. Izno ( talk) 18:09, 6 July 2023 (UTC) reply

Comments by Barkeep

@ Izno: recused arbs have to follow editor rather than arb rules, so no editing the PD, comments only in discrete sections here, etc etc. Since I'm inactive arb rules still apply for me (because I could choose to active for the entire case or for parts). Barkeep49 ( talk) 18:06, 6 July 2023 (UTC) reply

Just speaking from Arb wisdom handed down over time. My concretely ARBPOL for recusal links to wiktionary which defines it as An act of recusing; removing oneself from a decision/judgment because of a conflict of interest and so acting like an arb does not seem comptabile with removing oneself from decision/judgement. Barkeep49 ( talk) 18:13, 6 July 2023 (UTC) reply

@ MZMcBride: ARBPOL says Requests for recusal after a case has entered the voting stage will not be granted, except in extraordinary circumstances. What do you see as the extraordinary circumstances here? Barkeep49 ( talk) 18:06, 6 July 2023 (UTC) reply

MZM: Who cares what that policy page says? Well I do. I did as a member of the community and I do even more as an elected arb. ArbPol is not some obscure policy page when it comes to ArbCom. It is literally the policy which authorizes, and importantly to me, limits the powers of ArbCom. It is community ratified and indeed the community recently exercised its power to amend it. So yes it's important to me as an arb, even one who is inactive on this particular case, that it be followed and if you don't have extraordinary circumstances then all I can do is offer sympathy that you missed the chance for this discussion; which I will note was raised during the case request and was seriously handled despite not strictly following the letter of the policy in that the request for recusal happened at the case request and not at the arbs individual user pages. That to me is appropriate commonsense with the application of the policy, not just outright ignoring the plain meaning of its words. Barkeep49 ( talk) 18:26, 6 July 2023 (UTC) reply
As an arb who is active on the case I believe I can barge in and edit in your section to say I agree that a recused arb should not be editing the PD at all. Beeblebrox ( talk) 16:43, 8 July 2023 (UTC) reply


Comments by MZMcBride

Hi. I'm not super involved in wiki matters these days, but glancing at this case and skimming some of it, it's absolutely wild to me that Primefac isn't recused here.

ಮಲ್ನಾಡಾಚ್ ಕೊಂಕ್ಣೊ has been indefinitely blocked and globally locked for being a long-term abusive user. He's made millions of pointless edits with his bot, but when you look at how and why he was able to make so many stupid edits with a bot account, it was the constant rubber-stamping by Primefac (cf. Wikipedia:Bots/Requests for approval/MalnadachBot 10, Wikipedia:Bots/Requests for approval/MalnadachBot 9, Wikipedia:Bots/Requests for approval/MalnadachBot 7, etc.). Primefac even calls him a "trusted operator" in one of the requests for approval and speedily approves it.

Scottywong is being put on trial for responding to a user—and that user's millions of unnecessary and pointless edits—who we all now agree was acting in very bad faith and was acting abusively. This to me feels like an extremely mitigating factor in this case.

But what I really can't wrap my head around is that Primefac directly enabled this bad actor for years and is now sitting as a judge in this case? What on earth. I think even a kangaroo court like ArbCom could see how this is unacceptable. -- MZMcBride ( talk) 17:58, 6 July 2023 (UTC) reply

I think you should take some time to evaluate your reply here, Barkeep49. When someone raises a very clear conflict of interest and ethical breach, your response is to quote some obscure policy page? Who cares what that policy page says, the issue is what I laid out: Primefac directly enabled this bad actor's behavior for years. Scottywong is not the only user who was annoyed by these pointless edits. And every time someone like me investigated how these millions of edits were continuing, it pointed back to Primefac's approvals. -- MZMcBride ( talk) 18:15, 6 July 2023 (UTC) reply
If this were about the bot edits, or Malnadach's behaviour (outwith the socking), then you are absolutely correct and I would be recusing. However, the sockpuppetry as it relates to the case is nothing more than background. As you say, there are quite a few editors who find Lint fixing to be problematic, and yet Scottywong is the only one with an ArbCom case against them. This is not because of who he was arguing with but how he was arguing with them. FoF 5 is the only proposal that comes anywhere near the sphere of where I would consider myself to have a conflict, and it is such a straight-forward statement I see no reason to recuse from the entire case because of it. Primefac ( talk) 18:30, 6 July 2023 (UTC) reply
  • On the point of policy, it was raised by Folly Mox that Primefac and Izno recuse during the request stage. I made a comment on the request page that "As regards the request for Izno and Primefac to recuse, I'm not convinced that is needed as I don't see inappropriate contact between those two arbs and Scottywong. The discussions about Malnadach's bot, including approving of the bot, appear to be part of normal Wikipedia activity. If there are examples of friction between the two arbs and Scottywong, then I am sure they would recuse without being asked." And I said something similar during the internal ArbCom discussions on the case. So the matter was raised, discussed, and Izno decided to recuse while Primefac did not, and this was accepted by the Committee. So this has already been dealt with. The case was about the conduct of Scottywong, not the conduct of Malnadach. SilkTork ( talk) 19:02, 6 July 2023 (UTC) reply

Comments by Scottywong

I feel that FoF #8 draws unfair conclusions and makes incorrect assumptions about the evidence that I submitted in this case. The FoF accuses me of blaming Malnadach for my own poor behavior, and I believe that careful examination will show that that never happened. While part of my evidence did focus on Malnadach's actions (in an attempt to provide context for the whole situation), I believe that I was very clear that I was not attempting to shift blame. My evidence included statements like "Regardless of what we learned later about Malnadach's status as an LTA sockmaster, my comments were unambiguously inappropriate." and "While it's not ok to respond to this behavior in an unseemly way, it's also not ok to intentionally irritate other editors to provoke a response that can be exploited." (emphasis mine)

I had already apologized for my behavior on four separate occasions prior to the case, and didn't feel that it was appropriate or necessary to devote my evidence submissions in this case to crafting a fifth apology. I realize that what I said to Malnadach was inappropriate, I've admitted that several times, I've apologized for it, and I've committed to doing my best to not repeat it. I'm not sure what else I can say. I apologize if I was expected to devote my evidence to restating all of the things that I already said prior to the start of the case. Given the bombshell that dropped about Malnadach's true identity shortly before the start of the case, I decided to devote part of my evidence to enshrining that information into the case. But that doesn't mean that I believe that my statements are no longer inappropriate, and I think I was quite clear about that in my evidence.

It also doesn't feel particularly fair to be admonished for "attacking the character" of Malnadach in my evidence. Firstly, I don't feel like the factual evidence I submitted is "attacking" anyone, and secondly, an editor who turned out to be perhaps the most prolific LTA sockmaster in the history of Wikipedia is arguably deserving of some condemnation. I see now that there are some arbs that seem to be doubting the veracity of the private CU evidence that led to Malnadach's block, and if that block turns out to be mistaken, I'd be happy to retract any of the conclusions that I drew from it. —⁠ScottyWong⁠— 19:53, 6 July 2023 (UTC) reply

There are two sentences that popped out to me:
  • we can presume that Malnadach's choice to use a username ... could have been a conscious decision designed to subtly irritate other editors without violating policy
  • the purpose of making these specific edits was to intentionally irritate me
These are, I believe, phrases that fit the bill of what you are claiming you did not do. Primefac ( talk) 08:47, 7 July 2023 (UTC) reply
Fair enough. I still think there's a difference between providing context and shifting blame. But that FoF already has enough support to pass, so it's probably not worth arguing it any further. —⁠ScottyWong⁠— 14:39, 7 July 2023 (UTC) reply

@ Newyorkbrad: Thank you for saying this. I refrained from saying anything else because it seems every time I write anything in an attempt to defend myself, another arb jumps on the desysop bandwagon and votes to desysop me for "not dropping the stick" or "continuing the bickering". Even though there's virtually no chance that I'll emerge through this case with bit intact, I'm feeling quite discouraged from speaking up in my own defense, and I think it sets a chilling precedent for the future where editors will be more likely to refrain from submitting evidence on their behalf. Many of the arbs who have voted so far are making it clear that I would have fared better if I hadn't submitted evidence at all. FoF #8 is basically being used to desysop me for presenting the wrong evidence at Arbcom, and/or for making any attempt to defend myself against the accusations that were made. (Again, to be crystal clear, when I say "defend myself", I'm not implying that my comments to Maladnach weren't inappropriate, I'm simply trying to put everything into perspective and provide appropriate context while maintaining that my remarks were unambiguously inappropriate.) Therefore, @ Cabayi: you won't find any attempt to provide a justification or excuse for my inappropriate comments, because they were inexcusable. I can only offer that my intent was to communicate that Maladnach's username is difficult for English speakers to read/write, and the words came out wrong. I did not intend to communicate that I hate Indians, or that I think Indian culture is stupid, or that the Kannada language is dumb, or that non-native-English speakers should stay off the English Wikipedia, or anything along those lines. I realize how easily my words could be interpreted as xenophobia or even racism, and I regret that. My only defense can be to provide context for the situation (so that you can understand why I was in an annoyed/frustrated state at the time), and describe the intent behind my inappropriate statements. I never intended to provide evidence with the implication that "well, Maladnach is now a blocked sock, therefore I'm off the hook and my inappropriate statements don't matter anymore". That's how my evidence was interpreted by SilkTork, and that seems to be the primary reason that I'm being desysopped (obviously, I'm being desysopped for my uncivil comments, but several arbs have made it clear that those comments alone didn't originally strike them as sufficient grounds for desysopping, while FoF #8 is what's pushing everyone into that camp). I'm sure that even posting this message will trigger a sixth arb to put the final nail in the coffin, but since that seems to be a foregone conclusion at this point, what does it matter. —⁠ScottyWong⁠— 14:49, 8 July 2023 (UTC) reply

@ Newyorkbrad: Regarding the i-ban, I think it's also important to note that I had no contact with Malnadach after the closing of the VP RfC that I started in February, and had no intention of initiating any further contact with Malnadach after that point, until Malnadach decided to edit pages in my talk archives. While I understand why there is support for an i-ban, the presence of this particular i-ban would not have changed my behavior regardless of whether or not Malnadach was blocked, because I had no desire or intention for further interactions with Malnadach. I even agreed to refrain from leaving messages on their user talk page, at their request. —⁠ScottyWong⁠— 16:59, 8 July 2023 (UTC) reply

@ Anomie: Beeblebrox was referring to a brief comment I made about how my wife is a non-native English speaker whose native language uses non-Latin characters. While I can see how that might give off "I'm not racist, I have black friends" kind of vibe, it was offered alongside a guarantee that a deep dive through my 16-year contribution history at WP will not uncover any pattern of xenophobic or racist statements, because that's simply not who I am. And indeed, no evidence was submitted that suggested a historical pattern of racist or xenophobic behavior on my part. The comments from a decade ago at the Manning case are the only thing that even comes close, but they were not racist or xenophobic, they were based on my ignorance (at the time) on the issues of gender, gender identity, and biological sex; and I have strongly renounced those comments years ago. —⁠ScottyWong⁠— 18:48, 8 July 2023 (UTC) reply

@ SilkTork: Respectfully, can I ask that the rhetoric be toned down a bit? I shudder at the thought of the consequences that Arbcom would have found appropriate if my comments to Maladnach had included something along the lines of "you appear to me to be like a parent or partner who berates and insults their child or partner in a disturbing manner." I don't know where all of this is coming from, but regardless of what you think of me, I don't think I deserved that. —⁠ScottyWong⁠— 18:58, 8 July 2023 (UTC) reply

I will strike that. I agree that it comes across as more disturbing than I intended. SilkTork ( talk) 10:16, 9 July 2023 (UTC) reply

Comments by Silcox

Considering the fact that most headers here are in the form of "Comments by [username]" - as they should - can someone please rename the section currently headered "Conflict of interest" to read "Comments by MZMcBride", considering the fact that McBride started that section and was the only non-arb to have commented there? Thanks, Silcox ( talk) 09:04, 7 July 2023 (UTC) reply

Yes. Primefac ( talk) 10:08, 7 July 2023 (UTC) reply

Comments by Newyorkbrad

The listing above reflects 11 active arbitrators (15 total minus 2 inactive and 2 recused), but the proposed decision page says there are 9 active arbitrators. Could someone please check this and if necessary, adjust the count and the required majority (is it 5 or 6?) accordingly? I suspect that the 2 recusals might accidentally have been subtracted twice. Regards, Newyorkbrad ( talk) 15:51, 7 July 2023 (UTC) reply

@ Newyorkbrad: I fixed this. You were right because I didn't realize recused arbs still count as active for the purposes of the {{ casenav/data}}. – MJLTalk 17:14, 7 July 2023 (UTC) reply
For the record, it turns out that the problem was not with how I inputted data into {{casenav}} but instead with {{ ACMajority}} (now fixed). To any onlookers, please ignore what I said here. – MJLTalk 18:26, 8 July 2023 (UTC) reply

I am concerned by proposed finding 8 and the fact that it is passing unanimously. "Continued misconduct during the case" findings have historically been reserved for outrageous behavior that went beyond all bounds of decorum for arbitration case pages and interfered with the orderly and collegial resolution of the case. Whether or not I or anyone else agrees with Scottywong's evidence about Malnadoch (I myself found Malnadoch's abuse history to be of at least some relevance in my acceptance-stage statement), I find it to be relatively routine in the context of a case, and certainly not worthy of a finding contributing to a desysopping. I fear that a troubling precedent is being set that will deter future accused parties from fully presenting their responses and defenses. Newyorkbrad ( talk) 14:16, 8 July 2023 (UTC) reply

Obviously I can only speak for myself, but it was comments such as those I quoted in the section above that moved me to support that motion. The statements made by Scottywong could very well have been made without the editorialising and speculation. It is not so much what was said as how it was presented that seems to be that which the Arbs take issue. Primefac ( talk) 14:41, 8 July 2023 (UTC) reply

As I think about it, the passing of an interaction ban based partly on comments within the case, followed by support for desysopping based on the need for the i-ban, also strikes me as unfair bootstrapping. There is no reason to believe that Scottywong would ever have had occasion, or the desire, to mention Malnadoch again if this case had not been opened and he had not been invited to present evidence in it. Newyorkbrad ( talk) 15:07, 8 July 2023 (UTC) reply

The iban was brouight up by the community first, and looked likely to pass when the matter came our way, so I feel that the community told us they thought the iban was warranted, and I agree. These two people should not be interacting. For me that it is automatic disqaualification from being an administrator. I can't speak for the other arbs but my support for the iban was not dependent on Scotty's bahavior during the case, which I feel was suboptimal and lacking in genuine self-reflection, but I agree it was not highly disruptive. Beeblebrox ( talk) 16:53, 9 July 2023 (UTC) reply

Comments by Lourdes

SilkTork, hi and hope you have been well (sorry, we've not communicated for a long time now). I understand your view on xenophobia. I also read Blade's statement (on the other talk page) about why asking a person to change names is not a representation of xenophobia. I can also understand the perspective that when non-Westerners with apparently complicated names written in foreign language interact with Westerners, they may be asked to change their names to simple English names written in Latin script so the Western world may understand this. Would an American, say "James", feel the same way if they were to visit, say, Iran and were asked to change their name to "احسن" or "بانڈ" and to use that for all communication? It's a rhetorical question, and just a point to ponder.... Thank you, Lourdes 05:59, 8 July 2023 (UTC) reply

I'm still considering the racist issue. For me it is offensive to sneer at and insult someone's username regardless of that person's background. And while I'm aware that being in a position where one is subject to abuse just for being "foreign" makes any such abuse more sensitive, I'm not entirely convinced that Scottywong was attacking ಮಲ್ನಾಡಾಚ್ ಕೊಂಕ್ಣೊ for being Indian. I suspect Scottywong was lashing out thoughtlessly at anything Scottywong didn't like about ಮಲ್ನಾಡಾಚ್ ಕೊಂಕ್ಣೊ, and if ಮಲ್ನಾಡಾಚ್ ಕೊಂಕ್ಣೊ had been culturally, genetically, and sexually the same as Scottywong, there would still have been abuse about the username and the rainbow colours on the userpage. As such I do prefer the amended title to the FoF and have been considering supporting it in that form because I do feel this sense of "otherness" about some of Scottywong's behaviour.
As regards name changes for ease of communication - well, that does happen frequently between cultures. And also within cultures: if parents give someone an awkward name, it will often be changed to ease communication - sometimes voluntarily, sometimes just accepted usage. I think there will be a balance between wanting to preserve one's culture and wanting to be sociable, and often a middle ground will be found where everyone is happy. SilkTork ( talk) 12:10, 8 July 2023 (UTC) reply

Comment by Floq

For me, it is not xenophobic to request (or even require, if we wanted to) that someone use a Latin script for their signature here; it might be against current policy to insist on it, but not morally wrong. What is xenophobic (for lack of a better term; "culturally obnoxious" maybe? Or the simpler "bigoted"?) is condescendingly mocking someone else's language with names such as "Mr. Squiggles". Let's not soft-peddle the insult by focusing on whether non-Latin scripts should be used; it's the culturally-focused insult that matters. -- Floquenbeam ( talk) 15:30, 8 July 2023 (UTC) reply

Comments by Anomie

I'm finding a lot in this proposed decision that makes me feel confused or disappointed.

  • I'm confused as to why Principle 2 exists. Principle 1 says all it does and more.
  • Same for Principle 3 when Principle 4 exists.
  • FoF 2 seems like a "dig up everything negative someone ever did" finding. Do we really need to bring up stuff from 10 years ago, that was already looked at by ArbCom back then, to reinterpret it using today's changed mores? I see a few Arbs seem uncomfortable with it too, but despite that they're still supporting (since otherwise there wouldn't be support for the conclusion they seem to feel compelled to reach).
  • The situation around FoF 6b is even more worrying to me.
    • The link for "in a manner that has been perceived as racist" doesn't support that assertion.
    • While "in a manner that has been perceived as racist" is true, it's also a very weak statement. Is punishing people based on an angry mob's "perception" really the direction we want ArbCom to go?
    • The comment by User:Beeblebrox seems to be coming from several decades ago, as I don't recall an "I have friends who are X" argument (did SW even say that?) being met with anything other than ridicule since well before Wikipedia existed. I'd say the pendulum today has swing to the opposite extreme, where claimed "perception" is all with no regard for intent, fact, or reason.
  • I agree with User:Newyorkbrad about FoF 8. I see SW apologizing repeatedly for his comments while also attempting to provide context regarding provocation by ಮಲ್ನಾಡಾಚ್ ಕೊಂಕ್ಣೊ. Unfortunately all the arbs who have commented seem to be rushing to misinterpret that instead as more attacks on ಮಲ್ನಾಡಾಚ್ ಕೊಂಕ್ಣೊ. While SW shouldn't have risen to the bait in the first place, that baiting was happening should be taken into account and SW attempting to point that out shouldn't be held against him.
    • User:Primefac's interpretation of SW's statement "the purpose of making these specific edits was to intentionally irritate me" strikes me as particularly egregious along these lines.

The scary part is that I can easily imagine myself in a similar position, as I've faced such things in my own non-wiki life and in my time here there have been plenty of cases where I've been brusque and several where I've been wildly misinterpreted.

I can't say I've lost trust in SW as an admin from everything I've seen here, although I do hope he really has learned to better hold his tongue when confronted with trying editors and to drop a stick once the horse is dead. But if this case goes in the direction it appears to be going, I will have lost trust in ArbCom's ability to look at the facts rather than their own prejudices (or peer pressure and fear of being accused of having prejudices). Anomie 17:04, 8 July 2023 (UTC) reply

Comment by Daniel

I haven't commented on an ArbCom case in a long, long time; but I haven't seen an ArbCom proposed decision - findings of fact which are then used for remedies - which gives me as much cause for concern as this one. This feels like a situation where a snowball rolling down a hill has continued to gather pace, to the point that it's out of control. While maybe not as acutely as Orangemarlin, I can see this decision being viewed quite dimly in the future. I echo Anomie's two final paragraphs in their 17:04 comment above wholeheartedly. Daniel ( talk) 09:32, 9 July 2023 (UTC) reply

Comment by Nardog

I'm a bit troubled by L235's reasoning for reluctance to desysop. Adminship is perceived as such a big deal in no small part precisely because the bar for desysopping is so high (and the process to get there so arduous). And the bigger a deal it is perceived, the less people are going to be willing to run for or support RfAs. Arbs should weigh not just whether you're going to lose one admin or one editor by desysopping, but how many others you're going to by not desysopping. Nardog ( talk) 11:43, 9 July 2023 (UTC) reply

@ Nardog: Good point, and apologies in advance for my long response—below are some of the things I pondered as I cast my vote.
For sure, I think we'd all be better off if RfA participants felt more comfortable taking a gamble and supporting a candidate they're not sure about, secure in the knowledge that if they change their mind later and lose confidence, it'd be quick and easy and painless for all involved to remove the sysop tools. And for sure, RfA is a big deal partly because sysops are hard to remove. Two notes though:
(1) I think sysop is a big deal only partly because it's hard to remove, and mostly because it's a role of trust and responsibility socially and wiki-politically. And in any organization where you have people in roles of trust and responsibility, it's a big deal. And no matter how formally easy it is to remove them, it's always a big deal to select new folks. (Not to mention, there's a limit on how easy you can make it in practice to remove them!) Just think of, say, your local school district's superintendent, if you happen to live in the US. Superintendents are generally appointed and removed by simple majorities of the local school board—the lowest level of procedural protections available. And yet, the fierce drama when selecting new ones, and especially when removing existing ones!
(2) I also think that ArbCom being more or less willing to desysop administrators, on its own judgment, is a very imperfect proxy for the community deciding that it has lost trust in editors. What I mean by this is that all would not be fine if arbs approached arbitration cases as "mini-reverse-RfAs": if we each decide at the end whether we would support the person at RfA anew, and vote to desysop if not. I'm less confident about this than #1—maybe the community would truly elect more admins if any sysop that has lost the confidence of ArbCom (as opposed to engaging in significant misconduct as determined by ArbCom) was immediately removed by us. But I don't think that's our charge from the community, and I don't think it would actually make the community much more likely at all to support RfAs. (Not taking a policy stance on a community alternative to desysopping here.)
As a whole, I'm not convinced that the current system within which we operate produces very good results at all. There's a significant human cost to the way we do things now: for potential RfA candidates, yes, but also for community members affected by bad or marginal sysop behavior, for those who have to bring and participate in ANI threads and ArbCom cases, and for admins themselves who are brought to ArbCom. I actually don't know if being an arb is the best way to address those issues, though, since we can only make changes at the very very end of the process, and as I note above those changes have only a limited effect on e.g. voting at RfA. System design level changes may be better placed than us arbs, but I know those are hard to pass.
Best, KevinL (aka L235 · t · c) 16:13, 9 July 2023 (UTC) reply

Comment from The Blade of the Northern Lights

I wholeheartedly agree with Anomie above, and I'd like to add one more point. Desysopping is a gigantic red welcome carpet for any troll to endlessly provoke and bait people, and since this particular abusive troll is long banned it's with essentially no consequences for the one who did the trolling. I can't think of a bigger wet dream for a serial abuser than seeing his trolling result in an admin having people publicly fling things at him for which are 10 years old and then be desysopped on those grounds. Oh no, an administrator got exasperated and let it show towards... a long-term abuser? Not that, anything but that. Seriously, absolutely no administrator that I see here (myself included, 11 years ago I told a Historicist sock to "kindly go fuck off") hasn't had a couple of moments. Dealing with trolls is enough without having targets painted on the backs of those who are willing to do it. Who the hell are any of you to talk down to anyone about "civility"? The Blade of the Northern Lights ( 話して下さい) 16:27, 9 July 2023 (UTC) reply

  • That ಮಲ್ನಾಡಾಚ್ ಕೊಂಕ್ಣೊ might have been an LTA was not in evidence at the time of Scotty's comments. ArbCom is still considering the appeal. That "this particular abusive troll is long banned" is still not incontrovertible.
  • "kindly go fuck off", while lacking civility, does not include a slight on the target's ethnicity/nationality/language. One is a UCoC vioation, the other is not. The UCoC wasn't a factor in the discussions but it helps to show the qualitative difference here.
  • Scotty apologised (good) then circled back to show that ಮಲ್ನಾಡಾಚ್ ಕೊಂಕ್ಣೊ was the cause. That Scotty feels that *any* comment from a user can trigger a xenophobic reply, and that he has no control over his reply, is a red flag.
  • There is no remedy between admonishment and desysop. It would be great if there were, but applying such a remedy would probably undermine the admin's credibility to function in the role. If you have a viable intermediate step I can assure you that the committee would eagerly receive it.
  • "Who the hell are any of you"... the folks that stood and got elected. If you're discontented, or even if you're not, stand at the next ArbCom elections. A wider choice of candidates can only be a good thing.
Regards, Cabayi ( talk) 10:56, 10 July 2023 (UTC) reply
To add to Cabayi's first point, Malnadach's actions could've been done by anyone (assuming sufficiently poor social awareness), so the fact that Malnadach turned out to be an LTA did not factor into my analysis. Enterprisey ( talk!) 01:44, 12 July 2023 (UTC) reply

Comment by Paradise Chronicle

I am somewhat pleased that personal attacks are taken seriously, (although I doubt that in this case they were racially motivated). But then also; are you aware that "personal attacks" happen quite frequently and no-one bothers to bring them up? How about Scottywong turned it around and pulled SilkTork before the Arbcom for what they wrote and decided to strike? Paradise Chronicle ( talk) 13:21, 19 July 2023 (UTC) reply

Hey, P. The case is already closed. Closed cases are discussed at WT:ACN. Regards! Usedtobecool  ☎️ 13:41, 19 July 2023 (UTC) reply