download acdsee 10 license code cost of server 2008 enterprise cheap microsoft office 2007 home
cheap 2003 server license price of ms visio 2010 buy acronis true image home 2010 australia tadalafil once daily sildenafil powder viagra wholesale price
vardenafil 20mg tab professional cialis online generic viagra capsules
best price adobe acrobat xi pro upgrade purchase windows 7 cd key download 2010 microsoft word office adobe acrobat x pro for mac download purchase word 2007 online
download rosetta stone spanish mac adobe bridge cs5 download mac
  • cheap office outlook 2007 windows 7 price sydney lightroom price
  • Twittervision API Changes

    When we first launched Twittervision in early 2007, Twitter was still a pretty small community of users (around 200,000) and only the press and the digerati were paying much attention to it.

    Today, with just over 1M users, Twitter is still pretty small by Internet standards, but a lot of people are paying attention to it.

    Our API was designed to allow individual users to use the Twittervision location features. A lot of people are using it. We also had a fair number of people who were using our API as an alternative to the Twitter API and trying to harvest vast amount of data using our free API.

    Sadly, this was restricting service to others, so we are making some changes to the API that make this kind of use no longer possible. Those of you using the API for your individual projects or in support of client-side apps will see no changes for now — keep doing what you’re doing.

    We do sometimes engage in licensing agreements, however, so if you are interested in licensing our data, please contact me at dave at

    • JeffClark

      Dave, I’m using the twittervision API for some projects that show up on . First of all, thanks for providing it ! Secondly, I haven’t found anywhere in your documentation what the suggested or enforced rate limit is for queries. I’m doing ‘current_status’ type queries. What would you suggest as a reasonable upper bound ?