TODO LIST
-------------

Immediate issues:

        * Extended STATUS command: at least list DCCs active.
	
	* Keep track of why detached sessions died and inform users upon
	   failed reattach.
	   
        * auto-detach is a complete mess.
	
	* user-based authentication
	
	* 

        
	* Some errno messages are often wrong (like DCC proxying ends with Operation
	   now in progress)

	* run w/ ccmalloc
	
	* extended information needed for logfile stoppage. Such as,
	  you were killed or the socket error that caused it..
	
	* linkedlist iterator semi-mess. Figure out what to do about it
        
	* Mdidentd doesn't work 
	
	* FreeBSD unix-socket name truncate issue
	
        * on the fly banning and other fun admin tools?


Features that will never be added:

	* File server: it would be cool, but why?
	* Eavesdropping facilities for administrators.
	* Refrigerator: the idea is tempting... but no. No refrigerator.


General issues and features that will hopefully be implemented:

	* Reattach doesn't work on IrcII 2.8.2 (???)
	* Reloading the config file doesn't even touch the listening ports.
	* Support mIRC DCC Resume
	* ALLOWED command, to display where user is allowed to connect.
	* how bout a stupid announcement system to tell users options that
	   have changed after rehashes?
	* rule-set specific options: more specific control over stuff basically.
	* An account system of some sort to save settings and such for users.
	* A Party-line type of thing.
	* Encrypted password support in the config file
	* Turkish documentation. I'd do it but i'm too lazy.
	* mdidentd needs command line options for stuff in defs.h
	* Get it to work in win32 (yeah right ;)
	* A plug-in system..? So people could write their own features. That
	   or a scripting language.. However, I'm not sure what kind of stuff
	   people would write. I'm thinking useless stuff like games. Which
	   reminds me:
	* Everyone loves games. How bout some simple little games to enhance
	   your boring IRC sessions? Like dice rolling or slot machine or 
           hangman or text-based Quake?

	
Technical issues:
	* Modularize the stuff in lib/general.cpp
        * Not all memory allocation failures handled.
	* #include order of header files has caused compile failures
	  on FreeBSD at least. Other systems, i don't know. *Please* let
	  me know if ezbounce will not build on your machine.

	
