Knowledge talk:Requests for arbitration/Editing of Biographies of Living Persons

6182:), and then attempting to WikiLawyer around them. At some point when there is a pattern of continually approaching the line and stepping up to it, an individual crosses it, and I felt, as did the other AE admins, that DHeyward's behavior here, especially on the Scarborough article, reached that point. This pattern can also be seen with the new AE thread: if he had made that post while his appeal wasn't being considered at ARCA, it would have been an unquestionable topic ban violation, but because Jimmy Wales still in theory has the right of appeal from ArbCom (which he never exercises), it is a grey area that admins are put in an impossible place of enforcing: his commentary was more on the state of American politics on Knowledge than anything else, but he discussed my comment at this ARCA as a part of it, so it was grey.Finally, I do want to address DHeyward's behavior at AE, which I linked to in diff's above. I did consider Mr. Ernie's suggestion on DHeyward's talk page that I let it off with a warning: it would have been the easiest way out. At the same time, DHeyward had violated TPO on AE, and edit warred to reinsert those violations. He'd also just redirected his own talk page to AE, effectively canvassing his watchers there, and had edit warred to keep the redirect. Both of these behaviors are disruptive, especially to a high intensity process that attracts partisans from every angle to defend their friend or attack their opponent. I felt that the behavior in the thread, combined with what I saw as a bright line violation at Scarborough, and edge cases elsewhere, meant that DHeyward was likely to continue to be disruptive in areas where discretionary sanctions were active, as he had previously when hitting 4 reverts on a 1RR article.There was a consensus at AE that the topic ban should be reset, and that it should be made AP2, and I had reason to believe that he would likely continue disruption in the topic area since he was demonstrating the same behavior that led to a topic ban (edit warring) during the AE process. Given these circumstances, and the fact that the AN appeal did not achieve consensus to overturn, I think I was within my discretion to act upon the consensus of AE admins, and that I could reasonably expect that the TBAN would be preventative rather than punishment. I'm sorry to the arbs for my long comment, but this is a complex situation, and I felt that I should explain as clear as possible the reasoning given some of the questions Newyorkbrad raised. 6252:, I think the most concerning thing about your actions to me is that you haven’t once admitted that others might reasonably disagree with you, and that you insist that you were 100% in the right. Every admin at AE thought you violated your topic ban, and you kept insisting that there was no way you could have: when many reasonable people tell you that they view something differently than you, it is normally a sign that they may be seeing something you aren’t. I was strongly considering letting this off with a warning, but the edit warring on your own talk page and at AE were huge mistakes that suggested to me that you needed a longer break from this contentious area, especially when combined with what seemed to me and other admins to be pushing the limits on sanctions. I see how you might see these as BLP violations: I disagree that they were ban exempt, but I recognize your point of view. My largest concern is that if you go back into the area you will continue edit warring when you think you are right, even if reasonable people disagree and it should be discussed on the talk page. I think these concerns are warranted, and are the main reason that looking at the totality of the picture, I am still uncomfortable lifting sanctions, especially considering that I feel you have misrepresented a lot of what I have said here and haven’t recognized that much of your behavior as a part of the AE process has been disruptive. I would be willing to consider changing the sanction to 0RR in AP2 as a sign of good faith given your last post, but I would not be comfortable at this time completely lifting sanctions. 6211:, and when you consider that he is probably the most high profile news media personality to be in conflict with the President of the United States, I think he falls squarely within the sanction, just by looking at the article itself. I also see a history of trying to get around sanctions in this area, both with the original TBAN AE thread, the actions that led to this AE, and the various actions afterwards.Finally, in the context of the appeal above, I think it would be a bad idea for the committee to overturn this. Above, Sandstein is being critiqued for acting independently of other admins when there was no clear consensus at AE. Here, I acted with the unanimous consensus of all AE admins, and the appeal was not overturned at AN. While the committee is of course free to do as it chooses, criticizing one administrator for his actions not working with other admins in AE above, while also overturning a sanction that was unanimously deemed to be merited by other administrators at AE makes the forum very difficult to work in, and raises the question of whether an administrator should unilaterally close an AE filing without sanctions, when there is a clear agreement amongst administrators that sanctions should occur. I'm willing to admit my mistakes in the original TBAN wording, and while I can see why others might not have sanctioned, given the information that I was faced with at the time, the disruption that had been actively occuring on AE, and the consensus of administrators there, I think that I acted within discretion and in a procedurally correct manner. 4100:. No one is repeating the claims on-wiki. There is a very obtuse view that a link can, by itself, be a BLP violation. That's nonsense. We have much stricter policies regarding links in articles, but links provided for discussion can be ignored, or archived without affecting the encyclopedia. There is more disruption by deleting links on talk pages than by ignoring them. Revdel's are even more asinine. The reality is that a talk page discussion that says "Does this link have anything we can use ?" is not the same as saying "This link says Person X did Y, can we use it ?". The latter should be redacted if the claims are BLP violations, the former should be ignored or commented on but it need not be removed. We can't even control secondary content in sources in articles, so why stifle discussion (or worse, punish editors for trying to start a discussion? If we source NY Times in an article and they decide to have an inline link that leads to characterizations that WP would not publish (i.e. say a criminal charge), that doesn't forever invalidate the source. Papers like the guardian have second level links that are "NAtional Inquire"ish type stories on celebrities. 3965:

will be more anonymous trolls than there are good-faith editors and admins left to defend the project's basic principles in contentious topic areas. The goal of these trolls is simple: raise the personal cost of defending the project's basic policies beyond that which anyone wants to bear. Already I have been subjected to numerous attacks, death threats and harassment methods on and off the encyclopedia, for doing little more than demanding that our articles adhere to what reliable sources say, and that our articles reject anonymous attempts at assassinating the character of living people. ArbCom has taught the trolls that all they have to do is depict those who stand up against them as engaging in "battleground behavior" and they win. Already we've seen them come after JzG and others. If you don't think they'll keep going after every single person who tries to enforce the policies against them, you're delusional. And at some point, everyone with a shred of sanity will throw up their hands and give up — even the redoubtable HJ Mitchell, to whom I will entrust any future BLP violations I identify. ArbCom has written the textbook for destroying Knowledge from within.

6654:'s original topic ban placed on DHeyward was not a well formed sanction. Tony himself didn't even seem to understand what it covered, as seen by the AE request he brought and then retracted. If the sanctioning admin can't understand a sanction they create, how can we expect an editor to? Additionally, DHeyward's offending edit was removing a borderline BLP error. I will assume good faith and believe DHeyward when he says he didn't think Scarborough qualified as a politician AND that he was enforcing BLP. What caused more disruption to the project? The offending edit was a clear improvement to the article. The resulting attempts to punish DHeyward for running afoul of a poorly worded sanction and subsequent appeals have taken us to AN, Jimbo's page, AE (trips for DHeyward, MONGO, and The Rambling Man), and now ARCA. Tony continues to support his sanction, claiming the consensus from fellow admins at AE is on his side - but of course it is. Admin's rarely choose to side with editors when potential admin mistakes are involved, especially editors who have committed the cardinal sin of having a block log. 4925:

latitude than use in an article due to the difference in visibility. But "wide" doesn't mean "unlimited", and if someone is using such a discussion as a coatrack to push BLP violations or the material is egregiously bad, that is not acceptable and someone is right to stop it. In this case, I think NBSB had a good faith belief enforcement was necessary, and that assessment clearly was not way out of line with consensus on the matter. I therefore see no reason to overturn HJ Mitchell's decision that a legitimate exemption to a topic ban applied here. However, NBSB, I'd strongly advise you to take Gamergate related items off your watchlist. You were quite properly warned that while this instance fell under a topic ban exemption, your ongoing discussion of the matter after the topic ban was in place was clearly not allowed by it, and while that's stale for enforcement at this time, I think you could expect enforcement action if that continues. Topic bans apply to user talk pages as surely as any others.

554:, and has been at issue in the past. The question of the appropriateness of use of the quote function and how this user has been utilizing it has been at issue well beyond the ones under discussion. As noted by KrakatoaKatie above regarding the Dan Antonioli article, large blocks of quotes were used in the absence of them being incorporated into articles. At no time during the Antonioli discussion was any attempt made by the author to incorporate and expand the article with the use of those sources. This particular article had been under question for deletion and my involvement came from supporting the retention of the article, with the caveat that it needed a LOT of work, and in trying to urge its expansion, was met with the lack of response and the uptake of the argument by Alansohn, the same circumstances indicated by RedSpruce above. One argument at the time from 6199:, yes, I agree looking back, the sanction should have been an AP2 sanction. Oddly enough, I was trying to prevent WikiLawyering when I placed the article under the BLP page level restrictions at the time. I did not clarify after the 9 December AE, because I thought at the time it was clear that politicians were covered, and he should take a wide breadth from them. I had already been accused of being on a vendetta against him (which I wasn't), and I felt that increasing the sanctions for AP2 at that time he might view as vindictive rather than a clarification, but I also felt that the ban shouldn't be removed, because 4 reverts on 1RR is a lot of disruption.In terms of this specific appeal, and your question regarding politicians, I will push back a bit. While you can argue whether or not the city councilman is an American politician here, when the 4496:@62.157.60.27 takes me to task for "spreading misinformation about the ArbCom case even in his statement above" and for various other high crimes. If 62.157.60.27 has some particular correction to offer, 62.157.60.27 might be so good as to identify it. In the same jeremiad, 62.157.60.27 is apparently outraged that Brianna Wu expressed an opinion in the pages of Bustle with which 62.157.60.27 does not agree and wants ArbCom to do something about it. Like the flowers that bloom in the spring (tra la!) this has nothing to do with the case. The paragraph bearing my name is irrelevant, uncivil, and assumes no good faith; it is also very interesting that its “uninvolved” author is so well acquainted with the topic and with intricacies of Knowledge procedure but does not possess (or does not desire to use) a Knowledge account. 6230:: to your question of why TBAN him: because he has consistently shown over the last month that he is an editor who simply doesn't care what the behavioral norms are of Knowledge or what sanctions are in place so long as he thinks he is right. That indicates a strong likelihood that he will continue to be disruptive in the topic area. His edits here might be done in good faith (he thinks he is right, that he is being wronged, etc.) but they are still disruptive. That's how he got in this situation to begin with: 4 reverts on a 1RR article. It is a serious behavioral problem that needs to be addressed, and skirting the topic ban around the edges, and then crossing the on an article he should have 4522:@Rhoark’s standard of imminent harm creates a new "extra-special BLP" for talk pages. Would (to choose a pertinent example) saying that a software developer has prostituted herself rise to this standard? Would saying that she had slept with more than five men rise to this level? Would saying that the software developer had faked threats of assault, rape, and death qualify? These are three of the BLP violations in question here; they have been discussed many times and at great length on the talk page, as ArbCom members (all of whom have, I am sure, read the entire talk page archives with care and attention) well know. But of course the separate, vague, higher standard for BLP on talk pages is 1570:. Unfortunately, this finding continues to hold true today. The remedy that was enacted at the time of the finding was invoked several times as the case log indicates; Postdlf and Good Ol'factory whom invoked this remedy in 2009, have since been repeatedly subject to uncivil and unseemly conduct by Alansohn, including personal attacks (including in the form of very serious yet unsubstantiated allegations), as well as other inflammatory commentary and assumptions of bad faith. Allegations made in the heat of the moment is one thing, but this involves repeatedly making the same allegations, yet refusing to provide any evidence to substantiate them (despite being requested to do so). 6174:, I agree, in general, with your observations, but of course with the difference that I thought it was worth sanctioning. There are two factors that I think you and ArbCom should also consider here: the pattern of behavior that occurred both before and after this new topic ban which is now being discussed at AE, and the behavior of DHeyward during the AE thread itself. On the first case, from my reading of the AE thread, and the previous AE action where DHeyward had 4 reverts on a 1RR article, followed by a self-revert to his preferred version, he had a pattern of pushing the limits on what was acceptable in a sanctions, claiming BLP exemptions that are not obvious (as required by 7515:. This raised sub-issues, including: (1) whether the topic-ban included talk pages (I'm surprised that could still be unclear at this late date); (2) whether Erica Garner was a "politician" (debatable, but understandable to think not); (3) whether Joe Scarborough is a "politician" (he isn't today, though he used to be, but perhaps his is a "related article, broadly construed"); (4) whether removing a reference to a Donald Trump tweet referencing a blatantly false accusation against Scarborough constituted BLP enforcement (another instance of the Allegations Problem, which is one of the most difficult areas of BLP line-drawing, as I've discussed 6078:(and I think there are more, but it would likely be easier to see by reading the thread). This all is disruptive editing that makes both the AE process and the appeals more difficult for uninvolved editors to review, and has the potential to have a chilling effect on those that disagree with him. Despite this, there was no consensus at AN to overturn the sanction, and the consensus of administrators at AE was to reset the topic ban. I am fine with whatever the committee decides to do, but I see no way to get around the fact that a former member of congress who is also a prominent political commentator is well within this topic ban on 1948:. This is because the problem with Alansohn's behavior has been consistent. It didn't end during his year-long sanction period, it didn't end when the year-long sanction expired in June 2009, and it hasn't stopped since. In the June 2009 clarification linked to, when concerns were expressed that Alansohn's behavior had not improved, the arbitrators strongly encouraged Alansohn to render moot the question of how this case should proceed by improving his behavior. Other than saying that, no one answered the question of what we do next, and no one clarified the question of what should be done if the behavior doesn't improve: 6051:.I will note that my sanction here was the unanimous consensus of all admins commenting on the AE thread, and that there was no consensus at AN to overturn the appeal. I have no issue with the committee reviewing my actions here, and I have admitted and realized the topic ban could have been worded better to begin with: that does not affect DHeyward's sanction in this case however, as there was a clear and blatant TBAN violation and there were several others that were on the edges here.I also think that the committee should take into account DHeyward's conduct on his talk page, where he edit warred to redirect it to AE: 5273:"enforce the removal of clear BLP violations", however "in less clear cases they should request the attention of an uninvolved administrator". Involved admins can, therefore, use normal admin tools in clear cases. However, discretionary sanctions grant individual admins much more power and authority (in comparison normal admin tools when involved can be overturned by any other admin) so should only be used when the circumstances are absolutely clear and the admin is neutral. To answer the question more precisely, an admin can block or protect as a normal admin action but not impose a discretionary sanction. 1643:. In such circumstances, I find your position in those remarks incomprehensible. I would not have filed this request, had the problematic conduct merely been (or was likely to have been) an isolated incident. To be specific, in the 3 or 4 years I've provided uninvolved input at WQA, I can only recall one other incident where an user filed a retaliatory WQA and engaged in other incivility against uninvolved users, and even that was greeted with a sharp response; but if you think that such conduct is commonplace at WQA against uninvolved users, I invite you to submit evidence to that effect. 127:

control-f and search for "gay" or "homosexual" because Wolfe doesn't use any of those words. You have to read the whole article to find the single sentence where Wolfe says: "But so far as Mr. Schine is concerned, there has never been the slightest evidence that he was anything but a good-looking kid who was having a helluva good time in a helluva good cause. In any event, the rumors were sizzling away ..." For a book you would have to get the book at a library, to look up the text. If the quote parameter is used and the exact wording for the sentence is known, it can be searched in Google Book.

1576:. During this WQA, I also provided input as an uninvolved user. However, Alansohn has now attempted to involve me in his conflicts by filing a retaliatory WQA over something for which he was not a party to. The community is reluctant to say any further, when this intimidation tactic shall be employed by Alansohn against any user whom strongly makes a finding against him. The improvement in his conduct has, therefore, been so marginal that it has dismally failed to adhere to Knowledge's expected standards of behavior and decorum. Plenty of evidence is available to substantiate this at 8952:. A bot currently handles that AN notification. I don't know where Buffs gets the idea that discretionary sanctions has anything to do with the ECP policy, and I don't see the problem with the rationales as they are. If ECP is applied as a discretionary sanction, the admin should say so and log it, but it's not always the case that ECP is applied as a DS. (I don't think I've ever done it as a DS, but I could be wrong.) If it isn't, a standard rationale of 'persistent sockpuppetry' or 'persistent vandalism' or 'violations of the BLP policy' (and so forth) is sufficient for me. 5981:

out by Coffee. And I'll point out that Tony doesn't think BLPONUS applies to my edit that only removed material from Scarborough or that the lead states he is a former politician. In light of all that, there is no joy in participating where my time is being eaten up in these spaces defending edits that the community finds acceptable. I have no intention of violating 1RR, no intention of violating any discretionary sanction. I don't wish to be involved in any more disputes with TonyBallioni. There's no point in participating, though, if edits like the ones I made to

177:. Again the burden is one me, the person adding the information, to persuade the skeptic that the infomation is factual and verifiable. Although I thought they were well referenced, I should have been even more clear in the sources and quotes so that the information could stay in the article. I should never overburden the fact checker, it should be as easy as possible to confirm with clickable links, and quoted information. As the skeptical fact checker points out, the burden is on the person adding the fact to the article, to show that is comes from a reliable source. 5906:

filed as a party and you didn't clarify. When you filed as a party on Dec 9, you didn't recuse later per admin accountabilty but instead ignored your own admission of vagueness and implemented a new ban under a different arncom remedy. Shit, I don't even know when it expires because it's new but you keep saying it's an extension. What you should have done is to come out and say "I fucked up, the TBAN is expired. All the edits were productive." Only the last statement is true, though - "All the edits were productive." That makes you "THAT admin." --

2724:. The index of topics with an active discretionary sanctions provision will be updated with the new title, but previous references to the Footnoted Quotes decision do not need to be updated. The central log page of discretionary sanctions, however, should be updated for the current year. For prior years the new name should be noted along with the old one. The rename of the Footnoted Quotes case to Editing of BLPs is only for clarity in reference, and does not invalidate any previous action or pending sanctions taken under the provisions of this case. 3871:'s statement is an example of exactly why this needs clarification. It seems the arbs feel that some links are clearly not okay (which I agree with), but the "cut off" is what's blurry here. If arbs are unable to rule on this, what course of action would be recommended? An RfC invites all users to comment, including inexperienced ones. Given that this topic is (1) one of the most important policies on Knowledge, and (2) the subject of an ARBCOM ruling, it seems that ARBCOM should be the one to clarify it and make substantial changes to it. 3848:

about a politician committing fraud, then the talk page is the right venue to discuss that article. However, not all links are covered by BLPTALK, or shouldn't be. Links to Stormfront would never be acceptable. Links that contain libel or highly disparaging content should never be allowed. Folks seem to be misunderstanding "contentious material" and misrepresenting the example in BLP. Let's clarify it so that if (1) matches the rest of the BLP policy's intent and (2) matches how BLP is being enforced.

5963:. I didn't give those edits a second thought nor cared about his politics. He was in the news regarding the security of microchips with speculative execution of branching instructions that access kernel memory locations using the hardware page table but then flush the instruction pipe without clearing table entry (not necessary for execution but leaving it can lead to side channel attack). The edits weren't controversial and fixed language around his stock sales. They aren't disruptive edits. I 9037: 5195: 1857:

filing of this request for amendment and I wished this latest incident could have been resolved via regular dispute resolution channels. The only solution that I personally think would solve the CFD/DRV problem completely would be banning Alansohn from CFD/DRV participation (though I do worry that he would then create the same problem in another discussion area of Knowledge). It's gone on a long, long time and many editors have shown a lot of forbearance. It needs to be resolved. —

8967:, that third paragraph deals with the history of ECP, not the current state. I accept that there are a number of rationales which are subpar, however that's not a question for ARCA. It's a question for the admins who placed ECP those rationale - we also have RFPP and AN if it cannot be resolved with the admin in question. For a review of ECP on a wider scale, can I suggest an RfC? At any rate, I'm not seeing the problem that needs to be clarified from an Arbcom perspective. 4852:. Since to restore what someone else has flagged as a BLP violation you need a consensus, it follow that it is permissible to discuss in good faith possible BLP violations in talk space and on the appropriate noticeboard; after the discussion is over, if it's determined that the material was indeed a violation, then the discussion may be hatted or purged of the offending material, but, again, there needs to be a place where such a discussion can be had without hindrance. 2573:(Caveat: I was inactive when this case was decided.) In general, sitebans and blocks are restarted when violations (typically socking) are detected. However, the clock on other types of sanctions, such as the civility restriction imposed in this case, typically is not automatically reset upon a violation. I very strongly urge that Alansohn render this discussion a moot issue by adhering to a reasonable level of civility both before or after the one-year period expires. 8693:. Applying ECP is like any admin action—it might be reasonable to ask an admin why they had taken the action. However, it should be assumed that the first case applies if and only if mentioned in the edit summary. Admins have to take a lot of actions and requiring a discussion should be rare. In the second case, if there is reason to think that page protection should be reduced, ask the admin to do that or make a request at 3864:, I wish to be clear that I 100% agree with his and other admins' assessments of the situation and reading of the BLP policy. However, BLPTALK is still rather ambiguous and given the push back from other users I feel that ARBCOM weighing in on this issue and/or suggesting clarified wording of BLPTALK is needed. I chose this venue because of the past ruling and felt an RfC would not be the appropriate way to address this. 2008:. I have always been reluctant to block someone for conduct other than repeated vandalism. But given Alansohn's very clear editing restrictions, the extreme nature of his comments, and the fact that this was part of a pattern on his part that I had already tried to address with him on multiple occasions, I thought (and still think) a block was very appropriate. I logged it pursuant to his editing restrictions. 8826:, to follow up on my comments there: uses of page protection that are not explicitly related to active arbitration should be dealt with in standard community venues. If the use of protection outside of remedies has truly risen through dispute resolution without a solution emerging it should be dealt with as its own case and not shoehorned on to an old case that primarily dealt with behavior over a different issue. — 5949:

to blame me for it here to justify a brand new sanction. It is true that I was frustrated by this behavior and I could have acted better. But describing an edit on my talk page as nefarious "canvassing" when every single AE action starts with a notice on a users talk page about the AE discussion, lacks intellectual rigor. I notified Tony about this discussion on his talk page which I'm sure others saw and followed.

1104:), who wields absolute power as God-King of the project, understood to be separate from whatever Foundation responsibilities he might have. The community has no powers to "delegate" to the committee; there is the right to vanish and the right to fork. The community is always free to elect arbitrators who take a less expansive view of Arbcom's role but until such time it has authorized this body to act on its behalf. 4109:

pages are being disruptive, not collaborative. Ignore it per WP:BEANS. WP is not responsible for what others say offsite nor is a link any kind of affirmation. We've learned this with links to articles about the ArbCom committee itself. The stories were false. Portraying them as true on WP is problematic. Linking to them without judgement is not. Witch-hunting for those that dared add the link is disruptive.

7729:

when he returns, but I think he reasonably believed he was within the bounds of his editing restriction with the Scarborough/Montell/BLM edits. The topic ban is reset, however, this time explicitly under AP2. DHeyward appeals to AN, where there's no consensus to overturn it. As a participant in the AE threads, Sandstein should probably have let someone else close the AN thread, but he didn't, so there you go again.

6413:(to pick just one random example out of many) to see that members of Congress are frequently referred to as "politicians" - even long after they're dead or have left office. Our BLP articles obviously detail what people did throughout their lives not just what they are doing right now, it seems absurd to me that a biography of someone who served in Congress should not be considered a biography of a politician. 5924:

might be okay only in Scarborough is awful interpretation of BLP policy. A good question to ask yourself in these decisions is : "Will the WaPo include this information in the obit?" Answer: no. The fact that you don't see that it could be a BLP and the he might not be considered a politician is a huge AGF problem solved by a talk page comment. It's lunacy to think the same edit 3 days later is okay. --

8219: 3950:

it's inconvenient for you to be continually exposed to a reminder of how unjust the decision was and how precisely I predicted what would happen in its wake — a continual series of SPAs appearing and reappearing to demand that, in this topic area, reliable sources be ignored, BLP violations be accepted and living people be slandered. That is, as it happens, exactly what is going on now.

8853:; for example any admin that lowered a full or template protection to ECP for IAR reasons. It also seems that it would tie all those admins to this case - the core of which has nothing to do with applying protection outside of arbitration remedies or the enforcement thereof. It also appears to assume that "their reasoning" is actually lacking or otherwise not already explained. — 664:

But this arbitration case, of course, is not the place to debate the merits of such a change - the point is that Mr. Norton is unwilling to abide by the rules, which say that if one is unable to convince (the majority) of other editors of the merits of one's position, then it is unacceptable to continue on as if a negative consensus did not exist. Mr. Norton's editing is

2515:

necessary to deal with any future perceived problems -- real or imagined -- once these "editing restrictions" are over. Only now they will have to be weighed against real standards with proper oversight, and applied under the same standards that should be applied to all editors with (hopefully) a small measure of the consistency that has been absent over the past year.

6394:

step of the way. There is nothing inherently wrong with that, but if you believe - as I do - that the tban violation was clear cut then it does seem disruptive. Also, if the 2 appeals currently under consideration here end with the sanction being overturned you should probably all be prepared to spend a lot more time reading arca appeals of ae sanctions going forward.

3124:, it's called (bearing in mind that cases are very rarely cited by their full name, but by the applicable shortcut) but that the title is not ambiguous. The reason for the change is that possibly the broadest set of discretionary sanctions we have is authorised under an obscure case from seven years ago and under a name that gives no indication of its scope. 2113:

seen him on the project since, he has been contributing constructively and, in particular, making useful contributions to CfD and other areas. On looking at the evidence in this case, I am not seeing the problems which led to the Footnoted quotes case manifesting themselves, so it should not be treated as a "request for amendment" of the previous case.

515:. I was not very experienced or assertive as an admin, and I was intimidated, quite frankly, by the in-your-face, long-winded approach I faced on that talk page. When Woohookitty voiced her opinion, I dropped the issue, and the article remained as it was. The quotes in the references have been shortened somewhat in the current version of the article. 8207:. I asked for clarification and reminded him that, if it was under DS, to file it in the appropriate logs (even going so far as to provide a link to make it easier should that be the rationale). He stated that he probably overstepped where the protection needed to be. In the other, I asked for clarification and the Admin apparently felt it WAS under 1634:

users who contribute in DR) are extremely familiar with. I filed this request solely based on the conduct displayed by Alansohn during and after the WQA, and I've never contributed to (nor had a particular interest or position in) CFDs. In fact, the closest I could've come to interacting (if at all) with any of the users listed would've been on

2511:

thousand articles, expanded articles for every one of the 566 municipalities and 120 state legislators in New Jersey and almost all of its school districts and high schools (I think I've missed a few), written from scratch over 300 DYK articles (the most of any Knowledge editor) and been one of the most prolific vandal fighters in my spare time.

1892:'s comment below contains some interesting allegations that suggest to me that he may not be assuming good faith about those who have already posted here. I'll let most of his comments suggesting conspiratorial undertones and sneaky cabals speak for themselves. However, it's probably necessary that I respond directly to the following: 1912:, but it is purely a Knowledge association and is entirely the result of our interactions at CFD that have taken place since this time. This is exactly the same tactic that Alansohn has adopted in alleging that I had a conflict of interest in performing those blocks—he has taken events and relationships that have developed 3927:. This sense is longstanding and core to our policy's ultimate goal: ensuring that what the encyclopedia publishes about living people is well-supported, fair, sensitively-written and unsensational — all stemming from the use of highly-reliable sources and the avoidance of slander, gossip, whisper campaigns and rumormongering. 6590:, which is within the same calendar month. My view was that this clearly violated the topic ban as the Garner topic was related to multiple US politicians, when "broadly construed", as the ban stated. Myself, I have no particular axe to grind about US politics as I'm British and had only started the article in response to a 6271:

DHeyward acted very disruptively throughout this process, but if the committee thinks that a sanction should not happen because the wording was vague enough that good faith should be assumed, I will respect their judgement. Having a forum other than AE and AN to look at this is important, and I appreciate their review.

103:

is still left to wonder what preceded 'Cohn's boyfriend'. " Cohn's boyfriend" is very different from " Cohn's boyfriend". Which is it, if any? I looked up the ones I quoted because I wanted to see the exact wording. Others shouldn't have to repeat the effort to find out the exact, non-truncated, single-sentence quote.

2534:"So please clarify what you feel the "next step" should then be?" Evaluate all users fairly and objectively, both for those who agree with your personal interpretations of policy and especially those who don't where your judgment may be clouded. Avoid using administrative measures with editors where there is a clear 4407:

much-discussed question of whether actions associated with the GamerGate hashtag may be excluded because someone says "they were not really GamerGate supporters" and whether GamerGate is a "movement". One of the GamerGate victims had a 550 word libel revdel'd again; as you know, this is hardly a rare occurrence.

7696:, DHeyward says he used the guidance given there, about articles vs. edits, to frame his editing for the duration of the sanction. I see nothing that leads me to conclude that this is not true. I'm very puzzled why the sanction was not removed or at least clarified at this point, but it wasn't, so there you go. 7224:. If AE sanctions are truly intended to be anti-disruptive and not punitive, then identifying the disruptive action is the single most valuable thing to do. Even if you think the sanctioned editor is too stupid to understand, say it for the benefit of other editors reading the public, transparent thread. 7408:

that DHeyward has posted a retirement notice, which I am sure is not an outcome that anyone was hoping for. Since many retirements are non-permanent and the appeal hasn't been withdrawn, I'll be concluding my review regardless of it; the retirement announcement will not affect my analysis or conclusions.

8778:

With respect to my own protection cited here, the Kurdish set of articles had been a haven for socking-based disruption from confirmed accounts for months before I finally had to apply ECP to a set of related articles, to the relief of regular contributors. Anyway, some of these confirmed users would

8524:

Which is why I have a problem with the way this was initially brought to AFCA. I never said it was. This is no more than a straw man argument. There are hundreds of pages on the list of ECP protected pages which are BLPs that have nothing to do with ArbCom/DS. I don't have a problem with any of them.

8152:

You are saying that you are fine with this now that we are at ARCA, but the fact is that your most persistent activity of the last few weeks on Knowledge has been policing the use of ECP. As I said, that's fine. What I have an issue with is you making up a requirement that all BLP protections must be

7754:

More generally, if we can get into such a convoluted discussion about an AE sanction, it's time to replace AE. The attempt to have a AE as a procedure that would stick has ended up in a total mess of glue. I've earlier said the only reason I would support continuing AE is my inability to think of a

7748:

As for procedure, i think that: an appeal to arb com is proper. So is the admin removing the sanction themselves. So would be community consensus here or at ANB. The basic rule for procedure is NOT BURO. As for the merits: my first choice is removing the sanction without conditions. Future problems

7728:

DHeyward has strong views on BLP enforcement, and again, I have no reason to question his motives or his statements here. Could he have behaved better at the AE thread? Absolutely. Is his style abrasive to some? Undoubtedly. He should really think about how he approaches editing in these areas if and

7623:

from this specific request as with PMC above. I do want to comment broadly though on the topic of appeals to ARCA. Appealing to AN/AE and then ARCA is perfectly fine. In fact, it's what we'd expect. ARCA is the final venue of appeal, and it's typical to appeal at AE/AN before ARCA. See, for instance,

7539:

The AE admins' consensus was that violations took place, with a one-month reset as the remedy. DHeyward appealed to AN, where by my count 15 editors endorsed the sanction and 11 opposed it. The AN discussion was not the very model of a modern noticeboard debate, though in fairness so few of them are.

7496:

DHeyward argues that he believed that his edits were permissible. He emphasizes, repetitiously but plausibly, that he would not knowingly have violated the topic-ban so close to its expiration. He also points out that the sanction as imposed was ambiguous. (Clarity in sanctioning is good, but no rule

7181:

I feel bad for DHeyward because he keeps finding himself in situations where he is sanctioned, re-sanctioned and reported for violations of the re-sanctions. On the other hand, I don't think that Arbcom should second guess AE admins unless there is strong evidence that they have failed to comply with

6726:

whether the article in question even qualifies is questionable. A friend of mine who died of cancer last year, and who was a Unix system administrator and a book author, and might conceivably be notable, also ran for local public office one time, about 30 years ago. Does that make him a politician?

6725:

While I'm here: I agree with Mr Ernie. It doesn't make sense to enforce a sanction that was unclear to everyone, admittedly so by its author, who didn't get around to clarifying it. Especially when a) it was about to expire anyway, b) the edits were actually productive and made in good faith, and c)

6443:

I think the ban should be rescinded and a huge trout to TonyBalioni for without him, we would not be in this position we are in now. He wrote a horrible TBAN, DHeyward followed the TBAN, got an AE action against him a while back and it was closed as no violation, and DHeyward used that and then a new

6017:

is unambiguously an American politician: he is a former member of congress. That was a bright line that was clearly crossed over. The other cases were edge cases, but there were enough of them that I felt, as did the other admins at AE, that combined with the clear violation at Scarborough, the topic

5272:

WP:INVOLVED says that admins should not act in disputed cases but can act (use admin tools) in "straightforward cases" when "any reasonable administrator would have probably come to the same conclusion". This is entirely consistent with the BLP policy which states that admins when involved may act to

4889:

As Courcelles says, it's not our role to change the wording of BLPTALK, nor do I think we should be mandating a specific interpretation, which would have the same practical effect. AS Salvio says, the application of BLPTALK outside of article space isn't as cut and dried as it is in an article, and I

4402:

You will be pleased to know that @PalinFreeborn is cheering you on, @FortunateCat is calling on your vigor, @ED_Updates -- doubtless that same people who were so very eager for you to take action against Ryulong that they needed to tell you all about his religious background (avaricious Jew!) and sex

4103:

We don't regulate offsite content or links that are twice removed from articles. This is where talk page links are. No one is reading WP and following the link to validate a claim made on WP. If simply following links were bad, without claims, we would need to guard against the side bar content of

4007:

and I) were in agreement that the material in question was a BLP violation. I asked whether this was an isolated incident or a pattern of mis(conduct|judgement) and was presented with evidence of the latter. It would have taken something miraculous for that thread or the one against NBSB to have been

3847:

BLPTALK needs tweaking. The link that prompted this on GG was not just "contentious", it was libel. BLPTALK should reflect that discussion of RS or at least something that approaches RS (which is also key as the link from GG was not RS) is fine. If, for example, HuffPo has an article with some claims

2116:

On the other hand, my observations of some of the editors Good Olfactory names in his statement above are quite negative indeed - they have acted at times in a hostile, inflexible and provocative manner towards good faith editors in the CfD area at times, and if this goes to an actual case, I'll

1799:

he attempts to shift the focus of the discussion to what he views as procedural deficiencies in Knowledge processes (which apparently are intended to act as a justification for his behavior). These methods can be observed in the following recent discussions and the most recent WQA, where a number

1131:

a god-king, he's a very influential editor who has historically been granted certain roles by the community and the foundation. His 'powers' are whatever the community and the foundation collectively give him. If the community and the foundation disagree with Jimbo, the community and the foundation

908:

The only real controversy here, I think, is the same sort that was experienced when discretionary sanctions were enacted for the first time by the Committee. But even then, I wonder how/why it is that much of the community have, particularly in recent times, come to favour the discretionary sanctions

663:

I find it telling that Mr. Norton's statement, at the moment, is to argue the merits of his approach to footnotes. I have seen these arguments before, and continue to find them unconvincing; he both overstates the advantages and fails to consider the disadvantages, which I consider more significant.

81:

1) Allows for reconnection of broken links to a newspaper article. For example: if the title is: "Scientist killed", and the quote is "Today, John Bacon, a New Jersey scientist was killed when his car overturned". A Google search for the title may not find the article, its too general. Using the text

7816:

The issue I, as I see it, is that the sanction was vague in its terminology. As Katie stated above, just who is an "American politician"? Is it someone who ran for public office, and failed and never ran again? Is it someone who served a term 15-20 years ago and since has been in the private sector?

7734:

And here we are. How do I put all that together for myself? Like Brad, I would not have come down on the side of resetting this restriction. Andrew Davidson's rationale for the AE thread was shrill at best and over-the-top hyper-partisanship at worst. Whether we should overturn it is another matter,

7219:

My very best wishes has made some good suggestions regarding DGG's musing on AE reform. I'd like to add more transparency and, to impose a sanction, the enforcing admin must state specifically what action the sanctioned editor performed with at least one dif. If someone else has to be punished for

7127:

Brad, As you know, I endorsed the AE in the AN appeal, and I still do because, it's well within reasonable discretion to find the topics related. We are called upon to review the consensus discretion of other people, not Sandstein, and those people are endowed with their own reasoned discretion, so

6558:

I also want to echo something others have said - this is like the third or fourth venue that DHeyward has "appealed" to. The actual appeal - the one that follows policy - was soundly rejected at WP:AN. If you over turn the sanction then you are not only over ruling admins at WP:AE, you are also over

5980:

I do have pointy elbows sometimes as Katie mentioned. I try to avoid a lot of discussions that have heated participants. I slipped on dec 2 on the 1RR. I'll note as Kingsindian did how TonyBalloni objected to Volunteer Mareks 24 hour topic ban for the same type of 1RR/no consensus violation handed

5883:

Again, Dec 9th, Sandstein said articles that aren't about politicians can be edited even when the edits were about politicians. Erica Garner was/is not a politician. The only edit comes down to whether we should mention the death of a former employee on Scarboroughs article. Reasonable people may

4904:

I agree with Courcelles and Doug. Firstly, BANEX was correctly applied in this case. On the broader point, a blanket statement is not going to help here. It is perfectly legitimate, in almost all cases, to discuss on a talk page whether source X is a BLP violation or not (if consensus is that it is,

3949:

You are asking me to give in to an off-wiki-coordinated harassment campaign because it's apparently inconvenient for Knowledge to deal with the ramifications of the committee's actions. Sorry, but no, I will not just shut up and go away, as you and the endless string of trolls demand. I apologize if

2587:

I agree with Newyorkbrad's comments. With the expiry of the extension, nothing is stopping an administrator from using the restriction, and violations thereof, in considering whether a block is appropriate and if so of what length. If problems are persistent, the community is also free to (re)impose

2320:

I've got to agree with Kirill and Coren, if there are continuing problems that haven't been resolve through the usual channels, a new case might be appropriate, but I don't believe that this can ride on the tailcoats of the old Footnote case since even the restrictions have been expired for most

1638:

while the case was open. I can appreciate that the incivility and other misconduct cited might not match that type you happened to notice in 2007, but that some of his contributions are useful or that the incivility/misconduct has taken on a different form during DR in 2010, does not change the

1633:

I'm not sure whether a couple of your remarks (the last sentence of para 1 and para 2) are stemming from a genuine lack of familiarity with the expected standards of conduct during dispute resolution, or something else. I'm fiercely independent of any user or body of users, as ArbCom (and other

1199:

Logging case sanctions on ArbCom pages is the norm. It makes it easier to locate blocks or bans that are the result of a ruling. Additionally, a page was started to explain the logging requirement. If an actual problems arise from this requirement to log or the page explaining the ruling then we can

1046:

I am quickly approaching formally requesting that the arbitration revoke this 'remedy', and lift the threat of desysopping admins who refuse to accept it. Both of the above RfC statements had strong consensus support and endorsement. You're really not empowered by the community to act in the way you

904:

As in the previous request for clarification, I don't see how the response would be different - no, this is a remedy (not a new policy/guideline), and no, it cannot be voted down by the community. Basically, an area of the encyclopedia is now under a type of discretionary-sanctions-remedy - the mere

209:

editor, including myself, is reverting correct information and restoring back to an error, and the reason is not "clarity of references", then the remaining choices for deleting are: lack of research, or the editor is displaying article ownership. Anon is not equal to incorrect, there is no need for

170:

and other information involving their role in a Senate subcommittee. If the original editor had supplied better information, I am sure the deleter would have been less skeptical of the information and it would have remained. The quote function makes for a complete reference, and takes less effort to

102:

4) Redspruce himself quotes text in some of his notes and references. See below where he writes "On the other hand, author Tom Wicker refers to Schine as 'Cohn's boyfriend'". It takes up a little less space, because he only encloses two words from the text in the quote, but the reader, including me,

76:

in the sentence that was used. If they appear to clutter the article in larger articles, we can always write a few lines of code that can suppress them from displaying, but still allow them to be seen in editing. We could also have the reader choose in preferences if they want them displayed or not.

9109:

I probably could've wordsmithed a little better here to avoid what you're hearing. To be clear, I'm not suggesting any sort of formal amendment to the case or anything like that—rather, in cases where a user has concerns about an application of ECP they should determine which of the scenarios above

7671:

We could have saved ourselves a lot of trouble if the initial sanction had been clear. Setting aside for just a moment DHeyward's claims of removing BLP violations, the BLP policy defines living or recently deceased persons as within its remit. If this had been a simple BLP sanction about living or

7550:

That brings us here. I think DHeyward probably believed, more reasonably in some instances than in others but not beyond the bounds of AGF, that his edits were compliant. DHeyward might be well-advised to refine his editing style if (as I hope) he soon returns to editing, but I would not have voted

7529:

If I had been one of the administrators who worked on this AE thread, I would have found that while he sometimes came close to the line, DHeyward appeared to have a good-faith, rational belief that he had stayed onside each time. I would have opined against sanctioning him, though I would also have

7099:

than a standard AP2 TBAN; it might be arguably broader, since politicians might have other non-political interests which would fall under "related topics, broadly construed." The wording appears at first glance to be narrower than an AP2 TBAN but actually isn't and I think everyone accepts that it

6931:

provision. Please note the latter point, because it is important and I'll come back to it. TonyBallioni is a fervent defender of the "consensus required" provision in numerous venues (and I am a fervent opponent; however, the latter fact is not relevant here because I did not take any admin actions

6551:

It is also clear from DHeyward's statement that he blames everyone but himself for the consequences of his actions (no idea what "intellectual rigor" has to do with following Knowledge policies). Likewise claiming that "I slipped on dec 2 on 1RR" is a bit disingenous seeing as this "slip" consisted

6393:

In reply to some of the comments since I posted this: I'm happy to defer to admins and arbs and accept that the appeal is within established process - I'm not sure I was really arguing otherwise: my point was more simply that DHeyward has used every possible means to challenge these sanctions every

5948:

is baseless. In particular, I wasn't under any sanctions when this second AE was filed and the only action prior that he cited was his aborted Dec 9 AE complaint that he blamed himself. I'm extremely disappointed that TonyBalloni took the blame for his poorly defined sanction but then still tries

5905:

made a blatant error on the dates of Scarborough edit. It was also discouraging to note that you did not bring up your own filing and unclear sanction. It's impossible to keep up with the noise and ignorance, let alone the lack of accountability when a sanction. I asked for clarification when you

4428:

are not, and that the encyclopedia's defender should be less vehement in upholding its rules -- is risible. After all, the matter is a small content dispute: some editors want to use Knowledge to spread claims appearing in unreliable sources that specific women in software development are sluts and

4031:

In light of EF's reply and DHeyward's comment, I'll add: I'm not sure this is within the jurisdiction of ArbCom, but if it were my thoughts are that if something couldn't possibly be considered a reliable source, and it contains potentially defamatory claims, it has no business being linked to from

3964:

Salvio, if you truly believe that an editor's refusal to give into an anonymous harassment campaign aimed at forcing them out of a topic area is "battleground behavior," then you have laid the foundation for the destruction of the project, because there will come a tipping point at which time there

3769:

The same principle applies to problematic images. Questionable claims already discussed can be removed with a reference to the previous discussion. The BLP policy also applies to user and user talk pages. The single exception is that users may make any claim they wish about themselves in their user

2112:

Noting that I have been a past focus of his attention in 2007, and supported all of the previous ArbComs, RfCs, etc as a strong opponent of Alansohn, my observation was (and is) that his behaviour significantly improved after the original ArbCom limitations were put in place and any time I have

1856:

From my perspective, no progress has been made with any of these approaches. The problems associated with Alansohn's behavior have been consistent and relatively unrelenting, with the diffs provided by Ncmvocalist just the latest examples from months of similar behavior. I didn't encourage the

247:

Ironically, it was the inordinate concern on the part of McCarthy and his chief counsel, Roy M. Cohn, regarding the military server of McCarthy committee aid G. David Schine — a concern that may or may not have had a homosexual element to it — that was to precipitate the Army-McCarthy hearings that

8870:

Having been involved in the original discussion (and in fact I was the one that suggested that the WP:AN notification be required. Credit goes to MusikAnimal for the hard work though) on implementing ECP as a discretionary measure I would note that the whole point of the notification list at WP:AN

8244:

to see that there are dozens of pages under ArbCom rulings that are not logged anywhere. When notified, most admins go "Gee, you have a point there. I'll fix that!" Some have dug their heels in and said "No, I'm not going to do that". I haven't pursued such actions beyond a one-on-one conversation

7149:

Welcome and good luck. I don't get your suggestion that you need a definition of politician -- it's ordinary English, right? - and really, if you accept you need such definition, every sanction will read like a phone book -- and I extend the observation of ordinary English to 'topics related to'.

6786:

Arbcom could define a limited "toolbox" of specific types of restrictions that could be used by admins in such areas. For example, making 1RR restriction for a page would be allowed, but highly complicated restrictions (such as "consensus required" by Coffee) would not be included in the toolbox.

6760:

Speaking about this appeal, I do not think that any AE administrator acted outside the limits of their discretion, and therefore I do not see any reason to overturn the decisions on WP:AE and the discussion by WP community on WP:AN. Did AE admins demonstrate good judgement? I think they definitely

5967:

defend them but there is no reward to doing so and I have better things to do than jump when busybodies should just move on (re-read the detail above to get an idea of what I was thinking when Tony ascribed to as an "edge case."). Heck, the only "edge case" where I thought it may have been on the

5923:

I realize this might be your first go round with it but come on. A trump tweet followed by WaPo calling it BS doesn't mean we add it. Ted Cruz didn't assassinate Kennedy and Clinton didn't kill Vince Foster. Trump Tweeted all three and WaPo called bullshit on all three and your assertion that it

5841:

My request for clarification is: when an admin acknowledges confusion in interpretation, files and withdraws complaints that acknowledges it's on him but in the end ignores all that, creates a new TBAN under a different ArbCom remedy even though I didn't violate an AP2 remedies, how is it possible

5830:

Scarborough is no longer a politician and has not run or held office in 17 years. But back to AE: Now, there are tons of admins weighing in. Sandstein and TonyBallioni don't mention the Dec 9 filing and outcome. They both are aware by edit with the problems of clarity and confusion. There is no

5297:

As Callanecc notes above DS gives a lot more latitude to administrators than the normal BLP policy does. When using that extended latitude (AC/DS), administrators are expected to not be involved. In regards to normal actions, there are also many administrators on this site and as the committee has

4700:

and yet he is still somehow allowed to offer his input, while others are topic-banned or blocked for much less? Is there some sort of stipulation that some people or groups of people deserve protection against any kind of violations of these policies, while other living persons or groups of people

4610:

It's still more time than you apparently took before topic banning an admin in good standing for stating the central known fact of the gamergate controversy (a statement which was at the time of the block printed in the signpost, FFS). Sorry if my disgust at your appallingly poor block upsets you.

3827:

strong disagreement with the use of BANEX in this manner, suggesting that any links should be allowed to be posted on article talk pages if they are being discussed. I expressed the belief that BLPTALK need tweaking and that not all links are allowed to be posted on non-article spaces (e.g., links

2121:

problems associated with a very small number of editors who have very strong ideas on How Things Should Be around here - some of the ideas are good, but others are utterly illogical, and these guys brook no criticism and carry grudges, sometimes for years, against editors who take them on. One

1139:

Mind you, I'm not expressing any Anti-Jimbo sentiments at all. I'm not trying to attack Jimbo himself in the slightest, and the statements I say above are, as best I can tell, entirely consistent with how Jimbo views himself-- not as a god-king, but as a UK-esque constitutional monarch whose role

98:

3) It is not a copyright violation, the source is attributed, and the quote is usually a single sentence, well within the confines of "fair use". In the Tom Wolfe example, which has been deleted multiple times, the article is 4,254 words and my quote uses 43 of them, or 1%. Whole paragraphs can be

8108:

I’m not really sure how this is an end-run around ARBPIA4 (which I’ve ignored.) We have someone saying that using the Twinkle defaults for BLP protection requires logging, and when approached about it maintains that is the position. If Buffs is going to continue policing ECP (he can if he wants),

7686:

for elective office? Does it include everyone who ever made a speech on a political topic? Does it include activists? Does it include people who happened to be in the wrong place at the wrong time and wrote a book about their experience? Does it include former military who have written books? The

7407:

I've been reviewing this and the other new AE-related thread today, interspersed with some offline activities, and had reached a tentative conclusion subject to double-checking some things and finalizing my review. I'll be finishing up and posting tonight (Eastern US time). In the meantime, I see

6555:. And instead of acknowledging that DHeyward instead made excuses and tried to get other editors sanctions under various false pretexts. Tony and the AE admins actually went easy on him. Too easy apparently since he then proceeded to violate the limited sanction that was imposed. And here we are. 6270:

the sanction. I have no desire to extend the discussion here, and I respect Katie, DGG, Rick and NYB enough that I'm fine with removing this. I've only ever acted in this manner with regards to consensus, which was in favour of reseting the TBAN at AE. I stand by my recent comments above: I think

4643:

There seem to be constant revdels and topic-bans for what seems to be some of the most innocuous thing like posting a link to any articles or trying to discuss something on talk pages regarding certain people (Anita Sarkeesian, Zoe Quinn for instance), but there seems to be a double standard when

4406:

Look at the progress you have made! Yesterday, a vigorous and lengthy debate on the Talk page has proceeded through an additional 8,000 words of discussion devoted to whether WP:RS shall be disregarded for GamerGate because the entire press is biased against #GamerGate, 2,500 words revisiting the

4289:

to remove good faith links to potential sources (and good faith, sourced, discussion of existing sources). Editors should be able to point (link) to a source, and discuss it's appropriateness without fear of sanction. If a source is not reliable, or not usable for any other reason, that should be

4243:

I am not concerned by any one instance of this type of removal, reversion or deletion nor by the editors involved. I am concerned by the pattern, and the implications on consensus building if it is to become an accepted practice. I ask those commenting and the Arbitrators to focus on the relevant

3914:

matters relating to living people with the utmost sensitivity and care. A hopelessly-unreliable source (such as, for instance, a wholly-anonymous webpage, a personal blog or a series of putative screenshots) that contains or is intended to present highly-negative claims, allegations or inferences

2510:

A year was mandated and a year will end in two weeks. Now Jc37 appears to be trying to maintain this "Footnoted Quotes" beyond what was determined and agreed upon. In the past 12 months, I have made somewhere around 150,000 edits (I haven't counted), added tens of thousands of references to a few

2136:

Ncm: I certainly didn't have you in mind in my comments above - I apologise if I gave that impression. I think you've likely been caught in the crossfire actually - there is a lot more to the disagreement between these parties, in my view, than first appears. The CfD crew's modus operandi is

2022:

In the year since, I have periodically tried to bring his uncivil conduct to his attention, and Alansohn has periodically accused me of having abused my admin powers, alleging a conflict of interest on my part as some perception of his that I was acting only pursuant to a "friendship" (as he

1716:

discussions. As a regular participant at these discussions, I can attest that Alansohn's behavior has not substantially improved since the conclusion of his editing restrictions. I would classify the latest incident as relatively minor in isolation, but the accumulated history of his behavior

8937: 7186:

or established project norms. I concur with TonyBallioni's very patient and detailed explanation. Sandstein's statement about procedure is also on point, while I also acknowledge and respect that many Wikipedians see things much differently. Newyorkbrad's somewhat wordy ;) analysis shows that he

6306:

I have not formed a opinion of my own about the merits of the ban, and I don't think that I need to, because I think that this appeal should be rejected on procedural grounds. Although follow-up appeals to ARCA from AN or AE are allowed, I believe that, to avoid forum shopping, ArbCom should not

5837:

so everyone is operating on their own fresh reading of the ban. TonyBallioni then decides the topic ban should be extended and changed to an AP2 topic ban to avoid confusion. My edit at Scarborough stands as of now and violated nothing. If anything it reinforced both the AP2 and BLP findings by

5683:

I was topic banned for 1 month from articles about living and recently deceased American politicians, and related topics, broadly construed, by admin TonyBallioni. TonyBallioni had placed an article under 1RR using discretionary sanctions authorized under the BLP arbcom (note: not AP2). It was

4909:

need to be hidden or removed). In a minority of cases though, and this is one of them, the BLP violation is so clear and/or so gross that even including it on a talk page is not acceptable. Every case is different though, so it needs to be left to individual judgement as to when this applies. So

4131:

Just a quick clarification and summary: I have no position on WP: BANEX and whether NBSB's actions complied. I'm unfamiliar with the specifics of that policy. My disagreement with EvergreenFir (and others) seems to be in the application of BLP policy, whether on talk pages under WP:BLPTALK or in

4108:

that have a number of "Don't miss" articles. The fact is, if he claim isn't made on WP, the link is immaterial and certainly not a BLP violation. This is longstanding policy to allow for collegial discussion of subjects without fear. That should continue. Those that only delete links on talk

3987:

I have little to add here. I closed two AE requests where the result was astoundingly obvious (and have been taking flak for it on my talk page since). Posting links to obviously inappropriate material, especially where the source couldn't possibly be considered a reliable source for Knowledge's

2088:

I was shocked recently to realize just how long this was going on, and I am disappointed in myself for not being able to bring about a resolution. But I cannot make any progress with someone who dismisses complaints as "trivial," and labels responses to his personal attacks as "trolling."

126:

Well, what exactly do people have to say about whether Schine was gay or not, how strongly did they word it, and what words did they use. For instance the Tom Wolfe article up to a month ago required a paid subscription to the New York Times, but now is a free link, but you still can't just do a

106:

5) It doesn't add to clutter, any more than inline citations do already. No one forces a reader to scroll down to the reference section in an article, any more than one is forced to read the endnotes in a book. In scholarly books they can be between 25-50% of a book's pages. Just a few years ago

7824:

Did DHeyward come close to toeing over the line of his topic ban? Yes, he was close, but WHERE was the line drawn? The effect of the language, timing, and everything else snowballed into what we have now. The appeal is fine to arbcom, and I stand in agreement with in that the sanction should be

7386: 7190:

The question is: should Arbcom members vote to lift sanctions that they personal would not have imposed if they were admining at AE? Think about that carefully. There is a very real risk of establishing a precedent that is going to make you jobs very, very busy and potentially generate a lot of

5156:

I'm asking the Committee to clarify both of those things, what options (regular, DS etc) are and are not available to an administrator who is involved. For example, if you added a blatant BLP vio to an article I already participate in, is blocking you allowed? Is blocking you as a Discretionary

4924:

As pretty well always, there's no blanket ruling to make here. Appropriateness of material is on a case by case basis, though I would say that discussions as to whether or not certain material is appropriate at all should generally be given relatively wide latitude to take place, certainly more

4855:

Removal of material without discussion from talk pages or from the relevant noticeboard should be reserved for cases of egregious and uncontroversial BLP violations. This appears to have been one such case. That said, NBSB, you were right on the merits, but your approach still leaves much to be

3856:

Interpretations of this portion of the BLP policy are clearly divergent. Admins and REVDELers appear to interpret the language differently than some experienced user. Specifically, the current wording of BLPTALK does not explicitly state if some links that would be excluded from articles as BLP

3119:

Does it really matter if it's called "editing of BLPs", "of biographies of living persons", or "of biographies of living people"? Just create redirects from the other two. Ditto the naming convention (requests for arbitration/ versus arbitration/requests/case/). The important thing is not what,

3024:

I think that is a good point. We have a tendency for succinctness when possible (see the recent "Interaction at GGTF" for one even more obtuse to outsiders)... but in this one, you're right. It's likely to get shown to a lot of newer editors due to its breadth. Fine with this being made as a

2514:

Enough is enough. While I still maintain deep concerns regarding the manner in which the original decision was reached, I've done my time and that time is over. I look forward to the end of these restrictions, after which Jc37 will be free to use whatever legitimate administrative measures are

2023:

stated at the time in his response to my block notice). He has never elaborated or supported this accusation. Alansohn has gone so far as to take my words entirely out of context right below my own post, claiming that I myself had described my block of him as "taking the side of a friend";

