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 >
