A good app offers options. While most HN folk don't like Telegram's default, it at least gives you somewhat of a choice (and the user can force the E2E option even if the other party doesn't like it)(though they do not give the option to make all chats by default E2e, which is indeed a dark pattern). The other apps just shove possibly backdoored E2E down people's throats with no choice at all.
Your post is slightly ironic, considering Telegram doesn't give you any choice on using E2EE for groups or any chats for that matter, on majority of desktop clients. Know this: when you're not using end-to-end encryption, i.e. when you're using Telegram cloud chats, those chats are by definition as private as a backdoored E2EE chat would be. So one could argue they are front-doored by design.
This is an incorrect take. It's true that Signal's server code had not been updated for many months, but that doesn't have an effect on security as messages are end-to-end encrypted locally on the clients/apps. The client/app code had been consistently updated during this period.
Signal choosing not to federate isn't in the scope of this thread. IMO not federating is a guarantee of client quality. The last time I had a look at Matrix E2EE implementations, only Riot was barely usable. There was a ton of clients that didn't support it, didn't intend to, didn't have the confidence to go about implementing etc.
I know Telegram’s default is to give all the data to the server. But being honest about this makes them able to provide significant UX benefits. Backdoored E2E gives a false sense of security, and, backdoored or not, E2E’s UX sucks. (Also note that the backdoor/malware could be on any level of the stack; From WhatsApp’s plaintext backups, to NSO’s zero days.)
