Lonami

I personally don't think I'll find the time to do this but if you send a PR to build it on CI, I'll happily upload the artifact to PyPi.

Closing but if there's still interest on this someone might want to experiment removing: https://github.com/cher-nov/cryptg/blob/04a4faf55a891902b4c4a61f6805a9292b768175/.github/workflows/wheels.yml#L66 and seeing if it works (if it does I can merge a PR with the...

I'd prefer to avoid new features in v1. What would be the use case for this?

Why not make the call directly? This PR doesn't support `async`, and after it's set, if it changes later, it won't re-fetch them either.

`ChatAction` continues being a mess in v1 and I'm too afraid to make changes. I´d suggest using `events.Raw` if that works for the usecase instead.

I haven't given it much thought as it's not a priority for me. If you can find a way that's not very intrusive I'll happily merge it, because indeed having...

> I'm not sure if I'm doing something wrong. No, there seems to be an edge-case I failed to account for. I do not know when I'll have the time...

Thanks for investigating. Would you mind submitting a PR?

It is possible to extend the session format ([most recent change](https://github.com/Lonami/grammers/pull/301/files#diff-a1b09952affae15fd8ea75b9f63753a09e224d5a3eb5417c401cddb2a6b3a434)), however I'd actually be more interested in knowing why we don't continue after fixing the offset, because even if...

> if it is stuck or looping indefinitely (I don't see the difference between the two) By looping I mean constantly sending a message and reading bad message. But if...