Knowledge (XXG) talk:Arbitration/Requests/Case/Arbitration Enforcement sanction handling

1358:

you see fit. Of course that's not hypocritical of you; if I say "your experienced peers are saying X", that must mean "all those peers are more experienced than dearest Timotheus" or "all those peers always agree with Ncmvocalist" because what you say goes, no exceptions, no one else has a say, and no common sense is allowed to prevail because your sense is common to everyone. That they have disagreed with...no I shouldn't say that, because it would be undermining your unquestionable authority. My bad...I almost committed a mistake right there. I must remember if something goes wrong and I want to request the responsible users to take responsibility, I must be a Godking. But seeing that's not the case, I must shut up and act as if everything is perfectly fine. *Nod* *Smile* Way to go guys; we hold our heads high when we think about what your motion and what your roles in this circus has accomplished (as well as what will be accomplished in the future circuses). If an administrator makes a block, it cannot be modified because collaboration and mutual respect have been deprecated by a body of users in favor of process wonkery; what an accomplishment! And we have nothing but praise for the other unseemly approach this body of users are going to endorse: if someone changes your block, threaten to block them back and threaten arbitration...or better yet, don't even make the threat and run directly to us, the body, so we can desysop them in style even when you are to blame. Time to give out barnstars for such wonderful pearls of wisdom, and for passing it onto these brilliant administrators like Sandstein who received 50% support from a body of voters...no wonder nothing has gone wrong over the past few years...everything is just fine. :D :D :D :D :D <end: -->

3983:

depends on the circumstances, and I'm hesitant to give definitive answers to a wide hypothetical, but I think once an action has been decided and taken, it shouldn't be modified without a very good reason, and "I would've done differently if I'd made the call" is generally not in itself sufficient. The point of having admins is that we should be able to trust them to evaluate individual situations and exercise good judgment, as no two scenarios will be exactly the same. To 2A, arbitration enforcement actions are intended to be undertaken by a single administrator, and that admin takes full responsibility for the action. Preexisting consensus is not required, but good judgment is. If several other uninvolved admins, or uninvolved editors in good standing, are objecting to a sanction or have explicitly declined to place one, that doesn't prevent someone else from doing so, but it is at minimum incumbent upon an admin placing a sanction to carefully consider the objections others made before doing so. If the editor who has been sanctioned does not believe there would be a consensus of admins for the action in question, that editor may appeal, and at that point, consensus of admins (or arbitrators, if the appeal reaches us) would be measured during the appeal. The fact that the editor in question here (we all know that this hypothetical isn't too hypothetical, I believe) chooses not to take advantage of the process doesn't change what the process is.

1197:@ Elen, the mere words of Dreadstar reflect a different picture in my opinion. He is telling y'all (ArbCom) that administrators are prepared to be absurdly sanctioned if ArbCom are going to directly or indirectly authorise a single particular administrator to misuse the rulings and site policies to the detriment of the project. I'm not really commenting on Ludwig2/QuackGuru when I say that. What I am saying is that other admins (including some AE patrollers) have practically never encountered a situation where there blocks or sanctions need to be reversed in this fashion; EdJohnston's name pops to my mind as a good example. However, if a single administrator repeatedly finds his actions being subject to concerns, disputes, or even repeated reversals, that is a sign that this Community has serious concerns about that user's fitness as an administrator; whether he has the judgement and trust required of an administrator. This is not the first time this has happened with Sandstein...this is not even the second time...goodness knows if we're nearing a two digit number. To worry about whether AE blocks maintain their image is far less of a concern than an administrator imposing a block in response to a request for clarification. 1340:

disputes and that it won't invite any further disputes; I (and I know many people would agree with me) think you have no clue what you are talking about if you insist on that. The gravity of my concerns have been well known by the Committee and more than enough members of the Community. I've not hesitated to state those concerns in the relevant noticeboard discussions - including a most recent one concerning *surprise surprise* this Committee. In fact, as I recall, another administrator and a functionary endorsed those concerns despite your noted absence from that discussion. If recent enough feedback from a self-created administrator review has dismally failed to produce the desired results, then the purpose of the RfC/U was already served in that form (much like a recall RFA). I don't entertain absurd notions of bureaucracy for the sake of bureaucracy, but if you do, maybe the 4 comments I quoted above have some application in regards to you as well as Sandstein. I suggest you read what your experienced peers are saying on a practical level instead of having such unrealistic optimism on theory alone - Moreschi, HJ Mitchell....

3312:

is, in my view, a zero-tolerance, black-and-white one. That's because it's the Committee's job to make these kinds of hard decisions and to assume the responsibility for them, including for how broad the sanctions are phrased. Expecting enforcing admins to exercise some degree of discretion is just a form of passing the buck. If you choose to topic-ban a popular, well-networked user with many friends, you must expect - as has happened in this case - a degree of drama or even harassment to occur in each case of enforcement, no matter who takes action or how. I think it's not fair to expect the admins who volunteer to enforce your decisions for you to take shoulder this load by claiming that it's up to the admins to exercise some sort of discretion that no policy provides for. Instead, the Committee should assume its responsibility and say, yes, we decided to ban this user, broadly construed and so forth, and we (and not the admins) are responsible if they are blocked whenever they do something topic-related, no ifs and buts.

3077:

to reverse that action: unlike a normal admin action, consensus would be required to overturn the AE action. However, when a discussion is already underway, and there is no consensus on the blocking (or a preliminary consensus not to block), it seems unfair to unilaterally make the decision to block, and then insist on a new discussion to overturn it. If it really is acceptable to do that, could not an admin with an opposing viewpoint decide to "officially warn" someone, or block them for 1 second, and then close the AE request, preventing any further blocking without a brand new discussion? (I'm not advocating that, of course, just pointing out that it kind of follows from the answers to 1A). AE enforcement is meant to streamline things, but in the scenario described above, it's being used instead as a trump card. It shouldn't be. If there is an ongoing discussion at AE with differing viewpoints on blocking among the uninvolved admins, an admin shouldn't wade in and block before a consensus develops. --

2404:

because he wasn't getting his way. He did this a few years ago as a revenge/sabotage/scorched earth tactic. Very odd!) Ludwigs2 often sides, usually in tandem with Hans Adler (twins?), with pushers of pseudoscientific POV, although they often have some good ideas and can be collaborative and constructive when they aren't carrying a grudge, so I hesitate to consider them to be pushers of such POV. They are just enablers. QG engages in stonewalling and IDHT tactics which have often caused many months of disruption over a few words. I am still amazed that it hasn't been possible to get him banned for a very long time. Ludwigs2 uses very intimidating and threatening tactics backed by an attitude of (false) superiority, even promising/threatening to cause sustained warfare if he doesn't get his way "because he's right", and he does it. It's not a careless or idle threat. This isn't the first time.

1635:

infraction was at AN. If AN is covered under ArbCom sanctions, where do users come to hash things out? You can discuss an issue outside the context of an ArbCom ruling without invoking sanctions. That is obvious: are we going to use ArbCom sanctions for infractions in user talk page discussions too? Because of this, Sandstein's block was not covered under Arbitration sanctions, and Dreadstar's unblock was not reversing an ArbCom sanction. Just because an administrator says that something is under ArbCom, doesn't mean it actually is. There is no reason for other administrators to treat a block which is clearly outside of ArbCom sanction as if it's under ArbCom sanction merely because the blocking administrator invokes ArbCom. Therefore, this request for arbitration is inappropriate; however, you should consider advising Sandstein not to abuse ArbCom sanctions in the future.

453:). It is unfortunately to be expected that this leads to much grumbling by the editors so sanctioned and their friends. But as far as I recall, none of the (probably) dozens of the AE sanctions I have imposed have ever been overturned by the Committee or by the community on appeal, and I submit that this is a more useful benchmark of my enforcement practices than any individual disagreements. While it is a statistical certainty that some of my decisions (like those of most people) were not optimal, I have always attempted to act as fairly, predictably and as close to policy as possible within the time and resource constraints imposed by the volunteer nature of our work. To those who believe that the job could be done better, I say that they are very probably right, and invite them to stand for administrator and do some of this better enforcement work themselves. 1239:"Administrators are generally prohibited from reversing or overturning (explicitly or in substance) any action taken by another administrator pursuant to the terms of an active arbitration remedy, and explicitly noted as being taken to enforce said remedy, except: (a) with the written authorization of the Committee, or (b) following a clear, substantial, and active consensus of uninvolved editors at a community discussion noticeboard (such as WP:AN or WP:ANI). Should an administrator overturn an enforcement action outside of these circumstances, the Committee will review the matter and determine whether the action and reversal was warranted. Appropriate sanctions, from reminders and admonishments, up to and including desysopping, will be considered by the Committee for administrators who have taken an action which was not warranted in the circumstances." 1727:

Administrators should be free to use their own intelligence without fear of arbcom jumping down their throats; by establishing discretionary sanctions, ArbCom has effectively said "hands off now, we leave this to you". There are also various logistical problems with the policy as it stands - ArbCom will not normally respond quickly enough to enquiries before anything but a lengthy block expires (or this was the case historically, anyway), and as for community consensus - good luck divining anything of the sort at the dramaboards, with partisans from all sides jumping in like rabid wolverines. Sysops should be encouraged to actually talk to each other and work things out between themselves, and only if lengthy discussion proves absolutely fruitless should the rulings of higher authority be sought.

1216:. The amount of effort + length of time it takes to address the block or administrator concerned, under the alternatives, is unreasonable. For matters handled by the Community, unblocks are considered somewhat of a priority because it has never endorsed the idea that admins should be permitted to perpetuate that sort of damage. However, the Community and ArbCom seem to be divided due to the archaic wording in the SV motion. That is, any blocks imposed under AC's decisions are a priority; unblocks are subject to red tape and therefore not a priority. The most ironic part is that the Community and ArbCom seem to be in agreement on this: "AC's decisions are to be enforced appropriately/effectively and that the authority of those decisions should not be undermined by individual admins". 3508:

administrators who like to mete out sanctions regardless of the state of the discussion of a request (i.e., to sanction even in situations where a preponderance of administrators do not believe a sanction is appropriate) or just as seriously to interpret the "consensus" of administrators as supporting sanction even in situations where almost all other administrators would say there was either (a) no consensus or (b) a consensus not to sanction. Arbitration enforcement is in some ways even more powerful than arbitration decisions themselves, because at an arbcom case there must be a clear majority supporting a sanction before it can be placed. My read of the two situations described above is as follows:

3779:'s statement, I see choosing not to act is as much a part of the role of an administrator as choosing to act is. If there is consensus that a block is not warranted then that should have the same protection as consensus to block does. If consensus is unclear then absent an emergency situation or being privy to private information (both of which would need to be explicitly flagged as such) then no single admin should issue a block until it is clear that a block does have consensus. A useful analogy for me is that an admin closing an XfD as "keep" is acting in exactly the same capacity as if they were closing it as "delete", even though only one outcome requires using the administrative toolset. 1001:

but the worst political attacks - they don't get the result they are looking for, and things escalate as they try to fight the war with me harder. If I were more saintly than I am I could do a better job at keeping things cool - I'm more than wiling to admit I get periodically frustrated by the anti-fringe shenanigans and have unpleasant displays of temper, and that I can be an arrogant, stubborn ass when I get my goat up - but I don't think it's reasonable to suggest that I need to be far more saintly than everyone around me just to keep myself from getting blocked, and with respect to some editors no amount of saintliness that I could showed would be satisfactory regardless.

3815:

means to stop disruption quickly without getting bogged down in long discussions. Seeking consensus (and, of course, following it) is merely advised and not made mandatory. It's certainly possible to argue that acting without seeking prior consensus and acting against an emerging consensus are different things, and I agree, but this distinction is not supported by policy at the moment. That said, an admin following best practices, for instance, would not have blocked in the circumstances, but the block is neither an abuse of power nor invalid. Of course, should a sysop make a habit of acting against consensus, arbcom would consider asking said admin to stop doing enforcement.

1062:

the mistake of responding to what he thought was the substance of Sandstein's complaint, rather than the surface. (Both at AN and on his own talk page.) Instead of engaging in discussion and making clear to Ludwigs2 that as far as he was concerned the surface was the substance, Sandstein blocked Ludwigs2 55 minutes after the clock for his two-hour ultimatum was started, i.e. 65 minutes before the ultimatum ran out. Predictably, this arbitrary and draconian action has led to editors such as Short Brigade Harvester Boris, who is generally very critical of Ludwigs2 and had contributed to the derailing of his AN report against QuackGuru, finding themselves defending Ludwigs2.

2288:

topic-wide discretionary sanction on all editors, present and future. This shifts the responsibility of deciding which users need to be blocked or topic banned to AE. Admins at AE have far less evidence and less opportunity to discuss an overall case than ArbComs members do. Discretionary sanctions threaten any editor who participates in a sanctioned topic and may be counter-productive by discouraging the participation of disinterested editors. I urge the ArbCom to reduce the reliance on discretionary sanctions, and to rely more on specific remedies tailored to the problems found in the evidence presented during the ArbCom cases.

3208:

enforcement just by having enough people show up that any consensus becomes unfeasible to establish and timely action impossible to take, as is regularly the case on community noticeboards. Second, this would in effect compel admins who are interested in arbitration enforcement to take action as soon as possible without waiting for discussion, which would likely impair the quality and acceptance of enforcement actions, and by extension the effectiveness of this Committee's decisions. I would prefer that not to be the case, because I think that the discussions among the admins who regularly work at AE are often very helpful.

2073:

our dispute resolution process. Thus it is essential that disputes over AE action be (1) kept to a minimum and (2) resolved in an orderly manner. The current version has both of those benefits. Ncmvocalist's version has neither. Of course, the present system may be occasionally and marginally unfair to some editors, who received a stronger sanction then most other administrators would have imposed, or who had to wait while a discussion comes to a consensus to unblock, but occasional and marginal unfairness, I think, is an acceptable price to pay for the much-needed finality, at least in cases where arbitration is necessary.

1414:

unless he has a accumulated a special history of his/her own, and even then, it falls on everyone else to draw that history for you. That is not good enough in this era. You should be willing to review the blocks and unblocks that are enacted in ArbCom's interests, particularly when they are simultaneously said to be in the interests of the Community. Those that are worthy of being addressed in that way should be (they should not be addressed as such merely because of de facto authority handed out by the archaic motion from a previous era). If something is suboptimal, or only partially justifiable, that needs to be said

3517:

in the discussion of the request. (The reasonable parallel would be XfD.) Administrators who regularly apply sanctions when there is no clear consensus are also subject to the sanctions mentioned above. It is not helpful to have hardliners applying sanctions that don't have at minimum more than a majority support of uninvolved administrators, either for the reputation of AE itself (it's not appropriate to have a situation where it doesn't matter what others say if Admin Y is going to do what they want anyway) or to ensure that there is a multiplicity of administrators participating.

4048:

they are doing will be considered the correct course by the community. It is irrational to say that the committee deals with enforcement by letting anyone give sanctions at their own pleasure. Rather. the committee elevates on the assumption that others will give sanctions properly. For any admin in any circumstance to take an admin action without a good faith belief that it will have consensus is pointy at best, and a abuse of discretion at worst. As an admin, I have always thought that this was implied by the policies on these sanctions just as they apply everywhere else.

3882:. They can ask their colleagues what they think but they're not bound to take those opinions into account. There is no supervote because no vote is taking place. The enforcing admin is entirely responsible for their action and if they get it seriously wrong (or make strange calls frequently) they may be subject to sanction themselves. This will sometimes lead to actions which are controversial and sometimes heavyhanded but the issue then is whether the admin action was reasonable (and the DS procedure sets out guidelines on this) and not whether there was consensus for it. 3725:

sanctioned editors will steer clear of boundary-testing. Those may be valid arguments for not giving already-sanctioned editors the benefit of the doubt when they are causing problems. But there are also disadvantages to automatically blocking without considering the circumstances, including the creation of a culture where minor, fleeting, and relatively harmless transgressions become the subject of lengthy debate and controversy, compounding the "battleground" atmosphere that has often led the Committee to impose sanctions such as topic-bans in the first place.

2710:

block even if it is agreed). Administrator Y unilaterally imposes a block (where there is clearly no pressing need to), and did not obtain prior affirmative consent/agreement from administrator X, or at AN, AE, or here for imposing the block. If there is a division in opinion at AE regarding the appropriateness and duration of a block, has the committee indicated to its admins that they can unilaterally impose a block anyway? Does principle 3.1.2 only apply to discretionary sanctions? Or does that principle apply to requested enforcement of case remedies too?

