Known bugs:
-----------

When kicking users from forbidden channels (or other cases when a user
tries to join an empty channel and is kicked), Services will generate log
messages about "MODE +b for unknown channel".  These are harmless and can
be safely ignored.  The same or similar messages can also appear during a
netburst when modes are sent for a channel after all the users in the
channel have been kicked, or when joins and modes are sent for a user who
gets autokilled.

If you try to enter an empty channel and get kicked and banned by ChanServ,
you cannot get in with UNBAN or INVITE even if you would normally have
privileges to because ChanServ reports that the channel does not exist.
(Reported by Finny Merrill <griever@ircd-net.org>)

There appear to be some cases in which channel modes (+k, +o, and +q have
been reported) are set twice in succession for the same channel.  This
naturally has no effect on the channel itself, but some users have reported
it as annoying.  Services attempts to detect and correct this, but it may
still occur in some cases.

Services appears to incorrectly detect "mode bouncing" (i.e. the IRC server
reversing Services' mode changes) in some cases.  When this occurs,
commands like KICK and TOPIC as well as auto-ops and mode locking will no
longer work on that channel.  If this problem occurs, appropriate messages
will be written to the log file; the problem can be worked around by either
clearing the channel (removing all users from the channel) or restarting
Services.
