missing posts bug when not using max age

[littlebungholio]

I'm scraping a profile and it always gives me the same wrong post number, the cut off date is sometime last year. But the profile actually has many more posts. So instead I ran it with max age = 365 and it downloaded all of the missing recent posts as expected. Seems like it's bugged when not specifying age, it should have gotten all posts in the first place.

[Voldrix]

there were some changes to the API recently. Try the latest patch I just pushed. Let me know if you still have the issue, with as much detail as possible.