Skip to content
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 handling #2

Open
Kio-td opened this issue Jul 24, 2024 · 1 comment
Open

Rate limit handling #2

Kio-td opened this issue Jul 24, 2024 · 1 comment
Labels
enhancement New feature or request Stalled This issue/feat is waiting for an update from misskey.

Comments

@Kio-td
Copy link
Contributor

Kio-td commented Jul 24, 2024

So; Misskey doesn't like to tell what happens to a user until after they were given a ratelimit. That's a problem, because it can mean that at any point, the server can just give up; and Cardboard isn't smart enough (yet) to detect that ratelimit and wait for it to pass before sending commands to misskey again.

The idea is most likely to make all commands enter a queue that Cardboard will work through, and will only delete the command when it's been completed; then if hit with a ratelimit, it'll emit a event and will sleep until the ratelimit has been passed before sending more notes.

@Kio-td Kio-td added this to Todo Jul 21, 2024
@Kio-td Kio-td converted this from a draft issue Jul 24, 2024
@Kio-td
Copy link
Contributor Author

Kio-td commented Jul 24, 2024

@Kio-td Kio-td added enhancement New feature or request Stalled This issue/feat is waiting for an update from misskey. labels Jul 24, 2024
@Kio-td Kio-td moved this from Todo to On the back burner in Todo Jul 25, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request Stalled This issue/feat is waiting for an update from misskey.
Projects
Status: On the back burner
Development

No branches or pull requests

1 participant