You would think that would be the case, but I have checked the cursor on multiple pages, and only the a key is populated.
I agree. I was more so doing it to try to understand what is going on. Seems strange that the b key is never populated.
I guess there is no way to query for followers, and then query again later to only get new followers. I was thinking you may be able to store the cursor, but that seems like a no go (I had no idea the cursors were generated on a per call basis). I also thought maybe you could query followers, and stop once you get one you have already stored locally, but this doesn’t account for someone unfollowing, and then following again.
Seems like the only sure fire way to get new followers (without reading them all every time) is to use web hooks, which means you must have a web server storing them all. Since I was coding something that was meant to be run locally, I may have to rethink a few things. I could have a web server catching follows, and then query that web server with my app instead I guess. It’s just an extra layer I was hoping to avoid.
This still has issues of being out of date if for some reason the server crashed, and before it could reboot someone followed. You would likely need to periodically still loop through them all to double check that (or handle that on server boot to double check your data is still good).
Thanks for the info!