Moved the SilcClient and SilcClientConnection to the public

[silc.git] / TODO-1.0

diff --git a/TODO-1.0 b/TODO-1.0
index 1f821fdec6d46fc5714ef2984521c080f15762c1..a1957118693ac943cb92a0e5f6b0fe826dc05e0c 100644 (file)
--- a/TODO-1.0
+++ b/TODO-1.0
@@ -164,20 +164,3 @@ least could be done.
 
  o Check whether we can fully comply with RFC 2779.
 
-
-TODO in SILC Protocol
-=====================
-
- 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/