You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Maybe this is just me, but I would find it quite useful to be able to have two separate states for "unseen" and "unread" items.
What I mean by this, is that "unseen" items are newly downloaded items that I'm completely unaware of, which would transition to "unread" once I've acknowledged their existence but not yet actually read them. I'm not sure exactly what should trigger this transition, but middle-clicking an item would be one idea.
My reasoning for this is that I often find that many feeds have many items that I would like to save for background reading some rainy day, for which I currently let said items lie around indefinitely using the current "unread" state, but that interferes with my ability to be properly notified of new "unseen" items, since the feed having, say, 11 instead of 10 unread items isn't something that I'm likely to notice.
The text was updated successfully, but these errors were encountered:
Maybe this is just me, but I would find it quite useful to be able to have two separate states for "unseen" and "unread" items.
What I mean by this, is that "unseen" items are newly downloaded items that I'm completely unaware of, which would transition to "unread" once I've acknowledged their existence but not yet actually read them. I'm not sure exactly what should trigger this transition, but middle-clicking an item would be one idea.
My reasoning for this is that I often find that many feeds have many items that I would like to save for background reading some rainy day, for which I currently let said items lie around indefinitely using the current "unread" state, but that interferes with my ability to be properly notified of new "unseen" items, since the feed having, say, 11 instead of 10 unread items isn't something that I'm likely to notice.
The text was updated successfully, but these errors were encountered: