If you want to see me speak at SXSW, you can comment and vote on my session before 11:59 CDT on Friday, August 27. Here’s how SXSW panel selection is weighted: 30% popular vote (you!), 30% program staff and 40% advisory board, so I’ll need some votes before they will accept my session! Here are the details about my proposed session so you can decide on whether to vote for it.
Hacking RSS: Filtering & Processing Obscene Amounts of Information
Information overload is less about having too much information and more about not having the right tools and techniques to filter and process information to find the pieces that are most relevant for you. This presentation will focus on showing you a variety of tips and techniques to get you started down the path of looking at RSS feeds in a completely different light. The default RSS feeds generated by your favorite blog or website are just a starting point waiting to be hacked and manipulated to serve your needs. Most people read RSS feeds, but few people take the time to go one step further to hack on those RSS feeds to find only the most interesting posts. I combine tools like Yahoo Pipes, BackTweets, PostRank and more with some simple API calls to be able to find what I need while automatically discarding the rest. You start with one or more RSS feeds and then feed those results into other services to gather more information that can be used to further filter or process the results. This process is easier than it sounds once you learn a few simple tools and techniques, and no “real” programming experience is required to get started. This session will show you some tips and tricks to get you started down the path of hacking your RSS feeds.
Last week’s community manager tip about how 
You can’t get away with hiding anything in an online community; community members will notice even the smallest things. While this is true in communities of every size, it is especially noticeable in large communities with many members. People are often under the mistaken impression that they can post something in a wiki or other content system, and as long they don’t link to it, no one will be able to find it. However, we have these things called search engines and recent changes pages where people can find everything. This is especially true now that everything seems to have an RSS feed or email notifications, since many users choose to have changes, like new web pages or wiki recent changes feeds, pushed to them to review whenever they have a few spare minutes.
I often tell people that nagging is a big part of community management. Yes, you could call it by some other nice names, “encouraging”, “managing”, “asking”, “requesting”, but the reality is that it can seem a lot like nagging. As community managers, we stay focused on what the community needs, and this often means that we need help from others to provide information, blog posts, technical details and more.
Most community managers keep a close watch on their online communities to be able to respond quickly, but really good community managers know when to respond right away and when to wait. If something is truly wrong, you should step in immediately to let people know you are working on fixing the issue, and when someone has an urgent or quick question, responding right away can help a community member get through an issue and back to being productive. However, there are many times when waiting and watching can be the best strategy.
The balance between listening and talking is a tricky one for many community managers, especially new ones. As community managers, we get excited when people participate, but if we start to jump into every conversation or reply to every thread it can be a little overbearing and can shut the conversation down too early. I try to listen first, and respond later to give more people a chance to participate.