Six Apart spins like a Whirling Dervish

I’ve refrained from blogging about Six Apart lately, because I have nothing positive to say about them or their products right now, but I’m afraid I can’t let their latest marketing email pass without calling bullshit.

I have spent the best past of the last four or five months listening to various friends struggling on a daily basis to keep Movable Type up and running. In fact, if you’re a regular reader then you’ll have experienced for yourself some of the problems that Corante have had with MT: the slowness, the failed page loads, the inability to post comments and, at one point, Strange’s total absence. I know of at least four large commercial installations of MT that have struggled – and, at times, failed – because Movable Type simply did not scale. (Although the new Rebuild Queue has helped.) I have personal friends who have had significant problems with MT, even though their sites are relatively small. And I have consoled more than one developer as MT saps their will to live, with significant bugs in 6A’s code being found and, eventually, fixed.

(Note: I am not going to name names, other than Corante’s – you knew about that anyway. Businesses in particular seem to be very wary of admitting when they are having software problems, but I am talking about household names both in the UK and the US who are having problems, and not small ones.)

With all this in mind, I find it totally disingenuous of 6A when they write:

We talk a lot about helping bloggers succeed with Movable Type, and that requires us to also focus on an important rule: Failure Is Not An Option.

You see, one thing Movable Type users often have in common is that, whether they’re writing a personal parenting blog for friends and family, or they’re publishing their opinion on case law for a law blog, they just can’t accept downtime on their blog. Fortunately, Movable Type was designed from day one to be super-reliable, standing up to the heaviest traffic load, even if you get linked to be a huge website.

This is nothing more than marketing department spin. MT is not super-reliable. If it was, then I wouldn’t keep hearing of yet another blogger who has abandoned MT, or another company that’s fighting to keep its MT installation going.

Six Apart is talking about MT as if it’s only used by individual bloggers, and that the only problem is when you get linked to by a big site. But whilst there are plenty of individual bloggers who are having problems, there are also business who have paid good money to MT for a commercial licence and are now finding MT to be a liability. And it’s not necessarily a big link that’s causing the problem, but fundamental flaws in the way that MT deals with spam and comments, and other bugs in the code that frankly should have been picked up years ago.

The spam problem, as I understand it, is that MT doesn’t differentiate between a spam hit and a proper comment until it has hit the database. It does the same amount of work in both cases, and the only difference is where that comment eventually turns up: on your blog or in the junk folder. So if your blog is hammered by spammers, the database does the same amount of work as it would do if it were hammered by real commenters. Of course, a spambot can hit your database with more comments more quickly than a human being can, and that alone can bring a blog down.

I heard of one case where, every time a comment was made, it caused 250mb of data to be transferred between servers. Scale that up to 100s or 1000s of spam comments, and suddenly you have the kind of load that can melt a server.

So no. MT is not super-reliable, and it cannot stand up to the heaviest traffic loads.

Six Apart go on:

How does it work? Well, unlike most blogging tools, Movable Type supports two different ways of publishing your pages — it can look in your database and choose which posts to display each time someone visits your site, or it can just generate a regular HTML web page that gets displayed without having to touch your database. That’s what we’re talking about when we say Movable Type supports “static” or “dynamic” publishing — static publishing doesn’t talk to your database every time someone visits your blog, and it’s the default in Movable Type. We let you choose between both so you can set the right balance of performance and scalability. (Static publishing takes longer for you as an author, but less time for your readers — so if you’ve ever waiting for your site to “rebuild”, you can take some consolation in the fact that your readers will have less of a lag when they visit you.)

Aaah yes, the rebuild. They talk as if this is a good thing. The trouble with rebuild is it’s really not very efficient, and frequent comments cause superfluous tasks to be queued for the rebuild, so you end up wasting a lot of server capacity. God knows the number of times I’ve sat there, waiting for a blog to rebuild… and waiting, and waiting, and waiting.

If you have the very latest version of MT, you have Rebuild Queue, but if you don’t then it doesn’t matter whether your site is static or dynamic, the problem is total comment load, including both spam and valid comments.

Most other blogging tools don’t do rebuilds the way MT does, and I can’t think of another tool that I use that suffers as much from bugs and downtime as MT. Doing things differently doesn’t mean you’re doing them right and everyone else is doing them wrong.

Digg-proof

Now, if you have a huge farm of servers and lots of technical staff, you can make dynamic publishing work at very high traffic volumes, too. In fact, our LiveJournal team here at Six Apart invented a lot of the open source technology that makes that work — the people behind sites like Facebook and Digg and Wikipedia and our own Vox use it, too. But if you’re running on a regular web server at a standard hosting company, they’re going to get kind of annoyed if your blog is hitting the database thousands of times just because you wrote a popular post.

Most commercial installations don’t have big server farms, nor do they have lots of technical staff. Yet even if you do chuck a few extra blades and a couple of developers at the problem, it’s still difficult to make MT work in either mode, static or dynamic, if you’re being hammered by spammers. Again, writing popular posts isn’t the problem. Serving pages isn’t the problem. Comments are the problem.

Now, it’s very easy to blame the spammers, but the sad fact is that spammers aren’t going to go away, and tools have to be built to withstand their onslaughts. MT isn’t. It didn’t matter how many servers you threw at MT 3.2x, comment spam could still kill them.

Oh, and just to nitpick… all that lovely open source stuff from LiveJournal? Well, let’s remember that minor point of fact that 6A bought LJ for its open source goodies. No sneakily trying to claim credit for LJ, please.

You might’ve seen this effect already — ever check out a link that’s been promoted on a big site like Digg or Slashdot and been faced with a “database connection error” when you visit the blog that got Dugg? Well, Movable Type is designed to prevent you from ever having to face that problem.

I feel like a broken record. Spam, guys, spam. Not the Slashdot Effect. (For the record, I’ve noticed that the Slashdot Effect is nowhere near as strong as it used to be anyway.)

For more tips on how to make sure your blog is performing as reliably as possible, our community’s put together some resources:

* MT Wiki
* Performance tuning Movable Type
* Enabling FastCGI
* Movable Type System Architectures

MT was always a tool that you needed to have a reasonable amount of expertise to install. Then they made it a bit easier, so you didn’t need to have quite the developer chops that you used to. Now you need to be a developer again to make the damn thing work. Make up your minds, 6A. Either MT is a developer tool or a consumer tool – you can’t keep wavering between the two.

And of course, we haven’t yet achieved this goal of making blogs failure-proof. Some of the steps for making a Movable Type blog bulletproof are too obscure or confusing. So we want to collect your feedback on the questions and concerns you have about the reliability of your Movable Type site — if you’ve ever missed out on some page views or potential readers because your blog wasn’t reachable, let us know or briefly summarize your story on this Movable Type wiki page.

OK, so 6A haven’t achieved their goal of making blogs failure-proof, why spend five paragraphs claiming they had?

