Bug 98387

Summary: per-feed or per-folder priority and listing settings
Product: [Applications] akregator Reporter: Marc Haber <mh+kde-bugs>
Component: generalAssignee: kdepim bugs <kdepim-bugs>
Status: CONFIRMED ---    
Severity: wishlist CC: gerd, kdebugs
Priority: NOR    
Version: 1.0-beta8   
Target Milestone: ---   
Platform: unspecified   
OS: Linux   
Latest Commit: Version Fixed In:
Sentry Crash Report:

Description Marc Haber 2005-02-02 08:51:06 UTC 
Version:           1.0-beta8 (using KDE 3.3.2,  (3.1))
Compiler:          gcc version 3.3.5 (Debian 1:3.3.5-6)
OS:                Linux (i686) release 2.6.10-scyw00225

Hi!

I have a folder of high priority feeds (such as security notifications) and a folder of lesser priority feeds (new software versions being released etc).

Both groups show up in the KDE tray with the same "priority", so I frequently open akregator to find that a new minor version of some unimportant software that I do not even use has been released.

A solution to this issue would be to assign a "priority" to a feed which is then multiplied into the number of articles being shown in the tray icon. A priority of 0.1 in a feed would add "1" to the number in the tray icon if there are ten unread articles, and a priority of 0 in a feed would prevent new articles in a feed from being shown in the tray at all. A default of 1 would imply no change in the behavior.

Setting a priority on a feed folder would apply as a default to all feeds in the folder which do not have their own priority set.

Please consider adding this feature to a future version of akregator.
Comment 1 Frank Osterfeld 2005-11-22 02:12:04 UTC 
I agree that the unread count is not particular useful for people using many feeds (or high traffic ones). Mine showing 6942 right now and that is not good for nothing. Something like "act on new mail" in KMail would be useful.
Comment 2 Frank Osterfeld 2006-09-04 02:31:45 UTC 
*** Bug 99453 has been marked as a duplicate of this bug. ***
Comment 3 Frank Osterfeld 2006-09-04 02:36:39 UTC 
*** Bug 125016 has been marked as a duplicate of this bug. ***
Comment 4 Justin Zobel 2021-03-09 04:10:42 UTC 
Thank you for the bug report.

As this report hasn't seen any changes in 5 years or more, we ask if you can please confirm that the issue still persists.

If this bug is no longer persisting or relevant please change the status to resolved.