Dan
Currently, Pyrogram will ignore all the updates that arrived while a client was offline, that is, a client that was manually stopped (in case of internal reconnections the missing updates...
## Checklist - [x] I believe the idea is awesome and would benefit the library. - [x] I have searched in the issue tracker for similar requests, including closed ones.
Currently, we have: - `get_users` (plural) to get 1 or N (up to 200) users. - `get_chat` (singular) to get one full chat only. The API should be more consistent...
People complained `get_messages` was broken (#288), but the reality is they get confused by the fact that the method has optional arguments, which would lead to ignore them. A solution...
The current Message type should be reused for such draft messages.
It would be nice to have an extra arg to tell each send_* method used for uploading media to automatically send the respective action ("upload_video", "upload_video", etc.) while the upload...
Discussion around here https://t.me/PyrogramChat/139928 Basically, add a `File` object and a `message.file` attribute to store common metadata for downloadable files, like `.file.id`, `.file.ref`, `.file.size`, `.file.type` ("photo", "video", "audio", ...), `.file.mime`...
Reference: https://t.me/PyrogramChat/141619