Misplaced Pages

:Arbitration/Requests/Case: Difference between revisions - Misplaced Pages

Article snapshot taken from Wikipedia with creative commons attribution-sharealike license. Give it a read and then ask your questions in the chat. We can research this topic together.
< Misplaced Pages:Arbitration | Requests Browse history interactively← Previous editContent deleted Content addedVisualWikitext
Revision as of 19:14, 15 August 2014 view sourceTarc (talk | contribs)24,217 edits →Statement by Tarc: - further on the "suspected sock" angle← Previous edit Latest revision as of 04:54, 26 December 2024 view source MJL (talk | contribs)Extended confirmed users, Page movers, New page reviewers, Pending changes reviewers, Rollbackers, Template editors42,350 edits →Sabotage of Lindy Li's page: removing case as premature: declinedTag: Manual revert 
Line 1: Line 1:
<noinclude>{{Redirect|WP:ARC|a guide on talk page archiving|H:ARC}}
<noinclude>{{pp-semi-indef|small=yes}}{{pp-move-indef}}</noinclude>
{{ArbComOpenTasks}}__TOC__{{pp-semi-indef|small=yes}}{{pp-move-indef}}{{-}}

</noinclude>
=<includeonly>]</includeonly>=
<includeonly>= ] =</includeonly><noinclude>{{If mobile||{{Fake heading|sub=1|Requests for arbitration}}}}</noinclude>
<noinclude>{{ArbComOpenTasks|acotstyle=float:right}}</noinclude>{{NOINDEX}}
{{NOINDEX}}
{{Misplaced Pages:Arbitration/Requests/Case/Header<noinclude>|width=53%</noinclude>}}
{{Misplaced Pages:Arbitration/Requests/Case/Header<noinclude>|width=auto</noinclude>}}
== Banning Policy ==
<noinclude>{{-}}</noinclude>
'''Initiated by ''' ] (]) '''at''' 17:58, 15 August 2014 (UTC)

=== Involved parties ===
<!-- use {{admin|username}} if the party is an administrator -->
*{{userlinks|Hell in a Bucket}}, ''filing party''
*{{userlinks|Tarc}}
*{{userlinks|Smallbones}}
*{{userlinks|Jimbo Wales}}

<!-- The editor filing the case should be included as a party for purposes of notifications. -->

;Confirmation that all parties are aware of the request
<!-- All parties must be notified that the request has been filed, immediately after it is posted, and confirmation posted here. -->
*Diff. 1]
*Diff. 2]
*Diff. 3]

;Confirmation that other steps in ] have been tried
<!-- Identify prior attempts at dispute resolution here, with links/diffs to the page where the resolution took place. If prior dispute resolution has not been attempted, the reasons for this should be explained in the request for arbitration -->
*Link 1 ] (couldn't find in archives)
*Link 2 ]
*Link 3 ]
=== Statement by Hell in a Bucket ===
There is a lot of dispute if ] is covered under talkpage posting. It's my understanding that when banned that person is persona non grata and all edits are to be reverted. If in an article and it's not vandalism another editor may take responsibility for that edit but posting on their behalf or attempting to repost their concern is not appropriate. Enter ]. Tarc has been blasting insults, incivility and outright trolling on Jimbos page. Edits such as ] or this edit summary ]. Apparently the word cunt is not ok but telling a editor ] or telling me ] or the attitude that this is a game ]. There are many more edits stating that Smallbones and myself are whiteknighting, overzealous and etc. Jimbo has not replied and there is an impasse as Smallbones and I are within policy to revert on sight edits on or on behalf of a banned user without regard to 3rr. Why will we ban people then let them post if it's good contributions, there are plenty other editors with lots of great contributions banned and there is no question about it. ] (]) 18:18, 15 August 2014 (UTC)
:@Konveyor, if there was significant doubts you are correct but in this case all three accounts were spouting the same thing, terms of use nonsense, it was a very very clear duck case. It was clear enough theat a checkuser was done but I didn't have the correct beginning user which from the Block log the TheKohser isn't actually the master either but an older account ], at least according to this block log. ] (]) 18:35, 15 August 2014 (UTC)
::] that's why we are here you can't understand the difference of usage of the word as a word and an epithet. Please point out where I called someone a cunt? If you want people to be CIVIL you have to actually be civil yourself, not ask if they have the balls. I do that's why we are here, you are trolling and as ] rightfully says trying to pick a fight. Arbcom has dealt with the last comment you can drop your ] now, your horse is dissecated now, now move on to your disruptive trolling, time for a new issue. ] (]) 19:11, 15 August 2014 (UTC)

