Misplaced Pages

:Arbitration/Requests/Enforcement: 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 editNext edit →Content deleted Content addedVisualWikitext
Revision as of 10:12, 26 September 2014 editUnbroken Chain (talk | contribs)Autopatrolled, Extended confirmed users, Pending changes reviewers, Rollbackers32,193 editsNo edit summary← Previous edit Revision as of 10:14, 26 September 2014 edit undoUnbroken Chain (talk | contribs)Autopatrolled, Extended confirmed users, Pending changes reviewers, Rollbackers32,193 edits →Request concerning NeotarfNext edit →
Line 163: Line 163:


; Notification of the user against whom enforcement is requested : ; Notification of the user against whom enforcement is requested :
]
<!-- Please notify the user against whom you request enforcement of the request, and then replace this comment with a diff of the notification. The request will normally not be processed otherwise. -->


<!--- In the line below, replace USERNAME with the username of the editor against whom you request enforcement. ---> <!--- In the line below, replace USERNAME with the username of the editor against whom you request enforcement. --->

===Discussion concerning Neotarf=== ===Discussion concerning Neotarf===
<small>''Statements must be made in separate sections. They may not exceed 500 ] and 20 diffs, except by permission of a reviewing administrator. <br>Administrators may remove or shorten noncompliant statements. Disruptive contributions may result in blocks.''</small> <small>''Statements must be made in separate sections. They may not exceed 500 ] and 20 diffs, except by permission of a reviewing administrator. <br>Administrators may remove or shorten noncompliant statements. Disruptive contributions may result in blocks.''</small>

Revision as of 10:14, 26 September 2014

