Google会收集这些数据来分析用户的使用习惯、喜好等，以改进产品及服务。但由于Google Reader API并未正式发布，因此如果你想找出Google所收集的这些资料并不容易。尽管Google在05年就说"几周后发布"Google Reader API，但至今仍不见踪影。还好，Google Reader的爱好者挖掘了不少隐藏链接，你也可以将它们看作是未发布的API的一部分。
在以下链接（由Ionut提供）里，-代表的是你的Google Reader用户ID。要知道自己的用户ID，请打开Google Reader后，在浏览器地址栏里输入下面代码后回车：
javascript:prompt("User ID", _USER_ID);void(0);
以下是Google Reader的部分隐藏链接（请将-替换成上面的用户ID）：
*你通过邮件向好友分享过的文章
http://www.google.com/reader/vie ... le/tracking-emailed
*你标记为未读的所有文章（"标记所有为未读"的文章除外）
http://www.google.com/reader/vie ... racking-kept-unread
*你点击了主链接的所有文章
http://www.google.com/reader/vie ... king-item-link-used
*你点击了文章内容里的链接的所有文章
http://www.google.com/reader/vie ... king-body-link-used
*在列表模式下阅读过的文章
http://www.google.com/reader/view/user/-/state/com.google/read
*你订阅过的邮Google Reader推荐的feed：
http://www.google.com/reader/vie ... ndations-subscribed
GoogleReaderAPI
Note : This document is totally unofficial. You should not rely on anything on this document is you need an exact information. Google Reader API has not officially been released. This document has been made mainly by reverse engeneering the protocol.
Requierements
Google Reader API require :
http client GET and POST support Cookie support https client
https is only required for identification with Google to get the string called SID. You can rely on an external tool to connect with https and give you SID. If you do, https won't be required.
Cookie support is only required to pass to all pages the current SID, proof of identification. If are able to change add lines in headers, cookie support is not required anymore.
Google Reader API may require :
http client GET and POST support external tool to get SID (using https) putting SID into header
http://code.google.com/p/pyrfeed/wiki/GoogleReaderAPI
