doc/tgchange.txt

   1 Target Change for Messages
   2 Lee H <lee -at- leeh.co.uk>
   3 ---------------------------
   4
   5 If the server you are using uses the target change mechanism, then
   6 restrictions are placed on how many different users you can message in a set
   7 timeframe.
   8
   9 Target change does not apply to channels, ctcp replies or messages to
  10 yourself.
  11
  12 You will have a set number of 'slots', each different client you message
  13 will take up one slot.  A client doing a nick change will not use a new slot,
  14 however a client disconnecting from the server it is on and reconnecting
  15 will.  You will receive 1 new slot roughly every minute.
  16
  17 When all slots are filled, messages to new clients will not be accepted.
  18 Messages to clients already filling a slot will be accepted.  If all slots
  19 are full, you will receive the ERR_TARGCHANGE numeric, number 707 in the
  20 form:
  21 :<server> 707 <yournick> <targetnick> :Targets changing too fast, message dropped
  22
  23 The slots are operated as a FIFO (first in, first out), so the first person
  24 you message will be the first person removed from a slot, even if you are
  25 still talking to this person.
  26
  27 The number of slots in use will be kept through a reconnection, though the
  28 information in those slots will be dropped.  However, you will always
  29 receive one free slot on a reconnection.  Other servers using this mechanism
  30 will also be made aware of details about slots.
  31
  32 Target change can be avoided via the CNOTICE and CPRIVMSG commands, when you
  33 are opped or voiced in a channel, and you are messaging a client within that
  34 channel.  See /quote help cnotice and /quote help cprivmsg for more
  35 information.
  36
  37 --
  38 $Id: tgchange.txt 6 2005-09-10 01:02:21Z nenolod $