Knowledge:Arbitration/Requests/Clarification and Amendment/Archive 45

6949:

sorry. However, Martintg does not mention any actions he took that he regrets, any articles that he and his colleagues edited and now wish to repair or any editor he offended he now wishes to apologize to. This group shared a minority political point of view and damaged the neutrality of numerous articles and continued to collaborate off-wiki even after the case was presented against them. They do not accept that Knowledge articles should be neutral and tied up the time of numerous editors. While it may be that they will no longer coordinate their efforts, their approach as individuals is damaging to neutrality. It is irritating that as I and other editors were arguing with Martintg and his colleagues and they were presenting arguments against us that off-wiki there were agreeing that our arguments made sense and trying to develop a new approach. Surely editors like this drive away most of the editors we want to attract, people who have the ability to write articles and those who remain are tied up in silly disputes. Dispute resolution, reporting editors for 3RR, writing Wikiquette and ANI reports are extemely time-consuming and allowing editors like Martintg will only discourage capable editors who are discouraged by the processes to counter editors like Martintg.

1616:(based on his comments) and is applying that standard to non-science articles, such as an article on a book that happens to be critical of the science. The key factor should be if the book itself is notable, and its reception, not whether the book was reviewed by scientists or peer-reviewed journals before it can be considered notable or to meet the standards for a Good Article designation. I did not view that as a content issue, but a procedural or policy issue. On Amendment 2, no admin has taken any action, although it is a clear violation of policy on referencing, but if this should not be here, my apologies. Where would I take that issue, if this is not the right venue? I view Amendments 3 & 4 as being closely related, should I combine those into one amendment? This is the first issue that I have brought here, so if I have made an error on something, it was not intentional, nor intended to be disrespectful of your time and attention. If I can fix any of the issues to be framed in a different manner to be in compliance with your guidelines, I will be happy to do so. Regards, 2390:

tweak the code to make the bot properly deal with whatever novel situations arose. Much of the to-do with Lightmouse’s involvement with date-related bot activities arose from his moving forward when he believed a clear community consensus existed on date linking. In the end, the consensus he believed existed at that time proved to be well founded and is the current consensus today—and our guidelines reflect that consensus. Since the date-related conflict was rather unique (a particularly contentious issue with impassioned editors on both sides), there is no reason to think that Lightmouse can’t be trusted to go back to doing what he did before he got swept up in the date-jihad maelstrom: make and run sophisticated bots that improve Knowledge far more consistently and faster than humans can.

2576:. In my opinion, this strikes to the heart of the conflicts that arise between those who would like to see the guidelines presented in the Manual of Style implemented and enforced across the entirety of Knowledge with the use of bots, and those who think that such an approach will create more drama and conflict than it is worth (as individual editors and groups of editors object to bots sweeping through and making changes that at times seem arcane to those who have not followed the discussions at the Manual of Style). The fundamental divide is between those who want to see order and consistency brought to pages across the whole of Knowledge, and those who think an organic process is better and less disruptive. I would have thought a wider debate on precisely when automation on 4786:

made mistakes, and very few people can be fully calm after sufficient insults--and, in particular, while being set upon by more than a single harasser. As applies here: some of the IRC articles were rather weak; the subject is not really among the best-controlled tenth of WPedians; the almost simultaneous actions from three people would be enough to infuriate almost anyone. As I see it, concerted harassment should be treated as a major aggravating factor or even as meatpuppettry, whether done by coordination or just from exploiting the opportunity. And one sure sign of harassment is when it takes more than one route, or when it continues after the success of the initial round; I see the MfDs in exactly these lights: carrying things to that extent is persecution.

2854:). Until that happens, things here are on hold. As far as I can tell, the bot request isn't making very fast progress. I would also ask arbitrators to read through the bot request (both now, while it is in progress, and once it is closed) before proposing or voting on any motions. The underlying tension at the request seems to be between a desire on the one hand for simple bot requests that are easy to check, run trials on, and approve, and on the other hand a desire to have a more open-ended, flexible request approved, that allows the bot operator to reprogram the script without constantly going back to BAG. The problem being that open-ended requests are harder to assess and approve, which is (in my view) why the request is still open and struggling to make progress. 3264:

script-assisted work related to units of measure that I used to do (and many editors still do, even with variants of code I may have written myself) as a non-bot. I may even use such non-bot work to support the case for a bot. The Kirill proposed amendment is welcome but it not only puts BAG in charge of a non-bot account (which is a variation from the normal BAG scope), but it also prevents the Lightmouse account from applying non-bot semi-automation to units of measure until the BAG debate ends with a 'yes' at some unspecified time in the future, and worse for me, it may end with a 'no'. Please can you consider the text I proposed which would not connect BAG to the non-bot activities. I hope you don't mind.

4985:

it's time that the arbitration committee, or the community at large, address some of the clearly unaddressed problems here, that we are being deflected away from by motions such as this one, more directly. If Tothwolf were subtracted from this entirely, there would still be concerns to answer on the parts of the other accounts. Tothwolf hasn't behaved well, and clearly could have garnered more sympathy by writing and contributing, rather than arguing. But Tothwolf being the focus, or the entirety of the cause, clearly isn't correct. As observed, Miami33139's actions are serving quite ironically here to show that the spotlight should be shining on other accounts a bit more than it has done.

1801:

view, and an attempt to fix exactly where those boundaries are, especially with respect to a specific area of science, is beyond both our mandate and our competence. Amendment 2 is nonsense; if a hypothetical editor is currently not adhering to that rule, which is plainly stated in policy, what reason is there to believe that that editor would suddenly start adhering to it once it was plainly re-stated by ArbCom? I do not understand what action Amendment 3 is proposing, unless it is merely a justification for Amendment 4. I will have to investigate Amendment 4 further before commenting, with that investigation ideally to include reading a statement from ScienceApologist on the matter.

5078:(who filed this request). I'm particularly unimpressed by the "Waambulance" and "whine one one" taunts. I would like to see statements from Tothwolf and JBSupreme and theserialcomma, and also (if he is prepared to make a statement) Uncle G, who left a note about this on an arbitration page somewhere recently saying that things were boiling over in this area again. I'm also concerned about comments that the civility restriction passed on JBSupreme is not having any effect. Possible ways to proceed here would be a wide-ranging non-interaction restriction between Tothwolf and JBSupreme, theserialcomma and Miami33139, or even reopening the case in light of this continuing behaviour. 2927:. I don't think it is ever too late to bring up points such as that made by Gatoclass (and later withdrawn). I would actually like to see links to the discussions Gatoclass refers to, and those links should at a minimum be supplied to any BAG discussion, and arguably any BAG approval could be invalidated unless notification was given at the venues where this has been discussed before. Of course, Gatoclass may have missed other discussions, so what is really needed is a full and honest listing and assessment of past and present discussions about this subject. Hopefully that can happen and ArbCom will consider how many people took part in or were notified of the BAG discussions. 2483:

Lightmouse submits a new (date/unit) BRFA; 2 or 3) The BRFA is endorsed by Arbcom - they amend prior remedies to allow its passage; 3 or 2) The BRFA passes (or fails) the standard process, which will include a short trial. 4) Instead of being free to continue as he pleases, Lightmouse will remain under trial conditions for three months. Put simply, he will be on best behaviour and expected to be a top operator in responding to comments and complaints; he will be expected to, and I will, check a sample of his own edits at regular intervals; admins and others will be more heavy-handed in stopping the bot from continuing. That is my recommendation at least. -

8424:

could be considered as being in scope. I would request that for the editors subject to the topic ban, that clear (and "single voice of ArbCom") guidance be given regarding specific articles in and out of scope of the topic ban at the case mentioned. Editors should not find themselves in the position of interpreting a topic ban, interpreting ArbCom discussions as to scope of ban, or be potentially subjected to, for example (unfortunately), harassing policing by their editorial opposition where there is a difference of opinion on scope of ban. A prompt and clear response will go a long way toward calming the subject matter area.

5092:@Miami33139 I'm saying I'm unimpressed with your conduct at the ANI thread and the comments you left. You seem to be under a mistaken impression about the conclusions of the arbitration case. Changes in conduct was expected from all parties, and returning to the conduct that led to the arbitration case is likely to see a re-imposition of sanctions and/or warnings. Currently I'm waiting for my colleagues to comment on this amendment request, but in the meantime it would be good to see some more statements here. Tothwolf has mentioned Uncle G above, so I will ask him if he is able to make a statement here. 2405:

with quirky inconsistencies due to the inherent collaborative nature that lend themselves well to standardisation and automated maintenance. I missed his presence from the project, and have been motivated thus to take up scripting myself - of course, I cannot fill the huge gap left by Lightmouse. His remorse appears sincere and heartfelt; his gradual return to automation, under the parameters laid out appears to be well thought out, and seems to me to correctly balance the safeguards which the project may reasonably expect with the right of editors to engage in automation. I heartily support this appeal.

7205:@Jehochman: Please desist from further discussion of private correspondence. Any discussion of you emanated from your acting as a proxy filing an arbitration request as a direct result of Offliner's lobbying you. I regret needing to remind you that you were the origin and only reason for your own mention. This is the second instance of your discussing private correspondence and professing to be a victim of EEML editors. At least I now know (your feeling you were victimized when you, in fact, victimized Baltic and EE editors) where your outrageous accusation came from that I 6981:. Since our paths first crossed sometime in early 2007 the underlying dispute has taken the form of a global ideological war over the legacy of the 20th century. I believe in some ways the early editing disputes and the formulation of opposing positions on Knowledge talk pages have later influenced the positions some of the main players in this battle have taken. I may be as much involved in this ideological battle as Marting is. However I have not used Knowledge article space as a platform to promote my fringe ideas. I will rather let the 6677:. Hmmmm. I don't have any political agenda, I've never have been a member of any political group, let alone one with a published manifesto. Nor have I ever agitated at protest events or even have a blog, let alone write letters to editors. I'm just a regular Joe who enjoys editing Knowledge in my spare time, attempting to reflect reliable sources with due weight to the best of my abilities. I would suggest that Petri Krohn removes his huge political plank from his eye before complaining about the speck he perceives in my eye. 2587:(2) In my experience with bots such as this, a common problem is that they try to do too much and over-reach. Even the best bot operator in the world will get overwhelmed if they try to run a bot that makes thousands of similar but slightly different changes, that many people won't understand. Such bots need to be split into smaller tasks and those who frequent the Manual of Style pages and support such bots should have the patience to wait for a series of smaller tasks to be run, rather than everything being done in one go. 4846:) would have probably resulted in snowball closures of the discussions that Miami33139 initiated, with Miami33139, JBsupreme, and Theserialcomma more clearly standing out as the dissenting trio, instead of the more mixed reaction that occurred. So there is some fault for the continuance of this whole mess to be laid at Tothwolf's door. But extending restrictions doesn't address it in the slightest. All that the restrictions have done is supply parties to the case with something to game. 39: 6027:

a convenient way to socially network with a bunch of people I've come to know through contributing to Knowledge. Unfortunately this convenience led members of the list, myself included, into behaviour that crossed the line. This was due to a kind of mob mentality and a sense of hubris that developed along with it. This I regret. Prior to joining that list I was an editor in good standing, a clear block log, no ANI reports, no 3RR reports, no RFC/Us, no ArbCom cases about me, nothing.

7041:. Arbcom claimed no "good standing" in the Eastern European disputes arbitration, just that no actionable evidence against you was provided and that was the case. You were all battering Irpen, who refused that the scope should be changed from Piotrus and was overwhelmed by what became known as the EEML team. Provision of actionable evidence and the existence of actionable evidence is not the same, e.g. Irpen was sanctioned on the evidence of 22 reverts in the Holodomor denial article 5286:) are banned from interacting with each other, broadly construed. This includes things like not editing each other's userspace, not becoming involved directly with each other in discussions, and not nominating articles for deletion which another one has started. This does not prohibit commenting in the same discussion without directly interacting or editing the same articles so long as they are not directly in conflict. They may request enforcement of this restriction at the 6295:. It is true that I spent a bit too much time at the end of the case arguing for more equitable topic bans for the parties with Shell, as that end part did impact my study time a bit, and I probably ended up just annoying Shell too (sorry Shell). In that sense it was a distraction, but in terms of seeking an reciprocal interaction ban (which remains in force regardless of whether or not my topic ban is relaxed) was necessary and unavoidable under the circumstances. -- 6220:

which also means that anyone can devote as little or as much time as they can. I believe I'm a competent editor with an understanding of Knowledge's policies. I've had a long time to re-think things during my self imposed "site ban", and I do "get it" now. I just want to get on and derive some enjoyment from contributing to topics that interest me while allowing others to do the same, without this battleground BS. 2009 was an adventure I do not want to repeat. --

4493:. I think this AfD is representative of the continued disruption and misuse of deletion processes by these individuals. This article was nominated for deletion by Miami33139 shortly after I contested the prod deletion with the admin who deleted it. There are other articles that were similarly prodded/deleted which should also be contested, but that is not something I have the time to work on right now. While not showing the larger pattern, the edit history for 6886:

controversial areas and productive work elsewhere was needed to demonstrate how an editor in question copes with withdrawal from the battleground. Just going into self-imposed exile for the length of the topic ban (regardless of the real life constraints) does poor job answering the question whether editor's problematic behavior occurs again when he returns to the EE disputes. I still think that Martin's lift of the ban is premature at the moment. Also

4644:

make things worse. I think at this point I'd really like to see what the community decides in the AN/I discussion before we go too much further here. My own stress levels went down as far as the wikihounding goes when I simply stopped editing entirely, but it didn't fix the problem, it just meant I wasn't here to feel stressed out about it. If AN/I is ultimately unable to resolve things, I think I'd very much support reopening the original case. --

8404:, inviting comments about and edits to those templates from more experienced editors, so that all members of the community will have notice of the ArbCom decision and its topic scope. I have given the individual findings of fact on editor conduct in the ArbCom case a close reading to determine which articles are subject to the topic ban, but at least one editor who is about to be banned seems to read the topic restriction more narrowly. -- 6530:), which I find somewhat offensive. I do wonder why I have become the whipping boy of people like TFD who I have never crossed paths with in the past. Nor is it likely that I will interact with him in the future as our interests are divergent. At least Piotrus has the benefit of real opponents with real history of interaction and real issues which can be worked on. But as far as I'm concerned, the EEML horse is truly dead and buried. -- 4812:

It's-not-interaction-if-I-nominate-a-user's-draft-article-userpages-for-deletion-just-before-the-previous-restrictions-are-set-to-expire-as-long-as-I-don't-mention-the-user-by-name argument. I think that, as I questioned before, it was most unwise of JBsupreme and Theserialcomma to jump on Miami33139's bandwagon there. It was particularly unwise of Theserialcomma, who otherwise has mostly lifted xyrself out of this, it appears to me.

8868:

race-and-intelligence area with this article. Please find another area to edit in; at a minimum, if your editing in areas relating directly or indirectly to race issues or matters pertaining to members of a particular race or ethnicity is tendentious or problematic, I anticipate that we will be asked to expand the scope of the ban, and that we would have to consider that request very seriously. I hope that this will not be necessary.

2345:

previous usernames, and blocks thereunder. I realise this lack of transparency on my part made me look untrustworthy. My wikifriends have convinced me not to state that I didn’t appreciate the significance of this lack of disclosure because it would not be credible to the Committee. I can only apologise for my actions and for any other perceived indiscretions, and state that I have learned from these situations.

2590:(3) There are still levels of aggression, incivility and battling to be seen with those who support this and similar proposals. The first two editors above (Greg L and Ohconfucius) who showed enthusiastic support for Lightmouse were also the first two editors from this request to turn up at the bot request (where a discussion was already in progress), where they promptly escalated matters with these edits: 8724:

elements they involve, and not the main element. So on the topic of the voter intimidation case, there’s a race element because the New Black Panther Party is considered a black supremacist group, but the central controversy is over whether Obama’s department of justice is allowing politics to interfere with the objective application of justice, and that’s why the topic ban doesn’t cover it.

4857:, despite the attempts of myself and others to persuade them to do so, time and again. I know that for at least one other editor the assumption of good faith has been negated by months of evidence, here; and as Seth Kellerman points out above, Miami33139's "I vote delete on everything." rings much truer than the statements to the contrary on xyr user page, given what can be found in 5488:) is subject to an editing restriction for six months. Should Miami33139 make any edits which are judged by an administrator to be uncivil, personal attacks, assumptions of bad faith or disruptive to deletion discussions, Miami33139 may be blocked for the duration specified in the enforcement portion of the case. The six months starts from the day this motion passes. 4132:

I verified they had not been worked on since deletion. I nominated. All I ask is AGF. Uncle G was actually inflammatory role here. Uncle G advertising MfD in various places, using phrases like "flaring up" "not wise" and "being gamed" and highly suggestive of his opinion. This drew !voters questioning motives rather than the straight content issues raised about

4158:

per day. I have nominate for deletion less than 20 Knowledge articles in more than two months, which is a drastic change. Uncle G claim I am careless about deletion. In fact, of last nine closed AfD where I nominate, 5 were deleted with consensus of community. 2 were close as no consensus. 2 were keep. I do not think this is a record showing carelessness.

6615:

not to engage in such behaviour going forward, I don't understand the basis of Rlevse's reluctance, given that he was previously supported lifting the sanction of another editor with a similar FoF. The conditions that led to the problematical behaviour no longer exists, and having learnt my lesson, will ensure any similar will be avoided in the future. --

6929:

this is happening because he commented in a number of cases, including my case (which he was allowed to do). He should not be commenting on any cases according to the anonymous e-mailer to Petri. No so. In fact, the comments by Marting on-wiki were very much legitimate, much better than the cowardly letter by the anonymous emailer to Petri.

6216:

warpath. The way I see it, the bulk of the problems really boil down to personality clashes, some people are just implacably opposed to each other no matter what. Sad, but it's a fact of life. Probably in such cases interaction bans are the way to go when editors can't voluntarily refrain from finding fault and battling with others.

4600:

target articles/pages I would otherwise be editing, which ultimately results in less harm to the encyclopedia. That said, while I certainly felt less stress when I stopped editing, the behaviours clearly continued even in my absence, as even when I wasn't here they continued to target both my past contributions and other editors. --

2955:) with just a small set of units. It is possible to use automation to maintain/convert units of measure. Using automation to maintain/convert units is a 'good thing' and I'm sure we'll find a way. There aren't many editors contributing to the discussion and it'd be useful to have a wider range of views. Feel free to comment there. 4178:, it is burden of person adding material to add source material. It is indeed, "Somebody Else's Problem" to source article. This is basic conflict of Knowledge editing and deletion philosopy between Uncle G and myself but this is a schism between all volunteers on Knowledge. My own opinion, that material should be cited 3083:

functions that are not relevant to what you seem to be proposing, or that would be inappropriate in the current circumstances. I would like to see a current statement from BAG indicating specifically which functions you will be performing during this trial, and how they will monitor the results, before we move forward.

4174:

because other editors have already said it and my opinion not necessary. I made that statement to give weight to fact that I voted Keep on that AfD. Uncle G also has philosophy about sourcing requirement of articles. Uncle G claim at AfD that people like me are required to put source in article. Untrue according to

8393: 6116:

requesting an early relaxation and thus am prepared to acknowledge these issues and make the undertaking should be viewed as a positive development by the committee and be applauded, not ignored or viewed sceptically (which would be wholly unjustified given my previous good standing and good behaviour since).

4346:. This discussion was initiated by JBSupreme, with Miami33139 showing up to support him. This article was kept nearly unanimously during its first AfD, with the only delete !votes being JBSupreme and Miami33139. As of this posting, during the second AfD, again the only delete !votes are from JB and Miami. 8867:

I am in general agreement with the other arbitrators on their interpretation of the scope of the topic-ban. I also reiterate my view that while the New Black Panther Party case is not within the scope of the topic-ban, it is a really poor idea for Captain Occam to start his editing career outside the

8647:

Without reading the findings, especially the ones one locus, and case history, one could read it as being about "race and intelligence" or "race" and "intelligence". But if you read the findings on locus and case history, they clearly center on "race and intelligence". The proposed article by Captain

6973:

case. However, someone, who wishes to remain anonymous, contacted me, and – knowing the strong feelings I have privately expressed about the issue at hand – implied that I am a pussy if I do not express my strongest objection to this motion. He also sent me evidence (see appendix) he had prepared in

6242:

Igny launched against me while I was away, let alone interacted to any significant degree on any particular article. I just scanned the EEML archive and Igny isn't mentioned at all, so he didn't appear on the list's radar. Perhaps he may have been somewhat radicalised by the EEML case itself, and may

6205:

Russavia also became involved in this SPI case too, as he did in a number of other AE cases launching complaints against Radeksz, Biruitorul and Biophys. Consequently the Russavia-Biophys ArbCom case was opened. I took that opportunity to request an interaction ban for Russavia. I believe I conducted

6201:

Shortly after being granted permission to source a number of BLPs, I had an opportunity to undertake some study. Unfortunately about a month later, Igny involved me in an SPI case, however somebody kindly informed me of this via email. I can't recall having really interacted with him that much prior

4984:

So it seems to me that nothing particularly good has come out of the previous arbitration case. The interaction restrictions are being gamed, the taunting continues, and the behaviour in deletion discussions is even less an example of good practice than it was those several months ago. I think that

3334:

It appears that the Motion allows BAG to approve new applications and to amend an existing approval without reference to ArbCom. The Alternative Motion seems to require a separate application for amendment here, no matter how trivial the request change might be. I note Coren’s statement “to allow for

3006:

Add/maintain units is rather tedious work when done by hand. An amendment would allow me to do what many editors do, use a normal account to use semi-automation to add/maintain units of measure. Hopefully, the new fear, uncertainty and doubt relating to bot usage for similar tasks will be resolved at

2764:

Certainly; all these disruptive initiatives have been produced by a desire to improve Knowledge. The reason for the ArbCom decision was the absence of any consideration that others might not feel the same about what does improve it; this proposal that Lightmouse/Bobblewick, of all people, should have

2340:

I became a key player in encouraging a more discerning approach to internal linking, particularly dates and times. In the early days this resulted in a number of blocks. I probably didn't respond in the right way to sysops who blocked me, finding it easy to think of them as "involved". I believe I’ve

2263:

I've been a Wikipedian for more than six years, and have played a key role in ensuring that metric and non-metric units are provided in the clearest and most conventional ways for our international readers. I was early in recognising the value of automation for janitorial work in such a large, global

1887:

I don't see anything here that requires ArbCom intervention. Issues over content should first go through lower levels of dispute resolution (and aren't likely to gain tranction at ArbCom ever); other issues seem to be requests for enforcement rather than something that would require amending a case.

1498:

that has resulted in a number of disruptive or BLP issues. Previous attempts to address this problem area have not been successful, as noted above. A topic ban as outlined, which can be reviewed at some point in the future, may give him time to reflect and/or seek a mentor that perhaps can help him

8857:

The two Arbiters above covered it fairly completely but I'd also like to note that topic banned editors shouldn't be discussing the topic with other editors, especially not to try to influence their editing. I also want to remind Captain Occam that if people known to be associated with him suddenly

8729:

It would be helpful if arbitrators could clarify whether this interpretation is correct. I also approve of Vecrumba’s suggestion above, that labels be placed be placed on all of the articles covered by topic bans in order to forestall any future confusion over this. However, if this solution is to

8639:

on the proposed decision talk page, I asked the arbitrators whether my topic ban extended to this article, and all three of the arbitrators who expressed an opinion there (Newyorkbrad, Rlevse, and Carcharoth) stated that in their opinion it did not. Rlevese and Carcharoth both also explained why in

7426:

As with some of the other editors who were sanctioned in this decision, I would be agreeable to at least some curtailment or narrowing of the remedy—partly based on the feeling that the breadth of the remedy may have been wider than necessary to begin with, and in any event due to the lapse of time.

7175:

To TheFourDeuces' gross misrepresentations, suppositions, and personal attacks, I invite him to provide evidence where anything I (or other EEML members) have represented on Knowledge is other than a fair and accurate representation of reputable sources—and representing majority scholarly opinion on

6800:

without any issue or drama, so it would be disappointing if the Committee where to now apply the brakes and not relax the topic ban further in some way. I could have just as easily waited out the remainder of my topic ban and return to editing later, I've got plenty of other things to do in the mean

6246:

As to Igny's question whether a topic ban is designed to demonstrate if an "editor's problematic behavior occurs again when he returns to the EE disputes", note that I had edited German related topics in January and February with no problems, and I think I amply demostrated decorum in my response to

6124:

After nearly eight weeks of waiting, I am appreciative that the Committee is finally acting on this and has proposed a couple of motions. But I have to question whether Brad's proposed motion isn't a pandora's box of gaming potential (as it was originally pointed out when he first proposed it in the

6026:

The locus of the WP:EEML case relates to off-wiki co-ordination and canvassing, which was done via a mail list. In the nearly nine months since I've taken stock, while taking a break to pursue some postgrad study. During that time I've reflected on what went wrong. I joined the maillist primarily as

5013:

I will take resolute action next time Tothwolf complains to me about baiting, taunting or bullying by the folks who've already been warned. Those folks would do well to steer a wide path around Tothwolf, and to scrupulously avoid committing similar abuse of any other editors. You have the chance to

4861:

in the project namespace over and over again. What we really have here are two accounts that have failed to follow good practice for a long time, and have reached what is probably an all-time low (more on which later) quite recently, primarily in conflict with an editor that in turn does xyrself no

4807:

I've been asked to comment here, by two people. I've hesitated because I really don't want to get entangled in this. There's not much that I can add, strictly speaking, that isn't already available for perusal. Apart from the electronic mail messages sent to me by Tothwolf and two administrators,

4635:

and I discussed just such a potential solution before the original ArbCom case was filed. I have a strong feeling that if a simple interaction-type restriction were put in place, these editors would still follow my edits in order to remove content from or nominate articles and pages for deletion, or

4131:

I see based on Uncle G description, how the timing of the MfD of Tothwolf userpages could appear baiting. It was not. I did know which article Tothwolf kept in userspace and did mean to ask to be deleted. It was not timed for baiting purpose. I knew it was many months since they were deleted at AfD.

2947:

This is an update. We have been in discussion at BAG for a month and a bit about reviving Lightbot with just the units of measure component. I thought it was simply matter of restating the previous Lightbot BRFA with just the units component, and amending if needed based on real examples of where it

2418:

I too have always found Lightmouse helpful and unfailingly courteous, and always willing to act promptly to fix any problems (which were few) in his scripts and bot. I believe that WP has benefited greatly from his involvement and will continue to do so if he's allowed to use his skills to the full.

2404:

I have found Lightmouse proactive, reactive, and curteous at all times. Lightmouse has been a great inspiration to me, not only because he demonstrated to me that he cares deeply about the project, but also because he understands the potential benefits of automation for this project, which is filled

1829:

I'm inclined to agree with MastCell (and take no action), but would add that ScienceApologist needs more than anything else to rein in any aggressive aspects to his postings. If he finds himself being annoyed by what others are saying, find ways to take a break or rephrase replies. It is a fine line

1394:

Clarification on my post re NW: the diff was to illustrate that you read the 3rd ref, did not see any evidence of Watts being labeled a "denialist" and asked ScienceApologist to clarify where it came from. It was not meant to indicate that you warned him nor that you took any administrative actions

8698:

I’d also like to add that in order to avoid similar requests for clarification being necessary in the future, it would be helpful if ArbCom could come up with a clearly-defined boundary for my (and David.Kane’s and Mathsci’s) topic ban. For example, if the topic bans cover every article related to

8674:

article in the past three months, and have only edited it a total of 11 times in all the time I’ve been active on Knowledge. Contrary to Slrubenstein’s statement, the arbcom ruling about me also does not state that I’ve engaged in POV-pushing on these articles—I’m being sanctioned for edit warring

6948:

I object to lifting this remedy. Considerable time was spent on the EEML case and its members, rather than accepting the facts presented, wasted months of time of arbitrators and witnesses and were very offensive to them. Martintg's defence is basically that he fell into the wrong crowd and he is

6614:

case involved off-wiki co-ordination and canvassing, which was done via a mail list. Prior to joining that list I was in good standing, a clear block log, no ANI reports, no 3RR reports, no RFC/Us, no ArbCom cases about me, nothing. Having ended such off-wiki co-ordination, and given an undertaking

6111:

Having ended such off-wiki co-ordination, and given an undertaking not to engage in such behaviour going forward, the conditions that led to the problematical behaviour no longer exists. There will be no off-wiki coordination, no canvassing, no usage of hidden communication to create the appearance

5191:

Shell, thanks for advancing the discussion. Re the section below, are these ideas you are raising for discussion purposes or are you asking that they be voted on as motions. If the latter, someone (I'll do it if I'm here, or a clerk, or anyone really) should set them up with the support/oppose/etc.

4909:

Yes, I think that we really do know. We really do know that JBsupreme is acting to always oppose whatever Tothwolf happens to want here, rather than in pursuance of xyr stated position, and not acting in good faith. It flies in the face of reason to assume that an editor who declares something an

4785:

When someone chooses to harass a person here, there are two things necessary in the target: some weakness that an be exploited as the basis for the harassment, and a tendency to sometimes reply inappropriately. In a sense, almost anyone meets these requirements to be a target: Any active editor has

4643:

Sigh, I dunno... Seth Kellerman really is correct above where he mentions that I Plaxicoed myself when I fell into the baiting which was happening while the original case was open. I really want to be more careful with what I say here this time so as to not say the wrong thing and otherwise somehow

4157:

Uncle G raise deletion activity which is not at all related to Tothwolf and Uncle G show no connection to Tothwolf in my activity. Uncle G claim I have not adjusted my actions towards deletion. Prior to Arbcom I would propose or nominate many pages each day for deletion. After Arbcom I do maybe one

4100:

I understand that deletion of material often upsets people and I have acted at Arbcoms suggestion on my deletion activities. I have slowed down the rate of proposing deletion and deletion requests to be more managable. The overlap with Tothwolf is minor and not any sort of personal vendetta against

3215:

The current configuration is wholly dependent on BAG. I thought BAG would simply revive the relatively uncontroversial non-date portion of Lightbot. Unfortunately, those involved in the date delinking dispute (on both sides) have become involved. I think we'd get an early and defendable decision if

2989:

I had thought that the BAG revival of the unit portion of Lightbot would be a mere administrative matter. I was wrong. Some editors involved in the date delinking debate (from both sides) have become involved in the debate about units. Nobody (apart from me) appears to be considering moving forward

2502:

A 'unit of measure' is any sequence of characters that relates to measurement of things. This includes but is not limited to units defined by the BIPM SI, the US NIST or any other weights and measures organisation or none at all. This includes but is not limited to time, length, area, volume, mass,

2189:

1426:

seem specious since there is currently acknowledgment on the talkpage that a line identifying Anthony Watts as a denialist/skeptic/anti-environmentalist should exhist in the lead, perhaps with different wording than what I suggested. Whether inserting information that a living person is a "skeptic"

8830:

Second, the topic ban applying to named editors is much broader (which is why it doesn't use the same language as the discretionary sanctions) and applies to articles about race and about intelligence. The topic ban's objective is to prevent exportation of the dispute to other areas and to prevent

8656:

The locus findings make clear this case is narrowly about race and intelligence (the category is linked there). One of the reasons the locus is so narrow is because the editors in question had a very narrow focus and the further questions arise because these editors are expanding this focus. I did

8626:

article, and I’ve stated this several times on the talk page for that article. The reason Aprock, Slrubenstein and Muntuwandi have been asking about this here is because I also stated on this article’s talk page that I consider my decision to stay out of this article a voluntary one, so I did not

7741:

I think this modification would allow Martintg to edit all the articles he's mentioned in his request, without getting involved in the nationalist dispute articles that have previously been troublesome for these editors. The existing broader topic-ban expires in December, and I've left that timing

7179:

I believe Martintg is ready to return to productive editing. If his behavior is less than exemplary, ArbCom will be watching. Perhaps a review at three months to "re-up" the lifting of his topic ban for the rest of the original term if impartial, uninvolved editors have a genuine concern. Martintg

6446:

This is an incredible blanket statement. TFD has no idea what my politics are, or that of other members, and I ended collaboration with the list at beginning of the case. The political viewpoints are as diverse as can be expected by the differing backgrounds and locations of the group members. For

6219:

I'm perplexed at Igny's comments here, given that he hasn't made that many recent edits himself either. We all operate under different constraints. After completing the semester I found time from family and friends to source those BLPs that I had committed to sourcing. Knowledge is a free project,

5181:

I've proposed some motions, 2 new remedies in the case and one minor update to reflect what appear to be the prevailing concerns. Due to confusion over interaction restrictions in the past, I've attempted to flesh out the restriction a bit more and wouldn't be adverse to other Arbs tweaking it if

4537:

Note the massive numbers of automated or semi-automated edits by Miami33139 which remove Beyond My Ken's changes to the articles. I also noticed that the script Miami33139 uses for this task doesn't function properly in that it often improperly re-orders navigational and stub templates and removes

4213:

As an outside observer it appears to me that Tothwolf has been failed by the wikipedia system repeatedly throughout this ordeal. Baiting is difficult to demonstrate, and more difficult to demonstrate without walls of text. Tothwolf tends to be verbose and disorganized with providing difs, and he

4173:

Uncle G also has a different Knowledge philosophy than me, and is hardly neutral towards my deletion activity which is why he raised it. Uncle G take out of context my statement "I vote delete on everything" from a prior AfD. I made that comment because I rarely vote Keep. I do not vote Keep often

2629:

Carcharoth, I agree Greg's and Ohconfucius's comments were a bit over-the-top and reminiscent of the old toxic MOSNUM discussions, but I think further restrictions, given that this was a one-time incident quickly contained, would be a bit much. Of course, if that occurs again, I couldn't blame you

2389:

Knowledge benefits from experienced automation experts such as Lightmouse. When I first became aware of Lightmouse, I found that he was always acutely sensitive to feedback from upset editors after a bot produced unexpected and undesirable results. He quickly (typically in a matter of hours) would

2348:

Since my return after the 12-month ban I have resumed manual janitorial work. I would like the chance to show good faith in the use of my skills in automation for the benefit of the project. Therefore, I am applying for an amendment to two of the three current remedies so that I might return in an

1800:

Amendment 1, as proposed, is a complete non-starter in my books: first, it drags ArbCom far too deep into evaluating an individual content dispute, one which we're entirely unqualified to resolve. The case already makes clear that there is a category between fringe science and majority scientific

8634:

However, I do intend to eventually create an article about the New Black Panther Party voter intimidation case. And this has nothing to do with my interest in race—I consider this a politics topic, and it’s the only recent political controversy in the United States that does not yet have its own

6928:

I support lifting the ban for Martin because he was productive and created sixty six new pages. Whatever problems he might have in the past, six months was a long time, and Martin was never a major "violator" anywhere. So I wonder what was the reason for the statements against him? Most probably,

6869:

I can not recommend the lift of the ban for Martin based on his recent WP activity. In the recent 100 edits he just wasted everyone's time when participating in Russavia-Biophys EEML-related ArbCom case, and after some break just when EEML case was due for review and just when others filed for an

4599:

While I would very much like to return to actively editing Knowledge, as it stands now I don't feel that I can unless the disruptive behaviours from Theserialcomma, Miami33139, and JBsupreme are fully addressed. When I'm not here editing, these individuals are not as readily able to tendentiously

2895:

Agree with Tony that other BAG members should be urged to comment. I think Carcharoth has a point about the inherent tension in the 'open' nature of the bot request, and the demands within the BAG for it to be firmly nailed down. I would like to remind all that the objective of this appeal is the

2743:

For the record, date-delinking was born out of a desire to improve WP. Date-delinking received enormous community support (via the various RfCs), and the end result of delinking was the removal of almost all linked dates (and date fragments) on millions of pages—something that has received little

1702:

Given ScienceApologist's lengthy history in front of the Committee, I've actually been struck by the change in his approach (for the better) in his editing over the past few months. I don't really see the grounds for imposing an editing restriction at present, particularly not the extremely broad

8423:

Given that there is contention regarding the role and nature of race (societal, biological, genomic) and that there is still debate as to what degree "race" as a societal concept is mirrored in real genetics, any race related topic dealing with concepts of, evolution, biology, heritability, etc.

6215:

Igny states I wasted everyone's time in that ArbCom case. It is true that I did waste a bit of time, it could have been spent more productively on my studies, but I think given the outcome it was well worth the effort. It's not a nice experience to be informed by email that some are still on the

6161:

will not attract the attention of my opponents who would attempt to wiki-lawyer a case that I had violated this new amended topic ban and shop for admin action, given that the Soviet period had a significant impact on visual arts in Estonia. I don't think it would be fair on me to provide such a

4195:

Uncle G make some claim about Theserialcomma. He can defend himself. Undoubtedly Theserialcomma have Tothwolf pages on his watchlist and follow to MfD. His involvement on WP sporadic for several months. Since at least April I see no other intersection between him and Tothwolf. I hardly think two

4146:

Uncle G show no other evidence, except bad faith on my motive, that I harass Tothwolf or that my editing shows substantial interest in Tothwolf. I have no interest in Tothwolf other than followup to delete articles in userspace that were previously deleted. I have been engage at userspace issues

3082:

Lightmouse, I am willing to give you another chance to engage in automation work, provided that it is done under appropriate supervision from BAG to ensure that we don't fall back into any repeats of your past conflicts. Having said that, the Lightbot 3 BAG approval request included a number of

2724:

Anomie also remarks, correctly, that the request for approval is backed by Lightmouse's fanclub at MOSNUM; so - aside for Jarry (I hope he realizes what he is getting into) - is this request for amendment. This is the same group and the same situation as the date-delinking case; a small group of

2482:

I have, to the best of my knowledge, never interacted with Lightmouse before this present appeal - that is to say, I have no prior axes to grind, only good faith. Okay. So now I think about it, it seems the best plan is thus (and I shall post this suggestion to Lightmouse's talk momentarily): 1)

1437:

within the fields of the social sciences. This discussion is not easily decided as a simple "yes" or "no". Additionally, with the sole exception of one diff from Polargeo, all the evidence above submitted is communication exclusively from editors with an acknowledged bone-to-pick with mainstream

6790:

Well sure, if the Committee wants to impose some kind of conditionality, that's fine with me. ArbCom wouldn't even need to be watching that closely, as it's been demonstrated here that there are more than enough eyes to scrutinise my behaviour, even by those wiki-warriors who believe there is a

6323:

Yes it is true that I have commented in a few ArbCom cases, but my conduct in doing so has been exemplary and I was motivated by the desire to reduce the level of conflict in that space. If some people are upset that I did comment, well I guess that is to be expected. The Committee can and does

4122:

that my editing had any interaction with Tothwolf? My nominations of two of his userpages for MfD particularly avoided discussing him and only focused on the fact that the content was previously deleted and stale. How could I be harassing Tothwolf without interacting with him? Tothwolf needs to

4096:

In this ANI post, he is essentially repeating the accusations of persecution that he made about myself and others in the Arbcom case. He blames Arbcom for his troubles. I do not feel I should have to defend myself all over again when he has sympathetic administrators (his claim) on ANI ready to

4083:

On the xpiration of his Arbcom sanctions, Tothwolf recently started an ANI discussion accusing me of hounding and harassing him again in the same manner that brought this issue to Arbcom the first time. He singled out the handful of deletions that involve him and his preferred editing area (IRC

3330:

It appears that the Motion permits LM to test proposed Lightbot functionality before taking the proposal to BAG either as a automation request or an amendment to an existing Lightbot approval. I’m picking up that most or all bot editors would regard this as good practice. On the face of it, the

8906:

Given what has elapsed here, I think the topic ban should be extended to include race-related articles. However, as I pointed out, a remedy proposing that in the proposed decision did not pass. I regret that Captain Occam chose (on the proposed decision talk page) to interpret this as implicit

8770:

include this article when counting R/I edits, as aprock says. I may be open to allowing this editing after a few months of non-controversial editing (and I would personally entertain a request for amendment at a future date to allow such editing). However, I see no reason to allow such editing

8723:

race—such as what causes the difference in average IQ between races, to what extent racial groups line up with genetic clusters based on geographic ancestry, etc. But the conclusion I’m drawing is that my topic ban does not extend to articles about controversies where race is only one of many

7500:

Noting that I've read Martintg's response and the postings at the user talk pages of Newyorkbrad and Rlevse, and my votes remain as posted below. I would ask that the editors that oppose this amendment think twice before trying to dispute editing that Martintg does following the passing of the

6992:

From this POVish point of expertise I can testify that Marting is the chief battle axe of the opposing side. He is not the benign Wikignome he now pretends to be. Anything he touches will turn into distortion of facts or into a political battlefield. His presence on Knowledge, in the contested

2903:

That the BAG operation should fall within the auspices of Arbcom in this particular instance may be a factor in the low participation rate there. The balance is not being struck apparently because an unnecessary complication – behavioural considerations – has been brought in. IMHO, behavioural

7004:. This has extended to multiple forums on the Internet outside Knowledge. In the evidence sent to me were new instances of this campaign, unknown to me previously. If this proposed motion were to pass, I feel that I will finally have to start an arbitration case against Marting on this issue. 6711:

Regarding point 3, whether a topic ban extends to commenting on a particular editor when there is no interaction ban in place is a grey area that certain admins have taken a position on. I note that Biophys has commented upon myself despite his topic ban here in this amendment request without

6515:

Again I don't know who TFD is referring too here, my record shows that I have a relatively clean record in this regard, apart from a block for a 3RR violation that was applied 20 hours after I had undone my 4th revert, and a mis-applied block for alleged OUTING that never ocurred. In fact the

2849:

What is the status of this amendment request? As far as I can see, the bot request is still in progress (it has been open for 22 days and is still being edited), and that request needs to be either accepted, or modified and accepted, before any motions can be proposed here by arbitrators (per

2344:

Finding the adversarial atmosphere of the case difficult to cope with, I ultimately declined to defend myself. I now regret my failure to participate properly, which I realise is frowned upon. I was strongly criticised during the case over a bot application to BAG in which I failed to declare

1573:

mentality of certain actors in fringe science areas is inescapable, in spite of some distasteful tactics, contributions from a wide range of people can be valuable to Knowledge. I recommend that this malformed enforcement request be summarily dismissed with a caution to GregJackP about filing

6115:

On a final note, I could have just as easily waited out the remainder of my topic ban and quietly slipped back into editing the area without subjecting myself to this, without having to acknowledge the issues that led to topic ban or make an undertaking in regard to the future. The fact I am

4191:

Uncle G raise significant issue with evidence on questionable deletion activity involve JBsupreme. He can defend himself. When reading Uncle G statement, be careful to differentiate JBsupreme edits from mine. I should not be punish for JBsupreme activity. JBsupreme obviously in contradictory

3200:

Is there any update on the status of this, or currently pending request for action? If necessary, this request should be withdrawn and re-filed when it is ready for action. I don't think it's a good practice for requests to stay open on this page indefinitely. (This is a process point, not a

8450:

To some of the commentary subsequently, I would respectfully request that we stick to the request for clarification, not relitigate R&I in the light of other articles. Either "Race (classification of humans)", for example, is in scope (that is, with respect to all sanctioned editors, so

6247:

an EE dispute not of my making thrust upon me by Igny in the form of the SPI in March and again in the follow-up Russavia-Biophy case (and note that I didn't involve Igny in my proposals presented in the case workshop). So the risk of problematic behaviour has been demonstrated to be nil. --

3382:

Thanks. On the basis of what you say, both motions permit testing of the BRFA functionality using the Lightmous account. Since one motion has passed, I'll start testing the BRFA functionality immediately to support the ongoing BRFA discussions. What'll happen if both motions get five votes?

3263:

Thank you. However, the requested amendment to 7.1 was to be "Lightmouse is indefinitely prohibited from using any automation whatsoever on Knowledge, except that he is permitted to do so in the field of ‘units of measure’...". This would allow me to use the Lightmouse account to do routine

2656:. When I wrote that, I perceived that Lightmouse was the recipient of unnecessary third-degree by Anomie. But, apparently that is a legitimate role of Anomie’s so I shouldn’t have criticized him for being out of line. I am truly sorry for that. As for my “gratuitous” image when I linked to “ 6885:

Update: I understand I could be too harsh in my statement and quite possibly our personal clashes in the past contributed to this. But in any case a "site-wide self-imposed ban" is not the right way to deal with topic bans. Topic bans were placed in part to reduce battleground mentality in

4401:

I know I made some huge mistakes in allowing myself to be baited back in December while the original case was open. While not an excuse for my own behaviour in how I responded, at the time I was extremely frustrated with how long the case had been dragging out without any resolution to the

4109:

2% of my editing in the last two month has any overlap with Tothwolf. None of these overlapping edits are about him. Even while nominating his two userspace articles at MfD I did not direct any commentary to or about him. His accusation that a small handful of edits are persecuting him are

3278:

You're free to ask BAG to simply authorize the semi-automated editing you'd like to do, independent of any bot request, and I see no particular reason why they would refuse to do so. However, given the problems we've had in the past, I'm not willing to give you a blanket permission to use

7082:

3) Martintg did little else than take exceptional efforts to violate the spirit of the topic ban and remain an attention-seeking nuisance in the EE topic area despite topic ban. Immediately after the Arbitration ended, Martintg was back on arguing at Mass killings under Communist regimes,

4169:

and open each article. The ones which look bad, I nominate. Another volunteer is heavily interested in web browser or open source games so Tothwolf "stalking tool" will show overlap between our edits and he claim I stalk other volunteer. This type of accusation is most frustrating to me!

8495:, Captain Ocaam, David kane and Mikemikev generally pushed two views: that average diferences in IQ according to race have or likely have a genetic basis, and that races are biologically real (or natural divisions among humans). The first claim was relevant to some other articles, like 4662:

I've found it largely counterproductive to argue with Theserialcomma, Miami33139, and JBsupreme, or attempt to edit an article they've nominated for deletion. They argue against reliable sources, revert/remove my edits, or otherwise attempt to discredit me in some manner, often claiming

8454:

This article falls under the "Race and intelligence" topic ban of (DATE), widely construed. Participating editors are reminded not to contact topic banned editors regarding this article as such contact can be taken as baiting editors to violate their topic ban. Thank you for everyone's

4934:— JBsupreme and Miami33139 reiterating their argument, presented numerous times before to sound rejection by many people, that it's not up to the two of them to put in the effort of looking for sources for information that has no sources cited, but that that's Someone Else's Problem. 4748:

that I largely put on hold starting in November 2009 when the ArbCom case was initiated. As I've previously mentioned, I really do not feel that I can edit while the wikihounding and harassment is taking place and I found it much less stressful to instead focus on my work outside of

2718:

which will count how often it has edited a page or queue changes; he is unwilling or unable to produce a bot which will write edit summaries reflecting what it actually does; and I see no reason to believe that this bot (if overriden by a human editor), will not come back and revert

6061:

Since December I have created some articles on German politicians and political organisations and had sourced a small number of Estonian biographies without any issues (many were not notable so I hadn't bothered with those) after I requested and was granted a relaxation to my topic

1106: 1830:

between strong arguments for what you are saying, and being dismissive of what others are saying. I think both ScienceApologist and GregJackP are capable of sorting things out here if they make the effort, and possibly with help from others if they continue to end up in disputes.

1574:

frivolous enforcement requests in the future. Allowing this kind of activity will encourage a situation similar to that which existed on this page two years ago when dozens of frivolous and ultimately dismissed enforcement requests were filed against me over the period of a year.

8827:

and any closely related articles (which, for example, were for whatever reason not tagged as part of the controversy category). However, individual sanctions under this remedy can be very wide-ranging and can prevent specified editors working on any article, or commenting on any

8675:

and false claims of consensus, and the finding of fact about me does not mention POV-pushing at all. For these reasons, as well as the reasons given by Rlevse and Carcharoth that I quoted, I don’t think my topic ban should be extended beyond the locus of dispute for this case.

6720:. So evidently there is an element of off-wiki co-ordination going on here. (Perhaps TFD was also canvassed off-wiki to comment here, that would explain his involvement given no real history between us, who knows). It is a pity that Petri has chosen to resume this troubled 6731:

Why should some one like Petri Krohn, apparently an activist with a clear and documented political agenda, be allowed to smear me and sour my editing experience because he imagines me to be his political enemy solely because I happen to have an interest in Baltic topics?

2610:, but I would suggest arbitrators consider what happened there and whether any form of restrictions are needed to prevent a similar dynamic arising again where a familiar group of users turn up to use inflammatory language to defend Lightmouse, his bot, or his proposals. 7268:, Martintg has recently been violating or testing the limits of his existing topic ban. My name featured prominently in the mailing list archives as somebody to be neutralized. It is not at all appropriate for Martintg to be carrying on, today, a vendetta against me. 2012: 931: 8396:, with a helpful response from arbitrator Carcharoth, how the community might help make editors aware that some articles are within the scope of the discretionary sanctions to be adopted in the soon final decision of that case. I have already written a template 7007:

I have no objections to Martin using his freedom of speech to promote his ideas on the Internet. However, I cannot see why – having broken the key principles of Knowledge – he should again be given a license to distort Knowledge to fit his political agenda. --

6695:

Petri Krohn has also appended what seems essentially to be a polemic written by someone "who wishes to remain anonymous" presented as evidence. Who ever this anonymous person is, perhaps it is Petri Krohn himself, I will never the less address the main points:

8804:

are centrally about race and claimed differences between races. I agree that it's outside of the topic ban for that reason. However, I reiterate that it's a very bad idea to edit in such a controversial area on the heels of an ArbCom case. See NYB's comment.

8665:

This seems reasonable to me. Although my involvement in other race-related articles was brought up in order to show the focus of my editing over the past year, the locus of dispute makes it clear that this arbitration case was specifically about articles in

4811:

As I suggested at the ACN talk page, it does look like things are being gamed here. This request to mute Tothwolf is more such. I'm not sure that we should be continuing to buy the self-descriptions that aren't borne out by actions over the months, or the

8765:

is prohibited by the topic ban. The remedy says that the topic ban applies to "race and intelligence related articles, broadly construed." Construing it broadly, I think all articles about race controversies are included, including the Race article, and we

8703:, then that’s very easy to understand—it means that if an article is listed in this category then we can’t edit it, but if it isn’t then we can. However, I predict that a less clearly-defined boundary will result in a lot of further confusion over this. -- 6324:

examine the behaviour of anyone participating, as they did in the Eastern European disputes case. Krohn's mysterious emailer had every opportunity to present evidence against me, and I'm sure they did during that case however the Committee exercised their

5115:

Thanks to Uncle G for the statement and thanks to others for their statements. There should be enough here now to allow an assessment of what to do here. Currently waiting for further comments from other arbitrators before deciding where to go from here.

2008: 927: 6507:"Dispute resolution, reporting editors for 3RR, writing Wikiquette and ANI reports are extemely time-consuming and allowing editors like Martintg will only discourage capable editors who are discouraged by the processes to counter editors like Martintg." 2900:

to have committed; OTOH, it is as much for Lightmouse to demonstrate that, without being put into a straightjacket where he cannot possibly do anything wrong (after all, what's the point?), he is responsive and capable of running a bot in a responsible

7713:) is topic banned from articles about national, cultural, or ethnic disputes within Eastern Europe, their associated talk pages, and any process discussion about these topics, until December 22, 2010 (one year from the closing of the original case). 6376:

was initiated this year where absolutely no one from the EEML voted, yet it resulted in a "Keep". While it was clearly wrong to canvass the first AfD, non-involvement in the 4th actually resulted in an outcome I would have wanted anyway. Go figure.

8907:

support for him editing so close to the boundaries here. There are plenty of articles he could chose to edit that are unrelated to either race or intelligence or both. There is absolutely no need to test the boundaries here in any way whatsoever.

6429:

Sure, the canvassing was wrong, I accept that, but I stand by the substance of all my edits (but in some cases not the form, i.e. the occasional edit warring). I not sure why I need to apologise to TFD though, I've not known TFD prior to the EEML

2004: 1996: 923: 915: 4565:

in particular has been a target of particular interest to Miami33139. He has worked very hard on expanding articles about FTP clients, web browsers, email clients, etc which Miami33139 began to target after he noticed Mabdul was also a member of

4931: 4343: 6412:

No, I didn't say that at all. There is nothing wrong with the individuals, but unfortunately a mob mentality developed and led some of us of otherwise good standing (I had a clear block log prior to joining the EEML) to cross the line, which I

5290:

board or by email to the Arbitration mailing list; they may not request enforcement or action against each other for any other reason or at any other venue. Attempts to game this restriction should be treated as a violation of the restriction.

5130:

I agree with Carcharoth. Miami, the comments you have made are over the line and cross into NPA. You are apparently unable or unwilling to see that. I agree with Carcharoth that this area may need to be reopened, or an amendment passed here.

6907:

Re NYB and SirFozzie, I understand that you are willing to put your trust in that Martintg will not return to the "previous behavior". Could you clarify by showing examples of particular behavior that might warrant reinstatement of the ban?

6471:"It is irritating that as I and other editors were arguing with Martintg and his colleagues and they were presenting arguments against us that off-wiki there were agreeing that our arguments made sense and trying to develop a new approach." 3371:

And no, the motions can't apply at the same time: they are alternative to each other. The first proposed effectively lifting the restriction, the second allows for an exception only but leaves the restriction in place for the time being.

1682:

When I first saw this enforcement action being developed, that's where I thought we were headed. I'm surprised it ended up here. I was going to not comment at all, but the arbitrators actually asked for a statement from me. I obliged them.

8636: 8658: 2000: 1992: 919: 911: 6718:"However, someone, who wishes to remain anonymous, contacted me, and – knowing the strong feelings I have privately expressed about the issue at hand – implied that I am a pussy if I do not express my strongest objection to this motion" 3730:

Better than nothing, but I expect the insistence on a single task will cause all sort of headaches for us down the line due to the distinction between the fully automated and semi-automated versions of the unit conversion BAG request.

3505:

This goes too far in the other direction, given the amount of past trouble borne out of Lightmouse's well-intended but ultimately disruptive automated editing. I am amenable to supporting a loosening of the restrictions to allow for

1245:

Statement by GregJackP that I "misrepresented what references actually state" and "misrepresented that the articles referenced are peer-reviewed when they are not" are both disputed by myself. No amendment of this sort is necessary.

2876:

has been the only active BAG member on this matter has now gone on vacation until 16 August. I have no idea about BAG processes, but I wonder whether it is possible for other BAG members to be requested to be a little more active.

7176:

the Baltics and Eastern Europe. I regret that more than half a year has passed since imposition of the topic ban and TFD is not alone in continuing to demonstrate offensive bad faith in re-litigating EEML with unfounded charges.

1988: 907: 8571: 6455:"They do not accept that Knowledge articles should be neutral and tied up the time of numerous editors. While it may be that they will no longer coordinate their efforts, their approach as individuals is damaging to neutrality." 5923: 5882: 4910:"abuse of userspace" one minute is acting in good faith when xyr next actions, in relation to the editor who is, supposedly, abusing that userspace, are to then attempt to re-claim, and prevent the deletion of, the page in xyr 8730:

be used, I think the labels need to be placed by either clerks or arbitrators themselves. Otherwise, they’re going to represent only one editor’s interpretation of the scope of topic bans, which is not necessarily correct. --

8345:

Given the fact that there seems to be some confusion about what the scope of articles covered by the remedy: "8) Captain Occam (talk · contribs) is topic-banned from race and intelligence related articles, broadly construed."

7501:

alternative amendment. It will only serve to promote more ill-feeling. At some point, you need to learn how to work together, even if that seems impossible right now. And if you can't work together, learn to avoid each other.

6750:

in his statement. I checked out that article and found and fixed some issues. But I don't see the relevance here, unless Petri Krohn is attempting to insinuate something that editors were warned not to do in a previous ArbCom

6165:

Therefore, given that I've already served almost 8 month of my topic ban, I ask that the committee take into consideration my former good standing, post ban good behaviour and assurances going forward (which seemed sufficient

2467:

I can't say anything else about Lightmouse without repeating what those above me have already said, so I won't. I urge the ArbCom to give Lightmouse a second chance, as they have with other parties to the date delinking case.

5841: 4866: 4823: 2990:

to a trial. So we're still a long way off. The caution is understandable but it may lead to the debate taking a lot longer. It may also lead to BAG deciding not to revive the previous permit of Lightbot to add/maintain units.

1438:

climate science and related issues. The statement made by Polargeo started a fruitful discussion on his talkpage that was resolved to my satisfaction. Discussion as to what that will ultimately entail is still ongoing. See

3398:

Normally, we then go with preferences, then with "least opposition". As a rule, though, we prefer it when things aren't that ambiguous and we'd work it out before enacting one or the other to clarify everyone's position.

2896:

first step in the rehabilitation of Lightmouse. On one hand, it is to give the community some sense of security that LM will not be allowed complete free reign to once again commit whatever 'errors' and 'negligences' he is

1612:@Steve Smith. How can I clarify these issues? I do not intend Amendment 1 to be in regards to content at all, nor to fix exact boundaries. I believe that ScienceApologist views anything that is not the consensus view as 4316:

It does appear that Miami has improved his deletion practices somewhat. His AfD nominations have all been reasonable. I am still seeing the old "That source isn't notable enough" arguments in other discussions, though.

8582: 4308:

Miami33139 and JBsupreme are reminded to observe deletion best practices when nominating articles for deletion, including the consideration of alternatives to deletion such as merging articles or curing problems through

8401: 7128:

4) Let me sum up what you wrote: you're all innocent, joined good-heartedly and suddenly became a victim to a mob mentality and hubris and crossed the line. That's not accepting fault but whitewashing and playing down.

1769:

In response to GregJackP, we'll give him a few days to make statements here. Ultimately, though, if he doesn't want to participate, we're just going to start without him, which is unlikely to be in his best interests.

1236:

ScienceApologist has misrepresented what references actually state, and has misrepresented that the articles referenced are peer-reviewed when they are not. See below, Statement by GregJackP (3) for diffs and details.

3216:

we had a new BAG application (e.g. Lightbot 6) with contributions only from editors uninvolved with date delinking. Also, did you see my ? I don't want the one year restriction to go much further into its second year.

1296:(I can forward the last one to any ArbCom member that does not have access to this journal)) stated "skeptic" and were not peer-reviewed articles. He continues to assert that they are peer-reviewed and say denialist ( 5919: 4218:

It is disappointing that such little scrutiny was given to the behavior of Miami, JBSupreme and Theserialcomma, especially with such a parade of users who suffered bad experiences at their hands submitting evidence.

4973:

for just over 12 hours. Not only is no effort being put into looking for sources, it's fairly clear that little, possibly no, effort is being put into even reading the articles themselves before joining in deletion

8771:

immediately after the case closed; users should take this opportunity to branch out. (Actually, the case isn't even closed yet, although it should be according to the time-stamps.) I have no strong views on whether

2574:"...the potential benefits of automation for this project, which is filled with quirky inconsistencies due to the inherent collaborative nature that lend themselves well to standardisation and automated maintenance" 4423:. It was later explained to me that it might have been better had I focused more on showing how they had been doing similar things to other editors. Towards that end, as I mentioned on AN/I, while I was blocked by 1595:@Krill. I agree, and I have notified him of this request, but I don't know how to get him to reply here. I would note that he has made comments on Polargeo's talk page showing that he is aware of this request. 6968:

I loathe getting in any way involved in the Knowledge arbitration process and have thus far been able to avoid any involvement – so much so, that I have not even written a word to my defense in the now infamous

4383:, perhaps he felt that totwolf's comments were too long, and didn't read them? I know it was probably meant to mock the editor, but how much blood can be squeezed from that turnip? The comments were retracted. 7973: 1971: 5915: 5907: 4437:

fairly complete and gives a pretty good overview of their interactions with other editors. Note that while that page is currently protected from editing by the general public, it can be transwikied if needed.

1640: 7206: 6801:

time. However the fact that I am requesting an early return should be viewed as a positive development as it indicates that I have acknowledged the issues of the past and have undertaken to more forward. --

6372:

where only two or three EEML members independently voted and these resulted in "No Concensus", despite the closing admin being made aware of the existance of the EEML case and its membership. Finally a 4th

4214:(IMO) Plaxicoed himself during the case itself with his brazen taunting (i.e. repeatedly telling others to "kick rocks"). Tothwolf's actions during the case were not excusable, however, Principle 3 states 890: 8678:

As I said, my ability to edit the Race (classification of humans) article is not important to me, but I would definitely consider it a loss if I were disallowed from editing any article that mentions race

4959:— Miami33139 demonstrating this attitude in action, even though some of the information removed (dealing with the authorship) is directly sourceable to page 58 of the very book cited in the AFD discussion. 4226:

Miami nominated userfied articles within Tothwolf's userspace for deletion. I have no difs to provide as the articles have been moved several times and may be deleted, but Miami should not have done this.

1703:

restriction proposed by Greg. It seems to me that 90% of Greg's complaint is based on simple disagreement with SA, and the remaining 10% consists of gray areas that seem to have been resolved in any case.

3886: 7692: 7541: 4287:

The sanction against Tothwolf, that he shall not cast aspersions without evidence, is irrelevant as the general consensus on ANI is that he has evidence and that he has a good reason to feel he is being

2709:

is a vague request (it took a while even to get specifics out of Lightmouse) for a general-purpose bot which can do anything Lightmouse fancies on a wide array of topics, some of which aren't even units.

6283:

Notwithstanding the fact that Biophys may well be risking a violation of his topic ban by commenting here, my involvement in the Russavia-Biophys case was related to Russavia's behaviour in the SPI case

6243:

have adopted other people's past battles as his own. I hope that is not the case, since from what I have seen of Igny in the past, he seems to be quite a reasonable person with which I could work with.

4462:

which as I explained on AN/I was due to the combination of the continued wikihounding and my workload. As I also mentioned on AN/I, Theserialcomma and JBsupreme also became involved in these two MFDs.

7285:

Statements here may address all the amendments, but individual statements under each proposed amendment are preferred. If there is only one proposed amendment, then no statements should be added here.

6421:"However, Martintg does not mention any actions he took that he regrets, any articles that he and his colleagues edited and now wish to repair or any editor he offended he now wishes to apologize to." 5030:

8755: 7239:

I will keep it short. Pro-nationalist editors involved in disrupting Knowledge should be topic-banned for quite some time. I doubt that lifting Marting's ban would be a net positive for the project.

5911: 5903: 2264:

project, and taught myself automation skills. I believe I have significantly benefited Knowledge. Many editors have used and continue to use my scripts; some have been inspired to create their own.

7928: 6309:

I see no battleground here. People are free to express their views or concerns on this page. I welcome this as it gives me an opportunity to respond as necessary to allay any legitimate concern. --

8719:

In light of the comments below (particularly Cool Hand Luke’s comment), the way that I’m currently interpreting the scope of my topic ban is that it covers all controversies that are specifically

2852:"Lightmouse/Jarry, please go ahead and move the request through BRFA; once it's verified and approved by BAG, we can pass the necessary motions on our end to allow you to actually implement it." 2493:

That sounds fine to me. The BRFA will be called 'Lightbot 4'. It will be a copy of the units of measure section of Lightbot 3. It will not contain any reference to dates. Thus the text will be:

8814: 8349:, I would like to request a clarification of what articles are covered. (Note, I'm not sure of the best way to handle this request, so if this is premature I apologize and request guidance.) 4831: 4827: 4678: 4368: 3096: 3092:

Lightmouse/Jarry, please go ahead and move the request through BRFA; once it's verified and approved by BAG, we can pass the necessary motions on our end to allow you to actually implement it.

1774: 7806: 6068:

In regard to my plans in the area, I would like to continue to expand the range of arts and literature topics for Wikiproject Estonia. Previously I had filled in many significant gaps such as

2796: 8739: 8712: 8383: 7862: 5899: 5770: 5595: 3491: 3464: 2725:

editors would very much like to make sweeping changes of format for which they have no consensus beyond themselves - so they want a bot to do whatever changes to units they decide they want.

815: 810: 803: 798: 793: 788: 783: 778: 773: 768: 763: 758: 753: 748: 743: 738: 733: 728: 723: 718: 711: 706: 701: 696: 691: 686: 681: 676: 671: 7612: 5778: 5603: 4090:

In finding 6 & 7, it was found that Tothwolf's repeated accusations (against many editors, including myself) were often in bad faith, against evidence to the contrary, and poor decorum.

3478: 7652: 7457:

Looking at this, I'd be willing to let this go, with the caveat that there's not much wiggle room here, and that a return to previous behaviors will mean it's near-immediate reinstatement.

5753: 5728: 5555: 5530: 5403: 5154: 4917:

There's plenty more evidence to be found. I'm not going to provide an exhaustive list because, as yet another editor has said, doing so is a large task (and I really want to get around to

3309: 3283: 3273: 1465: 1211: 666: 661: 656: 651: 646: 641: 636: 631: 626: 619: 614: 609: 604: 599: 594: 589: 584: 579: 574: 569: 564: 559: 554: 549: 544: 539: 534: 527: 522: 517: 512: 507: 502: 497: 492: 487: 482: 477: 472: 467: 462: 457: 452: 447: 442: 435: 430: 425: 420: 415: 410: 405: 400: 395: 385: 380: 375: 370: 365: 360: 355: 350: 343: 338: 333: 328: 323: 318: 313: 308: 303: 298: 293: 288: 283: 278: 273: 268: 263: 258: 251: 246: 241: 236: 231: 226: 221: 216: 211: 109: 101: 96: 84: 79: 71: 6438:"This group shared a minority political point of view and damaged the neutrality of numerous articles and continued to collaborate off-wiki even after the case was presented against them." 5425: 5210: 5201: 1585: 1408: 8788: 7769: 7450: 7278: 5791: 5616: 5363: 5338: 5186: 3254: 3210: 3087: 1930: 206: 201: 196: 191: 186: 181: 176: 171: 166: 8619:

Since Cool Hand Luke is commenting here, I’m assuming that it’s acceptable for this to be discussed here when the case isn’t closed yet, so I’m going to offer my statement about it now.

7875: 7785: 5741: 5543: 5417: 5168: 3681:

Proposed. At the conclusion of that task, the Committee will be in a much better position to evaluate whether further relaxation of the restriction is warranted, and to what extent. —

3250:

Given that we're essentially waiting for BAG in any case, I don't see any need for this to remain an open issue from our end. I've proposed a motion below to leave this in BAG's hands.

3225: 8862: 8851: 8614: 8413: 7831: 7510: 7335: 7320: 6539: 5438: 5125: 5101: 3927: 3239: 3181: 3107: 3016: 2936: 2863: 2734: 2624: 1855: 1839: 1764: 141: 8930: 8877: 7854: 7798: 7436: 6854: 5351: 5140: 4903: 4874: 4427:

I spent a considerable amount of time reviewing and documenting both my and other editors' interactions with Theserialcomma, Miami33139, and JBsupreme. That documentation can be found

3735: 3195: 3057: 2540: 1538:, which is a book written from the perspective of global warming denialism about the history of global warming. The reassessment was challenged by GregJackP's acknowledged IRL friend, 1118: 8916: 8486: 7494: 6958: 6256: 5682:) is subject to an editing restriction for six months. Should JBsupreme make any edits which are judged by an administrator to be uncivil, personal attacks, assumptions of bad faith, 5587: 5087: 3768: 3561: 3074: 2639: 1892: 126: 7644: 7603: 7466: 6763: 6741: 5762: 5564: 3725: 3168: 2690: 1810: 8480: 7818: 7688: 7621: 7537: 6170:

so why aren't mine?) and support the first motion to lift my ban entirely so that I can have clear air to make a positive contribution without the threat of vexatious litigation. --

5891: 5395: 4431:. While the sections which cover Miami33139 and JBsupreme's behaviour and interactions with other editors are far from complete, the section which covers Theserialcomma's behaviour 4300: 3712: 3326:

I hope this is the right place to post this (please relocate if not). I’m confused about the Motion and the Alternative Motion. Can someone help me understand the following issues?

2912: 2834: 2816: 2774: 2759: 1824: 1692: 845: 6239:

I am some what mystified by Igny's claims of "our personal clashes in the past", as I can't recall a single instance where we might of clashed personally, apart from the recent SPI

5372: 4853:. It, too, doesn't appear to have worked. If anything, things are worse now than they were at the time. Neither Miami33139 nor JBsupreme are following best practices, or indeed 4084:

clients) from the dozens of deletion areas I have been working in (Table-top role-playing games, Web browsers, media players, firewall software, and other miscellaneous software).

3781: 3403: 3362:

work around a 'bot task: That includes the usual dry runs in user space, the test runs okayed by BAG, and whatever minor tweaks are generally included in a single bot request. —

2890: 2428: 1906: 1389: 8901: 8692: 8541: 8418: 7674: 7363: 7254: 6810: 4484: 4481: 4467: 4465: 4320: 4197: 3698: 3552: 3145: 3131: 2677: 1672: 1476: 1268:

position, in spite of earlier sanctions and despite having been cautioned to: "to respect all policies and guidelines," he has attempted to insert negative information into a BLP.

7589: 7525: 4526: 3154: 8536: 8377: 7566: 7415: 7391: 6337: 6318: 6304: 6135:, an 18th Century figure of Imperial Russia (thus clearly not a former Soviet republic and outside the scope of his ban), that didn't stop his opponents from claiming otherwise 4640:

where they did not edit previously (as they've already been doing) in order to block or restrict my edits while claiming they were already editing articles in those topic areas.

4521: 3392: 2413: 1882: 1795: 5849: 4235:

In that same dif, he said "Paranoid ramblings of Tothwolf", "Other than his walled garden, I ain't following his editing or hounding him", "enough paranoia", "paranoid ranting"

3759: 3538: 2559: 1915: 7165: 6487:"Surely editors like this drive away most of the editors we want to attract, people who have the ability to write articles and those who remain are tied up in silly disputes." 6234: 6229: 4681:, I was advised not to participate in the MFDs that Miami33139 initiated, which seemed sensible to me given the past results of interacting with these three individuals. With 3923: 3845: 3376: 3366: 2603: 2487: 2477: 1516:

Recommend dismissal on the basis of a bad faith filing and a sanctioning of the editor who brought this malformed request for amendment to this page since Knowledge is not a

8609: 6007: 2372: 8652: 8643: 7908: 5206:

Oops :-) I've added in the bits I completely missed since they were meant as motions, but I'm certainly open to discussing any of the motions and changing them as needed.

4818:

Whilst Tothwolf has apparently resisted temptation to blow xyr top this time around, xe still hasn't done xyrself any favours. Actually rolling up xyr sleeves and editing

3351: 2462: 2399: 8444: 8309: 7751: 7272: 6977:

Martin's actions on the Internet, on and off Knowledge, show that his only interest on the web is promoting a fringe nationalistic agenda, or in Knowledge terms, he is a

6705: 4256:, Miami has declined to explain why he mocked Tothwolf with "tl;dr". He justified the taunting posts on the talk pages of JBSurpreme and Theserialcomma based on Tothwolf 2446: 2032: 7730: 4937: 2964: 1080: 7229: 7200: 5018: 4775: 4653: 4609: 2042: 1709: 1650: 6359: 3665: 2942: 7264:

I oppose any loosening of sanctions on Martintg, unless there is a specific restriction against pursuing past disputes stemming from the EEML Case. Per my explanation

7034:

1) of course the previous relaxation had caused no problem. Nor did Radeksz's or Piotrus's. In all cases they were used as basis to demand more like a slippery slope.

6938: 6179: 4392: 4311:

Although I am admittedly ignorant of all things IRC and not a good judge of reliability of sources and thus notability of software, I can see bad deletion discussions.

3919: 3911: 1629: 1608: 1192: 1150: 123: 25: 7427:

Of course, if the remedy is lifted or narrowed, there would be a strong expectation that the problematic behaviors addressed in the original decision must not recur.

6832: 6624: 6605: 6528: 5003: 3543:

Normally, I'd be a second choice here, but I think the other one is better, and both on the verge of passing, so, indicating my preference for the other one as such.

1255: 8389: 8358: 4925: 4457: 3828: 2799:

and was executed in a coup d'etat. The issue here is the technical merits of the bot. Calling others “children of Robespierre” was designed to provoke. I know that;

1897:

I think I am going to decline these amendments, that no action needs to be taken at this time, and agree with Carcharoth about the suggestion on how this should go.

1748: 1523: 1439: 4988:

To that end, I suggest that it is in Tothwolf's best interests to concentrate upon article writing, rather than this, for a time. I suggest, for starters, getting

4620:

I do wish these editors would stop with the personal attacks though. I don't really care to be called "paranoid", "delusional", etc and the semi-constant claims of

4530:

which should also be taken into account. The wikihounding of Beyond My Ken by Miami33139 can be easily seen in the edit histories of the articles from these links:

6158: 4865:

I can understand why the assumption of good faith has gone out of the window for that editor that I mentioned. It's fairly clear from the actions by JBsupreme at

4718: 4516:

Upon Miami33139's return, not only did he resume his wikihounding of myself, but also other editors. An extreme case can be seen in Miami33139's interactions with

4469: 4463: 3685: 7940: 7521:

return to the topic area, and I would support a more limited relaxation at this time. I am not, however, very favorable to removing it entirely at this time. —

6646: 5023: 4766:) to make it easier for the anonymous editor to update the version information, which previously resulted in nearly daily edits to the large comparison tables. -- 1563: 1153: 8521:

not only to push the same POV as they were pushing at R&I, but also to change a WP article so that it would support the edits they were making at R&I.

6917: 6901: 6879: 6524:

I don't understand what TFD seeks to gain in continuing to flog the EEML dead horse, even insinuating there is some kind of far-right anti-Semitic agenda at play

4152: 1590: 5825: 3455: 6108:. Despite my continuing studies I expect to devote a little more of my time than in the past few months, as I do enjoy contributing my free time to Knowledge. 5720: 5701: 5522: 5503: 4797: 4693: 4162: 2244:

except that during the three-month trial he is permitted to use the account 'Lightbot' to edit only in the field of units of measure, under the supervision of

1222: 6367:

which resulted in "No Concensus". I did canvas that on the EEML and that was wrong, no bones about it. After the EEML ArbCom case began there a two more AfDs

5659: 5650: 4533: 2565:

I would like to pick up on one point made above, add a general point about bots such as this, and point out one illuminating exchange that occurred elsewhere.

5330: 5306: 4352: 3915: 3907: 2314: 1938: 853: 8600:

Finally I would like to seek clarification on the Meatpuppetry. Would it be necessary to file a completely new request or can this be handled in this case.

6838: 6785: 4535: 4531: 3594: 1443: 7240: 5686:, JBsupreme may be blocked for the duration specified in the enforcement ruling below." The six months is reset to start from the day this motion passes. 4550: 2653: 2607: 1453:

All areas of dispute resolution have not been exhausted before bringing this here, and there is no indication that arbcom should get involved at this time.

8775:

is included; I think it is technically outside of the topic ban, but I would caution the user. Controversial editing in this area may lead to AE or other

8745: 8627:

think it should be necessary for me to promise to never edit this article for the duration of my topic ban. But apparently, my statement that I would be

7307: 5052: 3039: 2765:

a general purpose bot to impose his whims shows that nothing has changed, and the children of Robespierre still wish to improve us, whatever we may want.

2168: 7118: 6934: 6870:

amendment Martin rushed with several BLP fixes for EE related persons as if it was simply done to satisfy the previous amendment and justify a new one. (

2803:

know that. Moreover, both “bot to impose his whims” and “ still wish to improve us” are failures to assume good faith and are arguably personal attacks.

2433:

I have read the statements by Users Greg L, Ohconfucius, and Colonies Chris. I would like to say that my own experience strongly supports what they say.

6278: 5145:

I don't think Tothwolf is the wrongdoer here. I don't know whether this requires an amendment, but it does appear to be hounding to me. Move on, Miami.

7135: 7133: 6837:

I'll keep it short. I've never ever come across Artem Karimov in the past, never interacted with him or even worked on a common set of articles beyond

3853: 3514: 1980: 899: 4554: 6389: 4945: 4819: 4756: 4674: 4546: 4472: 4455: 3903: 3608: 3415: 7090:

Next, he violated the spirit of the Russavia interaction ban and the EE topic ban with a comment about Russavia that sounded positive but had teeth

6196: 4759: 4583: 4061: 2744:

negative feedback. The hard-working and dedicated efforts of the "fanclub" should be commended as the results are a simpler and easy-to-use WP for

1754: 1547: 4558: 2310: 1470: 1340: 1249: 1074: 7109: 7106: 7103: 6688:. Okay, should I be getting scared now that this individual appears to be stalking me outside Knowledge gathering non-existent "evidence" of this 4896: 4892: 4881: 8670:, and I don’t think there’s any evidence that I’ve caused disruption outside of this category. For example, I’ve only made a single edit to the 8397: 8329: 7149: 7076: 7054: 4618:

I'm really not sure what else I can add here in addition to what I brought up on AN/I but I'll see what I can come up with in the next day or so.

4342:

It does not appear that JBSupreme has improved his deletion practices any more than he improved his civility. I am particularly concerned about

2975: 2971: 2952: 2706: 2249: 2177: 1502: 1416: 1197: 8347: 6017:

This is a request to amend EEML Remedy 7 to end the topic ban that applies to Martintg and allow him to edit articles related to Eastern Europe.

2702: 2591: 1677: 6930: 6150: 5408:

We can try this regime and see if it helps. If not, we may need to reopen the original case for a more thorough review of recent developments.

4762:) be considered both disruptive and wikihounding? I created this LSR template on July 9, 2009 (using the same method we use in the majority of 4326: 7531: 4692:. As far as I could see, every single fact there can be cited, with the reference that Miami33139 also removed easy to locate via archive.org 3321: 8194: 7100: 4183: 4081: 2162: 1030: 148: 8547: 7760:. My apologies for the cross-posting, but I'd responded to both Martintg and Jehochman there before seeing that they'd posted here as well. 7115: 4449: 3136:

Concur with Kirill; I'd like to see the BAG reviews before implementation but, if all looks good, then it will be a straightforward matter.

2995:

Consequently, this is a formal request to Arbcom. Please allow progress by amending the remedy that also applies to the Lightmouse account:

6525: 4885: 4850: 4332: 4306:

Further comments in regards to Miami33139 and JBSupreme's participation in deletion discussions. Finding 3 of the arbitration case states

4257: 4230: 3895: 2715: 2597: 2594: 6385: 1655: 1147: 1135: 8589:

article. In summary, I have always taken for granted that this current controversy is spread over a number of related articles including

6943: 6793: 6667: 6661: 4072:

This recently expired. It should be extended for one year without opening a new case. It should be amended to include making accusations.

7087: 5641:

The reason for the motion is understandable, but I think (1) might well be sufficient and my preference would be to try it alone first.

5221: 2384:

Other editors are free to comment on this amendment as necessary. Comments here should be directed only at the above proposed amendment.

8824: 8332: 8050: 7682: 6596:

I just want to use my time to contribute something useful to the topics I've indicated above, all I ask is that I be treated fairly. --

6381: 6128:

This isn't an idle concern, recently Biophys was topic banned from editing articles about the Soviet Union and former Soviet Republics

4928:— I mentioned snowball keep decisions where single editors stand out, earlier. Here's one such. The editor standing out is JBsupreme. 4539: 4202: 8750: 7121: 7091: 7084: 7037:

2) you never had a previously un-problematic record. Since the start of your Martintg account you revealed what Arbcom referred to as

7000:

For several years now Martin has been waging a politically motivated attack campaign against me, that is my Knowledge account and the

6287: 6145: 6138: 6125:

EEML case). Not gaming by me, but by my opponents who would seek to exploit the ambiguity present to game and shop for admin action.

4815:

This leaves us with Miami33139, Tothwolf, JBsupreme, and all of the people who have, variously, interacted with them over the months.

2547: 8242: 7234: 6129: 4753: 2825:

good faith. It was a bad idea to give the Jacobins a guillotine; I'm not sure giving these doctrinaires a bot is a good idea either.

2377: 1543: 1531: 8563: 8388:

I thank aprock for his notification of this clarification request. Yes, I too am interested in the scope of the topic ban under the

6374: 2925: 2660:

I had intended that to be a bit of humor to defuse the seriousness of the matter. Seeing Carcharoth’s reaction, I clearly failed at

6463:

Again this is a nonsense blanket statement. I've always striven for neutrality, as you can see from the many articles I've created.

1272: 8331:. When the tool server stats are consulted, the implication is that "race" and "intelligence" articles are being considered here 6997:. So far he has shown no interest in editing outside his chosen battlefield, for example in his field of professional expertise. 4966: 4594: 4574: 4101:

him. Requesting MfD requests of deleted articles kept in userspace is simple followup of deletions made six months or a year ago.

8555: 7290: 6963: 6708:. I don't think it appropriate to re-litigate something from 2008. In any case I've not edited that article since September 2008. 6013: 5035: 3968: 2073: 1485:, pseudoscience, climate change, or other areas involving minority scientific views, including related BLPs, interpreted broadly. 1139: 8508: 2978:) but I'm not sure when that will end. As far as Arbcom is concerned, the connection with BAG and Lightbot is only relevant to: 1697: 1634: 8188: 6590: 6119: 5173:

I think we have two issues to address here - Miami33139 and JBSupreme's behavior towards Tothwolf and in deletion discussions.

4965:— Another piece of evidence that putting deletion and content policies into action correctly is at a new low. At the point of 4962: 2258: 2232:

except that he is permitted to do so in the field of ‘units of measure’ on a three-month trial basis, under the supervision of

2124: 1024: 981: 6798: 6571: 6063: 6042: 4403: 4093:

Evidence in the Arbcom case showed Tothwolf has a history of "crying wolf" (making accusations) when people edit in his area.

1372:

Part mentioning me struck. I was only seeking clarification on the issue; I didn't get a chance to look into the issue fully.

8146: 7259: 6561: 5964: 4843: 4490: 4460: 4017: 3022: 1348: 1344: 1337: 1334: 1331: 1328: 1325: 1322: 1319: 1316: 4222:

Furthermore, there appears to be much consensus among editors that Miami was attempting to deliberately provoke Tothwolf.

3602: 1559: 1313: 1306: 1303: 1300: 8315: 8098: 7954: