Announcements and discussions for Gnus, the GNU Emacs Usenet newsreader
 help / color / mirror / Atom feed
From: Tim Landscheidt <tim@tim-landscheidt.de>
To: info-gnus-english@gnu.org
Subject: Re: RSS with Gnus (elfeed backend?)
Date: Fri, 02 Apr 2021 18:21:07 +0000	[thread overview]
Message-ID: <87blawfsz0.fsf@passepartout.tim-landscheidt.de> (raw)
In-Reply-To: <87r1jsn1rp.fsf@pc-117-162.ovh.com>

Garjola Dindi <garjola@garjola.net> wrote:

>> Have you tried gwene.org?
>> You register the rss feed with the site, and it shows up as a newsgroup
>> you can subscribe to via news.gwene.org. I follow many
>> sites in gnus via this method. You may find many of the site you wish to
>> follow are already there...

> Thanks for the suggestion. I am aware of gwene and I have used it in the
> past. But I would prefer something which does not depend on a
> centralized server. This defeats one of the purposes of RSS itself, in
> my opinion. And there is also the issue of private feeds, of course.

> I really think that nrss should be improved to solve its shortcomings
> and it seems that elfeed is a very good feed reader. I wish I had the
> skills to propose some patches or something.

> I will study the code and the documentation on how to build a new
> backend, but it will take months for me. Maybe if I start something this
> will motivate real elisp programmers to chime in?

It's even worse because Emacs already has yet another (rath-
er fragile) RSS reader, newsticker, that AFAIR does not
share code with either, and nnrss has an asynchronous, yet
somewhat manual out-of-Gnus retriever
(nnrss-generate-download-script), the keys for moving to the
next or the next unread article in newsticker are "reversed"
compared to Gnus, elfeed seems to have a separate system for
scoring articles, etc., etc., etc.  newsticker as well as
nnrss feel like "technology demonstrators", i. e., yeah, you
can read RSS feeds in Emacs or Gnus, but nobody really does.

So if someone would implement a (preferably new) nice, clean
backend for Gnus that DWIM, I'd be eternally grateful :-).

Tim


_______________________________________________
info-gnus-english mailing list
info-gnus-english@gnu.org
https://lists.gnu.org/mailman/listinfo/info-gnus-english

  reply	other threads:[~2021-04-02 18:21 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-01 18:59 Garjola Dindi
2021-04-01 19:19 ` Jose A. Ortega Ruiz
2021-04-02  6:43   ` Garjola Dindi
2021-04-02 20:44     ` Jose A. Ortega Ruiz
2021-04-03  7:34       ` Garjola Dindi
2021-04-02 15:04 ` Jeffrey DeLeo
2021-04-02 15:29   ` Garjola Dindi
2021-04-02 18:21     ` Tim Landscheidt [this message]
2021-04-03  7:30       ` Garjola Dindi
2021-04-04  0:06         ` Eric Abrahamsen
2021-04-04  9:59           ` Garjola Dindi

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=87blawfsz0.fsf@passepartout.tim-landscheidt.de \
    --to=tim@tim-landscheidt.de \
    --cc=info-gnus-english@gnu.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).