[twitter-dev] Weird hex/alphanumeric ids for retweets?

2010-12-08 Thread Marc Provost
Hi everyone, I have a problem that puzzles me: I get ids back from twitter which are in an alphanumeric/hex format, for instance take a look at the tweet packet at the bottom of this message. The id 31fe39275142e6fe is completely different from the format I'm used to, e.g. 11897582800343040.

[twitter-dev] Re: Weird hex/alphanumeric ids for retweets?

2010-12-08 Thread Marc Provost
        id_str = 12413709859164160 id will be parsed as a number, id_str as a string. Just to clarify: This is *not* an API bug, it's a bug in your parser. Tom On 12/8/10 4:49 PM, Marc Provost wrote: Hi everyone, I have a problem that puzzles me: I get ids back from twitter which

[twitter-dev] Re: Weird hex/alphanumeric ids for retweets?

2010-12-08 Thread Marc Provost
/10 4:49 PM, Marc Provost wrote: Hi everyone, I have a problem that puzzles me: I get ids back from twitter which are in an alphanumeric/hex format, for instance take a look at the tweet packet at the bottom of this message.  The id 31fe39275142e6fe is completely different from

[twitter-dev] Re: Weird hex/alphanumeric ids for retweets?

2010-12-08 Thread Marc Provost
Thanks Tom, it was a bug with the parser I use (MGTwitterEngine), which overode the tweet id with the place id if it was present. Marc On Dec 8, 11:05 am, Marc Provost mprov...@gmail.com wrote: Actually, what is weird about these ids is that the url --http://api.twitter.com/1/geo/id