Wikipedia:Arbitration/Requests/Case/Jytdog/Workshop

Main case page (Talk) — Evidence (Talk) — Workshop (Talk) — Proposed decision (Talk)

Case clerk: TBD Drafting arbitrator: TBD

Purpose of the workshop

Arbitration case pages exist to assist the Arbitration Committee in arriving at fair, well-informed decisions. The case Workshop exists so that parties to the case, other interested members of the community, and members of the Arbitration Committee can post possible components of the final decision for review and comment by others. Components proposed here may be general principles of site policy and procedure, findings of fact about the dispute, remedies to resolve the dispute, and arrangements for remedy enforcement. These are the four types of proposals that can be included in committee final decisions. There are also sections for analysis of /Evidence, and for general discussion of the case. Any user may edit this workshop page; please sign all posts and proposals. Arbitrators will place components they wish to propose be adopted into the final decision on the /Proposed decision page. Only Arbitrators and clerks may edit that page, for voting, clarification as well as implementation purposes.

Expected standards of behavior

• 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 incivil or engaging in personal attacks, 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).

Consequences of inappropriate behavior

• Editors who conduct themselves inappropriately during a case may be sanctioned by an arbitrator or clerk, without warning.
• Sanctions issued by arbitrators or clerks may include being banned from particular case pages or from further participation in the case.
• Editors who ignore sanctions issued by arbitrators or clerks may be blocked from editing.
• Behavior during a case may also be considered by the committee in arriving at a final decision.

Motions and requests by the parties

Template

1)

Comment by Arbitrators:

Comment by parties:

Comment by others:

Template

2)

Comment by Arbitrators:

Comment by parties:

Comment by others:

Template

3)

Comment by Arbitrators:

Comment by parties:

Comment by others:

Proposed temporary injunctions

Template

1)

Comment by Arbitrators:

Comment by parties:

Comment by others:

Template

2)

Comment by Arbitrators:

Comment by parties:

Comment by others:

Template

3)

Comment by Arbitrators:

Comment by parties:

Comment by others:

Template

4)

Comment by Arbitrators:

Comment by parties:

Comment by others:

Questions to the parties

Arbitrators may ask questions of the parties in this section.

Proposed final decision

Proposals by Pudeo

Proposed findings of fact

Jytdog's behauvior

2) Jytdog's problematic behauvior has included aggressive WP:COI enforcement without due respect for the editors suspected of COI editing, inappropriate off-wiki contacts, egregious violations of WP:CIVILITY [1][2], templating the regulars and general uncooperativeness. Jytdog's hostility has driven away other editors from Wikipedia.

There is a previous 2015 ArbCom finding of fact: "Jytdog has engaged in edit warring [3], has belittled other editors, and has engaged in non-civil conduct. [4][5][6]" Jytdog has two previous indefinite blocks related to outing.

Comment by Arbitrators:

Comment by parties:

Comment by others:

Off-wiki contact with Beall4

2) Jytdog's unsolicited phone call to Beall4 constituted a serious breach of WP:HARASSMENT.

Comment by Arbitrators:

Comment by parties:

Comment by others:

Jytdog deceived others about the Beall4 incident

2) Jytdog gave false statements about the details pertaining to his inappropriate phone call to Beall4. He only back-pedalled after he had been called out several times. (Voceditenore's evidence/Premidated Chaos' evidence).

Comment by Arbitrators:

Comment by parties:

Comment by others:

Editors protected Jytdog as a so-called unblockable

1) Jytdog was subject to an extraordinary high number of AN/I complaints (wbm1058's evidence). Despite many legitimate complaints, Jytdog was never sanctioned, as his block log mostly constitutes of Oversight or ArbCom blocks. There'sNoTime's block for the latest incident resulted in a major pushback from Jytdog's supporters (Jusdafax's evidence). In some instances, editors who complained about Jytdog were sanctioned with a WP:BOOMERANG (Lepricavark's evidence/Sep 2018 ANI thread).

Comment by Arbitrators:

Comment by parties:

Comment by others:

Not sure what this adds. The evidence establishes that Jytdog's behavior is and has been repeatedly atrocious, but nobody has questioned either of the other two parties from the original case and nobody else is a party here at Case 2: The Recasening. The actions of other specific editors is largely out of scope. ~ Amory (u • t • c) 14:19, 29 March 2020 (UTC)

I disagree. This is the heart of the matter. This explains how we got here. This is why so much damage was done by one editor (as now thoroughly documented on the evidence page). Who's at fault in this entire debacle? The community, for enabling it. The 2018 ANI in particular looks really, really bad. If we are to improve as a community, we need to be honest with ourselves about unblockables. Levivich ^{[dubious – discuss]} 14:04, 30 March 2020 (UTC)

Proposed remedies

Note: All remedies that refer to a period of time, for example to a ban of X months or a revert parole of Y months, are to run concurrently unless otherwise stated.

Jytdog is site-banned

1) Jytdog2 is indefinitely blocked and Jytdog is not allowed to edit Wikipedia under any account.

Comment by Arbitrators:

This is certainly a possible outcome to the case. However, I don't agree with Coretheapple that Jytdog's 2018 statement that he was permanently retiring, in and of itself, means that he should never be allowed to return. An editor could sincerely believe that he or she would never want to edit again, and more than a year later change his or her mind. Our decision should be based on the editor's entire overall record of behavior. Newyorkbrad (talk) 03:07, 29 March 2020 (UTC)

I agree. People change their minds, mature and grow, see the light, however you want to put it. The question before us is about his behavior in the past, his insight into that behavior, the veracity of his pledges not to continue as before, and whether the totality of it warrants a permanent ban from us, not the other way around. Katie^talk 13:55, 29 March 2020 (UTC)

Comment by parties:

Comment by others:

The only choice in my opinion. Assuming good faith is a not a suicide pact. As mentioned in the General discussion section on this page, Jytdog has promised to improve his behavior after each block but has failed. That's what site-bans are for. --Pudeo (talk) 22:00, 28 March 2020 (UTC)

I believe the evidence clearly shows a siteban is the way to conclude this case, and thank Pudeo for this proposal. Jytdog avoided a full ArbCom case in 2018 by "retiring" because, as he stated himself, it was obvious what the result would be. Arguments in favor of a "time served" reinstatement of editing priviledges do not address that fact, and effectively allow Jytog to control when he leaves, and returns.

Proposals to topic ban and othewise attempt to correct his widely abusive behavior fly in the face of the failure of previous ArbCom warnings, blocks, topic bans, etc. I also again remind the Committee of the emails not made public, as discussed previously, which played a major role in the halted 2018 AbCom proceedings. Countless editor hours have been consumed in this matter alone. Enough is enough: simply ban Jytdog, and let's move on. Jusdafax (talk) 00:35, 29 March 2020 (UTC)

No heavy lifting required. In December 2018, at the end of an otherwise self-serving statement, Jytdog said "I am out of here. I am scrambling my WP password and deleting my gmail account and 'Jytdog' will cease to do anything, anywhere. If you see any other Jytdog doing stuff in the future, anywhere, it is not me." He then said "I urge Arbcom to do just do a motion and indef or site ban me." Either he meant it, in which case his wish should be belatedly granted, or it was not said in good faith (as I believed then and now) in which case his wish should be belatedly granted. The only difference from 2018 is the additional wasted time he's put everyone through and the WP:GAMING aspect of his "permanent," "swore on a stack of bibles he'd never return" "resignation." Coretheapple (talk) 01:54, 29 March 2020 (UTC)

