Wikipedia:Arbitration/Requests/Enforcement/Archive315

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

Request concerning Minaro123

User who is submitting this request for enforcement

TrangaBellam (talk · contribs · deleted contribs · logs · filter log · block user · block log) 20:13, 23 January 2023 (UTC)[reply]

User against whom enforcement is requested

Minaro123 (talk · contribs · deleted contribs · logs · filter log · block user · block log)

Search CT alerts: in user talk history • in system log

Sanction or remedy to be enforced

WP:ARBIPA

Diffs

of edits that violate this sanction or remedy, and an explanation how these edits violate it

1. 24 January 2023 Claims the "official" map of the district to mention a certain region. It took minutes to disprove the claim and establish that he had cited a map by a barely known publisher. Minaro123 reasoned that if the map had any problem, it should have been banned by the government and the lack of a ban established the official status. Wow!
2. 18 January 2023 I do not know how to explain this.
3. 18 January 2023 Representative chat-bot behavior; their replies have little relation to the topic under discussion.
4. 18 January 2023 Claiming that Wikipedia has an exhaustive list of reliable sources and accordingly, removing sources from prominent Indian media!
5. 11 january 2023 Cavalier attitude with sources; citing scholars who do not support the content before being forced to concede grudgingly.
6. 3 January 2023 Claims that "Brokpas had never claimed to be Aryans at all." This is a 180-degree misrepresentation of content and shows the insistent POV-pushing; see the current version of Aryan Valley where multiple scholars note the Brokpas to have claimed themselves as Aryans for decades!
7. Talk:Aryan_Valley/Archive_1#Lead_dispute (3 January 2023) - An example of "discussion" with Minaro123.

Diffs of previous relevant sanctions, if any

1. 18 January 2023 Indefinite P-block from Aryan Valley and t/p under AC/DS. This arose out of an AN3 complaint.

If

WP:AC/DS#Awareness and alerts

)

• Alerted about discretionary sanctions in the area of conflict in the last twelve months, see the system log linked to above.

Additional comments by editor filing complaint

I argue that Minaro123 has a CIR issue; his contributions are essentially disinformation and the noise-to-signal ratio is too high to be a net positive. Right after being subject to a sanction, he is misrepresenting sources and defending the same using ridiculously tortous arguments!

He can either be indefinitely blocked from the project or sanctioned with an indefinite T-Ban from anything that has to do with Brokpas (broadly construed). I, Joshua Jonathan, and others have wasted sufficient editorial resources in the process of engaging him and trying to sort the wheat from the chaff.

@Elinruby: You wrote, The central issue here is however that it isn't up to TB to decide [] what ethnic group [Minaro123] belongs to. Provide the diff where I tried to "decide" (or even comment) on Minaro123's ethnicity.

Bishonen, thanks for chiming in on the applicability of REDACT. I did not restore the new text because I was unsure about the extent to which it was to replace the old post. Hence, I chose to alert Elinruby of the revert at his t/p and the REDACT policy so that he could reincorporate his edits in compliance. TrangaBellam (talk) 22:15, 24 January 2023 (UTC)[reply]

Elinruby, thanks for your compliance with REDACT. That said

My request for the diff where I had decided on Minaro123's ethnicity remains unanswered. Do note that I have to comment on Minaro123's ethnicity explicitly; not on the ethnicity of Brokpas, to which he belongs to (per you).

Also unanswered is K3's query about how Minaro123 — who is editing for months and has raked in about a thousand edits — is a newbie. Actually, you have doubled down on the claim by accusing me to be "biting" him citing the very evidence, that I had cited as the latest example of their incompetency!

Can you please double-check your diffs? The diff linked to your claim that [n]obody in this story here claims that they are [Aryans] — thereby contradicting scholars like Mona Bhan, D.S. Bhagabati et al and about a dozen journalists — has no relevance. Frankly, there is not a single source which notes that the Brokpas do not claim being Aryans!

Minaro123 removed information sourced from OPEN, Mint etc. by claiming that the sources were not featured in Wikipedia's list of reliable sources; it is obvious that he took it as an "exhaustive" list. TrangaBellam (talk) 06:03, 25 January 2023 (UTC)[reply]

I won't reply to Elinruby in any substantial manner (unless requested by RP or other admins) since I believe he is spamming the board with irrelevant stuff to take the focus away from Minaro123. I have no clue about which ethnologist got dismissed and by whom. That said, my edits were supported by K3 and JJ, two of the most veteran editors in S. Asian topics; frankly, it was JJ who had overhauled the content before I jumped in. TrangaBellam (talk) 18:57, 25 January 2023 (UTC)[reply]

@

a sanctions-regime covering all South Asian social groups. TrangaBellam (talk) 05:12, 26 January 2023 (UTC)[reply

]

@RegentsPark I will concede to such a perspective.

But, in addition, some sort of (logged) warning needs to be provided about participating in discussions at the t/p in a coherent fashion. As I (and JJ) noted at the 3RRN thread, it is quite a feat to discuss anything with him. You ask him about X, and he replies about Y. TrangaBellam (talk) 17:23, 26 January 2023 (UTC)[reply]

Latest edit. If admins agree that

According to geographer Frederick Drew,It is made up of a very narrow strip, ledge, or flat irrigated ground. Between two distinct stages of the great river cliff. As a result, there is a precipitous drop in ground on one side. While on the other side of the vertical cliff, overhanging the narrow fields, which received their registed heat and quickly ripped the crops, the palaces did not drop their heat even at night. Water flows across the field from a ravine on the high mountain. Apple trees, apricot trees, mulberry trees, and vines are all grown. In association with the cereal, on the narrow space and thrive well with the mixture of moisture and warmth.

is mainspace-worthy content, what can I say? TrangaBellam (talk) 09:01, 27 January 2023 (UTC)[reply]

@Elinruby: You write, Kargil, one of the villages in question, is *on* the line of control and is occupied by the Indian Army. - Kargil is a city, and the headquarters of the eponymous district but it is not a village. Two of the four Brokpa villages lie in Kargil, and the remaining two in Leh. None of these four villages lie *on* the LOC. None of these four villages are "occupied" by the Indian Army. If you persist in misrepresenting sources, the next AE thread will be on you.

@RegentsPark: I guess the sanction is decent and there really isn;t any way to enforce coherence in t/p discussions. I can only hope that we are not kicking the can down the road :) TrangaBellam (talk) 10:36, 28 January 2023 (UTC)[reply]

Notification of the user against whom enforcement is requested

Notified

Discussion concerning Minaro123

Statements must be made in separate sections. They may not exceed 500 words and 20 diffs, except by permission of a reviewing administrator.
Administrators may remove or shorten noncompliant statements. Disruptive contributions may result in blocks.

Statement by Minaro123

1^[1] I have welcomed TrangaBellam to welcome a have a constructive critisim here regarding the Map and i told him I could be wrong ,^[2] and since Indian book deport was established before 1936 ^[3],i added it only in a talk section to have a opinion about others editor.
2,4: I have added the information cited by international reliable newspaper like BBC^[4] news,The hindu ^[5], Aljezerra , The Hindu says which cited that" One theory says they arrived from Gilgit, Pakistan in the seventh century; a popular story is that they are descendants of Alexander’s army, while many argue that the Aryans are the indigenous inhabitant of india^[6]. I talked about it in a talk section ,but TrangaBellam have ignored it and added the newspaper like Mint which have a no mention under the reliable newspaper by wikepedia .
3: I tried to explain to TrangaBellam to add a geographical boundaries in a lead because Aryan valley is a geographical area and have a boundary , because TrangaBellam have removed the part which was backed by reliable sources here ^[7] .
5: I wanted them to add about geography and History of Aryan valley^[8] , now i have added the content in geography section of Dah, Ladakh.
6: I wanted them to emphasis the Aljezerra cited that " Brogpas do not associate their Aryanism with its ‘dirty and cruel’ history in Germany and elsewhere" .^[9] TrangaBellam and other were adding mainly about 'Aryan association ' in the history section so I was afriad that i could go against the reality. I have said the statement in this context.
6: I have created a 13 Topic in active discussion page ^[10][11] Aryan valley ,and has a actively participating in talk page .

My major contribution related to the topic of Aryan valley is: ^[12] In a old revision of Brokpa page ,the population of the Brokpa was false however i have discussed in Brokpa talk section ^[13]title=Brokpa&oldid=1124611839 And add a corrected it .

The

Thank you Minaro123 (talk) 22:14, 23 January 2023 (UTC)[reply]

Statement by Elinruby

The thing that strikes me the most here is the utter certitude of TB and K3 of the correctness of their actions. Bookku is correct in saying that this is fundamentally a content dispute. My issue is the way it's been addressed. I first became aware of the article at AfD, where the rationale was that the residents of Aryan Valley weren't *really* Aryan.

Nobody in this story here claims that they are, mind you, but the important part is that the article survived AfD because it was about a place, not a people. That night it was edited into an article about how the people of the area are not really Aryans, over repeated attempts to discuss, as recent as yesterday.

I did want to address Bookku's concern about quality. Recent deletions include cited work by me about apricot and barley cultivation, and cited ethnography]. Nobody is suggesting that the article should not meet normal standards, which is why I suggested AfC. I would not oppose requiring him to publish that way, if my assurances that I will help don't seem sufficient. Meanwhile, having edited Aryan Valley into something unrecognizable, TB filed a 3RR complaint, and this complaint, and is currently trying to redirect another village article to the article about how the people who live in Aryan Valley aren't really Aryan. all within the last couple of days. Elinruby (talk) 19:42, 24 January 2023 (UTC)[reply]

(Earlier) Minaro123 wants to write an article(s) about a group of villages. I was under the impression that we encourage that. He is willing to learn the standards and apply them. For example, Wikipedia does indeed have a list of perennial sources. I don't know where "exhaustive" came from. He really does need to figure out how to run spell-check however, yes.

I remain baffled as to Trangabellam's goal. I think Mindaro123 should work on his articles, offline if necessary, and publish them through AfC. I will continue to help him. TB should be admonished about newbie, biting, and encouraged to find something else to do.(later: besides the Aryan-ness of the Minaro, that is)

The current version of Aryan Valley should be moved to Aryan Valley (problems Trangabellam has with the name) The central issue here is however that it isn't up to TB to decide whether Minaro123 is competent or what ethnic group he belongs to. To the extent that he's a problem, it's being addressed. At this point it may as well be in Draft, since the article he was writing is gone. At that point the AfC process can be a failsafe, if anyone is worried about his English. I don't think he realizes how bad it is, but I do and will work with him on ways to deal with that, by editing the article myself if need be.Elinruby (talk) 23:10, 23 January 2023 (UTC)[reply]

TB reverting my statement

Could someone please explain to TB that they are involved? I'm under the impression that the policy they cited doesn't apply here. If I'm wrong about that, I will rework the statement to include the words they questioned, although it all seems off-topic to me. I would appreciate a clarification that TB is a party here. I now need to be offline for a while, will address this on my return. Elinruby (talk) 20:43, 24 January 2023 (UTC)[reply]

Housekeeping

TB presents themself as a subject matter expert, so it did not occur to me that this editor would not realize that Minaro123, participant in many a discussion about the oral history of the Minaro, is a member of the Minaro ethnic group. Apparently TB believes that the above account somehow accuses them of outing an editor who has their name and all of the IP addresses they have used on their user page. It would not have occured to me that it could be read this way. I am not interested in TB. I just want Minaro123 to be allowed to contribute an article. Hopefully this clears up any confusion. Elinruby (talk) 00:10, 25 January 2023 (UTC)[reply]

@Kautilya3:. Yes. My question is why? Elinruby (talk) 01:32, 25 January 2023 (UTC)[reply]

@Bishonen: Thanks. I stand by it fine. I just think it's off-topic. But by all means if somebody disagrees.

@TrangaBellam: (trying again) You keep telling Minaro123 that the Minaro are Bropka Elinruby (talk) 11:41, 25 January 2023 (UTC)[reply]

@RegentsPark: sure. That is why I called the whole ethnicity thing off-topic. Just saying, my neighbors would get upset if someone assigned them some other ethnicity. Some exasperation is understandable, especially when it was cited ethnologists that were getting dismissed, not just the elders of Dha. All of the effort that went into discussion here was completely one-sided. I don't pretend to understand what TB is trying to accomplish, but they essentially gutted the Aryan Valley article and are now piously lecturing me on my talk page about the integrity of content. I will be offline most of the day but will check this when I get back to see if there are questions Elinruby (talk) 18:44, 25 January 2023 (UTC)[reply]

@Bookku: I strongly support the adoption of the articles. I am particularly concerned about Aryan Valley, which was transformed overnight into something other than the article that survived AfD. By the people calling his objections disruptive editing. Please let me know if I can help.

@RegentsPark: I noticed you crossed out the part about Minaro123 taking a break. He has exams coming up and needs to take a break. I am encouraging him to focus on his exams. He is upset about this episode however. As for what to do about this complaint, yeah, I proposed the AfD restriction. I have said I'll help him, but a formal process won't hurt him, since we agree that there's a problem there, and nothing is stopping me from helping him on a draft. I would like to mention that when I first encountered him at the AfD, he was citing the elders of Dha, so the fact that he is citing ethnologists is vast progress in a couple of weeks, and he does learn. I have some concerns about 1RR however, since I would have thought that it would apply in any event to all parties given that the area in question abuts the Line of Control. Could you please clarify what discretionary sanctions apply to these articles? And that they apply to all editors? I'd appreciate it. Elinruby (talk) 18:55, 27 January 2023 (UTC)[reply]

@RegentsPark: I admit that I am out of my area of expertise here, but frozen or not, that conflict is ongoing, is it not? Kargil, one of the villages in question, is *on* the line of control and is occupied by the Indian Army. Dah is 40-some miles from the front. I don't claim to fully understand this dispute, but I can understand why Minaro would object to repeatedly being told that his ethnic group believes they are Aryan. The point I don't understand is why TB is so adamant in saying it, based on that one sociologist they keep citing, to the point of promo. Clearly, strong feelings are involved, is all I am saying, and if DS is going to be applied then I personally think it should be applied to all involved. Thank you for your previous reply, btw. I am not trying to give you a hard time, but I'm just not sure that the proposed solution addresses the entire problem. I will of course abide by whatever you decide and will try to help Minaro123 to do so. I do think there is a lot of merit in Bookku's suggestion, fwiw. Elinruby (talk) 20:39, 27 January 2023 (UTC)[reply]

Statement by Bookku

Uninvolved opinion.

• Two very recent edit summaries 1, 2 by User:Minaro123 seem to have expressed psychological depression as co-Wikipedian I feel concerned.
• Above complaint in part seems to be content dispute brought here before completing protocol mentioned @
  WP:DDE
  and in part legitimate linguistic abilities concern.
• IMO content disputes are best resolved through regular
  WP:DR
• Info @ User:Minaro123 and writing style indicates that Minaro123 seem to represent some linguistic minority, though they seem to understands English reading, they would need little more improvement in English proficiency and some support while writing. Another user seem to willing to provide such linguistic support to them (appreciated).
• IMO We certainly allow them continue to write in own user space, Draft and AFC.
• And also allow participate in main space talk page discussion in spite of linguistic difficulties. Many say, even billion plus populations feel they are not best represented on Wikipedia, if some one from very small communities feel so, we can not do much about it if Reliable sources do not support.

Still I feel we should not take their right to represent their and their community's encyclopedic concerns on the respective talk pages. And not curtail right to WP:DR through WP:ARE.

Bookku (talk) 07:18, 24 January 2023 (UTC)[reply]

As I already admitted and again pointed out by @TrangaBellam concerns about English grammar of @Minaro123 even in their good faith edits seem quite legitimate as of the day.

• Let @Minaro123 focus on their studies.
• Shift all concerned articles to draft namespace.
• Each of us experienced users will adopt two two articles each develop in a years time with minimum expectation of WP standard.
• I am ready to adopt two such drafts for non-disputed content from my side.

Bookku (talk) 13:53, 27 January 2023 (UTC)[reply]

Statement by Kautiya3

I am not writing a full statement here since the user seems to be voluntarily withdawing. But to drive home the CIR issue, he was told on 20 November 2022 the need for

The user has been editing for more than a year and is extended-confirmed. If he still appears to Elinruby as a "newbie", that itself is an indication of a CIR issue.

We have also had to face edit-warring/tag-teaming from apparent members of the ethnic group, who are variously called Brokpa/Dard/Minaro/Aryan. So this doesn't stop with one supposedly "newbie" editor. -- Kautilya3 (talk) 08:46, 24 January 2023 (UTC)[reply]

A gentle reminder to Elinruby that he is editing a section titled "Discussion concerning Minaro123". It is not a discussion concerning TB or K3 or AfD's or page titles or barley cultivaion. -- Kautilya3 (talk) 01:13, 25 January 2023 (UTC)[reply]

Tsewang Namgyal conquered "Lhasa" using an absolutely junk source. -- Kautilya3 (talk) 18:18, 26 January 2023 (UTC)[reply

]

• This conflict is above my paygrade, but I want to comment (only) on Elinruby changing their statement and Tranga Bellam reverting that change, per Elinruby's
  WP:REDACT does not apply here, Elinruby. If you redact, in a significant way, something that has been replied to, you wrongfoot the person/s who replied. Don't do it. Even if there were no policy or guideline about it, it's confusing and discourteous. What's wrong with crossing out? However, a problem with Tranga Bellam's revert is that it removed the quite different text that you added in place of your original statement. You are most welcome to re-add that text yourself. (It needs a spellcheck, though.) Feel free to change or shorten it in any way you like, or leave it out, since nobody has replied to it. But please use cross-out for your original statement, if you no longer stand by it. Bishonen | tålk 22:05, 24 January 2023 (UTC).[reply
  ]
• In a nutshell, it appears that, while editing in good faith, there are competence issues with Minaro123's edits. The question, I guess, is which one outweighs the other. I'll take a look but, meanwhile, Elinruby, please note that the stated ethnicity of any editor is not something that should be used as a pro or con in an argument. Wikipedia is a
  reliably sourced encyclopedia, not a crowd sourced one. --RegentsPark (comment) 13:51, 25 January 2023 (UTC)[reply
  ]

  After reviewing Minaro123's edits, yes, there are competence issues. I see examples of improper sourcing (e.g., here where did the literacy rate come from and the household number is less than half of what is in the source), and lots of moving stuff around breaking the relationship between the content and the citation (e.g. here). And then there is the unskooled book mentioned by Kautilya3 as well as the use of raj era sources. That said, the editor appears to be taking a break and has made an incremental contribution to wikipedia. I'm inclined to just let this pass lightly, perhaps by placing a 1RR restriction to reduce the probability of edit warring when they return. --RegentsPark (comment) 22:40, 25 January 2023 (UTC)[reply]

  @TrangaBellam: my thinking is that a 1RR restriction will alleviate problems associated with the sloppy sourcing. Perhaps I am wrong but they do seem to be adding content in a relatively underserved area and we don't want to throw the baby out with the bathwater. --RegentsPark (comment) 17:17, 26 January 2023 (UTC)[reply]

  @Kautilya3, Bookku, TrangaBellam, and Elinruby:. I guess the draft space restriction is reasonable. So, a 1RR restriction and article creation and submission through AFC? --RegentsPark (comment) 15:56, 27 January 2023 (UTC)[reply]

  @

  WP:ARBIND. The existing 1RR restriction that you refer to, afaik, pertains only to articles related to the Kashmir conflict. --RegentsPark (comment) 20:06, 27 January 2023 (UTC)[reply

  ]

• 1RR and article creation through AFC sounds reasonable to me based on what's been presented here. Callanecc (talk • contribs • logs) 10:48, 28 January 2023 (UTC)[reply]

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

Request concerning SashiRolls

User who is submitting this request for enforcement

Tryptofish (talk · contribs · deleted contribs · logs · filter log · block user · block log) 15:43, 23 January 2023 (UTC)[reply]

User against whom enforcement is requested

SashiRolls (talk · contribs · deleted contribs · logs · filter log · block user · block log)

Search CT alerts: in user talk history • in system log

Sanction or remedy to be enforced

• [1] 1-way IBAN with me, as an AE sanction
• [2] 1-way IBAN with me reaffirmed by the community a week ago (January 15), as a condition of unbanning. From the close: There is very little rope left on the coil, and I cannot imagine another unban gaining consensus.

Diffs

of edits that violate this sanction or remedy, and an explanation how these edits violate it

• [3] Giving me a "thanks" notification for an edit I made, January 22, 2023.

Additional comments by editor filing complaint

Facepalm This is so far beyond "I told you so", that I can't believe I have to post this.

It's a relatively small thing, to "thank" someone, and on the face of it, not something one would normally expect to result in sanctions. But, our

Under the circumstances, though, it seems to me that he should have made it his business to know what the IBAN rules are. And there was no particular reason for him to have thanked me for that edit I made ([4]). It was completely unrelated to anything I'm aware of him doing, and I don't see him making an edit in that RfC after I made that formatting fix. From my end, it feels creepy, like he was following edits I made and letting me know that he was seeing them. Although I'm under no restrictions under the 1-way ban, I actually have no idea what edits, if any, SashiRolls has been making, because I'm not concerning myself with that, and I sure didn't ask for that blue notification that brings me here. --Tryptofish (talk) 15:43, 23 January 2023 (UTC)[reply]

Following up after the comments so far, I find it plausible that it was a matter of inadvertent mis-click/mis-swipe. Not unlike someone accidentally hitting rollback on a 1RR page, and then quickly self-reverting – except that here, there is no way to self-revert. As I already said, I'm OK with a firm understanding that this will absolutely not happen again, and I'm not comfortable with a severe sanction. But there's no getting around the fact that SR was viewing my edit when the error happened, which, in the future should be a big flashing red light that when you are viewing anything I've done, be very, very careful.

I think that Politrukki's comments directed at me are worthy of administrators taking note, and I am seriously sick and tired of this kind of conduct. (Seriously, the fact that I didn't go back and check whether SR had edited the page earlier indicates that I could have followed SR there and somehow manipulated him into thanking me? Yes, in filing this AE request, I checked if he had also been editing there around the time that I edited there, in case it was an inadvertent thank, but in fact I didn't check the whole page history, because I'm not looking for SR's edits.) Anyway, I think that Floq has read the situation astutely. --Tryptofish (talk) 00:36, 24 January 2023 (UTC)[reply]

Also: seeing Vanamonde's comment about Mr Ernie, I understand Mr Ernie's comment in the context of discussions that he and I have had, and his comment was not a sarcastic one. I appreciate it. --Tryptofish (talk) 00:39, 24 January 2023 (UTC)[reply]

Notification of the user against whom enforcement is requested

• [5]

Discussion concerning SashiRolls

Statements must be made in separate sections. They may not exceed 500 words and 20 diffs, except by permission of a reviewing administrator.
Administrators may remove or shorten noncompliant statements. Disruptive contributions may result in blocks.

Statement by SashiRolls

I had no intention of having any contact whatsoever with my accuser. I think this must have been due to a careless swipe closing a window while looking through the RfC on Vector 2022 last night. When blocked, the giant 'thanks' button did not appear at the bottom of the screen on the phone app, so I'm used to just swiping from bottom to top to make the app disappear.

I am aware that thanking someone is not permitted and would not have done it intentionally.

It is my assumption that wp:banex allows me to reply to this immediate escalation.

I will look into this further when I get home from the hospital this evening, as normally I thought you had to confirm to give thanks, which I certainly did not do... unless the dialog box was also swept away in the effort to close the window.

-- SashiRolls ^{🌿 · 🍥} 16:45, 23 January 2023 (UTC)[reply]

I have just checked and indeed no confirmation is necessary on Android... You have two seconds to cancel if you misclick / mis-swipe. -- SashiRolls ^{🌿 · 🍥} 16:52, 23 January 2023 (UTC)[reply]

Please do not accuse me of lying. I guarantee you I just thanked SFR and was given only 2 seconds to cancel using Chrome on Android. Talk about a gotcha' filing and a wp:agf failure.  :/. -- SashiRolls ^{🌿 · 🍥} 17:26, 23 January 2023 (UTC)[reply]

Again, please do not accuse me of lying. I just thanked Bishonen for her comment and was unable to take a screenshot of the tiny line of text appearing beneath the BIG BLUE BUTTON at the lower right of the screen where your thumb goes to swipe Chrome into the background on Android. It disappeared that quickly. I may have mispoken when using the word "app". It is for Commons that I sometimes use the App, but apparently I need to redownload it because it hasn't worked for months now. I assure you, I had absolutely no intention whatsoever of interacting with him. -- SashiRolls ^{🌿 · 🍥} 18:19, 23 January 2023 (UTC)[reply]

Nableezy: on pages with significant amounts of text scattered all over the place (such as in the Vector 2022 RfC) I find the easiest way to read, by far, is by going to the top diff and then clicking "previous diff" so that I have enough context to understand what's going on. Perhaps in future, this method of reading would be best avoided as it apparently makes inadvertent errors such as this one possible. Thanks to those who compensated for my incompetence in video capturing using my phone! -- SashiRolls ^{🌿 · 🍥} 19:15, 23 January 2023 (UTC)[reply]

@Isabelle Belato: It's alright: no blood, no foul. I've gotten my heart-rate back down now and appreciate the comment below explaining that diff-viewing is a reasonable way of reading a complicated discussion (but that has unexpected risks on mobile). I was unaware of these risks because while blocked I did not see a thanks button. I don't believe this inadvertent mistake warrants any further sanctions and would ask for whoever closes this to put themselves in the position of someone (me) who had a heart attack during their three-week long appeal and who did not appreciate this thread. Granted, I can put myself in the shoes of the person KoA describes below as having been the victim of a terrible "car crash" I caused and see that they might want retribution for such reckless swiping.

My apologies for my inadvertent role in this. I would like to be able to continue to thank people and so I will avoid flipping through diff-view in mobile should either of the good users I'm i-banned with come gnoming in threads I've previously made comments in. This will surely help avoid offended reactions. I would prefer to be able to continue to thank helpful users like yourself.

I would ask that no further comments be made about my cardio-vascular health anywhere on en.wp. -- SashiRolls ^{🌿 · 🍥} 20:12, 23 January 2023 (UTC)[reply]

Statement by KoA

And here I just caught myself earlier today thinking I hadn't heard anything about SR since their unban (and hadn't gone looking either until I saw this).

All I'll say is that multiple editors in the unban discussion did mention one of SR's issues is a sort of stalking of targets that warranted the sanctions in the first place. That context matters even if it were just a little thing that wasn't directly spelled out in ban policy instead of this. Tryptofish was correct to come here in part because there is no other realistic option to discuss an I-ban violation even when it's one-way. Otherwise, it would be like someone who caused a car crash (accident or not) chastising one of those who got hit for asking the cops to get involved.

Regardless of intent or accident, SR already knows they are supposed to steer clear of Tryptofish, and

Others that can test it can assess the validity of the Vector 2022 comments, but what led to the interaction can also become a red herring from later behavior, so that's why the comments caught my eye. KoA (talk) 18:11, 23 January 2023 (UTC)[reply]

• Nableezy, Tryptofish linked the diff in their section that was thanked.[6]. As you mention, SR was there at that discussion too (basically that they wanted to keep the Vector 2022 and that they were already familiar with it from the French wiki).[7] It at least makes sense that the interaction was because they crossed paths there and not through contribs. KoA (talk) 18:59, 23 January 2023 (UTC)[reply]
• Sashirolls, you know better with respect to Granted, I can put myself in the shoes of the person KoA describes below as having been the victim of a terrible "car crash" I caused and see that they might want retribution for such reckless swiping. You're already being warned to stop sniping at AE and likely to get by with just a warning despite ramping up the battleground behavior again. You are the one who "crashed" into Tryptofish in this case regardless of intent, and instead of lashing out like in the analogy, all you needed to do was recognize the problems it caused other editors in showing it was an accident rather than use the opportunity to take unneeded potshots and go beyond
  WP:BANEX with respect to your I-ban. KoA (talk) 22:41, 23 January 2023 (UTC)[reply
  ]
• On Buffs' and Politrukki's comments, I will remind both of you not to violate the
  WP:ASPERSIONS principle that is in effect here being a GMO DS discussion in your comments on Tryptofish. Admins have been letting enforcement of that slip lately. KoA (talk) 15:16, 24 January 2023 (UTC)[reply
  ]

Without making any other statement or claim as to this filing, I just wanted to point out, @ScottishFinnishRadish @Isabelle Belato-- @SashiRolls is talking about using the mobile site on the Android Chrome app. Not using the Wikipedia for Android App. Very different interfaces on iOS between these two so I can imagine it's similarly very different on Android.

I just tested it (on @Tewdar ) on iOS Chrome mobile version on the DIFF (not the history or contribs pages) and indeed, it only gives 2 seconds to cancel before it goes through with the thank action. On the history or contribs pages, the "thank? confirm cancel" persists, but on the DIFF, it is ephemeral.— Shibbolethink ^{(♔ ♕)} 18:27, 23 January 2023 (UTC)[reply]

Statement by Tewdar

If you view a diff using a mobile web browser (Chrome, Firefox, Opera...) and hit "thank", it gives you two seconds to cancel, without confirmation.  Tewdar  18:35, 23 January 2023 (UTC)[reply]