=== Statement by uninvolved Konveyor Belt ===

{{ping|Hell in a Bucket}} "It's my understanding that when banned that person is persona non grata and all edits are to be reverted." This is not the central argument here. Tarc or anyone else does not deny this policy. Rather, the debate is whether uninvolved editors can revert suspected socks with no proof of socking, as this is what you and Smallbones have been doing. <span style="text-shadow:0em 0em 1em #003399;">]</span><span style="text-shadow:0em 0em 1em #FF8C00;">]</span> 18:26, 15 August 2014 (UTC)

=== Statement by Kww ===
I think it's pretty obvious that Tarc is doing this solely to stir up a fight, a.k.a. to disrupt Misplaced Pages. There's no possible improvement to an encyclopedia by restoring talk page comments by a banned editor, so ] is inapplicable. As for Konveyor Belt's argument: so long as we have our restrictions on checkuser in place, an admin's best judgement is all we generally have to go on when it comes to socking and block evasion. It's apparent from the discussion that Tarc agrees that the edits are likely from a banned editor, and is "''taking ownership''" only as fig-leaf to preserve the comments.&mdash;](]) 18:30, 15 August 2014 (UTC)


=== Statement by uninvolved editor ] ===
It seems to me that if an edit from a banned user introduces content of sufficient quality that another editor in good standing sees fit to restore it after a revert, in the absence of evidence that the user in good standing is acting as a sockpuppet, the restored content should not be subject to reversion on-sight, as the alternative allows banned editors an effective heckler's veto. ] 18:47, 15 August 2014 (UTC)

=== Statement by Tarc ===
Hell in a Bucket is mounting a rather superlative misdirection campaign by highlighting my use of silly internet memes ("a challenger appears", come at me bro", etc...) in edit summaries. For someone who casually throws around misogynist c-bombs into discussions in this project, and someone who acts as deplorably as he did at ] in defending the c-word, I find it to be the height of hypocrisy to call ''anyone'' out for incivility.

This whole mess is about a few different things, but one in particular; a fundamental difference in opinion regarding what it means to edit a page in this project, be it a user talk page or an article-space page. One site has a strict interpretation of "banned means banned", and that all edits by socket (whether proven or unproven) can and will be reverted on sight. This means that any possibly banned user who posts a question to Jimbo's talk page is automatically reverted, as well as a possibly banned user who adds a freely-licensed image to an article is automatically reverted. The other side wishes to evaluate the merits of the post or the article addition and believes that either should remain in place unless there is something egregiously wrong, e.g. ] or a topic ban violation. This is a collision of a draconian interpretation of the ban policy vs. how things usually flow in this project, and have flowed for years. Users have traditionally been granted a bit latitude in allowing banned users to post to their talk pages; I do that myself with a few people on mine. Users have also been traditionally able to "take responsibility" for revert article content and have been able to re-add it as their own if deemed a "good edit". Both of these have been denied lately; at Jimbo's page, and one involving a suspected sock of Russavia. I asked Kww if he plans to call for a block of the user, as he threatened to do to me, who restored the image at Dassault Falcon 7X, but have yet to see a response.

Note: despite Kww's false assertion and , I have not actually ever restored content added by a Russavia sock, though I believe his situation and the one we're going over here are two aspects of the same problem.

The other aspect of this is the situation of editors reverting ''suspected'' socks of banned/blocked users...and no, not that they are literally flagged as a suspected sock, but that the reverter him/herself is the one with the suspicion. That is how I got embroiled into this mess initially, when Hell and Smallbones were reverting an account with no block log and no SPI. The account is ''now'' blocked, but I and others are rather uncomfortable with regular users patrolling another user's talk page and removing content based on their own guesswork alone.

If this case is accepted, I would urge the committee to ''not'' focus on the ''who'' but more of the substance of what is at stake here. "Russavia" and "Mr. 2001" (alleged to be "thekohser") are being invoked here as boogeymen, people that quite frankly no one, even myself, particularly care for. We shouldn't craft policy or make decisions with the aim in mind of punishing specific editors.

So this is where we're at... "banned means banned" vs. "if a rule prevents you from improving the encyclopedia, ignore it". ] (]) 18:51, 15 August 2014 (UTC)

=== Clerk notes ===
:''This area is used for notes by the clerks (including clerk recusals).''

=== Banning Policy: Arbitrators' opinion on hearing this matter <0/0/0/0> ===
{{anchor|1=Banning Policy: Arbitrators' opinion on hearing this matter}}<small>Vote key: (Accept/decline/recuse/other)</small>

== DragonflySixtyseven ==
'''Initiated by ''' -- ] ] '''at''' 02:20, 13 August 2014 (UTC)

=== Involved parties ===
<!-- use {{admin|username}} if the party is an administrator -->
*{{admin|DeltaQuad}}, ''filing party''
*{{admin|DragonflySixtyseven}}
*{{admin|Toddst1}}, ''inactive''
*{{admin|Bbb23}}
*{{userlinks|Rlevse}}, ''inactive''
<!-- The editor filing the case should be included as a party for purposes of notifications. -->

;Confirmation that all parties are aware of the request
<!-- All parties must be notified that the request has been filed, immediately after it is posted, and confirmation posted here. -->
*
*
*
*

;Confirmation that other steps in ] have been tried
<!-- Identify prior attempts at dispute resolution here, with links/diffs to the page where the resolution took place. If prior dispute resolution has not been attempted, the reasons for this should be explained in the request for arbitration -->
*
*
*
*
*

=== Statement by DeltaQuad ===
From incidents spanning from late 2007 to present day, DragonflySixtyseven has demonstrated issues with ] and the ], in relation to his administrative actions. At least 5 times since the start of 2007, Dragonfly67 has inappropriately reverted other administrators blocks without seeking consensus at any time nor contacting the original blocking administrator. He did not even discuss the original action with the administrators making them.

Last time in 2011, ], Dragonfly67 ] by , which he failed to follow through on when he unblocked & .

There are 5 relevant incidents listed below:
#] (specifically the )
#
#
# (the two blocks by the original admins were for different reasons)
#The Aug 2014 unblock of &

Furthermore DS67 seems to ] for a users actions, which is a community-wide administrative duty. In the 2011 incident (see block log link above) he says ''"Pay attention. I said, a) I'm not convinced he's a sock, b) '''if he gets out of line, I'll block him myself. I'm handling this. If he misbehaves, bring him to my attention.'''"'' (emphasis my own), telling other admins that they must go through him to take action on him. I did not see that at the time coming from an SPI when I made my block.

These actions make it difficult for administrators to work with DS67, and there is a repeat issue. Each time that it has been taken to ANI, admins have disagreed with the process DS67 has taken. The admins, every time have been left not happy with the result, and unwilling to wheel war for fear of getting sanctioned themselves, including myself. Also, there is a disregard for declined unblock requests at the time of some of the unblocks. I'm not here because I think desysop is the right or best option, but clearly talking it out one on one or with the community hasn't produced results. -- ] ] 02:20, 13 August 2014 (UTC)
:{{ping|AGK}} I don't have the perfect answer for you as to how were going to deal with this. Dispute resolution is never about knowing the outcome of it. Could it work, yes. Will it work, it's hard to say. I was hoping, as I said on DS' talkpage to refile if things didn't resolve out, so i'm not saying this won't need Arbitration yet, i'm saying not now. I'm not trying to slap arbitration procedure here, but as Floquenbeam said, this now makes it harder for me to refile down the road if I can't resolve it out. If someone had commented, the fine, I could see it, but no one did. You have already found everything that is being discussed so far at ] talkpage, which hasn't gone far just yet. -- ] ] 23:15, 14 August 2014 (UTC)

