updates.

[silc.git] / TODO

diff --git a/TODO b/TODO
index afa8ad7445eb2783a697ae0979c0098f038b241b..b5037a6f98d5bc2bc3056c97df74696892e82c76 100644 (file)
--- a/TODO
+++ b/TODO
@@ -102,10 +102,6 @@ Manual (Do these to 0.9 and 1.0).
 TODO in SILC Protocol
 =====================
 
-Current protocol version is 1.0.  However, it is far from being perfect,
-and needs to include additional features.  Following protocol TODO entries
-describe new stuff to be added to protocol versions 1.x.
-
  2. Define that WHOIS and IDENTIFY commands must send list of errors
     if multiple Client ID (or Channel ID and Server ID for IDENTIFY) was
     requested and was not found.  Each unfound entry must cause an error
@@ -129,17 +125,3 @@ describe new stuff to be added to protocol versions 1.x.
  20. Services support?
 
  21. Subscription/IRC's notify kind support?
-
- o Inviting and banning by public key should be made possible.  To be
-   included in protocol version 1.2.
-
- o UTF-8 support/requirement for nicknames & channel names.  UTF-8 support
-   in terminals and OS's are so hazy that this matter is left for
-   consideration in next version of the protocol (1.2).  For good UTF-8
-   reference and tutorial see: http://www.cl.cam.ac.uk/~mgk25/unicode.html.
-   What should CLI application do if it receives nickname that it cannot
-   display without messing up the terminal?  If UTF-8 is mandatory in
-   SILC then SILC clients cannot be allowed to start on terminals that do
-   not support UTF-8 (which renders 98% of users unable to use CLI SILC
-   app without hacking their environment).  See also site
-   http://gratrix.net/unicode/