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
> 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
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
> ye
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
> Hmm.. I tested with oauth via both 'api.twitter.com' and
> 'tw
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 upda
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 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
On Tue, Mar 2, 2010 at 8:25 PM, Marc Mims 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 hos
* TJ Luoma [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.x
On Tue, Mar 2, 2010 at 6:03 PM, Dewald Pretorius 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 tr
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,
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 tw
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 wrote:
> anything going to twitter.com (and not api.twitter.com), w
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 wrote:
> 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.twitt
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 wrote:
> Does OAuth go to the api.twitter.com? The API documentation still has the 4
> OAuth methods going to tw
13 matches
Mail list logo
