I has improved quite a bit. The phone app still requires navigating over its settings to get less battery consumption, and having ntfy or any other unifiedPush notification provider available in the phone. But with the default configs, you get Jami working at least. I tried it before, and I found before synchronization between devices was a mess. Currently it just works. I still find it hard on immediate/urgent calls or messages, which might not happen when you expect, but other than that it’s working.

On the desktop, the default configs are pretty sane.

And the best part, it’s being actively developed. And the UI is undergoing through lots of improvements. So if usability is your concern, it’s getting better, and each release improves over the prior one…

The audit is true, but at least Jami didn’t make up its own crypto lib, it uses standard already in use crypto stuff. To there’s a huge difference there.

BTW, they are actually re-writing stuff… But yes, they need more recent audits…

Have you read it’s github front page?

This is an experimental cryptographic network library. It has not been formally audited by an independent third party that specializes in cryptography or cryptanalysis. Use this library at your own risk.

BTW, if you look at its issues (including closed ones, which most probably aren’t really closed) you’ll find pretty interesting discussions about its crypto not being right. That said, I’m not sure what irungentoo brings to the picture…

At any rate, if you’re looking for distributed messaging, I’d look into Jami. It also uses DHT and something similar to torrents mechanism. Jami is my only option so far for distributed messaging. There’s also Briar, but I don’t like it for regular messaging, particularly on phones (too much battery usage), neither its underlying technology, but if it’s to your liking, then that’s another option for distributing messaging.

What I post from lemmy.ml wouldn’t be seen there if that were the case, but it’s seen there, so that doesn’t seem the case…

BTW. I’ve already joined… That said, I see the same posts missing. Of course that doesn’t apply to one I made myself from lemmy.ml. There’s also a bot one from 9 days ago, but the rest are at least 1 month old…

pending for subscription, we’ll see, and while pending, still not syncing properly…

I’m all for Jami, and XMPP.

Jami is the GNU alternative, if you’re wondering

Also FYI: https://lemmy.ml/c/xmpp@slrpnk.net

yes

deleted by creator

XMPP, 🙂

The phone doesn’t poll, instead it goes to sleep, and gets awakened by the push notifications. Just like GCM/FCM ones. Part of the key thing, because not any one can self host, is that it requires very little information in comparison, and some providers are open source and even free SW. The one I use is ntfy, there’s the next cloud (next push), and not long ago you can use the conversation push service (up.conversation.im) through the Convesations xmpp client. I was aware of Conversations capable of becoming a unified push distributor, but actually was looking for it to use a unified push distributor instead.

But I was informed already it’s not necessary, and doesn’t make much sense, by being very low power consumer, even though it requires to keep unrestricted battery consumption on the background. So no issues by Conversations not supporting using a unified push notifications distributor.

It depends on the distributor:

https://unifiedpush.org/users/distributors

And how much info they collect. I understand the ntfy requires is really bare minimum compared to what GCM/FCM asks and collects.

On mobile, it’s sort of a needed if you one doesn’t wand to use GCM/FCM which is really bad privacy wise, and particularly needed on peer to peer applications, because they tend to drain the battery…

Some other benefit is that for those who can, they can self-host ntfy, nextcloud with unified push provider, and so on…

On the list of apps supporting unifid push, I even see element (matrix), but I don’t identify any xmpp one:

https://unifiedpush.org/users/apps

Yeap, I noticed it being a unified push distributor, actually in its settings on can find the option to enable it.

OK, I won’t worry about battery usage then. But the argument about unified push notifications not being useful, but the GCM/FCM actually found useful is somehow hard to understand. But I understand what you’re saying about battery usage. Thanks a lot !

If the distro supports apparmor, then firejail + apparmor offer together sandboxing for quite a set of applications (apparmor includes few profiles by itself, but firejal has quite a few, and one can enable apparmor on all, or the ones wnated). Arch has pretty good wikies about firejail + apparmor.

Jami doesn’t require a phone number, which is p2p. Xmpp (+ Omemo) doesn’t require a phone number and it’s federated… I mean, if a service is willing to rid of phone numbers, it’ll do totally without them.

Being using mull for so long, even when it was not available on f-droid official repos, but only divestos f-droid repo.

The only thing really bothering on mull is a config one really must change, security.OCSP.require, the default to true prevents reaching several sites. But other than that mull shouldn’t get in your way, and one can change other config to one’s liking if in need.

Jami with unifiedPush notifications is a pretty good option

Why not looking for distributed mechanism, which don’t depend on trusting central servers or particular instances on decentralized mechanisms, like jami, or similar?