Google’s Leaked Video

September 12th, 2007 at 12:00 am

There was a video leaked from a Google team working ont he back end of Google reader.  Basically the video was a meeting of the team and they were discussing some points and plans for Google Reader.

The video was, however, removed quickly after but that didn’t stop bloggers with copies to report what they saw on it.  Fanboy from Google Blogoscoped posted these notes on the video, pretty much summarizing the whole secret meeting caught on tape. 


1. Google will work on a standard for feed publishers to tell aggegrators about changes in the feed (‘this post has been deleted’ etc.). Such a standard doesn’t exist yet. They will be working with blog tools like Blogger and MovableType.

2. 2/3 of the content has only one subscriber. Think about feeds for own-name-searches, own blogs and blog comments. There are feeds with up to tens of millions of subscribers. The crawl rate of feeds is prioritized when they’ve got more subscribers. They’re updated within one hour when there’s more than one subscriber, or else once in three hours.

3. The feed backend now contains 10 terabytes of raw data from 8 million feeds. The index size grows with 4% a week, but this number is probably not accurate.

4. Currently the standard distributed database called BigTable is mostly used. For search Mustang is currently used, Google’s library for creating search engines. Mustang underlies the web search and most other search engines, except for Gmail’s search feature as that requires instant updates and a specific index for each user. Mustang currently handles 1-2 search queries per second, but is able to handle thousands.

5. The Reader team is going to integrate more social features. Currently items can be sent to friends by email, and there are no plans for creating a Reader-inbox for that.

6. Google’s recent big social effort is called Mocha-Mocha (or Mocka-Mocka?), and will become the infrastructure for all social stuff across all of their applications. As a part of this, a new feature called Activity Streams will be introduced or at least implemented in Reader this quarter. This will be comparable to Facebook’s News Feed (Minifeed?) feature, and integrate Gmail’s addressbook and contact list.

7. Also there will be some other Gmail and Orkut integration, but this might just mean there will be links to Reader.

8. Google is interested in allowing users to comment on items they share, but this currently isn’t a priority.

9. Calling tags ‘labels’ is called ‘kind of a historic accident and needlessly confusing’.

10. When you press the ‘Mark all as read’ button, Google remembers that you’ve ‘read’ all items between two timestamps. You can never uncheck the ‘Mark as read’ checkbox for those items.

11. Currently there is no plan to integrate Reader with Universal Search. This is because Universal Search doesn’t provide its backends with user IDs (so Gmail results can’t be shown either), and because it requires a lookup time of less than 1/4 second, which Reader cannot provide yet.

12. When searching in Reader, you may also get results from before you aren’t subscribed to anymore, or from your friends’ items. This is intentional, but by some users considered as a bug.

13. Three people are working on Reader’s backend, and three plus one intern are working on the frontend.

14. Very soon, Reader will recommend feeds to the user, based on previous subscriptions and other Google activity.

15. Next week, Reader will be released in several languages. One month after that, it will be available in 40 languages.

16. According to FeedBurner statistics, Google Reader is the world’s largest full-content reader. My Yahoo is the largest headline reader, bug also iGoogle is big. As Google has grown into the market, the usage of Bloglines hasn’t really decreased much.

17. Reader has a loyal user base (based on pageviews per user), higher than any other product except for Gmail and Orkut. 70 % of the users use Firefox, so feed syndication is still mostly a geek thing.

18. Feeds are currently monetized by FeedBurner. Reader might be more directly monetized in the future, but Google wants to watch out showing ads next to other people’s content. This is a problem with Google News too. They might do something like they did with the non-free Opera: show the content owners’ ads in the interface when they’re AdSense publishers. Google wants to make publishing full articles in feeds more interesting to webmasters by creating ways to monetize them.

This was supposed to be confidential information but it really doesn’t matter now.  Most of these are already facts and there is no incarcerating information but it’s still great when the blogosphere gets some insider information from time to time.  I just hope the Noogle (Noogle= New Google employee) didn’t get fired.