[twitter-dev] Re: More OAuth Changes from Yesterday's Mega-Deploy

2009-04-09 Thread Chad Etzel
Hi Matt, Unfortunately I don't have time right now to throw together a sample app to test this, so I'll ask you :) Do these new parameters play nice with possibly pre-existing parameters in the callback? i.e. if callback is http://foo.com/bar/baz.html then the re-direct will actually call http:

[twitter-dev] Re: More OAuth Changes from Yesterday's Mega-Deploy

2009-04-09 Thread Matt Sanford
Hi Chad, They should, yes. I did not test what will happen if you already have a user_id or screen_name parameter but based on the logic it should add a second one. For an example of what they look like where there are no other parameters take a gander at the return page on Abraham's

[twitter-dev] Re: More OAuth Changes from Yesterday's Mega-Deploy

2009-04-09 Thread Abraham Williams
If you include user_id or screen_name in you authorize url they will be replaced on callback. On Thu, Apr 9, 2009 at 12:27, Matt Sanford wrote: > Hi Chad, > They should, yes. I did not test what will happen if you already have a > user_id or screen_name parameter but based on the logic it sh