The FAQ has a When do public IPs get exposed with an answer that seems to me a bit outdated as it does not mention swarm calls. Neither does it mention that the client IP can leak when Web link previews are enabled. Has someone the time and the knowledge to update the answer?
The best thing to do is to turn off the link preview
A better answer is to update the FAQ…
Maybe it should be set to off by default
The FAQ for documentation is outdated, it was probably written before swarm was developed, and now sending messages requires a direct connection between devices.
Since Jami documentation is contributed in the same way as code, it’s likely that I’ll already be working on the code by the time I can update it…
That’s the nature of P2P, and Jami’s not designed to work over Tor. Real time video chat’s not going to work over Tor anyway so that’d be pointless, and there are other P2P messengers that do that such as Ricochet Refresh. That’s why most P2P messengers that aren’t built to work over Tor offer relays, as does Signal by the way. You can use a VPN, and that’s what most people use when using a P2P messenger or BitTorrent which uses DHT just like Jami does. I use Mullvad VPN or IVPN. Add me on Jami if you want to talk. I’d set up an OpenWrt VPN router with a Raspberry Pi if I were you. That’s the best way to do it so that your computer has no visibility into what your real IP address is. It’s called a VPN gateway, just like how Whonix has its Tor gateway.