I don't think this will play nicely with the "limit post count" feature. For instance, if someone sets the limit to 25, and one post is hidden in the initial 25, the next batch will be downloaded, meaning up to 49 posts could be displayed instead of the requested 25.

There are a couple of ways to solve this:
* Discard all posts after the limit and adjust `after` to re-download them
* Store the excess posts in a linked list and continue processing them when the user requests more posts

I'm happy to do this if you want, since it'll require a fair bit of refactoring.