Jump to content

Wikipedia:Bots/Requests for approval/ProtectionBot

From Wikipedia, the free encyclopedia
This is an old revision of this page, as edited by Dragons flight (talk | contribs) at 11:32, 30 December 2006 (create). The present address (URL) is a permanent link to this revision, which may differ significantly from the current revision.
(diff) ← Previous revision | Latest revision (diff) | Newer revision → (diff)

Operator: Dragons flight

Automatic or Manually Assisted: Automatic

Programming Language(s): Python (partially dependant on pywikipedia, but mostly original code)

Function Summary: Intended to automatically protect templates and images appearing on the main page or today's featured article, and unprotect them when they are no longer in these high profile locations. This bot will require sysop rights.

Edit period(s) (e.g. Continuous, daily, one time run): Every 15 minutes

Edit rate requested: N/A

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

Function Details: The bot reads Main Page and Main Page/Tomorrow, identifies the current and immediate future featured articles, and then generates a list of all templates/images appearing on any of these four pages. The bot then checks each template and image to see whether it is protected (i.e. edit=sysop, move=sysop). If it is not protected, the bot will automatically protect the template/image, and add that item to an internal list. The bot will also check this internal list for items it has protected in the past but which are no longer in high profile locations and restore those items to their pre-existing state. It will not remove protection that had been added by someone else.

I have already written code capable of performing most (but not all) of the above functions, but I am coming here to get feedback from the community before carrying this project further. As noted above, this bot would require sysop rights in addition to ordinary bot approval. For a related proposal, see: Wikipedia:Bots/Requests_for_approval/Shadowbot2. Dragons flight 11:32, 30 December 2006 (UTC)[reply]

Discussion