Twitter Account followers count mismatch

restapi

#1

When we get the followers count of particular twitter account, we got an invalid count in response.

Actual count: 40
In response: 37000

We tried yesterday, but today its coming as 40. Why this inconvenience? Please assist.

Response Header:

{date=[Wed, 27 Feb 2019 06:00:14 GMT], null=[HTTP/1.1 200 OK], server=[tsa_a], content-length=[3282], expires=[Tue, 31 Mar 1981 05:00:00 GMT], x-response-time=[47], x-frame-options=[SAMEORIGIN], x-rate-limit-reset=[1551247597], x-rate-limit-remaining=[898], x-rate-limit-limit=[900], x-transaction=[0014a08400ee7a7d], strict-transport-security=[max-age=631138519], pragma=[no-cache], set-cookie=[guest_id=v1%3A155124721419352617; Max-Age=63072000; Expires=Fri, 26 Feb 2021 06:00:14 GMT; Path=/; Domain=.twitter.com, lang=en; Path=/, personalization_id=“v1_H+H+hpjQrEppWI+WADYakA==”; Max-Age=63072000; Expires=Fri, 26 Feb 2021 06:00:14 GMT; Path=/; Domain=.twitter.com], last-modified=[Wed, 27 Feb 2019 06:00:14 GMT], x-xss-protection=[1; mode=block; report=https://twitter.com/i/xss_report], x-content-type-options=[nosniff], content-disposition=[attachment; filename=json.json], x-connection-hash=[547fd44b9222f485f864ec50af2e80b9], x-access-level=[read-write-directmessages], x-twitter-response-tags=[BouncerCompliant], content-type=[application/json;charset=utf-8], cache-control=[no-cache, no-store, must-revalidate, pre-check=0, post-check=0], status=[200 OK]}


#2

What account is it? that’s a big discrepancy


#3

https://twitter.com/ZohoPageSense


#4

Nothing looks odd to me there (i only looked at users/show and compared with web interface)


#5

Now its fine. But yesterday when I make a call I got different number. Thats why I provided the headers. Based on this Twitter team can check their logs or storage how it was.


#6

We’re not able to do that, or to comment on this. I suspect your call was probably just hitting a different datacenter with a cached or partially-sync’d set of data. In these kinds of scenarios things usually settle out on subsequent calls (as has happened here).


#7

Eventhough the request is cached, how this huge difference occurs?


#8

Could be a variety of reasons that are specific to our architecture, but I’d imagine probably synchronisation between backend datasets as a follower graph was mirrored.


closed #9

This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.