3 ms·
I think the developers of a couple of the biggest RSS readers should get together and decide on a standard file format to store "metadata" such as read items, s
by waxjar 14y ago
I think the developers of a couple of the biggest RSS readers should get together and decide on a standard file format to store "metadata" such as read items, starred items, etc.
This file could be stored on a server or in a user's Dropbox folder. It would allow users to pick an RSS reader freely (per platform), without losing and rebuilding all their data. It also keeps all this metadata in sync, one less worry for the developers.
- jlgaddis 14y agoWhat's in it for them, though? I'm guessing that most of the developers want you to use their reader and I'm not sure there's an advantage (for them) in adding code that makes it easier for you to switch to another product. Don't get me wrong. I totally agree w/ you and wish that switching is easier. That "cost of switching", though, is the primary reason I'm still using the reader that I am (and have been for years).
- mindcrime 14y agoWhat's in it for them, though? A rising tide lifts all boats. If something is developed that makes the entire ecosystem more attractive, then everybody benefits. I'm guessing that most of the developers want you to use their reader and I'm not sure there's an advantage (for them) in adding code that makes it easier for you to switch to another product. Sure there is... because I'm more likely to try your product in the first place if I know I'm not locked into it. "The best way to capture users is to make it easy for them to leave" and all that.
- waxjar 14y agoThat's a good point and likely the reason this won't ever happen. The upside for app developers is that they won't have to run their own servers or rely on a commercial third party to keep state in sync.