Serendipity Forums

I am currently experiencing some strange behaviour concerning my RSS feed (http://schimanke.com/index.php?/feeds/index.rss2). From time to time old entries show up as new items in my feed. Here are three examples:

"Video zeigt angebliche Front des iPhone 4G" - originally posted 29 March 2010 at 16:54, appeared as new item in RSS feed on 08. July 2010 at 14:19

"iPad News-Zusammenfassung" - originally posted on 29 March 2010 at 12:24, appeared as new item in RSS feed on 07 July 2010 at 08:38

"Arbeitet Apple an iAd? Event am 07. April?" - originally posted on 27 March 2010 at 08:08, appeared as new item in RSS feed on 03 July 2010 at 16:28

Any ideas why this is happening?

schimanke wrote:Any ideas why this is happening?

You didn't by any chance edit/update those entries?

YL

Which feed-reader are you using? Some readers set articles to unread, if there is an update. This can also happen, if someone writes a comment oder the article gets a pingback.

Within tiny-tiny-rss i can disable this "feature".

Thanks for your answers. I found out that it seems only to affect Google Reader. The feed seems to be okay.

No, I didn't update the entry nor did anybody write a comment...

Could this problem be related to the RFC 2616 settings in s9y?

Hi!

schimanke wrote:Could this problem be related to the RFC 2616 settings in s9y?

Yes, this is exactly the reason. Sadly due to google reader's widespread use, I generally recommend to disable the s9y feature by ENABLING the RFC 2616 compliance.

Regards,
Garvin

Thanks Garvin! I will see how this develops...

Garvin, the old entries still show up in Google Reader despite using the suggested settings. Could that be related to the Google cache? Will it ever stop?

Hi!

schimanke wrote:Garvin, the old entries still show up in Google Reader despite using the suggested settings. Could that be related to the Google cache? Will it ever stop?

When you enable the RFC-compliance, this will only take effects for newly pulled RSS-Feeds. So if a reader has old entries from a previous run, it won't remove them from display usually.

I'm not exactly sure right now if editing a very old entry will still update its "last_modified" timestamp. This is a functionality independent from the RFC setting I believe. The RFC setting priorily affects the HTTP-Headers; if a client sends a specific Cached Time, only entries will be sent from that time on, but no more than the most recent 15 entries.

Regards,
Garvin

Thanks for the clarification.