Wikipedia:Bots/Requests for approval/cocoabot

Cocoabot

• (BRFA
• Approved BRFAs
• talk
• contribs
• count
• SUL
• logs
• page moves
• block log
• rights log
• flag)

Operator: Cocoaguy

Automatic or Manually Assisted:Automatic

Programming Language(s):PHP 5.1

Function Summary:A clone of Jayden54Bot; Dead link cleaning This bot will automatically notify article authors when "their" article is up for deletion in an Article for Deletion discussion.

Edit period(s) (e.g. Continuous, daily, one time run):Twice Daily

Edit rate requested: 4 edits per min

Already has a bot flag (Y/N):No

Function Details:A clone of Jayden54Bot; Often when an article is nominated for deletion the original author is never notified using the {{AFDWarning}} or {{AFDNote}} tags. This bot will scan WP:AFD/Today twice a day, and check for new nominations. It will then notify the original author of each nominated article using the {{AFDWarning}} or {{AFDNote}} tags. This will help avoid biting new users (who don't know much about the deletion process) and give article authors a better chance to fix the article. (Cocoaguy ここがいい _contribs^talk) 00:05, 17 May 2007 (UTC)

Discussion

Feel free to start running the AFD notifying task as a clone of an already approved bot, but you said in the function summary "Dead link cleaning". Can you explain that further? Did Jayden54Bot also do that? —METS501 (talk) 00:55, 17 May 2007 (UTC)

Scratch dead link cleaning. I was only told this by another user but not sure. it is truly "This bot will automatically notify article authors when "their" article is up for deletion in an Article for Deletion discussion." (Cocoaguy ここがいい _contribs^talk) 01:06, 17 May 2007 (UTC)

Ok, so i do have approval to run cocoabot; just to clarify? (Cocoaguy ここがいい _contribs^talk) 01:08, 17 May 2007 (UTC)

Yep, Speedily Approved. This bot shall run with a flag. —METS501 (talk) 02:13, 17 May 2007 (UTC)

Approval revoked until bot is registered and identity confirmed. --ST47Talk 18:08, 17 May 2007 (UTC)

I'm glad the discussion on this bot has been opened again. I have no problem with Cocoaguy running this bot, since I've stopped running my bot (due to lack of time), but a few things must be cleared up. First of all, Coacoaguy has not got the source code yet for the AFD task nor has he asked for it yet (I'm happy to give it to anyone who asks). It's quite complex as there are a few things to keep in mind (such as double notifications, opt-out lists, and more). Secondly the 'dead-link cleaning' task refers to another small (unapproved) task that I did with my bot account. Once a day I ran a small script to help out the WP:DEAD project with clearing their link lists. Since that only accounted for 2 edits a day I didn't bother getting approval for that. I have posted the source for that task online, and it's available at User:Jayden54/WPDead Source.js. Personally I don't really care whether someone takes over the AFD notifications because it didn't seem all that popular. But I would like to see someone take over the dead-link removal task, because it really helps the WP:DEAD project and they deserve all the help they can get. Cheers, Jayden54 19:01, 17 May 2007 (UTC)

As am I. The offer of assistance was nice, but I don't think this person has a clue. Salad Days 00:22, 18 May 2007 (UTC)

The bot account has been registered, and has blanked its own userpage. --ST47Talk 10:29, 18 May 2007 (UTC)

I have blocked the bot for going insane and doing some downright strange stuff (just see the above link). Sean William 04:04, 19 May 2007 (UTC)

It appears the account has been compromised. I have enabled the autoblocker in hopes of blocking the hijacker's IP. Sean William 04:13, 19 May 2007 (UTC)

A user has requested the attention of the operator. Once the operator has seen this message and replied, please deactivate this tag. (user notified)

A note to say what exactly the operator is needed for. We need you to send a BAG member a verifiable communique stating that you are Cocaoguy, and that you have control of the bot account, and that it has been recovered from the hijacker. If, in fact, it have not been hijacked and merely malfunctioned, please make that clear here. A way to verify your identity would be to use a PGP key to sign your message, if the public part had already been shared, or by making some other commitment (providing unguessable, but verifiable, information). If you don't have such info, but know another user on Wikipedia who can verify your identity, please do that and ask them to contact one of us. Thanks, Martinp23 22:07, 19 May 2007 (UTC)

Martinp23, according to Wikipedia:Requests for checkuser/Case/Cocoabot, the account wasn't registered by Cocoaguy. The account will have to be usurped by a bureaucrat so that Cocoaguy can register it. Sean William 22:14, 19 May 2007 (UTC)

Just noticed that after creating a new RFCU (now deleted), but got sidetracked :). My advice changes then, and I suggest that Cocoaguy speaks to a 'crat, as detailed by Sean, above. Martinp23 23:37, 19 May 2007 (UTC)

I was afraid this would happen :( --ST47Talk 00:25, 20 May 2007 (UTC)

I would suggest that Cocoaguy just picks a different bot account name now and move on, with the lesson learned that you should register the account before making the bot request. --Cyde Weys 00:53, 20 May 2007 (UTC)

I think it's important that, once Cocoaguy regains control over the bot account, the bot should go through a trial period just like a normal bot approval request. This bot is NOT a direct clone of my bot, because Cocoaguy is not using my source code (and to be honest, I don't think Cocoaguy has even written the bot yet). Jayden54 09:58, 20 May 2007 (UTC)