About 6 months ago, I burned my blog’s RSS feed to Feedburner. I was using WP-Shortstat as a WordPress plugin, and the RSS feed subscribers didn’t look realistic (and they weren’t!) as it was over reporting on the number of subscribers. I’ve been happy with Feedburner since, and it provided a very simple view to my feed’s statistics, and there was a plugin to view the statistics right in my WordPress dashboard.
When I was syndicated on Planet Foresight, I created a Linux feed on Feedburner so those users weren’t subject to my entertainment and copyright rants, and later I burned a feed of the Foresight Linux Newsletter as well.
Since then, I continue to learn more about Feedburner and its features, in no particular order:
- Feedburner takes over Steve Smith’s WordPress plugin for Feedburner stats, renames it Feedsmith.
- Rick @ Feedburner recaps why partial feeds are a bad thing. I couldn’t agree more – I’m too lazy to follow links out of my feedreader just because a site wants hits. I’ll usually end up unsubscribing after a while unless the site has really, really good content, like TV Squad.
- It might be fun to create a Headline Animator – if I could do a non-cheesy looking one, might be a good way to market the Foresight newsletter
- I can’t believe I didn’t know about FeedFlares until today – what a great concept. Add little tags to the end of your posts, such as “add to del.icio.us”, “email author” etc. See the whole list here. I’ve already updated my feed. And the have an open FeedFlare API to create your own.
I also use Feedburner as tool combined with the Foresight Wiki based on Confluence. Confluence gives you the ability to build a feed right from the dashboard, but it’s really only useful for tracking a whole space, and not independent pages.
The first feed I built was the Foresight Linux Newsletter. Using Confluence, I created a RSS 2 feed based on any news post in the Newsletter space. Confluence gave me me a feed that looks like this:
Not necessarily human readable, or easy for a subscribe to type in to their feedreader, though possible using cut and paste.
I took that feed, and burned it in Feedburner, and got this:
Much better, and now I have statistics tracking for our subscribers (Which we need more of!)
The second feed I created in Confluence, was for the Package Request page on the Wiki. On this page, users can request software packages to be added to the Foresight repository, so they can install them via Conary, instead of building and compiling the software by hand.
Confluence doesn’t give you an option, at least that I could find, to build a feed for a specific page. First, I gave the the wiki page a specific label, “package-requests”. I then went to the Feed Builder, and chose to build a feed in the Developer space, with a label “package-requests” and to show all new edits and comments on the page. Confluence gave me the feed:
I burned that in Feedburner and came up with:
So if you want to add that to your feedreader, you will see all requests and comments for new packages, as well as edits to the page when someone marks a package as added to the repository.
I’m really starting to dig the power of Feedburner.