Misplaced Pages

This is an old revision of this page, as edited by Lord Roem (talk | contribs) at 02:44, 10 February 2013 (→Brandmeister: closing). The present address (URL) is a permanent link to this revision, which may differ significantly from the current revision.

• WP:AE
• WP:ARE

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.

Arbitration enforcement action appeal by NestleNW911

Ceco31

Oliveriki

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

Request concerning Oliveriki

User who is submitting this request for enforcement

Grandmaster 21:48, 3 February 2013 (UTC)

User against whom enforcement is requested

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

Sanction or remedy to be enforced

Misplaced Pages:ARBAA2#Standard discretionary sanctions

Diffs of edits that violate this sanction or remedy, and an explanation how these edits violate it

1. February 3, 2013

Diffs of notifications or of prior warnings against the conduct objected to (if required)

There are warnings at talk of this user, but in addition to that I reported him to this board a few months ago, so he is well aware of AA2 sanctions:

Additional comments by editor filing complaint

Some time ago the account of Oliveriki caused major disruption in the article about Nagorno-Karabakh, appearing out of nowhere and reverting it to a months old version by the banned user. I reported him back then, but the diffs were considered stale, and no action was taken: I described in much detail his disruptive behavior in that report. Despite being here for about 2 years, Oliveriki has only made 21 edits to date, large proportion of which are reverts in support of banned accounts. Oliveriki has been absent since April 2012, but yesterday he appeared as usual out of nowhere to rv a contentious AA article, to which he never contributed before: Oliveriki is clearly an SPI, used solely for edit warring. He made almost no useful contributions in 2 years that he has been registered here. I believe it is time to restrict his activity, because appearing time after time after long periods of inactivity just to rv in support of suspicious accounts is not in line with AA arbitration ruling. Grandmaster 21:48, 3 February 2013 (UTC)

I think the fact that Oliveriki turns up after being long dormant only to join another edit war is a sufficient ground for a topic ban. And the accounts he reverts for are extremely suspicious too, as it was mentioned here. I see no reason why Oliveriki should be allowed to edit AA area, to which with one minor exception he makes no useful contributions, and moreover, as others pointed out, he aggravates the existing or starts new edit wars. The only article that he created in two years is not linked by any other article. If we do not stop him now, he will do the same thing next time, like he did before. I think it should be made really clear that the use of SPIs to edit war will not be tolerated in AA area. Also of note that out of 5 accounts that waged the edit war at Nagorno-Karabakh 3 have already been banned (Winterbliss, Dehr, Sprutt), with remaining 2 accounts (Oliveriki and Zimmarod) continuing the same behavior in another article. Grandmaster 20:30, 4 February 2013 (UTC)

While I understand concerns of Sandstein, I would like to show the chain of events which made me file this report. I'm a long time contributor to Shusha, which is why I have it on my watchlist. This article attracts a lot of sockery. Zimmarod (talk · contribs), who was inactive since 14 December 2012, makes an edit to Shusha on 29 January 2013. I'm leaving aside the actual merits of the edit, it is a different issue. When reverted, the edit is restored on 3 February 2013 by Oliveriki (talk · contribs), who was inactive since April 2012. After that the same edit is restored by 517design (talk · contribs), who was also inactive since 14 December 2012 (again) until the same day of 3 January 2013, when 517design made a cosmetic edit to Sergey Lavrov. The the next day 517design reverted Shusha. Prior to that, the last edits by both Zimmarod and 517design were to WP:AE on 14 December 2012, where they both posted in defense of another banned user. Isn't it strange that all 3 accounts that were long inactive returned to life at the same time on the same article? Or that 2 of them posted at AE in support of another user, after which they both vanished? It is probably worth mentioning that all these 3 accounts have a limited number of edits (less than 500 each). Grandmaster 21:53, 5 February 2013 (UTC)

Notification of the user against whom enforcement is requested

Discussion concerning Oliveriki

Statement by Oliveriki

None of my recent or past edits are in any way wrongful or violating anything at all. I do not edit frequently, and that is entirely ok. Grandmaster, on the other hand, is fueling edit war by abusing AE with meaningless filings. It is his second filing against me – the first one was dismissed. I am the author of the Azgapet article, which is a useful contribution. There is nothing objectionable with my recent edit, in which I reverted Brandmeister. I included edit summary, explaining why I did that.

Oliveriki (talk) 19:25, 4 February 2013 (UTC)

Comments by others about the request concerning Oliveriki

Comment by The Devil's Advocae

• Sockpuppet or not, Oliveriki is clearly a tendentious SPA. The account is focused exclusively on the subject of Nagorno-Karabakh and in that focus does nothing but attempt to push a pro-Armenian position in articles by aggravating or sparking edit wars.--The Devil's Advocate _{tlk. cntrb.} 17:28, 4 February 2013 (UTC)

• I don't see why it is true. Zimmarod (talk) 00:38, 5 February 2013 (UTC)

