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

Twitter developer documentation and resources:
API updates via Twitter:
Issues/Enhancements Tracker:
Change your membership to this group:!forum/twitter-development-talk

Reply via email to