]>
Commit | Line | Data |
---|---|---|
1 | Target Change for Messages | |
2 | Lee H <lee -at- leeh.co.uk> | |
3 | --------------------------- | |
4 | ||
5 | Reworked by Jilles Tjoelker, February 2010. | |
6 | ||
7 | If the server you are using uses the target change mechanism, then | |
8 | restrictions are placed on how many different users you can message in a set | |
9 | timeframe. This also applies to invites. | |
10 | ||
11 | Target change does not apply to channels, ctcp replies, messages to | |
12 | yourself or messages to services. | |
13 | ||
14 | You will have a set number of 'slots', each different client you message | |
15 | will take up one slot. A client doing a nick change will not use a new slot, | |
16 | however a client disconnecting from the server it is on and reconnecting | |
17 | will. You will receive 1 new slot roughly every minute. | |
18 | ||
19 | Additionally, clients that message or invite you are placed in one of a | |
20 | small number of special slots, in many cases allowing replies without using | |
21 | a slot. | |
22 | ||
23 | When all slots are filled, messages to new clients will not be accepted. | |
24 | Messages to clients already filling a slot will be accepted. If all slots | |
25 | are full, you will receive the ERR_TARGCHANGE numeric, number 707 in the | |
26 | form: | |
27 | :<server> 707 <yournick> <targetnick> :Targets changing too fast, message dropped | |
28 | ||
29 | The slots are operated in an LRU (least recently used), so the person you | |
30 | have talked to least recently will be replaced. | |
31 | ||
32 | The number of slots in use will be kept through a reconnection, though the | |
33 | information in those slots will be dropped. However, you will always | |
34 | receive one free slot on a reconnection. Other servers using this mechanism | |
35 | will also be made aware of details about slots. | |
36 | ||
37 | Target change does not apply if you are opped or voiced in a channel, and | |
38 | you are messaging a client within that channel. This can be done explicitly | |
39 | using the CNOTICE and CPRIVMSG commands, see /quote help cnotice and /quote | |
40 | help cprivmsg, but is also implicit in a normal /msg, /notice or /invite. | |
41 | ||
42 | -- | |
43 | $Id: tgchange.txt 6 2005-09-10 01:02:21Z nenolod $ |