Wild Ideas

Random and wild ideas for Coldsweat.

Muted feeds

It would be cool to have a way to "mute" a feed to avoid its entries to appear in the unread lists. Feeds like "Dribbble popular" are nice to have but they clutter the unread views (too many posted entries). The idea is to still fetch the feed but show its entries only in the single feed view.

One can mute a feed right when it is added to Coldsweat (in the Subscribe modal dialog) or in the About modal dialog.

Fav feeds

Make a query with all the feeds that have N saved entries in the last N days. This would be a good measure to figure out a sort of favorite feeds.

By limiting the query within a given _timedelta_ we avoid to pick up old feeds no longer followed regularly.

This fav feeds information would also be used in the web UI to alter the presentation and present entries more or less aggressively depending of their group.

Status log

By adding a new feed status log we can effectively create a record of each feed health. A new database table would track the HTTP status returned by the feed server.

This way Coldsweat could be more precise when disabling a feed by sampling the frequency of the error. For example: if a feed returns 100 404/500 errors in a row, well, there's a good change that will be broken forever.

At database level something like this will suffice:

• id
• feed_id
• status
• checked_on

Then the current `error_count` field would be replaced by:

select count(error_count) from status where feed_id = $id

Similarly the `last_checked_on` field would be replaced by:

select checked_on from status where feed_id = $id order by checked_on desc limit 1

Obviously these would be aggregated so we don't run N queries for N feeds.