More on comments

Following my last post about blog comments, a couple of posts have popped up in my feed reader about the topic. Firstly James Cridland ponders what makes him decide to leave a comment on a blog, or use his own blog to respond:

First, this reply is going on a bit, and it would be quite difficult to leave this in Martin’s blog comments anyway. (Because I’ve used more than one link here, it probably would be regarded as spam, too). A reply in my blog affords me the space to reply.

Second, by my blogging here as a reply to Martin’s post over there, it means that those that read my blog are aware of Martin’s posting. If I’d have just posted on Martin’s blog, nobody would be aware of Martin’s posting. The extra addition of Google Juice, etc, also is a good thing for both of us.

Third, this is just as relevant a posting as many of my others here; if people really want to read my witterings here (as apparently quite a few do), then it’s probably just as useful to them to read this reply.

Length of response is definitely an issue for me when deciding whether to comment or post. The second point is also an important one, I think, especially in terms of the visibility of a conversation.

John Naughton also picked up the theme today, answering those that have wondered why he doesn’t allow comments on his excellent blog. His three reasons are that he lacks time to moderate and answer comments; that his blog is predominantly a resource for capturing his own thoughts for his own purposes, rather than being a  conversational  exercise; and finally John quotes a Dave Winer post:

Do comments make it a blog? Do the lack of comments make it not a blog? Well actually, my opinion is different from many, but it still is my opinion that it does not follow that a blog must have comments, in fact, to the extent that comments interfere with the natural expression of the unedited voice of an individual, comments may act to make something not a blog.

Interesting. I’m starting to think that the ideal situation would be that everyone has their own blog, and we respond to one another using our own platform, and don’t use comments.

The trouble is that not everyone has, or probably ever will have, their own blogs. So those that actively want feedback have to make the facility available – no matter how unsatisfactory it might be.

Everyone needs a Dave

…including me. Jeremy Gould points us towards his latest bit of furniture – the ‘Dave‘:

Dave

It’s a pretty handy looking laptop table, and only twenty quid from Ikea. Face it – every home should have a Dave.

On blog comments

How do you track the conversations that go on in comments around the blogosphere? It’s easy enough to know what the actual blogs themselves are doing, after all – we have our feed readers, Google’s blog search and technorati. We have trackbacks and pings to let us know when people are linking to us on their sites. But what about the hidden conversations that are happening in the comments?

There are two angles to this. For example, it annoys me that when I comment on someone else’s blog, I am leaving content there that isn’t aggregated on my blog. I see DavePress as my little hub on the web, from which you can find out what I am doing elsewhere, on Twitter, or del.icio.us, or Flickr. I have a widget on this blog that displays the latest comments here – I’d also like one that displays my latest comments elsewhere.

This might be a fairly selfish thing to want, but the ability to do this has more practical advantages too. If we want people, whether public servants or those working for private enterprises, to engage with bloggers and to respond to them we really ought to be providing a way for those responses to be easily tracked.

Likewise, when a discussion is going on around an issue, with lots of stuff in the comments, how can that be tracked, or even found in the first place? You can subscribe to comment feeds I guess, but if you do that with every blog you’ll end up with twice as many feeds as you have already…

I think this could be a really important issue if we are to start using blogs as consultation mediums.

I suppose one possible answer is that we abandon comments altogether, and instead everyone responds to everyone else via blog entries, linking to the original.  I have read of some bloggers turning off the comments on their site for exactly this reason.

It’s a funny decision to make, actually, whether to start your own post on a subject or whether to respond in the comments. I don’t think I have a hard and fixed rule about it, maybe it just comes down to how much I have to say on a topic.

Does anyone have any ideas on how we can track comment conversations – whether our own or those we are interested in? What could change to make it easier?

Polling day

DavePress pollEvery day, WordPress and the community around it manages to surprise and delight me more. I have mentioned how it can be used to consult before, specifically by using the amazing CommentPress theme. But you can also create small polls to run on your site too, whether on a page of their own or by running in the sidebar.

This is done using the Democracy plugin, which is really easy to set up and deploy. It allows you to set the options, or give voters the ability to add their own. IP addresses can be logged to stop multiple votes, and you can store an archive of polls on a page.

I am running a quick example on this site asking readers how they access the content on this blog. OK, so it probably isn’t very scientific, but it’s fun, and another great example of the flexibility, and sheer genius, that is WordPress and the people that use it.

barcampukgovweb Developments

barcampukgovwebThe community that formed around the barcamp for uk gov web types (hence the name) has been working hard to start developing idea and connections that can start to have a real beneficial effect on the way that public services are using the web as a medium for communication and collaboration.

One of the ways this is working is through the Google Group, which is seeing some interesting discussions and some germs of top quality ideas are starting to emerge.

The trick is to capture these ideas and the various links and put them in a space where collaboration can start to happen. This can now be achieved using the GovHack wiki, set up by Adam McGreggor. A section for projects has been created, and once the discussions on the mailing list reach a point where it’s appropriate to do so, a page is created on the wiki to allow the ‘work’ to begin.

So, things are moving gradually, but at least they are moving. Mini-meets, like yesterday’s in a cafe at the House of Fraser store in Victoria, London, can only help as ideas are bandied about and possible solutions demonstrated. We need to ensure, though, that as much is documented as possible, so those that can’t engage face-to-face can still use the mailing list and the wiki to get involved.

I think it’s amazing that this is taking off in the way it has – fine, it’s incremental and evolutionary rather than there being any massive quick developments – but hey! maybe that’s just the British way. And there’s nowt wrong with that.

WordPress is a platform

WordPressSimon Dickson points to a new theme that turns WordPress into a Customer Relationship Management (CRM) tool. This confirms to me something that I have been thinking for a while that WordPress is no longer a blogging system, nor a content management system, but actually a platform upon which applications can be built.

Let’s take the evidence:

  • CommentPress turns WordPress into a super consultation platform by allowing readers to comment paragraph by paragraph on documents presented as posts on the blog
  • Prologue turns WordPress into a Twitter clone, allowing users to post very short messages as a cool way of keeping people in touch with one another. If you want to engage with Twitter-lke technology then this is a great way of being able to do it on your own terms
  • Now WPContactManager, as I mentioned above, turns WordPress into a CRM.

This is the advantage of open source software, of course, that because people have access to the innards of the system, they can understand how it works and put it to innovative uses. Of course, the flexibility of WordPress certainly helps, with themes and plugins being used to achieve much of these innovations.

It will be interesting to see what other applications based on WP start to emerge.

Redesigning DavePress

I have been wanting to give this blog a redesign almost ever since I started it. For some reason I just haven’t taken to the Mandigo theme I was using – a bit dark, maybe? I do think that darker themes are less forgiving of some of the clutter that we bloggers like to fill our sidebars with.

So, I have settled on PopBlue, by Bob, which is a much lighter theme and hopefully the single sidebar will focus attention on the content rather than the widgets and other crud. I ‘designed’ a quick logo, using an icon from the free Crystal Clear set and a bit of text.

Couple of jobs to get done though, including:

  •  Sorting out the CSS for images so that text floats nicely  around them in posts (any help gratefully received…)
  • Making blockquotes stand out a bit more
  • Replacing the standard search bar with my Google CSE one

So, there is plenty to be done…

Social Media Risks

One thing that came out of the recent barcamp for UK government types is that as much as those who really dig this stuff do their best to champion its use wherever possible, it really comes down to how senior managers feel about it.

The issue, of course, is one of risk. Doing anything different is inherently risky, and when that something different is directly engaging with people through an online conversational medium, then it’s even riskier. I don’t think we social media enthusiasts should ignore the fact (and it is, I think, a fact) that there are some really quite persuasive arguments as to why government, or indeed any organisation, shouldn’t go near this stuff.

Shel Holtz has come up with five common reasons why organisations won’t risk social media:

#1 – IT won’t let us

IT doesn’t want to spend the time or money to test social media software on company networks, claiming it can cost tens of thousands of dollars and take up to a year to make sure applications don’t conflict with existing programs. They also resist external hosting, asserting that it puts company data at too much risk. (Makes you wonder how much they care about our 401(k) data, since that’s never housed on internal servers.)

#2 – It will be abused

Employees will say inappropriate things. Customers will complain. Bad language will appear on comments. People will insult management. We’ll end up spending time on issues we don’t really think are important. Care to add to the list?

#3 – Management fears loss of control

The company has invested considerable time, effort, and money to craft a brand image that will be completely destroyed if we open it up to the masses. Besides, transparency is a bad thing and we don’t need our internal workings on display.

#4 – Legal and regulatory risks

Nobody likes a lawsuit. Besides, the Securities and Exchange Commission will the company if an employee inadvertently makes a forward-looking material statement. Pharmaceutical companies fear the FDA’s punitive powers for promotion of unapproved indications while the financial services industry fears fines from the bodies that regulate their activities.

#5 – We don’t have the time or resources

Communicators are already overworked. Where are they supposed to find the time to do all this new stuff? How can they even stay on top of the ever-shifting social media landscape?

These are all valid points, but that doesn’t mean there aren’t convincing counter-arguments, or mitigating actions that can be made to minimise them. In a future post I will cover what we can do to convince people that these are issues that can be overcome.