Wikipedia

Wikipedia:Requests for arbitration/Betacommand

< Wikipedia:Requests for arbitration

Case Opened on 23:59, 29 March 2007 (UTC)

Case Closed on 23:33, 3 May 2007 (UTC)

Please do not edit this page directly unless you wish to become a participant in this case. (All participants are subject to Arbitration Committee decisions, and the ArbCom will consider each participant's role in the dispute.) Comments are very welcome on the Talk page, and will be read, in full. Evidence, no matter who can provide it, is very welcome at /Evidence. Evidence is more useful than comments.

Arbitrators, the parties, and other editors may suggest proposed principles, findings, and remedies at /Workshop. That page may also be used for general comments on the evidence. Arbitrators will then vote on a final decision in the case at /Proposed decision.

Once the case is closed, editors may add to the #Log of blocks and bans as needed, but closed cases should not be edited otherwise. Please raise any questions at Wikipedia:Requests for arbitration#Requests for clarification.

Involved parties

edit

Requests for comment

edit

Statement by AnonEMouse

edit

Betacommand (talk · contribs) is an administrator and expert coder of bots and tools. Unfortunately, he has a long history of controversial use of both bots and admin tools (the RFC above is related). I was only made aware of him in the last week, and in that time he has shown up three times on the WP:ANI board; they're enough for me to bring this RFAR.

  1. Wikipedia:Administrators' noticeboard/IncidentArchive218#Emergency: Betacommand deletion at bot speeds - please review impending block
  2. Wikipedia:Administrators' noticeboard/IncidentArchive218#Betacommand AGAIN - this time.2C ext. link removals
  3. Wikipedia:Administrators' noticeboard/IncidentArchive220#Betacommand questionable blocking

The first incident, on March 21, had Betacommand apparently using a computerized tool from his own account to remove links to usenet groups across hundreds of articles, without discussion. His edit speeds have been estimated at 30 edits per minute. Many editors quickly showed up at his user talk page to complain; his responses were minimal, curt, or entirely lacking, and the deletion went on at high speeds. (See User talk:Betacommand/20070301#Removal of Usenet posts and the following 3 sections.) He stopped after I posted on his talk page emphasizing I was an admin and this was an official warning; I was ready to block him if he didn't stop to discuss, and made an "emergency" post on AN/I asking for review of the impending block. In the face of extensive later criticism, mostly on AN/I, he rolled back most or all of his edits. I was happy with that, thought that would be the end of it, and even thanked him for doing so the next day I edited.[1] As part of the fallout, he apparently lost Bot approval rights: Wikipedia talk:Bots/Approvals group#Betacommand; Wikipedia:Bureaucrats' noticeboard#Another bot deflagging

The second incident, on March 23, he again used a computer assisted tool, no longer at 30, but still at 5 to 15 edits per minute, removing other external links across unrelated articles, including to the official site of USAID, a US government agency, apparently based on a third party article about spam links in Google. He claimed on AN/I he was doing this without the aid of a bot. Given two similar incidents in three days, and the fact that removal of Bot rights didn't seem to help, several people discussed a community ban. Instead, I made a proposal that he roll back his controversial edits, and promise not to go on any mass deletion sprees without discussion beforehand, or approval by another experienced editor. He rolled back his edits, but did not agree to the last condition. He also did not apologize, accept that his actions were wrong, or promise not to repeat them, stating merely that he was debugging his tool.

The third incident is today, March 26. He has apparently blocked a user for participation in a content dispute. After mass criticism on AN/I by many admins, he unblocked the user, without admitting that he was wrong. That same page, today, uncovered issues with apparently automated blocking users for username violations. User:Mel Etitis apparently blocked Betacommand for this, or a combination of these actions.

AN/I consensus seems to be that these recurring issues demand further action, and that Betacommand has lost the community's trust as an admin. If the community noticeboard could take intermediate steps besides outright ban, I'd take it there. As far as I understand, it can't. Apparently stewards won't desysop someone without an arbcom ruling either. Betacommand is a well-meaning user, and a skilled bot developer, who has the community effect of a porcupine in a nudist colony. Hopefully some kind of intermediate action besides outright ban will be enough to de-quill him. --AnonEMouse (squeak) 18:59, 26 March 2007 (UTC)[reply]

Response to ChrisO

edit

I'm actually not that interested in considering the incidents separately; separately they're each, not good, but everyone makes mistakes. I'm concerned with a long history of disregard for other users (see above and below). I'm concerned with 3 major (look at the people involved in each!) AN/I incidents in 6 days, without a single "I understand", "I was wrong", or "I won't do it again". I'm not interested in punishing him for what he did, that can be fixed, or has been fixed. I'm concerned with preventing the next one. --AnonEMouse (squeak) 20:56, 26 March 2007 (UTC)[reply]

Response to Mackensen

edit

By clerk permission! :-) As my response to ChrisO above, and as Chrislk02's clarification why arbitration is still necessary, and Comment by Chacor below. The individual issues are all or mostly settled, the problem is that they just keep on coming. I'm not even talking about dredging up stuff from November or December. The 3 incidents from my statement were in the last 6 consecutive days. From Bishonen's statement: Wikipedia:Administrators'_noticeboard/IncidentArchive208#Trigger-happy_blocking_by_Betacommand is another big todo, Feb 27-28, less than a month before. Chris's list of incidents below fills in the spaces between that. :-(. I'm not asking for a ban, but we need something, maybe probation, maybe a formal reprimand, maybe a temporary desysop, but something with teeth. Each time people assume he's learned and it won't happen again, but the issues just keep coming. Like a bull in a china shop, every time he turns there's a loud crash. --AnonEMouse (squeak) 19:20, 27 March 2007 (UTC)[reply]

Statement by Mel Etitis

edit

[With regard to Tony Sidaway's (initially) only comment on the issue.] Ah, history slipping in here a little. I suggest that you look at the facts of the matter, including my message at WP:AN/I in which I explained the mistake behind my block, and asked if people thought that I should unblock. --Mel Etitis (Talk) 19:46, 26 March 2007 (UTC)[reply]

With regard to this RfArb, I can only add that, like many editors, I've watched a series of problems arise because of Betacommand's inappropriate use of bots and now blocks, and it seems to a large proportion of the many admins and other editors commenting on him at WP:AN/I that it's inappropriate that he should continue to be trusted with admin tools. It may be that he simply needs more experience before being allowed them, it may be that he's temperamentally unsuited — I don't know. --Mel Etitis (Talk) 20:16, 26 March 2007 (UTC)[reply]

Statement by Chrislk02

edit

Here is a recent timeline of suspicious, controversial and possible innapropriate actions by betacommand many that I have been involved with, witnessed and or confronted betacommand about.

  • 27 Nov 2006 - [2], and following logs. Started deleting images upwards of 20 per minute for a time period deleting updwards of 500 images over a short period of time.
  • 28 Nov 2006 - betacommand is blocked and then unblocked for running an unauthorized deletion bot. The unblock comment states, "(I don't think he is going to do that again) "
  • 18 Feb 2007 - [3] HighinBC expresses concerns of Betacommands bolcking habits.
  • 20 Feb 2007 - [4] an administror expresses concerns of betacommands blocking and denying of unblock requests in relation to a usernameblock
  • 22 Feb 2007 - [5] in his contribs where he pretty much started auto reporting all usernames that had been blocked before to WP:RFCN in what was believed to be to make a point. This was mentioned at WP:ANI and on his talk page
  • 22 Feb 2007 - comment I left regarding bad usernames. Situation where betacommand made a point, only sees things in black and white.
  • 22 Feb 2007 - [6] a thread where I expressed my concerns over blocking habits, point violations and other concerns I have had.
  • 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 improabbly 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)
  • 21 Mar 2007 00:01 - 17:34 [7], [8], [9], [10], [11], [12], [13] a series of 3,000 external link removals at bot like speeds with many more per hour than humanly possible at times.
  • 21 Mar 2007 - ANI posting regarding link deletion at bot like speeds.
  • 23 Mar 2007 13:16 - 17:37 -Fairly rapid remval of abou 200 (appprox) external links in a similar manner as objeted 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 207 - most recent ANI posting regarding innapropriate block of a user editing an article he was engaged in.

I think all of these actions, plus several other pas actions which I have not summarized here (his block log includes 3 blocks for unatuirhorized bots). There are also several other username blocks that many users have expressed concern over. usernames such as user:Chrisgodwin was blocked. It was later unblocked with a WP:RFCN, however it opens the question what led him to block. Having God in the name will often lead to a block but godwin is an appropriate name. There are many other blocks that were questionable. After every occasion, betacommand has generally re-started the questionable behavior until threatneed with a block again. I have asked him nicley what is going on before and got a nice answer however the actions did not stop. I belive that any administrator willing to block without personal review or just block a name because it contains the substring of a possible offensive term is more of a detrmiment to this project than any innapropriate name that spends an extra 20 minutes around because it is blocked manually. 1 instance would be ok, 2 instances would be ok. There are multiple instance where this editor/administrator has abused there power and I have serious concerns about what will hapen in the future. Other things that will hurt this project is automated removal of content, and testing bots/script debugging on live articles. This may have been addressed but his willingngess to use the project as a sandbox for his development is also innparopriate. If even a fraction of the over 3,000 link removals were eroneous or left mistakes, it would take a significant amount of time to go behing and clean it up. And, in fact, many of those edits were erroneous and his talk page at one time had 10+ complaints regarding these actions. The next day, the actions started again. I have never once heard him admit that what he was doing is wrong, however justified it every time. I think it is important, especially for an administrator, to admit when they may have made a mistake. I do not think there is anything preventing betacommand from developing a a new script that will leave a wake of disaster and forcing the rest of the project to cleanup the mess. There are certain sites that should be removed, blind removal by a poorly developed tool at bot like speeds is innapropriate. There is a reason there is a bot approval process.

In summary, betacommand has shown repeated abuse of administrator tools over a period of time including blocking and deleting as well as abuse of Bot policies. If it were n isolated incident, i would be more likley to drop it but these incidents have occured over time which leads me to believe that betacommand should not be entrusted with the administrators tools.-- Chrislk02 (Chris Kreider) 20:02, 26 March 2007 (UTC)[reply]

As a further clarification, i respect Betacommands contributions to this community. I have no vendetta against him and would actually not like to see him immediatly de-sysopped. My concerns posted here are only for what I feel are actions that have and, should similar actions be repeated, permanently damage this community. -- Chrislk02 (Chris Kreider) 15:23, 27 March 2007 (UTC)[reply]

Chrislk02's clarification why arbitration is still necessary

edit

As a further clarification, I believe that this request for arbitration is still necessary as an review of his behavior and for a final ruling. He has got many "Dont do it agains," which have gone unheeded. While I feel an immediate de-sysop is innapropriate, I feel that this should be a last, "Dont do it again" that is endorsed by the community and the arbitration commitee. The many message left at ANI and on his talk page have apparently been left in vain. -- Chrislk02 (Chris Kreider) 18:29, 27 March 2007 (UTC)[reply]

Chrislk02's response to Nick

edit

I at no point claimed that the username blocks by betacommand were current, merely having occured since the originial WP:RFCN had been opened. My orignial ANI posting may have been poorly worded, but I later clarified it. And, actually after realizing that Mel's block of betacommand was possibly due to my poor communication, I contacted mel and attemplted to clarify myself and expressed concerns that I felt the block was innapropriate and that betacomamnd should be unblocked. Any users that I unblocked [14], [15], [16], and [17], I gave several hours for comment by the community and closed only the ones with a clear consensus to allow. I did not unblock any users without requesting the communitys input, and only proceeded when I was sure that the community wanted said users unblocked. My concerns of acting without community consensus are the reason for my ANI posting, and I was actually told that I should just unblock them if I felt it innpropriate. -- Chrislk02 (Chris Kreider) 02:49, 27 March 2007 (UTC)[reply]

Statement by Betacommand

edit

Ok in regard to username blocks I have almost completely stopped issuing those, and with hindsight I should not have blocked as many borderline users as I did. In the rare cases where I do issue them now they are for obvious reasons. Removing mass external links was inappropriate and should not have happened, as I said on the ANI post I shall seek consensus before removing any external links in the future. The bot operator issue as been solved, the scope and exact task are being reviewed by WP:BAG. And to make a clarification I have never abused my bot account User:BetacommandBot.

In regard to the Pallywood issue I made a mistake. I attempted to stop what I thought was an edit war over a {{notability}} tag. Not thinking that protecting the page made since the whole conflict was over a template, I added the template back (I assumed in good faith that the tag was valid) and left a note on the talk page warning the involved parties that they needed to solve the issue on the talk page and not revert war about the tag. Since I did not protect the page, (I hoped valid edits could continue) on the talk page I left a note saying that continued revert warring would get the person blocked. Less than 24 hours later a user removes the template. Seeing this as a continuation of the edit conflict I blocked the user in question for 24 hours. I was attempting to contain the revert war and promote discussion. I see now that how I handled the issue was a mistake. I should have left the page the way I found it and full protected it and filed a RFC on the issue. I have not looked too deep into this dispute. On Hindsight I should have done a more through examination of the issue before acting. I attempted to step in a stop the edit war without enough information. That was a mistake and I don’t plan on that happening again. I am sorry for how I handled the issue, and should have been more careful of my actions. As what appeared to happen here was that I was using admin tools in an edit dispute. That was not my intent, and I shall be very careful in the future to avoid the appearance of admin tool abuse, and I shall be very careful in the future to avoid similar problems again. Betacommand (talk • contribs • Bot) 22:03, 26 March 2007 (UTC)[reply]

Statement by Parker007

edit

According to the BOT Policy esp WP:BOT#Assisted_bots, it clearly states that a bot account is not required. I quote from the policy "Assisted bots are defined as any software that allows rapid editing of articles, while not saving any changes without some human interaction." and "Assisted bots don't necessarily need bot approval."

I shall now quote a statement from the initiating party User:AnonEMouse The first incident, on March 21, had Betacommand apparently using a computerized tool from his own account to remove links to usenet groups across hundreds of articles, without discussion. His edit speeds have been estimated at 30 edits per minute.

I therefore conclude, per the policy WP:BOT, human assisted bots have no policy grounds for any action taken against them, if they are human assisted bots.

Sincerly,

--Parker007 03:48, 7 April 2007 (UTC)[reply]

Preliminary decisions

edit

Arbitrators' opinion on hearing this matter (6/1/0/0)

edit
  • Flip-flopping again. Are there open unresolved problems related of recent date? [time passes] I'm not convinced that the attention of the arbitration committee is required here. I see many different possible problems–some addressed by the community, some not, but none beyond the community's grasp. People of good judgement disagree on many of issues raised here–does the community want to sacrifice its judgement on these questions? Ceremonial reject. Mackensen (talk) 18:19, 27 March 2007 (UTC)[reply]

Temporary injunction (none)

edit

Final decision

edit

All numbering based on /Proposed decision (vote counts and comments are there as well)

Principles

edit

Administrators

edit

1) Wikipedia administrators are trusted members of the community and are expected to follow Wikipedia's policies and guidelines. Occasional lapses of judgment are tolerated, but consistently poor judgment may result in de-sysopping.

Passed 9 to 0, 23:32, 3 May 2007 (UTC)

Automated editing

edit

3) Various tools exist to partially or fully automate repetitive editing tasks. The Wikipedia:Bots/Approvals group (BAG) recognizes three types of bots:

  1. Unsupervised automatic - User runs a bot without being in its presence
  2. Supervised automatic - User runs a bot and watches the edits, but does not have to interact directly
  3. Manually-assisted - User must confirm every change manually

Additionally, editors may use scripts to assist in performing repetitive edits. Generally, scripts require manual confirmation of each edit. Unsupervised and supervised automatic bots require approval of the BAG. Manually assisted bots and scripts may require approval if the editor anticipates making high-speed edits.

Passed 9 to 0, 23:32, 3 May 2007 (UTC)

Access to automated editing tools

edit

4) An editor who misuses automated editing tools such as bots and scripts, or fails to respond appropriately to concerns about their use, may lose the privilege of using such tools.

Passed 9 to 0, 23:32, 3 May 2007 (UTC)

Admin bots

edit

5) Admins should not run bots on their sysop account that are enabled to perform sysop actions (blocking, deleting, etc) without specific community approval from Wikipedia:Bots/Requests for approval and/or WP:RFA.

Passed 6 to 2, 23:32, 3 May 2007 (UTC)

Communication

edit

7) Due to the collaborative nature of Wikipedia, proper communication is extremely important, and all editors are expected to respond to messages intended for them in a timely manner and to constructively discuss controversial issues. This is especially true for administrators in regard to administrative actions. Such expected communication includes: giving appropriate (as guided by Wikipedia's policies and guidelines) warnings prior to, and notification messages following, their actions; using accurate and descriptive edit and administrative action summaries; and responding promptly and fully to all good-faith concerns raised about their administrative actions.

Passed 9 to 0, 23:32, 3 May 2007 (UTC)

Blocking

edit

8.1) Blocking is a serious matter. Administrators should be exceedingly careful when blocking. Blocks should be made only if other means are not likely to be effective; prior discussion or warnings should generally precede all blocks. Blocks should be used only to prevent damage or disruption to Wikipedia, and if there could be any reasonable doubt about whether a block is appropriate, other administrators and/or the community should be consulted. Following a block, the blocked editor should be notified of the block on their talk page, and additional notification on site may be appropriate to seek community input.

Passed 6 to 1, 23:32, 3 May 2007 (UTC)

Findings of fact

edit

Automated image deletion

edit

1) On 27 November 2006, from 17:52 to 19:43 (UTC), Betacommand used an unauthorized automated tool to delete 1,590 images ([18], [19], [20], [21]). He apparently indiscriminately deleted every image which was tagged for speedy delete, with no regard for {{Replaceable fair use disputed}} tags or talk page disputes concerning whether fair use deletion criteria applied. These deletions were criticized at User talk:Betacommand (see "deletion" through "Block" and WP:ANI ([22]). On November 28, he was blocked for a week by Dragons flight with a block summary of "Using an unauthorized deletion bot" ([23]), and unblocked six and a half hours later by Geni (talk · contribs · blocks · protections · deletions · page moves · rights · RfA) with a block summary of "I don't think he is going to do that again" ([24]).

Passed 9 to 0, 23:32, 3 May 2007 (UTC)

The image deletions were conducted inappropriately

edit

2.1) Betacommand's image deletions were conducted inappropriately and showed poor judgment because he used an inappropriate methodology of deleting all images tagged for speedy delete, with no regard for {{Replaceable fair use disputed}} tags or talk page disputes concerning whether fair use deletion criteria applied.

Passed 9 to 0, 23:32, 3 May 2007 (UTC)

Unsatisfactory communication regarding image deletions

edit

3) A number of editors expressed concerns regarding Betacommand's image deletions on User talk:Betacommand, including Irpen ([25]), Tvccs (twice) ([26]), Visor ([27]), Citizensmith (twice) ([28]), 172.202.174.36 ([29]), Dgies (twice) ([30]), HighInBC (twice) ([31]), Jenolen ([32]), HarryCane ([33]), Wisekwai: ([34]), Zanimum ([35]), Timothyarnold85 ([36]), ceejayoz (twice) ([37]). Betacommand made no apparent direct response to any of the above editors either at User talk:Betacommand or at any of the editor's talk pages. ([38]). The only apparent direct responses Betacommand made to queries on his talk page were to answer technical queries about how the deletions were accomplished ([39], [40]). Betacommand's only other apparent comments on the image deletions were two on WP:ANI ([41], [42]).

Passed 9 to 0, 23:32, 3 May 2007 (UTC)

Inappropriate username blocks

edit

4) Betacommand has blocked large numbers of editors for alleged violations of Wikipedia:username policy. For example, in February 2007, from 15:52, 1 February through 23:05, 27 February (UTC), Betacommand blocked approximately 1,000 editors ([43]). These blocks have attracted numerous complaints on multiple occasions ([44], [45], [46], [47], [48]). A number of Betacommand's username blocks have been overturned ([49]).

Passed 7 to 0, with 2 abstentions, 23:32, 3 May 2007 (UTC)

Unsatisfactory communication regarding username blocks

edit

7) A number of editors expressed concerns regarding Betacommand's username blocks at User talk:Betacommand, including Benedict the Moor ([50], [51], [52]), (jarbarf) ([53]), Ryan Postlethwaite: ([54]) and Friday ([55]). Betacommand made no apparent direct response to any of the above editors, either at User talk:Betacommand or at any of the four editor's talk pages. ([56]). One of the few direct responses Betacommand made to queries on his talk page was a short and incomplete reply to a query by HighInBC: [57], [58]. There were four general discussions which included discussion of Betacommand's username blocks: Wikipedia:Requests for comment/Betacommand, and three discussions at WP:ANI; Betacommand did not participate in the RFC, and participated only minimally in the ANI discussions ([59], [60], [61]).

Passed 9 to 0, 23:32, 3 May 2007 (UTC)

Use of an automated tool to disrupt Wikipedia:Requests for comment/User names

edit

8) After complaints about his username blocks on 18 February 2007 and following, Betacommand began using an automated tool that made numerous reports at Wikipedia:Requests for comment/User names ([62], [63]), including several obvious violations ([64], [65], [66], [67]), giving as reason on his talk page, "Im getting tired of being bitched at for no reason. thus I am reporting VERY [sic] block to make sure the bitching stops ..." ([68]). Betacommand was blocked by Pschemp with a block summary: "refuses to stop bot reporting with this account" ([69]) and was unblocked 12 minutes later by Wangi ([70]).

Passed 9 to 0, 23:32, 3 May 2007 (UTC)

Disruption of WP:AIV

edit

