Lonami Exo d81eb0b2e8 Apply pts returned by some additional requests ... 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.		2023-01-14 12:31:01 +01:00
..
connection	Stop using asyncio.get_event_loop()	2023-01-11 21:02:29 +01:00
__init__.py	Add type hints to all public methods in the client	2019-05-03 21:38:41 +02:00
authenticator.py	Add extra security checks during authkey gen	2020-01-14 12:12:55 +01:00
mtprotoplainsender.py	Fix-up missing loggers from f271316	2019-01-12 12:15:29 +01:00
mtprotosender.py	Apply pts returned by some additional requests	2023-01-14 12:31:01 +01:00
mtprotostate.py	Protect against potential replay attacks	2022-05-18 12:24:28 +02:00
requeststate.py	Avoid explicitly passing the loop to asyncio	2020-07-25 18:39:35 +02:00