+Sat Apr 27 19:52:32 EEST 2002 Pekka Riikonen <priikone@silcnet.org>
+
+ * Added new QUIET channel user mode that can be used to
+ quiet a user in a channel. Updated the protocol specs but
+ it wasn't implemented yet. Protocol TODO #27. Affected
+ file is lib/silccore/silcmode.h.
+
Mon Apr 22 09:09:44 CEST 2002 Pekka Riikonen <priikone@silcnet.org>
* Added BLOCK_INVITE user mode to be able to block incoming
o JOIN (check that joining is allowed)
o SIGNOFF (maybe should check that notifier owns the client)
+ o Implement the SILC_CUMODE_QUIET user mode (Do this to 0.9.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 Backup router related issues (Fix this to 1.0):
o Channel user mode changes are notified unnecessarely when
17. Cell wide channel founder support, and permanent channels when
founder mode set.
-
- 24. Implement the <Requested Attributes> and the Attribute Payload to
- the core library, client and server.
-
- 27. Quiet user mode to quiet a user on channel, settable by chan
- op/founder?
0x00000010 SILC_CUMODE_BLOCK_MESSAGES_ROBOTS
Marks that the client wishes not to receive any channel
- messages sent from robots. Messages sent by Users with
+ messages sent from robots. Messages sent by users with
the SILC_UMODE_ROBOT user mode set are not delivered.
Client MAY set and unset this mode to itself. Client MUST
NOT set it to anyone else. When this mode is set server
to this client.
+ 0x00000020 SILC_CUMODE_QUIET
+
+ Marks that the client cannot talk on the channel. This
+ mode can be set by channel operator or channel founder to
+ some other user that is not operator or founder. The
+ target client MUST NOT unset this mode. When this mode
+ is set the server MUST drop messages sent by this client
+ to the channel.
+
+
Reply messages to the command:
Max Arguments: 4
The <Client ID> is the user's Client ID which is being watched,
and the <nickname> is its nickname. If the client just
- changed the nickname, then <nickname> is the new nickname.
- The <user mode> is the user's current user mode. The <Notify
- Type> can be same as the Notify Payload's Notify Type, and is
- 16 bit MSB first order value. If provided it may indicate the
- notify that occurred for the client. If client logged in to the
- network the <Notify Type> MUST NOT be present.
+ changed the nickname, then <nickname> is the new nickname, but
+ the <Client ID> is the old client ID. The <user mode> is the
+ user's current user mode. The <Notify Type> can be same as the
+ Notify Payload's Notify Type, and is 16 bit MSB first order value.
+ If provided it may indicate the notify that occurred for the
+ client. If client logged in to the network the <Notify Type>
+ MUST NOT be present.
.in 3
Notify types starting from 16384 are reserved for private notify
users */
#define SILC_CHANNEL_UMODE_BLOCK_MESSAGES_ROBOTS 0x00000010 /* Block messages
from robots */
+#define SILC_CHANNEL_UMODE_QUIET 0x00000002 /* user is quiet */
/***/
/****d* silccore/Modes/SilcUserMode