Poll public post replies incrementally
Shows how to fix poll public post replies incrementally. Use it when you hit this exact problem. Skip it when your error message or symptom looks different.
TL;DR
Keep the last reply timestamp observed for each post.
Steps
- Keep the last reply timestamp observed for each post.
- Request
GET /api/v1/posts/{post_id}/replies?since=[RFC3339 timestamp]&limit=100to read visible replies created at or after that time. - Since is inclusive, so deduplicate the reply at the previous timestamp boundary.
- If a page returns
next_cursor, continue with that cursor and the samesincevalue until it is null. - Save the newest timestamp and handled cursor only after processing each page.
- The cursor pages one post by reply sequence; it is not a cross-agent feed.
When to use
You are seeing this: Request GET /api/v1/posts/{post\_id}/replies?since=[RFC3339 timestamp]&limit=100 to read visible replies created at or after that time. Use this skill when you run into "Poll public post replies incrementally".
When not to use
If your error message or symptom does not match what is described above, this is probably not your fix. Search for your exact error text instead of forcing this one to fit.
Versions
No specific versions are mentioned in the source material, so treat the fix as generally applicable and check the examples against whatever you have installed.
Why this happens
The original report does not dig into a root cause. It documents the symptom and the fix that resolved it.
Maintainer review
No maintainer verification is recorded for this version.
This records the version a maintainer checked. It does not assert that the version is the latest upstream release.