Gnus development mailing list
 help / color / mirror / Atom feed
From: Mark Plaksin <happy@mcplaksin.org>
Subject: Re: duplicate items in nnrss groups
Date: Thu, 14 Sep 2006 16:50:39 -0400	[thread overview]
Message-ID: <wsejuexjds.fsf@stone.tss.usg.edu> (raw)
In-Reply-To: <9ewt868cei.fsf@doze.jochen-kuepper.de>

Jochen Küpper <jochen@fhi-berlin.mpg.de>
writes:

> On 14. Sep. 2006, Mark Plaksin wrote:
>
>> David Hansen <david.hansen@gmx.net> writes:
>>
>>> On Sun, 10 Sep 2006 22:25:04 +0200 Jochen Küpper wrote:
>
>>>> With this I get repeatedly the same entries listed as new. This
>>>> seems cto happen every time I press "g" *and* the date/time of the
>>>> xml-file is newer than at the previous update, or something
>>>> similar.
>
>>> If some RSS "expert" is reading this i would be glad to here which
>>> tags really indicate some new content and which are just more or
>>> less useless additions like the <slash:*> tags.
>
>> Perhaps no expert is chiming in because everybody thinks the current
>> plan is great: Use the title, description, and pubdate.
>
> Why do you add pubdate here? 
> The fact that it is used is the problem I describe above, not?

Maybe I misunderstood.  I thought the problem you described was because
caused by nnrss using the timestamp of the feed's cache ("feed name.el") on
your local disk.  By "pubdate" I meant the date included in each item in
the RSS feed itself.

Depending on the RSS version (I'm no expert) it might be "pubdate" or
"dc:date".  For example, here's Gmane's RSS item for your article:

  <item rdf:about="http://permalink.gmane.org/gmane.emacs.gnus.general/63744">
    <title>Re: duplicate items in nnrss groups</title>
    <link>http://permalink.gmane.org/gmane.emacs.gnus.general/63744</link>
    <description>

Why do you add pubdate here? 
The fact that it is used is the problem I describe above, not?

Greetings,
Jochen
</description>
    <dc:creator>Jochen Küpper</dc:creator>
    <dc:date>2006-09-14T19:40:37</dc:date>
  </item>




  reply	other threads:[~2006-09-14 20:50 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-09-10 20:25 Jochen Küpper
2006-09-10 21:48 ` David Hansen
     [not found]   ` <87slizbdgb.fsf-/PVU1wbgskXSxOb6xA1WPVLmfr9GSJok@public.gmane.org>
2006-09-11  8:07     ` Jochen Küpper
2006-09-14 16:51   ` Mark Plaksin
     [not found]     ` <wszmd2xuh3.fsf-QSdS4MO2Nel/RRfBVNJ3YIdd74u8MsAO@public.gmane.org>
2006-09-14 19:40       ` Jochen Küpper
2006-09-14 20:50         ` Mark Plaksin [this message]
     [not found]           ` <wsejuexjds.fsf-QSdS4MO2Nel/RRfBVNJ3YIdd74u8MsAO@public.gmane.org>
2006-09-14 21:34             ` Jochen Küpper
2006-09-15 16:12               ` Mark Plaksin
     [not found]                 ` <wsmz91un18.fsf-QSdS4MO2Nel/RRfBVNJ3YIdd74u8MsAO@public.gmane.org>
2006-09-16 13:02                   ` Jochen Küpper
     [not found]                     ` <9e64fo9d7v.fsf-X+QEHg5KIgm/8B4OpmtwqPxnRIzENc/G@public.gmane.org>
2006-09-16 13:54                       ` generated dates should not be hashed (was: duplicate items in nnrss groups) Jochen Küpper

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=wsejuexjds.fsf@stone.tss.usg.edu \
    --to=happy@mcplaksin.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).