"WP:AE" redirects here. For the automated editing program, see Misplaced Pages:AutoEd.
Noticeboards
Misplaced Pages's centralized discussion, request, and help venues. For a listing of ongoing discussions and current requests, see the dashboard. For a related set of forums which do not function as noticeboards see formal review processes.
General
Articles and content
Page handling
User conduct
Other
Category:Misplaced Pages noticeboards

    Click here to add a new enforcement request
    For appeals: create a new section and use the template {{Arbitration enforcement appeal}}
    See also: Logged AE sanctions

    Important informationShortcuts

    Please use this page only to:

    • request administrative action against editors violating a remedy (not merely a principle) or an injunction in an Arbitration Committee decision, or a contentious topic restriction imposed by an administrator,
    • request contentious topic restrictions against previously alerted editors who engage in misconduct in a topic area designated as a contentious topic,
    • request page restrictions (e.g. revert restrictions) on pages that are being disrupted in topic areas designated as contentious topics, or
    • appeal arbitration enforcement actions (including contentious topic restrictions) to uninvolved administrators.

    For all other problems, including content disagreements or the enforcement of community-imposed sanctions, please use the other fora described in the dispute resolution process. To appeal Arbitration Committee decisions, please use the clarification and amendment noticeboard.

    Only autoconfirmed users may file enforcement requests here; requests filed by IPs or accounts less than four days old or with less than 10 edits will be removed. All users are welcome to comment on requests except where doing so would violate an active restriction (such as an extended-confirmed restriction). If you make an enforcement request or comment on a request, your own conduct may be examined as well, and you may be sanctioned for it. Enforcement requests and statements in response to them may not exceed 500 words and 20 diffs, except by permission of a reviewing administrator. (Word Count Tool) Statements must be made in separate sections. Non-compliant contributions may be removed or shortened by administrators. Disruptive contributions such as personal attacks, or groundless or vexatious complaints, may result in blocks or other sanctions.

    To make an enforcement request, click on the link above this box and supply all required information. Incomplete requests may be ignored. Requests reporting diffs older than one week may be declined as stale. To appeal a contentious topic restriction or other enforcement decision, please create a new section and use the template {{Arbitration enforcement appeal}}.

    Appeals and administrator modifications of contentious topics restrictions

    The Arbitration Committee procedures relating to modifications of contentious topic restrictions state the following:

    All contentious topic restrictions (and logged warnings) may be appealed. Only the restricted editor may appeal an editor restriction. Any editor may appeal a page restriction.

    The appeal process has three possible stages. An editor appealing a restriction may:

    1. ask the administrator who first made the contentious topic restrictions (the "enforcing administrator") to reconsider their original decision;
    2. request review at the arbitration enforcement noticeboard ("AE") or at the administrators' noticeboard ("AN"); and
    3. submit a request for amendment ("ARCA"). If the editor is blocked, the appeal may be made by email.

    Appeals submitted at AE or AN must be submitted using the applicable template.

    A rough consensus of administrators at AE or editors at AN may specify a period of up to one year during which no appeals (other than an appeal to ARCA) may be submitted.

    Changing or revoking a contentious topic restriction

    An administrator may only modify or revoke a contentious topic restriction if a formal appeal is successful or if one of the following exceptions applies:

    • The administrator who originally imposed the contentious topic restriction (the "enforcing administrator") affirmatively consents to the change, or is no longer an administrator; or
    • The contentious topic restriction was imposed (or last renewed) more than a year ago and:
      • the restriction was imposed by a single administrator, or
      • the restriction was an indefinite block.

    A formal appeal is successful only if one of the following agrees with revoking or changing the contentious topic restriction:

    • a clear consensus of uninvolved administrators at AE,
    • a clear consensus of uninvolved editors at AN,
    • a majority of the Arbitration Committee, acting through a motion at ARCA.

    Any administrator who revokes or changes a contentious topic restriction out of process (i.e. without the above conditions being met) may, at the discretion of the Arbitration Committee, be desysopped.

    Standard of review
    On community review

    Uninvolved administrators at the arbitration enforcement noticeboard ("AE") and uninvolved editors at the administrators' noticeboard ("AN") should revoke or modify a contentious topic restriction on appeal if:

    1. the action was inconsistent with the contentious topics procedure or applicable policy (i.e. the action was out of process),
    2. the action was not reasonably necessary to prevent damage or disruption when first imposed, or
    3. the action is no longer reasonably necessary to prevent damage or disruption.
    On Arbitration Committee review

    Arbitrators hearing an appeal at a request for amendment ("ARCA") will generally overturn a contentious topic restriction only if:

    1. the action was inconsistent with the contentious topics procedure or applicable policy (i.e. the action was out of process),
    2. the action represents an unreasonable exercise of administrative enforcement discretion, or
    3. compelling circumstances warrant the full Committee's action.
    1. The administrator may indicate consent at any time before, during, or after imposition of the restriction.
    2. This criterion does not apply if the original action was imposed as a result of rough consensus at the arbitration enforcement noticeboard, as there would be no single enforcing administrator.
    Appeals and administrator modifications of non-contentious topics sanctions

    The Arbitration Committee procedures relating to modifications and appeals state:

    Appeals by sanctioned editors

    Appeals may be made only by the editor under sanction and only for a currently active sanction. Requests for modification of page restrictions may be made by any editor. The process has three possible stages (see "Important notes" below). The editor may:

    1. ask the enforcing administrator to reconsider their original decision;
    2. request review at the arbitration enforcement noticeboard ("AE") or at the administrators’ noticeboard ("AN"); and
    3. submit a request for amendment at the amendment requests page ("ARCA"). If the editor is blocked, the appeal may be made by email through Special:EmailUser/Arbitration Committee (or, if email access is revoked, to arbcom-en@wikimedia.org).
    Modifications by administrators

    No administrator may modify or remove a sanction placed by another administrator without:

    1. the explicit prior affirmative consent of the enforcing administrator; or
    2. prior affirmative agreement for the modification at (a) AE or (b) AN or (c) ARCA (see "Important notes" below).

    Administrators modifying sanctions out of process may at the discretion of the committee be desysopped.

    Nothing in this section prevents an administrator from replacing an existing sanction issued by another administrator with a new sanction if fresh misconduct has taken place after the existing sanction was applied.

    Administrators are free to modify sanctions placed by former administrators – that is, editors who do not have the administrator permission enabled (due to a temporary or permanent relinquishment or desysop) – without regard to the requirements of this section. If an administrator modifies a sanction placed by a former administrator, the administrator who made the modification becomes the "enforcing administrator". If a former administrator regains the tools, the provisions of this section again apply to their unmodified enforcement actions.

    Important notes:

    1. For a request to succeed, either
    (i) the clear and substantial consensus of (a) uninvolved administrators at AE or (b) uninvolved editors at AN or
    (ii) a passing motion of arbitrators at ARCA
    is required. If consensus at AE or AN is unclear, the status quo prevails.
    2. While asking the enforcing administrator and seeking reviews at AN or AE are not mandatory prior to seeking a decision from the committee, once the committee has reviewed a request, further substantive review at any forum is barred. The sole exception is editors under an active sanction who may still request an easing or removal of the sanction on the grounds that said sanction is no longer needed, but such requests may only be made once every six months, or whatever longer period the committee may specify.
    3. These provisions apply only to contentious topic restrictions placed by administrators and to blocks placed by administrators to enforce arbitration case decisions. They do not apply to sanctions directly authorized by the committee, and enacted either by arbitrators or by arbitration clerks, or to special functionary blocks of whatever nature.
    4. All actions designated as arbitration enforcement actions, including those alleged to be out of process or against existing policy, must first be appealed following arbitration enforcement procedures to establish if such enforcement is inappropriate before the action may be reversed or formally discussed at another venue.
    Information for administrators processing requests

    Thank you for participating in this area. AE works best if there are a variety of admins bringing their expertise to each case. There is no expectation to comment on every case, and the Arbitration Committee (ArbCom) thanks all admins for whatever time they can give.

    A couple of reminders:

    • Before commenting, please familiarise yourself with the referenced ArbCom case. Please also read all the evidence (including diffs) presented in the AE request.
    • When a request widens to include editors beyond the initial request, these editors must be notified and the notifications recorded in the same way as for the initial editor against whom sanctions were requested. Where some part of the outcome is clear, a partial close may be implemented and noted as "Result concerning X".
    • Enforcement measures in arbitration cases should be construed liberally to protect Misplaced Pages and keep it running efficiently. Some of the behaviour described in an enforcement request might not be restricted by ArbCom. However, it may violate other Misplaced Pages policies and guidelines; you may use administrative discretion to resolve it.
    • More than one side in a dispute may have ArbCom conduct rulings applicable to them. Please ensure these are investigated.

    Closing a thread:

    • Once an issue is resolved, enclose it between {{hat}} and {{hab}} tags. A bot should archive it in 7 days.
    • Please consider referring the case to ARCA if the outcome is a recommendation to do so or the issue regards administrator conduct.
    • You can use the templates {{uw-aeblock}} (for blocks) or {{AE sanction}} (for other contentious topic restrictions) to give notice of sanctions on user talk pages.
    • Please log sanctions in the Arbitration enforcement log.

    Thanks again for helping. If you have any questions, please post on the talk page.

    Arbitration enforcement archives
    1234567891011121314151617181920
    2122232425262728293031323334353637383940
    4142434445464748495051525354555657585960
    6162636465666768697071727374757677787980
    81828384858687888990919293949596979899100
    101102103104105106107108109110111112113114115116117118119120
    121122123124125126127128129130131132133134135136137138139140
    141142143144145146147148149150151152153154155156157158159160
    161162163164165166167168169170171172173174175176177178179180
    181182183184185186187188189190191192193194195196197198199200
    201202203204205206207208209210211212213214215216217218219220
    221222223224225226227228229230231232233234235236237238239240
    241242243244245246247248249250251252253254255256257258259260
    261262263264265266267268269270271272273274275276277278279280
    281282283284285286287288289290291292293294295296297298299300
    301302303304305306307308309310311312313314315316317318319320
    321322323324325326327328329330331332333334335336337338339340
    341342343344345346

    Ithinkicahn

    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 Ithinkicahn

    User who is submitting this request for enforcement
    EtienneDolet (talk · contribs · deleted contribs · logs · filter log · block user · block log) 03:05, 18 September 2014 (UTC)
    User against whom enforcement is requested
    Ithinkicahn (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:AA2
    Diffs of edits that violate this sanction or remedy, and an explanation how these edits violate it
    • The user engages in a relentless effort to remove any mention of the Armenian Genocide in Misplaced Pages. It's a classic case of WP:IDONTLIKEIT. The user's edit-summaries are almost always misleading. They're often entirely irrelevant to what the user's edit actually entails (i.e. 14 August , March 12, and 31 July edits). It's impossible to detect when and where the user has deleted references of the Armenian Genocide. Therefore, all edits must be examined. These are the only ones I happened to come across:
    1. 15 September
    2. 26 August
    3. 20 August
    4. 18 August
    5. 16 August
    6. 15 August
    7. 14 August
    8. 31 July
    9. 29 July
    10. 15 July
    11. 24 May
    12. 21 May
    13. 12 March
    14. 2 March
    15. 2 March
    16. 22 February
    • The user also assumes an overt WP:BADFAITH towards his "opponents". He has openly exclaimed, even after I told him to stop with the badfaith assumptions, that "I have reason to assume bad faith on your part because of my experience with you in the past" (29 July). In an article where I have made only six constructive and harmless edits (), the user kept hurling accusations at me by calling me a POV pusher and accused me of historical revisionism (here and here). The user continued doing this even after I kindly told him to stop. Apparently, he was not interested in adhering to basic Misplaced Pages policy either (). Even with third-party users stating that the article was NPOV and reliably sourced (), Ithinkicahn continued unilaterally placing the POV tag and had edit-warred to get his way ().
    If discretionary sanctions are requested, supply evidence that the user is aware of them (see WP:AC/DS#Awareness and alerts)
    • Gave an alert about discretionary sanctions in the area of conflict in the last twelve months, on 23 February 2014
    Additional comments by editor filing complaint

    I've tried to work with the user on countless occasions. In the past, I've granted him a barnstar and was always supportive of his edits in Turkey related articles. However, once the user started editing in Armenian related topics, it turned into an entirely different story. His deletion of massive amounts of information (often times sourced) concerning the Armenian Genocide is highly problematic. Most of his edits regarding the Armenian Genocide are driven by his own personal opinions and fall contrary to the general consensus Misplaced Pages has instilled regarding the subject. Consequently, the deceptive edit-summaries make it necessary to tend and examine each edit. Furthermore, an uncompromising attitude towards those that don't fall into the user's POV makes it almost impossible to work with him. Hence, for the reasons I have mentioned, I suggest that the user be banned from all topics related to Armenia and Turkey.

    Notification of the user against whom enforcement is requested


    Discussion concerning Ithinkicahn

    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 Ithinkicahn

    Statement by (username)

    Result concerning Ithinkicahn

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

    • Editor hasn't edited since September 16, according to contribution. Wouldn't say stale, but revisiting this when editor returns may be the way to go. - Penwhale | 05:57, 23 September 2014 (UTC)

    SeattliteTungsten

    SeattliteTungsten is blocked for 48 hours.  Sandstein  09:12, 24 September 2014 (UTC)
    The following discussion has been closed. Please do not modify it.

    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 SeattliteTungsten

    User who is submitting this request for enforcement
    Zero0000 (talk · contribs · deleted contribs · logs · filter log · block user · block log) 11:10, 23 September 2014 (UTC)
    User against whom enforcement is requested
    SeattliteTungsten (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
    Misplaced Pages:ARBPIA : 1RR violation
    Diffs of edits that violate this sanction or remedy, and an explanation how these edits violate it
    1. 21:18, 22 September 2014 Reverted to reintroduce BBC material deleted in the previous edit. Rewrote it slightly.
    2. 00:47, 23 September 2014 Reverted previous edit.

    Note that SeattliteTungsten called both edits "reverts" in his/her edit summary.

    Diffs of previous relevant sanctions, if any
    1. 16:56, 11 September 2014 Official warning issued by HJ Mitchell on account of Sep 10-11 AN/I case]
    If discretionary sanctions are requested, supply evidence that the user is aware of them (see WP:AC/DS#Awareness and alerts)
    • 12:54, 27 July 2014 Issued with standard ARBPIA notice.
    • Participated in an arbitration request or enforcement procedure about the area of conflict in the last twelve months, on Sep 8-11.
    Additional comments by editor filing complaint

    I didn't want to submit this case, and over a period of 9 hours twice offered to let SeattliteTungsten avoid it by self-reverting. However, he/she just wants to argue so here we are.

    As Penwhale has already pointed out, SeattliteTungsten's understanding of the rule is defective. It is also defective in terms of what a revert is. If reverts can be sanitised by making some changes to the reverted text, then we can happily revert all day long as long as we remember to change the text a little each time. The 1RR rule would become inoperative. In each case, some text had just been deleted in toto and SeattliteTungsten put it back with some changes. The changes don't alter the fact that SeattliteTungsten reinserted ideas and their sources that another editor had just completely removed. In each case, SeattliteTungsten correctly used the word "revert" in his/her edit summary so it is puzzling that he/she now wants to argue they weren't reverts after all. Zero 06:17, 24 September 2014 (UTC)

    Notification of the user against whom enforcement is requested

    Notified Zero 11:13, 23 September 2014 (UTC)


    Discussion concerning SeattliteTungsten

    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 SeattliteTungsten

    The complaintant's contribution to Misplaced Pages is overall worthwhile and positive. However, the current complaint is frivolous and wholly without merit.

    1. The purpose of the 1RR rule is to prevent an "edit war"; there is no edit war here. 0) "Obama is black" 1) "Obama is white" 2) "Obama is black" 3) "Obama is white" 4) "Obama is black": not until #4 is there a violation of 1RR ("edit war") because #0 and #1 are edits and #2 and #3 are permissible first reverts. This required sequence did not occur.
    2. The 1RR rule applies to edits of the same text. 5) "Obama is a black Democrat" 6) "Obama is a white Republican" 7) "Obama is a black Democrat": I expect there is consensus that #7 is not a a 1RR violation. Suppose the same editor instead submitted sequentially, 7A) "Obama is black Republican" and then 7) "Obama is a black Democrat": by the complaintant's erroneous logic, the editor has committed a 1RR violation with two reverts, first the #7A "white" to "black" revert and then the #7 "Republican" to "Democrat" revert. I hope there is equal consensus that it is incorrect to conclude that #7 becomes a 1RR violation only if the intermediate version #7A is uploaded. (Even if the language of 1RR were to literally support this interpretation, in the immortal words of the Florida Supreme Court in Bush v. Gore, it would be "a hypertechnical reliance upon statuatory provisions" and therefore incorrect as a matter of substance.) The complaintant's examples are from different sections and do not have the 0,1,2,3,4 pattern required for a 1RR violation.
    3. The 1RR rule requires reversions to previously existing text. Despite the inaccurate characterization of "revert" in both comments, neither of the two edits was a revert that restored previously existing text.
    4. Both examples are instances of new text that did not previously exist. Indeed, the incorporation of elements based on the prior edits to create new text is the intention of a collaborative process. This distinguishes the changes as edits and not reverts. WP policy explicitly states, "The first and foremost alternative to reverting when you find you disagree with an edit is to find a third version of the text that incorporates at least some of the elements of the prior text and the current text." Both examples cited are third versions of text and, therefore, are not reverts. In the first example, the text about the BBC was substantially reduced to incorporate an element of the prior edit that the text was unnecessary or irrelevent or too long. In the second example, the reference to GPF's position was changed from an indirect reference to a direct quote to address the concern of the prior edit that the statement might be misquoted or otherwise taken out of context.
    5. The first example has eight different changes only one of which is claimed to be a revert (but isn't... see above) while seven of the eight changes are original work.
    6. Re: User:Penwhale's interpretation that *RR refers to edits of the same page not the same text, I do not agree. It lacks context. There is no edit war here. *RR is about preventing ad nauseum back-and-forths reverting the same text to a previous version. Distinct *RRs require an intervening edit by someone else before it is possible to revert a second time. The 3RR policy explicitly clarifies, "A series of consecutive saved revert edits by one user with no intervening edits by another user counts as one revert." This should be clear: multiple reverts are only multiple reverts when there is an intervening re-revert. For the hypertechinical readers: if someone happens to make an intervening minor edit to a completely unrelated section of a page, the wholly unrelated intervening edit to a completely different section does not suddenly create a *RR violation where one did not exist before. Such a claim is absurd. Therefore, the meaning is clearly, "A series of saved revert edits by one user that are unaffected by intervening edits by another user counts as one revert" so even if there are intervening edits, the intervening edits must be edits, i.e., reverts, to the affected text.
    7. Re: User:Penwhale's characterization of BBC as revert, I strongly disagree with this characterization and will explain why this is the case technically, contextually, substantively, and editorially. (I do not like technical reasons and I believe contextual and substantive reasons are more important here. The editorial reason is ironic to the point of being humorous.)
      1. Technically, to "revert" means to return to a previous state. This was not the case here. The BBC example is not an example of being returned to a previous state. The introduced edit was a new state that had not previously existed so it cannot technically be a revert. There were only fourteen words added about the BBC of which five words were either "the", "separation" or "barrier" in an article about the separation barrier. Under the absurd definition that an edit containing any new words (only nine "unique" words were added) that were previously deleted constitutes a revert, by reductio ad absurdum we would have the ridiculous definition of any new edit having the word, "the" is a "partial revert" if any previous edit existed which contained the deleted the word, "the"!
      2. Contextually, I am reiterating that there is no edit war. The context of this edit is the definition of what Misplaced Pages policy encourages editors to do: collaborate by incorprating some of the previous edit into new (third) text. The complaintant is wasting time making frivolous complaints when a review of the edits shows they were in different sections and there was and is no edit war comprised of reversions of the same text.
      3. Substantively, this was actually an example of a properly working collaborative process, the opposite of what is alleged: the "first" text contained 43 words about the BBC. The "second" text contained 0 words. The "third" text was a compromise that was shortened to 14 words. Contrary to the complaintant's misleading description of a non-existent, imaginary edit war, "happily revert all day long as long as we remember to change the text a little each time" the correct and non-misleading description of a collaborative process was "FIRST: 43 words; SECOND: 0 words; THIRD: 14 words" which is the opposite of an edit war and is a good example of (in the present case) two editors with different POVs quickly converging upon a solution. The reality is that the third text (alleged 1RR violation) was a 67% compromise from 43 down to 14 words, yet after immediately receiving a 67% compromise the complaintant alleges an editing violation that is characterized as being uncompromising when the reality of the evidence presented is actually an example of convergence -- the opposite of an edit war. (For the scientifically oriented readers, an "edit war" regarding 43 words comprised of edits that are each 67% compromises has a half-life of about 1 - 2 edits.)
      4. Editorially, the compromise text which is cited as the first example by the complaintant has now been restored by another editor (unknown to me) who has derisively mocked the complaintant's deletion of the BBC as an authoritative source of English language usage. In the end, it is the defendant's proposed compromise text that now seems to be accepted as the editorial consensus on the subject page. The irony should not be lost on neutral reviewers that from an editorial perspective, the case for sanctioning should be against the complaintant: in the extreme for vandalism but at least for bad judgment. In addition to typing one hundred times on the defendant's user page, "I am sorry for wasting other people's time filing a frivilous complaint" the complaintant should be ordered to perform self-flagellation with a wet noodle for having bad editorial judgment.

    The complaint should be summarily dismissed. Because the complaintant was informed (generally) that the cited examples do not constitute a 1RR violation for the above reasons prior to filing the complaint, the complaintant should sanctioned with a symbolic 1-hour block and a request to type, "I am sorry for wasting other people's time filing a frivilous complaint" one hundred times on the defendant's user page as a sanction for wasting time by filing this frivilous complaint. SeattliteTungsten (talk) 00:07, 24 September 2014 (UTC)

    Statement by (username)

    Result concerning SeattliteTungsten

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

    • The BBC-related material is definitely a revert (partial revert, but a revert nonetheless). I am a bit more lenient on the other one, as the citation that SeattliteTungsten provided is a little better, although in spirit it is still reintroducing something that was removed. - Penwhale | 07:28, 24 September 2014 (UTC)
    • The request has merit. Both edits are reverts as described at WP:3RR ("a "revert" means any edit (or administrative action) that reverses the actions of other editors, in whole or in part, whether involving the same or different material") because both reintroduce texts, or parts of text, that a previous edit removed. Because SeattliteTungsten's long response indicates that they misunderstand or refuse to accept the revert restriction, a block is required to enforce it. SeattliteTungsten is blocked for 48 hours.  Sandstein  09:12, 24 September 2014 (UTC)

    Neotarf

    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 Neotarf

    User who is submitting this request for enforcement
    Hell in a Bucket (talk · contribs · deleted contribs · logs · filter log · block user · block log) 10:12, 26 September 2014 (UTC)
    User against whom enforcement is requested
    Neotarf (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
    Misplaced Pages:Arbitration/Requests/Case/Manning naming dispute :

    ]

    Section 4.2 ] violate this sanction or remedy, and an explanation how these edits violate it, even after being shown and asked to desist Neotarf basically told them to get over it or take it to the correct board.


    Additional comments by editor filing complaint

    I apologize in advance if I did not file this correctly and I ask for help to correct it as I have never made an Arb Enforcement request.

    Notification of the user against whom enforcement is requested

    ]


    Discussion concerning Neotarf

    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 Neotarf

    Statement by (username)

    Result concerning Neotarf

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