search

stringer-rss / stringer

A self-hosted, anti-social RSS reader.
MIT License
3.94k stars 396 forks source link

Meltdown Android RSS Client #217

Closed jmazzi closed 11 years ago

jmazzi commented 11 years ago

I'm not sure who's end this problem is on. Meltdown is an Android Fever RSS client. The source for it is available here. Using it's feature to "Mark all as read" doesn't work. All articles come back on refresh.

How could I help troubleshoot this problem? What information would be useful to debug this?

swanson commented 11 years ago

First we should look at the Meltdown source to figure out what API calls it is making for this feature. Then check if we have implemented it correctly in Stringer.

My hunch is that we have not implemented this part of the API.

queuebit commented 11 years ago

From looking at the Meltdown source, it looks like it is likely using the mark=group&as=read arguments to "Mark all as read."

Looking at the Fever API implemented in Stringer, it seems to only respond to mark=item.

Sorry that I am not familiar enough with the code base to make a change / PR, but hopefully the investigation helped.

jmazzi commented 11 years ago

From the docs:

Marking a feed or group as read is similar but requires one additional argument to prevent marking new, unreceived items as read: mark=? where ? is replaced with feed or group as=read id=? where ? is replaced with the id of the feed or group to modify before=? where ? is replaced with the Unix timestamp of the the local client’s most recent items API request

The URL meltdown hits is /fever/?api&mark=group&as=read&id=1&before=1373377397. From what I can tell, the before time should be the date an article was created in stringer. All items that were received before the timestamp should be marked as read for the passed in id. The id can be a group or feed.

jmazzi commented 11 years ago

@queuebit @swanson I'm going to push my branch to heroku shortly, but everything seems to be working locally on #219