1805:@WJBscribe: AEBLOCK merely requires adequate time for a consensus to emerge before unblocking. If an admin mistakenly applies AEBLOCK, a consensus to that effect would emerge at ANI within a few hours—the admin wanting to unblock simply has to wait (and if they will be absent, they can forget the issue because another admin will unblock once consensus is clear). If the block is so egregious that unblocking cannot wait for half a day, the blocking admin will be sanctioned in due course. No benefit will come from an admin choosing to override the blocking admin 3204:". Even this does not require admins to follow or look for consensus, but only advises them to listen to the opinions of other admins (which they may then choose to disregard). As far as I know this was an intentional decision by the arbitrators who drafted these rules. Any discussion that does occur is merely an aid for coming to the right conclusion, but it is not envisioned by any rule to be a consensus-forming process. Discussion and consensus become relevant only at a later stage – in an appeal, either to the community or to administrators. 1272:"WP editors have a policy they should follow. WP:OWN. This same policy should also apply to administrative actions. We don't "own" blocks and protections. If someone questions, or "edits" an admin. action - then it's possible that the edit or change was done to improve the project. Talk. Discuss. Become familiar with the folks we're working with. Blocks should be a last resort, and only to prevent some sort of distruction that's going on. Please step back for a time, consider what others are saying, and think about the big picture." - Ched 3044:

consensus. I have also seen him full on defer to other admins who disagree with him at AE when closing a case. His actions in the related AE surprised me. I think this is the first time he has pushed through his preferred action in the face of what was arguably a developing consensus for a simple warning. I'm not saying he was wrong, Sandstein is usually technically correct (the BEST kind of correct!), but it is curious that he would act... Out of character, I guess? I'm not sure how best to describe it.

2017:

that any other points will bide until they can be dealt with; I am reminded of my courses in philosophy. I continue to have a vast respect for Sandstein's judgment at AE and elsewhere, but I think that in this instance there has been a misinterpretation of the response to the original notice. Reading it in that light, it does not appear to be a recalcitrant refusal or a promise to stick to his guns at any cost, but rather as just one small step in an extended process of working things out. -

2936:'s comment accurately summarises the situation I am seeking clarification in relation to, and what the principle intended to address). Unlike the example in Roger's comment which may have been contemplated in initial AE design, the situations like what I've described in 2A have gradually arisen in more recent years because of a few very specific AE active admin who have not got the message fully, or who are often being misguided (perhaps by users with their own agenda). Please 3854:

of the tools or making an action explicitly reserved for administrators. A refusal to act cannot therefore be an administrative action as no administrative action has taken place. As a hypothetical if a bunch of people are hurling abuse at each other and furiously edit-warring, and - for whatever reason - an administrator explicitly refuses to act in respect of any of them, are each of them immunised against blocking? The common sense answer has to be "Certainly not".

3825:, yes, Sandstein, admins are allowed to exercise their best judgement when enforcing an arbcom-imposed restriction; sometimes, a block will be needed, others a warning will suffice and others the violation may even be too inconsequential to warrant any action and could even lead to a boomerang on the OP. We trust administrators, that's why we have tasked them with enforcing our decisions, we don't want you to become automata. Your common sense is valued. 3717:" (Emphasis added.) As I said, in many, perhaps most, cases an editor topic-banned from X who edits on X should indeed be blocked. However, enforcement of ArbCom sanctions, like sane enforcement of anything, requires the guided exercise of judgment and discretion. No matter how carefully the Committee crafts its remedies, there will always be borderline cases in which editors and admins can disagree in good faith as to whether the topic-ban applied. ( 1310:, the fact is you cannot impose blocks in the guise of something else - be it AE or otherwise. If something does not fall under AE, but you act as if it does, then you are in the wrong and your pride will bear the consequences. If you want to block someone for inappropriate pseudoscience advocacy, you cannot act as if the block is merely for something that can be interpreted as threat by some people, otherwise the outcome will be no different. 1124:, there are more rigid rules for unblocking which are clearly set out in the blocking template. Whatever the merits or demerits of the block, Dreadstar did not follow those rules, although he was evidently acting in good faith. Even if Dreadstar broke those rules, I do not believe that warrants an ArbCom case. There is an ongoing problem with Ludwigs2's conduct on wikipedia. He must surely have been aware that if he wished to edit 1007:

mind to cannot unilaterally use their powers to dispose of editors they have unilaterally decided are fringe editors), and adding some teeth to behavioral policy (so that anti-fringe editors cannot consistently violate civility and talk page guidelines with impunity, as they currently do now). Otherwise, we have what we have: I will obviously try to be more saintly, but no matter how much I try it will solve nothing.

2143:

editors, found the charges to be "clear". Sandstein invented his own process and then violated it by blocking before the end of the period he granted. Process was violated and accordingly the block was void. Also the penalty was disproportionate. Bringing the matter here seems petulant but I don't want anybody to be desysopped. Arbcom should be addressing the substantive issue: the obstructive editing of the

818:. In the case of an obviously bad block like this common sense should dictate immediate reversal, and since the blocking admin in such a case clearly demonstrates a lack of common sense simply for having made the block in the first place, it's up to other admins to redress the issue. Tying their hands serves the project no good; It simply serves to perpetuate an unjust block for no productive reason. -- 3287:, no matter what the circumstances may be. If that is not so, then you should tell admins which criteria they should use to decide whether or not to take action. I caution, though, that this (and any added consensus requirements) may have the effect that your sanctions against popular and well-networked users may be enforced much less effectively, if at all, than your sanctions against other editors. 1269:"I agree with what User Tznkai has advised, the wiki is a place that need rules and guidlines and essays and all but it is not all so clear cut, as he says, the nuances are also important to consider. The wiki should not be a cold hard place, wield the tools with a degree of compassion, take a step back for a couple of weeks and remember that you are an editor and an admin." - Off2riob 1512:(after edit conflicts with kww and Arthru Rubin) I've not been involved in any way shape or form with this, and I have no opinion regarding whether the block was justified or not. However, the block was made, and it was clear to all concerned that it was an AE block. Whether it should have been discussed first, I have no opinion and it matters little - the fact is that it wasn't. 2039:

implied in some arbs' accept votes) would be yet another case of the committee taking its unhelpful "Da Rules" approach. Clarification on when an admin can claim AE status for a block would be a good use of arbitration, more useful, in my view, than looking at the behaviour of the parties here. And if we must look at behaviour, I think we need a fair look at all parties.

2068:. I disagree with Ncmvocalist that any change to AEBLOCK is necessary. Despite their repeated aspersion casting at Sandstein, both in this request and in some other previous discussions, Ncmvocalist has inexplicably failed to bring this allegedly long-term improper behavior to the attention of the committee or the community via the proper channels. As far as I can tell, 1266:"Get out of AE and DR in general for a few weeks. Take a proverbial walk around the block. You're very by the book and you seem to have difficulty approaching situations with nuance when it is needed. Admin intervention has to be the means to an end, and that end has to eventually be content creation, and I'm not sure if you see the link in your own actions." - Tznkai 3677:

felt, at some level at least, that the block was justified. If I was subject to a block I felt was unfair, I think I would make an appeal for the case to be examined, to continue editing, but also to try to prevent injustices in the future from occurring. If I felt the block, and the duration of the block, was at some level justified, I would probably not bother. --

2700:

further breaches). Administrator Y did not obtain prior affirmative consent/agreement from administrator X, or at AN, AE, or here, for imposing the further block. Can the committee please confirm in those circumstances whether administrator Y's further block would be considered a modification of administrator X's block, and that such an action is unauthorised?

285:, albeit without addressing their threat. Moreover, Ludwigs2 is an "editor working in the area of conflict (defined as articles which relate to pseudoscience, broadly interpreted)", as per the discretionary sanctions remedy, and therefore discretionary sanctions can be applied to him in reaction to threats made in connection with that topic area. 252:, to undo my AE action. I therefore respectfully ask the Committee to take the steps it considers appropriate to prevent Dreadstar from continuing to unilaterally revert AE actions. At the same time, I welcome any advice or criticism by the Committee about whether my AE action was appropriate or what other action, if any, would have been better. 4007:

purely technical violation should necessarily be sanctioned. I recognize this as a possible problem -- there have been instances of an ed. first making a purely technical edit, followed by one that is a little more substantive, and so on. An admin is expected to judge the situation, and see if a pattern is developing that needs to be stopped.

1281:"Overall, I got the feeling that you thought you were in charge of everything and no one was going to tell you any different. And if someone had a different opinion, you'd just threaten to block them. Less talk, more listening would be a great thing. I would lay off the block button for a while. The power seems to be going to your head." - Tex 3818:

time, an admin who decided to impose a 1-sec. block to prevent others from imposing harsher sanctions would clearly be trying to game the system and could probably be sanctioned himself. My personal feeling is that the only action which qualifies as admin action, in these cases, would be closing (and hatting) an AE thread without action.

1087:(3) In the climate change arbitration, Arbcom apparently came to the conclusion that the main problem was severe polarisation, and that the pro-science side was to a large extent responsible for it. While I do not agree that this was the best point to address for solving the entire problem, I do see it as one valid point among several. 3995:

in an application, I'm hesitant to say they cannot just becuase it's possible there will be consensus against them. The onus definitely relies upon individual administrators. I'd advise that in areas where a consensus is in the process of forming, or has formed, against the administrator action, due caution and restraint be advised.

2058:

opinion of a single administrator, can be "boldly and decisively" overturned; a block that is not a "bad block" in the eyes of any administrator can only be overturned by consensus - but if no administrator thinks that it is a "bad block" there's no realistic chance that there will be a consensus, clear or otherwise, to overturn it.

3721:) There will be instances in which an editor may believe in good faith that his or her edit was permissible, and when told it wasn't, will accept the ruling and sin no more. There are editors who faithfully abide by a topic-ban for a long period of time, making useful edits in other areas, and then stray in an isolated instance. 323:

and agreed to withdraw the comment. A topic ban would have been too broad, as the problem here did not involve article editing, and an interaction ban would almost certainly have had to be applied to both editors in order to work, but there was no actionable case (as I saw it) for an interaction ban against QuackGuru at the time.

2872:

if uninvolved administrators (plural) opine and determine a breach of a topic ban in 2A is minor that it does not warrant a block (or that a block is going to be ineffective), it doesn't matter; any admin who wants to block and first imposes a block will have a supervote. Is that correct? And is that what you want/wanted?

1145:

usually have been related to fringe science or pseudoscience. Editing restrictions have been proposed for both these editors, but have not so far found approval from the community. A typical posting on ANI by Ludwigs2 occurred in October 2010, following postings on several other noticeboards. It concerned the article

2093:

on the most recent election, which does not seem to be the kind of massive community discontent you appear to be portraying. (I should confess that I have conveniently forgotten to mention that every single one of those 50%+ of voters are either uninformed, misguided, just plain dumb, or Sandstein himself.)

4085:

The first part seems to be easily answered, so I will defer to my colleague's comments on it. As for the second one, my opinion sits where NativeForeigner's does. If an administrator is confident, acting in good faith, and has a basis for making the block, then I wouldn't say it should be prohibited.

3853:

Placing a fresh block for conduct that has already been dealt with - at least on the face of it and absent a rationale from the second admin - seems to me to be gaming the prohibition on modifying another administrator's blocks. On the second question, what distinguishes administrative actions is use

3676:

Since this seems to have been instigated by a particular case, and there has been much discussion about it, I would like to make a point about said case. No appeal I saw was made against the block, except for a frivolous suggestion to have the block extended by a day. This suggests that the defendant

3344:

So the instant problem of Sandstein's "overly literal interpretation of the remedy with no regard for its spirit" - and indeed his history of such narrow and binary interpretations, not unusual amongst the Knowledge (XXG) demographic, really pales into insignificance with the systemic problem that we

3207:

Second, as has been mentioned above, requiring admins not to act in the absence of a consensus to act would have two effects that would severely impair the effective enforcement of the decisions made by this Committee. First, sanctioned users who have many friends, as seems to be case here, can block

3076:

I'm glad to see this has been asked already, I was about to. I think the answers so far to 1A are pretty reasonable and uncontroversial. I'm more interested in Arbs' answers to 2A. Normally, an admin can take unilateral AE action without waiting for a discussion, and then the normal AE rules apply

2871:

Correct me if I am wrong, but it seems to me you are saying principle 3.1 of the case only applies to discretionary sanctions, and does not apply at all to requests to enforce individual editor topic ban case remedies enacted by the committee. That is, in the 2A hypothetical, you are saying that even

2814:

tendencies at AE (be it as far as the noticeboard requests or actions he takes at those requests), I think the community is entitled to hear that from you directly, rather than his comments on arbitrators 'deliberate intentions'. Alternatively, if previous reminders or indications have not worked for

2403:

