Implementing Fever: Marking #167

Closed
opened 2019-03-07 19:01:33 -05:00 by jking · 0 comments
Owner

The specification suggests that there is no way to mark Kindling as read without also marking Sparks; this is not terribly relevant, but a source of some confusion for me.

The specification also mentions:

Adding unread_recently_read=1 to your POST data will mark recently read items as unread.

This appears to be the only way to mark items as unread; it's not clear what, exactly, constitutes a a recently read item, nor why you wouldn't simply want the same level of control as for other operations.

The specification suggests that there is no way to mark Kindling as read without also marking Sparks; this is not terribly relevant, but a source of some confusion for me. The specification also mentions: > Adding `unread_recently_read=1` to your POST data will mark recently read items as unread. This appears to be the only way to mark items as unread; it's not clear what, exactly, constitutes a a recently read item, nor why you wouldn't simply want the same level of control as for other operations.
jking added this to the 0.8.0 milestone 2019-03-07 19:01:33 -05:00
jking closed this issue 2019-04-10 18:28:58 -04:00
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Blocks
#156 Implement Fever
MensBeam/Arsse
Reference: MensBeam/Arsse#167
No description provided.