18th July 2008
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 know what you are doing 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. The Blog Herald's regular readers should understand blogging conversations; consequently, the technology must be easy for visitors to use and simple for bloggers to administer. However, the two can collide. For one thing, there are a myriad of choices available to the blogger, while 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. As it happens, I reckon that the latter is probably the channel where most of the detritus travels, with various anti-spam solutions 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 sticking with less onerous rules and filtering on the server side.
Admittedly, I have stumbled into forcing visitors to register before adding a comment and then making them log in thereafter. While I think that it's for security reasons, WordPress creates a password and then sends it to the person who is registering rather than displaying it 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.
There could be a number of reasons for the non-arrival of the relevant email. One is ironic: being an automated email, it gets 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 I 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 challenging to track down the cause of the issue, yet it kicks off other thoughts as to its resolution. One is to remove the needed for registration and logging 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 place. Since it seems to be performing well enough, 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 were to use it on an ongoing basis. While it worked fine, 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. Intense Debate is another option, one of many if my hunch is right. 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 is only an interim approach while I consider what the way forward will be.
6th April 2008
By default, Evolution doesn't display images in HTML emails. It's a good security and anti-spam practice, but it's also nice to have the ability to override this behaviour. While the Ctrl+I keyboard shortcut (View>Show Images is the way to do it through the menus) will do the trick on an email by email basis, you need to add the email address to your address book for a more permanent approach. There's a little extra to make the latter work, and it involves heading to Evolution's Preferences dialogue box (Shift + Ctrl + S or View>Preferences) and selecting Mail Preferences from the sidebar. Clicking on Mail Preferences gets you where you need to be. The part of the screen that's relevant is Loading Images, and there are three options: Load images in email from contacts is the option that you probably want more than Always load images from the Internet because keeping Evolution's anti-spam defaults is most likely an excellent idea. Apart from sender whose images you don't want to see, you should now have images displaying in HTML emails.
Aside: The theme in use for the above screen capture was from Ubuntu Studio rather than SlicknesS, which is my usual choice. The latter makes the above screen unusable because the text cannot be distinguished from the background, and it's only for this tab that it happens too, a combination of possible Evolution programming inconsistencies colliding with potential theme design gremlins in my view.
6th December 2007
On my blogs, I use the Bad Behaviour plugin to keep spammers at bay. It usually works very well, so imagine my surprise when it started kicking me out when I tried logging into the system. I started to wonder what happened to my IP address...
It now turns out that the repository being used by the plugin got moved by its author, and that was the cause of my predicament (and his: he locked himself out of his own blog too!). A new version was duly released to resolve the issue and all is well again. It is a tale that emphasises the importance of regression testing to check that you don't change anything that you shouldn't.
22nd May 2007
Over the history of the internet, I have seen halcyon online dreams turn sour, with the world of Web 2.0 suffering the same lurch. It was only in the mid-nineties that the web was considered a levelling platform and a place for interaction and sharing. It also was a lot safer than it is today, an ironic observation given how e-commerce has taken off until you realise the financial gain from scams like phishing. Human nature does have a habit of spoiling things and the result is the number of patches that Windows has needed over the years, that and the expansion of security software from being all about antivirus packages to the inclusion of anti-spam, anti-spyware and firewall applications.
You would think that the above would have all but killed off the optimism that abounded in the late nineties, only for it to resurface again with the explosion of the blogosphere and, of course, there is Second Life. But there are signs of slippage even in this brave new world: comment spam has become a scourge for blogs, though the likes of Akismet and the WordPress Bad Behaviour plug-in see off most of it for me.
Then, there remains flaming on web forums. In fact, what has prompted this post is my observation of the transformation of a friendly forum thread into a hostile exchange. It started out as a communication regarding the welfare of someone who needed to retire from the annual Rab TGO Challenge with a high fever. Everything was going well until someone poked a hole in another poster's grammar, yet it was the mention of fitness that really turned things sour, especially when someone’s admission of a 20-a-day smoking habit drew the ire from a fitness fanatic. While it was all unnecessary, it shows how people can mess up with technology: to realise those optimistic dreams that I mentioned earlier, we have to change to make it happen. For now, I suppose that we’ll have to live in hope…
12th April 2007
I have just learned about and started to use two new tools on my other blog to combat comment spam. While Akismet was doing well, I was moderating more than I liked. One plug-in is Bad Behaviour, and this interrogates incoming traffic and blocks anything that is attempting the nefarious. This cuts off spambots before they can even see the blog. Spam Karma 2 is the other new weapon in my arsenal. It is another spam detector and using it alongside Akismet is following the defence in depth approach: when spam gets past one, it is unlikely to pass the other. Both can coexist together, while there apparently is an Akismet plug-in for Spam Karma that does away with the need for Akismet itself. Though the array of options offered by Spam Karma may put off some, that means that extra power is there should it ever be needed.
7th March 2007
My other blog is experiencing what feels like a deluge of comment spam. All that I can say is thank goodness for Askimet. And that is with visitors having to subscribe in order to post comments. It seems that a way has been found around that. I did have a spurious user with obdolbin.com as their website address and got rid of them but the flow still continues. Blogger does seem to have a way around this: entering the letters from an image to stop bots from doing their thing. Maybe we'll see WordPress doing the same?
Update: It seems that the torrent has now slowed to a trickle. Maybe getting rid of the spurious user has worked after all and it just took a while for the effect to kick in.