Category: Weblogging

Categories
Social Media Weblogging

Technorati, Technorati, wherefore art thou Technorati

I remember once being critical of TypeKey because (as I said at the time) centralized services don’t scale. Those who didn’t agree pointed out the excellence of both Google and Technorati to demonstrate how well centralization works.

This week, as I noticed comment spam in a TypeKey controlled blog, I thought back on that argument and still believe that centralization doesn’t scale. True, Google seems to be the exception, as it takes a licking but keeps on ticking (though it has faltered a time or two in the recent past, and lately it seems as if you have to wade through sellers trying to get to useful information). As for Technorati, though–I can’t be the only one who wonders if this service will ever be able to re-capture it’s former glory, as days go by searching on both keyword and URL, only to get less than useful results.

I feel like I’m kicking baby squirrels again being critical of Technorati — I like Dave, and think he’s providing a very useful product (which, I should add, is not costing me penny). I’m glad he got VC funding, and a great gig at CNN. And I like the fact that Dave never gives excuses when things go wrong.

But today was the first day in six that I got anything back for my weblog and this afternoon the results will most likely differ wildly from what it was this morning. This is seriously cutting into my ego surfing, forcing me to take drastic measures.

I’m warning you Dave — if you don’t get Technorati fixed soon, the squirrels get it.

Cute squirrels begging Dave for help, saying they're road kill without it.

Categories
Social Media Technology Weblogging

Exit door

Recovered from the Wayback Machine.

I wanted to to thank those (Steve, Loren, Liza, Tim) who have volunteered their weblogs for conversion for my upcoming tutorials on weblog tool independence. This is in addition to those who are offering space and installation of MT 3.1.

I’ve been asked if because of this series I’m thinking of switching back to Movable Type; what I’m going to do with this weblog moving forward, I’d prefer to leave for the denouement. (Sorry Marc – no peeking at the end.) The purpose of the series isn’t to sell one weblogging tool or another, as much as it is to sell the idea of weblog tool independence.

Sam Ruby once said, and I can’t find where, that the first thing to look for when evaluating a weblogging tool is the exit. Most tools provide an import utility and instructions, but very few provide an easy to use method to export entries into a format consumable by other tools. In fact, Movable Type is one of the best in this regard, though it’s also relatively easy to export from Blogger.

Weblogging tool lock-in serves no one, not even the tool makers. If a person feels they can’t easily move their weblog to a different tool, but they’re also not happy with the one they’re using, they’re going to be vocal in their criticism of the tool; this is the only outlet they have for their frustration. A better approach would be to give them an easy out, so they don’t feel ‘trapped’.

Moving the data is only part of the battle, though. The tough part is handling the differences in tags, functions, and plugins. But there’s a method to the madness, and the tools are more alike than unalike when it comes to processing that data they all hold in common.

Of course, none of us wants to have to spend time moving to different weblogging tools; we’re here to put deathless prose and pithy comments online, not spend time fiddling with technology. Still, it’s hard to be creative when your software crashes, your writing disappears, your post takes forever to publish, your host shuts your weblog service down in a hissy fit, or you’re fighting off hordes of comment spammers who clutter up your space (not to mention taking down your server with the force of their attacks).

Categories
Weblogging

Oh dear but this is sad

Recovered from the Wayback Machine.

With some of the current unpleasantness going on in the WordPress support forum and elsewhere, I’ll focus more quickly on getting the WordPress to Movable Type format export finished. This doesn’t mean I’m encouraging people to move, as I really like WordPress. And it doesn’t mean you’re locked into moving back to Movable Type: most major weblogging tools provide utilities and instructions for importing MT formatted weblog data.

(That’s why I will only support the MT format–using Atom is just a way of showing that you’re geeky. Sorry, but why focus on an export format not supported by most tools?)

However, some of the decision making can have some pretty adverse impacts on the non-geeks who just want to use a weblogging tool that works and doesn’t get them spammed. I really like WordPress, and respect and like many of the people who work on and help support the tool; but right now, there are a lot of growing pains and a little too much arrogance associated with the core community, and this isn’t good for the tool.

(I wonder if I just lost my volunteers for my upcoming tutorials?)

Categories
Weblogging

MT and WP Tutorials

My thanks to the two people who have volunteered their sites for conversion from MT to WP 1.3: Steve from Rodent Regatta and Loren from In a Dark Time. I’d hoped for two more, but we’ll go with these fine gentlemen. As soon as WP 1.3 releases and I have a chance to upgrad my sites and make sure all is well, I’ll tackle their moves.

I’ve also had a couple of Movable Type 3.1 folks who have volunteered installations and space, but right now this beta is all hush-hush so I’ll give them credit later.

I’ve been asked why I’ve dropped the port-a-blogging business. Part of the reason is that I’ve postponed buying my camera because of changing financial circumstances. I had planned on putting book money into the fund, but the book didn’t materialize. The money that has been donated (for which I am grateful) will go to film and development; with my Nikon 995, this will do.

However, the main reason for shutting down the weblogging porting biz is that my charging any kind of fee-based service is just not a workable proposition with WordPress. It’s not that the community surrounding WordPress is inimical to someone charging for services associated with WordPress development; it’s that if the service isn’t offered for no charge when you start, it most likely will be within a week or so after starting.

Additionally, people are now getting paid to work in the Movable Type environment, where before they did it for thanks and tips and I sometimes wonder if that hasn’t changed the perception of expectations between ‘weblog developer’ and ‘weblog community’. Movable Type has moved into the arena of the fiercely paid, with an associated expectation of service on demand; while leaving other tools such as WordPress to be obsessively free, but still competing in the same marketplace.

It’s hard to find the words to say without sounding petty, but I’ll give it a shot: I love to tinker with tech and to write, and I enjoy helping others, and don’t mind that I don’t get paid; but I don’t want to feel obligated to do things this way.

I can’t beat the cost of doing things for free, and I don’t want to volunteer to help all people with all things related to WordPress. Nor do I want to become One with the Force, as it were, in order to get legions of adoring fans. I’ve been working with tech close to 25 years now; I stopped having love affairs with my tools back when when I thought Java was hot, only to find out it was just another pretty langauge now fat and bloated by eating too many constructs.

Instead, I’ll convert this small select group of folk, and write tutorials that might help others do the job themselves. Then that will be it for my development and writing online about weblogging tools. Somehow, somewhere along the way, it stopped being fun.

I’ll still write on technology–gentle PHP and might MySQL, Internet ins and out and gotchas, and twisty techs like RDF, with other bits of this and that thrown in; but only as the interest moves me, and that way we’ll all have fun.

Categories
Technology Weblogging

MT and WP: There and back again

Both Movable Type and WordPress should be having new releases in the upcoming weeks. Movable Type is scheduled to release August 31 (I can’t find this in writing–can someone point this out?); No announced date for WP 1.3, but forum talk has it that the current nightly builds are getting progressively stable.

With both releases, there is bound to be a movement between these two products. I imagine since MT has a larger installed base, there will be more movement from MT to WordPress. However,announcements about stronger comment spam prevention and dynamic PHP pages in MT 3.1 could be luring some old MT users back to MT from WordPress.

Currently I’m working on a WP to MT export script that will export WordPress entries into Movable Type format for import into MT. WP supports an RSS/Atom export, but that won’t work with MT 3.1 (or will it?) Before I can release it, though, I need to test it with MT 3.1. If anyone has a working beta of this product, and wouldn’t mind letting me create a weblog for testing, I’d be appreciative.

When 3.1 releases, I’ll port one of my WordPress weblogs to MT 3.1 and then write up the process as a tutorial here in Burningbird. I’ll cover how to export the data, import it into MT, and how to move the weblog’s distinctive look by converting between tool template elements. This will include merging stylesheets; taking WordPress’ single template and porting it into MT’s multi-template environment; how the commenting structure differs; and covering differences between the tools for functions to list categories, recent comments, and so on.

To do this, I again need access to a working version of 3.1 and someone willing to let me create a weblog in their environment, for demonstration purposes (we can get rid of it when I’m done with writeup, and taking screenshots.) I could download 3.1 myself, but I don’t have – and won’t have– a TypeKey.

When 1.3 releases, my hope is to port 2-4 current Movable Type weblogs into WordPress 1.3, writing up the process just as with the WP to MT 3.1 port: how to move the distinctive look, covering functional differences, what functions to use for sidebar information, and so on. By covering multiple weblogs, I should hit most of the major challenges people would face. I’ll also add any of my customizations that the individual want, such as per-comment moderation or fullpage preview, comment editing, and so on.

(I’ll first be upgrading Burningbird from 1.2 to 1.3, which means upgrading my modifications and plugins. When finished, I’ll do another code documentation generation and post links.)

For this, I need volunteers from among Movable Type users who are interested either in moving to WordPress completely, or seeing what their weblog will look like in WordPress. They’ll need to have both the space and extra MySQL database for me to create the new WP weblog, and to provide me access to their system. They’re welcome to follow along with the effort, but they can’t hover. Hovering people make me twitchy.

Finally, I need non-techs to read the tutorials as I write them and let me know when the writing leaves them lost, or my instructions aren’t clear. I know that techs will let me know when I’ve done something wrong, technically.

Hopefully, when I’m done, people–whether technical or not–can use these tutorials to move from WordPress to Movable Type, and from Movable Type to WordPress–not just moving the data, but all covering all aspects of the move, including look and feel. This will be the last time I cover moving between tools, and I won’t be following Movable Type after 3.1.

Disclosure: I don’t work for Six Apart, I’m not part of the WordPress team, and have closed my ‘port-a-bloggy’ business. I won’t be getting either a Six Apart t-shirt, or a WordPress thong (I have been offered a JournURL t-shirt). I am not writing this up for a major publication. No one will be sending me flowers or chocolates, and telling me they love me for this. I may or may not get extra links for this for a time, but it won’t make an overall difference in my popularity. I would need to talk about sex, become a man or Dooce, or switch to being a warblogger to do this.

All of which means that I’m not financially or emotionally dependent on either product, which one you use, or whether you move or not.

I am doing this because it should be fun, and probably more helpful than talking about politics (though I will continue talking about politics, sex discrimination, hikes, photography, and whatever else it is I talk about here). Also because my version of ‘open source’ support is to use and/or tweak software and then write about it so others can do the same. I also believe people should be able to move freely between tools, even if they aren’t technically inclined.

(My final reason is that if people continue to have problems with comment spam in MT 3.1 I don’t want to hear them bitching about it!)

(Just joking on that latter.)

(Sorta.)