[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#749534: qa.debian.org: rss feeds get updated on every pull due to pubdate set to "now"



On 27/05/14 at 21:45 +0200, Paul Gevers wrote:
> Package: qa.debian.org
> Severity: minor
> User: qa.debian.org@packages.debian.org
> Usertags: udd
> 
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA256
> 
> Thanks for supporting feeds for the TODO list on https://udd.debian.org/dmd/.
> However, I constantly get "new" feeds because on every pull the
> pubdate of items is updated and my feed reader (icedove) displays new
> items.
> 
> Furthermore, my feed checker (integrated in icedove) reports the following
> issues on https://udd.debian.org/dmd/feed/?email=elbrus%40debian.org:
> 
> This feed does not validate.
> 
>     line 38, column 12: link must be a full and valid URL: (4 occurrences) [help]
> 
>               <link></link>
>                     ^
> 
> In addition, interoperability with the widest range of feed readers could be improved by implementing the following recommendations.
> 
>     line 16, column 6: An item should not include both pubDate and dc:date (8 occurrences) [help]
> 
>               <dc:date>2014-05-27T19:43:22+00:00</dc:date>
>               ^
> 
>     line 17, column 4: item should contain a guid element (8 occurrences) [help]
> 
>             </item>
>             ^
> 
>     line 60, column 4: A channel should not include both pubDate and dc:date [help]
> 
>             <dc:date>2014-05-27T19:43:22+00:00</dc:date>
>             ^
> 
>     line 61, column 2: Missing atom:link with rel="self" [help]
> 
>           </channel>
> 
> Thanks.
> Paul

Hi,

I've implemented a very partial fix for this problem.

First, I've switched the update time from "now" to "today", so items
will only show up as updated once per day. (yes, I know, it's still
annoying)

Second, I've added support for specifying a per-item date, and
added one where it was trivial to. The problem is that there are items
for which there's no obvious date. Of course, the best solution would be
to use the first time an item is shown, but we currently have no way to
do that.

I haven't done anything about the validation issues.
 
Lucas


Reply to: