Change the feed db schema to keep track of the (un)read status

[idflood]

For my use case the current way of storing feeds is not really helpful. I think that the feed items should be marked as read/unread and their state saved in db. With a view listing all feed items by date this would be much more faster to see if there is some new article to read or not.

So instead of overwriting the feed items when the cache ends, the app should update or create the feed item in a table.

In a second time, there could be some automated cleanup of these items. Ideally the method would be defined in config. Max items by feed / time max / ...

What do you think?

[geekuillaume]

I had the same idea but I'm lacking of time now.
I'm adding it on the Todo list ;-)