up
...
lots of people waiting :)
Shipping tomorrow, Monday if it slips.
On Thu, Jan 29, 2009 at 10:51, Karthik fermis...@gmail.com wrote:
Alex,
Any updates on these new API's?
We are eagerly awaiting for its release.
Thanks,
Karthik
On Jan 23, 3:46 am, Alex Payne a...@twitter.com wrote:
I'm already working on this.
Thank you, thank you!
On Jan 23, 3:46 am, Alex Payne a...@twitter.com wrote:
I'm already working on this. It'll be new methods, I think. Should be
ready to deploy by early next week.
On Thu, Jan 22, 2009 at 10:15, Scott C. Lemon scottcle...@gmail.com wrote:
Alex,
Thank you for the
iematthew wrote:
Perhaps a leaner version for requesting a user's followers and friends
would help? Say, a method that only returns the ID and screen name for
the user's followers or friends, but in lots of a thousand or ten
thousand at a time.
Yes, please!
-Matt
Alex,
Thank you for the quick reply ... and I agree ... it seems that
returning the list of followers or friends as an array of IDs would be
most effective. This is somewhat how Facebook does it with their
API. That would allow us to gain access to the information in a much
more compact way.
I'm already working on this. It'll be new methods, I think. Should be
ready to deploy by early next week.
On Thu, Jan 22, 2009 at 10:15, Scott C. Lemon scottcle...@gmail.com wrote:
Alex,
Thank you for the quick reply ... and I agree ... it seems that
returning the list of followers or
The only reply I can think of for this is HOT!
I just spent the past couple weeks building a service to search ones
followers (http://tweepsearch.com) and I still feel bad about pounding
the API. This will make it _much_ easier.
Thanks for making this change!
dpc
On Jan 22, 2:46 pm, Alex
Alex,
are status update POSTs still excluded from this limit?
Mario.
On Tue, Jan 20, 2009 at 11:48 PM, Alex Payne a...@twitter.com wrote:
Up until now we've allowed users and IPs on our whitelist an unlimited
number of requests per hour. When our whitelist was in the tens and
low
Yes.
On Wed, Jan 21, 2009 at 04:07, Mario Menti mme...@gmail.com wrote:
Alex,
are status update POSTs still excluded from this limit?
Mario.
On Tue, Jan 20, 2009 at 11:48 PM, Alex Payne a...@twitter.com wrote:
Up until now we've allowed users and IPs on our whitelist an unlimited
Perhaps a leaner version for requesting a user's followers and friends
would help? Say, a method that only returns the ID and screen name for
the user's followers or friends, but in lots of a thousand or ten
thousand at a time.
On Jan 21, 12:19 am, Jesse Stay jesses...@gmail.com wrote:
Alex,
I agree, ID/ScreenName only responses would cut down on A LOT of traffic.
On Wed, Jan 21, 2009 at 3:28 PM, rhysmeister therhysmeis...@hotmail.com wrote:
Yeah, somehow being able to periodically fully replicate your twitter
data would be really good and reduce requests considerably.
On Jan
Alex,
Look forward to working with you on this.
As you know PeopleBrowsr passes all requests via a cache to minimise
API requests on Twitter.
Our requests which are coming from many clients will appear as coming
from one IP address.
Clients like Tweetdeck that dont cache, will make many more API
Alex,
Can you please address the issue of how you would recommend that an
application be able to fetch the total list of a users followers? I'm
hearing all sorts of accusations and bluster, but want to understand
from your perspective how you would propose an application do this?
It's obvious
In light of this, do we get a rate_limit_status type feed for a
given IP, or do we keep an internal track of our calls (which could be
inaccurate)?
On Jan 21, 4:48 am, Alex Payne a...@twitter.com wrote:
Up until now we've allowed users and IPs on our whitelist an unlimited
number of requests
On Wed, Jan 21, 2009 at 10:20 PM, Aditya adi...@adityamukherjee.com wrote:
In light of this, do we get a rate_limit_status type feed for a
given IP, or do we keep an internal track of our calls (which could be
inaccurate)?
You mean like the rate_limit_status API call?
Can you please address the issue of how you would recommend that an
application be able to fetch the total list of a users followers? I'm
hearing all sorts of accusations and bluster, but want to understand
from your perspective how you would propose an application do this?
Right now, you
Alex, thanks - this is what we were looking for. In our defense, I did send
you several personal e-mails and you mentioned this wasn't on your roadmap.
While the limit will still eventually get us, this will get us much
further. Is it necessary to implement the limit before these changes are in
Up until now we've allowed users and IPs on our whitelist an unlimited
number of requests per hour. When our whitelist was in the tens and
low hundreds, this made sense. Now that we have more developers on the
whitelist than we can reasonably maintain close communication with, we
need to put a
Alex, you and I have discussed this, but I still think this is a bad
decision until some sort of better method is placed around getting the list
of followers of a user. This basically limits how big any application on
your platform can get. Right now it takes 400 requests alone to get Robert
19 matches
Mail list logo
