Misplaced Pages

Revision as of 11:20, 12 May 2013

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.

Dicklyon

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 Dicklyon

User who is submitting this request for enforcement

Apteva (talk) 07:01, 30 April 2013 (UTC)

User against whom enforcement is requested

Dicklyon (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

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

1. 30 April 2013 Have you (twice)
2. 29 April 2013 named editor, discussion directed at and about editor, not content
3. 29 April 2013 "you're wrong"
4. 29 April 2013 "you mis-parse it"
5. 28 April 2013 you, your ... agenda
6. 28 April 2013 you
7. 27 April 2013 named editor, failure to assume good faith (I am of course he or she also)

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

This is an editor who has been warned countless times not to personalize discussions, and insists on continuing.

1. Warned on 26 April 2013 by Apteva (talk · contribs)
2. Warned on 26 April 2013 by Apteva (talk · contribs)
3. Warned on 30 April 2013 by Apteva (talk · contribs)
4. Warned on 4 January 2013 by Apteva (talk · contribs)
5. Warned on 3 January 2013 by Born2cycle (talk · contribs)

Additional comments by editor filing complaint

This creates a very toxic editing environment that does not encourage and welcome participation.

Notification of the user against whom enforcement is requested

Discussion concerning Dicklyon

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 Dicklyon

The underlying problem is embodied in the person of Apteva, not in me pointing that out. Shouldn't we insist that he respect the wishes of the community in banning him from his continuing anti-MOS disruption such as this section blanking?

I ask here again, can his topic ban be rephrased to include the part that the closer omitted from what the community had overwhelmingly endorsed? See Misplaced Pages:Administrators' noticeboard/Archive244#Continuing topic ban violations by Apteva Dicklyon (talk) 14:28, 30 April 2013 (UTC)

• Proposal – clarify Apteva's topic ban by adding the bolded phrase or something like it:

Apteva is topic banned indefinitely from modifying or discussing the use of dashes, hyphens, or similar types of punctuation, broadly construed, including but not limited to at the manual of style and any requested move discussion, and from advocating against the MOS being applicable to article titles.

As for Born2Cycle's comments below, note that he advertises his long-running campaign at User:Born2cycle#A goal: naming stability at Misplaced Pages and at User:Born2cycle/FAQ. When he ramps it up as he recently did here and continues to do here, am I not allowed to comment on that? It doesn't seem that his various warnings (including Misplaced Pages:Arbitration/Requests/Case/Article titles and capitalisation#Born2cycle warned) and pledges (including User:Born2cycle/pledge) and sanctions (most recently Misplaced Pages:Administrators' noticeboard/Archive245#Continued tendentious editing by Born2cycle) over the last several years have had much moderating influence on this disruptive behavior of domination of move discussions. Dicklyon (talk) 18:49, 1 May 2013 (UTC)

Speaking of personalization, I cracked up my wife with my quip at the Yosemite ranger station last summer, "Who can prevent forest fires?"

Statement by Ohconfucius

It really is too early for silly season, but this request is all rather surreal. It's very possible to take things too literally, and it looks very much like a good example. Apteva has carefully chosen diffs every instance of the word "you", then uses it to accuse Dick of making a "personal" argument in the sense prohibited by the Arbcom ruling. All I see is civil discussion. Such use of "you" was most often innocent, when Dick was trying to address an answer to or comment on what Apteva said. Methinks Apteva is a month too late with this. -- Ohconfucius  11:32, 30 April 2013 (UTC)

• Indeed, B2C, beware of the Boomerang. I find myself often questioning the utility of posting to Apteva's talk page. I don't know if he's feels that a particular user is bullying him, as it is obvious from his reaction to DL, or are they so burnt out that they have become generally ultra-sensitive to criticism: but this removal, within 6 minutes, may indicate a strong streak of WP:IDIDNTHEARTHAT. That, plus the diffs supplied by Apteva in evidence against DL – particularly the first two – strongly suggests a serotonin top-up (i.e. a holiday in the sun) would be largely beneficial. -- Ohconfucius  18:55, 1 May 2013 (UTC)
• I just saw this and this as other recent examples of an overwrought editor's objection. It's surreal.

  Also, since Apteva already launched this AE against DL, this looks very much like harassment. Apteva, you really do need to take that well-earned holiday in the sun. -- Ohconfucius  01:48, 7 May 2013 (UTC)

• As to B2C, I was johnny come lately to the Kelly Yeomans suicide article, but I do and did object to B2C carry on his advocacy in that connection. I also made a complaint to an admin at about the time the RM was closed. Note that he is the top contributor to that discussion by a very long margin. He entered the discussion, and was there pushing his point of view against near-unanimous opposition right until it was closed. That indicated B2C still doesn't know when to stop, although before I got involved in that discussion, others had already complained to him on his talk page, to no avail. -- Ohconfucius  12:37, 9 May 2013 (UTC)

Statement by Johnuniq

I suppose admins will have noticed at least some of the background which has involved enormous discussions in multiple areas. I ask that admins considering this case think of what would benefit the encylopedia, rather than basing a decision on whether "Have you read it?" is an abuse of a talk page. A tiny part of the background:

• AE: Dicklyon reported by Apteva October 2012; result: withdrawn.
• RfC/U: Apteva December 2012.
• ANI January 2013; result: Apteva topic banned.
• AE: Apteva reported by SarekOfVulcan January 2013; result: Apteva warned.

Johnuniq (talk) 11:59, 30 April 2013 (UTC)

Statement by (SmokeyJoe)

The listed warnings are not less personal or confrontational than the listed violations. --SmokeyJoe (talk) 12:02, 30 April 2013 (UTC)

I don't think that we have or want rules on the use of the second person singular pronoun, or the use of names. They are especially useful when thanking, for example. I don't feel that I know Apteva or Dicklyon very well, but have noticed, in reasonable debating, that Apteva comes across as tense, and Dicklyon comes across as direct, perhaps terse readable as snide. This combination is prone to inflame. I don't think blocks are useful in calming. The two could each be asked to not address or reference the other. --SmokeyJoe (talk) 05:06, 1 May 2013 (UTC)

Statement by Apteva

This is a very serious issue that must be dealt with in an effective manner, and passing it off as otherwise is ludicrous. For example, while this editor is the worst offender that I have seen, should they be allowed this pattern of editing, it is like a cancer that spreads to other editors. I suggest a one month block (oddly, the editor in question says they are on a wikibreak), escalating to longer blocks if the pattern continues. Apteva (talk) 16:01, 30 April 2013 (UTC)

To SmokeyJoe, the correct place to use you and an editor's name is on their talk page, not at an article or project talk page. All of Dicklyon's comments that are directed to me need to be solely and only on my talk page, not snide remarks at an RM discussion. Apteva (talk) 16:05, 30 April 2013 (UTC)

To My very best wishes, the comments do a great deal of harm. There are two methods of decision making used, consensus and parliamentary, and neither permit directing comments to an individual. One requires directing comments to the group, the other to the moderator. There are no exceptions. Apteva (talk) 18:38, 30 April 2013 (UTC)

To Johnuniq, obviously the AE complaint in October 2012 should not have been withdrawn, as doing so may have reinforced the idea that there was nothing wrong with the violations that had occurred, and a specific remedy should have instead been suggested. Apteva (talk) 18:44, 30 April 2013 (UTC)

To My very best wishes, it is not a problem if an editor says "I disagree with your argument because..." once, and it can be forgiven, but it is prudent to point it out to them on their talk page that it would have been better to say "the argument" instead of "your argument" so that it does not become a habit. When it does become a habit, it becomes a very serious problem. As to "it might be a good idea to politely tell someone that they are wrong and explain why (assuming they are capable of accepting someone else criticism and improving)." I have brought this up ad nauseum (and quite politely) on the editor in question's talk page. I need someone to make it more important to them, so that they will stop. Apteva (talk) 19:27, 30 April 2013 (UTC)

This, by another editor, not Dicklyon, is the sort of post that I am objecting to. "I take it you haven't bothered to follow any of the links to BMI." Apteva (talk) 01:58, 2 May 2013 (UTC)

To Omnedon, incivility is a related, but different subject from personalization. I am only addressing personalization here. Apteva (talk) 03:07, 2 May 2013 (UTC)

To Omnedon, personalization if not as much about "talking directly to other editors" as it is talking about other editors, when the subject is not any editor, as it is on the talk page of an article or project page. See talk page guidelines. Apteva (talk) 16:36, 2 May 2013 (UTC)

To ErikHaugen, absolutely. "since you understand it much better than I do, maybe you should take the next crack at it" excludes anyone else who might want to "take the next crack". That comment belongs only and solely on the editor in question's talk page, not on the article or project talk page. This is basic talk page protocol. Apteva (talk) 17:09, 3 May 2013 (UTC)

Still more. Deleted with the edit summary "noise". Dicklyon began by saying "I didn't want to mention you by name", which is a thought that does not need to be said, and while commendable, using "you" is no better, nor is any personalization. This edit was at first deleted by another editor and then un-deleted. "can you please just stop it" belongs only and solely on the talk page of whichever editor, such as myself, that this was directed to. Apteva (talk) 21:53, 6 May 2013 (UTC)

• A narrowing of my topic ban would be a very good move. The current topic ban is totally political and totally absurd and intended solely to silence dissent. Topic ban everyone who does not agree with one side and then pretend there is consensus. The real topic ban that should have been proposed and the restrictions that should be imposed, is to not propose any page moves based on hyphens and dashes for one year, and remove the absurd restriction to one account, that is severely impacting my ability to improve the encyclopedia. Those are the two outcomes that I request with regard to myself. Apteva (talk) 19:18, 9 May 2013 (UTC)

B2C is well known for being wordy. That in itself is not a problem. All discussions can be closed regardless of how wordy they are. Apteva (talk) 14:36, 11 May 2013 (UTC)

As to the truth that MOS does not apply to titles, the idea that it does was rejected as absurd when it was first proposed, and only implemented by topic banning those who disagreed. It was brought up at AT in January and rejected. Obviously the suggestion that it does needs to be removed from the MOS. Stifling dissent by topic banning is absurd and even juvenile. I have not to my knowledge said anything about the topic any time in the last month, and this is a non-issue that does not address any activity that needs to be curtailed. Apteva (talk) 14:36, 11 May 2013 (UTC)

As to Dicklyon's last paragraph about Smokey the Bear, the two words that jumped out at me were "last summer". Was this going on last year, long before I started complaining, and became an in-joke at that time that they were using "you" too much, instead of correcting the problem? Apteva (talk) 14:42, 11 May 2013 (UTC)

Comment by Beyond My Ken

I suggest that reviewing admins considering sanctioning Apteva for filing an entirely frivolous enforcement request, and consider Dicyklon's suggestion that Apteva's topic ban be adjusted per the original community consensus. Beyond My Ken (talk) 16:21, 30 April 2013 (UTC)

Statement by The Devil's Advocate

One should note Dicklyon is the one who filed the RfC/U against Apteva that resulted in the community sanctions. Apteva filed a frivolous request regarding another editor back in January, which lead to a lot of ill will, after that editor was responsible for initiating the AE case about Apteva noted by Johnuniq above. The one who seems to be personalizing disputes the most is Apteva by filing these types of frivolous requests against various opponents.--The Devil's Advocate _{tlk. cntrb.} 16:43, 30 April 2013 (UTC)

@Gato, the only topic ban issued since the case allowed the editor to reference the MOS in order to justify edits in articlespace. In other words, general discussion of the application of MOS were not allowed, but only that which is necessary to explain an edit the editor made to an article. However, I think you could consider just imposing a ban on filing AE requests. Apteva's AE requests have been rather POINTy and frivolous, demonstrating clear battleground behavior.--The Devil's Advocate _{tlk. cntrb.} 19:00, 5 May 2013 (UTC)

Comment by My very best wishes

Perhaps I used to significantly stronger wording and accusations in another subject area, but the comments in the diffs look a little tense but more or less harmless. I do not see any reason for sanctions.

@Apteva. Yes, I partly agree: comment on content, not on the contributor. However, I do not really see a huge problem if someone tells: "I disagree with your argument because..." or "your edit is inconsistent with RS policy because...", instead of telling "this argument" and "this edit". Catching others on minor technicalities is not really a good idea. And remember, they could be right: perhaps this is your problem. In fact, it might be a good idea to politely tell someone that they are wrong and explain why (assuming they are capable of accepting someone else criticism and improving). But this is just a general idea; I only saw your diffs.My very best wishes (talk) 19:15, 30 April 2013 (UTC)

Sorry, but I did not see this ANI post. Frankly, having so protracted disputes about minor technical issues is beyond imagination and disruptive. Just to clarify, I am not familiar with this case, but only looked at the diffs provided above and do not see them too disruptive per se, although the whole dispute is obviously disruptive. My very best wishes (talk) 16:09, 1 May 2013 (UTC)

Comment by uninvolved A Quest for Knowledge

The majority of diffs presented in this RfE are not persuasive of any gross misconduct. However, there are three that appear to cross the line:

• Apteva, seem seem to have returned to your campaign to deny that the WP:MOS applies to style in titles
• If you don't like the way the lead is stated or bold, that would be a less disruptive thing to work on than continuing to push your minimalist naming agenda.
• Apteva just likes to follow me around and disagree, it appears.

Clearly, there seems to be some sort of personalization of this dispute that should not have been personalized. Perhaps a reminder/warning to Dicklyon to not personalize disputes might be the best way of handling the situation. A short break (perhaps a month) might also be helpful. A Quest For Knowledge (talk) 00:45, 1 May 2013 (UTC)

Statement by Born2cycle

As a regular target and witness of Dicklyon's inappropriately personalized commentary on article/WP talk pages, I must concur with this statement of A Quest For Knowledge (talk · contribs), which I simply repeat:

However, there are three that appear to cross the line... Perhaps a reminder/warning to Dicklyon to not personalize disputes might be the best way of handling the situation.

To Quest's list of three line crossings, I would also add:

• "no need to disrupt a long-stable name just because Born2cycle finally got his way at Yogurt"
• "This is just another tool that Born2cycle can use to argue to try to get his way, ..."

Those references to me in terms of Dicklyon's opinion that what happened at Yogurt was me getting "my way" is WP:BATTLEGROUND language. It certainly does not reflect how I view these situations. That Dicklyon sees it that way (and not just with me) is a problem, and explains why he makes the inappropriately personalized comments on article/WP talk pages that he does. That needs to be addressed.

I think the following suggestion from Quest is going too far, though it would be appropriate if the problematic behavior continues after the warning: " A short break (perhaps a month) might also be helpful."

I strongly oppose any BOOMERANG result to the petitioner of this request, as the underlying complaint has reasonable basis, and BOOMERANGing would discourage others from reporting inappropriately personalized commentary on article/WP talk pages, and this would effectively sanction (in the approve sense) such behavior, not only from Dicklyon, but from others as well. --B2C 16:00, 1 May 2013 (UTC) series of edits to this statement done. --B2C 16:23, 1 May 2013 (UTC)

Reply to Dicklyon

Dicklyon asks above: "am I not allowed to comment on that? ". Sure, if you think I or anyone else has been behaving inappropriately, bring it to our attention on our respective user talk pages. Not on article/WP talk pages. On article/WP talk pages, please refer only to substance, including arguments actually made, not what you imagine to be someone's motivations, whether or not you believe your opinion is backed up by what they say on their user page. By the way, if you think anything on my user page suggests anything inappropriate, please bring that up too... on my user talk page. Not anywhere else.

This is the key thing. Don't bring up negative stuff about specific WP users on article/WP talk pages. That's all. It reflects poorly on all of us. --B2C 20:23, 1 May 2013 (UTC)

• Here's a specific suggestion: When commenting on article/WP talk pages, ignore the signature. That is, reply only with comments that would make sense and mean the same thing regardless of who posted the comment to which you are replying. Thus, if they say something helpful, replying with a "thank you" is fine, despite the personal "you" reference. But if you're going to make a comment that only makes sense because of other stuff that person has written elsewhere, it almost certainly is not appropriate to bring that up on that article/WP talk page, especially if the intent is to convey something negative.

  For example, if someone says something which seems to contradict what they said or did elsewhere, question the user about the apparently contradictory behavior on that user's talk page, not on the article/WP talk page. --B2C 20:55, 1 May 2013 (UTC)

• I also oppose Dicklyon's proposal to gag Apteva with respect to advocating against the applicability of MOS on article titles. That's a very controversial issue that has no consensus, and to seek muzzling others about that, especially when he is a proponent of one side and Apteva is a proponent of the other, is just another example of Dicklyon treating WP as a WP:BATTLEGROUND. --B2C 22:04, 1 May 2013 (UTC)

• Dicklyon is at it again, making personalized comments about me on a policy talk page instead of addressing content :
  • "B2C has no problem with ambiguity in titles as long as there are not two articles fighting for the same title; he defines that to be unambiguous."***NOTE: (that's not true but that's beside the point)
  • "He has been very consistent about that, as you can see from the history of the "precision" criterion, in which he has consistently worked to say that precision is bad and that titles should have just enough to distinguish the articles, not to point out their topics."
  • "B2C has not advocated doing away with recognizability, but has several times to rephrase it, like in 2009 when it tried to say what precision was good for: "Good article titles are precise enough to indicate the topic unambiguously, but not more so." he changed it into a more negative and discouraging form "Good article titles are only as precise as necessary to indicate the name of the topic unambiguously."
  • "That was one subtle step, but he keeps after it, like in his proposal at Wikipedia_talk:Article_titles/Archive_36#Proposal: clarifying PRECISION, which seeks to "clarify" by getting rid of any consideration for ambiguity in titles, by changing it to add the bolded part here: "Titles usually use names and terms that are precise (see below), but only as precise as necessary to identify the topic of the article unambiguously with respect to other Misplaced Pages titles." "
  • "Clearly, B2C has no problem with ambiguity, only with article title collisions."
  • "Looking at real cases where B2C pushes a narrow interpretation might; he typically does not have consensus on his side, but always pretends to."

I'm sorry, but what place do any of Dicklyon's opinions about me or anyone else have on any policy talk page? --B2C 04:26, 2 May 2013 (UTC)

Dicklyon is at again (yes again).

It's not a good scheme, but until we can turn back the clock on some of B2Cs changes to titling guidelines, it's the mess we're stuck with.

Why is it okay to personalize in the middle of an RM discussion like this, never mind that the ad hominem attack claim is entirely without basis. --B2C 22:24, 5 May 2013 (UTC)

Violation?

It has been suggested that my behavior in RM discussions recently has been problematic in some manner. Part of my pledge is based on the assumption that I don't always recognize when my behavior is problematic, and so I pledge to pay heed when others tell me it is. So if my behavior has been problematic recently, I'm not aware of where or why, and nobody has told me. Regardless, I'm quite confident there is no problematic behavior occurring now. I only say this because more than one person has suggested there is a problem and actions should be taken.

The closer of the AN about me recognized all this and closed accordingly:

Meaning: An uninvolved admin may ban from a particular discussion he is involved in on a case by case basis after a warning that can be enforced with a block between 24 hours and the duration of the discussion he is disruptive in. This includes discussions about the close of a move or article titles discussion anywhere on Misplaced Pages.

For the record, I have not received any warnings from any administrator about any of my behavior anywhere, and I'm not aware of being disruptive in any discussions any where, certainly not any ongoing ones. To block or ban me in any way for behavior in some closed discussion in which I was not even warned seems purely punitive, inconsistent with the previous AN, and not conducive to improving anything on WP. Thank you. --B2C 00:06, 11 May 2013 (UTC)

People are citing statements made by editors involved in the discussion in question. These are not warnings from uninvolved administrators on my talk page, which is what I'm due, I believe, presuming no egregious behavior on my part, before any kind of penalty is imposed. As I've noted elsewhere, the outcome of the suicide RM discussion was obvious early. My involvement was one of curiosity pursued with those who chose to participate. If I had been told my behavior was problematic I would have stopped. --B2C 04:56, 11 May 2013 (UTC)

Omnedon - Regardless of what I've been told many times by many people, what does that have to do with whether I deserve to be blocked or punished otherwise for specific behavior in a particular discussion without a warning from an uninvolved administrator as was stated in the AN as quoted above? --B2C 20:51, 11 May 2013 (UTC)

Huw - you seem to misunderstand my point when you say, "His suggestion in response is that those expressing concern needn't participate in the discussion ". I'm saying those who think a discussion is "done", or think it has gone off on inappropriate tangents or whatever, but is still ongoing, don't need to participate. In fact, I can't imagine continuing in a discussion that I thought was done, just to complain that others are still continuing. If others want to continue, what is it to me? Why should I complain about them wanting to continue? I just don't get that. --B2C 20:56, 11 May 2013 (UTC)

Statement by Omnedon

Having looked at all of the diffs, I see no statements that cross the line of incivility. I've been asked by editors if I had "even bothered to read such-and-such", and things of that nature; and I admit it was annoying to me. And yes, Dicklyon tends to be rather direct when he disagrees, perhaps pushing the envelope a bit. But requesting a block for these diffs seems extreme to say the least. The term "thin-skinned" comes to mind. I've seen far worse wrongly excused and even justified. As a side note, B2C should perhaps not be among those casting stones here, given his own past record here (mentioned above). Omnedon (talk) 00:01, 2 May 2013 (UTC)

I understand that the focus is personalization, but a request for a block simply for talking directly to other editors in a discussion seems even more incredible. I had assumed, incorrectly, there there was a civility component here. Omnedon (talk) 12:10, 2 May 2013 (UTC)

It's interesting that you would direct me to read the talk page guidelines, given the nature of your complaint. And yes, it is a good practice to focus on content and not editors. But it seems to me that Dicklyon was talking to editors in most cases. Omnedon (talk) 12:56, 3 May 2013 (UTC)

B2C, you have been told many times by many people in many discussions over many months. You seem to choose not to hear or acknowledge. Omnedon (talk) 11:57, 11 May 2013 (UTC)

Statement by Tony1

This is a waste of everyone's time. Tony (talk) 03:42, 2 May 2013 (UTC)

Statement by ErikHaugen

These diffs don't demonstrate anything that violates the arbcom remedy. Apteva seems to think that using the word "you" is personalizing; consider this diff supplied as evidence, where DL uses the phrase "you" when suggesting to another user that he go ahead with his proposal: "That all sounds good, but since you understand it much better than I do, maybe you should take the next crack at it." If Apteva thinks this is an example of personalizing disputes, or even of problematic behavior, then perhaps Apteva should not be bringing AE requests. I think sanctions for frivolous or vexatious requests might be an overreaction, but I think at least a warning is in order, as this does have the appearance of a vendetta and is at least a waste of everyone's time.

DL gives Apteva several warnings in the other diffs supplied. I don't think this is in itself necessarily a problem either; others have commented that that should only happen on user talk pages or AN or here or whatever, but this isn't personalizing the dispute, so the arbcom remedy isn't relevant.

Apteva: Do you stand by this diff? Do you really think this is evidence of problematic behavior, in any way? ErikHaugen (talk | contribs) 16:41, 3 May 2013 (UTC)

No, it does not exclude anyone, and no, it does not belong on the user's talk page. That is two editors discussing how to edit an article, one making a request of another, in a collegial and constructive manner. Please don't waste AE's time with this kind of thing again. ErikHaugen (talk | contribs) 08:38, 5 May 2013 (UTC)

Statement by Huwmanbeing

I've looked at the diffs that Apteva provided; though a few indicate annoyance, I'm afraid I don't see behavior that rises to a level that requires sanction; in at least a couple of cases I confess I can't even ascertain what inappropriate personalization or incivility the diff is meant to indicate (unless simply using the second-person pronoun is considered a violation, which would seem a bit odd).

The corrective actions described by Gatoclass sound appropriate as regards Apteva and Born2cycle. In particular, a reasonably short ban followed by "escalating bans for future breaches" would I think help interrupt what's clearly been a long-running cycle without being unnecessarily severe. ╠╣uw  01:50, 6 May 2013 (UTC)

One extra point: regarding Born2cycle's statement above that no one gave him any indication that his behaviors were problematic: , , , , , , etc.

His suggestion in response is that those expressing concern needn't participate in the discussion (a suggestion he's previously made elsewhere ) ╠╣uw  02:58, 11 May 2013 (UTC)

Statement by (In ictu oculi)

After a review of the diffs offered this request appears to be verging on frivolous. "So we're done. Or fix it way Huwmanbeing suggests, even though you mis-parse it. " is a example of personalization? What if it was mis-parsed, how then does someone note something is mis-parsed without saying it? This does not deserve any result action. In ictu oculi (talk) 04:36, 7 May 2013 (UTC)

As an aside, which some may not consider relevant, but I personally consider is Dicklyon has a 59.29% article contribution vs 3.29% WikipediaTalk contribution, a very healthy balance in contributing to article space rather than making/changing rules for others to follow. There are one or two frequent WikipediaTalk (inc MOS) contributors who barely contribute to article space. There's something not very balanced in that kind of diet. In ictu oculi (talk) 04:45, 7 May 2013 (UTC)

Statement by Glrx

This filing seems to be another sad episode in a long running dispute. I've come across bits and pieces in the past, and have looked at the material above and comments by Gatoclass below.

I'm not a MOS warrior, I don't go around enforcing MOS, but I try to follow the endash rules, I have corrected some edits to follow MOS (I usually let the 'bots do it), and I have renamed some articles to use MOS-preferred punctuation. My editing has crossed paths with Dicklyon on several electronics articles as recently as today with Talk:Cat's-whisker detector. In those technical articles, I've been impressed with Dicklyon's research, argument, and clarity. I have not had similar interactions with Apteva or Born2Cycle. Generally, I stay far away from MOS debate.

I see no reason to sanction Dicklyon here. I do not see the complaints as being significant. Some complaints were about Dicklyon maintaining his own talk page (the "noise" edit comment while deleting some Apteva posts), and some complaints seem to seek a gag order (only discuss an editor's past history on his talk page). Ad hominem arguments should be avoided, but comments that attempt to accurately characterize an editor's global position seem fair game; unfortunately they can also come across as dismissive. Dicklyon may not be 100% civil, but I don't see A Quest for Knowledge's examples as worthy of sanctions. I'm not happy with Dicklyon's "Only YOU can prevent forest fires" comment, but otherwise his comments here are reasonable. I'd like Dicklyon to be a bit more diplomatic when engaging difficult editors, but that should not mean he cannot demand contrary sources.

Gatoclass proposes a one month topic ban on page move discussions for B2C. There was an earlier discussion (B2C needs to display higher tolerance of other editors) that TP closed. That discussion had support for OPTION A (complete ban on page move discussions) and OPTION B (ban that limits interaction on page move discussions); many supported B first and then A if B fails to work. TP's remedy ignored A and B and laid out a case-by-case warning with modest block for subsequent misbehavior in that case; TP was also concerned about bias in the commenters. My problem with TP's remedy is that it is not a restriction until somebody complains to an admin, so there's no penalty for B2C testing the limits. Gatoclass is proposing OPTION A with an expiration in one month. Gatoclass also worries that the proposed topic ban on page moves may not be general enough, but I don't see a pressing need to tailor something more general. I'd point to B2C's earlier promise about better behavior and ask him to follow it. I hope there is no more trouble down the road, but if there is, it can be addressed then. However, I think there was more support for an indeterminate OPTION B: B2C may comment once (or twice) on page move discussions. That seems the better option; it does not unduly restrict B2C's participation in page moves but would avoid extended debate; it would not have the fuzziness of debate until there's an objection.

I'm clueless about what to do with Apteva. Apteva is sensitive about several issues, but that sensitivity is not something than can be remedied here. Some of that sensitivity can be understood. Taking action on that sensitivity is the thing that needs to be curtailed. Apteva may not like something, but that does not mean Apteva should act on it. For example, I wish this current enforcement action did not happen. Apteva's request for a one month block on Dicklyon is not narrowly tailored for the perceived conduct nor is it of appropriate length. In contrast, Dicklyon's suggestion of amending the January topic ban is narrowly tailored (but goes beyond the just punctuation discussion). I'm not sure I'd include all of MOS; the extension might include just capitalization; there was a diff about capitalization. However, I have an incomplete view of Apteva editing. Gatoclass's diffs below are a mixed bag for me. The capitalization argument is a bit pointy, but the Suicide-of-X comments do not seem too far out of line (I'm am mystified why Suicide-of-X or Al Capone should be addressed at BLP). Consequently, I do not know what to do. Glrx (talk) 00:01, 9 May 2013 (UTC)

Statement by MelanieN

FYI about B2C: there were several people who cautioned him on his talk page or were considering reporting him for reverting to his old editing habits at the Suicide of Kelly Youmans discussion. Among other things, he twice characterized opinions he didn't agree with as "ridiculous"; he twice hid comments by others (I restored the second set); and he asked the same question seven times, five of them in boldface, even though the question had been directly responded to at least three times (by Joe Decker, tryptofish, and myself). Sorry, I am traveling and posting via iPhone so cannot post diffs. MelanieN (talk) 03:00, 11 May 2013 (UTC)

Statement by (username)

Statement by Kumioko

That's nothing more than using a legalese justification to do the same thing but justifying it in a different way. Either way, as Dianna points out, at this point its still a waste of time. Its punitive rather than preventative plain and simple. Kumioko (talk) 10:26, 12 May 2013 (UTC)

Result concerning Dicklyon

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

Some of Dicklyon's comments are less than ideal, but I don't think them serious enough to warrant a sanction, IMO they might at most merit a reminder. On the other hand, I can to some extent sympathize with his exasperation, having read some of the discussion at Talk:Suicide of Kelly Yeomans, where Born2cycle's repeated advocacy of a page move request that was rejected by a five to one majority might itself be considered disruptive. As for the proposal to amend Apteva's topic ban, I would have to look at that in more detail before expressing an opinion. Gatoclass (talk) 17:54, 3 May 2013 (UTC)

Having taken a look through some of the earlier discussions (it's hardly possible to read them all since there are so many) it seems to me there is a solid case to be made for a sanction against Born2cycle for the continuation of his well documented, disruptive argumentativeness at Talk:Suicide of Kelly Yeomans, and for a broadening of the existing sanction against Apteva. What I'm struggling to decide on is the scope of such sanctions. For Born2cycle, I am inclined to propose a one-month topic ban on all page move discussions, with escalating bans for future breaches, but I'm not sure if a ban on page move discussions alone will be sufficiently broad. For Apteva, I am seeing disturbing parallels in some of his recent edits with the types of arguments, and the intransigence, that got him community banned from certain types of MOS-related punctuation discussions, indicating that a broader ban may be necessary, but where does one draw the line? MOS relates in one way or another to almost every aspect of editing, so an undifferentiated ban may be impractical, but the current ban is beginning to look too narrow. I am still considering these issues, but in the meantime I would appreciate some input from other users on the same. Gatoclass (talk) 08:41, 5 May 2013 (UTC)

Since Seraphimblade imposed the original topic ban on Apteva, I have asked for his opinion on its scope. He seems not to be very active lately however, and we can't keep this request open indefinitely, so if he hasn't replied in the next couple of days I will move forward on this request regardless. Gatoclass (talk) 15:37, 8 May 2013 (UTC)

Seraphimblade has not been active in some time, but I think his comment here is relevant to the current proceedings. Apteva apparently believes that the RfC and sanctions already imposed upon him or her are some sort of mistake—I've seen no suggestion at all that Apteva takes any kind of responsibility for problems others have with his/her approach to discussions. When a topic ban is imposed, the expectation is that the person disengage entirely from the problematic area. It's kind of a last resort in the hopes that a site ban is not needed. It is not an invitation to wikilawyer around the topic area in the way that Apteva has continued to do. The diffs noted by Dicklyon and by Gatoclass show that the same kinds of problem persist, and therefore that a broader topic ban at minimum is needed. One option is the one proposed by Dicklyon; another is to add an additional ban, something along the lines of: "Apteva is indefinitely prohibited from engaging in discussions and edits relating to the Manual of Style or policy about article titles" (as was imposed upon PManderson in the case cited). I broadly agree with Gatoclass's comments, not just about Apteva but about Dicklyon and Born2cycle as well. Paul Erik 02:04, 9 May 2013 (UTC)

I too see little evidence that Apteva has conceded an issue with his past behaviour, indeed he appears to be every bit as insistent on his correctness as before. However, he has indicated on my talk page that he no longer "keep repeating myself as I once did", which sounds like a step forward. Nor has a great deal of evidence been presented of recent misconduct on Apteva's part, or of a wider MOS problem. So although I too have considered a broad MOS ban, I'm not sure it would be necessary at this point; I'm inclined to think that a broadening of the topic ban to include the clause proposed by Dicklyon might be sufficient at this stage. If that changes, a broader ban can always be imposed at a later date. Gatoclass (talk) 08:41, 9 May 2013 (UTC)

Apteva appears somewhat persistent/repetitive in this AE request, although on the whole there does seem to be a step forward as you note. Certainly a less broad topic ban would be preferable if it can achieve the results. Paul Erik 12:26, 9 May 2013 (UTC)

I am in the process of summarizing the evidence presented above and will post it along with my conclusions shortly. Gatoclass (talk) 06:21, 11 May 2013 (UTC)

Okay, to summarize:

• Born2cycle made 69 comments over the course of ten days at Talk:Suicide of Kelly Yeomans - almost as many comments as the next three contributors combined. In addition to reopening a recently closed RM discussion (which I think he was entitled to do in the circumstances) he also initiated three separate discussion sub-threads and participated heavily in a fourth; this in a discussion where the consensus was clearly and overwhelmingly against his POV. Born2cycle states in his evidence regarding that discussion that If I had been told my behavior was problematic I would have stopped, but several users expressed frustration, some on multiple occasions, with his tactics (sample: ) and B2c not only did not stop, he was still proposing to continue the discussion a few hours before it was closed. In light of his previous warnings and pledges, I therefore propose to ban Born2cycle for one month from RM-related discussions.
• Due to concerns raised above and in earlier discussions that Apteva is breaching their ban by other means, I propose to clarify the scope of the ban by broadening it in line with the proposal outlined in earlier discussions, namely to add the clause and from advocating against the MOS being applicable to article titles. Also, I think Apteva is entitled to some clarity regarding the circumstances by which he can appeal the original ban. I therefore propose that they be permitted to appeal the ban six months from the date it was imposed, or 6 July, and every six months thereafter. Any such appeal should I think be lodged at WP:AN rather than here at AE since the original ban was imposed by the community; Apteva is of course entitled to appeal the broadening of the ban proposed here (assuming it is implemented) in accordance with normal AE practice.
• Regarding the charges against Dicklyon, I think it should be clarified that merely employing the words "you" and "your argument" etc do not constitute meaningful "comment on contributor" and are not actionable here; nor are occasional references to a user's previous history of discussion so long as such referrals are relevant to the discussion at hand and not excessive, disruptive, or objectionable in other ways. While some of Dicklyon's comments have clearly had an undertone of hostility, there has been a degree of provocation in the past which mitigates those responses to a degree. I think a certain degree of robustness in discussion must be accepted or we will end up encouraging WP:GAMING of the relevant policies. I therefore propose to post a reminder rather than warning to Dicklyon on this occasion.

In accordance with my usual practice, I will leave these proposals on the table for 24 hours, after which I will implement them if there have been no objections from uninvolved admins. Gatoclass (talk) 08:00, 11 May 2013 (UTC)

I object to the proposed one-month topic ban on User:Born2cycle. This is far beyond the scope of the remedy devised by User:TParis on the 20th of February, which read, in part, "An uninvolved admin may ban from a particular discussion he is involved in on a case by case basis after a warning that can be enforced with a block between 24 hours and the duration of the discussion he is disruptive in. This includes discussions about the close of a move or article titles discussion anywhere on Misplaced Pages". A user came to my talk page while the talk page discussion was in the process of being closed, and I declined to take any action against B2C at that time, because by the time I arrived at Talk:Suicide of Kelly Yeomans the discussion had been closed for 15 minutes and the remedy seemed punitive even at that point. So a one-month topic ban issued two weeks after the fact makes no sense to me. -- Dianna (talk) 04:59, 12 May 2013 (UTC)

I haven't examined the case and can't therefore comment on most proposed sanctions, but at first glance I find a sanction like " from advocating against the MOS being applicable to article titles" inadvisable because it is not content-neutral. The arbitration process, and admins generally, have no authority over content issues, including over the question as to how we apply the MOS to content. We must therefore not enact sanctions that ban a user from voicing a particular opinion. But, if their conduct in discussions about this topic is deficient, we can ban them from discussing the topic altogether, irrespective of the opinions they put forward.  Sandstein  06:58, 12 May 2013 (UTC)

Gilabrand

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 Gilabrand

User who is submitting this request for enforcement

Nomoskedasticity (talk) 12:01, 10 May 2013 (UTC)

User against whom enforcement is requested

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

Sanction or remedy to be enforced

Misplaced Pages:ARBPIA#General 1RR Restriction

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

1. 10 May 2013 Embedded in a series of edits that don't do much is a small change intended to reinforce the notion that Ariel University is an Israeli institution (first paragraph).
2. 10 May 2013 removes paragraph from same article

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

• Gilabrand has been blocked a number of times already for ARBPIA violations. Notified under case here.

Additional comments by editor filing complaint

The first edit constitutes a revert insofar as an earlier edit today by a different editor attempted to locate Ariel University in "Israel" (when in fact it is in the West Bank). Gilabrand's edit is more of the same, expressed slightly differently.

• Sandstein, you have previously sanctioned Gilabrand twice yourself under ARBPIA, . I fail to see why you are now unwilling to do so. Nomoskedasticity (talk) 13:23, 10 May 2013 (UTC)
• @ErikHaugen -- as the edit summary notes, the second edit removes "unsourced commentary" from the article. Nomoskedasticity (talk) 16:50, 10 May 2013 (UTC) One sentence removed by the edit (thus perhaps alleged to be "unsourced") is: "In July 2006 the Council for Higher Education rejected the proposal (which had been paired with an initiative by Shimon Peres to unite several regional colleges in the Galilee into one umbrella university)." Nomoskedasticity (talk) 17:03, 10 May 2013 (UTC)

• As a gesture of goodwill I would like to withdraw this report (assuming that it's up to me to propose such a thing). I first approached Gilabrand to request that she self-revert and was disappointed that she refused to do so; even so, I think other editors' views that the edits themselves weren't significant enough are likely to carry the day, so in the interests of saving people's time here I suggest that this report be closed. Nomoskedasticity (talk) 19:50, 11 May 2013 (UTC)

Notification of the user against whom enforcement is requested

Discussion concerning Gilabrand

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 Gilabrand

I added the word "Israeli" to the article, because there is no question that Ariel University is an Israeli institution. This is hardly the same as stating it is "in Israel." I also made a long series of copyedits to the lead and other paragraphs. I did not revert anything that the above editor edited. He took out the word Israeli, but I was not working on that paragraph and did not touch it. In fact I was not even aware that anyone else was editing the page because I was in the middle of an edit when he removed the word Israeli, and I had not seen it before I saved my edits. Improving the English and reorganizing the material so it is chronological and not repetitive was my only aim. --Geewhiz (talk) 12:19, 10 May 2013 (UTC)

Statement by Soosim

I just went and reinstated gilabrand's edits. the edits are fine. if you look at the timing, it clearly is a case of simultaneous editing by gilabrand and nomo. no reason for any sanctions here at all. and if nomo wants to discuss Israeli versus in Israel, fine. but not here. Soosim (talk) 14:48, 10 May 2013 (UTC)

Statement by Zero0000

(Not commenting on Gilabrand's highlighted actions at the moment) In my opinion Sandstein's legal analysis is not correct. It is normal practice for sanctions to be modified and extended over time. Once someone has been warned about the existence of the sanctions, it is their responsibility to keep informed about them. There is some possibility for discretion in relation to individual editors who may honestly not know about the changes, but in the case of an experienced editor who has met and commented on the 1RR restriction multiple times it is hard to see why such discretion is appropriate. Gilabrand was warned about the existence of the sanctions and provably knows they were extended to include 1RR. It is enough to satisfy the warning requirement as well as fair process. Zero 03:17, 11 May 2013 (UTC)

Statement by The Devil's Advocate

It seems to me that the report by Nomoskedasticity does not show a deliberate violation of 1RR. First of all, the reasoning that the first edit is some sort of revert is rather shaky as saying a university is an Israeli institution is different from saying it is an institution in Israel. Secondly, the time between edits is very narrow as Nomoskedasticity made the revert a minute after Gilabrand's last edit and the subsequent edit that is being characterized as a second revert was just eight minutes later and may not have created an edit conflict given that the changes did not involve the same content. Not even sure what is so objectionable about the bit that was removed. The statement being removed was unsourced puffery stating "University status is an issue of prestige, increased government funding for research, as well as the ability to issue doctorate degrees" and deleting such content seems completely legitimate.--The Devil's Advocate _{tlk. cntrb.} 03:54, 11 May 2013 (UTC)

Result concerning Gilabrand

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

In my view, this request is procedurally unactionable because it contains no diff proving that Gilabrand was previously individually notified of discretionary sanctions in general and of Misplaced Pages:ARBPIA#General 1RR Restriction in particular. The wording of WP:AC/DS#Warnings mandates such a warning (it uses the imperative form "shall"), no matter how aware of these sanctions Gilabrand may in fact have been, or whether they have previously been sanctioned. A notification about the 1RR restriction in particular is needed because that provision is not a Committee decision, but has apparently been imposed by administrators as a discretionary sanction, such that the warning requirements apply to it also.  Sandstein  13:13, 10 May 2013 (UTC)

Looking at my old sanctions of Gilabrand, it appears that I made these on the basis of a 2008 notification of Gilabrand by PhilKnight. That notification should have been cited in the request. However, these earlier cases did not involve the general 1RR restriction, so we still need a diff of a prior warning about that specific restriction.  Sandstein  14:48, 10 May 2013 (UTC)

Is there some analysis of the second edit demonstrating that it is a revert? ErikHaugen (talk | contribs) 16:38, 10 May 2013 (UTC)