This is an old revision of this page, as edited by Arcticocean (talk | contribs) at 19:43, 24 May 2009 (→Parishan: Hyperlink fix.). The present address (URL) is a permanent link to this revision, which may differ significantly from the current revision.

• WP:AE

Requests for enforcement

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 WP:AE WP:ARE 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: ask the administrator who first made the contentious topic restrictions (the "enforcing administrator") to reconsider their original decision; request review at the arbitration enforcement noticeboard ("AE") or at the administrators' noticeboard ("AN"); and 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: the action was inconsistent with the contentious topics procedure or applicable policy (i.e. the action was out of process), the action was not reasonably necessary to prevent damage or disruption when first imposed, or 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: the action was inconsistent with the contentious topics procedure or applicable policy (i.e. the action was out of process), the action represents an unreasonable exercise of administrative enforcement discretion, or compelling circumstances warrant the full Committee's action. The administrator may indicate consent at any time before, during, or after imposition of the restriction. 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: ask the enforcing administrator to reconsider their original decision; request review at the arbitration enforcement noticeboard ("AE") or at the administrators’ noticeboard ("AN"); and 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-enwikimedia.org). Modifications by administrators No administrator may modify or remove a sanction placed by another administrator without: the explicit prior affirmative consent of the enforcing administrator; or 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: 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. 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. 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. 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.

Parishan

The following discussion is archived. Please do not modify it. Subsequent comments should be made in a new section. A summary of the conclusions reached follows.

Parishan notified of the Armenia-Azerbaijan 2 discretionary sanctions remedy and issued with advice for editing. AGK 19:37, 24 May 2009 (UTC)

Request concerning Parishan

User requesting enforcement

76.93.86.242 (talk) 19:49, 20 May 2009 (UTC)

User against whom enforcement is requested

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

Arbitration case whose sanctions are to be enforced

Misplaced Pages:Requests for arbitration/Armenia-Azerbaijan 2

Sanction or remedy that has been violated

Misplaced Pages:Requests for arbitration/Armenia-Azerbaijan 2#Edit warring considered harmful

Diffs of edits that violate this sanction or remedy

], , , , , , , , , ,

Explanation how these edits violate the sanction or remedy at issue

A single-purpose account, currently edit warring on number of pages.

Enforcement action requested (block, topic ban or other sanction)

Block or any other sanction at admin's discretion

Additional comments

Notification of the user against whom enforcement is requested

The requesting user is asked to notify the user against whom this request is directed of it, and then to replace this text with a diff of that notification. The request will normally not be processed otherwise.

Discussion concerning Parishan

• Comment. I'm currently evaluating Parishan's contributions to the Armenia (etc.) subject area for concerning edits. If any are found, the discretionary sanctions remedy of Armenia-Azerbaijan 2 would require Parishan to be placed on notice before sanctions could be dispensed; presently, s/he has not been issued a caution (complete with link to the case page), and so the possible outcomes of this complaint are somewhat limited. On a related note, I hold concerns that 76.93.86.242 is vexatiously filing this complaint—Parishan is in disagreement with the IP in a number of articles in this subject area—or, no less worryingly, is baiting Parishan into revert warring. (All aspects of this comment are tentatively made: I have made but a preliminary review of the situation at the time of making it.) AGK 14:35, 22 May 2009 (UTC)

• This is a very bad faith request. Parishan is a long established user, with thousands of contribs since 2006. How could he be described as a single purpose account? Grandmaster 16:27, 22 May 2009 (UTC)

  It follows the pattern of my request (probably because the IP is unfamiliar with them). Anyway, the IP turned very odd with his two insults (, ). brandспойт 16:56, 22 May 2009 (UTC)

Agree with AGK's comments. I'm inclined towards a notification of the existence of the discretionary sanctions, and editing advice about requesting protection or dispute resolution earlier instead of edit warring. PhilKnight (talk) 18:54, 22 May 2009 (UTC)

I think this edit by the IP is clearly a vandalism, WP:POINT violation and a nationalistic attack: , and is actionable per AA2 case. Also, 96.247.54.18 (talk · contribs · WHOIS) appears to be the same person, judging by this edit: I think Parishan in this case was simply reverting vandalism, which he is allowed to do. Grandmaster 19:50, 22 May 2009 (UTC)

I agree the last 4 diffs should be ignored, because the edit being reverted was essentially vandalism. PhilKnight (talk) 19:59, 22 May 2009 (UTC)

I actually think it is about time Parishan be placed under restrictions. Admins have always repeated that he's not under restrictions but that he was indeed edit warring. See the comments made by the administrators following links: , , , , ,

Just because the report was filed by an IP should not change the fact that all other members with this long a history of incivility and edit warring have had restrictions imposed on them ages ago. And Brand's justification does not make sense, most of the reverts of Parishan were directed toward edits supported also by established editors, particularly those about the Iranian monument in the Eurovision concert. And it does not seem that the IP's intentions was to report him, as seen from here. The IP asked what was done against the others, and was suggested to report, and then drafted his report.--Marshal Bagramyan (talk) 20:17, 22 May 2009 (UTC)

The talkpage of the Eurovision contest article explains why those reverts were made. It is not my fault that those "established editors" did not bother to read it or comment on it before getting involved with those edits. Parishan (talk) 05:40, 23 May 2009 (UTC)

I've posted information about the discretionary sanctions, and given advice concerning edit wars on Parishan's talk page. I don't think any further action is required at this stage. PhilKnight (talk) 12:25, 23 May 2009 (UTC)

Result concerning Parishan

This section is to be edited only by the administrator closing this request for arbitration enforcement. Use {{discussion top}} / {{discussion bottom}} to mark it as closed.

PhilKnight (talk · contribs · blocks · protections · deletions · page moves · rights · RfA) has issued Parishan with discretionary sanctions notice and with advice on editing constructively and in a manner that avoids edit warring; further to this, no action need be taken. If any editor observes Parishan violating either the Arbitration decision or Phil's editing advice, they should file a fresh complaint on this noticeboard (citing the fact that Parishan has already been notified of the Armenia-Azerbaijan 2 discretionary sanctions remedy).

AGK 19:37, 24 May 2009 (UTC)

The above discussion is preserved as an archive. Please do not modify it. Subsequent comments should be made in a new section.

Davelong7

The following discussion is archived. Please do not modify it. Subsequent comments should be made in a new section. A summary of the conclusions reached follows.

The account hasn't edited for 2 days (and is probably a throwaway). I'll consider taking action iff it becomes active again. AGK 14:43, 22 May 2009 (UTC)

Attention: This request may be declined without further action if insufficient or unclear information is provided in the "Request" section below.

Request concerning Davelong7

User requesting enforcement

Jehochman 21:35, 20 May 2009 (UTC)

User against whom enforcement is requested

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

Arbitration case whose sanctions are to be enforced

Misplaced Pages:Requests for arbitration/September 11 conspiracy theories

Sanction or remedy that has been violated

Misplaced Pages:Requests for arbitration/September 11 conspiracy theories#Discretionary sanctions

Diffs of edits that violate this sanction or remedy

Explanation how these edits violate the sanction or remedy at issue

Single purpose, COI account. Probably a sock puppet.

Enforcement action requested (block, topic ban or other sanction)

Ban from 9/11 pages, including talk pages.

Additional comments

Notification of the user against whom enforcement is requested

The requesting user is asked to notify the user against whom this request is directed of it, and then to replace this text with a diff of that notification. The request will normally not be processed otherwise.

Discussion concerning Davelong7

Result concerning Davelong7

This section is to be edited only by the administrator closing this request for arbitration enforcement. Use {{discussion top}} / {{discussion bottom}} to mark it as closed.

The account hasn't edited for 2 days, so I'm taking no action for now. If it becomes active again, then I'd be strongly inclined to install a block for inappropriate editing.

AGK 14:42, 22 May 2009 (UTC)

The above discussion is preserved as an archive. Please do not modify it. Subsequent comments should be made in a new section.

Meowy

The following discussion is closed. Please do not modify it. Subsequent comments should be made in a new section.

Request concerning Meowy

User requesting enforcement

brandспойт 17:25, 22 May 2009 (UTC)

User against whom enforcement is requested

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

Arbitration case whose sanctions are to be enforced

Misplaced Pages:Requests for arbitration/Armenia-Azerbaijan 2

Sanction or remedy that has been violated

Courtesy, Provocation

Diffs of edits that violate this sanction or remedy

, ,

Explanation how these edits violate the sanction or remedy at issue

1rv parole violation, misuse of the word 'vandalism'

Enforcement action requested (block, topic ban or other sanction)

At admin's discretion as per AA2 decision

Additional comments

After some calmness Meowy sticked to his pattern again. Filled to avoid delay since Meowy once made one conspiratorial concern on it.

Notification of the user against whom enforcement is requested

Discussion concerning Meowy

I'm inclined towards a notification of the existence of the discretionary sanctions, and editing advice about taking care in the use of the word 'vandalism'. PhilKnight (talk) 18:57, 22 May 2009 (UTC)

Meowy has already been notified, and placed on editing restriction back in 2007, which limited him to 1rv per week on any page. Meowy has repeatedly violated this restriction, the last time on 30 March 2009. Please check the log of blocks here: Grandmaster 19:34, 22 May 2009 (UTC)

Hi Grandmaster, thanks for explaining. For his last block for exceeding 1RR he was blocked for a week, so 2 weeks this time? PhilKnight (talk) 19:55, 22 May 2009 (UTC)

That's up to you to decide, I cannot say anything as an involved party. Grandmaster 19:58, 22 May 2009 (UTC)

It might be wise to reconsider the notion of making blocks. Meowy has been already punished from bad blocks and has often been the target of provocations. Seehere and read the entire section and more recently here. Besides, involved parties are required to discuss their changes and Meowy was actively involved in the discussion, Baku87 came and left this comment, which clearly shows that he had little knowledge of what was being discussed. It's time that the enforcement be fully applied by the initial requirement of leaving a relevant comment for each revert, as it was initially required. Had this happened Elsanturk's gimmicks and his failure to provide any comments would not have ended in Meowy's block, a user who is makes many fruitful contributions. Reverts should only be permitted to users who are actually involved in the talkpage and, speaking from experience, it is very frustrating that a user suddenly pops from out of the blue (like Baku87), makes controversial edits without even the slightest thought of consensus and fails to give any input on the talk page. --Marshal Bagramyan (talk) 22:05, 22 May 2009 (UTC)

Wise, certainly. But some consider it to be wiser to blindly apply a policy. That's easy, no reliability. An ashamed admin of wk:fr, Sardur (talk) 23:25, 22 May 2009 (UTC)

Result concerning Meowy

Blocked for 2 weeks for the violation of the 1RR restriction.  Sandstein  06:18, 23 May 2009 (UTC)