Support for SILC 1.2 INVITE and BAN commands. Client supports

[silc.git] / TODO

diff --git a/TODO b/TODO
index 4b03ae96814a2b4300e67b515a9e6e479f7bba1d..e597065a0c864ce460d4f0cd8221dd4addf81bf9 100644 (file)
--- a/TODO
+++ b/TODO
@@ -1,30 +1,26 @@
-TODO/bugs in Irssi SILC Client
+TODO for Irssi SILC Client 1.0
 ==============================
 
- o bugs parsing nicknames with @ in NICK_CHANGE.
+ o Signed message payload handling on UI
 
- o UTF-8 encode/decode WHOIS userinfos, topic, etc.
+ o Support to set arbitrary pulic key in CMODE
 
- o Manaul file for silc(1) and silc.conf.
+ o INVITE/BAN by public key file and Client ID, new INVITE/BAN list handling
+   in command reply.
+
+ o bugs parsing nicknames with @ in NICK_CHANGE
 
  o Testing - See test plan:
      http://silcnet.org/docs/silc-client-1.0-test.pdf
      http://silcnet.org/docs/silc-client-1.0-test.ps
 
 
-TODO/bugs In SILC Server
+TODO for SILC Server 1.0
 ========================
 
- o If client's public key is saved in the server (and doing public key
-   authentication) then the hostname and the username information could
-   be taken from the public key.  Should be a configuration option!
-
- o Backup router related issues:
-
-       o Add special handling in router and server for "connection
-         timed out" error.  Be optimistic.
+ o Remove client from invite lists in KICKED and KILLED.
 
- o Manual file for silcd(8) and silcd.conf.
+ o 1.2 backup router support
 
  o Testing
 
@@ -32,15 +28,10 @@ TODO/bugs In SILC Server
 TODO/bugs In SILC Libraries
 ===========================
 
- o Get rid of VERSION, PACKAGE and other autoconf stuff from silcdefs.h.
-
  o WIN32 silc_net_create_connection_async does not work the same way
    than on Unix.  Do it with threads on WIN32.  The function works but
    is not actually async currently (Fix this to 0.9.x).
 
- o Private key encryption to silc_pkcs_[save/load]_private_key[_data]
-   function.
-
 
 TODO in Toolkit Documentation
 =============================
@@ -48,6 +39,9 @@ TODO in Toolkit Documentation
 Stuff that needs to be done in order to complete the Tooolkit Reference
 Manual (Do these to 0.9.x).
 
+ o Document the "notify" and "command_reply" client operations variable 
+   argument lists for all possible notify types and command replys.
+
  o Write "Programming with Toolkit" document, describing how to build
    Toolkit, how the build system works, where is everything, how
    new (external) projects can be glued into Toolkit (use irssi as an