From: Kevin Ryde <user42@zip.com.au>
To: ding@gnus.org
Subject: Re: nnrss lacks basic crosspost detection; should use guid
Date: Mon, 02 Mar 2009 08:46:09 +1100 [thread overview]
Message-ID: <87k5789ase.fsf@blah.blah> (raw)
In-Reply-To: <87r61jwqit.fsf@jidanni.org> (jidanni@jidanni.org's message of "Sat, 28 Feb 2009 04:53:14 +0800")
jidanni@jidanni.org writes:
>
> <guid isPermaLink="false">35873 at http://www.coolloud.org.tw</guid>
What do the specs say about the scope of a non-permalink guid?
I recently struck these two feeds
http://rss.weather.com.au/sa/adelaide
http://rss.weather.com.au/nt/darwin
which have the same guid (non-permalink), but different content. (They
update every 15 minutes or something, the guid changes with such
updates, but to the same new value for the two locations.)
It made me suspect non-permalink guid is only for the given feed url,
apparently not univeral nor even throughout the given server. (I jigged
up Message-ID from my rss2leafnode program accordingly, but couldn't
find the right bit of the specs to confirm or deny.)
next prev parent reply other threads:[~2009-03-01 21:46 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-27 20:53 jidanni
2009-02-27 20:54 ` jidanni
2009-03-01 21:46 ` Kevin Ryde [this message]
2009-03-01 22:14 ` Russ Allbery
2009-03-08 0:20 ` jidanni
2009-03-14 0:52 ` Kevin Ryde
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=87k5789ase.fsf@blah.blah \
--to=user42@zip.com.au \
--cc=ding@gnus.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).