Monday, September 22, 2008

How do I share my Google Reader Shared Items Feed and process it via Yahoo Pipes?

Google Reader provides all kinds of nice feeds from your "folders" (tags) and your shared items. Most of 'em can be managed by any feed reader, including Yahoo Pipes.

Except for the Shared Items Feed. That one requires a cookie corresponding to a Google Gmail account. I'd like to be able to share manipulate that feed, so I've posted a question on the Google Reader Group:

Share my Google Reader Shared Items Feed and process in Yahoo Pipes - How Do I? | Google Groups

Public Google Reader folders (tags) have feeds. They don't require authentication; I can manage them in Yahoo Pipes, anyone can see them.

Things are different from the Google Reader Shared Items (and probably starred items too). They have a feed, but it requires a Google (Gmail?) account to be read.

For example, here's the Atom feed for my shared items:

http://www.google.com/reader/atom/user/06457543619879090746/state/com.google/reading-list

I think anyone with a Google account can view it (may have to log in) this feed using Google Reader.

I can't add it to Bloglines though, and Yahoo Pipes can't process it.

I do realize that anyone can view the web version of this:

http://www.google.com/reader/shared/06457543619879090746

but that's not what I want to share. I want to be able to publicly share and process the shared items feed including sharing it with people who don't have a Gmail account.

Is there a way to do this (short of using a feed proxy)?

I doubt there's a solution today, but maybe Google will rethink this requirement ...

Update 2/2/09: I find a fix from a different angle.

2 comments:

Abel said...

I realize this post is a few months old. You might have figured it out by now, or Google might have changed things since your posting...

Have you tried this: http://www.google.com/reader/public/atom/user/06457543619879090746/state/com.google/broadcast

I just found it myself

John Gordon said...

Thanks, I'll try again. I could do the feed, but the problem was reading it required a google cookie stored with gmail authentication.