Bug 143393

Summary:	ability to view percentage of read articles
Product:	[Applications] akregator	Reporter:	Kae Verens <kae>
Component:	general	Assignee:	kdepim bugs <kdepim-bugs>
Status:	REPORTED ---
Severity:	wishlist
Priority:	NOR
Version:	unspecified
Target Milestone:	---
Platform:	Fedora RPMs
OS:	Linux
Latest Commit:		Version Fixed In:

Description Kae Verens 2007-03-23 15:34:36 UTC

Version:            (using KDE KDE 3.5.6)
Installed from:    Fedora RPMs

instead of showing how many unread articles are in a section, it would be nice to have the figure as a percentage. using that figure, every few months, I could prune out the rss channels that I find that I'm not reading.

As an example of what I mean, let's say there is an RSS channel for Flower Arranging, and another for Guitar Stomping. After 3 months, the FA channel has 20 articles and the GS channel has 10. I've read 1 article in GS, and 4 in FA.

The present system would show this as:
Guitar Stomping (9)
Flower Arranging (16)

the above makes it appear that GS is read more often than FA.

using percentages, though, the channels would be listed as:
Guitar Stomping (90%)
Flower Arranging (80%)

this is more correct - FA is obviously more useful to me than GS, so I can safely delete the GS channel.



ps: I'm not actually a fan of flower arranging.

Comment 1 Bram Schoenmakers 2007-05-19 22:39:31 UTC

Can't you decide for yourself what you find interesting and what not?

Comment 2 Kae Verens 2007-05-20 18:29:21 UTC

yes, on an individual post by post basis. but the feature would allow you to find out which aggregations you are finding more useful, and so help you decide which aggregation you should drop if you find you haven't got time to read through all posts.

some people might find that useful, some people might not. Personally, I'd like it.

Comment 3 Justin Zobel 2021-03-09 04:11:19 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.