I’ve got some questions about how the Standard streaming API works. As I understand it from reading around, the “elevated access” referred to in the Streaming API required to use the “count” parameter in statuses/filter is PowerTrack (i.e. enterprise) - is that correct, or have I read it wrong?
Assuming the above paragraph is correct, I’m currently using the rest API to check about 250 accounts using the REST statuses/get_user_timeline endpoint at timed intervals; the streaming API makes more sense for this purpose, but also means potentially missing tweets if my app disconnects for any length of time. Is it common practice to use the standard streaming API for this, and then use the REST API to fill in any gaps (by checking for tweets between the last one the stream connection retrieved for a user before going offline, and the next one it gets once back up)? Or is there a better/preferred way to do this?