If they want to understand where the problems are, they should start offering some support instead of expecting the people they’ve let down put the time and effort into writing it all up for them on their wiki. I know of people who have paid good money for MT who have had to fight to get 6A’s attention for support – 6A have complained when people ‘don’t use the ticketing system’ when the ticketing system was in fact broken. Hell, I even know of companies that have had to fight to pay them for a licence to use their software as per their terms and conditions. What sort of way is that to run a business?

Give proper support to the people whose MT blogs are failing, and you’ll soon gather all the stories you need to figure out what’s screwed up with MT. Instead of asking us to put the effort in, why don’t you, for a change?

We’ll start blogging about the reliability stories we’ve heard, both where MT has held up under pressure as well as where MT didn’t do what you’d expect, and how to fix it. Until then, you can help by pointing us at examples of Blog Failure, whether it’s on Movable Type or not, and we can all work together to help solve the problem.

Frankly 6A’s marketing department should be given, at the very least, a strong talking to for this email and especially the first and last paragraphs. Why should we do your work? It’s not the consumer’s job to figure out what’s wrong with your software – that’s your job, and if you provided decent support you’d have most of the answers by now anyway.

MT 3.34, released on 17 Jan 2007, has helped a few of my friends and contacts, but they are still having to do significant work to get all the plug-ins installed and working efficiently. Spam is still a problem. FastCGI gives a perceived speed increase, but frankly is a bit like faking it.

And whilst Rebuild Queue helps, it comes too late for many individual users and large MT installations. In commercial settings, MT’s damaged reputation has rubbed off not just on other third-party blog-related tools, but also on those evangelists who championed blogs in the first place, obscuring blogs’ benefits with serious performance issues that blot everything else out. It also makes it much harder to sell other Web 2.0 applications because of the fear that they too won’t scale.

The truth is that 6A have dropped the ball. They abandoned MT and their users, and their lack of support and updates has caused significant problems for even those people who are paying to use the software. Instead of keeping on top of MT and ensuring that it can cope with a rapidly changing environment and increasingly sophisticated spammers, they’ve spent the last two years focused on Vox.

Personally, I find it hard to have faith in Six Apart’s commitment to developing, improving and supporting Movable Type, which is why I now advise clients to avoid it at all costs.

Technorati Tags: ,

Bad Flickr: No donut for you

The day before yesterday, I blogged about Flickr forcing users to switch over to using a Yahoo! ID to access their Flickr account, and the patronising email I got about it. I was not a happy camper.

Now the furore has developed, and Flickr/Yahoo look even worse. Maybe it’s just bad timing, but it seems there are three main issues running concurrently here.

1. The forced switch to a Yahoo! ID.
2. Flickr forcing graceless limits to friends and tags.
3. Yahoo! using ‘all rights reserved’ and ‘non-commercial’ Creative Commons licensed photos on their Wii page, for commercial gain.

Oh dear. What a mess.

The forced switch to Yahoo!
Flickr announced in 2005 that they were going to be shifting to the Yahoo! log-in, and in a BBC article from September 05, they reassured people that all would really be ok with this move:

“We care deeply about our community, and their worries are ours,” [Caterina] Fake told the BBC News website.

“But I think the fears are unfounded. As always, the proof is in the pudding. We’re tending to our knitting, and making sure the Flickr experience is as good as it’s always been.”

But mistrust of Yahoo! goes back a long way, and disgruntled Flickr members started the Flick Off group to protest. There are now 1533 members, counting down to the day when Flickr IDs will be turned off and some of them will quit Flickr for good. The official Flickr forum thread is currently running at 1681 responses, and still going strong. The issues people are worried about include:

  • Finding an available Yahoo! ID that doesn’t suck.
  • Hating your existing Yahoo! ID; or losing the password and being unable to retrieve it.
  • Hating the unpleasant and long-winded Yahoo! sign-up process, which includes questions some people find intrusive and objectionable. For an insight into this process, take a look at Chris Messina’s screenshots.
  • Intermittency of Yahoo! sessions – people like being permanently logged into Flickr and don’t want to have to keep logging into Yahoo! (This is supposed to have been fixed now, but not everyone is happy with the cookie-based solution.)
  • Concern that, in the UK at least, Yahoo! is wedded to British Telecom’s broadband service and that by tying Flickr to Yahoo! they are also tying Flickr to BT. This is not good – if you want to change ISP you loose your BT Internet email address, which would then invalidate your Yahoo! ID and cut you off from Flickr.
  • Yahoo!’s habit of tracking usage using cookies and other methods.
  • Fear that Yahoo! will terminate your account for reasons unclear or unreasonable, thus locking you out of Flickr.
  • Fear that your Yahoo! account will expire without you realising it, thus locking you out of Flickr.
  • The item in the official help page that says if you terminate your Yahoo! account, you will also terminate your Flickr account and delete all your photos (see below).
  • A perception that Yahoo! marketing practises are unethical and exploitative.
  • Fear that Yahoo! will screw with Flickr the same way they screwed with other sites they bought in the past.
  • Technical issues with the Yahoo! sign-in screen, such as it timing out and not allowing browsers to save the password.
  • Issues with different Terms of Service for Yahoo!
  • Confusion for people with multiple accounts of either kind.
  • A feeling that if one has signed up with and paid money to Flickr, one should not have to now sign up to Yahoo!
  • Problems with people losing photos and contacts after merging their Flickr account with their Yahoo! account.
  • Concern that people who have paid for Pro accounts, but who choose not to switch to Yahoo!, will lose their money.

I could go on – this list is just culled from the first two pages of the thread and, whilst it’s admirable to see some participation from Flickr staff, they don’t seem to be really appreciating the depth of feeling about this nor do they appear to be systematically answering questions. Are these concerns and fears legitimate? Some are minor niggles that aren’t all that big of a deal, some have already been addressed by the Flickr team, but some are deeply disturbing. For example, if you delete your Yahoo! ID, you will also be deleting your Flickr account, as the official help page says:

I’m going to delete my Yahoo! account. What happens to my Flickr photos?
If you sign in to Flickr with a Yahoo! ID and you then delete your Yahoo! account, you will not be able to sign in to your Flickr account. In the future, this will delete your Flickr account as well, including all of your photos, but currently your Flickr account must be deleted separately.

This seems like a really rather harsh policy. Are users really clear on this point?

Technorati Tags:

Continue reading

Yahoo/Flickr get the bullyboy tactics out

If there’s one thing I hate, it’s being told what to do. That’s why I’ve been a freelance for so long. I like making my own decisions and resent having them made for me, so it’s not surprising that I feel royally peeved with Yahoo and Flickr for sending me this email:

Dear Old Skool Account-Holding Flickr Member,

On March 15th we’ll be discontinuing the old email-based Flickr sign in system. From that point on, everyone will have to use a Yahoo! ID to sign in to Flickr.

We’re making this change now to simplify the sign in process in advance of several large projects launching this year, but some Flickr features and tools already require Yahoo! IDs for sign in — like the mobile site at m.flickr.com or the new Yahoo! Go program for mobiles, available at: http://go.yahoo.com.

95% of your fellow Flickrites already use this system and their experience is just the same as yours is now, except they sign in on a different page. It’s easy to switch: it takes about a minute if you already have a Yahoo! ID and about five minutes if you don’t.

You can make the switch at any time in the next few months, from today till the 15th. (After that day, you’ll be required to merge before you continue using your account.) To switch, start at this page:

http://flickr.com/account/associate/

Nothing else on your account or experience of Flickr changes: you can continue to have your FlickrMail and notifications sent to any email address at any domain and your screenname will remain the same.

Complete details and answers to most common questions are available here:

http://flickr.com/help/signin/

Thanks for your patience and understanding – and even bigger thanks for your continued support of Flickr: if you’re reading this, you’ve been around for a while and that means a lot to us!

Warmest regards,

– The Flickreenos

This email does not fill me with the warm fuzzy glow I usually associate with Flickr. Instead, my brain reinterprets if for me thus:

Hey! Unhip square kid with no friends!

You may not have noticed, but we’ve been making it increasingly difficult for you to sign in to Flickr using your original Flickr ID by burying the sign-in page deep in the bowels of our site, where we hoped you’d never find it. It seems, however, that you haven’t taken the hint, and are still using your old ID. For shame. From March 15th you’re not going to be able to use your old ID anymore, and we’re going to force you to either sign up to Yahoo or use your Yahoo ID instead. We don’t really care if this is an inconvenience for you – you’re just going to have to lump it.

We’re making this change now because it makes life much easier for us. We also want to introduce you to a plethora of Yahoo services that you’ve never shown the least bit of interest in, and probably neither want nor need. We’ve already introduced some new features to Flickr and we made them Yahoo-only, so that we can pretend that we’re doing you a favour by forcing you to use your Yahoo login. Just to prove it, here are two things that you can’t currently do. Fool.

Anyway, you’re so old-fashioned and behind the times that you’re one of only 5% of cretins who still use the old Flickr ID, so give it up already. You’re like one of those little grannies who refuse to move out of a hideous towerblock that’s scheduled for redevelopment by nice coffee shop owners, just because it’s ‘home’ or some such nonsense. This is progress, dammit.

OK, OK, we’ll give you a couple of months to come to terms with the fact that we own your ass. But after that, you will be assimilated, like it or not. Resistance is futile.

Of course, we do appreciate that you were one of the people who coughed up cold, hard cash for a proper Flickr account back when we really needed the money, but hell, Yahoo gave us big bucks a while back, so meh. Whatever.

Warmest fuzzy wuzzies. No really, we do care. Honest. No, don’t look at us like that. Look, we’re about to turn into squirrels even cuddlier and cuter than the Trotts. Just you wait and see… Look! Look!!

– The cutesy wutesy Flickreenosywosy

You know, I like Flickr. There are some astonishingly good people working there. There are also some astonishingly good people working at Yahoo, but yet I don’t like the Yahoo brand at all. It’s unpleasant. It says ‘ignorant false-hearted redneck who always hangs on other people’s coat-tails’ to me. They are a brand that started off ‘pretty cool’ in the mid-90s, sank to ‘horrible’ in 2001 and have now rebounded to ‘icky’ (in no small part to some absolutely awful TV adverts), with a hint of ‘cool’ because of the services they’ve bought. That’s a shame, because I think that the people I know who work for Yahoo and Flickr are some of the smartest cookies out there, and all lovely to boot.

But I feel like I’m being both patronised and bullied at the same time by this email. Not once do they apologise for any inconvenience they may cause me, not a single ‘sorry’. Come on Flickr, you can do better than this. You are the Web 2.0 posterboys, your site is the one everyone talks about when they want a good example of community and social networking. Surely you are the people who understand that someone’s attachment to a site, even to a log-in, isn’t logical but emotional, and that you have to factor that in to how you deal with your community?

I didn’t join up to Yahoo Photos, I joined Flickr, and I rather resent the way I’m being told to move my log-in. You can be sure that I will be one of the bloodyminded few who will hold on to their Flickr log-in until the very last moment, just out of principle. Is there truly no behind-the-scenes solution to this? Would it not be better to use an OpenID solution, so that people have the option of using one log-in for whichever services they like? Or is this the beginning of a new mega-login trend? Are they going to start forcing people to use their Yahoo ID to log into Del.icio.us, or Upcoming? Oh god… you’re not trying to be Google are you?

Don’t let us down here Flickr. You created something wonderful, and now you have an opportunity to do something cool about your login problem, instead of just forcing users to dance to your tune.

Technorati Tags:

Edelman: Must try harder

As you might or might not know, I’ve got a relationship with Edelman, the PR company. I know Richard Edelman, I’ve spoken to their clients about blogging, had meetings with them, and spoken at two of their events. I have also worked closely with Jackie Cooper PR, their sister company, providing training and consultancy.

So I’m pretty embroiled with Edelman, and that makes me even more disappointed to be using the ‘Blog Fuckwittery’ category on this post, but it can’t be helped, I’m afraid.

If you’re into the whole PR thing, then you’ll likely have noticed recently that Edelman have got themselves into a bit of a pinch by helping create a fake blog for Wal-Mart. Called ‘Wal-Marting Across America‘, it purported to be a blog by a couple who decided to go on a cheap holiday in an RV (that’s camper van to us Brits), staying in Wal-Mart car parks overnight. What the blog failed to mention was that the project was a publicity stunt and that Wal-Mart were paying for their petrol, food, and the RV. This trick is known in the trade as ‘astroturfing’ (i.e. faking grassroots). Another way of describing it is ‘lying by omission’, and we all know lying is bad.

I’m not going to go into detail here about what was wrong with this specific project because lots of other people have done that, and I don’t much feel like parroting them. (For balance, I include the frankly lame responses from Richard and Steve.) But I do want to discuss a creeping disquiet I’ve felt lately that this serves only to reinforce.

Now, I like Richard Edelman – he seems to be a nice guy, quite savvy, and genuinely interested in the blogosphere, but the problem here is not just that Richard and his team were not transparent, it’s more fundamental than that. It’s that they are still thinking in old media terms: This was a typical ‘broadcast media’ stunt, an attempt to change the way people think about Wal-Mart by playing up the warm fuzzy angles and neglecting to mention that the whole thing was set up from the start. That is such an old-school way of thinking and it reveals just how much of the bloggers’ ethos has percolated through to the heart of what Edelman do, i.e. ‘not a lot’.

The other week, Kevin and I were invited by Richard and his team to attend a briefing that they, with Technorati, were giving their clients about the European blogosphere. Kevin was on the panel and I was asked by Richard just before the event if I could stand up and say something about the difference between US and UK top ten bloggers. I didn’t really blog it, bar a quick mention on Chocolate and Vodka, because I ended up feeling a little bit uncomfortable with some of the basic premises on show, such as ‘the A-list are important’.