• Roem, the article in question notes that there is some dispute about whether there was a fortress or town there in the past, which would have gone by a different name. What Oliver is inserting with that revert is material that states in the lede that it served as an Armenian fortress as though it were settled history. This is typical tendentious reverting.--The Devil's Advocate _{tlk. cntrb.} 23:24, 4 February 2013 (UTC)

• Brandmeister erased a perfectly referenced passage, and refused to engage on talk pages. Zimmarod (talk) 00:38, 5 February 2013 (UTC)

• How exactly? He was the only one who commented at talk. Grandmaster 17:35, 8 February 2013 (UTC)

• Sandstein, the material being reverted in by Oliveriki as part of an edit war was stating in the lede as fact that Shusha was previously a town and fortress, when the material in the article says there is dispute over whether any town or fortress was present in the area prior to the establishment of Shusha. Stating in the editorial voice in the lede that Shusha was previously an Armenian town and fortress is tendentious. Given the minimal activity of Oliveriki, I think not so much as warning Oliver seems misguided. Accounts that apparently only show up to pick a fight or join one should not be ignored. The action last year was incredibly disruptive and this recent edits was similarly disruptive.--The Devil's Advocate _{tlk. cntrb.} 22:10, 5 February 2013 (UTC)

Comment by Golbez

• I too have thought that Oliveriki and Zimmarod could be socks, and thought it was extremely curious that both of them made their first edits in months (many months, in Oliveriki's case) on the same edit on the article at the same time. That said, since we aren't talking in terms of an SPI, this is an AE request, I would agree that the one-revert restriction is proper, but not sure how useful it would be so long as the others are still around. --Golbez (talk) 19:58, 4 February 2013 (UTC)

• Please mind WP:AGF. I keep hearing this from you for many times already without any evidence and despite the multiple SPI tests. Zimmarod (talk) 00:38, 5 February 2013 (UTC)

• Please mind WP:DTTR. --Golbez (talk) 15:10, 6 February 2013 (UTC)

• I think one revert restriction will not help, Oliveriki usually turns up to make 1 rv, after which the edit war is picked up by other accounts. This is their way of evading 1 rv per day restriction that is imposed on many AA articles. He should be either topic banned, or not allowed to rv at all. If he needs to rv, he can notify others about the edit that needs to be undone. Grandmaster 20:38, 4 February 2013 (UTC)

Comment by Zimmarod concerning Oliveriki

I am commenting because User:Grandmaster and his pals mentioned me here. But I need to note that this is yet another foul AE request by Grandmaster, an attempt – the second such attempt in fact, here was the first - to ban Oliveriki under fake claims of misconduct. Grandmaster is a serial violator of WP:AGF, also because he accuses me here to have a connection with someone else with absolutely NO evidence at all, calling me and others "suspicious accounts" in this and all other AE requests. Grandmaster is clearly covering for User:Brandmeister, with whom he has for a long time tried to WP:OWN the Nagorno-Karabakh topic, and who has been engaged in an edit war in the article Shusha. Here is when the same well-referenced passage was erased by Brandmeister for the first time , then the same passage was removed by Brandmeister for the second time , and here is the third time when the same passage was erased by Brandmeister without any attempt to explain the multiple removals on talk pages. Grandmaster perhaps is also in a violation of WP:BATTLEGROUND because he treats very normal and reasonable edits of the same editor Oliveriki as an excuse to file repeated AE requests, accusing Oliveriki in just about everything imaginable without evidence. Zimmarod (talk) 00:33, 5 February 2013 (UTC)

• Please also note the canvassing by User:Grandmaster per WP:CANVASS, directing User:Golbez to comment on this topic: and . Zimmarod (talk) 00:52, 5 February 2013 (UTC)

• It's almost as if I had an interest in you, seeing as how I've accused you of being a sockpuppet in the past and I reverted your most recent edit. I'm an interested party; telling me about this is not "canvassing". --Golbez (talk) 15:11, 6 February 2013 (UTC)

Result concerning Oliveriki

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

• I think this should be closed with no action, but I'm open to the idea of a topic-ban if others feel Oliveriki is pushing a specific agenda. The sole mainspace edit he's made this year, which is also the edit at issue here, is the addition of content with a cited source. When it was reverted by another, he didn't add it back in or engage in any other behavior that would bring up red flags. Personally, I'd need something more serious to feel comfortable imposing a block. -- Lord Roem ~ (talk) 19:42, 4 February 2013 (UTC)

• Please stop the threaded discussion; keep posts in a section with your own statement. --Lord Roem ~ (talk) 00:58, 5 February 2013 (UTC)

• Because the report contains no diff of a warning that meets the formal requirements of WP:AC/DS#Warnings, administrators here can do nothing but issue such a warning. But because the edit reported here does not appear problematic to me, I don't see any grounds on which to issue a warning. The mere fact that it is a revert is not as such a problem, and the revert is not on its face non-neutral or otherwise unconstructive. I would instead examine whether the repeated filing of unactionable AE requests by Grandmaster against Oliveriki is grounds for restrictions against Grandmaster.  Sandstein  08:39, 5 February 2013 (UTC)

Brandmeister

SMcCandlish

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

Request concerning SMcCandlish

User who is submitting this request for enforcement

SarekOfVulcan (talk) 17:00, 8 February 2013 (UTC)

User against whom enforcement is requested

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

Sanction or remedy to be enforced

Misplaced Pages:Arbitration/Requests/Case/Article titles and capitalisation#All parties reminded and Misplaced Pages:Arbitration/Requests/Case/Article titles and capitalisation#Discretionary sanctions

Diffs of edits that violate this sanction or remedy, and an explanation how these edits violate it

1. 2013-02-08 Violates ARBATC's instruction not to personalize disputes

Diffs of notifications or of prior warnings against the conduct objected to (if required)

1. Warned on 2013-02-01 by Sandstein (talk · contribs)

Additional comments by editor filing complaint

Two of the violations in this diff include is seeking administrative power for the specific intent (perhaps among other more legitimate intents) of shutting up opponents of his/her MOS views and further fantasizes that MOS should have thought-policing, neither of which appears to be supported by the candidate's statements.

Notification of the user against whom enforcement is requested

Done.

Discussion concerning SMcCandlish

Statement by SMcCandlish

1.  I have a right like any other editor in good standing to raise problems with a candidate's statements at, and behavior patterns relevant to, their RFA. The fact that in this case those of this candidate – as evidenced by not one but two anti-MOS introductory rants by the candidate! – involve MOS in disturbing ways does not magically mean that WP:ARBATC can be used to censor RFA, for me or anyone else. Such an idea is illogical, since RfAs are named on a per-candidate basis and entirely consist of reviews of the personal behavior of candidates and their espoused positions on Misplaced Pages editing and administration issues, and thus are already personalized, by definition. Thus raising issues about the behavior and statements of the candidate is not "personalizing" a style (or other) issue even as broadly construed under WP:ARBATC, the case that SarekOfVulcan is making.

If SarekOfVulcan believes I am misinterpreting the RFA candidate's arguably extremist views expressed at the RFA with regard to WP:MOS (e.g. that WP:CONSENSUS and WP:BRD be "suspended" with regard to MOS and that control over MOS be turned over to lone censors, some kind of super-'crat or something!), and his/her history of tooth-gnashy debate about MOS, from talk page to talk page, then that is something SarekOfVulcan can seek clarification about at the RFA page. It's not an AE matter. I am also not the first or only RFA respondent to note that the anti-MOS (and anti-MOS-editors, bad-faith-assuming) rants by the candidate are alarming.

