Free bot software for linux

Potbot is an IRC bot written in Perl. It it intended for aditional code to be added to produce a custom bot to do a certain job. Its code is modular to allow for easy additions. The bot is fully functional as it is, without any code additions.

This bot is certainly not finished. Its very buggy and nasty and the documentation is certainly incomplete. But. i felt like i should put a package up on sourceforge.. so here goes. This is potbot version 2-beta.

All configuration is done by editing potbot.pl in the same directory as this README. To run the bot, simple type ./potbot at bash.

RockBot is a fully functional multi-channel bot for IRC. It has hundreds of usefull commands for managing channels, amusing your friends, and protecting ownership. It is a good alternitive to an eggdrop type bot.
DCC model of rockbox is different like eggdrop. In RockBot YOU NEVER initiate a DCC chat with the bot. In all cases the bot will send you a DCC chat request when it needs one due to the type of data its returning. If you have trouble with DCCs it may be the bot cannotdetermine its true IP address on the machine. Try playing with "#define PPP" in config.h.
Enhancements:
- The data files and memory model were totally re-written. RockBot now uses a multiple-channel scheme for keeping track of users, and also allows one user to store multiple hostmasks under one "handle". There is also a "global" config that controls the default settings for channels and high level bot users. In order to diferentiate
- between global commands and local channel commands the following syntax has been implimented:
- (Note: This example assumes CMDCHAR is !)
- Sent to a channel -> !userlist = userlist of the channel typed in
- Sent to a channel -> !#mychannel userlist = userlist of #mychannel
- Sent to a channel -> !!userlist = global userlist
- ---
- Privmsg to bot -> #mychan userlist = userlist of #mychan
- Privmsg to bot -> !userlist = global userlist
- ---
- When you use JOIN a data file will be created to contain the new channels users, settings, topic etc. The LEAVE command parts the bot but does NOT remove the datafiles, however REMCHAN does.

PCJBot is a jabber bot written in PCJ. It can do various things on a jabber multi-user chat (MUC) channel. PCJ means for POE::Component::Jabber, the bot uses this POE perl module to connect to a jabber server and a chat room.


Plugins include:
Bloglines
Cron
DNS lookups
Fortunes
Math
Spelling
Seen" nick
Spellcheck
URL repository
Weather lookup

Its an IRC bot coded in C++, being started in C. Its main advantage is that several bots can run simultaneously in the same process, making it ideal for shells where the background processes are limited, but not the connections. It doesnt eats much resources, compared to running many instances of mbot.
Main features:
- IPv6 networking support
- Partial TCL scripting compatibility with eggdrop
- All the standard irc commands are available
- Can be in many channels
- Flood protection
- Database, dictionary-like
- DCC Send, easily accessible and configurable
- DCC Chat with partyline
- Different access levels, defined with a userlist
- Recognize and use irc services (NickServ/ChanServ)
- Log channels and privates
- Can send logs to an email, when they are renewed
- Extensions done with dynamic libraries in C++, to which Ive called modules, and can be added/removed while the bot is running
- Conversations with an Artificial Intelligence module (based on C-Alice)
- Watch nicks and log when they are on IRC
- Lots of other stuff, check the available modules

IQ has been my pet project since September 2003. IQ is an intelligent, modular IRC robot written in PHP. I wrote the original branch, 0.1.x, back in late 2003, and developed it and modules for it until early 2004. At some point in June 2004, I became inspired to rewrite the bots core and start the 0.9.x branch.
The new (0.9.x) branch of IQ is just about an entire rewrite of the original, with better coding techniques, and usage of object oriented PHP. Bugs from the original have been corrected, and dozens of new features have been added. My goal with IQ is to create a truly multi-purpose IRC bot that may be easily coded for, while keeping the core relatively light-weight.
IQ is built from modules and can dynamically load and unload modules. Writing modules for the bot is simple, and any PHP developer should be able to write his or her own modules to have the bot act as needed. Modules utilize a binding system (modeled after that used by eggdrop), which create triggers that can be executed upon any regular event (msg, join, kick, nick, quit, part, etc), as well as other bot-specific events (idle, connect, disconnect), and call lambda-style functions in the module to perform the desired actions.
Enhancements:
- Fixed case-sensitivity issues with dancer ircd
- Improved mode checking for non-hybrid ircds
- Miscellaneous bug fixes and code cleanups
- Added Database class for support for MySQL and pgSQL database servers
- Headlines module removed
- Added currency module
- Added idletime module
- Disallowed running as root

bot-trap allows your Web site to automatically ban bad Web robots (a.k.a. Web spiders) that ignore the robots.txt file.

This does not include Googlebot and other well-behaved robots.

The main advantage over other implementations of this concept is that bot-trap has a manual "unban" feature so that humans can unban, but robots cant.

How It Works:

- You place a small "web-bug" strategically in your web pages. This bug is just a tiny image link that says to go to /bot-trap/index.php. Normal people dont see this link, but web bots do.

- You create a /robots.txt file that tells web bots not to go to the /bot-trap directory.
When the bad robot visits /bot-trap/index.php anyway, /bot-trap/index.php adds the IP address of the bad bot to a block list in /.htaccess. They are blocked from access to the site from then on. You can also be emailed when this happens.

Safeguards

It is possible that someone is banned who shouldnt be. Perhaps a previous user of an IP address in a DHCP pool was a naughty user and ran a bad bot, but now the new user is banned. Not to worry, the custom "403 Forbidden" page allows any user to unban themselves by typing a requested word into a form box. Real people can easily do this, but bots cant!

Installation:

1. Unpack the tarball in your web page root directory:
# tar -xzf bot-trap-x.x.tar.gz
2. Either add a line to your root .htaccess file like:
ErrorDocument 403 /bot-trap/forbid.php
or copy the premade one (bot-trap/htaccess-root-example). Notice that since once an IP is banned, it cant access anything in /, so the 403 page should be in /bot-trap, and /bot-trap/.htaccess should only say "Allow from all". Look at the forbid.php file in the distribution to see how to do this, or just use it as-is.
3. Make sure .htaccess controls are allowed in your Apache configuration (especially the "AllowOverride" directive). This allows bot-trap to ban IP addresses using the htaccess mechanism.
4. Create the empty file blacklist.dat in your web root directory, and make blacklist.dat, .htaccess, and the bot-trap directory in your web root directory owned by the www user with write permission. If web server uses a group (like the group "www-data" on Debian GNU/Linux), set these files and directories group-writable.
5. Edit bot-trap/settings.php to hold the correct email addresses to send alerts to.
6. Add "web-bugs" to your main web page to catch the bad bots. This is the XHTML code:
< !-- Bad robot trap: Dont go here or your IP will be banned! -->
< a href="/bot-trap/">< img src="bot-trap/pixel.gif" border="0"
alt=" " width="1" height="1"/>< /a>

7. Add the bot-trap directory to your robots.txt file, or copy the example robots.txt file (bot-trap/robots.txt.example) to the root directory.
8. Make sure /.htaccess and all other files have the correct permissions and ownership for your site.

CWBot is an IRC bot to provide online services in Morse usable with the CWirc client. It can broadcast world news in Morse and Hellschreiber, RAC ham news, act as a MorseMail to CWirc repeater, or send fortune cookies in Morse, over an IRC channel or throught DCC chat, with adjustable keying speed and Farnsworth spacing. The project is easily extendable with scripts or external programs to provide additional services in Morse.
Architecture of the bot
CWBot is really composed of two parts : the bot core (the "cwbot" program itself) and the external chat engines.
The bot core
The bot core is a very basic IRC bot that maintains a connection to an IRC server, stays on a channel and replies to "Hello" and "Help". It doesnt do anything else by itself. To interact with users, it relies on external programs (the chat engines) that handle the chatting itself.
The core uses 2 types of chat engines : the channel chat engine, which does the chatting on the IRC channel the bot is on, and the DCC CHAT engine, which chats with individual DCC CHAT requestors. It spawns one instance of the
channel chat engine, and as many instances of the DCC CHAT engine as there are DCC CHAT sessions open. The core handles the translation between IRC or DCC CHAT messages and the chat engines, and takes care of starting/stopping
them transparently.
The chat engines
The chat engines (channel chat engine or DCC CHAT engine) are external programs that read and write plain text messages throught their standard inputs and standard outputs. The channel chat engine is meant to be spawned once and run forever. Should it stop for whatever reason however, the bot core will try to respawn it. The DCC CHAT engine is spawned whenever a DCC CHAT connection opens, and either runs until it decides to stop, provoking the termination of the DCC CHAT session, or until the bot itself terminates the session and kills it. Since there can be more than one DCC CHAT engine running at any given time,
they must be careful not writing to the same files or sharing resouces without talking to each other, if they need to share things.
Enhancements:
- The parser in the news broadcast scripts has been corrected to process the BBCs XML newsfeed properly.