Ticket #74 (new enhancement)

Opened 2 years ago

Last modified 2 years ago

'old' status for articles

Reported by: ttrss@s126.de Assigned to: fox
Priority: wishlist Milestone:
Component: backend Version:
Keywords: Cc:

Description

Hi, I really would appreciate a feature, where I can distinguish between read-old articles and read articles. (Like the "old" flag in mutt, if you know what I mean)

Workflow would be: I read all the "hot" articles, which draw my attention from one feed right away, and postpone the not-so-hot articles by marking them as OLD, but still unread (with one button). Later I could revisit the feed, hopefully with more time to read all or some more articles.

Additionally there should be a second number in the Feed-Frame, subsuming the number of OLD articles in the feed.

thx for considering.

sincerly,

/fux

PS: thx for the 1.2 release, big improvements for me. Keep on the good work.

Change History

06/16/06 13:35:58 changed by fox

1. Are you sure that starring articles for later view doesn't cut it?

2. I'm not sure about the name. When I saw "old" in ticket name, my first thought was about marking articles nearing expiration in some special way. Maybe it's intuitive for a mutt user, but I'm not sure about everyone else (Gnus user as myself being an example).

06/16/06 19:24:17 changed by ttrss@s126.de

1. well starring would do the trick, as I don't use any starring-feature at the moment, but intuitively starred articles are on a higher priority and this wouldn't match the meaning for those 'old' articles in general. So if one actually uses the starred-article-feature for its purpose, he/she won't be able to use it for the mark-as-old-feature. And secondly, there yet is no nice "star-all-unread-articles-and-jump-to-next-feed-with-new-articles"-button

2. well ok, you name it :) - meaning should indicate "subject read, but article unread" so for example 'unread' would match this criteria, too.

Greetings,

/fux

06/16/06 20:41:47 changed by fox

I think that starred state could be used both ways here. For example:

1. unread & starred = saved for later 2. just starred = interesting/saved in archive/whatever.

An action to toggle starred state of selected articles already exists.

Workflow would be somewhat different:

1. read unread articles, star some for later. 2. view feed (in starred mode?) and read those articles, maybe remove starred state if they are of no interest any more.

I can understand that this won't feel entirely comfortable to you (at first), but I try to avoid interface feature creep. Adding another mechanism which feels _very similar_ to the one that already exists doesn't seem like a Good Idea (tm) to me.