a5c46d31e4
Purge a lot of really old and obsolete documents, and merge some together where possible. Lots of efnet docs and the old ircd-ratbox manpage (lol) was purged. Reorganise everything nice and neatly as possible. Things describing features can be found in features/, and some more technical documents were moved to techinical/. Old credits file was consolidated into credits-past.txt, and a reference was added to it in the credits.
43 lines
2 KiB
Text
43 lines
2 KiB
Text
Target Change for Messages
|
|
Lee H <lee -at- leeh.co.uk>
|
|
---------------------------
|
|
|
|
Reworked by Jilles Tjoelker, February 2010.
|
|
Channel target change added by Jilles Tjoelker, August 2010.
|
|
|
|
If the server you are using uses the target change mechanism, then
|
|
restrictions are placed on how many different users and/or channels you can
|
|
message in a set timeframe. This also applies to invites (for the target
|
|
user) and topic changes.
|
|
|
|
Target change does not apply to ctcp replies, messages to yourself, messages
|
|
to services and joins.
|
|
|
|
You will have a set number of 'slots', each different target you message
|
|
will take up one slot. A client doing a nick change will not use a new slot,
|
|
however a client disconnecting from the server it is on and reconnecting
|
|
will. You will receive 1 new slot roughly every minute.
|
|
|
|
Additionally, clients that message or invite you are placed in one of a
|
|
small number of special slots, in many cases allowing replies without using
|
|
a slot.
|
|
|
|
When all slots are filled, messages to new targets will not be accepted.
|
|
Messages to targets already filling a slot will be accepted. If all slots
|
|
are full, you will receive the ERR_TARGCHANGE numeric, number 707 in the
|
|
form:
|
|
:<server> 707 <yournick> <target> :Targets changing too fast, message dropped
|
|
|
|
The slots are operated in an LRU (least recently used), so the person or
|
|
channel you have talked to least recently will be replaced.
|
|
|
|
The number of slots in use will be kept through a reconnection, though the
|
|
information in those slots will be dropped. However, you will always
|
|
receive one free slot on a reconnection. Other servers using this mechanism
|
|
will also be made aware of details about slots.
|
|
|
|
Target change does not apply if you are opped or voiced in a channel, and
|
|
you are messaging that channel or a client within that channel. The latter
|
|
can be done explicitly using the CNOTICE and CPRIVMSG commands, see
|
|
/quote help cnotice and /quote help cprivmsg, but is also implicit in a
|
|
normal /msg, /notice or /invite.
|