9pfs/solanum-vs-hackint-and-charybdis
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

Clarify propagation of JOIN and SJOIN.

Browse source
This commit is contained in:
Jilles Tjoelker 2009-02-06 15:58:02 +01:00
parent 18fc47e681
commit 2d042188c7
1 changed files with 5 additions and 0 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

5
doc/technical/ts6-protocol.txt
View file

@ -270,6 +270,8 @@ exists and has a greater (newer) TS, wipe all simple modes and statuses and
change the TS, notifying local users of this but not servers (note that change the TS, notifying local users of this but not servers (note that
ban-like modes remain intact; invites may or may not be cleared). ban-like modes remain intact; invites may or may not be cleared).
A JOIN is propagated with the new TS of the channel.
KICK KICK
source: any source: any
parameters: channel, target user, opt. reason parameters: channel, target user, opt. reason
@ -648,6 +650,9 @@ this but not servers (invites may be cleared). In the latter case, kick on
split riding may happen: if the key (+k) differs or the incoming simple modes split riding may happen: if the key (+k) differs or the incoming simple modes
include +i, kick all local users, sending KICK messages to servers. include +i, kick all local users, sending KICK messages to servers.
An SJOIN is propagated with the new TS and modes of the channel. The statuses
are propagated if and only if they were accepted.
SJOIN must be used to propagate channel creation and in netbursts. For regular SJOIN must be used to propagate channel creation and in netbursts. For regular
users joining channels, JOIN must be used. Pseudoservers may use SJOIN to join users joining channels, JOIN must be used. Pseudoservers may use SJOIN to join
a user with ops. a user with ops.