Easy to install, works on every platform I need it, super-simple bot support and the UX is very nice. You even have tools to make write-only groups (microblogs of sorts) and actual moderation tools for larger groups.
For a "community", I'd pick Discord though.
Matrix as a technology is a good competitor, but the UI/UX for every client I've tried rangers from "death by a thousand cuts" to atrocious.
Case in point: I got a notification about a message on a channel on my phone from my Element client. I open it and what do I see? Not the message. A "Syncing" -message that lasts longer than I can stand to wait. My phone actually falls back to sleep and turns off the screen while I'm waiting for it to sync. And after it has synced, does clicking the notification take me to the channel? Of course not and now I've already forgotten where the notification was from.
How come? It's completely proprietary and it's never been audited.
One paper tried to validate Telegram's protocol: https://www.researchgate.net/publication/346702021_Automated... That seems to have gone well. The mechanisms used seem very similar to the mechanism used in Signal's last audit from 2017.
Another paper only verified part of the protocol in a specific way: https://www.computer.org/csdl/proceedings-article/sp/2022/13... This last paper found flaws that should allow some side channel attacks (though I find it hard to believe that 3 microsecond differences can be measured against the client unless the attacker controls the server) but concludes that the protocol should be secure enough with their proposed fixes, which Telegram seems to have implemented; the problems mainly stem from implementation bugs, something the Signal protocol wasn't necessarily checked for during their extensive audit.
Based on this research I can't say I can find much wrong with mtproto2. It's proprietary in the same way the Signal protocol is proprietary, in that it was originally invented for a specific purpose inside a specific app. Just because nobody has bothered to copy the protocol to their app like WhatsApp did with Signal doesn't mean it's any more or less secure.
In the context of an app that can't encrypt group messaging and doesn't encrypt private messaging by default, I don't think focusing on the potential insecurity of mtproto2 makes sense. Telegram made some dubious, foolish security theatre ("hack our server and win a prize!") but on a protocol level there are no glaring mistakes that necessarily invalidate the protocol itself. The big problem here is that only a fraction of users actually use this seemingly-secure protocol on the first place.
They are both documented, both have source code of implementation available.
They even took some ideas that people in the crypto had pointed out and updated their mtproto protocol to 2.0 https://core.tlgr.org/mtproto
I always found it funny - here's a privacy focused alternative to Whatsapp! But we'll need your phone number, first. Why? Oh, y'know, to limit spam and stuff. 'cuz that definitely can't be done any other way.
Sure, I can get prepaid cards. Or I can just use Whatsapp. If I do anything illegal, I can do better than Telegram.
I feel that the average person would be inclined to use signal more if it required a phone number than otherwise.
Same procedure as with N26 and ING online banks, though the latter didn't work due to connection problems so I had to do it at the post office.
I like prepaid because I avoid contracts whenever I can. And I liked that I can get one fast.
I understand the reasoning - they can tie an identity to any SIM card and find you pretty fast if your number/IMEI pops up in some suspicious communications, but still, privacy blah blah.
This is the country that recently was against the EU wide chat surveillance directive that surfaces every few years now.
Individual retailers and service providers may have different policies, of course.