Operator: X clamation point
Automatic or Manually Assisted: Automatic
Programming Language(s): PHP, using a modified version of ClueBot classes
Function Summary: Daily, uploading and protecting images from Commons which are on the Main Page
Edit period(s) (e.g. Continuous, daily, one time run): Continuous
Already has a bot flag (Y/N): Has a bot flag, but no admin flag.
Function Details: This bot will first do a search for all images currently included on the Main Page. It then checks which ones are on Commons and which ones are uploaded locally. It looks at the ones from Commons, and determines if they are already protected or not. If it is not, it uploads it to the English Wikipedia. After that, it puts {{ C-uploaded}} onto the image. Every day, it deletes the images that it uploaded for the previous day, bringing the Commons version back.
Source code is available at User:X!/Main Page bot Source. The results of 1 day of a dry run is at User:X!/MPBot Dry Run.
So the bot runs one time per day? How does it synchronize with the change of TFA? That is, how do you guarantee there is no window between the TFA cahnge and the bot running? — Carl ( CBM · talk) 02:40, 30 September 2008 (UTC) reply
How are you planning on preventing timed vandalism attacks over on Commons from being replicated and protected here? east718 // talk // email // 03:14, 30 September 2008 (UTC) reply
It might be better if the bot operates on tomorrow's featured article. If some vandalism happens to slip by due to the 10 minute gap, it will probably be noticed by the TFA team before the article is made live the next day. The bot would still undo its actions on yesterday's featured article as originally planned. — Carl ( CBM · talk) 04:08, 30 September 2008 (UTC) reply
Comment - I am running a dry run currently, saving the results to a text file (which will be released soon). X clamation point 22:01, 3 October 2008 (UTC) reply
After giving this more and more consideration, this seems inappropriate for a bot. If all of this time is going to be spent writing a bot in PHP, why not instead implement cascading protection from the various projects to Commons inside MediaWiki itself? Likely not a very simple task, but it's the best solution to this particular problem that I see. -- MZMcBride ( talk) 06:32, 4 October 2008 (UTC) reply
Ok, so after reading this over a few times, I think the current status of this bot needs to be clarified:
X clamation point 04:06, 5 October 2008 (UTC) reply
Since no one has raised any objections to the actual task and the code seems to be stable Approved for trial (7 days). Please provide a link to the relevant contributions and/or diffs when the trial is complete. under your main account, place Putt9567 at the front of your edit/delete/upload summaries so we can filter them out, also please place a link to this brfa and make it clear that it is a bot making the edit -- Chris 03:58, 6 October 2008 (UTC) reply
SELECT CONCAT('* ',log_action,' on [[:Image:',log_title,']] at ',log_timestamp) FROM logging WHERE log_comment LIKE '{{Putt9567}}%' AND log_user = 3010110 AND log_title NOT LIKE 'Image-%';
Sorry, I apologise if I did not make a comment earlier before the trial run because I do not monitor WP:RBA on a regular basis. For almost a year now, I have been semi-automatically protecting the Commons images for TFA, OTD, and POTD using a cascading protected page on Commons:User:Zzyzx11/En main page. Much of its details are explained on Commons:User talk:Zzyzx11/En main page. Some of the disadvantages I mention there may be relevant to SoxBot11, namely:
Therefore, if the bot functions as the way it currently does, do not be surprised if it frequently has to make posts on the IRC channels. On the other hand, IMO, based on my observations here and for reasons on Commons I will not go into for security reasons, it is a little harder to vandalise Commons images than ones directly stored here. Cheers. Zzyzx11 (Talk) 04:29, 7 October 2008 (UTC) reply
Operator: X clamation point
Automatic or Manually Assisted: Automatic
Programming Language(s): PHP, using a modified version of ClueBot classes
Function Summary: Daily, uploading and protecting images from Commons which are on the Main Page
Edit period(s) (e.g. Continuous, daily, one time run): Continuous
Already has a bot flag (Y/N): Has a bot flag, but no admin flag.
Function Details: This bot will first do a search for all images currently included on the Main Page. It then checks which ones are on Commons and which ones are uploaded locally. It looks at the ones from Commons, and determines if they are already protected or not. If it is not, it uploads it to the English Wikipedia. After that, it puts {{ C-uploaded}} onto the image. Every day, it deletes the images that it uploaded for the previous day, bringing the Commons version back.
Source code is available at User:X!/Main Page bot Source. The results of 1 day of a dry run is at User:X!/MPBot Dry Run.
So the bot runs one time per day? How does it synchronize with the change of TFA? That is, how do you guarantee there is no window between the TFA cahnge and the bot running? — Carl ( CBM · talk) 02:40, 30 September 2008 (UTC) reply
How are you planning on preventing timed vandalism attacks over on Commons from being replicated and protected here? east718 // talk // email // 03:14, 30 September 2008 (UTC) reply
It might be better if the bot operates on tomorrow's featured article. If some vandalism happens to slip by due to the 10 minute gap, it will probably be noticed by the TFA team before the article is made live the next day. The bot would still undo its actions on yesterday's featured article as originally planned. — Carl ( CBM · talk) 04:08, 30 September 2008 (UTC) reply
Comment - I am running a dry run currently, saving the results to a text file (which will be released soon). X clamation point 22:01, 3 October 2008 (UTC) reply
After giving this more and more consideration, this seems inappropriate for a bot. If all of this time is going to be spent writing a bot in PHP, why not instead implement cascading protection from the various projects to Commons inside MediaWiki itself? Likely not a very simple task, but it's the best solution to this particular problem that I see. -- MZMcBride ( talk) 06:32, 4 October 2008 (UTC) reply
Ok, so after reading this over a few times, I think the current status of this bot needs to be clarified:
X clamation point 04:06, 5 October 2008 (UTC) reply
Since no one has raised any objections to the actual task and the code seems to be stable Approved for trial (7 days). Please provide a link to the relevant contributions and/or diffs when the trial is complete. under your main account, place Putt9567 at the front of your edit/delete/upload summaries so we can filter them out, also please place a link to this brfa and make it clear that it is a bot making the edit -- Chris 03:58, 6 October 2008 (UTC) reply
SELECT CONCAT('* ',log_action,' on [[:Image:',log_title,']] at ',log_timestamp) FROM logging WHERE log_comment LIKE '{{Putt9567}}%' AND log_user = 3010110 AND log_title NOT LIKE 'Image-%';
Sorry, I apologise if I did not make a comment earlier before the trial run because I do not monitor WP:RBA on a regular basis. For almost a year now, I have been semi-automatically protecting the Commons images for TFA, OTD, and POTD using a cascading protected page on Commons:User:Zzyzx11/En main page. Much of its details are explained on Commons:User talk:Zzyzx11/En main page. Some of the disadvantages I mention there may be relevant to SoxBot11, namely:
Therefore, if the bot functions as the way it currently does, do not be surprised if it frequently has to make posts on the IRC channels. On the other hand, IMO, based on my observations here and for reasons on Commons I will not go into for security reasons, it is a little harder to vandalise Commons images than ones directly stored here. Cheers. Zzyzx11 (Talk) 04:29, 7 October 2008 (UTC) reply