Update to layer 123 again (79f6da2 by Lonami)
Try to fix new custom.Message again (b85f50e by Lonami)
Fix patched import (acb066a by Lonami)

Fix messages.search accidentally being used over getHistory (23041f3 by Lonami)

Move Message redefinitions back to patched (9a47fdc by Lonami)

Fix definition typo in patched module (845fe88 by Lonami)

Fix TypeNotFoundError was not being propagated (8f0de3d by Lonami)

Update proxy docs and license year (75db9f7 by Lonami)

Fix download of PhotoSizeProgressive (b0158b3 by Lonami)

Correctly sort PhotoSizeProgressive thumb size (73b9de2 by Lonami)
Handle progressive size in _photo_size_byte_count (b102f1f by Lonami)
Update file.size to reflect the size of the largest thumbnail (ff3c21c by Lonami)

Fix patched module was never automatically imported (0e8bd82 by Lonami)

Update to layer 124 (#1708) (2c2a07d by AndrewLaneX)

Update message to include ttl_period (0d05d0d by Lonami)
Add new event types to AdminLogEvent (175b30f by Lonami)
Add a new docs page for Chats vs Channels (b475a2e by Lonami)

Fix invoking requests ordered (a955138 by Lonami)

Handle DestroySessionRes (292a36f by Lonami)
Fix setting logout result was not checking for future cancellation (4c771bf by Lonami)

Version 1.20 (view new and changed raw API methods)

Update to version 1.20 (d9691c9 by Lonami)

Use tgcrypto if available (#1715) (42cc9e6 by igerzog)

Don't omit False flag values from serialization (8724949 by Lonami)
Update known errors and error message (3ee94bd by Lonami)

Support clicking buttons that require password (bfa7e4c by Lonami)

Warning to everyone storing user identifiers

If your code is storing the user_id or sender_id in a database, make sure to use the type "long" or "int64". The user IDs will soon become larger than 2³¹ - 1, so they will not fit in a signed int32 type.

We recommend using int64 and not uint32 to prepare for whatever may happen in the future.

Telethon will accomodate to this change by reading and serializing the identifiers as uint32 (thus gaining an extra bit of size). For more size, Telegram will need to change the schema, so this is the best it can do for now.

Python itself does not care about the integer size, the session files also handles large integers, and so does JSON or pickle, so no changes are needed here.

You only need to worry about this if your database stores it as a signed integer 32-bits wide. If you're not storing user IDs anywhere this does not concern you.

See https://t.me/BotNews/57 for the official statement and more information.