Re: [twitter-dev] Re: forcing api.twitter.com resources - tomorrow
hi all - just following up on this - i haven't seen any fallout from it, and i want to make sure that everything turned out ok. 2010/3/3 Raffi Krikorian ra...@twitter.com yes - you could just use api.twitter.com for oauth methods. we're working on getting those moved to the versioned endpoints as well, just FYI - so you may have to move them again to api.twitter.com/1 at some point. 2010/3/3 Caizer cai...@gmail.com Hmm.. I tested with oauth via both 'api.twitter.com' and 'twitter.com'. Both works well. And I can see the xauth uri has 'api.twitter.com' in front. Can I just change all those twitter.com to api.twitter.com? including oauth methods? It seems like api documentation for oauth method is not yet updated. On 3월3일, 오전11시09분, Raffi Krikorian ra...@twitter.com wrote: brian - this is exactly my understanding as well. we'll be putting a bunch more eyes on this. On Tue, Mar 2, 2010 at 3:51 PM, Brian Smith br...@briansmith.org wrote: Dewald Pretorius wrote: Raffi, There appears to be ground for confusion here. I'm sure some folks are still sending some API calls to twitter.com. Could you please put up a page that explains which calls *must* go to api.twitter.com, and after tomorrow won't work on twitter.com? And vice versa, which calls must go to twitter.com, and won't work on api.twitter.com. Here is my understanding: Right now, you might be able to access resources through api.twitter.comthat aren't part of the official public API. Starting tomorrow, api.twitter.com will only implement the official, public API. If you rely on resources that aren't in the official public API, and you are accessing them through api.twitter.com, your program will probably stop working tomorrow. If you are only using the published API through api.twitter.com, or you are accessing resources through the twitter.com domain, this change doesn't affect you (AFAICT), but, you should change your code to use http[s]://api.twitter.com/1/ instead of http[s]://twitter.com/ as the base URI at your earliest convenience, as Twitter said a few months ago. Since the OAuth resources are documented as being on twitter.com (not api.twitter.com), you should be accessing them through twitter.com(not api.twitter.com), even though you should be accessing the Twitter API through api.twitter.com. Correct? - Brian (@BRIAN_) -- Raffi Krikorian Twitter Platform Teamhttp://twitter.com/raffi -- Raffi Krikorian Twitter Platform Team http://twitter.com/raffi -- Raffi Krikorian Twitter Platform Team http://twitter.com/raffi
[twitter-dev] Re: forcing api.twitter.com resources - tomorrow
Hmm.. I tested with oauth via both 'api.twitter.com' and 'twitter.com'. Both works well. And I can see the xauth uri has 'api.twitter.com' in front. Can I just change all those twitter.com to api.twitter.com? including oauth methods? It seems like api documentation for oauth method is not yet updated. On 3월3일, 오전11시09분, Raffi Krikorian ra...@twitter.com wrote: brian - this is exactly my understanding as well. we'll be putting a bunch more eyes on this. On Tue, Mar 2, 2010 at 3:51 PM, Brian Smith br...@briansmith.org wrote: Dewald Pretorius wrote: Raffi, There appears to be ground for confusion here. I'm sure some folks are still sending some API calls to twitter.com. Could you please put up a page that explains which calls *must* go to api.twitter.com, and after tomorrow won't work on twitter.com? And vice versa, which calls must go to twitter.com, and won't work on api.twitter.com. Here is my understanding: Right now, you might be able to access resources through api.twitter.comthat aren't part of the official public API. Starting tomorrow, api.twitter.com will only implement the official, public API. If you rely on resources that aren't in the official public API, and you are accessing them through api.twitter.com, your program will probably stop working tomorrow. If you are only using the published API through api.twitter.com, or you are accessing resources through the twitter.com domain, this change doesn't affect you (AFAICT), but, you should change your code to use http[s]://api.twitter.com/1/ instead of http[s]://twitter.com/ as the base URI at your earliest convenience, as Twitter said a few months ago. Since the OAuth resources are documented as being on twitter.com (not api.twitter.com), you should be accessing them through twitter.com (not api.twitter.com), even though you should be accessing the Twitter API through api.twitter.com. Correct? - Brian (@BRIAN_) -- Raffi Krikorian Twitter Platform Teamhttp://twitter.com/raffi
Re: [twitter-dev] Re: forcing api.twitter.com resources - tomorrow
yes - you could just use api.twitter.com for oauth methods. we're working on getting those moved to the versioned endpoints as well, just FYI - so you may have to move them again to api.twitter.com/1 at some point. 2010/3/3 Caizer cai...@gmail.com Hmm.. I tested with oauth via both 'api.twitter.com' and 'twitter.com'. Both works well. And I can see the xauth uri has 'api.twitter.com' in front. Can I just change all those twitter.com to api.twitter.com? including oauth methods? It seems like api documentation for oauth method is not yet updated. On 3월3일, 오전11시09분, Raffi Krikorian ra...@twitter.com wrote: brian - this is exactly my understanding as well. we'll be putting a bunch more eyes on this. On Tue, Mar 2, 2010 at 3:51 PM, Brian Smith br...@briansmith.org wrote: Dewald Pretorius wrote: Raffi, There appears to be ground for confusion here. I'm sure some folks are still sending some API calls to twitter.com. Could you please put up a page that explains which calls *must* go to api.twitter.com, and after tomorrow won't work on twitter.com? And vice versa, which calls must go to twitter.com, and won't work on api.twitter.com. Here is my understanding: Right now, you might be able to access resources through api.twitter.comthat aren't part of the official public API. Starting tomorrow, api.twitter.com will only implement the official, public API. If you rely on resources that aren't in the official public API, and you are accessing them through api.twitter.com, your program will probably stop working tomorrow. If you are only using the published API through api.twitter.com, or you are accessing resources through the twitter.com domain, this change doesn't affect you (AFAICT), but, you should change your code to use http[s]://api.twitter.com/1/ instead of http[s]://twitter.com/ as the base URI at your earliest convenience, as Twitter said a few months ago. Since the OAuth resources are documented as being on twitter.com (not api.twitter.com), you should be accessing them through twitter.com(not api.twitter.com), even though you should be accessing the Twitter API through api.twitter.com. Correct? - Brian (@BRIAN_) -- Raffi Krikorian Twitter Platform Teamhttp://twitter.com/raffi -- Raffi Krikorian Twitter Platform Team http://twitter.com/raffi
Re: [twitter-dev] Re: forcing api.twitter.com resources - tomorrow
For the OAuth endpoints on api.twitter.com, was the sign off redirection bug [1] ever fixed? This was one issue keeping me from switching from twitter.com - api.twitter.com for the OAuth methods. Josh [1] http://code.google.com/p/twitter-api/issues/detail?id=1207 2010/3/3 Raffi Krikorian ra...@twitter.com yes - you could just use api.twitter.com for oauth methods. we're working on getting those moved to the versioned endpoints as well, just FYI - so you may have to move them again to api.twitter.com/1 at some point. 2010/3/3 Caizer cai...@gmail.com Hmm.. I tested with oauth via both 'api.twitter.com' and 'twitter.com'. Both works well. And I can see the xauth uri has 'api.twitter.com' in front. Can I just change all those twitter.com to api.twitter.com? including oauth methods? It seems like api documentation for oauth method is not yet updated. On 3월3일, 오전11시09분, Raffi Krikorian ra...@twitter.com wrote: brian - this is exactly my understanding as well. we'll be putting a bunch more eyes on this. On Tue, Mar 2, 2010 at 3:51 PM, Brian Smith br...@briansmith.org wrote: Dewald Pretorius wrote: Raffi, There appears to be ground for confusion here. I'm sure some folks are still sending some API calls to twitter.com. Could you please put up a page that explains which calls *must* go to api.twitter.com, and after tomorrow won't work on twitter.com? And vice versa, which calls must go to twitter.com, and won't work on api.twitter.com. Here is my understanding: Right now, you might be able to access resources through api.twitter.comthat aren't part of the official public API. Starting tomorrow, api.twitter.com will only implement the official, public API. If you rely on resources that aren't in the official public API, and you are accessing them through api.twitter.com, your program will probably stop working tomorrow. If you are only using the published API through api.twitter.com, or you are accessing resources through the twitter.com domain, this change doesn't affect you (AFAICT), but, you should change your code to use http[s]://api.twitter.com/1/ instead of http[s]://twitter.com/ as the base URI at your earliest convenience, as Twitter said a few months ago. Since the OAuth resources are documented as being on twitter.com (not api.twitter.com), you should be accessing them through twitter.com(not api.twitter.com), even though you should be accessing the Twitter API through api.twitter.com. Correct? - Brian (@BRIAN_) -- Raffi Krikorian Twitter Platform Teamhttp://twitter.com/raffi -- Raffi Krikorian Twitter Platform Team http://twitter.com/raffi
[twitter-dev] Re: forcing api.twitter.com resources - tomorrow
Raffi, Can you please clarify how and/or if OAuth will be affected. My OAuth token and authorize requests also go to twitter.com, not api.twitter.com. On Mar 2, 4:35 pm, Ryan Alford ryanalford...@gmail.com wrote: Does OAuth go to the api.twitter.com? The API documentation still has the 4 OAuth methods going to twitter.com. http://apiwiki.twitter.com/Twitter-REST-API-Method:-oauth-request_token http://apiwiki.twitter.com/Twitter-REST-API-Method:-oauth-request_tokenhttp://apiwiki.twitter.com/Twitter-REST-API-Method:-oauth-authorize http://apiwiki.twitter.com/Twitter-REST-API-Method:-oauth-authorizehttp://apiwiki.twitter.com/Twitter-REST-API-Method:-oauth-authenticate http://apiwiki.twitter.com/Twitter-REST-API-Method:-oauth-authenticatehttp://apiwiki.twitter.com/Twitter-REST-API-Method:-oauth-access_token http://apiwiki.twitter.com/Twitter-REST-API-Method:-oauth-access_tokenRyan On Tue, Mar 2, 2010 at 3:31 PM, Raffi Krikorian ra...@twitter.com wrote: hi all. tomorrow we're going to put an operational change in place that will force all traffic that is addressed tohttp://api.twitter.comto go to instances that are specifically serving api.twitter.com code. what does this mean for you? if you're only using documented api.twitter.com methods (and not calling any undocumented methods that have been designed to support twitter.com), then this means absolutely nothing to you :P just giving a heads up - we'll be actively monitoring the list and we'll try to be in IRC when it happens in case there are any hiccups. -- Raffi Krikorian Twitter Platform Team http://twitter.com/raffi
Re: [twitter-dev] Re: forcing api.twitter.com resources - tomorrow
anything going to twitter.com (and not api.twitter.com), will stick with twitter.com. On Tue, Mar 2, 2010 at 1:23 PM, Dewald Pretorius dewaldpub...@gmail.comwrote: Raffi, Can you please clarify how and/or if OAuth will be affected. My OAuth token and authorize requests also go to twitter.com, not api.twitter.com. On Mar 2, 4:35 pm, Ryan Alford ryanalford...@gmail.com wrote: Does OAuth go to the api.twitter.com? The API documentation still has the 4 OAuth methods going to twitter.com. http://apiwiki.twitter.com/Twitter-REST-API-Method:-oauth-request_token http://apiwiki.twitter.com/Twitter-REST-API-Method:-oauth-request_token http://apiwiki.twitter.com/Twitter-REST-API-Method:-oauth-authorize http://apiwiki.twitter.com/Twitter-REST-API-Method:-oauth-authorize http://apiwiki.twitter.com/Twitter-REST-API-Method:-oauth-authenticate http://apiwiki.twitter.com/Twitter-REST-API-Method:-oauth-authenticate http://apiwiki.twitter.com/Twitter-REST-API-Method:-oauth-access_token http://apiwiki.twitter.com/Twitter-REST-API-Method:-oauth-access_token Ryan On Tue, Mar 2, 2010 at 3:31 PM, Raffi Krikorian ra...@twitter.com wrote: hi all. tomorrow we're going to put an operational change in place that will force all traffic that is addressed tohttp://api.twitter.comto go to instances that are specifically serving api.twitter.com code. what does this mean for you? if you're only using documented api.twitter.com methods (and not calling any undocumented methods that have been designed to support twitter.com), then this means absolutely nothing to you :P just giving a heads up - we'll be actively monitoring the list and we'll try to be in IRC when it happens in case there are any hiccups. -- Raffi Krikorian Twitter Platform Team http://twitter.com/raffi -- Raffi Krikorian Twitter Platform Team http://twitter.com/raffi
Re: [twitter-dev] Re: forcing api.twitter.com resources - tomorrow
So the OAuth methods have not been moved to api.twitter.com? If not, then what is going to happen when those OAuth requests go to twitter.com? Are they going to be blocked? Ryan On Tue, Mar 2, 2010 at 5:03 PM, Raffi Krikorian ra...@twitter.com wrote: anything going to twitter.com (and not api.twitter.com), will stick with twitter.com. On Tue, Mar 2, 2010 at 1:23 PM, Dewald Pretorius dewaldpub...@gmail.comwrote: Raffi, Can you please clarify how and/or if OAuth will be affected. My OAuth token and authorize requests also go to twitter.com, not api.twitter.com. On Mar 2, 4:35 pm, Ryan Alford ryanalford...@gmail.com wrote: Does OAuth go to the api.twitter.com? The API documentation still has the 4 OAuth methods going to twitter.com. http://apiwiki.twitter.com/Twitter-REST-API-Method:-oauth-request_token http://apiwiki.twitter.com/Twitter-REST-API-Method:-oauth-request_token http://apiwiki.twitter.com/Twitter-REST-API-Method:-oauth-authorize http://apiwiki.twitter.com/Twitter-REST-API-Method:-oauth-authorize http://apiwiki.twitter.com/Twitter-REST-API-Method:-oauth-authenticate http://apiwiki.twitter.com/Twitter-REST-API-Method:-oauth-authenticate http://apiwiki.twitter.com/Twitter-REST-API-Method:-oauth-access_token http://apiwiki.twitter.com/Twitter-REST-API-Method:-oauth-access_token Ryan On Tue, Mar 2, 2010 at 3:31 PM, Raffi Krikorian ra...@twitter.com wrote: hi all. tomorrow we're going to put an operational change in place that will force all traffic that is addressed tohttp://api.twitter.comto go to instances that are specifically serving api.twitter.com code. what does this mean for you? if you're only using documented api.twitter.com methods (and not calling any undocumented methods that have been designed to support twitter.com), then this means absolutely nothing to you :P just giving a heads up - we'll be actively monitoring the list and we'll try to be in IRC when it happens in case there are any hiccups. -- Raffi Krikorian Twitter Platform Team http://twitter.com/raffi -- Raffi Krikorian Twitter Platform Team http://twitter.com/raffi
[twitter-dev] Re: forcing api.twitter.com resources - tomorrow
Raffi, There appears to be ground for confusion here. I'm sure some folks are still sending some API calls to twitter.com. Could you please put up a page that explains which calls *must* go to api.twitter.com, and after tomorrow won't work on twitter.com? And vice versa, which calls must go to twitter.com, and won't work on api.twitter.com. On Mar 2, 6:03 pm, Raffi Krikorian ra...@twitter.com wrote: anything going to twitter.com (and not api.twitter.com), will stick with twitter.com. On Tue, Mar 2, 2010 at 1:23 PM, Dewald Pretorius dewaldpub...@gmail.comwrote: Raffi, Can you please clarify how and/or if OAuth will be affected. My OAuth token and authorize requests also go to twitter.com, not api.twitter.com. On Mar 2, 4:35 pm, Ryan Alford ryanalford...@gmail.com wrote: Does OAuth go to the api.twitter.com? The API documentation still has the 4 OAuth methods going to twitter.com. http://apiwiki.twitter.com/Twitter-REST-API-Method:-oauth-request_token http://apiwiki.twitter.com/Twitter-REST-API-Method:-oauth-request_token http://apiwiki.twitter.com/Twitter-REST-API-Method:-oauth-authorize http://apiwiki.twitter.com/Twitter-REST-API-Method:-oauth-authorize http://apiwiki.twitter.com/Twitter-REST-API-Method:-oauth-authenticate http://apiwiki.twitter.com/Twitter-REST-API-Method:-oauth-authenticate http://apiwiki.twitter.com/Twitter-REST-API-Method:-oauth-access_token http://apiwiki.twitter.com/Twitter-REST-API-Method:-oauth-access_token Ryan On Tue, Mar 2, 2010 at 3:31 PM, Raffi Krikorian ra...@twitter.com wrote: hi all. tomorrow we're going to put an operational change in place that will force all traffic that is addressed tohttp://api.twitter.comtogo to instances that are specifically serving api.twitter.com code. what does this mean for you? if you're only using documented api.twitter.com methods (and not calling any undocumented methods that have been designed to support twitter.com), then this means absolutely nothing to you :P just giving a heads up - we'll be actively monitoring the list and we'll try to be in IRC when it happens in case there are any hiccups. -- Raffi Krikorian Twitter Platform Team http://twitter.com/raffi -- Raffi Krikorian Twitter Platform Teamhttp://twitter.com/raffi
Re: [twitter-dev] Re: forcing api.twitter.com resources - tomorrow
Dewald Pretorius wrote: Raffi, There appears to be ground for confusion here. I'm sure some folks are still sending some API calls to twitter.com. Could you please put up a page that explains which calls *must* go to api.twitter.com, and after tomorrow won't work on twitter.com? And vice versa, which calls must go to twitter.com, and won't work on api.twitter.com. Here is my understanding: Right now, you might be able to access resources through api.twitter.com that aren't part of the official public API. Starting tomorrow, api.twitter.com will only implement the official, public API. If you rely on resources that aren't in the official public API, and you are accessing them through api.twitter.com, your program will probably stop working tomorrow. If you are only using the published API through api.twitter.com, or you are accessing resources through the twitter.com domain, this change doesn't affect you (AFAICT), but, you should change your code to use http[s]://api.twitter.com/1/ instead of http[s]://twitter.com/ as the base URI at your earliest convenience, as Twitter said a few months ago. Since the OAuth resources are documented as being on twitter.com (not api.twitter.com), you should be accessing them through twitter.com (not api.twitter.com), even though you should be accessing the Twitter API through api.twitter.com. Correct? - Brian (@BRIAN_)
Re: [twitter-dev] Re: forcing api.twitter.com resources - tomorrow
On Tue, Mar 2, 2010 at 6:03 PM, Dewald Pretorius dewaldpub...@gmail.com wrote: There appears to be ground for confusion here. I'm sure some folks are still sending some API calls to twitter.com. I'm not even sure what Twitter is talking about. The initial post in this thread was completely vague. This is fairly troublesome, considering that: $ curl --location --referer ;auto -D - -s --netrc http://api.twitter.com/1/account/verify_credentials.xml; fails but $ curl --location --referer ;auto -D - -s --netrc http://twitter.com/account/verify_credentials.xml; works fine (as I mentioned earlier in another thread). I don't know why, but it's been doing it all day. I wonder how much other stuff is going to break tomorrow. TjL
Re: [twitter-dev] Re: forcing api.twitter.com resources - tomorrow
* TJ Luoma luo...@luomat.net [100302 15:58]: I'm not even sure what Twitter is talking about. The initial post in this thread was completely vague. This is fairly troublesome, considering that: $ curl --location --referer ;auto -D - -s --netrc http://api.twitter.com/1/account/verify_credentials.xml; fails but $ curl --location --referer ;auto -D - -s --netrc http://twitter.com/account/verify_credentials.xml; works fine (as I mentioned earlier in another thread). I don't know why, but it's been doing it all day. I wonder how much other stuff is going to break tomorrow. Both of those curl commands work for me. Perhaps you have a .netrc entry for twitter.com but not for api.twitter.com? @semifor
Re: [twitter-dev] Re: forcing api.twitter.com resources - tomorrow
On Tue, Mar 2, 2010 at 8:25 PM, Marc Mims marc.m...@gmail.com wrote: Both of those curl commands work for me. Perhaps you have a .netrc entry for twitter.com but not for api.twitter.com? Argh. I thought it would match *.twitter.com AND that curl would complain if I used --netrc but it didn't find a matching host :-/ Ok, so now I just need to know why Tweetie on the Mac and iPhone keep telling me that I'm using the wrong password when I know I'm not. TjL
Re: [twitter-dev] Re: forcing api.twitter.com resources - tomorrow
brian - this is exactly my understanding as well. we'll be putting a bunch more eyes on this. On Tue, Mar 2, 2010 at 3:51 PM, Brian Smith br...@briansmith.org wrote: Dewald Pretorius wrote: Raffi, There appears to be ground for confusion here. I'm sure some folks are still sending some API calls to twitter.com. Could you please put up a page that explains which calls *must* go to api.twitter.com, and after tomorrow won't work on twitter.com? And vice versa, which calls must go to twitter.com, and won't work on api.twitter.com. Here is my understanding: Right now, you might be able to access resources through api.twitter.comthat aren't part of the official public API. Starting tomorrow, api.twitter.com will only implement the official, public API. If you rely on resources that aren't in the official public API, and you are accessing them through api.twitter.com, your program will probably stop working tomorrow. If you are only using the published API through api.twitter.com, or you are accessing resources through the twitter.com domain, this change doesn't affect you (AFAICT), but, you should change your code to use http[s]://api.twitter.com/1/ instead of http[s]://twitter.com/ as the base URI at your earliest convenience, as Twitter said a few months ago. Since the OAuth resources are documented as being on twitter.com (not api.twitter.com), you should be accessing them through twitter.com (not api.twitter.com), even though you should be accessing the Twitter API through api.twitter.com. Correct? - Brian (@BRIAN_) -- Raffi Krikorian Twitter Platform Team http://twitter.com/raffi
