Moved silc_client_ch[u]mode[_char] to client library from silc/.

[silc.git] / doc / FAQ

diff --git a/doc/FAQ b/doc/FAQ
index 18cd9e7af2c93bb9f7d38c4d0957fa860468b721..44d9056616ea846ee217ec0b40335a980a4c70da 100644 (file)
--- a/doc/FAQ
+++ b/doc/FAQ
@@ -4,13 +4,12 @@ Frequently Asked Questions
 Q: What is SILC?
 A: SILC (Secure Internet Live Conferencing) is a protocol which provides
    secure conferencing services in the Internet over insecure channel.
-   SILC is IRC like although internally they are very different.  Biggest
-   similiarity between SILC and IRC is that they both provide conferencing
-   services and that SILC has almost same commands as IRC.  Other than
-   that they are nothing alike.
-
-   Biggest differences are that SILC is secure what IRC is not in any
-   way.  The network model is also entirely different compared to IRC.
+   SILC superficially resembles IRC although internally they are very
+   different.  Biggest similarity between SILC and IRC is that they both
+   provide conferencing services and that SILC has almost same commands
+   as IRC.  Other than that they are nothing alike.  Biggest differences
+   are that SILC is secure what IRC is not in any way.  The network model
+   is also entirely different compared to IRC.
 
 
 Q: Why SILC in the first place?
@@ -30,8 +29,14 @@ A: SILC still has a lot things to do.  The time of completion is much
 Q: Why use SILC? Why not IRC with SSL?
 A: Sure, that is possible, although, does that secure the entire IRC
    network? And does that increase or decrease the lags and splits in
-   the IRC network?  SILC is not meant to be IRC replacement.  IRC is
-   good for some things, SILC is good for same and some other things.
+   the IRC network?  Does that provide user based security where some
+   specific private message are secured.? Does that provide security
+   where some specific channel messages are secured?  Security is not
+   just about applying encryption to traffic and SILC is not just about
+   `encrypting the traffic'.  You cannot make insecure protocol suddenly
+   secure just by encrypting the traffic.  SILC is not meant to be IRC
+   replacement.  IRC is good for some things, SILC is good for same and
+   some other things.
 
 
 Q: Can I use SILC with IRC client?  What about can I use IRC with SILC
@@ -44,6 +49,21 @@ A: Answer for both question is no.  IRC client is in no way compatible
    That just is not possible.
 
 
+Q: Why client/server protocol is based on IRC? Would it be more
+   interesting to implement something extensible and more powerful?
+A: They are not, not the least.  Have you read the protocol
+   specification?  The client superficially resembles IRC client but
+   everything that happens under the hood is nothing alike IRC.  SILC
+   could *never* support IRC because the entire network toppology is
+   different (hopefully more scalable and powerful).  So no, SILC protocol
+   (client or server) is not based on IRC.  Instead, I've taken good
+   things from IRC and leaved all the bad things behind and not even tried
+   to burden myself with the IRC caveats that will burden IRC and future
+   IRC projects til the end.  SILC client resembles IRC client because it
+   is easier for new users to start using SILC when they already know all
+   the commands.
+
+
 Q: Why SILC? Why not IRC3?
 A: Question that is justified no doubt of that.  I didn't start doing SILC
    to be replacement for IRC.  SILC was something that didn't exist in