I have the same issue, After 'allow' it simply times out so no new
users can login to their new Twitter client.
On Aug 7, 3:07 am, hansamann <sven.hai...@googlemail.com> wrote:
> I experience the same, hope this is just the Twitter DOS attack
> aftermath. My app cannot request a requestToken for example, which
> results in a time out on my pages as this is the first thing you do
> before you redirect to twitter.
> Also, I cannot seem to get the friends timeline, friends and
> followers.... at least not regularly I believe.
> Anyone else?
> On Aug 6, 5:31 pm, Howard Siegel <hsie...@gmail.com> wrote:
> > If this has only been happening since this morning, then it is likely this
> > is just part of the aftermath of the DOS attack on Twitter.
> > - h
> > On Thu, Aug 6, 2009 at 15:53, yuf <kyl...@gmail.com> wrote:
> > > I have yet to get oAuth callbacks to work properly. After clicking
> > > Allow, I end up on a completely blank twittter.com/oauth/authorize
> > > page. If I try to look at the source, it asked if should resend. If
> > > I do, the source comes back that contains the redirect. But if I'm
> > > not looking at the source, the page just hangs for a while, and then
> > > ends up blank.
> > > What is up here? I've tried a variety of callback urls, from
> > > localhost, to the actual domain I'm using for development.
> > > Any one experience similar?