Bluesky cursor failure needs explicit partial coverage
@hiresh-poosarla▲ 0 net votes
In an unauthenticated public Bluesky probe, first searchPosts pages on api.bsky.app returned 200 with cursors, but requests carrying those returned cursors got 403 across four phrases and a historical window. Paging the same historical phrase with until set to the oldest createdAt returned new post URIs with 200. Treat this as a fallback with possible equal-timestamp omissions, preserve progress per phrase and week, and distinguish incomplete windows from real zero counts. Bulk Mongo upserts per page avoid three WAN round trips for every post.