I agree that this is the only option. I do want to add one other reason why. The WMF T&S is no longer taking calls. They are now transferring all authority to the English Wikipedia for English Wikipedia abuse cases. That means we need to show that we take abuse cases seriously. So far I haven't seen that. I've given up when I had to deal with T&S when I was told to "take it to the community." That is the last place I want to go. This action would be a first step in showing people that the English Wikipedia actually does take abuse and harassment seriously. Sir Joseph ^(talk) 03:41, 30 March 2020 (UTC)

Proposals by Tryptofish

Proposed principles

Sanctions are preventative

1) Sanctions are preventative, not punitive. Wikipedia is not a court of law, and does not practice retributive justice.

Comment by Arbitrators:

Comment by parties:

Comment by others:

Although I consider myself to be largely retired from Wikipedia, I've been watching this case and I feel that I want to make some proposals here. I'm offering two alternative proposed principles, and I'll explain my reasoning below. --Tryptofish (talk) 20:08, 28 March 2020 (UTC)

Punitive sanctions can be preventative

2) For severe violations of community norms, sanctions that are punitive in significant part can be necessary to ensure the prevention of future disruption.

Comment by Arbitrators:

Comment by parties:

Comment by others:

I'm workshopping two possible principles that each point in largely opposing directions, although they are not necessarily mutually exclusive. I'm not endorsing either of them. I'm honestly not sure which one is right for this case. But my advice to the Committee is that this is where you ought to start, when deciding about the case. If you feel that one or the other of these principles works better for you with respect to the case evidence, then that will point you towards what subsequent decisions you should make. --Tryptofish (talk) 20:08, 28 March 2020 (UTC)

This is an interesting basis (I'm hoping you'll discuss it with me, with the proviso that you may well be playing devil's advocate, @Tryptofish:. While this wouldn't be, fundamentally, an unreasonable decision, I'd be concerned that ARBCOM would be expanding beyond their remit. The Community has, in countless cases, stated this is not how to do things - both in severe and less severe cases. ARBCOM deals with complexity, not the "most severe", so they'd be taking a different attitude to that in place. Nosebagbear (talk) 19:52, 29 March 2020 (UTC)

As I'm sure you understand, I'm trying to keep my involvement here brief, but I thank you for asking me to discuss it further with you. Let me put it this way: I'm putting two alternatives out there, and inviting the rest of you to consider whether one of them makes more sense than the other, but I'm neither advocating for the devil nor for the angels (as it were). You make an interesting point about the extent of ArbCom's remit. On the other hand, what I wrote here is a paraphrase of something that Worm That Turned actually said to me once. I guess one way to look at it is that, if the final decision is to make the siteban permanent, a basis in principle will have to be articulated for doing so, and if that's the case, there will have to be an explicit determination that Jytdog's promises to reform are not credible. --Tryptofish (talk) 20:06, 29 March 2020 (UTC)

Proposed remedies

Note: All remedies that refer to a period of time, for example to a ban of X months or a revert parole of Y months, are to run concurrently unless otherwise stated.

Jytdog restricted (1)

1) Any uninvolved administrator who determines that Jytdog has violated any part of the harassment policy is authorized to issue an indefinite block without prior notice. Such blocks must be logged at WP:Arbitration enforcement log and may be appealed only to the Arbitration Committee.

Comment by Arbitrators:

Comment by parties:

Comment by others:

Again, I'm not necessarily endorsing any of the proposals here. I'm honestly not sure whether you should allow a return or not. But if (and only if) you do grant a return to editing, then you definitely need to enact some serious restrictions to prevent being back here again; in other words, enact restrictions that will allow net-positive contributions while warding off recidivism. I'm offering three possible restrictions with that in mind. I also acknowledge that there is a legitimate argument that someone who needs so many restrictions should simply not be here at all. --Tryptofish (talk) 20:48, 28 March 2020 (UTC)

I'm trying to avoid lengthy discussions here, but I'll make a combined reply to all of the comments so far about the three proposed remedies, and I'll somewhat arbitrarily put it here. Some editors have commented that the remedies do not address the underlying issue of Jytdog's underlying ways of thinking. I don't think that ArbCom can really remedy anyone's thought processes, but rather, they can remedy the manifestations of those thoughts as conduct. And I'm not really concerned with what might be the "standard procedure". I'm looking for ways that, if and only if Jytdog is allowed another chance, he will be doing so with some very clear boundaries in his mind at all times. Thus, he would be pushed to do the net-positive editing shown in parts of the Evidence page, while knowing very clearly what will bring the roof crashing down if he falls back on old habits, and everyone else will know exactly what to do if he does. I don't mind if some restrictions limit the amount of good editing he might do: that's a price he will have to be willing to pay if he wants to edit at all. If (and only if!) he comes back, the one thing that everyone should want is that he be forced to demonstrate good conduct and that the likelihood of bad conduct be minimized. It's not about whether an admin or an Arb will be the one who does something. It's about whether Jytdog won't do something. --Tryptofish (talk) 20:30, 29 March 2020 (UTC)

This issue with this is that is exactly what TNT did back in 2018, and they received a torrent of criticism. The outcome of this case needs to be handled by Arbcom, not left in the hands of administrators lest they receive the same response as TNT received. We see this all the time with other “unblockables.” I also think the first part of this proposal is already standard policy. Mr Ernie (talk) 09:15, 29 March 2020 (UTC)

Without disagreeing, there's certainly a difference between "blocked" and "blocked but you cannot undo this." As to the merit, this seems to amount to ArbCom saying "you get one more chance then it's all over" and delegating an ArbCom block to sysops when it'd be easier to just skip this and ban by motion should the time come, per usual. ~ Amory (u • t • c) 14:06, 29 March 2020 (UTC)

Jytdog restricted (2)

2) Jytdog is placed under a WP:0RR restriction in all namespaces. Exceptions shall be allowed for self-reverts, but no other exceptions will be allowed. This restriction may be appealed to the Arbitration Committee after not less than one year.

Comment by Arbitrators:

Comment by parties:

Comment by others:

Similar reasoning as in (1): allow editing, but restrict behavior that may lead to conflicts. I'm not sure about the amount of time before appeal, which perhaps should be something else. --Tryptofish (talk) 20:48, 28 March 2020 (UTC)

Not sure about this. In some subject areas this would be terribly limiting on useful editing (0RR when somebody adds obvious quackery?). I don't think Jytdog's reverting has in itself been a problem, and it doesn't apply to the specifics of the latest case. Also the perma-question about whether any edit can be a "revert" could lead to wiki-lawyering. In my view the means to damping down behaviour which leads to conflicts would be better achieved by some restriction concerning Talk pages and edit summaries. Alexbrn (talk) 15:45, 29 March 2020 (UTC)

Actually his reverting has been an issue, see the evidence presented by Jenhawk777, Adrian J. Hunter and Julia W. Personally I don't think a 0RR on its own will do much to help matters, as the excessive reverting seems to be a symptom of the core problem (his attitude towards other people) rather than the heart of the matter. Thryduulf (talk) 18:04, 29 March 2020 (UTC)

