From: Eric S Fraga <e.fraga@ucl.ac.uk>
To: ding@gnus.org
Subject: Re: Why am I getting duplicate messages on RSS groups?
Date: Sun, 28 Apr 2024 11:02:37 +0100 [thread overview]
Message-ID: <87cyq9by9u.fsf@ucl.ac.uk> (raw)
In-Reply-To: <87edar7qnn.fsf@gmx.net>
On Saturday, 27 Apr 2024 at 03:06, James Thomas wrote:
> The latter, I suppose, since it could vary by site. I had the following:
>
> '(slash:comments slash:hit_parade num_comments ups)
>
> ...for slashdot.org (before I switched to the new nnatom backend).
Thank you. None of these appear in the headers for my rss feeds, most
of which are mastodon tags or individuals. Mastodon rss feeds are quite
minimal in the information they propagate unfortunately.
--
Eric S Fraga via gnus (Emacs 30.0.50 2024-04-18) on Debian 12.5
next prev parent reply other threads:[~2024-04-28 10:03 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-17 8:52 Nasser Alkmim
2024-04-17 9:28 ` Emanuel Berg
2024-04-17 10:47 ` Nasser Alkmim
2024-04-26 5:42 ` Nasser Alkmim
2024-04-17 15:08 ` Tim Landscheidt
2024-04-26 15:16 ` James Thomas
2024-04-26 15:32 ` Eric S Fraga
2024-04-26 21:36 ` James Thomas
2024-04-28 10:02 ` Eric S Fraga [this message]
2024-04-27 6:54 ` Nasser Alkmim
2024-04-27 9:33 ` James Thomas
2024-04-27 13:07 ` Nasser Alkmim
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=87cyq9by9u.fsf@ucl.ac.uk \
--to=e.fraga@ucl.ac.uk \
--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).