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 to http://api.twitter.com to 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 >
