Rate-limit errors from Bluesky

[scripting]

I'm kind of stuck with my little feed reader in bluesky.

It works, but a few hours into it, at 10PM last night, we start getting rate-limit errors from bluesky.

If it really is a rate limit, shouldn't reset after a while?

The code that actually does the sending to Bluesky is here.

https://github.com/scripting/textcasting/blob/main/plugins/platforms/bluesky/code.js

Any help much appreciated. :-)

PS: I don't want to change this code, I've built a lot of stuff on top of it, and it's a small part of what I'm doing.

[colin-walker]

What limit are you getting hit by?

https://docs.bsky.app/blog/rate-limits-pds-v3

When I first built the integration with my blog it was the createSession limit that got me so had to save the refresh token then use that against com.atproto.server.refreshSession instead.

[scripting]

@colin-walker -- i get an error response back from bluesky like this:

{
    "error": "RateLimitExceeded",
    "message": "Rate Limit Exceeded"
}

as far as i know that's all the information i have.

[colin-walker]

I suspect then that it is the createSession limit you're hitting. If you use the same code across everything and it's all authorised against your DID then you might trigger it cumulatively across your apps.

I'd try saving the API refresh token then each time you post check it exists and use that against refreshSession. If that returns an error (likely refresh token expired but they used to have quite a long life) then go to createSession.

[scripting]

I have to be careful diving into this stuff, because this is just an experiment, it's in this context that i ask -- is this based on a review of the code I linked to or just a general comment.

Also, it never clearing the rate-limit, it's still blocking posts 12 hours after it started. That doesn't sound very rational, but i have to admit I am not anything like an expert in Bluesky api.

[colin-walker]

An educated guess based on a quick look at the code and my own previous experience.

[scripting]

gotcha. i need to try moving things around a bit before embarking on what amounts to a breaking change here.

[scripting]

how long to accesstokens last?

[colin-walker]

Last thing I saw a refresh token lasts 2 months.

[scripting]

All of a sudden it's posting again. I guess it got unstuck? Now I've limited it on my end to three posts per hour. Let's see if it can keep that going for a while. Then I'll try increasing to 5. Knock wood.

[scripting]

I found a way to add a cache for accessTokens without disrupting the code too much, and learned that they expire after about an hour. Not hard to account for. And the app seems to be holding up better. It's all voodoo because I can't see what's going on on the Bluesky side.

[scripting]

The rate-limit code is in this file.

https://github.com/scripting/textcasting/blob/main/plugins/platforms/bluesky/code.js

I had to store the cache on disk because this code is loaded from disk for each request, it's part of a plugin architecture that works for other services, not just bluesky.

As noted above, the accessTokens do expire, so I delete them after 59 minutes (assuming the timeout is at 60).