ReadWriteWeb

The Second Coming of Content and RSS Feeds

Written by Richard MacManus / November 21, 2005 10:52 AM / 11 Comments

Feedburner CEO Dick Costolo has just posted what I think is a milestone post for RSS and Web 2.0: How feeds will change the way content is distributed, valued, and consumed. In it he expounds on the future direction of his company Feedburner, which I've long considered to be the leading company in the RSS Publishing space. (NB: this post is NOT about the other RSS news of the day, Microsoft's Simple Sharing Extensions. I'll address that in a separate post).

There are 3 themes in particular from Dick's post which grabbed my attention:

1) RSS feeds encompass much more than blogs now

2) Feed becomes input to content on the site

3) Focus on the feed item - attach threads to the item and track it across the Web while it gets remixed and re-published.

With regard to 1), many of us have been noticing the trend for RSS feeds to extend into non-blog content. 2005 has really been the year in which that trend has solidified, as Dick's venn diagram perfectly illustrates:

RSS venn diagrams
Graphic courtesy of Feedburner

Feed becomes input to content on the site

This is where it gets really interesting. Feeds becoming input to the website reminded me of Erik Benson and others' experiments with the Bloglines API back in February 2005. At that time, Erik re-modelled his whole blog so its content was entirely made up of inputs from his many feeds. He did that because his content was being published all over the Web - in del.icio.us, Flickr, 43Things, LiveJournal, other blogs. So feeds became his method for keeping track of all his content and bringing it all together.

It makes total sense for Feedburner to be right in the middle of this 'pulling together' of feeds from all over the place - and other feed input mechanisms. People like Erik have the programming knowledge to manage their feed 'inputs' this way, but the vast majority of people (like me) would rather a service like Feedburner did that work for us - via our Feedburner feed and some simple hook-ins to systems like Movable Type, Wordpress and Typepad.

Dave Winer recently pointed to a post by Adam Green, which explored similar territory. Adam thinks 2006 will be the year the Web explodes:

"The explosion I am talking about is the shifting of a website's content from internal to external. Instead of a website being a "place" where data "is" and other sites "point" to, a website will be a source of data that is in many external databases, including Google. Why "go" to a website when all of its content has already been absorbed and remixed into the collective datastream."
(emphasis mine)

His post specifically referenced Google, but I think this trend is much larger than even Google. The thing which is going to tie all this together is of course feeds. Mainly RSS, but perhaps Atom's much-vaunted extensibility will come into play too.

Focus on the feed item

This gets to the heart of the matter and I think Feedburner is onto something big here. Feedburner now views the item (e.g. a single post from your blog, or a specific search result in a topic feed) as "the atomic unit of measure in the feed", which will in turn lead to Feedburner managing syndicated content "at a more atomic level by attaching 'threads' to the item." It reminded me of the Design for Data and "content will be more important than its container" themes I was big on at the end of last year and beginning of this (and which I will be re-focusing on now). Incidentally those R/WW posts from a year ago led to a collaboration with Joshua Porter on a Digital Web article, which led to an O'Reilly Media book contract. But I digress...

If you think about it, focusing on the feed item is a profound change in how we think about RSS feeds. Up till this year, most of us thought of RSS feeds as a way to subscribe to single sources of content. But over 2005 it's become apparent that content is being remixed, mashed up and re-published across many sources - leading to heated ethical debates over content rights and confusion amongst publishers on how to 'monetize' (sorry I can't help but use that word) their content. Fred Wilson had a nice post on this theme recently, entitled The Future of Media (aka Please Take My RSS Feed).

The 2.0 Toolset

Dan Saffer recently explored this issue from a different angle, a post entitled The Web 2.0 Experience Continuum. Dan's post is all about the need for a next-generation tool set to deal with what he calls semi-structured and unstructured Web experiences. He wrote:

"The tools we’ll use to find, read, filter, use, mix, remix, and connect us to the Internet will have to be smarter and do a lot more work than the ones we have now."

What he's referring to is at the aggregation and filtering level, whereas Feedburner is at the feed/item level. So I think there are opportunities for developers to create those Aggregation 2.0 tools, which will complement what Feedburner is in the middle of building. 

webfeeds
Graphic courtesy of Leigh Blackall

I've got my own ideas on what the next generation of Aggregator/Filter tools will look like, so perhaps I'll even get stuck in and try to build part of this vision out myself. Exciting times!


9 TrackBacks

TrackBack URL for this entry: http://www.readwriteweb.com/cgi-bin/mt/mt-tb.cgi/2563

Comments

