waffle

@Henriquelay #1023 was merged, you can rebase on master and this should be mergeable

https://github.com/teloxide/teloxide/pull/1007#issuecomment-1941440013 @teloxidebot label +S-blocked

For some context: the two main reasons why we did not do something like that before are - you can't impl setters on `Request` since they will overlap[^1] - we...

For context /2: _the_ idea is to keep the way users call requests (`bot.method(x).optional(y).await?`) and to keep all the features (opt-in things like throttling, default parse mode, etc) but make...

I think what @HKalbasi is trying to highlight here is that dialogues are usually short lived, so in a lot of cases it does not matter much if we lose...

I think my biggest concern here is that this requires quite a bit of design & implementation work. Given our capacity I don't think we'll be able to get to...

I'm not really sure if that's useful. Most of the bots I've seen, usually send a single message to a chat at a time, so there is simply nothing to...

Oh, I see! Yeah, for single-group notification batching like so makes a lot of sense (I also have a bot like this lmao). I _think_, this can be implemented as...

You should switch to the `dev` branch of this repo, it contains the `teloxide-core` source code.

I don't think that we can make a single abstraction that can be used by both throttle and batcher. While they share some things, they differ a lot in details.