=== Statement by uninvolved Go Phightins! ===
It seems preposterous to me that this case has to remain open, notwithstanding the fact that the initiator no longer wishes to see an arbitration, and is exchanging dialogue with the other user in question. Isn't the whole point of arbitration a last resort to other forms of dispute/conflict resolution? Please let this close without someone voting accept ... '''] ]]''' 19:49, 14 August 2014 (UTC)

=== Statement by Floq ===
I understand the reopening was done because of a very specifically worded procedure ], but this would have been a great time to IAR. Now that it's back, I agree with GP that letting this fade away would be best for now. Discussion is ongoing.

<small>And {{ping|Go Phightins!}} regarding your edit summary: with two daughters, every time I see the words "let it go" now, a horrible song from ] starts running through my brain and I can't make it stop. If you do that to me again, I will block you indefinitely.</small> --] (]) 21:10, 14 August 2014 (UTC)

*AGK: Well, the biggest development is that 36 minutes after it was filed, the filer decided to approach it another way, and withdrew the request before anyone - involved party, kibitzer, or arb - made any comment. I'm not sure why any other development needs to have occurred. But the filer did post on DS67's talk page, and began a discussion about it. I have no idea how they are going to deal with this, or if they will be successful, but I find it hard to believe that not giving them a chance to do so is for the best. The problem is, by resurrecting this now, before that discussion has a chance to go anywhere, I think it makes it very difficult for the filer to start a case if it doesn't work out in a week. That's why allowing it to be withdrawn (now, optimally, but in 13 hours if we must wait (or 4 hours if we count from DQ's initiation, and not AGK's restoration!)), without anyone voting accept or decline, would be best IMHO. --] (]) 22:19, 14 August 2014 (UTC)

=== Statement by Bbb23 ===
Considering that the probability is this will be declined, I just want to make a few procedural points. Although everyone was notified, those notifications were reverted when DQ withdrew the request, so they may not be aware of this request. DQ withdrew the case because, as I understand it, he thought that the only possible outcome was a desysop or nothing. I have since disabused him of that notion. Nonetheless, he still appears to want to keep this from ArbCom until there's more discussion on DS's talk page, and I believe we should honor his wish. {{ping|Worm That Turned}} As is obvious from the discussion on DS's talk page, I, too, was unaware of DS's history. I'm glad I wasn't alone in that regard. :-) --] (]) 00:48, 15 August 2014 (UTC)
=== Statement by NE Ent ===
It seems to me the committee has enough time wasting, energy sapping pointless scutwork to do (i.e. WMF drama) without dragging cases out of the dustbin. I always thought the pillars were quite clear: ] Let it go, let it go, turn away and slam the door! <small>]</small>

=== Statement by Nsk92 ===

I am not familiar with the block issues that led to the current request and it seems that there is a rush to decline this case. But I feel that, as long as the case is being considered for possible acceptance, DF67's deletion practices should also be discussed. In my opinion, DF67's deletion summaries are consistently inadequate and have been so for years. I brought this matter up at ANI a few years ago but of course nothing happened. As far as I can tell, DF67 never closes any XfD's or PRODS and almost all (or perhaps all) of his deletions involves pages that have not been CSD tagged/PRODDed/XfDed by another editor.
Presumably all of these deletions are done as CSDs, but the deletion summaries (with rare exceptions when G6 or G8 is mentioned) almost never indicate that a deletion is performed on ] grounds. Instead, typically DF67's deletion summaries provide a general verbal explanation such as "inappropriate use of user page", "overly promotional", "for user's own good", "notability not asserted", "this is not an article", etc. In the vast majority of cases these pages probably did need to be deleted, but that does not excuse the consistently inadequate nature of DF67's deletion summaries. First, when the specific deletion process (XfD,PROD or CSD) used to delete the page is not specified in the deletion summary, it is not clear which venue and how the page creator should use to appeal the deletion after it happened. Second, if, as it appears to be the case, DS67 deletes all these pages without CSD tagging them first, this deprives the page creators and other interested editors from the opportunity to contest deletion and possibly try to quickly improve the page. Usually, even in fairly obvious CSD A7 and A9 cases, the page's creator gets at least a few minutes of grace period to contest the deletion and try to improve the page after the page is CSD tagged and before it is actually deleted. (There are cases like CSD G6, where it is fine to delete a page without CSD tagging it first, but I would think that for most mainspace and user pages CSD tagging a page is necessary before the actual deletion). Third, it is not clear to me that it is appropriate for an admin to delete a page that he/she CSD tagged, even if a few minutes of grace period are given to the page's creator to contest a CSD nomination. CSD is a process that requires high precision and I always assumed that at least two sets of eyes (the person placing a CSD tag and then an admin performing the deletion) are needed in terms of checks and balances, except for technical cases. Fourth, many of DS67's deletion summaries appear problematic even if one interprets them as simply CSD nominations. For example, DF67 often uses "notability nota asserted" as the deletion summary for mainspace articles, e.g. ,, , , , etc. It is not necessary for an article to '''assert''' notability even for surviving an AfD, and it is certainly not required for overcoming CSD A7 and A9 criteria that a page '''assert''' notability. What is needed to overcome CSD A7 and A9 is that an article provide some plausible indication of notability. There is a big difference between this and "asserting" notability. DF67 also deletes, again apparently without CSD tagging them first (and without using MfD) lots and lots of user pages; again presumably these deletions are made basically as CSD deletions, even though the deletion summaries used by DF67 do not indicate this. A typical deletion summary used by DF67 when deleting user pages is "inappropriate use of user page" ], ], ], ],], ], etc. Another favorite of DF67 is "for user's own good" ],],],], etc. What are we supped to think happened here? Is he using CSD U5? CSD G11? Or something else? It's impossible to tell, and it is not even clear that for some of these user pages there is a relevant CSD criterion that could be invoked. Plus in general, deleting a user page is a pretty radical step that many editors take as an affront, and usually a prior warning to the author is in order possibly followed by an MfD. All of the above diffs/links refer to deletions that took place within the last 30 days. There are too many problems here as we are not talking about an occasional application of IAR but rather about a consistent deviation from our standard deletion procedures. ] (]) 02:12, 15 August 2014 (UTC)

=== Clerk notes ===
:''This area is used for notes by the clerks (including clerk recusals).''

=== DragonflySixtyseven: Arbitrators' opinion on hearing this matter <0/3/0/2> ===
{{anchor|1=DragonflySixtyseven: Arbitrators' opinion on hearing this matter}}<small>Vote key: (Accept/decline/recuse/other)</small>

*Awaiting statements. ] ]] 10:37, 14 August 2014 (UTC)
:* {{reply|Go Phightins!}} The procedure is quite clear.<p>All: Could someone summarise what developments since this request was filed make arbitration no longer necessary? How exactly are the small group of editors involved going to deal with this? ] ]] 22:03, 14 August 2014 (UTC)
*Full disclosure - I made a judgement regarding the most recent case and put down some conditions on the user in question, which I thought settled matters between DS and Bbb23. I was unaware of the history around the case and DS' previous unblocks. I don't believe I need to recuse, but if anyone feels I should, please do contact me. Now that's over - I'm awaiting statements, noting that this can be archived in 24 hours if no arbitrator accepts, as DQ has "withdrawn" his request. ]<sup>TT</sup>(]) 11:18, 14 August 2014 (UTC)
*'''Summarily decline, as withdrawn'''. I hope that the discussion elsewhere has been useful. ] (]) 22:46, 14 August 2014 (UTC)
*'''Decline''', if the filer thinks there's still hope short of arbitration, I'm inclined to hope so too. I also think that in cases like this, formal requests for comment can have a reasonable chance of success. I know that not everyone's fond of RfC/U, but it can show that the community believes a change to be necessary (or, alternatively, doesn't), and provide a firm basis for further action if those changes don't occur. The hope, of course, is that the clear statement would eliminate any need for us to take drastic action. ] <small><sup>]</sup></small> 22:55, 14 August 2014 (UTC)
*'''Decline''' (without prejudice) as withdrawn by filer. <span style="text-shadow:grey 0.118em 0.118em 0.118em;" class="texhtml"> ''']'''</span> ] 09:20, 15 August 2014 (UTC)
*'''Decline''' without prejudice. I fully agree that this would have been a good time to ] and this needn't have been forced back open. ] (]) 15:16, 15 August 2014 (UTC)

Latest revision as of 04:54, 26 December 2024

"WP:ARC" redirects here. For a guide on talk page archiving, see H:ARC. Arbitration Committee proceedings Case requests

Currently, there are no requests for arbitration.

Open cases
Case name Links Evidence due Prop. Dec. due
Palestine-Israel articles 5 (t) (ev / t) (ws / t) (pd / t) 21 Dec 2024 11 Jan 2025
Recently closed cases (Past cases)

No cases have recently been closed (view all closed cases).

Clarification and Amendment requests

Currently, no requests for clarification or amendment are open.

Arbitrator motions
Motion name Date posted
Arbitrator workflow motions 1 December 2024
Requests for arbitration


Shortcuts

About this page

Use this page to request the committee open an arbitration case. To be accepted, an arbitration request needs 4 net votes to "accept" (or a majority).

Arbitration is a last resort. WP:DR lists the other, escalating processes that should be used before arbitration. The committee will decline premature requests.

Requests may be referred to as "case requests" or "RFARs"; once opened, they become "cases". Before requesting arbitration, read the arbitration guide to case requests. Then click the button below. Complete the instructions quickly; requests incomplete for over an hour may be removed. Consider preparing the request in your userspace.

To request enforcement of an existing arbitration ruling, see Misplaced Pages:Arbitration/Requests/Enforcement. To clarify or change an existing arbitration ruling, see Misplaced Pages:Arbitration/Requests/Clarification and Amendment.


File an arbitration request


Guidance on participation and word limits

Unlike many venues on Misplaced Pages, ArbCom imposes word limits. Please observe the below notes on complying with word limits.

  • Motivation. Word limits are imposed to promote clarity and focus on the issues at hand and to ensure that arbitrators are able to fully take in submissions. Arbitrators must read a large volume of information across many matters in the course of their service on the Committee, so submissions that exceed word limits may be disregarded. For the sake of fairness and to discourage gamesmanship (i.e., to disincentivize "asking forgiveness rather than permission"), word limits are actively enforced.
  • In general. Most submissions to the Arbitration Committee (including statements in arbitration case requests and ARCAs and evidence submissions in arbitration cases) are limited to 500 words, plus 50 diffs. During the evidence phase of an accepted case, named parties are granted an automatic extension to 1000 words plus 100 diffs.
  • Sectioned discussion. To facilitate review by arbitrators, you should edit only in your own section. Address your submission to arbitrators, not to other participants. If you wish to rebut, clarify, or otherwise refer to another submission for the benefit of arbitrators, you may do so within your own section. (More information.)
  • Requesting an extension. You may request a word limit extension in your submission itself (using the {{@ArbComClerks}} template) or by emailing clerks-l@lists.wikimedia.org. In your request, you should briefly (in 1-2 sentences) include (a) why you need additional words and (b) a broad outline of what you hope to discuss in your extended submission. The Committee endeavors to act upon extension requests promptly and aims to offer flexibility where warranted.
    • Members of the Committee may also grant extensions when they ask direct questions to facilitate answers to those questions.
  • Refactoring statements. You should write carefully and concisely from the start. It is impermissible to rewrite a statement to shorten it after a significant amount of time has passed or after anyone has responded to it (see Misplaced Pages:Talk page guidelines § Editing own comments), so it is often advisable to submit a brief initial statement to leave room to respond to other users if the need arises.
  • Sign submissions. In order for arbitrators and other participants to understand the order of submissions, sign your submission and each addition (using ~~~~).
  • Word limit violations. Submissions that exceed the word limit will generally be "hatted" (collapsed), and arbitrators may opt not to consider them.
  • Counting words. Words are counted on the rendered text (not wikitext) of the statement (i.e., the number of words that you would see by copy-pasting the page section containing your statement into a text editor or word count tool). This internal gadget may also be helpful.
  • Sanctions. Please note that members and clerks of the Committee may impose appropriate sanctions when necessary to promote the effective functioning of the arbitration process.

General guidance

  • This page is for statements, not discussion.
  • Arbitrators or clerks may refactor or delete statements, e.g. off-topic or unproductive remarks, without warning.
  • Banned users may request arbitration via the committee contact page; don't try to edit this page.
  • Under no circumstances should you remove requests from this page, or open a case (even for accepted requests), unless you are an arbitrator or clerk.
  • After a request is filed, the arbitrators will vote on accepting or declining the case. The <0/0/0> tally counts the arbitrators voting accept/decline/recuse.
  • Declined case requests are logged at Misplaced Pages:Arbitration/Index/Declined requests. Accepted case requests are opened as cases, and logged at Misplaced Pages:Arbitration/Index/Cases once closed.