Comparing akregator and liferea (rss readers)
I have previously reviewed both akregator and liferea. In this post, I want to compare the two rss reader applications.
For reference, here are the links to the two reviews:
I’ll note that each of those reviews contains an image of the main screen for the particular application. You might find it useful to refer back to those review.
The akregator reader is designed for the KDE desktop. In fact, it is part of the Kontact suite of KDE programs, although it can be used without the remainder of the Kontact suite. I am using only akregator, but not the rest of Kontact.
The liferea application is a gnome application. However, my testing of liferea has been while running KDE.
As a KDE user, akregator would thus be the natural choice for me to use. If I were a Gnome user (or, for that matter, an XFCE user) I would probably choose to run liferea. I presume that akregator will run under either Gnome or XFCE (not tested). However, because of the way that akregator is integrated into the KDE desktop, you might find that you are running more KDE services that a Gnome user would like.
The main screen of akregator contains, for each listed message:
- the message title,
- the name of the feed,
- the author of the message,
- the data and time that the message was originally posted.
By contrast, the liferea screen contains, for each message:
- the date and time of posting,
- an icon (apparently the favicon for the site),
- the message title.
I find the akregator screen a lot more useful. The site icon on the liferea screen is not very useful. Many wordpress sites will have the same wordpress icon, while many blogger sites will have the same blogger icon. So it is harder to identify where a message is coming from when using liferea. Even when you click on the message line, to display the feed content for that message, liferea provides less information that I would like about the message source. You have to open the full message before you can be sure where it came from.
I see this difference between the two rss readers as being a major plus for akregator.
When reading the feed content for a message with akregator, I often see advertisements. Those ads are not particularly annoying, as they are mainly static ads (no moving parts).
By contrast, I have not seen any advertising in the feed content presented by liferea. I am not sure why. I presume that both readers are getting the same data from the sites, so presumably liferea is doing some filtering.
I’ll call this a plus for liferea.
The cookie handling in liferea is more primitive. Cookies are used, but are not integrated with a browser. It is possible to manually copy a cookies.txt file (in netscape format) to the liferea configuration directory. However, with firefox and chromium both using sqlite for cookies, it is not easy to manually integrate cookies.
Apparently you can still use a site that requires a login, and liferea will present an authentication page for you to use. I presume is keeps this information in cookies. I have not tested this ability. Likewise, akregator supposedly has an ability to directly request authentication where needed, though again I have not tested this. At least with akregator, using konqueror for site login would be a more congenial approach.
I’ll count this as a plus for akregator.
Browsing a full message
In akregator, I can click on a message title to see what is in the feed. At the bottom of that message, there is a link to “Complete Story”. Clicking on that “Complete Story” opens the full message in a tab on akregator. Alternatively, if I middle-click on “Complete Story”, it opens the full message in my browser (currently configured to open in a konqueror tab).
Alternatively, I can middle-click on the message title (in the main display of message titles) to directly open the full message in my browser. Or I can right-click on the message title and select to open the full message in an akregator tab or in my browser.
The message, when opened in an akregator tab, looks reasonably complete. At sites where I am logged in (vi konqueror), I can readily post comments.
With liferea I have similar choices, but they are less convenient. Clicking on a message title shows the feed content. Middle clicking on the title marks the message as unread. I suppose that might be useful, though I have not used it accept for testing. To open the full message in either a liferea tab or in my browser, I must right-click on the message title and then select how I want to open the message.
I’ll count this as a plus for akregator.
Marking a message
In akregator, I can right-click on a message title, and mark the message as important. Then, at a later time, I can set the main screen to show important messages, so that I can see which messages I have marked. I do this when I have commented on a message, and want to return later to see whether there was a response. I also do this when I don’t have time to do more than skim a message, but the skimming is enough to see that I will want to revisit the message at a later time.
With liferea when I right click on a message title, one of the options is to “toggle item status”. That turns out to be what marks the message as important.
I’ll call this a tie between the two readers.
Both readers are buggy. I’m not sure why, but neither of them seems to be able to keep count.
With akregator, the count of unread messages is correct most of the time. But, occasionally, it gets off by one. And when it is off by one, it is harder to tell whether there are any unread messages. At that point, I usually close akregator (“quit” from the tray icon), and then restart it. That gets the count correct again.
For liferea, there is a virtual folder for unread messages. The folder content seems to be correct on which messages are unread. But the number of unread messages listed can be wildly off. Stopping and restarting liferea does briefly fix the problem, but before long the count will again be wildly off. It does not seem to be worth the effort of stopping and restarting liferea to fix this.
On a number of occasions, akregator has crashed on me. When I restart it, I am offered the choice of restoring the failed session or making a clean start. I usually choose to restore the failed session. But, even with that choice, data is sometimes lost. That is, messages that I have seen and read are missing from the display and will be refetched and marked as new. This can be annoying.
Thus far, I have not had any crashes with liferea.
I’ll count this as a plus for liferea.
Both are reasonably good rss readers, though both have imperfections. My personal preference is for akregator. However, my overall advice is to use akregator if you are a KDE user, and otherwise to use liferea.