mirror of
https://github.com/LonamiWebs/Telethon.git
synced 2026-01-08 09:40:48 +03:00
When a bot account sends a message, deletes it, and sends a new one, very reliably it would detect a gap, and as a result recover the second message it sent, processing it itself (because the hack with `_self_outgoing` cannot possibly work when catching up). Now certain `rpc_result` are also processed as-if they were updates (including the ones from deleting messages), which solves this gap issue. Not entirely sure if it's a hack or the intended way to do it (since Telegram *does* return proper `updates` for other RPCs), but it seems to solve this particular problem. Other requests such as reading history, mentions or reactions also return an instance of this type, but the `pts_count` should be 0, and at worst it should simply trigger a gap, which shouldn't be a big deal. |
||
|---|---|---|
| .. | ||
| _updates | ||
| client | ||
| crypto | ||
| errors | ||
| events | ||
| extensions | ||
| network | ||
| sessions | ||
| tl | ||
| __init__.py | ||
| custom.py | ||
| entitycache.py | ||
| functions.py | ||
| helpers.py | ||
| hints.py | ||
| password.py | ||
| requestiter.py | ||
| sync.py | ||
| types.py | ||
| utils.py | ||
| version.py | ||