It's both. We're continuously improving our caching architecture and backing store systems and improved consistency is a direct result. Consistency is many orders of magnitude better now than just six months ago. An incorrect count shouldn't happen. It's almost certainly either a known issue.
-John Kalucki http://twitter.com/jkalucki Services, Twitter Inc. On Fri, Dec 11, 2009 at 8:50 AM, tobi <interf...@p3k.org> wrote: > Hi John > > > Probably some cache inconsistency on our end. > > Does that mean something like “Sorry, that is the way Twitter is doing > its cache thing, we all have to live with it” or rather that this > issue could be in fact solved somehow on your end? > > Should I file a report on Google Code? > > Regards, > tobi >