2.  Sandstein's warning is subject to an open dispute, yet this new AE by SarekOfVulcan depends on it . At WT:AE#Request for input by ArbCom members concerning an AE action (and at User talk:SMcCandlish and User talk:Sandstein before Sandstein opened the matter at WT:AE), I am disputing the validity of Sandstein's warning, which SarekOfVulcan is here relying on, because I have shown that it is based on false accusations and Sandstein himself admitting he was not aware of the background of the issue. Two other productive editors, Neotarf and Noetica. have already quit Misplaced Pages over the same Sandstein warning/threats they received for the same discussion. Sandstein refuses to retract the warnings (and even seems to suggest they "cannot" be retracted, for unclear reasons). I have to note that at WT:AE and at both relevant user talk pages, various editors, including other admins, have raised serious concerns about the propriety of Sandstein's "warning" actions and subsequent refusal to even reconsider (and they have done so on more than one basis).

Sandstein himself started the thread at WT:AE in an effort to get Arb input to help resolve the issue (unsuccessfully so far, though various other admins and non-admins have responded), and notes that there's a procedural question of how one can even appeal such a warning and the basis for it at all. (This is a nontrivial issue, because a discretionary-sanctions warning under WP:ARBATC is not a normal warning one might discuss at WP:AN, but a special ARBCOM one that is very akin to an out-of-process topic ban). As none of this is resolved yet, the basis for SarekOfVulcan's new AE request is subject to multiple levels of dispute already, and it does nothing but muddy the water. It appears at this juncture that I will have to at least formally request clarification on the scope, applicability and intent of ARBATC and its overbroad and vague discretionary sanctions, and possibly also request an RFARB separately to get the false warning expunged. Or I may simply quit Misplaced Pages, too, because I am tiring rapidly of being followed around from page to page by SarekOfVulcan and a couple of others trying to find any excuse to abuse ARBATC to punitively block me.

3.  ARBATC sanctions are being misused unintentionally if not consciously abused, by two very involved admins, to get around a consensus against their proposal for censorious, punitive MOS-related administrative action. Sandstein previously sought to topic-ban Noetica in a related discussion, along with anyone else (insert SMcCandlish, Neotarf, whoever, on the basis of whatever whim) who raised related issues, but did not gain consensus to do so, being supported by essentially no one but SarekOfVulcan. This was in the "Mexican–American War" dashes-and-hyphens dispute. Post-ARBATC anti-dash tendentiousness by Apteva was what led Noetica to successfully have Apteva topic-banned at WP:AN. After that ban, Apteva filed a retaliatory, frivolous AE request against Noetica. When myself and others attempted to point out that Apteva was simply abusing AE as part of his established pattern of forum-shopping and disruption, Sandstein, with no knowledge of what had been going on, declared that we were personalizing a MOS dispute and issued bogus warnings for making "broad and unfounded allegations" and using AE as some kind of forum for random venting, when in fact our statements with regard to the posts of Apteva and other parties were narrow, relevant, and proven true at WP:AN already, where Apteva was then blocked for sockpuppetry, too.

This baseless warning by Sandstein and its near-immediate abuse by SarekOfVulcan here to shut me up or hound me off the system right on the heels of Noetica and Neotarf, shows that ARBATC is simply being programmatically misapplied to thwart consensus against ham-fisted efforts to censor anything related to MOS disputes. This is a case of two admins deciding that a style matter should be perpetually off limits simply because they think it is "lame" (Sandstein's word), and trying to use ARBATC to accomplish what consensus already told them they can't have (shut-up-or-else punitive bans). That makes it both a content dispute and a dispute over administrative authority, not an editor wrongly claiming an admin is "involved" because they've argued about something with the editor.

4.  The illegitimate admin goal of personally censoring and character-assassinating me has escalated to the level of blatant harassment already. As noted toward the bottom of WT:AE and at User talk:Sandstein, I believe I am being subjected to a clear tag-team WP:HARASSMENT effort (particularly WP:WIKIHOUNDING), and this frivolous, "how dare you be critical at RFA" AE request by one of the admins directly involved in the ongoing dispute the resolution of which is still under discussion at WT:AE, is further evidence of this. Again, I am not the only one who has raised concerns about this at WT:AE and User_talk:Sandstein.

5.  This AE request is frivolous and vexatious, is based on "facts" that are disputed, and interferes with normal operation of RFA. It also amounts to a drawn-out case of WP:FORUMSHOPPING. It is asking the toher parent for new permission for Sandstein and SarekOfVulcan already-rejected proposal to issue blanket topic-bans to just forcibly shut up everyone in the dash vs. hyphen debate. It's a style dispute that later resolved itself in a poll that ArbCom endorsed. Yet here we are, with Sandstein and SarekOfVulcan (effectively even if not intentionally) tag-teaming to censor me, Noetica, et al., into oblivion for non-disruptive posts only tangentially related to the same discussion. What part of "no, you don't get to censor everyone because you don't think MOS discussions are important" didn't they understand? Sandstein's recent, bogus warnings to us were issued due to him severely misunderstanding our responses to Apteva's filing a vindictive AE request against Noetica. But SarekOfVulcan, perhaps because I supported Noetica's criticisms of Sarek's involvement in the discussion, is taking Sandstein's warnings as blanket license to follow me around and make WP:WIKILAWYERish trouble, like supposing that I can't be critical in a RFA if MOS issues are mentioned. I quite understandably, in my view, feel like a witness who has himself been falsely accused of being the criminal and threatened with prosecution, after testifying against someone who was actually found guilty already in part due to my good faith testimony. I defies reason and strongly suggests a personal, emotional motivation. The continuing campaign to personalize everything to do with MOS (even tangentially, like it being among the background concerns about someone's RFA) as an excuse to abuse process, like special warnings and AE filings, to go after me personally, is the real WP:ARBATC violation that's going on. Good editors are leaving Misplaced Pages in droves, and this sort or browbeating misuse of admin authority is one of the main reasons why.

— SMcCandlish  Talk⇒ ɖכþ Contrib. 20:05, 8 February 2013 (UTC)

SMcCandlish's response to Cailil's initial "Result" post

SarekOfVulcan added me to the party list at ARBATC, but I did not post a statement there and no findings of fact or remedies addressed me, so I was not a party in any relevant sense. This is important as background to begin with, but note that Sarek said "I didn't dive far enough into to figure out who was 'the problem' ... Remember, 'involved party' does not mean 'potential recipient of sanctions'..." So even Sarek knows that the basis for sanctioning me in particular is shaky to begin with. But the problems with this AE filing go far beyond this. The two pages at issue here (WP:AE itself, a post of mine to which Sandstein issued a confused warning about that was not cognizant of any of the salient facts that led to my post, and badly misconstrued it; and the RFA now at issue), do not have the ARBATC warnings Cailil refers to on them.

Being process pages at which MOS issues can legitimately be discussed, including with particular reference to specific parties, no one would reasonably assume that ARBATC could possibly apply to them, pretty much by definition. They are pages in which the discussion are automatically "personalized" because they are by their nature about specific parties. (WP:CIVIL and WP:NPA of course still apply, but WP:ARBATC logically cannot.) I reiterate what I've said at my talk, Sandstein's talk and WT:AE: Sandstein's warning/threat in relation to my participation on WP:AE is blatantly procedurally invalid and necessarily void, and should be explicitly vacated as such, but whatever process there may be to do that. Partly resultantly and partly severably, SarekOfVulcan's new AE request is also procedurally invalid under ARBATC, both as an extension of Sandstein's warning, and individually as an attempt to enforce ARBATC beyond its scope. Sorry to sound kinda legalistic, but I didn't make ArbCom operate this way.

Now, if I go to WT:AT or WT:MOS and call someone a poopie-head because I don't like their style ideas, then I expect to be AE'd legitimately. Until then, I have other stuff to do that's actually useful. PS: The idea Cailil raises, that Sandstein's warning could be moot due to my "being a party", supposedly, to ARBATC originally would actually resolve half of my WT:AE dispute with Sandstein on a technicality, but the false accusation issue would remain and I'm not going to let that go just because some admin buddies of his follow me around and harass me. — SMcCandlish  Talk⇒ ɖכþ Contrib. 20:33, 8 February 2013 (UTC)

PS: I am not making ad hominem comments about SarekOfVulcan (and that was my talk page, not his) or Sandstein. Ad hominem is a logic fallacy, in which irrelevant facts or allegations about a debate opponent are raised in an effort to distract attention away from the actual point and from flaws in one's own argument. In this case, I am making an actual claim, under WP:POLICY, that WP:HARASSMENT policy is being violated with regard to me. I had already elaborated on this claim at WT:AE before this vexatious AE was opened by Sarek. If it doesn't stop, I will be seeking a remedy at WP:RFARB. I have also specifically stated and defended beyond any reasonable doubt that Sandstein made false accusations against me in the course of issuing and defending his warning; this previous discussion at WT:AE and our user talk pages is pertinent and summarizing that or referring to it also does not constitute any form of ad hominem attack. — SMcCandlish  Talk⇒ ɖכþ Contrib. 20:43, 8 February 2013 (UTC)

PPS: Yes, I understand that I have been notified of ARBATC's outcome, that I have been warned whether legitimately or otherwise. It is not my intent to unduly "personalize" anything here, but I cannot be expected to respond to entirely personalized accusations with entirely impersonal responses that pretend that specific parties are not involved. That's not ARBATC's intent, and AE cannot actually operate that way. If you (Cailil or anyone) have concerns about any particular statement I've made, I'll be happy to address them. — SMcCandlish  Talk⇒ ɖכþ Contrib. 21:01, 8 February 2013 (UTC)

SMcCandlish's statement in response to the two particular accusations by SarekOfVulcan

Sarek writes "Two of the violations in this diff include is seeking administrative power for the specific intent (perhaps among other more legitimate intents) of shutting up opponents of his/her MOS views and further fantasizes that MOS should have thought-policing, neither of which appears to be supported by the candidate's statements."

1. Candidate issued not just one but two rants in his RFA Q&A section indicating an extreme level of dissatisfaction with MOS, others editors of it whom he/she feels need to be administratively sanctioned under ARBATC, and an intent to see to it that WP:CONSENSUS and WP:BRD be "suspended" with regard to MOS.
2. Candidate also outlined an imagined system whereby a special admin, whom he/she calls a "moderator", would have essentially unlimited authority to act as a benevolent dictator on MOS matters.

So, um, I kinda have to stick to my criticism of this admin candidate's candidacy, exactly as I wrote it. Even if I were wrong about either of these points, the only two SarekOfVulcan makes, neither of them are WP:ARBATC violations, but normal criticism at a RfA. They also do not violate WP:NPA or any other policy. Being civil does not require being sweet or pretending to be happy about what someone is proposing. — SMcCandlish  Talk⇒ ɖכþ Contrib. 20:55, 8 February 2013 (UTC)

In response to your later comment ("insane shit"? seriously?), I did not bring a MOS-related dispute to RFA and "personalize" it. I don't have any extant MOS or AT dispute with that editor. I did not need to bother digging up anything specific to quote from MOS talk that the candidate may have said, since addressing the alarming proposals the candidate made at the top of their own RFA, and noting their own admission of having been an MOS editwarrior, was enough to strongly oppose. — SMcCandlish  Talk⇒ ɖכþ Contrib. 23:59, 8 February 2013 (UTC)

SMcCandlish's response to NE Ent

Your second point is interesting, and echoes something Cailil said. I reiterate that it would moot the procedural grounds for my dispute with Sandstein , but not resolve the false accusation issue, nor make SarekOfVulcan's claim that ARBATC prevents an editor from raising "personal" concerns at RFA if they happen to mention MOS, since everything about RFA is personal by definition and ARBATC is intended to stop personalization of disputes about style and article title issues, which that wasn't anyway. Your third point isn't even one I would go so far as to make; I do consider the "big yellow box" up top of WT:MOS, WT:AT, etc. to be sufficient at those talk pages, but such templated warnings would not be appropriate or applicable to WP:AE or WP:RFC. — SMcCandlish  Talk⇒ ɖכþ Contrib. 21:56, 8 February 2013 (UTC)

SMcCandlish's response to Bagumba

Of course a response to your editing behavior at RFA (namely, following up someone else's comments with a declaration that you refuse to read them and a non sequitur statement that your concerns are satisfied, without addressing whether the concerns raised by the other editor were satisfied) is "personal" to you, since it's about your behavior. This has nothing to do with anything under discussion here. It is certainly unrelated to WP:ARBATC, which is about ah hominem personalization of style and article title disputes. Basically, I'm seeing now a pattern of misinterpretation of "personalize" and of what ARBATC covers, not just in Bagumba's post here, but more generally. Anyone who has not actually read the findings and remedies at ARBATC should do so before commenting here, or you're just muddying the water. — SMcCandlish  Talk⇒ ɖכþ Contrib. 22:04, 8 February 2013 (UTC)

PS: I feel that blatantly labeling a candidate "incompetent", as you recommend, would be far more of an incivility or personal attack than suggesting that their double-barreled ranting about MOS and proposals for out-of-process dictatorial control over it indicates a desire to gain admin authority for purposes we don't give admin authority for. I did not need to cite anything that the candidate said at MOS, because the candidate already indicated regretting having said them, and meanwhile their own introductory Q&A material was far more damning. Others had alread quote MOS and one of its subpages and the user's own talk archives for MOS-related issues, anyway, so my doing so would have been redundant. — SMcCandlish  Talk⇒ ɖכþ Contrib. 22:11, 8 February 2013 (UTC)

SMcCandlish's response to The Devil's Advocate and Cailil and Lord Roem

You've all suggested I'm overreacting and/or being too wordy. I don't feel that I was truly overreacting, and the exact history of the dispute is somewhat complicated.; this has been very stressful – I feel like an elk that's been hunted by a pack of wolves, honestly. But, I'm actually getting some small noteworthy amount of traction at WP:ARCA (thanks to Sandstein for being big enough to start the procedure), and feel that resolution may actually be possible instead of me simply leaving Misplaced Pages. My sense of emergency has receded, but I don't think it was wrong of me to be alarmed, nor to defend myself in detail. That said, I no longer need to do so, and will thus zip it, unless some new assault begins that I have to respond to differently. At an rate, I have a busy day offline tomorrow, so if a response is needed out of me, please be patient. Sorry if the above has been a "wall of text" for anyone; there was a lot to cover, and it seemed safer to cover it than not. — SMcCandlish  Talk⇒ ɖכþ Contrib. 03:49, 9 February 2013 (UTC)

Comments by others about the request concerning SMcCandlish

Statement by ErikHaugen

This request is pretty far out in the weeds. ARBATC says DS are to be applied at "all pages related to the English Misplaced Pages Manual of Style and article titles policy, broadly construed." I think it's difficult to stretch this to RFA, but even if one does, the entire point of RFA is in some sense to discuss the editor, ie "personalize". Discussing the editor's conduct and/or intentions at WT:MOS or AT can not be considered in itself to be a violation of ARBATC. This obviously has to be done in as civil a manner as possible, so it might be worth examining SMC's comments there to see if they rise above acceptable standards per WP:NPA/etc. I think they do not.

Additionally, whether or not the statements quoted by the filer here are supported by the candidate's statements doesn't seem relevant. Did SMC misunderstand the candidate? If so does that mean we block him for misunderstanding someone? That would be strange.

@Calil—Regarding SMC's comments that you quoted (on SMC's talk page): that was in the context of responding to an accusation, and on a user talk page. This is not personalizing a MOS dispute. Please; this kind of clampdown on how people can defend themselves has gone too far. ErikHaugen (talk | contribs) 20:31, 8 February 2013 (UTC)

@SarekOfVulcan—Yes, I noticed your quotes and in my statement I commented on your analysis of them. I'm not sure what you're trying to tell me. ErikHaugen (talk | contribs) 20:58, 8 February 2013 (UTC)

SoV, I still don't understand what point you're trying to make with these quotes. Are you trying to imply that SMC should be blocked for misreading a comment? Do you believe SMC is deliberately fabricating things that another editor said so that he can shoot that editor down for some unknown reason? ErikHaugen (talk | contribs) 22:26, 8 February 2013 (UTC)

Statement by NE Ent

• This filing is ridiculous. If an Rfa candidate brings up MOS, an editor is entitled to express a related opinion related to MOS.
• The purpose of a DS warning is to ensure the editor is aware of DS and therefore can be pretty much be placed by any admin at any time. (Whether a non-admin can I think is an open question.) Therefore the claim that Sandstein's warning is "invalid" is as ridiculous as this filing.
• @Cailil: no, in general, the big yellow box is not sufficient in general because we have a not bureaucracy / bold policy around here, and editors can edit articles without reading the talk page. But clearly is this case it's moot point as SMC is aware of the sanctions. NE Ent 20:27, 8 February 2013 (UTC)

Further comments by SarekOfVulcan

@ErikHaugen: if SMcCandlish had said "I have grave questions about the candidate after reading his proposed 'solution' to MOS problems", this wouldn't have been an issue. His comments I quote above are what make this into an ARBATC vio, in my view. --SarekOfVulcan (talk) 20:52, 8 February 2013 (UTC)

Erik, I'm not sure how any reasonable "misunderstanding" can turn Dirtlawyer's comments into what SMcCandlish claimed. --SarekOfVulcan (talk) 22:13, 8 February 2013 (UTC)

Both Bagumba and I have specifically called out SMC's claim that Dirtlawyer is seeking adminship for the (possibly) sole purpose of having power in MOS disputes. Why do you keep insisting this is a "misreading"? --SarekOfVulcan (talk) 22:30, 8 February 2013 (UTC)

@SMcCandlish: SarekOfVulcan's claim that ARBATC prevents an editor from raising "personal" concerns at RFA -- never said any such thing. I just indicated that ARBATC prevents you from making insane shit up about people with whom you're having disputes about the MOS.--SarekOfVulcan (talk) 22:18, 8 February 2013 (UTC)

Speaking of making stuff up.... --SarekOfVulcan (talk) 02:18, 9 February 2013 (UTC)

Statement by Bagumba

I am not involved with MOS, but interacted with SMcCandlish at the RfA in question before this AE request was opened. I had called SMC out for his charge that the RFA candidate "is seeking administrative power for the specific intent (perhaps among other more legitimate intents) of shutting up opponents of his/her MOS views, in ways that thwart WP:CONSENSUS policy."

This is quite different from your usual "I oppose because he appears incompetent based on A, B, and C incidents at MOS". SMC followed in kind with a response to me, which appears personalized—but perhaps I'm too involved too judge.—Bagumba (talk) 21:30, 8 February 2013 (UTC)

Statement by Hans Adler

This report is in such incredibly poor taste that it absolutely needs to become a boomerang. Cailil, you are way out of line. There is nothing inappropriate in , and if you think otherwise you should look for something else to do that is more in keeping with your qualifications. A certain degree of sense, common and otherwise, is expected of admins using their privileges. This applies to you as well as to SoV and to Sandstein. Apart from the obvious ethical concerns, I don't think it is wise to play power games while Arbcom is looking at a matter. Hans Adler 22:35, 8 February 2013 (UTC)

Statement by The Devil's Advocate

I believe the tone of Sarek's notification was a bit provocative myself so SMc's response is somewhat understandable. Honestly, I feel SMc is going overboard at this point, but I think it is largely because of the fallout from the recent AE case against Noetica and the rather frivolous warnings given out at the end. Overall, Sarek's conduct in this topic area has been a big part of the problem as of late by my estimation. Review the recent AE cases in this topic area and you will see what I mean.--The Devil's Advocate _{tlk. cntrb.} 23:30, 8 February 2013 (UTC)

Result concerning SMcCandlish

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

• I'd like to hear SMcCandlish's response before commenting further. --Lord Roem ~ (talk) 17:17, 8 February 2013 (UTC)

• I have a few thoughts after reading through the massive wall of text that's developed in this section over the past few hours. First, I don't think the RFA comment is actionable under the discretionary sanctions authorized by ARBATC. From a skim of the final decision, that was not at all contemplated as part of the scope of their remedies. Do I like the attitude/civility in the remark? No. But I think it's on the line to the extent that I wouldn't be comfortable imposing any sanction for it. Second, even if this remark was made in a discussion on the MOS pages (as some other links have shown) I don't feel they're enough to impose a block. It's a heated area, that can't be denied, but imposing sanctions for any and all signs of frustration would not help anyone. All parties need to calm down, but that's not something I feel we can force in any manner at this time. Third, and this isn't really related to the merits of this dispute, but I would advise SMcCandlish to shrink down his responses, if only because it's getting a bit too much. --Lord Roem ~ (talk) 01:57, 9 February 2013 (UTC)

• Like Lord Roem I'd like to hear SMcCandlish's response. However WRT the diff presented by Sarek, whether this is acceptable conduct at RFA or whether it crosses the line into evidence of a battleground mentality is the question. It's also worth noting that the RFA candidate did raise the issue of their experiences on the MOS so SMC was not just jumping in with this out of the blue.
  Also as a technical note whether SMC was warned or not is not especially relevant, they were a party to WP:ARBATC and would need no warning before being sanctioned if it comes to that. Furthermore contributors to pages with a big yellow box alerting all to active sanctions have had sufficient constructive warning of sanctions anyway--Cailil 18:47, 8 February 2013 (UTC)

  Still going through this but I'd advise you SMC to stop making personalized or ad hominem comments about anyone anywhere, for your own sake. Your comments at SoV's your talk page are not helpful to your case and your response above contains significant counter-productive personal commentary. Commenting about a candidate at RFA might be acceptable, but using other fora to cast aspersions about others is not. Also FYI, as above enforcement of the RFAR against named parties to the original Request for Arbitration do not rely on them having further warnings of discretionary sanctions. You've had sufficient warning by being involved in that RFAR and you were notified of its outcome--Cailil 20:22, 8 February 2013 (UTC)

  I'm in agreement with Lord Roem, I don't think we can issue a sanction for this remark. However, I do disagree that the RFAR does not cover areas beyond the specific MOS pages, if a dispute about them is brought elsewhere, (but that makes no difference in this particular instance). As I see it since the RFA candidate raised the issue of disputes around the MOS SMcCandlish was not brining an issue there out of the blue. Like LR I think SMC's comment is overly, and needlessly personal - it assumes bad faith and conjectures on the motives of another editor - but frankly ARBATC does not empower us to stop that at RFA. Like RL I'd ask SMcCandlish to please post more briefly and when upset please take a step back. I'd also remind all participants in discussions around this topic area to stop making personal remarks - such behaviour is forbidden by the RFAR--Cailil 19:13, 9 February 2013 (UTC)

E4024

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

Request concerning E4024

User who is submitting this request for enforcement

Athenean (talk) 01:25, 10 February 2013 (UTC)

User against whom enforcement is requested

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

Sanction or remedy to be enforced

WP:ARBMAC, Misplaced Pages:ARBAA2

Diffs of edits that violate this sanction or remedy, and an explanation how these edits violate it

E4024 is a Turkish nationalist with a severe case of battleground mentality and a long history of disruption on Greek and Armenian-related topics . He has been consistently engaging in tendentious editing, edit-warring, incivil and POINTy behavior, and several other forms of disruption, documented below.

General Tendentious editing

1. tries to hide mention of the Armenian genocide, even though it is important for context
4. even though lahmacun is widely consumed in Armenia
6. unbelievable

Aggressive, incivil behavior

Removing or manipulating relevant, reliably sourced material with spurious edit summaries

1. claim is in the Pew Forum 2011 source - either he didn't bother checking or is outright lying
3. the source states exactly what was in the article
4. Hovanisian is a perfectly reliable source
6. the source clearly states Vehib was of Albanian origin - E4024 is trying to hide that
7. removes Perseus with a spurious edit summary
8. note ethnic baiting in the edit summary
9. again with the ethnic baiting

Bad faith assumptions

3. note the part about "writers whose surnames end in "ian"" (i.e. Armenians) at the bottom of this interminable POV rant
4. again with the last names ending in -ian
5. and again.
6. Assumes admin (Deskana) who declined a checkuser request in an SPI he filed is a sock of the user he assumed was socking. This is absolutely incredible, I have never seen such paranoid (and clueless) bad faith assuming in five years of editing wikipedia

False claims of source falsification

Aggressive behavior in his talkpage, impossible to communicate with this user

1. even though he is clearly edit-warring

Aggressive, insulting edit summaries

Disruptive, drive-by POV tag bombing on articles he simply doesn't like

1. article doesn't say anything about "enslaved minorities"
3. accompanied by edit-warring

Tendentious cn tag bombing

1. even though he article is filled with sources to that effect
2. even though it's already sourced
7. , followed by edit-warring

Trolling

Trying to manipulate other users

Requesting page protection right after edit-warring in other to make sure the page is stays is his preferred version

1. edit-warring
2. within five minutes of his revert

WP:POINTy, retaliatory behavior

1. Requests speedy deletion when after he couldn't have his way regarding the Turkish spelling for "pastourma" and "soutzouki"
2. in retaliation for this
3. in retaliation for this added tag within minutes of being reverted on the talkpage, never mind the inanity of removing the tag itself

Disruptive deletion nominations

1. right after users Dr. K. and Proudbolsahye worked hard on the article

Incredibly petty disruption

Intellectual dishonesty

1. Conceals a revert of this edit inside another edit, with a deceitful edit summary
2. nothing in the source about the demonstrators "violating" anything, misuses loaded words for effect

Diffs of notifications or of prior warnings against the conduct objected to (if required)

1. Warned on January 10 2013 by Dr.K. (talk · contribs)
2. Warned on December 11 2012 by EdJohnston (talk · contribs)
3. Warned on May 15 2012 by Qwyrxian (talk · contribs)

His talkpage is in general a graveyard of warnings, blocks, and conflicts, but he takes great care to sanitize it. However, his talkpage history is quite illuminating.

Additional comments by editor filing complaint

I apologize for the length of the report, but the disruption caused by this user is massive, long-term, and across dozens of articles. I have only included diffs from the last month or so, which gives an idea of how intensive the disruption is. If I were to include diffs older than 1-2 months, there would be hundreds of them. E4024 is responsible for virtually every kind of disruption I can think of, or have experienced in my past 5 years of editing wikipedia. Incivility, edit-warring, POINTy retaliatory behavior, tendentious editing, ethnic baiting, it's all there. Communicating with this user is impossible, he instantly reverts any posts to his talkpage often with aggressive and insulting edit summaries (an example of many , there are dozens in his talkpage history). Armenian and Greek editors are enemies, not people to discuss things with. After extensive interaction with this user, it is my distinct impression that he is not here to build a neutral encyclopedia where Greek and Armenian-related topics are concerned, but to fight great battles and right great wrongs. For this, I propose that he be banned from all topics relating to Greeks and Armenians, per WP:ARBMAC and WP:ARBAA2. Athenean (talk) 02:19, 10 February 2013 (UTC)

Notification of the user against whom enforcement is requested

Discussion concerning E4024

Statement by Sprutt

E4024 is a disruptive account which refuses to comply with WP's rules after the many formal and informal warnings. It defies advice about how to be a better editor. Sprutt (talk) 02:26, 10 February 2013 (UTC)

Statement by E4024

Comments by others about the request concerning E4024

Result concerning E4024

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