There were a lot of other bloggers there, but that didn’t make me feel any better about it, because it was a little too much like they were there for show. For a long time I’ve felt that Richard is indulging in the zooification of bloggers – collecting and displaying them the way that rich people used to do with exotic animals. I worry that this makes him feel that he’s got a better understanding of the phenomenon than he actually has.

Surrounding myself with Chinese speakers does not instantaneously make me a fluent Chinese speaker. Yes, having access to Chinese speakers can help me learn Chinese better and faster, but only if I actually bother to speak Chinese to them. Surrounding yourself with bloggers is a pointless tactic if you don’t talk about blogs with them, if you don’t actually put some effort into learning what all this stuff means. You can’t pick it up by osmosis.

And this Wal-Mart debacle shows that Edelman still have a long way to go before they genuinely understand blogging. There are a lot of values and ethics they have yet to instil in all their staff at an instinctive level – Wal-Marting Across America should have been simply impossible to conceive, one of the ideas that they never had because it runs so counter to blogging culture. The fact that it wasn’t shows that too many people at Edelman think the old school way, about control and being on-message and spin. This is not the blogger way.

Kevin frequently talks about how he sees big media trying to adapt blogs to their business model instead of adapting their business to blogs, and Edelman are making exactly the same mistake – trying to use blogs for PR, instead of trying to adapt PR to blogs. Having a blog isn’t a magic bullet, it doesn’t fix anything. The magic comes from transparency, openness, honesty and engagement. As Kevin says, that’s the cluetrain, this is just clue-fucked.

Now, a few days after the furore, Richard has outlined the steps Edelman are taking to remedy the situation within Edelman. I have a few thoughts about his ideas, in order:

1. ‘Best practice’ is not something you get by put down rules into a document, or creating a set of processes you make people follow. It’s achieved by ensuring your staff have a deep understanding of what blogging is and how blogging culture works.

2. A single class on ethics in social media will not solve your problem – it will barely scratch the surface. I spent six months this year with employees from JCPR, giving them as thorough an insight into blogging as possible by introducing them to all the surrounding technologies and communities, and by encouraging them to read and write blogs. We spent two hours every fortnight for six months talking about and participating in social media, and you know what? There’s still a lot more they don’t know yet (but we’re working on it!). Blogging is not something you can learn in an afternoon, or a day – it’s as complex and alien to PR people as Chinese culture is complex and alien to me. Do not underestimate the scope of the differences – what’s acceptable in PR circles is far from acceptable in blogging circles and it takes a lot of unpicking to see exactly what’s what.

3. A hotline? That indicates to me that you know your staff haven’t got the requisite clue. But tell me, where are you getting all these lovely guidelines from? I’ve been doing blog consulting for nearly three years, and frankly I’m still learning things. The field is evolving rapidly, and I have yet to come across a nice set of guidelines that encapsulate it all.

4. Who’s writing your ethics materials? Please, God, don’t say WOMMA.

Finally, Richard asks for advice, to which my response is: If you really want to understand blogging properly, stop collecting bloggers to display at your events and start actually learning about the blogosphere. Set up a proper training course for your staff, run by someone who actually knows blogs, and who is not a PR blogger. I am highly sceptical of PR, and that allows me to point out to PR people where what they do is at odds with what bloggers do. If you simply employ PR people who happen to blog, all you’ll get is the same old PR attitudes, but with comments and trackbacks. And we all know that that is not enough.

I do think Edelman are doing better than most, but you are also more vocal than most, and if you’re going to talk the bloggy talk, you damn well better be capable of walking the bloggy walk, otherwise you’re going to look more than a little foolish.

How can anyone get a blog this wrong?

Thanks to Geeklawyer for pointing out the truly dreadful ‘blog‘ by Watson Farley & Williams, an international legal firm. As he says, it wouldn’t have taken them long to find someone to help them understand what this blog malarky is all about, but instead they’ve gone the FIUY (fuck it up yourself) route and have ended up with something truly atrocious.

Let’s have a quick look at what they did wrong.

a) The blog entries are PDFs. What on earth do they think they are doing? Why use a PDF? Blog entries are supposed to be easy to read in your browser at the click of a button, they shouldn’t involved downloading anything at all, let alone a PDF.

b) The blog entries are dire. The company has asked the trainees to blog, but obviously hasn’t helped them understand what blogs are, what might be good to write about, or how best to write it. Instead of an insight into life in a law firm, you get trite nonsense: “Oh it’s so great top work here… And look! Free booze!” I’m not going to pick on the trainees individually though – it’s not their fault they’ve been asked to do this and given no proper help or direction.

c) No comments.

d) No trackbacks.

e) No archives.

f) No blogroll.

g) No RSS.

h) No links to other blogs.

i) The blog entries are PDFs. Ok, I know I said that once already, but I really can’t get over it. PDFs. For the blog entries. WTF?

In fact, this ‘blog’ has absolutely none of the technology that makes a blog a blog. This is not a blog. It’s is a collection of poorly written PDF articles. Where’s the openness? The transparency? The honesty? The interest? The passion? If I wrote a blog about watching paint dry it’d have more passion than this one, and it’d be a lot more interesting.

Now I’m not the only blog consultant in town, but frankly you don’t need to be a blog consultant to see just how dreadful this attempt at latching on to a ‘hip’ and ‘cool’ phenomenon is. Ask any blogger what makes a blog a blog and they’ll probably give you a list much the same as above, but obviously Watson Farley & Williams are quite happy spouting bullshit and following trends from a safe distance of several hundred light years.

I wonder if they’ll do a L’Oreal (fix it) or a Juicy Fruit (pull it and pretend it never happened)?

Comment is Infrequent

The Guardian‘s Comment is Free site has been troubled again this week after they introduced a half hour waiting period in between comments. The accusation levelled at the commenters was that the discourse was not of a high enough standard and that a wait of half an hour would force people to calm down and think a bit harder before they posted. Thus, the assumption goes, would the conversation become more erudite, more intellectual, more stimulating.

Georgina Henry said, in her post Less is More:

[T]he sheer number of comments now coming in from individuals is making it harder to keep the quality of the debate high through post-moderation alone.

Aside from the persistent breaches of our talk policy a frequent cause of complaint is the pointless chatter that litters threads. Too many comments have nothing to do with the original post, or degenerate into back-and-forth slanging matches with others which just get in the way of reasoned argument and put off people who want to engage with the original piece.

[…] For those that want to cotinue to debate the issues raised by CiF bloggers, we’re proposing to introduce a comment frequency cap which will only allow individuals to comment once every half an hour. If it works it might make for more thoughtful contributions from those who tend to write before they think. If it doesn’t work – ie, if it simply dries up or drives away the best while leaving us with the worst – we’ll think again.

