This page aims to gather as many resources as possible (technical or not) and
condense them to create concise documentation. Then, this can then be
integrated into a tutorial or a help page on the website or in the clients.
It's because your account is not connected to the DHT. Verify your internet connection or try to relaunch the application. If you use the push notifications, try to disable this option (and re-enable it).
Jami saves its configuration (account, certificates, history) at
different locations depending the platform.
GNU/Linux: global configuration is under
~/.config/jami/dring.yml and Accounts files are under
~/.local/share/jami/. Finally some cache can be stored in ~/.cache/jami
OSX: The full configuration is under ~/Library/Application
Support/Jami if installed via https://jami.net. Via the appstore it's ~/Library/Containers/com.savoirfairelinux.ring.macos/Data/Library/Application Support/jami
Android: The full configuration is under /data/data/cx.ring
(may require root privileges)
Windows: global configuration is under
%AppData%/Local/jami/dring.yml and Account files are under
%AppData%/Local/jami/. Finally, some caches are in %USERPROFILE%/.cache/jami
Jami is not like a lot of communication software. It's not based on any central server and your account is only stored on your device. When you want to use Jami with your account, you don't have to use a classical login/password authentification.
When you create a new Jami account, you don't have to provide private informations like a mail or a phone number. But this is the informations you can provide (all optionals):
A display name, it's the name client will display on your contact entry with the avatar. It can contains special character.
A password. This password is used to protect the account archive in your device.
So, after this step, the client will generate an archive (protected by the password you gave). This archive will contains your account's keys. And a JamiID is now created (a 40 chars length string. Technically, this ID is the fingerprint of your public key. And that's it, you have a Jami account.
With Jami, you are not forced to have a password on your account.
Don't worry, it's a decentralized system, consequences are not the same than on other systems.
With a centralized system, you use your password to authenticate on a public server. Someone who knows your password can usurp your identity.
With Jami, your account is stored in a folder on your device. The password is only used to protect you from someone who have a physical access to your device by encrypting the account's archive (and don't let anyone access your private key)
If your device is encrypted, you may not want/need to use a password.
For a while, Jami had no username management system. Instead, we had to use Infohashs. They are quite difficult to use for most people (ie : 3d1112ab2bb089370c0744a44bbbb0786418d40b). To mitigate the issue, we created a system that associate your Infohashs to a username of your choice that will be much more easier to remember. We recommand you to create a username: Jami will be friendlier.
The technology we used to associate a username to a Infohashs, Ethereum blockchain, is also distributed, but it doesn't allow to modify or delete the association between a username and a InfoHash.
You can still create an account without a username if you wish. Please note that if you choose this option, it is still possible to register a username later.
Link another device to your account, so your account will be in two devices. You can find this option in the account's settings page.
Copy the account's archive on a USB flashdrive or any another place. This file can be found in the paths given in the previous question. In the linux client, you can export this archive from the client in the account's settings page.
Nothing. Because we don't have access to your datas, we can't have an option like "I forget my password". You are the only one in charge of your datas, so take care.
If you are scared to forget a password, please use a password manager.
When you choose to "link your device with another account", you have to enter the password of your account on your first device and a PIN. This PIN is generated by the first device, when you click on "Link this account to another device" (Generally in Settings -> Accounts -> Choose your account -> Link this account to another device), the account will be sent on the DHT during 5 minutes and a PIN is generated at this moment. This is the PIN you need to enter on the other device.
A Jami account only exists on linked devices with this account. So, you only have to delete this account in app on all these devices and your account will not exists anymore. Or to uninstall Jami.
If you delete the account's archive, your account will no longer exists. If you uninstall Jami, your data will be deleted too. And nobody will be able to retrieve your account. Never ever.
In the settings page, go to Accounts, choose your account and click on the Delete button in the GUI. Another way is to remove configuration files
In the hamburger menu, choose Manage accounts, choose the account to delete and click on the trash icon.
Note for accounts with a username
The technology that handle usernames is also distributed. So, it depends the nameservice you choose to make the translation between a nickname and your Jami ID. By default, a username is registered on ns.jami.net where you can't modify the Jami ID associated to this username. So, if you delete or if you lost your account you will not be able to retrieve this username, ever. Nobody will be able to recreate an account with the same username.
NOTE: If your account has a username, this username will not be deleted. For example, if you use the username pseudo on the name server ns.jami.net, when you will delete your Jami account and you create a new account, you will not be able to retrieve this username, because ns.jami.net can't prove it's your username.
If you do not want to lose your account, please back-up files related to this one.
ICE descriptors of other Jami users. ICE is a protocol that help establishing communication between two computers
certain text messages
as indicated above, accounts currently being linked to a new device
Audio/video streams and some text messages pass through the VOIP protocol.
Text messages can be sent either via VOIP or DHT (the distributed network) depending on whether a VOIP communication channel is already open or not.
Push notifications allow Jami to operate in a way more adapted to the context of mobility (energy consumption, data...). However, for the moment, notifications go through Google's servers, via the Firebase service. Only one identifier is transferred and it is unusable for anyone who does not have access to your account.
The DHT proxy is a server that registers on the DHT for you and relays your information to you. Thus, it is the server that will be active on the DHT and will participate in the network, and no longer the target device. Multiple devices can register on the same DHT proxy.
The usernames are registered on an Ethereum blockchain. By default, it's ns.jami.net that is used, but if you are a developper, you can create your own system. Hence, nothing forces you to implement it with a blockchain. You can check results at http://ns.jami.net/name/test, where "test" is a username for which we are looking for a matching Infohashs.
Note: This is only for client based on LRC (desktop ones)
First you will need to export all your accounts (For GNU/Linux: Settings => Account => Export account). Then you will need to copy the database (in ~/.local/share/jami for example).
Then on the new device, when you will open Jami for the first time, you have to re-import your accounts via the archive previously saved. This will re-import your settings and contacts (with empty conversations). Then close the client and replace the database with the one previously saved. That's all!
We can describe 3 main connectivity scenarios. A classic configuration (1.), behind a VPN (2.), via Tor (3.). As Jami is a p2p app, I think you understand that (2.) or (3.) is a bit mandatory to avoid IP leaking.
Moreover, even if it's my answer, you can choose to not trust my answer and check the code, or use wireshark or other tools. Generally, I (and the other devs I think) are using the first scenario (sometimes the second one), and we surely can't test all the network we want, so if you discover a bug, please open a issue.
Anyway, in these 3 scenarios, there is 3 main actions:
The Jami application is running a DHT (https://opendht.net) node on your device. So every operations on the DHT will use your ips. This is why Jami has the option to use a dhtproxy (eg dhtproxy.jami.net), this will avoid to use your node, but will use another node on the network (which will see your ip). Note that your message is not sent directly to the other device. In fact your message is sent on some nodes of the DHT and your contact will retrieve the message on this node. So, your contact don't see your IP at this step, but the node who get the message will (or they will see the IP of the proxy).
Send a file
As described in the docs, you will send a message with all the IP you know that your peer can contact in an encrypted packet. So, if your peer send you a file or you send a file, your addresses will appear in the ICE message.
Same as above, the IP is present in the ICE.
Behind a VPN
Send a message
The IP of your VPN will be used by the DHT node. If you want a proof, you can compile dhtnode and run the 'la' command to get your public detected address. This is what I got:
./tools/dhtnode -b bootstrap.jami.netBootstrap: bootstrap.jami.net:4222OpenDHT node be58fdc9f782269bfc0bbfc21a60bca5f02cb881 running on port 54299 (type 'h' or 'help' for a list of possible commands)>> laReported public addresses:IPs OF MY VPN
So, if you don't use a proxy, your VPN addresses will be used for using the DHT. If you use a dhtproxy, the dhtproxy will see your VPN addresses
This file is located in the same directory of dring.yml
The best way to check which options are supported is through the command "ffmpeg -h encoder=[encoder_name]" where encoder_name can be whichever of libx264, libvpx, mpeg4, h263, libopus, libspeex, g722, pcm_alaw, pcm_mulaw (FFmpeg names for all of Jami's supported encoders).