I'm looking through some XEPs, looking for one that specifies that all requests sent from non-roster JIDs can be rejected.
(Yes, I use Xabber, not #Conversations, as my #XMPP client on #Android. Every time I try to use Conversations, I have a very strong reaction and end up deleting it. I think the most recent time is permanent. I just can't stand it.)
One thing I really wish #jabber app like #Conversations could do is ephemeral small group chats. The sort of thing where you just want to make one-off arrangements with a few people, or have a quick check-in to get on the same page, but you know you won't need to group chat for long enough to make it worth setting up a #MUC room. The fediverse can be useful for this, and Wire's group chat is better for this than ongoing team chat IMHO.
If #delta.chat (or a fork of it) added voice/ video chat using the #Jami protocols, allowing Jami accounts to be associated with email accounts, that might be the best of both worlds. A reliable, federated transport and storage for text messages, file attachments, and voice mails, and a fairly robust #P2P voice/ video chat experience (both one-to-one chat and group conference). Same if native #Jabber apps like #Conversations supported #Jami for voice/video chat.
@jcbrand#Jabber might get more uptake if every team focused on a serving a particular use case well, as #fediverse apps have been doing more recently (eg #Mastodon for micro-blog, #PeerTube for video, #PixelFed for images). Rather than a confusing foam of mostly identical, outdated IM interfaces, most of which get developed for a few years and then die. There are great apps with solid development teams, like #Conversations and #Conversejs, but these seem to be the exception. @Muto@debacle
@bortzmeyer@imacrea in theory, either protocol can be used for any kind of chat. But while the #Riot client is great for team chat, I haven't seen a #Matrix client with an instant messenger UI I would recommend for friends and family use. #Jabber (#XMPP) is the opposite. Apps like #Conversations (Android) and #Pidgin (desktop) are fine for one-to-one IM but I have yet to see a Jabber client that does group chat as well as Riot. This piece explains the differences well: https://blogs.gnome.org/tbernard/2018/05/16/banquets-and-barbecues/
@imacrea the best #XMPP app I've used in almost 20 years of testing is #Conversations on #Android. If there were XMPP apps with a similar or better level of polish for iOS, GNU/Linux, MacOS, and Windows, *and* the web, so users could sign up for a service and use a branded fork of the web interface without having to learn about server and client choice right away (as with email), it might be useable by mere mortals.
@tootbrute > wish more stuff had built in mesh server functionality...
I want to see a serverless app like #Jami with a UI like #Conversations (#XMPP app for #Android). That way, the #UX is as seamless as that of an app for a centralized service, but as with #BitTorrent, everyone who's running the app is also "running a server", in the sense of sharing bandwidth and processing power with the network.
We had an amazing meetup at the first day of #35c3. The developers of #K9 mail, #Tusky, #Öffi, #Newpipe and #Conversations were all there (and probably a few more I forgot)! Thank you all for coming.
@z428 Die Diskussion ist in der Tat schon sehr steinig. Aber auch hier zeigt sich bereits die #Abhängigkeit. Man kann sich doch über andere Kommunikationskanäle über Profile und Namen austauschen, z.B. via E-Mail sich die Namen schicken? Und wenn man via #Conversations einen neuen XMPP-Kontakt hinzufügt bekommt der Gegenüber das auch mit. Wir werden das bestimmt nicht ohne Weiteres aufbrechen. Aber früher oder später müssen "wir" (als Gesellschaft) auch Farbe bekennen: Wollen wir unabhängig sein? Oder wollen wir schlicht die Bequemlichkeit suchen? @majestyx
Clover is going on a trip today, will be away for a bit. So I created a restricted account on Susan's Android tablet, and allowed the following apps to be used: