[emacs-w3m:11166] Re: sb-atom and sb-rss fetching already deleted articles
David Engster <deng <at> randomsample.de>
2010-03-03 21:48:51 GMT
Katsumi Yamaoka <yamaoka <at> jpl.org> writes:
>>>>>> In [emacs-w3m : No.11162] David Engster wrote:
>> I've implemented the approach I quoted above and attached a patch
>> against current CVS. The advantage of this approach is that it works
>> more generally, without the need for an extra parameter.
> Oh, I understood what you meant at last. It picks articles of
> which the date is newer than the ones having already been fetched,
> and saves articles of which the date cannot be identified. That's
> an excellent idea!
I had to change this a bit. Turns out there are feeds out there which
happily introduce new items with *older* dates (the 'topthemen' from the
sueddeutsche-de shimbun, for instance). To make those items show up, I
now compare with the date of the *oldest* existing article in the
group. This should still make sure that the article wasn't expired and
is actually a new one.
I also made sure that the returned items are sorted by ascending
date. This is to make sure that newer articles get higher article
numbers in Gnus, since in the expiry process, it is the article with the
highest article number which is kept and never deleted.
It's still not perfect, though. Imagine a feed introduces one new item
with an old date; it will get the highest article number in Gnus. If you
now completely expire the group, only this article will remain. When you
now refresh the group, all items with a newer date will again show
up. However, I think this is a very rare case - it would need a feed
which introduces new items with old dates and a pretty short expiry
time. If this really turns out to be problem, it could still be fixed in