ith the relevant end user as the twitter authenticated user, I
can do 200*150=3 API calls in one hours without whitelisting the
IP address, which is more than the 2 I could do with whitelisting.
Can anyone give a counter example where whitelisting is absolutely
necessary?
Thank you,
Boaz
plicitly spell out how it actually works?
>
> Boaz - as the thread Srikanth referenced states, official word from
> Twitter is that you get 20,000 calls per hour *per user* from your
> whitelisted IP. (Of course, it's not that cut and dried - POSTs are
> different than GETs are d
ny behvior
where my limits are affected by other users with which I share the
resource.
Am I missing something? Could it be just a matter of luck/random
behavior?
Thank you,
Boaz
On Aug 22, 12:03 am, "Darren Bounds (Cliqset)"
wrote:
> Hello Chad,
>
> Can you confirm that this is not
Just to clarify: I am testing with unauthenticated calls
On Aug 23, 5:17 pm, boaz wrote:
> Hello everyone,
>
> I checked the behavior on an AWS instance _without_ static IP (which
> is called by Amazon elastic IP) and I do not see any problem with the
> limits. The "limit
Different question on the same email that states that Twitter will
start tracking every t.co click, whether on twitter.com or a Twitter
app. Does anyone know if Twitter will update their API to allow us to
get the Twitter Update ID that referred a particular click?
Thanks,
Boaz
On Sep 1, 8:34
Just received an email titled "Twitter Apps and You." In the email,
Twitter says that "when you click on [t.co] links from Twitter.com or
a Twitter application, Twitter will log that click. We hope to use
this data to provide better and more relevant content to you over
time."
Any idea if Twitter
