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
