Hi, I'm glad you tried the api.twitter.com URI pattern as well -- as it's really the correct one.
It is unusual for this method to take that long. Have you tried this sequence outside of the code environment you're working in? Is there anything about your coding environment that may be mis-detecting the completion of the request? What kind of performance are you getting from other calls? Taylor On Tue, Dec 21, 2010 at 8:57 AM, Dave McCall <d...@dave-mccall.com> wrote: > FYI, I have tried the same using https://api.twitter.com as well. > Also in step 3 I have currently changed it to "https://api.twitter.com/ > oauth/authorize" because I believe that is the more correct URL > (though authenticate does appear to work). > > Any thoughts? > > -- > 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