1964:

The fundamental issue is that Alansohn has a recurring problem with turning content disputes into personal ones, by making attacks on contributors in the course of disagreeing with their arguments or policy/guideline interpretations. I have tried repeatedly to address this with him through

1685:

Well, looking at Alansohn's lack of responsiveness to the clerk's request, I'm not sure if there would be sufficient evidence from both sides for the case to proceed. I don't have anything further to contribute myself, except possibly at workshop-pd stage. My primary concern was Alansohn's

5134:

In an apparent conflict between policy and Arbcom decision, which prevails? My own opinion is that involved Administrators are able to block, but not log it as a Discretionary Sanction and the block would be subject to the lower standard for reversal that we use for other blocks. There isn't a

641:

at this point Wildhartlivie, IvoShandor, Arnoutf, qp10qp, SallyScot, AndToToToo, CBM, Shirahadasha, and I have expressed opposition to the practice of putting chunks of text into footnotes, a practice that is not supported by any Knowledge policy or guideline, and that is in no way the norm at

8214:

Second, yes, I've asked for others to be more clear and, if necessary, to log such actions in accordance with ArbCom directives. In most instances, an admin says "hmm...you have a point there" and it's either clarified, clarified and logged, or any of a number of other actions which amount to

6889:

To clarify, when I said the above, I meant that I thought the purpose of ARCA would be to look at procedural matters (for instance, was the AN request closed correctly? I think it was.) If ArbCom is ready to hear the entire case from the beginning, let me me know and I'll comment accordingly.

1025:

has given a clear expression from the community that 'general sanctions' of this kind, and policy, pseudo-policy, and new processes by arbcom fiat are not allowed. Policy creation, and ability to apply a 'general sanction' to the entire community, are powers never delegated to the Arbitration

184:

As RAN knows, I am the "skeptical editor" in all of the above cases. As RAN knows, in two of these I RVed technical changes made without comment by an anon editor. As RAN knows, in the other cases I was reverting for reasons that had nothing to do with skepticism. As RAN knows, in no case did

4820: 7107:

The only remaining questions in my mind are whether he reasonably relied on Sandstein's interpretation of the ban to be significantly narrower than its bare wording (you accept that he did, if I understand you correctly, and I think I agree, though his subsequent poking at the limits of his

2159:

23–30 September 2008, by which stage they were a functioning and tightly-knit group of coordinated editors and any action taken would in that context be thoroughly compromised as per above. Were it a year rather than a few months I'd strike my comment; as it is I'll leave it, with this

6518:

here. If you get a DS, through WP:AE otherwise, exactly where and how many times can you appeal? It seems like the appeal procedure is: 1) on the sanctioning admin's talk page, then 2) at WP:AN, then 3) here then 4) Jimbo I guess. Is it possible to squeeze in WP:AE or WP:AN/I in there too?

8167:

As for your objections: when someone has made it their mission on Knowledge to enforce policy on something, are incorrect on what the policy says, and invokes ArbCom as a reason for their position when ArbCom has said nothing of the sort, the place you go to ask for clarification is here.

3778:. Although this policy applies to posts about Wikipedians in project space, some leeway is permitted to allow the handling of administrative issues by the community, but administrators may delete such material if it rises to the level of defamation, or if it constitutes a violation of 7103:

Given that scope, the question is not whether Erica Garner or Joe Scarborough are living or recently deceased politicians, but whether they are topics broadly related to politicians, which they clearly are. That would make DHeyward's edits unambiguously violations of the topic ban.

1941:

I understand the concern regarding the "dregding up" of an old case—if nothing had happened regarding the case for 18 months, I would agree. But this is not the first time a user has brought the case before the Arbitration Committee again for clarification or further action; see

6657:

Tony, would you consider removing the current topic ban on DHeyward? His behavior will certainly be closely watched. We've already had one editor retire as a direct result of your administrative actions, and it appears we'll soon have another one retire (if he isn't blocked first).

8949:

combat any form of disruption (such as vandalism, edit wars, etc.) on any topic, given that semi-protection has proven to be ineffective. Notification is to be posted in a subsection of AN for review, unless the topic is already authorized for 30/500 protection by the Arbitration

7286:

In other words, if ya'll are going to do topic based restrictions, precise definition during drafting, and giving the benefit of the doubt to the editor in the gray areas, would reduce the necessity for some much post-edit haggling over whether an edit was or wasn't a violation.

4691:

who has previously been blocked due to statements he made, but was apparently allowed back and is blatantly spreading misinformation about the ArbCom case even in his statement on this very page and has called other editors "rape apologists" on the site he identified as his own

8565:

still applies. Specifically: "While discretionary sanctions give administrators necessary latitude, they must not...repeatedly fail to properly explain their enforcement actions". Saying that no one can even ask removes that layer of accountability to the community as a whole.

5298:

noted before no perception of an admin thinking they are the only one enforcing things gives them the ability to act where policy wouldn't allow it. Doing so could result in DS or sanctions for that administrator. I know that's not claimed here, but felt the need to add it. --

2330:

I'm also not very excited about resuscitating a really old case where the area in which the dispute took place had shifted (from BLP to deletion process) - particularly so when there is a landmark decision right above it. I recommend filing a fresh new case if necessary. -

584:. That discussion was obviously ignored and rejected, which brings it to issue yet again, with the same issues. I truly believe a ruling by ArbCom is necessary in this case since efforts at resolution over a variety of articles with a variety of editors has been the case. 7100:

was a badly-constructed ban. The only respect in which it is clearly narrower than an AP2 ban is that it only applies in article space (and perhaps with respect to people involved in post-1932 politics but who are long deceased, but that question doesn't come up here).

4890:

agree with his comments on material on a talk page or BLPN - it needs to be possible to discuss at least most suggested BLP violations, which might mean including a link. Hatting or purging may be required after a discussion is concluded. I don't see a role for us here.

8807:— it includes Buffs' objection to my application of ECP as well as a comment from another admin, who supported my applying ECP to several Kurdish-related articles. That aside, that this matter is before the Committee —what purview does it have over this?— surprises me. 4849:

hen material about living persons has been deleted on good-faith BLP objections, any editor wishing to add, restore, or undelete it must ensure it complies with Knowledge's content policies. If it is to be restored without significant change, consensus must be obtained

7722:

just before the sanction expired taking center stage. DHeyward is adamant that a) this is a BANEX in that he was removing a BLP violation, and b) Scarborough is not an American politician. He also says he would not have violated the sanction so close to its expiration

5782:"Withdrawing this myself per IAR and Sandstein's comments. This is causing more confusion than it is clarification, and apparently my wording wasn't as clear as I thought it was. Apologies to all involved for wasting any time and anything construed as being personal." 518:

I think Alansohn's allegations about RedSpruce are intended to draw attention away from the core of this request, which is the use of long quoted statements or even paragraphs in cited references and the actions of two editors who almost always act as one. They use a

158:. Again, to persuade the skeptical editor, easy to vet, fully quoted citations should be used to persuade them that the information is real and not vandalism. A good editor should always be skeptical, and that why the best references are complete, and easy to verify. 8750: 7717:

under the topic ban or even under AP2. (January 4 is unquestionably more than a month after December 2, and I have to wonder if NEWBLPBAN wasn't used as an excuse here.) That discussion veers off into AP2 territory quickly, with DHeyward's removal of a section of

6614:

submission form is quite complex and it was quite late at night when I was working through its intricate requirements for diffs and detail. Some latitude should please be allowed for editors who are trying to use the process in good faith but find it difficult.

90:

quote supporting the citation is displayed with the actual wording by the original author. The Knowledge trend should be to make it easy to fact check an article, not harder. You shouldn't have to get a book from the library or purchase an article to find out the

6979:. He has not been a politician for 17 years. However, let's assume for the sake of argument that "past politicians" is covered in the TBAN. So the only way in which DHeyward's edit would be allowed is if it was removing a BLP violation. I come to this very point. 2518:

That I have been able to accomplish so much in this past year given the undue harshness of these restrictions is a small miracle. I look forward to accomplishing that much more in the next year without the claim of "editing restrictions" being waved as a threat.

2274:

I'm not particularly enthusiastic about dredging up a two-year-old case (and a remedy that's been expired for the better part of a year) to sanction someone, even if they do need sanctioning. This would be better framed as a new case request, in my opinion.

5760:"I think that this is technically not a violation. The topic ban was phrased as "topic-banned from articles about ... politicians and related topics". This means that the ban encompasses only politician-related articles, not politician-related edits. While the 9087:

should be asked to clarify their reasoning and/or modify the protection level; 5) admins who have placed ECP as per the "semi-protection has proven to be ineffective" scenario should not be required to also manually log the action. Does this seem to cover it?

8871:

was precisely so that there was a log of all ECP's that were levied, irrespective of what they were levied for. Requiring admins to log it elsewhere _as well as it being automatically logged at AN_ is just a box ticking exercise which adds virtually no value.

821:

This is based on two bits of logic: Editing and improving is the Wiki way; having a policy page noone could edit, and having this page "fixed" for all time with whatever the Arbcom came up with in a few days' discussion goes against this. Secondly, it's basic

3762:, as appropriate. When seeking advice about whether to publish something about a living person, be careful not to post so much information on the talk page that the inquiry becomes moot. For example, it would be appropriate to begin a discussion by stating 2125:

Good Olfactory's admission above that he has used his admin tools to further his position in a dispute to protect friends - something which he should most definitely have taken to AN/I instead - is also an issue. (Read in connection with 2nd note below)

82:

string from the quote will find it. Broken links that can't be reconnected are usually deleted. Even if an external link for the citation is broken, and no other version of the newspaper article appears online, a fully-quoted reference can stand on its own.

7356: 1762:

He users his opportunity to present arguments in CFD and DRV as a vehicle for personal attacks against editors who disagree with him (or, often, against editors who have attempted to intervene with him or have blocked him in the past, including me and

5823:. It's like someone adding the Vince Foster suicide to Hillary Clinton - it's a BLP violation to try and link the deaths of these people into biographies of living people, at least in my mind and I've been battling the people adding it for 10 years (see 5266: 7540:

I note in passing that it might have been better if someone else had closed the AN thread (though the "no consensus" outcome was likely inevitable), and I note with strong disapproval how many people's opinions lined up along predictable partisan lines.

6366:

Come on. This was already appealed at AN and the appeal was declined. Do we really want everyone who is unhappy with their AE sanction appealing to both AN and to ARCA going forward? You can interpret the topic ban as narrowly as you want, it was still

1724:

I will state that prior to the editing restrictions being lifted, I did block Alansohn twice for incidents of trolling, assuming bad faith, and making personal attacks. The first block was made in response to this personal attacks and feuding with

1135:

I'm amazed to see anyone even espousing the notion of an absolute power over any group of humans in the 21st century (even if it is just an encyclopedia-making project). That's just not the way humans do things anymore-- ESPECIALLY not on a Wiki.

7665:

I agree that the appeal is proper. If we're going to have steps in an appeal process, and if those steps are outlined, then an editor has the right to avail him/herself of each of those steps. I'm a newbie here, but I can at least piece together that

4435:

Knowledge talk pages are a weapon against GamerGates’s victims. Those who object to this continuing outrage are necessarily and inconveniently guilty of battleground behavior and must be driven from Knowledge, leaving the way clear for the trolls.

8647:

states "While discretionary sanctions give administrators necessary latitude, they must not...repeatedly fail to log sanctions...Administrators who fail to meet these expectations may be subject to any remedy the committee considers appropriate..."

6842:

and think this request should be closed because this is simply forum-shopping. AE sanctions can be appealed somewhere (either AN or ARCA or AE itself). The former was chosen and it failed, so the matter should be allowed to rest. My condolences to

7925: 7561:

But the question here is not just whether I personally disagree with the AE decision, but whether ArbCom should go so far as to overturn it. Before I reach that question, I'd welcome others' opinions on the views I've expressed so far. Thank you.

5485: 5028: 3229: 85:

2) It provides the actual information for fact checking the citation. It makes it easy to double check references that are already in place. You no longer have to have the attitude "trust me" it is in the book, or it is in the article. The actual

3857:

violations are also excluded from non-article space. Moreover, it's unclear if BANEX covers the removal of links from non-article spaces. I request that the ARBCOM clarify this issue as part of the BLP decision for the sake of users and admins.

7615: 4374:

The attention of the Arbitration Committee is drawn to the circumstance that, last night, this page was widely extolled on Twitter by a variety of anonymous accounts bearing GamerGate regalia and celebrating the expected further sanctioning of

3099:

My objections: Redirects are cheap and renames cause backwards compatibility issues. The chosen name is too close to the Manipulation of Biographies of Living Persons case. If we are going to move it, why does it use the old naming convention?

1943: 5345:

Agree with Callanecc about DS, but think that there is almost never any reason to use the admin tools oneself when one is involved , and "clear" is not sufficient guidance. Rather, it's an open invitation to doing it and trying to defend it.

4747: 99:

used in citations with the blockquote parameter in the body of the article without being considered an abuse of fair use. The titles of the articles, which in newspapers can be longer than the quote, are not considered a violation of fair use.

8982: 7884: 5394: 3188: 7834: 7445:

First, the appeal is procedurally proper. The policy provides for it, and the right to appeal an AE outcome to ArbCom is an important safety valve, even though we respect the AE admins' judgment in most cases, and grant appeals only rarely.

5326: 3915:

about living people has no business anywhere on the encyclopedia. It cannot possibly aid the writing of the encyclopedia in any way, because it is categorically forbidden from use in any way. Anything which even stems from it is effectively

3909:

I think it's fairly apparent what the letter and spirit of the policy are intended to do — prevent the encyclopedia from being used as a weapon of character assassination or a tool of online trolls. To that end, policy demands that we treat

9097: 7392:

Awaiting further statements, and will review tomorrow. Note that we'll look at the related AE and AN threads in reviewing this, so that while anyone may comment here, it's not necessary to repeat every point that's already been made there.

5380: 9083:, and it is automatically logged to AN; 3) admins who have placed ECP as discretionary sanctions but not logged the actions in the DSLOG should be asked to do so; 4) admins who appear to have placed ECP outside of the scenarios allowed at 8958: 7741: 5813:

about 30 days into the 1 month topic ban and lists it as a "blatant violation." My edit was to restore long-standing consensus that mentioning the death of an aide is a BLP violation and I removed it because the Washington Post said it's

4866: 6630:. That article recounts "Krzanich's involvement in politics" and repeatedly details Krzanich's interaction with Trump and the policies of his administration. Editing this article therefore seems to be a fresh violation of the topic ban. 523:

approach to buttress each other's arguments, introduce irrelevant subjects or fallacies into discussions, and bully other editors. I feel there are user conduct and encyclopedia content issues here that ArbCom should investigate. Thanks.

7921: 7402: 5481: 5444: 5340: 5024: 4931: 3225: 1752:. Since these blocks were imposed I have been one of Alansohn's more popular targets of attack, so I have not considered blocking him further, but have made good faith efforts to discuss with him some of the problems that continue.) 6018:

ban should be reset. Two other administrators suggested making the ban broader since there might have been some confusion: I agreed that was wise given the previous sanction. Regardless, Scarborough was a bright line, and it was not an

2084:

also joined in that thread as well and asked Alansohn to explain a comment about policy violations, he responded not with anything relevant to the conduct issues, but rather with issues of policy and guideline interpretation at CFD.

6966:

and later by others. The decisive edit (agreed to by all people involved) was DHeyward's edit on Joe Scarborough. I am using the word "decisive" properly: without the Scarborough edit, it is very unlikely that DHeyward would have been

5311: 5292: 4726:

I understand why EvergreenFir brought this here, but the arbitrators have said what needs to be said, and nothing else useful is going to come out of this thread, whether it is closed promptly or a week from now. I suggest the former.

7635: 4899: 4835: 905:

fact that it applies to a wider area, or has more specific requirements (such as, in terms of logging) does not change the effect of the remedy. Persistently insisting it is new policy or against Knowledge norms does not make it so.

6957:

against DHeyward. It is 100% certain that based on the diffs provided by Andrew Davidson, DHeyward wouldn't have been sanctioned at all; indeed, Andrew Davidson was admonished in the closing statement for their "hyperbole". However,

5815: 4919: 8921: 6705:

has stated his first choice would be to remove the sanction. How can/should we move forward here so we can wrap this up? Are there still any arbs who would like to comment or should we work based on those who have commented so far?

4429:

whores. Others think this is clearly prohibited by policy. ArbCom in its majesty, it seems, believes that Knowledge will be served well by exhaustively and repeatedly discussing the matter on talk pages, on drama boards, and here.

1577: 283:

But so far as Mr. Schine is concerned, there has never been the slightest evidence that he was anything but a good-looking kid who was having a helluva good time in a helluva good cause. In any event, the rumors were sizzling away

8998: 8089:. The committee could also clarify whether all actions taken to enforce the BLP policy are under DS or whether the current practice of enforcing it as normal admin actions is fine. I'm sorry to bother you all with this, but since 2939: 2766: 2117:

be happy to spend some time at that point finding examples of this for the evidence pages as it would be a great opportunity to fix CfD. It's an area of the encyclopaedia which has been a problem for a long time, mainly due to

1965:

explanations and pleas, assuming his good faith throughout, but he has turned his sights on one contributor after another at CFD, and those who try to change or sanction his behavior in turn get subject to his attacks as well.

9026: 7917: 7909: 7766: 7323:

Long AE threads are bad enough. By the time there's been even one appeal, the purpose and intended functioning of Discretionary Sanctions has been thoroughly subverted. We didn't need DS to go through all the drama, including a

5884:

conclude that A) he is no longer a politician just as he now longer is a lawyer or college student and B) references to Klausutis have been removed for years for obvious BLP reasons. it's why my "violating" edit still stands. --

5477: 5469: 5365: 5020: 5012: 4830:

of the Committee, but I do think the AE admins got this one right, the link served no useful purpose, and BANEX was correctly (and even if you disagree, in good faith) invoked. I'm just not seeing anything for ArbCom to do here.

3221: 3213: 2751: 4804: 8897:

while logging of discretionary sanctions for this situation is a pretty tiny benefit for most instances (how often are these sanctions modified?), due to the rigid rules surrounding arbitration enforcement, it's still welcome.

7262:

thus: "A politician is a person active in party politics, or a person holding or seeking office in government." So ya'll work so hard to maintain the editorial integrity of an encyclopedia which is then disregarded in favor of

5131:, which states that "Administrators may enforce the removal of clear BLP violations with page protection or by blocking the violator(s), even if they have been editing the article themselves or are in some other way involved." 8987:

I would think the current practice would be if an editor does not expressly state ECP is being applied as an arbitration enforcement relating to discretionary sanctions, it would be assumed it is a regular application of ECP.

8560:

I'm sorry. I guess I thought we were on a site where the policies actually mattered. I guess us mere peons have to follow the rules to the letter and intent doesn't matter while admins get all sorts of leeway? Last I checked,

7051:

Now, I come to the punchline. There is a good-faith determination that DHeyward thought that he was removing a BLP violation and did not intend to violate his topic ban. His edit was completely proper (in fact, required under

7848: 6679:, then it seems to me the natural course of action is to either clarify the ban or remove it, not insist that it be enforced. TonyBallioni chose the latter course of action, and it is hard to see how that benefited anything. 3152: 4842:

While its application needs to be very strict and proactive in mainspace, which is where most people end up looking and where an allegation may sound like it's made in Knowledge's voice, its application on talk pages and on

7020:

is an integral part of BLP policy. Since no consensus for any text was found, edit-warring against consensus by the IP/sock/troll was illegitimate and a BLP violation. This is what happened initially: eventually the person

5408: 2350: 7516: 1951:. The behavior has not improved, and I feel that multiple requests to the committee by different users should be a signal that something further needs to be done. The question has not been rendered moot, as hoped for. 7158:

political activist/who prominently interacted with presidential candidates and city political leaders, fall within reasonable construction of these ordinary English phrases. (As an aside, Erica Gardner was created on the

1976:, then a frequent closer of CFD discussions). Alansohn was civil and even complimentary towards me at the time (though persisted in attacks on others). I even tried to address others' incivility towards him as well. 6720: 2154:

Good Olfactory has asserted to me, and may well be right, that he was not friends with those involved at the time he made the block on Alansohn, which was April 2008. My project's first run-in with the CfD group was

7913: 7905: 5473: 5465: 5016: 5008: 3217: 3209: 2990: 6234:

thought to asks demonstrates that he could use some more time off from this area to hopefully cool down and get used to editing in less contentious areas where there is less feuding between people from different POVs.

1894:"Good Olfactory's admission above that he has used his admin tools to further his position in a dispute to protect friends - something which he should most definitely have taken to AN/I instead - is also an issue." 71:

The quote function is a part of the all the citation templates. Quoting the actual text in the article aids the researcher and the fact checker, thats why the snippet view of Google is so popular, you can see the text

6471:" I declined to take action in an enforcement request of 9 December 2017 against DHeyward because, for the reasons cited by DHeyward, I did not think that DHeyward's actions as reported there violated their topic ban" 6032:

was substantially different than previous versions removed on BLP grounds to the point where classifying them as the same topic is even a stretch: it was about Trump advancing a conspiracy theory and was cited to the

7380: 987: 5180: 3009:

Personally I think that's a good idea, but I'll wait for other committee members to comment as well. Whichever title is chosen the other should be a redirect to it as they are both logical and useful search terms.

219: 3974: 3959: 2434:

In the time since then, though he apparently has done good work in vandal patrol, and elsewhere, he simply hasn't followed the restriction. And though he hasn't been blocked (or even warned) for "every" violation,

868: 130:

6) Editors are skeptical of new information added to articles, so the best effort should be made to persuade them that the information is legitimate, and make that vetting process as easy as possible. For example:

8768: 4631: 2567: 1595:

A CFD restriction would address the first type of problematic behavior that Good Olfactory has pointed out; but if that's all that ArbCom is willing to do, the other two types would still remain a problem...?

3904: 571:

archives. That particular method links us to a page at the Times website that purchase is required to access the rest of the article, which may or may not contain the material actually being cited. I took it to

566:

preservation at all, and there were archive options available to be used when sources were in danger of being lost online. What I have seen is often copy and pasting of the opening paragraphs from, for example,

6755: 5260: 4132:

article space under WP:BLP. As I understand it, non-BLP-compliant sources may not be used to source BLP material. As it's been applied by a number of admins, non-BLP-compliant sources may not be used to source

2189:

by Good Olfactory). There may be argument for a reprimand with relation to abuse of admin tools here - it was a clear conflict of interest situation in the terms I outlined in my first post in this comment.

622: 4526:

what is wanted here by those who have so successfully exploited -- and continue to use -- Knowledge's talk pages to punish their enemies and all who stand in their way -- now including, as mentioned above,

1580:, which should also paint a clear picture of any further voluntary dispute resolution on the matter. I request ArbCom to put an end to the unfortunate effects of Alansohn's disruption and gross misconduct. 121:

Schine and Cohn were rumored to have a sexual relationship, although there has never been any proof of this. More recently, some historians have concluded it was a friendship and that Schine was heterosexual.

8917:

Other editors are free to make relevant comments on this request as necessary. Comments here should opine whether and how the Committee should clarify or amend the decision or provide additional information.

7352:

5176:

1268: 4882: 1166: 715: 3988:

purposes is, at best, grossly negligent. I note that Retartist says they did it in good faith and I have no reason to doubt their word, but that's not the sort of conduct we need in difficult topic areas.

3982: 2639: 2032:

Often Alansohn's most inflammatory comments do not expressly identify individuals, but are still understood as attacks on others with whom he disagrees. At a minimum, the heated rhetoric is disruptive.

9119: 1927: 677: 4800:

Other editors are free to make relevant comments on this request as necessary. Comments here should address why or why not the Committee should accept the case request or provide additional information.

4126: 7681:

So, who is and isn't an American politician? Does 'politician' include everyone who has ever held elective office at any level, no matter how long ago or for how long? Does it include everyone who ever

7122: 7060:

and "consensus required" also points to this outcome. Nobody claims that DHeyward's edits were disruptive or harmed the encyclopedia. TonyBallioni's ban was poorly worded and confusing to even himself.

6796: 6774: 6573: 6454: 5165: 3936: 841: 8054: 7893: 5453: 4996: 4987: 3197: 2994: 2794: 2721: 1177:

were noted then this special enforcement remedy wouldn't have existed. Similar remedies were applied to other cases but policies are created following a process --not specific arbitration remedies. --

8177: 8118: 6220: 2913: 2194: 2164: 2145: 2089:

Anyone who cannot participate in a forum without turning discussions personal, and who cannot respond to complaints about their own conduct without escalating the hostility, does not belong there.

1557:

to remove the "for one year" part, and in addition to that, impose a ban, probation, or any other remedy that will put an end to the problems, and subsequently act to ensure that they do not recur.

888: 6750: 4369: 1309: 7595: 7571: 7431: 7417: 6900: 6877: 4647:

accusing someone of criminal behavior of the most vile kind and calling on the Obama administration to arrest and prosecute them has not been interpreted as a BLP violations against living persons.

4540: 4508: 4076: 4046: 3072: 2779: 2279: 1666: 1605: 6729:

This does seem to me to be of-a-piece with the Tony1 wrongful block situation, and the AE report by SarahSV above. Some sanctions-related bolt has come loose and needs to be re-tightened, firmly.

3674: 2335: 1174: 6475:

So apparently Sandstein DOES NOT in fact "ignore the views of other uninvolved admins". Gee, perhaps the consensus in the MONGO case was actually leaning towards the way that Sandstein closed it?

6448: 6422: 6008: 4716: 3138: 2838: 2325: 1026:

Committee. Please note, the Arbitration Committee were given full time to make the case for why they should have this power, but don't appear to have made it to the satisfaction of the community.

8823: 8731: 8246: 3112: 3029: 2884: 2808: 2582: 2436: 657: 7171: 7137: 6802: 6641: 6568: 6528: 6509: 6491: 4151: 3058: 3044: 2868: 2852: 2822: 6559:

ruling the broader community at WP:AN. I can see over ruling one or the other, but both? You will also be incentivizing forum shopping, topic ban envelope pushing and other disruptive behavior.

4678: 2255: 1219: 593: 537: 404: 8859: 8725: 8153:

logged, telling admins this, and when it is pointed out to you that you are wrong, you responding that you aren't. You have said on two occasions that ArbCom requires ECP of BLPs to be logged.

7658: 7214: 7079: 6428: 6361: 6002: 5674: 2633: 2621: 2597: 2551: 1877: 496:

talk archives for previous discussions, and spent an entire afternoon on it. In the end, I concluded that it is/was a copyright violation of four different websites, including one site with a

8865: 4721: 4156: 4025: 3019: 8102: 7803: 7787: 7318: 6286: 6121:: the last day of your current topic ban is 4 February 2018. You may begin editing in the topic area again on 5 February 2018 unless ArbCom lifts the sanction earlier. I hope that is clear. 5143: 4620: 4451: 3919:. Suggesting, as one editor did, that an inflammatory, anonymous screed full of unsupported attacks, disproven allegations and outright lies about living people (the so-called "dossier") is 2315: 1207: 1194: 998: 981: 8817: 8665: 6863:

An addendum: if ArbCom does end up considering the merits of the ban in this venue, I'll be happy to provide my views on how the sanction was bad. In particular, some things I'll say about

6104:

I, as well as other admins, did consider these edits presented by Andrew as part of a pattern of editing around the edge, but the Scarborough edit was the bright line violation in my mind.

4087: 2900: 2291: 1305: 8316:

The point is that ECP is indeed applied for DS reasons. If you're saying the third paragraph no longer applies and admins can just do whatever they want, why bother having a policy at all?

7074: 6990:

request; please also see TonyBallioni's responses to me. Here, I give a capsule summary of the important points. The text in question was inserted by a throwaway sock/troll account called

6646: 6280: 6261: 6244: 6191: 6166: 6152: 6130: 6113: 6091: 4789: 3898: 2505: 171:

verify the facts. I only blame myself for the deletions for not providing more complete information, all new information should be treated with skepticism, and I applaud skeptical editors.

8804: 7246:

If I was better person, I wouldn't find myself ironically amused (and somewhat saddened) by the way wiki-volunteers disregard Knowledge mainspace in the Knowledge space: According to us,

4546: 2969: 2486:

From what I can tell, the biggest problem is the presumption of bad faith of other editors (often magnified with incivility). A look at his statement below even shows indications of this.

8745: 8281: 6857: 6820: 4484: 2979: 2130: 2080:

As that thread shows, his response was to call the incidents "trivial," again accuse me and Good Ol'factory of trolling, and of trying to "manufacture knowingly false disputes." When

1695: 1652: 1589: 8944: 8885: 8690: 6313:, but focus on any important procedural errors with the sanction or the appeal below. To the extent I understand this somewhat confusing appeal, such errors are not being alleged here. 5831:

debate regarding whether my edits advanced the purpose of Knowledge. No one is aware of the history of Scarborough and the eath of his aide 20 years ago, just that Trump smeared him.

4741: 1429: 1149: 458: 8811: 8796: 8636: 8562: 7233: 7117: 6437: 6387: 5915: 4736: 2499: 1776: 1114: 918: 164:. Again, if the references were clearer, and the quote function used to it's fullest, perhaps the skeptical editor would be persuaded that the information comes from a reliable source. 8657: 8596: 8575: 8548: 8183: 6047:. A reasonable editor could have made an argument for it's inclusion on the talk page, and have argued that there were a change in circumstances. That means that it is not covered by 5089: 4285:

is being used to suppress the normal working of the Knowledge Project; preventing discussion of sources, and improvement of the encyclopedia through consensus. Editors are leveraging

4179: 2042: 1896:

I want to be clear that I made no such admission, and that is Orderinchaos interpreted my comment in this way, he is mistaken. At the time the blocks were performed, I hardly knew

9058: 8880: 8686: 7339: 7208: 6330: 6325: 5933: 5893: 5875: 5851: 4174: 8773: 7986: 5595: 3775: 1301: 1293: 8912: 8832: 8706: 6715: 6688: 6667: 4579: 4203: 4121: 3727: 2528: 1080: 1059: 1038: 1022: 780: 550:

I am commenting mostly to reinforce that in my view, this is not an issue of attempts at ownership of an article, or articles. The practice under discussion here is pervasive with

7347: 3387: 194: 8779:

go on to disrupt articles that were not protected at all, so the formality of semiprotecting those articles first just so they could be immediately ECP'd seemed redundant to me.

7176: 4597: 3093: 2415: 2102: 963: 8614:. An analogy: police officer arrests someone but puts the cuffs on too tight. I'm asking for the cops to make sure the cuffs are the proper tightness, not invalidate the arrest. 7856: 7036:

for an example. It is well-known that such things in political areas are litigated over and over, often for years. This particular edit has been fought over since at least 2004.

5416: 4960: 4302:) is not to protect living persons (although this is a pleasing side effect); but to protect Knowledge from slandering or libeling living persons (and the consequences thereof)" 4112:

The sole exception is "outing" and the simple rule of thumb is if the Oversight committee is not going to remove it, it's not a policy violation and it should be left alone. --

3696: 3160: 8907: 4795: 4759: 1791:

he accuses the person who is bringing the behavioural problems to his attention of "trolling" or of manufacturing a problem in an attempt to get him blocked or disciplined;

1173:. Biographies of living people are subject to a strict policy. Special enforcements are part of Knowledge's general sanctions. If we had had a "footnoted quotes" case where no 6948:

While the edits here are related to politics, the article as a whole is not related to any specific politician. If that was not the intention, the topic ban was poorly worded.

5946:

I also see a history of trying to get around sanctions in this area, both with the original TBAN AE thread, the actions that led to this AE, and the various actions afterwards

5753: 5649: 3003: 50: 8258: 7204:, with all due respect, AE is the about the only thing preventing this place from blowing up. Reform would be beneficial, but eliminating it would be a huge step backwards.- 6356: 4364: 2674: 7029:

the passage into something closer to neutrality, which seemed to satisfy the IP/troll/sock. Again, the crucial point is that there was no consensus for this phrasing either.

2985: 2178: 1916:

the block was performed to retroactively assume that such a relationship pre-existed and thereby created a conflict of interest. It's cute, but it's a misrepresentation.

1552: 1159: 8783: 8128:

While the ECP of Joe Girardi was short-lived, you still need to log your actions here per the ArbCom ruling on BLPs. Please do so. Buffs (talk) 21:29, 24 October 2019 (UTC)

7006:, for example). Trump had tweeted about this matter, which WaPo (among others) deemed as a conspiracy theory without any basis in fact. Please see the talk page discussion 5864:

The word "article" usually refers only to mainspace pages. If any other related pages (such as the page's talk page) are to be covered it will usually be stated explicitly.

5211:

This isn't a clerk action, but can I ask you to clarify your request? Are you asking the Committee to clarify whether: (a) Admins may act while involved in accordance with

1949: 36: 7749:

can be dealt with as they occur, preferably without using AE. I also will not oppose any other proposal for removing it, even if it adds a restriction I think unnecessary.

7422:

I was planning to post on this tonight, but my comments on the previous ARCA request took me much longer than I'd anticipated, so it'll have to be tomorrow. My apologies.

7095:" is any different to "post-1932 American politics," since anything political is necessarily "related" to politicians. I certainly can't see how it could be construed as 2465: 2122:

could be forgiven for thinking this amendment motion, and the stages which led to it, are an orchestrated campaign by the members of that group to silence an opponent.

1483: 1297: 1289: 818:, and have the arbcom's explicit approval of it being treated like any other policy, e.g. it may be edited, adapted, or, (in extreme cases), voted down by the community? 7195: 1071:

Frankly, Jimbo's opinion of how the Knowledge policies should work are worth exactly as much as the next guy's. Knowledge is not a top-down authoritarian organisation. --

7530:

observed—and I observe here—that the best way to avoid having to discern the parameters of a topic-ban from the inside is to avoid being topic-banned in the first place.

7220:

something, then the admin has to go on record that they believe they did it and that they believe it's bad. And "disruption" is a result, not an action. Say what they

4750:. I think everyone should be advised to wait for consensus before redacting links - excepting where the content is illegal or in some way liable to cause imminent harm. 1018: 6397:

As for the violation itself, I'm a bit flummoxed to see so many admins and others argue that Scarborough is not a politician. Someone who has been a member of Congress

6292: 2647: 138:. If the references were clearer, it would be easier for the skeptical editor to see which information was correct. The dates that were deleted by the skeptic were the 5794:

Nobody changes or clarifies the TBAN (or even whether it is an ABAN which I raised Dec 9) so a reasonable person would conclude that the actions were not a violation.

3712: 2557: 6620:

DHeyward is banned for one month from all edits about, and all pages related to post-1932 politics of the United States and closely related people, broadly construed.

2287:

there is enough substantive matter to justify it, then a new case request might be appropriate. Otherwise, a dead case resuscitation doesn't seem appropriate. —

2072:

and by calling me a troll again when I posted a question about a comment of his at yet another CFD (in which he had been uncivil yet again towards BrownHairedGirl.

5663: 8685:, and the action should be logged. The second case is a normal admin action which can be changed by another admin, and there is no log but pages are automatically 7108:

subsequent ban should perhaps give us pause for thought) and then whether that reliance is sufficient to overturn the sanction, on which I don't have an opinion.

6991: 6061: 5801: 5784: 5691: 4712: 4420:

This flagrant effort to pervert Knowledge's disciplinary mechanism is not likely to arouse your notice or evoke your concern. The standard discussed below -- that

1285: 8090: 5842:

for an editor to keep up with these shifting sands? If an admin realizes there is a clarity issue, shouldn't they have a duty to clarify it before sanctioning? --

4082: 1787:

When concerns about his behavior are brought to his attention, I have found he uses one of three approaches to avoid taking responsibility for his misbehavior:

1567: 7498: 6464:"What can be done about this situation at AE, which seems to have been going on forever, that Sandstein can simply ignore the views of other uninvolved admins? " 6295:

against DHeyward because, for the reasons cited by DHeyward, I did not think that DHeyward's actions as reported there violated their topic ban. As concerns the

6267: 5704:" He hadn't edited the article or otherwise engaged in the deletion discussion when filed as a party. The first allegation of creation was obviously in error. 5668: 5157:

Sanction allowed? Is a topic ban allowed? I believe the first but not the latter two are correct, but I'd like the Committee to clarify where the line is drawn.

2077:

I responded on his talk page, in which I complimented him as an editor, and pointed out exactly what I had a problem with and what I hoped for going forward.

8535:

If it isn't, a standard rationale of 'persistent sockpuppetry' or 'persistent vandalism' or 'violations of the BLP policy' (and so forth) is sufficient for me.

7241: 2542:) as a crutch or to prolong a process that was already arbitrarily long and been remarkably disruptive. Join me in counting down the days to freedom. Move on. 1775:

