User-specific data is accessible using the cookie named “SID.” Feed retrieval No cookies or session IDs are required to access this member-specific data.
Google Reader users are assigned a 20-digit user ID used throughout Google’s feed system.
Google Reader’s “lens” provides only one view of the available data. You can also retrieve and synchronize feed subscription lists with an established user base that could be in the millions, providing a better experience for users on multiple devices and platforms. Google and its team of engineers and server clusters can handle the hard work of understanding feeds in various formats and states of validation, allowing developers to focus on the interaction experience and other differentiating features. Jason confirmed my documentation below is very accurate and Google plans to release a feed API “soon” and perhaps within the next month! Google Reader engineer Chris Wetherell has also confirmed the API in the comments below.Ī reliable feed parser managed by a third party lowers the barrier to entry of new aggregator developers.
#Google reader 2.0 update#
Update 10:40 p.m.:Jason Shellen, PM of Google Reader, called me to let me know that Google built its feed API first and the Google Reader application second as a demonstration of what could be done with the underlying data. I will walk you through the (previously) undocumented Google Reader API. The data technologies powering Google Reader can easily be used and extended by third-party feed aggregators for use in their own applications. Google’s AJAX front-end styles back-end data published in the Atom syndication format. Google Reader is an online feed aggregator with heavy use of JavaScript and pretty quick loading of the latest feed data from around the web.
0 kommentar(er)
