Gnus development mailing list
 help / color / mirror / Atom feed
From: Ted Zlatanov <tzz@lifelogs.com>
To: ding@gnus.org
Subject: nnrss through Google Reader (was: Gnus' speed)
Date: Wed, 29 Jul 2009 13:20:09 -0500	[thread overview]
Message-ID: <877hxr8i7a.fsf_-_@lifelogs.com> (raw)
In-Reply-To: <m27hxsklwr.fsf@cyberhut.org>

On Wed, 29 Jul 2009 15:07:00 +0800 CHENG Gao <chenggao@gmail.com> wrote: 

CG> nnrss is really a headache, esp. when I have many subscriptions. Gnus is
CG> slow in comparison with other dedicated RSS readers. I use NetNewsWire
CG> and can see the speed gap. I am trying to find a solution to make RSS
CG> reading offline. 
...
CG> Another candidate is nntp//rss (http://www.methodize.org/nntprss/). But
CG> its download link is b0rked.

I use it and have the JAR file.  It's OK, but has trouble with some
feeds.

I'd really like to use Google Reader.  Its protocol has been
reverse-engineered here:

http://code.google.com/p/pyrfeed/wiki/GoogleReaderAPI 

in case anyone is interested.  The API may change before release so any
code written may have to be redone.  Looks like the easy way to get
all the current headlines is:

https://www.google.com/reader/atom/user/-/state/com.google/reading-list?xt=user/-/state/com.google/read

according to one comment.

This would be a nice mix of nnkiboze and nnrss, but all the work is done
at the Google server and you're not killing the host of the RSS feed
with repeated requests.  You can get the headlines for a specific feed
only, too.

Ted




  reply	other threads:[~2009-07-29 18:20 UTC|newest]

Thread overview: 41+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-28 18:34 Gnus' speed Daniel Clemente
2009-07-28 21:03 ` Leo
2009-07-29  8:03   ` Daniel Clemente
2009-07-29  8:44     ` David Engster
2009-07-29 11:03       ` Karl Kleinpaste
2009-07-29 11:59         ` David Engster
2009-07-29 12:26           ` Karl Kleinpaste
2009-07-29 12:44             ` David Engster
2009-07-29 18:30               ` Ted Zlatanov
2009-07-29 20:19                 ` Tom Tromey
2009-07-30  6:03                   ` Daniel Pittman
2009-07-31  6:30                 ` Bill White
2009-07-29 18:46           ` Reiner Steib
2009-08-15  1:07           ` Miles Bader
2009-08-15  1:50             ` Daniel Pittman
2009-07-29 18:25       ` Ted Zlatanov
2009-07-29  9:47     ` Leo
2009-07-29 18:24     ` Ted Zlatanov
2009-07-30  5:58       ` Daniel Pittman
2009-07-30 13:33         ` Ted Zlatanov
2009-07-31  5:06           ` Daniel Pittman
2009-08-02 14:20       ` Steinar Bang
2009-08-03 14:38         ` Ted Zlatanov
2009-07-30  5:59     ` Daniel Pittman
2009-07-29  7:07 ` CHENG Gao
2009-07-29 18:20   ` Ted Zlatanov [this message]
2009-07-31 13:44     ` nnrss through Google Reader Ted Zlatanov
2009-07-30  0:38   ` Gnus' speed Kevin Ryde
2009-07-29 18:55 ` Reiner Steib
2009-07-30  0:29   ` Kevin Ryde
2009-07-30  7:41     ` Adam Sjøgren
2009-08-04  1:10       ` Kevin Ryde
2009-08-15  1:11     ` Miles Bader
2009-08-15  8:28       ` Steinar Bang
2009-08-16  3:50         ` Miles Bader
2009-08-04 17:48   ` Daniel Clemente
2009-08-04 17:46 ` Daniel Clemente
2009-08-05  5:52   ` Steinar Bang
2009-08-05  5:55     ` Steinar Bang
2009-08-05  8:20       ` Daniel Clemente
2009-08-05 15:10         ` Steinar Bang

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=877hxr8i7a.fsf_-_@lifelogs.com \
    --to=tzz@lifelogs.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).