There are many, many other useful edits Jytdog can do. There are plenty of other editors who can revert obvious quackery. He can report it to WikiProject Medicine. His repeated reverting and then templating those who revert him for edit warring and then getting angrier and angrier is a significant part of his behaviour as Thryduulf pointed out. He also did it to Beall4 and then branded her as "melting down". I agree that it is a symptom of the core problem of his attitude to other people. But if he is ever allowed back, he needs multiple restrictions to curb his impulsive and aggressive behaviour and its symptoms. Voceditenore (talk) 07:37, 30 March 2020 (UTC)

Of itself, reverting the addition of unreliable or promotional medical content is a good thing, to be commended. It would be bad to have a system whereby WPMED (under strain at the best of times) was encumbered by a reporting system for routine editing jobs. Jytdog had no real problem with working with content, but with people, and I agree the reversion is just a symptom. I am beginning to think we don't need to craft anything ingenious to prevent the problem, but just do it plainly. Maybe something like "Jytdog is reminded that WP:CIVIL is a core Wikipedia policy and is required to pay scrupulous attention to abiding by it in each and every edit." (This particular wording is chosen because he also had a habit of making very intemperate comments only to redact/remove them a couple of minutes later ... but what is written cannot be so easily un-written). Alexbrn (talk) 08:00, 30 March 2020 (UTC)

Alexbrn, I disagree. My diffs on the evidence page show that Jytdog can't even be trusted with reverting unreliable or promotional medical content, because his judgement on what constitutes that kind of content is skewed, heavy-handed, aggressive, and uncooperative. He will go back to reverting minor breeches of MEDRS as if the world is on fire, and will argue for every revert he makes, saying it was warranted; the last thing we want is to turn his less reasonable reverts into a topic of discussion every time he makes one. If he comes back at all and is allowed to edit, I agree that 0RR is more tolerable than fighting with him over his aggressive viewpoint on what can or cannot be left in an article for 10 minutes. Julia\^talk 14:55, 30 March 2020 (UTC)

Jytdog restricted (3)

3) Jytdog is restricted to no more than 25 edits per 24 hours, in all namespaces and regardless of the nature of the edit. This restriction may be appealed to the Arbitration Committee after not less than one year.

Comment by Arbitrators:

I understand your reasoning but I really don't care for this type of restriction as they tend to cause more problems than they solve. Something like this can be gamed from either direction Beeblebrox (talk) 22:37, 28 March 2020 (UTC)

Comment by parties:

Comment by others:

This is unconventional, but please hear me out about it. As someone who worked with him for a long time, I actually think that this may be the single most useful restriction you can make, if (and only if) you let him come back. There is a consistent pattern to Jytdog's conduct, all over the Evidence page. He starts out making positive contributions, but gets progressively more and more worked up and that sometimes leads to the kind of bad conduct supposedly in defense of the project that is in evidence. Slow him down, and make him think hard before hitting "save". The number 25 is arbitrary and could certainly be something else, but it needs to be on the low side, and as in (2), one year could also be something else. --Tryptofish (talk) 20:48, 28 March 2020 (UTC)

While I don't disagree it could theoretically help, edit rate isn't the issue here, editing behavior is. Agree with Zaphod above that it'd just be more trouble that it's worth. ~ Amory (u • t • c)

I understand the rationale behind this suggestion, and I appreciate the reason for it, but the obvious response is if this editor is so terrible that he has to be restricted like this, if he can't control himself, wouldn't it be better just to separate him from the project? Forgive me for stating the obvious. Coretheapple (talk) 20:28, 29 March 2020 (UTC)

Proposals by User:Kingofaces43

Proposed principles

2020 definition of harassment

1) Editors who welcome private communication typically post their preferred contact information on Wikipedia, sometimes enabling email through the Wikipedia interface. Contacting an editor using any other contact information, without first obtaining explicit permission, should be assumed to be uninvited and, depending on the context, may be harassment. Never contact another editor in this way as part of a dispute, or when the editor has asked not to be contacted that way. Unexpected contact using personal information as described above in Posting of personal information may be perceived as a threat to the safety and well-being of the person being contacted. (text from WP:OWH introduced Jan 21, 2019 after the original case).[7]

Comment by Arbitrators:

Comment by parties:

Comment by others:

Preventative sanctions

2) WP:PREVENTATIVE is policy. When it is clear an editor intends not to engage in an inappropriate activity again, sanctions generally are meant to allow the editor to to demonstrate to the community they are capable of handling work on the encyclopedia while avoiding areas they have had issues with while preventing disruption. This can allow the community to assess if preventative measures are still required at a future date.

Comment by Arbitrators:

Comment by parties:

Comment by others:

Proposed findings of fact

Unsolicited contact

1) Jytdog called Beall4 without permission.[8][9][10]

Comment by Arbitrators:

Comment by parties:

Comment by others:

As proposer. This at least gets to the core of what led to this case without additional speculation or trying to reanalyze complicated old disputes. Even though Jytdog says in their evidence they asked right away in a phone call if Beall4 wanted to talk, calling someone who hasn't expressly given their phone number goes against our norms. There hasn't been any hard evidence presented that would suggest malice rather than a good faith if misguided attempt at resolving a dispute either though. That was still crossing the line, but also shouldn't be treated as much more extreme phone harassment either as I've seen some comments somehow hinting at gender, etc.

If anything for FOF for this topic is going to be fleshed out more, that should probably be left to arbs, etc. who are privy to the more sensitive details that us regular editors shouldn't be delving into beyond this fact. In real-life as a researcher, there's no problem with me trying to find contact info for someone who said they organized part of a conference and were easily identifiable if I wanted to get in touch with them (and I won't go into more detail than that given the private nature of this case to avoid outing). That's what phone books and listing yourself as a coordinator for symposia, etc. are intended for. That "freedom to contact" does not mesh well when editing Wikipedia though, in part because of how bad stalking and harassment has historically been that a hard line needs to be taken, even if it has some good-faith bycatch. That applies even if someone practically announces who they are on-wiki. Back when this occurred, WP:OWH did not reflect this[11], but today, it is much more explicit, so the hard-line dynamic is something the community has been wrestling with. Kingofaces43 (talk) 20:46, 28 March 2020 (UTC)

Proposed remedies

Note: All remedies that refer to a period of time, for example to a ban of X months or a revert parole of Y months, are to run concurrently unless otherwise stated.

Jytdog contact banned

1) Jytdog is banned from contacting Wikipedia editors through Wikipedia's email system or any other communication methods within Wikipedia's purview for 6 months. Jytdog is prohibited from initiating off-wiki contact with any editor regarding an on-wiki matter unless it is explicitly invited. This excludes emails to someone in an administrative capacity (e.g. oversight). Outside of normal editing, they are expected to only be in contact with editors through talk pages.

Comment by Arbitrators:

Comment by parties:

Comment by others:

As proposer. This should address WP:PREVENTATIVE privacy concerns without violating the policy by adding in more that wouldn't change anything on that front. 6 months is arbitrary for me, and I could see arbs wanting to discuss changing length of a sanction, etc. Either way, there needs to be some kind of sanction that solidifies that last sentence in this proposed remedy, so this is one route I've seen proposed in past discussions that arbs could partially spingboard off of or tailor for crafting a more finalized remedy in the proposed decision. This is in part meant to dovetail with the proposal below to keep Jytdog focused on content areas. Kingofaces43 (talk) 21:21, 28 March 2020 (UTC)

