Much thanks to Terry/Kineda for reviving the spirit of the WordPress 2.0 Theme Competition that was intended by the original competition (that was later discovered to be a hoax) by launching a new one at wordpressarena.com with trusted, named judges like Terry aka Kineda, James aka Shadow, Bryan Veloso aka Avalonstar, and Dan Cameron.

The hoax competition had a lot of juicy prizes associated with it (likely because none of them were ever actually going to be awarded to anyone seeing as how it was a hoax). Theme designers worked their butts off creating new WordPress 2.0 themes in an effort to win some of those excellent prizes. While the new WordPress Arena competition is offering an iPod shuffle to the overall winner, the runner up prizes of a year’s worth of hosting (which people aren’t necessarily likely to take advantage of, generous as it may be, as changing webhosts is quite a production) and a book on the Zen of CSS Design aren’t quite as tempting as the electronic and cash goodies these designers were originally promised as prizes.

So I ask the community: if you have the means, please help reward the designers for all of their hard work and sponsor the WordPress Arena 2.0 Theme Competition by donating some enticing prizes to be awarded. This would then allow for more categories for themes to be judged upon and more winners, as was promised in the original competiton that sadly turned out to be a scam.

These theme designers who submitted their hard work to the hoax competition must feel really scammed and taken advantage of. Let’s make them feel appreciated - honor them for their work. Surely there must be some companies or individuals who have the means to donate some more prizes (cash or otherwise) and be proud sponsors of the new WordPress 2.0 Theme Competition.

WordPress Arena has graciously extended the deadline for submission of themes to May 1st to a) allow for the time for more sponsors to get involved and then decide on judging criteria for the new prizes, and b) provide extra time for the many theme designers who got scammed to learn about the new theme competition so they can all get their submissions in and for the rest of us to spread the word about the new competition. Winners will be announced on May 15th, 2006.

From the folks at WordPress:

An important security issue has been brought to the attention of the WordPress team and we have worked diligently to bring you a new stable release that addresses it. Our latest version 2.0.2 contains several bugfixes and security fixes.

I highly recommend that you download the newest release and upgrade your WordPress installation(s) ASAP (and backup your database before upgrading!).

For those of us with many blogs, this is one of those pains in the neck that makes you wish you had a hosted solution that did the upgrading for you. But all in all, the pros of getting all the features and customizability of the full version of WordPress makes it worth the hassle for those who are technically inclined enough to handle WordPress.

(The rest of you should check out WordPress.com — they’ve had a lot of upgrades lately, including new themes, WordPress Widgets, and more - which I’ll write about in a later post, but suffice it to say good things are happening over there )

BTW - It has not been clarified whether this security vulnerability which was found (and fixed) was in any way related to the supposed hacking of the WP 2.0 Theme Competition that was being hosted by kycap.com, but based on the dialog in the WordPress support forums it does appear that the KYCAP theme competition was a hoax, which, if true, is just evil. Fortunately, a new WordPress 2.0 Theme Competition has sprung out of this mess and is being run and judged by some of the more well known and respected (i.e., trustworthy) members of the WP community

I have been having some seriously frustrating conversations with the tech support people over at Six Apart. I’m hoping that they will eventually do right by me, but as it stands right now I’m ready to pull my hair out.

TypePad currently does not support 301 permanent redirects, or any modifications at all to the .htaccess file.

This prevents visitors who have bookmarked your site from knowing that it has been moved to a new location, unless you manually update each and every post to provide the link for the current URL (which is what I have been doing).

The bigger problem, however, stems from the fact that the search engines have no idea where you went. Without a 301 permanent redirect, they do not know that they should no longer index the old URL, and that the previous content can now be found at your new URL. The same holds true for technorati being able to recognize that your new blog is actually your old blog — just with a new domain name.

TypePad’s customer support says that they don’t allow customers to modify the .htaccess file for security reasons because it contains account information. Now that’s reasonable, but what if I were to just provide them with a text file that contains all of the redirect codes (which they could clearly see was not a security threat) and then the customer support themselves could just add that code to the existing .htaccess file? It would take them two seconds to do the copy and paste. Obviously, there isn’t any technological reason why they could not do this. It’s a matter of will they choose to help me or not.

And remember, it’s not like TypePad is a free service — I paid $149 for my TypePad Pro membership, and had been planning on renewing it indefinitely as I have other blogs on TypePad that I had not been planning on moving (like my blog of Best Funny Pictures, which averages 3000+ visitors a day). But if they’re going to continue to hold my old URL hostage and refuse to allow me to set up 301 permanent redirects to this blog, I’m not going to be a happy customer — and probably won’t continue to be a customer at all as a result.

I’m still waiting to hear back from this customer support (we’ve been arguing back and forth about the 301 permanent redirects for quite a bit) and will obviously report the ultimate results here. Wish me luck.

Update: the official final response from TypePad customer support has come back

At this time, we do not provide the service you requested to our users.

Buggers!
Now do you see even more why it’s important to get your own domain name before you start blogging?

I also wish I hadn’t been intimidated by WordPress and had used that from the beginning… Oh well, at least I’m using it now!

I’ve previously reported that wordpress.com did not give bloggers the ability to incorporate AdSense ads into their blogs. I just came across a post in the wordpress.com FAQ that explains the reasoning was to avoid the attack of the spam blogs that free sites like Blogger.com got slammed by. However, they also hinted that we could expect functionality for including ads on wordpress.com in the future:

We currently don’t allow Adsense or other JS ad code on the site, though we probably will in the future. However right now it is keeping sploggers (spam bloggers) from exploiting WP.com and only a few legit users have asked for it.

We’ll announce when you’ll be able to add Adsense or Yahoo or Chitika to your templates.

I look forward to the time when they do allow wordpress.com bloggers to earn a little money for their hard spent hours blogging through adsense, ypn, chitika, and what-have-you. I think that would be a great move for wordpress.com as right now that’s the number one reason I’m not recommending it to bloggers looking for a hosted solution (in which case I’d currently say go with TypePad). There are plenty of legitimate bloggers who would like to be compensated somewhat for their writing.

That doesn’t mean that I don’t think that wordpress.com should continue to take a hard stance against sploggers (spam bloggers) - by all means, nuke their butts! They could make it easier to identify splogs by adding a little button of ‘flag as spam’ in the dashboard for wordpress.com users who are logged in and surfing other wordpress.com blogs. Right now they’re asking users to use the Feedback button to send them a note when someone comes across a splog - but by installing a button on the dashboard that automatically sends that feedback they could make the process of reporting splogs that much easier…(my 2 cents)

c|net posted an article yesterday about how Google indavertantly revealed internal projections. Some of this leaked information should be of great importance (and very disturbing) for professional bloggers:

Google said that “AdSense margins will be squeezed in 2006 and beyond.”

It’s not like Google isn’t already making a ton of money from AdSense - the leak also said that:

Google expected ad revenue to grow from “$6 billion this year to $9.5 billion next year.”

So why does Google need to reduce publisher’s earnings even more?? As it is, earnings paid on AdSense clicks are marginal compared to what the advertisers are paying for those clicks (and what’s going in Google’s pockets).

Looks like bloggers need to take a better look at the Yahoo! Publisher Network (which is still in Beta) because Google is apparently planning on screwing AdSense publishers in the upcoming future.