Official channel for updates about Telethon. Join our groups: • English: @TelethonChat • Russian: @TelethonRussian • Off-topic: @TelethonOfftopic Find useful snippets at @TelethonSnippets2
Periodically save update state (#4071) (68ea208 by Kacnep89)
Читать полностью…Fix conversion and time zone issues (#4072) (a942b02 by Kacnep89)
Читать полностью…Add file IDs section to the FAQ (6bc7245 by Lonami)
Add docs warning to file.id about it not being maintained (b68c1f4 by Lonami)
Remove mentions to methods in generated TL ref (b87a8d0 by Lonami)
Expand documentation on using the raw API (1f79f06 by Lonami)
Move working with messages to the wiki (f334d5b by Lonami)
Читать полностью…Fix ChatAction for groups with hidden members (4de1609 by Lonami)
Читать полностью…Users of unofficial clients are having trouble logging into their accounts
Earlier we reported that starting from February 18, when authorizing in unofficial applications, users will not be able to request authorization codes in the form of SMS or phone calls, and that such codes will only come in other active sessions.
To date, the editors know that:
1. The first messages from users of unofficial applications that they cannot receive an authorization code in the form of a phone call or SMS began to arrive only on February 20-21.
2. Many of these users do not receive authorization codes even in active sessions: the user logs into the account in the official application, then starts authorization in the unofficial one and ... nothing happens: the code does not come anywhere at all.
We continue to monitor the situation.
In case you still haven't seen it, remember that it is no longer possible to request SMS from Telethon, or even sign up. There will be an update printing a deprecation warning if you try using those methods eventually.
Читать полностью…Prevent publishing to PyPi if tl.telethon.dev is out-of-date (610b8c3 by Lonami)
Читать полностью…Version 1.27 (view new and changed raw API methods)
Читать полностью…Change maximum photo size to 2560px (#4024) (1f8b590 by Nick80835)
Читать полностью…Apply pts returned by some additional requests (d81eb0b by Lonami)
Читать полностью…Sort RPC error data (6332690 by Lonami)
Add script to sync errors with Telegram's JSON (7a74ded by Lonami)
Sync list of known errors with Telegram's JSON (94cc897 by Lonami)
Fix PERSISTENT_TIMESTAMP_EMPTY for new entries with pts 1, count 0 (6d2a5da by Lonami)
Bump to v1.26.1 (979e381 by Lonami)
Update to layer 150 (7288c99 by Lonami)
Fix payment.py example (#4005) (061a84b by yumupdate)
Читать полностью…Introduce trace-level logs to MessageBox (c72c7b1 by Lonami)
Читать полностью…Implement progress_callback for sending albums (33c5ee9 by Lonami)
Remove dead code from send_file (0f7756a by Lonami)
Update to layer 155 (177386e by Lonami)
Handle invalid buffers at protocol level (f3414d1 by Lonami)
Propagate errors at the connection level (acd3407 by Lonami)
Handle errors at connection level (be59c36 by Lonami)
Handle timeout error during getDifference (516a2e7 by Lonami)
FYI: Telethon's mode with updates disabled relied on invokeWithoutUpdates
, but apparently that's not intended to work. Probably another thing to deprecate.
Slightly improve documentation (0563430 by Lonami)
Deprecate force_sms and sign_up (07a7a8b by Lonami)
If you're having trouble signing in, this may be why:
Читать полностью…Support Message without client as inputs to forward_messages (acfde71 by Lonami)
Читать полностью…Update to layer 152 (6dece6e by Lonami)
Bump to v1.27 (daf21f1 by Lonami)
Fix downloading vcard and webdoc with Path (9f077e3 by Lonami)
Читать полностью…Wrap init request in invokeWithoutUpdates if requested (cc3d25e by Lonami)
Читать полностью…Ignore improperly formatted errors from Telegram's JSON (c932d79 by Lonami)
Propagate account being logged-out errors (fb97a8a by Lonami)
Stop using asyncio.get_event_loop() (83bafa2 by Lonami)
Version 1.26.1 has been released which should fix PersistentTimestampEmptyError
. Thanks to everyone who reported the issue.
The problem occured when a new channel was created and an update for "message read" arrived before "new message", which caused Telethon to initialize the state for the new channel as 0, which led to the error above. Telethon now knows why and when it happens, and correctly sets the initial state as 1 when this occurs (Telegram seems to be aware of this issue, as it sends the second update with a value of 2 instead of the expected 1).
Fix messagebox state trace was not logging the object (a8ce308 by Lonami)
Promote messagebox warnings to errors (59ffad0 by Lonami)
Add more debug traces to the messagebox (e750eb7 by Lonami)
Change updates add_done_callback to discard tasks more reliably (5080715 by Lonami)
Читать полностью…