bemyak

A very shitty implementation that probably works only for my usecase can be found here: https://gitlab.com/bemyak/roll_bot/-/blob/0a13f0961dabc707738e9b19eeaad7c404ab6cf1/src/telegram.rs#L362-452

Why should this be an opt-in option rather than a default? The performance hit is rather minimal, but the benefit is that any message can be sent despite its length....

I totally agree. Can we just change the default behaviour of the `send()` method in the existing `Requester` wrappers? I mean, why would somebody prefer __not__ to split messages that...

Hi! I'm starting working to push this feature forward. The main issue currently is the SQL injection vulnerability. We definitely need to use prepared statements, i.e., replace all user-defined parameters...

@thunder-spb , ah I see now, thanks for the clarification. This is not planned but should be pretty easy to implement.

I've just run into the issue that this PR addresses. Any plans on getting it merged?

Friendly bumping @superdump and @alice-i-cecile to review this PR :heart:

Compressing is needed so that a diagram code (PlantUML, Diag, etc) could be compressed and sent to [Kroki](https://kroki.io/) or to the PlantUML public server (see the [compression section](https://plantuml.com/text-encoding#82af841589057aa8) in docs)....

Yes, right now I'm using the `load_data` function exactly as described in the [Zola docs](https://www.getzola.org/documentation/templates/overview/#remote-content). This change will allow me to construct a GET request instead of POST, so it'll...

An example use of this filter is like this: in .md file: ```plantuml {% plantuml(comment="simple diagram") %} participant Zola participant Kroki Zola -> Kroki: POST /plantuml/svg\nContent-type: text/plain\n activate Zola Kroki...