From: jidanni@jidanni.org
To: rra@stanford.edu
Cc: ding@gnus.org
Subject: Re: nnrss lacks basic crosspost detection; should use guid
Date: Sun, 08 Mar 2009 08:20:43 +0800 [thread overview]
Message-ID: <87fxho27c4.fsf@jidanni.org> (raw)
In-Reply-To: <87eixghovc.fsf@windlord.stanford.edu>
RA> I'm fairly certain that's correct. One of the feeds I generate uses a
RA> timestamp for the guid -- it's unique for that particular feed, but it's
RA> definitely not going to be globally unique.
Well, it turns out the only time a server can use <guid
isPermaLink="true"> is when the guid fully matches a vaild URL.
I.e., the RSS standard has glued the Usenet etc. concept of unique
Message-ID together with the concept of permanent URI.
So now there is no way to say, "yes, message A in the feed X I
provide, is the same as message A in feed Y that I provide", unless
one is also willing to give a permanent URI. I suppose. See
http://core.trac.wordpress.org/ticket/9280
Anyway, maybe nnrss should have a switch:
(set nnrss-assume-all-guids-are-like-usenet-message-ids t)
next prev parent reply other threads:[~2009-03-08 0:20 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
2009-03-01 22:14 ` Russ Allbery
2009-03-08 0:20 ` jidanni [this message]
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=87fxho27c4.fsf@jidanni.org \
--to=jidanni@jidanni.org \
--cc=ding@gnus.org \
--cc=rra@stanford.edu \
/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).