+<samp class="highlight">Q: Channel name doesn't have #-character or does it?</samp><br />
+A: The #-character is not mandatory part of channel name, like it is in
+IRC. This means that giving the command /JOIN #silc and /JOIN silc
+will join to different channels. This is intentional since the
+#-character clearly is IRC feature and has nothing to do with SILC. If
+you want it to have the character then just join to the channel with
+#-character in the name.
+<br /> <br />
+
+<a name="f2_130"></a>
+<samp class="highlight">Q: Does SILC support moderated channels?</samp><br />
+A: Yes. Channel founder can moderate both normal users and channel
+operators so that they cannot talk on the channel. It is also possible to
+queit one specific user on the channel if needed.
+<br /> <br />
+
+<a name="f2_140"></a>
+<samp class="highlight">Q: What does the "watching" mean?</samp><br />
+A: You can set a "watch" list for yourself in the server. This means that
+you can watch for certain nicknames in the network. For example, if you
+add a nickname "foo" to the watch list you will be notified when the foo
+logins to the network, leaves the network, changes its user mode or
+changes its nickname. This way you can watch for example when does you
+friend login to the network.
+<br /> <br />
+
+<a name="f2_150"></a>
+<samp class="highlight">Q: Is it possible to reject watching?</samp><br />
+A: Yes. Since it is clear that not everyone wants to be spied on you can
+set a mode for yourself which rejects watching you. Even if someone is
+watching the nickname you have, your logins, logoffs, mode changes or
+nickname changes will not be notified to the watcher.
+<br /> <br />
+
+<a name="f2_160"></a>
+<samp class="highlight">Q: Is it possible to block private
+messages?</samp><br />
+A: Yes. You can block incoming private messages by setting a mode that
+prevents unwanted private messages. Only the private messages that are
+secured with a private message key are delivered to you. This implies
+that you have negotiated the private key with the sender of the message,
+and therefore want to receive messages from that user. Other private
+messages that are secured with normal session keys are dropped when the
+mode is set.
+<br /> <br />
+
+<a name="f2_170"></a>
+<samp class="highlight">Q: Is it possible to block channel
+messages?</samp><br />
+A: Yes it is. By setting a mode that accomplishes this you can prevent
+the server of sending any channel messages to you. There is also a mode
+that allows blocking channel messages from normal users. This means that
+you will receive channel messages only when it is sent by channel operator
+or channel founder. It is also possible to block channel messages sent by
+robots. A user on the channel can have a robot mode set (which means that
+the user is actually a robot program), and messages sent from that user
+can be blocked with the mode.
+<br /> <br />
+
+<a name="f2_180"></a>
+<samp class="highlight">Q: Is it possible to block invites?</samp><br />
+A: It sure is. You can set a mode that prevents the server of sending
+invite notifications to you. This can for example prevent invite
+flooding. The downside is that it may make joining to a invite only
+channels a bit harder.
+<br /> <br />
+
+<a name="f2_190"></a>
+<samp class="highlight">Q: Does SILC support multimedia messages, like
+video/audio streaming?</samp><br />
+A: Yes it does. The new version of the protocol supports sending of MIME
+objects as messages. Since MIME objects can easily represent any kind of
+data, such as video stream, audio stream, images, etc. it is easy to send
+these multimedia messages in SILC. It also makes video conferencing
+possible with SILC. It can work by sending the stream(s) to a channel and
+everybody who joins the channel can receive the stream. This feature in
+the protocol surely makes possible many kind of multimedia applications in
+the future.
+<br /> <br />
+
+<a name="f2_200"></a>
+<samp class="highlight">Q: Is it possible to send picture/image messages?
+</samp><br />
+A: Yes. Since it is possible to send any kind of MIME object as a message
+it is also possible to send pictures and images as messages. It would be
+possible to for example send a hand/mouse written messages.
+<br /> <br />
+
+<a name="f2_205"></a>
+<samp class="highlight">Q: What kind of presence modes SILC
+support?</samp><br />
+A: By presence we mean indication of presence in the network, and SILC
+supports several different kinds of presence modes. They can be changed
+with the UMODE command which changes your user mode in the network.
+Currently there is the following modes for presence: GONE (I'm away),
+INDISPOSED (I cannot be here), BUSY (I'm busy, don't bother me), PAGE
+(page me if you want to talk), and HYPER (I'm hyper active, talk to me).
+When mode is not set it means you are present in the network. There are
+many other user modes as well, but they are not directly related to
+presence indication.
+<br /> <br />
+
+<a name="f2_210"></a>
+<samp class="highlight">Q: Does SILC support anonymity?</samp><br />
+A: The protocol has a user mode which indicates that user is anonymous
+user. The user cannot set or unset the mode itself, but a server which
+provides these anonymous chatting services can set the mode for the user
+that connects to the server. User that has the mode set has their
+username and hostname information scrambled. There are other ways of
+making anonymity in SILC but they all are implementational methods, and
+protocol does not handle those methods.
+<br /> <br />
+
+<a name="f2_220"></a>
+<samp class="highlight">Q: Does SILC support services?</samp><br />
+A: Yes it does. There is command called SERVICE which can be used by
+clients and servers to negotiate a service agreement with a remote server.
+The protocol does not however define any services currently.
+<br /> <br />
+
+<a name="f2_230"></a>