This is an old revision of this page, as edited by Coppertwig (talk | contribs) at 19:44, 9 August 2009 (→why an absolutist interpretation of "ban" violates basic WP principles, comment by Abd: Uncollapsing collapse box in last section). The present address (URL) is a permanent link to this revision, which may differ significantly from the current revision.
Revision as of 19:44, 9 August 2009 by Coppertwig (talk | contribs) (→why an absolutist interpretation of "ban" violates basic WP principles, comment by Abd: Uncollapsing collapse box in last section)(diff) ← Previous revision | Latest revision (diff) | Newer revision → (diff)Summaries of some comments by Abd originally at Misplaced Pages:Arbitration/Requests/Case/Abd-William M. Connolley/Workshop
extended argument by Abd, reviewing this issue with respect to this case
- (As summarized by Coppertwig)
Re proposal "Administrators blocks can be brought up for review by any editor":
Passing this would lead to more disputes taken to AN or ANI rather than less disruptive steps per WP:DR. Small-scale discussion by the parties could be disrupted by a third party taking it to a noticeboard, leading to mass decisions made by often poor-informed editors, voting based on prejudgment, distorted evidence, or shallow interpretations and biased arguments. There should be an RfC, which has proper process, before a ban is considered at ANI.
The situation between WMC and me could have been handled non-disruptively with, at most, use of an unblock template and possibly appeal to Arbcom (which happened anyway). If WMC had complained to a noticeboard about a non-disruptive edit by me, he would have found little support.
I took this straight to arbcom because a cabal-dominated RfC on WMC would have necessitated arbcom anyway, as in the JzG case. Proper process and examination of evidence at RfAr leads to different results than ANI, for example the NYScholar case in which a closing admin counted votes without paying attention to involvement.
Enric Naval, rather than pursuing dispute resolution with me such as discussion via a mediator, would prefer to go to a noticeboard to ask that I be banned. Arbcom should discourage this. -- Abd as summarized by Coppertwig 15:50, 9 August 2009 (UTC)
extended argument by Abd, reviewing this issue with respect to this case |
---|
|
Abd's analysis of the AN/I community ban discussion and his No Contest close
- (As summarized by Coppertwig)
It was mostly involved editors commenting. I cut the discussion short to minimize disruption since I knew it was going to Arbcom anyway. If the cabal had not confronted the issue in this case I would not have had to name them here either.
I am not contesting the one-month community ban. However, my "plea" was "no contest," not "guilty," and does not constitute evidence against me.
Uninvolved editors don't tend to comment early on, especially when there is a lack of evidence so they see nothing to comment on, and when there's been an early pile-on by editors with prejudgements, some uninvolved ones naturally go along with the flow.
I'm not canvassing for support in this case. The arbitrators will decide based on whether they are convinced by arguments, not by number of votes.
If I were annoying a lot of people due to an incompatible personality or something, Arbcom might have to act. But I named the cabal so that can see that the opposition is from an identifiable faction. Being part of a cabal isn't wrong; it just needs to be recognized. Abd as summarized by Coppertwig 18:09, 9 August 2009 (UTC)
Abd's analysis of the AN/I community ban discussion and his No Contest close |
---|
|
Relevance to this case, comment by Abd
- (As summarized by Coppertwig)
Re proposal "In enacting bans on an editor, administrators should take reasonable steps to ensure that the editor is notified of the block/ban and its duration."
There are several problems with an article talk page notification of a ban. User talk ensures the user knows about it, and also gives them a chance to reply in-situ, possibly with replies by others who watch their talk page. It also ensures that the user cannot deny knowing about the ban. Since I replied in-situ and was warned for it, I didn't receive a mere warning for my later one-character edit.
WMC not only refused to notify Hipocrite on user talk but editwarred with Rootology to keep any notice of this RfAr off, which serves the long-term goals of both himself and Hipocrite.
I've successfully used an article talk page notification as a gentler form of warning, suggesting that the user is free to act as if they haven't seen it. The editor reformed. Abd as summarized by Coppertwig 18:43, 9 August 2009 (UTC)
Relevance to this case, comment by Abd |
---|
|
why an absolutist interpretation of "ban" violates basic WP principles, comment by Abd
- (As summarized by Coppertwig)
No rule established on Misplaced Pages supersedes IAR, which, as stated, actually requires an editor to make an edit if they see a way to improve the encyclopedia.
"Interacting with that section" is not necessarily covered by a ban. For example, I was encouraged to continue with mediation related to cold fusion during my ban. Some are taking an extreme position that any consultation with banned editors is meatpuppetry. The purpose of bans is to prevent disruption, not to punish for past disruption.
Administrative bans are different from community bans. They don't need to be logged because the administrator would only be able to block for disruptive edits anyway. Self-reversion or bot reversion could be useful ways to allow the edits to remain in the page history as suggestions.
Contrary to what some might think, I support administrative bans, but under certain conditions:
- An identifiable administrator takes primary responsibility for them
- The supervising admin can also decide to unblock as conditions change
- The supervising admin should be uninvolved. Cooperation with the banned editor and use of mentors too can also help.
- An administrative ban can be seen as a warning that the admin considers the edits disruptive and is likely to block.
A ban based on a discussion is often better viewed as an administrative ban by the closing admin. It can be difficult to establish whether there was true community consensus; and maintaining communication and ability to lift the ban can have long-term advantages.
Edits to an article from which an editor is banned can complicate enforcement. Some are obviously harmless at first glance and some are not. I had proposed self-reverted edits and there had been no opposition to the idea. A self-reverted pair of edits is normally harmless and actually indicates intention to comply with the ban in substance. It's much more efficient than describing a proposed edit in talk.
The cabal did not consider harmless edits to violate bans, when SA was involved, but only when it was me. This is tragic, because self-reverted edits were successful in a case involving User:PJHaseldine in getting two editors cooperating with each other. Self-reverted edits are a way for a banned editor to begin to establish cooperation and success, and are harmless at worst. Abd as summarized by Coppertwig
why an absolutist interpretation of "ban" violates basic WP principles, comment by Abd
- IAR. No rule established on Misplaced Pages supersedes IAR. If an editor, no matter who, sees an edit that improves the project, IAR, as stated, actually requires -- as much as any rule can require us to do anything -- the editor to make the edit. This is why the attempts to strictly enforce the SA Fringe science topic ban, with respect to spelling corrections, was rejected by clear consensus. (It was only the disruptive intent behind those edits, independently determined, that led to his block. He was not blocked for ban violation, see the decision.)
- "interacting with that section" is not necessarily covered by a ban. For example, some bans allow the editor to discuss an article on Talk for the article, SA's ban was like that. In the case of my Cold fusion ban, I was encouraged to continue to participate in the mediation being conducted by Cryptic C62, and we were considering content there, and certainly this is a form of "interaction." Likewise, an editor may be allowed to make suggestions to non-banned editors. Note that there are editors here who take an extreme position that any cooperation toward improving content between banned editors and editors in good standing is "meat puppetry." Hence if I consult with an expert in the field of Cold fusion, Jed Rothwell, seeking to find sources -- and we have reliable source on him being an expert (Simon, 2002), in spite of the derisive comments that have been routine -- I'm accused of MP.
- The purpose of bans is to prevent disruption, not to punish for past disruption. How to treat bans varies with the nature of the ban; a community ban, determined by a consensus of uninvolved editors, is different from an administrative ban, which may be completely unilateral (as with WMC's original ban of me from CF), or based on a discussion with no uninvolved editor analysis or consensus, but closed by an admin based on the "weight of the arguments," or sometimes on !votes. A community ban is properly logged at WP:RESTRICT, and may be enforced by any admin without review of the original cause. Thus a primary concern in such a ban is ease of enforcement, to avoid useless debate over dead horses. Hence an administrator may presume that an edit is disruptive, if it violates a community ban, and any editor may revert such an edit on sight, with only one exception: the content being restored is illegal (i.e, BLP or copyright violation).
- Administrative bans are different. There is no provision for logging them at WP:RESTRICT, and that's quite proper, because an administrative ban is often little more than the judgment of one administrator that an editor's participation at an article is disruptive. The administrator may enforce this ban, but definitely not strictly, i.e., an administrator should never block an editor for "defiance" of the administrator's ban, but only for disruptive edits, hence there is no question of "harmless edits." Blocking for defiance is practically proof of involvement, a sign that the administrator has become personally involved. However, I can imagine situations where short blocks would be in order, where it was difficult to judge whether an edit was disruptive or not. And the goal would be to shift the behavior, and, in fact, self-reversion, which I discuss below, is a ready solution. Another solution, Beetstra will understand, would be bot reversion. An editor could be effectively banned from any arbitrary set of articles, or articles under a category, through the use of a bot which would automatically revert such edits. So an administrative ban would simply represent an edit to a protected page that controls the bot. We could avoid many blocks with this. Another way to look at this would be as a flagged revision process taken back another step. The editor would know, would have been informed, that all edits satisfying certain conditions would be reverted. That leaves them in place in history as "suggestions." And they would have an edit summary referring directly or indirectly to the reason for the revert.
- Contrary to what some might think, I support administrative bans, they are greatly preferable to community bans, but the conditions should be understood better.
- Every administrative ban should have a supervising admin, who can determine conditions and application. Ideally, there should be backup, a process whereby another admin can assume this position. Administrative bans are not community bans, to be enforced by just anyone, they are enforced, generally, by the admin who declares them. That admin is expected to understand the situation better than others, to be able to tell if an edit is disruptive or not, whereas admins without sufficient experience with the situation may not be able to judge as well. This, though, leads to the possibility of abuse, which is addressed through ordinary recusal rules.
- This concept of a supervising admin is actual practice; generally, an admin who blocks may unblock. An admin who deletes may undelete, even if there was an AfD preceding. One who decides may undecide, or may set conditions. Obtaining a "consensus of uninvolved editors" as required for a community ban can be a very disruptive process requiring wide discussion, which is why we have a system where decisions short of such a consensus are made by uninvolved admins, and then disagreements over this can be handled through ordinary dispute resolution process. Further, community bans are far less flexible, freezing in place an apparent consensus at one time, which may have been the result of what later can be seen as undue influence.
- The supervising admin should be uninvolved, where possible. Generally, bans will be more successful, long-term, if the cooperation of the banned editor can be obtained, and the use of mentors, volunteers, who can advise the supervising admin, the banned editor, and the community regarding a ban, should be encouraged.
- An administrative ban may be seen as a general warning: "I have decided that your edits to Cold fusion are disruptive, and that you have made so many of these edits that it is likely that future editing will also be disruptive. While I will not block you for useful edits, you are warned that your own judgment on this may be biased, and I reserve the right to determine that any particular edit is disruptive and I may block you for it. If you want to be safe from being blocked, do not edit the article. I do not have time to engage in debate with you; if you wish to have this ban lifted, get a mentor and ask the mentor to communicate with me about it, I assure you I will give it fair consideration, aimed at ensuring that your participation in the community is positive and productive. If you believe that my judgment is biased, here is how you may appeal this ...."
- An administrative ban based on a discussion is little different, unless the discussion was sufficiently extensive to represent a clear community opinion and shows a consensus of uninvolved editors, which is actually difficult to determine. To do a primitive analysis on the NYScholar ban discussion took me three or four hours. It's much easier to consider a ban as an administrative ban, which can be just as effective, if not more effective in the long run. (A ban which maintains communication and a process for having it lifted is less likely to result in disruptive socking.)
- Edits to an article from which an editor is banned can complicate enforcement. In fact, with a spelling correction, it is normally immediately visible that the edit is not disruptive; but with a more complex edit, determining if the edit is disruptive or not can be too time-consuming; hence there is a presumption that such edits may be reverted, and, as well, an editor editing contrary to a ban may be blocked, but if it was obvious that the edit was harmless at worse, this would be "stupid," as WMC called it in the case of SA's edits under ban (see my Evidence)
- Self reverted edits were proposed in the SA case, by me, as a solution to the complication of enforcement by "harmless edits." Before suggesting this to SA, I cleared it with Carcharoth, who thought it a good idea. SA rejected it, and some editors rejected it, but not as being ban violations, but the opposite, as unnecessary, presumably if it's a good edit, why revert it? I also proposed this at WP:BAN, and there was a little support and no opposition, but I hadn't attempted to move it into the policy.
- Unless there is something specially disruptive about it, a self-reverted pair of edits does not frustrate the purpose of a ban; on the contrary, if the edits are done as I suggested, with a summary including "will self-revert per ban," the edit represents cooperation with the ban, not defiance of it. It's easy to verify that a pair of edits has no effect, and the edit summary flags to look for that. Further, should an admin block an editor for such an edit, it should be easy to establish that there was no intentional violation of the substance of the ban.
- The cabal did not consider harmless edits to violate bans, when SA was involved, but only when it was me. My suggestion was rejected by ScienceApologist, quite likely, because his purpose in finding and making the spelling corrections was disruption, to complicate ban enforcement, not to simplify it. However, note, he was not banned from the topic, per se, and he was allowed to post to the Talk page, and therefore he would be, presumably, not discouraged from reading the article itself. The same was true for me; whereas much of the flap over my block (which I likewise did not take to AN or ANI) was based on a assumption that I'd been banned from the topic and had no business even looking at the article. In any case, editors who had been very clear that what SA was doing -- absent that showing of disruptive intention -- was quite acceptable, including WMC, suddenly became attached to "strict interpretation, banned is banned, period, end of topic."
- This is tragic, because I had suggested self-reversion to User:PJHaseldine, an editor whose topic ban (article only) I had supported. It reconciled him to the decision, because it still allowed him to efficiently "suggest" an edit. In order for that edit to be realized, he'd need the cooperation of another editor. And it worked. Self-reversion started a process where PJH and an editor who had supported his ban (not me, another) began to cooperate. When I was blocked for this, this is the editor that took the matter to AN, motive unclear. As to simple spelling corrections, the argument that the editor should suggest these corrections on article Talk, if permitted, or user Talk or by email, is preposterous. A self-reverted edit is a suggestion, ordinarily nothing more or less, a very efficient one. To describe a spelling correction would take so much time that I would not bother, and then the editor who decides to make the fix likewise has to find it.
- In general, allowing self-reverted edits leaves open a path for any banned editor to begin to cooperate with the community, and to establish a pattern of success. Or it's harmless at worst. It leaves behind no mess that needs to be cleaned up, and arguing against the edit, if nobody picks it up and takes responsibility for it, would be useless disruption. --Abd (talk) 22:26, 6 August 2009 (UTC)