It's also possible that whatever you're using to parse the resultant XML is greedily selecting any field that is labeled "id" -- if there is a place_id associated with the Tweet, it will be embedded in a deeper node of the status object. In fact, the string-based id you presented represents a location in Great Britain: ( GET http://api.twitter.com/1/geo/id/3a1d856bf1925a2e.json ). You might want to review how your XML parsing handles nested objects.
@episod <http://twitter.com/episod> - Taylor Singletary On Thu, Jun 2, 2011 at 6:44 AM, Scott Wilcox <sc...@dor.ky> wrote: > The parser you're using can't handle the 'snowflake' generated IDs, the > numbers are too huge for it. > > Use id_str instead. > > On 2 Jun 2011, at 13:47, gavinb wrote: > > > Hi all > > > > Was hoping to get a little help with a quick questions, if possible? > > > > I currently use statuses/home_timeline.xml to get the recent timeline > > (including retweets) of the signed in user, but I have a slight issue > > in that it returns tweet id's such as id = 3a1d856bf1925a2e; if the > > poster is using geo tagging. With these types of ID's i cant > > retweet. How can i get twitter api to return the normal format id's > > such as id = 76174785381535744; > > > > any help appreciated > > > > Gavin > > > > -- > Scott Wilcox > > @dordotky | sc...@dor.ky | http://dor.ky > +44 (0) 7538 842418 | +1 (646) 827-0580 > > > > -- > Twitter developer documentation and resources: https://dev.twitter.com/doc > API updates via Twitter: https://twitter.com/twitterapi > Issues/Enhancements Tracker: > https://code.google.com/p/twitter-api/issues/list > Change your membership to this group: > https://groups.google.com/forum/#!forum/twitter-development-talk > -- Twitter developer documentation and resources: https://dev.twitter.com/doc API updates via Twitter: https://twitter.com/twitterapi Issues/Enhancements Tracker: https://code.google.com/p/twitter-api/issues/list Change your membership to this group: https://groups.google.com/forum/#!forum/twitter-development-talk
