Skip to content

Commit 44b49ba

Browse files
authored
Explicit that KICK should be relayed (#223)
This is mostly copy-pasted from PART
1 parent 00cbf72 commit 44b49ba

File tree

1 file changed

+5
-1
lines changed

1 file changed

+5
-1
lines changed

_includes/messages/channel.md

+5-1
Original file line numberDiff line numberDiff line change
@@ -253,10 +253,14 @@ Servers MAY allow the `INVITE` with no parameter, and reply with a list of chann
253253

254254
The KICK command can be used to request the forced removal of a user from a channel.
255255
It causes the `<user>` to be removed from the `<channel>` by force.
256+
257+
This message may be sent from a server to a client to notify the client that someone has been removed from a channel. In this case, the message `<source>` will be the client who sent the kick, and `<channel>` will be the channel which the target client has been removed from.
258+
256259
If no comment is given, the server SHOULD use a default message instead.
257260

258-
The server MUST NOT send KICK messages with multiple users to clients.
261+
Servers MUST NOT send multiple users in this message to clients, and MUST distribute these multiple-user `KICK` messages as a series of messages with a single user name on each.
259262
This is necessary to maintain backward compatibility with existing client software.
263+
If a `KICK` message is distributed in this way, `<comment>` (if it exists) should be on each of these messages.
260264

261265
Servers MAY limit the number of target users per `KICK` command via the [`TARGMAX` parameter of `RPL_ISUPPORT`](#targmax-parameter), and silently drop targets if the number of targets exceeds the limit.
262266

0 commit comments

Comments
 (0)