Jump to content

Wikipedia:Administrative action review

From Wikipedia, the free encyclopedia

This is an old revision of this page, as edited by Uanfala (talk | contribs) at 22:14, 28 April 2023 (→Cullen328's block of Esculenta: new section). The present address (URL) is a permanent link to this revision, which may differ significantly from the current revision.

Shortcuts
Formal review processes
For RfCs, community discussions,
and to review closes of other reviews:
Administrators' noticeboard
In bot-related matters:
Discussion about closes prior to closing:

Administrative action review (XRV/AARV) determines whether use of the administrator tools or other advanced permissions is consistent with Wikipedia's policies and guidelines. Any action (or set of related actions) involving a tool not available to all confirmed editors—except those covered by another, more specific review process—may be submitted here for community review. The purpose of an administrative review discussion is to reach a consensus on whether a specific action was appropriate, not to assign blame. It is not the place to request comment on an editor's general conduct, to seek retribution or removal of an editor's advanced permissions, or to quibble about technicalities.

To request an administrative action review, please first read the "Purpose" section to make sure that it is in scope. Then, follow the instructions below.

Purpose

Shortcut

Administrative action review may be used to request review of:

  1. an administrator action
  2. an action using an advanced permission

Administrative action review should not be used:

  1. to request an appeal or review of an action with a dedicated review process
    For review of page deletions or review of deletion discussion closures, use Wikipedia:Deletion review (DRV)
    For review of page moves, use Wikipedia:Move review (MRV)
  2. to ask to remove a user's permissions:
    Permissions granted at WP:PERM may be revoked by an administrator if XRV finds them to be misused.
    Repeated or egregious misuse of permissions may form the basis of an administrators' noticeboard or incidents noticeboard report, or a request for arbitration, as appropriate.
  3. to argue technicalities and nuances (about what the optimal action would have been, for example), outside of an argument that the action was inconsistent with policy.
  4. to ask for a review of arbitration enforcement actions. Such reviews must be done at arbitration enforcement noticeboard ("AE"), at the administrators' noticeboard ("AN"), or directly to the Arbitration Committee at the amendment requests page ("ARCA").
  5. for urgent incidents and chronic, intractable behavioural problems; use Wikipedia:Administrators' noticeboard/Incidents ("ANI") instead
  6. for serious, entrenched or persistent disputes and cases of rule-breaking; use Wikipedia:Arbitration ("ArbCom") instead
  7. for a block marked with any variation of {{CheckUser block}}, {{OversightBlock}}, or {{ArbComBlock}}; Contact the Arbitration Committee instead
  8. to attack other editors, cast aspersions, or make accusations of bias. Such requests may be speedily closed.

Instructions
Initiating a review

  1. Before listing a review request, try to resolve the matter by discussing it with the performer of the action.
  2. Start a new discussion by clicking the button below and filling in the preloaded template.
  3. Notify the performer of the action of the discussion.
    You must leave a notice on the editor's talk page. You may use {{subst:XRV-notice}} for this purpose.
    Use of the notification system is not sufficient.

Start a new discussion

Participating in a discussion
Any editor in good standing may request a review or participate in discussing an action being reviewed. Participation is voluntary. The goal of the discussion is to determine whether the action is consistent with Wikipedia's policies. Contributions that are off-topic may be removed by any uninvolved administrator. You may choose to lead your comment with a bold and bulleted endorse or not endorsed/overturn, though any helpful comment is welcome. Please add new comments at the bottom of the discussion.

Closing a review
Reviews can be closed by any uninvolved administrator after there has been sufficient discussion and either a consensus has been reached, or it is clear that no consensus will be reached. Do not rush to close a review: while there is no fixed minimum time, it is expected that most good faith requests for review will remain open for at least a few days.

The closer should summarize the consensus reached in the discussion and clearly state whether the action is endorsed, not endorsed, or if there is no consensus.

After a review
Any follow-up outcomes of a review are deferred to existing processes. Individual actions can be reversed by any editor with sufficient permissions. Permissions granted at WP:PERM may be revoked by an administrator.

Closed reviews will be automatically archived after a period of time. Do not archive reviews that have not been formally closed.

review of pblock

There's not much in the way of uninvolved feedback here, but what little we have seems to indicate that the block (which has since been lifted) was within discretion. Extraordinary Writ (talk) 23:28, 19 April 2023 (UTC)[reply]

The following discussion is closed. Please do not modify it. Subsequent comments should be made on the appropriate discussion page. No further edits should be made to this discussion.

Action: Partial-block from article space of Simoooix.haddi for edit warring and disruptive editing to push a POV at various pages, most recently here, here, here.
User: Valereee (talk · contribs · logs)

I p-blocked this editor after various discussions, and I'm not actually sure I've got it right. The other editor in the dispute, M.Bitton, may be just as much at fault. I don't have any expertise in the subject, just wanted to see if this seemed reasonable. Just a reality check for me. Valereee (talk) 16:00, 9 April 2023 (UTC)[reply]

I came to Wikipedia with the intention to contribute, and I acknowledge that I may make mistakes soemetimes. However, I do not believe that my last edits were disruptive. It would be beneficial to have editors with at least some basic knowledge about the subject to confirm this. Unlike M.Bitton (who was reverting my edits after following me of course), I have provided explanations for my last edits in the comments. SimoooIX (talk) 16:17, 9 April 2023 (UTC)[reply]
Neither Algerian nor Ottoman victory is very illuminating for the reader here given the current state of the article. I am pretty sure that if you had spent some time improving the content, for instance at least linking to Oruç Reis there would not be such skepticism of your edits. I think you do have a minor point, but best if you were to first explain to the reader before just changing the info boxes. fiveby(zero) 17:24, 9 April 2023 (UTC)[reply]
I appreciate your response. While I acknowledge that "Ottoman" may not be entirely accurate, it was the best term I could come up with. Referring to it as an "Ottoman victory" is still way better than calling it an "Algerian victory," as the latter would be an anachronism. SimoooIX (talk) 17:32, 9 April 2023 (UTC)[reply]
The word Ottoman has no place in there for the simple reason that the Barbarossa brothers didn't seek the help of the Ottomans until after those dates (this is basic knowledge). M.Bitton (talk) 18:21, 9 April 2023 (UTC)[reply]
basically Barbarossa brothers were Ottoman corsairs before coming to modern-day Algeria. SimoooIX (talk) 18:28, 9 April 2023 (UTC)[reply]
I don't mind teaching history, but this is not the place to do it. For now, things like you personally attacking me on your third ever edit (for no reason whatsoever) and insulting the Algerian president on fr.wp are more relevant. M.Bitton (talk) M.Bitton (talk) 18:31, 9 April 2023 (UTC)[reply]
You could have "teached" me history in your comments when you reverted my edits. SimoooIX (talk) 19:30, 9 April 2023 (UTC)[reply]
  • Good p-block--without any opinion on which text is more correct, Simooix.haddi has edit warred across multiple articles and expressed clear intent at M.Bitton's talk page to continue edit warring (largely based on what appear to be honest misunderstanding of our edit warring policy), without adequately engaging in discussion at a relevant talk page. Simooix can now continue to seek a consensus by starting talk page discussions in the appropriate locations, with reference to RS. signed, Rosguill talk 17:12, 9 April 2023 (UTC)[reply]
    Sorry but did i "express clear intent at M.Bitton's talk page to continue edit warring"? I don't think so.
    I have reverted their edits since they didn't give any explanation for their revert in the comments. SimoooIX (talk) 17:25, 9 April 2023 (UTC)[reply]
    This string of responses is what concerns me. Also, your participation here isn't really desired; Valereee is asking for input from other administrators and experienced editors--even if you fit that description, as the subject of the p-block you will have an obviously biased view of its propriety. You can request that the block be lifted by filing a normal unblock request at your talk page; although unless/until an uninvolved editor opines here that the block was inappropriate, you're not going to get very far making that assertion (a more successful unblock request would clarify how you intend to deal with editing disputes moving forward). signed, Rosguill talk 17:43, 9 April 2023 (UTC)[reply]
    "This string of responses is what concerns me." i didn't mean that i wil continue edit-warring by that.
    "Also, your participation here isn't really desired;Valereee is asking for input from other administrators and experienced editors--even if you fit that description". Valereee sent me a link to this discussion. I think that's an invitation. SimoooIX (talk) 18:00, 9 April 2023 (UTC)[reply]
    It was a courtesy notification, as we'd be discussing you. I'm really here because I want to hear what other experienced, well-intentioned editors think. I wish the two of you would stop relitigating your disputes. Valereee (talk) 19:46, 9 April 2023 (UTC)[reply]
    Trust me that's what i wish too. I also hope if just M.Bitton's interactions would be less toxic than they already are.
    I admit that i have made a mistake in my third edit (which i apologized for already). but I'm not the only one who had issues with this editor. SimoooIX (talk) 20:07, 9 April 2023 (UTC)[reply]
What is p-block? Permanent block? Partial block? Practical block? Some of us are civilians, can't assume we are up on all the jargon.
Also, User:Rosguill, "Your participation here isn't really desired" is not how we work here. Sorry, but I skipped the rest of your post after that. I don't have time for engaging editors who write stuff like that. If you're going to write things like that you should learn to expect that I guess.
OK, so, I don't have time or interest to look over the whole thing, and there's no link for the various discussions, but just looking at Siege of Jijel, we have:
  • User:Simoooix.haddi changes "Algerian" to "Ottoman. On the merits, I assume it's debatable -- The Algerian forces were operating under the nominal suzerainity of the Ottomans IIRC, so the bold edit is defensible. The edit summary is very poor and actually inflammatory: "Algerian victory in 1517? That doesn't make any sense". But it makes perfect sense. It might be wrong, but its not madness. Don't do that. Insulting edit summary = bad edit. I'd consider a rollback on that basis.
  • So User:M.Bitton rolls back that edit, but doesn't say why. No edit summary. Is the rollback because Bitton doesn't agree with the content? Or the edit summary? or doesn't like Simooox personally? Or the Ottomans generally? Or just likes to revert stuff? Who knows? The proper edit summary would be "Reverted per WP:BRD, make your case on talk". But they didn't do that. Bad.
  • Simoooix then should have not reverted the edit and instead opened a thread on talk page making their case. But instead he reverted again -- edit war now looming, particularly since their summary was "aren't you the warrior against anachronism?" which is about the editor not the edit. Bad. However, since Bitton left no edit summary, which is kind of dismissive. it's understandable that Simoooix would just revert. Wrong, but to a degree just being human.
  • So the next step would be Bitton (or anyone) to re-revert, with an edit summary something like "Reverted again per WP:BRD, DO NOT EDIT WAR, instead make you case on the talk page" Optional extra work, but best, would be for Bitton (or someone) to open a thread on the talk page with content like "An editor is changing Ottoman to Algerian and is insisting, they are requested to make their case here". I generally do this. But nobody has done this yet.
So, I think what we have here is an opportunity for a learning experience. User:Valereee could have left messages on both editors' talk page teaching them how it should have been done. This is how the admin corps, the best of our best, helps editors to learn and grow. That is how the editor corps improves, and that's more important than the somewhat obscure issue at hand.
So really nobody was excellent here. I guess there's more expectation for an admin to be excellent, or try, tho. If Valereee didn't have the time to do this correctly, per WP:FAILSAFE they should have let it go, I guess. So, maybe a growing experience for all three participants.
And your second choice would have been to take the issue to ANI I think. If you're going to block somebody -- and per WP:HURTS every block risks permanently alienating the editor, or at least hurting their morale -- do that. Get other admins's eyes on it, an let the editor have a chance to explain themself. (And, finally... I gather this has spread over several articles, but that just makes it more compelling to educate the participants.) Herostratus (talk) 17:51, 9 April 2023 (UTC)[reply]
Herostratus My suggestion to SimoolX was primarily so that they would avoid providing additional rope here to justify their hanging. If you'd read the rest of my comment, that would have been quite clear, as I gave them advice for how to go about requesting an unblock. There's also the irony that you apparently don't know what WP:P-block means and couldn't be bothered to look it up? signed, Rosguill talk 17:57, 9 April 2023 (UTC)[reply]
I hope that "you apparently don't know what [first use of acronym, and not even linked] means and couldn't be bothered to look it up" isn't how you you think toward the reader when you write articles. I'd like the same courtesy. There's hella acronyms here. I get that "everybody knows what I do, or anyway should" is a common, if unconscious, human attitude. Fight it.
You gave three examples of bad behavior right off. I picked one. It wasn't bad behavior, or anyway egregious, or much worse than the other guy. There's a limit to how deep I can or will dig.
Asking for feeback on actions is admirable, and good on you. If the attitude is "wtf dude, I expect confirmation and flattery, not actual critisism'" (and I've seen this before), not so great. Don't snark at me for your failure to at least take this to ANI discussion before kicking an editor off the project -- and every block has an n-percent chance of that, where n is some non-zero numbers. If you don't know that you had better learn fast, I think. Herostratus (talk) 19:57, 10 April 2023 (UTC)[reply]
Rosguill didn't take the action or open this discussion. I did those. Valereee (talk) 12:23, 11 April 2023 (UTC)[reply]
You might expect them to know what this discussion is about, but there's a limit to how deep they can or will dig. ScottishFinnishRadish (talk) 12:31, 11 April 2023 (UTC)[reply]
FWIW, I did discuss/advise at both editors' talks here, here, here and here and an article talk, plus at another editor's user talk. I'm not sure where I gave the impression this was a lack-of-time issue, I've been editing all day. For me this is a 'was this the right move?' issue. Valereee (talk) 17:59, 9 April 2023 (UTC)[reply]
I appreciate your previous intervention on the ScotishFinishRadish talk page, where you were impartial and listened to both sides. However, I'm disappointed that you didn't follow the same approach this time. Instead of discussing the matter, you blocked me without warning and labeled my edits as 'disruptive'. SimoooIX (talk) 18:15, 9 April 2023 (UTC)[reply]
  • Why did you set the p-block duration to indefinite, Valereee?—S Marshall T/C 20:40, 9 April 2023 (UTC)[reply]
    SM, what I'd like to see is this editor listening to what people are telling them. An indef requires someone to listen rather than simply waiting something out. I have zero objection to anyone lifting the block once the editor starts listening instead of arguing. Valereee (talk) 20:52, 9 April 2023 (UTC)[reply]
    Indeed. Time limited blocks do not ensure understanding. An indefinite block is not of infinite duration. It can be removed once understanding is understood. Sometimes sooner than a randomly determined time-limited block. -- Deepfriedokra (talk) 21:01, 9 April 2023 (UTC)[reply]
    I have experienced disagreements with other editors where I was in the wrong side. In those instances, when the other editor explained themselves in a civil and respectful manner, and pointed out my mistakes, I was convinced and expressed gratitude. However, unfortunately, that was never the case with M.Bitton. SimoooIX (talk) 21:29, 9 April 2023 (UTC)[reply]
The discussion above is closed. Please do not modify it. Subsequent comments should be made on the appropriate discussion page. No further edits should be made to this discussion.

Review of concerning block

Action: https://en.wikipedia.org/wiki/Special:Log?type=block&user=&page=user%3ABatreeq&wpdate=&tagfilter=&wpfilters%5B%5D=newusers&wpFormIdentifier=logeventslist
User: Courcelles (talk · contribs · logs)

It seems I was blocked as a punishment. Per the first link above, I attempted a constructive discussion above and the other edit warrior abandoned the discussion (Talk:Asmara#Native_name_in_infobox). They reported me to 3RR once, but it was closed due to inactivity. I reported them citing their abandonment of the talk page discussion, and as noted above the thread was ignored by the initial administrator. Finally, they reported me again and Courcelles blocked both of us. Unacceptable. I have tried to clarify why only to be ignored. There is lack of accountability and the block appears to have wrongly been used as a punishment. Keep in mind that I never actually violated 3RR and was trying to keep a talkpage discussion going, so you can see why I see this block as unjust. I do have a fairly good track record on WP with this being my first block. Such aggressive measures have potential to drive people away, and I am reconsidering my involvement after this blatant abuse of authority! Driving people away is obviously not conducive to attracting people of diverse backgrounds across the world to enhance the world's largest encyclopedia. – Batreeq (Talk) (Contribs) 03:56, 11 April 2023 (UTC)[reply]

  • I think the block was excessive for an editor who had not yet been notified of CTOP procedures, but still a justifiable response to low-level edit warring at Asmara. Both Batreeq and Leechjoel were clearly aware of the ongoing dispute given the prior failure to resolve the issue on a talk page, and should have proceeded to organizing an RfC rather than resorting to edit warring. A short block by an uninvolved admin responding to a reasonable edit warring report with a clearly given explanation is not abuse. signed, Rosguill talk 04:52, 11 April 2023 (UTC)[reply]
    So then what should have happened, from an objective standpoint, is both editors be referred to WP:RFC. I will admit that despite being on WP for a long time (though not a highly active editor), I am not familliar with all the rules, policies, processes, etc... (WP:CREEP) including RfC. It is therefore the duty of those granted administrator privileges to keep this in mind in these situations.
    While I don't think this was blatant abuse, an outright wasn't the right way of going about it nor the most appropriate use of the blocking tool (which I still take issue to because it appears to have been used to punish) especially considering the miniscule effect a 24 h block has on something that has been happening, spaced out over weeks to months, since 2021. – Batreeq (Talk) (Contribs) 09:10, 11 April 2023 (UTC)[reply]
You do not need to have violated 3RR to be considered edit-warring. Curbon7 (talk) 05:14, 11 April 2023 (UTC)[reply]
I'm not sure I'm following the diffs perfectly, but Batreeq, it looks like you've reported people/been reported before for edit-warring? Valereee (talk) 13:01, 11 April 2023 (UTC)[reply]
If you were blocked, as you claim, as punishment, then one would think that the other user was also blocked for punishment. Two editors are warring over some content, two editors get blocked. Drmies (talk) 14:21, 11 April 2023 (UTC)[reply]
  • Oh, this is new. I submit that Batreeq was aware enough of our policies on edit warring to [5] accuse another editor of violating them last year. Ironically, in this same dispute that has now entered a third year of reverting, between the same two editors! I was shocked to find that Bateeq was formally unaware of CTOP, while Leechjoel9 was. Given the equality of disruption, but the inequality of awareness, I chose to take the same action with both editors, a day block and a formal warning in the AE log against edit warring. And to assuage adminacct concerns, I responded to Bateeq on ANEW while reverting their attempts at threaded discussion on the AElog itself. Courcelles (talk) 14:54, 11 April 2023 (UTC)[reply]


A few thoughts:

  • It was a slow motion edit war. The recent ones of those reported averaged weeks apart and all of the reported ones averaged months apart. In light of this a 24 hour block could not possibly be seen as directly preventative. However just giving someone a "whack" might be seen as preventative to stop the behavior although such a rationale is not "official". So "as punishment" is not the only alternate explanation to "clearly p[reventative"
  • IMO Batreeq has been shown to be more wiki-saavy than they profess to be. However it's quite common for moderately experienced editors to not be fully aware of the minefield that WP:CTOP articles are. Also, it is plausible that they did not fully realize that a slow motion edit war is still a sanctionable edit war.
  • It can be argued that a 24 hour block is not severe. Nevertheless, the more that somebody cares the more severe it is, so it would be a mistake to automatically consider a 24 hour block to be not severe.

IMO, both from a fairness and effectiveness standpoint there should have been a warning first. IMO Courcelles did what they thought was best but should have thought this through more thoroughly. Also, being close to an edge case makes it not indicative of an admin problem, just a review of this action. That said, making the same edit ~10 times over ~2 years was a behavior that needed to be stopped. North8000 (talk) 15:55, 11 April 2023 (UTC)[reply]

  • Looks like a reasonable block. Slow motion edit warring is still edit warring, and the fact 3RR wasn't breached doesn't mean nobody can be blocked. Neither party has engaged in any talk page discussion about this in the last year, and if someone else isn't engaging then there are other ways to resolve a dispute other than edit warring. Normally I'd expect some sort of warning to make sure the editor is familiar with policies on edit warring, but Batreeq has given such a warning to the other editor and reported them to an edit warring noticeboard, so that isn't necessary here. Blocks can be used to "deter the continuation of present, disruptive behavior" according to the blocking policy, it's clear the edit warring was going to continue. Hut 8.5 18:36, 11 April 2023 (UTC)[reply]
  • So where do we go from here? In regards to settling the dispute with the article, since that editor refuses to engage on the talk page. – Batreeq (Talk) (Contribs) 21:55, 14 April 2023 (UTC)[reply]
    Batreeq, you should open an WP:RfC. I would recommend using the opening statement Should the Arabic name of the city be listed in the infobox? Prior discussion at Talk:Asmara#Native_name_in_infobox. then list your argument in a subsection for discussion. signed, Rosguill talk 22:11, 14 April 2023 (UTC)[reply]

Summary?: It's been 8 days since the last post regarding the block. IMO the result is that that it would have been better and more typical to precede it with some type of of warning/ notification, but that the use of the block was not improper. North8000 (talk) 17:21, 19 April 2023 (UTC)[reply]

Cullen328's block of Esculenta

Action: block of Esculenta [6]
User: Cullen328 (talk · contribs · logs) (prior discussion)

I'm requesting review of Cullen328's block of Esculenta.

It happened immediately after this ANI thread was started, before almost anyone had responded. The reason given for the one-month block was Disruptive editing: Unapproved mass creation of articles and another content using ChatGPT or other AI technology. From the subsequent discussion, it became clear that no disruption had occurred (there was only positive feedback on the articles in question), that the allegation of mass creation was dubious (the editor had created barely four articles per day for the preceding week), and that there was no credible evidence for the involvement of AI (with decent evidence to the contrary).

The only legitimate criticism of Esculenta was for earlier incivility, but that would have never required a block, let alone one of such duration. I find it disturbing that such a block could have happened, and it's troubling that it still hasn't been reversed. – Uanfala (talk) 22:14, 28 April 2023 (UTC)[reply]

Retrieved from "https://en.wikipedia.org/w/index.php?title=Wikipedia:Administrative_action_review&oldid=1152217432"