OK, that's likely another issue then -- there were some DNS changes today
and some servers/networks/JDKs/etc. are slow on the uptake.

Thanks!
Taylor

On Tue, Mar 1, 2011 at 1:57 PM, David <dtran...@gmail.com> wrote:

> Hi Taylor,
>
> Thanks for the heads-up - definitely remember reading that and just haven't
> looked at that part of the codebase in a while, but I've updated our oauth
> path.
>
> A few users are still reporting this timeout issue, but they also seem to
> be saying that twitter.com doesn't seem to be loading for them.
>
> David
>
> --
> 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

Reply via email to