Just tested with Shibbolethink 😁.  Tewdar  18:38, 23 January 2023 (UTC)[reply]

Statement by Nableezy

What was the diff Tryptofish? Because personally I'd be willing to buy it was an accident that I will make sure will never be repeated if it was a diff from a discussion SR was involved in, but if they just randomly trolling through Tryptofish's contributions to go through them for god knows what then I personally would say it doesnt matter if it was an accident, block for the IB vio anyway. nableezy - 18:49, 23 January 2023 (UTC)[reply]

oh nvm see it linked in your statement. Given that SR had already commented in that discussion I suppose it was possible they were just going through more recent comments. But honestly I dont get why youd even be on somebody's diff like that to be in that position in the first place. nableezy - 18:58, 23 January 2023 (UTC)[reply]

Statement by Objective3000

I’m no fan of Sashi, !voted neutral with TBan last time and block on all previous times. I’ve also been sarcastically “thanked” in the past by another editor. But, my feeling on this is Meh. Sashi will have to try harder than this to get blocked again. O3000, Ret. (talk) 19:01, 23 January 2023 (UTC)[reply]

Just not enough evidence to convict, as I would say as a jury member. If convincing evidence appears; I'll wholeheartedly support an indef. O3000, Ret. (talk) 01:06, 24 January 2023 (UTC)[reply]

Statement by Sideswipe9th

I've just sent two videos to ScottishFinnishRadish demonstrating the two different ways that en.m.wikipedia handles sending thanks for contributions. If you're looking at the history for a page, there is a confirmation requirement prior to sending thanks. However if you're browsing by the diff views, sending thanks has no confirmation, and only a 2 second window to cancel as other editors have said. I don't know of any other ways to send thanks via the mobile site. I'd be happy to send these videos by email to any other admins who'd want to see, but I don't want to upload them to files/commons if I can avoid it. Sideswipe9th (talk) 19:05, 23 January 2023 (UTC)[reply]

To nableezy, I often find it significantly easier when reading a highly active page to read through the contributions made since my last view or edit via the diff view. This makes it easier for me to identify which comments/contributions I've seen already and which ones are new. Sometimes I'll do this just as a block of all changes since my last view, and sometimes I'll step through each one at a time, depending on how my attention span is behaving at the time. I imagine other neurodiverse editors will do something similar when catching up on active pages. Sideswipe9th (talk) 19:09, 23 January 2023 (UTC)[reply]

Statement by Mr Ernie

Let me at least use this opportunity to thank everyone who chooses to contribute to Wikipedia. Mr Ernie (talk) 19:21, 23 January 2023 (UTC)[reply]

Statement by Floq

Would the same uninvolved admin who closes this with an assumption that this was an unfortunate coincidence and a weak reminder that SR shouldn't thank TF also remind SR that using terms like "accuser", "immediate escalation, "gotcha filing", and "agf failure" above, about someone they're ibanned from, is also an iban violation? I presume this is SR on their best behavior, and they still can't help but test the boundaries. --Floquenbeam (talk) 19:28, 23 January 2023 (UTC)[reply]

Statement by Buffs

Error or not, the worst punishment appropriate here is a

As for reading through old posts, I know I've done so to see where I could have done better and that means looking through diffs to see what others said too. It seems to be a reasonable mistake...SR, please avoid being even close to such behavior in the future. Buffs (talk) 20:23, 23 January 2023 (UTC)[reply]

Re:Floq's comments, he's being accused of violating his IBan by the same person. Kinda hard to point out the (potential) problematic behavior of another editor here otherwise. Both would do well to drive down the temperature by

WP:AGF more, but due to the IBan, there isn't another avenue to ask and clarify. Buffs (talk) 15:08, 24 January 2023 (UTC)[reply

]

Based on the timeline of SashiRolls's edits and Tryptofish's edit, it could be argued that Tryptofish creepily followed SashiRolls to the page, but I think if TF wished to annoy SashiRolls, TF could have found a better way.

Even though a technical violation happened, the filing is unnecessary escalation. As the two-way IBAN is yet to be reinstated, a peaceful resolution could have been reached by assuming good faith and leaving a message to SashiRolls asking them to refrain from using "thank" function. Moreover, Tryptofish, your claim that "IBAN has no exceptions, footnotes, or special circumstances, full stop" is both

SashiRolls shouldn't say they were accused of lying if they weren't accused of lying, but I believe this is moot after their last comment.

What more there is to be done? Close with no action.

I guess that I am involved because I have commented on the conduct of SashiRolls in the past although not in the recent unblock request, where I was sincerely undecided and chose to remain silent. As is pretty well known, I edit using the fully functional desktop site on Android smartphones, and my thank function requires an affirmative verification before it goes through, because I choose to use fully functional software instead of slipshod WMF software deviations. All that being said, I am perfectly willing to accept that WMF software botchery may well yield a less acceptable result when using any of their less than fully functional sites and apps. But what really concerns me here is the snide, confrontational remarks by SashiRolls that Floquenbeam points out above. This editor is fresh off a lengthy block for this type of behavior, and I was prepared to assume that this editor would refrain from stuff like this, but I guess that I was wrong. Maybe they will now stop behaving this way, or maybe they will continue and get blocked again, this time forever for real. Time will tell, I suppose, but after the comments by SashiRolls above, I am not optimistic about their future as a Wikipedia editor. Cullen328 (talk) 08:08, 24 January 2023 (UTC)[reply]

Statement by starship.paint

@Isabelle Belato, ScottishFinnishRadish, Bishonen, Tamzin, and Vanamonde93: - can we wrap this up? starship.paint (exalt) 07:13, 29 January 2023 (UTC)[reply]

Statement by (username)

Result concerning SashiRolls

This section is to be edited only by uninvolved administrators. Comments by others will be moved to the sections above.

• @SashiRolls: I've tested on the app and on the mobile view on Android and both of them request a confirmation. The app even opens a big window warning you can't undo a thanks. I'd appreciate if another univolved user could confirm this, but right now this appears to be a clear case of breach of sanctions. Isabelle Belato ^🏳‍🌈 17:10, 23 January 2023 (UTC)[reply]

  I just downloaded the app to check, and it certainly asks for confirmation when I did it from the diff view and history view. ScottishFinnishRadish (talk) 18:11, 23 January 2023 (UTC)[reply]

  I've now seen that in the mobile web interface in the diff view there is no confirmation. ScottishFinnishRadish (talk) 19:00, 23 January 2023 (UTC)[reply]

  Thanks Shibbolethink. That's a very odd behaviour and should probably be changed. In that case, this should probably be closed with no action.

  @SashiRolls: Apologies if it appeared that I called you a liar. Exactly because I couldn't reproduce that behaviour (and was unaware of it till today) that I asked for other users to confirm whether it was an actual thing or not. Isabelle Belato ^🏳‍🌈 19:01, 23 January 2023 (UTC)[reply]

• It seems completely incredible to me that this was done on purpose. I could imagine Sashi sarcastically thanking Tryptofish for something meaningful, but Tryp's edit in this instance was the most uncontroversial gnoming. Surely Sashi could and would have found a better way to either annoy or "reach out in a friendly way". Bishonen | tålk 17:20, 23 January 2023 (UTC).[reply]
• Just to avoid a whole lot of debating about technical things, and keeping in mind that it would be a lot harder to sell this as an accident twice (even if it really were an accident both times), could we compromise on SR agreeing to disable the thank button by CSS? (I can take a stab at the correct CSS, but would probably best to ask at
  WP:VPT.) This would be considered an extension of the IBANs, i.e. as long as SR is subject to an IBAN, they would be expected to keep this CSS rule active. Once pblocks from thanking go live (which has seemingly been a month away for ~18 months), we could switch to that if desired. -- Tamzin^{[cetacean needed]} (she|they|xe) 18:58, 23 January 2023 (UTC)[reply
  ]

  @Tamzin: I guess if SushiRolls agrees with it, then sure. Otherwise, my recommendation to them would be to avoid checking the diffs by users they are iban'ed with while on mobile to make sure this doesn't happen again. Isabelle Belato ^🏳‍🌈 19:04, 23 January 2023 (UTC)[reply]

• Based on the evidence that no confirmation is required on a tiny mobile screen, and that this was a discussion SR was already participating in, I don't any action needed on the original complaint. I'm a little less impressed by the language used by SR in response to said complaint, and also in the responses to the response (Mr. Ernie, what exactly does your statement above achieve?) per Floq. I would support closing with a reminder to SR both about the IBAN and about temperate language at AE. Vanamonde (Talk) 19:37, 23 January 2023 (UTC)[reply]

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

Request concerning CanterburyUK

User who is submitting this request for enforcement

Shibbolethink (talk · contribs · deleted contribs · logs · filter log · block user · block log) 17:49, 27 January 2023 (UTC)[reply]

User against whom enforcement is requested

CanterburyUK (talk · contribs · deleted contribs · logs · filter log · block user · block log)

Search CT alerts: in user talk history • in system log

Sanction or remedy to be enforced

• WP:GENSEX
• WP:ARBBLP

Diffs

of edits that violate this sanction or remedy, and an explanation how these edits violate it

1. Within the past month or so, has become a quasi-
   WP:TPG
   in numerous ways.
2. Violates 1RR to re-insert preferred text with more favorable descriptions of Peterson and disfavorable of others: [8][9][10] Edit: [ See diffs below ] See also: [11] and second 1RR vio: [12][13][14]Edit: [ See diffs below ] (also adding meta-commentary to page [15])
3. bludgeons discussions by repeatedly raising arguments in new sections (user has made 15+ on talk in the past 20 days) ([16][17][18] - more diffs available upon request) despite warnings by myself and others: [19][20][21]. Forcing others to fix fragmentation [22]
4. placing their comments above others or otherwise increasing prominence [23][24][24][25]
5. replying to multiple users' with the same argument ([26][27][28][29]) and demanding users respond to past arguments when users have already replied (
   WP:SEALION
   ).
