Not too many sites use RSS 1.0 any more. It’s a completely different standard than RSS 2.0 — even the abbreviation stands for something different: RDF Site Summary (instead of Really Simple Syndication). But recently, I wanted to subscribe to a hilarious web comic called The Oatmeal, only to find that its feed uses RSS 1.0. Not to be discouraged, I decided to add RSS 1.0 support to my feed-to-email script, feedmbox. Download links below.

I’ve also updated the license to OWL 0.9. Enjoy!

I’ve been using Newspipe for a while now to send my subscribed feeds to an email folder, but there are a few things I don’t like about that arrangement. Newspipe is not actively maintained. I thought about porting it to FreeBSD (it isn’t in ports yet) — but it’s somewhat Windows-centric (it uses a .INI file, for example), and it’s licensed under the GPL. That makes three strikes. I decided instead to write my own utility in Ruby to do just what I need.

From the links below you can download the feedmbox utility. The README should tell you all you need to know. It takes OPML input and turns that into email output by polling each feed in the OPML document and converting each new item into an email message. Feedmbox uses a SQLite3 database to keep track of which items it has seen before.

To convert HTML to text, I started with this version from Chew, and then tweaked it to my own requirements. Chew’s version didn’t preserve “title” or “alt” tags from images — mine prefers “title”, but will use “alt” if “title” is not present. Chew’s also used CGI.escape, which doesn’t handle all HTML entities. I switched to using the “htmlentities” rubygem instead.

So, I have all of my feeds specified in a file named sterling.opml in my Personal folder. I want my feed emails to go to my Mail/feeds folder, which is in mbox format. I added a crontab entry to periodically execute the following command:

feedmbox.rb ~/Personal/sterling.opml >> ~/Mail/feeds

That, my friends, is Really Simple Syndication.

When we last left our valiant plugin, it had just succeeded in implementing all of the features requested by László Monda, except for one: László wanted to be able to use the rss.png from /wp-includes/images to avoid an extra GET request when loading the page. Although I had provided a way to override the location for the images, he didn’t want to put all of the images in /wp-includes/images, because that directory gets overwritten by upgrades to WordPress. He resorted to making a one-line custom modification to the code.

Well, I hate forcing people to patch my code for the functionality they desire. I can also see his point. Although the overhead of a single GET does not concern me much, I imagine in bandwidth-restricted circumstances every little bit helps. On the other hand, I don’t want to hard-code the location of this image, because existing users may be customizing the images used for the opml-browser plugin. So, I implemented László’s change as an option: the “Monda option” — or more verbosely, “Use rss.png from wp-includes/images?” This option overrides the “Image URL” option for rss.png only.

This one change accompanies a bump to version 2.4. Download links below.

Oh, and if you’re wondering about the word “legendary” in the title of this post, just ask Google a mindent tudni.

I never seem to be able to stick my fingers in a WordPress plugin without getting them nasty. After I released version 2.2 of the OPML Browser, László came up with several more suggestions. I didn’t agree to all of them, but here are the ones I’ve included in version 2.3:

• Added option for “Show clickable folders for categories”, with a default value of true. You can now uncheck this option to suppress the folder icons. Of course, if you do that, the user cannot collapse categories.
• Escape any special HTML characters found in the text, title, description, xmlUrl, or htmlUrl attributes, but without double-escaping.
• Changed img tags to use the “id” attribute instead of the obsolete “name” attribute.

The last two items allow the widget to validate cleanly at html5.validator.nu.

I shall now go wash the PHP off my hands.

A user (I have users?!?) named László Monda offered some enhancement suggestions for my OPML Browser plugin for WordPress. I have implemented them in version 2.2, which you can download from the links below.

Specifically, I added the following options:

• Image URL, defaulting to the previous hard-coded location (images subdirectory). László wanted to be able to reuse the rss.png in the /wp-content/images directory instead of loading two RSS icons. He can do that now by changing the “Image URL” in the widget options to that directory and making sure that all of the needed images are located there.
• Include OPML descriptions as tooltips, with a default value of true. If you uncheck this option, then no tooltips will be displayed. I also added a delay of one second between the mouseover and the tooltip display.
• Include “Get this widget” link?, with a default value of true. If you uncheck this option, the link will not be displayed and you must either plaster my praises all over your blog or reconcile your conscience to your ingratitude in some other way.

