evan-chaney / telegram-notifyrs Goto Github PK

Hi!

Since crate are provide only blocking implementation, it shoudn't bring WHOLE LOT hyper async code and block on it but should use
ureq.

Also, there must be some documentation, perhaps.

Ran into an instance earlier where the chat_id that I was issued was greater than i32. As per Telegram docs, they suggest that the chat_id may be greater than 32 bits but smaller than 52 and signed that a 64-bit integer or double-precision float type are safe for storing this identifier.