Prevent rate limit when performing bulk follower lookup for filter#1078
Merged
dimdenGD merged 3 commits intoAug 5, 2025
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR fixes an issue on the user's own followers page when using the filter functionality, due to what looks to be a new(?) additional rate limit handler on the user lookup endpoint imposed by X when called in quick succession.
At least for me, this is easily reproducible by calling https://api.x.com/1.1/users/lookup.json?user_id=1708130407663759360 six times in quick succession (opening in a browser logged in to X and refreshing the page works fine to test this). The first 5 requests succeed, while the 6th and all requests thereafter, until backing off for some period of time, begin to return
{"errors":[{"message":"Sorry, that page does not exist","code":34}]}instead.I tested with multiple increments and 60 seconds seemed to be the smallest increment that doesn't eventually fail.