Volgens de grote Van Dale (2005) betekent gozer ‘kerel’ of ‘vent’ en dat is
juist, maar daarmee is de gevoelswaarde niet uitgedrukt. Een gozer is
doorgaans een toffe vent. Een jongen van de gestampte pot. Een gozer is een
bink – waarschijnlijk iemand, zo wil de romantische voorstelling, met een
grote bek en een klein hartje.
Hello world !
I 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
- a shell
- python 2.5 or higher
- sqlite3 (already in 2.7)
- optional is SQLAlchemy support .. enable this in gozerdata/mainconfig .. (set db_driver to “alchemy”) .. needs python sqlalchemy driver.
- download here http://gozerbot.org/download/gozerbot-1.0.1.tar.gz
- or see http://gozerbot.googlecode.com
- or clone the mercurial repo at https://gozerbot.googlecode.com/hg
- GOZERBOT is free code (BSD) and can be cloned where needed.
!! make a separate user and group for the bot !!
wget the latest code from http://gozerbot.googlecode.com/
untar it
cd into the bot dir and run the following:
- IRC
./bin/gozerbot -o <userhost of the owner> -s <server> -c <\#channel>notice the thats for escaping the # in the channel name
- Jabber / XMPP
the self register code in GOZERBOT is not working yet, so you have to register a user for the bot yourself
./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
you 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>gozerplugs 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
you can user the !plug-enable -a command to load all plugins
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
- we are on #dunkbots Freenode
- MAKE REGULAR BACKUPS OF YOUR BOT DIRECTORY
- main site and docs - http://gozerbot.org
- source - http://gozerbot.googlecode.com/hg
- development - http://jsonbot.googlecode.com
- HANDBOOK
- BASIC
- FAQ
- FLEET
- FLOW
- INSTALL
- JABBER
- OPER
- joining a channel
- parting a channel
- show ps line of the bot
- show running threads
- quiting the bot
- rebooting the bot
- see what plugins are installed
- reloading a plugin
- get help on a plugin
- upgrading
- installing remote plugins
- when you want to add new users to the database
- deleting a user
- to see if there is already a record in the database
- merging a user
- show the users of the bot
- getting the userhosts of an user
- adding userhosts to an existing user
- get help about the user plugin
- getting/setting the control character of a channel
- get an alias
- set an alias
- RELAY
- RSS
- first check if you have RSS permission
- if this is not the case add it
- see which rss commands the bot has with
- you will want to add a url to the RSS system, we use slashdot as an example
- see if the url works
- to let the bot check for updates
- see if the thread is running
- if you want to stop watching
- see what other data the rss feed has to offer
- so if we also want for example the link field added
- poll time
- TOURDECODE
- UDP
- UPGRADE
- USER
- plugins documentation
- core
- base
- 8B
- ALARM
- AUTOREPLY
- AUTOVOICE
- AWAY
- BANNER
- BASH
- BEATS
- BENDER
- BOTSNACK
- BUGTRACKER
- BUZZ
- CHATLOG
- COUNTRY
- DNS
- DOPE
- DRINKS
- ECHO
- EVENT
- FACTS
- FANS
- GCALC
- GCOLLECT
- GRAB
- GREETING
- HELLO
- HEX2IP
- HEXJOIN
- HTTPWATCH
- IDENTI
- IDENTIFY
- IDLE
- IPCALC
- KICKBAN
- LAG
- LART
- LINKS
- LNS
- LOG
- MAILEXCEPTIONS
- MARKOV
- MPD
- ONELINER
- OPS
- PIT
- POWERNICK
- PROBE
- PROJECTTRACKER
- RBLCHECK
- REGISTER
- RELAY
- REMIND
- RSS
- SEARCH
- SED
- SEEN
- SHAKESPEAR
- SHOP
- SHOUTCAST
- SNARF
- TCP
- TEL
- TIMEBOMB
- TIMER
- TINYURL
- TOPIC
- TRANSLATE
- UDP
- UMODE
- URBAN
- URL
- URLINFO
- WEATHER
- WHOIS
- WIKIPEDIA
- WIKIQUOTE
- WISDOM
- WOWWIKI
- YAHOO
- olddb
Special thnx goes out to Annemiek, Danny, Kirsten, Doscha and my parents Anneke and Thies. They made me possible and this bot to begin with.
;]
- #xs4all on irc.xs4all.nl
- #dudinet on irc.dudi.org
- #linux.nl on irc.xs4all.nl
- #freebsd.nl on irc.xs4all.nl
- #cable-gang on irc.xs4all.nl
- #dunkbots on irc.xs4all.nl
- #fifo on irc.fifo.nl
- #trac on irc.freenode.net
- #mononoke on irc.mononoke.net
- #dunkbots on irc.freenode.net
- #dragonflybsd on efnet.xs4all.nl
I 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 ;]
Aim 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
maze 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 ;]
trbs 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 ;]
In 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 ;]
Now 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 ;]
qirtaiba 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 ;]
snore 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.
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 http://youtu.be/lDIxfHlgL4Q
budy 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 ;]
Rex is the ever aware always present never leaving aroundness that is here to shine on my path ;] Lots lots of testing done for GOZERBOT
DJMuggs 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
Arc 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 ;]
Wiebel 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.
Knorrie has been helping me out testing the Jabber (xmpp) part of the bot. Many many hours of debugging together, including hooking nagios up into the bot.
Antarez is one of the buddies being there from the early (#linux.nl) days. As a bot sceptic, it was fun to try the silent mode in the #bbq channel. Couldn’t get the channel to accept bots though ;]
kristall was there also from the beginning, programming plugins and testing the bot for me. Still there is the #dunkbots channel ;]
Laagje 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/
- Andre Drijver
- Harm Oerlemans
- Rinaldo Sikking
- pacopablo
- anarcat
- snore !!
- gozerbot.admin
- gozerbot.aliases
- gozerbot.botbase
- gozerbot.cache
- gozerbot.callbacks
- gozerbot.channels
- gozerbot.commands
- gozerbot.config
- gozerbot.datadir
- gozerbot.dbusers
- gozerbot.eggs
- gozerbot.eventbase
- gozerbot.eventhandler
- gozerbot.examples
- gozerbot.exit
- gozerbot.fleet
- gozerbot.generic
- gozerbot.gozerimport
- gozerbot.ignore
- gozerbot package
- gozerbot.jsonusers
- gozerbot.less
- gozerbot.monitor
- gozerbot.morphs
- gozerbot.partyline
- gozerbot.periodical
- gozerbot.plughelp
- gozerbot.plugins
- gozerbot.reboot
- gozerbot.redispatcher
- gozerbot.runner
- gozerbot.sausers
- gozerbot.stats
- gozerbot.tests
- gozerbot.users
- gozerbot.wait
- gplugs.8b
- gplugs.alarm
- gplugs.autoreply
- gplugs.autovoice
- gplugs.away
- gplugs.banner
- gplugs.bash
- gplugs.beats
- gplugs.bender
- gplugs.botsnack
- gplugs.bugtracker
- gplugs.buzz
- gplugs.chatlog
- gplugs.country
- gplugs.dns
- gplugs.dope
- gplugs.drinks
- gplugs.echo
- gplugs.event
- gplugs.facts
- gplugs.fans
- gplugs.gcalc
- gplugs.gcollect
- gplugs.grab
- gplugs.greeting
- gplugs.hello
- gplugs.hex2ip
- gplugs.hexjoin
- gplugs.httpwatch
- gplugs.identi
- gplugs.identify
- gplugs.idle
- plugins documentation
- gplugs.ipcalc
- gplugs.kickban
- gplugs.lag
- gplugs.lart
- gplugs.links
- gplugs.lns
- gplugs.log
- gplugs.mail
- gplugs.mailexceptions
- gplugs.markov
- gplugs.mpd
- gplugs.oneliner
- gplugs.ops
- gplugs.pit
- gplugs.powernick
- gplugs.probe
- gplugs.projecttracker
- gplugs.rblcheck
- gplugs.register
- gplugs.relay
- gplugs.remind
- gplugs.rss
- gplugs.search
- gplugs.sed
- gplugs.seen
- gplugs.shakespear
- gplugs.shop
- gplugs.shoutcast
- gplugs.snarf
- gplugs.tcp
- gplugs.tel
- gplugs.timebomb
- gplugs.timer
- gplugs.tinyurl
- gplugs.topic
- gplugs.translate
- gplugs.udp
- gplugs.umode
- gplugs.urban
- gplugs.url
- gplugs.urlinfo
- gplugs.weather
- gplugs.whois
- gplugs.wikipedia
- gplugs.wikiquote
- gplugs.wisdom
- gplugs.wowwiki
- gplugs.yahoo
- gplugs.olddb.birthday
- gplugs.olddb
- gplugs.olddb.infoitem
- gplugs.olddb.karma
- gplugs.olddb.lists
- gplugs.olddb.quote
- gplugs.olddb.todo
- gplugs.olddb.user