Wikipedia:Requests for arbitration/Betacommand/Evidence

From Wikipedia, the free encyclopedia

Please make a section for your evidence and add evidence only in your own section. Please limit your evidence to a maximum 1000 words and 100 diffs; a shorter, concise presentation is more likely to be effective. Please focus on the issues raised in the complaint and on diffs which illustrate behavior which relates to the issues. If you disagree with some evidence you see here, please cite the evidence in your own section and provide counter-evidence, or an explanation of why the evidence is misleading. Do not edit within the evidence section of any other user.

Anyone, whether directly involved or not, may add evidence to this page. Please make a header for your evidence and sign your comments with your name.

When placing evidence here, please be considerate of the arbitrators and be concise. Long, rambling, or stream-of-conciousness rants are not helpful.

As such, it is extremely important that you use the prescribed format. Submitted evidence should include a link to the actual page diff; links to the page itself are not sufficient. For example, to cite the edit by Mennonot to the article Anomalous phenomenon adding a link to Hundredth Monkey use this form: [http://en.wikipedia.org/w/index.php?title=Anomalous_phenomenon&diff=5587219&oldid=5584644] [1].

This page is not for general discussion - for that, see talk page.

Be aware that arbitrators may at times rework this page to try to make it more coherent. If you are a participant in the case or a third party, please don't try to refactor the page, let the arbitrators do it. If you object to evidence which is inserted by other participants or third parties please cite the evidence and voice your objections within your own section of the page. It is especially important to not remove evidence presented by others. If something is put in the wrong place, please leave it for the arbitrators to move.

Arbitrators may analyze evidence and other assertions at /Workshop. /Workshop provides for comment by parties and others as well as arbitrators. After arriving at proposed principles, findings of fact or remedies, arbitrators vote at /Proposed decision. Only arbitrators may edit /Proposed decision.

Contents 1 Evidence presented by Ryanpostlethwaite 1.1 Evidence of inappropriate username blocks 1.2 The response of Chrislk02 to betacommands username blocks 2 Evidence presented by Betacommand 2.1 Usernameblocks 3 Evidence presented by Chrislk02 3.1 Deletion Bot 3.1.1 Username Blocks - Instantaneous 3.1.2 Username blocks - Community involvement 3.2 Rapid Blocking 3.3 Bot external link deletions 4 Evidence presented by Chick Bowen 4.1 Betacommand's rate of deletion is not unique 5 Evidence presented by Friday 5.1 Betacommand not very responsive to feedback and questions 6 Evidence presented by {your user name} 6.1 {Write your assertion here} 6.2 {Write your assertion here}

[edit] Evidence presented by Ryanpostlethwaite

[edit] Evidence of inappropriate username blocks

The following usernames have been blocked by betacommand which do not infringe on WP:U, after community input, they have all been reversed

1. Block log of User:Is he back? - Archive discussion on name
2. Block log of User:Alrite Darling U Gd? - Archive discussion on name
3. block log of User:Dani casale* - Archive discussion on name
4. block log of User:Fatterwhales - Archive discussion on name
5. block log of User:Chrisgodwin - Archive discussion on name
6. block log of User:*gvan !!! - Archive discussion on name
7. block log of User:Young&26sexy - Archive discussion on name
8. block log of User:Welala!!! - Archive discussion on name
9. block log of User:Snoopjon91 - Archive discussion on name
10. block log of User:Karenlister1 - Archive discussion on name
11. block log of User:I Love my Cat!!! - Archive discussion on name
12. block log of User:EMO*FOREVER* - Archive discussion on name
13. block log of User:Coolperson123456789 - Archive discussion on name
14. block log of User:Clevercutie;) - Archive discussion on name
15. block log of User:B;uedog - Archive discussion on name
16. block log of User:IHateItAroundHere - Archive discussion on name

Ryanpostlethwaite contribs/talk 08:59, 30 March 2007 (UTC)

[edit] The response of Chrislk02 to betacommands username blocks

