I am unsure how user lookup works behind the scenes, but the api seems slow. I assume that it search the users without taking my account as a context or as a priority. What I mean here is the API is slow regardless if I am searching for a user from my following/followers or anyone on the twitter.
It’d be great if user lookup takes the user’s account as a priority in search. For instance if I am searching “Jack”, search Jack from my account’s followers/following or if I engaged with the user in the past(even Jack and I neither of us following each other) and then in the end find anyone on twitter who matches with the phrase.
What exactly do you mean by “slow”? A lof of perceived speed is due to connection speed and or library implementation.
In v1.1 there are fields that use the authenticating user’s context like following but not in v2
I’ve compared the speeds it is def not network issues.
Thanks for pointing out the user’s context. When you say user’s context does it search only in that specific context or is it like saying to twitter, search first in my following list?
As far as I know there’s nothing that influences retrieval of objects based on your follows or whatever - usually things are cached based on frequency of use, but I’m not Twitter so I’ve no special insight here.
What kinds of response times are you observing? Does it vary by user? Is this from your local machine or on a server?
Curious about whether this is specific to either v1.1 or v2, and also what you mean by “slow”.
Are you using fields and expansions in v2? what parameters are you calling the API with? etc.
system
Closed
#6
This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.
