On Fri, 25 Mar 2005 01:55:51 -0800, Brion Vibber wrote:
That was the culprit when I kept getting old versions served on the RecentChanges feed. Turns out we only keep _one_ timekey for _two_ feeds, so if an edit happens and the RSS cache gets updated, the Atom version won't be (and vice versa).
Did you just discover this, or did you forget to report the bug? :)
I tracked this down yesterday. It's so blindingly obvious when you look at the code that I suspected it might be intentional. For my own installation, I just cut $expire down by a few orders of magnitude.
While I was debating whether I should still report it or write a patch, along came a list message that allowed me to sneak in my discovery and off-load responsibility.
Btw, is there a deeper reason why the limit on RC entries is encoded twice in the URL (previous and current value)?
Roger