

deleted by creator
Please also consider following me on https://mov.im/?blog/debacle@movim.eu
deleted by creator
The #Jabber feature sets are defined in the compliance suite, e.g. here:
“XEP-0479: #XMPP Compliance Suites 2023”
https://xmpp.org/extensions/xep-0479.html#im
Many Jabber clients do end-to-end encryption by default. I would not care too much in the age of #surveillance directly at the source, i.e. on the device 🤷
If you want an even more coherent feature set and also be sure, all your clients encrypt by default, your best bet is #Snikket by @snikket_im. Highly recommended!
YMMV, but my minimum requirements were:
Federated just like lemmy or mastodon or email, so I can choose a server or even selfhost.
First class clients for Linux available, not only Android/iOS, no Electron bloatware.
No phone number involved.
That rules out Signal, Whatsapp and some more. Matrix fits. However I prefer #Jabber a.k.a. #XMPP. Matter of taste, I guess 🤷
PS: “Note to yourself”, incl. file upload, is supported by all servers and most clients, AFAIK.
The problem is, that none of the grocery stores or street markets or supermarkets in my area accept Monero 🤷
deleted by creator
@HiddenLayer555
If file transfer is an issue with Briar, maybe #Jabber/#XMPP is better suited for our use case?
By default, modern clients use XEP-0363, i.e. file is uploaded to your server (typically encrypted) and download link plus decryption key is sent to the receiver.
However, files can also be transmitted directly using XEP-0234. This works only, if both parties are online at the same time. Clients can fall back to this method, e.g. if files are too large for the server.