max_id_str and max_id differs in search_metadata of search/tweets.json


#1

It seems, like max_id is truncated, because it differs to max_id_str.

Could that be? Should I always use max_id_str?

"search_metadata": { "completed_in": 0.03, "max_id": 466154692679307260, "max_id_str": "466154692679307265", "query": "%23bluehawks", "refresh_url": "?since_id=466154692679307265&q=%23bluehawks&include_entities=1", "count": 10, "since_id": 0, "since_id_str": "0" }

#2

This happens with JavaScript as it exceeds 32bit integers. Use max_id_str.