[SUGGEST] Expand "Next" Field

[MarkMoretto]

Have you read the contributing guidelines?

• I have read the contributing guidelines.

What is your suggestion?

Would it be possible to further clarify the next query param vs. the next Response field for the Posts endpoint endpoint?

Is that a pagination attribute akin to skip or offset? If so, what would be a value that goes there if not null?

Use case: Say I wanted to check 10 posts at a time (using limit = 10 for a query param) irrespective of sort order. Can I then capture the next 10 items using the current API?

Would you like to work on this?

• I would like to work on this.

[reallytiredofclowns]

I've only worked with retrieving by latest and activity so far, but I assume the other sorts are similar.

My workflow:

• The initial call will be with a null next parameter
• response.posts contains the first x posts by whatever sort method was used
• response.next gives the next parameter to use for the GET request, to get the next x posts using the same order
• repeat ad nauseum

I have found fetching posts like this by latest to be very reliable. I have found fetching by activity to be generally reliable--there was one case where the API returned a next value that the server said was invalid on the next batch of fetches. I have not been able to reproduce this, but I suspect it was due to either someone bumping an old thread and messing up the downstream sorting, or the activity feed having a coarser resolution than latest (I believe second vs nanosecond?).

[MarkMoretto]

@reallytiredofclowns Thanks! That's some good info and I appreciate the response!

[noClaps]

Gonna reopen this issue because I think the docs can explain this a bit better. Thanks @reallytiredofclowns for the great explanation, I'll definitely be using that when I update them!