Ruslan Ibrahimau (Ibragimov)

> Primitive, which distributes permits at the fixed rate or suspends current coroutine until it's available. Or immediately returns (like offer in channels), to respond on current request, that it...

> If we want to implement rate-limiting in our own software, the most transparent way to do that is not to return until the ratelimit-interval has been reached. Yes, it...

> But this is not something which you can handle in a general-purpose rate limiter, because it depends on the actual call you make. The rate-limiter doesn't make the call,...

Firefox with blocking third-party cookies:  Disqus works fine in same setup.

> Btw, all of this seems to work fine if domains related, i.e. www.example.com and remark42.example.com yes, for same domain it works, i.e. `comments.foo.com` can be used in `foo.com`, but...

@igoradamenko why do you need to use iframe?

Why you treat self-hosted solution as third-party? You already load some JS, so what the problem to do all job within this file? What vectors of attack you considered?

@igoradamenko with preact, post-css/sass/less, bem-like approach, plus shadow dom (about 80% support) you can build mature solution for conflicting styles/js problems. I believe you can do it :+1:

@Reeywhaar at least user can see comments in such case, and user can leave comments. So as quick fix it's good solution.

So what we should do: Generate `bootique.sh` for every application (with meta info inside). Looks like build plugin or bootique module best for it. Generate `bootique-completion.sh` once for all bootique...