The majority of commenters were outraged at this arbitrary limitation of their freedom to post, and unsurprisingly so. They feel that it’s their site now, and that The Guardian has acted undemocratically and heavy-handedly. Commenter Sealion said:

Wow, what an atrocious idea. So what’s the problem? Cif has become increasingly popular and thats a problem for you? So you suggest that people don’t use your site, they go find another, or use a talkboard. Cif is a talkboard….did you really think it was a blog?

By your own admission, discussions have become better when the originator has come online to debate with the commentators. 1 post every 30 minutes? That’s altrui knackered then. And Sunny. In fact anyone who wants to get involved in a discussion is going to have to wait 30 minutes for a reponse from somebody they may have raised a point to, which is going to kill any debate stone dead, or persuade people to create multiple screen names to get around it and add chaos to confusion.

People will also write longer pieces because they have only one chance, and then they’ll probably go off and do something else because this isn’t much of a spectator sport.
Yes, it will probably get rid of a lot of abuse and pointless comments, the same as it will get rid of just about everything else. This will kill discussion, people will just post an essay length summary of their opinion and then leave.

Of course, it didn’t take commenters long – about 1 hour and 4 minutes – to figure out that The Guardian were using cookies to achieve their aim and that, by deleting the cookie one could post as much as one wanted.

But the reason people feel miffed is not just to do with their ability to post comments. Henry had posted previously that CiF had around 10,000 commenters, but only 100 people have posted over 207 comments each, with two having posted over 1,500 and one person approaching 2,500. This is a power-law distribution. Now, quantity is not the same as quality, but I would wager that if you plotted the quality of the comments, that too would follow a power law: the majority of users write perfectly acceptible comments and the name calling, ad hominem attacks and unpleasentness is committed by a small minority of users. Yet by imposing a half hour wait on every single user The Guardian are reacting disproportionately, as if the problem is widespread ‘bell-curve’ problem. It’s not, and the commenters know it. They feel as if they have been treated unjustly and that The Guardian has meted out an indiscriminate punishment to all without bothering to try and solve the problem posed by a minority.

After an evening of protest, Georgina Henry ceded some ground, and the system has changed so that the half hour wait is per article, not across the whole site. However, she doesn’t acknowledge that the commenters’ protests are in any way valid, and in my view fails to take in their points at all. She says:

Thank to the odd commenter who understands and supports what we’re trying to do. Just to reiterate, for the critics, there are other audiences that we’re trying to reach which this might help – they include the vast majority of people who read CiF but never comment; those who comment occasionally when they have something worthwhile to say; those who used to read us but are put off by the mindless irrelevant chatter that infects many of the threads and those who would like to engage with the original argument but have to scroll through too much rubbish before they do so.

How is this supposed to help? It’s natural that there should be a power-law of comment frequency amongst readers. I would expect nothing less – it’s how almost all these sorts of websites work. Lots of people read, some post once, and a tiny minority post frequently. This distribution is extremely common and well understood. Apart from, it seems, by Ms Henry.

There is no need to try to encourage those who don’t post to post by shutting up those who do post. Maybe the people who don’t post don’t post because they are happy just reading? Is there actually any evidence of droves of people put off by ‘mindless irrelevant chatter’? If that’s the reasoning behind limiting posting times, then I fear that there’ll be disappointment when the number of people posting doesn’t suddenly increase in leaps and bounds.

But there are a couple of themes here that CiF needs to understand. Firstly, ‘messy’ comments is not only inevitable, it can also be good. Euan Semple said:

We can tolerate a lot of apparent messiness and our ability and desire to make patterns allows us to get real value from it.

Dave Snowden was right when he said if you have a complex environment you need to have simple rules. Complex rules just result in a mess.

One mans rubbish is another man’s gold dust.

We can work together on complex activities with minimal directions.

The question is, what are the rules? Putting a wait time on posting is not a rule that is going to encourage less chaotic commenting, it’s just going to string it out over a longer period of time, and maybe destroy some valuable conversation that might have otherwise happened.

Perhaps, more important, is whether or not the original author actually takes part in the comments thread. Blogging, done well, is about a conversation, and on CiF, it seems that that conversation is rather one-sided: columnist opines; commenters comment. It that really any way to encourage an intelligent discourse?

What to do? The Guardian is – understandably – worried about not just quality of conversation, but also libel, defamation and other things that they might get sued for. This is serious shit – they cannot and should not allow libellous material on their site. They have to strike a balance between chilling out about the mess and ensuring that really nasty stuff gets dealt with.

But half hour waits will not appreciably help, especially if all it takes to sidestep the delay is to delete a cookie. Keeping the existing system will annoy people more than it will help. The Guardian will have to be more innovative than that.

Here’s a thought. How about learning from sites that face a similar problem. Slashdot is well known for having a rather low common denominator amongst the comments. Yet it’s still readable… So long as you know that you can filter out the rubbish by using the built in ratings system. Digg also uses a ratings system and comments with a low enough score are hidden from the casual reader: whilst they remain on the site, you have to unhide them to read them. Could the Guardian not improve on these systems?

It’s essential to remember that the problem is not really a technological one, but a social one. Comment ratings systems are only a tool to allow the community to look after itself, but the tool has to be well crafted in order for it to work.

Let’s consider a simple thumbs up/thumbs down system which the community can use to police itself. It can have a sliding scale of punishment, to allow for the varying severity of misdemeanours: -10 points, say, and your comment is hidden; -20 and you have to wait half an hour before your next comment is published; -50 and your comment is deleted. Extreme behaviour gets a ban.
The problem is, such systems can be gamed. Even if you have a system wherein you can only vote once for each comment, malicious behaviour from a minority can break the system. How could you combat this? Perhaps by using Amazon’s Mechanical Turk – send all comments to MTurk and pay an uninvolved strangers to answer the question “Is this comment abusive?”. I’m assuming that a combination of RSS and MTurk’s API would make it possible to integrate this seamlessly into the site so that you have an impartial input into whether or not comments are good or bad.

It’s possible to completely outsource comment moderation, but my personal feeling would be that it’s preferable to let the community have a stab at self-moderation first. The more people feel divorced from the way that a community is run, the less they care about it. I think this is why people react less well on threads where the author of the blog post doesn’t engage in the discussion, particularly when they don’t answer (reasonable) questions that are directly put to them. Taking the comment moderation and giving it to some third party, whether a room of moderators at The Guardian or an external moderation house, feels a bit like saying to the community ‘Right, you can’t be trusted’.

So I think there are a few things to pull out of all this:

  • The Guardian needs to chill out about comments. They’re not all going to be Nobel Prize winning essays, and some of them may go off topic. No big deal.
  • CiF bloggers need to interact more with the commenters and stop thinking of commenters as annoying, underemployed and overopinionated. Digs like “My guess from looking at the email addresses is that the list is overwhelmingly male” by Georgina Henry do not show much respect for the people who make CiF as vibrant as it is.
  • The Guardian needs to think about ways in which the community can self-moderate and use technology to facilitate that process, not try to use (shoddy) technological fixes to try and arbitrarily shut people up.