The behavior of both QuackGuru and Ludwigs2 is often problematic. QG is generally a scientific skeptic, but gives them a bad name because of his abominable editing tactics. (I say "generally" because he has been known to suddenly change "sides" and aide fringe editors in gross policy violations, just

1966:

Disclosure: I edit heavily in the pseudoscience topic area, and find both QuackGuru and Ludwigs2 at times frustrating as collaborators. I find it refreshing that the block/unblock comments at AN do not break down along traditional battle lines. Unless some pattern (presumably as a percentage of admin

1726:

Given this, I see no reason why areas subject to discretionary sanctions should not be dealt with in the usual manner. If you find a grossly bad block (no comment on this one, BTW), you normally would overturn it - and no, that is not wheel warring, that is BRD applied to sysop work, as it should be.

1634:

Let's acknowledge that Ludwigs' statement was inappropriate. Let's also acknowledge that the block was inappropriate for reasons stated by others above. We have to consider the actual situation surrounding the statement by Ludwigs. This block was not covered by the arbitration sanctions, since the

1589:

On a more general note (without casting aspersions on either part in this case), arbs, I would urge to re-examine the idea of discretionary sanctions and the rules about reversing AE actions. If you want admins to clean up the mess left after big arbitrations cases, you can't tie our hands behind our

1006:

If you want to solve this problem, IMO, you're going to have to revisit the pseudoscience arbitration and take some actions to force the anti-fringe editors out of their battleground mentality. That will mean pulling some of the teeth from the arbitration rulings (so that administrators who are of a

501:

This false assumption is understandable in an admin who does not have experience in AE situations. But exactly for this reason you should have heeded the clear instructions of the Committee, as left in a template on the blocked user's talk page, not to unblock (on pain of possible desysopping) except

4047:

consensus, but all admin actions are based upon the assumption that they would have consensus. This is especially true of the particularly drastic ones at DS. Especially because they require an explicit consensus to reverse, it is reckless for an admin to use these without being quite sure that what

3843:

This is perhaps the least hypothetical hypothetical I've seen in a while. Blocking after a prior block has expired strikes me as double jeopardy in the absence of either a fresh violation, or a consensus of uninvolved editors that the editor actually needs a harsher block (the situation that comes

2958:

discussing the best way to handle the request, I don't believe this principle or the procedures intended to (as Roger's statements suggest to me) deliberately let an admin make a unilateral block and cut the desired discussion off where there were no genuine supervenient circumstances requiring that

2709:

An administrator X refuses to block an user after reviewing a complaint alleging a breach of a topic ban (which was imposed as a case remedy). Other administrators opine on the issue at AE and there appears to be division regarding the appropriateness of any block (and the appropriate duration for a

2699:

An administrator X blocks an user for a period of time after reviewing a complaint alleging a breach of a topic ban (which was imposed as a case remedy). After the block has expired, administrator Y imposes another block of the same or a longer duration for the same complaint (and where there are no

2467:

Very roughly, I estimate that those problems are 1) a result of admins dealing with similar problem for years, and burning out, thus preferring simpler solution based around "making examples" and "putting God's fear into" all concerned and 2) dominance of US legal/juristic mentality, which (roughly)

2321:

In other words, this was an unfortunate confluence of individuals and circumstances that hardly merits the attention of Arbcom. The only issues even vaguely worth addressing are how far admins can stretch claims that they are acting under an AE regime (it seems to have been almost an afterthought on

2103:

I'll pass over the "experienced peers" part, since I'm not quite sure how you arrived at the conclusion that HJ is more "experienced" than me with respect to AE. Perhaps the new definition of "experienced" is "people who agree with Ncmvocalist"? In that case I freely confess that I'm "inexperienced"

2092:

you referred to has 15 editors who opined that "Sandstein's approach to what he perceives as disruption is adequate overall", which, of course, you conveniently forgot to mention - not to mention more than 50% of voters who bothered to express an opinion thought he should be elected to the committee

2016:

In my experience working with Ludwigs2, I have come to the conclusion that he approaches talkpage posts in the manner of realtime conversations rather than posting completed thoughts. He approaches consensus by dealing iteratively with small pieces and feelers that may bear no fruit in the assurance

1991:

would be just as disruptive there as at the original article; similarly, incivility at usertalk or AfD would be covered if directly stemming from a pseudoscience-related dispute. In the case of BLP, broad applicability is absolutely clear. I am on-again-off-again involved in patrolling AE, and would

1665:

requires much more significant criteria to be met before an unblock can take place - including a more significant consensus. If a very few editors can get together with repect to potentially borderline cases, and claim that because they think it wasn't taken under AE, they can reverse it without the

1399:

The Wild West is unavoidable while some admins put cowboy police hats on; the only thing that can be done is to address the inherent cause (and not just because of a sweeping rule which limits itself to a single a outcome). That is, sometimes it is the block which is the cowboy action; simply ruling

1357:

Oh...how silly of me for not acknowledging your authority. You, dearest Timotheus, like Sandstein, have evidently been given ultimate authority on Knowledge (XXG) by AC to do whatever you like...you can ask others not to misrepresent your comments while essentially misrepresenting others comments as

1090:

Similar mechanisms are at work in the general area of pseudoscience, but in a much purer form. The main difference is that in the climate change area we had actual scientific experts who were respected by the pro-science side. General pseudoscience-related discussions, however, are usually dominated

1061:

It would never have occurred to me to see this as a threat. Sandstein, however, contacted Ludwigs2 on his talk page, asked him for a reason why he should not block Ludwigs2 for making a threat, while pointing at his statement in the AN thread where he gave more details. Ludwigs2 then apparently made

1047:

V, you did not provide V. You cannot provide V. Will you stop adding OR?'" (completely made-up example for clarity). Normally this would be easy to deal with, but not if such a user is getting massive support due to (3). Ludwigs2 described a natural reaction, the aim of which is to gradually get the

1000:

The long and the short of it is that there are still a number of editors and administrators fighting the old pseudoscience wars. They keep trying to fight that war with me, but - because I'm not the pseudoscience advocate they think I am, am generally rational, and am usually capable of evading all

985:

I make no bones about confronting people on errors in their reasoning. I'm not always right, but I am (as a rule) rational and reasonable, and I expect that other editors be (as a rule) rational and reasonable as well. In my view the final authority in a consensus discussion is reason, which means

977:

For what it's worth, here's my opinion on why this issue escalated to this point this quickly. Much of this has to do with the way my personality and skills interacts with the still-simmering fringe and pseudoscience issues on project. The result is that I am often (much to my chagrin) a flashpoint

785:

No, I'm not asserting anything as strong as ineligibility due to prior interactions. I'm merely noting that he and I have had words in the recent past, on an editor-to-editor basis. It was nothing particularly significant, but it was sufficient to demonstrate a level of personal animosity. My main

728:

There was no trouble on the article talk page, no trouble on the article itself, I was engaged in a RfC about removing synthesis from the article (so I couldn't possibly have been pushing a viewpoint): In short, there was no actual, foreseeable, imminent, or even theoretical threat of any unpleasant

573:

This request is as hasty and ill-considered as the original block. Quite apart from the fact that the block was disproportionate to begin with, and that it was even more disproportionate to claim AE protection for it, it also had several technical problems (insufficient warning, failing to adhere to

322:

As to why I believed a short block was more appropriate than a topic or interaction ban: I considered the block to be the most appropriate measure to prevent Ludwigs2 from making such threats in the (near) future. I would have lifted the block myself had Ludwigs2 shown that he understood the problem

3994:

The eventual action is of course appealable and beholden to consensus. An administrator, if they see a consensus against applying a particular sanction, they ought not apply it because presumably such AE an action would be undone. However, if there is disagreement, and an administrator is confident

3817:

Concerning what constitutes an admin action, well, this is trickier. In general, declining to act has generally not been considered an admin action and, so, another admin may decide to act without violating the prohibition on modifying someone else's action without consent or consensus. At the same

3516:

2A) If multiple administrators have opined and there is no really clear consensus for applying sanctions (or no clear consensus on what sanction should be applied) then sanctions should not be applied. The assessment of consensus should, ideally, be done by an administrator who has not participated

3282:

result in enforcement action, then the Committee should articulate this standard explicitly. I currently work on the assumption that if you topic-ban somebody from "X, broadly construed", this means that you expect this editor to be blocked in each and every case in which they make a X-related edit

3053:

to Roger, would you consider closing an AE request with no action an administrative action? It does not require use of the tools, but it is something only an admin is allowed to do. If so, does it enjoy the protection of other AE admin actions? So if, for example, HJ Mitchell had closed the case

2353:

Dreadstar unilaterally overturned an AE block, provided minimal explanation, blanked the thread on their talk page and went away, seemingly doing an unblock-and-sleep. Suggestions have been made also that D may be "pro-pseudoscience", though I've not found any evidence for this. If true, then there

2167:

I think Ncmvocalist's arguments should be seriously considered. The very specific issues of this case should not be the main focus of the ArbCom case. Rather, one should take a general critical look at the AE system and then improve the system. If the Arbs think that this is against the rules under

1837:

an AEBLOCK, i.e. a block of someone who has violated an AC decision or sanctions imposed upon them. If they have not done so, then the block should have no special status simply because it is claimed to be an AEBLOCK by the blocking admin. If an AEBLOCK is a "bad block", then surely it cannot be an

1441:

To not undo AE blocks is a bright-line rule. It's bad enough to tolerate pseudoscience advocates on Knowledge (XXG), but having admins that condone the advocacy unblocking advocates without consequence compounds the problem. Comparing Sandstein's history to Dreadstar's is not like comparing coal to

1221:

In the cases of SV and Trusilver, arbs not only endorsed the respective blocks; in the former, they later showed their willingness to impose blocks in a relatively similar fashion (I think it was Sam Blacketer who later imposed a block on Giano). However, in this case, the block undermined ArbCom's

1144:

If a case is opened, as now seems possible, it might be necessary to look at the legitimacy of both the specific block and unblock. This depends partly on an awareness of the history of postings on noticeboards over the last six months concerning QuackGuru and Ronz. The articles concerned vary, but

981:

I am broadly considered a 'pseudoscience advocate'. I'm not: in fact I am very knowledgable about science and scientific methodology - far more so than most of the putative science people who label me as an advocate - and I usually work on fringe topics in order to restore some measure of NPOV and

650:

I think too that the block should not have been made as an arbitration sanction, because the comments were not made in a pseudoscience article talk page but at AN. Also, even if Dreadstar had been wrong to remove the block, the suggestion that he re-block for procedural reasons is unreasonable, as

3652:

While I see the point of those that say that DS has never required consensus, I think its important to distinguish the difference between not requiring a consensus to do something , and doing something in spite of consensus to the contrary. If an admin sees something requiring immediate unilateral

3311:

I appreciate your input, and in most routine AE cases, such as applying discretionary sanctions to run-of-the-mill nationalist propagandizing, there is indeed a broad range of possible admin responses. But when the Committee directly bans a particular user, the only enforcement approach that works

3247:

No, that would be pointless because an admin acting against known consensus would have to expect their action to be overturned on appeal. What I mean is that I read the existing rules to mean that admins are neither expected not required to wait for or act only based on consensus. If and where the

2953:

I can't even imagine how the case principle I just quoted (or the AC procedures I linked to above) seriously intended to deliberately allow an admin to unilaterally impose a block even if the block is against already-formed consensus not to block (that is how I interpret Roger's statements too). I

2906:

that Roger Davies seems to have surprisingly forgotten why a certain principle was added in an older arbitration case. That appears to be happening in respect of the principle in this case also (and of course, I invite Risker to correct me if I'm wrong or provide more detail about the principle in

2119:

Because when someone say "I suggest you read what your experienced peers are saying on a practical level instead of having such unrealistic optimism on theory alone", they are obviously not suggesting that "your experienced peers" are more "experienced" than the one allegedly "having...unrealistic

2072:

seems to be a redlink. One of the greatest virtues, in my opinion, of the current version of AEBLOCK is that it provides a degree of finality to AE actions, which are generally made in the most divisive areas of Knowledge (XXG) - only these areas would have undergone arbitration, the final step in

1933:

not on any pseudoscience talk page, so it seemed quite a stretch, if not an outright bogus claim that the block fell under AE. Although remotely and tangentially related to pseudoscience disputes, it was really about behavior on AN. I also did not perceive Ludwigs2's comment to be a real threat,

1879:

Consensus is not just a headcount, in reviewing the comments on AN, it appeared to me that there was clear consensus that the block was bad and should be overturned. This was bolstered by the comments and timing of the blocking admin who did not adequately describe what the problem comments were;

1722:

rather troubling. In my various absences from the site I've missed large chunks of drama, but I was around when discretionary sanctions initially began to be applied, and the whole point of them was for arbcom to delegate authority to administrators they had previously reserved for themselves - at

1693:

Keep in mind that the purpose of AEBLOCK, as I understand it, was to provide a reasonable degree of protection to admins working in that area. If you are going to treat every incident as if AEBLOCK didn't exist (which is what you're doing) regardless, then it doesn't provide any protection at all,

1413:

I'm saying keep the general rule but change the consequences to apply to either blocks or unblocks, rather than unblocks alone. Currently, we are making an unblocking admin pay (and the user subject to the treatment to pay) while a blocking admin who escalates in this fashion does not pay anything

1408:

knows Sandstein's history of gambling with his pride, subsequently losing it, and then running here for comfort; this has happened at least once a year now and I'm sure you remember it quite vividly as well. This circus routine, born as a result of an absurdly written rule, needs to change because

1177:

to reverse the block was clearly posted, one can not then "assume good faith" in a deliberate flouting of an ArbCom ruling. This is not even a very close call. And has naught to do with Ludwgs2, and everything to do with the belief that otherwise no ArbCom ruling has any real force or effect. I

814:: You appear to be saying that it's alright for one sysop to lynch someone at a whim, but that anyone who wants to cut the lynching victim down needs to fill out forms in triplicate first. If there really is a prohibiting rule here, that rule is pure bureaucratic nonsense that is a poster-boy for 606:

well), but rather by inventing or strengthening yet more Draconian sanctions for editors showing even a modicum of personal initiative. The AE block protection was not one of the brightest ideas to begin with, and recent events have show just how broken it is. I strongly urge the committee not to

541:

One should not revert another admins block without discussing it with them first or at least obtaining consensus at AN. The comments by Ludwig2 where uncivil and do not improve the atmosphere of editing in this difficult area. Sandsteins block was not unreasonable given the comments. I am sure all

380:

Ludwigs2 states that "that he and I have had words in the recent past, on an editor-to-editor basis". Diffs for this would be helpful, because I recall no such interactions. It is possible, I suppose (although I can't recall it either) that I took admin actions against Ludwigs2 at some time in the

4006:

As for "broadly construed" I understand that to mean that it refers to the breath of the topic area -- that a ban from , say, articles on comic books would also include articles on the history of comic books, because normally the same sort of problems would arise. It does't mean that a very minor

2998:

After countless genuine attempts have been made to convey the essence of "spirit versus letter" (or that a narrow view is not likely to resolve matters) to an AE admin here over the years, responses even as of today leave a clear indication that issues will persist in the future too. Seems such a

2471:

Solution is relatively simple: think if a sanction can be tailored to the case, restricting editor from the very specific area of focus, but in a way that allows him to constructively edit elsewhere. Topic bans are often enough, blocks are rarely necessary. 1RR/0RR/civlity/voting restrictions are

2416:

This must not happen! The rightness or wrongness of the original block shouldn't even be a factor in this decision unless there are clear signs that (1) the blocking admin's account has been hijacked or (2) they have suddenly become completely insane, clearly proven by other edits than the block.

2314:

Begin with two editors who could most charitably be described as "difficult." Fold in one admin widely known for his heavy-handedness. Leaven with an enforcement regime that institutes a first-mover advantage for blocking admins almost without regard to merits, give a light dusting with an admin

2287:

Editors involved in arbitration spend considerable time collecting and presenting evidence, which the ArbCom presumably spends considerable time and attention reading and analyzing. But instead of imposing carefully reasoned remedies on the actual participants, the resolution is often to impose a

2038:

I would urge the committee not to make this a "he broke the rules, we grill him" situation. It was clearly a controversial block and many have disputed whether it really fell under AE at all, and furthermore, Dreadstar's said he won't do it again, so taking a case just to desysop him (which seems

1897:

All the commenting editors on AN, with the exception of Sandstein, Ludwigs2 and QuackGuru, were uninvolved in the actual issue, which was Ludwigs2's statement about QuackGuru. This was not a content dispute or a dispute that directly involved other editors. The issue is not pseudoscience, but a

1545:

What sanctions are required (anything from a formal reminder to one or more specific editors all the way up to desysopping are at the committee's discretion) and whether this requires a full case or a motion, I don't know. Doing nothing though is a sure fire way to confusion at the very least and

1418:

because it can, like in this case, form a critical part of that user's history or pattern of decision making. This includes pre-handling, handling and post-handling (including discussing with a peer towards a more sensible resolution than threatening to, or otherwise directly escalating to here).

3965:

I agree with Thryduulf about 1A. There would need to be something additional, and in a possibly uncertain case like this it would be very wise to seek consensus first. Otherwise it would facilitate administrator-shopping, and one point of arb enforcement is to avoid this. I also agree with him

3814:

Concerning 2A, both the imposition of discretionary sanctions and the enforcement of an ArbCom-imposed restriction do not require consensus; any admin may act without having to go through AE and without having to seek consensus. That's the point of arbitration enforcement, after all: to have the

3760:

Regarding 1A, the key part of your scenario are the words "After the block has expired". Once the block has expired any further blocking, for any cause, is a new action. I suspect that in most circumstances this second blocking would be very ill-advised and possibly a bad block. There exists the

3043:

Since the dramastorm came anyway (sorry, Ncmvocalist) I will comment on the AE after all. Despite the criticism, I have found that Sandstein goes out of his way to accommodate other admins positions at AE. Most commonly he will state he disagrees with something but will not stand in the way of

2363:

But only half these "cases" need to be examined. If it's "Sandstein/Dreadstar", then the other two don't matter, they can be dealt with through a proper RFC/U process first. If it's "QuackGuru/Ludwigs2", then whatever the admins did won't matter, because L2 has successfully carried his tactic of

2057:

is that the protections it provides attach to a block as long as (1) it is claimed to an AE block and (2) there's some colorable basis, grounded in the cited arbitration decision, for the block. To interpret it as WJBscribe does would essentially deprive it of all meaning - a "bad block", in the

994:

I have learned the hard way the kind of political games that anti-fringe editors play on project, and I have become adept at defusing/deflecting them. This also infuriates some people: It is understandably frustrating for those who rely on political ploys to get their way on project to have the

3188:

This looks like an appeal in the guise of a clarification request, and an attempt to circumvent the Committee's rule that appeals are heard only if they are made by the user who is the subject of the sanction. Because that user has chosen, in this instance, not to appeal the block, and the user

3159:

I was one of the admins who opined against a block in the "hypothetical" scenario. I disagree with the block for reasons I've stated elsewhere (mainly that it is based on an overly literal interpretation of the remedy with no regard for its spirit), but at the end of the day AE cannot afford to

3025:

I feel it's worth noting that the situation described in 2A just played out in a recently closed AE request (it's still there but hatted). I assume that part was unmentioned in the hopes of avoiding a dramastorm, so I won't name it directly. That said, I consider it valuable context that arbs

2142:

The block by Sandstein violated the principles of natural justice and due process. In all jurisdictions of the English-speaking world the accused is given a clear statement of the charges against him at the start of the trial. Ludwigs2 was entitled to similar consideration, whether or not other

2099:

As to my "noted absence" from some discussion that you didn't even bother to name, and which I have no idea about, I was not aware that I must review every single noticeboard thread that exists. I am also, sadly, "notably absent" from a large number of other noticeboard threads. Perhaps you can

2088:@Ncmvocalist: Did I say I would have blocked Ludwigs2? All right, to be clear, if it were up to me, I would simply have asked for a refactoring, but it was not, and what I would have done is irrelevant to the question at hand. Please kindly refrain from misrepresenting my comments. And the said 1057:

capable of doing that (as some of you should be aware), but if I have to go that route things will get progressively more ugly. We don't want that (or at least I don't), so give me another solution." (The background was an earlier AN thread in which Ludwigs2 had asked for a QuackGuru ban, and a

362:

I agree that the facts are sufficiently clear that addressing the matter via motion should suffice; there is no need to open a full arbitration case as far as I am concerned. I suggest that the scope be limited to Dreadstar's unblock (and my block, if it is deemed problematic). There are cleary

3982:

To 1A, I think that it's generally common courtesy to discuss an issue with the other admin when one is considering modifying their action, especially when nothing new has taken place that changes the circumstances since that admin made their decision. Whether such an action would be justified

3704:

When as an arbitrator I voted to topic-ban an editor from a topic, it was with the intention that that editor should steer clear of that topic, because his or her participation in that topic was unhelpful to the encyclopedia or the community or both. Blocking is, in many cases, the appropriate

3700:

Now that I've left the Committee, I don't plan to comment regularly in these threads; and I have nothing to say about the specific disputes surrounding this and other pending requests, other than that they are the sort of infighting I'm glad not to be responsible for policing any more. My only

3507:

I was pinged to comment here. I do indeed remember both this case, and the early stages of the discussion about revisions to the discretionary sanctions process that were made, in part, as a result of that case. The clear intention at the time was to address the fact that AE seems to attract

2235:

editors, a good chunk of the block period could pass before that's achieved, especially when it's unclear what entirely uninvolved means. For that reason, admins claiming AE protection for their blocks have a corresponding responsibility not to hand them out frivolously, and not to stretch the

1339:

not a single person is willing to state that they would impose a block in response to a request for a clarification...but you seem quite ready to be the exception to make this embarassing circus complete. Maybe you are among the handful of our admins that think that's an orderly way to resolve

475:

You are right that I did not communicate optimally in this case. In retrospect I should have made it more clear to Ludwigs2 what my concerns about his statement were, as Casliber has already noted, and I should perhaps have given him another chance to address his threat when his response to my

3724:

An approach of automatically blocking every such editor in "each and every instance ... no matter what the circumstances may be" may have the advantages Sandstein urges. These are, if I understand him correctly, that discretion and subjectivity in the enforcement process are reduced, and that

3512:

1A) is a clear superimposition of the second administrator's decision, overriding the first administrator's decision. This is not acceptable and, if there have been prior warnings, could easily lead to desysop or other sanction such as restriction from participating in any way in arbitration

2618: 2095:

I don't know if the current process is sufficiently orderly for your taste - of course sometimes it does fail, and perhaps we have different perceptions on how large that failure rate is; it is sufficient for me that your alternative will generate more disorder. "We must do something. This is

1541:

It is clear to me therefore that the strict and clear rules laid down by the ArbCom were broken. It is my opinion that the ArbCom needs to either follow through with the stated consequences of breaking its rules if it wants to continue to have these rules respected and not sacrifice the moral

96: 1742:

Having read through some more threads, it does appear as though the block was bad and the reversal correct in the spirit of the blocking policy, if not its letter. This is not a huge deal - bad blocks do happen - but can we please, please avoid 4 weeks of painful melodrama in a full case and

1614:

Speaking as one of the editors who opposed the unblock (albeit opaquely), I think only the most strained reading of that conversation would see an obvious consensus to unblock among uninvolved editors. Even if this were not an AE block, I would expect that Dreadstar contact Sandstein before

1565:

If arbcom acts on this request arbcom should take a well considered (and not just perfunctory) look at all parties. There are obvious reasons that enforcement blocks recieve special consideration. This works both ways. AE blocks should not be reversed lightly, at the same time it's highly

701:, since self-refactored) could hardly be construed as a threat against another editor: yes I was frustrated with a difficult situation, and probably spoke out of turn, but the last line clearly notes that I don't want things to go down an unpleasant route. How could that constitute a threat? 3199:

