Wikipedia:Bots/Requests for approval/DASHBot 14

The following discussion is an archived debate. Please do not modify it. To request review of this BRFA, please start a new section at WT:BRFA. The result of the discussion was

Approved.

DASHBot 14

Operator: Tim1357 (talk · contribs)

Automatic or Manually assisted: Automatic

Programming language(s): Python

Source code available: Its pretty much just an SQL query.

Function overview: Tag (some) cross-namespace redirects for speedy deletion per WP:CSD#R2.

Links to relevant discussions (where appropriate): Not applicable

Edit period(s): The query is lightweight so how about one every 6 hours?

Estimated number of pages affected: 1 or 2 a day.

Exclusion compliant (Y/N): Yes.

Already has a bot flag (Y/N): Yes.

Function details: The bot will look for all redirects that point from the main namespace to any of the following namespaces:

Special
Talk
User
User talk
File
File talk
MediaWiki
MediaWiki talk
Help talk
Category talk

AND they are not in Category:Wikipedia orphaned talk pages that should not be speedily deleted I leave out the template talk namespace because there are some that exist already that seem appropriate. (Example : T:DYKT)

After these redirects are found, the bot tags them with {{db-r2}}.

Discussion

This is pretty uncontroversial and I think can be speedily approved, but I might be missing some flaw. Tim 1357 ^talk 02:24, 19 May 2010 (UTC)[reply]

However, I am unsure of if I should use {{Rediruser-warn}} on the creator's talk page, because it is not always the creator who made the article a redirect. Perhaps it would just be better to tag the redirect? Tim 1357 ^talk 22:58, 19 May 2010 (UTC)[reply]

Why not warn the user that edited it just before it became a redirect - the last non-redirect non-bot non-IP editor? Josh Parris 02:53, 20 May 2010 (UTC)[reply]

Function details don't specify what will happen after you find these redirects. Josh Parris 01:41, 20 May 2010 (UTC)[reply]

I do in the Function overview section, but added to details section as well. Tim 1357 ^talk

Per Wikipedia:Bots/Requests for approval/7SeriesBOT 2, what other checks will the bot make on the redirect? If some vandal comes along to New York and redirects it to [[File:New York.jpg]], will the bot be clever enough to see what's happened? If the bot is that clever, what will it do about articles that are salvageable? Josh Parris 02:08, 20 May 2010 (UTC)[reply]

You must remember that the bot is not deleting the page, the deleting admin still has to glance at the page, making you scenario unlikely. However, I see your point. I'll add a condition that strips pages older than 1 month. Tim 1357 ^talk 02:49, 20 May 2010 (UTC)[reply]

Seems like an acceptable work-around to me. Josh Parris 02:54, 20 May 2010 (UTC)[reply]

Approved for trial (10 edits). Please provide a link to the relevant contributions and/or diffs when the trial is complete. Exercise your code while we resolve the warning criteria and method Josh Parris 07:19, 22 May 2010 (UTC)[reply]

Trial complete., 10 pages tagged and 10 users alerted. [1] (Note:It might require an admin to check, as admins may have deleted the pages) Tim 1357 ^talk 20:24, 22 May 2010 (UTC)[reply]

{{BAGAssistanceNeeded}} could an admin look into this?

Tim1357, what of these warnings? Josh Parris 10:04, 24 May 2010 (UTC)[reply]

I decided to use the standard {{Rediruser-warn}} warn message because, in my mind, over-messaging is better than under-messaging. In other words, I'd rather have the bot send out some redundant messages to people who may not care, rather than not messaging users at all. Perhaps, in the near future, I will add a function to scan backwards through the article's history to check for the user who redirected the page. As for now, however, I will do what {{db-r2}} tells me to do, and leave the message template on the authors talk page. Tim 1357 ^talk 10:57, 27 May 2010 (UTC)[reply]

Okay, taking a look through the bot's taggings, here's my thoughts, On Spécial:Liste de suivi you reverted the bot's edit and the bot immediately re-did it, are you going to put in a 3RR check or something similar? Asset-based community development/version 2 made me think about users moving pages, will the bot give them time to tag the page themself (e.g. user moves a page to userspace, goes back to the old page to tag it, but bot has already done so and warned them). Obviously if it's only running once every six hours, this is highly unlikely to happen, but better safe than sorry :D. The tagging itself seems fine, looking over the edits briefly, all were deleted by admins, and all seemed to meet R2. - Kingpin¹³ (talk) 22:04, 27 May 2010 (UTC)[reply]

With the edits to Spécial:Liste de suivi, I reverted the bot's edit because I accidentally had the bot message the mainspace page Yug instead of User talk:Yug, and I wanted to start the process over. I agree that the instance of a user moving a page and being beaten by DASHBot is unlikely, but I will add a function to exclude pages that have been edited less than 5 minutes ago. Tim 1357 ^talk 22:15, 27 May 2010 (UTC)[reply]

Hmm, this all seems to be going well, but I don't feel that 5 minutes is enough. CSD suggests one to two days (admittedly that's for deletion, isn't really clear on the tagging), if it was a page move. Maybe you could put in a check to see if it was a page move? If not I personally think an hour or so would be a better time. But ~five minutes seems okay for a redirect creation not caused by a page move. - Kingpin¹³ (talk) 22:52, 27 May 2010 (UTC)[reply]

A user has requested the attention of the operator. Once the operator has seen this message and replied, please deactivate this tag. (user notified) Any news? MBisanz ^talk 05:45, 7 June 2010 (UTC)[reply]

Sure, Ill put in a condition to strip pages that have been moved in the past two days. Tim 1357 ^talk 20:34, 7 June 2010 (UTC)[reply]

Approved. MBisanz ^talk 01:36, 8 June 2010 (UTC)[reply]

The above discussion is preserved as an archive of the debate. Please do not modify it. To request review of this BRFA, please start a new section at WT:BRFA.