Posts in category "blogging"

Disqus recently released a update which includes the ability to export comments on a WordPress blog so I have just exported all historic comments left on this blog (when it was running WordPress) into Disqus.

This operation was slightly complicated because this blog now uses Habari but the necessary steps were:

1. Download and install the new Disqus 2.0 plugin for Wordpress.
2. Delete all obvious spam so the export only processes genuine comments and runs faster.
3. Switch the archived WordPress copy of the blog back to the original location.
4. Export all comments from WordPress into Disqus.
5. Claim comments left by myself using an alternative email address before I had even heard about Disqus.
6. Wrap the WordPress blog in cling-film, label and place back into cryogenic storage.
7. Reinstate the Habari blog.

However, because I am pretty stupid and overly hasty, inevitably I omitted step 3. This meant that while all comments appeared on the Disqus site, the permalinks to the individual blog articles were incorrect and referenced '/wordpress/' instead of '/blog/'.

As it wasn't obvious how to rectify this issue or perform a selective bulk delete so I could repeat the process, I sent an email to Disqus support explaining the problem and asking for help.

24 minutes later, Jason from Disqus emailed me saying he'd fixed all the URL's.

What a fantastic service. What a fantastic product. What fantastic people.

So now I can put the kettle on and reaquaint myself with 886 comments (including some old friends) that have now been restored to their rightful place.

The only gap that remains is that a relatively small number of comments left on my blog after the Habari migration and prior to the adoption of Disqus are not currently visible. Hopefully, when the Disqus API is fully released, even this may be possible.

I suspect I have different audiences reading my blog, Tumblr, Friendfeed, Jaiku, GR Shared Items. I call this reader fragmentation but havent applied for copyright yet. Should I ?

Define your favourite Web 2.0 service in two words (or less)

• Blogging: Dear diary
• Flickr: Cat photos
• FriendFeed: 'Friend's Feeds'
• Tumblr: 'Disposable blogging'
• Wikipedia: 'Online encyclopedia'
• Twitter: 'Inane drivel'
• del.icio.us: 'Period overload'
• Disqus: 'Modern flamewars'
• Digg: 'Technical narcissism'
• Last.fm: 'Dire Straits'
• YouTube: 'Cat videos'
• LinkedIn: 'Gizza job'

There is a new, improved Monthly Archives plugin available for Habari which is now installed on this blog.

I realise that I'm probably the only person to ever scan the historical archives but I really like it so, once again, many thanks to Chris Meller and the Habari community.

Many disgruntled readers have contacted me via email, IM, facsimile, phone and anonymous poison pen letters to ask Hey Norman - whatever happened to the unified blogging day scheduled for Friday 18 April ?

Apologies for the delay but before we get started, some random, meaningless statistics:

• Feedburner: 66 subscribers.
• Google Reader : 'From your 189 subscriptions, over the last 30 days you read 6,807 items, starred 1 items, shared 325 items'.
• Twitter: Following 19. Followers 55. Updates 1,292 in 87 days.
• FriendFeed: Subscribed to 35. Subscribed to me: 30. Comments: 180 this week, 504 all time. Likes: 77 this week, 188 all time.
• Disqus: Comments left: 59 in 21 days. Comments on my blog: 31 in 14 days. Precious clout points - 12.

Originally, on Unified Blogging Day, I was going to religiously transcribe every single 'output' over a 24 hour period into a separate blog entry (annotated with timestamp and channel).

This was primarily a final effort to alienate loyal (but shell-shocked) readers who had survived the WordPress to Habari migration.

However, thankfully, FriendFeed already aggregates that inane stream of consciousness beautifully formatted here.

A secondary aim of Unified Blogging Day was to conduct a detailed poll to see how people subscribe to each 'output' but Habari doesn't have a 'Poll' plugin so just leave a comment below indicating which channel(s) you are a) aware of, b) subscribe to c) devour feverishly and d) blissfully unaware of.