CiF could be a great site, but it needs some significant work and a change in attitude from the bloggers there in order to evolve from the ‘soap-box with hecklers’ model to a being a real blog.

And finally, thanks to tomper for this blog post’s title.

We’re off on holiday now for two weeks. I look forward to seeing if we’ve any comments when we get back…

Comment is F**ked

First off, I want to say that I really admire the ambition of the Guardian Unlimited’s Comment is Free. It is one of the boldest statements made by any media company that participation needs to be central to a radical revamp of traditional content strategies.

As Steve Yelvington said this week:

Editors, please listen. If you’re not rethinking your entire content strategy around participative principles, you’re placing your future at risk.

The Guardian seems to understand this need for participation to be integrated with its traditional content, but as with many media companies: “The future is here. It’s just not widely distributed yet.” It is, therfore, not hugely surprising to find that Comment is Free is having a few teething troubles. Ben Hammersley, European alpha geek and one of the people behind CiF, knew there would be risks:

Perhaps the most prominent liberal newspaper in the anglophone world, opening a weblog for comment and opinion, with free and open user commenting is, to put it mildly, asking for trouble. … This means that we have to employ a whole combination of technological and social countermeasures to make sure that the handful of trolls do not, as they say, ruin it for the rest of us. Frankly, it gives me the fear.

Ben was right to be concerned. Honestly, I wish there were a clearer headed assessment of the risks involved with blogging by media companies. Don’t get me wrong. I think that media companies should blog, but the risks aren’t as simple as they may appear and something on the scale of CiF is of course going to have problems. The Guardian appear to have focused mainly on the risks posed by commenters and have put a lot of energy into figuring out how they can have open comments without falling foul of UK libel law.

But people are people, and you are bound to get abusive, rude or irrelevant comments. Any publicly commentable website will reflect the cross-section of society that reads it, so it’s inevitable that some comments will not be as civil and insightful as we would prefer. Trolls happen.

Just this week, Engadget had to temporarily shut off its comments “because of the unacceptable level of noise / spam / junk / flaming / rudeness going on throughout our boards”.

Where the Guardian has fallen over is in their assessment of the risks posed by their choice of columnist to blog on CiF. Rather than thinking about who would make a really good blogger, they seem to have made the same mistake as the rest of the big media who have tried their hand at blogging: They’ve given their biggest names blogs, despite the fact that these people have no idea how to. Now a bit of a tiff has kicked off between the Guardian’s stable of columnists, the commenters on Comment is Free and the bloggers there. (Thanks to my colleague Nick Reynolds at the BBC who blogged about this internally and brought it to my attention.)

Catherine Bennett writes a column so full of uninformed generalisations about blogging in the UK, specifically political blogging, as to completely lack credibility. She seems to be trying to discredit the Euston Manifesto, a net-born political movement in the UK, by painting it as the creation of a sexually obsessed, semi-literate male-dominated blogging clique. I’ll leave it to you to follow the link to the Manifesto and draw your own conclusions.

Another Guardian columnist, Jackie Ashley, defends professional columnists, and says: “To those of you who think you know more than I do, I’m eager to hear the arguments: just don’t call me a fucking stupid cow.” Polly Toynbee asks commentors: “Who are you all? Why don’t you stop hiding behind your pseudonyms and tell us about yourselves?”

Ms Toynbee why don’t you step out from behind your byline and tell us a little about yourself instead of belittling us? It’s usually worked for me when trying to dampen an online flame war.

I’m sitting here reading her column, and I really don’t understand how she expected this to put out the fires. She asks for civility and for people to tell us who they are, but then she says of one of her anonymous detractors:

What do you do all day, MrPikeBishop, that you have time to spend your life on this site? I suppose the answer may be that you are a paraplegic typing with one toe and then I shall feel guilty at picking you out as one particular persecutor.

What do you expect when you respond to ad hominem attacks with patronising ad hominem attacks? Do you really see this as a solution? Are you treating your audience with the kind of respect that you for some reason think you deserve by default?

Ms Toynbee professes to answer her many e-mails, but I do get the sense that the Guardian’s columnists are simply not used to this kind of medium, they are not used to getting feedback in public where they can’t just hit ‘delete’ to get rid of a pesky critic.

Suw – who I should inform Ms Bennett is female and blogs, thank you very much – likened such old school thinking to this:

It’s like them walking into a pub, making their pronouncements and then walking out. Later, they are shocked to find out that everyone is calling them a wanker.

An interesting comment on CiF from altrui May 18, 2006 12:04 (I can’t link directly to the comment):

One observation – those who respond to commenters tend not to be abused so much. There is a certain accountability required among political commentators, just as there is for politicians. Until now, opinion formers have never really had to justify themselves. I can think of many of the commentariat who write provocative and incendiary pieces which cause no end of trouble, yet they carry on stoking up argument and division, without censure or even a requirement to explain themselves.

Two issues here: Columnists are not used to engaging in conversation with their readers; and the readers have had years to build up contempt of specific writers and are now being given the opportunity to revile them in public. A lethal combination of arrogance and pent-up frustration – no wonder CiF has soured. Question is, can the Guardian columnists learn from their mistakes and pull it back from the brink?

A few suggestions. Don’t treat your audience as the enemy. If you’re going to talk down to your audience, they are going to shout back. And quite honestly, I would say to any media organisation that your best columnists and commentators don’t necessarily make the best bloggers. Most media organisations thinkg blogging is simply snarky columns. Wrong, wrong and wrong.

It’s a distributed conversation. Ms Ashley says: “As with child bullies, I wonder if these anonymous commenters and correspondents would really be quite so “brave” if they were having a face to face conversation.” You’re right, and I am in no way defending some of the toxic comments that you’re receiving. But step back. Read your column as if it were one side of a conversation and think how you would respond.

Many columnists seem to use the British public school debating trick that really is a form of elitist trash-talking. Belittle your opponents as much as possible. Most will lose their heads, and therefore the argument. But, again, step back. Would you ever address someone face-to-face in the patronising manner of your columns and honestly expect anything approaching a civil response? It seems that your debating strategy has worked all too well, and your audience is so angry that they are responding merely with profanity and vitriol.

Again, having said all of that, I’m glad that the Guardian aren’t letting growing pains stop them. They are choosing one of their best CiF commenters to become a CiF blogger. Bravo.

How many news outlet staff actually read their own RSS feeds?

I don’t have a TV. I also don’t have a radio. I get my news the same way any self-respecting geek does, via the intarwebthingy. It used to be that I would pop along to news websites and see what was going on, but then Dave Winer invented RSS and that saved me all the fuss and bother of having to figure out whether a site had been updated or not by conveniently feeding new articles into my aggregator. Wonderful.

