| Revision as of 05:44, 22 June 2006 editAaron Schulz (talk | contribs)Extended confirmed users26,051 edits →Known Issues: m← Previous edit | Revision as of 19:07, 22 June 2006 edit undoAaron Schulz (talk | contribs)Extended confirmed users26,051 edits →Known Issues: doneNext edit → | ||
| Line 25: | Line 25: | ||
| <s>Deletion/protection log sychronization can sometimes be off, causing re-protected restored pages to be delisted, even though they were reprotected. Sometimes this corrects itself, but it sometimes will not. Someone may have to add the entry back to ] manually.</s> | <s>Deletion/protection log sychronization can sometimes be off, causing re-protected restored pages to be delisted, even though they were reprotected. Sometimes this corrects itself, but it sometimes will not. Someone may have to add the entry back to ] manually.</s> | ||
| :See bug 5987. | :See bug 5987. | ||
| :Fixed |
:Fixed, the bot now uses HTTP request chains to check if the page is still protected by scanning for the header notice. To doublecheck, it also compares the timing of the last restoration (for restored pages) with the protection timing (this also catches semi-move protects, which the first test does not). | ||
| :The delist function was re-written yet again to http request the listed pages only, so it can now pick up pages that were deleted, became protected '''deleted pages''', restored, or moved (and it fixes the list entry to the new location). | |||
| :The downside is that the protection log has to go way back each time, and that will not always catch things if they are for long protected pages. | |||
| ==Future abilities== | ==Future abilities== | ||
Revision as of 19:07, 22 June 2006
About VoABot
Misplaced Pages editing bot run by Voice of All | This user account is a bot operated by Voice of All (talk). It is used to make repetitive automated or semi-automated edits that would be extremely tedious to do manually, in accordance with the bot policy. Administrators: if this bot is malfunctioning or causing harm, please block it. |
The point of this bot is to keep WP:PP updated and to archive fullfulled/denied WP:RFPP requests.
Main Tasks
A) This bot automatically updates the semi-protected, full-protected, move-protected, and the other (non-article/non-user/non-image) lists at WP:PP. It extracts the data, hourly, from the protection/deletion log and lists pages. Every half hour mark (i.e. "2:30" ect...) it checks for pages to delist and at the beginning of each hour it checks for pages to list.
B) This bot also automatically cleans up WP:RfPP. It makes it so that each "current" section can have no more than 3 consecutive 6+ hour old fullfilled/denied requests. They are moved to the fullfilled/denied section, which can only have no more that 15 requests unless they are less than 12 hours old. The extra ones are removed. Additionally, entries with "===" for the section instead of "====" are fixed.
Other Tasks
A) If an admin protected a non-user/user talk page without a summary, it will not be listed on WP:PP, that is part of the D.P. filter. Such admins will automatically be notified. It will re-add this warning if it is deleted to quickly, since it only checks a)how long ago the protection was and b)if the message is already there. It will not "know" if someone removed it.
B) This bot keeps the list of admins JS list variable up to date at User:VoABot/adminlist/monobook.js. This avoids slower and more server using HTTP request checks when users get history stats from User:Voice of All/History/monobook.js.
Contrubitors
I wrote the script by and large, though I templated some code from an autoAFD lister by User:Johnleemk.Voice-of-All 20:42, 21 May 2006 (UTC)
Known Issues
While this bot is programmed to filter out deleted article protections, it still sometimes can't tell the difference. Do NOT bother removing them, contact User:Voice of All and report the incident; there may be a permanent solution that will filter out similar entries in the future.
- Fixed, the bot now uses HTTP request chains to check for deleted page templates, subst or not.
Deletion/protection log sychronization can sometimes be off, causing re-protected restored pages to be delisted, even though they were reprotected. Sometimes this corrects itself, but it sometimes will not. Someone may have to add the entry back to WP:PP manually.
- See bug 5987.
- Fixed, the bot now uses HTTP request chains to check if the page is still protected by scanning for the header notice. To doublecheck, it also compares the timing of the last restoration (for restored pages) with the protection timing (this also catches semi-move protects, which the first test does not).
- The delist function was re-written yet again to http request the listed pages only, so it can now pick up pages that were deleted, became protected deleted pages, restored, or moved (and it fixes the list entry to the new location).
Future abilities
This bot (or VoABot2 most likely) may, in the future, check specified pages for banned users that are still editing (it will do an IP range check) and revert them. It will check every 5-30 minutes, depending on the page.Voice-of-All 21:23, 28 May 2006 (UTC)
Categories: