Worth browsing / importing and seeing what his RSS subscriptions is you're interested in Web 2.0 / API / Mash ups. He's also been following the OPML / Attention conversation:
"For those who haven’t grokked it yet, OPML is essentially a way to exchange lists of RSS feeds between RSS aggregators. (Alex explains it here). However, it has the potential to do much more - since your RSS feeds are indicative of your interests, your OPML file is a major source of attention data. "
"While I agree with how OPML files can become as important as other real-world documents in mainstream life, I do have a pedestrian question.
The discussion above assumes there is one central OPML file that aggregates all this user attention data over time.
Reality though is much messier.
As I look at my own situation, I have "OPML assets" scattered all over the place.
The biggest one is at Bloglines as I described earlier.
And as other tagging and RSS aggregation sites proliferate, I'm likely to have another half a dozen more at places like Digg and others.
Where is the centralization?"
Centralization of all these OPML files and RSS subscriptions? Answer: an OPML file. An OPML file can point to other OPML files and urls (that each in turn can include RSS urls and normal links). So you could have your 'master' OPML file, that points to all the others you're maintaining on other systems / apps. The interface for all this isn't there yet. opmlmanager.com comes close but I don't think you can include / point to other OPML files (Bernard? and Pieter?). If you could that would be very useful. I managed to get OPML Editor installed now: that's another way of managing the centralization, so more OPML playing ahead for me.
But not yet. Time for turkey now.