Puffbox – Page 58 – Simon Dickson's gov-tech blog, active 2005-14. Because permalinks.

6 May 2008

e-government, technology

coveritlive, downingstreet, liveblog

More Gov live blogging

There’s no doubt what the hot trend in blogging is: real time, thanks largely (or perhaps solely?) to the superb CoverItLive application/service. And following the apparent success of the Progressive Governance Summit last month, we’ll be seeing another e-government example today.

More than 80 MDs, CEOs, chairmen and Presidents from big-name global companies, plus a few heads of government (including our own) and various other dignitaries are attending ‘Business Call To Action’ – a London conference, backed by the UK government and UN Development Programme, to talk about what business can do to reduce poverty in the developing world, and get the Millennium Development Goals back on track. It’s quite an illustrious guest list, even if it’s only published in PDF.

The web component isn’t Downing Street-branded, but it’s being managed by the Downing Street team, with some Puffbox assistance (although most of the work has been handled by someone else). The plan is to run another liveblog of the proceedings, again using CoverItLive… plus a bit of video, and Flickr/Twitter mashing if schedules allow.

On my last post on the subject, Paul Canning queried the value of liveblogging, in the context of election coverage… and I take his point, in that context. But for something like this, it can provide an excellent channel for colour commentary, or even ‘context sensitive links’: when we did the ProGov event, people were contributing URLs providing additional background on the points being raised, for people who didn’t know the subjects. (Like, for example, me.)
5 May 2008

company, technology

support, ubuntu, wordpress

Long Term Support for WordPress

Oops. I wrote this piece yesterday, wishing that WordPress offered Long Term Support for occasional releases, along the lines of Ubuntu. I then get a comment from Mr WordPress himself, Matt Mullenweg, telling me that there actually is a long-term supported release. Here it is for the record…

The official policy from Team WordPress about software upgrades, as described by Matt Mullenweg last month, is pretty straightforward: when we release a new version, you should upgrade. Like, immediately. But when you’re dealing with the corporate world, where you deliver a project and effectively walk away, it isn’t quite so simple… and I’d personally welcome a Long Term Support approach along the lines of Ubuntu.

WordPress was built for bloggers: technically literate self-publishers, with some grasp at least of what’s involved in running a website. But as I’ve documented here countless times, and as my continuing mortgage payments demonstrate, comms professionals with no particular IT skills find its convenience, flexibility and simplicity (not to mention the price) equally appealing.

But the chink in the armour, if you like, is WordPress updates. Corporate projects tend to come with lists of requirements, which push well beyond normal blog-based sites. Normally, these requirements are achievable using plugins or a bit of custom code. But as Matt acknowledges, when an upgrade comes, there’s no guarantee that a particular plugin will work. And even worse, given that most plugins are offered up by volunteers, there’s no guarantee that the plugin will be updated accordingly.

I’m afraid Matt’s assertion that ‘having a secure site is much more important than the functionality of a single plugin’ won’t really stand up in the corporate context. You’ll ultimately face a decision between a site which might be at risk, but does everything you want; or (to put it provocatively) an under-performing site which still won’t be 100% secure anyway, because nothing ever is. And I’m afraid most marketing or communications people will choose the former.

There’s also the issue of the high-visibility upgrade notifications in the more recent WordPress releases. Whilst these are fantastic for those of us who run our own server setups, and aren’t scared of the upgrade process, I’ve had several phone calls from clients who are seeing this warning, and panicking (I’d say) unnecessarily. And I can’t honestly promise them that ‘hey, just do it, nothing can possibly go wrong.’

There is a compromise solution here: and that’s the model of Ubuntu‘s Long Term Support releases.

There’s a new version of Ubuntu’s Linux package every six months, with a promise to offer product support (ie minor fixes) for at least 18 months. But some of these are designated as having Long Term Support: these come with a promise of three years’ worth of fixes for the desktop version, and five years’ worth for server versions. It doesn’t mean that you’ll never have to do a major upgrade. But it’s a guarantee that the fundamentals won’t change for a considerable period – long enough to put the IT manager’s mind at rest.

That’s the kind of commitment I’d value as a WordPress ‘developer’. I want to present pitches to clients based on guarantees, not probability. And I’ve seen specific examples of excellent WordPress plugins, perfectly secure and stable in their own rights, which suddenly become obsolete because something changes in the next major WordPress release. Looking back, the changes are almost certainly for the better overall; but not if I’ve built a particular function around a particular plugin which no longer works.

The v2.5 release of WordPress takes it to a new level of maturity. A policy of LTS releases, ideally via simple ‘overwrite this file with that file’ patching, would signal the product’s readiness to be taken most seriously in corporate environments. And it would make an already strong proposition almost undeniable.

… and here’s the info about the ‘legacy 2.0 branch’ which is almost exactly what I was asking for. Now, I consider myself fairly well versed in the ways of WordPress, but I’d never even heard of this, and various Google searches yielded nothing.

I guess my only response would be that the description of the legacy branch needs to be rethought. The word ‘legacy’ (to me anyway) sounds negative; the idea of ‘Long Term Support’ sounds positive.

My thanks to Matt for correcting me, without making me sound like a total idiot.
4 May 2008

company, politics, technology

coveritlive, downingstreet, guidofawkes, iaindale, liveblog

Liveblogging the election results

Interesting to note some of the attempts to ‘live blog’ the election results last week – with Guido Fawkes, Slugger O’Toole and ConservativeHome all using CoverItLive‘s fantastic liveblogging ‘app’. Needless to say, there’s significant variation in the tone of each site’s usage.

Of course, it’s ironic to note both having a pop at Gordon Brown’s leadership when, dare I mention it, it was a Downing Street website – produced by yours truly – which first brought this technology to the attention of the UK political scene.

Now Iain Dale’s gone a bit CoverItLive-crazy, using it as an ad-hoc chatroom facility. It’s not really what it was intended for, and it’s probably quite hard work for Iain and colleague Shane Greer to moderate, but it does the job I suppose. They’re making good use of the popup polling mechanism, it must be said.

Correction: It took a heck of a lot of digging to find it, but I discover that ConservativeHome did use the CoverItLive tool back in January. My apologies; a straightforward Google search didn’t reveal it. I’m grateful to Guido for the advice to the contrary.
3 May 2008

politics

borisjohnson, democracy, kenlivingstone, londonmayor, turnout, twitter

The perfect ballot battle

In all the analysis of Ken’s downfall and Boris’s triumph, one element I hope doesn’t get ignored is the turnout. The RSA’s Matthew Taylor blogged on Friday suggesting it was the most interesting result of all, and I’m inclined to agree – although possibly for the opposite reason.

The London mayoral contest should have been the perfect electoral tussle. With all due respect to Paddick et al, it was always a two-horse race. Two instantly recognisable figures, well known by both broadsheet and tabloid readerships. A posh bloke versus a champion of the working class, neither of them ‘party men’. Plenty of real local issues to focus on. Plenty of media exposure too. A fairer electoral system, allowing you a ‘free vote’ for your first preference (with all the possibilities that offers) before casting your ‘proper’ second vote. And most importantly, an end result that was genuinely in the balance.

Yet it only stirred 45% of Londoners to bother to vote. Granted, this was up from previous years: 34% in 2000, and 37% in 2004. But it falls well, well short of the 70% we used to expect at general elections. And it means that, even taking both first and second preference votes into account, the winner only won the active support of 21.5% of the total electorate.

Of course we should be happy to see turnout rising. But it’s hard to imagine an election that could have been easier to ‘sell’ to the voters; and we only managed 45%. It’s not great, is it.

PS: Interesting to see the Tories heavily promoting their Twitter account on the conservatives.com homepage. We knew it was official, but I guess this makes it a formal comms channel for them… although I note the promo goes for the ‘subscribe via SMS’ approach, watering down the commitment to Twitter a bit.
24 Apr 2008

company

Pause for thought

It’s been a week since I wrote anything on the blog, and it’s likely to be another week before I write anything else. I thought I’d explain why, in case you thought I was dead or something.

It’s partly because so much of what’s happening at the moment is party-political, with elections imminent and a few (ahem) Whitehall issues dominating the headlines. This blog is about the business of politics and government, but we try never to express a party-political preference. And that would be nigh-on impossible in the current circumstances.

It’s also partly because I’ve got several projects I’d love to talk about, but can’t. Two are virtually complete: under starter’s orders, but not yet out of the stalls. Two more are in relatively advanced stages of development, and should make quite a splash in mid-May. And then there’s the one I’m most excited about, which will probably be my main focus into June. (No disrespect to the others, all exciting in their own right… but this one is huge.)

But it’s mainly because I’m worn out, and need a few days off. So let’s all sit back and watch the banter of the London mayor vote (and its aftermath)… and reconvene here again after the Bank Holiday break. All those in favour? Great. Night night, everyone.
18 Apr 2008

news, technology

bbc, blogging, rss

Full-text feeds on BBC blogs

It’s great to see the long-awaited improvement to the BBC’s blog infrastructure coming fully on-stream. I’m hearing reports of long, long hours being worked this week; and the inevitable post-launch debugging work continues. The Beeb’s Jem Stone describes the full horror, and scores extra points for an obscure Guns N Roses reference.