When concerns were highlighted of more blocking issues with Betacommand, Chrislk02 (talk • contribs) looked further into these and uncovered futher issues with Betacommands username blocks which were not highlighted in Beta's Rfc. Upon seeing these, instead of simply unblocking these usernames, he requested community input by taking them to WP:RFCN [2], [3], [4], [5], [6], [7], [8], [9], [10] (most of which have now been unblocked). Chrislk02 then went ahead to alert the wider community of these issues by requesting comment on this issue at WP:AN/I. At no time did chris suggest that Betacommand should be blocked for these issues, and he even went ahead soon after to clarify that the username issues were from last month and that Betacommand should have been unblocked, he was simply requesting further comments on the issue before he undid another administrators actions. Chrislk02 did at no point misuse his tools, and neither did he suggest that anyone else should misuse theirs, he acted diligently throughout the whole process and thought of the whole community in his actions. An invalid block should not remain on an account, and this is the reason that Chrislk02 acted as he did. Ryanpostlethwaite contribs/talk 01:37, 30 March 2007 (UTC)

[edit] Evidence presented by Betacommand

[edit] Usernameblocks

As I stated in the past a few of my 1,100 username blocks were inappropriate. Most were backed with 110% proof. one perfect example that chris mentions above User:Fatterwhales is proof. It may not be obvious, but check the user creation log. 13:35, February 13, 2007 User:Fatwhales created. 12:32, February 19, 2007 blocked by Messedrocker for vandalism. 11 minutes later 12:43, February 19, 2007 User:Fatterwhales created. within a minute I block because I see it on the IRC newuser feed. a few hours later cant sleep clown will eat me unblocks. Special:Contributions/Fatterwhales 13:03, March 22, 2007 user starts a vandalism spree. 17:09, March 22, 2007 WP:SSP opened. This is just one case that sticks out of my memory. Given the issues that were raised before I have almost completely stopped username blocks. Betacommand ^{(talk • contribs • Bot)} 01:45, 30 March 2007 (UTC)

See also [11] for a few reasons that users were blocked. Betacommand ^{(talk • contribs • Bot)} 19:47, 30 March 2007 (UTC)

[edit] Evidence presented by Chrislk02

My major concern is the inappropriate use of scripts/bot like tools, especially being an administrator. I am going to show evidence of several past instances of possible abuse. These past occurrences, probably dealt with at the time, are being used to show a recurring pattern of inappropriate behavior.

[edit] Deletion Bot

The first occurrence of inappropriate use of tools starting in November of 2006. Below is a list of deletion logs that I believe show an inappropriate use of a deletion bot or some other inappropriate script, starting with the earliest.

• 27 November 17:52 - 18:01 approx 100 images deleted
• 27 November 18:55 - 19:16 : 500 images deleted
• 27 November 18:01 - 18:55 : 500 images deleted
• 27 November 19:16 - 19:54 : approx 400 images deleted

shows many deletions over a very short amount of time. Particularly notice the deletions that occurred at 19:42, during that single minute over 34 images were deleted. While I believe it is possible to delete many images per minute, I find it hard to believe that the images were manually deleted. In fact, another administrator, Dragons flight blocked Betacommand for 1 week with a block summary stating, "(Using an unauthorized deletion bot)." Several hours later, Betacommand was unblocked by Administrator Geni with an unblock summary stating, "(I don't think he is going to do that again)." This I believe is the first in a series of, while possibly good faith, very poor decisions made by Betacommand. I think it is important to notice that these actions were done using administrative tools (delete function).

[edit] Username Blocks - Instantaneous

After this, Betacommand slows down a little bit from what I can see and does not do too much that is controversially inappropriate. However, In February of 2007, Betacommand began again. Most notably with the blocking of new users whose usernames were inappropriate. It is my belief that he used some sort of reporting script and blocking tool, that worked either autonomously or semi autonomously that blocked users with inappropriate substrings in there name. While many of the username blocks were 100% appropriate, there were many good faith names that did not violate policy or community consensus at the time that Betacommand took it upon himself to block. Below are some excerpts from block log of username blocks that seem to not violate policy, over an extended period of time

• 03:48, 11 January 2007 Betacommand (Talk | contribs | block) blocked "Wowwoweeewow (contribs)" with an expiry time of indefinite (Please read our our username policy and choose another name {{usernameblocked}}) (Unblock) [12]
• 0:37, 10 January 2007 Betacommand (Talk | contribs | block) blocked "Blabber mouth katie (contribs)" with an expiry time of indefinite (Please read our our username policy and choose another name {{usernameblocked}}) (Unblock) [13]
• 01:03, 4 January 2007 Betacommand (Talk | contribs | block) blocked "Charbroil666 (contribs)" with an expiry time of indefinite (Please read our our username policy and choose another name {{usernameblocked}}) (Unblock) [14] Now, I am unaware of any consensus to instantly disallow usernames with the numbers 666 in it. If there was a policy against this, I have no problem rescinding this part of the complaint. However, there is a pattern of any names containing 666 being blocked. Here are several others that were also blocked. 666possum, Metal Warrior666, Rageaddict666. This is just the tip of the iceberg with this issue.

Now, the username blocks in and of themself are only part of the issue. What I find disconcerting is the fact that usernames blocks like the block of User:666possum, an account that was registered 06:30, 3 January 2007 and subsequently insantly blocked at the exact same time. Given no option to change their name, just instantly blocked. There are many other occurrences of this riddled throughout his block log. It is my belief that the instant blocking names such as the ones listed above hurts Wikipedia more than any inappropriate username that sits around for an extra hour and further shows evidence of misuse of a script or bot that uses administrative tools.

[edit] Username blocks - Community involvement

• On 13:19, 18 February 2007, User HighinBC expresses concerns over a recent streak of username blocks that were overturned at WP:RFCN on Betacommand's user talk page. This thread can be found here.
• On 02:16, 20 February 2007, User BigDT expresses concern over the fact the Betacommand deleted a userspage, after usernameblocking them, and covering up there unblock request through page deletion. This thread can be found here
• On 19:50, 22 February 2007, Betacommand starts autoreporting usernames to WP:RFCN in an essence flooding it with marginal names, some with are obvious blocks and nobody complained about, which could have been reported to WP:AIV or other places. This actions further supports my suspicions that Betacommand was using a script or some sort of bot that was blocking innapropriate usernames. here are his contributions during the period of auto reporting Note, he makes it very obvious that it is an autoreport from the edit summaries.
• On 21:45, 22 February 2007, Betacommand is blocked by User:Pschemp with a block summary stating, " (refuses to stop bot reporting with this account)". here is some dialogue involving other administrators in regards to this block, and inappropriate actions. I think it is important that several people believed Betacommand to be violating WP:POINT due to the recent scrutiny of his blocking actions. In this situation, he threw every blatantly inappropriate username to the community, clogging up both WP:AIV and WP:RFCN with blatantly obvious names. Names that nobody complained about his blocks of.
• On 21:57, 22 February 2007, User:Wangi unblocks betacommand with an unblock summary stating, "(rm inappropriate block)".
• On 15:21, 28 February 2007, after complaints of flooding WP:RFCN with names that should be obviously blocked, betacommand starts flooding WP:AIV with usernames. contributions from this time period. I think it is of special interest to note this edit where he floods AIV with over 20 very obvious block names. Names that NOBODY would question blocking of.

[edit] Rapid Blocking

While it has been brought to my attention that it is possible to perform such rapid blocks, I think that this excerpt from the block log is relevant, especially in allegations of using scripts or bots inappropriately.

• 23 Feb 2007 me expressing concerns in regards to the probably use of a blocking bot by beta command.
• 8 Mar 2007 - A series of 9 blocks in 1 minute, very improbably all were done manual with proper review.

14:43, 8 March 2007 Betacommand (Talk | contribs | block) blocked "59.167.13.50 (contribs)" (anon. only, account creation blocked) with an expiry time of 1 week (spamming) 
14:43, 8 March 2007 Betacommand (Talk | contribs | block) blocked "202.58.63.200 (contribs)" (anon. only, account creation blocked) with an expiry time of 1 week (spamming)
14:43, 8 March 2007 Betacommand (Talk | contribs | block) blocked "208.109.49.47 (contribs)" (anon. only, account creation blocked) with an expiry time of 1 week (spamming) 
14:43, 8 March 2007 Betacommand (Talk | contribs | block) blocked "59.167.243.12 (contribs)" (anon. only, account creation blocked) with an expiry time of 1 week (spamming) 
14:43, 8 March 2007 Betacommand (Talk | contribs | block) blocked "121.44.236.252 (contribs)" (anon. only, account creation blocked) with an expiry time of 1 week (spamming) 
14:43, 8 March 2007 Betacommand (Talk | contribs | block) blocked "210.11.241.21 (contribs)" (anon. only, account creation blocked) with an expiry time of 1 week (spamming) 
14:43, 8 March 2007 Betacommand (Talk | contribs | block) blocked "Tuddy (contribs)" (anon. only, account creation blocked) with an expiry time of indefinite (spamming) 
14:43, 8 March 2007 Betacommand (Talk | contribs | block) blocked "Voyages (contribs)" (anon. only, account creation blocked) with an expiry time of indefinite (spamming) 
14:43, 8 March 2007 Betacommand (Talk | contribs | block) blocked "Svm-en (contribs)" (anon. only, account creation blocked) with an expiry time of indefinite (spamming)

[edit] Bot external link deletions

• 21 Mar 2007 00:01 - 17:34 [15], [16], [17], [18], [19], [20], [21] a series of 3,000 external link removals at bot like speeds with many per hour.
• 21 Mar 2007 - ANI posting regarding link deletion at bot like speeds.
• 23 Mar 2007 13:16 - 17:37 -Fairly rapid removal of about 200 (appprox) external links in a similar manner as objected to on the previous ANI post. This action stopped when he was warned of a block again.
• 23 Mar 2007 - ANI posting regarding external link removal.
• 26 Mar 2007 - most recent ANI posting regarding inappropriate block of a user editing an article he was engaged in.

[edit] Evidence presented by Chick Bowen

[edit] Betacommand's rate of deletion is not unique

I would like to call the Committee's attention to this thread at the Admin noticeboard, in which Dragons flight presented evidence suggesting that some of our faster admins were using some level of automation to aid deletion (though not all of those in his chart, as the discussion makes clear). Betacommand's fastest deletion rate, 1.9 seconds per deletion over 13 minutes, is unusual but not unheard of. The consensus from that thread, as I understood it, was neither to allow nor excoriate the use of such aids, but to stress the necessity of proper care being taken. Please read the evidence above relating to Betacommand's rate of deletion in the context of this larger debate about the role of automation in deletion work in general. If deletion rate is to be used as grounds for desysopping, then a fair number of admins are at risk; I would urge the committee to focus on the more recent evidence (particularly that not already addressed by the bot approvals group) in its deliberations. Chick Bowen 18:29, 30 March 2007 (UTC)

[edit] Evidence presented by Friday

[edit] Betacommand not very responsive to feedback and questions

I have found Betacommand to be not very responsive to queries about his activities. When he does respond, he sometimes does so in a way that doesn't seem sensible or fails to address the issue. Examples include this thread about his blocking behavior. Here more recently I asked him if he rolled back on purpose. His response completely failed to address the question. Here I asked if he was using some automated tool and not checking what it was really doing. He replied by talking about a software issue, not answering the question. Here I questioned his reasons for some deletions. He replied by saying they were poorly written, but this was untrue and did not answer the question. I do not remotely suspect he means anything but the best, but I do not trust his judgment to use the admin tools. It's important for all editors, and particularly admins to be responsive to concerns about their activities. Friday (talk) 19:35, 30 March 2007 (UTC)

[edit] Evidence presented by {your user name}

[edit] {Write your assertion here}

Place argument and diffs which support your assertion; for example, your first assertion might be "So-and-so engages in edit warring", which should be the title of this section. Here you would show specific edits to specific articles which show So-and-so engaging in edit warring.

[edit] {Write your assertion here}

Place argument and diffs which support the second assertion; for example, your second assertion might be "So-and-so makes personal attacks", which should be the title of this section. Here you would show specific edits where So-and-so made personal attacks.