I guess what I¹m really trying to say is, I suppose, that for all of us who
have been lobbying for a bulk-lookup method for a pretty long time, what¹s
been made available here is quite disappointing. It¹s like you¹re giving us
the Ferrari we always wanted, but then tell us it has a fuel range of 2
OK, let me rephrase... For those of us maintaining a cached social graph for
our users and using the social graph methods to update our cache and then
using user/show to update the user objects, the new method is ³useless² as a
replacement for user/show, where you currently CAN do 20,000/hour assum
Uh, yes, we can. There are probably apps that are doing on the order of
100,000 user/show requests per hour. I won't name names ...
On 3/11/10 2:34 PM, Raffi Krikorian wrote:
> i wouldn't necessarily and harshly say "useless" :P it still prevents
> you from having to make 1000 user/show reques
Raffi,
Is there a limit on how many user/show requests can be done apart from the
standard 20k rate limit?
I'm thinking the limit of 1000 user objects per hour is frustratingly low
too. It's making me hesitate in my decision to use it.
Tim.
On Fri, Mar 12, 2010 at 8:34 AM, Raffi Krikorian wro
i wouldn't necessarily and harshly say "useless" :P it still prevents you
from having to make 1000 user/show requests (which you can't do right now).
On Thu, Mar 11, 2010 at 10:59 AM, Michael Steuer wrote:
> Oh wow, I missed that. I understood it was rate limited at 1000 calls/hour
> (which wo
Oh wow, I missed that. I understood it was rate limited at 1000 calls/
hour (which would come out to 20k user objects)
Having a limit of only 1,000 user objects an hour, renders this new
API pretty useless! Come on! I thought the idea was to give developers
who now do 10's of thousands of us
>From the wiki page:
> users/lookup
> Return up to 20 users worth of extended information, specified by either ID,
> screen name, or combination of the two. The author's most recent status (if
> the authenticating user has permission) will be returned inline. Users can,
> at most, look up 1000
At the risk of opening a huge can of worms, how much of an impact
would it be if *all* API calls required authentication? I know in my
own "products", it's zero impact to require everything to
authenticate. Would it simplify things for Twitter if *everything* had
to be authenticated?
--
M.
My understanding is that it is 50 users/lookup API calls x 20 user objects
per call = 1000 user objects. Not 1000 users/lookup calls of 20 user
objects.
Abraham
On Thu, Mar 11, 2010 at 10:06, Michael Steuer wrote:
>
> Erm, doesn’t 20,000 x users/show equate to 1,000 x users/lookup ?
>
> Or are
Erm, doesn¹t 20,000 x users/show equate to 1,000 x users/lookup ?
Or are you whitelisted for more than 20,000 API calls an hour?
On 3/11/10 9:53 AM, "Abraham Williams" <4bra...@gmail.com> wrote:
> So for something like Intersect [1] where I have to do sometimes tens of
> thousands of profile l
On Thu, Mar 11, 2010 at 09:53, Abraham Williams <4bra...@gmail.com> wrote:
> So for something like Intersect [1] where I have to do sometimes tens of
> thousands of profile lookups per hour I should stick with users/show? Or can
> I get an account whitelisted for more lookups per hour?
>
> Abraham
So for something like Intersect [1] where I have to do sometimes tens of
thousands of profile lookups per hour I should stick with users/show? Or can
I get an account whitelisted for more lookups per hour?
Abraham
On Thu, Mar 11, 2010 at 07:48, Raffi Krikorian wrote:
> hi all.
>
> we launched a
At this time, no. Sorry. In the future, we will reevaluate whether
this call should have authentication.
On Mar 11, 2010, at 8:22 AM, Harshad RJ wrote:
This is great!
But could authentication be made optional? The original API (user/
show) isn't, and those who want to replace it might n
Raffi, does the limit mean that if you call this API for 20 users at a
time, you can only use it 50 times per hour?
Cheers,
Tim.
On 12/03/2010, at 4:48 AM, Raffi Krikorian wrote:
hi all.
we launched an endpoint yesterday that allows you to fetch 20 users
by user_id or by screen_name at
This is great!
But could authentication be made optional? The original API (user/show)
isn't, and those who want to replace it might need to go through a lot of
code changes...
On Thu, Mar 11, 2010 at 9:18 PM, Raffi Krikorian wrote:
> hi all.
>
> we launched an endpoint yesterday that allows
15 matches
Mail list logo
