Re: verify_credentials response changed
I'll be following the @twitterapi bot from now on. This took me by surprise. 8 days notice is not a lot of time for everyone. Considering development, testing, and release cycles, even a small change can take longer than 8 days for larger applications.
verify_credentials response changed
It used to be that calling http://twitter.com/account/verify_credentials.xml would return a simple authorizedtrue/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?
Re: verify_credentials response changed
Permanent. See posts on the list about a week ago, and issue in tracker. -- Ed Finkler http://funkatron.com AIM: funka7ron ICQ: 3922133 Skype: funka7ron On Dec 11, 11:20 am, JakeS [EMAIL PROTECTED] wrote: It used to be that callinghttp://twitter.com/account/verify_credentials.xml would return a simple authorizedtrue/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?
Re: verify_credentials response changed
On 11 Dec 2008, at 16:20, JakeS wrote: It used to be that calling http://twitter.com/account/verify_credentials.xml would return a simple authorizedtrue/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/thread/fd3a63597f6d0d3c -Stut -- http://stut.net/
Re: verify_credentials response changed
On 11 Dec 2008, at 16:32, 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? I believe API changes will be announced by @twitterapi but I dunno if they'll be mentioned with any meaningful notice period there. Your best bet is to get a daily digest of the emails to this list and scan through them every day. -Stut -- http://stut.net/ 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 authorizedtrue/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/
Re: verify_credentials response changed
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 authorizedtrue/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/
Re: verify_credentials response changed
We'll try to find other avenues for communicating these changes. On Thu, Dec 11, 2008 at 08:47, JakeS [EMAIL PROTECTED] wrote: 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 authorizedtrue/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/ -- Alex Payne - API Lead, Twitter, Inc. http://twitter.com/al3x
Re: verify_credentials response changed
yes, follow the api bot @twitterapi On Dec 11, 9:32 pm, JakeS jakesteven...@gmail.com 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 stut...@gmail.com 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 authorizedtrue/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/