We just launched the first version of a new service this evening that we're very excited about. The service allows users of the photo sharing site Flickr to splice their public photos into another feed (like a blog feed). The announcement about our partnership can be found here.
Many of our publishers have expressed the desire to be able to use different publishing tools for different purposes (eg, a blogging tool, a bookmarks tool, a photo sharing tool, etc.) but still have one resulting feed that friends, family, and subscribers could access. Tonight's announcement is a fun step in this direction.
Burn This! - The Feedburner Weblog: Feed Splicing, Part I
I talked about adding this functionality -- feed splicing -- into Drupal. Just like you can add a home page or other URL to your user profile today, in the future you should be able to also add a URL pointing to any feed that is you, and Drupal will aggregate it for you.
This is already possible today through Drupal's aggregation capabilities, but I want to take it to the next level, doing personal aggregation for every member account in a community. Richard is doing this for his many weblogs using Magpie, and the effect is good -- especially when he can do things like post to Urban Vancouver but then still have the item show up on "his" site.
Congrats, Flickr-ites. And yes, of course I'm trying it out. I had recently switched the "visible" feeds here to use Feedburner (although I'm not redirecting the existing Drupal URLs at this point). But I don't think my Flickr pictures mesh well with the business nature of this site. Herewith the Feedburner feed of my personal site.
Side note: this breaks Technorati. I've never believed in them as a long term play in any case. It's interesting to see how many sites rely on instant spidering of updated feeds.
Comments
A MUST MUST MUST with Drupal
B. Mann,
Yes, you got it correct. "I talked about adding this functionality -- feed splicing -- into Drupal," THIS IS A MUST FOR DRUPAL! Please I'm begging you. Just do it.
I think my write up was a lit
I think my write up was a little confusing. Feed-splicing is already done by Drupal, and it's in CVS right now. Drupal has always had the ability to aggregate arbitrary feeds (even arbitrary feed items) through the use of keyword tagging and so-called "bundles" (that's how I build my Interesting Blogs and other bundles).
But in CVS, Drupal also generates a combined, "feed-spliced" feed of each of these bundles. So you could get, for example, a combined feed of every single person who writes a blog in Vancouver.
So that's at the site level. A site owner can roll their own custom bundle of feeds. But my idea is to implement at the Drupal user level as well. So, you could go to your user account page and add "your own" feeds, and it would splice them all together. And someone could subscribe to "you".
Building video servers
I find your splicing comments interesting because they make me think of broadcast studio master controls, which take inbound feeds, splice them together, and create one master feed that goes out for broadcast. This is how the regular content and the ads are spliced together. Much of this is now automated and you can practically build a complete TV station in a single server as long as you have no live content that requires flexible scheduling. Makes you go hmmmm........ (from Troy Angrignon at http://www.troyangrignon.com)