Open seboslaw opened 5 months ago
There is no consistent ordering to the knownFolowers right now due to the implementation of the service that provides that data, so paginating over the response isn't feasible and a cursor can't be supported.
Ok, gotcha. It would probably make sense to remove it from the spec then, right?
I think that's a good idea to remove this endpoint from docs or alert users about this issue (I lost a good time before found this issue on github)
The current backend implementation of https://github.com/bluesky-social/atproto/blob/main/lexicons/app/bsky/graph/getKnownFollowers.json doesn't return a
cursor
in the response. Thus, it's currently impossible to paginate the followers.To Reproduce
Steps to reproduce the behavior:
Expected behavior
I expect a cursor in the response if the count of followers is greater than the passed in limit.
Details
Additional context
Here is a sample response: