Skype is owned by Microsoft and all its calls pass through MS servers. No one knows what MS does with the data it gathers.
Jami is a free open alternative with no servers at all, calls connect directly between users. It's very easy to use, and a good privacy-friendly replacement for Skype.
Their website is at:
You can follow Jami on the Fediverse at:
The app is available for all major platforms including Android, iOS, Windows, Mac and Linux.
Oh, I see what you mean.
I'm not a developer so I'm not sure, but I *think* it sounds like the directory is distributed too?
"By adopting distributed hash table technology (as used, for instance, within the BitTorrent network), Jami creates its own network over which it can distribute directory functions, authentication and encryption across all systems connected to it."
...but the best people to comment on this are @Jami themselves.
@brandon @switchingsocial @Jami https://git.jami.net/savoirfairelinux/ring-project/wikis/technical/Name-Server-Protocol
1. Username are not at all mandatory
2. You can host your own nameserver (or just host a JSON file on your website for example)
Jami usernames are stored on a blockchain. For more info please see this article : https://jami.net/the-jami-blockchain-switches-from-proof-of-work-to-proof-of-authority/
Well. We do know some things that go on back there. Including NSA's PRISM.
Avoiding Microsoft is a good rule of thumb with regard to privacy.
@switchingsocial Yep. I've been doing it for a while. Except when it comes to VSCode...
Jitsi is good too:
But Jami is more of a direct replacement for Skype, Jitsi works a bit differently.
did you figuerd out how to change its proxy?
like I don't want that my ip adress is visable, but I also don't want everything on my phone go through the same vpn or what soever. Within a rooted phone that can be changed. But I have not found out a method that works with unrooted android except if the specific app that shall use a proxy has this function (note: ppl should not run googles version of android, but still many do)
As mentioned in previous comments, this could help answer some of your questions
I find it most regrettable that they are not working hand in hand with the folks that make #tox
Or if they have their reasons I would very much like to hear them.
I see features I would love in tox, but yet I see issues that tox already fixed.
I fell we're reinventing the wheel here.
I had heard of ring before but thought they were going the decentralized way, not the distributed one.
@Naughtylus @switchingsocial @Jami Why not put the question the other way around? Why not blame Tox for not working w/ Jami? Tox has had lots of drama, uses its own protocol, and has had development all but die. I have still yet to make a successful audio call on it that doesn't sound like shit. What would Jami gain?
I believe Ring/Jami only set out to be p2p in 2015. By then the development of tox had already started, although the project was still in its infancy.
Also correct me if I'm wrong, but Jami uses it's own protocol for p2p as well. AFAIK SIP isn't p2p.
In fact I would blame both teams for the split effort if they tell me they weren't aware of each other and/or they didn't take the time to look into one-another.
PS: tox audio calls worked fine last time I checked.
@Naughtylus @switchingsocial @Jami Last time I checked, which admittedly was around the new year, uTox audio was terrible and qTox was quite robotic, though I suppose usable in an emergency. Video showed an image for a moment, becoming a much of green blocks, from which it never recovered. I tried to hold out hope for #tox for a long time, but as time went on, I found it increasinlgy hard to be positive.
@Naughtylus @switchingsocial @Jami Somewhere I posted about the relation of #jami to #sip. When as Ring it first came out, they made a big deal about using existing tech, not reinventing the wheel (w/ encryption, dht, etc.). Asked if they'd add #xmpp support (I think Reddit), they said architecturally it was very different. With SIP, one can call directly to an IP. Jami uses DHT to pass the IP to SIP, which then makes the call--as I understand it.
On git.jami.net. Or IRC mainly #jami on freenode. And we follow what #tox is doing. But a lot of parts are coming from known standads (SIP, ICE, TLS negotiation, certificate management, etc). (Jami is also a SIP client btw), And yes for Jami accounts, the DHT is used to share the IP (SDP messages for ICE in fact)
mastodon.at is a microblogging site that federates with most instances on the Fediverse.