Jump to content

Wikipedia:Arbitration/Requests/Enforcement/Archive313

From Wikipedia, the free encyclopedia
Arbitration enforcement archives:

SPECIFICO

[edit]

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 SPECIFICO

[edit]
User who is submitting this request for enforcement
Mr Ernie (talk · contribs · deleted contribs · logs · filter log · block user · block log) 13:21, 20 November 2022 (UTC)[reply]
User against whom enforcement is requested
SPECIFICO (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:Arbitration/Requests/Case/American_politics_2#Discretionary_sanctions_(1992_cutoff) Specifically, 1RR at the article.
Diffs of edits that violate this sanction or remedy, and an explanation how these edits violate it
  1. [1] First revert
  2. [2] Second revert
Diffs of previous relevant sanctions, if any
  1. [3] Blocked a few weeks ago for 48 hours for DS violation at Julian Assange (a very similar article where SPECIFICO excessively reverts)
  2. Many other topic bans and warnings, can be supplied if necessary.
If discretionary sanctions are requested, supply evidence that the user is aware of them (see WP:AC/DS#Awareness and alerts)

AE 3 months ago

Additional comments by editor filing complaint

The Biden laptop page is under 2 specific DS - 1RR and 24hr BRD. The DS violations are really the tip of the iceberg with the editing issues at this article. We recently had a RFC about some content, and moments after it closed SPECIFICO edited against the consensus with the misleading edit summary "consistent with RfC," launched an unsuccessful AN challenge, and still continues to attack the consensus. These seemingly pointless reverts are in line with that non-collaborative mindset. The DS seem to be important to SPECIFICO, as they've been warning other editors of them with comments that such behavior is not acceptable, even calling it "egregious". I attempted to discuss this with SPECIFICO (as we usually do among those active in the topic area), but as the discussion was not fruitful I have brought it here for review. I see that 1RR is in effect at the notice in the edit window but I can’t tell who actually applied it. Hopefully a reviewing admin can clarify. The edit notice says 1RR is active. This is where I usually check which DS applies. Now changed.

This is the first time I have ever filed an AE request against SPECIFICO (and only the 2nd time I've filed overall). I have commented when others have opened filings and added diffs of my experiences, which typically involved unnecessarily belittling and personal comments. For reference, there are 3 logged warnings (here are the closes for the most recent [4] [5]) to SPECIFICO at the WP:AELOG and several unlogged warnings resulting from previous AE discussions. I can provide the diffs to those if helpful (they typically go something like this or this). I can't recall at any of the previous filings SPECIFICO showing acceptance of some of the concerns that admins have pointed out. The belittling comments in this case were made to a new editor who could understandably be tripped up by some of the specific DS, especially when it's confusing to experienced editors and when they aren't filed correctly. As I said at a previous filing, warnings don't require any behavioral changes and are typically ineffective with editors who've been here a while. What about a very simple "thank you for the feedback I will take it on board?" Mr Ernie (talk) 20:13, 22 November 2022 (UTC)[reply]

It would be helpful if an admin could clarify where the "master record" of which DS is in force is located. As the Hawk noticed, the edit notice, the sanctioning admin, and the DS Log each said something different. As I've said before, I usually check the edit notice to see what is in effect before I make edits. I thought it would be well within process to bring it to AE to review since it was completely unclear what was actually in effect. Let's hope this is the last SPECIFICO AE report. Mr Ernie (talk) 02:45, 29 November 2022 (UTC)[reply]

KoA, please don't accuse me of hounding without diffs, especially here at a noticeboard. I think this is the first time I've ever filed a report against SPECIFICO for anything. I have commented in several of the many previous noticeboard reports, sometimes supporting sanctions for the reported behavior. A while ago it earned me a sanction for casting asperions (not hounding as you erroneously allege), so now I am careful to adds diffs when I comment. You also refer to "previous sanctions," but there has only been the one. Finally the comments / interaction that admins found problematic were between SPECIFICO and another editor. I would ask you to fix these multiple issues in your comments but this has already gone on long enough. I think I'm also over my word limit. Mr Ernie (talk) 21:33, 1 December 2022 (UTC)[reply]

Notification of the user against whom enforcement is requested


Discussion concerning SPECIFICO

[edit]

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 SPECIFICO

[edit]

Here is the page restriction on this article: "24-hour BRD, 1RR=no". 24-hour BRD was and is intended to provide an improved restriction, in that it does not limit the removal of obviously bad edits such as are often done by good faith but inexperienced editors. There have been numerous instances of more than 1RR by various editors on this page, all of whom presumably understood that it was not the applicable page restriction. SPECIFICO talk 16:45, 20 November 2022 (UTC)[reply]

If Ernie believed that a 1RR restriction was in effect for this article, why did he himself exceed that here 1 and here 2, and why didn't he report any of the various other instances of 1RR+ having been exceeded on this page ovevr the past several weeks? SPECIFICO talk 18:02, 20 November 2022 (UTC)[reply]

Thrydulf, this complaint is about 1RR. And it was initiated after I explained to OP that 1RR was not applicable. SPECIFICO talk 04:21, 22 November 2022 (UTC) Thryduulf, thanks for your reply. However the talk page discussion with that user was unrelated to this complaint, and that user later described it as "friendly" on the article talk page. I understand that all of us is subject to scrutiny at any time, but I would hope that there's at least some structure at this forum that differentiates it from ANI style open endedness. The more salient issue collateral issue, IMO, would be why OP has not conceded that this complaint was made in error, particularly in light of OP's longstanding repeated efforts to get me sanctioned for just about any reason.[reply]

@Buffs: It appears that you have misunderstood what's been posted in this thread. The Admin who placed the restriction intended only 24-hour BRD but did not change the pop-up notice to conform with the notice on the talk page. He has now confirmed that and the pop-up has been conformed to the talk page 24-BRD notice. When I informed Ernie of the applicable sanction, he disregarded that information and filed this report based on the vestigial 1RR. SPECIFICO talk 23:00, 27 November 2022 (UTC)[reply]

@Awilley: Why would you propose to restrict me from bringing Ernie to AE? I have never brought Ernie to AE, and he has repeatedly appeared at AE to disparage me, after promising to Sandstein that he would not do so (as the condition upon which Sandstein unbanned from Sandstein's previous sanction on Ernie in which he banned him from commenting me here). BTW, I don't support banning Ernie from making future reports on me. Any such complaint would stand on its merits. SPECIFICO talk 23:48, 28 November 2022 (UTC)[reply]

Buffs, here is my interaction with Ernie. It's not confrontational. SPECIFICO talk 07:52, 29 November 2022 (UTC)[reply]

@Thryduulf: I do not believe that a logged warning to me for civility reflects the facts, context, or evaluations in the record here. SPECIFICO talk 13:45, 1 December 2022 (UTC)[reply]

Statement by Red-tailed hawk

[edit]

I'm struggling to find out the extent to which discretionary sanctions exist for this page. There are ordinarily three places to check for these sorts of things: the discretionary sanctions log, the editnotice for the page, and the talk page of the article. Unfortunately, all three of these imply different things about the actual restrictions in effect on the article

  1. When I look at the discretionary sanctions log, other than the page on the Hunter Biden laptop controversy being semi-protected for one year, there are no logged restrictions on the page.
  2. When I look at the article talk page a {{American politics AE|1RR=no|Consensus required=no |BRD=yes }} tag on the talk page, which would imply that BRD is in effect and not 1RR. This was inserted by Doug Weller, an administrator.
  3. When I look at the page's editnotice, it says that the article is under both 1RR and BRD. The editnotice was created by FormalDude, a non-admin.

My reading of this all is that Doug Weller intended to place the page under WP:BRD and forgot to log it. An editnotice was later created, but FormalDude made a mistake and made the editnotice display a 1RR notice in addition to the BRD notice. In light of all of this, SPECIFICO's decision to make two reverts (and yes, they're very clearly reverts) and their response to Mr. Ernie indicates to me that SPECIFICO understood the restrictions to be consistent with those laid out in (2), which appears to be the intent of the admin who placed the BRD notice on the talk page but did not log the entry. (I don't fault Mr. Ernie for believing the page is under 1RR on the basis that the editnotice says so, but, as FormalDude is not an admin, there is no plausible way that FormalDude could have actually created a 1RR restriction on the article even if they wanted to.)

If admins want a 1RR on this article, it should be clarified at this AE request and then logged appropriately. If admins want a BRD on this article, it should be clarified at this AE request and then logged appropriately. However, this whole thing has taken an hour of my time to sort through, and I think that we generally want our article-specific DS restrictions to be easier to understand than this.

Red-tailed hawk (nest) 17:01, 20 November 2022 (UTC)[reply]

I don't endorse the retaliatory action language from FormalDude below; Mr Ernie went to SPECIFICO's talk page, told SPECIFICO that there existed a 1RR rule and that SPECIFICO had violated it, responded to SPECIFICO's statement that there's only BRD by pointing to the editnotice, and only after SPECIFICO did not respond for half a day did Mr Ernie open this report. Mr Ernie was in error only because because the editnotice erroneously displayed 1RR, but it would be fully appropriate to bring this forward on the basis of 1RR if such a sanction were actually imposed on the article. Implying malicious intent on the part of Mr Ernie seems plainly unwarranted at this juncture; to the contrary, the evidence suggests that Mr Ernie was acting in good faith. — Red-tailed hawk (nest) 17:33, 20 November 2022 (UTC)[reply]

Statement by Doug Weller

[edit]
agh, yes I wanted BRD and forgot to log. Mea culpa. Doug Weller talk 17:41, 20 November 2022 (UTC)[reply]
Logged. Doug Weller talk 17:44, 20 November 2022 (UTC)[reply]

Statement by Objective3000

[edit]

The revert and BRD rules (whichever apply in this case) were designed to stop/prevent edit warring. Hard to see how these two edits fit any problem that the originators of DS sanctions had in mind. O3000, Ret. (talk) 17:17, 20 November 2022 (UTC)[reply]

Given that the filer specifically requested enforcement per 1RR, and Doug and FormalDude have both clarified that the article is not under 1RR; it would seem like this is a good time for the filer to withdraw this request. O3000, Ret. (talk) 21:07, 20 November 2022 (UTC)[reply]
Whether SPECIFICO deserves a logged warning for likely serial, impolite tone or Ernie deserves (another) AE ban for a filing that defines triviality (to be polite), is above my pay grade (and retirement benefits). I would suggest that one keeps in mind that DS articles are where many admins “fear to tread”. (An impolite manner of saying use common sense.). I would suggest that both be banned from bringing the other to AE, which I think of as the drama board of the drama boards – more so than ARB or ARCA. Pardon my interruption. O3000, Ret. (talk) 02:44, 23 November 2022 (UTC)[reply]
Given AWilley's and SPECIFICO's comments, I withdraw any suggestion of AE banning and suggest a feast of trout. O3000, Ret. (talk) 23:56, 28 November 2022 (UTC)[reply]

Statement by FormalDude

[edit]

RTH is correct, the editnotice should not have displayed the 1RR. I've just fixed that. This request seems to be a retaliatory action from Mr. Ernie against SPECIFICO because of their comments supporting this EW report just two months ago where Mr. Ernie actually violated the 24-hr BRD himself on the Hunter Biden laptop article. ––FormalDude (talk) 17:22, 20 November 2022 (UTC)[reply]

Comment by GoodDay

[edit]

I think it would be best that the recent RFC result at the page-in-question, should be followed. Also, once Republicans take over the House in January 2023? Administrators may wish to put the page-in-question under more scrutiny. GoodDay (talk) 17:30, 20 November 2022 (UTC)[reply]

Statement by Adoring nanny

[edit]

I am concerned by this edit from the original complaint. When you've just gotten an unfavorable close of an RfC to which you've contributed extensively (over 20 contributions from USER:SPECIFICO to the RfC by my count), that is not the time to be editing the article in a manner inconsistent with the RfC close. That said, I am not concerned by SPECIFICO's AN challenge of the close. Challenging the close is a reasonable act. Adoring nanny (talk) 18:48, 22 November 2022 (UTC)[reply]

Statement by PhotogenicScientist

[edit]

I realize that this user's interactions with me have been brought up here, but I was hoping to stay out of this case if possible. However, regarding the discussion referenced here, I would say that SPECIFICO has been decidedly unfriendly in their interactions on the whole, despite the example to which they're referring above. PhotogenicScientist (talk) 20:01, 22 November 2022 (UTC)[reply]

@Thryduulf Apologies if this is the wrong forum to ask in, but regarding the issuing of warnings as a sanction:

  1. It seems like logged warnings are meant to be able to be referenced in the future, since they're added to WP:AELOG and are searchable, whereas unlogged warnings are only meant as a reminder to the intended user. Are only logged warnings considered relevant for any future AE cases about the warned user, or can unlogged warnings be taken into account?
  2. Is there a policy on how many logged warnings are "too many", and would prompt consideration of harsher sanctions? PhotogenicScientist (talk) 17:48, 1 December 2022 (UTC)[reply]
@Thryduulf and @Newyorkbrad It looks like this thread was archived with no action. I'm concerned that SPECIFICO's behavioral issues noted here have been allowed to continue, since they appear to be getting off without so much as a warning (logged or unlogged). PhotogenicScientist (talk) 13:23, 9 December 2022 (UTC)[reply]
@Thryduulf Not trying to volunteer you for work right this moment, but would you mind formally closing this? I don't think any other admin will be around at this point - this thread has gone a while with no discusion.
Again, not requesting this urgently or anything. I don't really know how much work it takes to properly close something like this. Thank you. PhotogenicScientist (talk) 17:47, 9 December 2022 (UTC)[reply]

@SPECIFICO I missed this earlier, but: particularly in light of OP's longstanding repeated efforts to get me sanctioned for just about any reason this sounds a lot like an aspersion with no supporting diffs. PhotogenicScientist (talk) 21:39, 1 December 2022 (UTC)[reply]

@Newyorkbrad Unfortunately, I don't believe this editor will consider what's been recommended to them at all. They have received warnings in the past about this behavior, yet they persist. And in this thread itself, they responded to every call-out of this behavior with denial, either that they weren't behaving badly, or that their behavior wasn't relevant. I don't see a reminder being of any use here. PhotogenicScientist (talk) 18:05, 9 December 2022 (UTC)[reply]

Statement by KoA

[edit]

Not involved in the dispute, and I stay out of the politics topics to avoid messes like this. However, I'm often wary of of one person heavily in a dispute with an editor running to AE for trivial edits as Newyorkbrad described it. I've seen Mr Ernie's name pop up at AE for awhile now and recall they had to be banned from AE itself[6][7] in part because Mr Ernie was WP:HOUNDING Specifico. Ernie later made a brief appeal,[8] but it looks like they have returned to similar battleground behavior since the ban seeing this AE. Coming to AE with that history and a not so clear cut case doesn't bode well.

Others have looked at Specifico's behavior, so I won't belabor that much except to be wary of how much others may be ratcheting up the incivility in the topic that can result in whoever gets reported first looking bad. That would mean not just focusing on Specifico, but those also contributing to the atmosphere, especially Mr Ernie given the previous sanctions related to their interactions with Specifico. Neither have clean hands based on past sanctions, so if a caution was to be given out, it would be wise to not hyperfocus on one side of the interaction. If this restart of their dispute (maybe this has been going on for awhile since I last saw) continues, it may be best to revisit the background on Ernie's AE ban and maybe consider an interaction ban with Specifico. Someone else could maybe look into the Specifico -> Mr. Ernie interactions further, but at least on the Mr. Ernie -> Specifico history, it seems like Ernie should be trying to stay away from Specifico rather than this. KoA (talk) 23:40, 22 November 2022 (UTC)[reply]

Thryduulf, as someone uninvolved, I'd be worried about a single logged warning for Specifico causing even more disruption. There's already a history of Mr Ernie hounding Specifico, and hounded editors tend to be much more terse towards those people, which makes assessing behavior even messier. While there's been subpar behavior all around, I haven't seen anything yet that really stands out beyond that terse attitude from Specifico. A single warning just comes across as a "gotcha" for Mr Ernie given the context of their past sanctions in the interactions.
Instead, it's increasingly clear that it's the interaction between the two that's the continuing source of disruption. There's a point where it doesn't matter whether one editor egged the other on for years or whether both were bull-headed from the start, that's where interaction bans come into play. A warning to both that their interaction issues are causing disruption would at least avoid emboldening either side of the interaction and maybe get the situation with them to deescalate. That or it'll give focus on the next incident on whether it should be a one or two-way Iban. Just focusing on one side of the interaction in a warning seems to be a recipe for escalation instead though. KoA (talk) 19:02, 1 December 2022 (UTC)[reply]

Statement by Buffs

[edit]

If it wasn't clear on the talk page, then it should be made clear (that appears to be complete). But since the user was clearly warned, appropriate enforcement should be applied. This applies as equally to the target of this enforcement request as to the filer or any participant. We need to be equal in our application of ArbCom rulings. Likewise, his tone was clearly out of line. RedHawk's statement is solid as well. Buffs (talk) 20:46, 27 November 2022 (UTC)[reply]

@SPECIFICO I stand by my assessment. ArbCom opinions below certainly concur mine/others' comments about your tone being unnecessarily confrontational (Thryduulf in particular nails it on the head), even if everything else could be chalked up to a misunderstanding. Buffs (talk) 04:55, 29 November 2022 (UTC)[reply]
@SPECIFICO At least 3 disagree with your assessment: NYB, Thryduulf, and myself. At this point. I've voiced my opinion and will not be replying to further requests unless requested by ArbCom Buffs (talk) 18:04, 29 November 2022 (UTC)[reply]

Statement by (username)

[edit]

Result concerning SPECIFICO

[edit]
This section is to be edited only by uninvolved administrators. Comments by others will be moved to the sections above.
  • If I am reading the diffs correctly, the first diff is rearranging material without removing anything, and the second one adds one word? If that is correct I'm not inclined to focus on the 1RR issue here. I agree that Specifico's treatment of another editor, though, was unnecessarily confrontational and rude. Newyorkbrad (talk) 14:56, 20 November 2022 (UTC)[reply]
    • I propose to take no action given the uncertainty (at best) as to whether this article was under 1RR, as well as the utterly trivial nature of the alleged violation in any case. However, I remain concerned that SPECIFICO recently confronted another editor about alleged DS violations in an unnecessarily rude and confrontational manner. The purpose of DS is to improve the editing environment on our most contentious topic-areas, not to ruin it. If we see much more of that sort of thing, some action might have to be taken. Newyorkbrad (talk) 21:44, 20 November 2022 (UTC)[reply]
    • I'm prepared for this to close without formal action, but I hope SPECIFICO carefully considers what has been said here. My greater concern is with his interaction with relatively new editors, rather than with the "regulars" on DS topics, although they should be treated civilly as well, and of course should reciprocate. Newyorkbrad (talk) 17:51, 9 December 2022 (UTC)[reply]
  • SPECIFICO has had his attention drawn to the need to improve the standard of his interpersonal actions on Wikipedia, including an interaction ban and findings of fact in two different arbitration cases (Interactions at GGTF; two FoFs) and Austrian Economics), and his 2013 block for "Creating an unappealing editing environment" (placed by NuclearWarfare) is likely also relevant. Yet here we are again, years later, dealing with the same issues. I think we need to, at minimum, consider a logged warning that regardless of the rights and wrongs of a situation being rude and/or confrontational is not acceptable behaviour. Thryduulf (talk) 03:48, 22 November 2022 (UTC)[reply]
    SPECIFICO: The original complaint was indeed about 1RR, but AE is able to examine the whole situation and while at least most people agree that your comments were factually correct there also exists concern (from at least NYB and myself) that the tone of your comments was not acceptable. Thryduulf (talk) 12:33, 22 November 2022 (UTC)[reply]
    Unless Newyorkbrad, Awilley or anyone else has contrary comments in the next day or so I intend to close this with a logged warning to SPECIFICO regarding civility and no other action. Thryduulf (talk) 13:36, 1 December 2022 (UTC)[reply]
    @SPECIFICO you've made it very clear that you see no problems with your interaction style, despite multiple independent observers over multiple years telling you time and again that there is, which is why something is needed. 16:06, 1 December 2022 (UTC) Thryduulf (talk) 16:06, 1 December 2022 (UTC)[reply]
    @PhotogenicScientist this should not have been archived with closure. I haven't got time to look into why that happened, but I have seen nothing that suggests SPECIFICO should not be formally warned. Not sure about Mr Ernie, but I'm leaning towards just informal words of advice at this point. Thryduulf (talk) 13:32, 9 December 2022 (UTC)[reply]
  • It's clear from the comments by Doug Weller and FormalDude that the article was not under a 1RR restriction, so a 1RR violation is impossible. I'm fine with any of the solutions people have proposed above: a close of no action, or a close with double warnings (logged or not, it makes no difference), or a close with double restrictions on bringing each other to AE for SPECIFICO and Mr Ernie. In any case, this should be probably closed. ~Awilley (talk) 22:35, 28 November 2022 (UTC)[reply]

Arbitration enforcement action appeal by Saucysalsa30

[edit]

Olympian

[edit]

Eyagi

[edit]

Arbitration enforcement action appeal by Yae4

[edit]

192.80.162.118

[edit]

Archwayh

[edit]

Vladdy Daddy Silly

[edit]

Scientelensia

[edit]

Dev0745

[edit]

Paddykumar

[edit]