Skip to main content

Google Reader Limits

There is something strange going on with my Google Reader account. Hundreds of items on my subscribed feeds have been disappearing regularly. One day, I would have 700 unread items on a particular feed and the next day the number would drop to 500. I have two Google Reader accounts and I have observed this phenomenon happen on both, and this has been going around for quite a while. Today I decided to investigate and while searching for a solution/cause of the problem, I discovered, for the first time, the limits of Google Reader.

There are 3 limits on Google Reader:

  1. Unread items older than 30 days are automatically marked as read.
  2. Items older than 10,000 most recent items are automatically marked as read.
  3. You cannot subscribe to more than 2000 subscriptions per account.

The implications of these limits are - you ‘lose’ unread articles, starting from the oldest, if you haven’t read a subscribed feed in the last 30 days. Also, if you have a large number of subscriptions with very high volume of updates, you are going to periodically lose unread articles, even if you regularly read all your subscriptions.

google-reader-trends

To put it in simpler terms, Google doesn’t keep items older than 30 days or items more than 10,000 in your Reader account with the status as ‘Unread’. So if you go on a vacation, trusting Google to safely keep your unread items until you return, you will be very disappointed.

However, you will be relieved to learn that Google Reader doesn’t actually delete any items, they are simply marked as read and archived. The post will still be in the system and you can find it either through searching, or navigating through the feed itself.

Even so, you are still going to lose track of what you’ve actually read and what has been automatically marked as read by the machine.

Interestingly, there is no mention about these limitations anywhere on Google Reader’s support and help files. It’s only through questions from aggrieved users who have suddenly found thousands of unread items lost, that Google employees have acknowledged their existence, on their forums.

According to one Google employee, these limitations are necessary to keep large and active accounts from getting very expensive computationally. One workaround to the problem, he suggested, is to sort your feeds by oldest first and show all items (using the all/new items toggle at the top of the screen) to get at old unread items in the feed.

If you want to prevent this from happening to your account, here are some steps you can take:

  1. Avoid subscribing to very high volume feeds such as Twitter or Tumbler feeds.
  2. Use RSS feed filters such as Yahoo Pipes to filter out noise. ReadWriteWeb has listed some more RSS filters.
  3. If a high volume feed is really important to you, create another Google Reader account (on another Gmail ID) and subscribe through it, to avoid the high volume feed from cannibalizing on your more important subscriptions.
  4. Unsubscribe from feeds you don’t read.

Alternatively, you can dump Google Reader and build your own web-based reader.

Will Google relax the limits in future? Maybe, but only if large number of users voice their dissatisfaction or ask for it. At this moment, this isn’t happening. Heck, many people are not even aware of it. So it is unlikely that Google Reader’s limits are going to change at any time in the near future.

Limits on other products that you should know
- Gmail contact
- Picasa Web Albums
- Google search results
- Hotmail inbox

Sources: 1, 2, 3

Comments

  1. Thanks for this. I'm surprised more haven't commented. I've noticed that items older than the 10,000 most recent are not being marked read anymore. I haven't hit 20,000, so I don't know what the new limit is.

    ReplyDelete
  2. >"...The post will still be in the system and you can find it either through searching, ..."

    Nope, incorrect. Search only works for things posted within the LAST 1 YEAR. If it's older than a year, it won't show in a search.

    It's really weird to have these types of functionality missing, considering Google is a search engine company!

    ReplyDelete
  3. "Nope, incorrect. Search only works for things posted within the LAST 1 YEAR. If it's older than a year, it won't show in a search."

    I just tried this and you are incorrect sir.

    ReplyDelete

Post a Comment

Popular posts from this blog

How to Record CPU and Memory Usage Over Time in Windows?

Whenever the computer is lagging or some application is taking too long to respond, we usually fire up task manager and look under the Performance tab or under Processes to check on processor utilization or the amount of free memory available. The task manager is ideal for real-time analysis of CPU and memory utilization. It even displays a short history of CPU utilization in the form of a graph. You get a small time-window, about 30 seconds or so, depending on how large the viewing area is.

How to Schedule Changes to Your Facebook Page Cover Photo

Facebook’s current layout, the so called Timeline, features a prominent, large cover photo that some people are using in a lot of different creative ways. Timeline is also available for Facebook Pages that people can use to promote their website or business or event. Although you can change the cover photo as often as you like, it’s meant to be static – something which you design and leave it for at least a few weeks or months like a redesigned website. However, there are times when you may want to change the cover photo frequently and periodically to match event dates or some special promotion that you are running or plan to run. So, here is how you can do that.

Diagram 101: Different Types of Diagrams and When To Use Them

Diagrams are a great way to visualize information and convey meaning. The problem is that there’s too many different types of diagrams, so it can be hard to know which ones you should use in any given situation. To help you out, we’ve created this diagram that lays out the 7 most common types of diagrams and when they’re best used: