Re: [twitter-dev] Getting Started
Does anyone have a working example of using the jtwitter library using callbacks? -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk
[twitter-dev] Getting Started
Hello, I am just getting started developing some proofs-of-concept for my company. One major snag is that I am of course behind a firewall. The OAuth API expects a URL that is available to twitter.com. I can't really do much more unless I start opening some ports (frowned upon). What solutions have other developers in the same position used? I also would like to avoid any user interaction with twitter (should be completely opaque). From reading the documentation it would appear that the XAuth is better suited to my use case. What experience have people had with this? Thanks for your time... -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk
Re: [twitter-dev] Getting Started
Hi Dan, Twitter actually doesn't need to be able to access your callback URL -- the web browser executing the callback does though. On your application record, just use a placeholder for the callback URL field (like your business's public-facing web site). On the request token step of OAuth, dynamically supply an oauth_callback pointing to the URL behind your firewall. Once the user authorizes, they'll be redirected to your URL as long as it's accessible for them. Thanks, Taylor @episod http://twitter.com/episod - Taylor Singletary - Twitter Developer Advocate On Wed, Feb 16, 2011 at 1:34 PM, Dan dro...@gmail.com wrote: Hello, I am just getting started developing some proofs-of-concept for my company. One major snag is that I am of course behind a firewall. The OAuth API expects a URL that is available to twitter.com. I can't really do much more unless I start opening some ports (frowned upon). What solutions have other developers in the same position used? I also would like to avoid any user interaction with twitter (should be completely opaque). From reading the documentation it would appear that the XAuth is better suited to my use case. What experience have people had with this? Thanks for your time... -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk
[twitter-dev] Getting Started...
Hello, I'm trying to migrate my code across to using oAuth, and there is no class for oAuth in the language I use, so I'm having to drop in at the deep end. At the moment, I am a bit stuck, I keep getting a 401 when I request a token. I have created this as my signature base string: POSThttps%3A%2F%2Fapi.twitter.com%2Foauth%2Frequest_tokenoauth_callback%3Doob%26oauth_consumer_key%3DAXpCOWR4c2IZVlSGNXvdZg%26auth_nonce%3DQP70eNmVz8jvdPevU3oJD2AfF7R7odC2XJcn4XlZJqk%26auth_signature_method%3DHMAC-SHA1%26auth_timestamp%3D1280511571%26auth_version%3D1.0 Created a signed hash of this, using my Consumer Secret Base-64 encoded the hash since it was non-unicode URL Encoded the Base-64 string which then gives me: oAuth oauth_nonce=QP70eNmVz8jvdPevU3oJD2AfF7R7odC2XJcn4XlZJqk, oauth_callback=oob, oauth_signature_method=HMAC-SHA1, oauth_timestamp=1280511571, oauth_consumer_key=AXpCOWR4c2IZVlSGNXvdZg, oauth_signature=4zCns2DZTQzmo2HpYY99dhJVl5A%3D, oauth_version=1.0 But when I make the POST request with the above set, I still get a 401 Unauthorised. Could someone steer me in the right direction please? Thanks :) Andy
[twitter-dev] Getting started with a twitter application
Hi everybody! I am about to develop a twitter application and I am stuck with starting the development of the application.How should I connect my application with a twitter api?
