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 5 years ago
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:
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.