                                What's New
               =============================================
               Summaries of changes in new Services versions


------------
Version 3.1:
------------

  + A limit can be set on the number of memos a nick can keep, and the
	limit can be varied or removed on a per-nick basis.
  + A limit can be set on the maximum number of channels a nick can
	register.  (This is not yet settable on a per-nick basis.)
  + The permissible frequency of use of the MemoServ SEND command can be
	set to prevent (or at least limit) memo flooding; for example, the
	default configuration prevents users from using the SEND command
	more often than once every five seconds.
  + OperServ autokills can be set to expire after a certain period of time,
	and can default to either not expiring or to having a certain
	duration.
  + Clone detection actually works now.
  + Slightly increased protocol support: basic support for ircd.dal 4.4.x
	(x >= 15) is now present, as is support for the ircu GLINE command.
	Services should also work better with classic irc2.x servers.
  + Many, many bugs fixed, as usual.  Also removed a typo in os-help.c that
	somehow made it into the 3.0.10 distribution.


------------
Version 3.0: (changes since 2.2.26)
------------

  + ChanServ access levels can finally be customized!  ChanServ has a new
	command, LEVELS, which allows the numeric access levels to be
	fine-tuned for each channel.  There are 11 settings available,
	each of which corresponds to a particular ChanServ command or
	function; for example, one can set the level at which users are
	automatically opped, and one can define a level at which users
	are to be automatically voiced as well.
  + Channel access lists may now only contain registered nicknames; this
	allows Services to run much faster and simplifies channel access
	checks.
  + Services admins can now view channel access and autokick lists and
	nickname access lists.
  + Read-only mode can now be set (and unset) both from the command line
	and during operation.
  + Numerous bugs, memory leaks, and potential security holes squashed.