First, the rules about enforcement actions (as well as discretionary sanctions, which are not at issue here) do not envision or require any form of discussion among whoever. The only exception is the case mentioned in the question but not at issue here because no discretionary sanctions are

990:

silly policy assertions, bluntly confronting admins and other long-term editors on unreasoning comments or behavior, blithely deconstructing senseless rhetorical arguments. This kind of thing wins me friends and respect in academia, but - understandably - infuriates some people on project,

2349:

Sandstein works heavily in the AE area, perhaps making overhasty or flat-out wrong decisions (and I'm pretty sure that for each AE action Sandstein has ever done, at least one editor feels they were completely and absolutely wrong) Seemingly, they also did a block-and-sleep, which is never

418:

that AE actions may not be unilaterally undone. If that is your intention, I recommend that for the sake of clarity you also propose a motion to that effect. (I think it would not be advisable to overturn that rule, but that decision is up to you, since it affects the authority of your own

3123:

While the IP has alluded to it, I'm going to make it explicit. This is another damn "hypothetical situation" thread that's actually not at all hypothetical, and like it or not the Arb's responses are going to be read in that context. Yep, it's another damn Malleus/Eric Corbett thread:

3054:

with a warning, would Sandstein need a "clear and active consensus" to block instead? I ask that you consider these scenarios seriously because it appears to me Arbcom is inadvertently creating a race to action in contentious cases where you are intending "deliberate and careful use".

1669:

If a AE block takes place, AEBLOCK must be followed when unblocking - I thought this point was made remarkably clear. In this case, it clearly wasn't followed, and the agreement of those few editors that the original block wasn't appropriate doesn't overcome or surpass that requirement.

2330:

Risker's acceptance comment got me thinking, sorry if this sounds cynical. If the scope of this case is to be widened to "ALL" parties, then it should be either simplified or split. There are four separate "cases" here, each independent of the other, divided equally into two "themes".

744:

in response to recent confrontations I've had with him. This block should never have happened, and since it did happen, appropriate actions should be taken to limit or remove sandstein's administrative powers. I will open a second arbitration thread on that issue in a couple of days.

1970:

More importantly, though, I would like to request clarification from ArbCom regarding whether the original comment is properly covered by the discretionary sanctions, as there seems to be some confusion on the issue. It has always been my understanding that the various sanctions cover

1461:

Comment to Ncmvocalist: I'm not saying that I'm particularly happy with Sandstein's original block, and I'm sympathetic to the view that the AE justification was a stretch. It wasn't patently ridiculous, though, making Dreadstar's unblock unacceptable, while Sandstein's block was only

673:

Since there are different opinions about whether one administrator should have used an arbitration or administrative block, and whether another administrator had the authority to remove the block, it might be more helpful to discuss the issue at a "request for clarification" instead.

1782:) the blocking admin in this case is wrong and the unblocking admin is right, ArbCom must defend AEBLOCK with suitable sanctions. Failure to act means that AEBLOCK is meaningless and future enforcement blocks can be undone without concern. The point of AEBLOCK is that there must be a 2261:

was rightly desysopped for undoing an ArbCom block last year so if you really wish to follow the letter of "the law", then that's the way to go. I think what needs to be looked into here though is whether or not categorizing this as an "AE block" was appropriate in the first place.

3573:, although admin X admitted at AE that they misread the topic ban the first time and now agree that editor A did in fact violate their ban, and that "another administrator would certainly be justified in per the topic ban's stipulation that refrain from discussing the ... topic." 2614: 91: 3966:

about 2A. Within the structure of arb enforcement, this is an admin action, and over-riding it would require prior consensus. Otherwise this too would facilitate administrator-shopping. As for the original block that set this off, our discussing this would need to be separate.

542:

Ludwig2 would have had to have done was simply acknowledge that a) what was said was inappropriate and b) agree to remove it and he would have gotten unblocked. Having another admin come in a revert things especially one who is favorable towards pseudoscience was not appropriate.

214:), of which several, as it appears to me from their statements, had been involved in disputes related to the editor threatened by Ludwigs2 and/or the topic of pseudoscience. Two editors, on the other hand, appeared to agree that Ludwigs2's statement at issue had been disruptive ( 955:

If there are no effective guarantees on AE sanctions that prevent abuse of this sort, then the system need to be dismantled and discarded. Any positive value it might have is far outweighed by the negative consequences of allowing admins to lynch editors at whim with impunity.

3951:. As for 2A, I'm not convinced it can be answered as a hypothetical question - and I'm not convinced that ArbCom trying to specify an answer wouldn't be micro-managing, rarely a good idea. I'd perhaps be willing to opine on a specific situation. And I like Roger's example. 3761:

possibility that the second administrator is in possession of new/additional information (which may or may not be publicly shareable) that justifies the action, so I am not going to say it will always be a bad block. Your question 2A requires more thought before answering.

3931:, advising administrators about when to act and when to not act. Whether or not, in this instance, that advice has been disregarded is an altogether difference matter. So, to turn back to the consensus issue, I still it's wise to obtain consensus but it's not compulsory. 3340:

The rule making AE non-overturnable effectively gives a form of absolute power to the Admins who frequent AE, which has been abused, just as the absolute power of checkusers has been abused (and historically, almost every other form of power, both absolute and otherwise).

2610: 2602: 315:

capable of doing that (as some of you should be aware), but if I have to go that route things will get progressively more ugly." I read this as a threat to cause unspecified serious disruption unless administrators take action against the other editor, and it appears even

85: 74: 1585:

This is daft. I would urge the Committee to reject this because there's no reason it couldn't be sorted out between the admins involved. Running to ArbCom every time someone reverses one of your actions is hardly the way to behave in a collaborative editing environment.

2226:

that must not be overturned, even though he did refer to the pseudoscience case in his statement. If it didn't fully register with me, there's a good chance Dreadstar didn't register all the implications of it either. I don't think he has dealt much with AE, if at all.

1777:

This has nothing to do with Ludwigs2 or Sandstein—the issue concerns what happens when an admin places an WP:AEBLOCK. Should a second admin who is aware that an AEBLOCK is involved be given an AGF get-off-free card when they overrule the blocking admin? Even if (that's

1212:@Elen The alternatives are not practicable because of the detrimental effects that blocking can have on contributors (which is different to other restrictions) - this is inevitable for editors who were already frustrated with what they perceived as tendentious editing 1889:

This entire situation seemed outrageously unfair to me, and to top it off, the blocking admin disappears and does not respond to the post-block comments made on Ludwigs2’s talk page or the objections raised on AN, only finally showing up to file this RFARB seven hours

1102:

derails, large numbers of such editors swarm in to support each other while showing very few signs that they know what is actually being discussed. (This is probably not the best I can do to describe this problem, so I may revise the description once I find the time.)

766:

template on my talk page, as well as notifying the committee by email. I've never been blocked under arbitration rulings before, and I was unsure about proper procedures, so I wanted to cover all my bases, but this may have confused things. My ignorance, my bad.

982:

common sense. However, this often means that I try to rein in ridiculously exaggerated skeptical claims as well as ridiculously exaggerated proponent claims; no one ever remembers that I do the latter and many editors get annoyed at me for trying to do the former.

3878:. The point here I think is that AE is designed as a streamlined summary process and has never required collective decisions before admin action. This is how it should be. It enables admins to act swiftly and decisively when the need arises, by authorising admins 3844:

to mind readily is a community request for an indefinite block/community ban.) But in most cases, if the block "fixed" the issue and there are no new violations, blocks are not punishment, and the discretion of the first administrator likely should be respected.

2230:

It also wasn't immediately obvious that the block was appropriate as an AE block. It was only distantly related to AE rulings; it was unnecessary; and it served only to stoke drama. If such a block can't be overturned until there's clear consensus from entirely

3139:

followed by a firestorm or wheel warring. The ArbCom should be very cautious in how it approaches the question in 2A, in that the question seems to be exploring ways that an ArbCom decision to impose discretionary sanctions can be nullified by a single admin.

2606: 2598: 1482:(I am not "involved" in this incident, but I would be if I were to take action, as I've had negative interactions with Ludwigs2, and — interesting — interactions with QuackGuru. Hence, it would be incorrect to note either that I'm "involved" or "uninvolved".) 80: 69: 1515:

Given that the block was made as an AE block, and that there is no dispute that it was an AE block, the rules for unblocking have been made clear previously. Per those rules, there are only four scenarios where the block should be removed prior to its expiry:

3898:

What you say is true though I find it wearying that once again a borderline call has been made and once again you are the instigator. Perhaps you might consider writing "de minimis non curat lex" on a post-it note and placing it prominently on your monitor?

2198:

and its talk page. He argued that attempts to ban QG had failed, so would people please help deal with his editing, because QG is a difficult editor to work with. In his frustration, Ludwigs expressed himself too strongly in the last paragraph of his post.

1222:

