From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.io/gmane.emacs.gnus.general/68855 Path: news.gmane.org!not-for-mail From: Ted Zlatanov Newsgroups: gmane.emacs.gnus.general Subject: Re: nnrss through Google Reader Date: Fri, 31 Jul 2009 08:44:07 -0500 Organization: =?utf-8?B?0KLQtdC+0LTQvtGAINCX0LvQsNGC0LDQvdC+0LI=?= @ Cienfuegos Message-ID: <87ws5p3r2w.fsf@lifelogs.com> References: <87zlao7j1z.fsf@CPU107.opentrends.net> <877hxr8i7a.fsf_-_@lifelogs.com> NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: ger.gmane.org 1249047942 19972 80.91.229.12 (31 Jul 2009 13:45:42 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Fri, 31 Jul 2009 13:45:42 +0000 (UTC) To: ding@gnus.org Original-X-From: ding-owner+M17275@lists.math.uh.edu Fri Jul 31 15:45:26 2009 Return-path: Envelope-to: ding-account@gmane.org Original-Received: from util0.math.uh.edu ([129.7.128.18]) by lo.gmane.org with esmtp (Exim 4.50) id 1MWsQE-0001L2-MM for ding-account@gmane.org; Fri, 31 Jul 2009 15:45:22 +0200 Original-Received: from localhost ([127.0.0.1] helo=lists.math.uh.edu) by util0.math.uh.edu with smtp (Exim 4.63) (envelope-from ) id 1MWsPX-0007zg-FO; Fri, 31 Jul 2009 08:44:39 -0500 Original-Received: from mx1.math.uh.edu ([129.7.128.32]) by util0.math.uh.edu with esmtps (TLSv1:AES256-SHA:256) (Exim 4.63) (envelope-from ) id 1MWsPU-0007zL-Fk for ding@lists.math.uh.edu; Fri, 31 Jul 2009 08:44:36 -0500 Original-Received: from quimby.gnus.org ([80.91.231.51]) by mx1.math.uh.edu with esmtp (Exim 4.69) (envelope-from ) id 1MWsPJ-00031l-5y for ding@lists.math.uh.edu; Fri, 31 Jul 2009 08:44:36 -0500 Original-Received: from main.gmane.org ([80.91.229.2] helo=ciao.gmane.org) by quimby.gnus.org with esmtp (Exim 3.36 #1 (Debian)) id 1MWsPs-0006Ny-00 for ; Fri, 31 Jul 2009 15:45:00 +0200 Original-Received: from list by ciao.gmane.org with local (Exim 4.43) id 1MWsPE-000385-Vf for ding@gnus.org; Fri, 31 Jul 2009 13:44:21 +0000 Original-Received: from 38.98.147.130 ([38.98.147.130]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Fri, 31 Jul 2009 13:44:20 +0000 Original-Received: from tzz by 38.98.147.130 with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Fri, 31 Jul 2009 13:44:20 +0000 X-Injected-Via-Gmane: http://gmane.org/ Original-Lines: 35 Original-X-Complaints-To: usenet@ger.gmane.org X-Gmane-NNTP-Posting-Host: 38.98.147.130 X-Face: bd.DQ~'29fIs`T_%O%C\g%6jW)yi[zuz6;d4V0`@y-~$#3P_Ng{@m+e4o<4P'#(_GJQ%TT= D}[Ep*b!\e,fBZ'j_+#"Ps?s2!4H2-Y"sx" User-Agent: Gnus/5.110011 (No Gnus v0.11) Emacs/23.1.50 (gnu/linux) Cancel-Lock: sha1:lSZ18SS8M2Ep4GwxajO6D1b+04k= X-Spam-Score: -1.5 (-) List-ID: Precedence: bulk Xref: news.gmane.org gmane.emacs.gnus.general:68855 Archived-At: On Wed, 29 Jul 2009 13:20:09 -0500 Ted Zlatanov 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