Wikipedia:Bots/Requests for approval/Lunabot


 * The following discussion is an archived debate. Please do not modify it. Subsequent comments should be made in a new section. The result of the discussion was Symbol oppose vote.svg Withdrawn by operator.

Lunabot
Operator: – Luna Santin  (talk)

Automatic or Manually Assisted: Automatic, supervised.

Programming Language(s): Perl.

Function Summary: Archives old cases in the Requests for checkuser namespace.

Edit period(s): Manual start, probably every few days.

Already has a bot flag: Nope.

Function Details: The script will execute all of the steps listed at Requests for checkuser/Procedures. In a nutshell, about three days after a checkuser response, a case subpage is summarized for listing at Requests for checkuser/Case, the case subpage itself is then marked closed with {{subst:rfcu top}} and {{subst:rfcu bottom}}, and the subpage's transclusion on Requests for checkuser is removed.

After getting a "max date" from its user, the script will assemble a list of case pages currently transcluded at Requests for checkuser. For each of those cases, the script will attempt to "date" the case by looking for "indicator/date pairs" (checkuser responses generally include one of the indicator templates, and end with a user signature which includes a timestamp). If a case cannot be dated, or if it is dated beyond the max date, it will be ignored. The script also skips any redirected pages, or pages which include the noarchive template.

If a given case subpage is ready to be archived, the script will build a list of sockpuppets (as judging from templates such as checkuser, checkip, and so on), and will compose a listing suitable for Requests for checkuser/Case (either appending to an existing listing, or adding a new one). At the end of this run, the /Case page will be updated to include listings for each case the script has decided to archive.

More recently, I've been adding some new features. Soon, the script will be capable of editing pages: saving its output for Requests for checkuser/Case, tagging case subpages with archival templates, and removing archived cases from Requests for checkuser. These features are a bit newer, and not as extensively tested, but I'll be keeping a close eye on things.

Discussion
I've actually been working on this thing, off and on, for some time -- see User:Luna Santin/RfcuParser -- but to date it's had read-only access. Since I had some spare time, here, I thought I might as well get it up to speed for write access, as well. – Luna Santin  (talk) 05:38, 10 January 2009 (UTC)
 * CU wants to run CU bot... speedy approve? BJ Talk 11:43, 10 January 2009 (UTC)
 * Mmm Luna, can it work with SSP2? Because I'd hate to break bad news :) -- lucasbfr  talk 17:38, 10 January 2009 (UTC)
 * If the formats/procedures are remotely similar, it shouldn't be too hard to rework it. I figure I'll worry about that "later". :p Once I have a first bot up and running, more shouldn't be too hard. – Luna Santin  (talk) 22:33, 10 January 2009 (UTC)
 * Give it a few tests, see how it goes and then lets rubber stamp :) -- Tawker (talk) 07:18, 12 January 2009 (UTC)
 * Ah, drat. Running into some issue with URL encoding (errors all cleaned up after, by now). Hadn't realized just how quickly the merger with SPI had been looming, so it may be best if I put this on hold for now, unless I can figure it out in the very near future. – Luna Santin  (talk) 10:09, 12 January 2009 (UTC)

I'm going to mark this as withdrawn, feel free to unmark it (by undoing my next edit) and move it back to BRFA if you get back to this later on. Anomie⚔ 19:14, 24 January 2009 (UTC)


 * The above discussion is preserved as an archive of the debate. Please do not modify it. Subsequent comments should be made in a new section.