Thanks Tom, I have access to the source code of the parser, will
investigate.
On Dec 8, 11:00 am, Tom van der Woerdt i...@tvdw.eu wrote:
1. Please, when you think that the API is wrong, attach the JSON (or
XML) part and not the output from your application.
2. I assume that you are using a
I'd recommend using id_str instead of id, instead of looking into the
code of the parser. The parser itself is probably fine, while the
language (which in your case really looks like Objective-C) may have
problems with it. Compiling as a 64-bit application may help.
Tom
On 12/8/10 5:03 PM,
Actually, what is weird about these ids is that the url --
http://api.twitter.com/1/geo/id/31fe39275142e6fe.json -- which is
generated in the packet works.
This is why I thought the parser I use was fine.
Marc
On Dec 8, 11:00 am, Tom van der Woerdt i...@tvdw.eu wrote:
1. Please, when you
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
