From: Haider Rizvi <harizvi@gmail.com>
To: ding@gnus.org
Subject: Re: Update RSS feeds less frequently
Date: Mon, 19 Dec 2022 13:44:49 -0700 [thread overview]
Message-ID: <m1edsvdsxq.fsf@gmail.com> (raw)
In-Reply-To: <87mt7lg73d.fsf@johnhaman.org>
John Haman <mail@johnhaman.org> writes:
> Adam Sjøgren <asjo@koldfront.dk> writes:
>
>>
>> A third solution is to read RSS via nntp on news.gwene.org¹ or on
>> feedbase.org² - mentioning the latter is a shameless plug, as I built it
>> to consume RSS myself :-)
Most of my rss / atom feeds are via gwene (and some via feedbase - thanks Adam for providing this service).
One option not yet mentioned: if you only want to use native RSS capabilities, you may want to look at nnrss-generate-download-script. Once you have a script, you can divide up into multiple prioritized scripts and fetch via cron as appropriate.
--
next prev parent reply other threads:[~2022-12-20 2:11 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-16 4:08 John Haman
2022-12-17 7:43 ` Bodertz
2022-12-17 12:50 ` Eric S Fraga
2022-12-17 16:33 ` John Haman
2022-12-17 16:59 ` Adam Sjøgren
2022-12-17 19:31 ` John Haman
2022-12-19 20:44 ` Haider Rizvi [this message]
2022-12-19 21:04 ` Bob Newell
2022-12-20 1:23 ` John Haman
2022-12-21 22:05 ` Bob Newell
2022-12-17 19:45 ` Bob Newell
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=m1edsvdsxq.fsf@gmail.com \
--to=harizvi@gmail.com \
--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).