|
Project Information
Featured
Downloads
Links
|
WELCOME TO GOZERBOTI am pleased to present to you version 1.0 of GOZERBOT, a IRC and Jabber(XMPP) bot. This is the final and last release of GOZERBOT, new development will continue with the JSONBOT at http://jsonbot.googlecode.com/ I will fix security bugs when i am still around, if you find any bugs please report them on http://code.google.com/p/gozerbot/issues/list requirements
download
licenseGOZERBOT is free code (BSD) and can be cloned where needed. contact the developer
start!! make a separate user and group for the bot !!
IRC./bin/gozerbot -o <userhost of the owner> -s <server> -c <\#channel> notice the thats for escaping the # in the channel name Jabber / XMPP./bin/gozerbot -t xmpp -o <JID of the owner> -u <bot JID> -p <pass> this creates the necesary directories and config files .. after checking if the bot runs fine you can run the bot in daemon mode with ./bin/gozerbot >> logfile 2>&1 & gozerbot-start is for globally installed bots running from ~/.gozerbot (debian and freebsd) you can also edit the gozerdata/mainconfig and gozerdata/fleet/default/config files nextyou can /msg the bot !join #channel to let the bot join channels, the bot wil remember channels it has joined you can use the “meet <nick>” command to add other users to the bot, if you are not in a channel or conference use: !user-add <username> <host or JID> non core plugins will not be loaded on default. use !reload <plugin> to enable a plugin. see the !available command to see what plugins can be reloaded when using commands in a /msg use –chan <channel> to let the command operate on a channel .. default channel in a /msg is the users nick notes
links
thnxSpecial thnx goes out to Annemiek, Danny, Kirsten, Doscha and my parents Anneke and Thies. They made me possible and this bot to begin with. ;] channelsi like to thank the following channels.
peopleI want to start with metioning 3 brothers of mine, who were there in the beginning, coding with me and shaping GOZERBOT as it is today. They thinked with me ;] AimAim was one of the first of many that started coding on GOZERBOT. Spend many many nights coding all kinds of cool bot network prototypes mostly called borknet, collective and pyronet (using the Pyro framework). Aim also made the partyline code which is still in JSONBOT mazemaze is the person who has had the most external influence on the bot, periodical, statefull reboot, numerous plugins. He also forked the bot when things were changing to fast. I was all growing into writing JSONBOT and maze pointed me on the thing that is important. API stability ;] see http://youtu.be/00xK0oisX4Y trbstrbs was the one with the smartest brains and he coded some key functionality into GOZERBOT namely the persistconfig. This allowed the user to edit the plugin configuration from the command line. trbs also created the markov plugin which gave us hours of humerous fun ;] NetfreakIn the beginning days i had some key figures around that enabled me to host the gozerbot.org site. Netfreak was the one who offered my a FreeBSD jail in which i could run my httpd and any other services i needed. Still gratefull for that NetFreak, we faced numerous paranoid OMG i am hacked moments. briljant way to get used to hosting stuff. BOFH galore ;] NomadNow you have budies and budies and Nomad is my budy, being there from the beginning, hosting my domains for me as i could not finance that myself. Nomad helps out with that and is still around ;] Thnx bro, wouldnt happened without yah ;] qirtaibaqirtaiba was a dude who asked for a feature request which i helped him with, to show his face in the channel again asking if i wanted to have GOZERBOT in the debian repositories. Sure do !! ;] Qirtaiba still does the debian package maintenance for me, also after many many years. Some people just stick around, gratefull for that ;] snoresnore man i miss ya ! snore was the one helping me out when GOZERBOT grew bigger, supporting me in every way he could. Basically what snore did was running GOZERBOT in a very busy channel of those days #fifo. So my changes were directly tested and numerous bug fixes were made that way. Loved those days , at its peek there were more then 30 people running directly from the mercurial repo. snore also helped me hosting my own mercurial repositories and maintained the gozerplugs for me. ]V[And then there are people that bring huge amounts of energy and enthusiasm to the party and ]V[ is the one doing that with GOZERBOT. Testing many many GOZERBOT with me, fleet sizes of 20+ bots were not unusual. ]V[ did a presentation on GOZERBOT on the CCC which you can see here bsodbudy of budies, always prepared to test for me when i need to release stuff. thank god i have bsod to think and dream with me, as a dreaming mind is the inspiration for the creation ;] RexodusRex is the ever aware always present never leaving aroundness that is here to shine on my path ;] Lots lots of testing done for GOZERBOT DJMUggsDJMuggs is the one going all back with me even before the DUDINET times. dj is the bro mak gab dude ! Also still around which gives me joy to see the faces are stil there ;] DJ broeder haha gaat lang terug allemaal ArcAngelArc it the light holding the candle in the #dunkbots rooms. Maintaining the peace. Did a lot of solaris testing for GOZERBOT. Still here bro, thnx ;] WiebelWiebel is the one hosting gozerbot.org right now. I owe him i beer i guess ;] Without Wiebel there wouldn’t be a version 1.0. Goes waay back with ;GOZERBOT as well. moreLaagje for his years of bot testing core. serkoon for his karma ratelimiter Snuf for his jabber testing TW for his making me learn the first steps. Wouzer for his getting the started done. Habbie for his support and sqlite research Jemfinch for his more and other ideas of inspiration, see his superb python bot: < dunker> @source <@supybot> dunker: My source is at http://supybot.sf.net/ missing
|
|
|