AnthroChat "To Do" List:
(Some ideas that have come up and that I think are worthy of implementation)


Web Site:

1.  Integrate read-only functions of the IRC services database into
the web site.  
    a.  Tie all the logins together (forums, polling, and services all
pull from the same authentication database)
    b.  Make current settings and information viewable to nick owners and 
channel founders/successors/admins/ops.

2.  Put the framework in place for a read/write version of the above so
that when Anope gets around to implementing full SQL compatibility, it'll
just work, and we can turn it on for the users.

3.  Include a copy of our mission statement, and clean up the references
to Furnet in the Network sub-section of the "Information" section.

4.  Update the graphical, location map of the servers to include the new 
ones.

5.  Include the parts of the UnrealIRCd documentation which outline user
modes and channel modes for our users to reference without having to dig
through the whole UnrealIRCd manual.

6.  To be more user-interactive, it's been suggested to put up a polling
system on the main page.  Since the forums already have polling ability,
I think we should dynamically create a list of polls for the front page
from the official polls happening on the forums.




--- Services --- 

Nickserv: 

1.  Add a users/announcements mailing list subscription option 
(off, by default).  Users can, at the flick of a switch, subscribe their
confirmed e-mail address to anthrochat-users and/or anthrochat-announce.

2.  Have services pull random guest nicknames from lists in a text file 
instead of just using a random number generator in places where services 
changes a user's nickname to GuestNUMBERS.  Change it to a random 
GuestAdjectiveFurryesquename, like GuestSillySimba or GuestWhiteDragon, 
etc.



Chanserv:

1.  Implement the ability to use the xOP commands while the numeric access
lists are in use.  Each of the xOP add commands should be able to be
user-configurable as to what numeric level in which they add the user.
IE.  vop #channel add user  will add the user at access level 3.



Memoserv:

1.  Allow a user to store a list of nicknames that are not allowed to send 
memos to that user.  (blacklist)

2.  Allow a user to interface memos with their registered e-mail address 
and have the following options:
    a.  e-mail messages once a day.
    b.  An option to e-mail all memos once they reach the max allowed or a 
specified number.
    c.  e-mail every single memo the moment that it's sent.



Hostserv:

1.  Allow users to set their own vhosts with a 30 day wait period between
changes and a 7 day wait period after registering a nickname.  For 10
minutes from the first change, allow one more change in the case of typos.