TODO/bugs in Irssi SILC client
==============================
- o /cumode for unknown nick does not give any error message (Fix this to
- 1.0).
+ o add --with-iconv
+
+ o UTF-8 encode/decode WHOIS userinfos, topic, etc.
+
+ o Testing
TODO/bugs In SILC Client Library
though). This should be added and perhaps new client operation
should be added to notify application that it was received and
set the key only if application wishes to set (accept the key) it
- (Do this to 1.0).
-
- o Remove conn->current_channel.
+ (Do this to 0.9.x).
- o Additions to do after protocol version 1.1:
-
- o Add support for list of errors in command replies. Protocol
- TODO entry 1.
+ o Testing
TODO/bugs In SILC Server
========================
- o Configuration file additions (Do this to 0.8.x):
+ o Implement the <Requested Attributes> and the Attribute Payload to
+ the core library, client and server. Maybe implementations of
+ RFC 2425 and RFC 2426 to make it complete.
- o Add incoming connection frequency, incoming connection frequency
- for single IP address, key exchange frequency, key exchange
- frequency for single IP. Add also frequency base.
+ o Add special handling in router and server for "connection timed out"
+ error. Be optimistic.
- o If server send CUMODE_CHANGE notify (like setting founder) to router
- and router does not have founder on channel (founder is left or there's
- no founder on channel at all), the router will accept the server's
- founder mode change, even though it perhaps should not do that (Fix
- this to 0.9).
+ o Backup router related issues (Fix this to 0.9.x):
- o The router should check for validity of received notify packets from
- routers (fix this to 0.9). Following NOTIFYs needs to be verified:
+ o Complete backup router support with standalone router
- o JOIN (check that joining is allowed)
- o SIGNOFF (maybe should check that notifier owns the client)
+ o Make the backup router work even if not all servers in the
+ cell use it. When primary goes down, also those that are
+ not using it (are not connected locally) are signoffed.
- o Backup router related issues (Fix this to 1.0):
+ o When primary goes down and removing clients of non-backup
+ aware server the SERVER_SIGNOFF includes the router's ID
+ not the server's ID, which it should include. The notify
+ is sent by backup.
- o Channel user mode changes are notified unnecessarely when
- switching to backup router on router crash.
+ o Testing
o Add a timeout to handling incoming JOIN commands. It should be
enforced that JOIN command is executed only once in a second or two
seconds. Now it is possible to accept n incoming JOIN commands
and process them without any timeouts. THis must be employed because
each JOIN command will create and distribute the new channel key
- to everybody on the channel (Fix this to 1.0).
-
- o Lots of statistics updating is missing around the server.
+ to everybody on the channel (Fix this to 0.9.x).
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 Testing
+
TODO/bugs In SILC Libraries
===========================
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 1.0).
+ is not actually async currently (Fix this to 0.9.x).
TODO in Toolkit Documentation
=============================
Stuff that needs to be done in order to complete the Tooolkit Reference
-Manual (Do these to 0.9 and 1.0).
+Manual (Do these to 0.9.x).
o ROBOdoc documenting missing from lib/silcutil/silcbuffer.h.
o ROBOdoc documenting missing from lib/silcutil/silcfileutil.h.
- o ROBOdoc documenting missing from lib/silccrypt/silchash.h.
-
o ROBOdoc documenting missing from lib/silccrypt/silccipher.h.
o ROBOdoc documenting missing from lib/silccrypt/silcpkcs.h.
o Write "Platform Implementations" document to describe what platforms
Toolkit support, what has been implemented, what has not been, what
works differently etc.
-
-
-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
- command reply to the sender. Also define that errors must be sent
- *after* sending successfully found entries (this way receiver may
- ignore them). To be included in protocol version 1.1.
-
- 4. Add "request parameters" or similar to the WHOIS command, which can
- be used to request various parameters (something not returned by
- standard WHOIS command) about clients (info that could be fetched
- even from clients). Additional specification (or appendix) should
- be done to define the payload and the parameters. It could be used
- to make the WHOIS command support various search conditions as well.
- This would be the way to extend the WHOIS command to support various
- new features without always making the command incompatible to previous
- version. To be included in protocol version 1.1.
-
- 17. Cell wide channel founder support, and permanent channels when
- founder mode set.
-
- 20. Services support?
-
- 21. Subscription/IRC's notify kind support?
-
- 22. Session detachment/resume?
-
- 23. Message blocking via user modes (which could be expanded via
- services, but basic blocking would be a feature)?
-
- 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/
projects / silc.git / blobdiff