h account to lock if the calls are
> unauthenticated? perhaps you are passing incorrect authentication instead?
> Abraham
>
> On Wed, Dec 16, 2009 at 09:08, Sal Conigliaro wrote:
>>
>> It appears that repeated (unauthenticated) calls to the API lock out
>> the account.
>>
&
It appears that repeated (unauthenticated) calls to the API lock out
the account.
The workaround is to use authenticated credentials when querying the
API. It would be helpful if the API docs could be revised to reflect
this.
Sal
On Dec 13, 8:01 pm, Sal Conigliaro wrote:
> Thanks Mark
Thanks Mark. I appreciate it.
On Dec 13, 1:28 am, Mark McBride wrote:
> I'll check with our abuse team, but this looks odd.
>
>
>
>
>
> On Sat, Dec 12, 2009 at 10:23 PM, Sal Conigliaro wrote:
> > Hi there-
>
> > I have an app that compares who you'
Hi there-
I have an app that compares who you're following to your friends
followers. To do this, I query ttp://twitter.com/friends/ids.json?user_id=X
and compare that to my (saved) list of IDs.
I noticed that if I make repeated (unauthenticated) queries to
http://twitter.com/friends/ids.json?use
Do a cURL request to whatismyip.com and see what address
your request is coming from.
On Dec 8, 2:13 pm, Jesse Bunch wrote:
> Hi,
>
> I am on a shared web hosting space, but my domain has a dedicated IP
> on the server. Am I correct in saying that the twitter API sees the
> dedicated IP address i
Check here:
http://groups.google.com/group/twitter-development-talk/browse_thread/thread/4e6a8b0c7d73d85
On Nov 17, 2:36 pm, Tim Haines wrote:
> Hi Marcel,
>
> Thanks for following up on this. The bad cert responses I got were
> inconsistent. Often it would work fine, so what you've outlined h
Hi Marcel-
I'm still seeing the cert hostname mismatch.
https://api.twitter.com/1/users/show/rwzombie.xml
The cert hostname returned is still shown as 'twitter.com'.
Sal
On Oct 18, 4:36 pm, Marcel Molina wrote:
> The change has been made but it probably hasn't been pushed out yet to
> the fu
