That’s also a lie. There is no way it would be impossible to remove the protection code (or parts of it) or make it not execute. That alone makes him a clown.

Seems it’s fixed now?

It actually seems more like a windows 10 compatibility dilemma for developers. You can support older systems but it would require some effort. The problem is not the absence of some specific certificates, but the absence of newer ciphers altogether.

This does give security but also removes backwards compatibility with some clients that might be important for some websites.

Wording is confusing. Here are some better takes that sound valid and are true:

• Telegram’s e2ee is only available for chats of 2 people, and only on official mobile client.

• Telegram’s e2ee is a feature you have to enable whenever you need it (called secret chats).

That bad encryption was not cracked for now. The other one, that is used to process chats between 2 users in end to end mode, can’t be enabled by default because it assumes no history is kept and no support for group chats.

Also, the arrest doesn’t seem to be related to any of the things you mentioned. If anything it shows there are no ways for (certain) governments to affect the messenger, for now.