He repeatedly mischaracterizes arguments he disagrees with and claims that users who choose to propose deletion for categories are engaging in "disruption" (

1085: 8633:

All sanctions and page restrictions must be logged by the administrator who applied the sanction or page restriction at Knowledge:Arbitration enforcement log.

1755:

Since the editing restrictions were lifted, I would categorize the general problems with Alansohn's edits into the following types of problematic behavior:

5107: 1249: 1122: 6303:

against the ban imposed by TonyBallioni, finding that there was not the required clear and substantial consensus of uninvolved editors to overturn the ban.

6073: 6070: 1068:

create the Arbitration Committee from whole cloth and by fiat. The Arbitration Policy did have to be agreed with by the community as with any other policy.

227: 175:

Here a skeptical editor removes the names of two people involved in the Army-McCarthy Hearings that were mentioned in their obituaries in the New York Times

8066:

to state that admins must either declare protection is for disruptive editing, or apply it under DS. He has taken to requesting logging of ECPs on BLPs at

896: 440: 4698: 4417:: GamerGate has handed every little PR shop a textbook on how to pervert Knowledge. ArbCom has written the textbook for destroying Knowledge from within. 4184:

I am working on a statement, which not only addresses all of the principle & policy aspects, but is also below the 500 word limit; in the meantime...

2263:: Could Alansohn be reminded that this is underway? I'm seeing lots of edits from them but no input here and I'd like to hear their side of the story. 8093:

contributions going back 2 weeks amount to a super-literal policing of the use of ECP, I'd prefer the committee clarify this before it gets any further.

7624:

arb comments at the Pseudoscience appeal above. Ignoring the specifics of this appeal, I am completely unconvinced by the arguments of forum-shopping. ~

3715:

for posting the link that was closed by HJ Mitchell with a topic ban. As a result of this enforcement request, the link and other links were REVDELed by

2717: 2421: 2064: 1991: 1988: 1640: 1635: 1277: 1170: 1006: 713: 7328:. The initial sanction was well-considered and valid both on process and on substance. And DHeyward has a nasty well-documented history of disruption. 7039:

This is not really important, but Volunteer Marek himself was the target of reverts by a sock/troll of some smears he claimed to be a BLP violation, on

4403:

life -- is asking User:Jimbo to stiffen your resolve. All are eager to see that you continue steadily on your course and remain firm in your intention.

4379:

which is and has long been their stated goal and plan. There, @theWTFMagazine links to an 8chan thread on that distinguished contributor which begins:

2073: 2006: 2003: 969:

Hm, well I think Tony was de-clerked, so he probably shouldn't be considered a binding expression of arbcom intent. But since I really never worked at

636: 508:

as a blatant copyright violation. I had no objections to recreation of a new article in original prose, and I probably should have made that clear.

8488: 3758:

Contentious material about living persons that is unsourced or poorly sourced and not related to making content choices should be removed, deleted, or

2070: 2067: 1050:

I would suggest that if you are still going to ignore the community consensus on what ArbCom may and may not do, you should consider your positions. --

923: 8460: 8422: 8396: 7672:

recently deceased persons, or even an AP2 sanction, DHeyward's edits would have been violations. That was not the sanction, though – the sanction was

6534: 325:

Tall, rich, and suave, the Harvard-educated (and heterosexual) Schine contrasted starkly with the short, physically undistinguished, and caustic Cohn.

8458: 8412: 8408: 8406: 6598:. I was therefore concerned that the article should not be improperly tagged while it was getting such exposure. I have been previously told by an 6466:. Note she does not offer any diffs or any other evidence for this claim aside from the fact that she doesn't like how the MONGO report was closed. 744: 627: 8414: 8394: 2061: 2058: 1977: 580:. The overall consensus at that time was that this practice violated the intent of the use of the quote function, as was summarized on that page by 8482: 8420: 8392: 8211:

and filed it under the logs as he should do so. In both instances, I felt such actions were appropriate and it was handled as it should have been.

7460:. On December 9, addressing another complaint against DHeyward, one of our most experienced AE administrators observed that the specific topic-ban 3309: 2562: 2048: 2045: 2033: 542: 464: 8736:

Like the others who have posted, I suggest that Buffs drop this matter. The extra "paperwork" he is seeking is a solution in search of a problem.

8428: 8424: 7486:. (Some other edits were cited, but those were the main focus.) The outcome was a one-month extension of a broader "American politics" topic ban. 6140: 4092:

The enforcement request for BANEX is a red herring. The issue is whether links, without any statements about the link content (i.e. "Please look

2186: 274: 8418: 8416: 8384: 6096:

I will also note that Andrew Davidson was not admonished for a baseless complaint, he was warned not to use hyperbole because of statements like

5135:

specific incident I'm thinking of, but I could see it becoming an issue in the future and would like clarification on how that might be handled.

1740: 1737: 8426: 8410: 8386: 8240:

Third, it seems quite obvious that the requirements for DS and ArbCom decisions are not being properly logged. You need to look no further than

6936:, namely the requirement that the person who inserts the text has to prove consensus, not the person who removes it. The wording of the TBAN is 2039: 1994: 1923:

And yes, the blocks were in 2009, not 2008. My mistaken dating/typo on your talk page in that regard doesn't change anything I've said above.

1743: 8632: 8474: 8444: 8442: 8440: 8438: 8436: 8434: 8432: 8430: 8404: 8402: 8400: 8398: 8390: 8388: 7647:

My comment was more in reply to Fyddlestix. I'm recused on this specific appeal, so I'll let other arbs comment on how they plan to proceed. ~

7468:

were not prohibited. DHeyward says he relied on this construction in interpreting the topic-ban for the rest of the month, and I believe that.

3630: 3618: 2240: 2009: 2455:

The third is (if the answer to my first question is "no"), does the committee feel that the 1 year restriction should be lifted at this time?

1871: 1804: 1801: 8899: 4953: 4872:

NorthBySouthBaranof, that's exactly the kind of battleground attitude I was referring to by "your approach still leaves much to be desired".

2492:

So no, this really isn't, and shouldn't be considered, "moot". It's a constant, ongoing problem, and one that I believe needs to be resolved.

2445:

The first is whether the 1 year restriction was to restart at the occurrence of each block (something I've seen done in other arbcom cases).

1212:

I agree with Flo that no action is needed, and with Mackensen in his comments re. the applicability of transitive devolution and delegation.

607: 8287: 2246:

I am seeing some problems here. I would be willing to see a motion which partially or fully restricts in the areas of CFD and CFD at DRV.

5817:. I had linked that article to the Scarborough talk page in November, before the TBAN, to head off the aspersions that surely would follow 5680: 3507: 1979:

Though in my view, Alansohn generally bore more responsibility for initiating the hostile exchanges and escalating and continuing them by

398: 5171: 2036: 1107:

All this is a way of saying that arguments over this remedy should turn on whether it's a good idea, not whether Arbcom can do it or not.

5818: 2843:

Sadly, yes. Baroque Arbcom case names are part of the colour and novelty of Knowledge. But I agree this new name has greater clarity. --

4313: 1870:

Normally I wouldn't have minded doing this, but I think I'd better not in light of his recent reaction to my posting on his talk page:

1573:

Good Ol'factory has in good faith, followed the dispute resolution process - opening a WQA which summarises one of the main incidents

7674:

topic-banned for one month from articles about living and recently deceased American politicians, and related topics, broadly construed

7458:

topic-banned for one month from articles about living and recently deceased American politicians, and related topics, broadly construed

6606:

iirc) that such tags can often cause offense when they suggest that the subject is not notable. The subject was covered by the policy

6208: 6204: 6058: 6052: 5835: 1750: 1029:

While the below Arbitration Committee members may say otherwise, this 'general sanction' is not in effect, and will not be enforced. --

738: 500:. Since there were no clean revisions (and the paragraphs/quotes in the cited references were longer than the article itself), I made 6067: 6064: 4640:

violations, can you at least explain why it is allowed to be one-sidedly used as some sort of hammer to punish ideological opponents?

152:. More easy to read references, with the quoted text may persuade the editor that the information is indeed correct and not vandalism. 8478: 3303: 3260: 687:

Please do not edit this text, regardless of whether the statement is your own or not. Further discussion is welcome on other mediums.

59:

Please do not edit this text, regardless of whether the statement is your own or not. Further discussion is welcome on other mediums.

8604:

I would also want the parties involved to understand that actions needing to be logged are not made ineffective by a failure to log.

8464: 8060: 7284:“When I use a word,” Humpty Dumpty said in rather a scornful tone, “it means just what I choose it to mean — neither more nor less.” 5969: 473: 8492: 8472: 8340: 6591: 6076: 5921: 3711:

because the link contained very problematic content, the nature of which can be seen in the enforcement request. There was also an

2233:

For the record, in line with Roger Davies request below, Alansohn was reminded at 03:35, 16 February 2010, by one of the clerks.

1700: 1546: 1350: 618: 436: 215: 8468: 8446: 6098:

tags Erica Garner, suggesting that her life did not matter, which is a derogatory implication given her role in Black Lives Matter

6045: 6042: 6029: 5821: 5811: 4748:

Knowledge:Biographies_of_living_persons/Noticeboard/Archive213#Contentious_BLP_content_in_sources_that_are_cited_for_other_reasons

2017:

Another admin reviewed and denied Alansohn's unblock request, finding that even that request itself contained further incivility.

8466: 6954: 6336: 4232:

of removal, reversion, and revdeletion of links to sources containing contentious material from article talk pages, citing WP:BLP

116:

Here is a good example of using quotes in citations and how they clear up what is in the article, and how it aids the researcher:

17: 8352: 8336: 6779:

I think reforming the system of discretionary sanctions (as suggested by DGG) could be reasonable. Two suggestions are obvious:

4776:

it. Otherwise the content of a link has absolutely no bearing whatsoever on Knowledge outside those portions that are discussed

3593: 577: 8204: 7160: 6497: 6341: 6300: 5977:. Someone even commented that my revert description that undid every edit I made wasn't clear enough. I'll get right on that. 4161:

All i want to say is that i posted the links in good faith and was stupid in posting so many links without checking each one --

4137: 3774:, though minors are discouraged from disclosing identifying personal information on their userpages; for more information, see 3555: 2141:

aggressors should be targetted for action here, not someone they provoked into a predictable response given his past history.

66: 8470: 6069:

and at AN, where he bludgeoned the conversation by pasting the same statement to multiple editors who endorsed this sanction:

5838:

ArbCom. The actual filer of the Jan 4 complaint that lengthened my TBAN was admonished because his complaint was baseless.

2588:

an appropriate restriction. Reiterating NYB, if Alansohn adheres to a decent level of civility, this will be entirely moot. --

1568:"Alansohn has repeatedly engaged in unseemly behavior, including personal attacks, incivility, and assumptions of bad faith" 8140: 5516: 3501: 3459: 2378: 1849: 1705: 1574: 1561: 1507: 1064:

I note that the view of Jimbo as 'God King Emperor' of the project is highly disputed these days. I also note that Jimbo did

7091:

As I've said privately to TonyBallioni, I can't see how the topic scope "living and recently deceased American politicians,

6500:, so it's not clear what the purpose of this is, except as a thinly disguised "appeal of an appeal of an appeal a sanction". 3613: 2024: 1686:

conduct during WQA, and the evidence I had to submit has already been submitted in the links in my initial statement here.

788:

This page is presumably meant to stand for all time. As it is effectively new policy, I would request that it be declared a

8158:

Therefore, it you are citing WP:BLP as your rationale for WP:ECP, it seems to me that you're applying it due to DS, not DE.

7870: