thanks matt I didn't think of verifying the source straight from the json api, you're perfectly right, this is super helpful.
and it appears that twitter4j has some funny behaviour, as I'm reading the geo location directly from the API when I receive an onStatus notification, hence something like status.geoLocation() I will need to dig in the code to understand what's happening, I'll come back to you as soon as I have answers many thanks again, have a good day thomas -- 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
