A related follow-up question. I have an application that looks for videos in tweets returned by hashtag search. Hitherto, I've been (A) doing the hashtag search, and (B) doing a status lookup for each returned tweet, in order to get at the extended_entities and hence the video. However, I've just come across a case similar to frangarcia's, in which data for a status from (A) had "truncated": true, but there was no extended_entities data for this status in (B).
When I add tweet_mode=extended to the URL in (A) for the particular hashtag in question, it looks as though all the status data in (A) includes the extended_entities, and hence that there is no need for stage (B).
Does that now apply in all cases: to retrieve videos in tweets on any given hashtag all I have to do is add the extra tweet_mode URL query parameter in (A), and there's no longer any need for (B)?
Thanks in advance