- Did some code cleanup based on profiling information
- Added an additional check to clonechannel()
- Added a BUGREPORTING file that contains instructions
  on how to send comprehensive bug reports
- Implemented add & del chanflags (you just give the
  flags you want to set or remove, not all of them)
- Changed del channel command so that it allows you to
  specify which channel to delete when sending the
  command to the channel
- Added devoice command
- Restored multiple modes
- Added support for services, this works just like
  the Q friendly mode except you can have several hosts
  (the global flag for services is "s")
- Rewrote processenv() and some related functions
- Backported pre_install.sh from oer+MySQL (allows you
  to make your initial configuration in "make install")
- Did some additional code cleanup
- The default for oer is now to have no debug messages,
  you will have to specify --enable-debug to configure
  if you want the messages (the size reduction of the
  optimized & striped binary vs. the binary with debug
  messages & symbols is about 70%)
- Added a TODO file (always first look at the TODO
  before suggesting anew feature)
- Added global flag "m" to make oer send messages
  instead of notices (not preferred)
- Added a validity check when adding new channels
- Fixed a bug in authorization checking (for example
  if you had a "dfv" user with *@* and a bunch of
  "o" users with their respective masks, the *@* mask
  would get matched for the "o" users)
- There was a memory leak when deleting a user with
  a password or removing the "d" flag from a user, fixed
- Changed the way list chanflags works: you will from
  now on have to specify "verbose" as a argument to
  list chanflags if you want the verbose listing
- Implemented server statistics (sstats)
- The stoned server checking was obviously broken and
  has always been (now only activity from server is
  counted as activity -- you may have to change your
  server ping frequencies to something more realistic,
  see /trace <nick> for the server class then see
  /stats y to see the respective Y: line, the ping
  frequency is the 2nd parameter for the Y:line)