But I’ve spotted one interesting development for the ‘bug or feature?’ desk. A few of the Beeb’s blogs are unexpectedly pumping out full text RSS feeds. Not all, it must be said. But as I write this, the feed for the BBC Internet Blog is dropping the entire posting, formatting and all, into the ‘description’ field; the feed for the dotlife blog is delivering the full text, stripped of all formatting, so it renders (in most cases) as a single paragraph. Looking back through the archives I compile as a bi-product of my onepolitics site, it looks like Nick Robinson’s feed was full-text for a brief while, but isn’t any more. Sadly.

If it’s a bug, guys, please don’t fix it. In fact, let it multiply. Given the problems you’ve had supporting the huge volume of comments, it’s probably in your interests to minimise hits to the blogging platform. Let Google Reader and Bloglines share the strain. And encourage us to actually read more of your stuff.
18 Apr 2008

e-government, news, politics

downingstreet, guardian, todayprogramme, twitter

No10 Twittering is front-page news

A bit of a surprise this morning to discover that the venerable Today Programme is on Twitter… with its first tentative tweets as far back as September last year, and a (more or less) daily service since December. The username ‘todaytrial’ doesn’t imply that it’s being taken too seriously… although it’s built into their BBC website pages. I suspect someone may now be regretting that choice of username. And it’s a rather incestuous ‘Following’ list, consisting solely of other BBC services.

Downing Street‘s Twitter efforts are front page news in the Guardian this morning – see the actual text here – which should help them pass the 1500 friends mark imminently. Meanwhile, it looks like the Tories are taking Twitter more seriously, with updates being written in Twhirl – and, intriguingly, nothing from Twitterfeed in a few days. Still only a modest 60-odd friends, though. That Labour account is still nothing more than Twitterfeeding, with no indication if it’s official or not, and an even more modest 21 followers.

PS: I see a few other recent political additions to the Twittersphere include Boris Johnson – who appears to be texting them in; and Comment Is Free, for whom Twitter might be the key to making the whole CiF experience more practical. @brianpaddick has been at it since January; if it’s official, @kenlivingstone is leaving it a bit late.
17 Apr 2008

news, technology

accessibility, bbc, coding, html, w3c

BBC News site: too wide, too tabular

I’ve given it a fair crack over an extended period, but I’ve reached my conclusion: I just don’t like the redesigned BBC News site. In ‘standard’ conditions, a desktop PC running at 1024×768, it’s clearly an improvement: brighter, more airy, less cramped. But away from the norm, they’ve broken the golden rule of any revamp: don’t make anything worse.

As any website’s usage data will show, most people are now running a 1024×768 screen resolution. And monitors are just getting bigger, right? Wrong. I have four ‘web devices’ I use on a regular basis, and the two I bought most recently – an Asus Eee (classic edition) and a Nintendo Wii, both of which have sold like hot cakes – don’t operate at the larger resolution. So when I look at the majority of pages on the BBC News site, I have to deal with arguably the Number 1 no-no in web usability: horizontal scrolling.

(Curiously though, I see the second-level / subject homepages – eg UK or Politics – the page body remains sized for 800-sized screens?)

What’s infuriating is that (a) for all the BBC’s army of supposed design and usability managers, consultants and experts, nobody considered these widely-used devices worthy of appropriate support; and (b) it doesn’t have to be like that. CSS-based coding using DIVs could allow the site to work ‘well enough’ at 800-width, whilst looking its best at 1024. Instead, the site continues to use TABLE markup for layout, in clear breach of W3C advice dated 1999(!):

Tables should not be used purely as a means to layout document content as this may present problems when rendering to non-visual media. Additionally, when used with graphics, these tables may force users to scroll horizontally to view a table designed on a system with a larger display. To minimize these problems, authors should use style sheets to control layout rather than tables.

When I do a coding job, most of my time is spent working with DIVs and CSS, trying to make designs work acceptably across all browsers and all common setups. It’s not fun. TABLEs would be much easier, much quicker and much cheaper for clients. But coding with DIVs is unquestionably the right thing to do.

The BBC isn’t alone here: the major UK news sites are all – without exception, as far as I can see – forcing screen widths beyond 800 pixels. The Telegraph also uses a TABLE approach; whereas the Guardian and Times don’t. But we expect higher standards from the BBC. And that’s what annoys me most. Like a lot of people, I used to advise that whatever the BBC was doing, we all should be doing too. I don’t feel I can say that now.

