]>
Commit | Line | Data |
---|---|---|
1 | Nick collision FNC | |
2 | Jilles Tjoelker <jilles -at- stack.nl> | |
3 | -------------------------------------- | |
4 | ||
5 | Nick collision FNC performs a forced nick change to the user's UID instead | |
6 | of a kill. The criteria for which user may keep the nick are the same as | |
7 | before. Server notices will say the clients are being "saved" instead of | |
8 | "killed". The client will get a 043 numeric, like this: | |
9 | :<server> 043 <uid> :Nick collision, forcing nick change to your unique ID | |
10 | ||
11 | The following conditions must be fulfilled: | |
12 | ||
13 | - All servers on the network must allow remote nicks starting with a digit. | |
14 | This is not checked; if this is not fulfilled, users will be killed right | |
15 | after being FNCed. | |
16 | ||
17 | - All servers on the path between the two clients must support TS6 and | |
18 | nick collision FNC (SAVE capab). If this is not fulfilled, the collision is | |
19 | resolved with kills as before. (This uses the ENCAP GCAP data for remotes.) | |
20 | ||
21 | - The general::collision_fnc option must be enabled on the server(s) that | |
22 | detect the collision. | |
23 | ||
24 | Technical details: | |
25 | ||
26 | The following message is used to propagate the nick change coming from the | |
27 | server that detected the collision: | |
28 | ||
29 | :<sid> SAVE <uid> <ts> | |
30 | ||
31 | The TS is compared to the current nick TS for the user; if it is not equal, | |
32 | the message is dropped. This prevents nick desyncs if the user changed their | |
33 | nick after being collided. A SAVE message also generates a server notice to | |
34 | +k. | |
35 | ||
36 | The SAVE message is used for propagation to the target's server, and also | |
37 | in several other cases if the destination supports SAVE. In other cases, a | |
38 | normal nick change or introduction with the UID as nick is sent. | |
39 | ||
40 | -- | |
41 | $Id: collision_fnc.txt 276 2005-10-02 20:23:15Z jilles $ |