That makes sense. In the mean time, can you give us some kind of heads up (ideally a couple days warning or something) if you are planning to make a change that could, as soon as it goes live, break an app? So we can try to be ready for it when you flip the switch :)
Thanks. Appreciate all that you're doing. Alex On Dec 11, 3:34 pm, "Alex Payne" <[email protected]> wrote: > Versioning is a major part of the design of the next version of the > Twitter API (a rewrite, essentially). We know it's been long since > missing from the API, and we're eager to fix that. Making life hard > for developers definitely isn't our goal. > > On Thu, Dec 11, 2008 at 12:05, Alex <[email protected]> wrote: > > > The Twitter ecosystem has grown quite a bit, and a lot of users are > > relying on the API (and third party software) nowadays. > > > Small API changes can break these applications, and could possibly > > affect thousands of Twitter users. > > > I understand that the API will need to evolve - but can you please > > consider a versioning policy similar to: > >http://www.google.com/support/adwordsapi/bin/answer.py?answer=33152&t... > > > Thanks. > > -- > Alex Payne - API Lead, Twitter, Inc.http://twitter.com/al3x
