Lonami
Oh, thank you for clarifying what's going on! It makes sense now. I'll let up to you whether to close this or leave it open to track improving the message.
Maybe it could be added to the documentation? "This error can occur due to various reasons, such as trying to decompress invalid data, data with a gzip header, etc."
I don't think I'll get to this soon, but you seem to have figured out the problem, so feel free to send a PR.
I would need to see if the logs mention "gaps" and the library attempted to recover. Never checked how it behaves if Telegram delays an update which is deleted before...
> I'm using master branch of the library from Sep 29, 2023 (5cee34a) Might be worth to try on a newer version. It may have been fixed. Otherwise, if you...
I don't think I'll be able to look into this any time soon. You could clone the project and try to remove that logic, see if it helps.
9c8d738f3622bcf9935ea13dfbd80418ed7addca should fix a pretty serious bug (after an error, when the state is reset, the read buffer was always empty, so any read attempts into the empty buffer would...
And if not, we have the previously-linked issue to discuss this on.
> If `input_user` is not open, how should the `user_id` field of the `InputMessageEntityMentionName` structure be used? Is there a better way Telegram's current syntax for inline mentions is using...