The recent changes feed is from 100-250kb (arguably another issue) and is cached forever. Are you suggesting that we should add one for every language that may be used by visitors? This could eat up cache pretty quickly.

When I looked at the source, I was surprised to see that, indeed, the cached RC feed data does not expire. I believe this is just a plain bug: the feed data should expire after 24 h, just like its timestamp does (adding a patch in a while).

So, assuming this gets fixed, the feed is cached only for languages somebody requested, and only for at most 24 h.

If that does not look acceptable to you, we are left with only the other option I mentioned: force content language always. But, that means saying “no” to the users requesting otherwise (see that bug #17868), and is not completely trivial – you will probably need to set wgLang to wgContLang during feed rendering (or refactor at least FeedUtils::formatDiff (and possibly other places) to explicitly pass the language to use; (mmm… that $wgUser->getSkin() seems interesting, too…).

Oh, in fact, we do have yet another option: keep the functionality as it is, only if wgLang!=wgContLang, do not cache the feed. But that would be a possibility to a DOS attack or something like that. (Or, we could use much shorter cache timeouts for those languages.)

Created attachment 6278
Use expiration not only for the timestamp, but also for the feed data

Currently, the feed timestamp stored in the cache expires in 24 hours, but the feed data does not expire at all, which is nonsense, since the data is used only if the timestamp is found in the cache.

Attached:

In bug 19812#c1 you see me "go pick some odd limit" to workaround. Yuck,

Bryan.TongMinh wrote:

Applied in r58978.