Sent when an client is invited to a channel. This is also sent
when the invite list of the channel is changed. This notify type
- is sent between routers and if the <Client ID> is argument is
- provided to the client as well. In this case the packet is
- destined to the client.
+ is sent between routers and if an client was invited to the
+ client as well. In this case the packet is destined to the client.
Max Arguments: 5
Arguments: (1) <Channel ID> (2) <channel name>
and the <removing client> is defined in the [SILC1] with
SILC_COMMAND_INVITE command.
- The <adding client> and <removing client> is never sent to the
- client indicated by the <Client ID>.
+ The <adding client> and <removing client> is never sent when the
+ packet is destined to a client.
2 SILC_NOTIFY_TYPE_JOIN
Arguments: (1) [<Client ID>] (2) <Channel ID>
The <Client ID> is the client that joined to the channel indicated
- by the <Channel ID>. The <adding client> and <removing client>
- indicates the added or removed client in the current invite list.
- The format of the <adding client> and the <removing client> is
- defined in the [SILC1] with SILC_COMMAND_INVITE command. If the
- <Client ID> is not provided then this
+ by the <Channel ID>.
3 SILC_NOTIFY_TYPE_LEAVE
the clients who is joined on the channel whose mode was changed.
Max Arguments: 4
- Arguments: (1) <Client ID> (2) <mode mask>
+ Arguments: (1) <ID Payload> (2) <mode mask>
(3) [<cipher>] (4) <[hmac>]
- The <Client ID> is the client who changed the mode. The <mode mask>
- is the new mode mask of the channel. The client can safely ignore
- the <cipher> argument since the SILC_PACKET_CHANNEL_KEY packet will
- force the new channel key change anyway. The <hmac> argument is
- important since the client is responsible of setting the new HMAC
- and the hmac key into use.
+ The <ID Payload> is the ID (usually Client ID but it can be Server ID
+ as well when the router is enforcing channel mode change) of the
+ entity which changed the mode. The <mode mask> is the new mode mask
+ of the channel. The client can safely ignore the <cipher> argument
+ since the SILC_PACKET_CHANNEL_KEY packet will force the new channel
+ key change anyway. The <hmac> argument is important since the client
+ is responsible of setting the new HMAC and the hmac key into use.
8 SILC_NOTIFY_TYPE_CUMODE_CHANGE