Need suggestions for time scheduling async tasks

The classic approach to rate limiting is via the use of a [token bucket](https://en.wikipedia.org/wiki/Token_bucket) \- here's an implementation for `chronos` (asyncdispatch alternative):

Need suggestions for time scheduling async tasks

Thank you for the suggestion, unfortunately the way it works is not clear to me, and how I should implement it for my use case. I realized the actual requests are done by a single procedure in my code, and I can calculate a sleep delay at the start of it, given the times previous requests were m

Need suggestions for time scheduling async tasks

Had a look at your repos after you mentioned that the german tax thing was your first project to receive a contribution (although that's not a repo tsk tsk). I seemed to remember you had some interesting projects so I thought it sounded strange. And that's when I found `at` after having first se

Need suggestions for time scheduling async tasks

@PMunch thanks for recommending `at`!! @viud09 it's a lightweight persistent task scheduler. I have an unpublished comment system that uses `at` combined with `limdb` for that exact purpose- in fact, having a rate limiter is the original use case why `limdb` AND `at` were written. I would reco

Need suggestions for time scheduling async tasks

Maybe the [at](https://nimble.directory/pkg/at) package could be helpful?

Need suggestions for time scheduling async tasks

I am writing a client/crawler/scraper library for a certain website, hopefully my first nimble package. The site has some rate limiting which I haven't figure out exactly yet, but will try to do. Once I do, I want to have a request scheduler so that all requests (async) done to the website are a