I've checked what you said.
Your advice is really helpful to me.
Thank you very much.


On Dec 7, 12:10 pm, Tom van der Woerdt <i...@tvdw.eu> wrote:
> 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.
>
> Tom
>
> 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
> > one.
>
> > On Dec 7, 11:59 am, Tom van der Woerdt<i...@tvdw.eu>  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?
>
> >> Tom
>
> >> 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]http://twitter.com/#!/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]http://twitter.com/#!/HuffingtonPost/status/12226467568025601
>
> >>> How can I deal with this problem?
>
> >>> By the way, I'm curious if Twitter developers are aware of this severe
> >>> bug.

-- 
Twitter developer documentation and resources: http://dev.twitter.com/doc
API updates via Twitter: http://twitter.com/twitterapi
Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list
Change your membership to this group: 
http://groups.google.com/group/twitter-development-talk

Reply via email to