decision in that it enforced the decision in a way which no arbitrator him/her self would have enforced (correct me if I'm wrong; if an arb was enforcing the pseudoscience decision, would they have imposed a block for the exasperated comment, and that too,

748:

Arbitration rulings were never intended to create petty tyrannies in which administrators could sanction editors with impunity according to irrational whims, momentary furies, or personal grudges. Sandstein went off the deep end on this, and Dreadstar

1860:

First, my apologies to ArbCom, I certainly did not intend to flout their rulings, this is the very first time that I’ve overturned a block even purported to be AE-related, and certainly my last one without bringing it to ArbCom first to avoid even the

1052:

of common sense and reason so that we can have a proper discussion on the page. I'm dropping this in your lap now, because if you don't do something to get him to fly right you'll leave me with no choice except to shout him down and shut him up. I'm

1039:

for weeks. QuackGuru has been communicating along the lines of "'No, it is a well established fact that penguins can't fly, and it is well known that your source is an April Fools' joke. There is even a video about how the fake documentary was made.

442:

I welcome any community or ArbCom review of my AE work. To my knowledge, I am among the few administrators who regularly engage in AE, and as a consequence I have issued a great number of AE sanctions (see the enforcement logs of the cases listed at

1926:

Why was there such a rush to block? And, indeed, I should have left a note on Sandstein’s talk page, that won’t happen again. Perhaps I should have given the AN discussion more time and waited for more consensus, but these things can be nebulous.

1069:; nothing has changed since then), as his last action before going to bed. To make matters worse, he declared this as an arbitration enforcement block to make sure it would not be reverted. Surely he was aware how controversial this block would be. 3657:. Obviously there is a gradient there and lots of grey area about what would be acceptable vs what would not be. Certainly no action/sanction required in this "hypothetical" but some guidance about the gradient could resolve potential future issues 882:

I can see some value to the former use; the latter use needs to stamped out with prejudice. I am not the first editor who has received incomprehensible AE sanctions for editing on fringe articles (I need only point to the recent 3-month topic ban

2463:"each problem is a nail" - if the admins decide that the request is actionable, too often they'll prefer a simple "block" or "topic ban" solution, where a less strict sanction (warning, 1RR/civility/interaction restriction) would be sufficient. 2423:

I suggest that ArbCom keep this very simple by cutting to the chase, ignoring everything about the various problems with various editors and the circumstances of the original block, and only addressing the last issue. Make an example here. --

3588: 2931:

I'm pretty sure I've been patient and brought this up in a very reasonable way, given there were a lot of ways this could have otherwise been raised. I also did think the 2A situation has been expressed clearly in my comments here (indeed,

2624: 2586: 58: 978:

on fringe topics, so that things which should be simple discussions become heated, congested, and eventually blow up into full-scale conflagrations like this. There are a few reasons for this, which I'll list out in bullet-point format

1150: 1840:

In this case, the question of whether Dreadstar was correct in determining that Sandstein's block fell outside the scope of the sanctions cannot be divorced from the issue of whether he was right to unblock, as some are seeking to do.

1537:

There was no permission from ArbCom, there was no clear consensus to unblock, the block and unblock were done by different users and Jimbo has not been involved (at least not that anybody has said in this request or on his talk page).

2836:

For the avoidance of doubt, those suggestions are false accusations made in bad faith without a shred of evidence (except possibly the bit about "other users" being friends of Eric Corbett as I don't know how accurate that is. Still,

3799:(i.e. should not be made harsher) in the absence of a. the imposing administrator's consent, b. a consensus of uninvolved editors or administrators, b. arbcom's authorisation or d. supervenient circumstances justifying the increase. 2954:

thought the idea is to reduce the number of unnecessary appeals and not force them to become a much more regular and frequent feature. Also, when a consensus is clearly desired by the admins in the first instance who are still

1615:

unblocking unilaterally. As it was at least nominally an AE block, the committee has a responsibility to uphold their explicit promise that reversals of AE blocks will be treated as more troubling than normal block reversals.

3946:

I agree with my colleagues's views on 1A - there would have to be something new or overlooked to justify a 2nd block. The phrase 'supervenient circumstances' is a great description but I'd warn against reading our article

1686:@ John Vandenberg, "Declining this case does not overturn WP:AEBLOCK." - actually, yes, yes it does. If you make an extrememly clear statement that, in all cases, (un)doing X will result in Y, someone (un)does X, and you 3708:

That being said, speaking only for myself, when I proposed or voted to topic-ban an editor from X topic ("broadly construed" or otherwise), it was not my intention that "this means that expect this editor to be blocked

601:

I see a worrying tendency in several Arbiters statements to once more not bolster the authority of ArbCom and the dispute resolution process in general by openness and well-reasoned, widely accepted decisions (i.e. by

3924: 876:

admin, an AE sanction is a 'state terror' tool, that allows an admin to dispose of any editor whom s/he dislikes - quickly, quietly, and with no possibility of redemption, on any trumped-up charge that admin can

2692:

My first request for clarification concerns the AC procedures - standard provision for appeals and modifications. In particular, the section entitled "Modification by administrators" in the following situation:

945: 2120:

optimism on theory alone". My grasp on the English language must be faltering quite a bit. Feel free to present my position in whatever way you see fit, then. Go ahead. Not that you need permission for it.

1880:

compounded by giving a ‘two hour after next edit’ time frame for Ludwigs2 to respond - which was not followed by Sandstein - then when Ludwigs2 did respond with a query as to what the problem comments were,

1048:

supporters of the non-communicator to realise just what they are supporting, with these words: "So, you guys want to keep QuackGuru around as an editor - okayfine. Now, tell me how to get him to use even a

2100:

provide a list so that I can add a belated disclaimer to each that my absence indicates no view on the question discussed in the thread, something that I had foolishly taken for granted until moments ago?

1278:"Threatening to block other admins over a difference in opinion is not ok. Full stop. In that context you'd be involved by any sane standard and threatening such blocks is really, really not ok." - JoshuaZ 1128:

or its talk page, he had to be on his best behaviour. Perhaps some community feedback through an RfC/U might help Ludwigs2 work out better ways of expressing himself and of interacting with other editors.

3705:

response when an editor intentionally disregards a topic-ban, and I have always appreciated the work of the admins on AE and elsewhere who enforce our decisions, including with blocking where necessary.

3566:

Other administrators opine on the issue at AE and there appears to be division regarding the appropriateness of any block (and the appropriate duration for a block even if it is agreed). Administrator Y

3192:

On the merits, I'm of the view that any discussion among admins or others about an enforcement request does not prevent any admin from taking, or not taking, any enforcement action they deem appropriate.

2907:

this case, as she was also an arb when this principle 3.1 was unanimously passed with Roger's **unreserved** support). The principle says because of the priority given to enforcement of arb sanctions..."

1939:

I believe a simple pre-block discussion by Sandstein with Ludwigs2 may have defused this situation entirely. My own intervention calmed the situation quite a bit, and led to a positive outcome and path

3248:

Committee expects admins to look for consensus instead of enforcing ArbCom decisions on their own initiative, they should be clear about it and tell us so in the rules, which is currently not the case.

2809:

The community elected the committee, not Sandstein. Even if for some bizarre reason you want Sandstein to remain entitled to keep up his repeated wikilawyering, his overly bureaucratic approach and his

790:

by asserting that he was looking for a reason to block me due to being miffed at me; the other alternatives I have considered are far more cynical and callous and would call for immediate desysopping.

3104:

dictum that blocks should generally require the initial input of (say) three admins in order to have standing against a simple reversal by another admin? Thus reducing the value of "first move wins."

311:, and reads in relevant part: "I'm dropping this in your lap now, because if you don't do something to get him to fly right you'll leave me with no choice except to shout him down and shut him up. I'm 3795:

Concerning 1A, I tend to agree with my learned colleague. As a general rule, I'd say that once an administrator has imposed a discretionary sanction on an editor, said sanction should not be modified

2795: 1898:

comment made by one editor about their potential behavior towards another on an appropriate noticeboard. As Sandstein correctly points out it was criticized by five editors at WP:AN: Hans Adler:

3610:

If admins were perfect, Go Phigtins! or NE Ent would have either removed the comments as I asked, blocked EC (which I did not ask for), or started a discussion here at AE, per Principle 3.1.2. --

2341:

Ludwigs2 adopts an approach which projects an air of superiority, and openly discusses and uses various "tactics" to acheive their aims, which tactics could be viewed as disruptive editing modes.

2060:

On the substance of this request, I concur with Thryduulf and Ale_Jrb, and I agree with Sandstein as to the general question of applicability of discretionary sanctions and similar provisions to

1967:

actions) can be established, or one of the parties is shown to be too involved to act, I think that the best course of action here is probably to pass Casliber's motions and put this behind us.

2147:

article by QuackGuru that editors as disparate as Ludwigs2, Mathsci and myself agree on. Finally, although I was named by the plaintiff, I was not told that the Arbcom debate was taking place.

3604: 2959:

action. I really don't see how that approach is ensuring priority enforcement actions are taken carefully in the first instance where possible, or are helpful especially in those situations.

1494:.) ArbCom needs to take this up, either declaring that the block should not be considered an AE block, or specifying a reason why policy that AE blocks not be overturned does not apply. — 3928: 1490:

an AE block, it looks to me as a simple threat of disruption, which L2 has done frequently. (Both threats, and actual disruption by "shouting down" editors acting in good faith and with

1838:

AEBLOCK at all and should be overturned as any other bad block should be - boldy and decisively to restore the status quo. No more consensus should be needed than for any other unblock.

3571:

imposes a block (where there is clearly no pressing need to), and did not obtain prior affirmative consent/agreement from administrator X, or at AN, AE, or here for imposing the block

3189:

asking the question is not in any way affected by this situation, there is in my view nothing that needs – in the sense of an actual controversy awaiting resolution – to be clarified.

2456:

I am not familiar with this particular case, but I am quite familiar with AE inefficiencies. The problems have are many years old, and can be in my experience briefly summarized as:

4091:

As for whether refusing to act is an admin decision, we are reading too much into the wording. Admin action would be closure of an AE thread in my books, not just opining there. --

2284:

I have no comment about the block or unblock. However if the ArbCom chooses to look at the broader matter of discretionary sanctions and AE then I'd like to comment on that issue.

1666:

more stringent requirements, then that defeats the entire purpose of requiring that consensus... and that's for borderline cases, where the extra certainty is even more important!

1091:

by sectarian self-described "skeptics" who tend to adore pretended experts on pseudoscience whose expertise generally manifests in using strong words rather than strong arguments.

3337:

It seems to to me that the "first mover advantage" is a long-standing Wiki problem which has been dealt with traditionally by consensus and discussion, and application of policy.

2703:

My second request for clarification concerns the AE sanction handling case (principle 3.1.2 - Deliberate and careful use of discretionary sanctions) in the following situation:

1035:(1) Sandstein's inclination to make essentially arbitrary draconian blocks. In this case Ludwigs2 reported extremely disruptive behaviour by QuackGuru that had been going on at 3701:

purpose in commenting here is to respond to the comment from Sandstein about his approach to AE, because while I respect his dedication and sincerity, I have a different view.

1234:

The archaic motion from March needs to be changed from what SirFozzie has quoted to something that works. My suggestion is not perfect, but it's something to work from/towards:

1076:

in mid-2007 was rather unfocused and ran out without conclusion. I don't have a full record of attempts to solve the problem, but I believe the last one is the one archived at

2468:

loves to deal with technicalities (letter) of the law rather then the spirit, and prefers sanctions (imprisonment) rather than more tailored sanctions (community work, etc.).

1077: 3135:

Unlike most threads involving Eric Corbett, it was dealt with in a reasonable amount of time, after a reasonable discussion, and resulted in a reasonable final decision that

1419:

We've tried the present system for several months; it's not working and the heated drama hasn't gone away in the long term. Rather, it is only aggravating a deeper problem.

483: 182: 786:

point is that there was no reasonable, rational explanation for his actions regarding me, so I have to assume his motivations were unreasonable and irrational. I am being

2239:

I ask ArbCom to draw a line under this by reminding admins not to impose AE blocks lightly, and not to overturn them unless the consensus to do so is unambiguously clear.

1260:"I'm puzzled. Sandstein evidently felt the foolish remark was egregious enough to justify a block, but gave no request or opportunity to remove the remark." - dave souza 4086:

Sometimes some administrators see with more clarity than others on stations, sometimes not. If there really is concern about it, accountability via ArbCom is an option.

725:, which is not by any stretch of the imagination a pseudoscience article. that's just bizarre, and apparently designed to punish me for complaining about QG's behavior 2747:), when this request is really about (as the name of the case suggests): Arbitration Enforcement Sanction Handling. One of the main parties to that case was AE-active 363:

unresolved underlying matters surrounding Ludwigs2 and QuackGuru, but I believe that these still need "normal" prior dispute resolution (such as a RFC or AE request).

3476: 1404:

going to be the cause is unacceptable in circumstances where suboptimal, merely partially justifiable, or even substandard sanctions were imposed in the first place.

1285:

I don't think any arbitrator can with a straight face suggest the Community has changed its stance since then because we see the same issues popping up repeatedly.

3653:

action, they should do so. but when they are aware of pre-existing consensus to the contrary, or at least significant debate, then the unilateral action can seem

1065:

Sandstein blocked Ludwigs2 for very little reason, essentially for being frustrated with the inefficient handling of a long-standing problem (look at the date of

514:

were involved in the discussions that led to the dispute, constitutes such consensus, I must respectfully doubt your ability, or willingness, to gauge consensus.

1099: 2581: 1542:

authority it has, or it needs to revise the rules to reflect what it is willing to follow up. A rule that is not enforced is worse than having no rule at all.

2911:

when an administrator knows that there is a division of opinion regarding whether a sanction is warranted, and there is no pressing need for immediate action,

950:) - If someone points me to where I can find a list of AE sanctions given, I'll start doing the research needed to see how extensive a problem this really is. 1872:

were meant to convey that I didn't think this was a Pseudoscience ArbCom situation as Sandstein did, but a behavioral issue outside the remit of AE. I think

1084:

you can see how David Gerard and SlimVirgin were about to fix an article between them, and then gave up after QuackGuru made it clear that he is the owner."

476:

message did not do so, rather than assume, as I did, that he simply chose not to do so for reasons of his own. I will take this into account in the future.

4102: 4080: 4059: 4032: 4001: 3989: 3977: 3960: 3939: 3907: 3890: 3862: 3848: 3835: 3809: 3788: 3770: 3737: 3690: 3666: 3642: 3619: 3530: 3324: 3299: 3260: 3242: 3220: 3174: 3149: 3113: 3086: 3063: 3035: 3008: 2981: 2881: 2855: 2722: 2570: 2524: 2433: 2373: 2301: 2271: 2247: 2181: 2156: 2129: 2113: 2082: 2028: 2003: 1956: 1850: 1818: 1799: 1766: 1752: 1736: 1708: 1681: 1652: 1624: 1604: 1575: 1555: 1501: 1471: 1455: 1428: 1394: 1367: 1349: 1319: 1294: 1248: 1206: 1187: 1162: 1138: 1110: 1021: 965: 846: 827: 800: 776: 683: 665: 616: 595: 563: 526: 465: 431: 397: 375: 358: 335: 297: 264: 2089: 1081: 1073: 1066: 25: 4020:

The only comment I am going to make is: there has never been the requirement of a consensus to use DS and I strongly oppose the idea of requiring one. --

1178:

suggest that ArbCom retract its rules if the rules have no force. I suggest that ArbCom strictly enforce such absolute rules if they are to have force.

718:

without explanation or the opportunity to address the issue. He was clearly on a beeline to blocking me, and only left a warning as a pro-forma exercise

3719:

It is not possible even in theory for any decision to anticipate every possible application of a remedy or every borderline situation that may come up.

2364:

making a threat at AN as a means to get QG in front of ArbCom. If that tactic works, who cares how the admins or the community deal with it? It works.

1918:

I think that Sandstein was rushed and sloppy in his comments and follow-up block, Sandstein should have clearly explained the situation as I did here:

3278:

rule. If it is indeed the view of the Committee that violations of ArbCom decisions that are considered less severe according to some standard should

579: 3345:

have created of non-overturnable admin actions. It would be better, if still not ideal, if these actions were subject to normal community scrutiny.

3920: 2654: 408:

I would appreciate advice about the form of dispute resolution that you believe I should have undertaken with respect to Dreadstar, in view of his

2829:

I and several other users are (a) friends of Eric Corbett, and (b) therefore incapable of assessing when enforcement is appropriate and necessary.

2315:

having a sense of fairness and proportion, and bake in a hot noticeboard until everyone goes into a tizzy. Result: one mountain out of a molehill.

2236:

definition of AE to cover any block the admin wants to firm up. AE shouldn't be used as a trump card to make it harder to correct admin actions.

498:). This is because, as here, ugly disputes about such topics have a tendency to spill out into other fora where they also need to be contained. 3202:

Prior to placing sanctions that are likely to be controversial, administrators are advised to elicit the opinions of other administrators at AE

2409:

Elen of Roads and others make the final and most important point of relevance here, one that must be dealt with very clearly and definitively:

21: 3055: 3027: 1883:

the blocking admin declined to answer that question, and instead immediately blocked the user. (Ncmvocalist describes this succinctly here:

894: 3513:

enforcement for an extended period (Arbcom seems to be big on the "don't appeal for a year" position right now, which would be sufficient).

909: 281:

Ludwigs2 to respond to my concerns about his threat, noting that I expected them to do so within two hours of their next edit, which they

2219:

Regarding the block being overturned, a key point is this: it did not fully register with me when Sandstein posted about his block on AN

1865:

of disregarding their rulings. With that said, I’m unclear on how WP:AN falls under the ArbCom Pseudoscience restrictions. My comments

991:

particularly those who do not have the academic training that I have and rely on more intuitive/emotional arguments to make their case.

2846:

I do wish the arbitrators would find a more effective way to tell Sandstein to cease engaging in such needlessly problematic conduct.

2744: 2504: 2499: 2494: 2489: 2484: 2479: 1214:(not sure if it's a justified perception in this case which is why I've called for the RfC/U - but the perception nevertheless exists) 921: 704:

besides, by comparison to other things I have seen on AN, ANI, and talk pages that have never received sanctions, this is milquetoast.

494:

about pseudoscience. This is evident, in particular, in the provision that allows "bans on any editing related to the topic" (compare

2648: 2069: 939: 927: 3718: 915: 3521:

Those were the intentions at the time of the case, and in the early discussions for improving the procedures. Hope that helps.

2826:

I've filed this request to circumvent the appeal procedure, and thereby game the system in relation to Eric Corbett's block; and

229:

Ludwigs2 without entering into discussion with me. Later, on his talk page, in response to a query from another user, Dreadstar

3096:

The principle of "do it first so the other admin will be wheel-warring" has been discussed before, without any solid answers.

2759: 2537: 933: 3728:

These are general thoughts borne of experience, not focused on any specific block or case, and of course everyone else's MMV.

2815:

him to change his approach to be more consistent with what is expected at all levels, maybe something else needs to be tried.

1263:"I think you sometimes let strict rules get in the way of proper judgment and more importantly, common sense" - Juliancolten 1153:. It initially named both QuackGuru and Ronz, but, after the initial posting, there was no further discussion of QuackGuru. 867:

admin, an AE sanction is an unfortunate but sometimes pragmatic tool for quickly stopping some tenacious editorial problems.

2823:

I am filing an appeal on behalf of a certain blocked user (Eric Corbett) but have concealed it in the form of this request;

2551:

Subsequent comments should be made on the appropriate discussion page. No further edits should be made to this discussion.

159:

Subsequent comments should be made on the appropriate discussion page. No further edits should be made to this discussion.

4112:

Subsequent comments should be made on the appropriate discussion page. No further edits should be made to this discussion.

2771: 2442:

Subsequent comments should be made on the appropriate discussion page. No further edits should be made to this discussion.

1718:

Speaking as an admin who has done ridiculous quantities of Arbcom enforcement work in my time, I find the entire ethos of

1697:

Note that I don't have an opinion on the appropriateness of the original block, but I do have an opinion on its reversal.

2169: 1757:

From memory, I do also think that Ncmvocalist's comments have a good deal of merit, and arbcom should bear them in mind.

1385:

You are not learning your lessons and this is definitely only the beginning; it does not take a genius to work that out.

17: 2789: 2777: 2023: 1998: 1223: 555: 2765: 3160:

become deadlocked like ANI whenever a big name is involved. The solution? More objective, level-headed admins at AE.

2191:

I hope the Committee won't take this case, because it's a mountain out of a molehill, largely of Sandstein's making.

3603:

otherwise they might have realized that EC really had broken his topic ban and simply removed EC's comments per the

346:

I am not aware of anything that would disqualify me from taking action as an uninvolved administrator in this case.

3638: 3348:

I understand, of course, that the idea is to prevent an infinite regress. More important though is the inequality

2783: 2125: 2109: 2078: 3833: 3807: 3491: 3059: 3031: 2672: 888: 679: 661: 3145: 2913:

it may be best for an administrator to raise the issue in the discussion venue for Arbitration Enforcement and

2733:

I think it's embarrassing that AE admins were responsible for attempting to derail this request into one about

2202:

Sandstein responded that AN wasn't the right place for dispute resolution (which is surely false; it is indeed

903: 612: 591: 559: 112: 1924: 756:

as an final though, I apologize for any part of this bureaucratic confusion that may be my fault: I placed an

753:

to receive the committee's thanks for redressing a significant abuse of the committee's delegated authority.

3633:'s concerns of casting aspersions please see the section below where I have provided the requested evidence. 1058:

general feeling seemed to be that QuackGuru is a serious problem but nothing should be done for the moment.)

3615: 2660: 2322:

Sandstein's part), and whether giving AE blocks the status of religious edicts is really such a great idea.

1446:. Retaliatory blocking by proxy isn't really much better than doing it yourself, it just muddies the trail.— 3927:. It doesn't talk about reaching consensus before a decision but it does include an extensive new section, 1491: 1228:

As pseudoscience advocacy was not being used as a reason for blocking, we can't look into that possibility.

382: 2738: 2429: 2396: 1921:

Unfortunately, he did not. The block was not even properly logged per the Pseudoscience Arbcom decision:

1498: 502:

in the case of "a clear, substantial, and active consensus of uninvolved editors". If you do believe that

137: 3733: 3634: 3169: 3082: 3004: 2977: 2877: 2851: 2718: 2642: 2563: 2295: 2177: 2121: 2105: 2074: 1833:. As I understand it, a block is not an AEBLOCK just because it is described as such - it must actually 1599: 1571: 1424: 1390: 1363: 1345: 1315: 1290: 1244: 1202: 447: 3184:

As the admin who made the block discussed in the second question, I'm offering the following comments:

2214:

after Ludwig asked for more information from Sandstein instead of withdrawing the comment immediately.

1072:(2) The behavioural problems of QuackGuru have long caused disruption, sometimes severe disruption. An 837:

Yes, I agree that including QuackGuru in this arbitration is an appropriate move. good suggestion. --

195:

template to Ludwigs2's talk page, which warns administrators not to unilaterally undo it except as per

40: 3558:

administrator X refuses to block an user after reviewing a complaint alleging a breach of a topic ban

1884: 4027: 3997: 3956: 3828: 3802: 3488: 2152: 1648: 1107: 1104: 884: 675: 657: 634: 2632:

List of any users involved or directly affected, and confirmation that all are aware of the request:

2414:

Since when can an admin violate the clear brightline decision to not overturn another admin's block?

2223: 2054: 1830: 1719: 1662: 415: 249: 196: 4097: 3784: 3766: 3141: 2753: 2043: 1950: 1846: 1551: 898: 608: 587: 277:

about the Pseudoscience discretionary sanctions. I also did not break any self-imposed deadline. I

189: 107: 2838: 2357:

And the big question, how do disputed AE blocks get resolved, what are the thresholds to overturn?

1381:@SirFozzie, well thank you for clarifying that you value Sandstein over the rest of the Community 709:

I was happy to retract the statement, but was never allowed the opportunity. Sandstein warned me

3984: 3685: 3662: 3630: 3611: 2460:"admin lottery" - rulings are not consistent and depend on which admins take interest in the case 2369: 1980: 1934:

but I could understand how others might interpret it that way, which is why I phrased it thusly:

1814: 1795: 1762: 1748: 1732: 1590:

back and you can't assume that every admin making AE actions has perfect judgement all the time.

1036: 1013: 957: 838: 819: 792: 768: 3654: 3284: 3201: 2065: 583: 478:

Nonetheless, you are mistaken to assume that discretionary sanctions do not apply to conduct on

1829:

Reading some of the comments above and below, I think ArbCom does need to clarify the scope of

645:

And Sandstein should have allowed Ludwigs2 the two hours he said he would allow for a response.

3932: 3900: 3883: 3855: 3776: 3269: 3109: 3100:

is a rough equivalent. Why not recognize that valid issue raised by Floq above - and issue a

2866: 2734: 2582:

Knowledge (XXG):Arbitration_Committee/Procedures#Standard_provision:_appeals_and_modifications

2517: 2425: 2388: 1620: 1495: 1183: 1158: 1134: 1080:. At the time I gave the following example that demonstrates the dimension of the problem: "t 169:

At 23:27, 8 March 2011, I blocked Ludwigs2 for 72 hours as a response to threats they made at

132: 1173:

Either ArbCom rulings have effect, or they do not. As the specific admonition to all admins

495: 248:, the "clear, substantial, and active consensus of uninvolved editors" that is required, per 3912: 3873: 3729: 3544:

meant to clarify a situation like the recent Sandstein/Eric Corbett brouhaha, Ncmvocalist's

3526: 3353: 3306: 3161: 3078: 3000: 2973: 2873: 2847: 2714: 2637: 2559: 2290: 2173: 2018: 1993: 1591: 1567: 1420: 1386: 1359: 1341: 1311: 1286: 1240: 1198: 760: 551: 2811: 2338:

QuackGuru adopts an approach unresponsive to changing circumstances, accompanied by reverts

2061: 987: 815: 575: 4021: 3952: 3845: 2240: 2148: 506:, which lasted about three hours and involved about seven other editors, of whom at least 126: 2064:, without expressing any opinion on whether Ludwigs2's comment in this case falls inside 1524: 1275:"The correct response to the criticism of the block would have been "D'oh! Sorry"." - Guy 1121: 722: 627:

Other editors complained about the block on both Ludwigs2's and Sandstein's talk pages:

479: 273:

Your assertions are incorrect. As I noted at the AN thread, Ludwigs2 had previously been

237: 207: 170: 715:(because I really wasn't sure what he was talking about), and he immediately blocked me 4092: 3915:

I'm not quite clear what Risker has got to do with this (but for information I replied

3895: 3869: 3780: 3762: 3579: 3315: 3290: 3251: 3227:

with regard to your first point, I hope you do not mean to imply that an admin may act

3211: 2933: 2748: 2267: 2258: 2040: 1988: 1946: 1843: 1690:

do Y, then the clarity of the statement is immediately brought totally into question.

1547: 517: 456: 422: 388: 366: 349: 326: 288: 255: 4078: 4055: 4014: 3973: 3948: 3678: 3658: 3238: 2392: 2365: 2206:

of the right places), and asked Ludwigs why he should not be blocked for his remark.

2195: 2144: 1810: 1791: 1758: 1744: 1728: 1467: 1451: 1125: 1095: 174: 3105: 2513: 1698: 1671: 1616: 1179: 1154: 1146: 1130: 693:

Let's be clear: Sandstein's block was deeply problematic for a number of reasons:

2713:

I have listed 1A and 2A above only, as I may have a follow up under each. Thanks,

2096:

something. Therefore we must do this." is a logical fallacy, not a valid argument.

1992:

greatly appreciate some guidance before I misinterpret the community standards. -

1411:

the circumstances are no longer perfectly identical to the previous two incidents.

212:

Slimvirgin, Hans Adler, Short Brigade Harvester Boris, The Four Deuces, Xxanthippe

2490:

On why so many admin heads are seen sticking in the sand when push comes to shove

580:

Knowledge (XXG):Administrators'_noticeboard#QuackGuru_again_-_what_do_I_do_now.3F

3522: 2899: 2530:

Clarification request: Arbitration Enforcement sanction handling (February 2015)

1151:

Knowledge (XXG):Administrators' noticeboard/Incidents/Problem on BLP noticeboard

640: 543: 1044: 1041: 183:

Knowledge (XXG):Requests for arbitration/Pseudoscience#Discretionary sanctions

121: 2820:

Even here, I am concerned that Sandstein appears to improperly suggest that:

206:

Following my announcement of the block, it was criticized by five editors at

2263: 654:

Therefore I do not see any reason for Arbitration action against Dreadstar.

628: 1566:

important that blocks of this sort be truly reflective of arbcoms intent.--

3755:

Arbitration Enforcement sanction handling: Arbitrator views and discussion

1078:

WP:Administrators' noticeboard/Archive220#Community ban for User:QuackGuru

4071: 4050: 4009: 3968: 3233: 3097: 2384: 1463: 1447: 1444:

here's a discussion of a block based on Dreadstar falsifying a 3RR report

721:

Sandstein is applying the pseudoscience arbitration result to discussion

181:). I labeled this block as an arbitration enforcement action pursuant to 2013:

Ludwigs2: if you do not think this is useful or accurate, please delete.

3919:). Anyhow, to the substantive point. The text you quote comes from the 2625:

principle 3.1.2 - Deliberate and careful use of discretionary sanctions

414:

If you decline this case, you in effect overturn the decision cited at

3713:

in which they make a X-related edit outside of the policy exceptions,

3749:

This area is used for notes by the clerks (including clerk recusals).

2999:

pity too, but I can't help but wonder what will eventuate next time.

1984: 1082:

Talk:Citizendium/Archive 4#Won't someone please think of the article?

225:

At 02:41, 9 March 2011, about three hours after the block, Dreadstar

2909:

When it is not entirely clear whether a sanction is appropriate, or

607:

further strengthen process wonkery over good sense and consensus. --

578:

anyways. Moreover, there was substantial support for the unblock at

1930:

The problematic comment by Ludwigs2 was made on the AN noticeboard,

1094:

It appears to me that whenever a discussion at an article such as

173:

against another editor in the context of a dispute concerning the

1723:

least as far as certain troublesome topic-areas were concerned.

1523:

When there is a clear consensus of uninvolved administrators at

1979:. To wit, if editors clearly and directly carry a dispute from 201:

Current state of the respective section of Ludwigs2's talk page

2194:

Ludwigs2 posted to WP:AN for help with QuackGuru's editing at

574:

the self-set deadline), and it should have been removed under