I also took this opportunity to move the OPML Browser project into a Mercurial repository on BitBucket, and to offer a .tar.bz2 download in addition to a .zip format. Enjoy!

I’ve been a much happier feed consumer since I started using Newspipe to pump my feeds to mutt. Subscribing to new feeds, however, got a bit more complicated. I’d have to edit my OPML file and make sure I got the new element inserted with all the right syntax. Even before that, I’d have to find the link to the feed I wanted. You’d be suprised how many sites don’t provide a direct link to their feed, so I’d often have to view the page source and search for an RSS autodiscovery link.

Then a few days ago, a reader asked me if I knew of a utility that would list all the autodiscovered feeds on a site. Since I could obviosuly use the same thing myself, I wrote it. It’s called feeds.rb. You just type a command like this at the command prompt:
feeds.rb http://example.com

… and it lists out all the feeds that have autodiscovery links on that page.

The next step, of course, is to automate including one of these links in my OPML file. Yes, I’m lazy — it’s one of the traits of an efficient programmer. I created a second script, called opmlsub.rb:

opmlsub.rb myopmlfile.opml -s http://example.com > myopmlfile.new

This one takes the given URL and adds an outline element for it to the incoming OPML file, spitting the result to stdout. If the URL is a feed, it will just use it directly. If it’s an HTML page, it will look for autodiscovery links and use the first RSS 2.0 link, if available, or the first ATOM link if an RSS 2.0 link can’t be found (I have to prefer RSS 2.0, being a member of The Board).

You can also instruct opmlsub.rb where to place the new link. The option -i TEXT specifies the value of the “text” attribute of an existing “outline” entry inside which the new link will be placed, as the new last child element. If not specified or not found, then the new element will be the last child of the “body” element.

I didn’t include options for editing and deleting elements. That’s easy enough to do with vim on the rare occasions when it’s needed.

Finally, I wanted to be able to do all this while looking at a page in Firefox (or Chromium, when it’s released on FreeBSD). So I created a third script named ‘clipsub’, which takes a URL from the clipboard (using xclip) and adds it to my OPML file without any intervention. I then mapped that to a key shortcut (mod4+shift+S) in my window manager, xmonad. Because opmlsub.rb validates a subset of the feed, I don’t have to worry about accidentally invoking this when a non-URL is on the clipboard. If any error occurs, clipsub pops up the error message in an xmessage window.

So now, when I see a site to which I’d like to subscribe, I just press ctrl+L (highlight the URL in the address bar), ctrl+C (copy it to the clipboard), and mod4+shift+S (subscribe) — and the posts start magically showing up in my feeds folder in mutt.

Mercurial repository on BitBucket

On this site I write examples in a variety of programming languages.  I’m sure that some of my WordPress (PHP) audience gets tired of hearing about Synergy/DE, Ruby, and C#.  Some Rubyist readers have commented that I should stick to writing about Ruby.  I experienced a wave of subscriptions from Lispers when I posted twice about Lisp, but they’re probably sick of all the non-Lisp posts I’ve written since then.  So, it’s time to give subscribers more choice.

Take a look over at the right sidebar (here, if you’re in a feed reader).  Scroll down below the ads and notice the new “Categories” widget.  You can now subscribe to any category by clicking the orange RSS icon beside its name.  Categories that contain other categories also include their content in the feed.  So, you can subscribe to specific programming languages, or the “WordPress” feed, or the “.NET” feed, or the “OPML” feed – depending on what you’re interested in reading.  Note that I often post under more than one category, so for instance if you subscribe to “PHP” you’ll get a superset of “WordPress” — because all WordPress posts are also under PHP – at least, so far.

How you, too, can display this glorious new Categories widget on your site

Surprise!  It’s really my trusty OPML Browser widget.  But it’s feeding from an OPML file that is automatically updated by a new WordPress plugin that you can download below.  This plugin generates an OPML file containing links to your categories and their feeds.  You can override the feed URLs (in case you want to feed them through FeedBurner), or let the plugin use the default feed URL.  You can generate the file on demand, but the plugin will automatically regenerate it any time you add, change, or delete a category.

Once you’ve got the Categories OPML plugin all set up, just add the OPML Browser widget to your sidebar and tell it where the file is located.  Make sure you have the latest version of the OPML Browser – the OPML for hierarchical categories posed a few challenges for the older version and required an update.