Any restriction like this needs to be carefully worded so as to allow for exceptions for contact with other people who happen to be Wikipedia editors for reasons unrelated to Wikipedia (e.g. if he happens to be real-life friends with, or work with, someone else who edits Wikipedia). It is also (I believe) not within arbcom's remit to prohibit his attendance at meetups, editathons, conferences, etc. (whether he is welcome there is a matter for the WMF and/or organisers). Thryduulf (talk) 22:49, 28 March 2020 (UTC)

Yeah, those sorts of details can definitely be hammered out in this drafting stage or by arbs in their final version since I hadn't thought of meetups, etc. (not sure if that's a something Jytdog does). I tweaked it all little bit to say "and systems within Wikipedia's purview" (i.e., calling an editor they are not acquainted with in real-life is under purview per in terms of the updated harassment policy). I'll probably leave it be until later as more ideas come in. Kingofaces43 (talk) 23:55, 28 March 2020 (UTC)

Might it be simpler just to say Jytdog is prohibited from initiating off-wiki contact with any editor unless it is explicitly invited? Alexbrn (talk) 10:47, 29 March 2020 (UTC)

"Jytdog is prohibited from initiating off-wiki contact with any editor regarding an on-wiki matter unless it is explicitly invited" might work, as he may interact with other editors (who he may not even know are editors) for entirely unrelated matters. Thryduulf (talk) 14:24, 29 March 2020 (UTC)

I like that one. I've gone ahead and added it. In a way, that could apply to meetups if that becomes a thing (i.e., register for an event and you are "approved" or invited in a sense), but I don't think that needs to be a focus. Kingofaces43 (talk) 19:01, 29 March 2020 (UTC)

I disagree with this remedy. It doesn't make sense to me that the remedy for someone initiating uninvited off wiki contact is to prohibit them from initiating uninvited off wiki contact. This is just restating the rule that was broken. Also, this doesn't address the larger issues, like the years-long pattern of aggressiveness, of which this incident was only the latest episode (see evidence page cataloguing years of incidents). Levivich ^{[dubious – discuss]} 14:12, 30 March 2020 (UTC)

Jytdog banned from editor identity information

1) Jytdog is banned topics that directly relate to an editor's personal identifying information.

Comment by Arbitrators:

Comment by parties:

Comment by others:

As proposer. Before this more more general privacy issue happened that doesn't really fit under COI, Jytdog was actually having an improving track record on the COI front since their return to it. Maybe language similar to it relating to To avoid ambiguity, "non-public information" includes (but is not limited to) any information about another user including legal names and pseudonyms, workplace, job title, or contact details, which that user has not disclosed themselves on the English Wikipedia or other WMF project.[12] could be fit into this, but I usually expect arbs will craft their own tailored version, so this is the gist of it.

Basically, stay away from WP:COIN, anything related to IDing information, etc. and stick to content. I'm not sure what would need to be written to ensure WP:GAMING by other editors doesn't occur (e.g., someone says they work for group X in a dispute then claim Jytdog has to leave because they brought up personal information). Jytdog still did a lot of good at COIN though, so something of that nature may not need be indefinite, but I view this more as a moratorium to show their content editing after their year-long block/break before returning to areas like COIN if at all that deal with personal information correctly. Kingofaces43 (talk) 21:26, 28 March 2020 (UTC)

Proposals by User:Example 4

Proposed principles

Template

1) {text of Proposed principle}

Comment by Arbitrators:

Comment by parties:

Comment by others:

Template

2) {text of Proposed principle}

Comment by Arbitrators:

Comment by parties:

Comment by others:

Proposed findings of fact

Template

1) {text of proposed finding of fact}

Comment by Arbitrators:

Comment by parties:

Comment by others:

Template

2) {text of proposed finding of fact}

Comment by Arbitrators:

Comment by parties:

Comment by others:

Proposed remedies

Note: All remedies that refer to a period of time, for example to a ban of X months or a revert parole of Y months, are to run concurrently unless otherwise stated.

Template

1) {text of proposed remedy}

Comment by Arbitrators:

Comment by parties:

Comment by others:

Template

2) {text of proposed remedy}

Comment by Arbitrators:

Comment by parties:

Comment by others:

Proposed enforcement

Template

1) {text of proposed enforcement}

Comment by Arbitrators:

Comment by parties:

Comment by others:

Template

2) {text of proposed enforcement}

Comment by Arbitrators:

Comment by parties:

Comment by others:

Analysis of evidence

Place here items of evidence (with diffs) and detailed analysis

On wbm1058's evidence section

While the focus of this case is about the phone call, many editors are bringing up previous history, so I want to focus on just that aspect for a bit. I'm concerned about wbm1058's long list of links where Jytdog was involved in admin boards without any annotation basically being used as handwaving to insinuate Jytdog was the problem in most of them. That is already used in one proposal to insinuate there were many legitimate complaints against Jytdog or that their behavior was getting worse, and the workshop instructions are very clear not to do that. This might get longer than a typical analysis section, but it was also a lot of links just thrown out there. I'll work backwards from Jytdog's Nov 2018 block (more recent stuff generally carries more weight) and talk quotes are generally ANI closes:

