------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
------- Additional Comments From caster matfyz cz 2006-06-19 23:53 -------
Exactly, I've just observed it with http://www.kde.org/dot/kde-apps-content.rdf - when you have an older version of app in your akregator archive, new version won't show up. It's the feed fault for publishing new article with same <guid> and bug should be filled for the feed.
Before KDE 3.5.3, I think there were 3 possibilities
a) feed contains two articles with same <guid> simultaneously (they are both present at one time), this resulted in those articles showing only as one, and updating status to NEW after EACH FETCH (until they were gone from the feed, replaced with newer articles). Now this was very annoying, because of the each fetch. Yeah it would need change of GUI/strings but I've read that KDE 3.5 is no longer strictly freezed because 4.0 is too far away, so it would be possible?
b) feed contains article with same <guid> as some older one, not simultaneously with the new one. If the older one is archived in akregator, the new one overwrites it and sets NEW. This is what happens with http://www.kde.org/dot/kde-apps-content.rdf for example.
c) feed is crazy and changes description/date/whatever each fetch, while keeping the same <guid>, annoying as a). This is case of google rss feeds? (not sure about that)
3.5.3 for sure made case b) not report such updated articles as NEW, while I think this bug and the real problem was about case a). 3.5.3 probably fixed all a) b) c) but at the cost of losing news from b). It would be possible to fix a) only though, probably not possible to fix c) without b).
While it's clearly problem of the feeds to be broken, it's hard to get all of them fixed, especially if you can't know you missed an article and the feed is broken. What would be best is one global option for marking updated articles as NEW, and per-feed option overriding the global one.