Art of Blogging

Obviously, I have hit the end of my rope with WordPress.

However, I am not ready to go work at some fast food place, so I have to come up with something.

I looked into Habari again and rather deeply. I have to say, it looks like they are doing some really good work and trying hard not to make mistakes that have been made before. Unfortunately, their ideas for what a blog should do are not the same as my ideas. Mostly, this is just a matter of taste, except for one major detail.

It seems they think it is a bad idea for blogs to be indexed by Search Engines and do some things to stop the SE’s from coming along and indexing. One of these things is stopping the blog from pinging Google et al. While I can see their point, I vehemently disagree.

I think unless you are making something truly private, EVERYTHING should be indexed.

One reason is because I am a marketer, and not a blogger. I want new people to find my stuff and not just the established blog community.

Another reason is due to how I use the web myself. For instance, for right or wrong, I do not go trawling Digg and the like for stuff to read and learn. I use Google. Every blog I have ever found has been through either Google or link travels.

Why would I want to do something that would make my personal methods of travel no longer work?

OK, I may very well be missing the point and have failed to do my homework fully, but this isnt my major reason for not trying Habari out at this time… my major reason is this blog network we are on right now.

I have a few such networks and Habari isnt set up to handle them the way MU tries to.

This isn’t a flaw with Habari, just a different set of priorities between what the developers want and what I want.

Again, I briefly looked into what it would take to roll my own blog script… I am pretty sure I could hack up something that would do what I needed and be fairly secure. I could even get it up and running in a fairly reasonable amount of time… say 6 months or so and it would do what I needed.

Seeing as how this blog network is easily a YEAR behind schedule due to personal reasons and dicking with WordPress and their inanities, that is not an option.

I started looking again at other options available to me in the pre-rolled realm.

The old school big hitter in the blog network arena is Movable Type. Sorry, I am not going to pay for it. If I wanted to pay for a blog engine, I would roll my own.

This sounds awfully callous of me, I know, but it is actually more a matter of cynicism. I have no real confidence in any code I didnt write or control the development of. There is always *something* that other devs do that I do not approve of. This means I have to hack and slash the code. If they make me pay, the license is far too restrictive for my purposes.

Also, I “pay” for the use of code by teaching others how to use it. This is my personal business model and ethical thinking… and I also am not unknown to make a donation to a project out side of my normal writing.

If MT was open sourced and free, they would get me as a user and would get far more value than their licensing fees… and odds are, they would get more actual cash out of me too.

On with the body count.

I looked at several other alternatives as well, but none of them even remotely looked like they would make me happy. Since most of those reasons are personal bias and NOT my thinking they were junk I wont go into the big long list.

What I am about to install and try out is LifeType.

LifeType is an Open Source multi-user, multi-blog platform.

It is not a hacked up abortion like WordPress MU is. LifeType is designed out of the box to run either one blog or hundreds of blogs.

To me, this is the proper approach to making a script of this nature.

A minor but important point is that the group doesn’t seem to have a problem saying they made a mistake.

For example, their current release comments are:

“Lifetype 1.2.6 is the latest maintenance release of the 1.2 branch and though we said that 1.2.5 was “as rock-solid as it gets”, there continued to be a number of improvements and at least one significant bug fix.”

Guess it wasn’t quit as rock solid as they thought.

That is the problem with bold words like that…. too much code to be able to say anything is perfect.

Least they ate their serving of crow and did the right thing rather than sweeping it under the rug until the next release version.

It seems that I can migrate the existing WP DB over to LifeType. If so, I will be publishing the slew of back logged articles I have here on WP and WP MU purely for archive purposes (and to not waste the content that I created) and we will continue as previously planned at this blog.

At this point, I have only uploaded the code to a test location and not started the installation, so this post itself counts as bold words on my part.

Wish me luck, I am going in!