V2 Roadmap

[Jahongir-Qurbonov]

Describe your suggested feature

V2 is great and the community is waiting for its stable version. We are willing to contribute if there is work to be done for a stable version.

Todos:

• Add QR code authorization
• Networking needs to be reconsidered
• Message entity parsing should be improved

[Lonami]

My plan for v2 was primarily to redesign the core of the library based on what I had learnt from making grammers, and use proper types.

As for the high-level API, my plan was to take what was most used from v1, and remove anything that didn't pull its own weight. This includes conversations and all ugly hacks used by custom types.

Honestly, v2 is probably not missing that much, but I'm sure it's also nowhere as stable as v1, network-wise. Another pain point is Markdown. CommonMark just doesn't cut it, as Telegram has many more formatting entities. This affects big part of the library and we need a better solution. We might just need to copy what the HTTP Bot API is doing for formatting.

[Jahongir-Qurbonov]

When can you review the network-wise? Better to copy Markdown from HTTP bot api in my opinion

[Lonami]

When can you review the network-wise?

Not sure. Telethon v1's network stack matured this much over time, and I suspect something similar will happen with v2.

Better to copy Markdown from HTTP bot api in my opinion

I'm hesitant. People might expect compatibility, which I'd rather not promise to maintain.

But, it's probably the best bet.

[Heshmatkhah]

Hi,
Thank you for your grate work.

Is v2 ready for production use?

People might expect compatibility

It's a major version update, do whatever you need to!

Thank you

[Lonami]

Is v2 ready for production use?

No, and I unfortunately do not know when it will be.