I do hope you'll continue to use @twitterapi and give us fair warning there. While appreciate the google groups as a resource, I am concerned it's not the best means of communicating breaking API changes to the large number of third-party developers out there.
Thank you for your help. On Dec 11, 10:40 am, Matt Sanford <[EMAIL PROTECTED]> wrote: > Hi Jake, > > For only change announcements and things form the API team check > out the twitter users @twitterapi (http://twitter.com/twitterapi). > We've had it for some time but just started making updates to it a > priority. You may also want to follow @twitter for outage announcements. > > Thanks; > — Matt Sanford > > On Dec 11, 2008, at 08:32 AM, JakeS wrote: > > > > > Really, I don't get emails from this group because it's often full of > > people's questions that do not relate to me. > > > Is there a better way we can be notified of API changes without all > > the extra conversation from the group? > > > On Dec 11, 10:30 am, Stut <[EMAIL PROTECTED]> wrote: > >> On 11 Dec 2008, at 16:20, JakeS wrote: > > >>> It used to be that > >>> callinghttp://twitter.com/account/verify_credentials.xml > >>> would return a simple "<authorized>true</authorized>" answer when > >>> given a correct username and password. Now it appears to be > >>> returning an entire serialized user object. > > >>> This change has broken the authentication process for the existing > >>> releases of my application. Is this change permanent, or is it a > >>> temporary glitch? > > >> Plenty of notice was given for this change... > > >>http://groups.google.com/group/twitter-development-talk/ > >> browse_thread... > > >> -Stut > > >> --http://stut.net/
