I just did a quick experiment to validate my hunch, and it’s true – WP Super Cache can cut your HTML load time in half in your WP deployment. Just check out the GrabPERF Measurement that backs this up.

Posted via email from Newest Industry Express

Newest Industry is now upgraded to Wordpress 2.7. You will notice no changes. I like that!

Ok, all I have to say is: If you do not have the Wordpress Automatic Upgrade plugin, go get it. The update took all of 30 seconds.

Thanks to the authors of that extremely useful piece of code.

Or should I say, welcome back.

Three years ago when I started blogging on a regular basis, the blog was name The Newest Industry after the Husker Du song of the same name. Then I migrated the content to Wordpress.com, and relinquished hosting it myself.

Well, I have decided to resurrect Newest Industry, but with all the same shiny content you would find at the Crazy Canuck Chronicles.

So, if it’s been a while, welcome back. Otherwise, a simple hello.

So, the last post I put up simply stated that I had failed in installing Worpress 2.6 on my own server. The permalinks were messed up and it looked a lot like an issue that a lot of people were having.

But, the catch was: the problem persisted when I tried to use Wordpress 2.5.1. Hmmm…wonder what’s up.

So today, I started thinking that it might be an Apache issue, rather than a Wordpress issue. So, taking a break from a massive project I’m doing (only so much performance data you can process before brain freeze), I started to poke around.

AllowOverride All

That did it. I was not letting Apache read the damn .htaccess file that Wordpress installed.

Excuse the thudding of my head on the desk.

Many apologies to the Automattic team. This user haz th dumb.

I decided over the weekend to have a go at running my own install of Wordpress 2.6, with an aim to perhaps hosting my own blog again, with the obvious gains in flexibility and monetization.

Let’s just say that it was frustrating.

The most frustrating part was the permalink issue. All known and posted fixes failed to resolve the issue of getting the permalinks to match those seen in this blog, which is the content I would be migrating. There is no clear and simple fix for those of us who just want the software to work, without having to spend two hours hacking.

I will try again when 2.6.1 is released, but it strikes me as odd that this made it out the door. However, I have seen worse unintended features appear in released software.

After a couple of days vacation, the FeedBurner feeds are back.

I bought the domain forwarding option from Wordpress.com (http://crazycanuck.org/), and then waited. I reactivated the feed at http://feeds.feedburner.com/crazycanuck this morning, and you can start using that again.

Rick Klau from FeedBurner left a comment last night, which prompted me to try again.

Hopefully things will remain stable now.

Technorati Tags: FeedBurner, feeds

I do not want to host my own blog.

Even if I wanted to, Wordpress.com does not make it easy to export content. This, however, is a separate discussion.

Skype and Web 2.0 (I hate the term, but I am using it) are inextricably linked.

Wordpress and Web 2.0 are inextricably linked.

Wordpress.com hates Skype. It’s that simple.

According to a Wordpress.com forum post:

Actually in this case it’s because skype and callme are being stripped. They’re not XML recognized tags and staff has stated that they won’t be supported.

And

Fraid not. Javascripts are still removed from input for security concerns. If you really need Skype, I would suggest getting a paid host.

See here.

Wordpress.com: BUILD A SKYPE WIDGET!

Thank you.

Technorati Tags: Wordpress.com, skype, widgets

Well, for some reason that I can’t determine, FeedBurner and my Wordpress.com feed stopped playing nicely this afternoon. And they won’t reload, because Wordpress.com wants to send all 1400+ articles in the database back to FeedBurner.

Sorry to do this to you all, but the FeedBurner feed is removed. Deleted.

Hope y’all switch to the Wordpress.com feed.

UPDATE: The FeedBurner Feed is back.

Joe Kottke of FeedBurner sent me an e-mail to tell me that the measurement of my feed was throwing off their GrabPERF Stats.

Guess what? FeedBurner can’t find the Wordpress feeds at http://crazycanuck.wordpress.com/feed/, hence the disruption.

Likely you won’t read this until it’s fixed, if it’s fixed.

I love Fridays.