* Opers with a small o in their O:Line flags were being propagated as a big O
* New command line option -x is for 'network debug' which will verbosely spit
  out synch info to the network via GLOBOPS.  This will spam a network like
  crazy, so please don't use it unless you've been instructed to.  This is to
  assist in debugging of misbehaving servers (read: software) over the network.
* Rewrote this.setusermode(), because it was a mess.
* Began work on breaking out usermodes into more discrete sections ala Bahamut,
  in particular:
        +w (Users) Allows the user to receive all WALLOPS messages.
        +b (Opers) User may receive CHATOPS messages.
        +g (Opers) User may receive GLOBOPS messages.
        +s (Users) Reception of variou server messages, including KILL.
        +c (Opers) Receive client connecting/disconnecting messages.
        +r (Opers) Receive 'rejected' client messages (i.e. unregd clients)
        +k (Opers) Receive server kill messages.
        +y (Opers) Observe STATS/INFO/LINKS/etc requests for possible abuse.
        +d (Opers) Can receive DEBUG notices.
        +n (Opers) For reception of 'routing' notices.
* Because of this, WALLOPS is now an oper only command.
* Replaced oper_notice() with umode_notice(), which writes out to all users
  of a particular user mode.
* CHATOPS, GLOBOPS, and GNOTICE now all work properly.
* Some appropriate messages are broadcast across the network, including more
  informative server messages (i.e. remote CONNECT, SQUIT, etc.)
* Let other opers know that a user is doing /EVAL.
* Add a kludge for 3.10 machines so that they'll mswait() longer, thus won't
  time out as quickly, hopefully giving them at least a few weeks worth of
  uptime.  The downside to this is that they run slower, alas.  (They probably
  should anyway, considering they don't have select() to throttle CPU usage.)

flags as they relate to QWK-masters and the routing thereof.

* Support complex /LIST syntax.  Similar to Bahamut's in concept, but entirely    different in implementation.  Functions more like complex /WHO, do a /LIST ?
  for usage information.
* Don't show channel topics on +p channels in /LIST.

  /WHO +c @#channel, +#channel, @+#channel, etc.
* New /WHO option: +l <class>, check for users only in a certain IRC class.
* New /WHO option: +t <time>, user has been on for more (+) or less (-) than
  <time> seconds.
* New /WHO option: +I for returning only IP addresses as opposed to hostnames.
--- Ideas for a lot of the new WHO flags came from Bahamut 1.4.36, thanks guys!

HTML pages from ANSI/CTRL-A text.

For use as an external chat pager (alternative to tone/playtone.js).

sbbs->terminated is now a BOOL (instead of bool).

not compatible with a C BOOL (int) pointer, so all js.terminated tests from JS
modules run from the BBS failed (always returned true).

(using JS_ValueToInt32 instead of JSVAL_TO_INT).

offset (which it is not), causing most message index "gets" by offset to fail.

don't proceed to this.work()

added.

(I always wanted to do that commit!)

and for system.clock_ticks

frequency of MSCLOCKS_PER_SEC... the initial value is undefined.

Fixed 100% CPU if no clients to poll or socket_select is not defined (v3.10).

  race conditions where some servers would think that a nick exists when we're
  in the process of sending it a KILL message or similar.
* User modes weren't propagating beyond servers one hop deep.
* Fixed up /WHO, the complex syntax wasn't working sometimes, and wasn't
  passing along to the correct function in some cases.

service scripts are executed - fixes if(this.method==undefined) checks.

connect properly.

  reporting this one.
* Fix a bug involving 3.10 and socket_select being undefined after a user
  object is killed.