This is happening RIGHT NOW for the following:
1) Go to
search.twitter.com and enter "tweetsforboobs OR
tweetforboobs" as the search.
2) Go to
http://tweetsforboobs.org and see the twitter feed on the
left.
Notice that the last tweet from 2 hours ago (VerticalMeasures) is not
in the twitter feed on
tweetsforboobs.org. Also note the ID of the
tweet - from VerticalMeasures that is missing from
tweetsforboobs.org:
5181937429
Now here is the log file of the Twitter API call:
DEBUG: 06:18:01 PM on Mon October 26th Doing CURL fetch with User
DEBUG: 06:18:01 PM on Mon October 26th Twitter responded with 200 HTTP
Status Code.
DEBUG: 06:18:01 PM on Mon October 26th MaxID:
5182676703
DEBUG: 06:18:01 PM on Mon October 26th There are: 0 results in this
fetch.
Updating number for api hits for hour: 18 to: 6
THROTTLE-69: 06:18:01 PM on Mon October 26th Slowing collection...
Avg: 0 returning delay: 180
DEBUG: 06:18:01 PM on Mon October 26th Checking for next page... ****
DEBUG: 06:18:01 PM on Mon October 26th There is NOT another page of
results...
DEBUG: 06:18:01 PM on Mon October 26th Old max:
5182676703 New max:
5182676703
DEBUG: 06:18:01 PM on Mon October 26th Old max:
5182676703 New max:
5182676703
Note that our id is already > the last tweet ID from VerticalMeasures,
yet we never got that tweet. Our id from the log snip:
(5182676703) is
NOT in our database (we never got it). It does not match the tweet ID
before Vertical Measures: 5180513610
Somehow the API is returning a new (and bigger) max id on 200
responses with no tweets in them OR on 403 (those are the only two
http codes in the log for today). Either way, that shouldn't be
happening.
Brian Roy
justSignal