Currently, yes. I thought assigning a unique IP to the domain would solve the problem, but apparently not. I'm working on testing it on a VPS through the same host.
On Sun, May 22, 2011 at 3:26 PM, Scott Wilcox <[email protected]> wrote: > Thats what I was thinking, shared hosting provider? > > On 22 May 2011, at 20:24, Matthew Vanden Boogart wrote: > > Thanks Scott. I'm making anonymous calls - nothing authenticated. Just > pulling some profile/timeline info. > > -matthew > > On Sun, May 22, 2011 at 2:41 PM, Scott Wilcox <[email protected]> wrote: > >> There is nothing provided by the API that can give you your own IP. >> >> Are you making OAuth authenticated calls? >> >> On 22 May 2011, at 18:18, matthewvb wrote: >> >> > Is there a way to get the API to respond back with the IP address >> > hitting it from the call? >> > >> > I'm running into a problem where something is eating away at my API >> > hits / hour. I've put a simple script on a few isolated domains (non- >> > Twitter calling ones) that are also having their API hits eaten up. >> > They have unique IPs assigned to them - so I'm not sure if the problem >> > is on my host's end and how they are "showing" my server to Twitter, >> > or if it's something on the API end. >> > > -- > Twitter developer documentation and resources: https://dev.twitter.com/doc > API updates via Twitter: https://twitter.com/twitterapi > Issues/Enhancements Tracker: > https://code.google.com/p/twitter-api/issues/list > Change your membership to this group: > https://groups.google.com/forum/#!forum/twitter-development-talk > -- Twitter developer documentation and resources: https://dev.twitter.com/doc API updates via Twitter: https://twitter.com/twitterapi Issues/Enhancements Tracker: https://code.google.com/p/twitter-api/issues/list Change your membership to this group: https://groups.google.com/forum/#!forum/twitter-development-talk
