From: jidanni@jidanni.org
To: ding@gnus.org
Subject: nnrss lacks basic crosspost detection; should use guid
Date: Sat, 28 Feb 2009 04:53:14 +0800 [thread overview]
Message-ID: <87r61jwqit.fsf@jidanni.org> (raw)
Alas,
http://www.coolloud.org.tw/tag/新移民/feed
http://www.coolloud.org.tw/tag/移民工/feed
have the same item,
<guid isPermaLink="false">35873 at http://www.coolloud.org.tw</guid>
with the same date even, but nnrss is not smart enough to mark it read
globally if read in one group.
Part of the problem is that nnrss totally ignores the guid, and
instead insists on making its own Message-IDs,
Message-ID: <828@=?utf-8?B?6KiC6Zax6Ium5YueX+enu+awkeW3pV/nmoTmlofnq6A=?=.nnrss>
Message-ID: <73@=?utf-8?B?6KiC6Zax6Ium5YueX+aWsOenu+awkV/nmoTmlofnq6A=?=.nnrss>
Decoding, <828@訂閱苦勞_移民工_的文.nnrss>, we see the encoded part
was merely the group description.
If the Message-ID just used the guid, perhaps crossposts could be
detected, and marked as read globally. Only if there is no guid, then
fall back to the current scheme.
next reply other threads:[~2009-02-27 20:53 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-27 20:53 jidanni [this message]
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
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=87r61jwqit.fsf@jidanni.org \
--to=jidanni@jidanni.org \
--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).