GeekShed IRC Network
I’ve Been Banned from a Channel!
Oct 12th
On GeekShed, channel moderators are free to ban anyone from channels they control for any reason at all. They do not need to explain the reason, and they do not have to be “fair.” Since every channel is different, you need to look at the situation and figure out the best approach:
- Check your ban and/or kick message for details on what went wrong. When someone bans you from a channel, you may find the reason in that message. If there are appeal instructions there, you can follow them if appropriate.
- In some channels, you can just wait the ban out. In channels where basic bans are only 3 hours, waiting is probably the best solution.
- Look at the Channel Appeals page for an appeal process for the channel.
- Follow the instructions if the channel is listed. Wait for channel staff to reply.
- If the channel isn’t listed, they have no appeal process. If you are in another channel with the person who banned you, you can ask him if you can talk to him privately.
- When you post an appeal or ask about a ban, be polite and respectful. Apologize if you have broken channel rules, and calmly explain why you think the ban should be lifted. You might review the guidelines on Manners and Polite Behavior on GeekShed as well as any rules posted for the channel itself.
- If the ban stands or cannot be appealed, just accept it and move on. Don’t try to force your way into channels where you are not wanted.
And a few don’ts:
- Do not complain or ask about the ban in other channels (that includes #help).
- Do not PM network staff. Opers will not get involved in channel bans.
- Do not post complaints or arguments in the GeekShed network forums. You’ll just get yourself banned from the forums as well. It’s okay to post in a channel forum specifically for appeals, if one exists (for instance, as in the case of #chris or #ericjess).
- Do not rejoin the channel until the ban is lifted. Do not use a BNC, a new connection or alternate nick to rejoin. These actions are ban evasion and you will be banned from the entire network, not just the channel.
If you happen to be looking for information on a ban from the GeekShed network (rather than from a channel), please check the Ban Appeals page.
—posted by Tengrrl/Bunny
Setting More Specific Channel Bans
Oct 6th
Last week, I explained how to set a simple channel ban that takes care of most situations. Occasionally, you need a stronger or different kind of ban. This week I’ll explain the more complicated channel bans that you can use. Check the Extended Ban tutorial for additional options.
First, you need to understand the different parts of a person’s connection information, which you can find using the WHOIS command. This is the way that information is included in a ban:
nick!ident@specific-hostmask.domain-info
Here is what that information means, with examples from the WHOIS information for LordBaconCheeseburger, which is ~TFlash@protectedhost-BACONYUM.hsd1.ga.comcast.net:
- nick = the user’s nickname
LordBaconCheeseburger in our example
- ident = the user information, either set by the client or set by the user in the client’s settings
TFlash in our example
- specific-hostmask = the unique part of the person’s network connection information
protectedhost-BACONYUM in our example
- domain-info = the more general information about the network connection
hsd1.ga.comcast.net in our example
You can set a ban using any of this information. The basic format stays the same. You simply vary the unique information necessary to identify a person. I’ll provide examples for several options below:
To ban someone who uses a specific nick: /mode #channel +b nick!*@* For example, to ban anyone using the nick LordBaconCheeseburger from the channel #topgear, you would use this command: /mode #topgear +b LordBaconCheeseburger!*@*
To ban someone whose nick changes slightly: You can also use the * as a wildcard in the nickname. Say the person has a habit of adding endings to the nickname (like |away, |home, and |work). Just add a wildcard at the end of the nickname to ban all the different versions. Your command would look like this:
/mode #topgear +b LordBaconCheeseburger*!*@*
To ban someone who always has the same ident: /mode #channel +b *!ident@* Because this information can by set by the client, be careful with these bans. In the case of web-based clients like GeekShed’s Flash client or Mibbit, the ident is the same for everyone. For example, this command: /mode #topgear +b *!TFlash@* would ban everyone using GeekShed’s Flash client from the channel #topgear.
To ban everyone who uses a specific network connection: /mode #channel +b *!*@*domain-info. You can make this ban as specific as you like. Here are some examples, using the information for banning LordBaconCheeseburger from the channel #topgear:
/mode #topgear +b *!*@*comcast.net bans everyone using Comcast
/mode #topgear +b *!*@*ga.comcast.net bans everyone in Georgia using Comcast
/mode #topgear +b *!*@*hsd1.ga.comcast.net bans everyone using the Comcast hsd1 server in Georgia
To combine bantypes: You can also combine these different banning techniques. For instance, you have had a lot of trouble with people using the GeekShed Flash client who connect from Georgia using Comcast. To ban them all from the channel #topgear, use this command: /mode #topgear +b *!TFlash@*ga.comcast.net
Before you try any of these bans, of course, be sure to check the information against others in the channel to avoid accidentally banning someone. Be sure that you have set the appeal information for your channel, so that people know what to do if they are banned accidentally.
Finally, for more details on how these bans work, check out the Bans & Mask Type Definitions from the Undernet website.
—posted by Tengrrl/Bunny
Setting a Simple Channel Ban
Sep 28th
Channel bans allow you to block someone from joining your channel. These bans offer a lot of flexibility, letting you ban someone in several different ways. This article will explain a simple ban. You can check the Extended Ban tutorial for additional options. You can also use the AKICK command to ban someone permanently.
To ban someone from your channel, you need to know the hostmask for the connection. Use the WHOIS command to get the details. For the user LordBaconCheeseburger, you’d use this command:
/whois LordBaconCheeseburger
In your status window, you’ll see something like this in response:
LordBaconCheeseburger is ~TFlash@protectedhost-BACONYUM.hsd1.ze.comcast.net LordBaconCheeseburger is a registered nick
LordBaconCheeseburger on #jupiterbroadcasting #theshed
LordBaconCheeseburger using Komma.GeekShed.net Subwolf.org
LordBaconCheeseburger has been idle 3mins, signed on Fri Sep 28 21:00:28
LordBaconCheeseburger End of /WHOIS list.
You need the information from the first line to set your ban. The information listed after the @ symbol is the hostmask. To set a simple ban for your channel, use this command:
/mode #channel +b *!*@hostmask
If you wanted to ban LordBaconCheeseburger from the channel #topgear, for instance, you’d type:
/mode #topgear +b *!*@protectedhost-BACONYUM.hsd1.ze.comcast.net
That’s all there is to it. Anyone with that hostmask is now banned from #topgear. Next week’s post will explain more complicated channel bans, so be sure to come back!
—posted by Tengrrl/Bunny
FAQs about GeekShed’s Spamfilter
May 27th
GeekShed maintains a spamfilter of URLs and phrases that are blocked network wide. Most of the entries on the list got there because someone was spamming the information on the network. Some entries are added because they link to malware, porn, or another kind of less than desirable site.
What happens when someone triggers the spamfilter in a channel?
If you make a statement or action in a channel that includes a URL or phrase on the spamfilter list, your text will be blocked completely. No one in the channel will see what you said (though you will probably see it). Immediately after the text, you’ll see one of these messages:
* Message blocked: Spamfilter match. Do NOT attempt to
get around this filter. If you think it is an error,
tell us in #help
* Message blocked: Spam URL
What happens when someone triggers the spamfilter in a private message?
Your text will also be blocked completely if you send a private message (PM) that includes a URL or phrase on the spamfilter list. The person you were trying to message will not see the message at all and will not know you tried to send a PM.
You’ll see this message in your status window or a query window, with <nick> replaced with the person you were sending the message:
* Message to <nick> blocked: Spamfilter match. Do NOT
attempt to get around this filter. If you think it is
an error, tell us in #help
What happens when someone triggers the spamfilter in a channel topic?
Your topic will not be set if you try to include text that is on the spamfilter list. Instead, you’ll see this message in your status window or in the channel:
* Setting of topic on #channel to that text is blocked:
Spamfilter match. Do NOT attempt to get around this
filter. If you think it is an error, tell us in #help
What is the punishment for triggering the spamfilter?
If you accidentally trigger the spamfilter, generally nothing happens. Just take note of the warning, and do not attempt to get around the filter or continue posting the blocked text.
If you continue to trigger the spamfilter, you may be banned from the network.
Does anyone else know when someone triggers the spamfilter?
Network staff will see a message that says you triggered the spamfilter. No one else will know (unless you tell them).
Can I see the list of words, phrases, and URLs on the spamfilter list?
No, we don’t provide a list to avoid abuse or misuse of the information. Do you honestly think we’d want to post a list of malware, porn, and undesirable sites?
Can someone add URLs or phrases to the spamfilter list for their channel?
Not exactly. Only network staff can add text to the GeekShed spamfilter. However, you can use the extended ban type ~T to block specific phrases from your channel, essentially, creating your own private spamfilter.
—posted by Tengrrl/Bunny
I’m Banned From My Own Channel
Jan 21st
It’s easier than you might think to get banned from a channel you own or where you are a moderator. It may be that you didn’t identify quickly enough or services were down and you couldn’t identify. It’s even possible you or someone in the channel set a ban too wide. An asterisk wildcard in the wrong place is all it takes.
If you find yourself in this situation, this is the simplest way to remove the ban:
/msg ChanServ UNBAN channel
So if I were banned from #topgear, I’d use this command:
/msg ChanServ UNBAN #topgear
After that, you should be able to join the channel again.
You can also remove the ban the traditional way. Say you or someone banned your hostmask or vhost. You add a ban with +b, and you can remove it with -b. If you had accidentally banned yourself with this command:
/mode #topgear +b *!*@my.own.address.net
You could unban yourself by typing this command:
/mode #topgear -b *!*@my.own.address.net
As a third option, you can also try inviting yourself into the channel. Usually a channel invite will get around a ban. This command will also work if your channel is set to invite only and you cannot join.
/msg ChanServ INVITE channel
So if I wanted into the channel #topgear, I’d use this command:
/msg ChanServ INVITE #topgear
If none of these options work for you, come ask for assistance in #help!
—tengrrl
Setting a ban appeal procedure for your channel
Apr 15th
We have written and loaded a module into services to allow you to specify a ban appeal procedure for your channel. This module will allow users to see your ban appeal information when they do /cs info #yourchannel and also online at http://www.geekshed.net/chanban/. We have made this URL easy to remember so that you can point people to it if they enter your channel asking about a ban in another channel.
Note: Because of the nature of services, this web page may be up to 5 mins out of date. Every channel with a ban appeal procedure specified will show up on this web page. If you do not wish your channel to show up do NOT specify a ban appeal procedure.
To specify ban appeal information for your channel use the following command:
/cs SET channel BANINFO [info]
An example of this would be:
/cs set #phil baninfo Bans cannot be appealed
To remove this, do the command with no appeal procedure specified. For example:
/cs set #phil baninfo
If you have any questions, ask in #help.
Note: Because of the nature of services, this web page may be up to 5 mins out of date. Every channel with a ban appeal procedure specified will show up on this web page. If you do not wish your channel to show up do NOT specify a ban appeal procedure.
To specify ban appeal information for your channel use the following command:
/cs SET channel BANINFO [info]
An example of this would be:
/cs set #phil baninfo Bans cannot be appealed
To remove this, do the command with no appeal procedure specified. For example:
/cs set #phil baninfo
If you have any questions, ask in #help.
Extended Bans Tutorial
Nov 1st
Silencing Users with Extended Bans
You can use extended bans to set up an alternative kind of ban that will give you more options, like silencing users. You can also read about how to set a simple channel ban and how to set more specific channel bans.
When you silence a user, you allow the person to stay in the channel, but block the person’s ability to participate in the discussion or change nicks. It’s an online equivalent of a short timeout, where the person has to sit quietly for several minutes before rejoining discussion.
To silence a user manually, you’d type:
/mode #YourChannel +bb ~q:nick!ident@user.host ~n:nick!ident@user.host
That command sets two bans, which is why the host information is listed twice. The first one (~q:nick!ident@user.host) prevents the user from participating in the discussion (unless the user is +v or higher). The ~q stands for quiet. The second one (~n: nick!ident user.host) prevents the user from changing nicks. The ~n stands for nick.
In #YourChannel, bans are normally set by the user’s host, so an example ban would look like this:
/mode #YourChannel +bb ~n:*!*@protectedhost-1234578.hsd1.va.comcast.net
~q:*!*@protectedhost-1234578.hsd1.va.comcast.net
That example bans anyone (with any nick or ident) with the hostmask protectedhost-12345678.hsd1.va.comcast.net.
Removing a Silence Extended Ban
If you silence a user manually, you have to remove the ban manually as well. Since you set the ban with +b, you will remove it by using the same command, but with -b. So to remove the ban, you would type:
/mode #YourChannel -bb ~q:nick!ident@user.host ~n:nick!ident@user.host
Everything is the same. You’re just removing the ban. Here’s the way to remove the example ban from above:
/mode #YourChannel -bb ~n:*!*@protectedhost-1234578.hsd1.va.comcast.net
~q:*!*@protectedhost-1234578.hsd1.va.comcast.net
Setting a Channel Extended Ban
There are two other kinds of extended bans:
- ~c sets an extended ban based on a channel users are in
- ~r sets an extended ban based on a user’s real name
You are unlikely to need either of these bans, but for the sake of thoroughness here is how they work.
To set an extended channel ban, you’d type:
/mode #YourChannel +b ~c:#channel
That ban would prevent anyone in #channel from joining #YourChannel.
Let’s pretend there’s a channel called #YourChannelHaters. We might decide that we do not want anyone from #YourChannelHaters to join #YourChannel. We could use this extended ban to prevent them from joining #YourChannel:
/mode #YourChannel +b ~c:#YourChannelHaters
You remove this kind of ban by switching to -b, so I could remove the ban on folks from #YourChannelHaters like this:
/mode #YourChannel -b ~c:#YourChannelHaters
Setting a Real Name Extended Ban
To set an extended ban based on a user’s real name, you’d type:
/mode #YourChannel +b ~r:*real_name*
The * character works as a wildcard, just as it does in other bans. Use the underscore character ( _ ) to represent spaces in the user’s real name. The underscore is also interpreted as an actual underscore character. In other words, the ban above would block someone using either “real name” (with a space) or “real_name” (with an underscore).
Here’s an example:
/mode #YourChannel +b ~r:*Jane_Doe*
That ban would prevent anyone who was using the real name “Jane Doe” or “Jane_Doe” from joining #YourChannel. Because of the * wildcard, someone with a real name like “Jane Doe rules” or “Jane_Doe_rules” would also be banned.
You remove this kind of ban by switching to -b, so I could remove the ban on “Jane Doe ” like this:
/mode #YourChannel -b ~r:*Jane_Doe*
—posted by bunny/tengrrl