ben
/
earwigbot
mirror of https://github.com/earwig/earwigbot
1
1
Fork 0
Code Releases 4 Activity
A Python robot that edits Wikipedia and interacts with people over IRC https://en.wikipedia.org/wiki/User:EarwigBot
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
288 Commits
2 Branches
39 MiB
 
Tree: d949269944
Branches Tags
${ item.name }
Create branch ${ searchTerm }
from 'd949269944'
${ noResults }
 ZIP  TAR.GZ
Ben Kurtovic d949269944 Some SQL updates, starting work on afc_history task. 13 years ago
bot Some SQL updates, starting work on afc_history task. 13 years ago
tests adding TestCalc for the IRC command; fixes, additions, cleanup to support etc 13 years ago
.gitignore Using logging throughout the bot now 13 years ago
LICENSE new blowfish.py module, some changes in Cryptography(), LICENSE cleanup 13 years ago
README.md Basic SQL querying support with oursql. 13 years ago
earwigbot.py Reorganizing functions in config.py; store User-Agent and IRC version in config; exception, docstring, and comment cleanup. 13 years ago

README.md

EarwigBot is a Python robot that edits Wikipedia and interacts with people over IRC.

History

Development began, based on the Pywikipedia framework, in early 2009. Approval for its fist task, a copyright violation detector, was carried out in May, and the bot has been running consistently ever since (with the exception of Jan/Feb 2011). It currently handles several ongoing tasks, ranging from statistics generation to category cleanup, and on-demand tasks such as WikiProject template tagging. Since it started running, the bot has made over 45,000 edits.

A project to rewrite it from scratch began in early April 2011, thus moving away from the Pywikipedia framework and allowing for less overall code, better integration between bot parts, and easier maintenance.

Installation

Dependencies

EarwigBot uses the MySQL library oursql (>= 0.9.2) for communicating with MediaWiki databases, and some tasks use their own tables for storage. It is not required.