[twitter-dev] Re: This account is locked due to too many failed login attempts. Try again in X seconds.
You are a rock star.
I took out the authentication for that call. It was only supposed to
auth when the user logs in, for calls using their UN and PW.
Thank you Mark
-Joe
On Apr 21, 7:48 pm, Mark McBride wrote:
> My guess is this block
>
> if($auth)
> {
> curl_setopt($ch, CURLOPT_USERPWD, "{$this->_authUsername}:
> {$this->_authPassword}");
> }
>
> Is setting the wrong username/password, and you've locked out that
> account. Prior to yesterday's patch this call would succeed, but you
> would have left a potentially unhappy user with a locked out account.
> Now we tell you you've locked it. Note that the endpoint you're
> accessing doesn't require access, so you can eliminate the auth
> setting if you want.
>
>---Mark
>
> http://twitter.com/mccv
>
> On Wed, Apr 21, 2010 at 6:05 PM, Joe Taylor wrote:
> > I'm sorry for my ignorance, but I'm think this is what you are asking
> > for.
>
> >http://twitter.com/statuses/user_timeline/mashable.xml?page=1
> > ($targetURL)
>
> > Code:
>
> >protected function _sendRequest($uri, $auth =TRUE, $method ='GET',
> > $data ='')
> >{
> >$ch = curl_init();
>
> >$protocol = ($this->_useSSL) ? 'https' : 'http';
> >$targetURL = "{$protocol}://" . self::API_URI . $uri;
>
> >curl_setopt($ch, CURLOPT_URL, $targetURL);
> >curl_setopt($ch, CURLOPT_RETURNTRANSFER, TRUE);
> >curl_setopt($ch, CURLOPT_HTTPHEADER, array('Expect:'));
>
> >if($auth)
> >{
> >curl_setopt($ch, CURLOPT_USERPWD, "{$this->_authUsername}:
> > {$this->_authPassword}");
> >}
>
> >if('POST' == ($method = strtoupper($method)))
> >{
> >curl_setopt($ch, CURLOPT_POST, TRUE);
> >curl_setopt($ch, CURLOPT_POSTFIELDS, $data);
> >}
> >else if('GET' != $method)
> >{
> >curl_setopt($ch, CURLOPT_CUSTOMREQUEST, $method);
> >}
>
> >curl_setopt($ch, CURLOPT_CONNECTTIMEOUT, TRUE);
> >curl_setopt($ch, CURLOPT_TIMEOUT, $this->_timeout);
>
> >$data = curl_exec($ch);
> >$meta = curl_getinfo($ch);
>
> >curl_close($ch);
>
> >return new Arc90_Service_Twitter_Response($data, $meta);
>
> >}
>
> > $data is returning:
> > " This account is locked due to too many failed login attempts. Try
> > again in 3100 seconds. error"
>
> > I hope this is what you were referring to...
>
> > -Joe
>
> > On Apr 21, 9:53 am, Mark McBride wrote:
> >> What specific endpoint are you calling? Are you authenticating the
> >> call? This is a recent change, and likely indicates that the
> >> credentials you're using are invalid.
>
> >>---Mark
>
> >>http://twitter.com/mccv
>
> >> On Wed, Apr 21, 2010 at 9:27 AM, Joe Taylor wrote:
> >> > "This account is locked due to too many failed login attempts. Try
> >> > again in X seconds."
>
> >> > Hello,
> >> > I'm receiving this error for the first time on an application that has
> >> > been working for almost a year. It only happens when we are searching
> >> > a profile for to pull up a single users stream.
>
> >> >http://www.twitterface.com/tech-news
>
> >> >http://skitch.com/kristicolvin/n97ci/twitterface-ungeeked
>
> >> > I was wondering if anyone could give me some insight to fix this. Any
> >> > help is greatly appreciated.
>
> >> > -Joe
>
> >> > --
> >> > Subscription
> >> > settings:http://groups.google.com/group/twitter-development-talk/subscribe?hl=en
[twitter-dev] Re: This account is locked due to too many failed login attempts. Try again in X seconds.
I'm sorry for my ignorance, but I'm think this is what you are asking
for.
http://twitter.com/statuses/user_timeline/mashable.xml?page=1
($targetURL)
Code:
protected function _sendRequest($uri, $auth =TRUE, $method ='GET',
$data ='')
{
$ch = curl_init();
$protocol = ($this->_useSSL) ? 'https' : 'http';
$targetURL = "{$protocol}://" . self::API_URI . $uri;
curl_setopt($ch, CURLOPT_URL, $targetURL);
curl_setopt($ch, CURLOPT_RETURNTRANSFER, TRUE);
curl_setopt($ch, CURLOPT_HTTPHEADER, array('Expect:'));
if($auth)
{
curl_setopt($ch, CURLOPT_USERPWD, "{$this->_authUsername}:
{$this->_authPassword}");
}
if('POST' == ($method = strtoupper($method)))
{
curl_setopt($ch, CURLOPT_POST, TRUE);
curl_setopt($ch, CURLOPT_POSTFIELDS, $data);
}
else if('GET' != $method)
{
curl_setopt($ch, CURLOPT_CUSTOMREQUEST, $method);
}
curl_setopt($ch, CURLOPT_CONNECTTIMEOUT, TRUE);
curl_setopt($ch, CURLOPT_TIMEOUT, $this->_timeout);
$data = curl_exec($ch);
$meta = curl_getinfo($ch);
curl_close($ch);
return new Arc90_Service_Twitter_Response($data, $meta);
}
$data is returning:
" This account is locked due to too many failed login attempts. Try
again in 3100 seconds. error"
I hope this is what you were referring to...
-Joe
On Apr 21, 9:53 am, Mark McBride wrote:
> What specific endpoint are you calling? Are you authenticating the
> call? This is a recent change, and likely indicates that the
> credentials you're using are invalid.
>
> ---Mark
>
> http://twitter.com/mccv
>
> On Wed, Apr 21, 2010 at 9:27 AM, Joe Taylor wrote:
> > "This account is locked due to too many failed login attempts. Try
> > again in X seconds."
>
> > Hello,
> > I'm receiving this error for the first time on an application that has
> > been working for almost a year. It only happens when we are searching
> > a profile for to pull up a single users stream.
>
> >http://www.twitterface.com/tech-news
>
> >http://skitch.com/kristicolvin/n97ci/twitterface-ungeeked
>
> > I was wondering if anyone could give me some insight to fix this. Any
> > help is greatly appreciated.
>
> > -Joe
>
> > --
> > Subscription
> > settings:http://groups.google.com/group/twitter-development-talk/subscribe?hl=en
[twitter-dev] This account is locked due to too many failed login attempts. Try again in X seconds.
"This account is locked due to too many failed login attempts. Try again in X seconds." Hello, I'm receiving this error for the first time on an application that has been working for almost a year. It only happens when we are searching a profile for to pull up a single users stream. http://www.twitterface.com/tech-news http://skitch.com/kristicolvin/n97ci/twitterface-ungeeked I was wondering if anyone could give me some insight to fix this. Any help is greatly appreciated. -Joe -- Subscription settings: http://groups.google.com/group/twitter-development-talk/subscribe?hl=en
[twitter-dev] Re: Can't get @Anywhere to respond
Thank you sir, it is now working.
On Apr 20, 7:24 pm, Abraham Williams <4bra...@gmail.com> wrote:
> I just tried it and it worked an created a valid access token. You might be
> having cookie issues or rate limit issues now.
>
>
>
> On Tue, Apr 20, 2010 at 19:21, Joe Taylor wrote:
> > K, I fixed the ID issue, and made it so the JS only calls
> > T("#authLogin_4").connectButton({ size: "large" });
>
> > Still no go. But best to clean everything up.
>
> > -Joe
>
> > On Apr 20, 7:08 pm, Abraham Williams <4bra...@gmail.com> wrote:
> > > Perhaps it is because there are several divs with the id "loginAuth"? You
> > > should only ever have a single id once per page.
>
> > > Abraham
>
> > > On Tue, Apr 20, 2010 at 19:04, Joe Taylor
> > wrote:
> > > > All of a sudden the iFrame isn't showing now either I'm at a loss
> > > > of what to do.
>
> > > > -Joe
>
> > > > On Apr 20, 6:04 pm, Joe Taylor wrote:
> > > > > I have registered the application and received the API Key. I believe
> > > > > I am doing the code right, but I can't get even the simplest
> > > > > implementation of @Anywhere to work on the site.
>
> > > > >http://www.tweettrakr.com/jmt3
>
> > > > > There should be a oAuth connect button in the far right pane. It
> > > > > creates an iframe in the div, with the right size but there is no
> > info
> > > > > in the frame container.
>
> > > > > This is the only implementation I have found to have any affect on
> > the
> > > > > div at all, most others result in nothing happening.
>
> > > > > Any help would be greatly appreciated.
>
> > > > > -Joe
>
> > > > > --
> > > > > Subscription settings:
> > > >http://groups.google.com/group/twitter-development-talk/subscribe?hl=en
>
> > > --
> > > Abraham Williams | Developer for hire |http://abrah.am
> > > PoseurTech Labs | Projects |http://labs.poseurtech.com
> > > This email is: [ ] shareable [x] ask first [ ] private.
>
> --
> Abraham Williams | Developer for hire |http://abrah.am
> PoseurTech Labs | Projects |http://labs.poseurtech.com
> This email is: [ ] shareable [x] ask first [ ] private.
[twitter-dev] Re: Can't get @Anywhere to respond
K, I fixed the ID issue, and made it so the JS only calls
T("#authLogin_4").connectButton({ size: "large" });
Still no go. But best to clean everything up.
-Joe
On Apr 20, 7:08 pm, Abraham Williams <4bra...@gmail.com> wrote:
> Perhaps it is because there are several divs with the id "loginAuth"? You
> should only ever have a single id once per page.
>
> Abraham
>
>
>
> On Tue, Apr 20, 2010 at 19:04, Joe Taylor wrote:
> > All of a sudden the iFrame isn't showing now either I'm at a loss
> > of what to do.
>
> > -Joe
>
> > On Apr 20, 6:04 pm, Joe Taylor wrote:
> > > I have registered the application and received the API Key. I believe
> > > I am doing the code right, but I can't get even the simplest
> > > implementation of @Anywhere to work on the site.
>
> > >http://www.tweettrakr.com/jmt3
>
> > > There should be a oAuth connect button in the far right pane. It
> > > creates an iframe in the div, with the right size but there is no info
> > > in the frame container.
>
> > > This is the only implementation I have found to have any affect on the
> > > div at all, most others result in nothing happening.
>
> > > Any help would be greatly appreciated.
>
> > > -Joe
>
> > > --
> > > Subscription settings:
> >http://groups.google.com/group/twitter-development-talk/subscribe?hl=en
>
> --
> Abraham Williams | Developer for hire |http://abrah.am
> PoseurTech Labs | Projects |http://labs.poseurtech.com
> This email is: [ ] shareable [x] ask first [ ] private.
[twitter-dev] Re: Can't get @Anywhere to respond
That is a good point I will troubleshoot that right now. On Apr 20, 7:08 pm, Abraham Williams <4bra...@gmail.com> wrote: > Perhaps it is because there are several divs with the id "loginAuth"? You > should only ever have a single id once per page. > > Abraham > > > > On Tue, Apr 20, 2010 at 19:04, Joe Taylor wrote: > > All of a sudden the iFrame isn't showing now either I'm at a loss > > of what to do. > > > -Joe > > > On Apr 20, 6:04 pm, Joe Taylor wrote: > > > I have registered the application and received the API Key. I believe > > > I am doing the code right, but I can't get even the simplest > > > implementation of @Anywhere to work on the site. > > > >http://www.tweettrakr.com/jmt3 > > > > There should be a oAuth connect button in the far right pane. It > > > creates an iframe in the div, with the right size but there is no info > > > in the frame container. > > > > This is the only implementation I have found to have any affect on the > > > div at all, most others result in nothing happening. > > > > Any help would be greatly appreciated. > > > > -Joe > > > > -- > > > Subscription settings: > >http://groups.google.com/group/twitter-development-talk/subscribe?hl=en > > -- > Abraham Williams | Developer for hire |http://abrah.am > PoseurTech Labs | Projects |http://labs.poseurtech.com > This email is: [ ] shareable [x] ask first [ ] private.
[twitter-dev] Re: Can't get @Anywhere to respond
All of a sudden the iFrame isn't showing now either I'm at a loss of what to do. -Joe On Apr 20, 6:04 pm, Joe Taylor wrote: > I have registered the application and received the API Key. I believe > I am doing the code right, but I can't get even the simplest > implementation of @Anywhere to work on the site. > > http://www.tweettrakr.com/jmt3 > > There should be a oAuth connect button in the far right pane. It > creates an iframe in the div, with the right size but there is no info > in the frame container. > > This is the only implementation I have found to have any affect on the > div at all, most others result in nothing happening. > > Any help would be greatly appreciated. > > -Joe > > -- > Subscription > settings:http://groups.google.com/group/twitter-development-talk/subscribe?hl=en
[twitter-dev] Can't get @Anywhere to respond
I have registered the application and received the API Key. I believe I am doing the code right, but I can't get even the simplest implementation of @Anywhere to work on the site. http://www.tweettrakr.com/jmt3 There should be a oAuth connect button in the far right pane. It creates an iframe in the div, with the right size but there is no info in the frame container. This is the only implementation I have found to have any affect on the div at all, most others result in nothing happening. Any help would be greatly appreciated. -Joe -- Subscription settings: http://groups.google.com/group/twitter-development-talk/subscribe?hl=en
