Fix add_admins property of custom.ParticipantPermissions (#3132) (45ed665 by ZubAnt)

Add new known RPC errors (#3134) (6a1f29d by SpEcHiDe)

Fix InlineQuery.event.geo returning None (bc6bcd3 by Lonami)

Handle non-user bans when iterating banned participants (9285e50 by Lonami)
Wrap requests in InvokeWithoutUpdatesRequest if no event handlers (49713b2 by Lonami)

Fix pin_message not returning Message on PMs (1e6be28 by Lonami)

Update docs to reflect current length of login codes in test servers … (2ea3153 by Newbytee)
Document new known RPC errors (#3137) (0a4b827 by SpEcHiDe)

Add Button.buy and Button.game (#3141) (9830c4e by New-dev0)
Include "chat" attribute in processing entities (#3133) (828cf2d by painor)
Add support for scheduled messages in iter_messages (#3127) (befba11 by New-dev0)

Change the way no_updates mode is enabled (2cb6cd5 by Lonami)
Include full request on the cause of RPC errors (8c56f95 by Lonami)

Update ChatAction to include MessageActionGameScore (#1651) (022c1db by Sunda001)

Update to layer 132 (#3142) (2182e7f by SpEcHiDe)

Implement Sticker Choosing Action (#3144) (391fbab by New-dev0)

Update to layer 133 (#3155) (28d3d4b by SpEcHiDe)

Telegram is changing user, chat and channel identifiers to occupy 64 bits instead of 32 bits!

If you were storing these values with an explicitly fixed size, you might want to consider updating that code to deal with long or i64 instead of the old int or i32 sizes.

Previous discussion: https://t.me/TelethonUpdates/1175 (and the follow-up, https://t.me/TelethonUpdates/1178)

Update documentation and list of known errors (3f5f5db by Lonami)
Add ttl parameter to send_file (2e1be01 by Lonami)

I'm steadily making progress towards version 2.0 of the library (after several years of waiting), so you might see a few polls pop up here over the next few weeks, where I see arguments in favour of a specific change, but the community may disagree for some reason (if you do, please argument why in @TelethonChat). So here it goes.

Note that version 2.0's primary goal is removing oddities (and necessarily breaking old code for the better). You can see progress in the v2 branch of GitHub, and the current list of breaking changes in v2-migration-guide.rst. Please do raise your voice if there is something you largely disagree with (and "ugh you're making me change my code!!1!" is not a good argument).

Poll #1. How should the output of __str__ and __repr__ change? (Sorry, but it needs to be public or bots would ruin it again.)

The current output of obj.stringify() is as follows:

InputPeerUser(
  user_id=123,
  access_hash=456
)

The current output of __str__ is as follows:

InputPeerUser(user_id=123, access_hash=456)

And the current output of __repr__ is as follows:

<telethon._tl.InputPeerUser object at 0x7f9f870d5fd0>

—

The idea would be for __str__ to be:

InputPeerUser(
  user_id=123,
  access_hash=456
)

And __repr__ to be:

InputPeerUser(user_id=123, access_hash=456)

The old __repr__ output isn't really useful. The only argument for keeping it is to not spam the REPL when using interactive mode. The old __str__ is hard to read, because objects get really big. Please vote on the options that apply.

(To whoever is using bots to vote on this without even looking at the message, thanks for ruining the way I gauge interest in a change, and I hope you get banned.)

Third-party developers using the Telegam API are required to support and properly display official sponsored messages in their apps by December 15, 2021.

https://corefork.telegram.org/api/sponsored-messages

ℹ️ @KeralaGramChannel