RSS gets me into terrible trouble, you know. At blog socials, like Tuesday night’s very enjoyable geek dinner, there’s always someone ready to quiz me on why either this site, or the Guardian’s weblogs, don’t have "proper" RSS feeds. Now, for those who don’t know the code, "proper" in this context means "full text". Why am I not distributing the full text of all those blogs?
An example of this comes from the wonderful Boing Boing where, in an otherwise very complementary post about the Observer blog, Cory Doctorow initially thinks the feed is full text, only to discover it’s not. "The RSS is fulltext (crap, no it’s not — this is such an important detail, Observer — get it right!)"
Important? Really? Why? I know the reasons why syndication is hugely powerful, useful thing – and most of those positive things have to do with aggregating snippets of information, firing them about easily and aggregating them in new and interesting ways. We don’t want RSS being an alternative to old-fashioned web pages for big slabs of text, do we?
Well, maybe some folk do. So, for the record, here are four good reasons why I think full text feeds suck.
1/ Blogs are about conversations. By failing to represent comment activity, and by making it harder to leave comment, RSS feeds kill conversation by allowing readers to stay in their little feedreading bunkers. Now, I know many superstar blogs don’t have comments. But ours do. And feeds offer no indication of the conversation that’s taking place around that post, or that site. For instance, the design of this site deliberately puts new comments right at the top of the front page, to show what posts are active. I hope people are tempted to comment just because they see what posts have a conversation going on. At work, when we switched RSS from full to excerpt on Onlineblog a year or two ago, comments per post jumped up, and today all our blogs have fantastic post to comment ratios. That would fall if our RSS feeds went full text. (And, for the record, I think comments trump RSS every time. Yah boo sucks).
2/ RSS reduces pageviews. And pageviews are vital for ego (personal blogs) or ad serving (commercial blogs) or justifying the time spent (all blogs). And I keep hearing that putting ads in your feed isn’t cool either, so I can only assume people would like to have content without cost or even the burden of an ad nearby, which is a nice idea, but somewhat unsustainable in the real world.
3/ Full content feeds make it easy for people to nick your work. I think web-based aggregators are bad enough, and there have long been sites claiming to aggregate sites for people’s convenience, but which – in reality – skirt the boundaries of plagiarism. And now it’s getting worse – there are services out there taking RSS feeds, reformatting into HTML, and thus making it a skoosh for those feeds to be displayed on webpages sans context or, even, attribution. Read/Write Web has been doing some interesting stuff on this.
4/ Full content feeds are a pain. My RSS reader of choice – NetNewsWire – shudders to a halt when confronted with full feeds off the likes of Jay Rosen’s Pressthink. I’d be a much happier bunny if I could decide what to read – rather than download the whole damned thing every time I fire up.
So, in short, RSS is a useful way to shunt headlines and brief descriptions around the web, and lots of other things. It’s another thing that’s making the online news environment such an interesting place to be at the moment (Simon Waldman, our director of digital publishing, gave an interesting speech recently on its broader implications for the online publishing biz).
But, today, as an alternative means of distributing all your content, it sucks.