9) After concerns were raised about his automated reporting at Wikipedia:Requests for comment/User names ([71]), on 28 February 2007 and continuing through 2 March, Betacommand began to report large numbers of obvious username violations at WP:AIV ( [72], [73], [74], [75]).

Passed 9 to 0, 23:32, 3 May 2007 (UTC)

edit

10) Beginning on 20 March 2007, Betacommand engaged in high-speed removal of external links. From 22:38, 20 March, through 4:35, 21 March (UTC), he removed 418 external links ([76]); from 14:16, 21 March through 17:34 (UTC), he further removed 2,121 external links ([77], [78], [79], [80], [81]). Beginning at 13:16, 21 March, the link removals were criticized at User talk: Betacommand (See "David Wong" through "Yes, please stop" and following) and WP:ANI ([82]).

On 23 March, from 13:15 through 15:29 (UTC), Betacomand removed 104 external links ([83]) which was again criticized at ANI ([84]), as well as Betacommand's reliance on this survey identifying "doorway domains" for spam. The rapid removal of external links raised concerns that Betacommand was using an unauthorized automated tool on his main account, and also that he was removing links so rapidly that he did not have, or take, time enough to determine if the links were valid.

Passed 9 to 0, 23:32, 3 May 2007 (UTC)

edit

11) Many links were removed inappropriately. For example, Betacommand classified as "spam" all links to the United States Agency for International Development's web site: www.usaid.gov, resulting in the removal of the following links: Global Development Alliance homepage from the article "The Global Development Alliance" ([85]), USAID Office of Foreign Disaster Assistance homepage from the article "Office of Foreign Disaster Assistance" ([86]), USAID's page on Hurricane Stan flood relief and recovery efforts" from the article "Hurricane Stan" ([87]), Biography of Andrew S. Natsios from the article on the head of the USAID, "Andrew Natsios" ([88]) and USAID's Iraq page from the article "Foreign aid to Iraq" ([89]), among others.

Passed 9 to 0, 23:32, 3 May 2007 (UTC)

edit

12) Betacommand's removal of external links was conducted inappropriately and showed poor judgment for the following reasons:

  1. he used an automated tool to edit with bot-like speed from an account that did not have a bot flag;
  2. his automated tool was still under development ([90]) and made large numbers of mistakes ([91], [92]), including breaking templates ([93], [94]) breaking list formatting ([95], [96]), leaving empty sections ([97], [98]), and deleting categories and inter language links ([99], [100]);
  3. he used an inappropriate methodology of identifying as spam, all links to web sites listed as having a "spam percentage" above a certain percent, according to a "study" by WebmasterWorld as reported here ([101], [102]); and
  4. links were removed indiscriminately without checking to see whether some of the links were appropriate in context.

Passed 8 to 1, 23:32, 3 May 2007 (UTC)

edit

13) A number of editors expressed concerns regarding Betacommand's link removals at User talk:Betacommand, including DMighton, wrp103 and Kla'quot ([103]]); intgr and Ehheh ([104]); Rsholmes, Susanlesch and Jordan Brown ([105]); AnonEMouse ([106]); Conti ([107]); intgr (again) and Arichnad ([108]); AnonEMouse (again) ([109]); Mithridates, BigDT, Arichnad (again), HighInBC and taviso ([110]); Angr, Flex, and Violask81976 ([111]); 64.160.39.153 and Fredsmith2 ([112]); LeinadSpoon ([113]); Vanrozenheim ([114]); Fredsmith2 (again) and Onorem ([115]); Ehheh and AnonEMouse (again) ([116]); Gandoman, Chacor, kingboyk and Dbachmann ([117]); George.Saliba ([118]). Betacommand was generally unresponsive to the above editors, ignoring many, giving curt replies to others and generally failing to adequately address the editorial concerns being raised.

Passed 9 to 0, 23:32, 3 May 2007 (UTC)

History of inappropriate blocks

edit

14) Betacommand has a history of inappropriate blocks. These include:

Passed 9 to 0, 23:32, 3 May 2007 (UTC)

History of poor judgment

edit

15) Several past incidents demonstrate that Betacommand has a history of poor judgment:

Passed 9 to 0, 23:32, 3 May 2007 (UTC)

Remedies

edit

Betacommand desysopped

edit

4) Betacommand's administrative privileges are revoked. He may reapply at any time via the usual means or by appeal to this committee.

Passed 9 to 0, 23:32, 3 May 2007 (UTC)


Retrieved from "https://en.wikipedia.org/w/index.php?title=Wikipedia:Requests_for_arbitration/Betacommand&oldid=1142571787"