Featured Channel: #LordKaT
Oct 25th
#LordKaT is the community hangout and IRC parallel to LordKaT’s video gaming, geek, and tech content site http://Live.LordKaT.com, which streams 24/7 as a Twitch.TV partner. The channel was founded by LordKaT on September 1, 2008. (Yes, that’s the right date. #LordKaT is a channel that migrated over from WyldRyde, so the channel is older than the GeekShed network.)
What happens in the channel?
In chat, we participate in scheduled live broadcasts, available at http://www.LordKaT.com after the show as Blip.tv videos or audio podcasts. Our current lineup includes these shows:
- This Week In Games (now in its 3rd year)
- Tuesday Tech Talk
- How To Do It (tech questions answered live)
- Turducken Is Tasty (sports talk)
- LordKaT Plays and Free Play Friday (video game streaming)
- LordKaT Live! (live Skype call-in community talk)
- A Dungeons & Dragons campaign live on-stream
- Wat (very late Friday nights we peek into that dark, disgusting, hilarious corner of the Internet)
Apart from shows, our community chat and unscheduled live streaming is a variety of gaming and community tech talk. From our mafia playing Team Fortress 2 at our own server to hard-core geek programming of a MUD server or adding new features to Live.LordKaT.com, there is often hilarious commentary from the stream regulars and casual small talk in the chat—all of which might sometimes go one step too far, leaving you laughing and feeling a part of the fun.
What are the channel policies?
We welcome everyone, but our content and discussions are intended for mature audiences. Visitors to Live.LordKaT.com are free to speak their minds, even in dissent, as long as their comments are honest, human, and respectful of others.
Active members of the community are recognized as friends and members of the LordKaT Mafia. Our community recognizes those who stand out through old-fashioned personal networking and contributing to the community. There is no application process for rank in channel. We get to know everyone through the time we spend hanging out together.
Anything else you want folks to know?
Our community extends well beyond our chatroom. Be sure to check out these additional resources:
- LordKaT’s Live Site, which embeds LordKaT’s stream from http://www.twitch.tv/lordkat
- Our mafia forums
- LKMafia Steam gaming group
- The collaborative data mine of the LordKaT Wiki
- Our community’s self-authored blogs (new bloggers are always welcome!)
- The frenzy of tweets surrounding @LordKaT
Want to have your channel profiled on the GeekShed website? Check out the requirements and use the online form to apply.
—posted by Tengrrl/Bunny
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
Two New Servers
Oct 4th
We have two new servers on the GeekShed network. Subwolf has donated Sheba, a server in a Chicago, Illinois data center, on behalf of his site Subwolf.org. Allan has donated Tyrol, a server in Irvine, California, on behalf of JupiterColony.com. Server Intrepid has been retired, after many years of fine service to the network.
We’ve updated the server map to show these changes. As always, we recommend that you choose one of the round robins to connect to the servers closest to your location for the best connection.
—posted by Tengrrl/Bunny
Featured Channel: #EricJess
Sep 29th
#EricJess is friendly, welcoming community where people discuss a wide range of topics. The channel was founded by Eric Jess in June 2010. Eric maintains a community forum and a website for the channel (where he streams live video, when his computer isn’t broken). Eric shared the following information about his channel:
What happens in the channel?
There’s always something going on in our chatroom. We mainly talk tech, as geeks do, but there are all sorts of other discussions as well. We often fall on the discussion of Harry Potter for some odd reason and bacon—unfortunately, as bacon is on my dislike list. But we discuss all sorts of other topics as well. Nearly anything goes.
We are here talking during all hours. We help people with any problems they may have, and we usually have an active stream on all the time (technology allowing), with many guest streamers.
What are the channel policies?
We try to have an answer for everything, including how to become channel staff and how to earn voice. If you feel you were banned from #EricJess incorrectly, you can make an appeal online.
Anything else you want folks to know?
Well of course there is more! We have a active social network and do giveaways as much as possible. We are a family here and learn and grow with each other!
Want to have your channel profiled on the GeekShed website? Check out the requirements and use the online form to apply.
—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
Are You Using Our Round Robins?
Jun 1st
This is an archived post. Please see the February 17, 2015 post for details on the current round robin configuration.
As we explain on our Servers page, you often achieve the best connection by connecting to the server geographically closest to you. To do this, you can find the closest server on the map and then connect to servername.geekshed.net – for example, enterprise.geekshed.net would be a good choice if you were in Europe.
Geographical Round Robins
You can also choose a pool of servers that are near you by using our round robin addresses. The biggest round robin pool is also the most general one (and the one most clients use on their prepopulated server lists): irc.geekshed.net. That round robin includes all the GeekShed servers.
If you want to choose a smaller pool, you can use one of these round robins, based on your geographical area:
- ap.geekshed.net if you’re in Asia or the Pacific
- ca.geekshed.net if you’re in Canada
- eu.geekshed.net if you’re in Europe
- us.geekshed.net if you’re in the United States
Special Connection Round Robins
We also have round robins based on pools of servers with special capabilities. If you need these features, use one of these options:
- ipv6.geekshed.net if you want an IPv6 server
- lightirc.geekshed.net if you’re configuring your copy of the LightIRC client
You may also notice that if you’re using GeekShed’s free BNC service, you’ll be connected to bnc.geekshed.net. That’s the pool for our BNC service.
—posted by Tengrrl/Bunny
[Photo: Robin mom by photofarmer, on Flickr]
Planned Maintenance for Thursday, May 31
May 29th
The data center for Intrepid, one of GeekShed’s servers, is migrating our data to a new server around 9 PM EDT (1 AM UTC) on Thursday, May 31. There will be a short interruption in service during the migration and reboot.
We’ve removed Intrepid from the network’s round robins to allow connections to the server to naturally decrease this week.
If you connect directly to Intrepid, please choose another server or use one of the round robins (e.g., us.geekshed.net) until the maintenance is completed.
We’ll have things back up and running as soon as possible after the migration. If you have any questions on Thursday, you can check in #help.
—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
How Long Have You Been On GeekShed?
May 21st
Some of the features on GeekShed require that you are a registered user on the network for a specific period of time. For example, GeekShed offers all of its users who have had a registered nickname longer than 90 days free access to our BNC service and a free vhost.
So how do you figure out how long you’ve been a registered user on GeekShed? Check the information for your nick using the INFO command, replacing nick with your nickname on the network:
/ns info NICK
For example, the user LordBaconCheeseburger would use this command:
/ns info LordBaconCheeseburger
Nickserv will return the basic information about your nick either in the channel where you typed the command or in your status window. For LordBaconCheeseburger, the response looks something like this:
-NickServ- LordBaconCheeseburger is TFlash NextGen
-NickServ- LordBaconCheeseburger is currently online.
-NickServ- Time registered: Feb 17 02:46:36 2012 UTC
-NickServ- Last quit message: Client exited
-NickServ- URL: http://www.baconfreak.com/
-NickServ- For more verbose information, type /msg NickServ INFO LordBaconCheeseburger ALL.
The third line (in bold above) gives you the information that you need to answer the question. In this example, the nick LordBaconCheeseburger was registered on February 17, 2012. All you have to do is calculate the difference between that date and today to determine how long you have been registered on GeekShed. You can use a site like Online Conversion to help you make the calculation.
For our example, LordBaconCheeseburger has been registered for 94 days, so he’s eligible for a BNC and a vhost—Hurrah!
If you are trying to find out if you are eligible for BNC or vhost, note that the server is very specific about its calculations. It will determine if you’re eligible based on the exact second that you registered. Changes in daylight savings time will also effect the calculation.
—posted by Tengrrl/Bunny