From: Ted Zlatanov <tzz@lifelogs.com>
To: ding@gnus.org
Subject: Re: nnrss through Google Reader
Date: Fri, 31 Jul 2009 08:44:07 -0500 [thread overview]
Message-ID: <87ws5p3r2w.fsf@lifelogs.com> (raw)
In-Reply-To: <877hxr8i7a.fsf_-_@lifelogs.com>
On Wed, 29 Jul 2009 13:20:09 -0500 Ted Zlatanov <tzz@lifelogs.com> wrote:
TZ> I'd really like to use Google Reader. Its protocol has been
TZ> reverse-engineered here:
TZ> http://code.google.com/p/pyrfeed/wiki/GoogleReaderAPI
TZ> in case anyone is interested. The API may change before release so any
TZ> code written may have to be redone. Looks like the easy way to get
TZ> all the current headlines is:
TZ> https://www.google.com/reader/atom/user/-/state/com.google/reading-list?xt=user/-/state/com.google/read
TZ> according to one comment.
TZ> This would be a nice mix of nnkiboze and nnrss, but all the work is done
TZ> at the Google server and you're not killing the host of the RSS feed
TZ> with repeated requests. You can get the headlines for a specific feed
TZ> only, too.
Funnily enough, my other RSS reader (NetNewsWire) now synchronizes with
Google Reader, so if Gnus could do it too, I'd be quite happy.
I looked into it, and Reader is an OK web interface on top of a pretty
good feed database. Gnus can probably do what NetNewsWire and others
have done to integrate. Now, NNW had help from Google directly, so I
assume they are using an "approved" API. We'd have to use the
reverse-engineered knowledge, which is risky.
In addition, I'm not sure if supporting a proprietary product is the
right thing, or if I should think about a more generic framework that
supports Google Reader but doesn't require it. Tighter integration is
surely better in the short term.
Ted
next prev parent reply other threads:[~2009-07-31 13:44 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 ` nnrss through Google Reader (was: Gnus' speed) Ted Zlatanov
2009-07-31 13:44 ` Ted Zlatanov [this message]
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=87ws5p3r2w.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).