@MrAldisaADS

My Android peers are all (?) on #Conversations or #Quicksy.

@delta

Designing top-down from the UI/UX is a good idea. It is, however, probably not a USP of Delta Chat. TTBOMK, at least #Conversations, #Dino and #Kaidan, have been developed with the same mindset.

But they do not share a common framework like Delta Chat. Everyone uses their own protocol implementation (in Java, Vala/C, and C++, repectively), which results in more work and potentially more bugs.

@vggonz

Para Android: #Conversations por @daniel o uno de sus forks.

Para iOS: #Monal por @Monal o #SiskinIM por @tigase.

@vascorsd I had something similar to that happen to me recently as well. I'm using a #prosody server, and I have my:

archive_expires_after = "5w"
... set in /etc/prosody/prosody.cfg.lua

Messages should be archived for 5 weeks.

Then messages sent in Gajim on one linux laptop were lost, when a second #Linux laptop who was subscribed to the same group, was turned off (absent from receiving messages) for 3 weeks. 2.75 of the 3 weeks worth of the group messages (where the laptop was turned off) silently never showed up, when #Gajim was re-opened on the second laptop.

This bodes very badly for me recommending XMPP to others. I now consider #DeltaChat to be a secondary choice, should something happen to #Signal (which is currently my privacy-respecting Messaging app goto).

Other clients who chatted in that same group, BTW: the latest stable #Monal in #iPadOS, and #Conversations in #Android

Prosody version is 13.0.0-1~bpo12+1, backend is sqlite, Gajim is 2.1.1. It was a private MUC, and OMEMO was used as much as possible.

#XMPP

#XMPP Events

#Berlin XMPP #Sprint: Devs from #DE, #FR & #UK featuring #Conversations, @dino, @ejabberd @kaidan #LiveDashboard, #Macaw, @Monal, #Renga and @prose
Sponsors: #XSF, Ammonit Measurement GmbH & @wikimediaDE

#chat #standards #interoperability #jabber #federation #decentralisation

Alt...

Developers at work at the XMPP Berlin Sprint

Im Ausland / auf #Reisen ist ein Smartphone jedoch sehr hilfreich.

Erst einmal wegen der Möglichkeit eine Offline Karte zu verwenden (via #OSM). Gerade beim #Wandern durch den Dschungel kann es hin und wieder sehr praktisch sein - besonders wenn man den Weg nicht erkennt.

Die zweite APP ist ein Messenger. Einmal um miteinander zu telefonieren, aber auch für Videocalls in die Heimart. Dies lief mit #Conversations einfach super!

Vielen Dank an den Entwickler! Selbst mit relative schlechtem Netz lief alles sehr gut! Wir haben zum telefonieren ausschließlich Audiocalls via Conversations verwendet.

#XMPP

Message Displayed Synchronization should work with #conversations (Android) and #monal (iOS) and of course with Gajim.

#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)

#prosody #conversations #gajim #dino #snikket #monocles #monal