Subscribe to comments for this post OR Subscribe to comments for all Read/WriteWeb posts

  • Hey Richard. I forgot if I've told you about this already, but we made the aggregated feeds a part of 43 People a while ago: Here's your feed page:

    http://ricmac.43people.com/feeds

    A couple things it does: anyone can suggest a feed that you own. You ultimately have control over your selection of feeds, but people subscribed to you will automatically inherit any changes in your set of feeds. It's similar to feedburner in that a person's feeds are aggregated in one place, but I think the fact that you can aggregate anyone's feeds (regardless of whether or not they have a 43 People account) is pretty cool. Anyway, I normally wouldn't do all of this self-promoting, but thought I'd share since it's on topic. :)

    Posted by: Erik Benson | November 21, 2005 11:17 AM



  • Re. aggregation and remixing etc etc - I don't disagree, but there's only a very limited set of things (items, feeds, one or two extensions) supported by the feed data model. What's needed is a more generic model that can represent arbitrary data in a Web-distributed fashion. Best bet right now are the Semantic Web technologies, which can integrate feed data along with pretty much whatever else you like - see :
    http://www.w3.org/2005/Talks/0517-boit-tbl

    Posted by: Danny | November 21, 2005 11:38 AM



  • Great Post!

    I think the tool you are talking about is feeddigest.com

    Posted by: Daniel Nerezov | November 21, 2005 8:41 PM



  • I spoke with Erik via email, but just want to give a public hat-tip to him for letting me know about the 43Things feeds. Excellent.

    Danny, thanks for the link to that Tim Berners-Lee talk. I'm definitely going to read that.

    Daniel, thanks for the comment. But with all due respect to FeedDigest, what this post is about is *way* beyond what they've built. The challenge is for all of us to make that step up to Aggregators 2.0 (forgive the Yet Another 2.0 reference).

    Posted by: Richard MacManus | November 21, 2005 10:33 PM



  • i think services like the searchfox "intellignet " reader are going to help define how we read content in the years to come. However the 2 i have seen so far namely searchox and findory both have to do something about the problems described. I think that if someone can actually come up with and intelligent, adaptive aggregator that willn do things like filter posts in a way that searchfox does and delete duplicates ect then they stand to make a killing with sufficent marketing

    Posted by: Alterion | November 22, 2005 2:24 AM



  • Great post. I've been selling the idea of feeds providing content (as well as pushing out content/blog content via RSS) to my clients for a while. It's especially useful for clients who don't/can't generate large amounts of content themselves but whose sites provide a hub of information for their users. There has been a definite shift in attitude towards content in the last 12 months (for the positive). I think you're right, 2006 is going to see big changes.

    Posted by: Sam Smith | November 22, 2005 8:26 AM



  • It would be really awesome if there could be a way (either a standalone app or a Web 2.0 weblet) that allowed me to "greenlight" RSS items that I am reading. My friend could then tune into what it is that I have "greenlighted" and I could tune into what he has "greenlighted" that I don't have already. Like-minded friends could read what we "greenlight" instead of personally being in the business of "greenlighting" RSS items.

    Now THAT would be cool.

    Posted by: Joseph Dowdy | November 22, 2005 11:47 AM



  • Joseph,

    The technology to "greenlight" posts that you read and automagically add them to your own feed already exists, and it is called reblogging: http://www.reblog.org/

    Posted by: Chris Anderson | November 22, 2005 2:22 PM



  • hi Richard,

    Great post, and very relevant to some of the thinking we've been doing for SuprGlu. Our service aims to provide a very easy way for people to create blog-like pages for their scattered (but RSS-accessible) content. We're still in the early stages of development, but I think it directly addresses the ideas you've presented here!

    http://www.suprglu.com

    Posted by: danny | November 22, 2005 3:51 PM



  • Hello RSS lovers,

    Although I have been using XML for seven years, I just recently jumped onto the RSS bandwagon by creating a windows based RSS ticker that scrolls my favorite feeds without having a browser open. If I see a headline or an update scroll across the screen, I just click on the link and it opens a browser and I read the article. So far, I love using it and I have other ideas to improve on it.

    Please take a look and give me your feedback.

    www.mightyticker.com

    Thanks,
    Shawn

    Posted by: Shawn | November 26, 2005 4:38 PM



  • Great article, here is an example of a cool implementation:

    http://home.comcast.net/~flyflyaway/sample_implementation_rss.htm

    Posted by: MoNKMoJo | November 30, 2005 12:15 PM




RECENT JOBS



TEXT LINK ADS


RWW PARTNERS


RWW READERS