RSS? OPML? ENT?
Mark pointed to Matt who's talking about a new module (ENT) for RSS 2.0. Sounds neat, but what I really need someone to do is evolve the spec for OPML. Instead of me having to re-categorize my feeds every time I install a new RSS parser, the OPML file should have pre-definied categories. And, instead of me having to maintain separate OPML files for all of my parsing applications, programmers should start enabling the user to dynamically load feeds from a centralized (local or remote) OPML file. C'mon folks – let's get smart with this stuff. I understand the need to maintain a proprietary database for the program in question, but your app shouldn't require me to maintain separate feed subscriptions. I'm not a programmer – I'm a user. And damnit, why can't “you” help make OPML smarter and more convenient for me?




