When making a start in the world of blogging, there are so many things to consider that you almost need a trial run first to learn the lingo. In fact, getting up to speed by using a service like that offered by Blogger or WordPress.com seems a very sensible starting point. Even so, the business is like building a house in that you only really what you are knowing after you have done the deed and made all the mistakes. That is particularly true when you go down the self-administered blog route. For starters, it’s so easy to pick the wrong domain name or hosting provider. Selecting your blogging software is the next step but that may not be so tricky; WordPress does a reasonable job and there’s always Movable Type, Expression Engine, Drupal (yes, really) or Habari.

That mention of blogging software brings me to something that I encountered recently: commenting functionality. I am coming around to the idea that this is probably something that needs to be considered up front because of the nature of blogging. After all, anyone that reads The Blog Herald regularly should be familiar with the idea of blogging conversations and that means that the technology to make it happen should be easy for visitors to use and easy for bloggers to administer. However, the two can collide. For one thing, there are a myriad of choices available to the blogger and the blight of comment spam is ever pervasive and growing.

When it comes to comment spam, it is best to realise that there are two sources of responses to a blog post: visitor comments or trackbacks (pingbacks?) from other blogs. I am of the opinion that the latter is probably the channel where most of the detritus travels and various anti-spam solutionss are on offer to curb its spread. Names from the WordPress world like Akismet, Spam Karma, Simple Trackback Validation and Bad Behaviour come to mind. The former can also be used, particularly when the unscrupulous make use of low cost labour in low cost countries, and that’s when the thorny questions of user registration and CAPTCHA’s arise. There is something to be said for not going to extremes with these and just stick with less onerous rules and filtering on the server side.

I must admit to having staggering into forcing visitors to register prior to adding a comment and then making them log in thereafter. I think that it’s for security reasons but WordPress creates a password and then sends it to the person who is registering rather than displaying on a web page. That can create another problem: what happens if the email fails to arrive? In the last week, this has happened with a visitor to my hillwalking blog and there could be a number of reasons for the non-arrival of the relevant email. One is ironic: being an automated email, it is getting stuck in the spam filters of the recipient’s mailbox and so never gets to them. It could also be a bug with WordPress itself (I have raised a ticket and am awaiting what Automattic might have to say to it) or a consequence of some setting made by a hosting provider. All of that makes it hard to track down the cause of the issue but it kicks off other thoughts as to its resolution. One is to remove the needed for registration and logging in in the first place but there are third party services that may help too. The former has turned out to be the case for this blog and it seems to be performing well enough so it is an acceptable option.

When it comes to using third party comment handling systems, what needs to be considered is how well they work with your blog. For instance, I gave Disqus a quick whirl and soon realised that I needed to update the themes for my WordPress blogs if I was to use it on an ongoing basis. Otherwise, it worked fine but I was left wondering if it would have been better to have brought it in when I started a blog rather than part way through and with comments made using the existing WordPress functionality. There’s also Intense Debate and I am almost certain that there are more like it but I’ll be sticking with what WordPress offers for now. The theme for my hillwalking blog has been modified to allow prospective commenters to get in touch with me if they are having problems. That’s is only an interim approach while I consider what the way forward will be.

Having had a pretty fallow summer when it came to ideas for this blog, I am now lucky to enjoy a flush of them. Also, because of the my now established one post per day rule, I am currently writing my posts ahead of time so that you can be assured of something new everyday rather than a load of stuff one day and nothing on the next. That works for me because I am largely a proactive blogger rather than a reactive one. As a result, I am not bothered by a need to break something before everyone else and I simply couldn’t do that anyway; I have learnt that there are many others who can make a much better job of it. Nevertheless, I do get inspired by what’s going on in the technology world and it’s just that I take my time over things before sharing with others; the chance for some additional consideration before post goes public is a very useful one. And then there are my own explorations that surely will turn up more ideas.

It was on this date several months ago that I moved my hillwalking blog into the world of WordPress. It’s a self-hosted WordPress instance and has been for all that time. Because of the move, I was taken into the world of MySQL, a world that intrudes still to this day. Most of the time for the migration was spent setting up a theme to fit in with the rest of the website of which it forms a very important part. The matter of importing all of the old posts took up time too, especially when it came to fixing glitches with the XML import. Still, it was all done in a weekend and my website hasn’t looked back since. More people now have a reason to visit and the blog may even have surpassed the photo gallery as the site’s main attraction. I kept up the old blog for a while but have dispensed with that by now; I was keeping both blogs synchronised and that became a tiring manoeuvre. Another upshot of the whole experience is that I have become more aware of the UK outdoor scene and learnt a think or two too. It might even have encouraged me to go from day tripping to multi-day backpacking, a real world change that is well removed from the world of technology.

A recent article by Lorelle VanFossen on The Blog Herald got me thinking about my blogging journey and what I have learned about myself. My brush with reactive blogging has taught a number of lessons. The first of these is that I just cannot keep up with others; someone always gets there first. Another lesson is that taking on a topic of the day takes up loads of time when it lies outside my area of expertise and I spend a lot of that time researching the topic. What follows from this is that if the post doesn’t flow from me, it either takes up a lot of time or it doesn’t happen at all. Yes, I have been known to bin stillborn posts due to loss of interest or where things just wouldn’t come together at all.

Following all of this, I have come to the conclusion that I am a proactive blogger. That said, I still need to get some bursts of inspiration from somewhere. For instance, my hillwalking blog always experiences a burst of activity after I have been trekking in the outdoors; such encounters never fail to produce something that is worth sharing. In the same vein, anything you find here is likely to influenced by what I have encountered in the technology world. Yes, news items do provide ideas for posts but it is in more leisurely way rather than the frenzied approach of some. And like the hillwalking world, such inspiration does have it peaks and troughs.

Having two blogs allows me to stream my content; I doubt that many visitors to my hillwalking blog would appreciate seeing posts on, for example, the minutiae of UNIX shell scripting. However, as disparate as these worlds are, there is something shared between them and it has started to cause some cross fertilisation between them: blogging itself. Rather than being too self referential on my hillwalking blog and preaching to the choir, I have taken the decision to muse of blogging and its progress right here. There is also some escape in the opposite direction too: technology does get used on the hill too. Examples include GPS receivers and digital mapping and my hillwalking blog is definitely the place for them. It is all very much audience driven and this consideration of content is the sort of thing on which a posting on The Blog Herald has been musing.

If you have been here before, you may have noticed my posting frequency has gone down recently. Part of the reason for this is my taking on two big Vista-related issues that have attracted a lot of attention and wading through the various articles on the web has taken a lot of time. Finding out as much as possible about Vista licensing was certainly a challenge, thanks in no small part to Microsoft’s legalese, but it has been the DRM/HDCP issue that has really swallowed time on me; a passion-stirring topic that raises tempers is almost guaranteed to generate much discussion. Add to this the need to take care when considering such an impassioned subject and time really does fly by…

Addressing contentious issues that attract comments taking each which view has got me thinking about my blogging habits, particularly given that blogging is a hobby of mine and I have plenty of other things to be doing. As result, the post rate slowed down. If I wanted to continue like that, I could post more detailed entries once or twice a week and leave it at that. Or I could keep things short and frequent, say one post per day. Another idea is to have one long entry per week and shorter ones one per day for other days in the week. Now, that sounds like a good way to go.

It seems strange to say it but I am making good use of Word’s blogging capabilities. Having had WordPress.com’s blog editor mangle one of my posts – incidentally while using Opera as my browser - is the cause of this turn of events.

When setting up new accounts, there are a number of presets available to be used to work with major blogging providers such as Blogger, WordPress, and TypePad. This is not all though as it is possible to hook up to other blogs in a more generic fashion. In fact, I have able to hook up to my other WordPress-powered blog; hosted on the same server as my personal website and with all of the associated programming and scripting handled by myself. Where you have a number of accounts set up in the application, a drop-down menu appears in the post so that you can select the account to be used.

Speaking of drop down menus embedded in the post, you can add categories to a post from the blog server’s own collection and you can have more than one in any post. This feature is a boon as is the ability to edit posts that are already on there but Word only seems to show a subset of all the posts on the server, about 20 I think, rather than every single one. Another caveat is that you need to use a separate window for each post or you’ll end up overwriting posts in error. Whether this is a result of RSS feed settings or is intrinsic to Word itself remains something that I have yet to discern. As it is Word, formatting, insertion of objects such as hyperlinks and images is very much part of the package. That said, uploading images via this route was not something that I tested until I was writing this post but it seems to work well.

Apart from the irritations discussed above, I did find Word crashing a few times but no data were lost thanks to its seemingly excellent file recovery capabilities, a definite counterpoint to some of my experiences with Word’s file recovery feature in previous versions. Eventually, the Office Diagnostics tools kicked in to see if all was well and, after carrying out both hardware (memory, hard drive, etc.) and software checks, an installation repair was performed. Let’s see if this resolves the issue. Even so, the crash repair and diagnostics were not something that I had seen to the same extent in previous versions of Office and they did look pretty impressive.

In summary, Word does seem to be good blogging tool but I wouldn’t use it on its own because of its inability to download a full list of posts for editing. A blog’s own interface will remain necessary for that. Also, Word is far from being the only “offline” blog editor out there and I am tempted to take a look at the likes of BlogJet and w.bloggar.