Google is about to launch its second Windows Phone app. This time, Google picked a service that was used by a few million users until it was discontinued last year: Google Reader.

While the new app won't be able to show the latest news from your feeds, it's a clear sign that Google started to embrace Microsoft's mobile platform. Apparently, Google was about to launch the app in January 2013, but developers were busy updating Google's apps for Android and iOS. A week ago, someone found the app and decided it's a good idea to release it. The application lets you login to your Google account and shows this message: "Google Reader has been discontinued. We want to thank all our loyal fans. We understand you may not agree with this decision, but we hope you'll come to love these alternatives as much as you loved Reader."


It's simple, minimalist and pretty late, just like Windows Phone.

If you created a full backup for your Google Reader account while it was still possible, you probably need a way browse the data. Fortunately, Mihai Parparita created Zombie Reader, a tool that resurects the Google Reader interface and transforms into a viewer for your data.

"Reader is a canonical single page application: once the initial HTML, JavaScript, CSS, etc. payload is delivered, all other data is loaded via relatively straightforward HTTP calls that return JSON (this made adding basic offline support relatively easy back in 2007). Therefore if I served the archived data in the same JSON format, then I should be able to browse it using Reader's own JavaScript and CSS," says Mihai.

Go to readerisdead.com, download the updated archive and use the instructions from the page. You still need Python 2.7 and some basic command-line skills. For Windows, you could use the instructions from my previous post and replace:

c:\python27\python reader_archive\reader_archive.py --output=download

with

c:\python27\python zombie_reader\zombie_reader.py download


Zombie Reader uses the Google Reader interface and your local data. It's like a Google Reader snapshot that preserved all your subscriptions, all the items you've read or marked as read, all your starred items, your tags and much more. Obviously, many features don't work (search, trends, subscribe), the application doesn't save your state and it doesn't show the latest posts from your subscriptions.

It does show your first read item, first starred item and the first shared item, as well as the people you followed before Reader's social features were removed. The "sort by oldest" feature is no longer limited to the last 30 days, it now sorts all your feed items.

"A side effect is that I now have a self-contained Reader installation that I'll be able to refer to years from now, when my son asks me how I spent my mid-20s," says Mihai. "It also satisfies my own nostalgia kicks, like knowing what my first read item was. In theory I could also use this approach to build a proxy that exposes Reader's API backed by (say) NewsBlur's, and thus keep using the Reader UI to read current feeds. Beyond the technical issues (e.g. impedance mismatches, since NewsBlur doesn't store read or starred state as tags, or has per item tags in general) that seems like an overly backwards-facing option." I'm sure that someone will build the proxy.

For some reason, a day before Google Reader was closed, Google Developers blog published an article about PubSubHubbbub, feeds and the Google Feeds API. PubSubHubbub (PuSH) is a protocol for sending notifications when a feed is updated. "Using the PuSH protocol, servers can subscribe to an almost arbitrarily large number of feeds and receive updates as they occur." Google encourages publishers to submit their feeds to a public PuSH hub like Google's hub and Superfeedr's Open PubSubHubbub Hub.

The most interesting part of the post is this one: "Google directly hosts many feed producers (e.g. Blogger is one of the largest feed sources on the web) and is a feed consumer too (e.g. many webmasters use feeds to tell our Search system about changes on their sites). Our PuSH hub offers easy access to hundreds of millions of Google-hosted feeds, as well as hundreds of millions of other feeds available via the PuSH ecosystem and through active polling." And something else: "We are planning some improvements to the Feed API, as part of our ongoing infrastructure work."

This means that Google's feed processing backend will continue to exist, but will focus on the Google Feeds API and Google Search index updates. Google Feeds API will also continue to exist and third-party feed readers could use it. All of this was an important part of the Google Reader backend, but Google Reader also had to manage subscriptions, labels, the read/unread state, create a search index for each user.


Hopefully, this also means that Google's services will continue to offer feeds. Maybe, at some point, even Google+ could add support for feeds.

Update: Google Feedfetcher is still running and shows almost the same number of subscribers. Here's a screenshot from FeedBurner:


"Feedfetcher is how Google grabs RSS or Atom feeds when users choose to add them to their Google homepage or Google Reader. Feedfetcher collects and periodically refreshes these user-initiated feeds, but does not index them in Blog Search or Google's other search services (feeds appear in our search results only if they've been crawled by Googlebot)." - from Google's help center.

Tomek Wasiak noticed Google Feedfetcher in his site's logs today. He subscribed to the site's feed in Google Reader and he's the only subscriber.

If you read the post about the well-connected Google Reader, you probably anticipated this chain reaction. All the services that integrated with Google Reader will remove their features, now that Reader is gone.

Google Alerts no longer supports RSS delivery and recommends users to switch to email delivery. "Google Reader is no longer available. To continue receiving Google Alerts, go to http://www.google.com/alerts/manage and change your alerts to email delivery," says Google.

You're probably wondering: what's the connection between Google Alerts feeds and Google Reader? Google Alerts feeds, which were added back in 2008, had public URLs and you could use any feed reader to subscribe to them. The trouble is that the feeds were generated by Google Reader and were actually a Google Reader feature, just like the web page monitoring feature.




Unfortunately, Google doesn't offer feeds for search results and the Web Search API has been deprecated and it was too limited to create a service like Google Alerts. The only obvious alternative is to screenscrape Google results.

Talkwalker Alerts looks almost like Google Alerts and offers both email alerts and feeds. The service is free for up to 100 alerts.

If you open Google Reader, you'll see this message:

Thank you for stopping by.

Google Reader has been discontinued. We want to thank all our loyal fans. We understand you may not agree with this decision, but we hope you'll come to love these alternatives as much as you loved Reader.

Sincerely,

The Google Reader team

Frequently-asked questions

What will happen to my Google Reader data?

All Google Reader subscription data (eg. lists of people that you follow, items you have starred, notes you have created, etc.) will be systematically deleted from Google servers. You can download a copy of your Google Reader data via Google Takeout until 12PM PST July 15, 2013.

Will there be any way to retrieve my subscription data from Google in the future?

No -- all subscription data will be permanently, and irrevocably deleted. Google will not be able to recover any Google Reader subscription data for any user after July 15, 2013.

Why was Google Reader discontinued?

Please refer to our blog post for more information.

I don't understand why Google removes Reader data so soon and why the message uses words like "systematically deleted", "permanently, and irrevocably deleted". It's like they try to get rid of everything that's related to Reader. I can still download Google Buzz data from Google Takeout. A similar message was posted for Google Health, but users had one year to download their data.

"Congratulations, you've reached the end of this internet. Look for another?" That's the message you see when you use the Google Reader bookmarklet and you read all the posts from your subscriptions. It's a joke that's quite bitter, now that the end of Google Reader is really close.


Google Reader was more than just a feed reader, it was probably the most well-connected Google service. It was integrated with so many Google services and now all of them will be a little less useful. The missing features, which relied on Google Reader, will show how important this service really was.

iGoogle's canvas view for feeds was powered by Google Reader and now it's no longer available, just like the Reader gadget.

"Reader is dead," says Mihai Parparita, one of the former Google Reader engineers. You still have 2-3 days to use Google Reader, but the best thing you can do is to export your data.

Google Takeout lets you export some of your Reader data, but not everything: your subscriptions, your notes, starred items, shared items, liked items, the list of followers and the people you were following, the items shared by the people you were following. Mihai Parparita wrote some Python scripts that download everything from your Google Reader accounts, including the entire content of the posts from your subscriptions. You need Python 2.7, some basic command-line skills and a lot of free storage: my backup has more than 5 GB for about 250 feeds (vs 125 MB for the uncompressed Takeout backup).


Here are some tips for running the script in Windows 7/8:

- install Python from here (Python 2.7.5 Windows Installer)
- download Mihai's zip file and extract the files
- open the folder in Windows Explorer and you should see a list of subfolders like "base", "bin", "feed_archive".


- Shift + right-click below the folders and select "open command-line window here".
- copy this code, paste it in the command-line window and press Enter (I assumed that Python's folder is c:\python27):

set PYTHONPATH=%cd%
c:\python27\python reader_archive\reader_archive.py --output=download

- a web page will open in your favorite browser and you'll need to click "Accept", copy the authorization code and paste it in the command-line window.
- wait until the script downloads all the files.

Mihai also started to write a script that lets you browse your archive. It's a work in progress, probably because the script for downloading your data is more important right now.

There's also a script for downloading a feed's archive. "Google Reader has (for the most part) a copy of all blog posts and other feed items published since its launch in late 2005 (assuming that at least one Reader user subscribed to the feed). This makes it an invaluable resource for sites that disappear, can serve as a backup mechanism and enables tools to be created." My post from 2007 provides another way to download the history of a feed. You can also upload your OPML file to this site, which preserves hitorical feed data.

"I don't fault Google for providing only partial data via Takeout. Exporting all 612,599 read items in my account (and a few hundred thousand more from subscriptions, recommendations, etc.) results in almost 4 GB of data. Even if I'm in the 99th percentile for Reader users (I've got the badge to prove it), providing hundreds of megabytes of data per user would not be feasible. I'm actually happy that Takeout support happened at all, since my understanding is that it was all during 20% time," says Mihai Parparita, who spent 5 years working on Google Reader.

If you're curious to know which Reader alternative gets a thumb up from Mihai, his answer is "a toss-up between NewsBlur and Digg Reader."

Google used this many times last year: "the playground is open". That's one of the most important things about Android: it's open source and any company can use it. One of the definitions of "open" is "accessible to all, unrestricted as to participants".

The playground for feed readers is now open. Google Reader's demise levels the playing field in the feed reading world. Now there are more competitors, there's more innovation, there are new platforms for distributing feeds, new interfaces. Suddenly, feed readers are a hot topic. Until now, Google Reader was the dominant service and platform, but Google didn't know what to do with it. Google Reader stopped adding new features back in 2010 and it was in maintenance mode ever since then. Few dared to challenge its position and most new feed readers were only Google Reader clients.

Google Reader's disappearance is Google's best idea for saving RSS. From stagnant to vibrant in 3 months - Google Reader's demise helped RSS more than the last 3 years of silence. The playground is now open.


And for those who are sad that Reader will soon be gone - don't worry, there's a bit of Google Reader in any feed reader that has launched in the past 3-4 years or will launch in the near future. Maybe it's time to get a better Reader, even if not from Google...

Back in 2007, Google accidentally made public an internal video about Google Reader. The video included a lot of useful information about Google Reader, the kind of details you'll never find in a Google post or presentation.

I'm trying to solve the puzzle and find the number of Google Reader users from 2007. Here are the hints:

1. At that time, Google Reader crawled 8 million feeds.

2. Two thirds of the feeds had only one subscriber, one third of the feeds had more than one subscriber.

3. Google Reader used 10TB for storing all the raw data.

4. The rate of user growth = the rate of growth for the number of feeds.

5. The index size grew 4% every week.

6. 70% of the Google Reader traffic came from Firefox (at that time, Firefox's market share was about 15%).

7. Gmail and orkut were the only Google applications that had a bigger number of pageviews/user than Google Reader.

8. The main Google Blog had 100,000 subscribers and this number includes all the subscribers from iGoogle, Reader and orkut.

So, at that time, only 2.6 million feeds indexed by Google Reader had more than one subscriber. Probably many of the feeds that had only one subscriber were used by other Google services powered by Google Reader's backend (orkut, Blogger widgets, Google Spreadsheets, Ajax API) or they were Google News/Blog Search feeds. It makes sense to assume that the number of Google Reader users was lower than the number of feeds with more than one subscriber.

Here's a chart from 2010 that shows Google Reader's user growth:



And something else from 2010: "the average Reader user reads about 105 items a day".

It's probably worth distinguishing Reader as a service from Reader as a platform.

Many people think that Google Reader could've been more successful if Google promoted it more. The truth is that Google Reader has been the service that connected to the biggest number of Google services. No other Google benefited from so many service integrations.

Here's an incomplete list. Start counting:

1. a link to Reader was displayed in Gmail's inbox when there was no mail

2. for many years, Google Reader could be found in the main navigation bar, next to Gmail, Calendar and Google Docs

3. Google Reader was the first Google service that worked offline and the first Google service that used Google Gears, back in 2007



4. Google Reader integrated with Google Social Search, a feature that allowed you to restrict results to the pages written by your friends or people you follow.



5. iGoogle integrated with Google Reader when it started to add support for canvas view. Maximize a feed gadget and you get the Google Reader interface.



6. Blogger's Following feature was powered by Google Reader. "The blogs you follow in Blogger have been added as subscriptions in Google Reader. Subscriptions can be managed in Reader without affecting your following list in Blogger."



7. Listen, Google's podcast manager app for Android, used Google Reader to store subscriptions.

8. Google Alerts integrated with Google Reader, so you could subscribe to feeds instead of receiving email notofcations.

9. Back in 2008, Google's mobile transcoder displayed the site's feeds at the top of the page and linked to Google Reader.

10. Google Reader was the only Google product with an interface optimized for Nintendo Wii.

11. Google Currents, launched in 2011, allowed you to import your Google Reader subscriptions.

12. Google Buzz's commenting feature was integrated with Google Reader.



13. When Bloglines was discontinued in 2010, Google Reader's team encouraged users to switch to Reader. The blog post includes a graph of Reader users over time.


14. The Google Groups redesign from 2010 was inspired by Google Reader.

15. Google bought FeedBurner to monetize Google Reader and launched AdSense for Feeds.

16. Back in 2007, Google Reader made shared items available to Google Talk contacts and many people complained about this.

17. Google's Power Readers feature from 2008 allowed you to "track the news sites and blogs Barack Obama and John McCain read" using Google Reader. It was a clever way to promote Google Reader. This feature was expanded to "include journalists, techies, fashion critics, foodies and more".

18. Google Toolbar for IE allowed you to subscribe to feeds using iGoogle or Google Reader.

19. Google Blog Search still has this link below the list of search results page: "Subscribe to a blog search feed for [query] in Google Reader". Google News had a similar link.


20. Google Spreadsheets has a special function for importing feeds that was initially called GoogleReader. Now it's called ImportFeed.

21. Google TV Queue uses Google Reader to manage subscriptions.

22. Google Reader was Google's infrastructure for feeds and the technology was used by iGoogle, orkut, Gmail's web clips, Blogger widgets, Google Spreadsheets and the Ajax API.

I'm sure you can find other examples of services that integrated with Google Reader. I didn't include all the third-party apps and services that used the unofficial Google Reader API. As you can see, Reader was an important part of the Google ecosystem and Google did promote the service in many ways.

There's just one week and a half and Google Reader will be history. If you're using the service, it's a good idea to export your data and switch to a different service. You can choose from Feedly, The Old Reader, MultiPLX, NewsBlur, Feedspot, Netvibes. I haven't decided which one I'll use, but Feedly is a strong contender.

Feedly is probably the service that will benefit the most from Google Reader's demise. It grew from 4 million users to 12 million users in only 3 months and that's impressive. The service was just a Google Reader client, an alternate interface for Google Reader that gained a foothold on mobile.

Feedly has recently started to migrate users from Google's backend to its own backend, while preserving most of their data. Feedly Cloud was built in record time and it's now a scalable infrastructure for Feedly that can also be used by other apps that were powered by the unofficial Google Reader API. There are 9 apps that use it, including gReader, Newsify and Sprout Social. If you don't like the mobile apps or the browser extensions, there's now a Feedly web app that's optimized for the desktop and replaces extensions. It's hard to morph from a client to a platforms in a few months.



I'll miss Google Reader, like many other power users. Unfortunately for us, Google is not the right company for niche services. Google wants to create products that are used by hundreds of million of users and Google Reader wasn't one of them. Feedly and other similar services will have to find a business model for something that's no longer cool, no longer supported by many browsers, no longer supported by Twitter (other sites to follow). For many people, social sites offer better value than feed readers and not even Google could change that.

"As a culture we have moved into a realm where the consumption of news is a near-constant process. Users with smartphones and tablets are consuming news in bits and bites throughout the course of the day — replacing the old standard behaviors of news consumption over breakfast along with a leisurely read at the end of the day. (...) Google is looking at pervasive means to surface news across products to address each user's interest with the right information at the right time via the most appropriate means," said Richard Gingras, Senior Director, News & Social Products at Google.

So what will you use instead of Google Reader?

It's hard to estimate the number of Google Reader users, but here are some data points:

- the most popular feed has more than 24 million subscribers (CNN):


- the second most popular feed has 6.6 million subscribers (Engadget):


- the third most popular feed has 1.7 million subscribers (NY Times)

- Google's official blog had 100,000 subscribers in 2007 and now it has about 353,000 subscribers


- JoelOnSoftware.com had 42,000 subscribers in 2008 and now it has 148,000 subscribers.

- according to FeedBurner, 87% of the subscribers to this blog's feed use Google Reader or iGoogle. Google Reader says that this blog has 115,035 subscribers, while the total number of subscribers is 144,173. Here are the FeedBurner stats (the green lines show the number of subscribers):


Here's the Google Trends chart for [google reader]:

Google announced that Google Reader will be discontinued on July 1st. It's a sad news, but it was inevitable. Google Reader has always been "on the chopping block" because it never got enough traction.

Everything started with a feed parser built by Chris Wetherell that turned into a feed reader, helped by Ben Darnell, Laurence Gonsalves, and Mihai Parparita. The product was launched in 2005 as a Google Labs project and it was significantly improved one year later, when the Google Reader team launched a completely new version. Over the years, Google Reader integrated with iGoogle, added social features and handled feed serving for all Google products. Back in 2007, Google Reader crawled 8 million feeds and 70% of the traffic was from Firefox users.

In 2011, Google removed Reader's social features and replaced them with a Google +1 button. It was the beginning of the end for Reader, who lost all the engineers from the original team. Google Reader is in maintenance mode ever since then.

While feeds are no longer important for many users and browsers start to drop support for reading feeds, social networks make newsfeeds popular and mobile apps like Flipboard simplify reading the news. Feeds are now a behind-the-scenes technology and full-fledged feed readers seem outdated.

"We know Reader has a devoted following who will be very sad to see it go. We're sad too. There are two simple reasons for this: usage of Google Reader has declined, and as a company we're pouring all of our energy into fewer products. We think that kind of focus will make for a better user experience," says Google's Alan Green.

It's hard to find a replacement for Google Reader, since Google Reader was the most popular feed reader and the competition couldn't keep up with it. You can still find some web-based feed readers, but none of them is as good as Google Reader. Congratulations to everyone who worked on the Reader team and thanks to all the people who subscribed to this blog in Google Reader.

Here's Google Reader's team from 2007:

Buzzfeed has an interesting article about the evolution of Google Reader. While the article mostly focuses on the social features that were removed from Google Reader a few months after Google+ was launched, there are some thought-provoking insights from former Google Reader engineers that reveal why the service has never been a priority for Google and why it can always be discontinued.

"In the beginning, the best word I can use is that Google tolerated the project. Then, they gave it — support is too strong a word. They gave it some thought," said Chris Wetherell, the Googler who started the project. Jenna Bilotta, a former user experience designer at Google, has a slightly different opinion: "Everyone from Google used Reader, from Larry and Sergey to the newest engineers. It's such a beloved project. Still, it was just in this limbo space. It wasn't really supported, but it wasn't actively being harmed."

The difficulty was that Reader users, while hyperengaged with the product, never snowballed into the tens or hundreds of millions. Brian Shih became the product manager for Reader in the fall of 2008. "If Reader were its own startup, it's the kind of company that Google would have bought. Because we were at Google, when you stack it up against some of these products, it's tiny and isn't worth the investment," he said. At one point, Shih remembers, engineers were pulled off Reader to work on OpenSocial, a "half-baked" development platform that never amounted to much. "There was always a political fight internally on keeping people staffed on this little project," he recalled. Someone hung a sign in the Reader offices that said "DAYS SINCE LAST THREAT OF CANCELLATION." The number was almost always zero. At the same time, user growth — while small next to Gmail's hundreds of millions — more than doubled under Shih's tenure. But the "senior types," as Bilotta remembers, "would look at absolute user numbers. They wouldn't look at market saturation. So Reader was constantly on the chopping block."

iGoogle, a much more popular service, will be discontinued next year and Google Reader's infrastructure is used to show feeds in iGoogle. Hopefully, Google Reader will still be available for some time, but it's mostly wishful thinking.

When Google Reader dropped support for the built-in sharing features and integrated with Google+, the settings page added a long list of JSON files you could save to your computer to export your followers, the items you've shared or starred, your notes and more. Until then, you could only export your subscriptions.


Now all these files can be downloaded from Google Takeout, a service that lets you export data from Google+, Google Drive, Google Contacts, Picasa Web, YouTube and more. Reader is probably the only Google service that sends users to Google Takeout to export data.


Unfortunately, you need to download 8 files even if you only want to export the subscriptions OPML file. Google has to create a ZIP archive first, so you'll have to wait a lot more. Instead of downloading a small XML file, you need to download a large archive (34MB for my account). That's a general issue with Google Takeout, which only lets you download all your YouTube videos, all your Picasa Web photos, all your Google Drive files.

Another service recently added to Takeout is Google Latitude. You can download a JSON file with your location history data.

Let's hope that developers will create cool apps that parse these JSON files and make them more useful. Maybe Google should also offer human-readable formats like HTML.

{ via Data Liberation Blog. Thanks, Herin. }

Google Reader's settings page has a new section where you'll find "experiments you can choose to opt-in and try out". It's like a small Google Reader Labs that only has a single experiment you can enable: smooth scrolling. This feature makes the transition between items smoother and it's especially useful in the expanded view.


While this feature is more difficult to find, you've probably noticed the colorful ball that's displayed when Google Reader loads new posts. The animation is one of the few colorful elements from the new Google Reader interface.


{ Thanks, Venkat. }

When Google Reader released the new interface, I complained that sharing a post takes too many clicks: you first need to +1 the post, then click the share box and finally click "share". Now it's easier to share a post: just click the new "share" button and click "share" once again in the modal dialog.



Another advantage is that you can use the old keyboard shortcut for sharing items: Shift+S. Unfortunately, you can't use keyboard shortcuts in the modal dialog, so you still need to click "Share".

Decoupling the "+1" button from the "share" button is a good idea and Google should adjust the code of the +1 widget to make this possible. "Liking" and "sharing" are two different actions and should be treated separately, especially considering that +1's are always public, while sharing can be limited to a few people or circles.

{ Thanks, Zachary and Herin. }

Brian Shih, a former Google Reader Product Manager, says that the latest Reader update is "a disaster". One of the reasons could be that most of the initial members of the Reader team left Google and the new team doesn't understand the goal of the product.

"It's as if whoever made the update did so without ever actually using the product to, you know, read something. Reader is a product built to consume information, quickly. We designed it to be very good at that one thing. G+ is an experience built around browsing (similar to Facebook) and socializing. Taking the UI paradigm for G+ and mashing it onto Reader without any apparent regard for the underlying function is awful and it shows," says Brian.

One of Brian's complaints is that it's a lot more difficult to share a post in the new interface. Instead of clicking "Share" or using a keyboard shortcut, you now have to click "+1", then click "Share on Google+", select your audience and then click the "Share" button. There's also a privacy downside: +1's are public, even if you only want to share a post with one or two people.

Fortunately, there's a way to share a post without first clicking +1, but it's not obvious. Just use the "share" box from Google's navigation bar.


{ via François }

The latest Google Reader update removed all the social features, including the section that allowed you to read the items you've shared. Fortunately, the shared items page is still available at http://www.google.com/reader/shared/username (replace username with your Gmail username) and you can subscribe to this page in Google Reader, but only if the page was public. Click "subscribe" and paste the URL of the shared items page. If you don't have a Gmail account, load the shared items feed in Reader, right-click "Your shared items" and copy the URL.


You can now use Google Reader's search box to find a post you've shared. Click the "All items" drop-down next to the search box, scroll down to the end of the list (or just press "End") and you'll find the shared items feed.

To unsubscribe from this feed, you need to go to the settings page, click "Subscriptions", type "shared items" in the search box and click the "unsubscribe button".

The new Google Reader interface is finally here and it also brings some functional changes: all the social features are removed and replaced by a Google +1 button. It's important to note that clicking the +1 button only adds the page to your Google Profile and you need to click the "share on Google+" box to share the page with your friends.

This means that the "share" and "like" buttons have been removed, you can no longer follow other Google Reader users and you can no longer read their shared items inside Google Reader. Folders and tags can no longer be public, the blogroll widget and the associated public page will stop being updated, while discussions are a thing of the past.



"When you find interesting items on Reader, you can choose to share them on Google+ publicly, or with a certain circles or friends. You can also add a comment in the sharebox to your shared items. Your comment will show up along with the item you've recommended in the streams of those you've shared with. Adding a note when sharing an item is a great way to let people know why you find a particular item interesting, relevant, or funny. To share an item with a note, just click the +1 button from underneath the item. You'll then be given the option to include any comments you might have in the Google+ share box. Your +1 will be public, but your notes in the share box will be only show up for circles and friends you've selected," explains Google.

What happened to all the posts you've shared or liked until today? You can export them from Reader's settings page, along with the items from people you follow, your discussions, your followers and the list of people you follow. Google offers two exporting options: JSON Activity Stream and a custom Google Reader JSON format, but they're not very useful without a software that parses them.

Unfortunately, all the items +1'd from Google Reader are treated like any other pages and there's no way to read the posts shared by your friends in Google Reader. In fact, there's no way to create a Google+ circle for the people you've followed in Google Reader. The new interface doesn't even offer keyboard shortcuts for sharing posts: Shift+s, Shift+d and "l" no longer work. The integration with Google+ is just an afterthought, instead of a proper replacement for Reader's sharing feature.

Update: Mihai Parparita, who worked on the Google Reader team, puts the changes into perspective and says that "Reader is on its fourth social model", after using Google Talk contacts, allowing you to manage your friends from the Reader interface and integrating with Google Buzz.