3 ms·
The problem with his example `retweet_count` is the blanket statement in the API: The timeline returned is the equivalent of the one seen when you view a u
by veyron 15y ago
The problem with his example `retweet_count` is the blanket statement in the API:
The timeline returned is the equivalent of the one seen when you view a user's profile on twitter.com.
Thus:
- the value is capped at 100 (since the retweet count is displayed up to 100)
- the value can be "100+" (https://twitter.com/#!/SEGA/status/144219968773423104 https://twitter.com/#!/SEGA/status/144219968773423104 says "Retweeted by ivucica and 100+ others")
Now, I don't disagree that the documentation should explain retweet_count more clearly, but I'm surprised that people trip up on this particular issue.
- nmcfarl 15y agoNow I don't use twitter's API, so I have no clue as to their conventions, but when I saw, in the documentation you qouted, the phrase the "equivalent of", I read this as the "raw data we used to produce" , and not the "exact string you see." Clearly I should have read it the other way - but I bet a lot of people will read it like I did.
- stilist 15y agoYou shouldn’t have to reverse-engineer a service to compensate for documentation gaps.