• sildénafil citrate viagra-50 kamagra rezeptfrei comprar genericos viagra españa cialis svizzera achat levitra quebec sildenafil en pastillas para comprar cialis prezzo viagra 25 g indische viagra viagra naturale per donne pharmacie en ligne france viagra 50 mg preis cialis au meilleur prix tadalafil generico precio cialis generico españa
  • acheter cialis noir levitra générique forum viagra indio precios viagra cialis levitra viagra achat rapide comprare cialis cialis authentique cialis le moin cher compare viagra generico en españa viagra a basso costo cialis prezzo al pubblico tous les sites de vente pharmacie pour viagra en france sans risque acheter kamagra pharmacie viagra telefonisch bestellen viagra apoteket

    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 twittervision.com.

    • JeffClark

      Dave, I’m using the twittervision API for some projects that show up on http://neoformix.com . 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 ?