I thought of a new use for my OPML Browser plugin, but the OPML file I intended to use with it threw me a couple of curve balls.

First of all, the file contained nested outline elements, with xmlURL attributes on the containing elements.  Until now, I displayed the feed icon if an item had a feed, and only displayed the folder icon if it didn’t (and it had child elements).  Because the only way to expand/collapse the tree is by clicking on the folder icon, I’ve changed this to display both icons in that case.

Second, my file nests the outline tags more than two levels deep.  I was using preg_match to parse the XML, with a non-greedy search for the end tag.  Can you guess what the problem was with that approach?  I’d get the end tag for an internal outline item when I was looking for the end of the outer item.  This only happened, of course, when an inner item was terminated by </outline>.

Rather than trying to get even fancier with my regular expressions, I decided to implement a real XML parser instead.  I took a look at SimpleXML, but it requires PHP5 and allow_fopen_url.  Then I looked at PHP’s built-in XML parser functions, but that’s event-based and I needed to wade through the document on my own terms.  So I implemented my own simple XML DOM parser, and included that with the plugin.

I realize that I’ve just added to the pile of reinvented wheels here, but I needed something simpler than SimpleXML (particularly in the requirements department) that nevertheless translated the event-based model of PHP’s built-in parser to a DOM model.

Thus, I created the very simple parser which you can download below.  It’s only 67 lines long.  It’s partially based on the example from wolfon, but simplified even further by adding an xmlElement class instead of trying to force all of the relationships into an array format.

To use:

require("xmlparse.php");

$dom = new xmlDOM($xml_text);   // Parses $xml_text

$dom->root is an xmlElement with a zero-length tagName whose children member is an array of the top-level elements (of which there should only be 1) .

$dom->find_tag($tagName, $from);

Returns the first xmlElement whose tagName matches $tagName, starting with the children of $from.  If $from is null, it starts from the root.  If not found, false is returned.

An xmlElement has the following members:

parent – the parent element
tagName – the tag name
attributes – an associative array of name => value
children – an array of child elements
data – any character data within the element

find_tag($tagName) – finds a descendant element with the specified tag name.  Returns false if none found.

Yes, this is such a major upgrade to my OPML Browser plugin for WordPress that it warrants bumping the initial digit in the version number.  Here’s what changed:

1. The plugin now expects to be installed in its own folder: (siteurl)/wp-content/plugins/opml-browser
2. JavaScript and CSS have been separated into their own files.
3. JavaScript events are now hooked on window load instead of in the HTML.
4. Added “alt” attribute to all “img” tags.
5. Images are now looked for in (siteurl)/wp-content/plugins/opml-browser/images
6. If an image cannot be found, it will be replaced by the supplied unknown.png (a question mark).
7. Added “Sort items?” option.  This sorts within categories, unless the “flatten” option is enabled (see next item).
8. Added the “Flatten hierarchy?” option.  This combines all items into one level.  If sorting, all items get sorted together.
9. The OPML description attribute is now displayed as a tooltip (as in the OPML Blogroll widget, but it also works in IE and Opera now!).

As far as I know, the OPML Browser can now do everything that the OPML Blogroll widget could do (items 7 through 9 filled that out), so I am herewith declaring the OPML Blogroll widget retired from further upgrades.  Please use this plugin’s widget instead from now on.  Let me know if I’ve forgotten any functionality that you need.

A big “thank you” to all of my users who requested various features and reported bugs.  This plugin would not be what it is today without your input. 

Thanks to a suggestion from Diego, I have added tooltips to each entry in the OPML Blogroll widget for WordPress.  These tooltips display the content of the “description” attribute of each outline entry, if one exists, when the user hovers the mouse over the entry.

Note that this is not an update to the OPML Browser plugin, although I plan to add the same feature to that plugin as well (along with a ton of other enhancements).

I used JavaScript to pop up and remove the Tooltips.  I decided to roll my own (with much help from Shelley Powers’ book Adding Ajax) rather than use an existing library, in order to keep the widget lean and to avoid conflicts with other libraries that might be in use on your blog.

Thanks to Internet Explorer, this seemingly simple enhancement required about twice as much JavaScript code as as a Firefox/Opera/Safari-only version would have.  Here are the differences that required special code for IE:

1. Of course, events don’t get passed to event handlers.  So you use window.event.  No big deal.
2. And we all know about addEventListener vs. attachEvent.  Not a problem, just wrap it in a function.
3. If you attach a property to a DOM object, lose the reference, and then reacquire that same element from the DOM later, it doesn’t have the property you added any more.  Apparently IE gives you a new object each time.  So in IE, this plugin has to look up the tooltip for the current item every time it wants to be displayed.
4. Not having the “currentTarget” property on the Event object in IE really sucks.  You can use “srcElement”, but it isn’t the same element as “currentTarget”.  For instance, if you have a “mouseover” event on an element that contains a link around an image, “currentTarget” gives you the element on which the event was specified, whereas srcElement will give you whatever contained element the mouse was actually over.  So this plugin accesses parentNode until it finds the one that’s meaningful.

Another nice “feature” of Internet Explorer keeps the tooltips from displaying at all in my theme – perhaps due to the use of float on nearby div’s.  I tried the fix outlined here to no avail.  It does work using the WordPress default theme, though, so there is hope.  Let me know how it works with your theme.

I also fixed a problem with the auto-discovery link in which the ending quote on the href was missing.

Linking to earlier versions for pingback.

UPDATE: 2009-05-11: I have incorporated all the features of this widget into my OPML Browser plugin version 2.0.  Please upgrade (it’s free). 

Shack Dougall spotted several HTML coding errors in the latest verion of my OPML Browser plugin.  Get the version 1.3 below.

Pingbacks to previous posts.

Version 1.2 of the OPML Browser plugin for WordPress has just been released!  This version includes some significant upgrades, including:

1. You may now have up to 9 opml-browser widgets. When upgrading, the options from your existing opml-browser widget are copied to the first opml-browser widget.  Thanks to Mark Barnes for suggesting this enhancement.
2. The option to exclude your domain now ignores differences in case when comparing domain names.  Thanks to Tony Lindskog for finding that one.
3. You can now override the title for the OPML link by entering text into the “OPML title override” field.  I didn’t want mine to read “FeedDemon Subscriptions”, so I added that for myself.
4. Added the ability to embed the browser within a page or post using a special [ opml-browser ] element in the text.  See the readme.
5. Added a “Get this widget” link at the bottom of the widget.  Thanks to TDavid for suggesting that little bit of self-promotion.

Download version 1.2 via the button below.  Pinging back to all previous posts for those following comments.

UPDATE: More corrections here.

Well, the OPML Browser plugin for WordPress has only been released for two days and already we’re up to version 1.1. Hopefully this one will last a while longer.

I added a new feature: start with all folders closed. Selecting this option will display the browser with all categories collapsed initially, unless the browser doesn’t support Javascript (otherwise the user wouldn’t be able to open them!).

I also completely reworked the code, using a class for the rendering engine. That allowed me to eliminate all global variables (almost always a good thing) and reduce the number of parameters being passed around. I still say PHP’s object syntax sucks, but it’s a good bit better than what I had before.

I even added some comments.

Let me know how you like it.

UPDATE: Get the latest version here.

Since I first released the OPML Blogroll widget, I’ve received numerous suggestions for enhancements. One that keeps coming up is the ability to show the hierarchy within the OPML file — categories, if you will.

Because of the way the original widget parses and displays the outline, this request was incompatible with the existing code. So I developed a new widget/plugin that does keep the hierarchy intact, and you can download it below. It also uses javascript to expand/collapse categories when the associated folder icon is clicked.

The code also includes an API for displaying an OPML browser within PHP code, so you don’t have to use the widget if your theme is not widget-compatible, or you want to display the browser somewhere else.

See the opml-browser-readme.txt file included in the download for full documentation and tips on how you can control the display through CSS styling to achieve some of the other suggested enhancements — such as scrolling within a limited height, bolding the categories, and removing the ability to expand/collapse categories.

There’s still one thing I haven’t figured out how to do, though. If the text of an item wraps, it wraps beneath the feed icon to the left. I’d like to be able to make it line up with the first line of text, but I’m not enough of a CSS wizard to manage that yet. Any suggestions?

UPDATE: Corrected a missing end-quote error in the autodiscovery link at 14:02 3-29-07

UPDATE: Get the latest version here.

Sorry Paul, this isn’t the big update you’re waiting for — just a few loose screws that needed tightening up.

After upgrading to WordPress 2.1, I noticed that the RSS icons in my OPML blogroll widget disappeared. I was using an image that is no longer distributed in the same location, so I put a copy of rss.png in the wp-content/widgets/images directory.