• Blog - a man barely alive but we have the technology to rebuild him.
• Tumblr - stuff I'm too embarassed to put on the blog.
• Technical blog - low traffic.
• Twitter - endless stream of drivel (soon to be upgraded to include 'Hello', Goodnight' and the state of my runny nose).
• Disqus - every single comment I have left on the blogoshpere (on Disqus enabled blogs).
• FriendFeed - unified feed of all of the above. Filters available to reduce the signal/noise ratio.

Anyone owning up to subscribing to duplicate channels will have stay behind after school for 1 hours detention (unless they have a note from Mummy).

A couple of Oracle bloggers (Laurent and Yas) are experimenting with Disqus on their blogs but Tim Hall has expressed some reservations about committing his blog comments to a hosted service outside of his control.

Jake Mckee is also taken by Disqus but eloquently expresses similar concerns about 'data ownership and presentation'.

I understand (and used to vehemently share) both Tim and Jake's reservations. It does seem perfectly natural to want all your blog content stored in your MySql database on your server. What if Disqus servers are slow and unresponsive or worse, even down ? Your blog would be accessible but your comments wouldn't. What is Disqus isn't around next year ?

How do you unlock your comments from the Disqus repository and migrate them back into your blog ? How do you backup your comments ? There is an export utility but, as Jake points out, currently no easy way to import the data back into the blog.

Having comments hosted on your own blog is entirely logical. Obviously, blog comments belong with the blog content. Without the associated comments, the blog is like a half-written book.

You manage the blog comments. You back them up. You moderate them. The blog comments obviously belong to you. All of them. Yes - even those 1,729 spam comments, you have to scan for the odd 'false positive'.

However, if I leave a comment on a Harry's disqus enabled blog, my comment is displayed on the original blog. The comment text that I typed in is no longer stored in Harry's database table for 'comments'. Worse, my comment is now simultaneously displayed on a Disqus community forum without my prior knowledge or approval.

But who actually owns that comment on Harry's blog. I thought of the words and typed them into the comment box. Do I own the comment ? Or does Harry ? Does it even matter ?

As an aside, having used the service for a week, I no longer view Disqus purely as a comment tracking service. I view Disqus as a 'content output' tracking service.

For example, I am now starting to ask idiotic questions and log issues on the Disqus forums. These posts are not clearly not comments (but original content) but I still want to track them (and, more importantly, responses to them) in my Disqus dashboard alongside my blog comments.

This blog used to run on WordPress but now runs on Habari which is a blogging platform currently being developed by a set of very talented people.

Undoubtedly, the number of developers and users running Habari is far fewer than the massive community using WordPress. Similarly, the number of available themes and plugins available for Habari is relatively small (albeit growing daily) and dwarfed by the vast, almost bewildering wealth of add-ons and the extensive range of themes available for Wordpress.

However, this isn't a bad thing because it forces anyone contemplating a migration to Habari to think carefully about the core plugins that are truly essential to adminster your blog and valuable for your readers.

One such plugin (for me) was an equivalent of the Wordpress sitemaps plugin. Rick Cockrum published a excellent summary of why an automatically generated sitemap is useful.

When I first configured and activated the sitemap plugin for Habari, nothing happened. No sitemap file was generated. Initially, I thought that maybe the sitemap was only generated after a post was published. So I published a new post. Still nothing happened..

I posted a enquiry on the Habari users mailing list. In an effort to 'help' the Habari community, I even opened a ticket (bug request).

Then, I made an amazing discovery when an anonymous author was forced to waste some of his valuable time to close my 'bug report':

The plugin is not intended to generate a file, rather to serve the sitemap xml document when requested.

So, it transpires that the Habari sitemaps plugin doesn't actually generate a file. The sitemap is simply a URL which is dynamically built, on request.

Now I believe this is a much neater solution. No need for the user to specify where the file should be placed. Less work for the plugin to do. Much cleaner. Much simpler. Credit to the author, Andrew da Silva.

The lesson I learned was that just because something has always been done that way doesn't necessarily mean it can only be done that way.

P.S. If you're worried about the performance impact of needlessly rebuilding a sitemap, on the fly for 234,432 entries, don't worry - some clever individual has already implemented a cache for the sitemap data.

1. Disqus lets you easily track all comments you have left scattered over the blogosphere.
2. Disqus allows you to administer comments on multiple blogs from a single dashboard.
3. Disqus has built-in effective protection against comment spam.
4. Disqus provides tight integration with Blogger, WordPress, Typepad, MT and Tumblr.
5. Disqus provides Javascript code for every other CMS.
6. Disqus supports threaded comments.
7. Disqus allows you to fix that embarrassing typo by editing comments.
8. Disqus ‘eat their own dog food’.
9. Disqus is free to use. 10.Disqus is used on over 4,000 blogs.
10. Disqus lets you subscribe to individual comment threads.
11. Disqus supports gravatars.
12. Disqus lets you rate comments you like (and dislike).
13. Disqus provides an RSS feed for all your comments.
14. Disqus styles comments in keeping with your blog.
15. Disqus is configurable and extensible.
16. Disqus is written in Django.
17. Disqus treats an email reply to an comment thread as as additional comment.
18. Disqus is under active development.
19. Disqus listen to user feedback.
20. Disqus offers an API so you can write your own applications.
21. Disqus allows you to use your OpenId credentials.
22. Disqus offer unbelievably helpful and prompt support.
23. Disqus provide excellent widgets.
24. Disqus supports multiple moderators and a range of moderation options.

Five months ago, I experimented with Disqus powered comments when this blog was running on WordPress. The trial was rather short-lived because I was disappointed that Disqus wasn't able to fully integrate with all the existing blog comments. Importing comments still isn't possible but Disqus says this feature is being worked on.

However, I have decided to reinstate Disqus for the following reasons:

• Disqus recently added integration with FriendFeed so any contributions I make on Disqus powered blogs will also be visible in my FriendFeed stream.
• I am encountering an ever increasing number of blogs using Disqus.
• I am hoping Disqus will help to trigger more comments, interest and interaction on the blog.
• Disqus provide a nice combination widget providing 'Popular', 'Recent Comments' and 'People'.
• The most recent release of Disqus included a raft of changes including support for Open ID.
• Disqus is being actively developed and, more importantly, listen to their users.

I still have some reservations that the couple of articles with decent comment threads included replies to earlier comments (which are no longer visible) so we are literally starting from zero. However, hopefully some comments will appear soon and the tabs will actually display something !

Aside: Unfortunately, adopting Disqus means I will no longer be using Matt Read's recently released Defensio plugin which is excellent and highly recommended for any Habari bloggers wading through a torrent of comment spam.

Its no good. I simply can't go on. I can no longer summon up the enthusiasm for blogging.

All the warnings from the blogging 101 courses over the years have proven to be very true.

I foolishly dipped my toe into Twitter and then FriendFeed but it's no good I simply can't go on with this any longer.

I can't bear to miss my children growing up just because 'Facebook is so last year, Dad.'

I can't bear to talk to my wife and be abrupt and terse simply because I am now limited to 140 characters.

The time has finally come for me to declare complete 100%, unadulterated blogging and Web 2.0 bankruptcy.

Thank you all from the pit of my burning, nauseous stomach for your comments during the past years.

Tomorrow I will resign from Oracle Corporation and will devote the rest of my life to my one true love.

Learning to play guitar well enough to cover 'Country Feedback' by R.E.M. Wish me luck.

Peace, love, empathy

The byte stream that is 'Blog in Isolation'.