Editing IRC
Jump to navigation
Jump to search
The edit can be undone. Please check the comparison below to verify that this is what you want to do, and then publish the changes below to finish undoing the edit.
Latest revision | Your text | ||
Line 65: | Line 65: | ||
== Channel Defense == | == Channel Defense == | ||
Occasionally, people and programs may generate traffic in the #noisebridge IRC channel with the intent of provoking negative emotional responses. If you currently have operator status in the IRC channel when this happens, use the guidelines | Occasionally, people and programs may generate traffic in the #noisebridge IRC channel with the intent of provoking negative emotional responses. If you currently have operator status in the IRC channel when this happens, use the following guidelines to handle the situation: | ||
* Do not op users if they have not authenticated with NickServ. Check if a user is authenticated with NickServ by sending NickServ the command info <user> in a private message. | * Do not op users if they have not authenticated with NickServ. Check if a user is authenticated with NickServ by sending NickServ the command info <user> in a private message. | ||
* Consider setting +r (only allow users registered with NickServ) and | * Consider setting +r (only allow users registered with NickServ) and -t (only ops can change the topic) on the channel. The overall channel mode should be +npr in this case. Under normal circumstances the channel mode should be +npt. | ||
* Consider using +q (channel-level ignore) instead of +b to silence the provoking users. This allows for users who were mistakenly caught with a hostmask that was too broad to still join the channel and find an op to help troubleshoot. | * Consider using +q (channel-level ignore) instead of +b to silence the provoking users. This allows for users who were mistakenly caught with a hostmask that was too broad to still join the channel and find an op to help troubleshoot. |