412:

that he is unwilling to reverse his reversal of my AE action.

3483:

The current arrangement breaks this in no uncertain manner.

1987:

is not usually covered by ARBPS, but a dispute carried from

233:

to undo his reversal of my arbitration enforcement action.

2505:

When to use the banhammer - and when not to: a simple math

381:

past, but such interactions do not matter with respect to

1983:

to another page, the sanctions should continue to apply.

1530:

When the blocking administrator reverts their own actions

2104:

and will probably remain so for the foreseeable future.

1945:

I believe that’s what we want in situations like this.

3916: 3601: 3598: 3595: 3592: 3583: 3129: 3125: 2903: 2801: 2678: 2666: 2475:

I invite interested editors to read my mini-essays on:

2220: 2215: 2212: 2209: 2207: 2200: 1943: 1941: 1935: 1931: 1922: 1919: 1914: 1911: 1908: 1905: 1902: 1899: 1893: 1891: 1881: 1873: 1870: 1868: 1866: 1743:

encourage sysops to talk to one another, for a change.

1443: 858:

Just a comment about the mixed nature of AE sanctions:

811: 716: 713: 710: 698: 646: 643: 637: 632: 511: 507: 503: 409: 317: 308: 282: 278: 274: 245: 241: 230: 226: 219: 215: 211: 200: 178: 48: 3607:, which is all that I asked for, before I went to AE. 1913:, plus one more on Ludwigs2's talkpage, GoetheFromm: 539:

It does appear dreadstar is involved in wheel-waring.

3359: 2804:

seem to continue, and that too in the name of Arbcom.

1533:

When done by or on the explicit instructions of Jimbo

3686: 2902:(who was an arbitrator at the time of the case) has 2500:

On why the little editor doesn't matter (but should)

697:

The statement in question (in the last paragraph of

149:

All statements made prior to the opening of the case

1520:

With written evidence of permission from the ArbCom

3679: 3467: 2915:seek a consensus, rather than to act unilaterally. 2800:, and it's disappointing to note that Sandstein's 2354:would have been even more serious misuse of tools. 2211:He blocked Ludwigs 90 minutes later for 72 hours, 1876:is an excellent description of the issue at hand. 1149:. The discussion on ANI was put onto this subpage 2472:usually better than broad topic bans. And so on. 3578:The decision to block wasn't unilateral because 486:is intended to cover all conduct related to the 2480:On the spirit and the letter of Knowledge (XXG) 2972:Perhaps more discussion and views are needed. 2447:Statements made after the case has been opened 2070:Knowledge (XXG):Requests for comment/Sandstein 4070:I will not support amending AE as requested. 3553:On a talk page, not Arbitration Enforcement, 1100:list of topics characterized as pseudoscience 582:- in my opinion enough to support consensus. 439:Comment with respect to Ncmvocalist's comment 8: 4043:I do not agree. There is no requirement for 1032:Three major issues have come together here: 995:wikipolitics rug pulled out from under them. 972:Note on the 'rapid escalation' of this issue 3775:Regarding 2A, contrary to how I interpret 1508:Comment by completely uninvolved Thryduulf 1328: 1299: 3358: 2588:Arbitration Enforcement sanction handling 318:Dreadstar agrees with this interpretation 3715:no matter what the circumstances may be. 3591:. Go Phightins! acted quickly (5 minutes 2383:I'd like to second the comments made by 2307:Comment by Short Brigade Harvester Boris 1255:Sandstein's administrator review of 2009 405:Response to John Vandenberg and Casliber 2168:which ArbCom operates, then I refer to 623:Statement by uninvolved The Four Deuces 3562:(which was imposed as a case remedy). 569:Statement by uninvolved Stephan Schulz 2514:Piotr Konieczny aka Prokonsul Piotrus 7: 3921:2011 case on Arbitration enforcement 3582:agreed that EC had violated his ban. 3274:Thanks for your advice concerning a 2839:Knowledge (XXG) is not a battlefield 2547:The following discussion is closed. 155:The following discussion is closed. 3925:major six-month public review of DS 3597:at WT:WER, as did NE Ent (3 minutes 3155:Passing comment from Harry Mitchell 2688:Statement by uninvolved Ncmvocalist 2163:Statement by uninvolved Count Iblis 1120:When an administrator blocks while 864:thoughtful, objective, and cautious 179:State of the AN thread at that time 2317:as I now see SV already has stated 651:it would seem unfair to Ludwigs2. 32: 3821:Finally, concerning the issue of 2138:Statement by the named Xxanthippe 1901:, Short Brigade Harvester Boris: 1067:WP:Requests for comment/QuackGuru 1028:Preliminary comment by Hans Adler 4108:The discussion above is closed. 3564:The complainant then goes to AE. 3026:should be aware of and review. 2802:problematic behavioural patterns 2438:The discussion above is closed. 1630:Comment by uninvolved Becritical 236:I submit that the discussion at 18:Knowledge (XXG) talk:Arbitration 3589:Administrator's are not perfect 2009:In defense of Ludwigs2 (2over0) 1169:Statement by uninvolved Collect 250:this Committee's prior decision 3600:) after I asked a second time, 3594:) after I asked for admin help 3587:Principle 2.2.1 applies here: 2485:On why good admins don't exist 1773:Comment by uninvolved Johnuniq 738:purely and completely punitive 534:Statement by uninvolved Jmh649 1: 3625:Statement by Hell in a Bucket 3497:16:30, 28 January 2015 (UTC). 3468:{\displaystyle Community: --> 3119:Observation by TenOfAllTrades 1658:Comment by uninvolved Ale jrb 4103:07:25, 8 February 2015 (UTC) 4081:23:49, 5 February 2015 (UTC) 4060:06:01, 5 February 2015 (UTC) 4033:21:54, 2 February 2015 (UTC) 4002:07:56, 1 February 2015 (UTC) 3990:11:55, 29 January 2015 (UTC) 3978:01:17, 29 January 2015 (UTC) 3961:19:55, 27 January 2015 (UTC) 3940:17:29, 28 January 2015 (UTC) 3929:"The Role of Administrators" 3908:16:49, 28 January 2015 (UTC) 3891:09:29, 28 January 2015 (UTC) 3863:09:13, 27 January 2015 (UTC) 3849:23:23, 26 January 2015 (UTC) 3836:10:50, 1 February 2015 (UTC) 3810:15:28, 26 January 2015 (UTC) 3789:22:19, 27 January 2015 (UTC) 3771:01:09, 26 January 2015 (UTC) 3738:15:37, 5 February 2015 (UTC) 3691:12:52, 3 February 2015 (UTC) 3667:23:02, 2 February 2015 (UTC) 3643:23:46, 1 February 2015 (UTC) 3620:21:39, 1 February 2015 (UTC) 3531:07:28, 29 January 2015 (UTC) 3333:Statement by Rich Farmbrough 3325:11:23, 7 February 2015 (UTC) 3300:09:23, 30 January 2015 (UTC) 3261:09:23, 30 January 2015 (UTC) 3243:03:34, 30 January 2015 (UTC) 3221:08:31, 27 January 2015 (UTC) 3175:02:49, 27 January 2015 (UTC) 3150:21:14, 26 January 2015 (UTC) 3114:20:46, 26 January 2015 (UTC) 3087:18:59, 26 January 2015 (UTC) 3064:16:11, 27 January 2015 (UTC) 3036:18:26, 26 January 2015 (UTC) 3009:16:12, 7 February 2015 (UTC) 2982:16:49, 28 January 2015 (UTC) 2882:15:48, 27 January 2015 (UTC) 2856:15:19, 27 January 2015 (UTC) 2841:even for this type of thing. 2723:19:12, 25 January 2015 (UTC) 2571:18:47, 25 January 2015 (UTC) 712:, I asked for clarification 2222:that he was doing it as an 2050:Comment by Timotheus Canens 1546:anarchy at the very worst. 1442:lily-white undies, either: 490:of pseudoscience, not only 4127: 3536:Statement by Lightbreather 3092:Short comment from Collect 2525:19:46, 16 March 2011 (UTC) 2434:01:04, 12 March 2011 (UTC) 2419:That is not the case here. 2374:23:20, 11 March 2011 (UTC) 2302:21:59, 10 March 2011 (UTC) 2272:14:17, 10 March 2011 (UTC) 2248:14:05, 10 March 2011 (UTC) 2182:14:40, 10 March 2011 (UTC) 2157:08:42, 10 March 2011 (UTC) 2130:15:23, 10 March 2011 (UTC) 2114:08:51, 10 March 2011 (UTC) 2083:05:56, 10 March 2011 (UTC) 2029:17:10, 11 March 2011 (UTC) 2004:01:12, 10 March 2011 (UTC) 1957:00:00, 10 March 2011 (UTC) 1429:04:05, 10 March 2011 (UTC) 1395:02:10, 10 March 2011 (UTC) 1368:14:21, 10 March 2011 (UTC) 1350:07:16, 10 March 2011 (UTC) 1249:01:53, 10 March 2011 (UTC) 1163:16:49, 10 March 2011 (UTC) 1122:enforcing ArbCom sanctions 966:17:16, 10 March 2011 (UTC) 853:On AE sanctions in general 847:23:25, 11 March 2011 (UTC) 617:09:25, 10 March 2011 (UTC) 527:00:37, 10 March 2011 (UTC) 270:Response to Stephan Schulz 242:at the time of the unblock 38: 3923:. Since then we've had a 3171:Penny for your thoughts? 2576:Case or decision affected 1851:23:01, 9 March 2011 (UTC) 1819:23:22, 9 March 2011 (UTC) 1800:21:59, 9 March 2011 (UTC) 1767:22:03, 9 March 2011 (UTC) 1753:21:59, 9 March 2011 (UTC) 1737:21:35, 9 March 2011 (UTC) 1709:21:11, 9 March 2011 (UTC) 1682:21:11, 9 March 2011 (UTC) 1653:18:56, 9 March 2011 (UTC) 1625:17:32, 9 March 2011 (UTC) 1605:17:09, 9 March 2011 (UTC) 1601:Penny for your thoughts? 1581:Comments from HJ Mitchell 1576:16:13, 9 March 2011 (UTC) 1556:15:35, 9 March 2011 (UTC) 1502:15:33, 9 March 2011 (UTC) 1472:17:31, 9 March 2011 (UTC) 1456:15:13, 9 March 2011 (UTC) 1320:15:36, 9 March 2011 (UTC) 1295:15:36, 9 March 2011 (UTC) 1207:14:53, 9 March 2011 (UTC) 1188:11:15, 9 March 2011 (UTC) 1139:09:51, 9 March 2011 (UTC) 1111:08:27, 9 March 2011 (UTC) 1022:19:15, 9 March 2011 (UTC) 828:20:37, 9 March 2011 (UTC) 801:17:16, 9 March 2011 (UTC) 777:07:51, 9 March 2011 (UTC) 684:20:53, 9 March 2011 (UTC) 666:14:47, 9 March 2011 (UTC) 596:07:28, 9 March 2011 (UTC) 564:06:59, 9 March 2011 (UTC) 466:16:26, 9 March 2011 (UTC) 432:10:55, 9 March 2011 (UTC) 398:17:47, 9 March 2011 (UTC) 376:15:50, 9 March 2011 (UTC) 359:08:22, 9 March 2011 (UTC) 336:08:30, 9 March 2011 (UTC) 298:07:40, 9 March 2011 (UTC) 265:06:38, 9 March 2011 (UTC) 4110:Please do not modify it. 3696:Statement by Newyorkbrad 2549:Please do not modify it. 2440:Please do not modify it. 2346:Administrator behaviour 1486:I'm not sure this block 733:In short, the block was 586:Sandstein and reject. -- 304:Response to Roger Davies 157:Please do not modify it. 2379:Comment by BullRangifer 1527:or other suitable venue 1478:Comment by Arthur Rubin 873:hasty, angry, or biased 3711:in each and every case 3472: 3180:Statement by Sandstein 2280:Comment by Will Beback 1856:Statement by Dreadstar 1561:Comment by Cube lurker 1193:Comment by Ncmvocalist 165:Statement by Sandstein 3672:Statement by Mrjulesd 3648:Statement by Gaijin42 3473: 2187:Comment by SlimVirgin 2046:04:30, 10 March 2011 1714:Comment from Moreschi 689:Statement by Ludwigs2 3605:GGTF ArbCom Remedies 3479:AEdecisions}" /: --> 3357: 2090:administrator review 2053:The way I interpret 1825:Comment by WJBscribe 1694:and has no purpose. 1610:Comment from Protonk 1488:should be considered 1400:that the unblock is 1116:Statement by Mathsci 782:Response to Jclemens 635:User:Volunteer Marek 472:Response to Deadstar 343:Response to Jclemens 307:The threat was made 118:Drafting arbitrators 3503:Statement by Risker 2538:Original discussion 2326:Comment by Franamax 240:did not constitute 3631:User:Lightbreather 3465: 3356:AEdecisions}": --> 3126:link to discussion 2550: 2452:Comment by Piotrus 1981:Talk:Pseudoscience 1849: 1226:? I'd think not). 1037:Talk:Pseudoscience 870:In the hands of a 861:In the hands of a 185:, and applied the 158: 3988: 3498: 3323: 3298: 3285:policy exceptions 3259: 3219: 3072:Statement by Floq 2622: 2591:arbitration case 2548: 2397:Elen of the Roads 2335:Editor behaviour 2318: 2246: 2027: 2014: 2002: 1962:Comment by 2over0 1955: 1842: 1706: 1679: 1377: 1376: 1325: 1324: 1229: 1215: 834:Comment to Risker 525: 464: 430: 396: 374: 357: 334: 296: 263: 156: 146: 145: 141: 130: 116: 100: 92:Proposed decision 89: 78: 67: 4118: 4100: 4095: 4076: 4030: 4024: 3987: 3937: 3905: 3888: 3877: 3860: 3832: 3806: 3688: 3683: 3635:Hell in a Bucket 3496: 3480: 3475: 3474: 3466: 3322: 3320: 3313: 3310: 3297: 3295: 3288: 3273: 3258: 3256: 3249: 3231:known consensus. 3218: 3216: 3209: 3172: 3166: 2870: 2799: 2682: 2655:deleted contribs 2592: 2522: 2520: 2495:Advocates needed 2399:, among others: 2316: 2298: 2293: 2245: 2243: 2041:Heimstern Läufer 2021: 2012: 1996: 1953: 1949: 1705: 1702: 1701: 1678: 1675: 1674: 1645: 1602: 1596: 1329: 1300: 1227: 1213: 1019: 1016: 986:I am constantly 963: 960: 949: 844: 841: 825: 822: 810:with respect to 807:Comment to Coren 798: 795: 774: 771: 765: 759: 548: 524: 522: 515: 463: 461: 454: 452: 446: 429: 427: 420: 395: 393: 386: 373: 371: 364: 356: 354: 347: 333: 331: 324: 295: 293: 286: 262: 260: 253: 194: 188: 135: 124: 110: 94: 83: 72: 61: 51: 34: 33: 4126: 4125: 4121: 4120: 4119: 4117: 4116: 4115: 4114: 4113: 4098: 4093: 4072: 4028: 4022: 3998:NativeForeigner 3933: 3901: 3884: 3867: 3856: 3826: 3800: 3757: 3745: 3698: 3674: 3650: 3627: 3574: 3570: 3565: 3561: 3557: 3554: 3538: 3505: 3352: 3351: 3335: 3316: 3314: 3304: 3291: 3289: 3283:outside of the 3267: 3252: 3250: 3212: 3210: 3182: 3170: 3162: 3157: 3121: 3094: 3074: 3056:204.101.237.139 3028:204.101.237.139 3023: 3021:Statement by IP 2864: 2751: 2690: 2640: 2553: 2532: 2523: 2518: 2512: 2454: 2449: 2444: 2443: 2381: 2328: 2309: 2296: 2291: 2282: 2255: 2253:Comment by Tarc 2241: 2189: 2165: 2140: 2052: 2036: 2034:Comment by Heim 2011: 1964: 1951: 1858: 1827: 1775: 1716: 1703: 1699: 1676: 1672: 1660: 1651: 1640: 1632: 1612: 1600: 1592: 1583: 1563: 1510: 1480: 1439: 1378: 1334: 1326: 1305: 1195: 1171: 1118: 1030: 1017: 1014: 961: 958: 901: 885:Littleolive oil 842: 839: 823: 820: 796: 793: 772: 769: 763: 757: 740:, and at worst 691: 625: 571: 544: 536: 518: 516: 504:this discussion 457: 455: 450: 444: 423: 421: 389: 387: 367: 365: 350: 348: 327: 325: 289: 287: 256: 254: 192: 186: 167: 161: 151: 56: 55: 54: 47: 43: 30: 29: 28: 12: 11: 5: 4124: 4122: 4107: 4106: 4105: 4088: 4087: 4083: 4067: 4066: 4065: 4064: 4063: 4062: 4036: 4035: 4018: 4004: 3992: 3980: 3963: 3944: 3943: 3942: 3910: 3893: 3880:as individuals 3851: 3841: 3840: 3839: 3793: 3792: 3791: 3756: 3753: 3752: 3751: 3744: 3741: 3697: 3694: 3673: 3670: 3649: 3646: 3626: 3623: 3576: 3575: 3572: 3568: 3563: 3559: 3555: 3552: 3537: 3534: 3519: 3518: 3514: 3504: 3501: 3499: 3486:All the best: 3464: 3461: 3458: 3455: 3452: 3449: 3446: 3443: 3440: 3437: 3434: 3431: 3428: 3425: 3422: 3419: 3416: 3413: 3410: 3407: 3404: 3401: 3398: 3395: 3392: 3389: 3386: 3383: 3380: 3377: 3374: 3371: 3368: 3365: 3362: 3334: 3331: 3330: 3329: 3328: 3327: 3302: 3265: 3264: 3263: 3224: 3223: 3205: 3194: 3193: 3190: 3181: 3178: 3156: 3153: 3142:TenOfAllTrades 3120: 3117: 3093: 3090: 3073: 3070: 3069: 3068: 3067: 3066: 3048: 3047: 3046: 3045: 3022: 3019: 3018: 3017: 3016: 3015: 3014: 3013: 3012: 3011: 2989: 2988: 2987: 2986: 2985: 2984: 2965: 2964: 2963: 2962: 2961: 2960: 2946: 2945: 2944: 2943: 2942: 2941: 2924: 2923: 2922: 2921: 2920: 2919: 2897: 2887: 2886: 2885: 2884: 2859: 2858: 2843: 2842: 2833: 2832: 2831: 2830: 2827: 2824: 2817: 2816: 2806: 2805: 2731: 2689: 2686: 2685: 2684: 2629: 2628: 2627:in particular) 2584: 2579: 2577: 2554: 2545: 2544: 2543: 2542: 2531: 2528: 2511: 2508: 2507: 2502: 2497: 2492: 2487: 2482: 2465: 2464: 2461: 2453: 2450: 2448: 2445: 2437: 2411: 2410: 2406: 2405: 2380: 2377: 2361: 2360: 2359: 2358: 2355: 2351: 2344: 2343: 2342: 2339: 2327: 2324: 2311:What a farce. 2308: 2305: 2281: 2278: 2276: 2254: 2251: 2188: 2185: 2164: 2161: 2139: 2136: 2135: 2134: 2133: 2132: 2051: 2048: 2035: 2032: 2010: 2007: 1989:Magnet therapy 1963: 1960: 1907:, SlimVirgin: 1857: 1854: 1839: 1826: 1823: 1822: 1821: 1774: 1771: 1770: 1769: 1755: 1715: 1712: 1659: 1656: 1646: 1631: 1628: 1611: 1608: 1582: 1579: 1562: 1559: 1535: 1534: 1531: 1528: 1521: 1509: 1506: 1505: 1504: 1479: 1476: 1475: 1474: 1462:questionable.— 1438: 1437:Comment by Kww 1435: 1434: 1433: 1432: 1431: 1375: 1374: 1373: 1372: 1371: 1370: 1356:<start: --> 1336: 1335: 1332: 1327: 1323: 1322: 1307: 1306: 1303: 1298: 1283: 1282: 1279: 1276: 1273: 1270: 1267: 1264: 1261: 1257: 1256: 1252: 1251: 1236: 1235: 1231: 1230: 1218: 1217: 1194: 1191: 1170: 1167: 1166: 1165: 1117: 1114: 1029: 1026: 1025: 1024: 1009: 1008: 1003: 1002: 998: 997: 996: 992: 983: 969: 968: 952: 951: 899:NuclearWarfare 880: 879: 878: 868: 850: 849: 835: 831: 830: 808: 804: 803: 783: 731: 730: 726: 719: 707: 706: 705: 690: 687: 624: 621: 620: 619: 609:Stephan Schulz 588:Stephan Schulz 570: 567: 535: 532: 531: 530: 473: 469: 468: 440: 436: 435: 406: 402: 401: 344: 340: 339: 305: 301: 300: 271: 166: 163: 162: 153: 152: 150: 147: 144: 143: 108:NuclearWarfare 59:Main case page 53: 52: 44: 39: 37: 31: 15: 14: 13: 10: 9: 6: 4: 3: 2: 4123: 4111: 4104: 4101: 4096: 4090: 4089: 4084: 4082: 4079: 4077: 4075: 4069: 4068: 4061: 4057: 4053: 4052: 4046: 4042: 4041: 4040: 4039: 4038: 4037: 4034: 4031: 4025: 4019: 4016: 4012: 4011: 4005: 4003: 4000: 3999: 3993: 3991: 3986: 3985:Seraphimblade 3981: 3979: 3975: 3971: 3970: 3964: 3962: 3958: 3954: 3950: 3949:Supervenience 3945: 3941: 3938: 3936: 3930: 3926: 3922: 3918: 3914: 3911: 3909: 3906: 3904: 3897: 3894: 3892: 3889: 3887: 3881: 3875: 3871: 3866: 3865: 3864: 3861: 3859: 3852: 3850: 3847: 3842: 3838: 3837: 3834: 3831: 3830: 3824: 3819: 3813: 3812: 3811: 3808: 3805: 3804: 3798: 3794: 3790: 3786: 3782: 3778: 3774: 3773: 3772: 3768: 3764: 3759: 3758: 3754: 3750: 3747: 3746: 3742: 3740: 3739: 3735: 3731: 3726: 3722: 3720: 3716: 3712: 3706: 3702: 3695: 3693: 3692: 3689: 3684: 3682: 3671: 3669: 3668: 3664: 3660: 3656: 3647: 3645: 3644: 3640: 3636: 3632: 3624: 3622: 3621: 3617: 3613: 3612:Lightbreather 3608: 3606: 3602: 3599: 3596: 3593: 3590: 3585: 3584: 3581: 3551: 3550: 3549: 3547: 3543: 3535: 3533: 3532: 3528: 3524: 3515: 3511: 3510: 3509: 3502: 3500: 3494: 3493: 3490: 3484: 3481: 3462: 3459: 3456: 3453: 3450: 3447: 3444: 3441: 3438: 3435: 3432: 3429: 3426: 3423: 3420: 3417: 3414: 3411: 3408: 3405: 3402: 3399: 3396: 3393: 3390: 3387: 3384: 3381: 3378: 3375: 3372: 3369: 3366: 3363: 3360: 3349: 3346: 3342: 3338: 3332: 3326: 3321: 3319: 3308: 3303: 3301: 3296: 3294: 3286: 3281: 3277: 3271: 3266: 3262: 3257: 3255: 3246: 3245: 3244: 3240: 3236: 3235: 3230: 3226: 3225: 3222: 3217: 3215: 3206: 3203: 3198: 3197: 3196: 3195: 3191: 3187: 3186: 3185: 3179: 3177: 3176: 3173: 3167: 3165: 3154: 3152: 3151: 3147: 3143: 3138: 3133: 3131: 3127: 3118: 3116: 3115: 3111: 3107: 3103: 3099: 3091: 3089: 3088: 3084: 3080: 3071: 3065: 3061: 3057: 3052: 3051: 3050: 3049: 3042: 3041: 3040: 3039: 3038: 3037: 3033: 3029: 3020: 3010: 3006: 3002: 2997: 2996: 2995: 2994: 2993: 2992: 2991: 2990: 2983: 2979: 2975: 2971: 2970: 2969: 2968: 2967: 2966: 2957: 2952: 2951: 2950: 2949: 2948: 2947: 2939: 2935: 2930: 2929: 2928: 2927: 2926: 2925: 2917: 2916: 2912: 2905: 2901: 2898: 2896: 2893: 2892: 2891: 2890: 2889: 2888: 2883: 2879: 2875: 2868: 2863: 2862: 2861: 2860: 2857: 2853: 2849: 2845: 2844: 2840: 2835: 2834: 2828: 2825: 2822: 2821: 2819: 2818: 2813: 2808: 2807: 2803: 2797: 2794: 2791: 2788: 2785: 2782: 2779: 2776: 2773: 2770: 2767: 2764: 2761: 2758: 2755: 2750: 2746: 2743: 2740: 2736: 2732: 2730: 2727: 2726: 2725: 2724: 2720: 2716: 2711: 2708: 2704: 2701: 2698: 2694: 2687: 2680: 2677: 2674: 2671: 2668: 2665: 2662: 2659: 2656: 2653: 2650: 2647: 2644: 2639: 2636: 2635: 2634: 2633: 2626: 2620: 2616: 2612: 2608: 2604: 2600: 2596: 2590: 2589: 2585: 2583: 2580: 2578: 2575: 2574: 2573: 2572: 2569: 2565: 2561: 2558: 2557:Initiated by 2552: 2541: 2540: 2539: 2534: 2533: 2529: 2527: 2526: 2521: 2515: 2506: 2503: 2501: 2498: 2496: 2493: 2491: 2488: 2486: 2483: 2481: 2478: 2477: 2476: 2473: 2469: 2462: 2459: 2458: 2457: 2451: 2446: 2441: 2436: 2435: 2431: 2427: 2421: 2420: 2415: 2408: 2407: 2402: 2401: 2400: 2398: 2394: 2390: 2386: 2378: 2376: 2375: 2371: 2367: 2356: 2352: 2348: 2347: 2345: 2340: 2337: 2336: 2334: 2333: 2332: 2325: 2323: 2319: 2312: 2306: 2304: 2303: 2300: 2299: 2294: 2285: 2279: 2277: 2274: 2273: 2269: 2265: 2260: 2252: 2250: 2249: 2244: 2237: 2234: 2228: 2225: 2221: 2217: 2216: 2213: 2210: 2208: 2205: 2201: 2197: 2196:Pseudoscience 2192: 2186: 2184: 2183: 2179: 2175: 2171: 2162: 2160: 2158: 2154: 2150: 2146: 2145:Pseudoscience 2137: 2131: 2127: 2123: 2118: 2117: 2116: 2115: 2111: 2107: 2101: 2097: 2091: 2087: 2086: 2085: 2084: 2080: 2076: 2071: 2067: 2063: 2056: 2049: 2047: 2045: 2042: 2033: 2031: 2030: 2025: 2020: 2008: 2006: 2005: 2000: 1995: 1990: 1986: 1982: 1978: 1974: 1968: 1961: 1959: 1958: 1954: 1948: 1944: 1942: 1937: 1936: 1932: 1928: 1925: 1923: 1920: 1916: 1915: 1912: 1910:, Xxanthippi 1909: 1906: 1903: 1900: 1895: 1894: 1892: 1887: 1885: 1882: 1877: 1875: 1871: 1869: 1867: 1864: 1855: 1853: 1852: 1848: 1845: 1836: 1832: 1824: 1820: 1816: 1812: 1808: 1804: 1803: 1802: 1801: 1797: 1793: 1790:the unblock. 1789: 1785: 1781: 1772: 1768: 1764: 1760: 1756: 1754: 1750: 1746: 1741: 1740: 1739: 1738: 1734: 1730: 1724: 1721: 1713: 1711: 1710: 1707: 1695: 1691: 1689: 1684: 1683: 1680: 1667: 1664: 1657: 1655: 1654: 1650: 1644: 1638: 1629: 1627: 1626: 1622: 1618: 1609: 1607: 1606: 1603: 1597: 1595: 1587: 1580: 1578: 1577: 1573: 1569: 1560: 1558: 1557: 1553: 1549: 1543: 1539: 1532: 1529: 1526: 1522: 1519: 1518: 1517: 1513: 1507: 1503: 1500: 1497: 1493: 1492:WP:COMPETENCE 1489: 1485: 1484: 1483: 1477: 1473: 1469: 1465: 1460: 1459: 1458: 1457: 1453: 1449: 1445: 1436: 1430: 1426: 1422: 1417: 1412: 1407: 1403: 1398: 1397: 1396: 1392: 1388: 1384: 1380: 1379: 1369: 1365: 1361: 1355: 1354: 1353: 1352: 1351: 1347: 1343: 1338: 1337: 1331: 1330: 1321: 1317: 1313: 1309: 1308: 1302: 1301: 1297: 1296: 1292: 1288: 1280: 1277: 1274: 1271: 1268: 1265: 1262: 1259: 1258: 1254: 1253: 1250: 1246: 1242: 1238: 1237: 1233: 1232: 1225: 1220: 1219: 1211: 1210: 1209: 1208: 1204: 1200: 1192: 1190: 1189: 1185: 1181: 1176: 1168: 1164: 1160: 1156: 1152: 1148: 1143: 1142: 1141: 1140: 1136: 1132: 1127: 1126:Pseudoscience 1123: 1115: 1113: 1112: 1109: 1106: 1101: 1097: 1096:pseudoscience 1092: 1088: 1085: 1083: 1079: 1075: 1070: 1068: 1063: 1059: 1056: 1051: 1046: 1042: 1038: 1033: 1027: 1023: 1020: 1011: 1010: 1005: 1004: 999: 993: 989: 984: 980: 979: 976: 975: 974: 973: 967: 964: 954: 953: 947: 944: 941: 938: 935: 932: 929: 926: 923: 920: 917: 914: 911: 908: 905: 900: 896: 893: 890: 886: 881: 875: 874: 869: 866: 865: 860: 859: 857: 856: 855: 854: 848: 845: 836: 833: 832: 829: 826: 817: 813: 809: 806: 805: 802: 799: 789: 784: 781: 780: 779: 778: 775: 762: 754: 752: 746: 743: 739: 736: 727: 724: 720: 717: 714: 711: 708: 703: 702: 700: 696: 695: 694: 688: 686: 685: 681: 677: 672: 668: 667: 663: 659: 655: 652: 648: 647: 644: 642: 638: 636: 633: 630: 622: 618: 614: 610: 605: 600: 599: 598: 597: 593: 589: 585: 581: 577: 568: 566: 565: 561: 557: 553: 549: 547: 540: 533: 529: 528: 523: 521: 513: 509: 505: 499: 497: 493: 489: 485: 481: 474: 471: 470: 467: 462: 460: 449: 441: 438: 437: 434: 433: 428: 426: 417: 411: 407: 404: 403: 400: 399: 394: 392: 384: 383:WP:UNINVOLVED 378: 377: 372: 370: 360: 355: 353: 345: 342: 341: 338: 337: 332: 330: 319: 314: 310: 306: 303: 302: 299: 294: 292: 284: 280: 276: 272: 269: 268: 267: 266: 261: 259: 251: 247: 243: 239: 234: 232: 228: 223: 221: 217: 213: 209: 204: 202: 198: 191: 184: 180: 176: 175:pseudoscience 172: 164: 160: 148: 142: 139: 134: 128: 123: 119: 114: 109: 105: 101: 98: 93: 87: 82: 76: 71: 65: 60: 50: 46: 45: 42: 36: 35: 27: 23: 19: 4109: 4073: 4049: 4044: 4008: 3996: 3967: 3935:Roger Davies 3934: 3903:Roger Davies 3902: 3886:Roger Davies 3885: 3879: 3858:Roger Davies 3857: 3827: 3822: 3820: 3816: 3801: 3796: 3748: 3727: 3723: 3714: 3710: 3707: 3703: 3699: 3680: 3675: 3651: 3628: 3609: 3586: 3577: 3569:unilaterally 3548:should say: 3545: 3541: 3539: 3520: 3506: 3487: 3485: 3482: 3471:AEdecisions} 3350: 3347: 3343: 3339: 3336: 3317: 3292: 3279: 3275: 3270:Roger Davies 3253: 3232: 3228: 3213: 3200:concerned: " 3183: 3163: 3158: 3136: 3134: 3122: 3101: 3095: 3075: 3024: 2955: 2937: 2914: 2910: 2908: 2894: 2867:Roger Davies 2792: 2786: 2780: 2774: 2768: 2762: 2756: 2741: 2735:Eric Corbett 2728: 2712: 2706: 2705: 2702: 2696: 2695: 2691: 2675: 2669: 2663: 2657: 2651: 2645: 2631: 2630: 2594: 2587: 2567: 2556: 2555: 2546: 2536: 2535: 2509: 2474: 2470: 2466: 2455: 2439: 2422: 2418: 2413: 2412: 2389:Arthur Rubin 2382: 2362: 2329: 2320: 2313: 2310: 2289: 2286: 2283: 2275: 2256: 2238: 2232: 2229: 2218: 2203: 2193: 2190: 2166: 2141: 2102: 2098: 2094: 2059: 2037: 2015: 1976: 1975:rather than 1972: 1969: 1965: 1938: 1929: 1917: 1896: 1888: 1878: 1874:this comment 1862: 1859: 1834: 1828: 1806: 1787: 1783: 1779: 1776: 1725: 1717: 1696: 1692: 1687: 1685: 1668: 1661: 1642: 1636: 1633: 1613: 1593: 1588: 1584: 1564: 1544: 1540: 1536: 1514: 1511: 1496:Arthur Rubin 1487: 1481: 1440: 1415: 1410: 1405: 1401: 1383:at any cost. 1382: 1284: 1196: 1174: 1172: 1147:Weston Price 1119: 1093: 1089: 1086: 1071: 1064: 1060: 1054: 1049: 1034: 1031: 971: 970: 942: 936: 930: 924: 918: 912: 906: 891: 872: 871: 863: 862: 852: 851: 787: 755: 750: 747: 741: 737: 734: 732: 692: 670: 669: 656: 653: 649: 626: 603: 572: 545: 538: 537: 519: 500: 491: 487: 477: 458: 448:uw-sanctions 424: 419:decisions). 413: 390: 379: 368: 361: 351: 328: 321: 312: 290: 257: 244:, or indeed 235: 224: 205: 168: 154: 133:Roger Davies 117: 103: 102: 63: 57: 3913:Ncmvocalist 3874:Ncmvocalist 3743:Clerk notes 3730:Newyorkbrad 3560:by editor A 3478:ArbCom: --> 3477:Policy: --> 3470:ArbCom: --> 3469:Policy: --> 3355:ArbCom: --> 3354:Policy: --> 3307:Newyorkbrad 3164:HJ Mitchell 3079:Floquenbeam 3001:Ncmvocalist 2974:Ncmvocalist 2940:address it. 2938:effectively 2904:noted today 2874:Ncmvocalist 2848:Ncmvocalist 2772:protections 2715:Ncmvocalist 2683:(initiator) 2638:Ncmvocalist 2560:Ncmvocalist 2292:Will Beback 2174:Count Iblis 2170:this policy 1594:HJ Mitchell 1568:Cube lurker 1421:Ncmvocalist 1387:Ncmvocalist 1360:Ncmvocalist 1342:Ncmvocalist 1312:Ncmvocalist 1287:Ncmvocalist 1241:Ncmvocalist 1199:Ncmvocalist 922:protections 897:) got from 641:User:Ocaasi 604:arbitrating 4023:Guerillero 3953:Dougweller 3846:Courcelles 3823:de minimis 3492:Farmbrough 3318:Sandstein 3293:Sandstein 3276:de minimis 3254:Sandstein 3214:Sandstein 3102:sua sponte 2956:reasonably 2784:page moves 2673:block user 2667:filter log 2242:SlimVirgin 2233:uninvolved 2149:Xxanthippe 2055:WP:AEBLOCK 1863:appearance 1831:WP:AEBLOCK 1786:consensus 1720:WP:AEBLOCK 1663:WP:AEBLOCK 1333:@Timotheus 1012:my 2¢. -- 934:page moves 812:this claim 742:vindictive 671:Suggestion 629:User: PPdd 520:Sandstein 512:Xxanthippe 508:Hans Adler 459:Sandstein 425:Sandstein 416:WP:AEBLOCK 391:Sandstein 369:Sandstein 352:Sandstein 329:Sandstein 291:Sandstein 258:Sandstein 197:WP:AEBLOCK 190:uw-aeblock 104:Case clerk 3896:Sandstein 3870:Thryduulf 3781:Thryduulf 3763:Thryduulf 3655:WP:POINTy 3580:Guettarda 2934:Thryduulf 2778:deletions 2749:Sandstein 2679:block log 2426:Brangifer 2259:Trusilver 2122:T. Canens 2106:T. Canens 2075:T. Canens 1947:Dreadstar 1844:WJBscribe 1548:Thryduulf 1416:each time 1224:like this 928:deletions 729:behavior. 699:this diff 546:Doc James 410:statement 227:unblocked 177:article ( 3797:in pejus 3681:Mrjulesd 3659:Gaijin42 3540:If this 3098:Zugzwang 2760:contribs 2745:contribs 2649:contribs 2393:Franamax 2366:Franamax 2224:AE block 2066:WP:ARBPS 1940:forward. 1811:Johnuniq 1792:Johnuniq 1759:Moreschi 1745:Moreschi 1729:Moreschi 1643:Critical 1406:Everyone 1045:provided 910:contribs 895:contribs 556:contribs 492:articles 231:declined 81:Workshop 70:Evidence 41:Shortcut 24:‎ | 22:Requests 20:‎ | 4029:My Talk 3229:against 3130:closure 3106:Collect 1904:, TFD: 1617:Protonk 1180:Collect 1155:Mathsci 1131:Mathsci 1050:modicum 1043:' – 'I 1015:Ludwigs 959:Ludwigs 877:manage. 840:Ludwigs 821:Ludwigs 794:Ludwigs 770:Ludwigs 761:unblock 735:at best 496:WP:TBAN 216:Collect 49:WP:AESH 4099:(ʞlɐʇ) 3829:Salvio 3803:Salvio 3687:(talk) 3523:Risker 3137:wasn't 2900:Risker 2790:rights 2766:blocks 2395:, and 2257:Well, 2062:WP:ANI 2044:(talk) 1985:Magnet 1973:topics 1890:later. 1847:(talk) 1788:before 1704:le_Jrb 1677:le_Jrb 1499:(talk) 1402:always 988:IARing 940:rights 916:blocks 816:wp:IAR 639:, and 576:WP:IAR 484:remedy 482:. The 275:warned 220:N419BH 131:& 4056:talk 4045:prior 4015:talk 3974:talk 3777:Roger 3430:: --> 3409:: --> 3388:: --> 3239:talk 2729:Sigh! 2519:talk 2350:good. 2024:cont. 1999:cont. 1977:pages 1784:clear 1688:don't 1525:WP:AN 1108:Adler 1074:RFC/U 751:ought 723:wp:AN 584:Trout 560:email 488:topic 480:WP:AN 279:asked 238:WP:AN 208:WP:AN 171:WP:AN 122:Coren 16:< 3957:talk 3917:here 3872:and 3785:talk 3767:talk 3734:talk 3663:talk 3639:talk 3629:For 3616:talk 3527:talk 3489:Rich 3146:talk 3110:talk 3083:talk 3060:talk 3032:talk 3005:talk 2978:talk 2895:Note 2878:talk 2852:talk 2754:talk 2739:talk 2719:talk 2661:logs 2643:talk 2564:talk 2430:talk 2370:talk 2297:talk 2268:talk 2264:Tarc 2178:talk 2153:talk 2126:talk 2110:talk 2079:talk 1815:talk 1796:talk 1763:talk 1749:talk 1733:talk 1649:Talk 1621:talk 1572:talk 1552:talk 1468:talk 1452:talk 1425:talk 1391:talk 1364:talk 1346:talk 1316:talk 1304:@Kww 1291:talk 1245:talk 1203:talk 1184:talk 1159:talk 1135:talk 1105:Hans 1055:very 904:talk 889:talk 788:kind 680:talk 662:talk 613:talk 592:talk 552:talk 510:and 313:very 309:here 138:Talk 127:Talk 113:Talk 97:Talk 86:Talk 75:Talk 64:Talk 26:Case 4074:AGK 4051:DGG 4010:DGG 3969:DGG 3546:2A) 3280:not 3234:DGG 2812:OWN 2796:RfA 2707:2A) 2697:1A) 2613:) ( 2605:) ( 2597:) ( 2385:Kww 2204:one 2019:2/0 1994:2/0 1807:now 1464:Kww 1448:Kww 1175:not 1098:or 946:RfA 676:TFD 658:TFD 283:did 246:now 222:). 203:). 4094:DQ 4058:) 4026:| 3976:) 3959:) 3787:) 3769:) 3736:) 3665:) 3641:) 3618:) 3556:An 3542:is 3529:) 3495:, 3241:) 3168:| 3148:) 3132:. 3128:, 3112:) 3085:) 3062:) 3034:) 3007:) 2980:) 2918:" 2880:) 2854:) 2721:) 2615:pd 2599:ev 2568:at 2566:) 2510:-- 2432:) 2391:, 2387:, 2372:) 2270:) 2180:) 2172:. 2159:. 2155:) 2128:) 2112:) 2081:) 1886:) 1835:be 1817:) 1809:. 1798:) 1780:if 1765:) 1751:) 1735:) 1647:__ 1637:BE 1623:) 1598:| 1574:) 1554:) 1470:) 1454:) 1427:) 1393:) 1366:) 1348:) 1318:) 1293:) 1247:) 1205:) 1186:) 1161:) 1137:) 956:-- 791:-- 767:-- 764:}} 758:{{ 682:) 664:) 615:) 594:) 562:) 558:· 554:· 451:}} 445:{{ 385:. 320:. 218:, 193:}} 187:{{ 120:: 106:: 90:— 79:— 68:— 4054:( 4017:) 4013:( 3972:( 3955:( 3876:: 3868:@ 3783:( 3765:( 3732:( 3661:( 3637:( 3614:( 3525:( 3463:s 3460:n 3457:o 3454:i 3451:s 3448:i 3445:c 3442:e 3439:d 3436:E 3433:A 3427:m 3424:o 3421:C 3418:b 3415:r 3412:A 3406:y 3403:c 3400:i 3397:l 3394:o 3391:P 3385:y 3382:t 3379:i 3376:n 3373:u 3370:m 3367:m 3364:o 3361:C 3309:: 3305:@ 3272:: 3268:@ 3237:( 3144:( 3108:( 3081:( 3058:( 3030:( 3003:( 2976:( 2876:( 2869:: 2865:@ 2850:( 2798:) 2793:· 2787:· 2781:· 2775:· 2769:· 2763:· 2757:· 2752:( 2742:· 2737:( 2717:( 2681:) 2676:· 2670:· 2664:· 2658:· 2652:· 2646:· 2641:( 2623:( 2621:) 2619:t 2617:/ 2611:t 2609:/ 2607:w 2603:t 2601:/ 2595:t 2593:( 2562:( 2516:| 2428:( 2368:( 2266:( 2176:( 2151:( 2124:( 2108:( 2077:( 2026:) 2022:( 2001:) 1997:( 1952:☥ 1813:( 1794:( 1761:( 1747:( 1731:( 1700:A 1673:A 1641:— 1639:— 1619:( 1570:( 1550:( 1466:( 1450:( 1423:( 1389:( 1362:( 1344:( 1314:( 1289:( 1243:( 1201:( 1182:( 1157:( 1133:( 1018:2 962:2 948:) 943:· 937:· 931:· 925:· 919:· 913:· 907:· 902:( 892:· 887:( 843:2 824:2 797:2 773:2 678:( 660:( 631:, 611:( 590:( 550:( 210:( 199:( 140:) 136:( 129:) 125:( 115:) 111:( 99:) 95:( 88:) 84:( 77:) 73:( 66:) 62:(

Text is available under the Creative Commons Attribution-ShareAlike License. Additional terms may apply.

Knowledge (XXG)

talk:Arbitration/Requests/Case/Arbitration Enforcement sanction handling - Knowledge (XXG)

Index