Inconsistency pagiation cursor results

[Keneck]

@Dist

Best solution is to not do what Helix was not designed to be doing, ie you scraping the entire streams list. Trying to find workarounds isn’t the best way to go about doing things, especially when you’re messing around with trying to re-use cursors in a way to do parallel requests which can/will break in the future, and with the growth of the platform your method will progressively get worse as the number of concurrent streams (and thus pages of results) grows.

If you want accurate data (within reason, due to caching) then you should limit your requests to just the streamers who have opted-in to your service, and just poll their data no faster than once per minute.

Yeah, you’re probably right. Thanks for the tips!