Am I just being too idealistic here? And where does it leave government’s commitment to dated accessibility rules: what’s the point, when sites with receiving many times more traffic – the sites which define the typical UK user’s internet experience – are imposing a contradictory de facto standard? I’d be more than happy to go back to TABLE coding.
15 Apr 2008

Uncategorised

Big fish in political blogging

It is a truth universally acknowledged that the right is better at blogging than the left. We can all think of reasons why – it’s easier in opposition, generally more affluent and more eloquent people, etc etc. But one factor I’ve started thinking about lately is the ‘big fish’ problem. Specifically how it relates to Comment Is Free.

Before I built my onepolitics political aggregation site, I hadn’t appreciated just how much content that one website generated. On a typical day, they publish 10-20 stories, sometimes as many as 30 – and all of them lengthy, considered pieces. The majority of items on the onepolitics homepage are usually from CiF; at certain times of the day or week, it can be entirely CiF.

My theory, still in development, is that Comment Is Free is too big. If you want to read left-leaning blog content, you could start and finish on that one website, and wouldn’t miss much. And if you’re a leftie blogger, getting an item on Comment Is Free would put your rant in front of many times more readers than any solo blog. (I believe it gets something like 400,000 unique users from the UK per month; that puts it well ahead of any pure ‘blog’, although it’s hardly a fair comparison.)

I was interested, in this context, to hear a comment from Slugger O’Toole founder Mick Fealty (hi Mick) – who, of course, manages to blog for both Comment is Free and the Telegraph. Asked about differences between the US, UK and Irish (North and south) blogospheres, he accepted that Slugger may have had a similar effect on blogging in its home patch of Northern Ireland:

In some respects Slugger was ahead of the curve. And it got big – probably almost too big, too quickly. And in some respects, in terms of developing a wider network, and people who would set up their own blogs, I think we may have been a slight inhibitor of growth.

I can’t say I’ve drawn a firm conclusion from all of this, but I’m quite prepared to propose that CiF has had a similarly negative effect on left-wing blogging in the UK. I emailed the Guardian a couple of weeks back, asking if they’d ever done any analysis of their usage patterns, or their position in UK blogging. So far, I’ve had no reply.
15 Apr 2008

e-government, politics

downingstreet, guidofawkes, labourparty, shanegreer

Playing party politics with hyperlinks
From the ‘you can’t win’ department… Guido today picks up on a piece by Shane Greer last week, claiming that ‘Brown uses Downing Street (web)site to promote Labour’. And what incendiary partisan material are we talking about, precisely? An external hyperlink.

The No10 site has a page of Gordon Brown’s speeches. Or strictly, as it states in the page’s first line, non-political speeches. If you heard that Gordon Brown had made a speech, it’s the logical first place to look. But what if the speech had been made in a party-political capacity? It would be wrong for No10 to carry that speech on their website. And nobody’s suggesting otherwise.

So what do you do – present people with a dead end, or try and be helpful? It’s not as if they don’t (or rather, didn’t) make clear that you’re crossing the line from government to politics. As Shane’s screengrab shows, the link stated: ‘political speeches at the Labour Party website’. And in keeping with the site’s approach to external links, it opened in a new window. Hey, there’s even a page explaining why they have to be selective about the material they carry, with links to both the Ministerial and Civil Service Codes.

Shane asks: ‘What exactly is the justification for using taxpayer (sic) money to drive traffic to the Labour Party website?’ Well, there are two.
1. Good customer service. If you walk into a shop to buy something, and they’re out of stock, you expect the salesperson to suggest somewhere else you might try. It costs them a sale, but they do it because of plain common decency.
2. More efficient use of taxpayers’ money. If you don’t tell people where else to look, they will contact you to ask. They will call the press office, or send emails. It’s much more time-consuming, and hence much more expensive, for a civil servant to have to respond personally to those calls and emails.
The link has now gone. Party politics 1, common sense 0.

But let’s not pretend this is a Labour thing. I worked in government comms as far back as 1995. People would call up, asking for speeches by Conservative ministers – notably during the party conferences, but not exclusively. We either produced a transcript scrubbed clean of party-political material; or we gave them the number for Conservative Central Office. It was the right thing to do. Were we using taxpayers’ money to help promote the Tory Party? By Shane’s argument, yes. Sorry.

Disclosure: Although I’m doing some work for/with the No10 web guys, I don’t have any inside knowledge of this matter. I haven’t spoken to them about it, and was not involved in this decision in any respect.

Disclaimer: Although I’m linking to their websites in the text above, I do not endorse the views expressed by Shane Greer or Guido Fawkes. My company, Puffbox Ltd, is not using its proceeds or resources to promote either Mr Greer or Mr Staines. Just so we’re clear.