Jami "Taranis" released

Posted Dec 25, 2021 12:18 UTC (Sat) by Moarc (guest, #137864)
In reply to: Jami "Taranis" released by Cyberax
Parent article: Jami "Taranis" released

It's peer-to-peer instead of a federation of servers, with an identity based around the user's public key, for which you can optionally register a nickname (in a way which evokes the ever-fashionable blockchain, the nickname being tied to that key once and for all - I'm not sure if they're actually using a blockchain for this, though).

It also doesn't try to poorly reinvent XMPP.

Jami "Taranis" released

Posted Dec 25, 2021 22:25 UTC (Sat) by KJ7RRV (subscriber, #153595) [Link] (2 responses)

Doesn't being peer to peer imply it wouldn't work well behind NAT and firewalls?

Jami "Taranis" released

Posted Dec 27, 2021 2:55 UTC (Mon) by droundy (subscriber, #4559) [Link] (1 responses)

They run a TURN server to get through NATs. Seems reasonable. They also have a few other servers required for bootstrapping to the DHT, receiving push notifications while running in the background on mobile, etc.

Jami "Taranis" released

Posted Jan 3, 2022 18:26 UTC (Mon) by bandali (guest, #98538) [Link]

Indeed. Though I'll just clarify that even though bootstrap.jami.net is used as the default bootstrap node, it doesn't have to be, and can be easily changed from Jami's advanced settings to point to any other reachable machine running OpenDHT -- including another device running Jami and OpenDHT on your local network. Or you could use a DHT proxy (disabled by default on desktop/laptop, but enabled on mobile as it helps reduce battery usage) instead of having Jami running an OpenDHT node on your device. Similarly to the bootstrap node, the address for the DHT proxy can also easily be changed to point away from the default servers. Likewise for the TURN server address.

More details in the Jami FAQ: https://git.jami.net/savoirfairelinux/jami-project/-/wiki...