Taking a look at how I was referencing images, I realized that it also wouldn’t work if your blog was not in the root folder of your domain. So I added a call to get_settings(‘siteurl’) to fix that up.

Last month I nearly ran out of bandwidth on Chip’s Quips, and after analyzing the requests I found that nearly half of the bandwidth for the month was consumed by requests for my OPML file. In my case, the OPML file resides on the same server as my site, so there’s no need to request it over HTTP. I added a “Local path” option to the widget which, if specified, will open the file locally.

So now of course the “OPML URL” option is no longer required. If you leave that empty, then the auto-discovery link will be suppressed. It doesn’t make much sense to auto-discover a link on the local file system.

I also discovered that WordPress’s cache support in wp-includes/cache.php ignores the $expire parameter that you can pass when adding or setting cache data. This has not been fixed in WordPress 2.1 either. I’ll have to come up with a better solution so the OPML file doesn’t get banged every fifteen minutes, whether or not it’s on a local drive. But we’ll leave that for the next revision.

UPDATE (3/29/07): Tony Lindskog found a bug where a feed that has no “text” attribute caused a regular expression parsing error, and Paul McGillivary found a missing end-quote in the auto-discovery link. I’ve included fixes for those as well.

UPDATE (3/29/07): For an OPML plugin that preserves the hierarchy within the OPML file (categories, usually) and lets you expand/collapse that hierarchy, go here.

UPDATE (4/17/08): The latest version of this plugin can be found here.

UPDATE: WordPress 2.2 stuffs this approach. But fear not, there is yet a far, far better way of doing this. Download and activate the FeedBurner FeedSmith plugin – it’s automagic!

For a while now I’ve been redirecting my WordPress feeds through FeedBurner using a content pumping hack. That approach has the advantage of maintaining the standard feed URLs for WordPress, but it does place a little more burden on my server. After changing servers, I discovered another disadvantage: for some reason FeedBurner suddenly stopped distinguishing individual visitors. I’m guessing it’s a change to the way fopen works on a URL between versions of PHP.

Then yesterday, Randy invited me to join the KBCafe FeedBurner network. While doing so, I also decided to join the FeedBurner Ad Network. Somehow, I don’t think feed advertisers would be exactly chomping at the bit to place ads in a feed with only four subscribers, three of them bots. Time to fix this.

The right way

Instead of regurgitating content, you can just return a header to redirect the client. If you haven’t already, rename wp-rss2.php in your root directory to wp-rss2-fb.php. Burn a feed in FeedBurner, using that page as the feed source. Now create a new wp-rss2.php that contains only:

<?php
header( 'Location: http://feeds.feedburner.com/ChipsTips');
?>

Replace “ChipsTips” in the URL with your FeedBurner feed name. This performs a temporary redirect, so your feed’s URL remains the same in all clients, they just always get redirected to FeedBurner. If you want to save yourself some traffic, you can use a permanent redirect instead:

<?php
header( 'Location: http://feeds.feedburner.com/ChipsTips', TRUE, 301);
?>

The 301 response code directs the client to permanently change the URL for this resource, which loses the advantage of keeping the standard WordPress URL. What if you decide to leave FeedBurner? Won’t you lose all your subscribers? Well, it turns out that FeedBurner will return the favor and permanently redirect your feed for 30 days if you unsubscribe. Randy says he’s tested it. So I decided to permanently redirect, hoping to improve throughput for both my feeds and my sites.

Next, make the same change to your ATOM (wp-atom.php), RSS 0.92 (wp-rss.php) and RDF 1.0 (wp-rdf.php) feeds. I decided to redirect all of these to my RSS 2.0 feed in FeedBurner, and then use FeedBurner’s SmartFeed service to convert to other formats as needed. That allows me to aggregate my FeedBurner stats.

And speaking of stats, after FeedBurner had a chance to collect them correctly for a day, I found that even before my move it had failed to disambiguate quite a few subscribers. I have more than twice as many subs as I had thought! Thanks to all of you!

Thanks to some suggestions from Sergio Longoni, this morning I whipped up version 1.1 of the opml-blogroll widget for WordPress.

New features include:

• OPML auto-discovery link tag added to the “head” section of your page automatically (Sergio provided the code).
• You can suppress the OPML image and link by unchecking a new option “Link to OPML?” which is checked by default when upgrading.
• If you keep the OPML link, I’ve added the new semi-standard OPML icon.
• Closed the “img” tag for the RSS icons for XHTML compliance (oops).