Blogs, you see, have been using RSS for almost as long as it and they have been around, because blog software is written by geeks, and geeks do like to save themselves some effort whenever they can. RSS was invented in 1997 when Winer created an XML syndication format for use on his blog. Now no self-respecting blog is without a feed. Yay us.

News outlets, on the other hand, suffer from Chronic 90s Web Buzzword Syndrome, which means that they are still thinking about ‘stickiness’ and ‘eyeballs’. I don’t know about you, but the thought of sticky eyeballs quite makes my stomach churn. However, they have – slowly, painfully, and with no small amount of looking over their shoulder to see if the Big Nasty Sticky Eyeball Eating Monster was creeping up behind them – adopted RSS. Despite the fact that bloggers saw RSS as a no-brainer, the media had to think long and hard before they committed to using a technology which made it easier for people to find out what they had published on their websites and which could, therefore, drive lots of traffic their way.

But they’ve got there. Sort of.

I’m glad that The Times, The Guardian, The Independent, the BBC et al are using RSS. I am, at heart, a lazy wossit, and I much prefer my news to come to me, rather than for me to have to go out and find it. However, I am afeared that the media has not quite paid enough attention to RSS, making the consumption of news via my aggregator a painful and unpleasant experience.

Firstly, no one seems to have figured out that when you change a story, the changes show up in some aggregators. I use NetNewsWire, and it’s set to show me the differences between old and new versions of an RSS feed. It’s true to say that sometimes NNW misinterprets what constitutes a change, but it also exposes all the real changes made to news stories.

The BBC seems to have the biggest problem with constantly changing RSS feeds. I brought this up once with a meeting of senior BBC news execs, and they failed to understand why this is a problem. It’s not just that it’s irritating – changing a story even a little bit causes it to be republished which then flags it up as ‘unread’ in my aggregator, even though I have actually read it. It’s also that changing stories after they have been published is unprofessional and damages the news source’s credibility. When I link to a news story, I want it to say the same thing next week as it said when I linked to it.

When I explained this to the BBC’s news execs, they cried in exasperation that they couldn’t possibly be expected to be right all the time, and where do you draw the line between a major update, which gives the story a new URL, and a minor update? Well, that is a good question. Another good question is, why do you even do minor updates? Perhaps better sub-editing, along with not rushing too fast to publish, would help get rid of the need for minor updates, and any major changes to the story are dealt with by a new article? Or perhaps there is an even better way to deal with additional facts coming in, such as saying ‘Update’ in the article, or some other methodology that I haven’t thought of that doesn’t screw with the integrity of the original.

To be fair, not all of the BBC’s RSS output is affected. Out of nearly 40 items from the BBC in my aggregator at the moment, five have changes. That’s only ~13%, which you might thing is negligible, but I think that figure should be zero.

You’ll also find, when you click through to the site, that the first paragraph is different from the excerpt that’s published in the RSS feed. Considering how concise some of these first paragraphs on the site are, it makes you wonder why the BBC are writing separate excerpts at all, and particularly makes me question why those excerpts get edited. Seems like make-work to me.

Here are a few examples from today, picked in sequence from headlines published around the 15:30 mark and including the copy from the website as well. I have replicated the additions (in italics) and the deletions (strikethrough) exactly as they show up in NetNewsWire, so you have to take into account its inherent over-enthusiasm for marking things as changed.

Virus-hit cruise firm apologises

Five hundred UK holidaymakers are sent home after their Hundreds of passengers whose cruise ship was detained because of holidays were ruined by a severe virus.virus outbreak are to be offered refunds.

Virus-hit cruise firm apologises

A travel company has apologised and offered a refund to hundreds of passengers whose cruise holidays were ruined by a virus outbreak.

US crash sparks Afghanistan riot

At least seven people are killed in the Afghan capital, Kabul, Violent disturbances rock Kabul after a deadly traffic accident involving a US convoy crashes, triggering a riot.military convoy.

US crash sparks Afghanistan riot

At least seven people have been killed in the Afghan capital Kabul after a traffic accident involving a US military convoy sparked mass rioting.

Race against time in Java quake

The United Nations warns that the task of bringing taking aid to the survivors of the earthquake in Indonesia is “enormous”.“enormous”, the United Nations warns.

Race against time in Java quake

The task of helping survivors of Saturday’s earthquake on the Indonesian island of Java is “a race against the clock”, the United Nations has warned.

Worse than the BBC is Google News. By it’s very nature, Google News is all about change, but by god that screws with your RSS feeds. Out of about 80 items, 68 had changes. Now, Google News aims to track news stories from multiple sources, so it is inevitable that their items should change frequently, but it makes it completely useless in an RSS aggregator, because every time I refresh, the items that I had read become marked as unread again because Google News have either done something as minor as changed the timestamp from “5 hours ago” to “6 hours ago”, which is not hugely useful, or added a new source, or substantively changed the copy.

This breaks Google News’ RSS feed in terms of usability. There’s just no way I can continue to have Google News in my RSS reader.

Now, what the BBC does get very right is its timestamps. Items published today have the time published as their timestamps, and items published yesterday and before have the date.

Would that The Times could learn that timestamps are important. Instead, RSS items from The Times are timestamped with the time that I refresh my aggregator, not the time that they are published. I have my news feeds grouped in one folder and I read them en masse. News is highly time-sensitive, and I want to read stuff as it comes in, so having an accurate timestamp is essential. The Times, however, hasn’t figured this out yet. Instead, I get a cluster of items grouped around a single timestamp, and when I refresh, I not only get new items, I get repeats of old items with the new ‘timestamp’. This is not helpful.

For example, I learnt that ‘3,000 UK troops are Awol since war began’ both at 11:09 and at 13:58; and that ‘Abbas threatens Hamas with referendum over blueprint’ both on 25th and 26th of May. These items are in the same feed, and appear to be identical, yet they are showing up twice.

The Guardian is pretty good, compared to The Times, Google News, and the BBC, in the way they treat RSS, as I would expect considering they have people like Neil McIntosh and Ben Hammersley to advise. They get timestamping right – the clusters of articles all being published at once is more to do with their editorial time-table than bugs in their RSS feed.

But there is still room for improvement. Whilst they do edit their RSS excerpts, sometimes just as pointlessly as the BBC, they do it a lot less often, so my main criticism would be that they are inconsistent in their excerpt writing habits. Some articles get a sentence, others get two bullet points; and sometimes the excerpt (and headline) is the same as on the site, and sometimes it isn’t. I have to say, I’d prefer a single sentence excerpt and headline which was the same as the site.

A few examples of what I mean.

Ghost ship washes up in Barbados

· 11 petrified corpses found in cabin· Letter left by dying man gives clue

After four months at sea, ghost ship with 11 petrified corpses washes up in Barbados

· Letter left by dying man gives clue to investigators

· Dozens of others thought to have perished en route

Climber left for dead rescued from Everest

A climber who was left for dead on Mount Everest has been found alive.

Climber left for dead rescued from Everest

· Team forced to leave Australian at 8,800 metres

· ‘I imagine you’re surprised to see me,’ he tells rescuer

Cage swaps Malibu for own desert island

Nicolas Cage has bought a 40-acre undeveloped island in the Bahamas for $3m (£1.6m)

Cage swaps Malibu for own desert island

Dan Glaister in Los Angeles

Monday May 29, 2006

The Guardian

Wherever you go, people stare at you. Paparazzi take pictures, fans ask for autographs, absolute strangers wonder aloud if they once met you at a party. For the hard-pressed celebrity there’s only one way to get away from it all: hide on your own desert island.

The surprise in all this is that the one newspaper who gets it spot on is The Independent. I really can’t fault their RSS feed at all. Timestamps are reliable, and again reveal their editorial timetable with many articles being published in the small hours and few being published during the day. Their excerpts vary in length, but some of the longer ones are more useful than those of other news outlets. Personally, I like longer excerpts because I would rather skim a two sentences that give me a better feel for whether I want to read the article than have just one short sentence that doesn’t tell me much.

Some examples, again with the copy from the RSS and the copy from the site:

British journalists killed in Iraq

Two British television journalists were killed in Iraq by a roadside bomb today.

British journalists killed in Iraq

PA

Published: 29 May 2006

Two British television journalists were killed in Iraq by a roadside bomb today.

Bush ‘planted fake news stories on American TV’

Federal authorities are actively investigating dozens of American television stations for broadcasting items produced by the Bush administration and major corporations, and passing them off as normal news. Some of the fake news segments talked up success in the war in Iraq, or promoted the companies’ products.

Bush ‘planted fake news stories on American TV’

By Andrew Buncombe in Washington

Published: 29 May 2006

Federal authorities are actively investigating dozens of American television stations for broadcasting items produced by the Bush administration and major corporations, and passing them off as normal news. Some of the fake news segments talked up success in the war in Iraq, or promoted the companies’ products.

Indonesia Earthquake: As a people, they already had little – now they are left with nothing

In the morning, Salim retrieved the lifeless body of his three-year-old son, Sihman, from the ruins of their brick and bamboo hut. In the afternoon, he buried him, digging the grave himself. As night fell, he searched through the rubble of his former home for scraps of food. “I have lost everything,” he said.

Indonesia Earthquake: As a people, they already had little – now they are left with nothing

By Kathy Marks in Bantul, Indonesia

Published: 29 May 2006

In the morning, Salim retrieved the lifeless body of his three-year-old son, Sihman, from the ruins of their brick and bamboo hut. In the afternoon, he buried him, digging the grave himself. As night fell, he searched through the rubble of his former home for scraps of food. “I “I have lost everything,” he said.

I like the fact that the RSS feed and the website copy are identical. To me, that’s ideal – what I see in RSS is what I get on the site. I also can’t see any evidence of changes, although I will say that this RSS feed is new in my aggregator so maybe this point will clarify itself over time.

Now, all this criticism may seem like pointless nit-picking. Perhaps some it is down to my inner editor screaming for consistency and my inner blogger begging for honesty, but certainly some of this has a direct impact on the usability of RSS feeds for the reading of news.

I want news. I have no problem with the idea of clicking on a link in my aggregator and reading the full article on the news outlet’s website – this is not a plea for full posts (although hell, that’d be great and if Corante can put advertising in their RSS feed, so can anyone, but that’s not the point I want to make).

It’s a plea for journalists and media IT staff to think a little harder about how news is being read these days. RSS is not a fad, and it’s not going to go away. It is going to flourish, with more and more people using it to get their news from many disparate sources. It is in your best interests to ensure that your RSS feeds work, that your editorial policies take into account the effect of new technology on the transparency of your medium, and that you strive at all times for honesty even if that means owning up to your updates (note, ‘update’ does not necessarily mean ‘mistake’).

Google News is revealing your reliance on syndicated content, and RSS is revealing your edits. If you want to remain credible, you must adapt. In an increasingly competitive world, where people choose which news sources to read not just based on content but also on usability and accessibility, can you really afford not to?

Nothing more than pollution

Blog astroturfing*. Someone please go and kneecap these people. I don’t know how much of this is bullshit, how much of it is real, and I really don’t care, because in either case this is just horrible, nasty pollution. I loathe astroturfers as much as I loathe word of mouth advertisers. It’s all just social spam and should be treated as such.

Finally, we have been receiving a lot of emails asking us why we are giving away seemingly-sensitive information. I can assure you that we are not jeopardizing our investment. Any discerning reader should know not to trust all of the information provided by admitted-astroturfers. I can tell you that a few of the blogs expressing outrage over the emergence of our enterprise are not written by who you think they are. I can also tell you that some of the posts made to this site will be provided by members of our blogforce. Have a good weekend.

Smug fuckers.

* Astroturfing: In American politics and advertising, the term astroturfing pejoratively describes formal public relations projects which deliberately seek to engineer the impression of spontaneous, grassroots behavior. The goal is the appearance of independent public reaction to a politician, political group, product, service, event, etc., by centrally orchestrating the behavior of many diverse and geographically distributed individuals.

As many reasons as there are bloggers

Mark Brady takes issue with an assertion made in this Sunday Times article that bloggers are like lemmings, all trying to find fame and fortune. Of course, it’s obvious that in fact there are as many reasons to blog as there are bloggers, and most bloggers couldn’t give a damn about ‘fame’ or ‘fortune’.

My beef with this is that the bloggers that “assume your [their] blog will be one of the tiny fraction that is brilliant” are not in fact the motives of the entire blogging population, or indeed a very large part of it. It’s a common attack pointed at bloggers. There are a lot of people blogging out there and not all of them are doing it for the same reason. One reason to blog is to reach friends and family without sending blanket emails to people. Another might be to keep a record of one’s life. Another might be to record notes and thoughts for a PhD, or other research project.

It’s an important point, and one that I keep seeing forgotten, over and over again, even by some long-time bloggers who should know better. Those of us in or heading for the spike are so very much in the minority, and we should not forget that. Most bloggers, the great vast majority of bloggers, simply don’t care about the power law, they don’t care about metablogging, they don’t care about stats. They just want to do what they do the way that they do it and that is, as far as I am concerned, wonderful.

Recently I’ve seen an increase in articles about blogging in the press, and most of them really don’t get it. I could fisk this Times piece so easily, but I just can’t be bothered. Reading it is like repeated poking myself in the eyes with a sharpened stick. I just want to scream ‘stop thinking ‘broadcast’, you morons!’, but I know my voice will just get blown away in the wind of rank stupidity and cluelessness.

I need to find some constructive developments to blog about instead, otherwise my ‘blog fuckwittery’ category is just going to take over the blog, like Japanese Knotweed rampaging through the gardens of England, unstoppable and voracious.