@ulfi I can relate, as I recently tried out #monal for #iPadOS. While praiseworthy for being the honest effort that it is, it doesn't have anywhere the bling-bling that the other chat apps have.
At this time, emoji reactions don't work yet in Monal, so with that shortcoming alone, I can't recommend #XMPP to any of the #Apple followers in my life. They almost certainly have high expectations for any new apps, for such functionality
Message Displayed Synchronization should work with #conversations (Android) and #monal (iOS) and of course with Gajim.
@getalifemike @notjustbikes I, for one, highly appreciate nlnet's sponsorship of the #Monal #XMPP client - a crucial piece of the larger XMPP ecosystem. In #Canada, where I'm from, 60% of #Canadians have iPhones! 
@menel Thanks! Their blog mentioned there is some funding from NLnet for Monal. That's great. It also occurred to me the Github issues for #Monal are public:
https://github.com/monal-im/Monal/issues
#xmpp
#XMPP enthusiasts out there: what would you say the ultimate Achilles heel of the XMPP ecosystem is, at present? Fragmentation of clients? What?
My sense is that it's this: when one goes to store an XMPP address in one's addressbook, there doesn't seem to be standard way to store an XMPP address. #Android doesn't have that as an allowable field, and #Thunderbird and #Nextcloud have an "Instant Messaging" field, where the type can be set to "XMPP". But are these two compatible with each other when trying to sync between them? Edit: Yes, but there's a catch: *the XMPP address must be prefixed with "xmpp:"*
So "user@foo.bar" is not an OK XMPP address, but "xmpp:user@foo.bar" is.
Then to make matters worse, now there's a wish to change the labeling of "XMPP Address" to "Chat ID": https://gultsch.social/@daniel/114012904576436518
It might be a long time before the address synchy-ness ever works again between Android <-> #Davx5 <-> Nextcloud <->Thunderbird
Note: Android allows a "Jabber" type for an IM address, where you *don't* prefix the address with "xmpp:".
(#DeltaChat gets to gloat hard here, as they have plain-old email addresses)
@eliasp
Es gibt nicht nur Signal. Siehe Artikel & Empfehlungen (abhängig von Sicherheitsbedürfnis & Vertraulichkeit) - Quelle:
https://www.kuketz-blog.de/messenger-matrix-uebersicht-vergleich-der-aktuellen-messenger/
Folgende Messenger haben eine Empfehlung bekommen - hier zusammengefasst nach #Zielgruppe, #Herkunft & #Betriebssystem (#Mobil / #Desktop):
1) #Threema - #Einsteiger - #Schweiz - für iOS & Android & Desktop (Win, macOS, GNU/Linux)
2) #Signal - Einsteiger - #USA - für iOS & Android & Desktop (Win, macOS, GNU/Linux)
3) #Monal (#XMPP) - #Fortgeschrittene - US / DE - für iOS & Desktop (macOS) - siehe https://de.m.wikipedia.org/wiki/Liste_von_XMPP-Clients
4) #Element (#Matrix) - Fortgeschrittene - #GB / #DE - für iOS & Desktop (diverse Clients für Win, macOS, GNU/Linux - siehe https://matrix.org/ecosystem/clients/)
5) #Conversations (XMPP) - Fortgeschrittene - DE - für Android (siehe https://de.m.wikipedia.org/wiki/Liste_von_XMPP-Clients)
6) #Briar - Nerds, Aktivisten, Journalisten - int. Team - für Android und Desktop (Win, macOS, GNU/Linux)
Link zur Messenger - Matrix:
https://www.messenger-matrix.de/
@methuselah #Conversations for #Android is indeed worth advocating as an #XMPP client, *when it comes to its full support of "multi-user chat"*. But as to #Monal for #iOS? Be careful what you assume: its "multi-user chat" support is only said to be "partial" at this time:
https://xmpp.org/software/software-comparison/
Edit: #Siskin (for iOS, is GPL3), is said to have "complete" support for multi-user chat.
After taking a closer look at #XMPP clients for the #linux desktop, there's this frustrating "tie" for finding a favorite.
#Dino, which is likeable for being able to do video and audio calls, only has limited support for multi-user chat (complete with fancy moderation tools). These audio and video calls it can do are AMD64-only at this time.
#Gajim, which is likeable for being able to do multi-user chat well (with great moderation tools), alas, can't do audio and video calls to the other XMPP clients (like, say, #Conversations, as they use a newer #WebRTC-based method now).
So there's this strange situation where one is tempted to use both at the same time.
My takeaway is that #Conversations for #Android is the only xmpp client that I would possibly and carefully recommend to family and friends at this time, as it can cover all of the above. (#Monal on #iOS/#MacOS only has "partial" support for Multi-user chat, BTW.)
Yes I'm aware of the existence of Snikket, Quicksy, and Prav. No need to chime in on those.
@famfo I looked at the "XMPP Software Comparison" page:
https://xmpp.org/software/software-comparison/
...and put my 4 favorite #XMPP clients in there: #Conversations #Gajim #Dino and #Monal. It compares compatibility across many XEPs.
Alas, when it comes to #OMEMO, no distinction is made as to the version of OMEMO.
@mastodonmigration Obligatory reminder that #Signal relies on a centralized and proprietary server, and does not belong here.
Users of #WhatsApp #Telegram #Discord #Signal and #Threema etc should use #XMPP instead, which is #FreeSoftware and federated.
Users - check out #Quicksy (Android and iOS), #Prav, #Conversations, #Cheogram, #MonoclesChat, #Gajim, #Movim, #Monal...
Self-hosters, check out #Snikket.
Learn more with this user's guide -
https://contrapunctus.codeberg.page/the-quick-and-easy-guide-to-xmpp.html
@janantos @nirro @bojkotiMalbona
TTBOMK, you can have A/V calls between #Conversations by @daniel (Android), #Dino by @dino (Linux, Windows), and #Monal by @Monal (iOS, macOS).
ugh, the new #monal icon looks like there’s always unread messages
for 