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
cialis alternatives tadalafil acquisto viagra livraison en heures kamagra consegna veloce comprar lovegra günstig kamagra viagra acquisto sicuro comprar levitra 10 mg acheter cialis france köpa viagra på apoteket livraison viagra suisse viagra venta en farmacias cialis que es viagra günstig bestellen cialis uden recept alternative viagra acquisto kamagra viagra rezeptfrei niederlande cialis vendita libera viagra se vende con receta forum viagra pour femme compra viagra madrid viagra 100mg hinta cialis mg generico kamagra receptfritt tabletten cialis köp viagra online viagras genericos baratas cialis im preisvergleich cialis generico on line

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 ?