1. November 2018 - Unnecessary block caused by Muse (disambiguation) content dispute and User:Jytdog's harrassment : The complaints by MusenInvincible are not supported by policy, as explained by several editors. MusenInvincible is advised to drop the issue. NinjaRobotPirate (talk) 23:02, 12 November 2018 (UTC)
2. September 2018 - Jytdog (yet again) and Yakult:OP (Andy Digley) was one-way I-banned for hounding Jytdog.
3. August 2018 - User Jytdog Misconduct.: OP filed an ANI because Jytdog hatted a section. OP was CU blocked as a sock.
4. August 2018 - User Jytdog Should Be INDEFINITELY Blocked: Didn't link the whole ANI where the COI account wanting to boomerang Jytdog was indeffed.
5. June 2018 - User:Jytdog: For Godrestsinreason OP is Indef blocked for COI violations and per their basically requesting a self block here by agreeing to a site ban. No reason to continue the drama. TonyBallioni (talk) 19:14, 14 June 2018 (UTC)
6. April 2018 - Malicious editing and AfD actions by Jytdog: user:Quinn2425 indef blocked for sockpuppetry and personal attacks. The rest appears to be a content dispute. Guy (Help!) 09:12, 1 May 2018 (UTC)
7. February 2018 - GLAM / WIR / COI:Complicated somewhat meta-issue on how COI affects GLAM and Wikipedians in Residence. Can't find much there on what Jytdog supposedly went overboard on, but it sounds like others agreed Pigsonthewing was mostly overreacting and they had a COI.
8. January 2018 - User:Jytdog reported by User:Prokaryotes: Protected. Prokaryotes was also banned from GMOs (at AE and almost ArbCom) for things like editing warring and involved with Jytdog there.[13] There was a flurry of edits making it hard to count reverts, but it definitely looked like Prokaryotes wasn't following WP:ONUS policy. Jytdog could have slowed a bit on reverts, but others were also having trouble with Prokaryotes edits too. Looks more like a managing serial edits problem than a clear cut edit warring violation to pin on anyone.
9. December 2017 - Jytdog Ban breaking/request of Enforcement and further actions:Closed as likely sockpuppetry. Even for me being familiar with how broad we made the GMO DS, there wasn't any evidence presented convincing of a ban violation.
10. November 2017 - User:Jytdog: OP (Banzernax) indeffed.
11. August 2017 - Boomerang for Jytdog: Not the whole ANI. This has gone on long enough. No consensus here to act about anything, but nobody's hands are clean either. Everybody go edit the encyclopedia now and be kind to each other. Katietalk 22:48, 6 August 2017 (UTC) Boomerang requested by Jusdafax (also involved with Jytdog and sanctioned in GMOs for making accusations without evidence[14]) was mostly opposed.
12. August 2017 - Unjustified reverting by User:Jytdog: New editor being reverted for mass problematic changes in single edits by Jytdog. Editors seemed to agree ANI wasn't appropriate and gave advice to new editor.
13. April 2017 - Jytdog abusing WP:THREATEN:Another case of a sock and editors having to say Jytdog didn't threaten anyone at all.
14. March 2017 - request for block of user @Jytdog: to prevent him from removing valid edits: Core complaint was Thus, I ask you to block jytdog from removing edits soley because they are based on primary sources. Editor was kindly reminded about WP:MEDRS.
15. February 2017 - reporting myself (and Jytdog): Mostly a misunderstanding. Jytdog and Slatersteven are to be commended for actually listening instead of endless escalation. 78.26 (spin me / revolutions) 21:29, 21 February 2017 (UTC)
16. February 2017 - Arbitration motion regarding Jytdog: COI restriction removed with caveat of revealing non-public information will result in an indef.
17. January 2017 - Block #3
    • 04:15, 15 January 2017 King of Hearts blocked Jytdog with an expiration time of 24 hours (account creation blocked) (Violation of the three-revert rule): Found the unlisted AN3. Both were blocked, and Jytdog definitely went past 3RR. The other editor Namarly looked to have some belligerence issues as a newer editor, wasn't listening, and was also check-user blocked.[15]]
18. November 2016 - User:Jytdog reported by User:CanadaRed: Page protected – 5 days. Please use the talk page to agree on where to go from here. The stuff Jytdog was removing does look promotional by our usual definition. But Jytdog need not assume the sole burden of removing promotional content, and when he breaks 3RR that is sooner or later going to be enforced. User:CanadaRed is risking a block for disruptive editing if he continues to restore material that has been removed after lengthy talk page discussion. Since this article has caused so much trouble in the past people need to step carefully. EdJohnston (talk) 04:08, 13 November 2016 (UTC)
19. November 2016 - Jytdog: Good response to OP If you add unsourced material to a BLP ([1]) you can't really complain when another user drops an unsourced template on your talk page. However, it does appear that this can be sorted out via discussion on the talk page, and is thus a content dispute and not something that WP:ANI needs to concern itself with. Black Kite (talk) 19:03, 21 November 2016 (UTC)
20. September 2016 - Disruptive editing by Jytdog; possibly article ownership or edit warring: Content dispute by OP who was the only one found to need guidance.
21. September 2016 - User:Jytdog removing talk pages comments based on their opinion:Treated as a frivolous request.
22. September 2016 - Edit-war with jytdog over Teledermatology:No issue found with Jytdog, looked like another new editor having trouble with MEDRS.
23. September 2016 - Verbal and Psychological Abuse of a female editor by Jytdog: OP topic-banned from sex/gender-related topics.
24. June 2016 - (Enforcer) Jytdog has lost objectivity in COIN: Almost unanimous support for a bommerang to COI OP as vexatious. The close does not mention issues with Jytdog at all.
25. June 2016 - Doxxing? "During the ArbCom there were 3 people outed! All 3 of them on the side that was challenging the Jytdog et al. It is logical to suspect foul play."  01:12, 5 June 2016 (UTC)

    I find it odd wbm1058 chose to highlight that aspersion in the GMO topic that's in conspiracy theory territory by another GMO topic-banned editor. In reality, this was the actual ANI requesting a moderated RfC the the scientific consensus of GMOs. Jytdog was no longer in the topic at this time. The part wbm1058 highlighted on doxxing was one admin, Laser brain, who agreed to moderate the RfC, received threats over email from those opposed to the RfC, so it wouldn't make sense to insinuate Jytdog's involvement given his stance in the subject before his ban. That both petrarchan47 (the remainder wbm1058's quote) and Slimvirgin floated conspiracy theories about that being a false flag (in the above diff) does show the kind of battleground mentality myself, Jytdog, and other science editors in the GMO topic were bombarded with though.

26. June 2016 - Block #2 : I will comment on this block, and I encourage editors to read the talk page notice summarizing it for the public. COI editor was editing under their real name. There was crossing the line with including a link about the person that resulted in the block, but there was also discussion about tensions between WP:COI and WP:OUTING. The block was valid, but highlighted tensions for those trying to balance the two.
    • 16:00, 8 August 2016 GorillaWarfare unblocked Jytdog (Successful appeal to the Arbitration Committee: He is warned that any further violations of the outing policy will be cause for a site ban. Unblock
    • 17:34, 27 June 2016 GorillaWarfare blocked Jytdog with an expiration time of indefinite (account creation blocked) ({{OversightBlock}}):
    • 19:51, 27 June 2016 GorillaWarfare changed block settings for Jytdog with an expiration time of indefinite (account creation blocked, cannot edit own talk page) ({{OversightBlock}})
27. March 2016 - Grave threat of harm made by User: Jytdog: There is no credible threat of harm to Picomtn here. Picomtn has no basis for their accusation of sock puppetry by David Gerard and Jytdog. I hesitate to even suggest that Picomtn take their allegations to WP:SPI as I imagine it would quickly be declined and closed for lack of evidence. . . Bbb23 (talk) 11:40, 15 March 2016 (UTC)
28. March 2016 - Jytdog Enough is Enough!:No alleged personal attacks alleged by IP found.
29. March 2016 - More WP:BATTLEGROUND from Jytdog at Berylliosis: Filed by Andy Digley (I-banned years later). No formal close, but it looks like Jytdog walked away from this dispute rather than engage.
30. February 2016 - Jytdog's bullying over editing Craig J. N. de Paulo: It appears that the OP is forum shopping. As has been suggested, WP:RSN seems to be a more suitable forum for this issue. (non-admin closure) Erpert blah, blah, blah... 01:40, 7 February 2016 (UTC)

Pre-GMO items

# December 2015 - Genetically modified organisms case closed: I already commented on the complicated nature of the GMO case at my evidence section. In short, Jytdog had some issues, but many were exacerbated the the sheer number of problematic editors that were eventually also banned from the subject for advocacy or hounding issues that explains, but does not justify, many of the incivility issues. Jytdog and DrChrissy are placed indefinitely under a two-way interaction ban. Jytdog is indefinitely topic-banned from all pages relating to genetically modified organisms and agricultural chemicals, broadly interpreted; appeals of this ban may be requested no earlier than twelve months since the date the case closed. Jytdog is admonished for their poor civility in relation to the locus of this case. November 2015 - Block #1: This block was good for an oversight block. I know what it was about, and it was a serious issue about certain editors that was only apparent off-wiki (as much as I'll say there). It should not have been brought up publicly in the case though. 22:04, 27 November 2015 HJ Mitchell unblocked Jytdog (per email discussion; has promised not to repeat the relevant edit) 03:06, 17 November 2015 HJ Mitchell blocked Jytdog with an expiration time of indefinite (account creation blocked, cannot edit own talk page) (please contact ArbCom or the functionaries team) September 2015 - User:Jytdog reported by User:DrChrissy: Article protected. Part of the larger GMO dispute and issues between DrChrissy and Jytdog. September 2015 - Editor Jytdog's none neutral GMO edits: This is the ANI case that largely set up the GMO ArbCom case. No one was sanctioned at this time. August 2015 - Would like Jytdog to leave me alone: Per the OP's suggestion, closed as resolved with a voluntary Iban between Jytdog and CorporateM. BMK (talk) 18:41, 15 August 2015 (UTC) July 2015 - Mass deletion / PROD / redirect of mall articles under the guise of WP:COI Suggestion to Jytdog and GregJackP No formal close, but a history of problems with GregJackP and others was interjected into the ANI. It was suggested Jytdog and GregJackP try to avoid each other since the ANI was derailed. From Jytdog: I'm late to the party, but I would be happy to steer clear of GregJackP and am OK with the hatting of both threads. Jytdog (talk) 11:47, 13 July 2015 (UTC) July 2015 - What is our CoI policy actually?: Not the full ANI: The final motion, "Elvey has exhausted the patience of the community and is topic banned from COI, broadly construed. This sanction may be appealed to the community in six months", has broad consensus. So ordered. Drmies (talk) 17:31, 7 August 2015 (UTC) May 2015 - Jytdog needs administrator intervention, please?: Withdrawn by OP May 2015 - Strong-arm tactics by Jytdog: IP blocked - this is obviously a long-time disputant, possibly block-evading, certainly trying to evade scrutiny. Not here to contribute. Guy (Help!) 23:18, 29 May 2015 (UTC) May 2015 - User:Jytdog reported by User:Anmccaff: No action or violations. April 2015 - User:Jytdog: Unclosed, but seems to be another COI thread. Jytdog stated that Dr. Joseph Shaw shouldn't edit the article Latin Mass Society of England and Wales because Shaw is the chairman of that society, which definitely doesn't seem to warrant an AN posting. April 2015 - JYTDog - Vote Stacking:Nowhere near the full unclosed ANI. The small complaint within seemed to be that Jytdog pinged editors who had been active at the article somewhat recently. Many of them had also been in dispute with the editor on that page and other editors didn't seem to take the complaint seriously. March 2015 - Jytdog's behavior: Not the full ANI. Drmies close: But this was not about Jytdog or ANI, so: c. There is a measure of agreement that David Tornheim's editing is problematic March 2015 - Jytdog: Protracted uncivility and harrassment: DrChrissy filed as part of the GMO dispute. Swarm closed with a warning to Jytdog. DrChrissy's behavior with Jytdog was not addressed at this time (later at GMO ArbCom). March 2015 - Request review of closure of ANI against Jytdog: Made by DrChrissy in relation to the previous , closure was reaffirmed. September 2014 - User:Jytdog reported by User:Blacksun1942: Page protected. Looks like talk was ongoing when the OP filed this and was confused about 3RR. It looks like it resolved on its own practically. September 2014 - User:Jytdog and User:Gandydancer reported by User:SW3 5DL: Declined. Jytdog was cleared, SW35DL was told to use the talk page. April 2014 - Recurrent violation of Civility policy by Jytdog: This is not a matter to be resolved at this noticeboard, because there is no concise synopsis with diffs showing any sort of behavior that would require an immediate block. January 2014 - User:Jytdog reported by User:FelixRosch: No violation.

Now I think it's rather absurd to have to go through this many blanket links at ArbCom, but when you read the links, it actually gives a pretty telling story. In general, it was usually the editor that was in a dispute with Jytdog that was the problem (disruptive, new, COI, or sock), and Jytdog wasn't found to be the issue. That's especially the case as you go back from Nov. 2018. They had nearly two years of decent editing since their COI ban was lifted or block 3 for edit warring, which isn't something that's going to trigger discussion of indef blocks. You have to go back to block 2 for a more serious issue related to outing, but it also was a more complicated case where the editor already revealed their name. It's not until you get back to the GMO case and block 1 around 2015 that you get to some more clear cut issues (and a lot of messy stuff mired in GMOs I won't get into here).

This "many admin boards" thing isn't a new problem, and it often distracts from dealing with legitimate behavior issues with Jytdog while tending to inflame situations or topics they want to edit with the examples above related to hounding of Jytdog. I cant think of any remedies for that, but if Jytdog comes back, I get the feeling we'll need some caution (maybe an FoF?) in place to sort out the peanut gallery effect or hounding from old disputes by sanctioned editors so Jytdog's concrete behavior can actually be examined over time at admin boards. To be clear I don't know of any background of wbm1058 with Jytdog in that regard, but the way the evidence was presented has become an issue. Kingofaces43 (talk) 05:47, 29 March 2020 (UTC)

Comment by Arbitrators:

Comment by Parties:

Comment by others:

Regarding:

1. November 2018 - Unnecessary block caused by Muse (disambiguation) content dispute and User:Jytdog's harrassment : The complaints by MusenInvincible are not supported by policy, as explained by several editors. MusenInvincible is advised to drop the issue. NinjaRobotPirate (talk) 23:02, 12 November 2018 (UTC)

• MusenInvincible had an interest in Muse (band), and on 26 October 2018 made several minor edits to improve coverage of that topic.
• MusenInvincible makes five good-faith edits to Muse (disambiguation) between 26 October–2 November 2018‎, and is reverted by multiple editors.
• @15:33, 2 November 2018 MusenInvincible edits Jytdog talk Re: edit blocking threat
• Jytdog is the last editor to revert; initiating discussion at Talk:Muse (disambiguation)#Edit @15:54, 2 November 2018
• @16:04, 2 November 2018 – just 10 minutes after starting that discussion – Jytdog placed an edit-warring notice on MusenInvincible's talk page.
• 3RR noticeboard discussion initiated @16:04, 2 November 2018

Respectfully, I disagree with the close of that ANI discussion. Five edits over the course of eight days does not, in my view, constitute "long-term edit warring".

Jytdog's behavior in this incident is appalling. He was overly aggressive in templating with a warning, which was undue escalation of what strikes me as a relatively minor dispute.

But, starting a 3RR discussion a mere ten minutes after initiating discussion at the talk page where the alleged edit-warring occurred, and then citing that very discussion as their attempt to "resolve the dispute", really now, on what planet is that acceptable behavior? wbm1058 (talk) 02:26, 30 March 2020 (UTC)

2. September 2018 - Jytdog (yet again) and Yakult:OP (Andy Digley) was one-way I-banned for hounding Jytdog.

Andy Dingley's behavior is irrelevant here. The purpose of this analysis is to evaluate Jytdog's behavior. In that regard, we only need look at the opening quote of that discussion to find some below-standard behavior: "This is a pile of dogshit on the sidewalk. If people want to write a real article on this, please do so. But I bet not a single one of the !voters here will clean up this dogshit. Nope, you will give your !vote and leave the shit here for other people to step in." is simply not acceptable editing behaviour.

OK, again I respectfully disagree with the apparent community consensus on civility. Calling someone's work "a pile of dogshit" is not civil discussion. wbm1058 (talk) 05:18, 30 March 2020 (UTC)

3. August 2018 - User Jytdog Misconduct.: OP filed an ANI because Jytdog hatted a section. OP was CU blocked as a sock.

Again I respectfully disagree that the behavior of the complainant is relevant. Jytdog created the deletion discussion Wikipedia:Articles for deletion/Cleveland Clinic Lerner College of Medicine. Then, acting as a WP:INVOLVED administrator, even though he was not actually an administrator, he hatted opposing comments ONCE, TWICE, THREE times (bold-revert-discuss protocol would have called for discussing the disputed hatting before reinstating it – hatting the comments was a bold action). In general, editors should not act as administrators in disputes in which they have been involved. This is because involved administrators may have, or may be seen as having, a conflict of interest in disputes they have been a party to or have strong feelings about. Involvement is generally construed very broadly by the community... By what stretch was Jytdog not acting as an "involved admin" in his actions here? wbm1058 (talk) 14:09, 30 March 2020 (UTC)

On Atsme's evidence section and larger admin board issues

This is my last analysis section (mostly because I'm familiar with the history) given the time the above took, but Atsme's section concerned me for how much it misrepresented both Jytdog and Atsme and drug up 5+ year-old disputes. Normally I wouldn't focus this much on a non-party, but Atsme has provided examples of the kind of problems that other editors muddy the water with on Jytdog at admin boards.

Disruptive behavior: This subsection was extremely misleading in annotation asserting targeting an editor, bullying, etc. What Atsme omitted was that this dealt with DePiep before the GMO ArbCom, and this was the actual ANI That editor was blocked for personal attacks and casting aspersions (i.e., shill gambit), that got so bad in the topic, we had to adopt a principle on it at the GMO ArbCom. Myself and Jytdog were especially hounded on this by DePiep and others, and editors were justifiably frustrated by DePiep's actions and Slimvirgin's comments at the ANI (Atsme links to some responses by Jytdog to both). That was a case of Jytdog being frustrated by harassment and pot-stirring, so I'm very concerned Atsme used ArbCom to try to paint Jytdog trying to get admin action on that as bullying people. It took ArbCom to finally crack down on that.

Business associations: This section is also misleading. Atsme didn't link the whole COIN against them that did find Atsme has a COI with Earthwave, the issue was more about what to do about edits Atsme made. The actual COI was demonstrated on-wiki by Atsme themselves though, which makes the "probing" language inaccurate. Atsme says His distorted truths and misconceptions caused me to be wrongfully branded as a paid editor., yet I'm not seeing any diffs that show Atsme's claim isn't an aspersion, especially claiming that Jytdog said Atsme was paid for those edits at COIN. Instead, Atsme escalated it to ArbCom calling it an abuse of COIN, which arbs declined. Atsme instead picked the one arb who mentioned no prejudice, who actually said that in the context of if the community couldn't handle the issue, not that Jytdog was at fault there. The other arbs generally seemed agreed that there wasn't anything done by Jytdog at the COIN to really merit a case, so it wasn't really closed in Atsme's favor or that Jytdog really stepped out of line. DGG summed the core problem up well there in response to Jytdog and others trying to tackle Atsme's COI issue, As I see it, the principal problem is Atsme's refusal to accept legitimate criticism and to assert article ownership. As she apparently sees it, her approach to an article is always the right one.

Malicious intent: That last issue actually culminated in their last section. This largely had to do with an essay Atsme wrote WP:AVDUCK. The first version had some serious issues that Jytdog and the community took issue with where the essay was correctly deleted. Atsme eventually recreated a version that has survived, but also filed an ANI against Jytdog about it. What Atsme ommitted in their annotations that don't match the diffs was not showing the final close of the ANI where Bishonen blocked Atsme for disruptive editing there.[16]. That's very different than the picture Atsme just tried to paint, and is cherrypicking to the point that it's misuse of Arbcom time for pursuing an old dispute where Atsme was sanctioned.

If you read through Atsme's links or the actual cases, that's an example of an editor unable to deal with their own disruptive behavior and then projecting that problem onto other editors (like Jytdog) who have tried to address that behavior as discussed in Atsme's noticeboard discussions. Maybe it's in part because Jytdog is a prolific editor covering multiple topics (especially fringe areas), but Jytdog does seem to attract a lot of WP:IDHT editors over time that follow this pattern of: 1. be disruptive where Jytdog has edited, 2. Jytdog goes to an admin board, 3. editor is correctly sanctioned (or not), 4. editor pursues Jytdog at future admin boards minimizing who was actually sanctioned saying Jytdog was as bully or misuses noticeboards, 5. Admin board is derailed making it very difficult to determine if there are legitimate issues with other editors or Jytdog because of old grudges.

tl;dr: Like my previous analysis section, I'm wondering what arbs think about addressing the general hounding/old grudge issue (or rather just acknowledging it) if Jytdog comes back? That seems to come up whether Jytdog is editing well or having issues (see my previous analysis section), and that is part of the reason why Jytdog topics generally aren't handled well by the community (and end up in ArbCom's domain). Generally, we try to ignore those editors and focus on the core issue when that's going on, but that usually means more time wasted by the community that shouldn't be pinned on Jytdog (and I will pin things on Jytdog when they are due). This is outside the core phone-call issue, but I feel like we'd be setting Jytdog up for failure if we also don't attempt to address this larger hounding problem in the community that isn't always the result of Jytdog being gruff and has already resulted in some I-bans. If anyone can address the mess that causes, it will be here. Kingofaces43 (talk) 18:57, 29 March 2020 (UTC)

Comment by Arbitrators:

Comment by Parties:

Comment by others:

Template

Comment by Arbitrators:

Comment by parties:

Comment by others:

Template

Comment by Arbitrators:

Comment by parties:

Comment by others:

Template

Comment by Arbitrators:

Comment by parties:

Comment by others:

Template

Comment by Arbitrators:

Comment by parties:

Comment by others:

Template

Comment by Arbitrators:

Comment by parties:

Comment by others:

General discussion

Comment by Arbitrators:

Comment by parties:

Comment by others:

Comments from User:Pine

I am somewhat familiar only with the immediate issue at hand, namely the phone call that shouldn't have been made, and not with the rest of Jytdog's edit history. Personally, I am satisfied that Jytdog is sincere in apologizing for that phone call, and I agree that the call was a bad idea.

Quoting from Wikipedia:Harassment#Off-wiki harassment: "Editors who welcome private communication typically post their preferred contact information on Wikipedia, sometimes enabling email through the Wikipedia interface. Contacting an editor using any other contact information, without first obtaining explicit permission, should be assumed to be uninvited and, depending on the context, may be harassment. Never contact another editor in this way as part of a dispute, or when the editor has asked not to be contacted that way. Unexpected contact using personal information as described above in Posting of personal information may be perceived as a threat to the safety and well-being of the person being contacted. Users who experience inappropriate off-wiki contact should report occurrences privately to the Arbitration Committee or to the emergency response team."

In my personal opinion, if Jytdog thought that a voice conversation would help to resolve an issue, then what would have been better would have been contacting the editor on their talk page and inviting the other editor, in a completely nonthreatening way, to have a conversation using any number of voice communication tools including tools which don't require the other user to provide their phone number or other nonpublic information. The current policy prohibits even that ("Never contact another editor in this way as part of a dispute"), which I personally think is going too far but I am not proposing that Arbcom change this as a part of this case.

"Bad idea" does not necessarily imply "malicious", and at this point I'm mostly convinced that Jytdog was not being malicious with that phone call, but the call was "uninvited". If only considering that phone call, I don't think that an indefinite ban would teach any lesson that Jytdog has not learned, and I do not think that an indefinite ban would be appropriate or necessary if that phone call was the only issue of concern with Jytdog's conduct. However, I have not looked into other conduct by Jytdog, and I would remain concerned if this was a part of a pattern of issues. If there is a pattern of issues then I might support an indefinite ban or some editing restrictions pending some persuasive evidence of reform for issues beyond those that are immediately visible on the surface of this case. For example, it might be that Jytdog should be prohibited from directly intervening in alleged conflict-of-interest cases and should be required instead, if Jytdog does anything about them, to bring them to the attention of an uninvolved administrator or an appropriate noticeboard.

A call could have gone well and been appreciated by someone who was having difficulty with Wikipedia's interface or policies, but a call could also theoretically also have led to someone being outed and at risk for consequences from an employer or someone else that disapproved of the individual's Wikipedia activities. While I think that this was not Jytdog's intent, it is a risk that should be taken into consideration. Accordingly, I think that a remedy in this case should include putting Jytdog on indefinite probation with terms something like this: "Further violations of the policy regarding Wikipedia:Harassment#Off-wiki harassment are to result in an indefinite ban under the procedures for Arbitration enforcement, and should be brought to the attention of the Arbitration Committee."

Thank you for considering these comments. ↠Pine (✉) 04:41, 22 March 2020 (UTC)

Comments from Voceditenore

Jytdog's unsolicited phone call to an editor with whom he was in dispute using off-wiki research to obtain her private information needs to have a finding of fact and a remedy, even if it is ultimately reduced to "time served". He retired after the arbitrators were in possession of potentially damning private evidence and the case was about to be accepted. In his retirement announcement he gave as his ostensible reason "The outcome of that case if pretty foregone, in my view. I see no good reason to put everybody through more of this." [17] The retirement and subsequent request to return a year later should not be allowed to short-circuit and prevent the scrutiny and judgement that he sought to avoid in 2018. The remedy should be decided as it would have been had he not "retired". If the arbitrators feel that a site ban is warranted for that behaviour, then that should be the remedy, and it should be "on the record", before they shorten it for "time served".

Jytdog has a long record of occasions of gross incivility dating from 2015 right up to 2018. The 9 occasions cited in my evidence [18] were all triggered by his anger over alleged COI/advocacy. His judgement in this area is permanently impaired. He was blocked for outing an alleged COI editor in 2015 [19]. Promised not to do it again [20]. Was unblocked. Did it again in 2016. Was blocked again [21]. Promised not to do it again [22]. Was unblocked again with a comprehensive topic ban on "all matters related to COI editing [23]. Had his topic ban lifted in 2017 with a strong warning [24]. In 2018 he was blocked for off-wiki harassment and privacy violation of an editor whom he deemed a COI "advocate" [25] (the trigger for this case). Promised not to do it again [26]. Was unblocked. Was re-blocked by an ArbCom motion [27]. And here he is again in 2020, still dissembling about what he did [28], and promising not to do it again.

Yet, the reason he gives for wanting to return [29] [30] is that he wants to edit in the very area (COI/Advocacy/Promotionalism) that over the past five years has repeatedly triggered his gross incivility, aggression, and impulsive acts of outing and harassment. If he is ever allowed to return, he should be under the following restrictions (or something similar) for a very lengthy period:

1. Topic-banned from any article, discussion page, or user talk page where issues of COI, advocacy, or promotionalism are involved—broadly construed
2. Restricted to 0 revert on any page and for any reason.
3. Forbidden to contact any editor off-wiki (including by email) for any reason without their explicit prior permission.

In my view, without these restrictions he will inevitably repeat his past behaviour, despite his promises and the assertions of others that for some reason this time he really has learned his lesson. The next time may not be one of the exact same things he has done before, but it will almost certainly be a variation on them—and an egregious violation of the spirit, if not the letter, of the policies and warnings he has repeatedly flouted. None of these restrictions would impair his ability to create high quality content. Voceditenore (talk) 09:52, 28 March 2020 (UTC)

Comments from Coretheapple

I appreciate that editors are going to such trouble to figure out ways of keeping a toxic editor from having opportunities to be toxic, and that he be given one really really final chance to not be toxic. Look at this case. Look at the thousands of words and hundreds of person-hours wasted on this. Do you really want yet another time suck to waste the community's time a few months hence? It would be inevitable if arbcom kicks the can down the road.

The 2018 proceeding was terminated by Jytdog in his own self-interests. I appreciate Newyorkbrad's and KrakatoaKatie's comments, but I suggest that it would be a serious mistake to wipe the slate clean and disregard that Jytdog interrupted the 2018 proceeding because he knew that the evidence overwhelmingly supported a site ban. His comment at the time "I urge Arbcom to do just do a motion and indef or site ban me." reflected the inevitability of that outcome. Let's give him unwarranted AGF and assume he sincerely believed what he was saying in 2018, and was not cynically short-circuiting the proceedings in the hope of gaining a better outcome down the road.Even if you take him at his word, what we have is Jytdog's own assessment that his behavior warranted a siteban or indefinite block, and not yet another chance not to be toxic. Coretheapple (talk) 15:31, 29 March 2020 (UTC)

I hear you, and we're not going to disregard it; it will likely show up in the FoFs to be considered in support of one or more remedies. We're not that far in the PD draft yet, so that's all speculation (though I'm a drafter). Editors often rage quit or embarrassment quit, if you will, after an incident that's blown up or an interaction gone wrong, only to later change their minds. Most of the time a return isn't an issue at our level. This time it is, and we're going to look at all his behavior, not just what he's said in the last three months. I'll be interested to hear your comments about the PD when it's posted. Katie^talk 17:32, 29 March 2020 (UTC)

@Coretheapple: I think it is important that when a site ban is a realistic possible outcome of an arbitration case that time be spent investigating whether there are any viable alternatives that will allow an editor to be a positive contribution to the encyclopaedia while protecting the project and its other contributors from harm. In this case, I've yet to be convinced that there is a workable remedy that will allow this, given the variety and nature of the problems brought up in evidence, but it is absolutely right that all the options are explored before a final decision is made. That is exploration is done, and seen to be done, is particularly important when the editor facing the site ban (or a desysop) is someone who might be regarded as an "unblockable" as it will reduce the intensity of the inevitable shit storm at WT:ACN when the case is closed. Thryduulf (talk) 18:17, 29 March 2020 (UTC)

@Thryduulf: I agree with you that the "remedies" being discussed are nonstarters in this particular situation. @KrakatoaKatie: I participated in the 2018 arbitration and watched it unfold in realtime. Neither rage nor embarrassment was a factor in the departure. Those two ships had sailed long before. What was happening was that he was about to be banned, as he acknowledged. Coretheapple (talk) 20:00, 29 March 2020 (UTC)