Faster user_info with less API requests #19
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Hi,
It is usual for
user_id
to contain duplicated user IDs, as long as the same person is very likely to have taken more than one picture. This can happen especially when the direct output ofphoto_search
is used (columnowner
). Instead of using the whole sequence ofuser_id
it would be wise to remove duplicates and then merge the result to the initial larger input. So, Flickr API will ask for each one of them only once. What do you think?Thanks.