Suggestions for future enhancements:

• Sergio suggested adding more control over how items are displayed. For instance, he would prefer “li” tags instead of a table. I’m going to give that some thought, but perhaps I could include options for prolog, epilog, pre-item, post-item, etc. and let you control the HTML.
• The Dead 2.0 skeptic (who appears to have been hammered out of the blogosphere by the traffic surge incumbent upon his identity intrigue) suggested a while ago that I add some form of paging, so that only the first N items would be displayed unless the user took some action.

What do you think of these suggestions? Got any more?

UPDATE: Latest version here.

In case you didn’t notice, I’ve converted Chip’s Tips into a WordPress blog. How do you like the new look?

I started Chip’s Tips back in 2001, before most people had ever heard of blogs. Yet, that’s more or less what it was from the start. I created my own XML grammar for outlining the topics, and another grammar for the posts themselves. Then I wrote Active Server Pages (ASP) to transform those XML documents into HTML pages using XSLT. It was my first project in both ASP and XSLT, and it worked quite well.

Lately, though, it’s been showing its age. ASP (not ASP.NET) is now an old technology. Blogs have evolved rapidly, and I wanted to be able to easily implement several key features:

1. An RSS feed for the posts
2. Comments and trackback/pingback
3. Tagging and multiple categories per post

Besides, my process for posting was less than smooth. I would copy an existing XML document for a post, modify its content, add an entry for it in the outline XML file, then upload both of those plus any download file. Often I would create unmatched tags in the body of the topic file so the XML parser would fail. Count on at least fifteen minutes of fiddling in addition to however long it took me to write a post. With a blog, all of that is automagic.

So, how did I migrate?

First, I needed a content migration strategy. I wrote a PHP script to read the existing outline and topic XML files and generate an RSS feed. That way, I could use WordPress’ RSS importer to pull the content.

Second, I set up the WordPress site and tweaked the theme I was using for Chip’s Quips to work here. Different color scheme, some new pages, etc. Add the Google ads and search, and the scripts for Technorati and ReefeRSS.

Third, I applied the same hack I used on Chip’s Quips to redirect the feeds, and burned the feeds at FeedBurner. Then I setup landing pages at FeedPass. Added the subscribe links along with the Chicklet generator and R-mail widget to the sidebar.

The hardest part was setting up all of the new categories (I wanted to reshuffle those) and tag all of the existing posts. I also included one unique tag per post that matched the original mnemonic from the old system.

Next, I modified showtopic.asp to permanently redirect to a tag search for the mnemonic requested, so any existing external topic links will be unbroken. Thanks to Steven Hargrove for providing the most excellent way to do this in ASP, as well as just about any other web language). Then I redirected default.asp to the main page, chip.asp to the “About” page, and resources.asp to the “Resources” page. I’m leaving topics.asp alone, because attempting to map from the old categories to the new proved too daunting. So, any external links to a general topic will still show the old outline page, but clicking on a link to a topic there will take you to the corresponding page on the new site.

Last but not least, I converted licensing to the CCD CopyWrite license, which I have also adopted for Chip’s Quips. No big change there from Creative Commons Attribution – you’re free to copy and reuse this content to your heart’s content, provided you give appropriate credit to yours truly.

Enjoy, and please feel free to comment!

I don’t know about you, but when Share Your OPML went live, my first thought was “Oh great, something else to keep updated!” It’s bad enough trying to keep my blogroll on my blog up to date with my subscriptions in my feed reader(s). Now there’s SYO to keep updated, too. Not to mention other similar sites like OPML Workstation and OPML Manager.

This little widget hopes to bring us some relief. Rather than having to reload your blogroll or manually update it every time your subscriptions change, you can display your blogroll directly from a hosted OPML file. So, you can keep your OPML at OPML Workstation or OPML Manager (would be nice if SYO offered an external link as well), and just keep that up to date. Or, you can host the OPML file on your own site and just hand the URL to SYO. Either way, you only have to keep this file updated in one place.

For me, that means that when I add a subcription to my Favorite Feeds folder in FeedDemon, I’ll export my OPML and upload it to my site. Done.

Installation and configuration instructions are included in the opml-blogroll-readme.txt file enclosed.

UPDATE: Latest version here.