1. Client experience & feature parity
Users keep comparing how well each protocol works on desktop, mobile, and in terms of UI polish.
- “Most of my contacts made the switch, and I’m now at roughly 95 % Signal for day‑to‑day conversations.” – skerit
- “Element is terrible, and many contenders are better in a way or another, but all lack some essential feature to turn them into practical alternatives.” – ezst
- “Signal Desktop app is sluggish… occasionally clicking and dragging images onto the application will cause it to freeze and eventually crash.” – DaSHacka
- “FluffyChat works on Matrix and has funny stickers and emojis.” – simgt
2. Trust, security, and federation
The debate centers on who controls the data, how encryption is handled, and whether the network can scale without a single vendor.
- “Signal is openly opposed to federation and to letting alternative clients use their server.” – ezst
- “Telegram group chats have no E2EE, private messages aren't E2EE by default.” – zadikian
- “Signal is still one company running one service. If they shut down tomorrow or change direction, I’m back to square one.” – morning‑coffee
- “XMPP had rather bad name… unsuitability for mobile clients, absence of end‑to‑end encryption.” – zajio1am
3. Self‑hosting vs. network effects
People weigh the effort of running their own server against the reality that most contacts stay on big‑brand apps.
- “I’ve been running a matrix server for about 2 years for family. It’s… ok. Clients are bad.” – WD‑42
- “ejabberd is a bit overkill for a few people though. Prosody could be easily set up in 15 minutes or less.” – petre
- “Self‑hosting federated instances like this is pretty interesting way to scale.” – iamcalledrob
- “The only good solution would be if all messaging apps used the same protocol so everyone could be reached.” – elminjo
These three themes—client usability, security/federation concerns, and the tension between self‑hosting and the dominance of centralized services—drive the bulk of the discussion.