My scenario is that we are opening that authorization page in a popup window
via `window.open()`. When the user clicks Allow, the popup window is
redirected back to our server, and a page is returned that notified the
opening page (the main window) that authorization is complete, and closes
the
Interesting... your example does indeed work as expected! I suppose there
must be some difference between that and what I am already doing. Thanks for
the example, hopefully it will help me drill down the problem!
On Mon, Aug 1, 2011 at 12:29 PM, Ciaran ciar...@gmail.com wrote:
Hi Nathan
For anybody whose interested, the problem turned out to be that I was
prefixing Twitter's OAuth URLs with 'www.'. After removing the prefix,
and having the urls be top-level, everything is working as expected.
On Aug 1, 2:04 pm, Nathan Rajlich nat...@tootallnate.net wrote:
Interesting... your
Hello all. I am using nodejs, and specifically ciranj's node-oauth[0]
module, attempting to override the default callback URL with an
explicit one as per the 1.0A specification changes. I'm not entirely
sure if it's a bug with the module or just me being dumb, but after I
changing the code from:
would make a lot of sense that you should be able to new
RequestToken using a string, or something like that.
Thanks
Nathan
hi
i have created 2 twitter in gmail account and yahoo account but
i need same user name wat can i do. how it save same user name.
Cheers,
Eric
I am new to twitter and OAuth.
I've decided to try Twitter4J. They have good examples on their
website but it's mostly oriented toward Desktop/Mobile apps.
I'm building a web app, and I'm still not confident about the OAuth
process.
Are there good examples anywhere?
I think I'm supposed to do
be better to wait on that until the interface is more
complete and I have a documentation page just for that Dispatch
module. Or maybe it's better to have a link up so people can figure
out what they can figure out; whatever you guys think is best!
Nathan
