Bip is an IRC proxy, which means it keeps connected to your preferred Internet Relay Client servers, can store the logs for you, and even send them back to your IRC client(s) upon connection.
You may want to use bip to keep your logfiles (in a unique format and on a unique computer) whatever your client is, when you connect from multiple workstations, or when you simply want to have a playback of what was said while you were away.
Basic usage:
* Copy sample bip.conf file found in tarball in ~/.bip/bip.conf
* Edit according to your needs
* Setup your favorite IRC client to connect to bip, and setup a IRC password according to the format “bip_username:bip_password:connection_id”
Use a single bip session for multiple irc connections. Each bip user can have
multiple irc networks to connect to, the connection_id identifies a connection
for a user. For example if a user connects on OFTC and efnet, he would
configure his client to connect to two servers, all with the same host (the one
on which bip is running), and he would set a different irc password for each of
the networks. ie “user:pass:OFTC” and “user:pass:efnet”.
Product's homepage
Here are some key features of "Bip":
· transparent detaching and attaching of clients
· proxy multiple users and IRC connections (multiuser, multiserver)
· automatically join channels upon connection
· backlog events (messages, nick changes, quits, …) upon client connection (optional)
· optional timestamp backlogs
· limit backlog to N lines per channel or backlog since since last client-quit or client-message
· logging support – can be disabled for low disk space servers/accounts. It can even be done in memory if you want backlog without file on disk (think wrt54g and the like)
· configurable logfile format using bip user, bip network name, channel name, and month/day (rotate logs)
· complete text file configuration (+vim syntax file)
· multiple IRC clients can access to the same IRC connection (same network, same nick) transparently
· SSL support on the port Bip listens to (client SSL)
· oidentd support for multiple identities (oidentd spoofing)
· bip runs in one process and tries hard not to hog your CPU for no reason
· low memory usage
What's New in This Release: [ read full changelog ]
· Fix hanging bip on hanging client connexions.
Find us on Google+
