Version: 1.1.1 (using KDE 3.4.1, Gentoo) Compiler: gcc version 3.3.5-20050130 (Gentoo 3.3.5.20050130-r1, ssp-3.3.5.20050130-1, pie-8.7.7.1) OS: Linux (i686) release 2.6.11.11 Some feeds, e.g. http://slashdot.org/index.rss, have embedded ads (sponsored listings). Each time the ad is changed/updated, the corresponding article is shown as "new". It's quite annoying if the same article pops up as new 5+ times all day, if there are 20 articles with embedded ads ... Thnx in advance!
This problem has nothing to do with the ads, the problem was the the comments count was used to detect changes. Which is a bad idea in general, and for slashdot in particular. When a comment was added at /., the article was marked as changed... This is fixed in 3.4.2.
Hmm, I'll test as soon as the gentoo packages of 3.4.2 are available. I didn't observe this particular problem with any other articles but those that have ads attached, so I assumed that the ads are involved?! Otherwise any article at /. should be renewed each fetch cycle, shouldn't it?
/. changes the articles, it seems that that's the reason why akregator shows them as "new". I observed that the 9 latest articles are without an ad. If a new article is submitted, the now 10th one get's an ad attached which makes it "new" for akregator?!
Interesting, I will observe this. So the other articles (1-9) are left unread? Then it is indeed caused by the ads. Do you use 3.4.2 now?
All articles are marked as "read", a new article appears and the 10th in the list is set to "new/unread" (as well as the new first one). It now has an ad attached which wasn't the case before. As to 3.4.2: nope, the ebuilds are not yet available for public merging =( I've to figure out how to unmask them, I'm using gentoo for about 10 days now ...
This problem appears in all versions of Akregator, you don't have to test it. :-) This is a Slashdot problem, they put their ads into the feed in a very silly way. Ads should be persistant for an article. I'll contact Slashdot about this, however, there will be no solution to this from Akregator side.
What a pity - thanks for your effort guys =)