6. adds "close and summary" to thread they started, ignoring others' comments and asserting preferred outcome [30] [31]
7. Repeatedly placing usernames in talk section headings in violation of
   WP:TPG: [32][33][34] despite warnings [35]
8. Using blatantly unreliable sources: Google drive, twitter, "countersignal", "thepostmillenial" to support pro-Peterson insertions [36][37] despite warnings [38] [39]
9. Justification for behavior is to make the page "most helpful to the reader" [40] and to "rebalance the bad influence the page has been" [41] AKA
   righting great wrongs
   .
10. This is not the first time they've been brought to a conduct board regarding NPOV, sources, TPG, and edit warring (though it was a long time ago, 2017): [42] or warned about disruption (2018)

Diffs of previous relevant sanctions, if any

N/A

If

WP:AC/DS#Awareness and alerts

)

• User received alerts about DS in these areas in the last twelve months, on 8 January 2023 and 12 January 2023.

Additional comments by editor filing complaint

In summary, per the diffs above, this user has recently focused a single-minded effort on providing more favorable coverage of

I propose the user be indefinitely topic-banned (or page-banned) from Jordan Peterson, as the most narrowly-targeted remedy which would stop this disruption. Thank you for your time and attention.— Shibbolethink ^{(♔ ♕)} 17:49, 27 January 2023 (UTC)(06:53, 28 January 2023 (UTC) edited to strike confusing diffs, replace, and lay it out in chronological order below)[reply]

Note: I apologize for the number of diffs and words. I think I have probably exceeded the 20 diff limit. I request an exception in this case given that the behavior in question from this user involves many repeated actions which require diff evidence for each. Happy to remove some of the repeat diffs and/or reduce word count as requested. Thanks — Shibbolethink ^{(♔ ♕)} 17:59, 27 January 2023 (UTC)[reply]

Notification of the user against whom enforcement is requested

17:48, 27 January 2023 (UTC)[reply]

@Mr Ernie

Evidence of 1RR vios

1. 22:32, 6 January 2023[43] CUK inserts header, cites twitter, Daily Mail, and other deprecated sources.
2. 22:57, 6 January 2023 SFR reverts to stable.
3. 14:55, 8 January 2023[44] CUK reinserts header and deprecated sources. (That's revert #1)
4. 15:50, 8 January 2023 I revert to stable.
5. 22:00, 8 January 2023 CUK again reinserts header and deprecated sources. (That's revert #2)

Later....

1. 11:53, 12 January 2023 CUK reinserts header and adds protest content with unreliable source (That's revert #1 - the header)
2. 16:03, 12 January 2023[45] FFF removes header and the UNDUE protest content
3. 23:07, 12 January 2023 CUK reverts FFF trimming of UNDUE (That's revert #2)
4. 23:16, 12 January 2023 SS9 restores stable
5. 24:19, 12 January 2023‎ CUK re-inserts Poilievre comments (part of the content block from 6 January 2023) (That's revert #3)

1RR says: An editor must not perform more than one revert on a single page—whether involving the same or different material—within a 24-hour period (emphasis mine) Neither of these were "consecutive reverts" aka sequential edits, to my understanding. Unless I'm missing something? — Shibbolethink ^{(♔ ♕)} 06:16, 28 January 2023 (UTC)[reply]

Sorry for the delay, I was waiting to see if CUK would respond! But I suppose he's had 48 hours now, and hasn't popped in. Regardless, I am not sure his response would change much about this situation.

I am inclined to agree with Sideswipe, FFF, and Girth Summit, the degree of passion CUK has displayed here, and the

WP:PAGs, and consider carefully how they behave on talk pages and in reverts/bold edits in controversial areas. Hopefully they correct they behavior and nothing else will be necessary! Thanks for all the help and input here, I think the PBAN will at least serve to stabilize that article space for the future.

Best,
Shibb — Shibbolethink ^{(♔ ♕)} 17:45, 29 January 2023 (UTC)[reply

]

Statements must be made in separate sections. They may not exceed 500 words and 20 diffs, except by permission of a reviewing administrator.
Administrators may remove or shorten noncompliant statements. Disruptive contributions may result in blocks.

Statement by CanterburyUK

Statement by Sideswipe9th

My thoughts on CanterburyUK mirror much of what Shibbolethink has said, so I'll keep this brief for now. I think a PBAN or TBAN from the Jordan Peterson article and talk page would be the narrowest remedy that applies here. However with Canterbury's propensity for sealioning and repetitive arguments, I do worry that such a narrow sanction would just shift this problem to another article and talk page in the same content areas. Sideswipe9th (talk) 18:39, 27 January 2023 (UTC)[reply]

As I said before, while a PBAN from the Peterson article and talk page is the narrowest remedy that'd apply in the circumstances, I do fear that such a narrow sanction will just shift this behavioural problem to another article and talk page, in the same or closely related content areas. Sideswipe9th (talk) 01:16, 29 January 2023 (UTC)[reply]

Statement by North8000

(Pinged) I did a quick read of the entire talk page and a quick scan of the edit history of the article. I did not analyze anything related to 1RR nor do an in-depth analysis. I don't see sanctionable behavior. The "favorable" coverage described looks like mostly straightforward informative info, something that persons desiring a negative article on him would want left out. The "above other editors" posting looks like proper talk page protocol where doing otherwise would have been wrong. While IMO the current level of talk page activity is IMO not problematic, my advice to CanteburyUK would be to dial it back a bit. Sincerely, North8000 (talk) 19:48, 27 January 2023 (UTC)[reply]

Statement by Mr Ernie

I’m not seeing a clear 1RR violation in the posted diffs (sequential edits are considered to be counted as one). And the bludgeon thing can be a bit subjective. Shibbole you made a couple hundred edits to a recent AN thread, and nobody really thought that was sanctionable. That said, I would support a warning related to making sure to use reliable sources. Mr Ernie (talk) 01:09, 28 January 2023 (UTC)[reply]

Statement by Firefangledfeathers

I doubt advising CanterburyUK to "dial it back a bit" will work. I worked hard to help them understand 1RR after their first violation (discussion), ending with a warning "not to make it the beginning of a pattern". They broke the rule four days later.

Shibbolethink tried here to get them to dial back their talk page section creation, but they've created four more since. I'd be less (though still plenty) concerned about the bludgeoning if they didn't take silence as agreement. Firefangledfeathers (talk / contribs) 07:11, 28 January 2023 (UTC)[reply]

North8000, did you only review the first diff when it comes to The "above other editors" posting? The second diff is problematic; I'd be surprised to learn you countenance that behavior. Firefangledfeathers (talk / contribs) 07:11, 28 January 2023 (UTC)[reply]

@Firefangledfeathers: Thanks for pointing that out, I looked at the second one too quickly and missed that. North8000 (talk) 14:46, 30 January 2023 (UTC)[reply]

Statement by Girth Summit

I think that Shibbolethink is correct that this user's contributions do essentially amount to disruptive sealioning. The issues first came to my attention when I realised that they had added some stuff to 'balance' critical comments in the article about a meat-only diet, when the source was actually comparing vegetarian diets to diets that contain some meat - in other words, it was irrelevant, and a misuse of the source to push a particular POV. A rookie error, perhaps, and not really something to worry about, but the have continued in the same vein, attempting to crowbar in Peterson-friendly material using primary sources, Tweets and so on, and their habit of adding numerous, needlessly verbose and repetitive comments have turned the talkpage into a completely impenetrable wall of text. This habit is a bad combination with their willingness noted above by Firefangledfeathers to interpret silence as consensus - the impression I get is of someone trying to wear everyone else down by relentless argumentation, in hopes that other editors will let them get on with what they want to do out of sheer exhaustion. Some time away from this article, and editing others that they are less personally invested in, might help them develop their understanding of how talk page discussions and the consensus-building process work here. Girth Summit _(blether) 13:07, 28 January 2023 (UTC)[reply]

Bishonen - I can't speak for Shibbolethink, but I predict that a TBAN will ultimately be necessary to stop this spreading elsewhere. I'm happy to wait and see, and will be happy to be proved wrong, but I can't say 'I told you so' if I didn't tell you so. Girth Summit _(blether) 18:29, 28 January 2023 (UTC)[reply]

Statement by Snow Rise

I'm a little torn here. On the one hand, the issues with the bludgeoning on the talk page (at least such as I observed in the brief window of my recent participation there) are quite pronounced, with the impact of the sheer number of rapid fire discussions opened (and the high volume of responses to other editors in those discussions) being further exacerbated by the size and wall-of-text nature of those replies, as well as a problematic unfamiliarity with standard talk page formatting and protocol. To understand what I mean, one need only do a superficial, high level visual review of the state of the TP as it presently reads. And that is before one even explores the details of what CanterburyUK actually advocates for, which to my eye, seem to suggest a fairly consistent confirmation bias when reviewing the sourcing, such as to exclude information which casts Peterson in anything less than a hagiographic light, regardless of the overall

On the other hand, we are talking about a relatively inexperienced editor here: yes, they have been on the project since 2008, but have only logged a little under 600 edits in that time, with gaps up to years in duration. With a pattern of involvement like that, it's possible that this is a sleeper sock account running parallel to others during that time, but I've seen no suggestion of that by any other community member, and absent at least that, I AGF this is just someone who occasionally gets the bug to edit on very particular political/BLP topics with hyperfocus over bursts of time: we do afterall get some genuine serial-SPA editors in that respect. That being the case, I'm not seeing a whole lot in terms of brightline policy violation just of yet. Obviously something substantial needs to change with regard to this editor's approach, and their talk page is kind of a mixed bag of concessions to that fact when engaging with some editors who have used a softer approach, while verging on

Perhaps Bish's action in implementing the current pageban is the correct approach in threading the needle, removing CanterburyUK from a very narrow space (where they are being particularly activist) for the time being, while maintaining most of their editorial permissions. Again, afterall, I can't say that I don't think that was where we were headed eventually anyway. But by the same token, had I arrived here before that action was taken, I think on the balance of things I would have advocated for no formal action just yet, purely to be pro-forma with giving this editor time to adjust their approach short of sanction. SnowRise ^{let's rap} 21:55, 28 January 2023 (UTC)[reply]

Yeeps, had to shorten this after I realized I had blown past the word count: in order to expedite that process, I simply removed an entire paragraph, in addition to other cuts, no doubt leaving my comments a little disjointed: anyone interested can see my original un-amended comments here. SnowRise ^{let's rap} 22:03, 28 January 2023 (UTC)[reply]

Statement by SchroCat

Rather like Mr Ernie above, I don't agree with the characterisation of the diffs (they can be hugely misleading without context), and sequential reverts are often considered as only being one, (except when people want to weaponise 1RR or 3RR restrictions). I also agree that bludgeoning is subjective and just counting comments doesn't give evidence or proof of anything. As to SEALIONING (dear lord, where do these ridiculous terms come from), again that's a subjective thing. CUK has made 44 edits on Jordan Peterson (they are 9th on the list of most active editors on the page); the person bringing this case has made 57. If you want the stats on bludgeoning accusation, CUK has made 138 edits to the Peterson talk page and are only 7th on the list of editors by volume on the page; the person who opened this thread has made 193.

While CUK may not be a model editor, I don't see their behaviour as sanctionable, particularly on the "evidence" presented. - SchroCat (talk) 17:42, 30 January 2023 (UTC)[reply]

Statement by (username)

Result concerning CanterburyUK

This section is to be edited only by uninvolved administrators. Comments by others will be moved to the sections above.

• I've page-blocked CanterburyUK indefinitely from Jordan Peterson and Talk:Jordan Peterson per Shibbolethink's diffs. That seems both obvious and minimal. Leaving this open in case somebody thinks there needs to be a topic ban as well, to prevent the Jordan Peterson-related disruption from moving to other pages. What do you say, @Shibbolethink:? Bishonen | tålk 13:36, 28 January 2023 (UTC).[reply]
• Everything here relates just to the JP page, so I think Bishonen's page block is sufficient for now. If further issues develop in other related articles, we could consider a TBAN at that point, but it feels a little overbroad to me at this juncture. Lord Roem ~ (talk) 01:07, 29 January 2023 (UTC)[reply]
• Since the evidence presented here relates to just the Jordan Peterson article and its talk page I agree that action only about that page is needed. @
  page ban instead of a partial block due to the limitation with partial blocking - that is, if CanterburyUK is temporarily blocked for something else it'll override and effectively remove the partial block whereas a page ban will remain in place. But that's about the method of paperwork rather than resolving the issue. Callanecc (talk • contribs • logs) 11:08, 30 January 2023 (UTC)[reply
  ]

• Ah, the page ban, a rare bird. Something for the paperwork feinschmecker. Of course you're right about the page block problem. On the other hand, the problem with page bans is that it's up to the user to abide by them — there's nothing technical keeping them off the page. That's awkward when there's a bit of a CIR issue. We don't want to set the user up for a series of escalating blocks just because they don't understand their ban. How about this: I try to keep an eye on CanterburyUK and their block log, to hopefully notice any shorter siteblock that destroys the partial blocks, and after such a shorter block expires, I restore the partials. Of course that would need a bit of bookkeeping, but I've done it before. Bishonen | tålk 12:41, 30 January 2023 (UTC).[reply]

• Sounds good to me. I guess you could also do both too. The page ban is the sanction and the partial block effectively enforces it. Callanecc (talk • contribs • logs) 12:47, 30 January 2023 (UTC)[reply]

• I was thinking "both" myself. But surely that would make it even harder for the user to understand. The bureaucracy of sanctions is hard enough to grasp for experienced editors. I have talked with several who assume page blocks also imply topic bans (one today by e-mail, actually). In fact, I'd sooner keep an eye on the partials than do any more <expletive removed> explaining. Bishonen | tålk 15:28, 30 January 2023 (UTC).[reply]
• Everybody seems OK with my partial blocks, so I'll close. Bishonen | tålk 11:45, 31 January 2023 (UTC).[reply]

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

Request concerning Dan Palraz

User who is submitting this request for enforcement

Tombah (talk · contribs · deleted contribs · logs · filter log · block user · block log) 12:19, 30 January 2023 (UTC)[reply]

User against whom enforcement is requested

Dan Palraz (talk · contribs · deleted contribs · logs · filter log · block user · block log)

Search CT alerts: in user talk history • in system log

Sanction or remedy to be enforced

• WP:DIS
• WP:POINT
• WP:TENDENTIOUS

Diffs

of edits that violate this sanction or remedy, and an explanation how these edits violate it

Dan Palraz has been exhibiting what I see to be extremely disruptive conduct and agenda-pushing on ARBPIA matters for a considerable amount of time. He is often edit warring to push his own viewpoints:

• #1
• #2
• #3
• #4
• #5

White phosphorus munitions:

• #1
• #2
• #3

Judaean Desert:

• #1
• #2
• #3
• #4

• #1
• #2
• #3

In addition to the obvious edit-warring, he occasionally refuses to leave edit summaries despite repeated requests (see here and here). When he does, he often just mentions the minor changes rather than the major ones. See this edit for example: while claiming to only update the population, he removed a chunk of information from the article.

Moreover, Dan moves pages without any discussion, despite the fact that it is undoubtedly required in those cases:

• Rock-cut tombs in ancient Palestine
• Ring Neighborhoods, Jerusalem was moved to Ring Settlements, East Jerusalem

• block 1 - for edit warring
• block 2 - from editing International recognition of the State of Palestine, for refusing to abide by ARBPIA after it's been explained

If

WP:AC/DS#Awareness and alerts

)

Me and other editors have warned him about his disruptive behavior previously (for example: #1, #2, #3, and by an admin, Doug Weller, right here), but each time he chooses to remove warnings as if nothing had occurred rather than responding and regretting his actions, often blanking his page (two examples: here and here).

Additional comments by editor filing complaint

It appears that some editors are of the belief that someone who has made mistakes in the past is not entitled to call for justice when they believe it is necessary. I'm surprised that there are some to prefer to make this about me, but I have answers for every accusation made here.

First of all, we all know ARBPIA is a heated subject and that everyone who writes about it has opinions and feelings on it, which occasionally may result in emotional behavior (as most those involved, myself included, sometimes do). But -

• Selfstudier claims that I have strong opinions, but I don't believe that he or other editors working in the same field are opinion-free. The exact opposite. I the past year, a lot of articles about Israel have completely shifted to the anti-Israel side, and I observe this trend every day. The ethnic component of Jewish identity is often completely rejected in discussions, the well-documented history of Jews in Palestine is dismissed as a biblical myth, and contemporary Israel's actions are frequently harshly criticized while the wrongdoings of the other side are frequently ignored. But again, though, I'm not criticizing Dan's beliefs; rather, I'm criticizing his disruptive methods of forcing them, bullying others to accept them.
• Selfstudier says I have canvassed before, but to be honest, I had no idea that this would be considered canvassing, otherwise, I wouldn't do it. I still wonder how is this different from from this post on Dan Palraz's talk page and another similar one.
• Selfstudier claims that this action was blanking, but no - it was archiving, as clearly stated in the edit summary.
• Selfstudier asserts that I breached 1RR in this article, and Iskandar even added that he believes I have never reverted, However, a quick glance would reveal that I immediately self-reverted after Selfstudier had requested me to.
• To be honest, I can't deny that I've been the target of a number of baseless allegations in the past. One of them had a claim that I and EladKarmel were the same editor, but it was promptly rejected as baseless. In the other, Iskandar323 made a claim that I had broken 1RR but then withdrew it. That, in my opinion, proves that sometimes people are too quick to pull the trigger when it comes to me.
• Iskandar323, you and other editors have been gently explaining the rules to Dan over a year now. You have defended him for too long. In fact, I wish I had the same level of support and guidance that Dan generally has - to me, criticism is usually delivered as a threat. But Dan Palraz, as we all can see, rejects that friendly guidance and patience.

In conclusion, I completely disagree with the comparison the editors here make between Dan and myself. Yes, we both have very strong opinions, but I think our mindsets and actions are really different. While I strive to become more familiar with the rules and always prefers to assume good faith, Dan's record demonstrates that he repeatedly breaks the same rules, many of them violations for which he has previously been blocked twice in the past (and here's another complaint making the same claim, July 2021). He had too many prior opportunities to behave better but chose to disregard them. It is abundantly clear to me from Dan's disruptive behavior, prior blocks, and what can only be described as a complete rejection of all criticism directed at him that his objective is not to improve Wikipedia but rather to advance his own opinions at all costs, making him unqualified to edit articles related to the ARBPIA. Tombah (talk) 07:54, 2 February 2023 (UTC)[reply]

While this AE is still active, Dan continues to push the same edit, also adding a personal attack—now for the sixth time in Judaean Desert. After being reverted for a sixth time, he finally started a discussion. Tombah (talk) 07:58, 2 February 2023 (UTC)[reply]

@Dan Palraz: A few corrections and clarifications: (1) I didn't modify "Palestine" to "West Bank" after filing this AE, check again the link you provided. I edited it on December 14th, two weeks before this AE. Since then, you've made anoter attempt to force the same edit, and Elmidae has undone this action (as he also did in the past, before I did it). (2) The issue is not "general behavior"; rather, general behavior is the only way, in my opinion, to characterize a long history of specific violations, such as edit-warring, disruptive and misleading comments, and occasional vandalism, despite being aware, despite numerous friendly warnings, and despite being blocked in the past for the same violations. (3) I didn't ask for a permanent ban; all I did was point out your past and present violations, along with examples. This is why we have AEs: so that uninvolved admins can choose the best course of action. Tombah (talk) 09:44, 2 February 2023 (UTC)[reply]

Moved to own section. Callanecc (talk • contribs • logs) 10:36, 2 February 2023 (UTC)[reply]

Notification of the user against whom enforcement is requested

notification

Discussion concerning Dan Palraz

Statements must be made in separate sections. They may not exceed 500 words and 20 diffs, except by permission of a reviewing administrator.
Administrators may remove or shorten noncompliant statements. Disruptive contributions may result in blocks.

Statement by Dan Palraz

Hi, sorry I did not check the page yesterday. I cannot properly defend myself as I do not understand what I am being accused of; yes, I moved

@Tombah: You are the one who changed "Palestine" to "West Bank" in said article after you filed this report: [46], which, again, just shows you do exactly what you accuse me of – and which makes it seem like you made it on purpose to get the reaction you wanted. Also, as can be proved quickly, you have consistently done {{WIKIHOUNDING}} on me for months, reverting several edits by me in way different topics every time you log in, which should be a reason for punishment against you as well. As all users who have interacted with us both for months agree here above, there is nothing I have done that you haven't. Either way, I don't think "general behavior" should be a reason for a permanent ban forever (even real crimes expire after years everywhere, so any punishment forever for honest editing without any bad words or real crimes sounds like a little too much), and as each bad behavior should get and does get its own immediate punishment: if I or anyone breaks the 1RR rule, there is a specific punishment for that. You have admitted you are basically requesting to have me permanently banned for pushing an agenda that is opposite to the one you are trying to push. I believe Wikipedia's general rules and automatic punishments for 1RR etc are capable of dealing with us both, and I here promise not to interact with Tombah, undo any of Tombah's edits or meddle with topics they are currently working on, I will do it for the sake of my own mental health above all. All I ask for is that Tombah also stop their months-long {{WIKIHOUNDING}} on me. Dan Palraz (talk) 09:23, 2 February 2023 (UTC)[reply]

Moved to own section. Callanecc (talk • contribs • logs) 10:36, 2 February 2023 (UTC)[reply]

Sorry, but just please take note that this edit was simply a reaction to [this]. Still, I can't see how reverting a change that had changed Palestine to West Bank is a reason for a permanent ban. But yes, if I was smarter, of course I shouldn't have done that right after Tombah had filed a report against me. Yes, I am impulsive, but have I committed any serious crimes here that warrant a ban *forever*, which is more than you what you get for killing someone? I plead guilty to falling for such provocations, I plead guilty for being impatient and getting too emotional, I never hid I have panic attack issues which sometimes make me unable to read messages posted or that make me go for weeks without being able to open Wikipedia, and I therefore commit to self-banning myself from the I/P conflict area for at least three months from now on and to exercise way more self-restraint and patience if I ever go back to the topic, if given a chance, especially as most users who commented above did speak up on my defense rather than on the OP's defense of my banning. I therefore ask for another chance, committing to avoiding any confrontation of the kind in the future, no matter how sure I am to be doing the right thing. Dan Palraz (talk) 11:00, 2 February 2023 (UTC)[reply]

Moved to own section. Callanecc (talk • contribs • logs) 11:06, 2 February 2023 (UTC)[reply]

Statement by Selfstudier

I wanted to wait for DP to defend himself but since we are already talking tban, I will say something now.

The principal charge here is disruption over an extended period. Complainant writes extremely disruptive conduct and agenda-pushing. It is true on several occasions I and others have reminded DP of things they ought not to do but I submit that if that description applies to DP, it applies equally to complainant. T writes Me and other editors have warned him about his disruptive behavior previously but I and other editors have warned T about their disruptive behavior, so? T speaks of DP blanking their page, when shortly after filing this complaint, they blanked their own, which points up complaints about their own behavior.

I was not a participant but let's take the recent content dispute at 6 day war. DP broke 1R and so did another editor, an editor that T had earlier canvassed See here in respect of another article. T and the same editor appear again at the second editing dispute mentioned and again, backing each other up, with DP in the middle.

T also recently breached 1R at another article. They actually broke it twice but because 2 of the reversions were contained in one edit, they were not required to self revert twice. See the short exchange here The two reversions were part of a large edit with edit summary "Styling". Is that not "disruptive"? T frequently, when reverted, simply reinserts the original edit without any attempt at discussion, essentially the same behavior complained of with respect to DP. I will let someone else comment more specifically about that but I can produce the diffs if needs be.

The point about page moves seems incidental, it is desirable to discuss/RM for page moves in a CT area, not sure there is an outright rule against bold moves, I actually agree that a page move is needed in both cases cited by T. In any case, such undiscussed moves are simple enough to deal with and both moves were reverted by T (after this filing).

DP does their homework even if they go a bit ott on occasion. T is a decent editor as long as they are in their comfort zone (Jewish history) but outside of that, exhibits a very strong POV, to put it mildly. (Examples here, here, here and here, all from one talk page (there are others similar).

I rather think that the outcome here, whatever that might be, should be the same for both of these editors.

@DanPalraz: I want to check that you are aware of and fully understand the one revert rule for this topic area? That you cannot do what was done at the 6 day war article. I seem to remember this being mentioned to you previously.Selfstudier (talk) 19:45, 1 February 2023 (UTC)[reply]

@

WP:WIKIHOUNDING, that is a serious accusation, what evidence do you have for that? Selfstudier (talk) 09:41, 2 February 2023 (UTC)[reply

]

@Tombah: Recent statement should go in your own section, under "Additional comments by editor filing complaint". Dan's reply, too, I left them a note at their talk page.Selfstudier (talk) 09:49, 2 February 2023 (UTC)[reply]

Statement by Iskandar323

I don't have a great deal to add, but I would echo the observations of Selfstudier has Dan Paltraz has certainly not acted in a vacuum. E.g. Dan has only been able to edit war on a certain point at

Some of Dan Palraz' edits have been problematic, but as others have noted one would be hard-pressed to find a sin that Dan committed which Tombar has not also committed. Tombar's talk page history contains one complaint after another of 1RR violations, edit warring and disruptive editing. This is just a garden-variety attempt to get rid of an editor with an opposing POV. Zero^talk 00:47, 1 February 2023 (UTC)[reply]

Statement by Number 57

Based on what I've seen from Dan Palraz's edits when they've appeared on my watchlist (particularly Shilat (edit | talk | history | protect | delete | links | watch | logs | views), a village partly in Israel and partly in no-man's land, which Dan repeatedly tried to (incorrectly) change to stating it was in the West Bank), I concur with Callanecc's view that he is unable to contribute to this topic area in an NPOV fashion, and an indef topic ban is appropriate. Number 57 20:08, 1 February 2023 (UTC)[reply]

Statement by (username)

Result concerning Dan Palraz

This section is to be edited only by uninvolved administrators. Comments by others will be moved to the sections above.

• I'm keen to hear what Dan Palraz has to say but on the face of it the evidence of edit warring and controversial page moves indicates to me that they aren't able to contribute constructively in this topic area. Given that I'm thinking that an indefinite topic ban from the Arab-Israeli conflict, broadly interpreted, would be appropriate. Callanecc (talk • contribs • logs) 11:32, 31 January 2023 (UTC)[reply]

I haven't yet seen anything that would convince me that the TBAN I suggested isn't appropriate, especially considering edits like this yesterday, but I note that there have been a number of comments about Dan Palraz's conduct being very similar to Tombah's (not in a vacuum for example). Can I ask that those who've made statements to that affect provide evidence for them? Alternatively, if you believe that there is a pattern of problematic conduct from Tombah a separate AE report can be filed to better document it all. Callanecc (talk • contribs • logs) 10:43, 2 February 2023 (UTC)[reply]

@Dan Palraz: Please only add comments in your own section ("Statement by Dan Palraz") rather than in different sections. It helps us keep track of what different people are saying. Callanecc (talk • contribs • logs) 11:06, 2 February 2023 (UTC)[reply]

Based on Dan Palraz's recent statement here I've settled on a 6 month topic ban. I would strongly caution you (Dan Palraz) though that if there are any problematic edits in this topic area after the topic ban expires you will almost definitely end up with an indefinite topic ban and that given that the behaviour continued it would be difficult to successfully appeal. Callanecc (talk • contribs • logs) 06:55, 4 February 2023 (UTC)[reply]

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

Request concerning Jim Michael 2

User who is submitting this request for enforcement

Red-tailed hawk (talk · contribs · deleted contribs · logs · filter log · block user · block log) 17:15, 30 January 2023 (UTC)[reply]

User against whom enforcement is requested

Jim Michael 2 (talk · contribs · deleted contribs · logs · filter log · block user · block log)

Search CT alerts: in user talk history • in system log

Sanction or remedy to be enforced

Discretionary sanctions, as authorized by Wikipedia:Requests for arbitration/Editing of Biographies of Living Persons#May 2014 (as amended by Wikipedia:Requests for arbitration/Editing of Biographies of Living Persons#Motion: contentious topic designation (December 2022)

Diffs

of edits that violate this sanction or remedy, and an explanation how these edits violate it

1. 16 January 2023 You're greatly overstating her international influence. You portray her as having been at the top of her field, but her international notability is well below that of Christiane Amanpour.
2. 16 January 2023 ...but few know much about her because she's primarily a domestic figure. Amanpour is far more international, but most people don't know much about her.
3. 22 January 2023 ...Amanpour is significantly more internationally notable
4. 26 January 2023 compare her to the more internationally notable Amanpour, or say why Walters should be included but Amanpour shouldn't.
5. 29 January 2023 I need to mention Christiane Amanpour again. No-one here has tried to refute that she outdoes Walters in everything but length of career
6. 29 January 2023 I mention Amanpour's notability to refute claims that Walters is - as some here claim/imply - the most notable female journalist
7. 30 January 2023 Amanpour is far more international & often broadcasts in both countries (and in a response to another editor in the same diff) Amanpour - whose career is in the UK & US - will receive a great deal of media coverage in many countries when she dies.

We don't do tokenism/quotas/discrimination:

1. 22 January 2023 We don't have quotas & don't practise
   positive discrimination
2. 22 January 2023 If you mean 'positive' discrimination, quotas or tokenism, we won't be doing anything like that.
3. 26 January 2023 There's no quotas, tokenism or positive discrimination, nor should there be.
4. 26 January 2023 a few people want to radically change things by using quotas
5. 29 January 2023 I agree that there shouldn't be quotas

Diffs of previous relevant sanctions, if any

• N/A

If

WP:CTOP#Awareness of contentious topics

)

• Alerted about discretionary sanctions or contentious topics in the area of conflict, on 26 January 2023 (see also the system log linked to above).

Additional comments by editor filing complaint

At the time of my writing, he has responded to precisely zero of these warnings, and has continued to bludgeon the discussion at will. Long-term editors generally shouldn't need to be warned by four separate editors that they are bludgeoning the exact same discussion in order to knock it off, and I'd ask that the user be given a logged warning as a discretionary sanction as a formal reminder to not bludgeon future discussions involving recently deceased people and a deterrent against repeating this sort of behavior in the future.

On a more procedural note, it looks like Jim Michael 2 has made exactly 20 diffs in this RfC when the one at 2023-01-16 00:46 is included. I am requesting an extension in both length of my complaint and in number of diffs I can link to (if need be; I'm not sure if my linking to the warning diffs counts) so that I can better demonstrate the extent of bludgeoning present.

I will separately note that Jim Michael 2 was warned for edit warring over this exact topic on the 2022 page less than a month ago. — Red-tailed hawk _(nest) 17:35, 30 January 2023 (UTC)[reply]

Notification of the user against whom enforcement is requested

30 January 2023

Discussion concerning Jim Michael 2

Statements must be made in separate sections. They may not exceed 500 words and 20 diffs, except by permission of a reviewing administrator.
Administrators may remove or shorten noncompliant statements. Disruptive contributions may result in blocks.

Statement by Jim Michael 2

I'm not going to even read that discussion on Talk:2022 again, let alone edit it, so this is action is pointless. I'm not going to revert any additions of Walters to 2022, including adding her to the lead & adding a photo of her. All further comments by me on that talk page will be unrelated to her. I'll no longer disagree with people who say that she was at the top of her field & should've been on ITN between Pelé & Benedict. Therefore, any restrictions imposed on me on that page are unnecessary.

The discussions on her have taken a ridiculous amount of time. I wish I'd stopped editing that discussion much sooner & had I known it'd continue for so long & be deluged with many people arguing for her inclusion I wouldn't have started contributing to it. I haven't edited any of the articles about Walters or Amanpour & don't intend to, so there's no point blocking me from editing those. I'm sorry for any problems I may have caused & for breaking any guidelines. Jim Michael 2 (talk) 17:30, 30 January 2023 (UTC)[reply]

Statement by Shibbolethink

As someone completely not involved in this situation and who doesn't know the accused, I think this is a pretty clear case of bludgeoning. If others don't find your arguments convincing, it isn't helpful to keep bringing them up. If others have warned you about bludgeoning, it is your perogative (and at your own peril) that you continue to bring it up. At some point, if others aren't carrying the banner for your arguments, they aren't worth making. I would agree this merits sanctions (and perhaps most of all preventative to stop this user from disrupting the discussion). I would recommend a temporary page block from this page until the RFC is closed or archived, whichever comes first. I say temporary only because this is a time-based discussion and the most narrow sanction is usually the best in cases like this.— Shibbolethink ^{(♔ ♕)} 17:21, 30 January 2023 (UTC)[reply]

Statement by Levivich

Jim says he quit the discussion sometime between 13:29 (his most-recent comments) and 17:15 (when this AE was filed). What a coincidence. Levivich (talk) 17:57, 30 January 2023 (UTC)[reply]

Statement by MarioJump83

This should bear mentioning that Jim Michael 2 used Anne Heche repeatedly when arguing about inclusion based on fame and popularity. I don't have any other comments, other than being involved in these discussions, which I staked a moderate position but I also noticed repetitive arguments which created the hostile environment for people in other side of the discussions. MarioJump83 (talk) 03:27, 31 January 2023 (UTC)[reply]

Statement by WaltCip

I am involved, so I am not completely without bias in this discussion. However, the

I've been heavily involved in these discussions with Jim. Similar behavior is occurring at Wikipedia talk:WikiProject Years. All from this month: dismissing inclusionists as "fans" of things they're adding (1, 2, 3, 4, 5); enforcing local consensus as policy (1, 2, 3, 4, 5, 6, 7, 8); accusing InvadingInvader of bad faith arguing for offering multiple compromises that would take the articles in different directions: (1, 2, 3, 4, 5). See also: Wikipedia:Village pump (policy)#Create Wikipedia:Manual of Style/Years. It's also worth nothing that this is part of a larger systemic issue at the WikiProject; the WikiProject talk page has a long series of arguments with other users engaging in similar ownership behavior going back well into the archives. Thebiguglyalien (talk) 15:23, 31 January 2023 (UTC)[reply]

Statement by InvadingInvader

(Disclaimer: involved) If anything, the core of the issue to me seems like a failure to assume good faith and violations of WP:OWN across the board. Admittedly, I originally viewed allegations of WP:OWN violations with skepticism, though at this point, I'm particularly concerned not just at the frequency of repeated arguments but also the hostile tone (such as "new editors proposing radical changes" and similar phrasings, as seen in the cited diffs), both of which creates an environment hostile to anything that goes along with "the regulars". Extraordinary Writ's statement is one I fully agree with; we all need to tone it down and look to reach middle ground more often. InvadingInvader (userpage, talk) 21:29, 31 January 2023 (UTC)[reply]

Statement by Black Kite

After a long time editing the current years pages I finally gave up during this discussion about Robbie Coltrane, the discussion may be enlightening regarding this case, or not. Black Kite (talk) 10:36, 2 February 2023 (UTC)[reply]

Statement by (username)

Result concerning Jim Michael 2

This section is to be edited only by uninvolved administrators. Comments by others will be moved to the sections above.

• Jim Michael 2's behavior in that RfC is...suboptimal, to say the least, and I agree that it crosses the line into bludgeoning/tendentiousness, particularly in light of all the warnings that weren't heeded. A block probably wouldn't have much
  WP:BATTLEGROUND) at Talk:2022 and related pages, and I'd strongly encourage the "regulars" there, especially Jim Michael 2, to dial down the temperature significantly if they want to avoid being sanctioned in the future. Extraordinary Writ (talk) 08:00, 31 January 2023 (UTC)[reply
  ]
• Jim Michael 2's conduct at the RfC isn't acceptable fits well into bludgeoning. Given that Jim Michael 2 has committed to stay away from the discussion I agree that a logged warning is sufficient at this point. Callanecc (talk • contribs • logs) 10:48, 2 February 2023 (UTC)[reply]
• I haven't attempted to read through the relevant discussions in detail yet, but I do want to note that the bludgeoning behavior appears to be continuing in a related ANI thread at Wikipedia:Administrators'_noticeboard/Incidents#Long_term_ownership_at_WikiProject_Years. I am thus a bit skeptical that a logged warning is enough, but that concern may be moot here if said ANI discussion imposes sanctions. _signed, Rosguill ^talk 22:54, 2 February 2023 (UTC)[reply]

  I agree with NewYorkBrad below that this seems to be outside the spirit of the sanctions authorized for BLP, and would recommend that the ANI thread be used to resolve the dispute rather than passing a sanction here. _signed, Rosguill ^talk 23:09, 2 February 2023 (UTC)[reply]

• I agree with the consensus that (1) Jim Michael 2's behavior in the cited discussion were unacceptable; (2) we welcome his promise to stop behaving that way; but (3) that promise needs to apply to all discussions, not just that particular one. (As a minor point, I'm not sure this discussion is best framed as enforcement of the BLP discretionary sanctions, though I don't propose to move it at this point. Read literally the DS/contentious topics remedy for BLPs applies to all content about recently deceased people, so this request is technically on-topic. However, the reason that recently deceased people counterintuitively were included in the biographies of "living" persons policy was to avoid anyone's thinking "so-and-so died this morning, so the protections of BLP no longer apply, so it would be a good time to add bunches of thinly sourced negative information and unduly weighted crap to their article." (This was especially important years ago when the sourcing requirements for non-BLP articles were much weaker than they are today.) The bludgeoning behavior here will warrant strong sanctions if it happens again, but the same would be true if that behavior occurred on any page, and BLP isn't necessarily the best framing of the problem.) Newyorkbrad (talk) 23:06, 2 February 2023 (UTC)[reply]

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

Request concerning Super Dromaeosaurus, Mzajac and Jeppiz

User who is submitting this request for enforcement

Cinderella157 (talk · contribs · deleted contribs · logs · filter log · block user · block log) 04:04, 31 January 2023 (UTC)[reply]

User against whom enforcement is requested

1. Super Dromaeosaurus (talk · contribs · deleted contribs · logs · filter log · block user · block log)

   Search CT alerts: in user talk history • in system log

2. Mzajac (talk · contribs · deleted contribs · logs · filter log · block user · block log)

   Search CT alerts: in user talk history • in system log

3. Jeppiz (talk · contribs · deleted contribs · logs · filter log · block user · block log)

   Search CT alerts: in user talk history • in system log

Sanction or remedy to be enforced

WP:ARBEE

Diffs

of edits that violate this sanction or remedy, and an explanation how these edits violate it

1. [47] Users like
   WP:PA (by Super Dromaeosaurus) Cinderella157 (talk) 06:06, 31 January 2023 (UTC)) (Add Users like to inadvertently truncated quote which is from the diff given. Cinderella157 (talk) 10:15, 4 February 2023 (UTC) )[reply
   ]
2. [48] Shows the subsequent posts [ie subsequent to the first diff.
   WP:BULLYING (specifically intimidation); uncivil; and, rising to the level of a personal attack.[reply
   ]