No, the tweets are fine.

ActionScript (and any other ECMAScript language) can't handle numbers larger than 53 bits. In a few days you'll see that the numbers will be wrong twice as much. A few weeks later this will duplicate again, and again, and again.

To solve this issue, a _str field (id_str, etc) was introduced for ECMAScript-based languages.

It's not your implementation, it's the language. :-)

Please use id_str instead of id.


On 12/7/10 9:08 PM, noriguard wrote:
Yes, I think the implementation is correct, and I use ActionScript.

Many of tweets are having correct ID, but some tweets are having wrong

On Dec 7, 11:59 am, Tom van der Woerdt<>  wrote:
Are you sure that your implementation is correct? It really sounds like
an issue with processing larger numbers. Are you using JavaScript,
ActionScript, or any other ECMAScript language?


On 12/7/10 8:48 PM, noriguard wrote:

During last several days, I've found that Twitter API frequently gives
wrong information, especially tweet ID.

For example, API send to me the tweet ID '12226467568025600' of
HuffingtonPost, the tweet URL is therefore following:

* [wrong]!/HuffingtonPost/status/12226467568025600

However, you can notice that it is actually not from HunffingtonPost
but from other guy.

The correct tweet ID must be 12226467568025601 (wrong ID plus one).

* [correct]!/HuffingtonPost/status/12226467568025601

How can I deal with this problem?

By the way, I'm curious if Twitter developers are aware of this severe

Twitter developer documentation and resources:
API updates via Twitter:
Issues/Enhancements Tracker:
Change your membership to this group:

Reply via email to