X-Git-Url: https://jfr.im/git/irc/freenode/web-7.0.git/blobdiff_plain/de97d23449ef27336c57c7ccaf76996e10861372..7e2cfda2a41b44d01c4514ef4f8ac80eb9848314:/content/kb/using/channels.md?ds=sidebyside diff --git a/content/kb/using/channels.md b/content/kb/using/channels.md index 03997179e..0ba1ffb1f 100755 --- a/content/kb/using/channels.md +++ b/content/kb/using/channels.md @@ -1,43 +1,37 @@ -Title: Channels ---- - -Channel Policies -================ - -In general, local policy and rules for each channel are set by that channel's operators. While we encourage all channel operators to adopt our [channel -guidelines](/pages/changuide), if a project or community decides to operate otherwise then we respect their decisions. If you believe that the way in which a -particular channel is run contravenes our [ground rules](/pages/policies) or runs counter to the freenode [philosophy](/pages/philosophy) then you should raise -your concerns first with the channel owners, and then with freenode staff who will address cases on an individual basis. - -Why can't I join a channel? -=========================== - -There are several things that might prevent you from joining a particular channel. In most cases the server will tell you the reason, but some clients do not -correcntly display that information to you, so it's useful to be able to check for yourself. Some of the common causes, in no particular order, are: - - * Check that you're logged in with services. You can log in by running `/msg NickServ IDENTIFY YourNickname YourPassword`. - - Some channels use mode `+r`, which prevents unregistered users, or users who aren't logged in, from joining. - * Check whether the channel has modes `+i` or `+k` set. These will prevent anyone from joining who isn't explicitly invited or doesn't know the channel password. - * Check whether mode `+j` is set. This is a join throttle, which prevents lots of users from joining in a short period of time. If this is the case, it might - be worth trying again after a minute or two, to see whether the join throttle is the reason. - * If you are logged in to services, check the channel ban list -- you can do this using `/mode #channel b`. - - If you've not been in the channel in question recently, it's possible that you're affected by a wide-ranging ban, so pay attention to any bans that include - `*` or `?` wildcards. Bans that begin with a `$` sign are extended ban types; you can see more information about these by sending the `HELP EXTBAN` command - on IRC. - - If you find a ban which matches you but you feel wasn't intended to keep you out, then talk to one of the channel operators to see about having it removed. - You can find a list of channel operators via the `/msg ChanServ ACCESS #channel LIST` command. - -If you're still stuck, feel free to ask a staff member for help in working out what's preventing you from joining. - - -Why can't I talk in a channel? -============================== - -The two most common causes for this are either a quiet mask -- use `/mode #channel q` to see the list and then check the advice above regarding bans -- or mode -`+m`, which prevents anyone who isn't voiced from talking. If you're still unsure, again, feel free to ask staff for help in working out what the problem might -be. - - +Title: Channels +--- + +Channel Policies +================ + +In general, local policy and rules for each channel are set by that channel's operators. While we encourage all channel operators to adopt our [channel +guidelines](pages/changuide), if a project or community decides to operate otherwise then we respect their decisions. If you believe that the way in which a +particular channel is run contravenes our [ground rules](pages/policies) or runs counter to the freenode [philosophy](pages/philosophy) then you should raise +your concerns first with the channel owners, and then with freenode staff who will address cases on an individual basis. + +Why can't I join a channel? +=========================== + +There are several things that might prevent you from joining a particular channel. In most cases the server will tell you the reason, but some clients do not +correctly display that information to you, so it's useful to be able to check for yourself. Some of the common causes, in no particular order, are: + +* Check that you're logged in with services. You can log in by running `/msg NickServ IDENTIFY YourNickname YourPassword`. + Some channels use mode `+r`, which prevents unregistered users, or users who aren't logged in, from joining. +* Check whether the channel has modes `+i` or `+k` set. These will prevent anyone from joining who isn't explicitly invited or doesn't know the channel password. +* Check whether mode `+j` is set. This is a join throttle, which prevents lots of users from joining in a short period of time. If this is the case, it might be worth trying again after a minute or two, to see whether the join throttle is the reason. +* If you are logged in to services, check the channel ban list -- you can do this using `/mode #channel b`. + +If you've not been in the channel in question recently, it's possible that you're affected by a wide-ranging ban, so pay attention to any bans that include `*` or `?` wildcards. Bans that begin with a `$` sign are extended ban types; you can see more information about these by sending the `/quote HELP EXTBAN` command on IRC. + +If you find a ban which matches you but you feel wasn't intended to keep you out, then talk to one of the channel operators to see about having it removed. +You can find a list of channel operators via the `/msg ChanServ ACCESS #channel LIST` command. + +If you're still stuck, feel free to ask a staff member for help in working out what's preventing you from joining. + + +Why can't I talk in a channel? +============================== + +The two most common causes for this are either a quiet mask -- use `/mode #channel q` to see the list and then check the advice above regarding bans -- or mode `+m`, which prevents anyone who isn't voiced from talking. If you're still unsure, again, feel free to ask staff for help in working out what the problem might be. + +