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.


COMMENTS / 12 COMMENTS

Poor old Observer

Neil McIntosh writes in praise of excepted RSS, and drops in this little nugget:

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 (…

Pigsaw Blog thought this on Jun 09 05 at 5:44 pm

If you can’t engage them, beat them redux

The Guardian’s Neil McIntosh (who is a really nice bloke) has written a rant on why full text RSS feeds “suck”. It’s 8PM, I’m supposed to be spending time with the most neglected person in my life, and I haven’t…

The Hole thought this on Jun 10 05 at 8:21 pm

RSS switch

I’ve decided to experiment by switching my RSS feeds from full text to summary. It’s all his fault.

Englishman in New York thought this on Jun 10 05 at 10:24 pm

4 +1 GrĂ¼nde gegen Volltextfeeds

So, for the record, here are four good reasons why I think full text feeds suck. De plus: [X] Keine Sekunde Zeit grad am Template zu fummeln, echt….

selbr.de thought this on Jun 16 05 at 11:00 am

It’s definitely possible to have an indication that there’s a conversation going on.

RSS 1.0 (which is the version that GU are using) defines the mod_annotation module which allows the individual items to contain the URL where discussion of the item takes place. It should be simple for Ben to add this to the GU blog RSS feeds. Of course, it’s possible that common RSS readers don’t take any notice of it :(
It’s even possible to have the complete list of comments in the RSS feed. Take a look at the RSS feeds that Robin is producing over at http://perfect.co.uk/ (e.g. http://www.perfect.co.uk/comments.xml ).

As someone who is happiest reading his RSS feeds in Bloglines, I’m a big fan of full RSS feeds. The fuller the better in my opinion. The only one of your points that rings true to me is point two. Much as I dislike them, I realise that ads are a necessary evil and we’ll only see more and more of them in RSS feeds over the next year.

Dave Cross thought this on Jun 09 05 at 1:03 pm

I’m with you Neil.
Reading full feeds over a dial-up access when pics are included brings everything to a halt.
Feeds are for speed; quick intro, yep I’m interested, click and I’m in…

Craig McGinty thought this on Jun 09 05 at 4:50 pm

I vote for 2, 3, and half of 4.

Page impressions (for ego and ads) are indeed what it make it all worth while. I’d tell you how many times a day I check my blog stats, but — like a doctor listening to an alcoholic saying how much they drink — you’d only double it to get an accurate answer.

You certainly don’t want people to nick your work. Those for who this matters most, I suspect, will be those with ads — the commercial content producers.

I agree with half of 4 because I find it depends on the feed. For a feed in which I often find relevant content, and which has one post every couple of days, I want the full text. It’s much easier to read. But for those which produce a lot of content, of which only some is of interest, I want summaries, because otherwise it’s a pain to have to scroll down the whole page to scan the news.

So, 2.5/4 from me — but you only needed to score 1/4 to win the argument, so thumbs up.

Nik thought this on Jun 09 05 at 5:13 pm

I’m in the full-text feeds camp.

Feeds get read in NetNewsWire on my Powerbook, and about half the time I’m reading them I’ll be without a network connection; on a train, between meetings, etc.

It’s much easier to read and flag a full-text feed for later follow-up (including checking the comments) than to make a sensible decision about flagging a frustratingly short snippet for later download and reading.

It is also, of course, possible to provide feeds of the comments if you want to.

I also like having access to articles I’ve already read, whether I’m on- or offline, as my own posts may well come a day or two after I’ve read a number of pieces, to which I’d then like to refer people. It’s easier to do that if the text that resonated with me in whatever way is available to me when I’m writing my own post.

Oh, and with about 500 subscriptions in NNW, I’ve not seen the slow-down problem to which you refer… ?

Paul Miller thought this on Jun 09 05 at 10:04 pm

First of all, any feed is better than no feed, no matter how bad it is :) .

I have to say I do prefer full content feeds. My own feeds are full content, although there is also an excerpts feed which is quite popular. Longer entries, i.e. those that use the Extended Entry field in MT, only have the first portion in the feed with a notice that it’s continued on site - I’d call that a good compromise.

In RSS 2.0 the comments tag can be used to link to an entry’s comments section - I use this and many aggregators now support it. Some even support the slash:comments tag and will display the number of comments posted already - SharpReader does this, for example.

As for theft of content, generally I’m not too bothered about this as my stuff is licensed via Creative Commons anyway and the license metadata is in the feed. Not that anyone ever notices that kind of thing, mind.

All in all, I think there are good reasons to go either way which vary from site to site. And at the end of the day, it’s actually having the feeds in the first place that matter the most, I feel.

And sorry for not chatting to you at the Geek Dinner :)
(Incidently TypePad says my URL is invalid. Strange)

Neil T. thought this on Jun 09 05 at 11:45 pm

My tuppence: I’m not convinced either way… because (heresy!) I’m not yet convinced by RSS.

I mean, I know it’s great in principle, but nobody’s done anything with it that makes me go “wow”. There’s nothing about using it that excites me. I like websites. RSS is just a bit, well, characterless.

Anyway, I suppose I’d prefer to be able to choose full text or extracts as I wanted. That way I could stay in my bunker or not, and the arguments above (and those elsewhere) would be fairly redundant. There’s not much choice either way at the moment, and that’s one thing that should change over time.

bobbie thought this on Jun 10 05 at 11:56 pm

I polled by half-dozen readers, and they split 50/50 between full text and summary. What I’ve done now is provided full-text category feeds, and a summary aggregate feed.

Is it possible to put MT Comment links in an RSS feed, or will they not work without the Javascript?

BTW, my weblog URL, http://www.kalyr.com/weblog is being blocked as an ‘invalid URL’.

Tim Hall thought this on Jun 12 05 at 10:25 am

I’ll admit that nine times out of ten, my RSS aggregator doesn’t need to do more than give me a snip - I know from a few lines if it’s something I want to read and off I go to the web browser to pull it up properly.

HOWEVER.

A “proper” RSS feed is a great thing if you want the posts without being subjected to the comments, or, as is often the case in the Wide Wide World Of Webcomics, the site’s interface is such horrendously undercooked ass that pulling the content through RSS is the only way to get at it in a sane, well organized fashion that doesn’t induce hair pulling.

So. I love the reformatting options (let’s be honest, some of the worst sites on the web are the shiteheaps chunked out by so-called “web designers”), but by and large I use it for what it’s best at - checking sites when they’re updated, as opposed to when they haven’t been.

solios thought this on Jun 14 05 at 9:13 pm

SPEAK / ADD YOUR COMMENT
Comments are moderated. I'll delete unpleasantness. Email me if you spot a comment that crosses the line.

XHTML: You can use these tags: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong>

Return to Top