Both modes only pass apis[0] into the relevant method, even when multiple APIs are available.
For "search" mode, this may make sense, since the number of tweets returned by the search is likely bounded by the 7-day search limit. However, for a particularly popular query and a high max_count, this bound may be very high and API reuse could help speed up the query.
There is no time bound on API queries for favorites, and here it definitely makes sense to allow for multiple API usage.
I don't know exactly how the Twitter API rate limiting works for such queries, so the above may be entirely invalid.
Both modes only pass
apis[0]into the relevant method, even when multiple APIs are available.For "search" mode, this may make sense, since the number of tweets returned by the search is likely bounded by the 7-day search limit. However, for a particularly popular query and a high
max_count, this bound may be very high and API reuse could help speed up the query.There is no time bound on API queries for favorites, and here it definitely makes sense to allow for multiple API usage.
I don't know exactly how the Twitter API rate limiting works for such queries, so the above may be entirely invalid.