# SOME DESCRIPTIVE TITLE. # Copyright (C) 2018-2025 Savoir-faire Linux Inc. and contributors # This file is distributed under the same license as the Jami package. # FIRST AUTHOR , YEAR. # #, fuzzy msgid "" msgstr "" "Project-Id-Version: Jami\n" "Report-Msgid-Bugs-To: \n" "POT-Creation-Date: 2025-01-14 03:53+0000\n" "PO-Revision-Date: 2022-09-14 17:45+0000\n" "Language-Team: English (United States) (https://app.transifex.com/savoirfairelinux/teams/49466/en_US/)\n" "MIME-Version: 1.0\n" "Content-Type: text/plain; charset=UTF-8\n" "Content-Transfer-Encoding: 8bit\n" "Language: en_US\n" "Plural-Forms: nplurals=2; plural=(n != 1);\n" #: ../../../user/all-features-by-client.md:1 msgid "All features by client" msgstr "" #: ../../../user/all-features-by-client.md:4 msgid "Legend:" msgstr "" #: ../../../user/all-features-by-client.md:6 msgid "✓ : Available" msgstr "" #: ../../../user/all-features-by-client.md:7 msgid "E : Experimental" msgstr "" #: ../../../user/all-features-by-client.md:8 msgid "X : Not yet available" msgstr "" #: ../../../user/all-features-by-client.md:9 msgid "N/A : Not applicable for this client" msgstr "" #: ../../../user/all-features-by-client.md:10 msgid "? : Unknown/under development" msgstr "" #: ../../../user/all-features-by-client.md:11 msgid "Desktop : Apple macOS, GNU/Linux, Microsoft Windows operating systems" msgstr "" #: ../../../user/all-features-by-client.md:12 msgid "iOS : iPad and iPhone devices with iOS operating system" msgstr "" #: ../../../user/all-features-by-client.md:13 msgid "Web : Jami access with a web browser" msgstr "" #: ../../../user/all-features-by-client.md:0 #: ../../../user/all-features-by-client.md:15 msgid "Text messaging" msgstr "" #: ../../../user/all-features-by-client.md:0 msgid "**Client**" msgstr "" #: ../../../user/all-features-by-client.md:0 msgid "Desktop" msgstr "" #: ../../../user/all-features-by-client.md:0 msgid "Android" msgstr "" #: ../../../user/all-features-by-client.md:0 msgid "Android TV" msgstr "" #: ../../../user/all-features-by-client.md:0 msgid "iOS" msgstr "" #: ../../../user/all-features-by-client.md:0 msgid "Web" msgstr "" #: ../../../user/all-features-by-client.md:0 msgid "✓" msgstr "" #: ../../../user/all-features-by-client.md:0 msgid "?" msgstr "" #: ../../../user/all-features-by-client.md:0 msgid "Group chat" msgstr "" #: ../../../user/all-features-by-client.md:0 msgid "X" msgstr "" #: ../../../user/all-features-by-client.md:0 msgid "Public chat" msgstr "" #: ../../../user/all-features-by-client.md:0 msgid "Chat history shared across devices" msgstr "" #: ../../../user/all-features-by-client.md:0 msgid "Send files" msgstr "" #: ../../../user/all-features-by-client.md:0 msgid "Auto accept images" msgstr "" #: ../../../user/all-features-by-client.md:0 msgid "Custom download location" msgstr "" #: ../../../user/all-features-by-client.md:0 msgid "Typing indicator" msgstr "" #: ../../../user/all-features-by-client.md:0 msgid "Read status" msgstr "" #: ../../../user/all-features-by-client.md:0 msgid "Reply to" msgstr "" #: ../../../user/all-features-by-client.md:0 msgid "Message edition" msgstr "" #: ../../../user/all-features-by-client.md:0 msgid "Emoji reaction" msgstr "" #: ../../../user/all-features-by-client.md:0 msgid "Update conversation's profile" msgstr "" #: ../../../user/all-features-by-client.md:0 msgid "Add/Kick members" msgstr "" #: ../../../user/all-features-by-client.md:0 msgid "Conversation's preferences" msgstr "" #: ../../../user/all-features-by-client.md:0 msgid "Search messages" msgstr "" #: ../../../user/all-features-by-client.md:0 msgid "Share messages" msgstr "" #: ../../../user/all-features-by-client.md:0 msgid "✓(1)" msgstr "" #: ../../../user/all-features-by-client.md:0 msgid "Share location" msgstr "" #: ../../../user/all-features-by-client.md:0 msgid "Media gallery" msgstr "" #: ../../../user/all-features-by-client.md:39 msgid "" "(1) Sharing messages and media is available on Android through the system-" "native sharing feature" msgstr "" #: ../../../user/all-features-by-client.md:41 msgid "Calling" msgstr "" #: ../../../user/all-features-by-client.md:0 msgid "Audio calls" msgstr "" #: ../../../user/all-features-by-client.md:0 msgid "Video calls" msgstr "" #: ../../../user/all-features-by-client.md:0 msgid "Group calls" msgstr "" #: ../../../user/all-features-by-client.md:0 msgid "E" msgstr "" #: ../../../user/all-features-by-client.md:0 msgid "Host call conference" msgstr "" #: ../../../user/all-features-by-client.md:0 msgid "Auto bitrate" msgstr "" #: ../../../user/all-features-by-client.md:0 msgid "Change video quality" msgstr "" #: ../../../user/all-features-by-client.md:0 msgid "Custom ringtones" msgstr "" #: ../../../user/all-features-by-client.md:0 msgid "Select camera" msgstr "" #: ../../../user/all-features-by-client.md:0 msgid "Video call recording" msgstr "" #: ../../../user/all-features-by-client.md:0 msgid "Leave audio message" msgstr "" #: ../../../user/all-features-by-client.md:0 msgid "Leave video message" msgstr "" #: ../../../user/all-features-by-client.md:0 msgid "Screen sharing" msgstr "" #: ../../../user/all-features-by-client.md:0 msgid "Window sharing" msgstr "" #: ../../../user/all-features-by-client.md:0 msgid "✓(3)" msgstr "" #: ../../../user/all-features-by-client.md:0 msgid "Media sharing" msgstr "" #: ../../../user/all-features-by-client.md:0 msgid "Hardware encoding\\*" msgstr "" #: ../../../user/all-features-by-client.md:0 msgid "Hardware decoding\\*" msgstr "" #: ../../../user/all-features-by-client.md:0 msgid "Mute sound" msgstr "" #: ../../../user/all-features-by-client.md:0 msgid "Texting while on call" msgstr "" #: ../../../user/all-features-by-client.md:0 msgid "Remote recording notification" msgstr "" #: ../../../user/all-features-by-client.md:0 msgid "Rendez-vous mode" msgstr "" #: ../../../user/all-features-by-client.md:0 msgid "Conference layout" msgstr "" #: ../../../user/all-features-by-client.md:0 msgid "Multistream" msgstr "" #: ../../../user/all-features-by-client.md:0 msgid "Push-to-talk" msgstr "" #: ../../../user/all-features-by-client.md:0 msgid "Videosplit" msgstr "" #: ../../../user/all-features-by-client.md:0 msgid "Audio processor\\*\\*" msgstr "" #: ../../../user/all-features-by-client.md:0 msgid "✓(2)" msgstr "" #: ../../../user/all-features-by-client.md:0 msgid "Voice activity" msgstr "" #: ../../../user/all-features-by-client.md:72 msgid "" "\\* This enables 4K video calling support
\\*\\* cf. {ref}`user/faq:How " "can I configure the audio processor?` in the FAQ" msgstr "" #: ../../../user/all-features-by-client.md:75 msgid "" "(1) Available on both X and Wayland
(2) Some features enabled by default" " and not configurable
(3) Only on X and not on Microsoft Windows" msgstr "" #: ../../../user/all-features-by-client.md:79 msgid "Account settings" msgstr "" #: ../../../user/all-features-by-client.md:0 msgid "Profile picture" msgstr "" #: ../../../user/all-features-by-client.md:0 msgid "Disable account" msgstr "" #: ../../../user/all-features-by-client.md:0 msgid "Delete account" msgstr "" #: ../../../user/all-features-by-client.md:0 msgid "Contact availability" msgstr "" #: ../../../user/all-features-by-client.md:0 msgid "Register username" msgstr "" #: ../../../user/all-features-by-client.md:0 msgid "Delete contacts" msgstr "" #: ../../../user/all-features-by-client.md:0 msgid "Block contacts" msgstr "" #: ../../../user/all-features-by-client.md:0 msgid "Link new device via DHT" msgstr "" #: ../../../user/all-features-by-client.md:0 msgid "Link new device via archive" msgstr "" #: ../../../user/all-features-by-client.md:0 msgid "Auto answer" msgstr "" #: ../../../user/all-features-by-client.md:95 msgid "Other features" msgstr "" #: ../../../user/all-features-by-client.md:0 msgid "Scan QR code" msgstr "" #: ../../../user/all-features-by-client.md:0 msgid "Display QR code" msgstr "" #: ../../../user/all-features-by-client.md:0 msgid "Block contact" msgstr "" #: ../../../user/all-features-by-client.md:0 msgid "System notifications" msgstr "" #: ../../../user/all-features-by-client.md:0 msgid "Supported languages" msgstr "" #: ../../../user/all-features-by-client.md:0 msgid "105\\*" msgstr "" #: ../../../user/all-features-by-client.md:0 msgid "2" msgstr "" #: ../../../user/all-features-by-client.md:0 msgid "Contacts shared across devices" msgstr "" #: ../../../user/all-features-by-client.md:0 msgid "Multi account" msgstr "" #: ../../../user/all-features-by-client.md:0 msgid "SIP account" msgstr "" #: ../../../user/all-features-by-client.md:0 msgid "SIP transferring" msgstr "" #: ../../../user/all-features-by-client.md:0 msgid "Dark theme support" msgstr "" #: ../../../user/all-features-by-client.md:0 msgid "JAMS\\*\\* support" msgstr "" #: ../../../user/all-features-by-client.md:0 msgid "Plugin support" msgstr "" #: ../../../user/all-features-by-client.md:0 msgid "Plugin store" msgstr "" #: ../../../user/all-features-by-client.md:0 msgid "Application translation" msgstr "" #: ../../../user/all-features-by-client.md:0 msgid "White labeling" msgstr "" #: ../../../user/all-features-by-client.md:115 msgid "" "\\* According to
" "\\*\\* JAMS (Jami Account Management Server) " msgstr "" #: ../../../user/all-features-by-client.md:118 msgid "Advanced settings" msgstr "" #: ../../../user/all-features-by-client.md:0 msgid "DHT proxy support" msgstr "" #: ../../../user/all-features-by-client.md:0 msgid "Push notification" msgstr "" #: ../../../user/all-features-by-client.md:0 msgid "N/A" msgstr "" #: ../../../user/all-features-by-client.md:0 msgid "UPnP" msgstr "" #: ../../../user/all-features-by-client.md:0 msgid "TURN configuration" msgstr "" #: ../../../user/bug-report-guide.md:1 msgid "" "**Note: We are currently a small number of developers active on the project." " As such, we cannot answer and tag all of the opened issues immediately, " "but we do notice and read them. Good bug reports provide us important " "feedback, which we thank you for and always appreciate.**" msgstr "" #: ../../../user/bug-report-guide.md:6 msgid "Bug report guide" msgstr "" #: ../../../user/bug-report-guide.md:9 msgid "" "This guide includes step-by-step instructions for reporting bugs and issues " "you encounter in Jami." msgstr "" #: ../../../user/bug-report-guide.md:12 msgid "Set up your environment" msgstr "" #: ../../../user/bug-report-guide.md:15 msgid "" "Be ready for data loss. Back up your account and link your account to as " "many devices as possible." msgstr "" #: ../../../user/bug-report-guide.md:17 msgid "" "Install the latest version (or even a beta version) of Jami. Reporting " "bugs/issues against older versions is less useful, and there is a likelihood" " of it already having been fixed in newer versions." msgstr "" #: ../../../user/bug-report-guide.md:22 msgid "How to report a bug" msgstr "" #: ../../../user/bug-report-guide.md:25 msgid "" "Create an account on the [Jami GitLab](https://git.jami.net/users/sign_up) " "if you don't have one already." msgstr "" #: ../../../user/bug-report-guide.md:29 msgid "Choose the right project to post your issue in:" msgstr "" #: ../../../user/bug-report-guide.md:31 msgid "{gitlab-project}`The Android client `" msgstr "" #: ../../../user/bug-report-guide.md:32 msgid "{gitlab-project}`The Qt client `" msgstr "" #: ../../../user/bug-report-guide.md:33 msgid "{gitlab-project}`The iOS client `" msgstr "" #: ../../../user/bug-report-guide.md:34 msgid "" "{gitlab-project}`The macOS client ` (deprecated by " "{gitlab-project}`the Qt client `)" msgstr "" #: ../../../user/bug-report-guide.md:36 msgid "" "{gitlab-project}`The Jami project in general (or if you are not sure) `" msgstr "" #: ../../../user/bug-report-guide.md:38 msgid "" "[If you know what you are doing you may choose one of the other " "projects](https://git.jami.net)" msgstr "" #: ../../../user/bug-report-guide.md:41 msgid "" "If you have multiple issues, please file separate bug reports. It will be " "much easier to keep track of them that way." msgstr "" #: ../../../user/bug-report-guide.md:44 msgid "" "The title is an explicit summary of the bug (e.g.: header bar is too big due" " to icon size)" msgstr "" #: ../../../user/bug-report-guide.md:47 msgid "Figure out the steps to reproduce the bug:" msgstr "" #: ../../../user/bug-report-guide.md:49 msgid "" "If you have precise steps to reproduce it (great!) you're on your way to " "creating a helpful bug report." msgstr "" #: ../../../user/bug-report-guide.md:51 msgid "" "If you can reproduce occasionally, but not after following specific steps, " "please provide additional information about the issue to help others " "understand and try to reproduce it." msgstr "" #: ../../../user/bug-report-guide.md:54 msgid "" "If you can not reproduce the problem, there may be little chance of it being" " reasonably fixable. If you do report it, please try your best to provide " "as much information/clues about its occurrence as possible." msgstr "" #: ../../../user/bug-report-guide.md:59 msgid "" "Make sure your software is up to date. Ideally, test an in-development " "version to see whether your bug has already been fixed." msgstr "" #: ../../../user/bug-report-guide.md:62 msgid "" "Try to isolate from the environment and reproduce (i.e. test on multiple " "devices)." msgstr "" #: ../../../user/bug-report-guide.md:65 msgid "Describe your environment(s) by specifying the following:" msgstr "" #: ../../../user/bug-report-guide.md:67 msgid "OS version" msgstr "" #: ../../../user/bug-report-guide.md:68 msgid "precise device model (important for mobile devices)" msgstr "" #: ../../../user/bug-report-guide.md:69 msgid "if you are using a beta version" msgstr "" #: ../../../user/bug-report-guide.md:70 msgid "" "what build you are using (F-Droid, Play Store, App Store, from " "`dl.jami.net`, your own build, etc.). If you have built your own version of" " Jami, please specify the exact Jami Daemon version and client version (you " "can obtain it using `jamid -v` and `jami -v`; but note that our packages are" " updated quite often) and the Git commit." msgstr "" #: ../../../user/bug-report-guide.md:75 msgid "" "network conditions: are both devices on the same local network? Different " "networks? Is one or both behind NAT? Are you using LTE? Are you using " "WiFi?" msgstr "" #: ../../../user/bug-report-guide.md:78 msgid "other elements if needed: SIP provider, hardware, etc." msgstr "" #: ../../../user/bug-report-guide.md:80 msgid "Writing a clear summary" msgstr "" #: ../../../user/bug-report-guide.md:83 msgid "" "How would you describe the bug using approximately 10 words? This is the " "first part of your bug report a developer will see." msgstr "" #: ../../../user/bug-report-guide.md:86 msgid "" "A good summary should quickly and uniquely identify a bug report. It should " "explain the problem, not your suggested solution." msgstr "" #: ../../../user/bug-report-guide.md:99 msgid "Writing precise steps to reproduce" msgstr "" #: ../../../user/bug-report-guide.md:102 msgid "How can a developer reproduce the bug on his or her own device?" msgstr "" #: ../../../user/bug-report-guide.md:104 msgid "" "Steps to reproduce are the most important part of any bug report. If a " "developer is able to reproduce the bug, the bug is very likely to be fixed." " If the steps are unclear, it might not even be possible to know whether " "the bug has been fixed. We are totally aware that some bugs may look " "obvious to you, but they are probably related to your environment. The more" " precise you are, the quicker the bug can be fixed." msgstr "" #: ../../../user/bug-report-guide.md:112 msgid "What should you include in a bug report?" msgstr "" #: ../../../user/bug-report-guide.md:114 msgid "" "Indicate whether you can reproduce the bug at will, occasionally, or not at " "all. Describe your method of interacting with Jami in addition to the " "intent of each step. After your steps, precisely describe the observed " "(actual) result and the expected result. Clearly separate facts " "(observations) from speculations." msgstr "" #: ../../../user/bug-report-guide.md:120 msgid "Good :" msgstr "" #: ../../../user/bug-report-guide.md:122 msgid "I can always reproduce by following these steps:" msgstr "" #: ../../../user/bug-report-guide.md:133 msgid "Bad :" msgstr "" #: ../../../user/bug-report-guide.md:140 msgid "Obtained Result" msgstr "" #: ../../../user/bug-report-guide.md:143 msgid "Please include:" msgstr "" #: ../../../user/bug-report-guide.md:145 msgid "The Jami daemon (jamid or libjami or libring) and client debug logs." msgstr "" #: ../../../user/bug-report-guide.md:146 msgid "The core dump if one was produced." msgstr "" #: ../../../user/bug-report-guide.md:148 msgid "Expected Result" msgstr "" #: ../../../user/bug-report-guide.md:151 msgid "It's a description of expected or desired behavior." msgstr "" #: ../../../user/bug-report-guide.md:154 msgid "Providing additional information" msgstr "" #: ../../../user/bug-report-guide.md:157 msgid "" "The following information is requested for most bug reports. You can save " "time by providing this information below the Expected results." msgstr "" #: ../../../user/bug-report-guide.md:160 msgid "Logs" msgstr "" #: ../../../user/bug-report-guide.md:162 msgid "Qt-based Jami client (GNU/Linux, Windows, macOS)" msgstr "" #: ../../../user/bug-report-guide.md:164 msgid "" "Go to the General settings. In the Troubleshoot section, you can click on " "\"Open logs\", where you will be able to get statistics (\"Show stats\") or " "start recording information via \"Receive logs\". Then you can just copy the" " result and explain your scenario." msgstr "" #: ../../../user/bug-report-guide.md:169 msgid "On GNU/Linux" msgstr "" #: ../../../user/bug-report-guide.md:171 msgid "Classic logs (by default logs only >= warning are logged):" msgstr "" #: ../../../user/bug-report-guide.md:177 msgid "" "Full log: Since the Jami client (GUI) and daemon are separated processes, " "the easiest way to get logs from both is to start them one at a time, " "manually." msgstr "" #: ../../../user/bug-report-guide.md:182 msgid "" "Ensure that no Jami client or daemon instances are running: check by running" " `ps aux | grep jami` in a terminal." msgstr "" #: ../../../user/bug-report-guide.md:184 msgid "" "Jami may still be running even if no windows are open, depending on your " "preferences." msgstr "" #: ../../../user/bug-report-guide.md:186 msgid "" "If either client or daemon are running, terminate them using `kill PID`." msgstr "" #: ../../../user/bug-report-guide.md:188 msgid "In one terminal, start the daemon with `jamid -d -c`" msgstr "" #: ../../../user/bug-report-guide.md:189 msgid "" "This executable is normally not in the `PATH`, and in the " "Debian/Trisquel/Ubuntu packages, it is located at `/usr/lib/x86_64-linux-" "gnu/jamid -d -c` or `/usr/libexec/jamid -d -c`." msgstr "" #: ../../../user/bug-report-guide.md:193 msgid "In another terminal, start the client, using `jami -d`." msgstr "" #: ../../../user/bug-report-guide.md:195 msgid "To get a backtrace, you can run the program inside GDB:" msgstr "" #: ../../../user/bug-report-guide.md:197 msgid "" "`gdb -ex run --args jami -d`, or `gdb -ex run --args /usr/libexec/jamid " "-cd`, depending on the component you need to debug." msgstr "" #: ../../../user/bug-report-guide.md:201 msgid "" "When it crashes, you can type `bt` (or even better, `thread apply all bt`) " "then press *Enter*. Then copy the backtrace and paste it in the issue." msgstr "" #: ../../../user/bug-report-guide.md:205 msgid "On macOS" msgstr "" #: ../../../user/bug-report-guide.md:207 msgid "Navigate to `/Applications/Jami.app/Contents/MacOS/`." msgstr "" #: ../../../user/bug-report-guide.md:208 msgid "" "Double click Jami. It will launch Jami and print the log to the terminal." msgstr "" #: ../../../user/bug-report-guide.md:210 msgid "Copy the log from terminal to a file." msgstr "" #: ../../../user/bug-report-guide.md:212 msgid "" "Alternatively, you could run `//Jami.app/Contents/MacOS/Jami " "-d` from the terminal." msgstr "" #: ../../../user/bug-report-guide.md:215 msgid "On Android" msgstr "" #: ../../../user/bug-report-guide.md:217 msgid "To gather logs via your phone using Jami itself:" msgstr "" #: ../../../user/bug-report-guide.md:219 msgid "Tap `Conversations`" msgstr "" #: ../../../user/bug-report-guide.md:220 msgid "Tap the three-dot menu on the top right" msgstr "" #: ../../../user/bug-report-guide.md:221 msgid "Tap `Settings`" msgstr "" #: ../../../user/bug-report-guide.md:222 msgid "Tap `Diagnostic logs`" msgstr "" #: ../../../user/bug-report-guide.md:224 msgid "To gather logs via your computer using the Android Debug Bridge (adb):" msgstr "" #: ../../../user/bug-report-guide.md:226 msgid "You need to have adb set up on your computer." msgstr "" #: ../../../user/bug-report-guide.md:227 msgid "Launch Jami on your smartphone and then execute" msgstr "" #: ../../../user/bug-report-guide.md:228 msgid "" "```adb logcat *:D | grep `adb shell ps | egrep 'cx.ring' | cut -c10-15` > " "logring.txt```" msgstr "" #: ../../../user/bug-report-guide.md:229 msgid "You now have a file containing the log of the client" msgstr "" #: ../../../user/bug-report-guide.md:231 msgid "For Windows" msgstr "" #: ../../../user/bug-report-guide.md:233 msgid "" "Open a terminal (cmd.exe) and launch Jami.exe with the following options:" msgstr "" #: ../../../user/bug-report-guide.md:236 msgid "`-d` to open a separate console window to receive logs" msgstr "" #: ../../../user/bug-report-guide.md:237 msgid "`-f` to write logs to `%localappdata%\\jami\\jami.log`" msgstr "" #: ../../../user/create-jami-account.md:1 msgid "Create Jami account" msgstr "" #: ../../../user/create-jami-account.md:4 msgid "CREATE A JAMI ACCOUNT ON:" msgstr "" #: ../../../user/create-jami-account.md:6 msgid "" "Android (EN) [create-jami-account-android-en.pdf](create-jami-account-" "android-en.pdf)" msgstr "" #: ../../../user/create-jami-account.md:8 msgid "" "Android (FR) [creer-compte-jami-android-fr.pdf](creer-compte-jami-android-" "fr.pdf)" msgstr "" #: ../../../user/create-jami-account.md:10 msgid "" "macOS (EN) [create-jami-account-macos-en.pdf](create-jami-account-macos-" "en.pdf)" msgstr "" #: ../../../user/create-jami-account.md:12 msgid "" "macOS (FR) [creer-compte-jami-macos-fr.pdf](creer-compte-jami-macos-fr.pdf)" msgstr "" #: ../../../user/create-jami-account.md:14 msgid "" "iOS (EN) [create-jami-account-ios-en.pdf](create-jami-account-ios-en.pdf)" msgstr "" #: ../../../user/create-jami-account.md:16 msgid "iOS (FR) [creer-compte-jami-ios-fr.pdf](creer-compte-jami-ios-fr.pdf)" msgstr "" #: ../../../user/create-jami-account.md:18 msgid "" "Windows (FR) [creer-compte-jami-windows-fr.pdf](creer-compte-jami-windows-" "fr.pdf)" msgstr "" #: ../../../user/faq.rst:2 msgid "FAQ" msgstr "" #: ../../../user/faq.rst:4 msgid "" "This is an exhaustive list of frequently asked questions, including some " "technical questions." msgstr "" #: ../../../user/faq.rst:13 msgid "Basics" msgstr "" #: ../../../user/faq.rst:16 msgid "What is Jami?" msgstr "" #: ../../../user/faq.rst:18 msgid "See the :doc:`introduction`." msgstr "" #: ../../../user/faq.rst:21 msgid "What does Jami mean?" msgstr "" #: ../../../user/faq.rst:23 msgid "" "The choice of the name Jami was inspired by the Swahili word `jamii` which " "means `community` as a noun and `together` as an adverb. It was chosen as " "it reflects the vision for the project: a free/libre program available to " "all that helps bring communities together, is community supported, and " "respects the freedom and privacy of the users." msgstr "" #: ../../../user/faq.rst:30 msgid "How can I make a bug report?" msgstr "" #: ../../../user/faq.rst:32 msgid "Please see the :doc:`bug-report-guide`." msgstr "" #: ../../../user/faq.rst:35 msgid "What makes Jami different from other communication platforms?" msgstr "" #: ../../../user/faq.rst:37 msgid "" "Jami does not work like most communication platforms because it is " "*distributed*:" msgstr "" #: ../../../user/faq.rst:40 msgid "Centralized, Decentralized, and Distributed network topology" msgstr "" #: ../../../user/faq.rst:43 msgid "" "Some of the consequences may seem surprising. For instance, since accounts " "are stored on your device, passwords are optional. However, the most " "significant practical differences are that you have more *freedom* and " "*privacy*." msgstr "" #: ../../../user/faq.rst:52 msgid "What do the green/orange/red status circles next to avatars mean?" msgstr "" #: ../../../user/faq.rst:53 msgid "" "On your own account, a red circle means that you aren't connected to the DHT" " or offline. You should have a detailled error banner explaining the issue. " "You may need to check your connection or restart the app." msgstr "" #: ../../../user/faq.rst:57 msgid "" "For contacts, no circle means that no device is detected on the DHT. This " "contact is unreachable. If an orange circle is present, this means that at " "least a device is announced on the DHT, so this contact SEEMS to be " "reachable. You do not have a direct connection towards this peer yet. But " "they should be able to receive connection requests. Because the device is " "not directly connected to anything, the device status is unable to be " "determine for sure. So this can be translated to \"Seems to be reachable\", " "but connection may fail (firewall, deadlock, NAT, etc)." msgstr "" #: ../../../user/faq.rst:65 msgid "" "The presence generally have a TTL of 10 min over the DHT and several hours " "if push notifications are enabled." msgstr "" #: ../../../user/faq.rst:67 msgid "" "If a green circle is present, this means that you're connected to a device " "of this peer." msgstr "" #: ../../../user/faq.rst:70 msgid "Why is a feature missing on my client?" msgstr "" #: ../../../user/faq.rst:72 msgid "" "Not every client implements all features; check the list :doc:`here ` to see if your client is missing the feature." msgstr "" #: ../../../user/faq.rst:76 msgid "You can make feature requests at https://git.jami.net." msgstr "" #: ../../../user/faq.rst:79 msgid "Does Jami support read receipts? Can I turn them on or off?" msgstr "" #: ../../../user/faq.rst:81 msgid "" "You can enable or disable read receipts on Android. Other platforms may " "still be working on this feature. Please see :doc:`All Features by Client " "` for the current status." msgstr "" #: ../../../user/faq.rst:86 msgid "Does Jami support typing notifications? Can I turn them on or off?" msgstr "" #: ../../../user/faq.rst:88 msgid "" "Most of the client support sending and receiving typing notifications. You " "can enable/disable them in the general settings." msgstr "" #: ../../../user/faq.rst:92 msgid "Can I share my screen?" msgstr "" #: ../../../user/faq.rst:94 msgid "" "Yes, on all platforms except for iOS. Search for a dedicated \"Share " "screen\" button while you are in a video call." msgstr "" #: ../../../user/faq.rst:99 msgid "Can I make group conference calls?" msgstr "" #: ../../../user/faq.rst:101 msgid "" "Yes. You can add Jami contacts to existing calls (audio or video) by " "clicking the \"Add participant\" button." msgstr "" #: ../../../user/faq.rst:105 msgid "Does Jami have group chats?" msgstr "" #: ../../../user/faq.rst:107 msgid "" "Yes, Jami now has :doc:`../developer/swarm` group chats. However, they are " "currently experimental and must be manually enabled from application " "settings. Also, group chats are currently limited to 8 participants (so " "that bugs and issues could be more easily found and fixed in smaller " "scenarios, and hopefully lift this limit in the future)." msgstr "" #: ../../../user/faq.rst:115 msgid "Why aren't my sent messages showing up on all linked devices?" msgstr "" #: ../../../user/faq.rst:117 msgid "" "Before :doc:`../developer/swarm`, an account's devices would receive the " "same messages from contacts if the device was online at the time of the " "message being sent, but *sent* messages would not show up on devices other " "than the one sending the message." msgstr "" #: ../../../user/faq.rst:122 msgid "" "With the introduction of Swarm, conversation histories of new Swarm " "conversations (including one-on-one conversations) are fully synchronized " "between all of an account's linked devices. If you are using an older " "version of Jami, please upgrade to the latest version with Swarm support. " "The latest version of Jami is always available from the Download page of the" " Jami website, at https://jami.net/download/." msgstr "" #: ../../../user/faq.rst:130 msgid "" "To learn more about Swarm, you can read our blog post `Synchronizing " "conversation history with Swarm `_ and see the :doc:`../developer/swarm` " "page of the Jami developer manual." msgstr "" #: ../../../user/faq.rst:137 msgid "Can I message offline contacts?" msgstr "" #: ../../../user/faq.rst:139 msgid "" "With :doc:`../developer/swarm` conversations, every device stores all a copy" " of all of the messages in that conversation. If a device (whether your " "own, or another participant's) is not available/online when a message is " "sent, when it comes back online again it will try to fetch any new messages " "from other online devices/peers and synchronize message history. This can " "be done whenever at least one other device that has a copy of the new " "messages is also online." msgstr "" #: ../../../user/faq.rst:147 msgid "" "You can read more about how Swarm conversations are synchronized in our blog" " post `Synchronizing conversation history with Swarm " "`_." msgstr "" #: ../../../user/faq.rst:152 msgid "" "If the participants in a conversation are often not online at the same time " "(for instance, due to timezone differences), one of them might choose to set" " up Jami on an often-online device that would receive the messages from each" " participant and relay it to the other(s) whenever they come online. Thus, " "acting similarly to a \"server\", all the while Jami remains distributed by " "nature." msgstr "" #: ../../../user/faq.rst:162 msgid "Where are the configuration files located?" msgstr "" #: ../../../user/faq.rst:164 msgid "" "Jami saves its configuration (account, certificates, history) at different " "locations depending on the platform." msgstr "" #: ../../../user/faq.rst:167 msgid "" "**GNU/Linux**: global configuration is under ``~/.config/jami/dring.yml``, " "and account-specific files are under ``~/.local/share/jami/``. Finally, " "there is a cache directory at ``~/.cache/jami/``." msgstr "" #: ../../../user/faq.rst:172 msgid "" "**macOS**: the full configuration is under ``~/Library/Application " "Support/Jami/`` if installed via https://jami.net. The app store version " "uses " "``~/Library/Containers/com.savoirfairelinux.ring.macos/Data/Library/Application" " Support/jami/``." msgstr "" #: ../../../user/faq.rst:177 msgid "" "**Android**: the full configuration is under ``/data/data/cx.ring/`` (may " "require root privileges to view or change from outside Jami)." msgstr "" #: ../../../user/faq.rst:180 msgid "" "**Windows**: global configuration is under " "``%AppData%/Local/jami/dring.yml``, and account-specific files are under " "``%AppData%/Local/jami/``. Finally, there is a cache directory at " "``%USERPROFILE%/.cache/jami/``." msgstr "" #: ../../../user/faq.rst:185 msgid "" "Note: audio and video messages are recorded in the local-data in the folder:" " ``sent_data``" msgstr "" #: ../../../user/faq.rst:188 msgid "" "For files, if a file is saved (right click on the file, then Save) it will " "be added to the directory you configured in the application settings." msgstr "" #: ../../../user/faq.rst:193 msgid "How much bandwidth do I need for calls?" msgstr "" #: ../../../user/faq.rst:195 msgid "" "For audio calls, Jami uses about 100 Kbps. For a video call, you need about" " 2 Mbit/s for medium quality. If your connection is slower, the bitrate " "will be automatically reduced." msgstr "" #: ../../../user/faq.rst:199 msgid "" "If you are hosting a video conference, you will approximately need an " "additional 2 Mbps per participant. So, for example for a conference with 10" " participants, each participant will need 2 Mbps up & down and the host will" " need 20 Mbps up and down." msgstr "" #: ../../../user/faq.rst:204 msgid "" "Jami also uses an algorithm to change the consumption depending of the " "quality of the link. So, the bitrate can have a minimum of 200 Kbit/s and " "maximum of 6 Mbit/s." msgstr "" #: ../../../user/faq.rst:209 msgid "" "How can Savoir-Faire Linux Inc. (SFL) afford to give Jami away for free? How" " does SFL make money with Jami?" msgstr "" #: ../../../user/faq.rst:211 msgid "" "`Savoir-Faire Linux Inc. `_ (SFL) is a " "consulting company with some R&D projects. Jami is a GPLv3+ project and this" " will not change. SFL already sells services for several fields of expertise" " (hosting, developing websites and applications, embedded software, etc). " "Jami is financed several ways:" msgstr "" #: ../../../user/faq.rst:216 msgid "" "`Donations `_" msgstr "" #: ../../../user/faq.rst:217 msgid "Customization contracts" msgstr "" #: ../../../user/faq.rst:218 msgid "Services for other projects" msgstr "" #: ../../../user/faq.rst:219 msgid "Visibility" msgstr "" #: ../../../user/faq.rst:220 msgid "R&D" msgstr "" #: ../../../user/faq.rst:221 msgid "https://jami.biz" msgstr "" #: ../../../user/faq.rst:223 msgid "As a distributed system, Jami incurs very low costs by design" msgstr "" #: ../../../user/faq.rst:224 msgid "" "Opt-in collection of anonymized statistics might be added in the future to " "better understand Jami usage; however, no personal data will be collected." msgstr "" #: ../../../user/faq.rst:227 msgid "Account management" msgstr "" #: ../../../user/faq.rst:230 msgid "What is a Jami account?" msgstr "" #: ../../../user/faq.rst:232 msgid "" "A Jami account is an `asymmetric encryption key " "`_. Your account is " "identified by a Jami ID, which is a `fingerprint " "`_ of your public key." msgstr "" #: ../../../user/faq.rst:239 msgid "What information do I need to provide to create a Jami account?" msgstr "" #: ../../../user/faq.rst:241 msgid "" "When you create a new Jami account, you don't have to provide any private " "information like an email, address, or phone number." msgstr "" #: ../../../user/faq.rst:244 msgid "" "This is the information you can provide if you choose (it's all optional):" msgstr "" #: ../../../user/faq.rst:247 msgid "An avatar." msgstr "" #: ../../../user/faq.rst:248 msgid "" "A display name, which is the name that clients will display for your " "contact. It can contain special characters." msgstr "" #: ../../../user/faq.rst:250 msgid "" "An optional username, which is a unique identifier that is directly " "associated with your Jami ID. This username->Jami ID mapping is stored on a" " server (``ns.jami.net`` by default, but you can host your own)." msgstr "" #: ../../../user/faq.rst:254 msgid "" "A password. This password is used to protect the account archive in your " "device." msgstr "" #: ../../../user/faq.rst:257 msgid "" "More information about Jami accounts is available in the :ref:`Technical " "Overview `." msgstr "" #: ../../../user/faq.rst:261 msgid "Where is my Jami ID?" msgstr "" #: ../../../user/faq.rst:263 msgid "" "Your Jami ID should be displayed prominently in whichever app you're using." " It looks like a long string of letters and numbers; for example: " "``f2c815f5554bcc22689ce84d45aefdda1bce9146``." msgstr "" #: ../../../user/faq.rst:268 msgid "Why don't I have to use a password?" msgstr "" #: ../../../user/faq.rst:270 msgid "" "You are not forced to have a password on your account. On a centralized " "system you would use your password to authenticate with a public server " "where your account is stored. Someone who knows your password could steal " "your identity." msgstr "" #: ../../../user/faq.rst:275 msgid "" "With Jami, your account is stored in a :ref:`folder ` on your device. **The password is only used " "to encrypt your account in order to protect you from someone who has " "physical access to your device.**" msgstr "" #: ../../../user/faq.rst:280 msgid "" "If your device is encrypted, you may not want or need to use a password, and" " indeed recent versions of Jami don't ask for an account encryption password" " by default when creating new accounts." msgstr "" #: ../../../user/faq.rst:284 msgid "" "Note: changing a password will only change the password on the current " "device and it's not synced (because their is no server and other devices can" " be offline anyway)." msgstr "" #: ../../../user/faq.rst:289 msgid "Why don't I have to register a username?" msgstr "" #: ../../../user/faq.rst:291 msgid "" "The most permanent, secure identifier is your :ref:`Jami ID `, but since these are difficult to use for some people, you " "also have the option of registering a username. Username registration " "requires a name server, such as Jami's default one at ``ns.jami.net``." msgstr "" #: ../../../user/faq.rst:297 msgid "" "If you don't register a username, you can still choose to register one later" " at any time." msgstr "" #: ../../../user/faq.rst:300 msgid "" "If you host your own nameserver at ``example.com``, usernames registered " "there can be looked up by searching for ``username@example.com``." msgstr "" #: ../../../user/faq.rst:304 msgid "Can I change my username?" msgstr "" #: ../../../user/faq.rst:306 msgid "" "With the default nameserver (``ns.jami.net``) you cannot change your " "username." msgstr "" #: ../../../user/faq.rst:310 msgid "What is the difference between a username and a display name?" msgstr "" #: ../../../user/faq.rst:312 msgid "" "You can use your username as an identifier. The username points to your " ":ref:`Jami ID `, which is your permanent, " "secure identifier. Two people cannot have the same username." msgstr "" #: ../../../user/faq.rst:317 msgid "" "A display name allows you to choose another name that identifies you to your" " contacts. Display names can be edited or changed at any time and only your" " contacts can see them." msgstr "" #: ../../../user/faq.rst:322 msgid "How can I back up my account?" msgstr "" #: ../../../user/faq.rst:324 msgid "There are two ways to back up your account:" msgstr "" #: ../../../user/faq.rst:326 msgid "" "Link another device to your account so your account will be on two devices." " You can find this option in the account settings page." msgstr "" #: ../../../user/faq.rst:328 msgid "" "Back up the :ref:`account archive `. This file can be found in the account files :ref:`folder " "`. In some clients, " "you can export this archive from the account settings." msgstr "" #: ../../../user/faq.rst:335 msgid "Can I retrieve my username without my keys?" msgstr "" #: ../../../user/faq.rst:337 msgid "" "If you used the default name server at ``ns.jami.net``, **you can not**. " "There is no way to prove it's your username without your key." msgstr "" #: ../../../user/faq.rst:340 msgid "" "If you use a different name server, there may be a way to move a username to" " a new Jami ID at the discretion of the administrator of that name server." msgstr "" #: ../../../user/faq.rst:344 msgid "" "For more information about name servers, see :doc:`../developer/name-server-" "protocol`." msgstr "" #: ../../../user/faq.rst:348 msgid "Can I recover my account if I forget my password?" msgstr "" #: ../../../user/faq.rst:350 msgid "" "No. There can not be a traditional account recovery process; you are the " "only person with access to your data. If you are worried about forgetting " "your password, please use a password manager." msgstr "" #: ../../../user/faq.rst:355 msgid "What happens when I delete my account?" msgstr "" #: ../../../user/faq.rst:357 msgid "" "Your account is only stored on your own devices. If you delete your account" " from each device, the account is gone and you cannot get it back (unless " "you already made a backup of it earlier). Nobody else can use your account " "after that." msgstr "" #: ../../../user/faq.rst:362 msgid "" "Your contacts will still have the messages you sent them, but all public " "record of your account on the DHT will eventually disappear due to absence " "and lack of activity." msgstr "" #: ../../../user/faq.rst:366 msgid "" "The default ``ns.jami.net`` name server **does not** delete any registered " "usernames -- other name servers might (not recommended), at their " "administrator's discretion. So, if you have an account with a username " "registered on the default name server and you delete or lose your account, " "and did not back up your account earlier, nobody (including you) will be " "able to register a new account with that username again, thus nobody can " "reach you at that username anymore." msgstr "" #: ../../../user/faq.rst:375 msgid "" "To avoid losing your account **please** :ref:`back it up `!" msgstr "" #: ../../../user/faq.rst:379 msgid "What happens when I link a new device?" msgstr "" #: ../../../user/faq.rst:381 msgid "" "When you link a device to your account, your :ref:`account archive " "` is put on the Jami " "network for a few minutes. It is protected with a password Jami gives you." msgstr "" #: ../../../user/faq.rst:386 msgid "" "The new device receives your full account certificate with the master RSA " "keys, but it generates a new device key for signing/encrypting messages." msgstr "" #: ../../../user/faq.rst:392 msgid "Advanced" msgstr "" #: ../../../user/faq.rst:395 msgid "What protocol does Jami use for the end-to-end encryption?" msgstr "" #: ../../../user/faq.rst:397 msgid "" "We use TLS 1.3 with a perfect forward secrecy requirement for the negotiated" " ciphers for calls and file transfers. Messages are encrypted with an RSA " "key." msgstr "" #: ../../../user/faq.rst:403 msgid "" "What data passes through my machine when I participate in the Jami network?" msgstr "" #: ../../../user/faq.rst:405 msgid "**All these data are encrypted**. There is:" msgstr "" #: ../../../user/faq.rst:407 msgid "" "ICE descriptors of other Jami users (ICE is a protocol that helps " "establishing communication between two computers)" msgstr "" #: ../../../user/faq.rst:409 msgid "certain text messages" msgstr "" #: ../../../user/faq.rst:410 msgid "accounts currently being linked to a new device, as explained above." msgstr "" #: ../../../user/faq.rst:412 msgid "" "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." msgstr "" #: ../../../user/faq.rst:418 msgid "Why am I able to communicate with myself?" msgstr "" #: ../../../user/faq.rst:420 msgid "Many users use Jami to transfer data from one machine to another." msgstr "" #: ../../../user/faq.rst:423 msgid "Should I enable push notifications?" msgstr "" #: ../../../user/faq.rst:425 msgid "" "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." msgstr "" #: ../../../user/faq.rst:432 msgid "What is a bootstrap server?" msgstr "" #: ../../../user/faq.rst:434 msgid "" "A bootstrap server is the entry point of the distributed network. To enter " "in a network, Jami must know one other node. This is the role of the " "bootstrap. It can be any node in the network, but, bootstrap nodes are " "generally always up and available. The default one in Jami is " "``bootstrap.jami.net``." msgstr "" #: ../../../user/faq.rst:441 msgid "What is a TURN server? What is STUN?" msgstr "" #: ../../../user/faq.rst:443 msgid "" "A TURN server is a relay, and is generally used when two peers can not " "contact to each other due to some firewall restriction, have NAT without any" " opened port, and no IPv6." msgstr "" #: ../../../user/faq.rst:447 msgid "" "A STUN server is only used for SIP accounts, and is generally used to get " "your public IP. For Jami accounts, the DHT already gives this information." msgstr "" #: ../../../user/faq.rst:452 msgid "What is DHT proxy?" msgstr "" #: ../../../user/faq.rst:454 msgid "" "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." msgstr "" #: ../../../user/faq.rst:459 msgid "Generally, to transfer data between two peers, there are 3 steps:" msgstr "" #: ../../../user/faq.rst:461 msgid "Exchange candidates (IPs) via the DHT" msgstr "" #: ../../../user/faq.rst:462 msgid "Negotiate the best p2p channel between the peers" msgstr "" #: ../../../user/faq.rst:463 msgid "Transfer data on this socket." msgstr "" #: ../../../user/faq.rst:465 msgid "The DHT is only used for the first step." msgstr "" #: ../../../user/faq.rst:468 msgid "" "What if I disable the DHT proxy on Android and what about push " "notifications?" msgstr "" #: ../../../user/faq.rst:470 msgid "There is basically 3 modes on how to use the Android application:" msgstr "" #: ../../../user/faq.rst:472 msgid "" "With push notifications (DHT proxy must be enabled). This mode supports" msgstr "" #: ../../../user/faq.rst:473 msgid "" "notifications for Android (via Google/Firebase, and soon UnifiedPush or " "Apple/APN). This decrease battery usage, by removing the sync needed with " "the DHT and without any socket always alive. + Without push notifications " "but with DHT proxy enabled. This avoids the application synchronizing with " "other nodes, but \"Run in background\" MUST be enabled to avoid the " "operating system killing the application. + Without DHT proxy. In this case," " \"Run in background\" MUST be enabled to avoid the operating system killing" " the application. The application will synchronize with the other DHT nodes." msgstr "" #: ../../../user/faq.rst:483 msgid "" "I still have issues with the Android application even if battery " "optimization is disabled" msgstr "" #: ../../../user/faq.rst:485 msgid "" "Please read https://dontkillmyapp.com for more details. If it does not solve" " your issue, you can open a bug report (ideally with a scenario to help us " "to reproduce and/or logs)." msgstr "" #: ../../../user/faq.rst:490 msgid "How does the username registration service work?" msgstr "" #: ../../../user/faq.rst:492 msgid "" "With the default name server (``ns.jami.net``), the usernames are registered" " on an Ethereum blockchain. If you are a developer, you can build your own " "name server with the underlying data storage technology of your choice (e.g." " you could use a SQL database rather than using a blockchain)." msgstr "" #: ../../../user/faq.rst:498 msgid "" "With the default name server, you can look up usernames at " "``https://ns.jami.net/name/test``, where ``test`` is a username for which we" " are looking for a matching :doc:`Infohash <../developer/jami-identifiers>`." " Once registered, this name server **does not** provide any way to remove " "the mapping." msgstr "" #: ../../../user/faq.rst:504 msgid "Read more about the Jami :doc:`../developer/name-server-protocol`." msgstr "" #: ../../../user/faq.rst:507 msgid "How can I change the timeout for a call?" msgstr "" #: ../../../user/faq.rst:509 msgid "" "In the ``dring.yml`` file (see :ref:`user/faq:Where are the configuration " "files located?`), you can change the ``ringingTimeout`` (in seconds)." msgstr "" #: ../../../user/faq.rst:514 msgid "How to back up and reimport conversations and accounts" msgstr "" #: ../../../user/faq.rst:516 msgid "This is only for clients based on LRC (desktop ones)." msgstr "" #: ../../../user/faq.rst:518 msgid "" "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)." msgstr "" #: ../../../user/faq.rst:522 msgid "" "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!" msgstr "" #: ../../../user/faq.rst:529 msgid "How secure are you?" msgstr "" #: ../../../user/faq.rst:531 msgid "" "**We use TLS/SRTP to secure connection and communications over the " "network.**" msgstr "" #: ../../../user/faq.rst:534 msgid "" "We implement SRTP over SIP using recommendations described in the following " "two RFCs:" msgstr "" #: ../../../user/faq.rst:537 msgid "`RFC 3711 `_" msgstr "" #: ../../../user/faq.rst:538 msgid "`RFC 4568 `_" msgstr "" #: ../../../user/faq.rst:540 msgid "" "Typically 2 kinds of sockets are negotiated. One for the control socket, " "the other for the media sockets." msgstr "" #: ../../../user/faq.rst:543 msgid "Typical control session will use the following cipher suite::" msgstr "" #: ../../../user/faq.rst:548 msgid "DTLS (fallback) supported::" msgstr "" #: ../../../user/faq.rst:552 msgid "TLS::" msgstr "" #: ../../../user/faq.rst:556 msgid "Supported crypto suite for the media session are:" msgstr "" #: ../../../user/faq.rst:558 msgid "``AES_CM_128_HMAC_SHA1_80 / SRTP_AES128_CM_HMAC_SHA1_80``" msgstr "" #: ../../../user/faq.rst:559 msgid "``AES_CM_128_HMAC_SHA1_32 / SRTP_AES128_CM_HMAC_SHA1_32``" msgstr "" #: ../../../user/faq.rst:562 msgid "When do public IPs get exposed?" msgstr "" #: ../../../user/faq.rst:564 msgid "" "We can consider three main connectivity scenarios: (1) a classic " "configuration, (2) behind a VPN, (3) via Tor. As Jami is a p2p application," " the reader would probably know that (2) or (3) is a bit mandatory to avoid " "IP leaking." msgstr "" #: ../../../user/faq.rst:569 msgid "" "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 as far as" " I know most other Jami developers) use the first scenario (sometimes the " "second one), and we surely can not test all the possible networks " "configurations we would like to, so if you discover a bug, please :doc:`open" " an issue `." msgstr "" #: ../../../user/faq.rst:576 msgid "Anyway, in these 3 scenarios, there are 3 main actions:" msgstr "" #: ../../../user/faq.rst:578 msgid "sending a message (this will use the DHT);" msgstr "" #: ../../../user/faq.rst:579 msgid "" "sending a file (TCP ICE connection as described here: " ":doc:`../developer/file-transfer`; and" msgstr "" #: ../../../user/faq.rst:581 msgid "" "placing a call (TCP + UDP ICE connection as described here: " ":doc:`../developer/calls`)." msgstr "" #: ../../../user/faq.rst:585 msgid "Classic config" msgstr "" #: ../../../user/faq.rst:587 ../../../user/faq.rst:613 #: ../../../user/faq.rst:647 msgid "Send a message" msgstr "" #: ../../../user/faq.rst:589 msgid "" "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)." msgstr "" #: ../../../user/faq.rst:599 ../../../user/faq.rst:633 #: ../../../user/faq.rst:653 msgid "Send a file" msgstr "" #: ../../../user/faq.rst:601 msgid "" "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." msgstr "" #: ../../../user/faq.rst:606 msgid "Calls" msgstr "" #: ../../../user/faq.rst:608 msgid "Same as above, the IP is present in the ICE." msgstr "" #: ../../../user/faq.rst:611 msgid "Behind a VPN" msgstr "" #: ../../../user/faq.rst:615 msgid "" "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:" msgstr "" #: ../../../user/faq.rst:630 msgid "" "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" msgstr "" #: ../../../user/faq.rst:635 msgid "" "Same as above, the ICE will contains: + addresses from your LAN + public " "address of your VPN + TURN address if TURN is enabled" msgstr "" #: ../../../user/faq.rst:638 ../../../user/faq.rst:676 msgid "Do a call" msgstr "" #: ../../../user/faq.rst:640 msgid "" "Same as above, your public address is replaced by your VPN address. You can " "see it in the logs from daemon. See :ref:`user/bug-report-guide:logs`." msgstr "" #: ../../../user/faq.rst:645 msgid "Tor" msgstr "" #: ../../../user/faq.rst:649 msgid "" "Tor basically does not supports UDP. This means that you can not use your " "DHT node locally, you MUST use a DHTProxy. That proxy will see the Exit " "node." msgstr "" #: ../../../user/faq.rst:655 msgid "" "I prefer a proof that any description. So, I did a file transfer with Jami +" " TOR. This is what I see in the logs for the remote:" msgstr "" #: ../../../user/faq.rst:667 msgid "" "The first ones are some 192.168.x.x so we don't care. 51.254.39.157 is the " "TURN address in France (my device is in the Canada). 185.220.101.24 is the " "Tor exit node:" msgstr "" #: ../../../user/faq.rst:678 msgid "" "This will not work (actually, you can create the SIP control connection " "because it's a TCP connection), but medias are negotiated in UDP, so this " "will fail." msgstr "" #: ../../../user/faq.rst:683 msgid "What ports does Jami use?" msgstr "" #: ../../../user/faq.rst:685 msgid "" "Jami works as a server and gets new ports for each connections (randomly " "bound). These are the ranges that can be used for each component:" msgstr "" #: ../../../user/faq.rst:688 msgid "dht: UDP [4000, 8888]" msgstr "" #: ../../../user/faq.rst:689 msgid "audio: UDP [16384-32766]" msgstr "" #: ../../../user/faq.rst:690 msgid "video: UDP [49152-65534]" msgstr "" #: ../../../user/faq.rst:691 msgid "SIP Control: UDP/TCP randomly bound" msgstr "" #: ../../../user/faq.rst:693 msgid "" "Note: if UDP is blocked, a dhtproxy can be used to use TCP instead. Note " "that medias will not work cause it only supports UDP." msgstr "" #: ../../../user/faq.rst:696 msgid "So for ufw, we recommend running ``sudo ufw default allow outgoing``." msgstr "" #: ../../../user/faq.rst:698 msgid "" "For now, you can not specify a specific range to configure ports used by " "Jami. The inbound traffic can be controlled without issue, Jami should work " "and can use a TURN server if needed." msgstr "" #: ../../../user/faq.rst:702 msgid "If you run your own proxy or nameserver:" msgstr "" #: ../../../user/faq.rst:704 msgid "dhtproxy, nameserver: TCP [80-100], 443" msgstr "" #: ../../../user/faq.rst:706 msgid "If you run your own TURN server:" msgstr "" #: ../../../user/faq.rst:708 msgid "TURN/STUN: TCP+UDP 3478, 5349" msgstr "" #: ../../../user/faq.rst:711 msgid "Can I use Jami in a local network (LAN) without internet access?" msgstr "" #: ../../../user/faq.rst:713 msgid "" "Yes! Thanks to Jami's architecture, Jami users on a local/private network " "can communicate among themselves using Jami, without requiring any outside " "connectivity such as the internet." msgstr "" #: ../../../user/faq.rst:717 msgid "" "To do so, from Jami's ``Account`` settings open ``Advanced account " "settings``. There, enable the ``Enable local peer discovery`` setting. " "Additionally, you may want to manually set the ``bootstrap`` node's address " "(default: ``bootstrap.jami.net``) to the IP address of another device on " "your network that also runs Jami and/or an OpenDHT node." msgstr "" #: ../../../user/faq.rst:724 msgid "" "If you will use this Jami account for communicating only with only with " "other devices on the same local/private network, you can disable TURN if you" " wish. If you do so, and later you decide to use this account also for " "communicating with other Jami devices outside your network, don't forget to " "enable TURN again, as it helps Jami work around issues with some overly " "restrictive firewalls." msgstr "" #: ../../../user/faq.rst:733 msgid "How can I configure the codecs even more?" msgstr "" #: ../../../user/faq.rst:735 msgid "" "Codecs can be configured via a file. In the configurations files, you can " "create a file called ``encoder.json`` like this:" msgstr "" #: ../../../user/faq.rst:755 msgid "or:" msgstr "" #: ../../../user/faq.rst:765 msgid "" "This file is :ref:`located in the same directory ` as ``dring.yml``." msgstr "" #: ../../../user/faq.rst:768 msgid "" "To check which options are supported, use the command ``ffmpeg -h " "encoder=[encoder_name]``, where ``encoder_name`` can be any of ``libx264``, " "``libvpx``, ``mpeg4``, ``h263``, ``libopus``, ``libspeex``, ``g722``, " "``pcm_alaw``, or ``pcm_mulaw`` (the FFmpeg names for all of Jami's supported" " encoders)." msgstr "" #: ../../../user/faq.rst:775 msgid "How can I configure the audio processor?" msgstr "" #: ../../../user/faq.rst:777 msgid "" "An audio processor allows Jami to clean up and process your microphone's " "audio. It can remove echo, reduce noise, and equalize your microphone's " "volume. Additionally, it can detect when you're speaking and send this " "information to participants in your call. The audio processor settings can " "be set in your ``dring.yml`` file. See :ref:`this section to find where this" " file is located `." msgstr "" #: ../../../user/faq.rst:783 msgid "The relevant preference keys are:" msgstr "" #: ../../../user/faq.rst:785 msgid "" "``audioProcessor``, which configures which audio processor to use. The valid" " options are:" msgstr "" #: ../../../user/faq.rst:787 msgid "" "``webrtc``: the `WebRTC Audio Processing library " "`_" msgstr "" #: ../../../user/faq.rst:788 msgid "" "``speex``: the `Speex DSP library `_" msgstr "" #: ../../../user/faq.rst:789 msgid "" "``null``: disables audio processing (though your system echo canceller may " "still be used, see below)" msgstr "" #: ../../../user/faq.rst:791 msgid "" "``echoCancel``, which configures how echo cancelling should be done. The " "valid options are:" msgstr "" #: ../../../user/faq.rst:793 msgid "" "``auto``: try to use your operating system's echo canceller (if it exists), " "otherwise fall back to the chosen audio processor's echo canceller" msgstr "" #: ../../../user/faq.rst:794 msgid "" "``audioProcessor``: only use the chosen audio processor's echo canceller" msgstr "" #: ../../../user/faq.rst:795 msgid "``system``: only use your operating system's echo canceller" msgstr "" #: ../../../user/faq.rst:796 msgid "``null``: don't do any echo cancelling" msgstr "" #: ../../../user/faq.rst:798 msgid "" "``noiseReduce``, ``true``/``false`` to set noise reduction on the audio " "processor" msgstr "" #: ../../../user/faq.rst:799 msgid "" "``automaticGainControl``, ``true``/``false`` to set automatic gain control " "on the audio processor" msgstr "" #: ../../../user/faq.rst:800 msgid "" "``voiceActivityDetection``, ``true``/``false`` to set voice activity " "detection on the audio processor" msgstr "" #: ../../../user/index.rst:3 msgid "User manual" msgstr "" #: ../../../user/index.rst:5 msgid "" "The Jami user manual introduces Jami and its features, provides additional " "information on methods of installing Jami, answers users' most common " "questions in the FAQ (frequently asked questions), and includes various user" " guides and tutorials for users, such as the :doc:`bug-report-guide` with " "step-by-step instructions for reporting bugs and issues." msgstr "" #: ../../../user/introduction.rst:2 msgid "Introduction" msgstr "" #: ../../../user/introduction.rst:4 msgid "Jami logo" msgstr "" #: ../../../user/introduction.rst:7 msgid "" "Jami is a free/libre, end-to-end encrypted and private communication " "platform that requires no central authority." msgstr "" #: ../../../user/introduction.rst:10 msgid "" "Jami's features include: text chats, voice and video calls, screen sharing, " "file sharing, conference calls, and :doc:`group chats <../developer/swarm>`." " Jami can also function as a regular SIP client." msgstr "" #: ../../../user/introduction.rst:15 msgid "" "Jami works on GNU/Linux, Windows, macOS, iOS, and Android. Multiple devices" " can be linked to a Jami account, and no personal information is required to" " create an account." msgstr "" #: ../../../user/introduction.rst:20 msgid "How does Jami work?" msgstr "" #: ../../../user/introduction.rst:22 msgid "" "Jami uses a `distributed hash table " "`_ (DHT) to connect " "peers. Jami accounts are asymmetric `X.509 certificates " "`_ generated by the GnuTLS library. " "Calls are made over the `Session Initiation Protocol " "`_ (SIP) after " "negotiating a `TLS " "`_-encrypted secure " "connection, performing `Secure Real-time Transport Protocol " "`_ (SRTP)" " communication which carries the media streams." msgstr "" #: ../../../user/introduction.rst:34 msgid "" "For more on how Jami works, see the `Jami and how it empowers users " "`_ talk by `Amin " "Bandali `_, as well as the :doc:`Technical " "Overview <../developer/technical-overview>` for more in-depth information." msgstr "" #: ../../../user/introduction.rst:41 msgid "Who makes Jami?" msgstr "" #: ../../../user/introduction.rst:43 msgid "" "The Jami project is led by `Savoir-faire Linux Inc. " "`_ -- a Canadian/Québécois GNU/Linux " "consulting company -- and is supported by a global community of free " "software enthusiasts, users, and contributors." msgstr "" #: ../../../user/introduction.rst:48 msgid "" "Jami is `free software `_ and " "an official GNU package, developed and distributed under the `GNU GPLv3+ " "`_ license." msgstr "" #: ../../../user/jami-distributed-network.md:1 msgid "Jami distributed network" msgstr "" #: ../../../user/jami-distributed-network.md:4 msgid "Connectivity" msgstr "" #: ../../../user/jami-distributed-network.md:6 msgid "" "Jami relies on a [distributed network](tutorials/Jami-distributed-network), " "that brings multiple advantages when compared to federated networks:" msgstr "" #: ../../../user/jami-distributed-network.md:10 msgid "No point of failure," msgstr "" #: ../../../user/jami-distributed-network.md:11 msgid "More resilient to censorship," msgstr "" #: ../../../user/jami-distributed-network.md:12 msgid "Do not depend on anything other than its users," msgstr "" #: ../../../user/jami-distributed-network.md:13 msgid "Trust amongst nodes is not necessary." msgstr "" #: ../../../user/jami-distributed-network.md:15 msgid "" "![Network-topo](https://git.jami.net/savoirfairelinux/jami-" "project/uploads/9b725e440c2705a2a3c4d0a3df092066/Network-topo.png)" msgstr "" #: ../../../user/jami-distributed-network.md:15 msgid "Network-topo" msgstr "" #: ../../../user/jami-distributed-network.md:17 msgid "This network forms a Distributed Hash Table (DHT)" msgstr "" #: ../../../user/jami-distributed-network.md:19 msgid "" "The core problem of distributed communication systems is peer connectivity, " "Jami achieves it through two elements:" msgstr "" #: ../../../user/jami-distributed-network.md:22 msgid "Encrypted announcements on DHT," msgstr "" #: ../../../user/jami-distributed-network.md:23 msgid "Use of standard protocols for NAT hole punching." msgstr "" #: ../../../user/jami-distributed-network.md:25 msgid "Jami is built on two distinct distributed networks:" msgstr "" #: ../../../user/jami-distributed-network.md:27 msgid "" "the OpenDHT kademlia network to provide distributed connectivity " "establishment and message distribution," msgstr "" #: ../../../user/jami-distributed-network.md:29 msgid "the JamiNS blockchain to provide distributed name registration." msgstr "" #: ../../../user/jami-distributed-network.md:31 msgid "The OpenDHT network" msgstr "" #: ../../../user/jami-distributed-network.md:34 msgid "" "See " "[](https://github.com/savoirfairelinux/opendht)" " for more information about OpenDHT, which provides a distributed key-value " "datastore for connectivity establishment (with ICE) and message distribution" " in Jami." msgstr "" #: ../../../user/jami-distributed-network.md:40 msgid "" "An OpenDHT network can be joined by knowing about any node already connected" " to the network. This node will then share its knowledge about other nodes " "on the network." msgstr "" #: ../../../user/jami-distributed-network.md:44 msgid "" "Jami clients use a persistent node cache to reconnect to the network after a" " first session. A configurable, known, stable \"bootstrap\" node is used for" " the first connection or if cached nodes don't answer." msgstr "" #: ../../../user/jami-distributed-network.md:48 msgid "" "Jami clients currently use bootstrap.jami.net:4222 as the default " "(configurable) bootstrap node and network ID 0 (the default, public OpenDHT " "network)." msgstr "" #: ../../../user/jami-distributed-network.md:52 msgid "Contribute to the OpenDHT network" msgstr "" #: ../../../user/jami-distributed-network.md:54 msgid "" "Every Jami account runs an OpenDHT node, contributing to the network and " "allowing Jami to scale." msgstr "" #: ../../../user/jami-distributed-network.md:57 msgid "" "Jami users can have full independence by running their own stable OpenDHT " "node and configure it as a bootstrap node in Jami, while helping to improve " "stability, robustness and resilience for every user of the public OpenDHT " "network." msgstr "" #: ../../../user/jami-distributed-network.md:62 msgid "" "A standalone node can be run using the [dhtnode " "utility](https://github.com/savoirfairelinux/opendht/wiki/Running-a-node-" "with-dhtnode) included with OpenDHT. dhtnode doesn't persist any data and " "has a default in-memory storage limit of 8 MiB." msgstr "" #: ../../../user/jami-distributed-network.md:67 msgid "" "Stable community-run DHT nodes will be added to the default bootstrap list " "at the request of their owner, as more bootstrap nodes means a more " "resilient, independent network." msgstr "" #: ../../../user/jami-distributed-network.md:71 msgid "The JamiNS blockchain" msgstr "" #: ../../../user/jami-distributed-network.md:74 msgid "" "The JamiNS blockchain is experimental and its architecture is expected to " "evolve." msgstr "" #: ../../../user/jami-distributed-network.md:77 msgid "" "Jami clients don't run blockchain nodes themselves but rather communicate " "with a JamiNS server using HTTP for name registration and query, with a REST" " API. This is because the resources needed to run a blockchain node are too " "high for most end-users." msgstr "" #: ../../../user/jami-distributed-network.md:82 msgid "" "The nameserver can be configured by-account in Jami, allowing to connect " "Jami clients to various more or less centralized user directories." msgstr "" #: ../../../user/jami-distributed-network.md:85 msgid "Contribute to the JamiNS blockchain" msgstr "" #: ../../../user/jami-distributed-network.md:87 msgid "" "The default Jami name service is ns.jami.net, provided by Savoir-faire Linux" " Inc., connected to an Ethereum blockchain node; the goal being to give " "everyone the possibility (if they which so) to run their own blockchain node" " and HTTP service, mine some Ether, and use it to pay the transaction fee " "needed to register their username in Jami." msgstr "" #: ../../../user/jami-distributed-network.md:93 msgid "" "Code of the Ethereum contract, the blockchain genesis file, and the NodeJS " "module (HTTP server) can be found here : " "[1](https://git.jami.net/savoirfairelinux/jami-nameservice)" msgstr "" #: ../../../user/jami-distributed-network.md:97 msgid "Running a Jami Node" msgstr "" #: ../../../user/jami-distributed-network.md:99 msgid "Pre-requisites:" msgstr "" #: ../../../user/jami-distributed-network.md:100 msgid "" "Geth 1.8.23+ (download from [HERE](https://geth.ethereum.org/downloads/))" msgstr "" #: ../../../user/jami-distributed-network.md:101 msgid "" "Jami genesis file (download from " "[HERE](https://git.jami.net/savoirfairelinux/jami-" "nameservice/blob/master/instructions/genesis.json))" msgstr "" #: ../../../user/jami-distributed-network.md:104 msgid "Joining the Jami Network" msgstr "" #: ../../../user/jami-distributed-network.md:106 msgid "" "The process of joining the Jami network is similar to the process of joining" " a regular ethereum network with the difference that the genesis file is " "used to initialize the data directory." msgstr "" #: ../../../user/jami-distributed-network.md:108 msgid "Download the Jami genesis file from the Jami github repo" msgstr "" #: ../../../user/jami-distributed-network.md:109 msgid "" "Create a directory on your computer which you will use to store the Jami " "blockchain data" msgstr "" #: ../../../user/jami-distributed-network.md:110 msgid "Example for MacOS (/Users/username/jamichain)" msgstr "" #: ../../../user/jami-distributed-network.md:111 msgid "Example for Linux (/home/username/jamichain)" msgstr "" #: ../../../user/jami-distributed-network.md:112 msgid "Example for Windows (C:\\Users\\username\\jamichain)" msgstr "" #: ../../../user/jami-distributed-network.md:113 msgid "" "Use geth to initialize the directory you created in (2) by running ```./geth" " --datadir /home/username/jamichain init genes is.json ```" msgstr "" #: ../../../user/jami-distributed-network.md:114 msgid "" "You can now start geth with the command-line options you need and specifying" " one of Jami's bootnodes as follows:" msgstr "" #: ../../../user/jami-distributed-network.md:119 msgid "" "This will start a geth daemon with an attached console which is now syncing " "with Jami's network." msgstr "" #: ../../../user/lan-only.rst:2 msgid "Use Jami on a LAN" msgstr "" #: ../../../user/lan-only.rst:4 msgid "" "Due the distributed nature of Jami, it is possible to use it over a LAN, " "without any Internet connection. This allows you to continue to communicate " "with other people in the company/building/country without global Internet " "access. However, some services are external so in this document we will " "explain some tweaks you may need." msgstr "" #: ../../../user/lan-only.rst:16 msgid "Boostraping" msgstr "" #: ../../../user/lan-only.rst:19 msgid "What is a bootstrap?" msgstr "" #: ../../../user/lan-only.rst:21 msgid "" "Jami uses the DHT technology to find other users. So, all the users you want" " to contact must be reachable on the same DHT network (e.g. if the Internet " "is split between two buildings, users in the first buildings will not be " "able to reach the second building). To enter a DHT network, one must be able" " to reach at least one other node. This node is called bootstrap, it is the " "entry point of the network. By default, **bootstrap.jami.net** is " "configured, but any node in the public DHT can be a bootstrap (it is a " "classic node, generally always online)." msgstr "" #: ../../../user/lan-only.rst:29 msgid "" "So, if the Internet is cut, you need another bootstrap to create a network. " "On a LAN, there is two ways to configure it in Jami:" msgstr "" #: ../../../user/lan-only.rst:33 msgid "Bootstrap settings" msgstr "" #: ../../../user/lan-only.rst:35 msgid "" "In the advanced account settings, the user can configure multiple " "bootstraps. **bootstrap.jami.net** is usually the default, " "**bootstrap.jami.net;your.bootstrap.tld** will be valid. The IP:port of " "another DHT node can be specified as a bootstrap." msgstr "" #: ../../../user/lan-only.rst:40 msgid "Running a bootstrap" msgstr "" #: ../../../user/lan-only.rst:42 msgid "" "It's possible to run a DHT node to serve as a bootstrap for Jami clients. In" " this case, the bootstrap field in the settings must be replaced by the new " "bootstrap. The documentation to run a DHT node is located in OpenDHT's wiki:" " https://github.com/savoirfairelinux/opendht/wiki/Running-a-node-with-" "dhtnode" msgstr "" #: ../../../user/lan-only.rst:48 msgid "Local Peer Discovery" msgstr "" #: ../../../user/lan-only.rst:50 msgid "" "Another way is to enable peer discovery. This will announce the bootstrap on" " the network by broadcasting UDP packets (like a printer). So, UDP broadcast" " must be supported by the network in order to work. However, this method " "does not need to specify an ip:port in the settings, so it can be preferred." msgstr "" #: ../../../user/lan-only.rst:56 msgid "TURN" msgstr "" #: ../../../user/lan-only.rst:58 msgid "" "Another external service is the TURN server, used as a fallback for " "connections if the NAT block all possible connections. Generally it is " "**turn.jami.net** but can be any TURN (we use coturn, cf. " ":doc:`/developer/setting-up-your-own-turn-server`)" msgstr "" #: ../../../user/lan-only.rst:62 msgid "" "On a LAN, it may be ignored (because there will be no NAT), but disabling it" " should not be necessary (because it will not be used if unreachable)." msgstr "" #: ../../../user/lan-only.rst:66 msgid "On mobile (DHT Proxy)" msgstr "" #: ../../../user/lan-only.rst:68 msgid "" "A DHT Proxy is used with mobile devices to save battery by avoiding " "synchronization. It is generally **dhtproxy.jami.net** but can be any DHT " "node with the REST API enabled. However, if the DHT proxy is using push " "notifications it will depend on another external service (Firebase or APN or" " a UnifiedPush instance). In this case, only the third one can be self-" "hosted." msgstr "" #: ../../../user/lan-only.rst:73 msgid "" "On iOS it is basically impossible to work without push, as the OS from Apple" " will kill any application as soon as it is in background. So you can not " "disable the usage of push notifications. However, for Android, you may want " "to self-host your proxy (with or without UnifiedPush support), or you can " "disable the DHT Proxy and enable \"Run in the background\" in order to use " "your local DHT." msgstr "" #: ../../../user/lan-only.rst:80 msgid "NameServer" msgstr "" #: ../../../user/lan-only.rst:82 msgid "" "Finally, the last external service you may need is a NameServer. This is " "used to translate addresses (the 40-characters fingerprint ID) to usernames." " You may not have access to **ns.jami.net**, but you can self-host one " "(:doc:`/developer/name-server-protocol`) or only use IDs." msgstr ""