Jonathan de Jong

Why hasn't this been escalated as a serious issue? Performance before features imo

What'd be the benefit of this? To me it seems like a push mechanism, or a "selection" mechanism to notify a script (not a program, I dont know of a...

I think an absolute maximum of 32 images (to prevent DoS) would be more than sufficient, tbh.

I can recommend looking into something like [sidekiq-rate-limiter](https://github.com/enova/sidekiq-rate-limiter). Then, mastodon can do something like dynamic throttling based on how many errors per hour or such there are, which means that...

TIP: you can parallelise the push queue massively, as most of it is HTTP connect and wait. Where we have a parallelisation of 8 for most CPU-intensive tasks (like ingress...

If you're using the default docker-compose file, i can recommend adding a new container with (something like) the following; ``` sidekiq_push: # adjust these two as required build: . image:...

Oh I just remembered: Deleting the subscriptions entirely should short-cut the jobs and return them complete, basically churning through them as quickly as they can without throwing them on the...

Possibly something a-la stoplight, that would check the ratelimit state for a given domain, and return "re-enqueue for in X seconds" as a possible outcome for the job?

+1, currently considering this role for automating nginx installations, and this is a missing feature (as having certbot stop nginx to do its job isnt exactly the most ideal) will...

Not stale https://nostalebots.xyz