Lonami Exo 6d2a5dada5 Fix PERSISTENT_TIMESTAMP_EMPTY for new entries with pts 1, count 0 ... Because Telegram can't actually use 0 for the pts, it uses 1, even if the count is 0. This forces the next update to use 2, or else it could not be fetched when using an offset of 1 (despite the count being 0 on the first update, which should not have bumped the second update to use 2). This caused Telethon to create an initial state of 0 for the new entry (and also "incorrectly" detected following updates as gaps, which would quickly trigger the call to get difference with a bad pts). Now Telethon is aware of this special-case and will not initialize state as 0, even if that's not the "correct" thing to do.		2022-12-22 20:30:38 +01:00
..
__init__.py	Handle bans when getting difference	2022-05-23 11:41:59 +02:00
entitycache.py	Backport v2 MessageBox	2022-05-13 12:29:58 +02:00
messagebox.py	Fix PERSISTENT_TIMESTAMP_EMPTY for new entries with pts 1, count 0	2022-12-22 20:30:38 +01:00
session.py	Add repr to updates session types for easier debugging	2022-05-16 09:36:13 +02:00