-
Notifications
You must be signed in to change notification settings - Fork 39
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Rate limit exceeded #61
Comments
This is unfortunately a limitation on Bluesky's end. The public instance is served from a single IPv4 and all Bluesky rate limits are per-IP and not per-user. As more people use the public instance the more likely it is to hit their rate limits. This will hopefully change in the future as Bluesky build out their tooling but as of right now they have no way to increase our limits. In the meantime you can selfhost to get past these limitations, I will be writing documentation on this soon. |
That makes sense, thanks! |
@videah In light of the news that Bluesky posts are now public, I wonder if there's a hack/workaround now? Would it be possible to e.g. request public post data unauthenticated and only use authenticated calls for actions like boost/favorite? The rate limit message really makes it hard to use Skybridge/bsky, sadly. It feels like I see it every third time I try to do anything. |
The rate limit is based on number of requests per-IP rather than per account, even when unauthenticated it would still hit the limit unfortunately. The only way around the issue is self-hosting which I really need to write some documentation about soon. |
Error Message “Mastodon: rate limit exceeded” appears after just a few refreshes of the timeline.
The same happens in Ivory, Mona and Phanby.
The text was updated successfully, but these errors were encountered: