Is it ok? Is there something else you recommend instead? I tried nextcloud talk and it was pretty bad. Jitsi was ok but self hosting it looked complicated. FOSS only, of course.
The only issue I have with GNU-Jami <u>is them checking for Unique Usernames</u> it’s annoying & problematic<br> You have the DHT (“Distributed Hash-Table” based on Ethereum) & that should be enough<br> why even check for the uniqueness of the attached username ?<br> The DHT should be the ID & names need to be detachable from it<br> & we can’t even edit the username once registered
Otherwise it’s high-quality Libre/Free-Software but with room for improvements
I found it to be inconsistent about receiving messages on Android.
Having good luck with SimpleX at the moment.
I use Jami and love it. If you want to use it on a de-googled phone you may not get live notifications though, which is annoying if you want to use it for calls. The simplest solution is to allow it to run in the background but it also allows you to use selfhosted push notifications which is cool. I just let it run an accept the hit to to my phone’s battery. Jami is fairly easy to use and looks friendly too, which is helpful for getting non-technical friends to join you on it.
I struggled with Nextcloud Talk too.
Highly recommend Jami 👍
Just so you know you can get push notifications on Jami. Jami has been supporting unified push notification for a while now, but it’s opt-in, some might not opt for it considering reducing privacy a bit, as some actually disable the proxy and some phone specific feature intending to prevent battery exhausting too fast.
For unified push support you can take a look at jami’s article about its unified push support. I use
ntfyBTW.But isn’t UnifiedPush libre & privacy-respecting enough ?
It is open source, which is good, but ultimately it depends on the service provider as usual, what it logs and for how long. The good thing, is that by design there’s not much which can be collected.
But for a mechanism that is supposed p2p distributed, unified push, their proxy stuff (which also helps reduce battery usage), make the app not such p2p, but the gain in battery life might be your priority. DHT is as well a point of gathering several connections, and also to collect metadata, but to be honest, DHT is so good for this purpose, that I don’t complain.
The thing is that on the phone by default you don’t get a pure p2p experience, which is BTW really hard, as requiring both ends being present if pure p2p, and it’s really hard to actually contact the other end at any time. Although if wanted, jami can be configured as such, except by the DHT part I believe.
I’m starting to wish I had an account on Lemmy.ML you guys are based & badasses (But that’s a topic for another day)
I still wish they didn’t check for Unique usernames, the DHT should be enough & the username should be a supplement that can be edited later
They don’t, I mean registering your username/basename is not a requirement, they chose the registration as the default to make it easier to be found. But you can get away with not registering your username/basename and instead exchange with your contacts you ID number, and with that besides able to choose whatever username/basename, there’s no central directory to find you, which is good depending on your use case, but the Jami guys are right to say that makes it virtually impossible for others to find you and establish a conversation unless you exchanged somehow your ID numbers, but that’s not actually finding, :)
That option is a one time choosing, when creating the account though.
I recommend Peer Calls as an alternative. Peer Calls uses peer-to-peer communication similar to Jami. You can check out Peer Calls on Github for more info.
So, in short, the things I really like about it:
- Simple to selfhost - Only one Docker container with no dependencies (database, storage, etc.) and you only need to forward HTTP/S traffic.
- Lightweight - You get voice and text chat; screen and file sharing. All of it directly P2P.
- Private - Selfhosting the signaling server will grant you control over the only step which requires a central server during the WebRTC connection process.
- No accounts - Just start using, no accounts are involved.
XMPP is absolutely the best option if you don’t care about metadata protection.
XMPP does video chat, or at least voice? What clients do you recommend? Linux, android, and iphone are all of interest. Thanks.
How about Movim ?? It’s an XMPP-Based Social-Media/Microblogging platform
Interesting, I’ll take a look at it, thanks., But I’ve been particularly interested in Jami because it runs on multiple platforms, is on F-droid, and is a GNU program.
Why the fascination with GNU ?
