Support for SILC 1.2 INVITE and BAN commands. Client supports

[silc.git] / TODO

diff --git a/TODO b/TODO
index 69513cff92b5e5b3f9787cfcdf078525b7ea8cb6..e597065a0c864ce460d4f0cd8221dd4addf81bf9 100644 (file)
--- a/TODO
+++ b/TODO
@@ -1,28 +1,26 @@
-TODO/bugs in Irssi SILC Client
+TODO for Irssi SILC Client 1.0
 ==============================
 
- o UTF-8 encode/decode WHOIS userinfos, topic, etc.
+ o Signed message payload handling on UI
 
- o Manaul file for silc(1) and silc.conf.
+ o Support to set arbitrary pulic key in CMODE
+
+ 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 Remove client from invite lists in KICKED and KILLED.
 
-       o Add special handling in router and server for "connection
-         timed out" error.  Be optimistic.
-
- o Manual file for silcd(8) and silcd.conf.
+ o 1.2 backup router support
 
  o Testing
 
@@ -34,9 +32,6 @@ TODO/bugs In SILC Libraries
    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
 =============================
@@ -44,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