achat de viagra acheter viagra internet viagra fabrique en inde commande levitra suisse kamagrajelly acheter viagra inde vente cialis europejours livraison prix viagra andorre prix levitra achat viagra 50mg telephone viagra pharmacie prix viagra thailande livraison rapide du cialis cialis générique 5mg levitra sur le net levitra sans ordonnance kamagra controindicazioni levitra farmacias del ahorro viagra på apoteket precio farmacia viagra cialis apotheke holland viagra cialis acheter pharmacie en ligne viagra kamagra quanto costa farmacia viagra apoteket levitra madrid cialis suomi viagra senza ricetta in farmacia viagra vendita on line cialis 5 mg effetti collaterali
pharmacie en ligne viagra levitra generico precio vente viagra en ligne comprar cialis online cialis piller generics online regalo viagra soft viagra online holland viagra kaufen at comprar kamagra costo viagra in italia viagra kaufen in wien cialis 10 mg españa levitra kaufen ohne rezept viagra aus indien gefährlich viagra mit rezept

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 ?