From: joakim@verona.se
Cc: ding@gnus.org
Subject: Re: problem with nnrss and slashdot
Date: Thu, 10 Aug 2006 08:42:51 +0200 [thread overview]
Message-ID: <m3irl13xck.fsf@kurono.home> (raw)
In-Reply-To: <ws64h2axlk.fsf@stone.tss.usg.edu> (Mark Plaksin's message of "Wed, 09 Aug 2006 08:43:19 -0400")
I was able to solve this problem localy for slashdot, after some
research.
There are several related threads on this:
http://thread.gmane.org/gmane.emacs.gnus.general/63268
http://article.gmane.org/gmane.emacs.gnus.general/62613
Looking in nnrss-check-group, a message ID is sythesized out of an rss
article by means of printing the lisp representation to a string and
do a md5 on it. This md5 is used to determine if the article has
changed.
Slashdot includes tags like:
"( slash:department nil "development-has-to-come-from-somewhere") . "
"( slash:section nil "developers") . "
"( slash:comments nil "46") . "
"( slash:hit_parade nil "46,44,36,28,12,3,1") . "
The number of comments vary with each rss poll, which makes the
article appear new again.
I tried a local patch whitch filters away slash: tags before md5. This
works but isnt a general solution.
I think the best would be, given the reasoning in the threads above,
to allow both article-md5, and date-md5 methods, selectable on a feed
basis.
Mark Plaksin <happy@mcplaksin.org> writes:
> Dave Goldberg <david.goldberg6@verizon.net> writes:
>
>>>>>>> On Mon, 07 Aug 2006 12:44:58 +0200, joakim@verona.se said:
>>
>>> joakim@verona.se writes:
>>>> I recently upgraded gnus, and now the rss feed from slashdot get new
>>>> copies everytime i update the group. Any hints?
>>
>>> This problem remains. Is there anything I can do to help debug it?
>>> Specifically I'm having problems with the slashdot rss feed.
>>
>> Just yesterday I decided to give gnus a try as an rss reader and
>> slashdot was one of my test cases. I see the same behavior as above.
>> However, I don't see it with a couple other feeds. I also took a look
>> at the changelogs and nnrss doesn't seem to have changed in some time.
>> Assuming it did work correctly once, I suspect that slashdot has made
>> some change that gnus is not prepared for.
>
> For me it happens in most of my nnrss groups. Not all of them but almost
> all of them. So I think it's Gnus that changed and not all the RSS feeds.
>
> I hope to have time to debug the problem in the next week or three.
>
>
>
--
Joakim Verona
http://www.verona.se
next prev parent reply other threads:[~2006-08-10 6:42 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-16 10:51 joakim
2006-06-21 15:15 ` Mark Plaksin
2006-08-07 10:44 ` joakim
2006-08-09 2:52 ` Dave Goldberg
2006-08-09 12:43 ` Mark Plaksin
2006-08-10 6:42 ` joakim [this message]
2006-08-10 20:01 ` David Hansen
2006-08-09 22:16 ` Dave Goldberg
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=m3irl13xck.fsf@kurono.home \
--to=joakim@verona.se \
--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).