Kyoshiro/bip
1
0
Fork 0
forked from bip/bip
Code Pull Requests Activity

Documentation :

Browse Source 
- README.floodcontrol is in README now
This commit is contained in:
Loc Gomez 2008-01-08 10:50:55 +01:00
parent 7ba4297a92
commit 9f9a2e0856
1 changed files with 0 additions and 25 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

25
README.floodcontrol
View File

@ -1,25 +0,0 @@
*** This is a warning about bip's replay/backlog system ***
Bip has a backlogging system which will send back parts of the last logs upon
client connection. Depending on your configuration, that may mean a *lot* of
data sent back to your client.
Users' messages will be replayed as if they were being sent at the moment your
client connects to bip, and if not disabled, system messages will appear as
coming from the "-bip" user.
Considering that, you may want to disable your client's anti-flood system,
totally or not, depending on it's flexibility.
Since bip doesn't replay CTCP messages, you can safely let your client's
anti-flood system manage them.
[Xchat]
If you're using Xchat, you can "disable" it by issuing these commands :
/set flood_msg_num = 1000
/set flood_msg_time = 10
In fact you'll tell xchat to activate its anti-flood system when you're
receiving more than 1000 messages in less than 10 seconds.
If you forgot to set these, private messages may not appear in separate tabs
as usual. If so, simply issue a :
/set gui_auto_open_dialog on