Operator: Excirial ( Talk, Contribs)
Automatic or Manually Assisted: Fully automatic, with the possibility to manually control the bots behaviour if desired.
Programming Language(s): C#.net, DotNetWikibot Framework
Function Summary:
Edit period(s) (e.g. Continuous, daily, one time run): Continuous(Burst)
Edit rate requested: 2 edits per persistent vandal.
Already has a bot flag (Y/N):
Function Details: Coreva's main task is identifying recurrent vandals and report them to Wikipedia:Abuse when they match the criteria set for such a report. Coreva will do this by downloading the block log at recent intervals (Once every 1-2 hours estimate), and then parsing this page to detect newly blocked IP addresses. Once valid addresses are found, it will request the individual block log for that IP and determine the amount of blocks, and if these blocks are recent. Once this matches the Abuse criteria it will create a new report regarding the vandal to request further investigation of this IP.
The entire bot should be light on server resources. Estimates are that with a scan frequency of once every two hours 30 IP's would be available for personal examination of their block logs. All these operations are read only, which should be less then the average user load generated. It should even be possible to let Coreva base its scan rate on a formula involving server load, log scan frequency and the amount of users to scan before the next full scan takes place.
The tasks listed might sound only moderately useful, but i deem repeating offenders a serious problem Wikipedia should deal with. The current amount of IP's that qualify for WP:Abuse compared to blocks is low, which makes detecting them a dull task for humans. Furthermore Coriva in its proposed form is just a start. Personally i have a few tasks in mind that will increase its effectiveness quite a bit, but as they say: One thing at a time.
A little status update: Coreva's development is coming along just fine, and is actually going way faster then i originally thought/estimated. At this time it is possible to fetch the block logs, process them, and store the users and IP's filtered into a SQL database that was made for that purpose. I also finalized the code that will fetch the amount of blocks from the server, but it still needs a little bit of work as it doesn't take the dates at which a user was blocked into account(Which is required for WP:Abuse).
Currently im finishing of the main tasks code, and starting on the code for some additional tasks i want Coreva to do. As the code for these extra tasks is not yet done, i will issue a new rfba detailing those tasks. Secondly, im starting to lean to make Coreva a manually operated bot, as there is no real gain in realtime downloading and processing of the logs. I think its more server friendly to start coreva manually at non peak times, and let the processing be spread over a few hours.
Excirial (
Talk,
Contribs) 16:21, 24 January 2008 (UTC)
reply
Approved for trial (5 edits). Please provide a link to the relevant contributions and/or diffs when the trial is complete. Make a few reports and report back here. -- uǝʌǝs ʎʇɹnoɟ ʇs(st47) 12:24, 8 March 2008 (UTC) reply
Operator: Excirial ( Talk, Contribs)
Automatic or Manually Assisted: Fully automatic, with the possibility to manually control the bots behaviour if desired.
Programming Language(s): C#.net, DotNetWikibot Framework
Function Summary:
Edit period(s) (e.g. Continuous, daily, one time run): Continuous(Burst)
Edit rate requested: 2 edits per persistent vandal.
Already has a bot flag (Y/N):
Function Details: Coreva's main task is identifying recurrent vandals and report them to Wikipedia:Abuse when they match the criteria set for such a report. Coreva will do this by downloading the block log at recent intervals (Once every 1-2 hours estimate), and then parsing this page to detect newly blocked IP addresses. Once valid addresses are found, it will request the individual block log for that IP and determine the amount of blocks, and if these blocks are recent. Once this matches the Abuse criteria it will create a new report regarding the vandal to request further investigation of this IP.
The entire bot should be light on server resources. Estimates are that with a scan frequency of once every two hours 30 IP's would be available for personal examination of their block logs. All these operations are read only, which should be less then the average user load generated. It should even be possible to let Coreva base its scan rate on a formula involving server load, log scan frequency and the amount of users to scan before the next full scan takes place.
The tasks listed might sound only moderately useful, but i deem repeating offenders a serious problem Wikipedia should deal with. The current amount of IP's that qualify for WP:Abuse compared to blocks is low, which makes detecting them a dull task for humans. Furthermore Coriva in its proposed form is just a start. Personally i have a few tasks in mind that will increase its effectiveness quite a bit, but as they say: One thing at a time.
A little status update: Coreva's development is coming along just fine, and is actually going way faster then i originally thought/estimated. At this time it is possible to fetch the block logs, process them, and store the users and IP's filtered into a SQL database that was made for that purpose. I also finalized the code that will fetch the amount of blocks from the server, but it still needs a little bit of work as it doesn't take the dates at which a user was blocked into account(Which is required for WP:Abuse).
Currently im finishing of the main tasks code, and starting on the code for some additional tasks i want Coreva to do. As the code for these extra tasks is not yet done, i will issue a new rfba detailing those tasks. Secondly, im starting to lean to make Coreva a manually operated bot, as there is no real gain in realtime downloading and processing of the logs. I think its more server friendly to start coreva manually at non peak times, and let the processing be spread over a few hours.
Excirial (
Talk,
Contribs) 16:21, 24 January 2008 (UTC)
reply
Approved for trial (5 edits). Please provide a link to the relevant contributions and/or diffs when the trial is complete. Make a few reports and report back here. -- uǝʌǝs ʎʇɹnoɟ ʇs(st47) 12:24, 8 March 2008 (UTC) reply