Operator: Winbots
Automatic or Manually Assisted: Manually assisted until I have corrected all bugs and false positives are few and far between.
Programming Language(s): PHP, my own classes to interact with Wikipedia's query.php, api.php, and index.php
Function Summary: Reverting vandalism.
Edit period(s) (e.g. Continuous, daily, one time run): Continuous
Edit rate requested: Only as often as it finds vandalism via Special:RecentChanges, but no faster than 10 edits per minute.
Already has a bot flag (Y/N): N
Function Details: Request RecentChanges and perform basic analysis on the data returned. If it finds something suspicious, request more information about that page and perform more in depth analysis on that information. If it determines that it looks like vandalization and it is in read-only mode: send information to owner. If it determines that it looks like vandalization and it is in read-write mode, request more information on user. If user has a long history on Wikipedia, log incident, but do nothing. If user is new/IP address, revert, log incident, and post a notice on the user's talk page.
The bot will also set its user page and its source code page when starting.
A couple questions.
Thanks! — Madman bum and angel ( talk – desk) 21:14, 24 July 2007 (UTC) reply
As you're probably aware, it took quite a bit of work to get our current antivandalism bots to where they are today. False positives obviously aren't the end of the world but they are still a problem. Having said that, I'd be interested in seeing what kind of scoring system you plan on implementing. -- S up? 08:35, 25 July 2007 (UTC) reply
I have now implemented the maxlag feature. The bot will sleep 10 seconds, then abort the edit if the server is lagged more than 2 seconds. Winbots 01:24, 27 July 2007 (UTC) reply
I have now coded the reverting/warning feature. It will remain disabled until such time as the bot is given a trial run, though. Winbots 16:57, 28 July 2007 (UTC) reply
I have also coded a feature to ask me about each revert before proceeding, if enabled. I plan on enabling this feature during the trial run, when the trial run is granted. Winbots 22:43, 28 July 2007 (UTC) reply
I'm approving you for a 50 revert trial. Each diff should be manually checked before allowing the bot to revert, so I expect an edit rate of no more than 2 epm. For the final 10 reverts, presuming you have had no problems, please set the bot to full-auto mode and (while watching) let it go at an edit rate of no more than 6epm (a 10 second sleep). Approved for trial. Please provide a link to the relevant contributions and/or diffs when the trial is complete. Thanks, Mart inp23 00:57, 29 July 2007 (UTC) reply
Matt, this is a major bot, so it helps to have more than one person look over the trial results before jumping ahead. As it is, there are a few instances of things like this, which don't make sense. Also, I note that the bot is reverting to the same page more than once, which I believe I explained on IRC to not be a good idea - we often get IPs or new users blanking massive sections of articles completely legitimately, where those articles violate BLP policy. There are similar cases which mean that a bot edit war is completely undesirable (by all means have a mode, manually set, which allows you to give the bot permission to make more than one revert, but by default it should be off).
For warnings, I'd suggest that you craft your own, and issue only two before reporting the user (so, report on the third offence). It would be nice if the bot could recognise other peoples' warnings, but not essential. Thanks, Mart inp23 12:21, 1 August 2007 (UTC) reply
Looks like it's working well, I don't see why not to Approved.. -- ST47 Talk· Desk 22:05, 12 August 2007 (UTC) reply
Operator: Winbots
Automatic or Manually Assisted: Manually assisted until I have corrected all bugs and false positives are few and far between.
Programming Language(s): PHP, my own classes to interact with Wikipedia's query.php, api.php, and index.php
Function Summary: Reverting vandalism.
Edit period(s) (e.g. Continuous, daily, one time run): Continuous
Edit rate requested: Only as often as it finds vandalism via Special:RecentChanges, but no faster than 10 edits per minute.
Already has a bot flag (Y/N): N
Function Details: Request RecentChanges and perform basic analysis on the data returned. If it finds something suspicious, request more information about that page and perform more in depth analysis on that information. If it determines that it looks like vandalization and it is in read-only mode: send information to owner. If it determines that it looks like vandalization and it is in read-write mode, request more information on user. If user has a long history on Wikipedia, log incident, but do nothing. If user is new/IP address, revert, log incident, and post a notice on the user's talk page.
The bot will also set its user page and its source code page when starting.
A couple questions.
Thanks! — Madman bum and angel ( talk – desk) 21:14, 24 July 2007 (UTC) reply
As you're probably aware, it took quite a bit of work to get our current antivandalism bots to where they are today. False positives obviously aren't the end of the world but they are still a problem. Having said that, I'd be interested in seeing what kind of scoring system you plan on implementing. -- S up? 08:35, 25 July 2007 (UTC) reply
I have now implemented the maxlag feature. The bot will sleep 10 seconds, then abort the edit if the server is lagged more than 2 seconds. Winbots 01:24, 27 July 2007 (UTC) reply
I have now coded the reverting/warning feature. It will remain disabled until such time as the bot is given a trial run, though. Winbots 16:57, 28 July 2007 (UTC) reply
I have also coded a feature to ask me about each revert before proceeding, if enabled. I plan on enabling this feature during the trial run, when the trial run is granted. Winbots 22:43, 28 July 2007 (UTC) reply
I'm approving you for a 50 revert trial. Each diff should be manually checked before allowing the bot to revert, so I expect an edit rate of no more than 2 epm. For the final 10 reverts, presuming you have had no problems, please set the bot to full-auto mode and (while watching) let it go at an edit rate of no more than 6epm (a 10 second sleep). Approved for trial. Please provide a link to the relevant contributions and/or diffs when the trial is complete. Thanks, Mart inp23 00:57, 29 July 2007 (UTC) reply
Matt, this is a major bot, so it helps to have more than one person look over the trial results before jumping ahead. As it is, there are a few instances of things like this, which don't make sense. Also, I note that the bot is reverting to the same page more than once, which I believe I explained on IRC to not be a good idea - we often get IPs or new users blanking massive sections of articles completely legitimately, where those articles violate BLP policy. There are similar cases which mean that a bot edit war is completely undesirable (by all means have a mode, manually set, which allows you to give the bot permission to make more than one revert, but by default it should be off).
For warnings, I'd suggest that you craft your own, and issue only two before reporting the user (so, report on the third offence). It would be nice if the bot could recognise other peoples' warnings, but not essential. Thanks, Mart inp23 12:21, 1 August 2007 (UTC) reply
Looks like it's working well, I don't see why not to Approved.. -- ST47 Talk· Desk 22:05, 12 August 2007 (UTC) reply