The attitude of Inoreader

This is my question for first time:

Hello,I’m a plus user in Inoreader,there’re some strange siuation happened in my account.

I havn’t mark any article as read for some specific feeds,but it looks like it will mark itself as read automatically if I don’t read for a period of time.It happens many times.

I don’t know whether it was the system automatism or the bug.

It bring me a lot of trouble.It was so annoying for me.

Besides,I have checked the rules setting that I havn’t set the “automatically mark as read” rule.

Please help me to solve the problem,thanks.

Then,Inoreader replys:

It’s a system automation process.
There is no limit for the amount of unread articles.
But articles older than a month are automatically considered as read. Most probably you hit this limitation for the provided feed.
Also, keep unread and mark above/below as read is not shown (not available) when you use “mark all as read”.
The 30-days limit is imposed by our database architecture because of the huge amount of user flags we need to store. It was the same in Google Reader and I am sure that even Google struggled with the same issue. All of this is needed because we are committed to keeping articles forever. We have billions in our databases and the only way to support this huge amount of data without tearing the platform apart is to have some limitations like this in place.
For such cases, we can suggest you to use the “send to” features (evernote, pocket, etc); use tags or the power of Rules where easily can make automation process with many actions like send to Evernote for example.

We hope you understand.


In fact,I was a lot unhappy for his first relpy because of the attitude that he show up in it,so I reply that:

I know this is the common situation in the industry.

However,you can’t deny that this demand is a objective reality,and I thought that it will be not humanized.
If you can take this demand as the professional(or higher) featrue,I think many people with big reading amount will buy it without any hesitation.
In other way,the two solutions you offered won’t wok for me:
1.These app or software(pocket or evernote) just be the storage for me,not the reading solution.If I take all the unread articles sending to these app,what is the reason for me to still use Inoreader?
2.Your rules are not strong enough for me,if you can’t did the  premium feature,I may can set the rule like this:
If the unread article was older than 29 days,then the system will send it to other apps or set them unread automatically.
 It’s a pity that your condition isn’t support the date setting,if it can,it can sovle the problem for a certain extent.
Hope you can do better.

However,I changed my mind after reading this reply:


Yes, we understand your point of view and there are many similar threads in our forum or here in our feedback form.

The thing is that we don’t just run a script that adds some read flags after 30 days, because we think it’s cool. It’s completely different story.

Behind Inoreader there is an ecosystem with 20 huge servers, more than half of them are databases. We currently have more than 6 billion articles and hundreds of thousands of active users, all of them reading, clicking, tagging, etc.. It’s a long long story.

One of the key factors because of which this system is ticking smoothly is the fact that we have vertical and horizontal sharding of the database. The vertical one is what’s imposing this 30-day limit. Only the first vertical shard of databases holds user information such as read flags. After this period articles are being pushed below and we simply cannot have flags there. We have made exceptions to stars, tags and broadcasts, but it’s not possible with unread flags. The solution to this problem is to use stars and tags – stars to quickly mark articles of interest and then tag and unstar them when you have more time.

I know it’s not solution that covers 100% of the use cases, but it’s something we can’t change at this point and I don’t think we will ever change it. Last year we had some pretty nasty periods when the service was in agony and was just about to collapse and this was one of the (if not THE) most important changes we made to stabilize it. More than a year has passed since then and we haven’t had a single database hiccup ever since. Of course we are keeping in mind similar feedback for the future but is not such easy as we want to be. We completely understand the benefit from such Premium option, but as I said it’s not such easy for implementation regarding to the financial and the intellectual part.

I hope you understand and find an easy way to keep your older articles available using our service until we find a solution for this. As you said we may add date factor to the rules or something else which will ease this process.




He didn’t escape from my question,he faced it and reply my very professional.

Thinking of my attitude when facing customer’s demands sometime,maybe what I did wasn’t enough,there’re many points that I have to learn.

Inoreader have did these things right:

  • Understand my demands and find some probable solution.
  • Explain the true siuation not escaping.
  • If the probable solution had been denied or unsatisfied,just analyse that what is user truely needed.
  • If customer raise some useful advice(truely),answer that it will probably be considered,which will made customer felt valued


Hope you do better,Inoreader,I will introduce you to my every friends:)


电子邮件地址不会被公开。 必填项已用*标注