Add missing async when downloading from URL (#3222) (f9643bf by Nenirey)

Improve readability for readthedocs/concepts/entities.rst (#3259) (805898c by vladdoster)
Slight rewording of error message (#3256) (530284a by SpEcHiDe)
Add support for new invite link format (#3213) (674b7d6 by kdrag0n)

Proper usage of messagebox in update handling loop (0129192 by Lonami)
Fix messagebox porting errors (259fcca by Lonami)
Remove GitHub workflow (0d597d1 by Lonami)
Fix constructing PtsInfo for channels (de2cd1f by Lonami)
Fix update handling for channels (1f40372 by Lonami)
Process self-produced updates like any other (f1a517d by Lonami)
Handle TypeNotFoundError during gzip packed msgs (015acf2 by Lonami)
Persist session state and usage fixes (f547a00 by Lonami)
Reimplement catch_up (4b85ced by Lonami)
Add missing catch_up param to client init (3aa53dd by Lonami)
Don't store empty pts in messagebox (4b61ce1 by Lonami)
Fix reset_deadline check in messagebox (f7ccf8d by Lonami)
Properly load and save channel state (f775484 by Lonami)
Reintroduce keepalive pings in the sender (b0b1f30 by Lonami)
Review, unify and simplify retry_range usage (a25f019 by Lonami)
Add new features from new layer (#3676) (539e3cb by New-dev0)
Merge branch 'v2' (ed70991 by Lonami)

Avoid usage of __builtins__ in the generator (#3161) (d9e2a8a by penn5)

Fix flood_sleep_threshold was not being forwarded (4aa23cf by Lonami)
Use threads for factorization (3c7bb53 by Lonami)
Document more RPC errors (0eadca6 by Lonami)

Allow restricting channels (#3679) (7778e54 by New-dev0)

Regarding the annoying captcha in the documentation, the Read The Docs team has responded to me via email with the following:
--
Thanks for contacting us. This is an automatic CDN's protection feature from Cloudflare that we use to avoid DDoS attacks. When the algorithm detects weird behavior on a particular domain (for example, *a lot* of traffic in a very small window of time) it enables captcha protection.

I'd expect the captcha to be disabled soon once this "weird behavior" situation gets mitigated. Let me know otherwise.
--
If this is very, very annoying, one can always clone the repository and build the documentation offline (with make html -e, after installing the necessary dependencies).

Remove input_peer parameter from get_me (d426099 by Lonami)
Make raw API types immutable (070af28 by Lonami)
Make upload_file private (f2ef0bf by Lonami)
Begin unification of event builders and events (9726169 by Lonami)
Rework methods to manage event handlers (0802f7e by Lonami)
Fix date usage in messagebox impl (05457ea by Lonami)
Fix saving entity types in sqlite (a16c397 by Lonami)
Implement dispatching events (a1fe805 by Lonami)
Introduce some filters (055eca4 by Lonami)
Add proper warnings when applying filters to updates fails (a3a60e6 by Lonami)

If you're experiencing slow upload or download speeds in Telethon, cryptg~=0.3 with binary wheels has (finally) been released on PyPi thanks to the work of a68366 to fix CI.

What this means is you can upgrade cryptg to get improved upload and download speed as some have reported (over 10MB/s both directions) with the following command:

pip install --upgrade cryptg~=0.3

Recently https://github.com/LonamiWebs/Telethon/issues/3753 has resurfaced. Due to seemingly sudden interest, I have pushed a fix to the v1.24 branch, which will eventually be a proper PyPi release. This also contains changes to update handling. Neither of these changes have been tested extensively (as in, by a large amount of users yet), so please report any new issues if you do find them.

If you want to install these changes, you can do so with the following command:
pip3 install -U https://github.com/LonamiWebs/Telethon/archive/v1.24.zip

The reason for the longer delay between updates was that I really wanted v2 finished, but other issues are essentially forcing me to maintain the v1 branch for a little longer. I do not plan to add new features to v1. These will still have to wait for v2. But fixes for larger issues such as these should come to v1 for a while longer. Unfortunately v2 is still ways to come, until I can get enough motivation to get back to it.

Also note that the v1.24 branch has had its layer updated (if you use raw API somewhere, some things may need updating).

This branch has been updated to the latest layer (meaning, you can now detect premium users). You can use the same command to update.

Version 1.25 (view new and changed raw API methods)

If you were using the v1.24 branch, the above update contains virtually no changes. But now that branch is available in PyPi for the wider public. Please report any bugs you may find with the new update handling in GitHub. The latest layer is also now available (144). You can use this version to send reactions and other premium features if you are premium, with raw API.

https://tl.telethon.dev/ has been updated to include these new raw API methods.

I could not test some of the fixes since I was unable to reproduce many of the issues people reported with regards to update handling. Please be sure to report any bug you may find with regards to update handling! In particular the scary-looking "Fatal error handling updates" which mentions ENTRY_SECRET, since this was the most common by far, should be fixed, but if it's not I would like to hear about it.

v1.25.2 was released earlier today. It contains two tiny changes:
• Updated list of errors and updates log messages to include the channel ID (otherwise the log messages were useless)
• get_dialogs (and iter_dialogs) were not filling the channel pts correctly (needed so that updates from them could be fetched properly). This is now fixed.

Nothing major but when reporting bugs please do so with the latest version (currently v1.25.2).

I've also (hopefully) fixed @TelethonianBot to start posting commits here (it was broken because the same code was used for StackOverflow which had started causing 403 on the requests).

Lower severity of some log messages during update handling (d2b1c3e by Lonami)
Add CHAT_FORWARDS_RESTRICTED to known errors (7f472ee by Lonami)

Fix get_running_loop usage in Python3.6 (#3941) (908375a by salismazaya)