Podcasting Essentials: Strength in Numbers

It’s been a few days since I first posted the first part of my series on podcasting. I wanted to continue that theme today and talk a little bit about your show format and decisions you need to make – particularly when deciding to do a show alone or with someone.

At Suicide Fan, I do two formats of shows. this is important because each format serves a different audience. I mean, both shows cater to sports fan, but there is a definite difference in fan that listens to each. The first format is what is typical for a podcast. 20-40 minute show, big bandwidth, mixing of elements, etc. This show was the original and continues to be the flagship show. The fanbase that is targetted is an internet-based audience. They surf the net, probably blog themselves and perhaps listen to podcasts regularly.

I decided early on that this show would be done with two people at a time because, frankly, it’s a whole lot easier and more natural sounding to do a show with someone than to try to create compelling and (let’s be honest) interesting show when flying solo. It’s all about conversation. Debate can be had with multiple people. The dynamics of a show shift when talking to someone than when talking to yourself.

My philosophy is always have a wingman if you’re going to talk more than 5 minutes. The exceptions to these rules are trained broadcasters who have done radio or television shows for years or those rare podcasters who just have an uncanny knack for pulling off an interesting monologue.

The second show is a 60 second daily show. The format of theis show is quite a bit different. For one, it’s done solo. Because it’s around a minute in length, I am able to offset the boring monogue stuff by adding continuous, but not overpowering, music behind me. Instead of talking about multiple issues, I focus on one topic. The verbage is meant to be concise and I often use a script to delineate my thoughts ahead of time. The fanbase served is a fast paced group that doesn’t have a lot of time for radio or television, and thus, not podcasts.

These two formats work well for a sports podcast but you should have a firm idea ahead of time who you want to target. Let’s be honest, you can’t target everyone, so don’t try. The key to building the podcast audience is not the quantity of listeners to a given show, but keeping a low turnover rate. You want folks to listen the first time and come back and listen all the time. You may get your dad to listen to a show, but unless the topic is interesting to him, or unless the format you have chosen suits his style, you may not get him to listen to the rest of the shows.

Understand your target audience and what makes them tick. This will help determine what choices you need to make in developing the show.

Maryland is upping their startup game

As an entrepreneur in the MD/DC/Northern VA area, I am glad to see this from a press release yesterday:

The Greater Baltimore Technology Council (GBTC) said on Monday that it is partnering with the Kauffman Foundation to make Kauffman eVenturing — a web site created specifically for
entrepreneurs — available for the first time to Maryland entrepreneurs. The site offers original articles written by entrepreneurs, as well as other articles and tools designed to help entrepreneurs grow their companies.

http://www.gbtechcouncil.org/news/GBTCnews.asp

Technorati Tags:

Attention Baltimore: Purple Friday Party and Podcast on Friday

I won’t rehash what I wrote over at SuicideFan. But I did want to extend the invitation to local readers who want to come out and celebrate the Ravens playoff hopes and share your reactions with the world (we will be recording). Come out and have some food, beer and fun and celebrate the Baltimore Ravens.

Details can be found here.

How We Mass Upgrade Blogs

I’ve been getting hounded for some time about how we manage mass upgrades at b5media. It makes no sense to tackle things like you might upgrade, say 1, blog. Download. Unzip. FTP. Upgrade. It’s fast, but not when you have over 20 blogs. So I’m releasing our (slightly modified) script for public consumption.

Remember, our methods work because we are consistent. We manage consistently. We centralize when possible. We use Subversion. We have standard naming conventions. We use standard practices. Because we are consistent, our methods work. Your mileage may vary. Depends on how consistent you are.

This script assumes two things. It assumes that the comment field of each unixaccount is a normalized domain name. That is

1
example.com

- no slashes. No www. no http://. Just the top level domain. This is a discipline thing and requires making sure each new account is assigned a domain. If a user account does not have a domain, add it with

1
usermod -c example.com user

where example.com is the domain and user is the unixaccount.

It also assumes that the admin has a centralized database somewhere that can be tapped into for the blog urls. I’ll leave you to your own devices on this one. The script also requires PHP with cURL and the script must be run from the command line interfact (CLI) so the script must be owned by root and have owner execution permisions.

Other than that, have at it. This is not supported in any way shape or form and my releasing it here is merely to fill a request. I will not support this. Period. Consider it for your academic uses. :)

I am available for paid consulting though.

Source Code

Update: The source code has been updated. Notably, I’ve learrned a new trick. That is reading in user input from the command line in PHP. So now, the script prompts for revision number of WordPress. If a revision number is given, the blogs are upgraded to that number. If not, it defaults to trunk. Also, I moved the SVN magic out of a shell script and into this script. It also adds a timer so I can stop looking at the clock. ;)

1
2
3
[root@b5media-db2 ~]# ./wpup.php
What WordPress Revision? (default TRUNK)  4731
Upgrades completed in 4 minutes and 54 seconds

How to Handle Security Flaws

Yesterday, over at Blog Herald, the new management demonstrated the entirely wrong way of handling security flaws. (The flaw I detailed here)

WordPress celebrated it’s 500,000 install last month and cheers to them. The platform is stable, fast, easy to use. It has no cumbersome plugin architecture (like Textpattern). That’s not to say that it has never had its share of security vulnerabilities. In fact, there have been a number of documented fixes over the years.

WordPress has it’s own contact address for securtiy issues. It is security@wordpress.org. In a dangerous world of XSS and SQL injection, the proper way to handle the discovery of a security flaw is to report it first and allow the vendor to provide a patch or a new version. I demonstrated this process when I reported the XSS flaw in the Democracy 1.2 plugin for WordPress. I alerted the plugin author, gave him an opportunity to provide a fixed version and he did.

That’s the responsible thing to do. Alert the autrhor. Let the vendor produce a fix. When a solution is handy, make the exploit public. Instead, J. Angelo Racoma, in his quest to be popular after buying Blog Herald, leaked the story the day before WordPress 2.0.6 was released.

Now, I’m not in on the day to day conversations at Automattic. I really have no idea if the release was scheduled for today or not. But regardless, reporting a bug that has not been publicized before ample time was provided for a bugfix, is irresponsible. The thousands of readers at the Blog Herald could very well have gone into a panic. The rumor mill could have begun to spin. And for what? Simply waiting a day or two would have meant Blog Herald could suggest installing WordPress 2.0.6. Instead, they mentioned a beta (read: could have bugs still) version of WordPress 2.0.6 was being publically tested.

J. Angelo’s comment to me was this:

the news would’ve spread even without us posting about it, so I thought it best to post this as a warning. Patching WP to fix bugs would always be a good idea.

Ah, but the word would spread after the public had been notified – which happened today with two reports – a day after J. Angelo decided to spook the world. Wave your hands in the air but offer no solution. Sounds like Democrats in Congress regarding Iraq.

Blog Herald’s reputation slipped with me ater the purchase from Matt Craven and BlogMedia. This incident causes me less to trust them because it appears they are only concerned with getting the scoop and not behaving as good blogizens.

WordPress 2.0.6: CRITICAL Security Release

WordPress 2.0.6 was released today. This is a critical security release (There are at least two security flaws that I know of that were fixed in this version). I went ahead and upgraded all of our blogs successfully.

If you manage more than, say, 10 blogs then perhaps Brian Layman’s script will be useful for you. As I noted in his comments, I do something similar but in a different way. It took me 4 minutes and 15 seconds to upgrade all 181 blogs currently active or being prepped in our network.