Is there any possibility of a test site, with these API response changes, being made available before the changes are introduced to the real site?
This would allow us to test our sites and applications against the test site and fix any bugs and bombs before users would otherwise experience them when the changes go live on the real site. My code is written very defensively and is generally OK with things like this, but the only real way to know for sure is to test it. This kind of testing is better done in a controlled environment than in the real live environment. It is not necessary that the test site accept geolocation updates, only that it return <status> elements with <geo> sub-elements, <user> elements with <geo_enabled> sub-elements, etc. The test site could even have a very small user database, it wouldn't need the entire live twitter database. Not would it need to support API requests that are POSTs, only GETs. Even if the test site is only available as little as 1 or 2 days before the real site goes live, given reasonable advance notice (1 week?) as to when the test site will be available, this could greatly smooth out the introduction of this really cool feature for all of us: twitter, twitter partners, and twitter users. Anything that could be done here would be greatly appreciated by me, and I believe the whole twitter development community. Comments expected and welcome. Jim Renkel On Aug 21, 11:25 pm, Raffi Krikorian <ra...@twitter.com> wrote: > Hi Damon. > > Yup - we've started updating the docs. > > Generally, there will always be a <geo> in the <status> (it may just > be empty, however, if there is no geolocated information attached), > and there will always be a <geo_enabled> on every <user> which is a > boolean representing whether the user has enabledgeolocationon his > or her account. > > On Aug 21, 2009, at 6:46 PM, Damon Clinkscales <sca...@pobox.com> wrote: > > > > > On Aug 20, 3:46 pm, Ryan Sarver <rsar...@twitter.com> wrote: > >> We wanted to give you all a heads up on a cool new feature that is > >> coming > >> soon -Geolocation. > >> We have also updated the wiki to reflect what theAPIwill look > >> like when it > >> launches, so check it out and let us know if you have any > >> questions:http://apiwiki.twitter.com/Twitter-REST-API-Method%3A- > >> statuses%C2%A0u...http://apiwiki.twitter.com/Twitter-REST-API-Method%3A-account%C2%A0ve > >> ... > > > Ryan, > > > Very cool stuff. Looking forward to it. > > > I'm assuming that you'll update the wiki (andAPIwhen it launches) > > such that > > everywhere a <status> element is returned, it will contain a <geo> > > element? > > > Thanks, > > -damon
