yetangitu/deltachat
1
0
Fork 0
mirror of https://github.com/deltachat/deltachat-android.git synced 2025-10-06 03:49:58 +02:00
Code Issues Releases Wiki Activity

Merge branch 'main' into adb/issue-3795

Browse source
This commit is contained in:
adb 2025-08-06 14:47:41 +02:00 • committed by GitHub
commit 2ef3811a56
No known key found for this signature in database
GPG key ID: B5690EEEBB952194
100 changed files with 3174 additions and 4265 deletions
Download patch file Download diff file Expand all files Collapse all files

28
CHANGELOG.md
View file

@ -1,6 +1,26 @@
# Delta Chat Android Changelog # Delta Chat Android Changelog
## Unreleased ## v2.10.0
2025-08
* fix "Archived" item's layout in chat-list
* don't enlarge "Saved Messages" and "Devices Messages" avatars on click
* share email address for email contacts instead of vCard
* open existing encrypted chat when opening a mailto link or clicking an email address in a message bubble
* update to core 2.10.0
## v2.9.0
2025-07
* hide contact email addresses in search results
* disable non-functional message editing and ephemeral messages timer settings in classic email thread chat
* don't enlarge email chats avatar placeholder
* improve message date/status footer layout, also in RTL languages
* display correct text when receiving a "Disappearing messages enabled" system message
* Update to core 2.9.0
## v2.8.0
2025-07
* Profiles focus on recognizing contacts * Profiles focus on recognizing contacts
* See the number of media directly in the profile, no need to tap around * See the number of media directly in the profile, no need to tap around
@ -12,12 +32,14 @@
* New icon for the QR icon * New icon for the QR icon
* Start rebuilding the experimental broadcast lists * Start rebuilding the experimental broadcast lists
into proper channels - note that this is work-in-progress into proper channels - note that this is work-in-progress
* Improved separation between unencryted chats/contacts and encrypted ones, avoiding mixing of encrypted and unencrypted messages in the same chat * Improved separation between unencrypted chats/contacts and encrypted ones, avoiding mixing of encrypted and unencrypted messages in the same chat
* Removed padlocks, as encrypted is the default "normal" state. Instead, unencrypted email is marked with a small email / letter (✉️) icon * Removed padlocks, as encrypted is the default "normal" state. Instead, unencrypted email is marked with a small email / letter (✉️) icon
* Classic email chats/threads get a big email / letter icon making it easy to recognize * Classic email chats/threads get a big email / letter icon making it easy to recognize
* After some time, add a device message asking to donate. Can't wait? Donate today at https://delta.chat/donate * After some time, add a device message asking to donate. Can't wait? Donate today at https://delta.chat/donate
* Allow to sort profiles up in the profile switcher * Allow to sort profiles up in the profile switcher
* Update to core 2.1.0 * Add new option to create unencrypted email thread
* Green checkmarks are removed where they mostly refer to guaranteed encryption, which is the default now. They are still used for profile's "Introduced by"
* Update to core 2.8.0
## v1.58.4 ## v1.58.4
2025-05 2025-05

4
build.gradle
View file

@ -27,8 +27,8 @@ android {
useLibrary 'org.apache.http.legacy' useLibrary 'org.apache.http.legacy'
defaultConfig { defaultConfig {
versionCode 723 versionCode 729
versionName "1.59.0" versionName "2.10.0"
applicationId "com.b44t.messenger" applicationId "com.b44t.messenger"
multiDexEnabled true multiDexEnabled true

BIN
fastlane/metadata/android/en-US/images/phoneScreenshots/1.png
View file

Binary file not shown.
Side by side Swipe Overlay

Before

Width:  |  Height:  |  Size: 292 KiB

After

Width:  |  Height:  |  Size: 277 KiB

Before After
Before After

BIN
fastlane/metadata/android/en-US/images/phoneScreenshots/2.png
View file

Binary file not shown.
Side by side Swipe Overlay

Before

Width:  |  Height:  |  Size: 818 KiB

After

Width:  |  Height:  |  Size: 805 KiB

Before After
Before After

BIN
fastlane/metadata/android/en-US/images/phoneScreenshots/5.png
View file

Binary file not shown.
Side by side Swipe Overlay

Before

Width:  |  Height:  |  Size: 287 KiB

After

Width:  |  Height:  |  Size: 271 KiB

Before After
Before After

BIN
fastlane/metadata/android/en-US/images/phoneScreenshots/8.png
View file

Binary file not shown.
Side by side Swipe Overlay

Before

Width:  |  Height:  |  Size: 556 KiB

After

Width:  |  Height:  |  Size: 548 KiB

Before After
Before After

5
jni/dc_wrapper.c
View file

@ -1272,11 +1272,6 @@ JNIEXPORT jboolean Java_com_b44t_messenger_DcChat_isProtected(JNIEnv *env, jobje
return dc_chat_is_protected(get_dc_chat(env, obj))!=0; return dc_chat_is_protected(get_dc_chat(env, obj))!=0;
} }
JNIEXPORT jboolean Java_com_b44t_messenger_DcChat_isProtectionBroken(JNIEnv *env, jobject obj)
{
return dc_chat_is_protection_broken(get_dc_chat(env, obj))!=0;
}
JNIEXPORT jboolean Java_com_b44t_messenger_DcChat_isSendingLocations(JNIEnv *env, jobject obj) JNIEXPORT jboolean Java_com_b44t_messenger_DcChat_isSendingLocations(JNIEnv *env, jobject obj)
{ {

2
jni/deltachat-core-rust

@ -1 +1 @@
Subproject commit 402e42f858514e5c1fbab3c88ad3d5f884009b8b Subproject commit 08bb0484eb6a91a4145e48e33bd1b3717cd0ff8f

420
src/main/assets/help/cs/help.html
View file

@ -36,27 +36,24 @@
<li><a href="#why-does-delta-chat-integrate-with-centralized-proprietary-applegoogle-push-services">Why does Delta Chat integrate with centralized proprietary Apple/Google push services?</a></li> <li><a href="#why-does-delta-chat-integrate-with-centralized-proprietary-applegoogle-push-services">Why does Delta Chat integrate with centralized proprietary Apple/Google push services?</a></li>
</ul> </ul>
</li> </li>
<li><a href="#encryption-and-security">Encryption and Security</a> <li><a href="#e2ee">Encryption and Security</a>
<ul> <ul>
<li><a href="#which-standards-are-used-for-end-to-end-encryption">Which standards are used for end-to-end encryption?</a></li> <li><a href="#which-standards-are-used-for-end-to-end-encryption">Which standards are used for end-to-end encryption?</a></li>
<li><a href="#whene2e">How can i know if messages are end-to-end encrypted?</a></li> <li><a href="#whene2e">How can i know if messages are end-to-end encrypted?</a></li>
<li><a href="#howtoe2ee">How can I get guaranteed end-to-end encryption and green checkmarks?</a></li> <li><a href="#can-i-still-receive-or-send-mails-without-end-to-end-encryption">Can i still receive or send mails without end-to-end encryption?</a></li>
<li><a href="#e2eeguarantee">What does the green checkmark and “guaranteed end-to-end encryption” mean?</a></li> <li><a href="#howtoe2ee">How can I establish a chat with a new contact?</a></li>
<li><a href="#nocryptanymore">A contact “sent a message from another device”, what can i do?</a></li> <li><a href="#e2eeguarantee">What does the green checkmark in a contact profile mean?</a></li>
<li><a href="#are-attachments-pictures-files-audio-etc-end-to-end-encrypted">Are attachments (pictures, files, audio etc.) end-to-end encrypted?</a></li> <li><a href="#are-attachments-pictures-files-audio-etc-end-to-end-encrypted">Are attachments (pictures, files, audio etc.) end-to-end encrypted?</a></li>
<li><a href="#openpgp-secure">Is OpenPGP secure?</a></li> <li><a href="#openpgp-secure">Is OpenPGP secure?</a></li>
<li><a href="#openpgp-alternatives">Did you consider using alternatives to OpenPGP for end-to-end -encryption?</a></li> <li><a href="#openpgp-alternatives">Did you consider using alternatives to OpenPGP for end-to-end-encryption?</a></li>
<li><a href="#is-delta-chat-vulnerable-to-efail">Is Delta Chat vulnerable to EFAIL?</a></li> <li><a href="#is-delta-chat-vulnerable-to-efail">Is Delta Chat vulnerable to EFAIL?</a></li>
<li><a href="#tls">Is a message exposed in cleartext if end-to-end encryption is not available?</a></li> <li><a href="#tls">Are messages marked with the mail icon exposed on the Internet?</a></li>
<li><a href="#message-metadata">How does Delta Chat protect metadata in messages?</a></li> <li><a href="#message-metadata">How does Delta Chat protect metadata in messages?</a></li>
<li><a href="#device-seizure">How to protect metadata and contacts when a device is seized?</a></li> <li><a href="#device-seizure">How to protect metadata and contacts when a device is seized?</a></li>
<li><a href="#how-can-i-check-encryption-information">How can i check encryption information?</a></li> <li><a href="#sealedsender">Does Delta Chat support “Sealed Sender”?</a></li>
<li><a href="#how-can-i-check-the-encryption-status-of-messages">How can I check the encryption status of messages?</a></li>
<li><a href="#why-do-i-see-unencrypted-messages">Why do I see unencrypted messages?</a></li>
<li><a href="#how-can-i-get-an-end-to-end-encrypted-chat-with-a-delta-chat-contact-who-sometimes-uses-webmail-or-another-non-autocrypt-e-mail-app">How can i get an end-to-end encrypted chat with a Delta Chat contact who sometimes uses webmail or another non-Autocrypt e-mail app?</a></li>
<li><a href="#how-can-i-ensure-message-end-to-end-encryption-and-deletion">How can I ensure message end-to-end encryption and deletion?</a></li>
<li><a href="#pfs">Does Delta Chat support Perfect Forward Secrecy?</a></li> <li><a href="#pfs">Does Delta Chat support Perfect Forward Secrecy?</a></li>
<li><a href="#is-end-to-end-encryption-of-delta-chat-as-safe-as-signal">Is end-to-end encryption of Delta Chat as safe as Signal?</a></li> <li><a href="#pqc">Does Delta Chat support Post-Quantum-Cryptography?</a></li>
<li><a href="#how-can-i-manually-check-encryption-information">How can I manually check encryption information?</a></li>
<li><a href="#importkey">Lze znovu použít můj stávající soukromý klíč?</a></li> <li><a href="#importkey">Lze znovu použít můj stávající soukromý klíč?</a></li>
<li><a href="#security-audits">Was Delta Chat independently audited for security vulnerabilities?</a></li> <li><a href="#security-audits">Was Delta Chat independently audited for security vulnerabilities?</a></li>
</ul> </ul>
@ -722,10 +719,10 @@ that achieves “instant delivery” of messages for all chatmail servers
including a potential one <a href="https://delta.chat/chatmail#selfhosted">you might setup yourself without our permission</a>. including a potential one <a href="https://delta.chat/chatmail#selfhosted">you might setup yourself without our permission</a>.
Welcome to the power of the interoperable and massive chatmail and e-mail system :)</p> Welcome to the power of the interoperable and massive chatmail and e-mail system :)</p>
<h2 id="encryption-and-security"> <h2 id="e2ee">
Encryption and Security <a href="#encryption-and-security" class="anchor"></a> Encryption and Security <a href="#e2ee" class="anchor"></a>
</h2> </h2>
@ -738,18 +735,26 @@ Welcome to the power of the interoperable and massive chatmail and e-mail system
</h3> </h3>
<p><a href="https://autocrypt.org">Autocrypt</a> is used for automatically <p>Delta Chat uses a <a href="#openpgp-secure">secure subset of the OpenPGP standard</a>
establishing end-to-end encryption with contacts and group chats. to provide automatic end-to-end encryption using these protocols:</p>
Autocrypt uses a limited and <a href="#openpgp-secure">secure subset of the OpenPGP standard</a>.
End-to-End encrypted messages are marked with a padlock
<img style="vertical-align:middle; width:1.2em; margin:1px" src="../lock-icon.png" alt="padlock" />.</p>
<p><a href="https://securejoin.delta.chat/en/latest/new.html">Secure-Join protocols</a> <ul>
are used for establishing chats with guaranteed end-to-end encryption <li>
which protects against network attacks and compromised servers. <p><a href="https://securejoin.delta.chat/en/latest/new.html">Secure-Join</a>
Chats marked with a green checkmark to exchange encryption setup information through QR-code scanning or “invite links”.</p>
<img style="vertical-align:middle; width:1.5em; margin:1px" src="../green-checkmark.png" alt="green checkmark" /> </li>
guarantee end-to-end encrypted messages.</p> <li>
<p><a href="https://autocrypt.org">Autocrypt</a> is used for automatically
establishing end-to-end encryption between contacts and all members of a group chat.</p>
</li>
<li>
<p><a href="https://github.com/chatmail/core/blob/main/spec.md#attaching-a-contact-to-a-message">Sharing a contact to a
chat</a>
enables receivers to use end-to-end encryption with the contact.</p>
</li>
</ul>
<p>Delta Chat does not query, publish or interact with any OpenPGP key servers.</p>
<h3 id="whene2e"> <h3 id="whene2e">
@ -759,28 +764,37 @@ guarantee end-to-end encrypted messages.</p>
</h3> </h3>
<p>All end-to-end encrypted messages carry a padlock:</p> <p>All messages in Delta Chat are <strong>end-to-end encrypted by default</strong>.
Since the Delta Chat Version 2 release series (July 2025)
there are no lock or similar markers on end-to-end encrypted messages, anymore.</p>
<p><img style="width:160px; margin:1px" src="../lock-screenshot.png" alt="padlock in bubble" /></p> <h3 id="can-i-still-receive-or-send-mails-without-end-to-end-encryption">
<p>End-to-end encryption is guaranteed if there is a green checkmark next to the chat title:</p>
<p><img style="width:211px; margin:1px" src="../green-checkmark-screenshot.png" alt="green checkmark in title" /></p>
<h3 id="howtoe2ee">
How can I get guaranteed end-to-end encryption and green checkmarks? <a href="#howtoe2ee" class="anchor"></a> Can i still receive or send mails without end-to-end encryption? <a href="#can-i-still-receive-or-send-mails-without-end-to-end-encryption" class="anchor"></a>
</h3> </h3>
<p>If you have a second communication channel with your chat partner, <p>If you use default <a href="https://chatmail.at/relays">chatmail relays</a>,
like a video chat or a different messenger, it is impossible to receive or send messages without end-to-end encryption.</p>
you can generate an invite link.</p>
<p>If you are together in person, <p>If you instead create a profile using a classic e-mail server,
you can show a QR code to your chat partner.</p> you can send and receive messages without end-to-end encryption.
Such messages lacking end-to-end encryption are marked with an e-mail icon
<img style="vertical-align:middle; width:1.2em; margin:1px" src="../email-icon.png" alt="email" />.</p>
<h3 id="howtoe2ee">
How can I establish a chat with a new contact? <a href="#howtoe2ee" class="anchor"></a>
</h3>
<p>You can send an invite link through another private chat,
show an invitation QR code when next to each other or in a video call,
or click on a “contact” that was shared in a chat.</p>
<ul> <ul>
<li> <li>
@ -795,135 +809,54 @@ on the Delta Chat app main screen.</p>
</li> </li>
</ul> </ul>
<p>Let your chat partner scan the QR image <p>Ask your chat partner to scan the QR image
with their Delta Chat app, with their Delta Chat app,
or click “Copy” or “Share” to create an invite link or click “Copy” or “Share” to create an invite link
and share it with your chat partner.</p> and share it with your chat partner.</p>
<p>Now wait while <a href="https://securejoin.delta.chat/en/latest/new.html#setup-contact-protocol">Secure-Join network messages are exchanged</a> between both devices.</p> <p>Now wait while <a href="https://securejoin.delta.chat/en/latest/new.html#setup-contact-protocol">end-to-end encryption is getting established</a>.</p>
<ul> <ul>
<li> <li>
<p>If both devices are online, <p>If both sides are online, they will soon see a (group or direct) chat
both sides will eventually see a (group or direct) chat with a green checkmark and can start messaging securely.</p>
<img style="vertical-align:middle; width:1.5em; margin:1px" src="../green-checkmark.png" alt="green checkmark" />
next to the title.</p>
</li> </li>
<li> <li>
<p>If one of the devices is offline, the green checkmarks will only <p>If one side is offline or in bad network,
appear later when the device is internet-connected again the ability to chat is delayed until connectivity is restored.</p>
and the Secure-Join network protocol completed.</p>
</li> </li>
</ul> </ul>
<p>Congratulations! <p>Congratulations!
You now will automatically use guaranteed end-to-end encryption You now will automatically use end-to-end encryption
with this contact and both of you can add each other to green-checkmarked groups with this contact.
<img style="vertical-align:middle; width:1.5em; margin:1px" src="../green-checkmark.png" alt="green checkmark" />, If you add each other to chat groups,
thereby automatically spreading guaranteed end-to-end encryption among its members.</p> end-to-end encryption will be established among all members.</p>
<h3 id="e2eeguarantee"> <h3 id="e2eeguarantee">
What does the green checkmark and “guaranteed end-to-end encryption” mean? <a href="#e2eeguarantee" class="anchor"></a> What does the green checkmark in a contact profile mean? <a href="#e2eeguarantee" class="anchor"></a>
</h3> </h3>
<p>Chat titles with green checkmarks <p>A contact profile might show a green checkmark
<img style="vertical-align:middle; width:1.5em; margin:1px" src="../green-checkmark.png" alt="green checkmark" /> <img style="vertical-align:middle; width:1.5em; margin:1px" src="../green-checkmark.png" alt="green checkmark" />
mean that all messages in the chat will be end-to-end encrypted and an “Introduced by” line.
and can not be read or altered by compromised e-mail servers or Internet providers.
Joining green-checkmarked group chats
safely spreads everybody’s encryption information (and green checkmarks)
in a manner that guarantees end-to-end encryption in the group and among members.</p>
<p>Contact profiles with green checkmarks
<img style="vertical-align:middle; width:1.5em; margin:1px" src="../green-checkmark.png" alt="green checkmark" />
mean that messaging a contact is currently guaranteed to be end-to-end encrypted.
Every green-checkmarked contact either did a direct <a href="#howtoe2ee">QR-scan</a> with you Every green-checkmarked contact either did a direct <a href="#howtoe2ee">QR-scan</a> with you
or was introduced by a another green-checkmarked contact. or was introduced by a another green-checkmarked contact.
Introductions happen automatically when adding members to groups. Introductions happen automatically when adding members to groups.
Whoever adds a contact to a green-checkmarked group becomes an introducer Whoever adds a green-checkmarked contact to a group with only green-checkmarked members
to those members who didn’t yet know about the added contact. becomes an introducer.
In a contact profile you can tap on the “Introduced by …” text repeatedly In a contact profile you can tap on the “Introduced by …” text repeatedly
until you get to the one with whom you directly did a <a href="#howtoe2ee">QR-scan</a>.</p> until you get to the one with whom you directly did a <a href="#howtoe2ee">QR-scan</a>.</p>
<p>Note that in a contact profile you may see and tap introducers
but there is no green checkmark in the profile title.
This usually means that the contact <a href="#nocryptanymore">“sent a message from another device”</a>.</p>
<p>For more in-depth discussion of “guaranteed end-to-end encryption” <p>For more in-depth discussion of “guaranteed end-to-end encryption”
please see <a href="https://securejoin.delta.chat/en/latest/new.html">Secure-Join protocols</a> please see <a href="https://securejoin.delta.chat/en/latest/new.html">Secure-Join protocols</a>
and specifically read about “Verified Groups”, the technical term and specifically read about “Verified Groups”, the technical term
of what is called here “green-checkmarked” or “guaranteed end-to-end encrypted” chats.</p> of what is called here “green-checkmarked” or “guaranteed end-to-end encrypted” chats.</p>
<h3 id="nocryptanymore">
A contact “sent a message from another device”, what can i do? <a href="#nocryptanymore" class="anchor"></a>
</h3>
<p>Your chat with a contact lost guaranteed end-to-end encryption.
The green checkmark was removed for this chat and contact when you see this warning.
<strong>If you find the sudden drop of guaranteed end-to-end encryption
surprising for this contact then don’t accept the warning!</strong>
Instead check with your contact through a second channel
like a video call, other messenger or a phone call,
to find out what happened.</p>
<p>If your contact actually caused the drop of guaranteed end-to-end encryption
please see the next paragraphs for common reasons and their mitigations.
Regardless, all other green-checkmarked chats remain guaranteed end-to-end encrypted
even if the contact is a member there.</p>
<p><strong>Your contact is using Delta Chat on a second device (phone or laptop)</strong></p>
<p>If they have another device with a Delta Chat app running,
they should remove the profile from the new device
and add it <a href="#multiclient">as a second device as described here</a>.
As soon as they message you afterwards, the warning will be gone
and guaranteed encryption is established with both devices of your contact.</p>
<p><strong>Your contact reinstalled Delta Chat using their old account login</strong></p>
<p>If they have <a href="#backup">a backup file</a>,
they should remove the profile from the new device
and rather import the backup file to re-create their profile.
As soon as they message you afterwards, the warning will be gone
and guaranteed encryption is re-established for this contact.</p>
<p>If they don’t have a backup file, it’s best to perform a <a href="#howtoe2ee">QR scan</a>
with your chat partner to re-establish guaranteed end-to-end encryption.</p>
<p><strong>Your contact sent a mail through a webmail interface or another e-mail app
and will get back to using Delta Chat soon again.</strong></p>
<p>If you are sure that the contact sometimes uses webmail,
or another mail app lacking end-to-end encryption,
then you may accept the warning.
As soon as your contact uses Delta Chat again,
guaranteed end-to-end encryption will be automatically re-established.</p>
<p><strong>Your contact stopped using Delta Chat entirely</strong></p>
<p>Sometimes remaining in contact is more important than end-to-end encryption.
<a href="#tls">“Transport Layer Encryption” (TLS)</a> may still meaningfully protect
the confidentiality of your messages between your device and the e-mail server.
But without end-to-end encryption you and your contact are trusting your e-mail server
to not read or manipulate your messages, and to not hand them to third parties.</p>
<p>In any case, you can not do much else than accept the warning.
Please also remove the contact from any active green-checkmarked group
which you can find in “Chats in Common” in the Contact profile.
This spares your contact from getting “unreadable” messages.</p>
<p>If the contact removed Delta Chat because of buggy or undesirable behaviour,
please consider posting to our <a href="https://support.delta.chat">support forum</a>
to help us identify and address common problems. Thanks!</p>
<h3 id="are-attachments-pictures-files-audio-etc-end-to-end-encrypted"> <h3 id="are-attachments-pictures-files-audio-etc-end-to-end-encrypted">
@ -948,8 +881,7 @@ and attachment metadata such as filenames.</p>
</h3> </h3>
<p>Yes, Delta Chat uses a secure subset of OpenPGP <p>Yes, Delta Chat uses a secure subset of OpenPGP
and only displays a padlock security indicator on a message requiring the whole message to be properly encrypted and signed.
if the whole message is properly encrypted and signed.
For example, “Detached signatures” are not treated as secure.</p> For example, “Detached signatures” are not treated as secure.</p>
<p>OpenPGP is not insecure by itself. <p>OpenPGP is not insecure by itself.
@ -970,7 +902,7 @@ which was thankfully adopted in summer 2023.</p>
<h3 id="openpgp-alternatives"> <h3 id="openpgp-alternatives">
Did you consider using alternatives to OpenPGP for end-to-end -encryption? <a href="#openpgp-alternatives" class="anchor"></a> Did you consider using alternatives to OpenPGP for end-to-end-encryption? <a href="#openpgp-alternatives" class="anchor"></a>
</h3> </h3>
@ -1013,17 +945,15 @@ as defined by the Autocrypt Level 1 specification.</p>
<h3 id="tls"> <h3 id="tls">
Is a message exposed in cleartext if end-to-end encryption is not available? <a href="#tls" class="anchor"></a> Are messages marked with the mail icon exposed on the Internet? <a href="#tls" class="anchor"></a>
</h3> </h3>
<p>Even if your messages are not guaranteed to be end-to-end encrypted, <p>If you are sending or receiving e-mail messages without end-to-end encryption (using a classic e-mail server),
they are still protected from Internet providers like cell or cable companies. they are still protected from cell or cable companies who can not read or modify your e-mail messages.
However, your and your recipient’s e-mail providers But both your and your recipient’s e-mail providers
may read, analyze or even modify your messages, may read, analyze or modify your messages, including any attachments.</p>
including any attachments,
if they are not end-to-end encrypted.</p>
<p>Delta Chat by default uses strict <p>Delta Chat by default uses strict
<a href="https://en.wikipedia.org/wiki/Transport_Layer_Security">TLS encryption</a> <a href="https://en.wikipedia.org/wiki/Transport_Layer_Security">TLS encryption</a>
@ -1036,10 +966,6 @@ then transport encryption will be enforced between e-mail providers
in which case Delta Chat communications will never be exposed in cleartext to the Internet in which case Delta Chat communications will never be exposed in cleartext to the Internet
even if the message was not end-to-end encrypted.</p> even if the message was not end-to-end encrypted.</p>
<p>Note that <a href="#howtoe2ee">maintaining guaranteed end-to-end encryption</a> on top of TLS encryption
provides pervasive safety between your and the recipient’s devices.
Not even your e-mail or Internet provider will be able to read or modify your messages.</p>
<h3 id="message-metadata"> <h3 id="message-metadata">
@ -1048,25 +974,25 @@ Not even your e-mail or Internet provider will be able to read or modify your me
</h3> </h3>
<p>Delta Chat protects most message metadata by putting the following information <p>Unlike most other messengers,
into the end-to-end encrypted part of messages:</p> Delta Chat apps do not store any metadata about contacts or groups on servers, also not in encrypted form.
Instead, all group metadata is end-to-end encrypted and stored on end-user devices, only.</p>
<p>E-mail Servers can therefore only see</p>
<ul> <ul>
<li>Subject line</li> <li>
<li>Group avatar and name</li> <p>the message date,</p>
<li>MDN (read receipt) requests (<code class="language-plaintext highlighter-rouge">Chat-Disposition-Notification-To</code>)</li> </li>
<li>Disappearing message timer (<code class="language-plaintext highlighter-rouge">Ephemeral-Timer</code>)</li> <li>
<li><code class="language-plaintext highlighter-rouge">Chat-Group-Member-Removed</code>, <code class="language-plaintext highlighter-rouge">Chat-Group-Member-Added</code></li> <p>sender and receiver addresses</p>
<li><code class="language-plaintext highlighter-rouge">Secure-Join</code> header containing secure join commands</li> </li>
<li>Notification about enabling location streaming</li> <li>
<li>WebRTC room URL</li> <p>and message size.</p>
</li>
</ul> </ul>
<p>E-Mail servers do not get access to this protected metadata <p>All other message, contact and group metadata resides in the end-to-end encrypted part of messages.</p>
but they do see the message date as well as the message size,
and, more importantly, the sender and receiver addresses.
E-mail servers need receiver addresses to route and
deliver messages to recipient’s devices.</p>
<h3 id="device-seizure"> <h3 id="device-seizure">
@ -1078,96 +1004,34 @@ deliver messages to recipient’s devices.</p>
<p>Both for protecting against metadata-collecting e-mail servers <p>Both for protecting against metadata-collecting e-mail servers
as well as against the threat of device seizure as well as against the threat of device seizure
we recommend to use a <a href="https://delta.chat/chatmail">chatmail server</a> we recommend to use a <a href="https://chatmail.at/relays">chatmail relay</a>
to create pseudonymous temporary profiles through QR-code scans. to create chat profiles using random e-mail addresses for transport.
Note that Delta Chat apps on all platforms support multiple profiles Note that Delta Chat apps on all platforms support multiple profiles
so you can easily use situation-specific profiles next to your “main” profile so you can easily use situation-specific profiles next to your “main” profile
with the knowledge that all their data, along with all metadata, will be deleted. with the knowledge that all their data, along with all metadata, will be deleted.
Moreover, if a device is seized then contacts using temporary profiles Moreover, if a device is seized then chat contacts using short-lived profiles
can not be identified easily, as compared to messengers which reveal can not be identified easily.</p>
phone numbers in chat groups which in turn are often associated with legal identities.</p>
<h3 id="how-can-i-check-encryption-information"> <h3 id="sealedsender">
How can i check encryption information? <a href="#how-can-i-check-encryption-information" class="anchor"></a> Does Delta Chat support “Sealed Sender”? <a href="#sealedsender" class="anchor"></a>
</h3> </h3>
<p>You may check the end-to-end encryption status manually in the “Encryption” dialog <p>No, not yet.</p>
(user profile on Android/iOS or right-click a user’s chat-list item on desktop).
Delta Chat shows two fingerprints there.
If the same fingerprints appear on your own and your contact’s device,
the connection is safe.</p>
<h3 id="how-can-i-check-the-encryption-status-of-messages"> <p>The Signal messenger introduced <a href="https://signal.org/blog/sealed-sender/">“Sealed Sender” in 2018</a>
to keep their server infrastructure ignorant of who is sending a message to a set of recipients.
It is particularly important because the Signal server knows the mobile number of each account,
which is usually associated with a passport identity.</p>
<p>Even if <a href="https://chatmail.at/relays">chatmail relays</a>
How can I check the encryption status of messages? <a href="#how-can-i-check-the-encryption-status-of-messages" class="anchor"></a> do not ask for any private data (including no phone numbers),
it might still be worthwhile to protect relational metadata between addresses.
We don’t foresee bigger problems in using random throw-away e-mail addresses for sealed sending
</h3> but an implementation has not been agreed as a priority yet.</p>
<p>A little <strong>padlock</strong> in a message bubble denotes
that the message was properly end-to-end encrypted from the given sender.
If there is <strong>no padlock</strong>, the message was not properly end-to-end encrypted
most likely because the sender uses an app or webmail interface
without support for end-to-end–encryption.</p>
<h3 id="why-do-i-see-unencrypted-messages">
Why do I see unencrypted messages? <a href="#why-do-i-see-unencrypted-messages" class="anchor"></a>
</h3>
<p>If a contact uses a non-Autocrypt e-mail app,
all messages involving this contact (in a group or 1:1 chat)
will not be end-to-end encrypted, and thus not show a “padlock” with messages.
Note that even if your contacts use Delta Chat on their account,
they might also use a non-Autocrypt e-mail app on that account
which then may cause intermittently unencrypted messages.
Replying unencrypted to unencrypted messages is mandated by Autocrypt
to prevent unreadable messages on the side of your contacts
and their non-Autocrypt e-mail app.</p>
<h3 id="how-can-i-get-an-end-to-end-encrypted-chat-with-a-delta-chat-contact-who-sometimes-uses-webmail-or-another-non-autocrypt-e-mail-app">
How can i get an end-to-end encrypted chat with a Delta Chat contact who sometimes uses webmail or another non-Autocrypt e-mail app? <a href="#how-can-i-get-an-end-to-end-encrypted-chat-with-a-delta-chat-contact-who-sometimes-uses-webmail-or-another-non-autocrypt-e-mail-app" class="anchor"></a>
</h3>
<p>If you need a safely end-to-end encrypted chat with a contact
who is using their e-mail account both with Delta Chat and non-Autocrypt apps (e.g. webmail),
it’s best to setup <a href="#howtoe2ee">guaranteed end-to-end encryption with them</a>
and then create a guaranteed end-to-end encrypted group chat with you two as members.
In this group chat all messages will be end-to-end encrypted
even if the direct chat between you two has a
<a href="#nocryptanymore">“… sent a message from another device”</a> warning.</p>
<h3 id="how-can-i-ensure-message-end-to-end-encryption-and-deletion">
How can I ensure message end-to-end encryption and deletion? <a href="#how-can-i-ensure-message-end-to-end-encryption-and-deletion" class="anchor"></a>
</h3>
<p>The best way to ensure every message is end-to-end encrypted,
and metadata deleted as quickly as possible
is <a href="#howtoe2ee">using chats with guaranteed end-to-end encryption</a>
and turning on <a href="#ephemeralmsgs">disappearing messages</a>.</p>
<p>Guaranteed end-to-end encrypted chats protect against <a href="https://en.wikipedia.org/wiki/Man-in-the-middle_attack">MITM attacks</a>
and turning on disappearing messages deletes the messages
on the server after a user-configured time.</p>
<p>If you don’t need a longer-lived copy of your messages on the server,
you can also turn on <a href="#delold">“delete messages from server automatically”</a>.</p>
<h3 id="pfs"> <h3 id="pfs">
@ -1177,45 +1041,52 @@ you can also turn on <a href="#delold">“delete messages from server automatica
</h3> </h3>
<p>No, Delta Chat doesn’t support Perfect Forward Secrecy (PFS). <p>No, not yet.</p>
This means that if your Delta Chat private decryption key is leaked,
<p>Delta Chat today doesn’t support Perfect Forward Secrecy (PFS).
This means that if your private decryption key is leaked,
and someone has collected your prior in-transit messages, and someone has collected your prior in-transit messages,
they will be able to decrypt and read them using the leaked decryption key.</p> they will be able to decrypt and read them using the leaked decryption key.
Note that Forward Secrecy only increases security if you delete messages.
Otherwise, someone obtaining your decryption keys
is typically also able to get all your non-deleted messages
and doesn’t even need to decrypt any previously collected messages.</p>
<p>Note, however, that if anyone obtains to your decryption keys, <p>We designed a Forward Secrecy approach that withstood
they will typically also be able to obtain your messages, initial examination from some cryptographers and implementation experts
irrespective if Perfect Forward Secrecy is in place or not. but is pending a more formal write up
The typical real-world situation for leaked decryption keys is device seizure to ascertain it reliably works in federated messaging and with multi-device usage,
which we discuss in our answer <a href="#device-seizure">on metadata and device seizure</a>.</p> before it could be implemented in <a href="https://github.com/chatmail/core">chatmail core</a>,
which would make it available in all <a href="https://chatmail.at/clients">chatmail clients</a>.</p>
<p>It is possible that Delta Chat evolves to support Perfect Forward Secrecy, <h3 id="pqc">
because OpenPGP is just a container for encrypted messages
but encryption key management (and thus key rotation or key “ratcheting”)
could be organized in flexible ways.
See <a href="https://gitlab.com/sequoia-pgp/openpgp-dr">Seqouia’s PFS prototype</a>
for existing experiments in the OpenPGP implementor community.</p>
<h3 id="is-end-to-end-encryption-of-delta-chat-as-safe-as-signal">
Is end-to-end encryption of Delta Chat as safe as Signal? <a href="#is-end-to-end-encryption-of-delta-chat-as-safe-as-signal" class="anchor"></a> Does Delta Chat support Post-Quantum-Cryptography? <a href="#pqc" class="anchor"></a>
</h3> </h3>
<p>It depends on what is important to you. <p>No, not yet.</p>
Delta Chat <a href="#pfs">does not support PFS</a> like Signal does
but it provides <a href="#e2eeguarantee">guaranteed end-to-end encrypted chats</a>
that are safe against compromised servers or corrupted networks.
Signal and most other PFS-supporting messengers do not provide
a practical scheme for protecting chat groups from network attacks
which are arguably more worrisome
than a potential attacker who seizes your phone and private encryption setup
but somehow not your messages, yet has a full record of all
past encrypted messages.</p>
<p>In any case, Delta Chat’s end-to-end encryption uses a <a href="#openpgp-secure">secure subset of OpenPGP</a> <p>Delta Chat uses the Rust OpenPGP library <a href="https://github.com/rpgp/rpgp">rPGP</a>
which has been <a href="https://delta.chat/assets/blog/2019-first-security-review.pdf">independently security-audited</a>.</p> which supports the latest <a href="https://datatracker.ietf.org/doc/draft-ietf-openpgp-pqc/">IETF Post-Quantum-Cryptography OpenPGP draft</a>.
We aim to add PQC support in <a href="https://github.com/chatmail/core">chatmail core</a> after the draft is finalized at the IETF
in collaboration with other OpenPGP implementers.</p>
<h3 id="how-can-i-manually-check-encryption-information">
How can I manually check encryption information? <a href="#how-can-i-manually-check-encryption-information" class="anchor"></a>
</h3>
<p>You may check the end-to-end encryption status manually in the “Encryption” dialog
(user profile on Android/iOS or right-click a user’s chat-list item on desktop).
Delta Chat shows two fingerprints there.
If the same fingerprints appear on your own and your contact’s device,
the connection is safe.</p>
<h3 id="importkey"> <h3 id="importkey">
@ -1250,7 +1121,7 @@ from most recent to older:</p>
<li> <li>
<p>2024 December, an <a href="https://github.com/rpgp/docs/blob/main/audits/NGI%20Core%20rPGP%20penetration%20test%20report%202024%201.0.pdf">NLNET-commissioned Evaluation of <p>2024 December, an <a href="https://github.com/rpgp/docs/blob/main/audits/NGI%20Core%20rPGP%20penetration%20test%20report%202024%201.0.pdf">NLNET-commissioned Evaluation of
rPGP</a> by <a href="https://www.radicallyopensecurity.com/">Radically Open Security</a> took place. rPGP</a> by <a href="https://www.radicallyopensecurity.com/">Radically Open Security</a> took place.
rPGP serves as the end-to-end encyption <a href="https://openpgp.org">OpenPGP</a> engine of Delta Chat. rPGP serves as the end-to-end encryption <a href="https://openpgp.org">OpenPGP</a> engine of Delta Chat.
Two advisories were released related to the findings of this audit:</p> Two advisories were released related to the findings of this audit:</p>
<ul> <ul>
@ -1643,6 +1514,11 @@ DeltaChat. To je něco co za běžných okolností dělá Delta Chat sám.</p>
</h3> </h3>
<p>Note:
Changing email addresses is temporarily disabled
because of ongoing changes to the DeltaChat core.
It should be available again in a few months.</p>
<ol> <ol>
<li> <li>
<p>Change your address in “Settings → Advanced → Password and Account” and <p>Change your address in “Settings → Advanced → Password and Account” and

438
src/main/assets/help/de/help.html
View file

@ -36,27 +36,24 @@
<li><a href="#warum-integriert-sich-delta-chat-in-zentralisierte-proprietäre-applegoogle-push-dienste">Warum integriert sich Delta Chat in zentralisierte, proprietäre Apple/Google-Push-Dienste?</a></li> <li><a href="#warum-integriert-sich-delta-chat-in-zentralisierte-proprietäre-applegoogle-push-dienste">Warum integriert sich Delta Chat in zentralisierte, proprietäre Apple/Google-Push-Dienste?</a></li>
</ul> </ul>
</li> </li>
<li><a href="#verschlüsselung-und-sicherheit">Verschlüsselung und Sicherheit</a> <li><a href="#e2ee">Verschlüsselung und Sicherheit</a>
<ul> <ul>
<li><a href="#welche-standards-werden-für-die-ende-zu-ende-verschlüsselung-verwendet">Welche Standards werden für die Ende-zu-Ende-Verschlüsselung verwendet?</a></li> <li><a href="#welche-standards-werden-für-die-ende-zu-ende-verschlüsselung-verwendet">Welche Standards werden für die Ende-zu-Ende-Verschlüsselung verwendet?</a></li>
<li><a href="#whene2e">Wie kann ich wissen, ob Nachrichten Ende-zu-Ende-verschlüsselt sind?</a></li> <li><a href="#whene2e">Wie kann ich wissen, ob Nachrichten Ende-zu-Ende-verschlüsselt sind?</a></li>
<li><a href="#howtoe2ee">Wie kann ich garantierte Ende-zu-Ende-Verschlüsselung und grüne Häkchen erhalten?</a></li> <li><a href="#kann-ich-e-mails-ohne-ende-zu-ende-verschlüsselung-empfangen-oder-senden">Kann ich E-Mails ohne Ende-zu-Ende-Verschlüsselung empfangen oder senden?</a></li>
<li><a href="#e2eeguarantee">Was bedeuten das “Grüne Häkchen” und die “garantierte Ende-zu-Ende-Verschlüsselung”?</a></li> <li><a href="#howtoe2ee">Wie kann ich einen Chat mit einem neuen Kontakt erstellen?</a></li>
<li><a href="#nocryptanymore">Ein Kontakt hat eine Nachricht von einem anderen Gerät gesendet”, was kann ich tun?</a></li> <li><a href="#e2eeguarantee">Was bedeutet das grüne Häkchen in einem Kontaktprofil?</a></li>
<li><a href="#sind-anhänge-bilder-dateien-audio-usw-ende-zu-ende-verschlüsselt">Sind Anhänge (Bilder, Dateien, Audio usw.) Ende-zu-Ende-verschlüsselt?</a></li> <li><a href="#sind-anhänge-bilder-dateien-audio-usw-ende-zu-ende-verschlüsselt">Sind Anhänge (Bilder, Dateien, Audio usw.) Ende-zu-Ende-verschlüsselt?</a></li>
<li><a href="#openpgp-secure">Ist OpenPGP sicher?</a></li> <li><a href="#openpgp-secure">Ist OpenPGP sicher?</a></li>
<li><a href="#openpgp-alternatives">Wurden Alternativen zu OpenPGP für die Ende-zu-Ende-Verschlüsselung in Betracht gezogen?</a></li> <li><a href="#openpgp-alternatives">Wurden Alternativen zu OpenPGP für die Ende-zu-Ende-Verschlüsselung in Betracht gezogen?</a></li>
<li><a href="#ist-delta-chat-anfällig-für-efail">Ist Delta Chat anfällig für EFAIL?</a></li> <li><a href="#ist-delta-chat-anfällig-für-efail">Ist Delta Chat anfällig für EFAIL?</a></li>
<li><a href="#tls">Wird eine Nachricht im Klartext gesendet, wenn keine Ende-zu-Ende-Verschlüsselung verfügbar ist?</a></li> <li><a href="#tls">Sind mit dem Mail-Symbol markierte Nachrichten im Internet sichtbar?</a></li>
<li><a href="#message-metadata">Wie schützt Delta Chat Metadaten in Nachrichten?</a></li> <li><a href="#message-metadata">Wie schützt Delta Chat Metadaten in Nachrichten?</a></li>
<li><a href="#device-seizure">Wie schützt man Metadaten und Kontakte, wenn ein Gerät beschlagnahmt wird?</a></li> <li><a href="#device-seizure">Wie schützt man Metadaten und Kontakte, wenn ein Gerät beschlagnahmt wird?</a></li>
<li><a href="#wie-kann-ich-die-verschlüsselungsinformationen-überprüfen">Wie kann ich die Verschlüsselungsinformationen überprüfen?</a></li> <li><a href="#sealedsender">Unterstützt Delta Chat „Sealed Sender“?</a></li>
<li><a href="#wie-kann-ich-den-verschlüsselungsstatus-von-nachrichten-überprüfen">Wie kann ich den Verschlüsselungsstatus von Nachrichten überprüfen?</a></li>
<li><a href="#warum-sehe-ich-unverschlüsselte-nachrichten">Warum sehe ich unverschlüsselte Nachrichten?</a></li>
<li><a href="#wie-kann-ich-einen-ende-zu-ende-verschlüsselten-chat-mit-einem-delta-chat-kontakt-führen-der-manchmal-webmail-oder-eine-andere-e-mail-anwendung-ohne-autocrypt-verwendet">Wie kann ich einen Ende-zu-Ende-verschlüsselten Chat mit einem Delta-Chat-Kontakt führen, der manchmal Webmail oder eine andere E-Mail-Anwendung ohne Autocrypt verwendet?</a></li>
<li><a href="#wie-kann-ich-ende-zu-ende-verschlüsselung-und-löschen-von-nachrichten-sicherstellen">Wie kann ich Ende-zu-Ende-Verschlüsselung und Löschen von Nachrichten sicherstellen?</a></li>
<li><a href="#pfs">Unterstützt Delta Chat “Perfect Forward Secrecy”?</a></li> <li><a href="#pfs">Unterstützt Delta Chat “Perfect Forward Secrecy”?</a></li>
<li><a href="#ist-die-ende-zu-ende-verschlüsselung-von-delta-chat-genauso-sicher-wie-die-von-signal">Ist die Ende-zu-Ende-Verschlüsselung von Delta Chat genauso sicher wie die von Signal?</a></li> <li><a href="#pqc">Unterstützt Delta Chat Post-Quantum-Verschlüsselung?</a></li>
<li><a href="#wie-kann-ich-die-verschlüsselung-manuell-überprüfen">Wie kann ich die Verschlüsselung manuell überprüfen?</a></li>
<li><a href="#importkey">Kann ich meinen existierenden privaten Schlüssel weiter verwenden?</a></li> <li><a href="#importkey">Kann ich meinen existierenden privaten Schlüssel weiter verwenden?</a></li>
<li><a href="#security-audits">Wurde Delta Chat unabhängig auf Sicherheitslücken geprüft?</a></li> <li><a href="#security-audits">Wurde Delta Chat unabhängig auf Sicherheitslücken geprüft?</a></li>
</ul> </ul>
@ -90,7 +87,7 @@
<ul> <ul>
<li><a href="#welche-app-berechtigungen-benötigt-delta-chat">Welche App-Berechtigungen benötigt Delta Chat?</a></li> <li><a href="#welche-app-berechtigungen-benötigt-delta-chat">Welche App-Berechtigungen benötigt Delta Chat?</a></li>
<li><a href="#funktioniert-delta-chat-mit-meinem-e-mail-anbieter">Funktioniert Delta Chat mit <em>meinem</em> E-Mail-Anbieter?</a></li> <li><a href="#funktioniert-delta-chat-mit-meinem-e-mail-anbieter">Funktioniert Delta Chat mit <em>meinem</em> E-Mail-Anbieter?</a></li>
<li><a href="#i-want-to-manage-my-own-server-for-delta-chat-what-do-you-recommend">I want to manage my own server for Delta Chat. What do you recommend?</a></li> <li><a href="#ich-möchte-meinen-eigenen-server-für-delta-chat-verwalten-gibt-es-empfehlungen">Ich möchte meinen eigenen Server für Delta Chat verwalten. Gibt es Empfehlungen?</a></li>
<li><a href="#weshalb-muss-ich-mein-e-mail-kennwort-in-delta-chat-eingeben-ist-das-sicher">Weshalb muss ich mein E-Mail-Kennwort in Delta Chat eingeben? Ist das sicher?</a></li> <li><a href="#weshalb-muss-ich-mein-e-mail-kennwort-in-delta-chat-eingeben-ist-das-sicher">Weshalb muss ich mein E-Mail-Kennwort in Delta Chat eingeben? Ist das sicher?</a></li>
<li><a href="#welche-nachrichten-erscheinen-in-delta-chat">Welche Nachrichten erscheinen in Delta Chat?</a></li> <li><a href="#welche-nachrichten-erscheinen-in-delta-chat">Welche Nachrichten erscheinen in Delta Chat?</a></li>
<li><a href="#unterstützt-delta-chat-html-e-mails">Unterstützt Delta Chat HTML-E-Mails?</a></li> <li><a href="#unterstützt-delta-chat-html-e-mails">Unterstützt Delta Chat HTML-E-Mails?</a></li>
@ -681,10 +678,10 @@ hat, das eine „sofortige Zustellung“ von Nachrichten für alle Chatmail-Serv
Einschließlich dem Chatmail-Server, <a href="https://delta.chat/chatmail#selfhosted">den Sie selbst ohne unsere Erlaubnis einrichten könnten</a>. Einschließlich dem Chatmail-Server, <a href="https://delta.chat/chatmail#selfhosted">den Sie selbst ohne unsere Erlaubnis einrichten könnten</a>.
Willkommen bei der Macht des interoperablen und massiven Chatmail- und E-Mail-Systems :)</p> Willkommen bei der Macht des interoperablen und massiven Chatmail- und E-Mail-Systems :)</p>
<h2 id="verschlüsselung-und-sicherheit"> <h2 id="e2ee">
Verschlüsselung und Sicherheit <a href="#verschlüsselung-und-sicherheit" class="anchor"></a> Verschlüsselung und Sicherheit <a href="#e2ee" class="anchor"></a>
</h2> </h2>
@ -697,17 +694,26 @@ Willkommen bei der Macht des interoperablen und massiven Chatmail- und E-Mail-Sy
</h3> </h3>
<p><a href="https://autocrypt.org">Autocrypt</a> wird verwendet, um automatisch <p>Delta Chat uses a <a href="#openpgp-secure">secure subset of the OpenPGP standard</a>
eine Ende-zu-Ende-Verschlüsselung mit Kontakten und Gruppenchats herzustellen. to provide automatic end-to-end encryption using these protocols:</p>
Autocrypt verwendet eine begrenzte und <a href="#openpgp-secure">sichere Untermenge des OpenPGP-Standards</a>.
Ende-zu-Ende-verschlüsselte Nachrichten sind mit einem Vorhängeschloss gekennzeichnet <img style="vertical-align:middle; width:1.2em; margin:1px" src="../lock-icon.png" alt="padlock" /></p>
<p><a href="https://securejoin.delta.chat/en/latest/new.html">Secure-Join-Protokolle</a> <ul>
werden für Chats mit garantierter Ende-zu-Ende-Verschlüsselung verwendet, <li>
die vor Netzwerkangriffen und kompromittierten Servern schützt. <p><a href="https://securejoin.delta.chat/en/latest/new.html">Secure-Join</a>
Chats, die mit einem grünen Häkchen markiert sind to exchange encryption setup information through QR-code scanning or “invite links”.</p>
<img style="vertical-align:middle; width:1.5em; margin:1px" src="../green-checkmark.png" alt="green checkmark" /> </li>
garantieren Ende-zu-Ende-verschlüsselte Nachrichten.</p> <li>
<p><a href="https://autocrypt.org">Autocrypt</a> is used for automatically
establishing end-to-end encryption between contacts and all members of a group chat.</p>
</li>
<li>
<p><a href="https://github.com/chatmail/core/blob/main/spec.md#attaching-a-contact-to-a-message">Sharing a contact to a
chat</a>
enables receivers to use end-to-end encryption with the contact.</p>
</li>
</ul>
<p>Delta Chat does not query, publish or interact with any OpenPGP key servers.</p>
<h3 id="whene2e"> <h3 id="whene2e">
@ -717,28 +723,36 @@ garantieren Ende-zu-Ende-verschlüsselte Nachrichten.</p>
</h3> </h3>
<p>Ende-zu-Ende-verschlüsselten Nachrichten sind mit einem Vorhängeschloss versehen:</p> <p>All messages in Delta Chat are <strong>end-to-end encrypted by default</strong>.
Since the Delta Chat Version 2 release series (July 2025)
there are no lock or similar markers on end-to-end encrypted messages, anymore.</p>
<p><img style="width:160px; margin:1px" src="../lock-screenshot.png" alt="padlock in bubble" /></p> <h3 id="kann-ich-e-mails-ohne-ende-zu-ende-verschlüsselung-empfangen-oder-senden">
<p>Die Ende-zu-Ende-Verschlüsselung ist garantiert, wenn neben dem Chat-Titel ein grünes Häkchen zu sehen ist:</p>
<p><img style="width:211px; margin:1px" src="../green-checkmark-screenshot.png" alt="green checkmark in title" /></p>
<h3 id="howtoe2ee">
Wie kann ich garantierte Ende-zu-Ende-Verschlüsselung und grüne Häkchen erhalten? <a href="#howtoe2ee" class="anchor"></a> Kann ich E-Mails ohne Ende-zu-Ende-Verschlüsselung empfangen oder senden? <a href="#kann-ich-e-mails-ohne-ende-zu-ende-verschlüsselung-empfangen-oder-senden" class="anchor"></a>
</h3> </h3>
<p>Wenn Sie einen zweiten Kommunikationskanal mit Ihrem Chatpartner haben, <p>Wenn Sie die Standard-<a href="https://chatmail.at/relays">Chatmail-Relays</a> verwenden, ist es unmöglich, Nachrichten ohne End-to-End-Verschlüsselung zu empfangen oder zu senden.</p>
wie einen Video-Chat oder einen anderen Messenger,
können Sie einen Einladungslink erstellen.</p>
<p>Wenn Sie persönlich zusammen sind, <p>Wenn Sie stattdessen ein Profil mit einem klassischen E-Mail-Server erstellen,
können Sie Ihrem Chat-Partner einen QR-Code zeigen.</p> können Sie Nachrichten ohne End-to-End-Verschlüsselung senden und empfangen.
Solche Nachrichten werden mit einem E-Mail-Symbol gekennzeichnet
<img style="vertical-align:middle; width:1.2em; margin:1px" src="../email-icon.png" alt="email" />.</p>
<h3 id="howtoe2ee">
Wie kann ich einen Chat mit einem neuen Kontakt erstellen? <a href="#howtoe2ee" class="anchor"></a>
</h3>
<p>You can send an invite link through another private chat,
show an invitation QR code when next to each other or in a video call,
or click on a “contact” that was shared in a chat.</p>
<ul> <ul>
<li> <li>
@ -747,133 +761,60 @@ tippen Sie auf den Titel der Gruppe, um die Mitgliederliste anzuzeigen,
und wählen Sie „QR-Einladungscode“.</p> und wählen Sie „QR-Einladungscode“.</p>
</li> </li>
<li> <li>
<p>Für <strong>Direktchat-Einladungen</strong>, <p>For <strong>direct 1:1 chat invitations</strong>,
tippen Sie auf das QR-Code-Symbol <img style="vertical-align:middle; width:1.8em; margin:1px" src="../qr-icon.png" /> tap the QR Code icon <img style="vertical-align:middle; width:1.8em; margin:1px" src="../qr-icon.png" />
auf dem Hauptbildschirm der Delta-Chat-App.</p> on the Delta Chat app main screen.</p>
</li> </li>
</ul> </ul>
<p>Lassen Sie Ihren Chat-Partner den QR-Code mit der Delta-Chat-App scannen. <p>Ask your chat partner to scan the QR image
Oder Sie klicken auf „Kopieren“ oder „Teilen“, um einen Einladungslink zu erstellen und diesen mit Ihrem Chat-Partner zu teilen.</p> with their Delta Chat app,
or click “Copy” or “Share” to create an invite link
and share it with your chat partner.</p>
<p>Warten Sie nun, während das <a href="https://securejoin.delta.chat/en/latest/new.html#setup-contact-protocol">Secure-Join-Protokoll</a> zwischen beiden Geräten abläuft.</p> <p>Now wait while <a href="https://securejoin.delta.chat/en/latest/new.html#setup-contact-protocol">end-to-end encryption is getting established</a>.</p>
<ul> <ul>
<li> <li>
<p>Wenn beide Geräte online sind, <p>If both sides are online, they will soon see a (group or direct) chat
sehen beide Seiten schließlich einen Gruppen- oder Direkt-Chat mit einem grünen Häkchen and can start messaging securely.</p>
<img style="vertical-align:middle; width:1.5em; margin:1px" src="../green-checkmark.png" alt="green checkmark" />
neben dem Titel.</p>
</li> </li>
<li> <li>
<p>Wenn eines der Geräte offline ist, erscheinen die grünen Häkchen erst <p>If one side is offline or in bad network,
später, wenn das Gerät wieder mit dem Internet verbunden ist the ability to chat is delayed until connectivity is restored.</p>
und das Secure-Join-Protokoll abgeschlossen werden kann.</p>
</li> </li>
</ul> </ul>
<p>Herzlichen Glückwunsch! 🎉 <p>Congratulations!
Sie verwenden nun eine garantierte Ende-zu-Ende-Verschlüsselung You now will automatically use end-to-end encryption
mit diesem Kontakt und Sie beide können sich gegenseitig zu grün markierten Gruppen hinzufügen with this contact.
<img style="vertical-align:middle; width:1.5em; margin:1px" src="../green-checkmark.png" alt="green checkmark" />, If you add each other to chat groups,
Dadurch wird die garantierte Ende-zu-Ende-Verschlüsselung automatisch unter den Mitgliedern dieser Gruppe verbreitet.</p> end-to-end encryption will be established among all members.</p>
<h3 id="e2eeguarantee"> <h3 id="e2eeguarantee">
Was bedeuten das “Grüne Häkchen” und die “garantierte Ende-zu-Ende-Verschlüsselung”? <a href="#e2eeguarantee" class="anchor"></a> Was bedeutet das grüne Häkchen in einem Kontaktprofil? <a href="#e2eeguarantee" class="anchor"></a>
</h3> </h3>
<p><strong>Chat-Titel mit grünen Häkchen</strong> <p>A contact profile might show a green checkmark
<img style="vertical-align:middle; width:1.5em; margin:1px" src="../green-checkmark.png" alt="green checkmark" /> <img style="vertical-align:middle; width:1.5em; margin:1px" src="../green-checkmark.png" alt="green checkmark" />
bedeuten, dass alle Nachrichten im Chat Ende-zu-Ende-verschlüsselt werden and an “Introduced by” line.
und nicht von kompromittierten E-Mail-Servern oder Internet-Providern gelesen oder verändert werden können. Every green-checkmarked contact either did a direct <a href="#howtoe2ee">QR-scan</a> with you
Beim Beitritt zu Gruppenchats mit grünen Häkchen or was introduced by a another green-checkmarked contact.
werden Verschlüsselungsinformationen (und die grünen Häkchen) aller Teilnehmer sicher so weitergegeben, Introductions happen automatically when adding members to groups.
dass die Ende-zu-Ende-Verschlüsselung in der Gruppe und zwischen den Mitgliedern garantiert werden kann.</p> Whoever adds a green-checkmarked contact to a group with only green-checkmarked members
becomes an introducer.
<p><strong>Kontaktprofile mit grünen Häkchen</strong> In a contact profile you can tap on the “Introduced by …” text repeatedly
<img style="vertical-align:middle; width:1.5em; margin:1px" src="../green-checkmark.png" alt="green checkmark" /> until you get to the one with whom you directly did a <a href="#howtoe2ee">QR-scan</a>.</p>
bedeuten, dass die Nachrichtenübermittlung an einen Kontakt derzeit garantiert Ende-zu-Ende-verschlüsselt ist.
Jeder grün markierte Kontakt hat entweder einen direkten <a href="#howtoe2ee">QR-Scan</a> mit Ihnen durchgeführt
oder wurde von einem anderen Kontakt mit grünem Häkchen eingeführt.
Das Einführen geschieht automatisch, wenn Sie Mitglieder zu Gruppen hinzufügen.
Wer einen Kontakt zu einer Gruppe mit grünem Häkchen hinzufügt, wird zum Einführenden
für die Mitglieder, die noch nichts von dem hinzugefügten Kontakt wussten.
In einem Kontaktprofil können Sie wiederholt auf den Text “Eingeführt von …” tippen
bis Sie zu demjenigen gelangen, mit dem Sie einen direkten <a href="#howtoe2ee">QR-Scan</a> gemacht haben.</p>
<p>Beachten Sie, dass Sie in einem Kontaktprofil unter Umständen Einführende sehen und antippen können, aber kein grünes Häkchen im Profiltitel vorhanden ist.
Dies bedeutet normalerweise, dass der Kontakt <a href="#nocryptanymore">“eine Nachricht von einem anderen Gerät gesendet hat”</a>.</p>
<p>Für eine ausführlichere Diskussion der “Garantierten Ende-zu-Ende-Verschlüsselung”, <p>Für eine ausführlichere Diskussion der “Garantierten Ende-zu-Ende-Verschlüsselung”,
siehe <a href="https://securejoin.delta.chat/en/latest/new.html">Secure-Join-Protokolle</a> siehe <a href="https://securejoin.delta.chat/en/latest/new.html">Secure-Join-Protokolle</a>
und dort speziell den Abschnitt zu “Verified Groups”, dem technischen Begriff und dort speziell den Abschnitt zu “Verified Groups”, dem technischen Begriff
für “Chats mit grünem Häkchen” oder “Garantierter Ende-zu-Ende-Verschlüsselung”.</p> für “Chats mit grünem Häkchen” oder “Garantierter Ende-zu-Ende-Verschlüsselung”.</p>
<h3 id="nocryptanymore">
Ein Kontakt hat eine Nachricht von einem anderen Gerät gesendet”, was kann ich tun? <a href="#nocryptanymore" class="anchor"></a>
</h3>
<p>Wenn Sie diese Warnung sehen, wurde das grüne Häkchen entfernt, da für den Kontakt die Ende-zu-Ende-Verschlüsselung nicht mehr garantiert werden kann.
<strong>Wenn Sie den Wegfall der garantierten Ende-zu-Ende-Verschlüsselung
für diesen Kontakt überraschend finden, akzeptieren Sie die Warnung nicht!</strong>
Versuchen Sie stattdessen mit Ihrem Kontakt über einen zweiten Kanal (z.B. Videoanruf, Telefon oder ein anderer Messenger) herauszufinden, was passiert ist.</p>
<p>Wenn Ihr Kontakt tatsächlich den Ausfall der garantierten Ende-zu-Ende-Verschlüsselung verursacht hat,
finden Sie in den nächsten Abschnitten häufige Gründe und Abhilfe.
Unabhängig davon bleiben alle anderen Chats mit einem grünen Häkchen garantiert Ende-zu-Ende-verschlüsselt,
auch wenn der Kontakt dort Mitglied ist.</p>
<p><strong>Ihr Kontakt verwendet Delta Chat auf einem zweiten Gerät (Smartphone oder Laptop)</strong></p>
<p>Wenn Ihr Kontakt ein weiteres Gerät mit Delta Chat eingerichtet hat,
sollte das Konto von dem neuen Gerät entfernen werden und <a href="#multiclient">als zweites Gerät, wie hier beschrieben</a>, erneut hinzugefügt werden.
Sobald sie sich danach schreiben, wird die Warnung verschwinden
und die Verschlüsselung ist mit beiden Geräten Ihres Kontakts garantiert.</p>
<p><strong>Ihr Kontakt hat Delta Chat mit seinem alten Login neu installiert</strong></p>
<p>Wenn Ihr Kontakt <a href="#backup">ein Backup</a> hat,
sollte das Profil auf dem neuen Gerät
entfernt werden und stattdessen das Backup importiert werden, um das Konto neu zu erstellen.
Sobald sie sich danach schreiben, wird die Warnung verschwinden
und die garantierte Verschlüsselung wird für diesen Kontakt wiederhergestellt.</p>
<p>Wenn Ihr Kontakt kein Backup hat, ist es am besten, einen <a href="#howtoe2ee">QR-Code-Scan</a>
mit Ihrem Chat-Partner durchzuführen, um die garantierte Ende-zu-Ende-Verschlüsselung wiederherzustellen.</p>
<p><strong>Ihr Kontakt hat eine E-Mail über Webmail oder eine andere E-Mail-Anwendung gesendet,
wird Delta Chat aber bald wieder benutzen.</strong></p>
<p>Wenn Sie wissen, dass der Kontakt manchmal Webmail,
oder andere E-Mail-Anwendungen ohne Ende-zu-Ende-Verschlüsselung verwendet,
dann können Sie die Warnung akzeptieren.
Sobald Ihr Kontakt Delta Chat wieder benutzt,
wird die garantierte Ende-zu-Ende-Verschlüsselung automatisch wiederhergestellt.</p>
<p><strong>Ihr Kontakt hat die Nutzung von Delta Chat komplett eingestellt</strong></p>
<p>Manchmal ist es wichtiger, in Kontakt zu bleiben als eine Ende-zu-Ende-Verschlüsselung zu haben;
die <a href="#tls">“Transport Layer Encryption” (TLS)</a> kann die Vertraulichkeit
Ihrer Nachrichten zwischen Ihrem Gerät und dem E-Mail-Server dennoch schützen.
Ohne Ende-zu-Ende-Verschlüsselung vertrauen Sie und Ihr Chat-Partner jedoch darauf, dass Ihr E-Mail-Server Nachrichten nicht liest oder manipuliert und sie nicht an Dritte weitergibt.</p>
<p>In jedem Fall können Sie nicht viel mehr tun, als die Warnung zu akzeptieren.
Bitte entfernen Sie den Kontakt auch aus allen aktiven, grün markierten Gruppen
die Sie unter “Gemeinsame Chats” im Profil des Kontakts finden können.
So vermeiden Sie, dass Ihr Kontakt “unlesbare” Nachrichten erhält.</p>
<p>Wenn der Kontakt Delta Chat aufgrund von Fehlern oder Bugs nicht mehr verwendet,
können Sie diese in unser <a href="https://support.delta.chat">Support-Forum</a> schreiben,
und uns so dabei helfen, häufige Probleme zu identifizieren und zu lösen. Vielen Dank!</p>
<h3 id="sind-anhänge-bilder-dateien-audio-usw-ende-zu-ende-verschlüsselt"> <h3 id="sind-anhänge-bilder-dateien-audio-usw-ende-zu-ende-verschlüsselt">
@ -897,10 +838,9 @@ und Anhang-Metadaten wie Dateinamen.</p>
</h3> </h3>
<p>Ja, Delta Chat verwendet eine sichere Untermenge von OpenPGP <p>Yes, Delta Chat uses a secure subset of OpenPGP
und zeigt nur dann ein Vorhängeschloss auf einer Nachricht an, requiring the whole message to be properly encrypted and signed.
wenn die gesamte Nachricht ordnungsgemäß verschlüsselt und signiert ist. For example, “Detached signatures” are not treated as secure.</p>
Zum Beispiel werden “Detached Signatures” nicht als sicher betrachtet.</p>
<p>Die meisten öffentlich diskutierten OpenPGP-Probleme <p>Die meisten öffentlich diskutierten OpenPGP-Probleme
resultieren in Wirklichkeit aus schlechter Usability oder schlechter Implementierung von Tools oder Anwendungen - oder beidem. resultieren in Wirklichkeit aus schlechter Usability oder schlechter Implementierung von Tools oder Anwendungen - oder beidem.
@ -961,16 +901,15 @@ so wie in der Autocrypt-Level-1-Spezifikation definiert.</p>
<h3 id="tls"> <h3 id="tls">
Wird eine Nachricht im Klartext gesendet, wenn keine Ende-zu-Ende-Verschlüsselung verfügbar ist? <a href="#tls" class="anchor"></a> Sind mit dem Mail-Symbol markierte Nachrichten im Internet sichtbar? <a href="#tls" class="anchor"></a>
</h3> </h3>
<p>Auch wenn Ihre Nachrichten nicht Ende-zu-Ende-verschlüsselt sind, <p>If you are sending or receiving e-mail messages without end-to-end encryption (using a classic e-mail server),
sind sie dennoch vor Internetanbietern wie Mobilfunk- oder Telefongesellschaften geschützt. they are still protected from cell or cable companies who can not read or modify your e-mail messages.
Allerdings können Ihr E-Mail-Provider und der des Empfängers But both your and your recipient’s e-mail providers
Ihre Nachrichten lesen, analysieren oder sogar verändern, may read, analyze or modify your messages, including any attachments.</p>
wenn sie nicht Ende-zu-Ende-verschlüsselt sind.</p>
<p>Delta Chat verwendet standardmäßig strikte <p>Delta Chat verwendet standardmäßig strikte
<a href="https://en.wikipedia.org/wiki/Transport_Layer_Security">TLS-Verschlüsselung</a>, <a href="https://en.wikipedia.org/wiki/Transport_Layer_Security">TLS-Verschlüsselung</a>,
@ -983,10 +922,6 @@ wird TLS zwischen den E-Mail-Anbietern durchgesetzt.
In diesem Fall wird die Delta-Chat-Kommunikation niemals im Klartext ins Internet gelangen In diesem Fall wird die Delta-Chat-Kommunikation niemals im Klartext ins Internet gelangen
selbst wenn die Nachricht nicht Ende-zu-Ende-verschlüsselt war.</p> selbst wenn die Nachricht nicht Ende-zu-Ende-verschlüsselt war.</p>
<p>Beachten Sie, dass die <a href="#howtoe2ee">Beibehaltung der garantierten Ende-zu-Ende-Verschlüsselung</a> zusätzlich zur TLS-Verschlüsselung
eine allumfassende Sicherheit zwischen Ihrem Gerät und dem des Empfängers bietet.
Nicht einmal Ihr E-Mail- oder Internet-Provider wird in der Lage sein, Ihre Nachrichten zu lesen oder zu verändern.</p>
<h3 id="message-metadata"> <h3 id="message-metadata">
@ -995,24 +930,25 @@ Nicht einmal Ihr E-Mail- oder Internet-Provider wird in der Lage sein, Ihre Nach
</h3> </h3>
<p>Delta Chat schützt die meisten Metadaten von Nachrichten, indem es die folgenden Informationen <p>Anders als die meisten anderen Messenger
in den Ende-zu-Ende-verschlüsselten Teil der Nachrichten verschiebt:</p> speichern Delta-Chat-Apps keine Metadaten über Kontakte oder Gruppen auf Servern. Auch nicht in verschlüsselter Form.
Stattdessen werden alle Gruppen-Metadaten durchgängig verschlüsselt und ausschließlich auf den Endgeräten der Nutzer gespeichert.</p>
<p>E-Mail-Server können deshalb nur das Folgende sehen:</p>
<ul> <ul>
<li>Betreffzeile</li> <li>
<li>Avatar und Name der Gruppe</li> <p>Uhrzeit und Datum der Nachricht</p>
<li>Lesebestätigungen (<code class="language-plaintext highlighter-rouge">Chat-Disposition-Notification-To</code>)</li> </li>
<li>Timer für verschwindende Nachrichten (<code class="language-plaintext highlighter-rouge">Ephemeral-Timer</code>)</li> <li>
<li><code class="language-plaintext highlighter-rouge">Chat-Group-Member-Removed</code>, <code class="language-plaintext highlighter-rouge">Chat-Group-Member-Added</code></li> <p>Absende- und Empfangsadresse</p>
<li><code class="language-plaintext highlighter-rouge">Secure-Join</code>-Header</li> </li>
<li>Aktivierung des Standort-Streamings</li> <li>
<li>WebRTC-Raum-URL</li> <p>Größe der Nachricht</p>
</li>
</ul> </ul>
<p>E-Mail-Server erhalten keinen Zugriff auf diese geschützten Metadaten, <p>All other message, contact and group metadata resides in the end-to-end encrypted part of messages.</p>
sehen aber Datum und Größe der Nachricht sowie die Absender- und Empfängeradressen.
E-Mail-Server benötigen Empfängeradressen, um Nachrichten
Nachrichten an die Geräte der Empfänger weiterzuleiten und zuzustellen.</p>
<h3 id="device-seizure"> <h3 id="device-seizure">
@ -1022,93 +958,36 @@ Nachrichten an die Geräte der Empfänger weiterzuleiten und zuzustellen.</p>
</h3> </h3>
<p>Sowohl zum Schutz vor E-Mail-Servern, die Metadaten sammeln, <p>Both for protecting against metadata-collecting e-mail servers
als auch gegen die Gefahr der Beschlagnahmung von Geräten as well as against the threat of device seizure
empfehlen wir die Verwendung einer für Delta Chat optimierten <a href="https://delta.chat/serverguide">E-Mail-Server-Instanz</a>, um pseudonym-temporäre Konten durch Scannen von QR-Codes zu erstellen. we recommend to use a <a href="https://chatmail.at/relays">chatmail relay</a>
Beachten Sie, dass Delta-Chat-Apps auf allen Plattformen mehrere Konten unterstützen. to create chat profiles using random e-mail addresses for transport.
Sie können also problemlos aktionsspezifische “1-Wochen-“ oder “1-Monats-Konten” neben Ihrem “Hauptkonto” verwenden, Note that Delta Chat apps on all platforms support multiple profiles
mit dem Wissen, dass alle temporären Kontodaten zusammen mit allen Metadaten gelöscht werden. so you can easily use situation-specific profiles next to your “main” profile
Wenn ein Gerät beschlagnahmt wird, können Kontakte mit temporären E-Mail-Konten with the knowledge that all their data, along with all metadata, will be deleted.
Konten nicht so leicht identifiziert werden, wie dies bei Messengern der Fall ist, die die Moreover, if a device is seized then chat contacts using short-lived profiles
Telefonnummern in Chatgruppen preisgeben, die wiederum oft mit legalen Identitäten verbunden sind.</p> can not be identified easily.</p>
<h3 id="wie-kann-ich-die-verschlüsselungsinformationen-überprüfen"> <h3 id="sealedsender">
Wie kann ich die Verschlüsselungsinformationen überprüfen? <a href="#wie-kann-ich-die-verschlüsselungsinformationen-überprüfen" class="anchor"></a> Unterstützt Delta Chat „Sealed Sender“? <a href="#sealedsender" class="anchor"></a>
</h3> </h3>
<p>Sie können den Status der Ende-zu-Ende-Verschlüsselung manuell im Dialog “Verschlüsselung” <p>No, not yet.</p>
(Android/iOS: Benutzerprofil, Desktop: Rechtsklick auf den Chat eines Benutzers) überprüfen.
Delta Chat zeigt dort zwei Fingerabdrücke an.
Wenn die gleichen Fingerabdrücke auf Ihrem eigenen Gerät und auf dem Gerät Ihres Kontakts erscheinen,
ist die Verbindung sicher.</p>
<h3 id="wie-kann-ich-den-verschlüsselungsstatus-von-nachrichten-überprüfen"> <p>The Signal messenger introduced <a href="https://signal.org/blog/sealed-sender/">“Sealed Sender” in 2018</a>
to keep their server infrastructure ignorant of who is sending a message to a set of recipients.
It is particularly important because the Signal server knows the mobile number of each account,
which is usually associated with a passport identity.</p>
<p>Even if <a href="https://chatmail.at/relays">chatmail relays</a>
Wie kann ich den Verschlüsselungsstatus von Nachrichten überprüfen? <a href="#wie-kann-ich-den-verschlüsselungsstatus-von-nachrichten-überprüfen" class="anchor"></a> do not ask for any private data (including no phone numbers),
it might still be worthwhile to protect relational metadata between addresses.
We don’t foresee bigger problems in using random throw-away e-mail addresses for sealed sending
</h3> but an implementation has not been agreed as a priority yet.</p>
<p>Ein kleines <strong>Vorhängeschloss</strong> in einer Nachrichten zeigt an,
dass die Nachricht vom Absender korrekt Ende-zu-Ende-verschlüsselt wurde.
Wenn <strong>kein Vorhängeschloss</strong> vorhanden ist, wurde die Nachricht nicht oder nicht korrekt Ende-zu-Ende-verschlüsselt.
Höchstwahrscheinlich, weil der Absender ein Webmail-Interface oder eine App
ohne Ende-zu-Ende-Unterstützung verwendet.</p>
<h3 id="warum-sehe-ich-unverschlüsselte-nachrichten">
Warum sehe ich unverschlüsselte Nachrichten? <a href="#warum-sehe-ich-unverschlüsselte-nachrichten" class="anchor"></a>
</h3>
<p>Wenn ein Kontakt keine Autocrypt-fähige App verwendet,
werden alle Nachrichten, die diesen Kontakt betreffen (in Gruppen- oder Direkt-Chats),
nicht Ende-zu-Ende-verschlüsselt und zeigen daher kein “Vorhängeschloss”.
Beachten Sie, auch Kontakte, die primär Delta Chat verwenden,
können gleichzeitig auch nicht-Autocrypt-fähige Apps verwenden.
Das unverschlüsselte Antworten auf unverschlüsselte Nachrichten wird von Autocrypt vorgeschrieben
um zu verhindern, dass unlesbare Nachrichten auf der Seite Ihrer Kontakte ankommen.</p>
<h3 id="wie-kann-ich-einen-ende-zu-ende-verschlüsselten-chat-mit-einem-delta-chat-kontakt-führen-der-manchmal-webmail-oder-eine-andere-e-mail-anwendung-ohne-autocrypt-verwendet">
Wie kann ich einen Ende-zu-Ende-verschlüsselten Chat mit einem Delta-Chat-Kontakt führen, der manchmal Webmail oder eine andere E-Mail-Anwendung ohne Autocrypt verwendet? <a href="#wie-kann-ich-einen-ende-zu-ende-verschlüsselten-chat-mit-einem-delta-chat-kontakt-führen-der-manchmal-webmail-oder-eine-andere-e-mail-anwendung-ohne-autocrypt-verwendet" class="anchor"></a>
</h3>
<p>Wenn Sie einen sicheren Ende-zu-Ende-verschlüsselten Chat mit einem Kontakt benötigen,
der sowohl Delta Chat als auch Nicht-Autocrypt-Anwendungen nutzt,
können Sie eine <a href="#howtoe2ee">garantierte Ende-zu-Ende-Verschlüsselung</a> einrichten, mit einer Gruppe mit Ihnen beiden als Mitgliedern.
In diesem Gruppenchat werden alle Nachrichten Ende-zu-Ende verschlüsselt werdejn,
auch wenn im Direkt-Chat eine
<a href="#nocryptanymore">“Nachricht von einem anderen Gerät gesendet”</a> wurde.</p>
<h3 id="wie-kann-ich-ende-zu-ende-verschlüsselung-und-löschen-von-nachrichten-sicherstellen">
Wie kann ich Ende-zu-Ende-Verschlüsselung und Löschen von Nachrichten sicherstellen? <a href="#wie-kann-ich-ende-zu-ende-verschlüsselung-und-löschen-von-nachrichten-sicherstellen" class="anchor"></a>
</h3>
<p>Der beste Weg, um sicherzustellen, dass alle Nachrichten Ende-zu-Ende-verschlüsselt sind
und Metadaten so schnell wie möglich gelöscht werden,
ist <a href="#howtoe2ee">die Verwendung von Chats mit garantierter Ende-zu-Ende-Verschlüsselung</a>
und die Aktivierung von <a href="#ephemeralmsgs">verschwindenden Nachrichten</a>.</p>
<p>Garantierte Ende-zu-Ende-Verschlüsselung schützt vor <a href="https://en.wikipedia.org/wiki/Man-in-the-middle_attack">MITM-Angriffen</a>
und das Aktivieren von “Verschwindende Nachrichten” löscht die Nachrichten
auf dem Server und Lokal nach einer vom Benutzer eingestellten Zeit.</p>
<p>Wenn Sie die Nachrichten auf Ihrem Gerät, aber nicht auf dem Server benötigen, können Sie auch in der Gruppe vereinbaren, <a href="#delold">“Nachrichten automatisch vom Server löschen”</a> einzuschalten.</p>
<h3 id="pfs"> <h3 id="pfs">
@ -1118,42 +997,52 @@ auf dem Server und Lokal nach einer vom Benutzer eingestellten Zeit.</p>
</h3> </h3>
<p>Nein, Delta Chat unterstützt kein “Perfect Forward Secrecy” (PFS). <p>No, not yet.</p>
Das bedeutet, wenn Ihr privater Delta-Chat-Schlüssel durchgesickert ist
und jemand Ihre vorherigen In-Transit-Nachrichten gesammelt hat,
können diese mit dem veröffentlichtem Schlüssel entschlüsselt werden.</p>
<p>Beachten Sie jedoch, dass jemand, der in den Besitz Ihrer privaten Schlüssel gelangt, in der Regel auch in der Lage sein wird, Ihre Nachrichten zu lesen - unabhängig davon, ob Perfect Forward Secrecy nun verwendet wird oder nicht. <p>Delta Chat today doesn’t support Perfect Forward Secrecy (PFS).
Die typische, reale Situation für durchgesickerte private Schlüssel, ist die <a href="#device-seizure">Beschlagnahme von Geräten</a>.</p> This means that if your private decryption key is leaked,
and someone has collected your prior in-transit messages,
they will be able to decrypt and read them using the leaked decryption key.
Note that Forward Secrecy only increases security if you delete messages.
Otherwise, someone obtaining your decryption keys
is typically also able to get all your non-deleted messages
and doesn’t even need to decrypt any previously collected messages.</p>
<p>Es ist möglich, dass Delta Chat eine Tages “Perfect Forward Secrecy” unterstützt - <p>We designed a Forward Secrecy approach that withstood
OpenPGP ist nur ein Container für verschlüsselte Nachrichten mit dem initial examination from some cryptographers and implementation experts
die Verwaltung der Schlüssel (und damit die Schlüsselrotation oder das Schlüssel-“Ratcheting”) but is pending a more formal write up
auf flexible Weise organisiert werden kann. to ascertain it reliably works in federated messaging and with multi-device usage,
Siehe <a href="https://gitlab.com/sequoia-pgp/openpgp-dr">Seqouias PFS-Prototyp</a> before it could be implemented in <a href="https://github.com/chatmail/core">chatmail core</a>,
für bestehende Experimente in der OpenPGP-Community.</p> which would make it available in all <a href="https://chatmail.at/clients">chatmail clients</a>.</p>
<h3 id="ist-die-ende-zu-ende-verschlüsselung-von-delta-chat-genauso-sicher-wie-die-von-signal"> <h3 id="pqc">
Ist die Ende-zu-Ende-Verschlüsselung von Delta Chat genauso sicher wie die von Signal? <a href="#ist-die-ende-zu-ende-verschlüsselung-von-delta-chat-genauso-sicher-wie-die-von-signal" class="anchor"></a> Unterstützt Delta Chat Post-Quantum-Verschlüsselung? <a href="#pqc" class="anchor"></a>
</h3> </h3>
<p>Das hängt davon ab, was für Sie wichtig ist. <p>No, not yet.</p>
Delta Chat <a href="#pfs">unterstützt kein PFS</a>,
bietet aber <a href="#e2eeguarantee">garantierte Ende-zu-Ende-Verschlüsselung</a>,
die vor kompromittierten Servern oder korrupten Netzwerken schützt.
Signal und die meisten anderen PFS-unterstützenden Messenger bieten kein
praktisches System zum Schutz von Chatgruppen vor Netzwerkangriffen.
Diese sind besorgniserregender und realer
als ein potenzieller Angreifer, der zwar Ihr Telefon und Ihre privaten Schlüssel beschlagnahmt,
aber irgendwie nicht Ihre Nachrichten - gleichzeitig aber eine vollständige Aufzeichnung aller
vergangenen verschlüsselten Nachrichten hat.</p>
<p>In jedem Fall verwendet die Ende-zu-Ende-Verschlüsselung von Delta Chat eine <a href="#openpgp-secure">sichere Untermenge von OpenPGP</a> <p>Delta Chat uses the Rust OpenPGP library <a href="https://github.com/rpgp/rpgp">rPGP</a>
das <a href="https://delta.chat/assets/blog/2019-first-security-review.pdf">unabhängig sicherheitsgeprüft</a> wurde.</p> which supports the latest <a href="https://datatracker.ietf.org/doc/draft-ietf-openpgp-pqc/">IETF Post-Quantum-Cryptography OpenPGP draft</a>.
We aim to add PQC support in <a href="https://github.com/chatmail/core">chatmail core</a> after the draft is finalized at the IETF
in collaboration with other OpenPGP implementers.</p>
<h3 id="wie-kann-ich-die-verschlüsselung-manuell-überprüfen">
Wie kann ich die Verschlüsselung manuell überprüfen? <a href="#wie-kann-ich-die-verschlüsselung-manuell-überprüfen" class="anchor"></a>
</h3>
<p>Sie können den Status der Ende-zu-Ende-Verschlüsselung manuell im Dialog “Verschlüsselung”
(Android/iOS: Benutzerprofil, Desktop: Rechtsklick auf den Chat eines Benutzers) überprüfen.
Delta Chat zeigt dort zwei Fingerabdrücke an.
Wenn die gleichen Fingerabdrücke auf Ihrem eigenen Gerät und auf dem Gerät Ihres Kontakts erscheinen,
ist die Verbindung sicher.</p>
<h3 id="importkey"> <h3 id="importkey">
@ -1490,6 +1379,11 @@ forum</a> veröffentlicht und diskutiert.</li>
</h3> </h3>
<p>Note:
Changing email addresses is temporarily disabled
because of ongoing changes to the DeltaChat core.
It should be available again in a few months.</p>
<ol> <ol>
<li> <li>
<p>Ändern Sie Ihre E-Mail-Adresse unter “Einstellungen → Erweitert → Passwort und E-Mail-Konto” und <p>Ändern Sie Ihre E-Mail-Adresse unter “Einstellungen → Erweitert → Passwort und E-Mail-Konto” und
@ -1588,10 +1482,10 @@ gesendet haben, Nachrichten an Ihre neue Adresse senden.</p>
Allerdings benötigen einige Anbieter besondere Einstellungen, um ordnungsgemäß zu funktionieren; eine von NutzerInnen erstellte Sammlung zu einigen Optionen findet sich unter <a href="https://providers.delta.chat">Provider Overview</a>.</li> Allerdings benötigen einige Anbieter besondere Einstellungen, um ordnungsgemäß zu funktionieren; eine von NutzerInnen erstellte Sammlung zu einigen Optionen findet sich unter <a href="https://providers.delta.chat">Provider Overview</a>.</li>
</ul> </ul>
<h3 id="i-want-to-manage-my-own-server-for-delta-chat-what-do-you-recommend"> <h3 id="ich-möchte-meinen-eigenen-server-für-delta-chat-verwalten-gibt-es-empfehlungen">
I want to manage my own server for Delta Chat. What do you recommend? <a href="#i-want-to-manage-my-own-server-for-delta-chat-what-do-you-recommend" class="anchor"></a> Ich möchte meinen eigenen Server für Delta Chat verwalten. Gibt es Empfehlungen? <a href="#ich-möchte-meinen-eigenen-server-für-delta-chat-verwalten-gibt-es-empfehlungen" class="anchor"></a>
</h3> </h3>

BIN
src/main/assets/help/email-icon.png Normal file
View file

Binary file not shown.
Side by side

After

Width:  |  Height:  |  Size: 349 B

420
src/main/assets/help/en/help.html
View file

@ -36,27 +36,24 @@
<li><a href="#why-does-delta-chat-integrate-with-centralized-proprietary-applegoogle-push-services">Why does Delta Chat integrate with centralized proprietary Apple/Google push services?</a></li> <li><a href="#why-does-delta-chat-integrate-with-centralized-proprietary-applegoogle-push-services">Why does Delta Chat integrate with centralized proprietary Apple/Google push services?</a></li>
</ul> </ul>
</li> </li>
<li><a href="#encryption-and-security">Encryption and Security</a> <li><a href="#e2ee">Encryption and Security</a>
<ul> <ul>
<li><a href="#which-standards-are-used-for-end-to-end-encryption">Which standards are used for end-to-end encryption?</a></li> <li><a href="#which-standards-are-used-for-end-to-end-encryption">Which standards are used for end-to-end encryption?</a></li>
<li><a href="#whene2e">How can i know if messages are end-to-end encrypted?</a></li> <li><a href="#whene2e">How can i know if messages are end-to-end encrypted?</a></li>
<li><a href="#howtoe2ee">How can I get guaranteed end-to-end encryption and green checkmarks?</a></li> <li><a href="#can-i-still-receive-or-send-mails-without-end-to-end-encryption">Can i still receive or send mails without end-to-end encryption?</a></li>
<li><a href="#e2eeguarantee">What does the green checkmark and “guaranteed end-to-end encryption” mean?</a></li> <li><a href="#howtoe2ee">How can I establish a chat with a new contact?</a></li>
<li><a href="#nocryptanymore">A contact “sent a message from another device”, what can i do?</a></li> <li><a href="#e2eeguarantee">What does the green checkmark in a contact profile mean?</a></li>
<li><a href="#are-attachments-pictures-files-audio-etc-end-to-end-encrypted">Are attachments (pictures, files, audio etc.) end-to-end encrypted?</a></li> <li><a href="#are-attachments-pictures-files-audio-etc-end-to-end-encrypted">Are attachments (pictures, files, audio etc.) end-to-end encrypted?</a></li>
<li><a href="#openpgp-secure">Is OpenPGP secure?</a></li> <li><a href="#openpgp-secure">Is OpenPGP secure?</a></li>
<li><a href="#openpgp-alternatives">Did you consider using alternatives to OpenPGP for end-to-end -encryption?</a></li> <li><a href="#openpgp-alternatives">Did you consider using alternatives to OpenPGP for end-to-end-encryption?</a></li>
<li><a href="#is-delta-chat-vulnerable-to-efail">Is Delta Chat vulnerable to EFAIL?</a></li> <li><a href="#is-delta-chat-vulnerable-to-efail">Is Delta Chat vulnerable to EFAIL?</a></li>
<li><a href="#tls">Is a message exposed in cleartext if end-to-end encryption is not available?</a></li> <li><a href="#tls">Are messages marked with the mail icon exposed on the Internet?</a></li>
<li><a href="#message-metadata">How does Delta Chat protect metadata in messages?</a></li> <li><a href="#message-metadata">How does Delta Chat protect metadata in messages?</a></li>
<li><a href="#device-seizure">How to protect metadata and contacts when a device is seized?</a></li> <li><a href="#device-seizure">How to protect metadata and contacts when a device is seized?</a></li>
<li><a href="#how-can-i-check-encryption-information">How can i check encryption information?</a></li> <li><a href="#sealedsender">Does Delta Chat support “Sealed Sender”?</a></li>
<li><a href="#how-can-i-check-the-encryption-status-of-messages">How can I check the encryption status of messages?</a></li>
<li><a href="#why-do-i-see-unencrypted-messages">Why do I see unencrypted messages?</a></li>
<li><a href="#how-can-i-get-an-end-to-end-encrypted-chat-with-a-delta-chat-contact-who-sometimes-uses-webmail-or-another-non-autocrypt-e-mail-app">How can i get an end-to-end encrypted chat with a Delta Chat contact who sometimes uses webmail or another non-Autocrypt e-mail app?</a></li>
<li><a href="#how-can-i-ensure-message-end-to-end-encryption-and-deletion">How can I ensure message end-to-end encryption and deletion?</a></li>
<li><a href="#pfs">Does Delta Chat support Perfect Forward Secrecy?</a></li> <li><a href="#pfs">Does Delta Chat support Perfect Forward Secrecy?</a></li>
<li><a href="#is-end-to-end-encryption-of-delta-chat-as-safe-as-signal">Is end-to-end encryption of Delta Chat as safe as Signal?</a></li> <li><a href="#pqc">Does Delta Chat support Post-Quantum-Cryptography?</a></li>
<li><a href="#how-can-i-manually-check-encryption-information">How can I manually check encryption information?</a></li>
<li><a href="#importkey">Can I reuse my existing private key?</a></li> <li><a href="#importkey">Can I reuse my existing private key?</a></li>
<li><a href="#security-audits">Was Delta Chat independently audited for security vulnerabilities?</a></li> <li><a href="#security-audits">Was Delta Chat independently audited for security vulnerabilities?</a></li>
</ul> </ul>
@ -726,10 +723,10 @@ that achieves “instant delivery” of messages for all chatmail servers
including a potential one <a href="https://delta.chat/chatmail#selfhosted">you might setup yourself without our permission</a>. including a potential one <a href="https://delta.chat/chatmail#selfhosted">you might setup yourself without our permission</a>.
Welcome to the power of the interoperable and massive chatmail and e-mail system :)</p> Welcome to the power of the interoperable and massive chatmail and e-mail system :)</p>
<h2 id="encryption-and-security"> <h2 id="e2ee">
Encryption and Security <a href="#encryption-and-security" class="anchor"></a> Encryption and Security <a href="#e2ee" class="anchor"></a>
</h2> </h2>
@ -742,18 +739,26 @@ Welcome to the power of the interoperable and massive chatmail and e-mail system
</h3> </h3>
<p><a href="https://autocrypt.org">Autocrypt</a> is used for automatically <p>Delta Chat uses a <a href="#openpgp-secure">secure subset of the OpenPGP standard</a>
establishing end-to-end encryption with contacts and group chats. to provide automatic end-to-end encryption using these protocols:</p>
Autocrypt uses a limited and <a href="#openpgp-secure">secure subset of the OpenPGP standard</a>.
End-to-End encrypted messages are marked with a padlock
<img style="vertical-align:middle; width:1.2em; margin:1px" src="../lock-icon.png" alt="padlock" />.</p>
<p><a href="https://securejoin.delta.chat/en/latest/new.html">Secure-Join protocols</a> <ul>
are used for establishing chats with guaranteed end-to-end encryption <li>
which protects against network attacks and compromised servers. <p><a href="https://securejoin.delta.chat/en/latest/new.html">Secure-Join</a>
Chats marked with a green checkmark to exchange encryption setup information through QR-code scanning or “invite links”.</p>
<img style="vertical-align:middle; width:1.5em; margin:1px" src="../green-checkmark.png" alt="green checkmark" /> </li>
guarantee end-to-end encrypted messages.</p> <li>
<p><a href="https://autocrypt.org">Autocrypt</a> is used for automatically
establishing end-to-end encryption between contacts and all members of a group chat.</p>
</li>
<li>
<p><a href="https://github.com/chatmail/core/blob/main/spec.md#attaching-a-contact-to-a-message">Sharing a contact to a
chat</a>
enables receivers to use end-to-end encryption with the contact.</p>
</li>
</ul>
<p>Delta Chat does not query, publish or interact with any OpenPGP key servers.</p>
<h3 id="whene2e"> <h3 id="whene2e">
@ -763,28 +768,37 @@ guarantee end-to-end encrypted messages.</p>
</h3> </h3>
<p>All end-to-end encrypted messages carry a padlock:</p> <p>All messages in Delta Chat are <strong>end-to-end encrypted by default</strong>.
Since the Delta Chat Version 2 release series (July 2025)
there are no lock or similar markers on end-to-end encrypted messages, anymore.</p>
<p><img style="width:160px; margin:1px" src="../lock-screenshot.png" alt="padlock in bubble" /></p> <h3 id="can-i-still-receive-or-send-mails-without-end-to-end-encryption">
<p>End-to-end encryption is guaranteed if there is a green checkmark next to the chat title:</p>
<p><img style="width:211px; margin:1px" src="../green-checkmark-screenshot.png" alt="green checkmark in title" /></p>
<h3 id="howtoe2ee">
How can I get guaranteed end-to-end encryption and green checkmarks? <a href="#howtoe2ee" class="anchor"></a> Can i still receive or send mails without end-to-end encryption? <a href="#can-i-still-receive-or-send-mails-without-end-to-end-encryption" class="anchor"></a>
</h3> </h3>
<p>If you have a second communication channel with your chat partner, <p>If you use default <a href="https://chatmail.at/relays">chatmail relays</a>,
like a video chat or a different messenger, it is impossible to receive or send messages without end-to-end encryption.</p>
you can generate an invite link.</p>
<p>If you are together in person, <p>If you instead create a profile using a classic e-mail server,
you can show a QR code to your chat partner.</p> you can send and receive messages without end-to-end encryption.
Such messages lacking end-to-end encryption are marked with an e-mail icon
<img style="vertical-align:middle; width:1.2em; margin:1px" src="../email-icon.png" alt="email" />.</p>
<h3 id="howtoe2ee">
How can I establish a chat with a new contact? <a href="#howtoe2ee" class="anchor"></a>
</h3>
<p>You can send an invite link through another private chat,
show an invitation QR code when next to each other or in a video call,
or click on a “contact” that was shared in a chat.</p>
<ul> <ul>
<li> <li>
@ -799,135 +813,54 @@ on the Delta Chat app main screen.</p>
</li> </li>
</ul> </ul>
<p>Let your chat partner scan the QR image <p>Ask your chat partner to scan the QR image
with their Delta Chat app, with their Delta Chat app,
or click “Copy” or “Share” to create an invite link or click “Copy” or “Share” to create an invite link
and share it with your chat partner.</p> and share it with your chat partner.</p>
<p>Now wait while <a href="https://securejoin.delta.chat/en/latest/new.html#setup-contact-protocol">Secure-Join network messages are exchanged</a> between both devices.</p> <p>Now wait while <a href="https://securejoin.delta.chat/en/latest/new.html#setup-contact-protocol">end-to-end encryption is getting established</a>.</p>
<ul> <ul>
<li> <li>
<p>If both devices are online, <p>If both sides are online, they will soon see a (group or direct) chat
both sides will eventually see a (group or direct) chat with a green checkmark and can start messaging securely.</p>
<img style="vertical-align:middle; width:1.5em; margin:1px" src="../green-checkmark.png" alt="green checkmark" />
next to the title.</p>
</li> </li>
<li> <li>
<p>If one of the devices is offline, the green checkmarks will only <p>If one side is offline or in bad network,
appear later when the device is internet-connected again the ability to chat is delayed until connectivity is restored.</p>
and the Secure-Join network protocol completed.</p>
</li> </li>
</ul> </ul>
<p>Congratulations! <p>Congratulations!
You now will automatically use guaranteed end-to-end encryption You now will automatically use end-to-end encryption
with this contact and both of you can add each other to green-checkmarked groups with this contact.
<img style="vertical-align:middle; width:1.5em; margin:1px" src="../green-checkmark.png" alt="green checkmark" />, If you add each other to chat groups,
thereby automatically spreading guaranteed end-to-end encryption among its members.</p> end-to-end encryption will be established among all members.</p>
<h3 id="e2eeguarantee"> <h3 id="e2eeguarantee">
What does the green checkmark and “guaranteed end-to-end encryption” mean? <a href="#e2eeguarantee" class="anchor"></a> What does the green checkmark in a contact profile mean? <a href="#e2eeguarantee" class="anchor"></a>
</h3> </h3>
<p>Chat titles with green checkmarks <p>A contact profile might show a green checkmark
<img style="vertical-align:middle; width:1.5em; margin:1px" src="../green-checkmark.png" alt="green checkmark" /> <img style="vertical-align:middle; width:1.5em; margin:1px" src="../green-checkmark.png" alt="green checkmark" />
mean that all messages in the chat will be end-to-end encrypted and an “Introduced by” line.
and can not be read or altered by compromised e-mail servers or Internet providers.
Joining green-checkmarked group chats
safely spreads everybody’s encryption information (and green checkmarks)
in a manner that guarantees end-to-end encryption in the group and among members.</p>
<p>Contact profiles with green checkmarks
<img style="vertical-align:middle; width:1.5em; margin:1px" src="../green-checkmark.png" alt="green checkmark" />
mean that messaging a contact is currently guaranteed to be end-to-end encrypted.
Every green-checkmarked contact either did a direct <a href="#howtoe2ee">QR-scan</a> with you Every green-checkmarked contact either did a direct <a href="#howtoe2ee">QR-scan</a> with you
or was introduced by a another green-checkmarked contact. or was introduced by a another green-checkmarked contact.
Introductions happen automatically when adding members to groups. Introductions happen automatically when adding members to groups.
Whoever adds a contact to a green-checkmarked group becomes an introducer Whoever adds a green-checkmarked contact to a group with only green-checkmarked members
to those members who didn’t yet know about the added contact. becomes an introducer.
In a contact profile you can tap on the “Introduced by …” text repeatedly In a contact profile you can tap on the “Introduced by …” text repeatedly
until you get to the one with whom you directly did a <a href="#howtoe2ee">QR-scan</a>.</p> until you get to the one with whom you directly did a <a href="#howtoe2ee">QR-scan</a>.</p>
<p>Note that in a contact profile you may see and tap introducers
but there is no green checkmark in the profile title.
This usually means that the contact <a href="#nocryptanymore">“sent a message from another device”</a>.</p>
<p>For more in-depth discussion of “guaranteed end-to-end encryption” <p>For more in-depth discussion of “guaranteed end-to-end encryption”
please see <a href="https://securejoin.delta.chat/en/latest/new.html">Secure-Join protocols</a> please see <a href="https://securejoin.delta.chat/en/latest/new.html">Secure-Join protocols</a>
and specifically read about “Verified Groups”, the technical term and specifically read about “Verified Groups”, the technical term
of what is called here “green-checkmarked” or “guaranteed end-to-end encrypted” chats.</p> of what is called here “green-checkmarked” or “guaranteed end-to-end encrypted” chats.</p>
<h3 id="nocryptanymore">
A contact “sent a message from another device”, what can i do? <a href="#nocryptanymore" class="anchor"></a>
</h3>
<p>Your chat with a contact lost guaranteed end-to-end encryption.
The green checkmark was removed for this chat and contact when you see this warning.
<strong>If you find the sudden drop of guaranteed end-to-end encryption
surprising for this contact then don’t accept the warning!</strong>
Instead check with your contact through a second channel
like a video call, other messenger or a phone call,
to find out what happened.</p>
<p>If your contact actually caused the drop of guaranteed end-to-end encryption
please see the next paragraphs for common reasons and their mitigations.
Regardless, all other green-checkmarked chats remain guaranteed end-to-end encrypted
even if the contact is a member there.</p>
<p><strong>Your contact is using Delta Chat on a second device (phone or laptop)</strong></p>
<p>If they have another device with a Delta Chat app running,
they should remove the profile from the new device
and add it <a href="#multiclient">as a second device as described here</a>.
As soon as they message you afterwards, the warning will be gone
and guaranteed encryption is established with both devices of your contact.</p>
<p><strong>Your contact reinstalled Delta Chat using their old account login</strong></p>
<p>If they have <a href="#backup">a backup file</a>,
they should remove the profile from the new device
and rather import the backup file to re-create their profile.
As soon as they message you afterwards, the warning will be gone
and guaranteed encryption is re-established for this contact.</p>
<p>If they don’t have a backup file, it’s best to perform a <a href="#howtoe2ee">QR scan</a>
with your chat partner to re-establish guaranteed end-to-end encryption.</p>
<p><strong>Your contact sent a mail through a webmail interface or another e-mail app
and will get back to using Delta Chat soon again.</strong></p>
<p>If you are sure that the contact sometimes uses webmail,
or another mail app lacking end-to-end encryption,
then you may accept the warning.
As soon as your contact uses Delta Chat again,
guaranteed end-to-end encryption will be automatically re-established.</p>
<p><strong>Your contact stopped using Delta Chat entirely</strong></p>
<p>Sometimes remaining in contact is more important than end-to-end encryption.
<a href="#tls">“Transport Layer Encryption” (TLS)</a> may still meaningfully protect
the confidentiality of your messages between your device and the e-mail server.
But without end-to-end encryption you and your contact are trusting your e-mail server
to not read or manipulate your messages, and to not hand them to third parties.</p>
<p>In any case, you can not do much else than accept the warning.
Please also remove the contact from any active green-checkmarked group
which you can find in “Chats in Common” in the Contact profile.
This spares your contact from getting “unreadable” messages.</p>
<p>If the contact removed Delta Chat because of buggy or undesirable behaviour,
please consider posting to our <a href="https://support.delta.chat">support forum</a>
to help us identify and address common problems. Thanks!</p>
<h3 id="are-attachments-pictures-files-audio-etc-end-to-end-encrypted"> <h3 id="are-attachments-pictures-files-audio-etc-end-to-end-encrypted">
@ -952,8 +885,7 @@ and attachment metadata such as filenames.</p>
</h3> </h3>
<p>Yes, Delta Chat uses a secure subset of OpenPGP <p>Yes, Delta Chat uses a secure subset of OpenPGP
and only displays a padlock security indicator on a message requiring the whole message to be properly encrypted and signed.
if the whole message is properly encrypted and signed.
For example, “Detached signatures” are not treated as secure.</p> For example, “Detached signatures” are not treated as secure.</p>
<p>OpenPGP is not insecure by itself. <p>OpenPGP is not insecure by itself.
@ -974,7 +906,7 @@ which was thankfully adopted in summer 2023.</p>
<h3 id="openpgp-alternatives"> <h3 id="openpgp-alternatives">
Did you consider using alternatives to OpenPGP for end-to-end -encryption? <a href="#openpgp-alternatives" class="anchor"></a> Did you consider using alternatives to OpenPGP for end-to-end-encryption? <a href="#openpgp-alternatives" class="anchor"></a>
</h3> </h3>
@ -1017,17 +949,15 @@ as defined by the Autocrypt Level 1 specification.</p>
<h3 id="tls"> <h3 id="tls">
Is a message exposed in cleartext if end-to-end encryption is not available? <a href="#tls" class="anchor"></a> Are messages marked with the mail icon exposed on the Internet? <a href="#tls" class="anchor"></a>
</h3> </h3>
<p>Even if your messages are not guaranteed to be end-to-end encrypted, <p>If you are sending or receiving e-mail messages without end-to-end encryption (using a classic e-mail server),
they are still protected from Internet providers like cell or cable companies. they are still protected from cell or cable companies who can not read or modify your e-mail messages.
However, your and your recipient’s e-mail providers But both your and your recipient’s e-mail providers
may read, analyze or even modify your messages, may read, analyze or modify your messages, including any attachments.</p>
including any attachments,
if they are not end-to-end encrypted.</p>
<p>Delta Chat by default uses strict <p>Delta Chat by default uses strict
<a href="https://en.wikipedia.org/wiki/Transport_Layer_Security">TLS encryption</a> <a href="https://en.wikipedia.org/wiki/Transport_Layer_Security">TLS encryption</a>
@ -1040,10 +970,6 @@ then transport encryption will be enforced between e-mail providers
in which case Delta Chat communications will never be exposed in cleartext to the Internet in which case Delta Chat communications will never be exposed in cleartext to the Internet
even if the message was not end-to-end encrypted.</p> even if the message was not end-to-end encrypted.</p>
<p>Note that <a href="#howtoe2ee">maintaining guaranteed end-to-end encryption</a> on top of TLS encryption
provides pervasive safety between your and the recipient’s devices.
Not even your e-mail or Internet provider will be able to read or modify your messages.</p>
<h3 id="message-metadata"> <h3 id="message-metadata">
@ -1052,25 +978,25 @@ Not even your e-mail or Internet provider will be able to read or modify your me
</h3> </h3>
<p>Delta Chat protects most message metadata by putting the following information <p>Unlike most other messengers,
into the end-to-end encrypted part of messages:</p> Delta Chat apps do not store any metadata about contacts or groups on servers, also not in encrypted form.
Instead, all group metadata is end-to-end encrypted and stored on end-user devices, only.</p>
<p>E-mail Servers can therefore only see</p>
<ul> <ul>
<li>Subject line</li> <li>
<li>Group avatar and name</li> <p>the message date,</p>
<li>MDN (read receipt) requests (<code class="language-plaintext highlighter-rouge">Chat-Disposition-Notification-To</code>)</li> </li>
<li>Disappearing message timer (<code class="language-plaintext highlighter-rouge">Ephemeral-Timer</code>)</li> <li>
<li><code class="language-plaintext highlighter-rouge">Chat-Group-Member-Removed</code>, <code class="language-plaintext highlighter-rouge">Chat-Group-Member-Added</code></li> <p>sender and receiver addresses</p>
<li><code class="language-plaintext highlighter-rouge">Secure-Join</code> header containing secure join commands</li> </li>
<li>Notification about enabling location streaming</li> <li>
<li>WebRTC room URL</li> <p>and message size.</p>
</li>
</ul> </ul>
<p>E-Mail servers do not get access to this protected metadata <p>All other message, contact and group metadata resides in the end-to-end encrypted part of messages.</p>
but they do see the message date as well as the message size,
and, more importantly, the sender and receiver addresses.
E-mail servers need receiver addresses to route and
deliver messages to recipient’s devices.</p>
<h3 id="device-seizure"> <h3 id="device-seizure">
@ -1082,96 +1008,34 @@ deliver messages to recipient’s devices.</p>
<p>Both for protecting against metadata-collecting e-mail servers <p>Both for protecting against metadata-collecting e-mail servers
as well as against the threat of device seizure as well as against the threat of device seizure
we recommend to use a <a href="https://delta.chat/chatmail">chatmail server</a> we recommend to use a <a href="https://chatmail.at/relays">chatmail relay</a>
to create pseudonymous temporary profiles through QR-code scans. to create chat profiles using random e-mail addresses for transport.
Note that Delta Chat apps on all platforms support multiple profiles Note that Delta Chat apps on all platforms support multiple profiles
so you can easily use situation-specific profiles next to your “main” profile so you can easily use situation-specific profiles next to your “main” profile
with the knowledge that all their data, along with all metadata, will be deleted. with the knowledge that all their data, along with all metadata, will be deleted.
Moreover, if a device is seized then contacts using temporary profiles Moreover, if a device is seized then chat contacts using short-lived profiles
can not be identified easily, as compared to messengers which reveal can not be identified easily.</p>
phone numbers in chat groups which in turn are often associated with legal identities.</p>
<h3 id="how-can-i-check-encryption-information"> <h3 id="sealedsender">
How can i check encryption information? <a href="#how-can-i-check-encryption-information" class="anchor"></a> Does Delta Chat support “Sealed Sender”? <a href="#sealedsender" class="anchor"></a>
</h3> </h3>
<p>You may check the end-to-end encryption status manually in the “Encryption” dialog <p>No, not yet.</p>
(user profile on Android/iOS or right-click a user’s chat-list item on desktop).
Delta Chat shows two fingerprints there.
If the same fingerprints appear on your own and your contact’s device,
the connection is safe.</p>
<h3 id="how-can-i-check-the-encryption-status-of-messages"> <p>The Signal messenger introduced <a href="https://signal.org/blog/sealed-sender/">“Sealed Sender” in 2018</a>
to keep their server infrastructure ignorant of who is sending a message to a set of recipients.
It is particularly important because the Signal server knows the mobile number of each account,
which is usually associated with a passport identity.</p>
<p>Even if <a href="https://chatmail.at/relays">chatmail relays</a>
How can I check the encryption status of messages? <a href="#how-can-i-check-the-encryption-status-of-messages" class="anchor"></a> do not ask for any private data (including no phone numbers),
it might still be worthwhile to protect relational metadata between addresses.
We don’t foresee bigger problems in using random throw-away e-mail addresses for sealed sending
</h3> but an implementation has not been agreed as a priority yet.</p>
<p>A little <strong>padlock</strong> in a message bubble denotes
that the message was properly end-to-end encrypted from the given sender.
If there is <strong>no padlock</strong>, the message was not properly end-to-end encrypted
most likely because the sender uses an app or webmail interface
without support for end-to-end–encryption.</p>
<h3 id="why-do-i-see-unencrypted-messages">
Why do I see unencrypted messages? <a href="#why-do-i-see-unencrypted-messages" class="anchor"></a>
</h3>
<p>If a contact uses a non-Autocrypt e-mail app,
all messages involving this contact (in a group or 1:1 chat)
will not be end-to-end encrypted, and thus not show a “padlock” with messages.
Note that even if your contacts use Delta Chat on their account,
they might also use a non-Autocrypt e-mail app on that account
which then may cause intermittently unencrypted messages.
Replying unencrypted to unencrypted messages is mandated by Autocrypt
to prevent unreadable messages on the side of your contacts
and their non-Autocrypt e-mail app.</p>
<h3 id="how-can-i-get-an-end-to-end-encrypted-chat-with-a-delta-chat-contact-who-sometimes-uses-webmail-or-another-non-autocrypt-e-mail-app">
How can i get an end-to-end encrypted chat with a Delta Chat contact who sometimes uses webmail or another non-Autocrypt e-mail app? <a href="#how-can-i-get-an-end-to-end-encrypted-chat-with-a-delta-chat-contact-who-sometimes-uses-webmail-or-another-non-autocrypt-e-mail-app" class="anchor"></a>
</h3>
<p>If you need a safely end-to-end encrypted chat with a contact
who is using their e-mail account both with Delta Chat and non-Autocrypt apps (e.g. webmail),
it’s best to setup <a href="#howtoe2ee">guaranteed end-to-end encryption with them</a>
and then create a guaranteed end-to-end encrypted group chat with you two as members.
In this group chat all messages will be end-to-end encrypted
even if the direct chat between you two has a
<a href="#nocryptanymore">“… sent a message from another device”</a> warning.</p>
<h3 id="how-can-i-ensure-message-end-to-end-encryption-and-deletion">
How can I ensure message end-to-end encryption and deletion? <a href="#how-can-i-ensure-message-end-to-end-encryption-and-deletion" class="anchor"></a>
</h3>
<p>The best way to ensure every message is end-to-end encrypted,
and metadata deleted as quickly as possible
is <a href="#howtoe2ee">using chats with guaranteed end-to-end encryption</a>
and turning on <a href="#ephemeralmsgs">disappearing messages</a>.</p>
<p>Guaranteed end-to-end encrypted chats protect against <a href="https://en.wikipedia.org/wiki/Man-in-the-middle_attack">MITM attacks</a>
and turning on disappearing messages deletes the messages
on the server after a user-configured time.</p>
<p>If you don’t need a longer-lived copy of your messages on the server,
you can also turn on <a href="#delold">“delete messages from server automatically”</a>.</p>
<h3 id="pfs"> <h3 id="pfs">
@ -1181,45 +1045,52 @@ you can also turn on <a href="#delold">“delete messages from server automatica
</h3> </h3>
<p>No, Delta Chat doesn’t support Perfect Forward Secrecy (PFS). <p>No, not yet.</p>
This means that if your Delta Chat private decryption key is leaked,
<p>Delta Chat today doesn’t support Perfect Forward Secrecy (PFS).
This means that if your private decryption key is leaked,
and someone has collected your prior in-transit messages, and someone has collected your prior in-transit messages,
they will be able to decrypt and read them using the leaked decryption key.</p> they will be able to decrypt and read them using the leaked decryption key.
Note that Forward Secrecy only increases security if you delete messages.
Otherwise, someone obtaining your decryption keys
is typically also able to get all your non-deleted messages
and doesn’t even need to decrypt any previously collected messages.</p>
<p>Note, however, that if anyone obtains to your decryption keys, <p>We designed a Forward Secrecy approach that withstood
they will typically also be able to obtain your messages, initial examination from some cryptographers and implementation experts
irrespective if Perfect Forward Secrecy is in place or not. but is pending a more formal write up
The typical real-world situation for leaked decryption keys is device seizure to ascertain it reliably works in federated messaging and with multi-device usage,
which we discuss in our answer <a href="#device-seizure">on metadata and device seizure</a>.</p> before it could be implemented in <a href="https://github.com/chatmail/core">chatmail core</a>,
which would make it available in all <a href="https://chatmail.at/clients">chatmail clients</a>.</p>
<p>It is possible that Delta Chat evolves to support Perfect Forward Secrecy, <h3 id="pqc">
because OpenPGP is just a container for encrypted messages
but encryption key management (and thus key rotation or key “ratcheting”)
could be organized in flexible ways.
See <a href="https://gitlab.com/sequoia-pgp/openpgp-dr">Seqouia’s PFS prototype</a>
for existing experiments in the OpenPGP implementor community.</p>
<h3 id="is-end-to-end-encryption-of-delta-chat-as-safe-as-signal">
Is end-to-end encryption of Delta Chat as safe as Signal? <a href="#is-end-to-end-encryption-of-delta-chat-as-safe-as-signal" class="anchor"></a> Does Delta Chat support Post-Quantum-Cryptography? <a href="#pqc" class="anchor"></a>
</h3> </h3>
<p>It depends on what is important to you. <p>No, not yet.</p>
Delta Chat <a href="#pfs">does not support PFS</a> like Signal does
but it provides <a href="#e2eeguarantee">guaranteed end-to-end encrypted chats</a>
that are safe against compromised servers or corrupted networks.
Signal and most other PFS-supporting messengers do not provide
a practical scheme for protecting chat groups from network attacks
which are arguably more worrisome
than a potential attacker who seizes your phone and private encryption setup
but somehow not your messages, yet has a full record of all
past encrypted messages.</p>
<p>In any case, Delta Chat’s end-to-end encryption uses a <a href="#openpgp-secure">secure subset of OpenPGP</a> <p>Delta Chat uses the Rust OpenPGP library <a href="https://github.com/rpgp/rpgp">rPGP</a>
which has been <a href="https://delta.chat/assets/blog/2019-first-security-review.pdf">independently security-audited</a>.</p> which supports the latest <a href="https://datatracker.ietf.org/doc/draft-ietf-openpgp-pqc/">IETF Post-Quantum-Cryptography OpenPGP draft</a>.
We aim to add PQC support in <a href="https://github.com/chatmail/core">chatmail core</a> after the draft is finalized at the IETF
in collaboration with other OpenPGP implementers.</p>
<h3 id="how-can-i-manually-check-encryption-information">
How can I manually check encryption information? <a href="#how-can-i-manually-check-encryption-information" class="anchor"></a>
</h3>
<p>You may check the end-to-end encryption status manually in the “Encryption” dialog
(user profile on Android/iOS or right-click a user’s chat-list item on desktop).
Delta Chat shows two fingerprints there.
If the same fingerprints appear on your own and your contact’s device,
the connection is safe.</p>
<h3 id="importkey"> <h3 id="importkey">
@ -1254,7 +1125,7 @@ from most recent to older:</p>
<li> <li>
<p>2024 December, an <a href="https://github.com/rpgp/docs/blob/main/audits/NGI%20Core%20rPGP%20penetration%20test%20report%202024%201.0.pdf">NLNET-commissioned Evaluation of <p>2024 December, an <a href="https://github.com/rpgp/docs/blob/main/audits/NGI%20Core%20rPGP%20penetration%20test%20report%202024%201.0.pdf">NLNET-commissioned Evaluation of
rPGP</a> by <a href="https://www.radicallyopensecurity.com/">Radically Open Security</a> took place. rPGP</a> by <a href="https://www.radicallyopensecurity.com/">Radically Open Security</a> took place.
rPGP serves as the end-to-end encyption <a href="https://openpgp.org">OpenPGP</a> engine of Delta Chat. rPGP serves as the end-to-end encryption <a href="https://openpgp.org">OpenPGP</a> engine of Delta Chat.
Two advisories were released related to the findings of this audit:</p> Two advisories were released related to the findings of this audit:</p>
<ul> <ul>
@ -1648,6 +1519,11 @@ would be done by the Delta Chat app.</p>
</h3> </h3>
<p>Note:
Changing email addresses is temporarily disabled
because of ongoing changes to the DeltaChat core.
It should be available again in a few months.</p>
<ol> <ol>
<li> <li>
<p>Change your address in “Settings → Advanced → Password and Account” and <p>Change your address in “Settings → Advanced → Password and Account” and

416
src/main/assets/help/es/help.html
View file

@ -6,7 +6,7 @@
<li><a href="#cuáles-son-las-ventajas-de-delta-chat-comparado-con-otras-aplicaciones-de-mensajería">¿Cuáles son las ventajas de Delta Chat comparado con otras aplicaciones de mensajería?</a></li> <li><a href="#cuáles-son-las-ventajas-de-delta-chat-comparado-con-otras-aplicaciones-de-mensajería">¿Cuáles son las ventajas de Delta Chat comparado con otras aplicaciones de mensajería?</a></li>
<li><a href="#qué-pasa-si-espero-un-mensaje-de-alguien-a-quien-no-le-escribí-en-el-pasado">¿Qué pasa si espero un mensaje de alguien a quien no le escribí en el pasado?</a></li> <li><a href="#qué-pasa-si-espero-un-mensaje-de-alguien-a-quien-no-le-escribí-en-el-pasado">¿Qué pasa si espero un mensaje de alguien a quien no le escribí en el pasado?</a></li>
<li><a href="#delta-chat-soporta-envío-de-imágenes-videos-documentos-y-otros-archivos">¿Delta Chat soporta envío de imágenes, videos, documentos y otros archivos?</a></li> <li><a href="#delta-chat-soporta-envío-de-imágenes-videos-documentos-y-otros-archivos">¿Delta Chat soporta envío de imágenes, videos, documentos y otros archivos?</a></li>
<li><a href="#multiple-accounts">What are profiles? How can I switch between them?</a></li> <li><a href="#multiple-accounts">¿Qué son los perfiles? ¿Cómo puedo cambiar entre ellos?</a></li>
<li><a href="#quién-ve-mi-foto-de-perfil">¿Quién ve mi foto de perfil?</a></li> <li><a href="#quién-ve-mi-foto-de-perfil">¿Quién ve mi foto de perfil?</a></li>
<li><a href="#signature">¿Puedo establecer un texto de firma con Delta Chat?</a></li> <li><a href="#signature">¿Puedo establecer un texto de firma con Delta Chat?</a></li>
<li><a href="#qué-significa-fijar-mutear-archivar">¿Qué significa fijar, mutear, archivar?</a></li> <li><a href="#qué-significa-fijar-mutear-archivar">¿Qué significa fijar, mutear, archivar?</a></li>
@ -36,27 +36,24 @@
<li><a href="#why-does-delta-chat-integrate-with-centralized-proprietary-applegoogle-push-services">Why does Delta Chat integrate with centralized proprietary Apple/Google push services?</a></li> <li><a href="#why-does-delta-chat-integrate-with-centralized-proprietary-applegoogle-push-services">Why does Delta Chat integrate with centralized proprietary Apple/Google push services?</a></li>
</ul> </ul>
</li> </li>
<li><a href="#cifrado-y-seguridad">Cifrado y seguridad</a> <li><a href="#e2ee">Cifrado y seguridad</a>
<ul> <ul>
<li><a href="#qué-estándares-se-utilizan-para-el-cifrado-de-extremo-a-extremo">¿Qué estándares se utilizan para el cifrado de extremo a extremo?</a></li> <li><a href="#qué-estándares-se-utilizan-para-el-cifrado-de-extremo-a-extremo">¿Qué estándares se utilizan para el cifrado de extremo a extremo?</a></li>
<li><a href="#whene2e">¿Cómo puedo saber si los mensajes están cifrados de extremo a extremo?</a></li> <li><a href="#whene2e">¿Cómo puedo saber si los mensajes están cifrados de extremo a extremo?</a></li>
<li><a href="#howtoe2ee">¿Cómo puedo obtener cifrado de extremo a extremo garantizado y estampillas verdes?</a></li> <li><a href="#can-i-still-receive-or-send-mails-without-end-to-end-encryption">Can i still receive or send mails without end-to-end encryption?</a></li>
<li><a href="#e2eeguarantee">¿Qué significa la estampilla verde y “cifrado de extremo a extremo garantizado”?</a></li> <li><a href="#howtoe2ee">How can I establish a chat with a new contact?</a></li>
<li><a href="#nocryptanymore">Un contacto “envió un mensaje desde otro dispositivo”, ¿qué puedo hacer?</a></li> <li><a href="#e2eeguarantee">What does the green checkmark in a contact profile mean?</a></li>
<li><a href="#los-adjuntos-imágenes-archivos-audio-etc-están-cifrados-de-extremo-a-extremo">¿Los adjuntos (imágenes, archivos, audio, etc.) están cifrados de extremo a extremo?</a></li> <li><a href="#los-adjuntos-imágenes-archivos-audio-etc-están-cifrados-de-extremo-a-extremo">¿Los adjuntos (imágenes, archivos, audio, etc.) están cifrados de extremo a extremo?</a></li>
<li><a href="#openpgp-secure">¿Es OpenPGP seguro?</a></li> <li><a href="#openpgp-secure">¿Es OpenPGP seguro?</a></li>
<li><a href="#openpgp-alternatives">¿Consideraron usar alternativas a OpenPGP para el cifrado de extremo a extremo?</a></li> <li><a href="#openpgp-alternatives">Did you consider using alternatives to OpenPGP for end-to-end-encryption?</a></li>
<li><a href="#es-delta-chat-vulnerable-a-efail">¿Es Delta Chat vulnerable a EFAIL?</a></li> <li><a href="#es-delta-chat-vulnerable-a-efail">¿Es Delta Chat vulnerable a EFAIL?</a></li>
<li><a href="#tls">¿Se expone un mensaje en texto claro si no está disponible el cifrado de extremo a extremo?</a></li> <li><a href="#tls">Are messages marked with the mail icon exposed on the Internet?</a></li>
<li><a href="#message-metadata">¿Cómo Delta Chat protege los metadatos en los mensajes?</a></li> <li><a href="#message-metadata">¿Cómo Delta Chat protege los metadatos en los mensajes?</a></li>
<li><a href="#device-seizure">¿Cómo proteger los metadatos y los contactos cuando se incauta un dispositivo?</a></li> <li><a href="#device-seizure">¿Cómo proteger los metadatos y los contactos cuando se incauta un dispositivo?</a></li>
<li><a href="#cómo-puedo-verificar-la-información-de-cifrado">¿Cómo puedo verificar la información de cifrado?</a></li> <li><a href="#sealedsender">Does Delta Chat support “Sealed Sender”?</a></li>
<li><a href="#cómo-puedo-verificar-el-estado-de-cifrado-de-los-mensajes">¿Cómo puedo verificar el estado de cifrado de los mensajes?</a></li>
<li><a href="#por-qué-veo-mensajes-sin-cifrar">¿Por qué veo mensajes sin cifrar?</a></li>
<li><a href="#cómo-puedo-obtener-un-chat-cifrado-de-extremo-a-extremo-con-un-contacto-de-delta-chat-que-a-veces-utiliza-webmail-u-otra-aplicación-de-correo-electrónico-no-autocrypt">¿Cómo puedo obtener un chat cifrado de extremo a extremo con un contacto de Delta Chat que a veces utiliza webmail u otra aplicación de correo electrónico no Autocrypt?</a></li>
<li><a href="#cómo-puedo-asegurar-el-cifrado-de-extremo-a-extremo-y-la-eliminación-de-mensajes">¿Cómo puedo asegurar el cifrado de extremo a extremo y la eliminación de mensajes?</a></li>
<li><a href="#pfs">¿Soporta Delta Chat Perfect Forward Secrecy?</a></li> <li><a href="#pfs">¿Soporta Delta Chat Perfect Forward Secrecy?</a></li>
<li><a href="#es-el-cifrado-de-extremo-a-extremo-de-delta-chat-tan-seguro-como-el-de-signal">¿Es el cifrado de extremo a extremo de Delta Chat tan seguro como el de Signal?</a></li> <li><a href="#pqc">Does Delta Chat support Post-Quantum-Cryptography?</a></li>
<li><a href="#how-can-i-manually-check-encryption-information">How can I manually check encryption information?</a></li>
<li><a href="#importkey">¿Puedo reutilizar mi clave privada existente?</a></li> <li><a href="#importkey">¿Puedo reutilizar mi clave privada existente?</a></li>
<li><a href="#security-audits">¿Se auditó Delta Chat de forma independiente en busca de vulnerabilidades de seguridad?</a></li> <li><a href="#security-audits">¿Se auditó Delta Chat de forma independiente en busca de vulnerabilidades de seguridad?</a></li>
</ul> </ul>
@ -154,8 +151,8 @@ aunque el destinatario no utilice Delta Chat.</p>
</h3> </h3>
<ul> <ul>
<li>Anonymous chat profiles with fast, secure and interoperable <a href="https://delta.chat/chatmail">chatmail servers</a> <li>Perfiles de chat anónimos con <a href="https://delta.chat/chatmail">servidores de chatmail</a> rápidos, seguros e interoperables
which offer instant Push Notifications for iOS and Android devices.</li> que ofrecen notificaciones Push instantáneas para dispositivos con iOS y Android.</li>
</ul> </ul>
<p>Soporte omnipresente, <a href="#multiple-accounts">múltiples perfiles</a> y múltiples dispositivos en todas las plataformas. </p> <p>Soporte omnipresente, <a href="#multiple-accounts">múltiples perfiles</a> y múltiples dispositivos en todas las plataformas. </p>
@ -166,9 +163,9 @@ which offer instant Push Notifications for iOS and Android devices.</li>
seguro contra ataques a la red y al servidor.</p> seguro contra ataques a la red y al servidor.</p>
<ul> <ul>
<li>Free and Open Source software, both app and server side. <li>Software libre y de código abierto, tanto para aplicaciones como para servidores.
Built on <a href="https://github.com/chatmail/core/blob/main/standards.md#standards-used-in-delta-chat">E-mail and Web Internet Standards</a>, Basado en <a href="https://github.com/chatmail/core/blob/main/standards.md#standards-used-in-delta-chat">Estándares de Internet para correo electrónico y web</a>,
<a href="https://xkcd.com/927/">to avoid “yet another standard syndrome (xkcd 927)”</a></li> <a href="https://xkcd.com/927/">para evitar el “síndrome de otro estándar más (xkcd 927)”</a></li>
</ul> </ul>
<h3 id="qué-pasa-si-espero-un-mensaje-de-alguien-a-quien-no-le-escribí-en-el-pasado"> <h3 id="qué-pasa-si-espero-un-mensaje-de-alguien-a-quien-no-le-escribí-en-el-pasado">
@ -213,7 +210,7 @@ Built on <a href="https://github.com/chatmail/core/blob/main/standards.md#standa
<h3 id="multiple-accounts"> <h3 id="multiple-accounts">
What are profiles? How can I switch between them? <a href="#multiple-accounts" class="anchor"></a> ¿Qué son los perfiles? ¿Cómo puedo cambiar entre ellos? <a href="#multiple-accounts" class="anchor"></a>
</h3> </h3>
@ -718,10 +715,10 @@ that achieves “instant delivery” of messages for all chatmail servers
including a potential one <a href="https://delta.chat/chatmail#selfhosted">you might setup yourself without our permission</a>. including a potential one <a href="https://delta.chat/chatmail#selfhosted">you might setup yourself without our permission</a>.
Welcome to the power of the interoperable and massive chatmail and e-mail system :)</p> Welcome to the power of the interoperable and massive chatmail and e-mail system :)</p>
<h2 id="cifrado-y-seguridad"> <h2 id="e2ee">
Cifrado y seguridad <a href="#cifrado-y-seguridad" class="anchor"></a> Cifrado y seguridad <a href="#e2ee" class="anchor"></a>
</h2> </h2>
@ -734,18 +731,26 @@ Welcome to the power of the interoperable and massive chatmail and e-mail system
</h3> </h3>
<p><a href="https://autocrypt.org">Autocrypt</a> is used for automatically <p>Delta Chat uses a <a href="#openpgp-secure">secure subset of the OpenPGP standard</a>
establishing end-to-end encryption with contacts and group chats. to provide automatic end-to-end encryption using these protocols:</p>
Autocrypt uses a limited and <a href="#openpgp-secure">secure subset of the OpenPGP standard</a>.
End-to-End encrypted messages are marked with a padlock
<img style="vertical-align:middle; width:1.2em; margin:1px" src="../lock-icon.png" alt="padlock" />.</p>
<p><a href="https://securejoin.delta.chat/en/latest/new.html">Protocolos de Secure-Join</a> <ul>
se utilizan para establecer chats con cifrado de extremo a extremo garantizado <li>
que protege contra ataques de red y servidores comprometidos. <p><a href="https://securejoin.delta.chat/en/latest/new.html">Secure-Join</a>
Los chats marcados con una estampilla verde to exchange encryption setup information through QR-code scanning or “invite links”.</p>
<img style="vertical-align:middle; width:1.5em; margin:1px" src="../green-checkmark.png" alt="green checkmark" /> </li>
garantizan mensajes cifrados de extremo a extremo.</p> <li>
<p><a href="https://autocrypt.org">Autocrypt</a> is used for automatically
establishing end-to-end encryption between contacts and all members of a group chat.</p>
</li>
<li>
<p><a href="https://github.com/chatmail/core/blob/main/spec.md#attaching-a-contact-to-a-message">Sharing a contact to a
chat</a>
enables receivers to use end-to-end encryption with the contact.</p>
</li>
</ul>
<p>Delta Chat does not query, publish or interact with any OpenPGP key servers.</p>
<h3 id="whene2e"> <h3 id="whene2e">
@ -755,28 +760,37 @@ garantizan mensajes cifrados de extremo a extremo.</p>
</h3> </h3>
<p>Todos los mensajes cifrados de extremo a extremo tienen un candado:</p> <p>All messages in Delta Chat are <strong>end-to-end encrypted by default</strong>.
Since the Delta Chat Version 2 release series (July 2025)
there are no lock or similar markers on end-to-end encrypted messages, anymore.</p>
<p><img style="width:160px; margin:1px" src="../lock-screenshot.png" alt="padlock in bubble" /></p> <h3 id="can-i-still-receive-or-send-mails-without-end-to-end-encryption">
<p>El cifrado de extremo a extremo está garantizado si hay una estampilla verde cerca del nombre del chat:</p>
<p><img style="width:211px; margin:1px" src="../green-checkmark-screenshot.png" alt="green checkmark in title" /></p>
<h3 id="howtoe2ee">
¿Cómo puedo obtener cifrado de extremo a extremo garantizado y estampillas verdes? <a href="#howtoe2ee" class="anchor"></a> Can i still receive or send mails without end-to-end encryption? <a href="#can-i-still-receive-or-send-mails-without-end-to-end-encryption" class="anchor"></a>
</h3> </h3>
<p>If you have a second communication channel with your chat partner, <p>If you use default <a href="https://chatmail.at/relays">chatmail relays</a>,
like a video chat or a different messenger, it is impossible to receive or send messages without end-to-end encryption.</p>
you can generate an invite link.</p>
<p>If you are together in person, <p>If you instead create a profile using a classic e-mail server,
you can show a QR code to your chat partner.</p> you can send and receive messages without end-to-end encryption.
Such messages lacking end-to-end encryption are marked with an e-mail icon
<img style="vertical-align:middle; width:1.2em; margin:1px" src="../email-icon.png" alt="email" />.</p>
<h3 id="howtoe2ee">
How can I establish a chat with a new contact? <a href="#howtoe2ee" class="anchor"></a>
</h3>
<p>You can send an invite link through another private chat,
show an invitation QR code when next to each other or in a video call,
or click on a “contact” that was shared in a chat.</p>
<ul> <ul>
<li> <li>
@ -791,119 +805,51 @@ on the Delta Chat app main screen.</p>
</li> </li>
</ul> </ul>
<p>Let your chat partner scan the QR image <p>Ask your chat partner to scan the QR image
with their Delta Chat app, with their Delta Chat app,
or click “Copy” or “Share” to create an invite link or click “Copy” or “Share” to create an invite link
and share it with your chat partner.</p> and share it with your chat partner.</p>
<p>Now wait while <a href="https://securejoin.delta.chat/en/latest/new.html#setup-contact-protocol">Secure-Join network messages are exchanged</a> between both devices.</p> <p>Now wait while <a href="https://securejoin.delta.chat/en/latest/new.html#setup-contact-protocol">end-to-end encryption is getting established</a>.</p>
<ul> <ul>
<li> <li>
<p>Si ambos dispositivos están en línea, <p>If both sides are online, they will soon see a (group or direct) chat
ambas partes eventualmente verán un chat (grupal o directo) con una estampilla verde and can start messaging securely.</p>
<img style="vertical-align:middle; width:1.5em; margin:1px" src="../green-checkmark.png" alt="green checkmark" />
junto al título.</p>
</li> </li>
<li> <li>
<p>Si uno de los dispositivos está sin conexión, las estampillas verdes solo aparecerán más tarde cuando el dispositivo vuelva a estar conectado a Internet y se complete el protocolo de red Secure-Join.</p> <p>If one side is offline or in bad network,
the ability to chat is delayed until connectivity is restored.</p>
</li> </li>
</ul> </ul>
<p>¡Felicitaciones! <p>Congratulations!
Ahora utilizarás automáticamente el cifrado de extremo a extremo garantizado You now will automatically use end-to-end encryption
con este contacto y ambos pueden agregarse mutuamente a grupos con estampilla verde with this contact.
<img style="vertical-align:middle; width:1.5em; margin:1px" src="../green-checkmark.png" alt="green checkmark" />, If you add each other to chat groups,
de esta manera se propagará automáticamente el cifrado de extremo a extremo garantizado entre sus miembros.</p> end-to-end encryption will be established among all members.</p>
<h3 id="e2eeguarantee"> <h3 id="e2eeguarantee">
¿Qué significa la estampilla verde y “cifrado de extremo a extremo garantizado”? <a href="#e2eeguarantee" class="anchor"></a> What does the green checkmark in a contact profile mean? <a href="#e2eeguarantee" class="anchor"></a>
</h3> </h3>
<p>Títulos de chat con estampillas verdes <p>A contact profile might show a green checkmark
<img style="vertical-align:middle; width:1.5em; margin:1px" src="../green-checkmark.png" alt="green checkmark" /> <img style="vertical-align:middle; width:1.5em; margin:1px" src="../green-checkmark.png" alt="green checkmark" />
significan que todos los mensajes en el chat estarán cifrados de extremo a extremo and an “Introduced by” line.
y no pueden ser leídos o alterados por servidores de correo electrónico o proveedores de Internet comprometidos. Every green-checkmarked contact either did a direct <a href="#howtoe2ee">QR-scan</a> with you
Unirse a chats grupales con estampillas verdes or was introduced by a another green-checkmarked contact.
difunde de manera segura la información de cifrado de todos (y las estampillas verdes) Introductions happen automatically when adding members to groups.
de una manera que garantiza el cifrado de extremo a extremo en el grupo y entre los miembros.</p> Whoever adds a green-checkmarked contact to a group with only green-checkmarked members
becomes an introducer.
<p>Perfiles de contacto con estampillas verdes In a contact profile you can tap on the “Introduced by …” text repeatedly
<img style="vertical-align:middle; width:1.5em; margin:1px" src="../green-checkmark.png" alt="green checkmark" /> until you get to the one with whom you directly did a <a href="#howtoe2ee">QR-scan</a>.</p>
significa que el envío de mensajes a un contacto está actualmente garantizado que está cifrado de extremo a extremo.
Cada contacto con estampilla verde hizo un escaneo directo de <a href="#howtoe2ee">QR</a> contigo
o fue presentado por otro contacto con estampilla verde.
Las presentaciones ocurren automáticamente al agregar miembros a grupos.
Quien agregue un contacto a un grupo con estampilla verde se convierte en un presentador
para aquellos miembros que aún no conocían al contacto agregado.
En un perfil de contacto, puedes tocar repetidamente el texto “Presentado por …”
hasta llegar al que hizo un escaneo directo de <a href="#howtoe2ee">QR</a> contigo.</p>
<p>Ten en cuenta que en un perfil de contacto puedes ver y tocar a las personas que te presentaron a ese contacto, pero puede pasar que no haya una estampilla verde en el título del perfil. Esto generalmente significa que el contacto <a href="#nocryptanymore">“envió un mensaje desde otro dispositivo”</a>.</p>
<p>Para obtener una discusión más detallada sobre “cifrado de extremo a extremo garantizado”, por favor consulta los <a href="https://securejoin.delta.chat/en/latest/new.html">protocolos Secure-Join</a> y lee específicamente sobre “Grupos Verificados”, el término técnico de lo que aquí se llama chats “marcados con una estampilla verde” o “cifrados de extremo a extremo garantizado”.</p> <p>Para obtener una discusión más detallada sobre “cifrado de extremo a extremo garantizado”, por favor consulta los <a href="https://securejoin.delta.chat/en/latest/new.html">protocolos Secure-Join</a> y lee específicamente sobre “Grupos Verificados”, el término técnico de lo que aquí se llama chats “marcados con una estampilla verde” o “cifrados de extremo a extremo garantizado”.</p>
<h3 id="nocryptanymore">
Un contacto “envió un mensaje desde otro dispositivo”, ¿qué puedo hacer? <a href="#nocryptanymore" class="anchor"></a>
</h3>
<p>Tu chat con un contacto perdió el cifrado de extremo a extremo garantizado.
La estampilla verde fue eliminada para este chat y contacto cuando veas esta advertencia.
<strong>Si encuentras sorprendente la repentina pérdida de cifrado de extremo a extremo garantizado
para este contacto, ¡no aceptes la advertencia!</strong>
En su lugar, verifica con tu contacto a través de un segundo canal
como una videollamada, otra app de chat o una llamada telefónica,
para averiguar qué sucedió.</p>
<p>Si tu contacto realmente causó la caída del cifrado de extremo a extremo garantizado, por favor vea los siguientes párrafos para conocer las razones comunes y sus mitigaciones. Sin embargo, todos los demás chats marcados con una estampilla verde siguen estando cifrados de extremo a extremo garantizado, incluso si el contacto es miembro allí.</p>
<p><strong>Tu contacto está usando Delta Chat en un segundo dispositivo (teléfono o computadora portátil)</strong></p>
<p>Si tienen otro dispositivo con la aplicación Delta Chat en funcionamiento,
deben eliminar la cuenta del nuevo dispositivo
y agregarla <a href="#multiclient">como un segundo dispositivo según se describe aquí</a>.
Tan pronto como te envíen un mensaje después, la advertencia desaparecerá
y se establecerá el cifrado garantizado con ambos dispositivos de tu contacto.</p>
<p><strong>Tu contacto reinstaló Delta Chat utilizando su antiguo inicio de sesión de cuenta</strong></p>
<p>Si tienen <a href="#backup">un archivo de respaldo</a>,
deben eliminar la cuenta del nuevo dispositivo
y en su lugar importar el archivo de respaldo para recrear su cuenta.
Tan pronto como te envíen un mensaje después, la advertencia desaparecerá
y se restablecerá el cifrado garantizado para este contacto.</p>
<p>Si no tienen un archivo de respaldo, es mejor realizar un <a href="#howtoe2ee">escaneo QR</a> con tu compañero de chat para restablecer el cifrado de extremo a extremo garantizado.</p>
<p><strong>Tu contacto envió un correo a través de una interfaz de correo web o otra aplicación de correo electrónico y volverá a usar Delta Chat pronto.</strong></p>
<p>Si estás seguro de que el contacto a veces utiliza webmail,
o alguna otra aplicación de correo que carece de cifrado de extremo a extremo,
entonces puedes aceptar la advertencia.
Tan pronto como tu contacto vuelva a utilizar Delta Chat,
el cifrado de extremo a extremo garantizado se restablecerá automáticamente.</p>
<p><strong>Tus contactos dejaron de usar Delta Chat completamente</strong></p>
<p>A veces, mantenerse en contacto es más importante que el cifrado de extremo a extremo. El cifrado de capa de transporte <a href="#tls">(“Transport Layer Encryption” o TLS)</a> puede proteger de manera significativa la confidencialidad de tus mensajes entre tu dispositivo y el servidor de correo electrónico. Pero sin el cifrado de extremo a extremo, tú y tu contacto están confiando en que el servidor de correo electrónico no lea ni manipule tus mensajes, y que no los entregue a terceros.</p>
<p>En cualquier caso, no puedes hacer mucho más que aceptar la advertencia.
Por favor, también elimina el contacto de cualquier grupo activo con estampilla verde
que puedas encontrar en “Chats compartidos” en el perfil del contacto.
Esto evitará que tu contacto reciba mensajes “ilegibles”.</p>
<p>Si el contacto eliminó Delta Chat debido a un comportamiento defectuoso o indeseable,
por favor considera publicar en nuestro <a href="https://support.delta.chat">foro de soporte</a>
para ayudarnos a identificar y solucionar problemas comunes. ¡Gracias!</p>
<h3 id="los-adjuntos-imágenes-archivos-audio-etc-están-cifrados-de-extremo-a-extremo"> <h3 id="los-adjuntos-imágenes-archivos-audio-etc-están-cifrados-de-extremo-a-extremo">
@ -927,10 +873,9 @@ y los metadatos de los archivos adjuntos, como los nombres de archivo.</p>
</h3> </h3>
<p>Sí, Delta Chat utiliza un subconjunto seguro de OpenPGP <p>Yes, Delta Chat uses a secure subset of OpenPGP
y solo muestra un indicador de seguridad de candado en un mensaje requiring the whole message to be properly encrypted and signed.
si todo el mensaje está correctamente cifrado y firmado. For example, “Detached signatures” are not treated as secure.</p>
Por ejemplo, las “firmas desvinculadas” no se consideran seguras.</p>
<p>OpenPGP is not insecure by itself. <p>OpenPGP is not insecure by itself.
Most publicly discussed OpenPGP security problems Most publicly discussed OpenPGP security problems
@ -950,7 +895,7 @@ which was thankfully adopted in summer 2023.</p>
<h3 id="openpgp-alternatives"> <h3 id="openpgp-alternatives">
¿Consideraron usar alternativas a OpenPGP para el cifrado de extremo a extremo? <a href="#openpgp-alternatives" class="anchor"></a> Did you consider using alternatives to OpenPGP for end-to-end-encryption? <a href="#openpgp-alternatives" class="anchor"></a>
</h3> </h3>
@ -993,17 +938,15 @@ as defined by the Autocrypt Level 1 specification.</p>
<h3 id="tls"> <h3 id="tls">
¿Se expone un mensaje en texto claro si no está disponible el cifrado de extremo a extremo? <a href="#tls" class="anchor"></a> Are messages marked with the mail icon exposed on the Internet? <a href="#tls" class="anchor"></a>
</h3> </h3>
<p>Even if your messages are not guaranteed to be end-to-end encrypted, <p>If you are sending or receiving e-mail messages without end-to-end encryption (using a classic e-mail server),
they are still protected from Internet providers like cell or cable companies. they are still protected from cell or cable companies who can not read or modify your e-mail messages.
However, your and your recipient’s e-mail providers But both your and your recipient’s e-mail providers
may read, analyze or even modify your messages, may read, analyze or modify your messages, including any attachments.</p>
including any attachments,
if they are not end-to-end encrypted.</p>
<p>Delta Chat by default uses strict <p>Delta Chat by default uses strict
<a href="https://en.wikipedia.org/wiki/Transport_Layer_Security">TLS encryption</a> <a href="https://en.wikipedia.org/wiki/Transport_Layer_Security">TLS encryption</a>
@ -1016,8 +959,6 @@ then transport encryption will be enforced between e-mail providers
in which case Delta Chat communications will never be exposed in cleartext to the Internet in which case Delta Chat communications will never be exposed in cleartext to the Internet
even if the message was not end-to-end encrypted.</p> even if the message was not end-to-end encrypted.</p>
<p>Ten en cuenta que <a href="#howtoe2ee">mantener un cifrado de extremo a extremo garantizado</a> sobre el cifrado TLS proporciona seguridad generalizada entre tus dispositivos y los del destinatario. Ni siquiera tu proveedor de correo electrónico o de Internet podrá leer o modificar tus mensajes.</p>
<h3 id="message-metadata"> <h3 id="message-metadata">
@ -1026,24 +967,25 @@ even if the message was not end-to-end encrypted.</p>
</h3> </h3>
<p>Delta Chat protege la mayoría de los metadatos de los mensajes al colocar la siguiente información en la parte cifrada de extremo a extremo de los mensajes:</p> <p>Unlike most other messengers,
Delta Chat apps do not store any metadata about contacts or groups on servers, also not in encrypted form.
Instead, all group metadata is end-to-end encrypted and stored on end-user devices, only.</p>
<p>E-mail Servers can therefore only see</p>
<ul> <ul>
<li>Subject line</li> <li>
<li>Group avatar and name</li> <p>the message date,</p>
<li>MDN (read receipt) requests (<code class="language-plaintext highlighter-rouge">Chat-Disposition-Notification-To</code>)</li> </li>
<li>Disappearing message timer (<code class="language-plaintext highlighter-rouge">Ephemeral-Timer</code>)</li> <li>
<li><code class="language-plaintext highlighter-rouge">Chat-Group-Member-Removed</code>, <code class="language-plaintext highlighter-rouge">Chat-Group-Member-Added</code></li> <p>sender and receiver addresses</p>
<li><code class="language-plaintext highlighter-rouge">Secure-Join</code> header containing secure join commands</li> </li>
<li>Notification about enabling location streaming</li> <li>
<li>WebRTC room URL</li> <p>and message size.</p>
</li>
</ul> </ul>
<p>Los servidores de correo electrónico no obtienen acceso a estos metadatos protegidos <p>All other message, contact and group metadata resides in the end-to-end encrypted part of messages.</p>
pero sí ven la fecha del mensaje así como el tamaño del mensaje,
y, lo que es más importante, las direcciones del remitente y del destinatario.
Los servidores de correo electrónico necesitan direcciones de destinatarios para enrutar y
entregar mensajes a los dispositivos del destinatario.</p>
<h3 id="device-seizure"> <h3 id="device-seizure">
@ -1055,82 +997,34 @@ entregar mensajes a los dispositivos del destinatario.</p>
<p>Both for protecting against metadata-collecting e-mail servers <p>Both for protecting against metadata-collecting e-mail servers
as well as against the threat of device seizure as well as against the threat of device seizure
we recommend to use a <a href="https://delta.chat/chatmail">chatmail server</a> we recommend to use a <a href="https://chatmail.at/relays">chatmail relay</a>
to create pseudonymous temporary profiles through QR-code scans. to create chat profiles using random e-mail addresses for transport.
Note that Delta Chat apps on all platforms support multiple profiles Note that Delta Chat apps on all platforms support multiple profiles
so you can easily use situation-specific profiles next to your “main” profile so you can easily use situation-specific profiles next to your “main” profile
with the knowledge that all their data, along with all metadata, will be deleted. with the knowledge that all their data, along with all metadata, will be deleted.
Moreover, if a device is seized then contacts using temporary profiles Moreover, if a device is seized then chat contacts using short-lived profiles
can not be identified easily, as compared to messengers which reveal can not be identified easily.</p>
phone numbers in chat groups which in turn are often associated with legal identities.</p>
<h3 id="cómo-puedo-verificar-la-información-de-cifrado"> <h3 id="sealedsender">
¿Cómo puedo verificar la información de cifrado? <a href="#cómo-puedo-verificar-la-información-de-cifrado" class="anchor"></a> Does Delta Chat support “Sealed Sender”? <a href="#sealedsender" class="anchor"></a>
</h3> </h3>
<p>Puede verificar manualmente el estado de cifrado de extremo a extremo en el diálogo “Cifrado” (perfil de usuario en Android/iOS o hacer clic derecho en el elemento de lista de chat de un usuario en el escritorio). Delta Chat muestra dos huellas digitales allí. Si las mismas huellas digitales aparecen en su propio dispositivo y en el dispositivo de su contacto, la conexión es segura.</p> <p>No, not yet.</p>
<h3 id="cómo-puedo-verificar-el-estado-de-cifrado-de-los-mensajes"> <p>The Signal messenger introduced <a href="https://signal.org/blog/sealed-sender/">“Sealed Sender” in 2018</a>
to keep their server infrastructure ignorant of who is sending a message to a set of recipients.
It is particularly important because the Signal server knows the mobile number of each account,
which is usually associated with a passport identity.</p>
<p>Even if <a href="https://chatmail.at/relays">chatmail relays</a>
¿Cómo puedo verificar el estado de cifrado de los mensajes? <a href="#cómo-puedo-verificar-el-estado-de-cifrado-de-los-mensajes" class="anchor"></a> do not ask for any private data (including no phone numbers),
it might still be worthwhile to protect relational metadata between addresses.
We don’t foresee bigger problems in using random throw-away e-mail addresses for sealed sending
</h3> but an implementation has not been agreed as a priority yet.</p>
<p>Un pequeño <strong>candado</strong> en una burbuja de mensaje indica que el mensaje fue correctamente cifrado de extremo a extremo por el remitente dado. Si no hay <strong>candado</strong>, es probable que el mensaje no esté correctamente cifrado de extremo a extremo, ya que el remitente utiliza una aplicación o interfaz de correo web sin soporte para el cifrado de extremo a extremo.</p>
<h3 id="por-qué-veo-mensajes-sin-cifrar">
¿Por qué veo mensajes sin cifrar? <a href="#por-qué-veo-mensajes-sin-cifrar" class="anchor"></a>
</h3>
<p>If a contact uses a non-Autocrypt e-mail app,
all messages involving this contact (in a group or 1:1 chat)
will not be end-to-end encrypted, and thus not show a “padlock” with messages.
Note that even if your contacts use Delta Chat on their account,
they might also use a non-Autocrypt e-mail app on that account
which then may cause intermittently unencrypted messages.
Replying unencrypted to unencrypted messages is mandated by Autocrypt
to prevent unreadable messages on the side of your contacts
and their non-Autocrypt e-mail app.</p>
<h3 id="cómo-puedo-obtener-un-chat-cifrado-de-extremo-a-extremo-con-un-contacto-de-delta-chat-que-a-veces-utiliza-webmail-u-otra-aplicación-de-correo-electrónico-no-autocrypt">
¿Cómo puedo obtener un chat cifrado de extremo a extremo con un contacto de Delta Chat que a veces utiliza webmail u otra aplicación de correo electrónico no Autocrypt? <a href="#cómo-puedo-obtener-un-chat-cifrado-de-extremo-a-extremo-con-un-contacto-de-delta-chat-que-a-veces-utiliza-webmail-u-otra-aplicación-de-correo-electrónico-no-autocrypt" class="anchor"></a>
</h3>
<p>Si necesitas un chat cifrado de extremo a extremo de forma segura con un contacto que está utilizando su cuenta tanto con Delta Chat como con aplicaciones no-Autocrypt (por ejemplo, webmail), lo mejor es configurar <a href="#howtoe2ee">cifrado de extremo a extremo garantizado con ellos</a> y luego crear un grupo cifrado de extremo a extremo garantizado con ustedes dos como miembros. En este chat de grupo, todos los mensajes estarán cifrados de extremo a extremo, incluso si el chat directo entre ustedes dos tiene una advertencia de <a href="#nocryptanymore">“… envió un mensaje desde otro dispositivo”</a>.</p>
<h3 id="cómo-puedo-asegurar-el-cifrado-de-extremo-a-extremo-y-la-eliminación-de-mensajes">
¿Cómo puedo asegurar el cifrado de extremo a extremo y la eliminación de mensajes? <a href="#cómo-puedo-asegurar-el-cifrado-de-extremo-a-extremo-y-la-eliminación-de-mensajes" class="anchor"></a>
</h3>
<p>La mejor manera de asegurar que cada mensaje esté cifrado de extremo a extremo
y que los metadatos se borren lo más rápido posible
es <a href="#howtoe2ee">utilizando chats con cifrado de extremo a extremo garantizado</a>
y activando la <a href="#ephemeralmsgs">desaparición de mensajes</a>.</p>
<p>Los chats con cifrado de extremo a extremo garantizado protegen contra ataques <a href="https://es.wikipedia.org/wiki/Ataque_de_intermediario">MITM</a>
y al activar “mensajes efímeros” se borran los mensajes
en el servidor después de un tiempo configurado por el usuario.</p>
<p>Si no necesitas una copia de tus mensajes en el servidor durante más tiempo,
también puedes activar <a href="#delold">“eliminar mensajes del servidor automáticamente”</a>.</p>
<h3 id="pfs"> <h3 id="pfs">
@ -1140,45 +1034,48 @@ también puedes activar <a href="#delold">“eliminar mensajes del servidor auto
</h3> </h3>
<p>No, Delta Chat no soporta Perfect Forward Secrecy (PFS). <p>No, not yet.</p>
Esto significa que si se filtra tu clave privada de descifrado de Delta Chat,
y alguien ha recopilado tus mensajes previos en tránsito,
podrán descifrarlos y leerlos utilizando la clave de descifrado filtrada.</p>
<p>Ten en cuenta, sin embargo, que si alguien obtiene tus claves de descifrado, <p>Delta Chat today doesn’t support Perfect Forward Secrecy (PFS).
también podrán obtener tus mensajes, This means that if your private decryption key is leaked,
independientemente de si se implementa o no el Perfect Forward Secrecy. and someone has collected your prior in-transit messages,
La situación típica en el mundo real para las claves de descifrado filtradas es la incautación del dispositivo, they will be able to decrypt and read them using the leaked decryption key.
que discutimos en nuestra respuesta <a href="#device-seizure">sobre metadatos e incautación de dispositivos</a>.</p> Note that Forward Secrecy only increases security if you delete messages.
Otherwise, someone obtaining your decryption keys
is typically also able to get all your non-deleted messages
and doesn’t even need to decrypt any previously collected messages.</p>
<p>It is possible that Delta Chat evolves to support Perfect Forward Secrecy, <p>We designed a Forward Secrecy approach that withstood
because OpenPGP is just a container for encrypted messages initial examination from some cryptographers and implementation experts
but encryption key management (and thus key rotation or key “ratcheting”) but is pending a more formal write up
could be organized in flexible ways. to ascertain it reliably works in federated messaging and with multi-device usage,
See <a href="https://gitlab.com/sequoia-pgp/openpgp-dr">Seqouia’s PFS prototype</a> before it could be implemented in <a href="https://github.com/chatmail/core">chatmail core</a>,
for existing experiments in the OpenPGP implementor community.</p> which would make it available in all <a href="https://chatmail.at/clients">chatmail clients</a>.</p>
<h3 id="es-el-cifrado-de-extremo-a-extremo-de-delta-chat-tan-seguro-como-el-de-signal"> <h3 id="pqc">
¿Es el cifrado de extremo a extremo de Delta Chat tan seguro como el de Signal? <a href="#es-el-cifrado-de-extremo-a-extremo-de-delta-chat-tan-seguro-como-el-de-signal" class="anchor"></a> Does Delta Chat support Post-Quantum-Cryptography? <a href="#pqc" class="anchor"></a>
</h3> </h3>
<p>It depends on what is important to you. <p>No, not yet.</p>
Delta Chat <a href="#pfs">does not support PFS</a> like Signal does
but it provides <a href="#e2eeguarantee">guaranteed end-to-end encrypted chats</a>
that are safe against compromised servers or corrupted networks.
Signal and most other PFS-supporting messengers do not provide
a practical scheme for protecting chat groups from network attacks
which are arguably more worrisome
than a potential attacker who seizes your phone and private encryption setup
but somehow not your messages, yet has a full record of all
past encrypted messages.</p>
<p>In any case, Delta Chat’s end-to-end encryption uses a <a href="#openpgp-secure">secure subset of OpenPGP</a> <p>Delta Chat uses the Rust OpenPGP library <a href="https://github.com/rpgp/rpgp">rPGP</a>
which has been <a href="https://delta.chat/assets/blog/2019-first-security-review.pdf">independently security-audited</a>.</p> which supports the latest <a href="https://datatracker.ietf.org/doc/draft-ietf-openpgp-pqc/">IETF Post-Quantum-Cryptography OpenPGP draft</a>.
We aim to add PQC support in <a href="https://github.com/chatmail/core">chatmail core</a> after the draft is finalized at the IETF
in collaboration with other OpenPGP implementers.</p>
<h3 id="how-can-i-manually-check-encryption-information">
How can I manually check encryption information? <a href="#how-can-i-manually-check-encryption-information" class="anchor"></a>
</h3>
<p>Puede verificar manualmente el estado de cifrado de extremo a extremo en el diálogo “Cifrado” (perfil de usuario en Android/iOS o hacer clic derecho en el elemento de lista de chat de un usuario en el escritorio). Delta Chat muestra dos huellas digitales allí. Si las mismas huellas digitales aparecen en su propio dispositivo y en el dispositivo de su contacto, la conexión es segura.</p>
<h3 id="importkey"> <h3 id="importkey">
@ -1213,7 +1110,7 @@ from most recent to older:</p>
<li> <li>
<p>2024 December, an <a href="https://github.com/rpgp/docs/blob/main/audits/NGI%20Core%20rPGP%20penetration%20test%20report%202024%201.0.pdf">NLNET-commissioned Evaluation of <p>2024 December, an <a href="https://github.com/rpgp/docs/blob/main/audits/NGI%20Core%20rPGP%20penetration%20test%20report%202024%201.0.pdf">NLNET-commissioned Evaluation of
rPGP</a> by <a href="https://www.radicallyopensecurity.com/">Radically Open Security</a> took place. rPGP</a> by <a href="https://www.radicallyopensecurity.com/">Radically Open Security</a> took place.
rPGP serves as the end-to-end encyption <a href="https://openpgp.org">OpenPGP</a> engine of Delta Chat. rPGP serves as the end-to-end encryption <a href="https://openpgp.org">OpenPGP</a> engine of Delta Chat.
Two advisories were released related to the findings of this audit:</p> Two advisories were released related to the findings of this audit:</p>
<ul> <ul>
@ -1604,6 +1501,11 @@ a message, but also appears on the map.</li>
</h3> </h3>
<p>Note:
Changing email addresses is temporarily disabled
because of ongoing changes to the DeltaChat core.
It should be available again in a few months.</p>
<ol> <ol>
<li> <li>
<p>Change your address in “Settings → Advanced → Password and Account” and <p>Change your address in “Settings → Advanced → Password and Account” and

420
src/main/assets/help/fr/help.html
View file

@ -36,27 +36,24 @@
<li><a href="#why-does-delta-chat-integrate-with-centralized-proprietary-applegoogle-push-services">Why does Delta Chat integrate with centralized proprietary Apple/Google push services?</a></li> <li><a href="#why-does-delta-chat-integrate-with-centralized-proprietary-applegoogle-push-services">Why does Delta Chat integrate with centralized proprietary Apple/Google push services?</a></li>
</ul> </ul>
</li> </li>
<li><a href="#encryption-and-security">Encryption and Security</a> <li><a href="#e2ee">Encryption and Security</a>
<ul> <ul>
<li><a href="#which-standards-are-used-for-end-to-end-encryption">Which standards are used for end-to-end encryption?</a></li> <li><a href="#which-standards-are-used-for-end-to-end-encryption">Which standards are used for end-to-end encryption?</a></li>
<li><a href="#whene2e">How can i know if messages are end-to-end encrypted?</a></li> <li><a href="#whene2e">How can i know if messages are end-to-end encrypted?</a></li>
<li><a href="#howtoe2ee">How can I get guaranteed end-to-end encryption and green checkmarks?</a></li> <li><a href="#can-i-still-receive-or-send-mails-without-end-to-end-encryption">Can i still receive or send mails without end-to-end encryption?</a></li>
<li><a href="#e2eeguarantee">What does the green checkmark and “guaranteed end-to-end encryption” mean?</a></li> <li><a href="#howtoe2ee">How can I establish a chat with a new contact?</a></li>
<li><a href="#nocryptanymore">A contact “sent a message from another device”, what can i do?</a></li> <li><a href="#e2eeguarantee">What does the green checkmark in a contact profile mean?</a></li>
<li><a href="#are-attachments-pictures-files-audio-etc-end-to-end-encrypted">Are attachments (pictures, files, audio etc.) end-to-end encrypted?</a></li> <li><a href="#are-attachments-pictures-files-audio-etc-end-to-end-encrypted">Are attachments (pictures, files, audio etc.) end-to-end encrypted?</a></li>
<li><a href="#openpgp-secure">Is OpenPGP secure?</a></li> <li><a href="#openpgp-secure">Is OpenPGP secure?</a></li>
<li><a href="#openpgp-alternatives">Did you consider using alternatives to OpenPGP for end-to-end -encryption?</a></li> <li><a href="#openpgp-alternatives">Did you consider using alternatives to OpenPGP for end-to-end-encryption?</a></li>
<li><a href="#is-delta-chat-vulnerable-to-efail">Is Delta Chat vulnerable to EFAIL?</a></li> <li><a href="#is-delta-chat-vulnerable-to-efail">Is Delta Chat vulnerable to EFAIL?</a></li>
<li><a href="#tls">Is a message exposed in cleartext if end-to-end encryption is not available?</a></li> <li><a href="#tls">Are messages marked with the mail icon exposed on the Internet?</a></li>
<li><a href="#message-metadata">How does Delta Chat protect metadata in messages?</a></li> <li><a href="#message-metadata">How does Delta Chat protect metadata in messages?</a></li>
<li><a href="#device-seizure">How to protect metadata and contacts when a device is seized?</a></li> <li><a href="#device-seizure">How to protect metadata and contacts when a device is seized?</a></li>
<li><a href="#how-can-i-check-encryption-information">How can i check encryption information?</a></li> <li><a href="#sealedsender">Does Delta Chat support “Sealed Sender”?</a></li>
<li><a href="#how-can-i-check-the-encryption-status-of-messages">How can I check the encryption status of messages?</a></li>
<li><a href="#why-do-i-see-unencrypted-messages">Why do I see unencrypted messages?</a></li>
<li><a href="#how-can-i-get-an-end-to-end-encrypted-chat-with-a-delta-chat-contact-who-sometimes-uses-webmail-or-another-non-autocrypt-e-mail-app">How can i get an end-to-end encrypted chat with a Delta Chat contact who sometimes uses webmail or another non-Autocrypt e-mail app?</a></li>
<li><a href="#how-can-i-ensure-message-end-to-end-encryption-and-deletion">How can I ensure message end-to-end encryption and deletion?</a></li>
<li><a href="#pfs">Does Delta Chat support Perfect Forward Secrecy?</a></li> <li><a href="#pfs">Does Delta Chat support Perfect Forward Secrecy?</a></li>
<li><a href="#is-end-to-end-encryption-of-delta-chat-as-safe-as-signal">Is end-to-end encryption of Delta Chat as safe as Signal?</a></li> <li><a href="#pqc">Does Delta Chat support Post-Quantum-Cryptography?</a></li>
<li><a href="#how-can-i-manually-check-encryption-information">How can I manually check encryption information?</a></li>
<li><a href="#importkey">Puis-je ré-utiliser ma clé privée existante ?</a></li> <li><a href="#importkey">Puis-je ré-utiliser ma clé privée existante ?</a></li>
<li><a href="#security-audits">Est-ce qu’un audit indépendant des failles de sécurité a été réalisé sur Delta Chat ?</a></li> <li><a href="#security-audits">Est-ce qu’un audit indépendant des failles de sécurité a été réalisé sur Delta Chat ?</a></li>
</ul> </ul>
@ -700,10 +697,10 @@ that achieves “instant delivery” of messages for all chatmail servers
including a potential one <a href="https://delta.chat/chatmail#selfhosted">you might setup yourself without our permission</a>. including a potential one <a href="https://delta.chat/chatmail#selfhosted">you might setup yourself without our permission</a>.
Welcome to the power of the interoperable and massive chatmail and e-mail system :)</p> Welcome to the power of the interoperable and massive chatmail and e-mail system :)</p>
<h2 id="encryption-and-security"> <h2 id="e2ee">
Encryption and Security <a href="#encryption-and-security" class="anchor"></a> Encryption and Security <a href="#e2ee" class="anchor"></a>
</h2> </h2>
@ -716,18 +713,26 @@ Welcome to the power of the interoperable and massive chatmail and e-mail system
</h3> </h3>
<p><a href="https://autocrypt.org">Autocrypt</a> is used for automatically <p>Delta Chat uses a <a href="#openpgp-secure">secure subset of the OpenPGP standard</a>
establishing end-to-end encryption with contacts and group chats. to provide automatic end-to-end encryption using these protocols:</p>
Autocrypt uses a limited and <a href="#openpgp-secure">secure subset of the OpenPGP standard</a>.
End-to-End encrypted messages are marked with a padlock
<img style="vertical-align:middle; width:1.2em; margin:1px" src="../lock-icon.png" alt="padlock" />.</p>
<p><a href="https://securejoin.delta.chat/en/latest/new.html">Secure-Join protocols</a> <ul>
are used for establishing chats with guaranteed end-to-end encryption <li>
which protects against network attacks and compromised servers. <p><a href="https://securejoin.delta.chat/en/latest/new.html">Secure-Join</a>
Chats marked with a green checkmark to exchange encryption setup information through QR-code scanning or “invite links”.</p>
<img style="vertical-align:middle; width:1.5em; margin:1px" src="../green-checkmark.png" alt="green checkmark" /> </li>
guarantee end-to-end encrypted messages.</p> <li>
<p><a href="https://autocrypt.org">Autocrypt</a> is used for automatically
establishing end-to-end encryption between contacts and all members of a group chat.</p>
</li>
<li>
<p><a href="https://github.com/chatmail/core/blob/main/spec.md#attaching-a-contact-to-a-message">Sharing a contact to a
chat</a>
enables receivers to use end-to-end encryption with the contact.</p>
</li>
</ul>
<p>Delta Chat does not query, publish or interact with any OpenPGP key servers.</p>
<h3 id="whene2e"> <h3 id="whene2e">
@ -737,28 +742,37 @@ guarantee end-to-end encrypted messages.</p>
</h3> </h3>
<p>All end-to-end encrypted messages carry a padlock:</p> <p>All messages in Delta Chat are <strong>end-to-end encrypted by default</strong>.
Since the Delta Chat Version 2 release series (July 2025)
there are no lock or similar markers on end-to-end encrypted messages, anymore.</p>
<p><img style="width:160px; margin:1px" src="../lock-screenshot.png" alt="padlock in bubble" /></p> <h3 id="can-i-still-receive-or-send-mails-without-end-to-end-encryption">
<p>End-to-end encryption is guaranteed if there is a green checkmark next to the chat title:</p>
<p><img style="width:211px; margin:1px" src="../green-checkmark-screenshot.png" alt="green checkmark in title" /></p>
<h3 id="howtoe2ee">
How can I get guaranteed end-to-end encryption and green checkmarks? <a href="#howtoe2ee" class="anchor"></a> Can i still receive or send mails without end-to-end encryption? <a href="#can-i-still-receive-or-send-mails-without-end-to-end-encryption" class="anchor"></a>
</h3> </h3>
<p>If you have a second communication channel with your chat partner, <p>If you use default <a href="https://chatmail.at/relays">chatmail relays</a>,
like a video chat or a different messenger, it is impossible to receive or send messages without end-to-end encryption.</p>
you can generate an invite link.</p>
<p>If you are together in person, <p>If you instead create a profile using a classic e-mail server,
you can show a QR code to your chat partner.</p> you can send and receive messages without end-to-end encryption.
Such messages lacking end-to-end encryption are marked with an e-mail icon
<img style="vertical-align:middle; width:1.2em; margin:1px" src="../email-icon.png" alt="email" />.</p>
<h3 id="howtoe2ee">
How can I establish a chat with a new contact? <a href="#howtoe2ee" class="anchor"></a>
</h3>
<p>You can send an invite link through another private chat,
show an invitation QR code when next to each other or in a video call,
or click on a “contact” that was shared in a chat.</p>
<ul> <ul>
<li> <li>
@ -773,135 +787,54 @@ on the Delta Chat app main screen.</p>
</li> </li>
</ul> </ul>
<p>Let your chat partner scan the QR image <p>Ask your chat partner to scan the QR image
with their Delta Chat app, with their Delta Chat app,
or click “Copy” or “Share” to create an invite link or click “Copy” or “Share” to create an invite link
and share it with your chat partner.</p> and share it with your chat partner.</p>
<p>Now wait while <a href="https://securejoin.delta.chat/en/latest/new.html#setup-contact-protocol">Secure-Join network messages are exchanged</a> between both devices.</p> <p>Now wait while <a href="https://securejoin.delta.chat/en/latest/new.html#setup-contact-protocol">end-to-end encryption is getting established</a>.</p>
<ul> <ul>
<li> <li>
<p>If both devices are online, <p>If both sides are online, they will soon see a (group or direct) chat
both sides will eventually see a (group or direct) chat with a green checkmark and can start messaging securely.</p>
<img style="vertical-align:middle; width:1.5em; margin:1px" src="../green-checkmark.png" alt="green checkmark" />
next to the title.</p>
</li> </li>
<li> <li>
<p>If one of the devices is offline, the green checkmarks will only <p>If one side is offline or in bad network,
appear later when the device is internet-connected again the ability to chat is delayed until connectivity is restored.</p>
and the Secure-Join network protocol completed.</p>
</li> </li>
</ul> </ul>
<p>Congratulations! <p>Congratulations!
You now will automatically use guaranteed end-to-end encryption You now will automatically use end-to-end encryption
with this contact and both of you can add each other to green-checkmarked groups with this contact.
<img style="vertical-align:middle; width:1.5em; margin:1px" src="../green-checkmark.png" alt="green checkmark" />, If you add each other to chat groups,
thereby automatically spreading guaranteed end-to-end encryption among its members.</p> end-to-end encryption will be established among all members.</p>
<h3 id="e2eeguarantee"> <h3 id="e2eeguarantee">
What does the green checkmark and “guaranteed end-to-end encryption” mean? <a href="#e2eeguarantee" class="anchor"></a> What does the green checkmark in a contact profile mean? <a href="#e2eeguarantee" class="anchor"></a>
</h3> </h3>
<p>Chat titles with green checkmarks <p>A contact profile might show a green checkmark
<img style="vertical-align:middle; width:1.5em; margin:1px" src="../green-checkmark.png" alt="green checkmark" /> <img style="vertical-align:middle; width:1.5em; margin:1px" src="../green-checkmark.png" alt="green checkmark" />
mean that all messages in the chat will be end-to-end encrypted and an “Introduced by” line.
and can not be read or altered by compromised e-mail servers or Internet providers.
Joining green-checkmarked group chats
safely spreads everybody’s encryption information (and green checkmarks)
in a manner that guarantees end-to-end encryption in the group and among members.</p>
<p>Contact profiles with green checkmarks
<img style="vertical-align:middle; width:1.5em; margin:1px" src="../green-checkmark.png" alt="green checkmark" />
mean that messaging a contact is currently guaranteed to be end-to-end encrypted.
Every green-checkmarked contact either did a direct <a href="#howtoe2ee">QR-scan</a> with you Every green-checkmarked contact either did a direct <a href="#howtoe2ee">QR-scan</a> with you
or was introduced by a another green-checkmarked contact. or was introduced by a another green-checkmarked contact.
Introductions happen automatically when adding members to groups. Introductions happen automatically when adding members to groups.
Whoever adds a contact to a green-checkmarked group becomes an introducer Whoever adds a green-checkmarked contact to a group with only green-checkmarked members
to those members who didn’t yet know about the added contact. becomes an introducer.
In a contact profile you can tap on the “Introduced by …” text repeatedly In a contact profile you can tap on the “Introduced by …” text repeatedly
until you get to the one with whom you directly did a <a href="#howtoe2ee">QR-scan</a>.</p> until you get to the one with whom you directly did a <a href="#howtoe2ee">QR-scan</a>.</p>
<p>Note that in a contact profile you may see and tap introducers
but there is no green checkmark in the profile title.
This usually means that the contact <a href="#nocryptanymore">“sent a message from another device”</a>.</p>
<p>For more in-depth discussion of “guaranteed end-to-end encryption” <p>For more in-depth discussion of “guaranteed end-to-end encryption”
please see <a href="https://securejoin.delta.chat/en/latest/new.html">Secure-Join protocols</a> please see <a href="https://securejoin.delta.chat/en/latest/new.html">Secure-Join protocols</a>
and specifically read about “Verified Groups”, the technical term and specifically read about “Verified Groups”, the technical term
of what is called here “green-checkmarked” or “guaranteed end-to-end encrypted” chats.</p> of what is called here “green-checkmarked” or “guaranteed end-to-end encrypted” chats.</p>
<h3 id="nocryptanymore">
A contact “sent a message from another device”, what can i do? <a href="#nocryptanymore" class="anchor"></a>
</h3>
<p>Your chat with a contact lost guaranteed end-to-end encryption.
The green checkmark was removed for this chat and contact when you see this warning.
<strong>If you find the sudden drop of guaranteed end-to-end encryption
surprising for this contact then don’t accept the warning!</strong>
Instead check with your contact through a second channel
like a video call, other messenger or a phone call,
to find out what happened.</p>
<p>If your contact actually caused the drop of guaranteed end-to-end encryption
please see the next paragraphs for common reasons and their mitigations.
Regardless, all other green-checkmarked chats remain guaranteed end-to-end encrypted
even if the contact is a member there.</p>
<p><strong>Your contact is using Delta Chat on a second device (phone or laptop)</strong></p>
<p>If they have another device with a Delta Chat app running,
they should remove the profile from the new device
and add it <a href="#multiclient">as a second device as described here</a>.
As soon as they message you afterwards, the warning will be gone
and guaranteed encryption is established with both devices of your contact.</p>
<p><strong>Your contact reinstalled Delta Chat using their old account login</strong></p>
<p>If they have <a href="#backup">a backup file</a>,
they should remove the profile from the new device
and rather import the backup file to re-create their profile.
As soon as they message you afterwards, the warning will be gone
and guaranteed encryption is re-established for this contact.</p>
<p>If they don’t have a backup file, it’s best to perform a <a href="#howtoe2ee">QR scan</a>
with your chat partner to re-establish guaranteed end-to-end encryption.</p>
<p><strong>Your contact sent a mail through a webmail interface or another e-mail app
and will get back to using Delta Chat soon again.</strong></p>
<p>If you are sure that the contact sometimes uses webmail,
or another mail app lacking end-to-end encryption,
then you may accept the warning.
As soon as your contact uses Delta Chat again,
guaranteed end-to-end encryption will be automatically re-established.</p>
<p><strong>Your contact stopped using Delta Chat entirely</strong></p>
<p>Sometimes remaining in contact is more important than end-to-end encryption.
<a href="#tls">“Transport Layer Encryption” (TLS)</a> may still meaningfully protect
the confidentiality of your messages between your device and the e-mail server.
But without end-to-end encryption you and your contact are trusting your e-mail server
to not read or manipulate your messages, and to not hand them to third parties.</p>
<p>In any case, you can not do much else than accept the warning.
Please also remove the contact from any active green-checkmarked group
which you can find in “Chats in Common” in the Contact profile.
This spares your contact from getting “unreadable” messages.</p>
<p>If the contact removed Delta Chat because of buggy or undesirable behaviour,
please consider posting to our <a href="https://support.delta.chat">support forum</a>
to help us identify and address common problems. Thanks!</p>
<h3 id="are-attachments-pictures-files-audio-etc-end-to-end-encrypted"> <h3 id="are-attachments-pictures-files-audio-etc-end-to-end-encrypted">
@ -926,8 +859,7 @@ and attachment metadata such as filenames.</p>
</h3> </h3>
<p>Yes, Delta Chat uses a secure subset of OpenPGP <p>Yes, Delta Chat uses a secure subset of OpenPGP
and only displays a padlock security indicator on a message requiring the whole message to be properly encrypted and signed.
if the whole message is properly encrypted and signed.
For example, “Detached signatures” are not treated as secure.</p> For example, “Detached signatures” are not treated as secure.</p>
<p>OpenPGP is not insecure by itself. <p>OpenPGP is not insecure by itself.
@ -948,7 +880,7 @@ which was thankfully adopted in summer 2023.</p>
<h3 id="openpgp-alternatives"> <h3 id="openpgp-alternatives">
Did you consider using alternatives to OpenPGP for end-to-end -encryption? <a href="#openpgp-alternatives" class="anchor"></a> Did you consider using alternatives to OpenPGP for end-to-end-encryption? <a href="#openpgp-alternatives" class="anchor"></a>
</h3> </h3>
@ -991,17 +923,15 @@ as defined by the Autocrypt Level 1 specification.</p>
<h3 id="tls"> <h3 id="tls">
Is a message exposed in cleartext if end-to-end encryption is not available? <a href="#tls" class="anchor"></a> Are messages marked with the mail icon exposed on the Internet? <a href="#tls" class="anchor"></a>
</h3> </h3>
<p>Even if your messages are not guaranteed to be end-to-end encrypted, <p>If you are sending or receiving e-mail messages without end-to-end encryption (using a classic e-mail server),
they are still protected from Internet providers like cell or cable companies. they are still protected from cell or cable companies who can not read or modify your e-mail messages.
However, your and your recipient’s e-mail providers But both your and your recipient’s e-mail providers
may read, analyze or even modify your messages, may read, analyze or modify your messages, including any attachments.</p>
including any attachments,
if they are not end-to-end encrypted.</p>
<p>Delta Chat by default uses strict <p>Delta Chat by default uses strict
<a href="https://en.wikipedia.org/wiki/Transport_Layer_Security">TLS encryption</a> <a href="https://en.wikipedia.org/wiki/Transport_Layer_Security">TLS encryption</a>
@ -1014,10 +944,6 @@ then transport encryption will be enforced between e-mail providers
in which case Delta Chat communications will never be exposed in cleartext to the Internet in which case Delta Chat communications will never be exposed in cleartext to the Internet
even if the message was not end-to-end encrypted.</p> even if the message was not end-to-end encrypted.</p>
<p>Note that <a href="#howtoe2ee">maintaining guaranteed end-to-end encryption</a> on top of TLS encryption
provides pervasive safety between your and the recipient’s devices.
Not even your e-mail or Internet provider will be able to read or modify your messages.</p>
<h3 id="message-metadata"> <h3 id="message-metadata">
@ -1026,25 +952,25 @@ Not even your e-mail or Internet provider will be able to read or modify your me
</h3> </h3>
<p>Delta Chat protects most message metadata by putting the following information <p>Unlike most other messengers,
into the end-to-end encrypted part of messages:</p> Delta Chat apps do not store any metadata about contacts or groups on servers, also not in encrypted form.
Instead, all group metadata is end-to-end encrypted and stored on end-user devices, only.</p>
<p>E-mail Servers can therefore only see</p>
<ul> <ul>
<li>Subject line</li> <li>
<li>Group avatar and name</li> <p>the message date,</p>
<li>MDN (read receipt) requests (<code class="language-plaintext highlighter-rouge">Chat-Disposition-Notification-To</code>)</li> </li>
<li>Disappearing message timer (<code class="language-plaintext highlighter-rouge">Ephemeral-Timer</code>)</li> <li>
<li><code class="language-plaintext highlighter-rouge">Chat-Group-Member-Removed</code>, <code class="language-plaintext highlighter-rouge">Chat-Group-Member-Added</code></li> <p>sender and receiver addresses</p>
<li><code class="language-plaintext highlighter-rouge">Secure-Join</code> header containing secure join commands</li> </li>
<li>Notification about enabling location streaming</li> <li>
<li>WebRTC room URL</li> <p>and message size.</p>
</li>
</ul> </ul>
<p>E-Mail servers do not get access to this protected metadata <p>All other message, contact and group metadata resides in the end-to-end encrypted part of messages.</p>
but they do see the message date as well as the message size,
and, more importantly, the sender and receiver addresses.
E-mail servers need receiver addresses to route and
deliver messages to recipient’s devices.</p>
<h3 id="device-seizure"> <h3 id="device-seizure">
@ -1056,96 +982,34 @@ deliver messages to recipient’s devices.</p>
<p>Both for protecting against metadata-collecting e-mail servers <p>Both for protecting against metadata-collecting e-mail servers
as well as against the threat of device seizure as well as against the threat of device seizure
we recommend to use a <a href="https://delta.chat/chatmail">chatmail server</a> we recommend to use a <a href="https://chatmail.at/relays">chatmail relay</a>
to create pseudonymous temporary profiles through QR-code scans. to create chat profiles using random e-mail addresses for transport.
Note that Delta Chat apps on all platforms support multiple profiles Note that Delta Chat apps on all platforms support multiple profiles
so you can easily use situation-specific profiles next to your “main” profile so you can easily use situation-specific profiles next to your “main” profile
with the knowledge that all their data, along with all metadata, will be deleted. with the knowledge that all their data, along with all metadata, will be deleted.
Moreover, if a device is seized then contacts using temporary profiles Moreover, if a device is seized then chat contacts using short-lived profiles
can not be identified easily, as compared to messengers which reveal can not be identified easily.</p>
phone numbers in chat groups which in turn are often associated with legal identities.</p>
<h3 id="how-can-i-check-encryption-information"> <h3 id="sealedsender">
How can i check encryption information? <a href="#how-can-i-check-encryption-information" class="anchor"></a> Does Delta Chat support “Sealed Sender”? <a href="#sealedsender" class="anchor"></a>
</h3> </h3>
<p>You may check the end-to-end encryption status manually in the “Encryption” dialog <p>No, not yet.</p>
(user profile on Android/iOS or right-click a user’s chat-list item on desktop).
Delta Chat shows two fingerprints there.
If the same fingerprints appear on your own and your contact’s device,
the connection is safe.</p>
<h3 id="how-can-i-check-the-encryption-status-of-messages"> <p>The Signal messenger introduced <a href="https://signal.org/blog/sealed-sender/">“Sealed Sender” in 2018</a>
to keep their server infrastructure ignorant of who is sending a message to a set of recipients.
It is particularly important because the Signal server knows the mobile number of each account,
which is usually associated with a passport identity.</p>
<p>Even if <a href="https://chatmail.at/relays">chatmail relays</a>
How can I check the encryption status of messages? <a href="#how-can-i-check-the-encryption-status-of-messages" class="anchor"></a> do not ask for any private data (including no phone numbers),
it might still be worthwhile to protect relational metadata between addresses.
We don’t foresee bigger problems in using random throw-away e-mail addresses for sealed sending
</h3> but an implementation has not been agreed as a priority yet.</p>
<p>A little <strong>padlock</strong> in a message bubble denotes
that the message was properly end-to-end encrypted from the given sender.
If there is <strong>no padlock</strong>, the message was not properly end-to-end encrypted
most likely because the sender uses an app or webmail interface
without support for end-to-end–encryption.</p>
<h3 id="why-do-i-see-unencrypted-messages">
Why do I see unencrypted messages? <a href="#why-do-i-see-unencrypted-messages" class="anchor"></a>
</h3>
<p>If a contact uses a non-Autocrypt e-mail app,
all messages involving this contact (in a group or 1:1 chat)
will not be end-to-end encrypted, and thus not show a “padlock” with messages.
Note that even if your contacts use Delta Chat on their account,
they might also use a non-Autocrypt e-mail app on that account
which then may cause intermittently unencrypted messages.
Replying unencrypted to unencrypted messages is mandated by Autocrypt
to prevent unreadable messages on the side of your contacts
and their non-Autocrypt e-mail app.</p>
<h3 id="how-can-i-get-an-end-to-end-encrypted-chat-with-a-delta-chat-contact-who-sometimes-uses-webmail-or-another-non-autocrypt-e-mail-app">
How can i get an end-to-end encrypted chat with a Delta Chat contact who sometimes uses webmail or another non-Autocrypt e-mail app? <a href="#how-can-i-get-an-end-to-end-encrypted-chat-with-a-delta-chat-contact-who-sometimes-uses-webmail-or-another-non-autocrypt-e-mail-app" class="anchor"></a>
</h3>
<p>If you need a safely end-to-end encrypted chat with a contact
who is using their e-mail account both with Delta Chat and non-Autocrypt apps (e.g. webmail),
it’s best to setup <a href="#howtoe2ee">guaranteed end-to-end encryption with them</a>
and then create a guaranteed end-to-end encrypted group chat with you two as members.
In this group chat all messages will be end-to-end encrypted
even if the direct chat between you two has a
<a href="#nocryptanymore">“… sent a message from another device”</a> warning.</p>
<h3 id="how-can-i-ensure-message-end-to-end-encryption-and-deletion">
How can I ensure message end-to-end encryption and deletion? <a href="#how-can-i-ensure-message-end-to-end-encryption-and-deletion" class="anchor"></a>
</h3>
<p>The best way to ensure every message is end-to-end encrypted,
and metadata deleted as quickly as possible
is <a href="#howtoe2ee">using chats with guaranteed end-to-end encryption</a>
and turning on <a href="#ephemeralmsgs">disappearing messages</a>.</p>
<p>Guaranteed end-to-end encrypted chats protect against <a href="https://en.wikipedia.org/wiki/Man-in-the-middle_attack">MITM attacks</a>
and turning on disappearing messages deletes the messages
on the server after a user-configured time.</p>
<p>If you don’t need a longer-lived copy of your messages on the server,
you can also turn on <a href="#delold">“delete messages from server automatically”</a>.</p>
<h3 id="pfs"> <h3 id="pfs">
@ -1155,45 +1019,52 @@ you can also turn on <a href="#delold">“delete messages from server automatica
</h3> </h3>
<p>No, Delta Chat doesn’t support Perfect Forward Secrecy (PFS). <p>No, not yet.</p>
This means that if your Delta Chat private decryption key is leaked,
<p>Delta Chat today doesn’t support Perfect Forward Secrecy (PFS).
This means that if your private decryption key is leaked,
and someone has collected your prior in-transit messages, and someone has collected your prior in-transit messages,
they will be able to decrypt and read them using the leaked decryption key.</p> they will be able to decrypt and read them using the leaked decryption key.
Note that Forward Secrecy only increases security if you delete messages.
Otherwise, someone obtaining your decryption keys
is typically also able to get all your non-deleted messages
and doesn’t even need to decrypt any previously collected messages.</p>
<p>Note, however, that if anyone obtains to your decryption keys, <p>We designed a Forward Secrecy approach that withstood
they will typically also be able to obtain your messages, initial examination from some cryptographers and implementation experts
irrespective if Perfect Forward Secrecy is in place or not. but is pending a more formal write up
The typical real-world situation for leaked decryption keys is device seizure to ascertain it reliably works in federated messaging and with multi-device usage,
which we discuss in our answer <a href="#device-seizure">on metadata and device seizure</a>.</p> before it could be implemented in <a href="https://github.com/chatmail/core">chatmail core</a>,
which would make it available in all <a href="https://chatmail.at/clients">chatmail clients</a>.</p>
<p>It is possible that Delta Chat evolves to support Perfect Forward Secrecy, <h3 id="pqc">
because OpenPGP is just a container for encrypted messages
but encryption key management (and thus key rotation or key “ratcheting”)
could be organized in flexible ways.
See <a href="https://gitlab.com/sequoia-pgp/openpgp-dr">Seqouia’s PFS prototype</a>
for existing experiments in the OpenPGP implementor community.</p>
<h3 id="is-end-to-end-encryption-of-delta-chat-as-safe-as-signal">
Is end-to-end encryption of Delta Chat as safe as Signal? <a href="#is-end-to-end-encryption-of-delta-chat-as-safe-as-signal" class="anchor"></a> Does Delta Chat support Post-Quantum-Cryptography? <a href="#pqc" class="anchor"></a>
</h3> </h3>
<p>It depends on what is important to you. <p>No, not yet.</p>
Delta Chat <a href="#pfs">does not support PFS</a> like Signal does
but it provides <a href="#e2eeguarantee">guaranteed end-to-end encrypted chats</a>
that are safe against compromised servers or corrupted networks.
Signal and most other PFS-supporting messengers do not provide
a practical scheme for protecting chat groups from network attacks
which are arguably more worrisome
than a potential attacker who seizes your phone and private encryption setup
but somehow not your messages, yet has a full record of all
past encrypted messages.</p>
<p>In any case, Delta Chat’s end-to-end encryption uses a <a href="#openpgp-secure">secure subset of OpenPGP</a> <p>Delta Chat uses the Rust OpenPGP library <a href="https://github.com/rpgp/rpgp">rPGP</a>
which has been <a href="https://delta.chat/assets/blog/2019-first-security-review.pdf">independently security-audited</a>.</p> which supports the latest <a href="https://datatracker.ietf.org/doc/draft-ietf-openpgp-pqc/">IETF Post-Quantum-Cryptography OpenPGP draft</a>.
We aim to add PQC support in <a href="https://github.com/chatmail/core">chatmail core</a> after the draft is finalized at the IETF
in collaboration with other OpenPGP implementers.</p>
<h3 id="how-can-i-manually-check-encryption-information">
How can I manually check encryption information? <a href="#how-can-i-manually-check-encryption-information" class="anchor"></a>
</h3>
<p>You may check the end-to-end encryption status manually in the “Encryption” dialog
(user profile on Android/iOS or right-click a user’s chat-list item on desktop).
Delta Chat shows two fingerprints there.
If the same fingerprints appear on your own and your contact’s device,
the connection is safe.</p>
<h3 id="importkey"> <h3 id="importkey">
@ -1228,7 +1099,7 @@ from most recent to older:</p>
<li> <li>
<p>2024 December, an <a href="https://github.com/rpgp/docs/blob/main/audits/NGI%20Core%20rPGP%20penetration%20test%20report%202024%201.0.pdf">NLNET-commissioned Evaluation of <p>2024 December, an <a href="https://github.com/rpgp/docs/blob/main/audits/NGI%20Core%20rPGP%20penetration%20test%20report%202024%201.0.pdf">NLNET-commissioned Evaluation of
rPGP</a> by <a href="https://www.radicallyopensecurity.com/">Radically Open Security</a> took place. rPGP</a> by <a href="https://www.radicallyopensecurity.com/">Radically Open Security</a> took place.
rPGP serves as the end-to-end encyption <a href="https://openpgp.org">OpenPGP</a> engine of Delta Chat. rPGP serves as the end-to-end encryption <a href="https://openpgp.org">OpenPGP</a> engine of Delta Chat.
Two advisories were released related to the findings of this audit:</p> Two advisories were released related to the findings of this audit:</p>
<ul> <ul>
@ -1589,6 +1460,11 @@ a message, but also appears on the map.</li>
</h3> </h3>
<p>Note:
Changing email addresses is temporarily disabled
because of ongoing changes to the DeltaChat core.
It should be available again in a few months.</p>
<ol> <ol>
<li> <li>
<p>Change your address in “Settings → Advanced → Password and Account” and <p>Change your address in “Settings → Advanced → Password and Account” and

BIN
src/main/assets/help/green-checkmark-screenshot.png
View file

Binary file not shown.
Side by side

Before

Width:  |  Height:  |  Size: 2.2 KiB

420
src/main/assets/help/id/help.html
View file

@ -36,27 +36,24 @@
<li><a href="#why-does-delta-chat-integrate-with-centralized-proprietary-applegoogle-push-services">Why does Delta Chat integrate with centralized proprietary Apple/Google push services?</a></li> <li><a href="#why-does-delta-chat-integrate-with-centralized-proprietary-applegoogle-push-services">Why does Delta Chat integrate with centralized proprietary Apple/Google push services?</a></li>
</ul> </ul>
</li> </li>
<li><a href="#encryption-and-security">Encryption and Security</a> <li><a href="#e2ee">Encryption and Security</a>
<ul> <ul>
<li><a href="#which-standards-are-used-for-end-to-end-encryption">Which standards are used for end-to-end encryption?</a></li> <li><a href="#which-standards-are-used-for-end-to-end-encryption">Which standards are used for end-to-end encryption?</a></li>
<li><a href="#whene2e">How can i know if messages are end-to-end encrypted?</a></li> <li><a href="#whene2e">How can i know if messages are end-to-end encrypted?</a></li>
<li><a href="#howtoe2ee">How can I get guaranteed end-to-end encryption and green checkmarks?</a></li> <li><a href="#can-i-still-receive-or-send-mails-without-end-to-end-encryption">Can i still receive or send mails without end-to-end encryption?</a></li>
<li><a href="#e2eeguarantee">What does the green checkmark and “guaranteed end-to-end encryption” mean?</a></li> <li><a href="#howtoe2ee">How can I establish a chat with a new contact?</a></li>
<li><a href="#nocryptanymore">A contact “sent a message from another device”, what can i do?</a></li> <li><a href="#e2eeguarantee">What does the green checkmark in a contact profile mean?</a></li>
<li><a href="#are-attachments-pictures-files-audio-etc-end-to-end-encrypted">Are attachments (pictures, files, audio etc.) end-to-end encrypted?</a></li> <li><a href="#are-attachments-pictures-files-audio-etc-end-to-end-encrypted">Are attachments (pictures, files, audio etc.) end-to-end encrypted?</a></li>
<li><a href="#openpgp-secure">Is OpenPGP secure?</a></li> <li><a href="#openpgp-secure">Is OpenPGP secure?</a></li>
<li><a href="#openpgp-alternatives">Did you consider using alternatives to OpenPGP for end-to-end -encryption?</a></li> <li><a href="#openpgp-alternatives">Did you consider using alternatives to OpenPGP for end-to-end-encryption?</a></li>
<li><a href="#is-delta-chat-vulnerable-to-efail">Is Delta Chat vulnerable to EFAIL?</a></li> <li><a href="#is-delta-chat-vulnerable-to-efail">Is Delta Chat vulnerable to EFAIL?</a></li>
<li><a href="#tls">Is a message exposed in cleartext if end-to-end encryption is not available?</a></li> <li><a href="#tls">Are messages marked with the mail icon exposed on the Internet?</a></li>
<li><a href="#message-metadata">How does Delta Chat protect metadata in messages?</a></li> <li><a href="#message-metadata">How does Delta Chat protect metadata in messages?</a></li>
<li><a href="#device-seizure">How to protect metadata and contacts when a device is seized?</a></li> <li><a href="#device-seizure">How to protect metadata and contacts when a device is seized?</a></li>
<li><a href="#how-can-i-check-encryption-information">How can i check encryption information?</a></li> <li><a href="#sealedsender">Does Delta Chat support “Sealed Sender”?</a></li>
<li><a href="#how-can-i-check-the-encryption-status-of-messages">How can I check the encryption status of messages?</a></li>
<li><a href="#why-do-i-see-unencrypted-messages">Why do I see unencrypted messages?</a></li>
<li><a href="#how-can-i-get-an-end-to-end-encrypted-chat-with-a-delta-chat-contact-who-sometimes-uses-webmail-or-another-non-autocrypt-e-mail-app">How can i get an end-to-end encrypted chat with a Delta Chat contact who sometimes uses webmail or another non-Autocrypt e-mail app?</a></li>
<li><a href="#how-can-i-ensure-message-end-to-end-encryption-and-deletion">How can I ensure message end-to-end encryption and deletion?</a></li>
<li><a href="#pfs">Does Delta Chat support Perfect Forward Secrecy?</a></li> <li><a href="#pfs">Does Delta Chat support Perfect Forward Secrecy?</a></li>
<li><a href="#is-end-to-end-encryption-of-delta-chat-as-safe-as-signal">Is end-to-end encryption of Delta Chat as safe as Signal?</a></li> <li><a href="#pqc">Does Delta Chat support Post-Quantum-Cryptography?</a></li>
<li><a href="#how-can-i-manually-check-encryption-information">How can I manually check encryption information?</a></li>
<li><a href="#importkey">Can I reuse my existing private key?</a></li> <li><a href="#importkey">Can I reuse my existing private key?</a></li>
<li><a href="#security-audits">Was Delta Chat independently audited for security vulnerabilities?</a></li> <li><a href="#security-audits">Was Delta Chat independently audited for security vulnerabilities?</a></li>
</ul> </ul>
@ -726,10 +723,10 @@ that achieves “instant delivery” of messages for all chatmail servers
including a potential one <a href="https://delta.chat/chatmail#selfhosted">you might setup yourself without our permission</a>. including a potential one <a href="https://delta.chat/chatmail#selfhosted">you might setup yourself without our permission</a>.
Welcome to the power of the interoperable and massive chatmail and e-mail system :)</p> Welcome to the power of the interoperable and massive chatmail and e-mail system :)</p>
<h2 id="encryption-and-security"> <h2 id="e2ee">
Encryption and Security <a href="#encryption-and-security" class="anchor"></a> Encryption and Security <a href="#e2ee" class="anchor"></a>
</h2> </h2>
@ -742,18 +739,26 @@ Welcome to the power of the interoperable and massive chatmail and e-mail system
</h3> </h3>
<p><a href="https://autocrypt.org">Autocrypt</a> is used for automatically <p>Delta Chat uses a <a href="#openpgp-secure">secure subset of the OpenPGP standard</a>
establishing end-to-end encryption with contacts and group chats. to provide automatic end-to-end encryption using these protocols:</p>
Autocrypt uses a limited and <a href="#openpgp-secure">secure subset of the OpenPGP standard</a>.
End-to-End encrypted messages are marked with a padlock
<img style="vertical-align:middle; width:1.2em; margin:1px" src="../lock-icon.png" alt="padlock" />.</p>
<p><a href="https://securejoin.delta.chat/en/latest/new.html">Secure-Join protocols</a> <ul>
are used for establishing chats with guaranteed end-to-end encryption <li>
which protects against network attacks and compromised servers. <p><a href="https://securejoin.delta.chat/en/latest/new.html">Secure-Join</a>
Chats marked with a green checkmark to exchange encryption setup information through QR-code scanning or “invite links”.</p>
<img style="vertical-align:middle; width:1.5em; margin:1px" src="../green-checkmark.png" alt="green checkmark" /> </li>
guarantee end-to-end encrypted messages.</p> <li>
<p><a href="https://autocrypt.org">Autocrypt</a> is used for automatically
establishing end-to-end encryption between contacts and all members of a group chat.</p>
</li>
<li>
<p><a href="https://github.com/chatmail/core/blob/main/spec.md#attaching-a-contact-to-a-message">Sharing a contact to a
chat</a>
enables receivers to use end-to-end encryption with the contact.</p>
</li>
</ul>
<p>Delta Chat does not query, publish or interact with any OpenPGP key servers.</p>
<h3 id="whene2e"> <h3 id="whene2e">
@ -763,28 +768,37 @@ guarantee end-to-end encrypted messages.</p>
</h3> </h3>
<p>All end-to-end encrypted messages carry a padlock:</p> <p>All messages in Delta Chat are <strong>end-to-end encrypted by default</strong>.
Since the Delta Chat Version 2 release series (July 2025)
there are no lock or similar markers on end-to-end encrypted messages, anymore.</p>
<p><img style="width:160px; margin:1px" src="../lock-screenshot.png" alt="padlock in bubble" /></p> <h3 id="can-i-still-receive-or-send-mails-without-end-to-end-encryption">
<p>End-to-end encryption is guaranteed if there is a green checkmark next to the chat title:</p>
<p><img style="width:211px; margin:1px" src="../green-checkmark-screenshot.png" alt="green checkmark in title" /></p>
<h3 id="howtoe2ee">
How can I get guaranteed end-to-end encryption and green checkmarks? <a href="#howtoe2ee" class="anchor"></a> Can i still receive or send mails without end-to-end encryption? <a href="#can-i-still-receive-or-send-mails-without-end-to-end-encryption" class="anchor"></a>
</h3> </h3>
<p>If you have a second communication channel with your chat partner, <p>If you use default <a href="https://chatmail.at/relays">chatmail relays</a>,
like a video chat or a different messenger, it is impossible to receive or send messages without end-to-end encryption.</p>
you can generate an invite link.</p>
<p>If you are together in person, <p>If you instead create a profile using a classic e-mail server,
you can show a QR code to your chat partner.</p> you can send and receive messages without end-to-end encryption.
Such messages lacking end-to-end encryption are marked with an e-mail icon
<img style="vertical-align:middle; width:1.2em; margin:1px" src="../email-icon.png" alt="email" />.</p>
<h3 id="howtoe2ee">
How can I establish a chat with a new contact? <a href="#howtoe2ee" class="anchor"></a>
</h3>
<p>You can send an invite link through another private chat,
show an invitation QR code when next to each other or in a video call,
or click on a “contact” that was shared in a chat.</p>
<ul> <ul>
<li> <li>
@ -799,135 +813,54 @@ on the Delta Chat app main screen.</p>
</li> </li>
</ul> </ul>
<p>Let your chat partner scan the QR image <p>Ask your chat partner to scan the QR image
with their Delta Chat app, with their Delta Chat app,
or click “Copy” or “Share” to create an invite link or click “Copy” or “Share” to create an invite link
and share it with your chat partner.</p> and share it with your chat partner.</p>
<p>Now wait while <a href="https://securejoin.delta.chat/en/latest/new.html#setup-contact-protocol">Secure-Join network messages are exchanged</a> between both devices.</p> <p>Now wait while <a href="https://securejoin.delta.chat/en/latest/new.html#setup-contact-protocol">end-to-end encryption is getting established</a>.</p>
<ul> <ul>
<li> <li>
<p>If both devices are online, <p>If both sides are online, they will soon see a (group or direct) chat
both sides will eventually see a (group or direct) chat with a green checkmark and can start messaging securely.</p>
<img style="vertical-align:middle; width:1.5em; margin:1px" src="../green-checkmark.png" alt="green checkmark" />
next to the title.</p>
</li> </li>
<li> <li>
<p>If one of the devices is offline, the green checkmarks will only <p>If one side is offline or in bad network,
appear later when the device is internet-connected again the ability to chat is delayed until connectivity is restored.</p>
and the Secure-Join network protocol completed.</p>
</li> </li>
</ul> </ul>
<p>Congratulations! <p>Congratulations!
You now will automatically use guaranteed end-to-end encryption You now will automatically use end-to-end encryption
with this contact and both of you can add each other to green-checkmarked groups with this contact.
<img style="vertical-align:middle; width:1.5em; margin:1px" src="../green-checkmark.png" alt="green checkmark" />, If you add each other to chat groups,
thereby automatically spreading guaranteed end-to-end encryption among its members.</p> end-to-end encryption will be established among all members.</p>
<h3 id="e2eeguarantee"> <h3 id="e2eeguarantee">
What does the green checkmark and “guaranteed end-to-end encryption” mean? <a href="#e2eeguarantee" class="anchor"></a> What does the green checkmark in a contact profile mean? <a href="#e2eeguarantee" class="anchor"></a>
</h3> </h3>
<p>Chat titles with green checkmarks <p>A contact profile might show a green checkmark
<img style="vertical-align:middle; width:1.5em; margin:1px" src="../green-checkmark.png" alt="green checkmark" /> <img style="vertical-align:middle; width:1.5em; margin:1px" src="../green-checkmark.png" alt="green checkmark" />
mean that all messages in the chat will be end-to-end encrypted and an “Introduced by” line.
and can not be read or altered by compromised e-mail servers or Internet providers.
Joining green-checkmarked group chats
safely spreads everybody’s encryption information (and green checkmarks)
in a manner that guarantees end-to-end encryption in the group and among members.</p>
<p>Contact profiles with green checkmarks
<img style="vertical-align:middle; width:1.5em; margin:1px" src="../green-checkmark.png" alt="green checkmark" />
mean that messaging a contact is currently guaranteed to be end-to-end encrypted.
Every green-checkmarked contact either did a direct <a href="#howtoe2ee">QR-scan</a> with you Every green-checkmarked contact either did a direct <a href="#howtoe2ee">QR-scan</a> with you
or was introduced by a another green-checkmarked contact. or was introduced by a another green-checkmarked contact.
Introductions happen automatically when adding members to groups. Introductions happen automatically when adding members to groups.
Whoever adds a contact to a green-checkmarked group becomes an introducer Whoever adds a green-checkmarked contact to a group with only green-checkmarked members
to those members who didn’t yet know about the added contact. becomes an introducer.
In a contact profile you can tap on the “Introduced by …” text repeatedly In a contact profile you can tap on the “Introduced by …” text repeatedly
until you get to the one with whom you directly did a <a href="#howtoe2ee">QR-scan</a>.</p> until you get to the one with whom you directly did a <a href="#howtoe2ee">QR-scan</a>.</p>
<p>Note that in a contact profile you may see and tap introducers
but there is no green checkmark in the profile title.
This usually means that the contact <a href="#nocryptanymore">“sent a message from another device”</a>.</p>
<p>For more in-depth discussion of “guaranteed end-to-end encryption” <p>For more in-depth discussion of “guaranteed end-to-end encryption”
please see <a href="https://securejoin.delta.chat/en/latest/new.html">Secure-Join protocols</a> please see <a href="https://securejoin.delta.chat/en/latest/new.html">Secure-Join protocols</a>
and specifically read about “Verified Groups”, the technical term and specifically read about “Verified Groups”, the technical term
of what is called here “green-checkmarked” or “guaranteed end-to-end encrypted” chats.</p> of what is called here “green-checkmarked” or “guaranteed end-to-end encrypted” chats.</p>
<h3 id="nocryptanymore">
A contact “sent a message from another device”, what can i do? <a href="#nocryptanymore" class="anchor"></a>
</h3>
<p>Your chat with a contact lost guaranteed end-to-end encryption.
The green checkmark was removed for this chat and contact when you see this warning.
<strong>If you find the sudden drop of guaranteed end-to-end encryption
surprising for this contact then don’t accept the warning!</strong>
Instead check with your contact through a second channel
like a video call, other messenger or a phone call,
to find out what happened.</p>
<p>If your contact actually caused the drop of guaranteed end-to-end encryption
please see the next paragraphs for common reasons and their mitigations.
Regardless, all other green-checkmarked chats remain guaranteed end-to-end encrypted
even if the contact is a member there.</p>
<p><strong>Your contact is using Delta Chat on a second device (phone or laptop)</strong></p>
<p>If they have another device with a Delta Chat app running,
they should remove the profile from the new device
and add it <a href="#multiclient">as a second device as described here</a>.
As soon as they message you afterwards, the warning will be gone
and guaranteed encryption is established with both devices of your contact.</p>
<p><strong>Your contact reinstalled Delta Chat using their old account login</strong></p>
<p>If they have <a href="#backup">a backup file</a>,
they should remove the profile from the new device
and rather import the backup file to re-create their profile.
As soon as they message you afterwards, the warning will be gone
and guaranteed encryption is re-established for this contact.</p>
<p>If they don’t have a backup file, it’s best to perform a <a href="#howtoe2ee">QR scan</a>
with your chat partner to re-establish guaranteed end-to-end encryption.</p>
<p><strong>Your contact sent a mail through a webmail interface or another e-mail app
and will get back to using Delta Chat soon again.</strong></p>
<p>If you are sure that the contact sometimes uses webmail,
or another mail app lacking end-to-end encryption,
then you may accept the warning.
As soon as your contact uses Delta Chat again,
guaranteed end-to-end encryption will be automatically re-established.</p>
<p><strong>Your contact stopped using Delta Chat entirely</strong></p>
<p>Sometimes remaining in contact is more important than end-to-end encryption.
<a href="#tls">“Transport Layer Encryption” (TLS)</a> may still meaningfully protect
the confidentiality of your messages between your device and the e-mail server.
But without end-to-end encryption you and your contact are trusting your e-mail server
to not read or manipulate your messages, and to not hand them to third parties.</p>
<p>In any case, you can not do much else than accept the warning.
Please also remove the contact from any active green-checkmarked group
which you can find in “Chats in Common” in the Contact profile.
This spares your contact from getting “unreadable” messages.</p>
<p>If the contact removed Delta Chat because of buggy or undesirable behaviour,
please consider posting to our <a href="https://support.delta.chat">support forum</a>
to help us identify and address common problems. Thanks!</p>
<h3 id="are-attachments-pictures-files-audio-etc-end-to-end-encrypted"> <h3 id="are-attachments-pictures-files-audio-etc-end-to-end-encrypted">
@ -952,8 +885,7 @@ and attachment metadata such as filenames.</p>
</h3> </h3>
<p>Yes, Delta Chat uses a secure subset of OpenPGP <p>Yes, Delta Chat uses a secure subset of OpenPGP
and only displays a padlock security indicator on a message requiring the whole message to be properly encrypted and signed.
if the whole message is properly encrypted and signed.
For example, “Detached signatures” are not treated as secure.</p> For example, “Detached signatures” are not treated as secure.</p>
<p>OpenPGP is not insecure by itself. <p>OpenPGP is not insecure by itself.
@ -974,7 +906,7 @@ which was thankfully adopted in summer 2023.</p>
<h3 id="openpgp-alternatives"> <h3 id="openpgp-alternatives">
Did you consider using alternatives to OpenPGP for end-to-end -encryption? <a href="#openpgp-alternatives" class="anchor"></a> Did you consider using alternatives to OpenPGP for end-to-end-encryption? <a href="#openpgp-alternatives" class="anchor"></a>
</h3> </h3>
@ -1017,17 +949,15 @@ as defined by the Autocrypt Level 1 specification.</p>
<h3 id="tls"> <h3 id="tls">
Is a message exposed in cleartext if end-to-end encryption is not available? <a href="#tls" class="anchor"></a> Are messages marked with the mail icon exposed on the Internet? <a href="#tls" class="anchor"></a>
</h3> </h3>
<p>Even if your messages are not guaranteed to be end-to-end encrypted, <p>If you are sending or receiving e-mail messages without end-to-end encryption (using a classic e-mail server),
they are still protected from Internet providers like cell or cable companies. they are still protected from cell or cable companies who can not read or modify your e-mail messages.
However, your and your recipient’s e-mail providers But both your and your recipient’s e-mail providers
may read, analyze or even modify your messages, may read, analyze or modify your messages, including any attachments.</p>
including any attachments,
if they are not end-to-end encrypted.</p>
<p>Delta Chat by default uses strict <p>Delta Chat by default uses strict
<a href="https://en.wikipedia.org/wiki/Transport_Layer_Security">TLS encryption</a> <a href="https://en.wikipedia.org/wiki/Transport_Layer_Security">TLS encryption</a>
@ -1040,10 +970,6 @@ then transport encryption will be enforced between e-mail providers
in which case Delta Chat communications will never be exposed in cleartext to the Internet in which case Delta Chat communications will never be exposed in cleartext to the Internet
even if the message was not end-to-end encrypted.</p> even if the message was not end-to-end encrypted.</p>
<p>Note that <a href="#howtoe2ee">maintaining guaranteed end-to-end encryption</a> on top of TLS encryption
provides pervasive safety between your and the recipient’s devices.
Not even your e-mail or Internet provider will be able to read or modify your messages.</p>
<h3 id="message-metadata"> <h3 id="message-metadata">
@ -1052,25 +978,25 @@ Not even your e-mail or Internet provider will be able to read or modify your me
</h3> </h3>
<p>Delta Chat protects most message metadata by putting the following information <p>Unlike most other messengers,
into the end-to-end encrypted part of messages:</p> Delta Chat apps do not store any metadata about contacts or groups on servers, also not in encrypted form.
Instead, all group metadata is end-to-end encrypted and stored on end-user devices, only.</p>
<p>E-mail Servers can therefore only see</p>
<ul> <ul>
<li>Subject line</li> <li>
<li>Group avatar and name</li> <p>the message date,</p>
<li>MDN (read receipt) requests (<code class="language-plaintext highlighter-rouge">Chat-Disposition-Notification-To</code>)</li> </li>
<li>Disappearing message timer (<code class="language-plaintext highlighter-rouge">Ephemeral-Timer</code>)</li> <li>
<li><code class="language-plaintext highlighter-rouge">Chat-Group-Member-Removed</code>, <code class="language-plaintext highlighter-rouge">Chat-Group-Member-Added</code></li> <p>sender and receiver addresses</p>
<li><code class="language-plaintext highlighter-rouge">Secure-Join</code> header containing secure join commands</li> </li>
<li>Notification about enabling location streaming</li> <li>
<li>WebRTC room URL</li> <p>and message size.</p>
</li>
</ul> </ul>
<p>E-Mail servers do not get access to this protected metadata <p>All other message, contact and group metadata resides in the end-to-end encrypted part of messages.</p>
but they do see the message date as well as the message size,
and, more importantly, the sender and receiver addresses.
E-mail servers need receiver addresses to route and
deliver messages to recipient’s devices.</p>
<h3 id="device-seizure"> <h3 id="device-seizure">
@ -1082,96 +1008,34 @@ deliver messages to recipient’s devices.</p>
<p>Both for protecting against metadata-collecting e-mail servers <p>Both for protecting against metadata-collecting e-mail servers
as well as against the threat of device seizure as well as against the threat of device seizure
we recommend to use a <a href="https://delta.chat/chatmail">chatmail server</a> we recommend to use a <a href="https://chatmail.at/relays">chatmail relay</a>
to create pseudonymous temporary profiles through QR-code scans. to create chat profiles using random e-mail addresses for transport.
Note that Delta Chat apps on all platforms support multiple profiles Note that Delta Chat apps on all platforms support multiple profiles
so you can easily use situation-specific profiles next to your “main” profile so you can easily use situation-specific profiles next to your “main” profile
with the knowledge that all their data, along with all metadata, will be deleted. with the knowledge that all their data, along with all metadata, will be deleted.
Moreover, if a device is seized then contacts using temporary profiles Moreover, if a device is seized then chat contacts using short-lived profiles
can not be identified easily, as compared to messengers which reveal can not be identified easily.</p>
phone numbers in chat groups which in turn are often associated with legal identities.</p>
<h3 id="how-can-i-check-encryption-information"> <h3 id="sealedsender">
How can i check encryption information? <a href="#how-can-i-check-encryption-information" class="anchor"></a> Does Delta Chat support “Sealed Sender”? <a href="#sealedsender" class="anchor"></a>
</h3> </h3>
<p>You may check the end-to-end encryption status manually in the “Encryption” dialog <p>No, not yet.</p>
(user profile on Android/iOS or right-click a user’s chat-list item on desktop).
Delta Chat shows two fingerprints there.
If the same fingerprints appear on your own and your contact’s device,
the connection is safe.</p>
<h3 id="how-can-i-check-the-encryption-status-of-messages"> <p>The Signal messenger introduced <a href="https://signal.org/blog/sealed-sender/">“Sealed Sender” in 2018</a>
to keep their server infrastructure ignorant of who is sending a message to a set of recipients.
It is particularly important because the Signal server knows the mobile number of each account,
which is usually associated with a passport identity.</p>
<p>Even if <a href="https://chatmail.at/relays">chatmail relays</a>
How can I check the encryption status of messages? <a href="#how-can-i-check-the-encryption-status-of-messages" class="anchor"></a> do not ask for any private data (including no phone numbers),
it might still be worthwhile to protect relational metadata between addresses.
We don’t foresee bigger problems in using random throw-away e-mail addresses for sealed sending
</h3> but an implementation has not been agreed as a priority yet.</p>
<p>A little <strong>padlock</strong> in a message bubble denotes
that the message was properly end-to-end encrypted from the given sender.
If there is <strong>no padlock</strong>, the message was not properly end-to-end encrypted
most likely because the sender uses an app or webmail interface
without support for end-to-end–encryption.</p>
<h3 id="why-do-i-see-unencrypted-messages">
Why do I see unencrypted messages? <a href="#why-do-i-see-unencrypted-messages" class="anchor"></a>
</h3>
<p>If a contact uses a non-Autocrypt e-mail app,
all messages involving this contact (in a group or 1:1 chat)
will not be end-to-end encrypted, and thus not show a “padlock” with messages.
Note that even if your contacts use Delta Chat on their account,
they might also use a non-Autocrypt e-mail app on that account
which then may cause intermittently unencrypted messages.
Replying unencrypted to unencrypted messages is mandated by Autocrypt
to prevent unreadable messages on the side of your contacts
and their non-Autocrypt e-mail app.</p>
<h3 id="how-can-i-get-an-end-to-end-encrypted-chat-with-a-delta-chat-contact-who-sometimes-uses-webmail-or-another-non-autocrypt-e-mail-app">
How can i get an end-to-end encrypted chat with a Delta Chat contact who sometimes uses webmail or another non-Autocrypt e-mail app? <a href="#how-can-i-get-an-end-to-end-encrypted-chat-with-a-delta-chat-contact-who-sometimes-uses-webmail-or-another-non-autocrypt-e-mail-app" class="anchor"></a>
</h3>
<p>If you need a safely end-to-end encrypted chat with a contact
who is using their e-mail account both with Delta Chat and non-Autocrypt apps (e.g. webmail),
it’s best to setup <a href="#howtoe2ee">guaranteed end-to-end encryption with them</a>
and then create a guaranteed end-to-end encrypted group chat with you two as members.
In this group chat all messages will be end-to-end encrypted
even if the direct chat between you two has a
<a href="#nocryptanymore">“… sent a message from another device”</a> warning.</p>
<h3 id="how-can-i-ensure-message-end-to-end-encryption-and-deletion">
How can I ensure message end-to-end encryption and deletion? <a href="#how-can-i-ensure-message-end-to-end-encryption-and-deletion" class="anchor"></a>
</h3>
<p>The best way to ensure every message is end-to-end encrypted,
and metadata deleted as quickly as possible
is <a href="#howtoe2ee">using chats with guaranteed end-to-end encryption</a>
and turning on <a href="#ephemeralmsgs">disappearing messages</a>.</p>
<p>Guaranteed end-to-end encrypted chats protect against <a href="https://en.wikipedia.org/wiki/Man-in-the-middle_attack">MITM attacks</a>
and turning on disappearing messages deletes the messages
on the server after a user-configured time.</p>
<p>If you don’t need a longer-lived copy of your messages on the server,
you can also turn on <a href="#delold">“delete messages from server automatically”</a>.</p>
<h3 id="pfs"> <h3 id="pfs">
@ -1181,45 +1045,52 @@ you can also turn on <a href="#delold">“delete messages from server automatica
</h3> </h3>
<p>No, Delta Chat doesn’t support Perfect Forward Secrecy (PFS). <p>No, not yet.</p>
This means that if your Delta Chat private decryption key is leaked,
<p>Delta Chat today doesn’t support Perfect Forward Secrecy (PFS).
This means that if your private decryption key is leaked,
and someone has collected your prior in-transit messages, and someone has collected your prior in-transit messages,
they will be able to decrypt and read them using the leaked decryption key.</p> they will be able to decrypt and read them using the leaked decryption key.
Note that Forward Secrecy only increases security if you delete messages.
Otherwise, someone obtaining your decryption keys
is typically also able to get all your non-deleted messages
and doesn’t even need to decrypt any previously collected messages.</p>
<p>Note, however, that if anyone obtains to your decryption keys, <p>We designed a Forward Secrecy approach that withstood
they will typically also be able to obtain your messages, initial examination from some cryptographers and implementation experts
irrespective if Perfect Forward Secrecy is in place or not. but is pending a more formal write up
The typical real-world situation for leaked decryption keys is device seizure to ascertain it reliably works in federated messaging and with multi-device usage,
which we discuss in our answer <a href="#device-seizure">on metadata and device seizure</a>.</p> before it could be implemented in <a href="https://github.com/chatmail/core">chatmail core</a>,
which would make it available in all <a href="https://chatmail.at/clients">chatmail clients</a>.</p>
<p>It is possible that Delta Chat evolves to support Perfect Forward Secrecy, <h3 id="pqc">
because OpenPGP is just a container for encrypted messages
but encryption key management (and thus key rotation or key “ratcheting”)
could be organized in flexible ways.
See <a href="https://gitlab.com/sequoia-pgp/openpgp-dr">Seqouia’s PFS prototype</a>
for existing experiments in the OpenPGP implementor community.</p>
<h3 id="is-end-to-end-encryption-of-delta-chat-as-safe-as-signal">
Is end-to-end encryption of Delta Chat as safe as Signal? <a href="#is-end-to-end-encryption-of-delta-chat-as-safe-as-signal" class="anchor"></a> Does Delta Chat support Post-Quantum-Cryptography? <a href="#pqc" class="anchor"></a>
</h3> </h3>
<p>It depends on what is important to you. <p>No, not yet.</p>
Delta Chat <a href="#pfs">does not support PFS</a> like Signal does
but it provides <a href="#e2eeguarantee">guaranteed end-to-end encrypted chats</a>
that are safe against compromised servers or corrupted networks.
Signal and most other PFS-supporting messengers do not provide
a practical scheme for protecting chat groups from network attacks
which are arguably more worrisome
than a potential attacker who seizes your phone and private encryption setup
but somehow not your messages, yet has a full record of all
past encrypted messages.</p>
<p>In any case, Delta Chat’s end-to-end encryption uses a <a href="#openpgp-secure">secure subset of OpenPGP</a> <p>Delta Chat uses the Rust OpenPGP library <a href="https://github.com/rpgp/rpgp">rPGP</a>
which has been <a href="https://delta.chat/assets/blog/2019-first-security-review.pdf">independently security-audited</a>.</p> which supports the latest <a href="https://datatracker.ietf.org/doc/draft-ietf-openpgp-pqc/">IETF Post-Quantum-Cryptography OpenPGP draft</a>.
We aim to add PQC support in <a href="https://github.com/chatmail/core">chatmail core</a> after the draft is finalized at the IETF
in collaboration with other OpenPGP implementers.</p>
<h3 id="how-can-i-manually-check-encryption-information">
How can I manually check encryption information? <a href="#how-can-i-manually-check-encryption-information" class="anchor"></a>
</h3>
<p>You may check the end-to-end encryption status manually in the “Encryption” dialog
(user profile on Android/iOS or right-click a user’s chat-list item on desktop).
Delta Chat shows two fingerprints there.
If the same fingerprints appear on your own and your contact’s device,
the connection is safe.</p>
<h3 id="importkey"> <h3 id="importkey">
@ -1254,7 +1125,7 @@ from most recent to older:</p>
<li> <li>
<p>2024 December, an <a href="https://github.com/rpgp/docs/blob/main/audits/NGI%20Core%20rPGP%20penetration%20test%20report%202024%201.0.pdf">NLNET-commissioned Evaluation of <p>2024 December, an <a href="https://github.com/rpgp/docs/blob/main/audits/NGI%20Core%20rPGP%20penetration%20test%20report%202024%201.0.pdf">NLNET-commissioned Evaluation of
rPGP</a> by <a href="https://www.radicallyopensecurity.com/">Radically Open Security</a> took place. rPGP</a> by <a href="https://www.radicallyopensecurity.com/">Radically Open Security</a> took place.
rPGP serves as the end-to-end encyption <a href="https://openpgp.org">OpenPGP</a> engine of Delta Chat. rPGP serves as the end-to-end encryption <a href="https://openpgp.org">OpenPGP</a> engine of Delta Chat.
Two advisories were released related to the findings of this audit:</p> Two advisories were released related to the findings of this audit:</p>
<ul> <ul>
@ -1648,6 +1519,11 @@ would be done by the Delta Chat app.</p>
</h3> </h3>
<p>Note:
Changing email addresses is temporarily disabled
because of ongoing changes to the DeltaChat core.
It should be available again in a few months.</p>
<ol> <ol>
<li> <li>
<p>Change your address in “Settings → Advanced → Password and Account” and <p>Change your address in “Settings → Advanced → Password and Account” and

461
src/main/assets/help/it/help.html
View file

@ -36,27 +36,24 @@
<li><a href="#perché-delta-chat-si-integra-con-i-servizi-push-centralizzati-proprietari-di-applegoogle">Perché Delta Chat si integra con i servizi push centralizzati proprietari di Apple/Google?</a></li> <li><a href="#perché-delta-chat-si-integra-con-i-servizi-push-centralizzati-proprietari-di-applegoogle">Perché Delta Chat si integra con i servizi push centralizzati proprietari di Apple/Google?</a></li>
</ul> </ul>
</li> </li>
<li><a href="#crittografia-e-sicurezza">Crittografia e Sicurezza</a> <li><a href="#e2ee">Crittografia e Sicurezza</a>
<ul> <ul>
<li><a href="#quali-standards-vengono-utilizzati-per-la-crittografia-end-to-end">Quali standards vengono utilizzati per la crittografia end-to-end?</a></li> <li><a href="#quali-standards-vengono-utilizzati-per-la-crittografia-end-to-end">Quali standards vengono utilizzati per la crittografia end-to-end?</a></li>
<li><a href="#whene2e">Come posso sapere se i messaggi sono crittografati end-to-end?</a></li> <li><a href="#whene2e">Come posso sapere se i messaggi sono crittografati end-to-end?</a></li>
<li><a href="#howtoe2ee">Come posso ottenere la crittografia end-to-end garantita e i segni di spunta verdi?</a></li> <li><a href="#posso-ancora-ricevere-o-inviare-mails-senza-la-crittografia-end-to-end">Posso ancora ricevere o inviare mails senza la crittografia end-to-end?</a></li>
<li><a href="#e2eeguarantee">Cosa significano il segno di spunta verde e la “crittografia end-to-end garantita”?</a></li> <li><a href="#howtoe2ee">Come posso stabilire una chat con un nuovo contatto?</a></li>
<li><a href="#nocryptanymore">Un contatto “ha inviato un messaggio da un altro dispositivo”, cosa posso fare?</a></li> <li><a href="#e2eeguarantee">Cosa significa il segno di spunta verde nel profilo di un contatto?</a></li>
<li><a href="#gli-allegati-immagini-file-audio-ecc-sono-crittografati-end-to-end">Gli allegati (immagini, file, audio, ecc.) sono crittografati end-to-end?</a></li> <li><a href="#gli-allegati-immagini-file-audio-ecc-sono-crittografati-end-to-end">Gli allegati (immagini, file, audio, ecc.) sono crittografati end-to-end?</a></li>
<li><a href="#openpgp-secure">OpenPGP è sicuro?</a></li> <li><a href="#openpgp-secure">OpenPGP è sicuro?</a></li>
<li><a href="#openpgp-alternative">Avete considerato l’utilizzo di alternative a OpenPGP per la crittografia end-to-end?</a></li> <li><a href="#openpgp-alternatives">Avete considerato l’utilizzo di alternative a OpenPGP per la crittografia end-to-end?</a></li>
<li><a href="#delta-chat-è-vulnerabile-agli-efail">Delta Chat è vulnerabile agli EFAIL?</a></li> <li><a href="#delta-chat-è-vulnerabile-agli-efail">Delta Chat è vulnerabile agli EFAIL?</a></li>
<li><a href="#tls">Un messaggio viene esposto in chiaro se la crittografia end-to-end non è disponibile?</a></li> <li><a href="#tls">I messaggi contrassegnati dall’icona della posta sono esposti su Internet?</a></li>
<li><a href="#message-metadata">In che modo Delta Chat protegge i metadati nei messaggi?</a></li> <li><a href="#message-metadata">In che modo Delta Chat protegge i metadati nei messaggi?</a></li>
<li><a href="#device-seizure">Come proteggere i metadati e contatti quando un dispositivo viene sequestrato?</a></li> <li><a href="#device-seizure">Come proteggere i metadati e contatti quando un dispositivo viene sequestrato?</a></li>
<li><a href="#come-posso-verificare-le-informazioni-di-crittografia">Come posso verificare le informazioni di crittografia?</a></li> <li><a href="#sealedsender">Does Delta Chat support “Sealed Sender”?</a></li>
<li><a href="#come-posso-verificare-lo-stato-di-crittografia-dei-messaggi">Come posso verificare lo stato di crittografia dei messaggi?</a></li>
<li><a href="#perché-vedo-messaggi-non-crittografati">Perché vedo messaggi non crittografati?</a></li>
<li><a href="#come-posso-ottenere-una-chat-crittografata-end-to-end-con-un-contatto-delta-chat-che-a-volte-utilizza-la-webmail-o-unaltra-app-e-mail-non-autocrypt">Come posso ottenere una chat crittografata end-to-end con un contatto Delta Chat che a volte utilizza la webmail o un’altra app e-mail non Autocrypt?</a></li>
<li><a href="#come-posso-garantire-la-crittografia-e-leliminazione-end-to-end-dei-messaggi">Come posso garantire la crittografia e l’eliminazione end-to-end dei messaggi?</a></li>
<li><a href="#pfs">Delta Chat supporta Perfect Forward Secrecy?</a></li> <li><a href="#pfs">Delta Chat supporta Perfect Forward Secrecy?</a></li>
<li><a href="#la-crittografia-end-to-end-di-delta-chat-è-sicura-quanto-quella-di-signal">La crittografia end-to-end di Delta Chat è sicura quanto quella di Signal?</a></li> <li><a href="#pqc">Does Delta Chat support Post-Quantum-Cryptography?</a></li>
<li><a href="#how-can-i-manually-check-encryption-information">How can I manually check encryption information?</a></li>
<li><a href="#importkey">Posso riutilizzare la mia chiave privata esistente?</a></li> <li><a href="#importkey">Posso riutilizzare la mia chiave privata esistente?</a></li>
<li><a href="#security-audits">Delta Chat è stata verificata in modo indipendente per le vulnerabilità di sicurezza?</a></li> <li><a href="#security-audits">Delta Chat è stata verificata in modo indipendente per le vulnerabilità di sicurezza?</a></li>
</ul> </ul>
@ -90,7 +87,7 @@
<ul> <ul>
<li><a href="#di-quali-autorizzazioni-ha-bisogno-delta-chat">Di quali autorizzazioni ha bisogno Delta Chat?</a></li> <li><a href="#di-quali-autorizzazioni-ha-bisogno-delta-chat">Di quali autorizzazioni ha bisogno Delta Chat?</a></li>
<li><a href="#delta-chat-funziona-con-il-mio-fornitore-e-mail">Delta Chat funziona con il <em>mio</em> fornitore e-mail?</a></li> <li><a href="#delta-chat-funziona-con-il-mio-fornitore-e-mail">Delta Chat funziona con il <em>mio</em> fornitore e-mail?</a></li>
<li><a href="#i-want-to-manage-my-own-server-for-delta-chat-what-do-you-recommend">I want to manage my own server for Delta Chat. What do you recommend?</a></li> <li><a href="#vorrei-gestire-il-mio-server-per-delta-chat-cosa-mi-consigliate">Vorrei gestire il mio server per Delta Chat. Cosa mi consigliate?</a></li>
<li><a href="#perché-devo-inserire-la-mia-password-e-mail-in-delta-chat-è-sicuro">Perché devo inserire la mia password E-Mail in Delta Chat? È sicuro?</a></li> <li><a href="#perché-devo-inserire-la-mia-password-e-mail-in-delta-chat-è-sicuro">Perché devo inserire la mia password E-Mail in Delta Chat? È sicuro?</a></li>
<li><a href="#quali-messaggi-vengono-mostrati-in-delta-chat">Quali messaggi vengono mostrati in Delta Chat?</a></li> <li><a href="#quali-messaggi-vengono-mostrati-in-delta-chat">Quali messaggi vengono mostrati in Delta Chat?</a></li>
<li><a href="#delta-chat-supporta-le-e-mail-html">Delta Chat supporta le e-mail HTML?</a></li> <li><a href="#delta-chat-supporta-le-e-mail-html">Delta Chat supporta le e-mail HTML?</a></li>
@ -719,10 +716,10 @@ che consente la “consegna istantanea” dei messaggi a tutti i server chatmail
incluso uno potenziale <a href="https://delta.chat/chatmail#selfhosted">potresti configurarlo tu stesso senza la nostra autorizzazione</a>. incluso uno potenziale <a href="https://delta.chat/chatmail#selfhosted">potresti configurarlo tu stesso senza la nostra autorizzazione</a>.
Benvenuti nella potenza del sistema interoperabile e massiccio di chatmail ed e-mail :)</p> Benvenuti nella potenza del sistema interoperabile e massiccio di chatmail ed e-mail :)</p>
<h2 id="crittografia-e-sicurezza"> <h2 id="e2ee">
Crittografia e Sicurezza <a href="#crittografia-e-sicurezza" class="anchor"></a> Crittografia e Sicurezza <a href="#e2ee" class="anchor"></a>
</h2> </h2>
@ -735,15 +732,26 @@ Benvenuti nella potenza del sistema interoperabile e massiccio di chatmail ed e-
</h3> </h3>
<p><a href="https://autocrypt.org">Autocrypt</a> viene utilizzato automaticamente per stabilire la crittografia end-to-end con contatti e chat di gruppo. Autocrypt utilizza un <a href="#openpgp-secure">sottoinsieme limitato e sicuro dello standard OpenPGP</a>. I messaggi crittografati end-to-end sono contrassegnati da un lucchetto <p>Delta Chat utilizza un <a href="#openpgp-secure">sottoinsieme sicuro dello standard OpenPGP</a>
<img style="vertical-align:middle; width:1.2em; margin:1px" src="../lock-icon.png" alt="padlock" />.</p> per fornire la crittografia end-to-end automatica utilizzando questi protocolli:</p>
<p><a href="https://securejoin.delta.chat/en/latest/new.html">Protocolli Secure-Join</a> <ul>
vengono utilizzati per stabilire chat con crittografia end-to-end garantita <li>
che protegge dagli attacchi di rete e dai server compromessi. <p><a href="https://securejoin.delta.chat/en/latest/new.html">Secure-Join</a>
Chat contrassegnata da un segno di spunta verde per scambiare informazioni sulla configurazione della crittografia tramite la scansione del codice QR o i “link di invito”.</p>
<img style="vertical-align:middle; width:1.5em; margin:1px" src="../green-checkmark.png" alt="green checkmark" /> </li>
garantisce messaggi crittografati end-to-end.</p> <li>
<p><a href="https://autocrypt.org">Autocrypt</a> viene utilizzato per stabilire
automaticamente la crittografia end-to-end tra i contatti e tutti i membri di una chat di gruppo.</p>
</li>
<li>
<p><a href="https://github.com/chatmail/core/blob/main/spec.md#attaching-a-contact-to-a-message">Condivisione di un contatto con una
chat</a>
consente ai destinatari di utilizzare la crittografia end-to-end con il contatto.</p>
</li>
</ul>
<p>Delta Chat non esegue query, pubblica o interagisce con alcun server di chiavi OpenPGP.</p>
<h3 id="whene2e"> <h3 id="whene2e">
@ -753,28 +761,37 @@ garantisce messaggi crittografati end-to-end.</p>
</h3> </h3>
<p>Tutti i messaggi crittografati end-to-end portano un lucchetto:</p> <p>Tutti i messaggi in Delta Chat sono <strong>crittografati end-to-end per impostazione predefinita</strong>.
Dalla serie di rilasci della Versione 2 di Delta Chat (Luglio 2025)
non ci sono più lucchetti o marcatori simili, sui messaggi crittografati end-to-end.</p>
<p><img style="width:160px; margin:1px" src="../lock-screenshot.png" alt="padlock in bubble" /></p> <h3 id="posso-ancora-ricevere-o-inviare-mails-senza-la-crittografia-end-to-end">
<p>La crittografia end-to-end è garantita se è presente un segno di spunta verde accanto al titolo della chat:</p>
<p><img style="width:211px; margin:1px" src="../green-checkmark-screenshot.png" alt="green checkmark in title" /></p>
<h3 id="howtoe2ee">
Come posso ottenere la crittografia end-to-end garantita e i segni di spunta verdi? <a href="#howtoe2ee" class="anchor"></a> Posso ancora ricevere o inviare mails senza la crittografia end-to-end? <a href="#posso-ancora-ricevere-o-inviare-mails-senza-la-crittografia-end-to-end" class="anchor"></a>
</h3> </h3>
<p>Se disponi di un secondo canale di comunicazione con il tuo partner di chat, <p>Se si utilizzano i <a href="https://chatmail.at/relays">relays di chatmail</a>,
come una chat video o un altro messenger, è impossibile ricevere o inviare messaggi senza la crittografia end-to-end.</p>
puoi generare un link d’invito.</p>
<p>Se siete insieme di persona, <p>Se invece si crea un profilo utilizzando un server di posta elettronica classico,
puoi mostrare un codice QR al tuo partner di chat.</p> è possibile inviare e ricevere messaggi senza crittografia end-to-end.
I messaggi privi di crittografia end-to-end sono contrassegnati da un’icona e-mail<br />
<img style="vertical-align:middle; width:1.2em; margin:1px" src="../email-icon.png" alt="email" />.</p>
<h3 id="howtoe2ee">
Come posso stabilire una chat con un nuovo contatto? <a href="#howtoe2ee" class="anchor"></a>
</h3>
<p>È possibile inviare un link di invito attraverso un’altra chat privata,
mostrare un codice QR di invito quando si è vicini o in una videochiamata,
o fare clic su un “contatto” condiviso in una chat.</p>
<ul> <ul>
<li> <li>
@ -783,139 +800,60 @@ tocca il titolo del gruppo di chat per vedere l’elenco dei membri,
e seleziona “Codice QR di Invito”.</p> e seleziona “Codice QR di Invito”.</p>
</li> </li>
<li> <li>
<p>Per <strong>inviti diretti alla chat 1:1</strong>, <p>Per <strong>inviti diretti alla chat 1:1</strong>,<br />
tocca l’icona del codice QR <img style="vertical-align:middle; width:1.8em; margin:1px" src="../qr-icon.png" /> toccare l’icona del Codice QR <img style="vertical-align:middle; width:1.8em; margin:1px" src="../qr-icon.png" />
nella schermata principale dell’app Delta Chat.</p> nella schermata principale dell’app Delta Chat.</p>
</li> </li>
</ul> </ul>
<p>Lascia che il tuo partner di chat esegua la scansione dell’immagine QR <p>Chiedere al partner di chat di scansionare l’immagine QR
con la loro app Delta Chat, con la propria app Delta Chat,
oppure fai clic su “Copia” o “Condividi” per creare un collegamento di invito oppure cliccare su “Copia” o “Condividi” per creare un link di invito
e condividilo con il tuo partner di chat.</p> e condividerlo con il partner di chat.</p>
<p>Ora attendi che <a href="https://securejoin.delta.chat/en/latest/new.html#setup-contact-protocol">i messaggi di rete Secure-Join vengano scambiati</a> tra entrambi i dispositivi.</p> <p>Ora aspettate che <a href="https://securejoin.delta.chat/en/latest/new.html#setup-contact-protocol">la crittografia end-to-end venga stabilita</a>.</p>
<ul> <ul>
<li> <li>
<p>Se entrambi i dispositivi sono online, <p>Se entrambe le parti sono online, vedranno presto una chat (di gruppo o diretta)
entrambe le parti vedranno eventualmente una chat (di gruppo o diretta) con un segno di spunta verde e potranno iniziare a messaggiare in modo sicuro.</p>
<img style="vertical-align:middle; width:1.5em; margin:1px" src="../green-checkmark.png" alt="green checkmark" />
accanto al titolo.</p>
</li> </li>
<li> <li>
<p>Se uno dei dispositivi è offline, verranno visualizzati solo i segni di spunta verdi <p>Se una delle due parti è offline o con rete scadente,
verranno visualizzati in seguito quando il dispositivo sarà nuovamente connesso a Internet la possibilità di chattare viene ritardata fino al ripristino della connettività.</p>
e il protocollo di rete Secure-Join è stato completato.</p>
</li> </li>
</ul> </ul>
<p>Congratulazioni! <p>Congratulazioni!
Ora utilizzerai automaticamente la crittografia end-to-end garantita Ora utilizzerai automaticamente la crittografia end-to-end
con questo contatto potete aggiungervi a vicenda nei gruppi contrassegnati da un segno di spunta verde con questo contatto.
<img style="vertical-align:middle; width:1.5em; margin:1px" src="../green-checkmark.png" alt="green checkmark" />, Se vi aggiungete a gruppi di chat,
diffondendo così automaticamente la crittografia end-to-end garantita tra i suoi membri.</p> la crittografia end-to-end sarà stabilita tra tutti i membri.</p>
<h3 id="e2eeguarantee"> <h3 id="e2eeguarantee">
Cosa significano il segno di spunta verde e la “crittografia end-to-end garantita”? <a href="#e2eeguarantee" class="anchor"></a> Cosa significa il segno di spunta verde nel profilo di un contatto? <a href="#e2eeguarantee" class="anchor"></a>
</h3> </h3>
<p>Titoli di chat con segni di spunta verde <p>A contact profile might show a green checkmark
<img style="vertical-align:middle; width:1.5em; margin:1px" src="../green-checkmark.png" alt="green checkmark" /> <img style="vertical-align:middle; width:1.5em; margin:1px" src="../green-checkmark.png" alt="green checkmark" />
significa che tutti i messaggi nella chat saranno crittografati end-to-end and an “Introduced by” line.
e non possono essere letti o modificati da server di e-mail o provider Internet compromessi. Every green-checkmarked contact either did a direct <a href="#howtoe2ee">QR-scan</a> with you
Partecipare alle chat di gruppo contrassegnate da un segno di spunta verde diffonde in modo sicuro le informazioni di crittografia di tutti (e i segni di spunta verdi) or was introduced by a another green-checkmarked contact.
in modo da garantire la crittografia end-to-end nel gruppo e tra i membri.</p> Introductions happen automatically when adding members to groups.
Whoever adds a green-checkmarked contact to a group with only green-checkmarked members
<p>Profili di contatto con segni di spunta verdi becomes an introducer.
<img style="vertical-align:middle; width:1.5em; margin:1px" src="../green-checkmark.png" alt="green checkmark" /> In a contact profile you can tap on the “Introduced by …” text repeatedly
significa che attualmente è garantita la crittografia end-to-end dei messaggi a un contatto. until you get to the one with whom you directly did a <a href="#howtoe2ee">QR-scan</a>.</p>
Ogni contatto contrassegnato dal segno di spunta verde ha effettuato una <a href="#howtoe2ee">scansione QR</a> diretta con te
o è stato presentato da un altro contatto contrassegnato da un segno di spunta verde.
Le presentazioni avvengono automaticamente quando si aggiungono membri ai gruppi.
Chi aggiunge un contatto a un gruppo contrassegnato da un segno di spunta verde diventa un introduttore
a quei membri che non erano ancora a conoscenza del contatto aggiunto. In un profilo di contatto è possibile toccare ripetutamente il testo “Presentato da…”.
fino ad arrivare a quello con cui hai effettuato direttamente una <a href="#howtoe2ee">scansione QR</a>.</p>
<p>Tieni presente che nel profilo di un contatto potresti vedere e toccare gli introduttori
ma non c’è il segno di spunta verde nel titolo del profilo.
Questo di solito significa che il contatto <a href="#nocryptanymore">“ha inviato un messaggio da un altro dispositivo”</a>.</p>
<p>Per una discussione più approfondita sulla “crittografia end-to-end garantita” <p>Per una discussione più approfondita sulla “crittografia end-to-end garantita”
consultare <a href="https://securejoin.delta.chat/en/latest/new.html">Protocolli Secure-Join</a> consultare <a href="https://securejoin.delta.chat/en/latest/new.html">Protocolli Secure-Join</a>
e leggi nello specifico i “Gruppi Verificati”, il termine tecnico e leggi nello specifico i “Gruppi Verificati”, il termine tecnico
di quelle che qui vengono chiamate chat “con segno di spunta verde” o “crittografate end-to-end garantite”.</p> di quelle che qui vengono chiamate chat “con segno di spunta verde” o “crittografate end-to-end garantite”.</p>
<h3 id="nocryptanymore">
Un contatto “ha inviato un messaggio da un altro dispositivo”, cosa posso fare? <a href="#nocryptanymore" class="anchor"></a>
</h3>
<p>La tua chat con un contatto che ha perso la crittografia end-to-end garantita.
Il segno di spunta verde è stato rimosso per questa chat e per questo contatto quando vedi questo avviso.
<strong>Se riscontri l’improvvisa rimozione della crittografia end-to-end garantita
inaspettatamente per questo contatto allora non accettare l’avviso!</strong>
Verifica invece con il tuo contatto attraverso un secondo canale
come una videochiamata, un altro messenger o una telefonata,
per scoprire cosa è successo.</p>
<p>Se il tuo contatto ha effettivamente causato la rimozione della crittografia end-to-end garantita
consultare i paragrafi successivi per i motivi comuni e le relative attenuazioni.
Indipendentemente da ciò, tutte le altre chat contrassegnate da un segno di spunta verde rimangono garantite con crittografia end-to-end
anche se il contatto è un membro.</p>
<p><strong>Il tuo contatto sta utilizzando Delta Chat su un secondo dispositivo (telefono o laptop)</strong></p>
<p>Se hanno un altro dispositivo con l’app Delta Chat in esecuzione,
dovrebbero rimuovere il profilo dal nuovo dispositivo
e aggiungerlo <a href="#multiclient">come secondo dispositivo come descritto qui</a>.
Non appena ti invieranno un messaggio, l’avviso scomparirà
e la crittografia garantita viene stabilita con entrambi i dispositivi del tuo contatto.</p>
<p><strong>Il tuo contatto ha reinstallato Delta Chat utilizzando il vecchio login del profilo</strong></p>
<p>Se hanno <a href="#backup">un file di backup</a>,
dovrebbero rimuovere il profilo dal nuovo dispositivo
e piuttosto importare il file di backup per ricreare il proprio profilo.
Non appena ti invieranno un messaggio, l’avviso scomparirà
e la crittografia garantita viene ristabilita per questo contatto.</p>
<p>Se non hanno un file di backup, è meglio eseguire una <a href="#howtoe2ee">scansione QR</a>
con il tuo partner di chat per ristabilire la crittografia end-to-end garantita.</p>
<p><strong>Il tuo contatto ha inviato un’e-mail tramite un’interfaccia webmail o un’altra app di posta elettronica
e presto tornerà a utilizzare Delta Chat.</strong></p>
<p>Se sei sicuro che il contatto a volte utilizza la webmail,
o un’altra app di posta priva di crittografia end-to-end,
allora puoi accettare l’avvertimento.
Non appena il tuo contatto utilizzerà nuovamente Delta Chat,
la crittografia end-to-end garantita verrà ristabilita automaticamente.</p>
<p><strong>Il tuo contatto ha smesso completamente di utilizzare Delta Chat</strong></p>
<p>A volte rimanere in contatto è più importante della crittografia end-to-end.
<a href="#tls">“Transport Layer Encryption” (TLS)</a> può comunque proteggere in modo significativo
la riservatezza dei tuoi messaggi tra il tuo dispositivo e il server di posta elettronica.
Ma senza la crittografia end-to-end tu e il tuo contratto vi fidate del vostro server di posta elettronica
a non leggere o manipolare i tuoi messaggi e a non trasmetterli a terzi.</p>
<p>In ogni caso, non puoi fare molto altro che accettare l’avvertimento.
Rimuovi anche il contatto da qualsiasi gruppo attivo contrassegnato da un segno di spunta verde
che puoi trovare in “Chat condivise” nel profilo dei contatti.
Ciò evita che il tuo contatto riceva messaggi “illeggibili”.</p>
<p>Se il contatto ha rimosso Delta Chat a causa di bug o di comportamenti indesiderati,
ti invitiamo a pubblicare post sul nostro <a href="https://support.delta.chat">forum di supporto</a>
per aiutarci a identificare e affrontare i problemi comuni. Grazie!</p>
<h3 id="gli-allegati-immagini-file-audio-ecc-sono-crittografati-end-to-end"> <h3 id="gli-allegati-immagini-file-audio-ecc-sono-crittografati-end-to-end">
@ -940,9 +878,8 @@ e metadati degli allegati come i nomi dei file.</p>
</h3> </h3>
<p>Sì, Delta Chat utilizza un sottoinsieme sicuro di OpenPGP <p>Sì, Delta Chat utilizza un sottoinsieme sicuro di OpenPGP
e visualizza solo un indicatore di sicurezza lucchetto su un messaggio che richiede che l’intero messaggio sia correttamente crittografato e firmato.
se l’intero messaggio è crittografato e firmato correttamente. Ad esempio, le “Firme staccate” non sono considerate sicure.</p>
Ad esempio, le “Firme distaccate” non sono considerate sicure.</p>
<p>OpenPGP non è insicuro di per sé. <p>OpenPGP non è insicuro di per sé.
La maggior parte dei problemi di sicurezza di OpenPGP discussi pubblicamentederivano in realtà da una cattiva usabilità o da cattive implementazioni di strumenti o app (o entrambi). La maggior parte dei problemi di sicurezza di OpenPGP discussi pubblicamentederivano in realtà da una cattiva usabilità o da cattive implementazioni di strumenti o app (o entrambi).
@ -957,10 +894,10 @@ e <a href="#security-audits">verificato per la sicurezza nel 2019 e nel 2024</a>
per migliorare ulteriormente le caratteristiche di sicurezza implementando il per migliorare ulteriormente le caratteristiche di sicurezza implementando il
<a href="https://datatracker.ietf.org/doc/draft-ietf-openpgp-crypto-refresh/">nuovo aggiornamento crittografico IETF OpenPGP</a> che per fortuna è stato adottato nell’estate 2023.</p> <a href="https://datatracker.ietf.org/doc/draft-ietf-openpgp-crypto-refresh/">nuovo aggiornamento crittografico IETF OpenPGP</a> che per fortuna è stato adottato nell’estate 2023.</p>
<h3 id="openpgp-alternative"> <h3 id="openpgp-alternatives">
Avete considerato l’utilizzo di alternative a OpenPGP per la crittografia end-to-end? <a href="#openpgp-alternative" class="anchor"></a> Avete considerato l’utilizzo di alternative a OpenPGP per la crittografia end-to-end? <a href="#openpgp-alternatives" class="anchor"></a>
</h3> </h3>
@ -1003,17 +940,15 @@ come definito dalla specifica Autocrypt Level 1.</p>
<h3 id="tls"> <h3 id="tls">
Un messaggio viene esposto in chiaro se la crittografia end-to-end non è disponibile? <a href="#tls" class="anchor"></a> I messaggi contrassegnati dall’icona della posta sono esposti su Internet? <a href="#tls" class="anchor"></a>
</h3> </h3>
<p>Anche se non è garantito che i tuoi messaggi siano crittografati end-to-end, <p>Se inviate o ricevete messaggi e-mail senza crittografia end-to-end (utilizzando un server e-mail classico),
sono ancora protetti dai fornitori di Internet come le società di telefonia mobile o via cavo. sono comunque protetti dalle compagnie telefoniche o via cavo che non possono leggere o modificare i vostri messaggi e-mail.
Tuttavia, i provider di posta elettronica tuoi e del destinatario Ma sia il vostro provider e-mail che quello del destinatario
potranno leggere, analizzare o addirittura modificare i tuoi messaggi, possono leggere, analizzare o modificare i vostri messaggi, compresi gli allegati.</p>
compresi eventuali allegati,
se non sono crittografati end-to-end.</p>
<p>Delta Chat per impostazione predefinita utilizza <p>Delta Chat per impostazione predefinita utilizza
<a href="https://en.wikipedia.org/wiki/Transport_Layer_Security">Crittografia TLS</a> rigorosa <a href="https://en.wikipedia.org/wiki/Transport_Layer_Security">Crittografia TLS</a> rigorosa
@ -1026,10 +961,6 @@ verrà applicata la crittografia del trasporto tra i provider e-mail
in tal caso le comunicazioni Delta Chat non verranno mai esposte in chiaro su Internet in tal caso le comunicazioni Delta Chat non verranno mai esposte in chiaro su Internet
anche se il messaggio non sarà crittografato end-to-end.</p> anche se il messaggio non sarà crittografato end-to-end.</p>
<p>Tieni presente che <a href="#howtoe2ee">mantenere la crittografia end-to-end garantita</a> oltre alla crittografia TLS
fornisce una sicurezza pervasiva tra i tuoi dispositivi e quelli del destinatario.
Nemmeno il tuo provider e-mail o Internet sarà in grado di leggere o modificare i tuoi messaggi.</p>
<h3 id="message-metadata"> <h3 id="message-metadata">
@ -1038,25 +969,25 @@ Nemmeno il tuo provider e-mail o Internet sarà in grado di leggere o modificare
</h3> </h3>
<p>Delta Chat protegge la maggior parte dei metadati dei messaggi inserendo le seguenti informazioni <p>Unlike most other messengers,
nella parte crittografata end-to-end dei messaggi:</p> Delta Chat apps do not store any metadata about contacts or groups on servers, also not in encrypted form.
Instead, all group metadata is end-to-end encrypted and stored on end-user devices, only.</p>
<p>E-mail Servers can therefore only see</p>
<ul> <ul>
<li>Linea oggetto</li> <li>
<li>Avatar e nome del gruppo</li> <p>the message date,</p>
<li>Richieste MDN (conferma di lettura) (“Chat-Disposition-Notification-To”)</li> </li>
<li>Temporizzatore dei messaggi che scompaiono (“Ephemeral-Timer”)</li> <li>
<li>“Membro del gruppo chat rimosso”, “Membro del gruppo chat aggiunto”.</li> <p>sender and receiver addresses</p>
<li>Intestazione “Secure-Join” contenente comandi di join sicuri</li> </li>
<li>Notifica sull’attivazione dello streaming della posizione</li> <li>
<li>URL della stanza WebRTC</li> <p>and message size.</p>
</li>
</ul> </ul>
<p>I server E-Mail non hanno accesso a questi metadati protetti <p>All other message, contact and group metadata resides in the end-to-end encrypted part of messages.</p>
ma vedono la data del messaggio e la dimensione del messaggio,
e, cosa ancora più importante, gli indirizzi del mittente e del destinatario.
I server E-Mail necessitano di indirizzi di destinatari per instradare e
consegnare messaggi ai dispositivi del destinatario.</p>
<h3 id="device-seizure"> <h3 id="device-seizure">
@ -1066,98 +997,36 @@ consegnare messaggi ai dispositivi del destinatario.</p>
</h3> </h3>
<p>Entrambi per la protezione dai server e-mail che raccolgono metadati <p>Both for protecting against metadata-collecting e-mail servers
nonché contro il pericolo di sequestro del dispositivo as well as against the threat of device seizure
consigliamo di utilizzare un’<a href="https://delta.chat/serverguide">istanza del server e-mail</a> ottimizzata per Delta Chat we recommend to use a <a href="https://chatmail.at/relays">chatmail relay</a>
per creare profili temporanei pseudonimi tramite scansioni di codici QR. to create chat profiles using random e-mail addresses for transport.
Tieni presente che le app Delta Chat su tutte le piattaforme supportano più profili Note that Delta Chat apps on all platforms support multiple profiles
in questo modo puoi utilizzare facilmente profili “1 settimana” o “1 mese” specifici per azioni accanto al tuo profilo “principale”. so you can easily use situation-specific profiles next to your “main” profile
con la consapevolezza che tutti i dati temporanei del profilo, insieme a tutti i metadati, verranno cancellati. with the knowledge that all their data, along with all metadata, will be deleted.
Inoltre, se un dispositivo viene sequestrato, i contatti utilizzano profili e-mail temporanei Moreover, if a device is seized then chat contacts using short-lived profiles
non possono essere identificati facilmente, rispetto ai messaggeri che rivelano can not be identified easily.</p>
numeri di telefono nei gruppi di chat che a loro volta sono spesso associati a identità legali.</p>
<h3 id="come-posso-verificare-le-informazioni-di-crittografia"> <h3 id="sealedsender">
Come posso verificare le informazioni di crittografia? <a href="#come-posso-verificare-le-informazioni-di-crittografia" class="anchor"></a> Does Delta Chat support “Sealed Sender”? <a href="#sealedsender" class="anchor"></a>
</h3> </h3>
<p>È possibile verificare manualmente lo stato della crittografia end-to-end nella finestra di dialogo “Crittografia”. <p>No, non ancora.</p>
(profilo utente su Android/iOS o clic con il pulsante destro del mouse sull’elemento dell’elenco chat di un utente sul desktop).
Delta Chat mostra due impronte digitali.
Se sul tuo dispositivo e su quello del tuo contatto vengono visualizzate le stesse impronte digitali,
la connessione è sicura.</p>
<h3 id="come-posso-verificare-lo-stato-di-crittografia-dei-messaggi"> <p>The Signal messenger introduced <a href="https://signal.org/blog/sealed-sender/">“Sealed Sender” in 2018</a>
to keep their server infrastructure ignorant of who is sending a message to a set of recipients.
It is particularly important because the Signal server knows the mobile number of each account,
which is usually associated with a passport identity.</p>
<p>Even if <a href="https://chatmail.at/relays">chatmail relays</a>
Come posso verificare lo stato di crittografia dei messaggi? <a href="#come-posso-verificare-lo-stato-di-crittografia-dei-messaggi" class="anchor"></a> do not ask for any private data (including no phone numbers),
it might still be worthwhile to protect relational metadata between addresses.
We don’t foresee bigger problems in using random throw-away e-mail addresses for sealed sending
</h3> but an implementation has not been agreed as a priority yet.</p>
<p>Un piccolo <strong>lucchetto</strong> in un fumetto denota
che il messaggio è stato correttamente crittografato end-to-end dal mittente specificato.
Se <strong>non è presente alcun lucchetto</strong>, il messaggio non è stato crittografato correttamente end-to-end
molto probabilmente perché il mittente utilizza un’app o un’interfaccia webmail
senza supporto per la crittografia end-to-end.</p>
<h3 id="perché-vedo-messaggi-non-crittografati">
Perché vedo messaggi non crittografati? <a href="#perché-vedo-messaggi-non-crittografati" class="anchor"></a>
</h3>
<p>Se un contatto utilizza un’app e-mail non Autocrypt,
tutti i messaggi che coinvolgono questo contatto (in un gruppo o in una chat 1:1)
non sarà crittografato end-to-end e quindi non mostrerà un “lucchetto” con i messaggi.
Tieni presente che anche se i tuoi contatti utilizzano Delta Chat sul proprio profilo,
potrebbero anche utilizzare un’app di posta elettronica non Autocrypt su quel profilo
che quindi potrebbe causare messaggi non crittografati in modo intermittente.
La risposta non crittografata a messaggi non crittografati è richiesta da Autocrypt
per evitare messaggi illeggibili tra i tuoi contatti
e la loro app e-mail non Autocrypt.</p>
<h3 id="come-posso-ottenere-una-chat-crittografata-end-to-end-con-un-contatto-delta-chat-che-a-volte-utilizza-la-webmail-o-unaltra-app-e-mail-non-autocrypt">
Come posso ottenere una chat crittografata end-to-end con un contatto Delta Chat che a volte utilizza la webmail o un’altra app e-mail non Autocrypt? <a href="#come-posso-ottenere-una-chat-crittografata-end-to-end-con-un-contatto-delta-chat-che-a-volte-utilizza-la-webmail-o-unaltra-app-e-mail-non-autocrypt" class="anchor"></a>
</h3>
<p>Se hai bisogno di una chat crittografata end-to-end sicura con un contatto
chi utilizza il proprio profilo sia con Delta Chat che con app non Autocrypt (ad esempio webmail),
è meglio configurare <a href="#howtoe2ee">la crittografia end-to-end garantita con loro</a>
e quindi crea una chat di gruppo crittografata end-to-end garantita con voi due come membri.
In questa chat di gruppo tutti i messaggi verranno crittografati end-to-end
anche se la chat diretta tra voi due ha a
<a href="#nocryptanymore">“… inviato un messaggio da un altro dispositivo”</a> avviso.</p>
<h3 id="come-posso-garantire-la-crittografia-e-leliminazione-end-to-end-dei-messaggi">
Come posso garantire la crittografia e l’eliminazione end-to-end dei messaggi? <a href="#come-posso-garantire-la-crittografia-e-leliminazione-end-to-end-dei-messaggi" class="anchor"></a>
</h3>
<p>Il modo migliore per garantire che ogni messaggio sia crittografato end-to-end,
e i metadati vengono eliminati il ​​più rapidamente possibile
è <a href="#howtoe2ee">utilizzare chat con crittografia end-to-end garantita</a>
e l’attivazione dei <a href="#ephemeralmsgs">messaggi a scomparsa</a>.</p>
<p>Le chat crittografate end-to-end garantiscono la protezione dagli <a href="https://en.wikipedia.org/wiki/Man-in-the-middle_attack">attacchi MITM</a>
e l’attivazione dei “messaggi che scompaiono” elimina i messaggi
sul server dopo un tempo configurato dall’utente.</p>
<p>Se non hai bisogno di una copia più longeva dei tuoi messaggi sul server,
puoi anche attivare <a href="#delold">“elimina messaggi dal server”</a>.</p>
<h3 id="pfs"> <h3 id="pfs">
@ -1167,45 +1036,52 @@ puoi anche attivare <a href="#delold">“elimina messaggi dal server”</a>.</p>
</h3> </h3>
<p>No, Delta Chat non supporta Perfect Forward Secrecy (PFS). <p>No, non ancora.</p>
Ciò significa che se la tua chiave di cifratura privata Delta Chat viene divulgata,
e qualcuno ha raccolto i tuoi precedenti messaggi in transito,
sarà in grado di decifrarli e leggerli utilizzando la chiave di cifratura trapelata.</p>
<p>Tieni presente, tuttavia, che se qualcuno ottiene le tue chiavi di decrittazione, <p>Delta Chat today doesn’t support Perfect Forward Secrecy (PFS).
in genere saranno anche in grado di ricevere i tuoi messaggi, This means that if your private decryption key is leaked,
indipendentemente dal fatto che Perfect Forward Secrecy sia attivo o meno. and someone has collected your prior in-transit messages,
La tipica situazione reale in caso di fuga di chiavi di decrittazione è il sequestro del dispositivo they will be able to decrypt and read them using the leaked decryption key.
di cui discutiamo nella nostra risposta <a href="#device-seizure">sui metadati e sul sequestro dei dispositivi</a>.</p> Note that Forward Secrecy only increases security if you delete messages.
Otherwise, someone obtaining your decryption keys
is typically also able to get all your non-deleted messages
and doesn’t even need to decrypt any previously collected messages.</p>
<p>È possibile che Delta Chat si evolva per supportare Perfect Forward Secrecy, <p>We designed a Forward Secrecy approach that withstood
perché OpenPGP è solo un contenitore per messaggi crittografati initial examination from some cryptographers and implementation experts
ma la gestione delle chiavi di crittografia (e quindi la rotazione delle chiavi o “cricchetto”) but is pending a more formal write up
potrebbero essere organizzati in modo flessibile. to ascertain it reliably works in federated messaging and with multi-device usage,
Vedi <a href="https://gitlab.com/sequoia-pgp/openpgp-dr">prototipo PFS di Seqouia</a> before it could be implemented in <a href="https://github.com/chatmail/core">chatmail core</a>,
per gli esperimenti esistenti nella comunità degli implementatori di OpenPGP.</p> which would make it available in all <a href="https://chatmail.at/clients">chatmail clients</a>.</p>
<h3 id="la-crittografia-end-to-end-di-delta-chat-è-sicura-quanto-quella-di-signal"> <h3 id="pqc">
La crittografia end-to-end di Delta Chat è sicura quanto quella di Signal? <a href="#la-crittografia-end-to-end-di-delta-chat-è-sicura-quanto-quella-di-signal" class="anchor"></a> Does Delta Chat support Post-Quantum-Cryptography? <a href="#pqc" class="anchor"></a>
</h3> </h3>
<p>Dipende da cosa è importante per te. <p>No, non ancora.</p>
Delta Chat <a href="#pfs">non supporta PFS</a> come fa Signal
ma fornisce <a href="#e2eeguarantee">chat crittografate end-to-end garantite</a>
che sono sicuri contro server compromessi o reti danneggiate.
Signal e la maggior parte degli altri servizi di messaggistica che supportano PFS non forniscono
uno schema pratico per proteggere i gruppi di chat dagli attacchi di rete
che sono probabilmente più preoccupanti
di un potenziale utente malintenzionato che si impadronisce del tuo telefono e della configurazione di crittografia privata
ma in qualche modo non i tuoi messaggi, ma ha un registro completo di tutti
messaggi crittografati precedenti.</p>
<p>In ogni caso, la crittografia end-to-end di Delta Chat utilizza un <a href="#openpgp-secure">sottoinsieme sicuro di OpenPGP</a> <p>Delta Chat uses the Rust OpenPGP library <a href="https://github.com/rpgp/rpgp">rPGP</a>
che è stato <a href="https://delta.chat/assets/blog/2019-first-security-review.pdf">controllato in modo indipendente sulla sicurezza</a>.</p> which supports the latest <a href="https://datatracker.ietf.org/doc/draft-ietf-openpgp-pqc/">IETF Post-Quantum-Cryptography OpenPGP draft</a>.
We aim to add PQC support in <a href="https://github.com/chatmail/core">chatmail core</a> after the draft is finalized at the IETF
in collaboration with other OpenPGP implementers.</p>
<h3 id="how-can-i-manually-check-encryption-information">
How can I manually check encryption information? <a href="#how-can-i-manually-check-encryption-information" class="anchor"></a>
</h3>
<p>È possibile verificare manualmente lo stato della crittografia end-to-end nella finestra di dialogo “Crittografia”.
(profilo utente su Android/iOS o clic con il pulsante destro del mouse sull’elemento dell’elenco chat di un utente sul desktop).
Delta Chat mostra due impronte digitali.
Se sul tuo dispositivo e su quello del tuo contatto vengono visualizzate le stesse impronte digitali,
la connessione è sicura.</p>
<h3 id="importkey"> <h3 id="importkey">
@ -1631,6 +1507,11 @@ verrebbe eseguito dall’app Delta Chat.</p>
</h3> </h3>
<p>Nota:
La modifica degli indirizzi e-mail è temporaneamente disabilitata
a causa delle modifiche in corso al nucleo di DeltaChat.
Dovrebbe essere nuovamente disponibile tra qualche mese.</p>
<ol> <ol>
<li> <li>
<p>Cambia il tuo indirizzo in “Impostazioni → Avanzate → Password e Profilo” e <p>Cambia il tuo indirizzo in “Impostazioni → Avanzate → Password e Profilo” e
@ -1715,19 +1596,19 @@ Tuttavia, alcuni provider necessitano di opzioni speciali per funzionare corrett
vedi <a href="https://providers.delta.chat">Panoramica fornitore</a></li> vedi <a href="https://providers.delta.chat">Panoramica fornitore</a></li>
</ul> </ul>
<h3 id="i-want-to-manage-my-own-server-for-delta-chat-what-do-you-recommend"> <h3 id="vorrei-gestire-il-mio-server-per-delta-chat-cosa-mi-consigliate">
I want to manage my own server for Delta Chat. What do you recommend? <a href="#i-want-to-manage-my-own-server-for-delta-chat-what-do-you-recommend" class="anchor"></a> Vorrei gestire il mio server per Delta Chat. Cosa mi consigliate? <a href="#vorrei-gestire-il-mio-server-per-delta-chat-cosa-mi-consigliate" class="anchor"></a>
</h3> </h3>
<ul> <ul>
<li>Most mail servers will work well. But what we personally recommend is a <li>La maggior parte dei server di posta funzionerà bene. Ma quello che personalmente consigliamo è un
chatmail relay server, as described <a href="https://delta.chat/en/2023-12-13-chatmail">in this server relay di chatmail, come descritto <a href="https://delta.chat/en/2023-12-13-chatmail">in questo
blogpost</a>.</li> articolo del blog</a>.</li>
<li>You can find an <a href="https://github.com/chatmail/relay">installation guide on GitHub</a>.</li> <li>Puoi trovare una <a href="https://github.com/chatmail/relay">guida all’installazione su GitHub</a>.</li>
</ul> </ul>
<h3 id="perché-devo-inserire-la-mia-password-e-mail-in-delta-chat-è-sicuro"> <h3 id="perché-devo-inserire-la-mia-password-e-mail-in-delta-chat-è-sicuro">

BIN
src/main/assets/help/lock-screenshot.png
View file

Binary file not shown.
Side by side

Before

Width:  |  Height:  |  Size: 2.2 KiB

420
src/main/assets/help/nl/help.html
View file

@ -36,27 +36,24 @@
<li><a href="#why-does-delta-chat-integrate-with-centralized-proprietary-applegoogle-push-services">Why does Delta Chat integrate with centralized proprietary Apple/Google push services?</a></li> <li><a href="#why-does-delta-chat-integrate-with-centralized-proprietary-applegoogle-push-services">Why does Delta Chat integrate with centralized proprietary Apple/Google push services?</a></li>
</ul> </ul>
</li> </li>
<li><a href="#beveiliging-en-versleuteling">Beveiliging en versleuteling</a> <li><a href="#e2ee">Beveiliging en versleuteling</a>
<ul> <ul>
<li><a href="#welke-standaarden-worden-gebruikt-bij-eind-tot-eindversleuteling">Welke standaarden worden gebruikt bij eind-tot-eindversleuteling?</a></li> <li><a href="#welke-standaarden-worden-gebruikt-bij-eind-tot-eindversleuteling">Welke standaarden worden gebruikt bij eind-tot-eindversleuteling?</a></li>
<li><a href="#whene2e">How can i know if messages are end-to-end encrypted?</a></li> <li><a href="#whene2e">How can i know if messages are end-to-end encrypted?</a></li>
<li><a href="#howtoe2ee">How can I get guaranteed end-to-end encryption and green checkmarks?</a></li> <li><a href="#can-i-still-receive-or-send-mails-without-end-to-end-encryption">Can i still receive or send mails without end-to-end encryption?</a></li>
<li><a href="#e2eeguarantee">What does the green checkmark and “guaranteed end-to-end encryption” mean?</a></li> <li><a href="#howtoe2ee">How can I establish a chat with a new contact?</a></li>
<li><a href="#nocryptanymore">A contact “sent a message from another device”, what can i do?</a></li> <li><a href="#e2eeguarantee">What does the green checkmark in a contact profile mean?</a></li>
<li><a href="#are-attachments-pictures-files-audio-etc-end-to-end-encrypted">Are attachments (pictures, files, audio etc.) end-to-end encrypted?</a></li> <li><a href="#are-attachments-pictures-files-audio-etc-end-to-end-encrypted">Are attachments (pictures, files, audio etc.) end-to-end encrypted?</a></li>
<li><a href="#openpgp-secure">Is OpenPGP secure?</a></li> <li><a href="#openpgp-secure">Is OpenPGP secure?</a></li>
<li><a href="#openpgp-alternatives">Did you consider using alternatives to OpenPGP for end-to-end -encryption?</a></li> <li><a href="#openpgp-alternatives">Did you consider using alternatives to OpenPGP for end-to-end-encryption?</a></li>
<li><a href="#is-delta-chat-vulnerable-to-efail">Is Delta Chat vulnerable to EFAIL?</a></li> <li><a href="#is-delta-chat-vulnerable-to-efail">Is Delta Chat vulnerable to EFAIL?</a></li>
<li><a href="#tls">Is a message exposed in cleartext if end-to-end encryption is not available?</a></li> <li><a href="#tls">Are messages marked with the mail icon exposed on the Internet?</a></li>
<li><a href="#message-metadata">How does Delta Chat protect metadata in messages?</a></li> <li><a href="#message-metadata">How does Delta Chat protect metadata in messages?</a></li>
<li><a href="#device-seizure">How to protect metadata and contacts when a device is seized?</a></li> <li><a href="#device-seizure">How to protect metadata and contacts when a device is seized?</a></li>
<li><a href="#how-can-i-check-encryption-information">How can i check encryption information?</a></li> <li><a href="#sealedsender">Does Delta Chat support “Sealed Sender”?</a></li>
<li><a href="#how-can-i-check-the-encryption-status-of-messages">How can I check the encryption status of messages?</a></li>
<li><a href="#why-do-i-see-unencrypted-messages">Why do I see unencrypted messages?</a></li>
<li><a href="#how-can-i-get-an-end-to-end-encrypted-chat-with-a-delta-chat-contact-who-sometimes-uses-webmail-or-another-non-autocrypt-e-mail-app">How can i get an end-to-end encrypted chat with a Delta Chat contact who sometimes uses webmail or another non-Autocrypt e-mail app?</a></li>
<li><a href="#how-can-i-ensure-message-end-to-end-encryption-and-deletion">How can I ensure message end-to-end encryption and deletion?</a></li>
<li><a href="#pfs">Does Delta Chat support Perfect Forward Secrecy?</a></li> <li><a href="#pfs">Does Delta Chat support Perfect Forward Secrecy?</a></li>
<li><a href="#is-end-to-end-encryption-of-delta-chat-as-safe-as-signal">Is end-to-end encryption of Delta Chat as safe as Signal?</a></li> <li><a href="#pqc">Does Delta Chat support Post-Quantum-Cryptography?</a></li>
<li><a href="#how-can-i-manually-check-encryption-information">How can I manually check encryption information?</a></li>
<li><a href="#importkey">Kan ik mijn bestaande privésleutel hergebruiken?</a></li> <li><a href="#importkey">Kan ik mijn bestaande privésleutel hergebruiken?</a></li>
<li><a href="#security-audits">Heeft Delta Chat ooit onafhankelijke beveiligingscontroles ondergaan?</a></li> <li><a href="#security-audits">Heeft Delta Chat ooit onafhankelijke beveiligingscontroles ondergaan?</a></li>
</ul> </ul>
@ -719,10 +716,10 @@ that achieves “instant delivery” of messages for all chatmail servers
including a potential one <a href="https://delta.chat/chatmail#selfhosted">you might setup yourself without our permission</a>. including a potential one <a href="https://delta.chat/chatmail#selfhosted">you might setup yourself without our permission</a>.
Welcome to the power of the interoperable and massive chatmail and e-mail system :)</p> Welcome to the power of the interoperable and massive chatmail and e-mail system :)</p>
<h2 id="beveiliging-en-versleuteling"> <h2 id="e2ee">
Beveiliging en versleuteling <a href="#beveiliging-en-versleuteling" class="anchor"></a> Beveiliging en versleuteling <a href="#e2ee" class="anchor"></a>
</h2> </h2>
@ -735,18 +732,26 @@ Welcome to the power of the interoperable and massive chatmail and e-mail system
</h3> </h3>
<p><a href="https://autocrypt.org">Autocrypt</a> is used for automatically <p>Delta Chat uses a <a href="#openpgp-secure">secure subset of the OpenPGP standard</a>
establishing end-to-end encryption with contacts and group chats. to provide automatic end-to-end encryption using these protocols:</p>
Autocrypt uses a limited and <a href="#openpgp-secure">secure subset of the OpenPGP standard</a>.
End-to-End encrypted messages are marked with a padlock
<img style="vertical-align:middle; width:1.2em; margin:1px" src="../lock-icon.png" alt="padlock" />.</p>
<p><a href="https://securejoin.delta.chat/en/latest/new.html">Secure-Join protocols</a> <ul>
are used for establishing chats with guaranteed end-to-end encryption <li>
which protects against network attacks and compromised servers. <p><a href="https://securejoin.delta.chat/en/latest/new.html">Secure-Join</a>
Chats marked with a green checkmark to exchange encryption setup information through QR-code scanning or “invite links”.</p>
<img style="vertical-align:middle; width:1.5em; margin:1px" src="../green-checkmark.png" alt="green checkmark" /> </li>
guarantee end-to-end encrypted messages.</p> <li>
<p><a href="https://autocrypt.org">Autocrypt</a> is used for automatically
establishing end-to-end encryption between contacts and all members of a group chat.</p>
</li>
<li>
<p><a href="https://github.com/chatmail/core/blob/main/spec.md#attaching-a-contact-to-a-message">Sharing a contact to a
chat</a>
enables receivers to use end-to-end encryption with the contact.</p>
</li>
</ul>
<p>Delta Chat does not query, publish or interact with any OpenPGP key servers.</p>
<h3 id="whene2e"> <h3 id="whene2e">
@ -756,28 +761,37 @@ guarantee end-to-end encrypted messages.</p>
</h3> </h3>
<p>All end-to-end encrypted messages carry a padlock:</p> <p>All messages in Delta Chat are <strong>end-to-end encrypted by default</strong>.
Since the Delta Chat Version 2 release series (July 2025)
there are no lock or similar markers on end-to-end encrypted messages, anymore.</p>
<p><img style="width:160px; margin:1px" src="../lock-screenshot.png" alt="padlock in bubble" /></p> <h3 id="can-i-still-receive-or-send-mails-without-end-to-end-encryption">
<p>End-to-end encryption is guaranteed if there is a green checkmark next to the chat title:</p>
<p><img style="width:211px; margin:1px" src="../green-checkmark-screenshot.png" alt="green checkmark in title" /></p>
<h3 id="howtoe2ee">
How can I get guaranteed end-to-end encryption and green checkmarks? <a href="#howtoe2ee" class="anchor"></a> Can i still receive or send mails without end-to-end encryption? <a href="#can-i-still-receive-or-send-mails-without-end-to-end-encryption" class="anchor"></a>
</h3> </h3>
<p>If you have a second communication channel with your chat partner, <p>If you use default <a href="https://chatmail.at/relays">chatmail relays</a>,
like a video chat or a different messenger, it is impossible to receive or send messages without end-to-end encryption.</p>
you can generate an invite link.</p>
<p>If you are together in person, <p>If you instead create a profile using a classic e-mail server,
you can show a QR code to your chat partner.</p> you can send and receive messages without end-to-end encryption.
Such messages lacking end-to-end encryption are marked with an e-mail icon
<img style="vertical-align:middle; width:1.2em; margin:1px" src="../email-icon.png" alt="email" />.</p>
<h3 id="howtoe2ee">
How can I establish a chat with a new contact? <a href="#howtoe2ee" class="anchor"></a>
</h3>
<p>You can send an invite link through another private chat,
show an invitation QR code when next to each other or in a video call,
or click on a “contact” that was shared in a chat.</p>
<ul> <ul>
<li> <li>
@ -792,135 +806,54 @@ on the Delta Chat app main screen.</p>
</li> </li>
</ul> </ul>
<p>Let your chat partner scan the QR image <p>Ask your chat partner to scan the QR image
with their Delta Chat app, with their Delta Chat app,
or click “Copy” or “Share” to create an invite link or click “Copy” or “Share” to create an invite link
and share it with your chat partner.</p> and share it with your chat partner.</p>
<p>Now wait while <a href="https://securejoin.delta.chat/en/latest/new.html#setup-contact-protocol">Secure-Join network messages are exchanged</a> between both devices.</p> <p>Now wait while <a href="https://securejoin.delta.chat/en/latest/new.html#setup-contact-protocol">end-to-end encryption is getting established</a>.</p>
<ul> <ul>
<li> <li>
<p>If both devices are online, <p>If both sides are online, they will soon see a (group or direct) chat
both sides will eventually see a (group or direct) chat with a green checkmark and can start messaging securely.</p>
<img style="vertical-align:middle; width:1.5em; margin:1px" src="../green-checkmark.png" alt="green checkmark" />
next to the title.</p>
</li> </li>
<li> <li>
<p>If one of the devices is offline, the green checkmarks will only <p>If one side is offline or in bad network,
appear later when the device is internet-connected again the ability to chat is delayed until connectivity is restored.</p>
and the Secure-Join network protocol completed.</p>
</li> </li>
</ul> </ul>
<p>Congratulations! <p>Congratulations!
You now will automatically use guaranteed end-to-end encryption You now will automatically use end-to-end encryption
with this contact and both of you can add each other to green-checkmarked groups with this contact.
<img style="vertical-align:middle; width:1.5em; margin:1px" src="../green-checkmark.png" alt="green checkmark" />, If you add each other to chat groups,
thereby automatically spreading guaranteed end-to-end encryption among its members.</p> end-to-end encryption will be established among all members.</p>
<h3 id="e2eeguarantee"> <h3 id="e2eeguarantee">
What does the green checkmark and “guaranteed end-to-end encryption” mean? <a href="#e2eeguarantee" class="anchor"></a> What does the green checkmark in a contact profile mean? <a href="#e2eeguarantee" class="anchor"></a>
</h3> </h3>
<p>Chat titles with green checkmarks <p>A contact profile might show a green checkmark
<img style="vertical-align:middle; width:1.5em; margin:1px" src="../green-checkmark.png" alt="green checkmark" /> <img style="vertical-align:middle; width:1.5em; margin:1px" src="../green-checkmark.png" alt="green checkmark" />
mean that all messages in the chat will be end-to-end encrypted and an “Introduced by” line.
and can not be read or altered by compromised e-mail servers or Internet providers.
Joining green-checkmarked group chats
safely spreads everybody’s encryption information (and green checkmarks)
in a manner that guarantees end-to-end encryption in the group and among members.</p>
<p>Contact profiles with green checkmarks
<img style="vertical-align:middle; width:1.5em; margin:1px" src="../green-checkmark.png" alt="green checkmark" />
mean that messaging a contact is currently guaranteed to be end-to-end encrypted.
Every green-checkmarked contact either did a direct <a href="#howtoe2ee">QR-scan</a> with you Every green-checkmarked contact either did a direct <a href="#howtoe2ee">QR-scan</a> with you
or was introduced by a another green-checkmarked contact. or was introduced by a another green-checkmarked contact.
Introductions happen automatically when adding members to groups. Introductions happen automatically when adding members to groups.
Whoever adds a contact to a green-checkmarked group becomes an introducer Whoever adds a green-checkmarked contact to a group with only green-checkmarked members
to those members who didn’t yet know about the added contact. becomes an introducer.
In a contact profile you can tap on the “Introduced by …” text repeatedly In a contact profile you can tap on the “Introduced by …” text repeatedly
until you get to the one with whom you directly did a <a href="#howtoe2ee">QR-scan</a>.</p> until you get to the one with whom you directly did a <a href="#howtoe2ee">QR-scan</a>.</p>
<p>Note that in a contact profile you may see and tap introducers
but there is no green checkmark in the profile title.
This usually means that the contact <a href="#nocryptanymore">“sent a message from another device”</a>.</p>
<p>For more in-depth discussion of “guaranteed end-to-end encryption” <p>For more in-depth discussion of “guaranteed end-to-end encryption”
please see <a href="https://securejoin.delta.chat/en/latest/new.html">Secure-Join protocols</a> please see <a href="https://securejoin.delta.chat/en/latest/new.html">Secure-Join protocols</a>
and specifically read about “Verified Groups”, the technical term and specifically read about “Verified Groups”, the technical term
of what is called here “green-checkmarked” or “guaranteed end-to-end encrypted” chats.</p> of what is called here “green-checkmarked” or “guaranteed end-to-end encrypted” chats.</p>
<h3 id="nocryptanymore">
A contact “sent a message from another device”, what can i do? <a href="#nocryptanymore" class="anchor"></a>
</h3>
<p>Your chat with a contact lost guaranteed end-to-end encryption.
The green checkmark was removed for this chat and contact when you see this warning.
<strong>If you find the sudden drop of guaranteed end-to-end encryption
surprising for this contact then don’t accept the warning!</strong>
Instead check with your contact through a second channel
like a video call, other messenger or a phone call,
to find out what happened.</p>
<p>If your contact actually caused the drop of guaranteed end-to-end encryption
please see the next paragraphs for common reasons and their mitigations.
Regardless, all other green-checkmarked chats remain guaranteed end-to-end encrypted
even if the contact is a member there.</p>
<p><strong>Your contact is using Delta Chat on a second device (phone or laptop)</strong></p>
<p>If they have another device with a Delta Chat app running,
they should remove the profile from the new device
and add it <a href="#multiclient">as a second device as described here</a>.
As soon as they message you afterwards, the warning will be gone
and guaranteed encryption is established with both devices of your contact.</p>
<p><strong>Your contact reinstalled Delta Chat using their old account login</strong></p>
<p>If they have <a href="#backup">a backup file</a>,
they should remove the profile from the new device
and rather import the backup file to re-create their profile.
As soon as they message you afterwards, the warning will be gone
and guaranteed encryption is re-established for this contact.</p>
<p>If they don’t have a backup file, it’s best to perform a <a href="#howtoe2ee">QR scan</a>
with your chat partner to re-establish guaranteed end-to-end encryption.</p>
<p><strong>Your contact sent a mail through a webmail interface or another e-mail app
and will get back to using Delta Chat soon again.</strong></p>
<p>If you are sure that the contact sometimes uses webmail,
or another mail app lacking end-to-end encryption,
then you may accept the warning.
As soon as your contact uses Delta Chat again,
guaranteed end-to-end encryption will be automatically re-established.</p>
<p><strong>Your contact stopped using Delta Chat entirely</strong></p>
<p>Sometimes remaining in contact is more important than end-to-end encryption.
<a href="#tls">“Transport Layer Encryption” (TLS)</a> may still meaningfully protect
the confidentiality of your messages between your device and the e-mail server.
But without end-to-end encryption you and your contact are trusting your e-mail server
to not read or manipulate your messages, and to not hand them to third parties.</p>
<p>In any case, you can not do much else than accept the warning.
Please also remove the contact from any active green-checkmarked group
which you can find in “Chats in Common” in the Contact profile.
This spares your contact from getting “unreadable” messages.</p>
<p>If the contact removed Delta Chat because of buggy or undesirable behaviour,
please consider posting to our <a href="https://support.delta.chat">support forum</a>
to help us identify and address common problems. Thanks!</p>
<h3 id="are-attachments-pictures-files-audio-etc-end-to-end-encrypted"> <h3 id="are-attachments-pictures-files-audio-etc-end-to-end-encrypted">
@ -945,8 +878,7 @@ and attachment metadata such as filenames.</p>
</h3> </h3>
<p>Yes, Delta Chat uses a secure subset of OpenPGP <p>Yes, Delta Chat uses a secure subset of OpenPGP
and only displays a padlock security indicator on a message requiring the whole message to be properly encrypted and signed.
if the whole message is properly encrypted and signed.
For example, “Detached signatures” are not treated as secure.</p> For example, “Detached signatures” are not treated as secure.</p>
<p>OpenPGP is not insecure by itself. <p>OpenPGP is not insecure by itself.
@ -967,7 +899,7 @@ which was thankfully adopted in summer 2023.</p>
<h3 id="openpgp-alternatives"> <h3 id="openpgp-alternatives">
Did you consider using alternatives to OpenPGP for end-to-end -encryption? <a href="#openpgp-alternatives" class="anchor"></a> Did you consider using alternatives to OpenPGP for end-to-end-encryption? <a href="#openpgp-alternatives" class="anchor"></a>
</h3> </h3>
@ -1010,17 +942,15 @@ as defined by the Autocrypt Level 1 specification.</p>
<h3 id="tls"> <h3 id="tls">
Is a message exposed in cleartext if end-to-end encryption is not available? <a href="#tls" class="anchor"></a> Are messages marked with the mail icon exposed on the Internet? <a href="#tls" class="anchor"></a>
</h3> </h3>
<p>Even if your messages are not guaranteed to be end-to-end encrypted, <p>If you are sending or receiving e-mail messages without end-to-end encryption (using a classic e-mail server),
they are still protected from Internet providers like cell or cable companies. they are still protected from cell or cable companies who can not read or modify your e-mail messages.
However, your and your recipient’s e-mail providers But both your and your recipient’s e-mail providers
may read, analyze or even modify your messages, may read, analyze or modify your messages, including any attachments.</p>
including any attachments,
if they are not end-to-end encrypted.</p>
<p>Delta Chat by default uses strict <p>Delta Chat by default uses strict
<a href="https://en.wikipedia.org/wiki/Transport_Layer_Security">TLS encryption</a> <a href="https://en.wikipedia.org/wiki/Transport_Layer_Security">TLS encryption</a>
@ -1033,10 +963,6 @@ then transport encryption will be enforced between e-mail providers
in which case Delta Chat communications will never be exposed in cleartext to the Internet in which case Delta Chat communications will never be exposed in cleartext to the Internet
even if the message was not end-to-end encrypted.</p> even if the message was not end-to-end encrypted.</p>
<p>Note that <a href="#howtoe2ee">maintaining guaranteed end-to-end encryption</a> on top of TLS encryption
provides pervasive safety between your and the recipient’s devices.
Not even your e-mail or Internet provider will be able to read or modify your messages.</p>
<h3 id="message-metadata"> <h3 id="message-metadata">
@ -1045,25 +971,25 @@ Not even your e-mail or Internet provider will be able to read or modify your me
</h3> </h3>
<p>Delta Chat protects most message metadata by putting the following information <p>Unlike most other messengers,
into the end-to-end encrypted part of messages:</p> Delta Chat apps do not store any metadata about contacts or groups on servers, also not in encrypted form.
Instead, all group metadata is end-to-end encrypted and stored on end-user devices, only.</p>
<p>E-mail Servers can therefore only see</p>
<ul> <ul>
<li>Subject line</li> <li>
<li>Group avatar and name</li> <p>the message date,</p>
<li>MDN (read receipt) requests (<code class="language-plaintext highlighter-rouge">Chat-Disposition-Notification-To</code>)</li> </li>
<li>Disappearing message timer (<code class="language-plaintext highlighter-rouge">Ephemeral-Timer</code>)</li> <li>
<li><code class="language-plaintext highlighter-rouge">Chat-Group-Member-Removed</code>, <code class="language-plaintext highlighter-rouge">Chat-Group-Member-Added</code></li> <p>sender and receiver addresses</p>
<li><code class="language-plaintext highlighter-rouge">Secure-Join</code> header containing secure join commands</li> </li>
<li>Notification about enabling location streaming</li> <li>
<li>WebRTC room URL</li> <p>and message size.</p>
</li>
</ul> </ul>
<p>E-Mail servers do not get access to this protected metadata <p>All other message, contact and group metadata resides in the end-to-end encrypted part of messages.</p>
but they do see the message date as well as the message size,
and, more importantly, the sender and receiver addresses.
E-mail servers need receiver addresses to route and
deliver messages to recipient’s devices.</p>
<h3 id="device-seizure"> <h3 id="device-seizure">
@ -1075,96 +1001,34 @@ deliver messages to recipient’s devices.</p>
<p>Both for protecting against metadata-collecting e-mail servers <p>Both for protecting against metadata-collecting e-mail servers
as well as against the threat of device seizure as well as against the threat of device seizure
we recommend to use a <a href="https://delta.chat/chatmail">chatmail server</a> we recommend to use a <a href="https://chatmail.at/relays">chatmail relay</a>
to create pseudonymous temporary profiles through QR-code scans. to create chat profiles using random e-mail addresses for transport.
Note that Delta Chat apps on all platforms support multiple profiles Note that Delta Chat apps on all platforms support multiple profiles
so you can easily use situation-specific profiles next to your “main” profile so you can easily use situation-specific profiles next to your “main” profile
with the knowledge that all their data, along with all metadata, will be deleted. with the knowledge that all their data, along with all metadata, will be deleted.
Moreover, if a device is seized then contacts using temporary profiles Moreover, if a device is seized then chat contacts using short-lived profiles
can not be identified easily, as compared to messengers which reveal can not be identified easily.</p>
phone numbers in chat groups which in turn are often associated with legal identities.</p>
<h3 id="how-can-i-check-encryption-information"> <h3 id="sealedsender">
How can i check encryption information? <a href="#how-can-i-check-encryption-information" class="anchor"></a> Does Delta Chat support “Sealed Sender”? <a href="#sealedsender" class="anchor"></a>
</h3> </h3>
<p>You may check the end-to-end encryption status manually in the “Encryption” dialog <p>No, not yet.</p>
(user profile on Android/iOS or right-click a user’s chat-list item on desktop).
Delta Chat shows two fingerprints there.
If the same fingerprints appear on your own and your contact’s device,
the connection is safe.</p>
<h3 id="how-can-i-check-the-encryption-status-of-messages"> <p>The Signal messenger introduced <a href="https://signal.org/blog/sealed-sender/">“Sealed Sender” in 2018</a>
to keep their server infrastructure ignorant of who is sending a message to a set of recipients.
It is particularly important because the Signal server knows the mobile number of each account,
which is usually associated with a passport identity.</p>
<p>Even if <a href="https://chatmail.at/relays">chatmail relays</a>
How can I check the encryption status of messages? <a href="#how-can-i-check-the-encryption-status-of-messages" class="anchor"></a> do not ask for any private data (including no phone numbers),
it might still be worthwhile to protect relational metadata between addresses.
We don’t foresee bigger problems in using random throw-away e-mail addresses for sealed sending
</h3> but an implementation has not been agreed as a priority yet.</p>
<p>A little <strong>padlock</strong> in a message bubble denotes
that the message was properly end-to-end encrypted from the given sender.
If there is <strong>no padlock</strong>, the message was not properly end-to-end encrypted
most likely because the sender uses an app or webmail interface
without support for end-to-end–encryption.</p>
<h3 id="why-do-i-see-unencrypted-messages">
Why do I see unencrypted messages? <a href="#why-do-i-see-unencrypted-messages" class="anchor"></a>
</h3>
<p>If a contact uses a non-Autocrypt e-mail app,
all messages involving this contact (in a group or 1:1 chat)
will not be end-to-end encrypted, and thus not show a “padlock” with messages.
Note that even if your contacts use Delta Chat on their account,
they might also use a non-Autocrypt e-mail app on that account
which then may cause intermittently unencrypted messages.
Replying unencrypted to unencrypted messages is mandated by Autocrypt
to prevent unreadable messages on the side of your contacts
and their non-Autocrypt e-mail app.</p>
<h3 id="how-can-i-get-an-end-to-end-encrypted-chat-with-a-delta-chat-contact-who-sometimes-uses-webmail-or-another-non-autocrypt-e-mail-app">
How can i get an end-to-end encrypted chat with a Delta Chat contact who sometimes uses webmail or another non-Autocrypt e-mail app? <a href="#how-can-i-get-an-end-to-end-encrypted-chat-with-a-delta-chat-contact-who-sometimes-uses-webmail-or-another-non-autocrypt-e-mail-app" class="anchor"></a>
</h3>
<p>If you need a safely end-to-end encrypted chat with a contact
who is using their e-mail account both with Delta Chat and non-Autocrypt apps (e.g. webmail),
it’s best to setup <a href="#howtoe2ee">guaranteed end-to-end encryption with them</a>
and then create a guaranteed end-to-end encrypted group chat with you two as members.
In this group chat all messages will be end-to-end encrypted
even if the direct chat between you two has a
<a href="#nocryptanymore">“… sent a message from another device”</a> warning.</p>
<h3 id="how-can-i-ensure-message-end-to-end-encryption-and-deletion">
How can I ensure message end-to-end encryption and deletion? <a href="#how-can-i-ensure-message-end-to-end-encryption-and-deletion" class="anchor"></a>
</h3>
<p>The best way to ensure every message is end-to-end encrypted,
and metadata deleted as quickly as possible
is <a href="#howtoe2ee">using chats with guaranteed end-to-end encryption</a>
and turning on <a href="#ephemeralmsgs">disappearing messages</a>.</p>
<p>Guaranteed end-to-end encrypted chats protect against <a href="https://en.wikipedia.org/wiki/Man-in-the-middle_attack">MITM attacks</a>
and turning on disappearing messages deletes the messages
on the server after a user-configured time.</p>
<p>If you don’t need a longer-lived copy of your messages on the server,
you can also turn on <a href="#delold">“delete messages from server automatically”</a>.</p>
<h3 id="pfs"> <h3 id="pfs">
@ -1174,45 +1038,52 @@ you can also turn on <a href="#delold">“delete messages from server automatica
</h3> </h3>
<p>No, Delta Chat doesn’t support Perfect Forward Secrecy (PFS). <p>No, not yet.</p>
This means that if your Delta Chat private decryption key is leaked,
<p>Delta Chat today doesn’t support Perfect Forward Secrecy (PFS).
This means that if your private decryption key is leaked,
and someone has collected your prior in-transit messages, and someone has collected your prior in-transit messages,
they will be able to decrypt and read them using the leaked decryption key.</p> they will be able to decrypt and read them using the leaked decryption key.
Note that Forward Secrecy only increases security if you delete messages.
Otherwise, someone obtaining your decryption keys
is typically also able to get all your non-deleted messages
and doesn’t even need to decrypt any previously collected messages.</p>
<p>Note, however, that if anyone obtains to your decryption keys, <p>We designed a Forward Secrecy approach that withstood
they will typically also be able to obtain your messages, initial examination from some cryptographers and implementation experts
irrespective if Perfect Forward Secrecy is in place or not. but is pending a more formal write up
The typical real-world situation for leaked decryption keys is device seizure to ascertain it reliably works in federated messaging and with multi-device usage,
which we discuss in our answer <a href="#device-seizure">on metadata and device seizure</a>.</p> before it could be implemented in <a href="https://github.com/chatmail/core">chatmail core</a>,
which would make it available in all <a href="https://chatmail.at/clients">chatmail clients</a>.</p>
<p>It is possible that Delta Chat evolves to support Perfect Forward Secrecy, <h3 id="pqc">
because OpenPGP is just a container for encrypted messages
but encryption key management (and thus key rotation or key “ratcheting”)
could be organized in flexible ways.
See <a href="https://gitlab.com/sequoia-pgp/openpgp-dr">Seqouia’s PFS prototype</a>
for existing experiments in the OpenPGP implementor community.</p>
<h3 id="is-end-to-end-encryption-of-delta-chat-as-safe-as-signal">
Is end-to-end encryption of Delta Chat as safe as Signal? <a href="#is-end-to-end-encryption-of-delta-chat-as-safe-as-signal" class="anchor"></a> Does Delta Chat support Post-Quantum-Cryptography? <a href="#pqc" class="anchor"></a>
</h3> </h3>
<p>It depends on what is important to you. <p>No, not yet.</p>
Delta Chat <a href="#pfs">does not support PFS</a> like Signal does
but it provides <a href="#e2eeguarantee">guaranteed end-to-end encrypted chats</a>
that are safe against compromised servers or corrupted networks.
Signal and most other PFS-supporting messengers do not provide
a practical scheme for protecting chat groups from network attacks
which are arguably more worrisome
than a potential attacker who seizes your phone and private encryption setup
but somehow not your messages, yet has a full record of all
past encrypted messages.</p>
<p>In any case, Delta Chat’s end-to-end encryption uses a <a href="#openpgp-secure">secure subset of OpenPGP</a> <p>Delta Chat uses the Rust OpenPGP library <a href="https://github.com/rpgp/rpgp">rPGP</a>
which has been <a href="https://delta.chat/assets/blog/2019-first-security-review.pdf">independently security-audited</a>.</p> which supports the latest <a href="https://datatracker.ietf.org/doc/draft-ietf-openpgp-pqc/">IETF Post-Quantum-Cryptography OpenPGP draft</a>.
We aim to add PQC support in <a href="https://github.com/chatmail/core">chatmail core</a> after the draft is finalized at the IETF
in collaboration with other OpenPGP implementers.</p>
<h3 id="how-can-i-manually-check-encryption-information">
How can I manually check encryption information? <a href="#how-can-i-manually-check-encryption-information" class="anchor"></a>
</h3>
<p>You may check the end-to-end encryption status manually in the “Encryption” dialog
(user profile on Android/iOS or right-click a user’s chat-list item on desktop).
Delta Chat shows two fingerprints there.
If the same fingerprints appear on your own and your contact’s device,
the connection is safe.</p>
<h3 id="importkey"> <h3 id="importkey">
@ -1247,7 +1118,7 @@ from most recent to older:</p>
<li> <li>
<p>2024 December, an <a href="https://github.com/rpgp/docs/blob/main/audits/NGI%20Core%20rPGP%20penetration%20test%20report%202024%201.0.pdf">NLNET-commissioned Evaluation of <p>2024 December, an <a href="https://github.com/rpgp/docs/blob/main/audits/NGI%20Core%20rPGP%20penetration%20test%20report%202024%201.0.pdf">NLNET-commissioned Evaluation of
rPGP</a> by <a href="https://www.radicallyopensecurity.com/">Radically Open Security</a> took place. rPGP</a> by <a href="https://www.radicallyopensecurity.com/">Radically Open Security</a> took place.
rPGP serves as the end-to-end encyption <a href="https://openpgp.org">OpenPGP</a> engine of Delta Chat. rPGP serves as the end-to-end encryption <a href="https://openpgp.org">OpenPGP</a> engine of Delta Chat.
Two advisories were released related to the findings of this audit:</p> Two advisories were released related to the findings of this audit:</p>
<ul> <ul>
@ -1640,6 +1511,11 @@ Normaal doet de Delta Chat-app dit uit zichzelf.</p>
</h3> </h3>
<p>Note:
Changing email addresses is temporarily disabled
because of ongoing changes to the DeltaChat core.
It should be available again in a few months.</p>
<ol> <ol>
<li> <li>
<p>Change your address in “Settings → Advanced → Password and Account” and <p>Change your address in “Settings → Advanced → Password and Account” and

273
src/main/assets/help/pl/help.html
View file

@ -36,27 +36,24 @@
<li><a href="#dlaczego-delta-chat-integruje-się-ze-scentralizowanymi-zastrzeżonymi-usługami-push-applegoogle">Dlaczego Delta Chat integruje się ze scentralizowanymi, zastrzeżonymi usługami push Apple/Google?</a></li> <li><a href="#dlaczego-delta-chat-integruje-się-ze-scentralizowanymi-zastrzeżonymi-usługami-push-applegoogle">Dlaczego Delta Chat integruje się ze scentralizowanymi, zastrzeżonymi usługami push Apple/Google?</a></li>
</ul> </ul>
</li> </li>
<li><a href="#szyfrowanie-i-bezpieczeństwo">Szyfrowanie i bezpieczeństwo</a> <li><a href="#e2ee">Szyfrowanie i bezpieczeństwo</a>
<ul> <ul>
<li><a href="#jakie-standardy-są-stosowane-do-szyfrowania-end-to-end">Jakie standardy są stosowane do szyfrowania end-to-end?</a></li> <li><a href="#jakie-standardy-są-stosowane-do-szyfrowania-end-to-end">Jakie standardy są stosowane do szyfrowania end-to-end?</a></li>
<li><a href="#whene2e">Skąd mogę wiedzieć, czy wiadomości są szyfrowane metodą e2e?</a></li> <li><a href="#whene2e">Skąd mogę wiedzieć, czy wiadomości są szyfrowane metodą e2e?</a></li>
<li><a href="#howtoe2ee">Jak mogę uzyskać gwarancję kompleksowego szyfrowania i zielone znaczniki wyboru?</a></li> <li><a href="#czy-nadal-mogę-odbierać-lub-wysyłać-wiadomości-bez-szyfrowania-end-to-end">Czy nadal mogę odbierać lub wysyłać wiadomości bez szyfrowania end-to-end?</a></li>
<li><a href="#e2eeguarantee">Co oznacza zielony znacznik wyboru i „gwarantowane kompleksowe szyfrowanie”?</a></li> <li><a href="#howtoe2ee">Jak mogę nawiązać czat z nowym kontaktem?</a></li>
<li><a href="#nocryptanymore">Kontakt „wysłał wiadomość z innego urządzenia”, co mogę zrobić?</a></li> <li><a href="#e2eeguarantee">Co oznacza zielony znacznik wyboru w profilu kontaktu?</a></li>
<li><a href="#czy-załączniki-zdjęcia-pliki-pliki-audio-itp-są-szyfrowane-metodą-end-to-end">Czy załączniki (zdjęcia, pliki, pliki audio itp.) są szyfrowane metodą end-to-end?</a></li> <li><a href="#czy-załączniki-zdjęcia-pliki-pliki-audio-itp-są-szyfrowane-metodą-end-to-end">Czy załączniki (zdjęcia, pliki, pliki audio itp.) są szyfrowane metodą end-to-end?</a></li>
<li><a href="#openpgp-secure">Czy OpenPGP jest bezpieczny?</a></li> <li><a href="#openpgp-secure">Czy OpenPGP jest bezpieczny?</a></li>
<li><a href="#openpgp-alternatives">Czy rozważałeś użycie alternatyw dla OpenPGP do szyfrowania typu end-to-end?</a></li> <li><a href="#openpgp-alternatives">Czy rozważałeś użycie alternatyw dla OpenPGP do szyfrowania typu end-to-end?</a></li>
<li><a href="#czy-delta-chat-jest-podatny-na-efail">Czy Delta Chat jest podatny na EFAIL?</a></li> <li><a href="#czy-delta-chat-jest-podatny-na-efail">Czy Delta Chat jest podatny na EFAIL?</a></li>
<li><a href="#tls">Czy wiadomość jest udostępniana w postaci zwykłego tekstu, jeśli szyfrowanie end-to-end nie jest dostępne?</a></li> <li><a href="#tls">Czy wiadomości oznaczone ikoną poczty są widoczne w internecie?</a></li>
<li><a href="#message-metadata">W jaki sposób Delta Chat chroni metadane w wiadomościach?</a></li> <li><a href="#message-metadata">W jaki sposób Delta Chat chroni metadane w wiadomościach?</a></li>
<li><a href="#device-seizure">Jak chronić metadane i kontakty w przypadku przejęcia urządzenia?</a></li> <li><a href="#device-seizure">Jak chronić metadane i kontakty w przypadku przejęcia urządzenia?</a></li>
<li><a href="#jak-mogę-sprawdzić-informacje-o-szyfrowaniu">Jak mogę sprawdzić informacje o szyfrowaniu?</a></li> <li><a href="#sealedsender">Does Delta Chat support “Sealed Sender”?</a></li>
<li><a href="#jak-mogę-sprawdzić-stan-szyfrowania-wiadomości">Jak mogę sprawdzić stan szyfrowania wiadomości?</a></li>
<li><a href="#dlaczego-widzę-niezaszyfrowane-wiadomości">Dlaczego widzę niezaszyfrowane wiadomości?</a></li>
<li><a href="#jak-mogę-uzyskać-zaszyfrowany-ened-to-end-czat-z-kontaktem-delta-chat-który-czasami-korzysta-z-poczty-internetowej-lub-innej-aplikacji-e-mail-bez-autocrypt">Jak mogę uzyskać zaszyfrowany ened-to-end czat z kontaktem Delta Chat, który czasami korzysta z poczty internetowej lub innej aplikacji e-mail bez Autocrypt?</a></li>
<li><a href="#jak-mogę-zapewnić-kompleksowe-szyfrowanie-i-usuwanie-wiadomości">Jak mogę zapewnić kompleksowe szyfrowanie i usuwanie wiadomości?</a></li>
<li><a href="#pfs">Czy Delta Chat obsługuje funkcję Perfect Forward Secrecy?</a></li> <li><a href="#pfs">Czy Delta Chat obsługuje funkcję Perfect Forward Secrecy?</a></li>
<li><a href="#czy-szyfrowanie-end-to-end-delta-chat-jest-tak-samo-bezpieczne-jak-signal">Czy szyfrowanie end-to-end Delta Chat jest tak samo bezpieczne jak Signal?</a></li> <li><a href="#pqc">Does Delta Chat support Post-Quantum-Cryptography?</a></li>
<li><a href="#how-can-i-manually-check-encryption-information">How can I manually check encryption information?</a></li>
<li><a href="#importkey">Czy mogę ponownie wykorzystać mój istniejący klucz prywatny?</a></li> <li><a href="#importkey">Czy mogę ponownie wykorzystać mój istniejący klucz prywatny?</a></li>
<li><a href="#security-audits">Czy Delta Chat był niezależnie kontrolowany pod kątem luk w zabezpieczeniach?</a></li> <li><a href="#security-audits">Czy Delta Chat był niezależnie kontrolowany pod kątem luk w zabezpieczeniach?</a></li>
</ul> </ul>
@ -90,7 +87,7 @@
<ul> <ul>
<li><a href="#jakich-uprawnień-potrzebuje-delta-chat">Jakich uprawnień potrzebuje Delta Chat?</a></li> <li><a href="#jakich-uprawnień-potrzebuje-delta-chat">Jakich uprawnień potrzebuje Delta Chat?</a></li>
<li><a href="#czy-delta-chat-działa-z-moim-dostawcą-poczty-e-mail">Czy Delta Chat działa z <em>moim</em> dostawcą poczty e-mail?</a></li> <li><a href="#czy-delta-chat-działa-z-moim-dostawcą-poczty-e-mail">Czy Delta Chat działa z <em>moim</em> dostawcą poczty e-mail?</a></li>
<li><a href="#i-want-to-manage-my-own-server-for-delta-chat-what-do-you-recommend">I want to manage my own server for Delta Chat. What do you recommend?</a></li> <li><a href="#chcę-zarządzać-własnym-serwerem-dla-delta-chat-co-polecacie">Chcę zarządzać własnym serwerem dla Delta Chat. Co polecacie?</a></li>
<li><a href="#dlaczego-muszę-wpisać-moje-hasło-e-mail-do-delta-chat-czy-to-jest-bezpieczne">Dlaczego muszę wpisać moje hasło e-mail do Delta Chat? Czy to jest bezpieczne?</a></li> <li><a href="#dlaczego-muszę-wpisać-moje-hasło-e-mail-do-delta-chat-czy-to-jest-bezpieczne">Dlaczego muszę wpisać moje hasło e-mail do Delta Chat? Czy to jest bezpieczne?</a></li>
<li><a href="#jakie-wiadomości-pojawiają-się-w-delta-chat">Jakie wiadomości pojawiają się w Delta Chat?</a></li> <li><a href="#jakie-wiadomości-pojawiają-się-w-delta-chat">Jakie wiadomości pojawiają się w Delta Chat?</a></li>
<li><a href="#czy-delta-chat-obsługuje-wiadomości-e-mail-w-formacie-html">Czy Delta Chat obsługuje wiadomości e-mail w formacie HTML?</a></li> <li><a href="#czy-delta-chat-obsługuje-wiadomości-e-mail-w-formacie-html">Czy Delta Chat obsługuje wiadomości e-mail w formacie HTML?</a></li>
@ -589,10 +586,10 @@ nadal będziesz mógł pisać, ale nie będziesz już powiadamiany o żadnych no
<p>Pamiętaj, że Delta Chat posiada <a href="#privacy-notifications">mały i chroniący prywatność system powiadomień push</a>, który zapewnia „natychmiastowe dostarczanie” wiadomości ze wszystkich serwerów chatmail, w tym potencjalnego, który <a href="https://delta.chat/chatmail#selfhosted">możesz skonfigurować samodzielnie bez naszej zgody</a>. Witamy w potędze interoperacyjnego i ogromnego systemu chatmail i e-mail :)</p> <p>Pamiętaj, że Delta Chat posiada <a href="#privacy-notifications">mały i chroniący prywatność system powiadomień push</a>, który zapewnia „natychmiastowe dostarczanie” wiadomości ze wszystkich serwerów chatmail, w tym potencjalnego, który <a href="https://delta.chat/chatmail#selfhosted">możesz skonfigurować samodzielnie bez naszej zgody</a>. Witamy w potędze interoperacyjnego i ogromnego systemu chatmail i e-mail :)</p>
<h2 id="szyfrowanie-i-bezpieczeństwo"> <h2 id="e2ee">
Szyfrowanie i bezpieczeństwo <a href="#szyfrowanie-i-bezpieczeństwo" class="anchor"></a> Szyfrowanie i bezpieczeństwo <a href="#e2ee" class="anchor"></a>
</h2> </h2>
@ -605,9 +602,21 @@ nadal będziesz mógł pisać, ale nie będziesz już powiadamiany o żadnych no
</h3> </h3>
<p><a href="https://autocrypt.org">Autocrypt</a> służy do automatycznego ustanawiania szyfrowania end-to-end kontaktów i czatów grupowych. Autocrypt wykorzystuje ograniczony i <a href="#openpgp-secure">bezpieczny podzbiór standardu OpenPGP</a>. W pełni zaszyfrowane wiadomości są oznaczone kłódką <img style="vertical-align:middle; width:1.2em; margin:1px" src="../lock-icon.png" alt="padlock" />.</p> <p>Delta Chat wykorzystuje <a href="#openpgp-secure">bezpieczny podzbiór standardu OpenPGP</a> do automatycznego szyfrowania typu end-to-end za pomocą następujących protokołów:</p>
<p><a href="https://securejoin.delta.chat/en/latest/new.html">Protokoły Secure-Join</a> służą do nawiązywania rozmów z gwarantowanym szyfrowaniem typu end-to-end, które chroni przed atakami sieciowymi i zagrożonymi serwerami. Czaty oznaczone zielonym znacznikiem wyboru <img style="vertical-align:middle; width:1.5em; margin:1px" src="../green-checkmark.png" alt="green checkmark" /> gwarantują szyfrowanie end-to-end wiadomości.</p> <ul>
<li>
<p><a href="https://securejoin.delta.chat/en/latest/new.html">Secure-Join</a> do wymiany informacji o konfiguracji szyfrowania poprzez skanowanie kodów QR lub „linki zaproszeń”.</p>
</li>
<li>
<p><a href="https://autocrypt.org">Autocrypt</a> służy do automatycznego ustanawiania szyfrowania typu end-to-end między kontaktami a wszystkimi członkami czatu grupowego.</p>
</li>
<li>
<p><a href="https://github.com/chatmail/core/blob/main/spec.md#attaching-a-contact-to-a-message">Udostępnienie kontaktu na czacie</a> umożliwia odbiorcom korzystanie z szyfrowania typu end-to-end z tym kontaktem.</p>
</li>
</ul>
<p>Delta Chat nie wysyła zapytań, nie publikuje ani nie wchodzi w interakcję z żadnymi serwerami kluczy OpenPGP.</p>
<h3 id="whene2e"> <h3 id="whene2e">
@ -617,100 +626,66 @@ nadal będziesz mógł pisać, ale nie będziesz już powiadamiany o żadnych no
</h3> </h3>
<p>Wszystkie całkowicie zaszyfrowane wiadomości są oznaczone kłódką:</p> <p>Wszystkie wiadomości w Delta Chat są <strong>domyślnie szyfrowane metodą end-to-end</strong>. Od wydania Delta Chat w wersji 2 (lipiec 2025 r.) nie ma już blokad ani podobnych znaczników na wiadomościach szyfrowanych metodą end-to-end.</p>
<p><img style="width:160px; margin:1px" src="../lock-screenshot.png" alt="padlock in bubble" /></p> <h3 id="czy-nadal-mogę-odbierać-lub-wysyłać-wiadomości-bez-szyfrowania-end-to-end">
<p>Pełne szyfrowanie jest gwarantowane, jeśli obok tytułu czatu znajduje się zielony znacznik wyboru:</p>
<p><img style="width:211px; margin:1px" src="../green-checkmark-screenshot.png" alt="green checkmark in title" /></p>
<h3 id="howtoe2ee">
Jak mogę uzyskać gwarancję kompleksowego szyfrowania i zielone znaczniki wyboru? <a href="#howtoe2ee" class="anchor"></a> Czy nadal mogę odbierać lub wysyłać wiadomości bez szyfrowania end-to-end? <a href="#czy-nadal-mogę-odbierać-lub-wysyłać-wiadomości-bez-szyfrowania-end-to-end" class="anchor"></a>
</h3> </h3>
<p>Jeśli masz drugi kanał komunikacji ze swoim partnerem na czacie, np. czat wideo lub inny komunikator, możesz wygenerować link zaproszenia.</p> <p>Jeśli korzystasz z domyślnych <a href="https://chatmail.at/relays">przekaźników chatmail</a>, odbieranie ani wysyłanie wiadomości bez szyfrowania end-to-end jest niemożliwe.</p>
<p>Jeśli jesteście razem osobiście, możesz pokazać kod QR swojemu rozmówcy.</p> <p>Jeśli zamiast tego utworzysz profil przy użyciu klasycznego serwera poczty e-mail, możesz wysyłać i odbierać wiadomości bez szyfrowania end-to-end. Takie wiadomości bez szyfrowania end-to-end są oznaczone ikoną e-mail <img style="vertical-align:middle; width:1.2em; margin:1px" src="../email-icon.png" alt="email" />.</p>
<h3 id="howtoe2ee">
Jak mogę nawiązać czat z nowym kontaktem? <a href="#howtoe2ee" class="anchor"></a>
</h3>
<p>Możesz wysłać link z zaproszeniem za pośrednictwem innego prywatnego czatu, wyświetlić kod QR zaproszenia, gdy kontakty znajdują się obok siebie lub w rozmowie wideo, albo dotknąć „kontakt”, który został udostępniony na czacie.</p>
<ul> <ul>
<li> <li>
<p>W przypadku <strong>zaproszeń grupowych</strong> dotknij tytułu czatu grupy, aby wyświetlić listę jej członków, i wybierz „Kod QR zaproszenia”.</p> <p>W przypadku <strong>zaproszeń grupowych</strong> dotknij tytułu czatu grupy, aby wyświetlić listę jej członków, i wybierz „Kod QR zaproszenia”.</p>
</li> </li>
<li> <li>
<p>Aby uzyskać <strong>bezpośrednie zaproszenia na czat 1:1</strong>, dotknij ikony kodu QR <img style="vertical-align:middle; width:1.8em; margin:1px" src="../qr-icon.png" /> na ekranie głównym aplikacji Delta Chat.</p> <p>Aby <strong>wysłać zaproszenie do czatu 1:1</strong>, dotknij ikony kodu QR <img style="vertical-align:middle; width:1.8em; margin:1px" src="../qr-icon.png" /> na ekranie głównym aplikacji Delta Chat.</p>
</li> </li>
</ul> </ul>
<p>Pozwól swojemu partnerowi czatu zeskanować obraz QR za pomocą aplikacji Delta Chat lub dotknij „Kopiuj” lub „Udostępnij”, aby utworzyć link zaproszenia i udostępnić go swojemu partnerowi czatu.</p> <p>Poproś rozmówcę o zeskanowanie obrazu QR za pomocą aplikacji Delta Chat lub dotknij „Kopiuj” lub „Udostępnij”, aby utworzyć link zaproszenia i udostępnić go rozmówcy.</p>
<p>Teraz poczekaj, aż między obydwoma urządzeniami <a href="https://securejoin.delta.chat/en/latest/new.html#setup-contact-protocol">nastąpi wymiana wiadomości sieciowych Secure-Join</a>.</p> <p>Poczekaj, aż <a href="https://securejoin.delta.chat/en/latest/new.html#setup-contact-protocol">szyfrowanie typu end-to-end zostanie nawiązane</a>.</p>
<ul> <ul>
<li> <li>
<p>Jeśli oba urządzenia są w trybie online, obie strony ostatecznie zobaczą czat (grupowy lub bezpośredni) z zielonym znacznikiem wyboru <img style="vertical-align:middle; width:1.5em; margin:1px" src="../green-checkmark.png" alt="green checkmark" /> obok tytułu.</p> <p>Jeśli obie strony są online, wkrótce zobaczą czat (grupowy lub bezpośredni) i będą mogły bezpiecznie wysyłać wiadomości.</p>
</li> </li>
<li> <li>
<p>Jeśli jedno z urządzeń jest w trybie offline, zielone znaczniki wyboru pojawią się później, dopiero gdy urządzenie zostanie ponownie połączone z Internetem i zostanie zrealizowany protokół sieciowy Secure-Join.</p> <p>Jeśli jedna ze stron jest offline lub ma słaby zasięg, możliwość czatowania zostanie wstrzymana do czasu przywrócenia połączenia.</p>
</li> </li>
</ul> </ul>
<p>Gratulacje! Teraz będziecie automatycznie korzystać z gwarantowanego kompleksowego szyfrowania tego kontaktu i oboje będziecie mogli dodawać się nawzajem do grup oznaczonych zielonym znacznikiem wyboru <img style="vertical-align:middle; width:1.5em; margin:1px" src="../green-checkmark.png" alt="green checkmark" /> , w ten sposób automatycznie rozpowszechniając gwarantowane kompleksowe szyfrowanie wśród swoich członków.</p> <p>Gratulacje! Teraz będziesz automatycznie korzystać z szyfrowania typu end-to-end dla tego kontaktu. Jeśli dodacie się nawzajem do czatów grupowych, szyfrowanie typu end-to-end zostanie nawiązane między wszystkimi członkami.</p>
<h3 id="e2eeguarantee"> <h3 id="e2eeguarantee">
Co oznacza zielony znacznik wyboru i „gwarantowane kompleksowe szyfrowanie”? <a href="#e2eeguarantee" class="anchor"></a> Co oznacza zielony znacznik wyboru w profilu kontaktu? <a href="#e2eeguarantee" class="anchor"></a>
</h3> </h3>
<p>Tytuły czatów z zielonymi znacznikami wyboru <img style="vertical-align:middle; width:1.5em; margin:1px" src="../green-checkmark.png" alt="green checkmark" /> oznaczają, że wszystkie wiadomości na czacie będą w pełni szyfrowane i nie będą mogły zostać odczytane ani zmodyfikowane przez zhakowane serwery poczty e-mail lub dostawców Internetu. Dołączanie do czatów grupowych oznaczonych zielonym znacznikiem bezpiecznie rozpowszechnia informacje o szyfrowaniu wszystkich osób (i zielone znaczniki wyboru) w sposób gwarantujący kompleksowe szyfrowanie w grupie i pomiędzy członkami.</p> <p>Profil kontaktu może wyświetlać zielony znacznik wyboru <img style="vertical-align:middle; width:1.5em; margin:1px" src="../green-checkmark.png" alt="green checkmark" /> i wiersz „Zweryfikowano przez…”. Każdy kontakt oznaczony zielonym znacznikiem albo wykonał z tobą bezpośrednie <a href="#howtoe2ee">skanowanie QR</a>, albo został zweryfikowany przez inny kontakt oznaczony zielonym znacznikiem. Weryfikacje odbywają się automatycznie podczas dodawania członków do grup. Osoba, która doda kontakt oznaczony zielonym znacznikiem wyboru do grupy zawierającej wyłącznie członków oznaczonych zielonym znacznikiem wyboru, staje się osobą weryfikującą. W profilu kontaktu możesz wielokrotnie dotykać tekstu „Zweryfikowano przez…”, aż dojdziesz do osoby, z którą bezpośrednio wykonałeś <a href="#howtoe2ee">skanowanie QR</a>.</p>
<p>Profile kontaktów z zielonymi znacznikami wyboru <img style="vertical-align:middle; width:1.5em; margin:1px" src="../green-checkmark.png" alt="green checkmark" /> oznaczają, że obecnie gwarantujemy, że wiadomości kontaktu będą szyfrowane metodą end-to-end. Każdy kontakt oznaczony zielonym znacznikiem albo wykonał z tobą bezpośrednie <a href="#howtoe2ee">skanowanie QR</a>, albo został zweryfikowany przez inny kontakt oznaczony zielonym znacznikiem. Weryfikacje odbywają się automatycznie podczas dodawania członków do grup. Ktokolwiek doda kontakt do grupy oznaczonej zielonym znacznikiem, staje się osobą weryfikującą dla tych członków, którzy jeszcze nie wiedzieli o dodanym kontakcie. W profilu kontaktu możesz wielokrotnie dotykać tekstu „Zweryfikowano przez…”, aż dojdziesz do osoby, z którą bezpośrednio wykonałeś <a href="#howtoe2ee">skanowanie QR</a>.</p>
<p>Pamiętaj, że w profilu kontaktu możesz widzieć i klikać osoby weryfikujące, ale w tytule profilu nie ma zielonego znacznika wyboru. Zwykle oznacza to, że kontakt <a href="#nocryptanymore">„wysłał wiadomość z innego urządzenia”</a>.</p>
<p>Aby uzyskać bardziej szczegółowe omówienie „gwarantowanego szyfrowania typu end-to-end”, zobacz <a href="https://securejoin.delta.chat/en/latest/new.html">Protokoły Secure-Join</a>, a w szczególności przeczytaj o „zweryfikowanych grupach”, technicznym określeniu tak zwanego tutaj „zielonego znacznika wyboru” lub „gwarantowanego szyfrowania end-to-end” czatów.</p> <p>Aby uzyskać bardziej szczegółowe omówienie „gwarantowanego szyfrowania typu end-to-end”, zobacz <a href="https://securejoin.delta.chat/en/latest/new.html">Protokoły Secure-Join</a>, a w szczególności przeczytaj o „zweryfikowanych grupach”, technicznym określeniu tak zwanego tutaj „zielonego znacznika wyboru” lub „gwarantowanego szyfrowania end-to-end” czatów.</p>
<h3 id="nocryptanymore">
Kontakt „wysłał wiadomość z innego urządzenia”, co mogę zrobić? <a href="#nocryptanymore" class="anchor"></a>
</h3>
<p>Twój czat z kontaktem utracił gwarantowane szyfrowanie typu end-to-end. Gdy zobaczysz to ostrzeżenie, zielony znacznik wyboru dla tego czatu i kontaktu został usunięty. <strong>Jeśli zdziwi cię nagły spadek gwarantowanego szyfrowania end-to-end tego kontaktu, nie akceptuj ostrzeżenia!</strong> Zamiast tego skontaktuj się ze swoim kontaktem za pośrednictwem drugiego kanału, takiego jak rozmowa wideo, inny komunikator lub rozmowa telefoniczna, aby dowiedzieć się, co się stało.</p>
<p>Jeśli twój kontakt rzeczywiście spowodował spadek gwarantowanego szyfrowania typu end-to-end, zapoznaj się z kolejnymi akapitami, aby poznać typowe przyczyny i sposoby ich łagodzenia. Niezależnie od tego, wszystkie inne czaty oznaczone zielonym znacznikiem są w pełni szyfrowane, nawet jeśli kontakt jest ich członkiem.</p>
<p><strong>Twój kontakt korzysta z Delta Chat na drugim urządzeniu (telefonie lub laptopie)</strong></p>
<p>Jeśli ma inne urządzenie z uruchomioną aplikacją Delta Chat, powinien usunąć konto z nowego urządzenia i dodać je <a href="#multiclient">jako drugie urządzenie zgodnie z opisem tutaj</a>. Gdy tylko skontaktuje się z tobą później, ostrzeżenie zniknie, a na obu urządzeniach twojego kontaktu zostanie ustanowione gwarantowane szyfrowanie.</p>
<p><strong>Twój kontakt ponownie zainstalował Delta Chat, używając swojego starego loginu do konta</strong></p>
<p>Jeśli ma <a href="#backup">plik kopii zapasowej</a>, powinien usunąć konto z nowego urządzenia i zamiast tego zaimportować plik kopii zapasowej, aby ponownie utworzyć konto. Gdy tylko skontaktuje się z tobą później, ostrzeżenie zniknie, a dla tego kontaktu zostanie przywrócone gwarantowane szyfrowanie.</p>
<p>Jeśli nie ma pliku kopii zapasowej, najlepiej wykonać <a href="#howtoe2ee">skanowanie QR</a> ze swoim partnerem czatu, aby przywrócić gwarantowane szyfrowanie end-to-end.</p>
<p><strong>Twój kontakt wysłał wiadomość e-mail za pośrednictwem interfejsu poczty internetowej lub innej aplikacji e-mail i wkrótce ponownie zacznie korzystać z Delta Chat.</strong></p>
<p>Jeśli masz pewność, że kontakt czasami korzysta z poczty internetowej lub innej aplikacji pocztowej, która nie zapewnia szyfrowania end-to-end, możesz zaakceptować ostrzeżenie. Gdy tylko twój kontakt ponownie skorzysta z Delta Chat, gwarantowane szyfrowanie end-to-end zostanie automatycznie przywrócone.</p>
<p><strong>Twój kontakt całkowicie przestał korzystać z Delta Chat</strong></p>
<p>Czasami utrzymanie kontaktu jest ważniejsze niż szyfrowanie end-to-end. <a href="#tls">„Szyfrowanie warstwy transportowej” (TLS)</a> może w dalszym ciągu w znaczący sposób chronić poufność wiadomości przesyłanych między urządzeniem a serwerem poczty e-mail. Jednak bez kompleksowego szyfrowania Ty i Twój kontakt ufacie swojemu serwerowi poczty e-mail, że nie będzie czytać ani manipulować waszymi wiadomościami i nie będzie przekazywać ich osobom trzecim.</p>
<p>W każdym razie nie możesz zrobić nic innego, jak zaakceptować ostrzeżenie. Usuń także kontakt z aktywnej grupy oznaczonej zielonym znacznikiem, którą znajdziesz w sekcji „Wspólne czaty” w profilu kontaktu. Dzięki temu twój kontakt nie otrzyma „nieczytelnych” wiadomości.</p>
<p>Jeśli kontakt usunął Delta Chat z powodu błędów lub niepożądanego zachowania, rozważ opublikowanie postu na naszym <a href="https://support.delta.chat">forum pomocy</a>, aby pomóc nam zidentyfikować i rozwiązać typowe problemy. Dzięki!</p>
<h3 id="czy-załączniki-zdjęcia-pliki-pliki-audio-itp-są-szyfrowane-metodą-end-to-end"> <h3 id="czy-załączniki-zdjęcia-pliki-pliki-audio-itp-są-szyfrowane-metodą-end-to-end">
@ -731,7 +706,7 @@ nadal będziesz mógł pisać, ale nie będziesz już powiadamiany o żadnych no
</h3> </h3>
<p>Tak, Delta Chat korzysta z bezpiecznego podzbioru OpenPGP i wyświetla wskaźnik bezpieczeństwa kłódki na wiadomości tylko wtedy, gdy cała wiadomość jest prawidłowo zaszyfrowana i podpisana. Na przykład „Odłączone podpisy” nie są traktowane jako bezpieczne.</p> <p>Tak, Delta Chat korzysta z bezpiecznego podzbioru OpenPGP, który wymaga prawidłowego zaszyfrowania i podpisania całej wiadomości. Na przykład „Odłączone podpisy” nie są traktowane jako bezpieczne.</p>
<p>OpenPGP samo w sobie nie jest niebezpieczne. Większość publicznie omawianych problemów związanych z bezpieczeństwem OpenPGP tak naprawdę wynika ze złej użyteczności lub złej implementacji narzędzi, lub aplikacji (lub obu). Szczególnie ważne jest rozróżnienie pomiędzy OpenPGP, standardem szyfrowania IETF, a GnuPG (GPG), narzędziem wiersza poleceń implementującym OpenPGP. Wiele publicznych komentarzy krytycznych na temat OpenPGP tak naprawdę omawia GnuPG, którego Delta Chat nigdy nie używał. Delta Chat korzysta raczej z implementacji OpenPGP Rust <a href="https://github.com/rpgp/rpgp">rPGP</a>, dostępnej jako <a href="https://crates.io/crates/pgp">niezależny pakiet „pgp”</a> i poddanej <a href="#security-audits">audytowi bezpieczeństwa w 2019 i 2024 roku</a>.</p> <p>OpenPGP samo w sobie nie jest niebezpieczne. Większość publicznie omawianych problemów związanych z bezpieczeństwem OpenPGP tak naprawdę wynika ze złej użyteczności lub złej implementacji narzędzi, lub aplikacji (lub obu). Szczególnie ważne jest rozróżnienie pomiędzy OpenPGP, standardem szyfrowania IETF, a GnuPG (GPG), narzędziem wiersza poleceń implementującym OpenPGP. Wiele publicznych komentarzy krytycznych na temat OpenPGP tak naprawdę omawia GnuPG, którego Delta Chat nigdy nie używał. Delta Chat korzysta raczej z implementacji OpenPGP Rust <a href="https://github.com/rpgp/rpgp">rPGP</a>, dostępnej jako <a href="https://crates.io/crates/pgp">niezależny pakiet „pgp”</a> i poddanej <a href="#security-audits">audytowi bezpieczeństwa w 2019 i 2024 roku</a>.</p>
@ -764,17 +739,15 @@ nadal będziesz mógł pisać, ale nie będziesz już powiadamiany o żadnych no
<h3 id="tls"> <h3 id="tls">
Czy wiadomość jest udostępniana w postaci zwykłego tekstu, jeśli szyfrowanie end-to-end nie jest dostępne? <a href="#tls" class="anchor"></a> Czy wiadomości oznaczone ikoną poczty są widoczne w internecie? <a href="#tls" class="anchor"></a>
</h3> </h3>
<p>Nawet jeśli nie ma gwarancji, że twoje wiadomości będą zaszyfrowane metodą end-to-end, nadal są chronione przed dostawcami Internetu, takimi jak operatorzy komórkowi lub telewizji kablowej. Jednakże dostawcy poczty e-mail zarówno twoi, jak i twojego odbiorcy mogą czytać, analizować, a nawet modyfikować twoje wiadomości, w tym wszelkie załączniki, jeśli nie są one w pełni zaszyfrowane.</p> <p>Jeśli wysyłasz lub odbierasz wiadomości e-mail bez szyfrowania end-to-end (korzystając z klasycznego serwera poczty), są one nadal chronione przed operatorami komórkowymi lub kablowymi, którzy nie mogą ich czytać ani modyfikować. Jednak zarówno twoi dostawcy poczty e-mail, jak i dostawcy poczty e-mail odbiorcy mogą czytać, analizować lub modyfikować twoje wiadomości, w tym wszelkie załączniki.</p>
<p>Delta Chat domyślnie korzysta ze ścisłego <a href="https://en.wikipedia.org/wiki/Transport_Layer_Security">szyfrowania TLS</a>, które zabezpiecza połączenia pomiędzy twoim urządzeniem a dostawcą poczty e-mail. Cała obsługa TLS Delta Chat została poddana niezależnemu <a href="#security-audits">audytowi bezpieczeństwa</a>. Co więcej, połączenie między tobą a dostawcą poczty e-mail odbiorcy będzie zazwyczaj również szyfrowane. Jeśli zaangażowane serwery poczty e-mail obsługują <a href="https://datatracker.ietf.org/doc/html/rfc8461">MTA-STS</a>, pomiędzy dostawcami poczty e-mail będzie egzekwowane szyfrowanie transportu. W takim przypadku komunikacja Delta Chat nigdy nie będzie udostępniana w Internecie w postaci zwykłego tekstu, nawet jeśli wiadomość nie została zaszyfrowana metodą end-to-end.</p> <p>Delta Chat domyślnie korzysta ze ścisłego <a href="https://en.wikipedia.org/wiki/Transport_Layer_Security">szyfrowania TLS</a>, które zabezpiecza połączenia pomiędzy twoim urządzeniem a dostawcą poczty e-mail. Cała obsługa TLS Delta Chat została poddana niezależnemu <a href="#security-audits">audytowi bezpieczeństwa</a>. Co więcej, połączenie między tobą a dostawcą poczty e-mail odbiorcy będzie zazwyczaj również szyfrowane. Jeśli zaangażowane serwery poczty e-mail obsługują <a href="https://datatracker.ietf.org/doc/html/rfc8461">MTA-STS</a>, pomiędzy dostawcami poczty e-mail będzie egzekwowane szyfrowanie transportu. W takim przypadku komunikacja Delta Chat nigdy nie będzie udostępniana w Internecie w postaci zwykłego tekstu, nawet jeśli wiadomość nie została zaszyfrowana metodą end-to-end.</p>
<p>Pamiętaj, że <a href="#howtoe2ee">utrzymywanie gwarantowanego szyfrowania typu end-to-end</a> oprócz szyfrowania TLS zapewnia wszechstronne bezpieczeństwo między urządzeniami twoimi i odbiorców. Nawet twój dostawca poczty e-mail lub Internetu nie będzie w stanie przeczytać ani zmodyfikować twoich wiadomości.</p>
<h3 id="message-metadata"> <h3 id="message-metadata">
@ -783,20 +756,23 @@ nadal będziesz mógł pisać, ale nie będziesz już powiadamiany o żadnych no
</h3> </h3>
<p>Delta Chat chroni większość metadanych wiadomości, umieszczając następujące informacje w całkowicie zaszyfrowanej części wiadomości:</p> <p>W przeciwieństwie do większości innych komunikatorów, aplikacje Delta Chat nie przechowują żadnych metadanych dotyczących kontaktów ani grup na serwerach, również w formie zaszyfrowanej. Zamiast tego wszystkie metadane grup są szyfrowane metodą end-to-end i przechowywane wyłącznie na urządzeniach użytkowników końcowych.</p>
<p>Serwery poczty e-mail widzą zatem tylko:</p>
<ul> <ul>
<li>Wiersz tematu</li> <li>
<li>Awatar i nazwa grupy</li> <p>datę wysłania wiadomości,</p>
<li>Żądania MDN (potwierdzenie odczytu) (<code class="language-plaintext highlighter-rouge">Chat-Disposition-Notification-To</code>)</li> </li>
<li>Licznik czasu znikania wiadomości (<code class="language-plaintext highlighter-rouge">Ephemeral-Timer</code>)</li> <li>
<li><code class="language-plaintext highlighter-rouge">Chat-Group-Member-Removed</code>, <code class="language-plaintext highlighter-rouge">Chat-Group-Member-Added</code></li> <p>adresy nadawcy i odbiorcy,</p>
<li>Nagłówek <code class="language-plaintext highlighter-rouge">Secure-Join</code> zawierający polecenia bezpiecznego łączenia</li> </li>
<li>Powiadomienie o włączeniu przesyłania strumieniowego lokalizacji</li> <li>
<li>Adres URL pokoju WebRTC</li> <p>oraz rozmiar wiadomości.</p>
</li>
</ul> </ul>
<p>Serwery poczty e-mail nie mają dostępu do chronionych metadanych, ale widzą datę wiadomości, jej rozmiar oraz, co ważniejsze, adresy nadawcy i odbiorcy. Serwery poczty e-mail potrzebują adresów odbiorców, aby kierować i dostarczać wiadomości do urządzeń odbiorców.</p> <p>Wszystkie pozostałe metadane dotyczące wiadomości, kontaktów i grup znajdują się w zaszyfrowanej metodą end-to-end części wiadomości.</p>
<h3 id="device-seizure"> <h3 id="device-seizure">
@ -806,61 +782,36 @@ nadal będziesz mógł pisać, ale nie będziesz już powiadamiany o żadnych no
</h3> </h3>
<p>Zarówno w celu ochrony przed serwerami poczty e-mail gromadzącymi metadane, jak i przed zagrożeniem przejęcia urządzenia, zalecamy użycie zoptymalizowanej <a href="https://delta.chat/pl/serverguide">instancji serwera poczty e-mail</a> Delta Chat w celu tworzenia pseudonimowych kont tymczasowych poprzez skanowanie kodów QR. Pamiętaj, że aplikacje Delta Chat na wszystkich platformach obsługują wiele kont, dzięki czemu możesz z łatwością korzystać z kont „1-tygodniowych” lub „1-miesięcznych” związanych z konkretnymi działaniami obok konta „głównego”, wiedząc, że wszystkie tymczasowe dane konta wraz ze wszystkimi metadanymi zostaną usunięte. Co więcej, jeśli urządzenie zostanie przejęte, nie będzie można łatwo zidentyfikować kontaktów korzystających z tymczasowych kont e-mail, w porównaniu z komunikatorami, które ujawniają numery telefonów w grupach czatów, które z kolei często są powiązane z tożsamością prawną.</p> <p>Both for protecting against metadata-collecting e-mail servers
as well as against the threat of device seizure
we recommend to use a <a href="https://chatmail.at/relays">chatmail relay</a>
to create chat profiles using random e-mail addresses for transport.
Note that Delta Chat apps on all platforms support multiple profiles
so you can easily use situation-specific profiles next to your “main” profile
with the knowledge that all their data, along with all metadata, will be deleted.
Moreover, if a device is seized then chat contacts using short-lived profiles
can not be identified easily.</p>
<h3 id="jak-mogę-sprawdzić-informacje-o-szyfrowaniu"> <h3 id="sealedsender">
Jak mogę sprawdzić informacje o szyfrowaniu? <a href="#jak-mogę-sprawdzić-informacje-o-szyfrowaniu" class="anchor"></a> Does Delta Chat support “Sealed Sender”? <a href="#sealedsender" class="anchor"></a>
</h3> </h3>
<p>Możesz sprawdzić stan szyfrowania end-to-end ręcznie w oknie dialogowym „Szyfrowanie” (profil użytkownika w systemie Android/iOS lub kliknij prawym przyciskiem myszy element listy czatu użytkownika na komputerze). Delta Chat pokazuje tam dwa odciski palców. Jeśli te same odciski palców pojawią się u ciebie i urządzeniu twojego kontaktu, połączenie jest bezpieczne.</p> <p>No, not yet.</p>
<h3 id="jak-mogę-sprawdzić-stan-szyfrowania-wiadomości"> <p>The Signal messenger introduced <a href="https://signal.org/blog/sealed-sender/">“Sealed Sender” in 2018</a>
to keep their server infrastructure ignorant of who is sending a message to a set of recipients.
It is particularly important because the Signal server knows the mobile number of each account,
which is usually associated with a passport identity.</p>
<p>Even if <a href="https://chatmail.at/relays">chatmail relays</a>
Jak mogę sprawdzić stan szyfrowania wiadomości? <a href="#jak-mogę-sprawdzić-stan-szyfrowania-wiadomości" class="anchor"></a> do not ask for any private data (including no phone numbers),
it might still be worthwhile to protect relational metadata between addresses.
We don’t foresee bigger problems in using random throw-away e-mail addresses for sealed sending
</h3> but an implementation has not been agreed as a priority yet.</p>
<p>Mała <strong>kłódka</strong> w dymku wiadomości oznacza, że wiadomość od danego nadawcy została prawidłowo zaszyfrowana. Jeśli <strong>nie ma kłódki</strong>, wiadomość nie została prawidłowo zaszyfrowana metodą end-to-end, najprawdopodobniej dlatego, że nadawca korzysta z aplikacji lub interfejsu poczty internetowej bez obsługi szyfrowania typu end-to-end.</p>
<h3 id="dlaczego-widzę-niezaszyfrowane-wiadomości">
Dlaczego widzę niezaszyfrowane wiadomości? <a href="#dlaczego-widzę-niezaszyfrowane-wiadomości" class="anchor"></a>
</h3>
<p>Jeśli kontakt korzysta z aplikacji e-mail bez Autocrypt, wszystkie wiadomości od tego kontaktu (w czacie grupowym lub 1:1) nie będą w pełni szyfrowane, w związku z czym nie będą wyświetlane z „kłódką” przy wiadomościach. Pamiętaj, że nawet jeśli twoje kontakty korzystają z Delta Chat na swoim koncie, mogą również używać na tym koncie aplikacji e-mail bez Autocrypt, co może powodować sporadyczne wysyłanie niezaszyfrowanych wiadomości. Odpowiadanie niezaszyfrowanych wiadomości na niezaszyfrowane wiadomości jest wymagane przez funkcję Autocrypt, aby zapobiec nieczytelnym wiadomościom po stronie twoich kontaktów i ich aplikacji e-mail bez Autocrypt.</p>
<h3 id="jak-mogę-uzyskać-zaszyfrowany-ened-to-end-czat-z-kontaktem-delta-chat-który-czasami-korzysta-z-poczty-internetowej-lub-innej-aplikacji-e-mail-bez-autocrypt">
Jak mogę uzyskać zaszyfrowany ened-to-end czat z kontaktem Delta Chat, który czasami korzysta z poczty internetowej lub innej aplikacji e-mail bez Autocrypt? <a href="#jak-mogę-uzyskać-zaszyfrowany-ened-to-end-czat-z-kontaktem-delta-chat-który-czasami-korzysta-z-poczty-internetowej-lub-innej-aplikacji-e-mail-bez-autocrypt" class="anchor"></a>
</h3>
<p>Jeśli potrzebujesz bezpiecznie, kompleksowo zaszyfrowanego czatu z kontaktem, który korzysta ze swojego konta zarówno w Delta Chat, jak i w aplikacjach bez Autocrypt (np. poczta internetowa), najlepiej skonfigurować z nim gwarantowane szyfrowanie typu end-to-end, a następnie utworzyć <a href="#howtoe2ee">gwarantowany zaszyfrowany end-to-end</a> czat grupowy z wami dwoma jako członkami. W tym czacie grupowym wszystkie wiadomości będą w pełni szyfrowane, nawet jeśli bezpośredni czat między wami zawiera ostrzeżenie <a href="#nocryptanymore">„…wysłano wiadomość z innego urządzenia”</a>.</p>
<h3 id="jak-mogę-zapewnić-kompleksowe-szyfrowanie-i-usuwanie-wiadomości">
Jak mogę zapewnić kompleksowe szyfrowanie i usuwanie wiadomości? <a href="#jak-mogę-zapewnić-kompleksowe-szyfrowanie-i-usuwanie-wiadomości" class="anchor"></a>
</h3>
<p>Najlepszym sposobem, aby mieć pewność, że każda wiadomość jest kompleksowo zaszyfrowana, a metadane usunięte tak szybko, jak to możliwe, jest <a href="#howtoe2ee">korzystanie z czatów z gwarantowanym szyfrowaniem end-to-end</a> i włączonymi <a href="#ephemeralmsgs">znikającymi wiadomościami</a>.</p>
<p>Gwarantowane szyfrowane metodą end-to-end czaty chronią przed atakami <a href="https://en.wikipedia.org/wiki/Man-in-the-middle_attack">MITM attacks</a>, a włączenie znikających wiadomości powoduje usunięcie wiadomości z serwera po upływie czasu skonfigurowanego przez użytkownika.</p>
<p>Jeśli nie potrzebujesz dłuższej kopii wiadomości na serwerze, możesz także włączyć opcję <a href="#delold">„automatycznie usuń wiadomości z serwera”</a>.</p>
<h3 id="pfs"> <h3 id="pfs">
@ -870,23 +821,48 @@ nadal będziesz mógł pisać, ale nie będziesz już powiadamiany o żadnych no
</h3> </h3>
<p>Nie, Delta Chat nie obsługuje funkcji Perfect Forward Secrecy (PFS). Oznacza to, że jeśli twój prywatny klucz deszyfrujący Delta Chat wycieknie i ktoś zdobędzie twoje wcześniejsze wiadomości w trakcie przesyłania, będzie mógł je odszyfrować i odczytać przy użyciu ujawnionego klucza deszyfrowania.</p> <p>No, not yet.</p>
<p>Należy jednak pamiętać, że jeśli ktoś zdobędzie twoje klucze deszyfrujące, zazwyczaj będzie mógł również uzyskać twoje wiadomości, niezależnie od tego, czy obowiązuje zasada Perfect Forward Secrecy, czy nie. Typową sytuacją w świecie rzeczywistym w przypadku wycieku kluczy deszyfrujących jest przejęcie urządzenia, które omawiamy w naszej odpowiedzi na temat <a href="#device-seizure">przejęcia metadanych i urządzenia</a>.</p> <p>Delta Chat today doesn’t support Perfect Forward Secrecy (PFS).
This means that if your private decryption key is leaked,
and someone has collected your prior in-transit messages,
they will be able to decrypt and read them using the leaked decryption key.
Note that Forward Secrecy only increases security if you delete messages.
Otherwise, someone obtaining your decryption keys
is typically also able to get all your non-deleted messages
and doesn’t even need to decrypt any previously collected messages.</p>
<p>Możliwe, że Delta Chat ewoluuje, aby wspierać Perfect Forward Secrecy, ponieważ OpenPGP to tylko kontener na zaszyfrowane wiadomości, ale zarządzanie kluczami szyfrowania (a tym samym rotacja kluczy lub „zapadanie kluczy”) mogłoby być zorganizowane w elastyczny sposób. Zobacz <a href="https://gitlab.com/sequoia-pgp/openpgp-dr">prototyp PFS firmy Seqouia</a>, aby zapoznać się z istniejącymi eksperymentami w społeczności implementatorów OpenPGP.</p> <p>We designed a Forward Secrecy approach that withstood
initial examination from some cryptographers and implementation experts
but is pending a more formal write up
to ascertain it reliably works in federated messaging and with multi-device usage,
before it could be implemented in <a href="https://github.com/chatmail/core">chatmail core</a>,
which would make it available in all <a href="https://chatmail.at/clients">chatmail clients</a>.</p>
<h3 id="czy-szyfrowanie-end-to-end-delta-chat-jest-tak-samo-bezpieczne-jak-signal"> <h3 id="pqc">
Czy szyfrowanie end-to-end Delta Chat jest tak samo bezpieczne jak Signal? <a href="#czy-szyfrowanie-end-to-end-delta-chat-jest-tak-samo-bezpieczne-jak-signal" class="anchor"></a> Does Delta Chat support Post-Quantum-Cryptography? <a href="#pqc" class="anchor"></a>
</h3> </h3>
<p>To zależy od tego, co jest dla ciebie ważne. Delta Chat <a href="#pfs">nie obsługuje PFS</a> tak jak Signal, ale zapewnia <a href="#e2eeguarantee">gwarantowane szyfrowane end-to-end czatów</a>, które jest zabezpieczeniem przed zaatakowanymi serwerami lub uszkodzonymi sieciami. Signal i większość innych komunikatorów obsługujących PFS nie zapewniają praktycznego schematu ochrony czatów grupowych przed atakami sieciowymi, które są prawdopodobnie bardziej niepokojące niż potencjalny atakujący, który przejmuje twój telefon i prywatne ustawienia szyfrowania i w ten sposób nie twoje wiadomości i mimo to ma pełny zapis wszystkich poprzednio zaszyfrowanych wiadomości.</p> <p>No, not yet.</p>
<p>W każdym razie szyfrowanie end-to-end Delta Chat wykorzystuje <a href="#openpgp-secure">bezpieczny podzbiór OpenPGP</a>, który został poddany <a href="https://delta.chat/assets/blog/2019-first-security-review.pdf">niezależnemu audytowi bezpieczeństwa</a>.</p> <p>Delta Chat uses the Rust OpenPGP library <a href="https://github.com/rpgp/rpgp">rPGP</a>
which supports the latest <a href="https://datatracker.ietf.org/doc/draft-ietf-openpgp-pqc/">IETF Post-Quantum-Cryptography OpenPGP draft</a>.
We aim to add PQC support in <a href="https://github.com/chatmail/core">chatmail core</a> after the draft is finalized at the IETF
in collaboration with other OpenPGP implementers.</p>
<h3 id="how-can-i-manually-check-encryption-information">
How can I manually check encryption information? <a href="#how-can-i-manually-check-encryption-information" class="anchor"></a>
</h3>
<p>Możesz sprawdzić stan szyfrowania end-to-end ręcznie w oknie dialogowym „Szyfrowanie” (profil użytkownika w systemie Android/iOS lub kliknij prawym przyciskiem myszy element listy czatu użytkownika na komputerze). Delta Chat pokazuje tam dwa odciski palców. Jeśli te same odciski palców pojawią się u ciebie i urządzeniu twojego kontaktu, połączenie jest bezpieczne.</p>
<h3 id="importkey"> <h3 id="importkey">
@ -1208,6 +1184,11 @@ Listy rozgłoszeniowe są nadal wysoce eksperymentalne i bardzo prawdopodobne,
</h3> </h3>
<p>Note:
Changing email addresses is temporarily disabled
because of ongoing changes to the DeltaChat core.
It should be available again in a few months.</p>
<ol> <ol>
<li> <li>
<p>Zmień swój adres w „Ustawienia → Zaawansowane → Hasło i konto” i wprowadź hasło do swojego nowego konta (i jeśli to konieczne, ustawienia serwera). Otrzymasz informację o przeniesieniu na nowy adres. Dodatkowe powiadomienie pojawi się również na czacie „Komunikaty urządzenia”.</p> <p>Zmień swój adres w „Ustawienia → Zaawansowane → Hasło i konto” i wprowadź hasło do swojego nowego konta (i jeśli to konieczne, ustawienia serwera). Otrzymasz informację o przeniesieniu na nowy adres. Dodatkowe powiadomienie pojawi się również na czacie „Komunikaty urządzenia”.</p>
@ -1281,19 +1262,17 @@ Oto, co robi Delta Chat z tymi uprawnieniami:</p>
Jednak niektórzy dostawcy potrzebują specjalnych opcji, aby działać poprawnie, zobacz <a href="https://providers.delta.chat">Przegląd dostawców</a></li> Jednak niektórzy dostawcy potrzebują specjalnych opcji, aby działać poprawnie, zobacz <a href="https://providers.delta.chat">Przegląd dostawców</a></li>
</ul> </ul>
<h3 id="i-want-to-manage-my-own-server-for-delta-chat-what-do-you-recommend"> <h3 id="chcę-zarządzać-własnym-serwerem-dla-delta-chat-co-polecacie">
I want to manage my own server for Delta Chat. What do you recommend? <a href="#i-want-to-manage-my-own-server-for-delta-chat-what-do-you-recommend" class="anchor"></a> Chcę zarządzać własnym serwerem dla Delta Chat. Co polecacie? <a href="#chcę-zarządzać-własnym-serwerem-dla-delta-chat-co-polecacie" class="anchor"></a>
</h3> </h3>
<ul> <ul>
<li>Most mail servers will work well. But what we personally recommend is a <li>Większość serwerów pocztowych będzie działać dobrze. Ale my osobiście polecamy serwer przekaźnikowy chatmail, jak opisano <a href="https://delta.chat/en/2023-12-13-chatmail">w tym wpisie na blogu</a>.</li>
chatmail relay server, as described <a href="https://delta.chat/en/2023-12-13-chatmail">in this <li>Możesz znaleźć <a href="https://github.com/chatmail/relay">przewodnik instalacji na GitHub</a>.</li>
blogpost</a>.</li>
<li>You can find an <a href="https://github.com/chatmail/relay">installation guide on GitHub</a>.</li>
</ul> </ul>
<h3 id="dlaczego-muszę-wpisać-moje-hasło-e-mail-do-delta-chat-czy-to-jest-bezpieczne"> <h3 id="dlaczego-muszę-wpisać-moje-hasło-e-mail-do-delta-chat-czy-to-jest-bezpieczne">

420
src/main/assets/help/pt/help.html
View file

@ -36,27 +36,24 @@
<li><a href="#why-does-delta-chat-integrate-with-centralized-proprietary-applegoogle-push-services">Why does Delta Chat integrate with centralized proprietary Apple/Google push services?</a></li> <li><a href="#why-does-delta-chat-integrate-with-centralized-proprietary-applegoogle-push-services">Why does Delta Chat integrate with centralized proprietary Apple/Google push services?</a></li>
</ul> </ul>
</li> </li>
<li><a href="#encryption-and-security">Encryption and Security</a> <li><a href="#e2ee">Encryption and Security</a>
<ul> <ul>
<li><a href="#which-standards-are-used-for-end-to-end-encryption">Which standards are used for end-to-end encryption?</a></li> <li><a href="#which-standards-are-used-for-end-to-end-encryption">Which standards are used for end-to-end encryption?</a></li>
<li><a href="#whene2e">How can i know if messages are end-to-end encrypted?</a></li> <li><a href="#whene2e">How can i know if messages are end-to-end encrypted?</a></li>
<li><a href="#howtoe2ee">How can I get guaranteed end-to-end encryption and green checkmarks?</a></li> <li><a href="#can-i-still-receive-or-send-mails-without-end-to-end-encryption">Can i still receive or send mails without end-to-end encryption?</a></li>
<li><a href="#e2eeguarantee">What does the green checkmark and “guaranteed end-to-end encryption” mean?</a></li> <li><a href="#howtoe2ee">How can I establish a chat with a new contact?</a></li>
<li><a href="#nocryptanymore">A contact “sent a message from another device”, what can i do?</a></li> <li><a href="#e2eeguarantee">What does the green checkmark in a contact profile mean?</a></li>
<li><a href="#are-attachments-pictures-files-audio-etc-end-to-end-encrypted">Are attachments (pictures, files, audio etc.) end-to-end encrypted?</a></li> <li><a href="#are-attachments-pictures-files-audio-etc-end-to-end-encrypted">Are attachments (pictures, files, audio etc.) end-to-end encrypted?</a></li>
<li><a href="#openpgp-secure">Is OpenPGP secure?</a></li> <li><a href="#openpgp-secure">Is OpenPGP secure?</a></li>
<li><a href="#openpgp-alternatives">Did you consider using alternatives to OpenPGP for end-to-end -encryption?</a></li> <li><a href="#openpgp-alternatives">Did you consider using alternatives to OpenPGP for end-to-end-encryption?</a></li>
<li><a href="#is-delta-chat-vulnerable-to-efail">Is Delta Chat vulnerable to EFAIL?</a></li> <li><a href="#is-delta-chat-vulnerable-to-efail">Is Delta Chat vulnerable to EFAIL?</a></li>
<li><a href="#tls">Is a message exposed in cleartext if end-to-end encryption is not available?</a></li> <li><a href="#tls">Are messages marked with the mail icon exposed on the Internet?</a></li>
<li><a href="#message-metadata">How does Delta Chat protect metadata in messages?</a></li> <li><a href="#message-metadata">How does Delta Chat protect metadata in messages?</a></li>
<li><a href="#device-seizure">How to protect metadata and contacts when a device is seized?</a></li> <li><a href="#device-seizure">How to protect metadata and contacts when a device is seized?</a></li>
<li><a href="#how-can-i-check-encryption-information">How can i check encryption information?</a></li> <li><a href="#sealedsender">Does Delta Chat support “Sealed Sender”?</a></li>
<li><a href="#how-can-i-check-the-encryption-status-of-messages">How can I check the encryption status of messages?</a></li>
<li><a href="#why-do-i-see-unencrypted-messages">Why do I see unencrypted messages?</a></li>
<li><a href="#how-can-i-get-an-end-to-end-encrypted-chat-with-a-delta-chat-contact-who-sometimes-uses-webmail-or-another-non-autocrypt-e-mail-app">How can i get an end-to-end encrypted chat with a Delta Chat contact who sometimes uses webmail or another non-Autocrypt e-mail app?</a></li>
<li><a href="#how-can-i-ensure-message-end-to-end-encryption-and-deletion">How can I ensure message end-to-end encryption and deletion?</a></li>
<li><a href="#pfs">Does Delta Chat support Perfect Forward Secrecy?</a></li> <li><a href="#pfs">Does Delta Chat support Perfect Forward Secrecy?</a></li>
<li><a href="#is-end-to-end-encryption-of-delta-chat-as-safe-as-signal">Is end-to-end encryption of Delta Chat as safe as Signal?</a></li> <li><a href="#pqc">Does Delta Chat support Post-Quantum-Cryptography?</a></li>
<li><a href="#how-can-i-manually-check-encryption-information">How can I manually check encryption information?</a></li>
<li><a href="#importkey">Posso reutilizar minha chave privada existente?</a></li> <li><a href="#importkey">Posso reutilizar minha chave privada existente?</a></li>
<li><a href="#security-audits">Was Delta Chat independently audited for security vulnerabilities?</a></li> <li><a href="#security-audits">Was Delta Chat independently audited for security vulnerabilities?</a></li>
</ul> </ul>
@ -720,10 +717,10 @@ that achieves “instant delivery” of messages for all chatmail servers
including a potential one <a href="https://delta.chat/chatmail#selfhosted">you might setup yourself without our permission</a>. including a potential one <a href="https://delta.chat/chatmail#selfhosted">you might setup yourself without our permission</a>.
Welcome to the power of the interoperable and massive chatmail and e-mail system :)</p> Welcome to the power of the interoperable and massive chatmail and e-mail system :)</p>
<h2 id="encryption-and-security"> <h2 id="e2ee">
Encryption and Security <a href="#encryption-and-security" class="anchor"></a> Encryption and Security <a href="#e2ee" class="anchor"></a>
</h2> </h2>
@ -736,18 +733,26 @@ Welcome to the power of the interoperable and massive chatmail and e-mail system
</h3> </h3>
<p><a href="https://autocrypt.org">Autocrypt</a> is used for automatically <p>Delta Chat uses a <a href="#openpgp-secure">secure subset of the OpenPGP standard</a>
establishing end-to-end encryption with contacts and group chats. to provide automatic end-to-end encryption using these protocols:</p>
Autocrypt uses a limited and <a href="#openpgp-secure">secure subset of the OpenPGP standard</a>.
End-to-End encrypted messages are marked with a padlock
<img style="vertical-align:middle; width:1.2em; margin:1px" src="../lock-icon.png" alt="padlock" />.</p>
<p><a href="https://securejoin.delta.chat/en/latest/new.html">Secure-Join protocols</a> <ul>
are used for establishing chats with guaranteed end-to-end encryption <li>
which protects against network attacks and compromised servers. <p><a href="https://securejoin.delta.chat/en/latest/new.html">Secure-Join</a>
Chats marked with a green checkmark to exchange encryption setup information through QR-code scanning or “invite links”.</p>
<img style="vertical-align:middle; width:1.5em; margin:1px" src="../green-checkmark.png" alt="green checkmark" /> </li>
guarantee end-to-end encrypted messages.</p> <li>
<p><a href="https://autocrypt.org">Autocrypt</a> is used for automatically
establishing end-to-end encryption between contacts and all members of a group chat.</p>
</li>
<li>
<p><a href="https://github.com/chatmail/core/blob/main/spec.md#attaching-a-contact-to-a-message">Sharing a contact to a
chat</a>
enables receivers to use end-to-end encryption with the contact.</p>
</li>
</ul>
<p>Delta Chat does not query, publish or interact with any OpenPGP key servers.</p>
<h3 id="whene2e"> <h3 id="whene2e">
@ -757,28 +762,37 @@ guarantee end-to-end encrypted messages.</p>
</h3> </h3>
<p>All end-to-end encrypted messages carry a padlock:</p> <p>All messages in Delta Chat are <strong>end-to-end encrypted by default</strong>.
Since the Delta Chat Version 2 release series (July 2025)
there are no lock or similar markers on end-to-end encrypted messages, anymore.</p>
<p><img style="width:160px; margin:1px" src="../lock-screenshot.png" alt="padlock in bubble" /></p> <h3 id="can-i-still-receive-or-send-mails-without-end-to-end-encryption">
<p>End-to-end encryption is guaranteed if there is a green checkmark next to the chat title:</p>
<p><img style="width:211px; margin:1px" src="../green-checkmark-screenshot.png" alt="green checkmark in title" /></p>
<h3 id="howtoe2ee">
How can I get guaranteed end-to-end encryption and green checkmarks? <a href="#howtoe2ee" class="anchor"></a> Can i still receive or send mails without end-to-end encryption? <a href="#can-i-still-receive-or-send-mails-without-end-to-end-encryption" class="anchor"></a>
</h3> </h3>
<p>If you have a second communication channel with your chat partner, <p>If you use default <a href="https://chatmail.at/relays">chatmail relays</a>,
like a video chat or a different messenger, it is impossible to receive or send messages without end-to-end encryption.</p>
you can generate an invite link.</p>
<p>If you are together in person, <p>If you instead create a profile using a classic e-mail server,
you can show a QR code to your chat partner.</p> you can send and receive messages without end-to-end encryption.
Such messages lacking end-to-end encryption are marked with an e-mail icon
<img style="vertical-align:middle; width:1.2em; margin:1px" src="../email-icon.png" alt="email" />.</p>
<h3 id="howtoe2ee">
How can I establish a chat with a new contact? <a href="#howtoe2ee" class="anchor"></a>
</h3>
<p>You can send an invite link through another private chat,
show an invitation QR code when next to each other or in a video call,
or click on a “contact” that was shared in a chat.</p>
<ul> <ul>
<li> <li>
@ -793,135 +807,54 @@ on the Delta Chat app main screen.</p>
</li> </li>
</ul> </ul>
<p>Let your chat partner scan the QR image <p>Ask your chat partner to scan the QR image
with their Delta Chat app, with their Delta Chat app,
or click “Copy” or “Share” to create an invite link or click “Copy” or “Share” to create an invite link
and share it with your chat partner.</p> and share it with your chat partner.</p>
<p>Now wait while <a href="https://securejoin.delta.chat/en/latest/new.html#setup-contact-protocol">Secure-Join network messages are exchanged</a> between both devices.</p> <p>Now wait while <a href="https://securejoin.delta.chat/en/latest/new.html#setup-contact-protocol">end-to-end encryption is getting established</a>.</p>
<ul> <ul>
<li> <li>
<p>If both devices are online, <p>If both sides are online, they will soon see a (group or direct) chat
both sides will eventually see a (group or direct) chat with a green checkmark and can start messaging securely.</p>
<img style="vertical-align:middle; width:1.5em; margin:1px" src="../green-checkmark.png" alt="green checkmark" />
next to the title.</p>
</li> </li>
<li> <li>
<p>If one of the devices is offline, the green checkmarks will only <p>If one side is offline or in bad network,
appear later when the device is internet-connected again the ability to chat is delayed until connectivity is restored.</p>
and the Secure-Join network protocol completed.</p>
</li> </li>
</ul> </ul>
<p>Congratulations! <p>Congratulations!
You now will automatically use guaranteed end-to-end encryption You now will automatically use end-to-end encryption
with this contact and both of you can add each other to green-checkmarked groups with this contact.
<img style="vertical-align:middle; width:1.5em; margin:1px" src="../green-checkmark.png" alt="green checkmark" />, If you add each other to chat groups,
thereby automatically spreading guaranteed end-to-end encryption among its members.</p> end-to-end encryption will be established among all members.</p>
<h3 id="e2eeguarantee"> <h3 id="e2eeguarantee">
What does the green checkmark and “guaranteed end-to-end encryption” mean? <a href="#e2eeguarantee" class="anchor"></a> What does the green checkmark in a contact profile mean? <a href="#e2eeguarantee" class="anchor"></a>
</h3> </h3>
<p>Chat titles with green checkmarks <p>A contact profile might show a green checkmark
<img style="vertical-align:middle; width:1.5em; margin:1px" src="../green-checkmark.png" alt="green checkmark" /> <img style="vertical-align:middle; width:1.5em; margin:1px" src="../green-checkmark.png" alt="green checkmark" />
mean that all messages in the chat will be end-to-end encrypted and an “Introduced by” line.
and can not be read or altered by compromised e-mail servers or Internet providers.
Joining green-checkmarked group chats
safely spreads everybody’s encryption information (and green checkmarks)
in a manner that guarantees end-to-end encryption in the group and among members.</p>
<p>Contact profiles with green checkmarks
<img style="vertical-align:middle; width:1.5em; margin:1px" src="../green-checkmark.png" alt="green checkmark" />
mean that messaging a contact is currently guaranteed to be end-to-end encrypted.
Every green-checkmarked contact either did a direct <a href="#howtoe2ee">QR-scan</a> with you Every green-checkmarked contact either did a direct <a href="#howtoe2ee">QR-scan</a> with you
or was introduced by a another green-checkmarked contact. or was introduced by a another green-checkmarked contact.
Introductions happen automatically when adding members to groups. Introductions happen automatically when adding members to groups.
Whoever adds a contact to a green-checkmarked group becomes an introducer Whoever adds a green-checkmarked contact to a group with only green-checkmarked members
to those members who didn’t yet know about the added contact. becomes an introducer.
In a contact profile you can tap on the “Introduced by …” text repeatedly In a contact profile you can tap on the “Introduced by …” text repeatedly
until you get to the one with whom you directly did a <a href="#howtoe2ee">QR-scan</a>.</p> until you get to the one with whom you directly did a <a href="#howtoe2ee">QR-scan</a>.</p>
<p>Note that in a contact profile you may see and tap introducers
but there is no green checkmark in the profile title.
This usually means that the contact <a href="#nocryptanymore">“sent a message from another device”</a>.</p>
<p>For more in-depth discussion of “guaranteed end-to-end encryption” <p>For more in-depth discussion of “guaranteed end-to-end encryption”
please see <a href="https://securejoin.delta.chat/en/latest/new.html">Secure-Join protocols</a> please see <a href="https://securejoin.delta.chat/en/latest/new.html">Secure-Join protocols</a>
and specifically read about “Verified Groups”, the technical term and specifically read about “Verified Groups”, the technical term
of what is called here “green-checkmarked” or “guaranteed end-to-end encrypted” chats.</p> of what is called here “green-checkmarked” or “guaranteed end-to-end encrypted” chats.</p>
<h3 id="nocryptanymore">
A contact “sent a message from another device”, what can i do? <a href="#nocryptanymore" class="anchor"></a>
</h3>
<p>Your chat with a contact lost guaranteed end-to-end encryption.
The green checkmark was removed for this chat and contact when you see this warning.
<strong>If you find the sudden drop of guaranteed end-to-end encryption
surprising for this contact then don’t accept the warning!</strong>
Instead check with your contact through a second channel
like a video call, other messenger or a phone call,
to find out what happened.</p>
<p>If your contact actually caused the drop of guaranteed end-to-end encryption
please see the next paragraphs for common reasons and their mitigations.
Regardless, all other green-checkmarked chats remain guaranteed end-to-end encrypted
even if the contact is a member there.</p>
<p><strong>Your contact is using Delta Chat on a second device (phone or laptop)</strong></p>
<p>If they have another device with a Delta Chat app running,
they should remove the profile from the new device
and add it <a href="#multiclient">as a second device as described here</a>.
As soon as they message you afterwards, the warning will be gone
and guaranteed encryption is established with both devices of your contact.</p>
<p><strong>Your contact reinstalled Delta Chat using their old account login</strong></p>
<p>If they have <a href="#backup">a backup file</a>,
they should remove the profile from the new device
and rather import the backup file to re-create their profile.
As soon as they message you afterwards, the warning will be gone
and guaranteed encryption is re-established for this contact.</p>
<p>If they don’t have a backup file, it’s best to perform a <a href="#howtoe2ee">QR scan</a>
with your chat partner to re-establish guaranteed end-to-end encryption.</p>
<p><strong>Your contact sent a mail through a webmail interface or another e-mail app
and will get back to using Delta Chat soon again.</strong></p>
<p>If you are sure that the contact sometimes uses webmail,
or another mail app lacking end-to-end encryption,
then you may accept the warning.
As soon as your contact uses Delta Chat again,
guaranteed end-to-end encryption will be automatically re-established.</p>
<p><strong>Your contact stopped using Delta Chat entirely</strong></p>
<p>Sometimes remaining in contact is more important than end-to-end encryption.
<a href="#tls">“Transport Layer Encryption” (TLS)</a> may still meaningfully protect
the confidentiality of your messages between your device and the e-mail server.
But without end-to-end encryption you and your contact are trusting your e-mail server
to not read or manipulate your messages, and to not hand them to third parties.</p>
<p>In any case, you can not do much else than accept the warning.
Please also remove the contact from any active green-checkmarked group
which you can find in “Chats in Common” in the Contact profile.
This spares your contact from getting “unreadable” messages.</p>
<p>If the contact removed Delta Chat because of buggy or undesirable behaviour,
please consider posting to our <a href="https://support.delta.chat">support forum</a>
to help us identify and address common problems. Thanks!</p>
<h3 id="are-attachments-pictures-files-audio-etc-end-to-end-encrypted"> <h3 id="are-attachments-pictures-files-audio-etc-end-to-end-encrypted">
@ -946,8 +879,7 @@ and attachment metadata such as filenames.</p>
</h3> </h3>
<p>Yes, Delta Chat uses a secure subset of OpenPGP <p>Yes, Delta Chat uses a secure subset of OpenPGP
and only displays a padlock security indicator on a message requiring the whole message to be properly encrypted and signed.
if the whole message is properly encrypted and signed.
For example, “Detached signatures” are not treated as secure.</p> For example, “Detached signatures” are not treated as secure.</p>
<p>OpenPGP is not insecure by itself. <p>OpenPGP is not insecure by itself.
@ -968,7 +900,7 @@ which was thankfully adopted in summer 2023.</p>
<h3 id="openpgp-alternatives"> <h3 id="openpgp-alternatives">
Did you consider using alternatives to OpenPGP for end-to-end -encryption? <a href="#openpgp-alternatives" class="anchor"></a> Did you consider using alternatives to OpenPGP for end-to-end-encryption? <a href="#openpgp-alternatives" class="anchor"></a>
</h3> </h3>
@ -1011,17 +943,15 @@ as defined by the Autocrypt Level 1 specification.</p>
<h3 id="tls"> <h3 id="tls">
Is a message exposed in cleartext if end-to-end encryption is not available? <a href="#tls" class="anchor"></a> Are messages marked with the mail icon exposed on the Internet? <a href="#tls" class="anchor"></a>
</h3> </h3>
<p>Even if your messages are not guaranteed to be end-to-end encrypted, <p>If you are sending or receiving e-mail messages without end-to-end encryption (using a classic e-mail server),
they are still protected from Internet providers like cell or cable companies. they are still protected from cell or cable companies who can not read or modify your e-mail messages.
However, your and your recipient’s e-mail providers But both your and your recipient’s e-mail providers
may read, analyze or even modify your messages, may read, analyze or modify your messages, including any attachments.</p>
including any attachments,
if they are not end-to-end encrypted.</p>
<p>Delta Chat by default uses strict <p>Delta Chat by default uses strict
<a href="https://en.wikipedia.org/wiki/Transport_Layer_Security">TLS encryption</a> <a href="https://en.wikipedia.org/wiki/Transport_Layer_Security">TLS encryption</a>
@ -1034,10 +964,6 @@ then transport encryption will be enforced between e-mail providers
in which case Delta Chat communications will never be exposed in cleartext to the Internet in which case Delta Chat communications will never be exposed in cleartext to the Internet
even if the message was not end-to-end encrypted.</p> even if the message was not end-to-end encrypted.</p>
<p>Note that <a href="#howtoe2ee">maintaining guaranteed end-to-end encryption</a> on top of TLS encryption
provides pervasive safety between your and the recipient’s devices.
Not even your e-mail or Internet provider will be able to read or modify your messages.</p>
<h3 id="message-metadata"> <h3 id="message-metadata">
@ -1046,25 +972,25 @@ Not even your e-mail or Internet provider will be able to read or modify your me
</h3> </h3>
<p>Delta Chat protects most message metadata by putting the following information <p>Unlike most other messengers,
into the end-to-end encrypted part of messages:</p> Delta Chat apps do not store any metadata about contacts or groups on servers, also not in encrypted form.
Instead, all group metadata is end-to-end encrypted and stored on end-user devices, only.</p>
<p>E-mail Servers can therefore only see</p>
<ul> <ul>
<li>Subject line</li> <li>
<li>Group avatar and name</li> <p>the message date,</p>
<li>MDN (read receipt) requests (<code class="language-plaintext highlighter-rouge">Chat-Disposition-Notification-To</code>)</li> </li>
<li>Disappearing message timer (<code class="language-plaintext highlighter-rouge">Ephemeral-Timer</code>)</li> <li>
<li><code class="language-plaintext highlighter-rouge">Chat-Group-Member-Removed</code>, <code class="language-plaintext highlighter-rouge">Chat-Group-Member-Added</code></li> <p>sender and receiver addresses</p>
<li><code class="language-plaintext highlighter-rouge">Secure-Join</code> header containing secure join commands</li> </li>
<li>Notification about enabling location streaming</li> <li>
<li>WebRTC room URL</li> <p>and message size.</p>
</li>
</ul> </ul>
<p>E-Mail servers do not get access to this protected metadata <p>All other message, contact and group metadata resides in the end-to-end encrypted part of messages.</p>
but they do see the message date as well as the message size,
and, more importantly, the sender and receiver addresses.
E-mail servers need receiver addresses to route and
deliver messages to recipient’s devices.</p>
<h3 id="device-seizure"> <h3 id="device-seizure">
@ -1076,96 +1002,34 @@ deliver messages to recipient’s devices.</p>
<p>Both for protecting against metadata-collecting e-mail servers <p>Both for protecting against metadata-collecting e-mail servers
as well as against the threat of device seizure as well as against the threat of device seizure
we recommend to use a <a href="https://delta.chat/chatmail">chatmail server</a> we recommend to use a <a href="https://chatmail.at/relays">chatmail relay</a>
to create pseudonymous temporary profiles through QR-code scans. to create chat profiles using random e-mail addresses for transport.
Note that Delta Chat apps on all platforms support multiple profiles Note that Delta Chat apps on all platforms support multiple profiles
so you can easily use situation-specific profiles next to your “main” profile so you can easily use situation-specific profiles next to your “main” profile
with the knowledge that all their data, along with all metadata, will be deleted. with the knowledge that all their data, along with all metadata, will be deleted.
Moreover, if a device is seized then contacts using temporary profiles Moreover, if a device is seized then chat contacts using short-lived profiles
can not be identified easily, as compared to messengers which reveal can not be identified easily.</p>
phone numbers in chat groups which in turn are often associated with legal identities.</p>
<h3 id="how-can-i-check-encryption-information"> <h3 id="sealedsender">
How can i check encryption information? <a href="#how-can-i-check-encryption-information" class="anchor"></a> Does Delta Chat support “Sealed Sender”? <a href="#sealedsender" class="anchor"></a>
</h3> </h3>
<p>You may check the end-to-end encryption status manually in the “Encryption” dialog <p>No, not yet.</p>
(user profile on Android/iOS or right-click a user’s chat-list item on desktop).
Delta Chat shows two fingerprints there.
If the same fingerprints appear on your own and your contact’s device,
the connection is safe.</p>
<h3 id="how-can-i-check-the-encryption-status-of-messages"> <p>The Signal messenger introduced <a href="https://signal.org/blog/sealed-sender/">“Sealed Sender” in 2018</a>
to keep their server infrastructure ignorant of who is sending a message to a set of recipients.
It is particularly important because the Signal server knows the mobile number of each account,
which is usually associated with a passport identity.</p>
<p>Even if <a href="https://chatmail.at/relays">chatmail relays</a>
How can I check the encryption status of messages? <a href="#how-can-i-check-the-encryption-status-of-messages" class="anchor"></a> do not ask for any private data (including no phone numbers),
it might still be worthwhile to protect relational metadata between addresses.
We don’t foresee bigger problems in using random throw-away e-mail addresses for sealed sending
</h3> but an implementation has not been agreed as a priority yet.</p>
<p>A little <strong>padlock</strong> in a message bubble denotes
that the message was properly end-to-end encrypted from the given sender.
If there is <strong>no padlock</strong>, the message was not properly end-to-end encrypted
most likely because the sender uses an app or webmail interface
without support for end-to-end–encryption.</p>
<h3 id="why-do-i-see-unencrypted-messages">
Why do I see unencrypted messages? <a href="#why-do-i-see-unencrypted-messages" class="anchor"></a>
</h3>
<p>If a contact uses a non-Autocrypt e-mail app,
all messages involving this contact (in a group or 1:1 chat)
will not be end-to-end encrypted, and thus not show a “padlock” with messages.
Note that even if your contacts use Delta Chat on their account,
they might also use a non-Autocrypt e-mail app on that account
which then may cause intermittently unencrypted messages.
Replying unencrypted to unencrypted messages is mandated by Autocrypt
to prevent unreadable messages on the side of your contacts
and their non-Autocrypt e-mail app.</p>
<h3 id="how-can-i-get-an-end-to-end-encrypted-chat-with-a-delta-chat-contact-who-sometimes-uses-webmail-or-another-non-autocrypt-e-mail-app">
How can i get an end-to-end encrypted chat with a Delta Chat contact who sometimes uses webmail or another non-Autocrypt e-mail app? <a href="#how-can-i-get-an-end-to-end-encrypted-chat-with-a-delta-chat-contact-who-sometimes-uses-webmail-or-another-non-autocrypt-e-mail-app" class="anchor"></a>
</h3>
<p>If you need a safely end-to-end encrypted chat with a contact
who is using their e-mail account both with Delta Chat and non-Autocrypt apps (e.g. webmail),
it’s best to setup <a href="#howtoe2ee">guaranteed end-to-end encryption with them</a>
and then create a guaranteed end-to-end encrypted group chat with you two as members.
In this group chat all messages will be end-to-end encrypted
even if the direct chat between you two has a
<a href="#nocryptanymore">“… sent a message from another device”</a> warning.</p>
<h3 id="how-can-i-ensure-message-end-to-end-encryption-and-deletion">
How can I ensure message end-to-end encryption and deletion? <a href="#how-can-i-ensure-message-end-to-end-encryption-and-deletion" class="anchor"></a>
</h3>
<p>The best way to ensure every message is end-to-end encrypted,
and metadata deleted as quickly as possible
is <a href="#howtoe2ee">using chats with guaranteed end-to-end encryption</a>
and turning on <a href="#ephemeralmsgs">disappearing messages</a>.</p>
<p>Guaranteed end-to-end encrypted chats protect against <a href="https://en.wikipedia.org/wiki/Man-in-the-middle_attack">MITM attacks</a>
and turning on disappearing messages deletes the messages
on the server after a user-configured time.</p>
<p>If you don’t need a longer-lived copy of your messages on the server,
you can also turn on <a href="#delold">“delete messages from server automatically”</a>.</p>
<h3 id="pfs"> <h3 id="pfs">
@ -1175,45 +1039,52 @@ you can also turn on <a href="#delold">“delete messages from server automatica
</h3> </h3>
<p>No, Delta Chat doesn’t support Perfect Forward Secrecy (PFS). <p>No, not yet.</p>
This means that if your Delta Chat private decryption key is leaked,
<p>Delta Chat today doesn’t support Perfect Forward Secrecy (PFS).
This means that if your private decryption key is leaked,
and someone has collected your prior in-transit messages, and someone has collected your prior in-transit messages,
they will be able to decrypt and read them using the leaked decryption key.</p> they will be able to decrypt and read them using the leaked decryption key.
Note that Forward Secrecy only increases security if you delete messages.
Otherwise, someone obtaining your decryption keys
is typically also able to get all your non-deleted messages
and doesn’t even need to decrypt any previously collected messages.</p>
<p>Note, however, that if anyone obtains to your decryption keys, <p>We designed a Forward Secrecy approach that withstood
they will typically also be able to obtain your messages, initial examination from some cryptographers and implementation experts
irrespective if Perfect Forward Secrecy is in place or not. but is pending a more formal write up
The typical real-world situation for leaked decryption keys is device seizure to ascertain it reliably works in federated messaging and with multi-device usage,
which we discuss in our answer <a href="#device-seizure">on metadata and device seizure</a>.</p> before it could be implemented in <a href="https://github.com/chatmail/core">chatmail core</a>,
which would make it available in all <a href="https://chatmail.at/clients">chatmail clients</a>.</p>
<p>It is possible that Delta Chat evolves to support Perfect Forward Secrecy, <h3 id="pqc">
because OpenPGP is just a container for encrypted messages
but encryption key management (and thus key rotation or key “ratcheting”)
could be organized in flexible ways.
See <a href="https://gitlab.com/sequoia-pgp/openpgp-dr">Seqouia’s PFS prototype</a>
for existing experiments in the OpenPGP implementor community.</p>
<h3 id="is-end-to-end-encryption-of-delta-chat-as-safe-as-signal">
Is end-to-end encryption of Delta Chat as safe as Signal? <a href="#is-end-to-end-encryption-of-delta-chat-as-safe-as-signal" class="anchor"></a> Does Delta Chat support Post-Quantum-Cryptography? <a href="#pqc" class="anchor"></a>
</h3> </h3>
<p>It depends on what is important to you. <p>No, not yet.</p>
Delta Chat <a href="#pfs">does not support PFS</a> like Signal does
but it provides <a href="#e2eeguarantee">guaranteed end-to-end encrypted chats</a>
that are safe against compromised servers or corrupted networks.
Signal and most other PFS-supporting messengers do not provide
a practical scheme for protecting chat groups from network attacks
which are arguably more worrisome
than a potential attacker who seizes your phone and private encryption setup
but somehow not your messages, yet has a full record of all
past encrypted messages.</p>
<p>In any case, Delta Chat’s end-to-end encryption uses a <a href="#openpgp-secure">secure subset of OpenPGP</a> <p>Delta Chat uses the Rust OpenPGP library <a href="https://github.com/rpgp/rpgp">rPGP</a>
which has been <a href="https://delta.chat/assets/blog/2019-first-security-review.pdf">independently security-audited</a>.</p> which supports the latest <a href="https://datatracker.ietf.org/doc/draft-ietf-openpgp-pqc/">IETF Post-Quantum-Cryptography OpenPGP draft</a>.
We aim to add PQC support in <a href="https://github.com/chatmail/core">chatmail core</a> after the draft is finalized at the IETF
in collaboration with other OpenPGP implementers.</p>
<h3 id="how-can-i-manually-check-encryption-information">
How can I manually check encryption information? <a href="#how-can-i-manually-check-encryption-information" class="anchor"></a>
</h3>
<p>You may check the end-to-end encryption status manually in the “Encryption” dialog
(user profile on Android/iOS or right-click a user’s chat-list item on desktop).
Delta Chat shows two fingerprints there.
If the same fingerprints appear on your own and your contact’s device,
the connection is safe.</p>
<h3 id="importkey"> <h3 id="importkey">
@ -1248,7 +1119,7 @@ from most recent to older:</p>
<li> <li>
<p>2024 December, an <a href="https://github.com/rpgp/docs/blob/main/audits/NGI%20Core%20rPGP%20penetration%20test%20report%202024%201.0.pdf">NLNET-commissioned Evaluation of <p>2024 December, an <a href="https://github.com/rpgp/docs/blob/main/audits/NGI%20Core%20rPGP%20penetration%20test%20report%202024%201.0.pdf">NLNET-commissioned Evaluation of
rPGP</a> by <a href="https://www.radicallyopensecurity.com/">Radically Open Security</a> took place. rPGP</a> by <a href="https://www.radicallyopensecurity.com/">Radically Open Security</a> took place.
rPGP serves as the end-to-end encyption <a href="https://openpgp.org">OpenPGP</a> engine of Delta Chat. rPGP serves as the end-to-end encryption <a href="https://openpgp.org">OpenPGP</a> engine of Delta Chat.
Two advisories were released related to the findings of this audit:</p> Two advisories were released related to the findings of this audit:</p>
<ul> <ul>
@ -1642,6 +1513,11 @@ seria feito pelo aplicativo Delta Chat.</p>
</h3> </h3>
<p>Note:
Changing email addresses is temporarily disabled
because of ongoing changes to the DeltaChat core.
It should be available again in a few months.</p>
<ol> <ol>
<li> <li>
<p>Change your address in “Settings → Advanced → Password and Account” and <p>Change your address in “Settings → Advanced → Password and Account” and

458
src/main/assets/help/ru/help.html
View file

@ -36,27 +36,24 @@
<li><a href="#почему-delta-chat-интегрируется-с-централизованными-проприетарными-push-сервисами-applegoogle">Почему Delta Chat интегрируется с централизованными проприетарными Push-сервисами Apple/Google?</a></li> <li><a href="#почему-delta-chat-интегрируется-с-централизованными-проприетарными-push-сервисами-applegoogle">Почему Delta Chat интегрируется с централизованными проприетарными Push-сервисами Apple/Google?</a></li>
</ul> </ul>
</li> </li>
<li><a href="#шифрование-и-безопасность">Шифрование и безопасность</a> <li><a href="#e2ee">Шифрование и безопасность</a>
<ul> <ul>
<li><a href="#какие-стандарты-используются-для-сквозного-шифрования">Какие стандарты используются для сквозного шифрования?</a></li> <li><a href="#какие-стандарты-используются-для-сквозного-шифрования">Какие стандарты используются для сквозного шифрования?</a></li>
<li><a href="#whene2e">Как узнать зашифрованы ли сообщения сквозным шифрованием?</a></li> <li><a href="#whene2e">Как узнать зашифрованы ли сообщения сквозным шифрованием?</a></li>
<li><a href="#howtoe2ee">Как получить гарантированное сквозное шифрование и зелёные галочки?</a></li> <li><a href="#могу-ли-я-получать-или-отправлять-письма-без-сквозного-шифрования">Могу ли я получать или отправлять письма без сквозного шифрования?</a></li>
<li><a href="#e2eeguarantee">Что означает зелёная галочка и “гарантированное сквозное шифрование”?</a></li> <li><a href="#howtoe2ee">Как мне установить чат с новым контактом?</a></li>
<li><a href="#nocryptanymore">Контакт “отправил сообщение с другого устройства”, что делать?</a></li> <li><a href="#e2eeguarantee">Что означает зеленая галочка в профиле контакта?</a></li>
<li><a href="#зашифрованы-ли-вложения-изображения-файлы-аудио-и-т-д-сквозным-шифрованием">Зашифрованы ли вложения (изображения, файлы, аудио и т. д.) сквозным шифрованием?</a></li> <li><a href="#зашифрованы-ли-вложения-изображения-файлы-аудио-и-т-д-сквозным-шифрованием">Зашифрованы ли вложения (изображения, файлы, аудио и т. д.) сквозным шифрованием?</a></li>
<li><a href="#openpgp-secure">OpenPGP безопасен?</a></li> <li><a href="#openpgp-secure">OpenPGP безопасен?</a></li>
<li><a href="#openpgp-alternatives">Рассматривали ли вы альтернативы OpenPGP для сквозного шифрования?</a></li> <li><a href="#openpgp-alternatives">Did you consider using alternatives to OpenPGP for end-to-end-encryption?</a></li>
<li><a href="#подвержен-ли-delta-chat-уязвимости-efail">Подвержен ли Delta Chat уязвимости EFAIL?</a></li> <li><a href="#подвержен-ли-delta-chat-уязвимости-efail">Подвержен ли Delta Chat уязвимости EFAIL?</a></li>
<li><a href="#tls">Будет ли сообщение передано в открытом виде, если сквозное шифрование недоступно?</a></li> <li><a href="#tls">Видны ли в Интернете сообщения, отмеченные значком почты?</a></li>
<li><a href="#message-metadata">Как Delta Chat защищает метаданные в сообщениях?</a></li> <li><a href="#message-metadata">Как Delta Chat защищает метаданные в сообщениях?</a></li>
<li><a href="#device-seizure">Как защитить метаданные и контакты при изъятии устройства?</a></li> <li><a href="#device-seizure">Как защитить метаданные и контакты при изъятии устройства?</a></li>
<li><a href="#как-я-могу-проверить-информацию-о-шифровании">Как я могу проверить информацию о шифровании?</a></li> <li><a href="#sealedsender">Does Delta Chat support “Sealed Sender”?</a></li>
<li><a href="#как-я-могу-проверить-статус-шифрования-сообщений">Как я могу проверить статус шифрования сообщений?</a></li>
<li><a href="#почему-я-вижу-незашифрованные-сообщения">Почему я вижу незашифрованные сообщения?</a></li>
<li><a href="#как-я-могу-получить-зашифрованный-сквозным-шифрованием-чат-с-контактом-delta-chat-который-иногда-использует-веб-почту-или-другое-приложение-электронной-почты-не-поддерживающее-autocrypt">Как я могу получить зашифрованный сквозным шифрованием чат с контактом Delta Chat, который иногда использует веб-почту или другое приложение электронной почты, не поддерживающее Autocrypt?</a></li>
<li><a href="#как-я-могу-обеспечить-сквозное-шифрование-и-удаление-сообщений">Как я могу обеспечить сквозное шифрование и удаление сообщений?</a></li>
<li><a href="#pfs">Поддерживает ли Delta Chat совершенную прямую секретность (Perfect forward secrecy, PFS)?</a></li> <li><a href="#pfs">Поддерживает ли Delta Chat совершенную прямую секретность (Perfect forward secrecy, PFS)?</a></li>
<li><a href="#является-ли-сквозное-шифрование-delta-chat-таким-же-безопасным-как-signal">Является ли сквозное шифрование Delta Chat таким же безопасным как Signal?</a></li> <li><a href="#pqc">Does Delta Chat support Post-Quantum-Cryptography?</a></li>
<li><a href="#how-can-i-manually-check-encryption-information">How can I manually check encryption information?</a></li>
<li><a href="#importkey">Можно ли повторно использовать существующий секретный ключ?</a></li> <li><a href="#importkey">Можно ли повторно использовать существующий секретный ключ?</a></li>
<li><a href="#security-audits">Проходил ли Delta Chat независимую проверку на наличие уязвимостей безопасности?</a></li> <li><a href="#security-audits">Проходил ли Delta Chat независимую проверку на наличие уязвимостей безопасности?</a></li>
</ul> </ul>
@ -719,10 +716,10 @@ Push-уведомления недоступны.</p>
включая потенциальный сервер, который <a href="https://delta.chat/chatmail#selfhosted">вы можете настроить самостоятельно без нашего разрешения.</a>. включая потенциальный сервер, который <a href="https://delta.chat/chatmail#selfhosted">вы можете настроить самостоятельно без нашего разрешения.</a>.
Добро пожаловать в мир мощной и совместимой системы chatmail и электронной почты :)</p> Добро пожаловать в мир мощной и совместимой системы chatmail и электронной почты :)</p>
<h2 id="шифрование-и-безопасность"> <h2 id="e2ee">
Шифрование и безопасность <a href="#шифрование-и-безопасность" class="anchor"></a> Шифрование и безопасность <a href="#e2ee" class="anchor"></a>
</h2> </h2>
@ -735,18 +732,26 @@ Push-уведомления недоступны.</p>
</h3> </h3>
<p><a href="https://autocrypt.org">Autocrypt</a> используется для автоматической <p>Delta Chat uses a <a href="#openpgp-secure">secure subset of the OpenPGP standard</a>
установки сквозного шифрования при работе с контактами и групповыми чатами. to provide automatic end-to-end encryption using these protocols:</p>
Autocrypt использует ограниченное и <a href="#openpgp-secure">безопасное подмножество стандарта OpenPGP</a>.
Сообщения, зашифрованные сквозным шифрованием, помечаются замком
<img style="vertical-align:middle; width:1.2em; margin:1px" src="../lock-icon.png" alt="padlock" />.</p>
<p><a href="https://securejoin.delta.chat/en/latest/new.html">Протоколы Secure-Join</a> <ul>
используются для создания чатов с гарантированным сквозным шифрованием, <li>
которое защищает от сетевых атак и скомпрометированных серверов. <p><a href="https://securejoin.delta.chat/en/latest/new.html">Secure-Join</a>
Чаты, отмеченные зелёной галочкой to exchange encryption setup information through QR-code scanning or “invite links”.</p>
<img style="vertical-align:middle; width:1.5em; margin:1px" src="../green-checkmark.png" alt="green checkmark" /> </li>
гарантируют сквозное шифрование сообщений.</p> <li>
<p><a href="https://autocrypt.org">Autocrypt</a> is used for automatically
establishing end-to-end encryption between contacts and all members of a group chat.</p>
</li>
<li>
<p><a href="https://github.com/chatmail/core/blob/main/spec.md#attaching-a-contact-to-a-message">Sharing a contact to a
chat</a>
enables receivers to use end-to-end encryption with the contact.</p>
</li>
</ul>
<p>Delta Chat не запрашивает, не публикует и не взаимодействует с какими-либо серверами ключей OpenPGP.</p>
<h3 id="whene2e"> <h3 id="whene2e">
@ -756,28 +761,37 @@ Autocrypt использует ограниченное и <a href="#openpgp-sec
</h3> </h3>
<p>Все сообщения, зашифрованные сквозным шифрованием, имеют значок замка:</p> <p>All messages in Delta Chat are <strong>end-to-end encrypted by default</strong>.
Since the Delta Chat Version 2 release series (July 2025)
there are no lock or similar markers on end-to-end encrypted messages, anymore.</p>
<p><img style="width:160px; margin:1px" src="../lock-screenshot.png" alt="Значок замка в пузырьке" /></p> <h3 id="могу-ли-я-получать-или-отправлять-письма-без-сквозного-шифрования">
<p>Сквозное шифрование гарантировано, если рядом с заголовком чата стоит зелёная галочка:</p>
<p><img style="width:211px; margin:1px" src="../green-checkmark-screenshot.png" alt="Зелёная галочка в заголовке" /></p>
<h3 id="howtoe2ee">
Как получить гарантированное сквозное шифрование и зелёные галочки? <a href="#howtoe2ee" class="anchor"></a> Могу ли я получать или отправлять письма без сквозного шифрования? <a href="#могу-ли-я-получать-или-отправлять-письма-без-сквозного-шифрования" class="anchor"></a>
</h3> </h3>
<p>Если у вас есть второй канал связи с вашим собеседником, <p>If you use default <a href="https://chatmail.at/relays">chatmail relays</a>,
например, видеочат или другой мессенджер, it is impossible to receive or send messages without end-to-end encryption.</p>
вы можете создать ссылку-приглашение.</p>
<p>Если вы встретились лично с собеседником, <p>If you instead create a profile using a classic e-mail server,
вы можете показать ему свой QR-код.</p> you can send and receive messages without end-to-end encryption.
Such messages lacking end-to-end encryption are marked with an e-mail icon
<img style="vertical-align:middle; width:1.2em; margin:1px" src="../email-icon.png" alt="email" />.</p>
<h3 id="howtoe2ee">
Как мне установить чат с новым контактом? <a href="#howtoe2ee" class="anchor"></a>
</h3>
<p>You can send an invite link through another private chat,
show an invitation QR code when next to each other or in a video call,
or click on a “contact” that was shared in a chat.</p>
<ul> <ul>
<li> <li>
@ -786,141 +800,60 @@ Autocrypt использует ограниченное и <a href="#openpgp-sec
и выберите “QR-код приглашения”.</p> и выберите “QR-код приглашения”.</p>
</li> </li>
<li> <li>
<p>Для <strong>приглашений в прямой чат 1:1</strong>, <p>For <strong>direct 1:1 chat invitations</strong>,
коснитесь значка QR-кода <img style="vertical-align:middle; width:1.8em; margin:1px" src="../qr-icon.png" /> tap the QR Code icon <img style="vertical-align:middle; width:1.8em; margin:1px" src="../qr-icon.png" />
на главном экране приложения Delta Chat.</p> on the Delta Chat app main screen.</p>
</li> </li>
</ul> </ul>
<p>Позвольте вашему собеседнику отсканировать QR-код <p>Ask your chat partner to scan the QR image
с помощью приложения Delta Chat, with their Delta Chat app,
или нажмите “Копировать” или “Поделиться”, чтобы создать ссылку-приглашение or click “Copy” or “Share” to create an invite link
и отправьте её вашему собеседнику.</p> and share it with your chat partner.</p>
<p>Теперь ожидайте, пока <a href="https://securejoin.delta.chat/en/latest/new.html#setup-contact-protocol">сообщения Secure-Join</a> будут переданы между обоими устройствами.</p> <p>Now wait while <a href="https://securejoin.delta.chat/en/latest/new.html#setup-contact-protocol">end-to-end encryption is getting established</a>.</p>
<ul> <ul>
<li> <li>
<p>Если оба устройства находятся в сети, <p>If both sides are online, they will soon see a (group or direct) chat
обе стороны в конечном итоге увидят (групповой или прямой) чат с зелёной галочкой and can start messaging securely.</p>
<img style="vertical-align:middle; width:1.5em; margin:1px" src="../green-checkmark.png" alt="зелёная галочка" />
рядом с названием.</p>
</li> </li>
<li> <li>
<p>Если одно из устройств не подключено к сети, зелёные галочки появятся только после того, <p>If one side is offline or in bad network,
как устройство снова подключится к Интернету the ability to chat is delayed until connectivity is restored.</p>
и сетевой протокол Secure-Join будет завершён.</p>
</li> </li>
</ul> </ul>
<p>Поздравляем! <p>Congratulations!
Теперь вы будете автоматически использовать гарантированное сквозное шифрование You now will automatically use end-to-end encryption
с этим контактом, и вы оба сможете добавлять друг друга в группы, отмеченные зелёной галочкой with this contact.
<img style="vertical-align:middle; width:1.5em; margin:1px" src="../green-checkmark.png" alt="зелёная галочка" />, If you add each other to chat groups,
тем самым автоматически распространяя гарантированное сквозное шифрование среди её участников.</p> end-to-end encryption will be established among all members.</p>
<h3 id="e2eeguarantee"> <h3 id="e2eeguarantee">
Что означает зелёная галочка и “гарантированное сквозное шифрование”? <a href="#e2eeguarantee" class="anchor"></a> Что означает зеленая галочка в профиле контакта? <a href="#e2eeguarantee" class="anchor"></a>
</h3> </h3>
<p>Чаты, помеченные зелёными галочками <p>A contact profile might show a green checkmark
<img style="vertical-align:middle; width:1.5em; margin:1px" src="../green-checkmark.png" alt="зелёная галочка" /> <img style="vertical-align:middle; width:1.5em; margin:1px" src="../green-checkmark.png" alt="green checkmark" />
означают, что все сообщения в чате будут зашифрованы сквозным шифрованием and an “Introduced by” line.
и не могут быть прочитаны или изменены скомпрометированными серверами электронной почты или интернет-провайдерами. Every green-checkmarked contact either did a direct <a href="#howtoe2ee">QR-scan</a> with you
Присоединение к групповым чатам с зелёной галочкой or was introduced by a another green-checkmarked contact.
безопасно распространяет информацию о шифровании всех участников (и зелёные галочки) Introductions happen automatically when adding members to groups.
таким образом, чтобы гарантировать сквозное шифрование в группе и между её участниками.</p> Whoever adds a green-checkmarked contact to a group with only green-checkmarked members
becomes an introducer.
<p>Профили контактов с зелёной галочкой In a contact profile you can tap on the “Introduced by …” text repeatedly
<img style="vertical-align:middle; width:1.5em; margin:1px" src="../green-checkmark.png" alt="зелёная галочка" /> until you get to the one with whom you directly did a <a href="#howtoe2ee">QR-scan</a>.</p>
означают, что отправка сообщений контакту в настоящее время гарантированно зашифрована сквозным шифрованием.
Каждый контакт с зелёной галочкой либо совершил с вами прямое <a href="#howtoe2ee">QR-сканирование</a>,
либо был представлен другим контактом с зелёной галочкой.
Знакомство происходит автоматически при добавлении участников в группы.
Тот, кто добавляет контакт в группу, отмеченную зелёной галочкой, становится представителем
для тех участников, которые еще не знают о добавленном контакте.
В профиле контакта можно несколько раз нажать на текст “Представлен …” несколько раз
пока не дойдёте до того, с кем вы непосредственно провели <a href="#howtoe2ee">QR-сканирование</a>.</p>
<p>Обратите внимание, что в профиле контакта вы можете увидеть и присоединённых знакомых,
но в заголовке профиля нет зелёной галочки.
Обычно это означает, что контакт <a href="#nocryptanymore">“отправил сообщение с другого устройства”</a>.</p>
<p>Для более подробного обсуждения “гарантированного сквозного шифрования” <p>Для более подробного обсуждения “гарантированного сквозного шифрования”
пожалуйста, обратитесь к <a href="https://securejoin.delta.chat/en/latest/new.html">протоколам Secure-Join</a> пожалуйста, обратитесь к <a href="https://securejoin.delta.chat/en/latest/new.html">протоколам Secure-Join</a>
и прочитайте о “Проверенных группах”, техническом термине, и прочитайте о “Проверенных группах”, техническом термине,
который здесь называется “группами с зелёной галочкой” или чатами с “гарантированным сквозным шифрованием”.</p> который здесь называется “группами с зелёной галочкой” или чатами с “гарантированным сквозным шифрованием”.</p>
<h3 id="nocryptanymore">
Контакт “отправил сообщение с другого устройства”, что делать? <a href="#nocryptanymore" class="anchor"></a>
</h3>
<p>Ваш чат с контактом утратил гарантированное сквозное шифрование.
Зелёная галочка была удалена для этого чата и контакта, и когда вы увидели предупреждение.
<strong>Если вы обнаружили внезапное прекращение гарантированного сквозного шифрования
для этого контакта, не принимайте предупреждение!</strong>
Вместо этого свяжитесь со своим контактом по второму каналу,
например, видеозвонок, другой мессенджер или телефонный звонок,
чтобы узнать, что произошло.</p>
<p>Если ваш контакт стал причиной потери гарантированного сквозного шифрования,
пожалуйста, ознакомьтесь с распространёнными причинами и способами их устранения в следующих параграфах.
Независимо от этого, все остальные чаты, отмеченные зелёной галочкой, остаются гарантированно зашифрованными сквозным шифрованием,
даже если этот контакт является его участником.</p>
<p><strong>Ваш контакт использует Delta Chat на втором устройстве (телефоне или ноутбуке)</strong></p>
<p>Если у него есть другое устройство с запущенным приложением Delta Chat,
ему следует удалить учётную запись с нового устройства
и добавить его <a href="#multiclient">как второе устройство, как описано здесь</a>.
После того, как он отправит вам сообщение, предупреждение исчезнет
и гарантированное шифрование будет установлено на обоих устройствах вашего собеседника.</p>
<p><strong>Ваш контакт переустановил Delta Chat, используя старые учетные данные для входа</strong></p>
<p>Если у него есть <a href="#backup">файл резервной копии</a>,
ему следует удалить профиль с нового устройства
и вместо этого импортировать резервную копию для восстановления своего профиля.
После того, как он отправит вам сообщение, предупреждение исчезнет,
и гарантированное шифрование будет восстановлено для этого контакта.</p>
<p>Если у него нет файла резервной копии, лучше всего выполнить <a href="#howtoe2ee">сканирование QR-кода</a>
с вашим собеседником, чтобы восстановить гарантированное сквозное шифрование.</p>
<p><strong>Ваш контакт отправил письмо через интерфейс веб-почты или другое приложение электронной почты
и снова вернулся к использованию Delta Chat.</strong></p>
<p>Если вы уверены, что ваш контакт иногда использует веб-почту
или другое приложение электронной почты, в котором отсутствует сквозное шифрование,
то вы можете принять предупреждение.
Как только контакт снова начнёт использовать Delta Chat,
гарантированное сквозное шифрование будет автоматически восстановлено.</p>
<p><strong>Ваш контакт полностью прекратил использование Delta Chat</strong></p>
<p>Иногда оставаться на связи важнее, чем сквозное шифрование.
<a href="#tls">“Протокол защиты транспортного уровня” (TLS)</a> всё ещё может существенно защитить
конфиденциальность ваших сообщений между вашим устройством и сервером электронной почты.
Но без сквозного шифрования вы и ваш контакт должны доверять серверу электронной почты,
который не должен читать и манипулировать вашими сообщениями, и не передавать их третьим лицам.</p>
<p>В любом случае, вы ничего не можете сделать, кроме как принять предупреждение.
Также удалите этот контакт из всех активных групп, отмеченных зелёной галочкой,
которые можно найти в разделе “Общие чаты” в профиле контакта.
Это избавит ваш контакт от получения “нечитаемых” сообщений.</p>
<p>Если контакт удалил Delta Chat из-за ошибок или нежелательного поведения,
пожалуйста, подумайте о том, чтобы поделиться этой информацией на нашем <a href="https://support.delta.chat">форуме поддержки</a>,
чтобы помочь нам выявить и устранить общие проблемы. Спасибо!</p>
<h3 id="зашифрованы-ли-вложения-изображения-файлы-аудио-и-т-д-сквозным-шифрованием"> <h3 id="зашифрованы-ли-вложения-изображения-файлы-аудио-и-т-д-сквозным-шифрованием">
@ -944,10 +877,9 @@ Autocrypt использует ограниченное и <a href="#openpgp-sec
</h3> </h3>
<p>Да, Delta Chat использует безопасное подмножество OpenPGP <p>Yes, Delta Chat uses a secure subset of OpenPGP
и отображает индикатор безопасности в виде замка только, requiring the whole message to be properly encrypted and signed.
если всё сообщение правильно зашифровано и подписано. For example, “Detached signatures” are not treated as secure.</p>
Например, “Отдельные подписи” не считаются безопасными.</p>
<p>OpenPGP сам по себе не является небезопасным. <p>OpenPGP сам по себе не является небезопасным.
Большинство обсуждаемых в публичной сфере проблем безопасности OpenPGP Большинство обсуждаемых в публичной сфере проблем безопасности OpenPGP
@ -967,7 +899,7 @@ Delta Chat вместо этого использует реализацию Ope
<h3 id="openpgp-alternatives"> <h3 id="openpgp-alternatives">
Рассматривали ли вы альтернативы OpenPGP для сквозного шифрования? <a href="#openpgp-alternatives" class="anchor"></a> Did you consider using alternatives to OpenPGP for end-to-end-encryption? <a href="#openpgp-alternatives" class="anchor"></a>
</h3> </h3>
@ -1010,17 +942,15 @@ Delta Chat вместо этого использует реализацию Ope
<h3 id="tls"> <h3 id="tls">
Будет ли сообщение передано в открытом виде, если сквозное шифрование недоступно? <a href="#tls" class="anchor"></a> Видны ли в Интернете сообщения, отмеченные значком почты? <a href="#tls" class="anchor"></a>
</h3> </h3>
<p>Даже если не гарантируется сквозное шифрование ваших сообщений, <p>If you are sending or receiving e-mail messages without end-to-end encryption (using a classic e-mail server),
они все равно защищены от интернет-провайдеров, сотовых операторов или кабельных компаний. they are still protected from cell or cable companies who can not read or modify your e-mail messages.
Однако провайдеры электронной почты, ваш и ваших получателей But both your and your recipient’s e-mail providers
могут читать, анализировать или даже изменять ваши сообщения, may read, analyze or modify your messages, including any attachments.</p>
включая любые вложения,
если они не зашифрованы сквозным шифрованием.</p>
<p>Delta Chat по умолчанию использует строгое <p>Delta Chat по умолчанию использует строгое
<a href="https://en.wikipedia.org/wiki/Transport_Layer_Security">TLS-шифрование</a>, <a href="https://en.wikipedia.org/wiki/Transport_Layer_Security">TLS-шифрование</a>,
@ -1033,10 +963,6 @@ Delta Chat вместо этого использует реализацию Ope
В этом случае сообщения Delta Chat никогда не будут переданы в открытом виде через Интернет, В этом случае сообщения Delta Chat никогда не будут переданы в открытом виде через Интернет,
даже если сообщение не было зашифровано сквозным шифрованием.</p> даже если сообщение не было зашифровано сквозным шифрованием.</p>
<p>Обратите внимание, что <a href="#howtoe2ee">поддержание гарантированного сквозного шифрования</a> поверх шифрования TLS
обеспечивает полную безопасность между вашими устройствами и устройствами получателя.
Ни ваш провайдер электронной почты, ни провайдер Интернета не смогут прочитать или изменить ваши сообщения.</p>
<h3 id="message-metadata"> <h3 id="message-metadata">
@ -1045,25 +971,25 @@ Delta Chat вместо этого использует реализацию Ope
</h3> </h3>
<p>Delta Chat защищает большинство метаданных сообщений, помещая следующую информацию, <p>Unlike most other messengers,
в зашифрованную сквозным шифрованием часть сообщений:</p> Delta Chat apps do not store any metadata about contacts or groups on servers, also not in encrypted form.
Instead, all group metadata is end-to-end encrypted and stored on end-user devices, only.</p>
<p>E-mail Servers can therefore only see</p>
<ul> <ul>
<li>Тема сообщения</li> <li>
<li>Аватар и название группы</li> <p>the message date,</p>
<li>Запросы MDN (уведомление о прочтении) (<code class="language-plaintext highlighter-rouge">Chat-Disposition-Notification-To</code>)</li> </li>
<li>Таймер исчезающих сообщений (<code class="language-plaintext highlighter-rouge">Ephemeral-Timer</code>)</li> <li>
<li>Участник-группы-чата-удалён (<code class="language-plaintext highlighter-rouge">Chat-Group-Member-Removed</code>); Участник-группы-чата-добавлен (<code class="language-plaintext highlighter-rouge">Chat-Group-Member-Added</code>)</li> <p>sender and receiver addresses</p>
<li>Заголовок <code class="language-plaintext highlighter-rouge">Secure-Join</code>, содержащий команды безопасного соединения</li> </li>
<li>Уведомление о включении потоковой передачи местоположения</li> <li>
<li>URL-адрес комнаты WebRTC</li> <p>and message size.</p>
</li>
</ul> </ul>
<p>Серверы электронной почты не получают доступ к этим защищённым метаданным, <p>All other message, contact and group metadata resides in the end-to-end encrypted part of messages.</p>
но они видят дату сообщения, а также его размер,
и, что более важно, адреса отправителя и получателя.
Серверам электронной почты нужны адреса получателей для маршрутизации и
доставки сообщений на устройства получателей.</p>
<h3 id="device-seizure"> <h3 id="device-seizure">
@ -1073,99 +999,36 @@ Delta Chat вместо этого использует реализацию Ope
</h3> </h3>
<p>Для защиты от серверов электронной почты, собирающих метаданные, <p>Both for protecting against metadata-collecting e-mail servers
а также от угрозы конфискации устройства, as well as against the threat of device seizure
мы рекомендуем использовать <a href="https://delta.chat/chatmail">сервер chatmail</a>, we recommend to use a <a href="https://chatmail.at/relays">chatmail relay</a>
для создания безымянных (псевдонимных), временных профилей через сканирование QR-кодов. to create chat profiles using random e-mail addresses for transport.
Обратите внимание, что приложения Delta Chat на всех платформах поддерживают несколько профилей, Note that Delta Chat apps on all platforms support multiple profiles
так что вы можете легко использовать отдельные профили, для конкретной ситуации, so you can easily use situation-specific profiles next to your “main” profile
помимо вашего “основного” профиля, with the knowledge that all their data, along with all metadata, will be deleted.
зная, что все их данные, вместе с метаданными, будут удалены. Moreover, if a device is seized then chat contacts using short-lived profiles
Кроме того, если устройство будет конфисковано, контакты, использующие временные профили, can not be identified easily.</p>
не могут быть легко идентифицированы, в отличие от мессенджеров, которые раскрывают
номера телефонов в групповых чатах, которые часто связаны с реальными личностями.</p>
<h3 id="как-я-могу-проверить-информацию-о-шифровании"> <h3 id="sealedsender">
Как я могу проверить информацию о шифровании? <a href="#как-я-могу-проверить-информацию-о-шифровании" class="anchor"></a> Does Delta Chat support “Sealed Sender”? <a href="#sealedsender" class="anchor"></a>
</h3> </h3>
<p>Вы можете проверить статус сквозного шифрования вручную в диалоговом окне “Шифрование” <p>Нет, пока нет.</p>
(профиль пользователя на Android/iOS или щелкните правой кнопкой мыши элемент списка чата пользователя в приложении для ПК).
Delta Chat показывает там два отпечатка.
Если на вашем устройстве и на устройстве вашего контакта показаны одинаковые отпечатки,
соединение безопасно.</p>
<h3 id="как-я-могу-проверить-статус-шифрования-сообщений"> <p>The Signal messenger introduced <a href="https://signal.org/blog/sealed-sender/">“Sealed Sender” in 2018</a>
to keep their server infrastructure ignorant of who is sending a message to a set of recipients.
It is particularly important because the Signal server knows the mobile number of each account,
which is usually associated with a passport identity.</p>
<p>Even if <a href="https://chatmail.at/relays">chatmail relays</a>
Как я могу проверить статус шифрования сообщений? <a href="#как-я-могу-проверить-статус-шифрования-сообщений" class="anchor"></a> do not ask for any private data (including no phone numbers),
it might still be worthwhile to protect relational metadata between addresses.
We don’t foresee bigger problems in using random throw-away e-mail addresses for sealed sending
</h3> but an implementation has not been agreed as a priority yet.</p>
<p>Маленький <strong>значок замка</strong> в сообщении означает,
что сообщение было правильно зашифровано сквозным шифрованием от данного отправителя.
Если <strong>замка нет</strong>, сообщение не было правильно зашифровано,
возможно, потому что отправитель использует приложение или веб-интерфейс электронной почты
без поддержки сквозного шифрования.</p>
<h3 id="почему-я-вижу-незашифрованные-сообщения">
Почему я вижу незашифрованные сообщения? <a href="#почему-я-вижу-незашифрованные-сообщения" class="anchor"></a>
</h3>
<p>Если контакт использует приложение электронной почты, не поддерживающее Autocrypt,
все сообщения, включающие этого контакта (в групповом или личном 1:1 чате),
не будут зашифрованы сквозным шифрованием, и поэтому не будут иметь “значок замка” в сообщениях.
Обратите внимание, что даже если ваши контакты используют Delta Chat на своем аккаунте,
они также могут использовать приложение электронной почты, не поддерживающее Autocrypt,
на том же аккаунте, что может привести к периодически незашифрованным сообщениям.
Ответ на незашифрованные сообщения незашифрованным сообщением является обязательным в Autocrypt,
чтобы предотвратить появление нечитаемых сообщений на стороне ваших контактов
и их приложении электронной почты, которое не поддерживает Autocrypt.</p>
<h3 id="как-я-могу-получить-зашифрованный-сквозным-шифрованием-чат-с-контактом-delta-chat-который-иногда-использует-веб-почту-или-другое-приложение-электронной-почты-не-поддерживающее-autocrypt">
Как я могу получить зашифрованный сквозным шифрованием чат с контактом Delta Chat, который иногда использует веб-почту или другое приложение электронной почты, не поддерживающее Autocrypt? <a href="#как-я-могу-получить-зашифрованный-сквозным-шифрованием-чат-с-контактом-delta-chat-который-иногда-использует-веб-почту-или-другое-приложение-электронной-почты-не-поддерживающее-autocrypt" class="anchor"></a>
</h3>
<p>Если вам нужен зашифрованный сквозным шифрованием чат с контактом,
который использует свой адрес электронной почты как с Delta Chat, так и с приложениями, не поддерживающими Autocrypt (например, веб-почтой),
лучше всего настроить с ним <a href="#howtoe2ee">гарантированное сквозное шифрование</a>
и затем создать гарантированно зашифрованный сквозным шифрованием групповой чат с вами двумя как участниками.
В этом групповом чате все сообщения будут зашифрованы сквозным шифрованием,
даже если прямой чат между вами двумя имеет предупреждение
<a href="#nocryptanymore">“… отправил сообщение с другого устройства”</a>.</p>
<h3 id="как-я-могу-обеспечить-сквозное-шифрование-и-удаление-сообщений">
Как я могу обеспечить сквозное шифрование и удаление сообщений? <a href="#как-я-могу-обеспечить-сквозное-шифрование-и-удаление-сообщений" class="anchor"></a>
</h3>
<p>Лучший способ обеспечить сквозное шифрование каждого сообщения,
где метаданные удаляются как можно быстрее,
это <a href="#howtoe2ee">использовать чаты с гарантированным сквозным шифрованием</a>
и включить <a href="#ephemeralmsgs">исчезающие сообщения</a>.</p>
<p>Чаты с гарантированным сквозным шифрованием защищают от <a href="https://en.wikipedia.org/wiki/Man-in-the-middle_attack">атак “человек посередине”</a>,
а включение исчезающих сообщений удаляет сообщения
на сервере через заданное пользователем время.</p>
<p>Если вам не нужна долгоживущая копия ваших сообщений на сервере,
вы также можете включить <a href="#delold">“удалять сообщения с сервера автоматически”</a>.</p>
<h3 id="pfs"> <h3 id="pfs">
@ -1175,44 +1038,52 @@ Delta Chat показывает там два отпечатка.
</h3> </h3>
<p>Нет, Delta Chat не поддерживает совершенную прямую секретность (PFS). <p>Нет, пока нет.</p>
Это означает, что если ваш личный ключ дешифрования Delta Chat будет скомпрометирован,
и кто-то собрал ваши предыдущие сообщения, переданные по сети,
то они смогут расшифровать и прочитать их с помощью скомпрометированного ключа дешифрования.</p>
<p>Обратите внимание, если кто-то получит доступ к вашим ключам дешифрования, <p>Delta Chat today doesn’t support Perfect Forward Secrecy (PFS).
они, как правило, также смогут получить доступ к вашим сообщениям, This means that if your private decryption key is leaked,
независимо от того, используется ли совершенная прямая секретность или нет. and someone has collected your prior in-transit messages,
Типичная реальная ситуация для утечки ключей дешифрования - это изъятие устройства, they will be able to decrypt and read them using the leaked decryption key.
о чём мы говорим в нашем ответе <a href="#device-seizure">о метаданных и изъятии устройства</a>.</p> Note that Forward Secrecy only increases security if you delete messages.
Otherwise, someone obtaining your decryption keys
is typically also able to get all your non-deleted messages
and doesn’t even need to decrypt any previously collected messages.</p>
<p>Возможно, Delta Chat будет развиваться в направлении поддержки совершенной прямой секретности (PFS), <p>We designed a Forward Secrecy approach that withstood
поскольку OpenPGP является всего лишь контейнером для зашифрованных сообщений, initial examination from some cryptographers and implementation experts
но управление ключами шифрования (и, следовательно, ротация ключей или “переключение” ключей) but is pending a more formal write up
могут быть организованы гибкими способами. to ascertain it reliably works in federated messaging and with multi-device usage,
См. <a href="https://gitlab.com/sequoia-pgp/openpgp-dr">прототип PFS Seqouia</a> before it could be implemented in <a href="https://github.com/chatmail/core">chatmail core</a>,
для существующих экспериментов в сообществе разработчиков OpenPGP.</p> which would make it available in all <a href="https://chatmail.at/clients">chatmail clients</a>.</p>
<h3 id="является-ли-сквозное-шифрование-delta-chat-таким-же-безопасным-как-signal"> <h3 id="pqc">
Является ли сквозное шифрование Delta Chat таким же безопасным как Signal? <a href="#является-ли-сквозное-шифрование-delta-chat-таким-же-безопасным-как-signal" class="anchor"></a> Does Delta Chat support Post-Quantum-Cryptography? <a href="#pqc" class="anchor"></a>
</h3> </h3>
<p>Это зависит от того, что для вас важно. <p>Нет, пока нет.</p>
Delta Chat <a href="#pfs">не поддерживает PFS</a>, как Signal,
но обеспечивает <a href="#e2eeguarantee">гарантированно зашифрованные сквозным шифрованием чаты</a>
защищенные от скомпрометированных серверов или поврежденных сетей.
Signal и большинство других мессенджеров, поддерживающих PFS,
не предоставляют практической схемы защиты групповых чатов от сетевых атак,
которые, возможно, вызывают большее беспокойство,
чем потенциальный злоумышленник, который захватывает ваш телефон и настройки персонального шифрования,
но почему-то не ваши сообщения, но при этом имеет полный отчет обо всех прошлых зашифрованных сообщениях.</p>
<p>В любом случае, сквозное шифрование Delta Chat использует <a href="#openpgp-secure">безопасное подмножество OpenPGP</a> <p>Delta Chat uses the Rust OpenPGP library <a href="https://github.com/rpgp/rpgp">rPGP</a>
которое прошло <a href="https://delta.chat/assets/blog/2019-first-security-review.pdf">независимую проверку безопасности</a>.</p> which supports the latest <a href="https://datatracker.ietf.org/doc/draft-ietf-openpgp-pqc/">IETF Post-Quantum-Cryptography OpenPGP draft</a>.
We aim to add PQC support in <a href="https://github.com/chatmail/core">chatmail core</a> after the draft is finalized at the IETF
in collaboration with other OpenPGP implementers.</p>
<h3 id="how-can-i-manually-check-encryption-information">
How can I manually check encryption information? <a href="#how-can-i-manually-check-encryption-information" class="anchor"></a>
</h3>
<p>Вы можете проверить статус сквозного шифрования вручную в диалоговом окне “Шифрование”
(профиль пользователя на Android/iOS или щелкните правой кнопкой мыши элемент списка чата пользователя в приложении для ПК).
Delta Chat показывает там два отпечатка.
Если на вашем устройстве и на устройстве вашего контакта показаны одинаковые отпечатки,
соединение безопасно.</p>
<h3 id="importkey"> <h3 id="importkey">
@ -1640,6 +1511,11 @@ Delta Chat</a>.</li>
</h3> </h3>
<p>Note:
Changing email addresses is temporarily disabled
because of ongoing changes to the DeltaChat core.
It should be available again in a few months.</p>
<ol> <ol>
<li> <li>
<p>Измените свой адрес в разделе “Настройки → Дополнительные параметры → Пароль и аккаунт” и <p>Измените свой адрес в разделе “Настройки → Дополнительные параметры → Пароль и аккаунт” и

420
src/main/assets/help/sk/help.html
View file

@ -36,27 +36,24 @@
<li><a href="#why-does-delta-chat-integrate-with-centralized-proprietary-applegoogle-push-services">Why does Delta Chat integrate with centralized proprietary Apple/Google push services?</a></li> <li><a href="#why-does-delta-chat-integrate-with-centralized-proprietary-applegoogle-push-services">Why does Delta Chat integrate with centralized proprietary Apple/Google push services?</a></li>
</ul> </ul>
</li> </li>
<li><a href="#encryption-and-security">Encryption and Security</a> <li><a href="#e2ee">Encryption and Security</a>
<ul> <ul>
<li><a href="#which-standards-are-used-for-end-to-end-encryption">Which standards are used for end-to-end encryption?</a></li> <li><a href="#which-standards-are-used-for-end-to-end-encryption">Which standards are used for end-to-end encryption?</a></li>
<li><a href="#whene2e">How can i know if messages are end-to-end encrypted?</a></li> <li><a href="#whene2e">How can i know if messages are end-to-end encrypted?</a></li>
<li><a href="#howtoe2ee">How can I get guaranteed end-to-end encryption and green checkmarks?</a></li> <li><a href="#can-i-still-receive-or-send-mails-without-end-to-end-encryption">Can i still receive or send mails without end-to-end encryption?</a></li>
<li><a href="#e2eeguarantee">What does the green checkmark and “guaranteed end-to-end encryption” mean?</a></li> <li><a href="#howtoe2ee">How can I establish a chat with a new contact?</a></li>
<li><a href="#nocryptanymore">A contact “sent a message from another device”, what can i do?</a></li> <li><a href="#e2eeguarantee">What does the green checkmark in a contact profile mean?</a></li>
<li><a href="#are-attachments-pictures-files-audio-etc-end-to-end-encrypted">Are attachments (pictures, files, audio etc.) end-to-end encrypted?</a></li> <li><a href="#are-attachments-pictures-files-audio-etc-end-to-end-encrypted">Are attachments (pictures, files, audio etc.) end-to-end encrypted?</a></li>
<li><a href="#openpgp-secure">Is OpenPGP secure?</a></li> <li><a href="#openpgp-secure">Is OpenPGP secure?</a></li>
<li><a href="#openpgp-alternatives">Did you consider using alternatives to OpenPGP for end-to-end -encryption?</a></li> <li><a href="#openpgp-alternatives">Did you consider using alternatives to OpenPGP for end-to-end-encryption?</a></li>
<li><a href="#is-delta-chat-vulnerable-to-efail">Is Delta Chat vulnerable to EFAIL?</a></li> <li><a href="#is-delta-chat-vulnerable-to-efail">Is Delta Chat vulnerable to EFAIL?</a></li>
<li><a href="#tls">Is a message exposed in cleartext if end-to-end encryption is not available?</a></li> <li><a href="#tls">Are messages marked with the mail icon exposed on the Internet?</a></li>
<li><a href="#message-metadata">How does Delta Chat protect metadata in messages?</a></li> <li><a href="#message-metadata">How does Delta Chat protect metadata in messages?</a></li>
<li><a href="#device-seizure">How to protect metadata and contacts when a device is seized?</a></li> <li><a href="#device-seizure">How to protect metadata and contacts when a device is seized?</a></li>
<li><a href="#how-can-i-check-encryption-information">How can i check encryption information?</a></li> <li><a href="#sealedsender">Does Delta Chat support “Sealed Sender”?</a></li>
<li><a href="#how-can-i-check-the-encryption-status-of-messages">How can I check the encryption status of messages?</a></li>
<li><a href="#why-do-i-see-unencrypted-messages">Why do I see unencrypted messages?</a></li>
<li><a href="#how-can-i-get-an-end-to-end-encrypted-chat-with-a-delta-chat-contact-who-sometimes-uses-webmail-or-another-non-autocrypt-e-mail-app">How can i get an end-to-end encrypted chat with a Delta Chat contact who sometimes uses webmail or another non-Autocrypt e-mail app?</a></li>
<li><a href="#how-can-i-ensure-message-end-to-end-encryption-and-deletion">How can I ensure message end-to-end encryption and deletion?</a></li>
<li><a href="#pfs">Does Delta Chat support Perfect Forward Secrecy?</a></li> <li><a href="#pfs">Does Delta Chat support Perfect Forward Secrecy?</a></li>
<li><a href="#is-end-to-end-encryption-of-delta-chat-as-safe-as-signal">Is end-to-end encryption of Delta Chat as safe as Signal?</a></li> <li><a href="#pqc">Does Delta Chat support Post-Quantum-Cryptography?</a></li>
<li><a href="#how-can-i-manually-check-encryption-information">How can I manually check encryption information?</a></li>
<li><a href="#importkey">Môžem znova použiť svoj existujúci súkromný kľúč?</a></li> <li><a href="#importkey">Môžem znova použiť svoj existujúci súkromný kľúč?</a></li>
<li><a href="#security-audits">Was Delta Chat independently audited for security vulnerabilities?</a></li> <li><a href="#security-audits">Was Delta Chat independently audited for security vulnerabilities?</a></li>
</ul> </ul>
@ -723,10 +720,10 @@ that achieves “instant delivery” of messages for all chatmail servers
including a potential one <a href="https://delta.chat/chatmail#selfhosted">you might setup yourself without our permission</a>. including a potential one <a href="https://delta.chat/chatmail#selfhosted">you might setup yourself without our permission</a>.
Welcome to the power of the interoperable and massive chatmail and e-mail system :)</p> Welcome to the power of the interoperable and massive chatmail and e-mail system :)</p>
<h2 id="encryption-and-security"> <h2 id="e2ee">
Encryption and Security <a href="#encryption-and-security" class="anchor"></a> Encryption and Security <a href="#e2ee" class="anchor"></a>
</h2> </h2>
@ -739,18 +736,26 @@ Welcome to the power of the interoperable and massive chatmail and e-mail system
</h3> </h3>
<p><a href="https://autocrypt.org">Autocrypt</a> is used for automatically <p>Delta Chat uses a <a href="#openpgp-secure">secure subset of the OpenPGP standard</a>
establishing end-to-end encryption with contacts and group chats. to provide automatic end-to-end encryption using these protocols:</p>
Autocrypt uses a limited and <a href="#openpgp-secure">secure subset of the OpenPGP standard</a>.
End-to-End encrypted messages are marked with a padlock
<img style="vertical-align:middle; width:1.2em; margin:1px" src="../lock-icon.png" alt="padlock" />.</p>
<p><a href="https://securejoin.delta.chat/en/latest/new.html">Secure-Join protocols</a> <ul>
are used for establishing chats with guaranteed end-to-end encryption <li>
which protects against network attacks and compromised servers. <p><a href="https://securejoin.delta.chat/en/latest/new.html">Secure-Join</a>
Chats marked with a green checkmark to exchange encryption setup information through QR-code scanning or “invite links”.</p>
<img style="vertical-align:middle; width:1.5em; margin:1px" src="../green-checkmark.png" alt="green checkmark" /> </li>
guarantee end-to-end encrypted messages.</p> <li>
<p><a href="https://autocrypt.org">Autocrypt</a> is used for automatically
establishing end-to-end encryption between contacts and all members of a group chat.</p>
</li>
<li>
<p><a href="https://github.com/chatmail/core/blob/main/spec.md#attaching-a-contact-to-a-message">Sharing a contact to a
chat</a>
enables receivers to use end-to-end encryption with the contact.</p>
</li>
</ul>
<p>Delta Chat does not query, publish or interact with any OpenPGP key servers.</p>
<h3 id="whene2e"> <h3 id="whene2e">
@ -760,28 +765,37 @@ guarantee end-to-end encrypted messages.</p>
</h3> </h3>
<p>All end-to-end encrypted messages carry a padlock:</p> <p>All messages in Delta Chat are <strong>end-to-end encrypted by default</strong>.
Since the Delta Chat Version 2 release series (July 2025)
there are no lock or similar markers on end-to-end encrypted messages, anymore.</p>
<p><img style="width:160px; margin:1px" src="../lock-screenshot.png" alt="padlock in bubble" /></p> <h3 id="can-i-still-receive-or-send-mails-without-end-to-end-encryption">
<p>End-to-end encryption is guaranteed if there is a green checkmark next to the chat title:</p>
<p><img style="width:211px; margin:1px" src="../green-checkmark-screenshot.png" alt="green checkmark in title" /></p>
<h3 id="howtoe2ee">
How can I get guaranteed end-to-end encryption and green checkmarks? <a href="#howtoe2ee" class="anchor"></a> Can i still receive or send mails without end-to-end encryption? <a href="#can-i-still-receive-or-send-mails-without-end-to-end-encryption" class="anchor"></a>
</h3> </h3>
<p>If you have a second communication channel with your chat partner, <p>If you use default <a href="https://chatmail.at/relays">chatmail relays</a>,
like a video chat or a different messenger, it is impossible to receive or send messages without end-to-end encryption.</p>
you can generate an invite link.</p>
<p>If you are together in person, <p>If you instead create a profile using a classic e-mail server,
you can show a QR code to your chat partner.</p> you can send and receive messages without end-to-end encryption.
Such messages lacking end-to-end encryption are marked with an e-mail icon
<img style="vertical-align:middle; width:1.2em; margin:1px" src="../email-icon.png" alt="email" />.</p>
<h3 id="howtoe2ee">
How can I establish a chat with a new contact? <a href="#howtoe2ee" class="anchor"></a>
</h3>
<p>You can send an invite link through another private chat,
show an invitation QR code when next to each other or in a video call,
or click on a “contact” that was shared in a chat.</p>
<ul> <ul>
<li> <li>
@ -796,135 +810,54 @@ on the Delta Chat app main screen.</p>
</li> </li>
</ul> </ul>
<p>Let your chat partner scan the QR image <p>Ask your chat partner to scan the QR image
with their Delta Chat app, with their Delta Chat app,
or click “Copy” or “Share” to create an invite link or click “Copy” or “Share” to create an invite link
and share it with your chat partner.</p> and share it with your chat partner.</p>
<p>Now wait while <a href="https://securejoin.delta.chat/en/latest/new.html#setup-contact-protocol">Secure-Join network messages are exchanged</a> between both devices.</p> <p>Now wait while <a href="https://securejoin.delta.chat/en/latest/new.html#setup-contact-protocol">end-to-end encryption is getting established</a>.</p>
<ul> <ul>
<li> <li>
<p>If both devices are online, <p>If both sides are online, they will soon see a (group or direct) chat
both sides will eventually see a (group or direct) chat with a green checkmark and can start messaging securely.</p>
<img style="vertical-align:middle; width:1.5em; margin:1px" src="../green-checkmark.png" alt="green checkmark" />
next to the title.</p>
</li> </li>
<li> <li>
<p>If one of the devices is offline, the green checkmarks will only <p>If one side is offline or in bad network,
appear later when the device is internet-connected again the ability to chat is delayed until connectivity is restored.</p>
and the Secure-Join network protocol completed.</p>
</li> </li>
</ul> </ul>
<p>Congratulations! <p>Congratulations!
You now will automatically use guaranteed end-to-end encryption You now will automatically use end-to-end encryption
with this contact and both of you can add each other to green-checkmarked groups with this contact.
<img style="vertical-align:middle; width:1.5em; margin:1px" src="../green-checkmark.png" alt="green checkmark" />, If you add each other to chat groups,
thereby automatically spreading guaranteed end-to-end encryption among its members.</p> end-to-end encryption will be established among all members.</p>
<h3 id="e2eeguarantee"> <h3 id="e2eeguarantee">
What does the green checkmark and “guaranteed end-to-end encryption” mean? <a href="#e2eeguarantee" class="anchor"></a> What does the green checkmark in a contact profile mean? <a href="#e2eeguarantee" class="anchor"></a>
</h3> </h3>
<p>Chat titles with green checkmarks <p>A contact profile might show a green checkmark
<img style="vertical-align:middle; width:1.5em; margin:1px" src="../green-checkmark.png" alt="green checkmark" /> <img style="vertical-align:middle; width:1.5em; margin:1px" src="../green-checkmark.png" alt="green checkmark" />
mean that all messages in the chat will be end-to-end encrypted and an “Introduced by” line.
and can not be read or altered by compromised e-mail servers or Internet providers.
Joining green-checkmarked group chats
safely spreads everybody’s encryption information (and green checkmarks)
in a manner that guarantees end-to-end encryption in the group and among members.</p>
<p>Contact profiles with green checkmarks
<img style="vertical-align:middle; width:1.5em; margin:1px" src="../green-checkmark.png" alt="green checkmark" />
mean that messaging a contact is currently guaranteed to be end-to-end encrypted.
Every green-checkmarked contact either did a direct <a href="#howtoe2ee">QR-scan</a> with you Every green-checkmarked contact either did a direct <a href="#howtoe2ee">QR-scan</a> with you
or was introduced by a another green-checkmarked contact. or was introduced by a another green-checkmarked contact.
Introductions happen automatically when adding members to groups. Introductions happen automatically when adding members to groups.
Whoever adds a contact to a green-checkmarked group becomes an introducer Whoever adds a green-checkmarked contact to a group with only green-checkmarked members
to those members who didn’t yet know about the added contact. becomes an introducer.
In a contact profile you can tap on the “Introduced by …” text repeatedly In a contact profile you can tap on the “Introduced by …” text repeatedly
until you get to the one with whom you directly did a <a href="#howtoe2ee">QR-scan</a>.</p> until you get to the one with whom you directly did a <a href="#howtoe2ee">QR-scan</a>.</p>
<p>Note that in a contact profile you may see and tap introducers
but there is no green checkmark in the profile title.
This usually means that the contact <a href="#nocryptanymore">“sent a message from another device”</a>.</p>
<p>For more in-depth discussion of “guaranteed end-to-end encryption” <p>For more in-depth discussion of “guaranteed end-to-end encryption”
please see <a href="https://securejoin.delta.chat/en/latest/new.html">Secure-Join protocols</a> please see <a href="https://securejoin.delta.chat/en/latest/new.html">Secure-Join protocols</a>
and specifically read about “Verified Groups”, the technical term and specifically read about “Verified Groups”, the technical term
of what is called here “green-checkmarked” or “guaranteed end-to-end encrypted” chats.</p> of what is called here “green-checkmarked” or “guaranteed end-to-end encrypted” chats.</p>
<h3 id="nocryptanymore">
A contact “sent a message from another device”, what can i do? <a href="#nocryptanymore" class="anchor"></a>
</h3>
<p>Your chat with a contact lost guaranteed end-to-end encryption.
The green checkmark was removed for this chat and contact when you see this warning.
<strong>If you find the sudden drop of guaranteed end-to-end encryption
surprising for this contact then don’t accept the warning!</strong>
Instead check with your contact through a second channel
like a video call, other messenger or a phone call,
to find out what happened.</p>
<p>If your contact actually caused the drop of guaranteed end-to-end encryption
please see the next paragraphs for common reasons and their mitigations.
Regardless, all other green-checkmarked chats remain guaranteed end-to-end encrypted
even if the contact is a member there.</p>
<p><strong>Your contact is using Delta Chat on a second device (phone or laptop)</strong></p>
<p>If they have another device with a Delta Chat app running,
they should remove the profile from the new device
and add it <a href="#multiclient">as a second device as described here</a>.
As soon as they message you afterwards, the warning will be gone
and guaranteed encryption is established with both devices of your contact.</p>
<p><strong>Your contact reinstalled Delta Chat using their old account login</strong></p>
<p>If they have <a href="#backup">a backup file</a>,
they should remove the profile from the new device
and rather import the backup file to re-create their profile.
As soon as they message you afterwards, the warning will be gone
and guaranteed encryption is re-established for this contact.</p>
<p>If they don’t have a backup file, it’s best to perform a <a href="#howtoe2ee">QR scan</a>
with your chat partner to re-establish guaranteed end-to-end encryption.</p>
<p><strong>Your contact sent a mail through a webmail interface or another e-mail app
and will get back to using Delta Chat soon again.</strong></p>
<p>If you are sure that the contact sometimes uses webmail,
or another mail app lacking end-to-end encryption,
then you may accept the warning.
As soon as your contact uses Delta Chat again,
guaranteed end-to-end encryption will be automatically re-established.</p>
<p><strong>Your contact stopped using Delta Chat entirely</strong></p>
<p>Sometimes remaining in contact is more important than end-to-end encryption.
<a href="#tls">“Transport Layer Encryption” (TLS)</a> may still meaningfully protect
the confidentiality of your messages between your device and the e-mail server.
But without end-to-end encryption you and your contact are trusting your e-mail server
to not read or manipulate your messages, and to not hand them to third parties.</p>
<p>In any case, you can not do much else than accept the warning.
Please also remove the contact from any active green-checkmarked group
which you can find in “Chats in Common” in the Contact profile.
This spares your contact from getting “unreadable” messages.</p>
<p>If the contact removed Delta Chat because of buggy or undesirable behaviour,
please consider posting to our <a href="https://support.delta.chat">support forum</a>
to help us identify and address common problems. Thanks!</p>
<h3 id="are-attachments-pictures-files-audio-etc-end-to-end-encrypted"> <h3 id="are-attachments-pictures-files-audio-etc-end-to-end-encrypted">
@ -949,8 +882,7 @@ and attachment metadata such as filenames.</p>
</h3> </h3>
<p>Yes, Delta Chat uses a secure subset of OpenPGP <p>Yes, Delta Chat uses a secure subset of OpenPGP
and only displays a padlock security indicator on a message requiring the whole message to be properly encrypted and signed.
if the whole message is properly encrypted and signed.
For example, “Detached signatures” are not treated as secure.</p> For example, “Detached signatures” are not treated as secure.</p>
<p>OpenPGP is not insecure by itself. <p>OpenPGP is not insecure by itself.
@ -971,7 +903,7 @@ which was thankfully adopted in summer 2023.</p>
<h3 id="openpgp-alternatives"> <h3 id="openpgp-alternatives">
Did you consider using alternatives to OpenPGP for end-to-end -encryption? <a href="#openpgp-alternatives" class="anchor"></a> Did you consider using alternatives to OpenPGP for end-to-end-encryption? <a href="#openpgp-alternatives" class="anchor"></a>
</h3> </h3>
@ -1014,17 +946,15 @@ as defined by the Autocrypt Level 1 specification.</p>
<h3 id="tls"> <h3 id="tls">
Is a message exposed in cleartext if end-to-end encryption is not available? <a href="#tls" class="anchor"></a> Are messages marked with the mail icon exposed on the Internet? <a href="#tls" class="anchor"></a>
</h3> </h3>
<p>Even if your messages are not guaranteed to be end-to-end encrypted, <p>If you are sending or receiving e-mail messages without end-to-end encryption (using a classic e-mail server),
they are still protected from Internet providers like cell or cable companies. they are still protected from cell or cable companies who can not read or modify your e-mail messages.
However, your and your recipient’s e-mail providers But both your and your recipient’s e-mail providers
may read, analyze or even modify your messages, may read, analyze or modify your messages, including any attachments.</p>
including any attachments,
if they are not end-to-end encrypted.</p>
<p>Delta Chat by default uses strict <p>Delta Chat by default uses strict
<a href="https://en.wikipedia.org/wiki/Transport_Layer_Security">TLS encryption</a> <a href="https://en.wikipedia.org/wiki/Transport_Layer_Security">TLS encryption</a>
@ -1037,10 +967,6 @@ then transport encryption will be enforced between e-mail providers
in which case Delta Chat communications will never be exposed in cleartext to the Internet in which case Delta Chat communications will never be exposed in cleartext to the Internet
even if the message was not end-to-end encrypted.</p> even if the message was not end-to-end encrypted.</p>
<p>Note that <a href="#howtoe2ee">maintaining guaranteed end-to-end encryption</a> on top of TLS encryption
provides pervasive safety between your and the recipient’s devices.
Not even your e-mail or Internet provider will be able to read or modify your messages.</p>
<h3 id="message-metadata"> <h3 id="message-metadata">
@ -1049,25 +975,25 @@ Not even your e-mail or Internet provider will be able to read or modify your me
</h3> </h3>
<p>Delta Chat protects most message metadata by putting the following information <p>Unlike most other messengers,
into the end-to-end encrypted part of messages:</p> Delta Chat apps do not store any metadata about contacts or groups on servers, also not in encrypted form.
Instead, all group metadata is end-to-end encrypted and stored on end-user devices, only.</p>
<p>E-mail Servers can therefore only see</p>
<ul> <ul>
<li>Subject line</li> <li>
<li>Group avatar and name</li> <p>the message date,</p>
<li>MDN (read receipt) requests (<code class="language-plaintext highlighter-rouge">Chat-Disposition-Notification-To</code>)</li> </li>
<li>Disappearing message timer (<code class="language-plaintext highlighter-rouge">Ephemeral-Timer</code>)</li> <li>
<li><code class="language-plaintext highlighter-rouge">Chat-Group-Member-Removed</code>, <code class="language-plaintext highlighter-rouge">Chat-Group-Member-Added</code></li> <p>sender and receiver addresses</p>
<li><code class="language-plaintext highlighter-rouge">Secure-Join</code> header containing secure join commands</li> </li>
<li>Notification about enabling location streaming</li> <li>
<li>WebRTC room URL</li> <p>and message size.</p>
</li>
</ul> </ul>
<p>E-Mail servers do not get access to this protected metadata <p>All other message, contact and group metadata resides in the end-to-end encrypted part of messages.</p>
but they do see the message date as well as the message size,
and, more importantly, the sender and receiver addresses.
E-mail servers need receiver addresses to route and
deliver messages to recipient’s devices.</p>
<h3 id="device-seizure"> <h3 id="device-seizure">
@ -1079,96 +1005,34 @@ deliver messages to recipient’s devices.</p>
<p>Both for protecting against metadata-collecting e-mail servers <p>Both for protecting against metadata-collecting e-mail servers
as well as against the threat of device seizure as well as against the threat of device seizure
we recommend to use a <a href="https://delta.chat/chatmail">chatmail server</a> we recommend to use a <a href="https://chatmail.at/relays">chatmail relay</a>
to create pseudonymous temporary profiles through QR-code scans. to create chat profiles using random e-mail addresses for transport.
Note that Delta Chat apps on all platforms support multiple profiles Note that Delta Chat apps on all platforms support multiple profiles
so you can easily use situation-specific profiles next to your “main” profile so you can easily use situation-specific profiles next to your “main” profile
with the knowledge that all their data, along with all metadata, will be deleted. with the knowledge that all their data, along with all metadata, will be deleted.
Moreover, if a device is seized then contacts using temporary profiles Moreover, if a device is seized then chat contacts using short-lived profiles
can not be identified easily, as compared to messengers which reveal can not be identified easily.</p>
phone numbers in chat groups which in turn are often associated with legal identities.</p>
<h3 id="how-can-i-check-encryption-information"> <h3 id="sealedsender">
How can i check encryption information? <a href="#how-can-i-check-encryption-information" class="anchor"></a> Does Delta Chat support “Sealed Sender”? <a href="#sealedsender" class="anchor"></a>
</h3> </h3>
<p>You may check the end-to-end encryption status manually in the “Encryption” dialog <p>No, not yet.</p>
(user profile on Android/iOS or right-click a user’s chat-list item on desktop).
Delta Chat shows two fingerprints there.
If the same fingerprints appear on your own and your contact’s device,
the connection is safe.</p>
<h3 id="how-can-i-check-the-encryption-status-of-messages"> <p>The Signal messenger introduced <a href="https://signal.org/blog/sealed-sender/">“Sealed Sender” in 2018</a>
to keep their server infrastructure ignorant of who is sending a message to a set of recipients.
It is particularly important because the Signal server knows the mobile number of each account,
which is usually associated with a passport identity.</p>
<p>Even if <a href="https://chatmail.at/relays">chatmail relays</a>
How can I check the encryption status of messages? <a href="#how-can-i-check-the-encryption-status-of-messages" class="anchor"></a> do not ask for any private data (including no phone numbers),
it might still be worthwhile to protect relational metadata between addresses.
We don’t foresee bigger problems in using random throw-away e-mail addresses for sealed sending
</h3> but an implementation has not been agreed as a priority yet.</p>
<p>A little <strong>padlock</strong> in a message bubble denotes
that the message was properly end-to-end encrypted from the given sender.
If there is <strong>no padlock</strong>, the message was not properly end-to-end encrypted
most likely because the sender uses an app or webmail interface
without support for end-to-end–encryption.</p>
<h3 id="why-do-i-see-unencrypted-messages">
Why do I see unencrypted messages? <a href="#why-do-i-see-unencrypted-messages" class="anchor"></a>
</h3>
<p>If a contact uses a non-Autocrypt e-mail app,
all messages involving this contact (in a group or 1:1 chat)
will not be end-to-end encrypted, and thus not show a “padlock” with messages.
Note that even if your contacts use Delta Chat on their account,
they might also use a non-Autocrypt e-mail app on that account
which then may cause intermittently unencrypted messages.
Replying unencrypted to unencrypted messages is mandated by Autocrypt
to prevent unreadable messages on the side of your contacts
and their non-Autocrypt e-mail app.</p>
<h3 id="how-can-i-get-an-end-to-end-encrypted-chat-with-a-delta-chat-contact-who-sometimes-uses-webmail-or-another-non-autocrypt-e-mail-app">
How can i get an end-to-end encrypted chat with a Delta Chat contact who sometimes uses webmail or another non-Autocrypt e-mail app? <a href="#how-can-i-get-an-end-to-end-encrypted-chat-with-a-delta-chat-contact-who-sometimes-uses-webmail-or-another-non-autocrypt-e-mail-app" class="anchor"></a>
</h3>
<p>If you need a safely end-to-end encrypted chat with a contact
who is using their e-mail account both with Delta Chat and non-Autocrypt apps (e.g. webmail),
it’s best to setup <a href="#howtoe2ee">guaranteed end-to-end encryption with them</a>
and then create a guaranteed end-to-end encrypted group chat with you two as members.
In this group chat all messages will be end-to-end encrypted
even if the direct chat between you two has a
<a href="#nocryptanymore">“… sent a message from another device”</a> warning.</p>
<h3 id="how-can-i-ensure-message-end-to-end-encryption-and-deletion">
How can I ensure message end-to-end encryption and deletion? <a href="#how-can-i-ensure-message-end-to-end-encryption-and-deletion" class="anchor"></a>
</h3>
<p>The best way to ensure every message is end-to-end encrypted,
and metadata deleted as quickly as possible
is <a href="#howtoe2ee">using chats with guaranteed end-to-end encryption</a>
and turning on <a href="#ephemeralmsgs">disappearing messages</a>.</p>
<p>Guaranteed end-to-end encrypted chats protect against <a href="https://en.wikipedia.org/wiki/Man-in-the-middle_attack">MITM attacks</a>
and turning on disappearing messages deletes the messages
on the server after a user-configured time.</p>
<p>If you don’t need a longer-lived copy of your messages on the server,
you can also turn on <a href="#delold">“delete messages from server automatically”</a>.</p>
<h3 id="pfs"> <h3 id="pfs">
@ -1178,45 +1042,52 @@ you can also turn on <a href="#delold">“delete messages from server automatica
</h3> </h3>
<p>No, Delta Chat doesn’t support Perfect Forward Secrecy (PFS). <p>No, not yet.</p>
This means that if your Delta Chat private decryption key is leaked,
<p>Delta Chat today doesn’t support Perfect Forward Secrecy (PFS).
This means that if your private decryption key is leaked,
and someone has collected your prior in-transit messages, and someone has collected your prior in-transit messages,
they will be able to decrypt and read them using the leaked decryption key.</p> they will be able to decrypt and read them using the leaked decryption key.
Note that Forward Secrecy only increases security if you delete messages.
Otherwise, someone obtaining your decryption keys
is typically also able to get all your non-deleted messages
and doesn’t even need to decrypt any previously collected messages.</p>
<p>Note, however, that if anyone obtains to your decryption keys, <p>We designed a Forward Secrecy approach that withstood
they will typically also be able to obtain your messages, initial examination from some cryptographers and implementation experts
irrespective if Perfect Forward Secrecy is in place or not. but is pending a more formal write up
The typical real-world situation for leaked decryption keys is device seizure to ascertain it reliably works in federated messaging and with multi-device usage,
which we discuss in our answer <a href="#device-seizure">on metadata and device seizure</a>.</p> before it could be implemented in <a href="https://github.com/chatmail/core">chatmail core</a>,
which would make it available in all <a href="https://chatmail.at/clients">chatmail clients</a>.</p>
<p>It is possible that Delta Chat evolves to support Perfect Forward Secrecy, <h3 id="pqc">
because OpenPGP is just a container for encrypted messages
but encryption key management (and thus key rotation or key “ratcheting”)
could be organized in flexible ways.
See <a href="https://gitlab.com/sequoia-pgp/openpgp-dr">Seqouia’s PFS prototype</a>
for existing experiments in the OpenPGP implementor community.</p>
<h3 id="is-end-to-end-encryption-of-delta-chat-as-safe-as-signal">
Is end-to-end encryption of Delta Chat as safe as Signal? <a href="#is-end-to-end-encryption-of-delta-chat-as-safe-as-signal" class="anchor"></a> Does Delta Chat support Post-Quantum-Cryptography? <a href="#pqc" class="anchor"></a>
</h3> </h3>
<p>It depends on what is important to you. <p>No, not yet.</p>
Delta Chat <a href="#pfs">does not support PFS</a> like Signal does
but it provides <a href="#e2eeguarantee">guaranteed end-to-end encrypted chats</a>
that are safe against compromised servers or corrupted networks.
Signal and most other PFS-supporting messengers do not provide
a practical scheme for protecting chat groups from network attacks
which are arguably more worrisome
than a potential attacker who seizes your phone and private encryption setup
but somehow not your messages, yet has a full record of all
past encrypted messages.</p>
<p>In any case, Delta Chat’s end-to-end encryption uses a <a href="#openpgp-secure">secure subset of OpenPGP</a> <p>Delta Chat uses the Rust OpenPGP library <a href="https://github.com/rpgp/rpgp">rPGP</a>
which has been <a href="https://delta.chat/assets/blog/2019-first-security-review.pdf">independently security-audited</a>.</p> which supports the latest <a href="https://datatracker.ietf.org/doc/draft-ietf-openpgp-pqc/">IETF Post-Quantum-Cryptography OpenPGP draft</a>.
We aim to add PQC support in <a href="https://github.com/chatmail/core">chatmail core</a> after the draft is finalized at the IETF
in collaboration with other OpenPGP implementers.</p>
<h3 id="how-can-i-manually-check-encryption-information">
How can I manually check encryption information? <a href="#how-can-i-manually-check-encryption-information" class="anchor"></a>
</h3>
<p>You may check the end-to-end encryption status manually in the “Encryption” dialog
(user profile on Android/iOS or right-click a user’s chat-list item on desktop).
Delta Chat shows two fingerprints there.
If the same fingerprints appear on your own and your contact’s device,
the connection is safe.</p>
<h3 id="importkey"> <h3 id="importkey">
@ -1251,7 +1122,7 @@ from most recent to older:</p>
<li> <li>
<p>2024 December, an <a href="https://github.com/rpgp/docs/blob/main/audits/NGI%20Core%20rPGP%20penetration%20test%20report%202024%201.0.pdf">NLNET-commissioned Evaluation of <p>2024 December, an <a href="https://github.com/rpgp/docs/blob/main/audits/NGI%20Core%20rPGP%20penetration%20test%20report%202024%201.0.pdf">NLNET-commissioned Evaluation of
rPGP</a> by <a href="https://www.radicallyopensecurity.com/">Radically Open Security</a> took place. rPGP</a> by <a href="https://www.radicallyopensecurity.com/">Radically Open Security</a> took place.
rPGP serves as the end-to-end encyption <a href="https://openpgp.org">OpenPGP</a> engine of Delta Chat. rPGP serves as the end-to-end encryption <a href="https://openpgp.org">OpenPGP</a> engine of Delta Chat.
Two advisories were released related to the findings of this audit:</p> Two advisories were released related to the findings of this audit:</p>
<ul> <ul>
@ -1645,6 +1516,11 @@ vykonáva aplikácia Delta Chat.</p>
</h3> </h3>
<p>Note:
Changing email addresses is temporarily disabled
because of ongoing changes to the DeltaChat core.
It should be available again in a few months.</p>
<ol> <ol>
<li> <li>
<p>Change your address in “Settings → Advanced → Password and Account” and <p>Change your address in “Settings → Advanced → Password and Account” and

420
src/main/assets/help/sq/help.html
View file

@ -36,27 +36,24 @@
<li><a href="#why-does-delta-chat-integrate-with-centralized-proprietary-applegoogle-push-services">Why does Delta Chat integrate with centralized proprietary Apple/Google push services?</a></li> <li><a href="#why-does-delta-chat-integrate-with-centralized-proprietary-applegoogle-push-services">Why does Delta Chat integrate with centralized proprietary Apple/Google push services?</a></li>
</ul> </ul>
</li> </li>
<li><a href="#fshehtëzim-dhe-siguri">Fshehtëzim dhe Siguri</a> <li><a href="#e2ee">Fshehtëzim dhe Siguri</a>
<ul> <ul>
<li><a href="#cilët-standarde-përdoren-për-fshehtëzim-skaj-më-skaj">Cilët standarde përdoren për fshehtëzim skaj-më-skaj?</a></li> <li><a href="#cilët-standarde-përdoren-për-fshehtëzim-skaj-më-skaj">Cilët standarde përdoren për fshehtëzim skaj-më-skaj?</a></li>
<li><a href="#whene2e">How can i know if messages are end-to-end encrypted?</a></li> <li><a href="#whene2e">How can i know if messages are end-to-end encrypted?</a></li>
<li><a href="#howtoe2ee">How can I get guaranteed end-to-end encryption and green checkmarks?</a></li> <li><a href="#can-i-still-receive-or-send-mails-without-end-to-end-encryption">Can i still receive or send mails without end-to-end encryption?</a></li>
<li><a href="#e2eeguarantee">What does the green checkmark and “guaranteed end-to-end encryption” mean?</a></li> <li><a href="#howtoe2ee">How can I establish a chat with a new contact?</a></li>
<li><a href="#nocryptanymore">A contact “sent a message from another device”, what can i do?</a></li> <li><a href="#e2eeguarantee">What does the green checkmark in a contact profile mean?</a></li>
<li><a href="#are-attachments-pictures-files-audio-etc-end-to-end-encrypted">Are attachments (pictures, files, audio etc.) end-to-end encrypted?</a></li> <li><a href="#are-attachments-pictures-files-audio-etc-end-to-end-encrypted">Are attachments (pictures, files, audio etc.) end-to-end encrypted?</a></li>
<li><a href="#openpgp-secure">A është i siguruar OpenPGP?</a></li> <li><a href="#openpgp-secure">A është i siguruar OpenPGP?</a></li>
<li><a href="#openpgp-alternatives">Did you consider using alternatives to OpenPGP for end-to-end -encryption?</a></li> <li><a href="#openpgp-alternatives">Did you consider using alternatives to OpenPGP for end-to-end-encryption?</a></li>
<li><a href="#a-mund-të-preket-delta-chat-i-nga-efail">A mund të preket Delta Chat-i nga EFAIL?</a></li> <li><a href="#a-mund-të-preket-delta-chat-i-nga-efail">A mund të preket Delta Chat-i nga EFAIL?</a></li>
<li><a href="#tls">Is a message exposed in cleartext if end-to-end encryption is not available?</a></li> <li><a href="#tls">Are messages marked with the mail icon exposed on the Internet?</a></li>
<li><a href="#message-metadata">Si i mbron Delta Chat-i tejtëdhënat në mesazhe?</a></li> <li><a href="#message-metadata">Si i mbron Delta Chat-i tejtëdhënat në mesazhe?</a></li>
<li><a href="#device-seizure">Si të mbrohen tejtëdhënat dhe kontaktet, kur shtien në dorë një pajisje?</a></li> <li><a href="#device-seizure">Si të mbrohen tejtëdhënat dhe kontaktet, kur shtien në dorë një pajisje?</a></li>
<li><a href="#how-can-i-check-encryption-information">How can i check encryption information?</a></li> <li><a href="#sealedsender">Does Delta Chat support “Sealed Sender”?</a></li>
<li><a href="#si-mund-ta-kontrolloj-gjendjen-e-fshehtëzimit-të-mesazheve">Si mund ta kontrolloj gjendjen e fshehtëzimit të mesazheve?</a></li>
<li><a href="#pse-shoh-mesazhe-të-pafshehtëzuar">Pse shoh mesazhe të pafshehtëzuar?</a></li>
<li><a href="#how-can-i-get-an-end-to-end-encrypted-chat-with-a-delta-chat-contact-who-sometimes-uses-webmail-or-another-non-autocrypt-e-mail-app">How can i get an end-to-end encrypted chat with a Delta Chat contact who sometimes uses webmail or another non-Autocrypt e-mail app?</a></li>
<li><a href="#how-can-i-ensure-message-end-to-end-encryption-and-deletion">How can I ensure message end-to-end encryption and deletion?</a></li>
<li><a href="#pfs">Does Delta Chat support Perfect Forward Secrecy?</a></li> <li><a href="#pfs">Does Delta Chat support Perfect Forward Secrecy?</a></li>
<li><a href="#is-end-to-end-encryption-of-delta-chat-as-safe-as-signal">Is end-to-end encryption of Delta Chat as safe as Signal?</a></li> <li><a href="#pqc">Does Delta Chat support Post-Quantum-Cryptography?</a></li>
<li><a href="#how-can-i-manually-check-encryption-information">How can I manually check encryption information?</a></li>
<li><a href="#importkey">A mund të ripërdor kyçin tim ekzistues privat?</a></li> <li><a href="#importkey">A mund të ripërdor kyçin tim ekzistues privat?</a></li>
<li><a href="#security-audits">A është bërë auditim i pavarur i Delta Chat-it për cenueshmëri sigurie?</a></li> <li><a href="#security-audits">A është bërë auditim i pavarur i Delta Chat-it për cenueshmëri sigurie?</a></li>
</ul> </ul>
@ -724,10 +721,10 @@ that achieves “instant delivery” of messages for all chatmail servers
including a potential one <a href="https://delta.chat/chatmail#selfhosted">you might setup yourself without our permission</a>. including a potential one <a href="https://delta.chat/chatmail#selfhosted">you might setup yourself without our permission</a>.
Welcome to the power of the interoperable and massive chatmail and e-mail system :)</p> Welcome to the power of the interoperable and massive chatmail and e-mail system :)</p>
<h2 id="fshehtëzim-dhe-siguri"> <h2 id="e2ee">
Fshehtëzim dhe Siguri <a href="#fshehtëzim-dhe-siguri" class="anchor"></a> Fshehtëzim dhe Siguri <a href="#e2ee" class="anchor"></a>
</h2> </h2>
@ -740,18 +737,26 @@ Welcome to the power of the interoperable and massive chatmail and e-mail system
</h3> </h3>
<p><a href="https://autocrypt.org">Autocrypt</a> is used for automatically <p>Delta Chat uses a <a href="#openpgp-secure">secure subset of the OpenPGP standard</a>
establishing end-to-end encryption with contacts and group chats. to provide automatic end-to-end encryption using these protocols:</p>
Autocrypt uses a limited and <a href="#openpgp-secure">secure subset of the OpenPGP standard</a>.
End-to-End encrypted messages are marked with a padlock
<img style="vertical-align:middle; width:1.2em; margin:1px" src="../lock-icon.png" alt="padlock" />.</p>
<p><a href="https://securejoin.delta.chat/en/latest/new.html">Secure-Join protocols</a> <ul>
are used for establishing chats with guaranteed end-to-end encryption <li>
which protects against network attacks and compromised servers. <p><a href="https://securejoin.delta.chat/en/latest/new.html">Secure-Join</a>
Chats marked with a green checkmark to exchange encryption setup information through QR-code scanning or “invite links”.</p>
<img style="vertical-align:middle; width:1.5em; margin:1px" src="../green-checkmark.png" alt="green checkmark" /> </li>
guarantee end-to-end encrypted messages.</p> <li>
<p><a href="https://autocrypt.org">Autocrypt</a> is used for automatically
establishing end-to-end encryption between contacts and all members of a group chat.</p>
</li>
<li>
<p><a href="https://github.com/chatmail/core/blob/main/spec.md#attaching-a-contact-to-a-message">Sharing a contact to a
chat</a>
enables receivers to use end-to-end encryption with the contact.</p>
</li>
</ul>
<p>Delta Chat does not query, publish or interact with any OpenPGP key servers.</p>
<h3 id="whene2e"> <h3 id="whene2e">
@ -761,28 +766,37 @@ guarantee end-to-end encrypted messages.</p>
</h3> </h3>
<p>All end-to-end encrypted messages carry a padlock:</p> <p>All messages in Delta Chat are <strong>end-to-end encrypted by default</strong>.
Since the Delta Chat Version 2 release series (July 2025)
there are no lock or similar markers on end-to-end encrypted messages, anymore.</p>
<p><img style="width:160px; margin:1px" src="../lock-screenshot.png" alt="padlock in bubble" /></p> <h3 id="can-i-still-receive-or-send-mails-without-end-to-end-encryption">
<p>End-to-end encryption is guaranteed if there is a green checkmark next to the chat title:</p>
<p><img style="width:211px; margin:1px" src="../green-checkmark-screenshot.png" alt="green checkmark in title" /></p>
<h3 id="howtoe2ee">
How can I get guaranteed end-to-end encryption and green checkmarks? <a href="#howtoe2ee" class="anchor"></a> Can i still receive or send mails without end-to-end encryption? <a href="#can-i-still-receive-or-send-mails-without-end-to-end-encryption" class="anchor"></a>
</h3> </h3>
<p>If you have a second communication channel with your chat partner, <p>If you use default <a href="https://chatmail.at/relays">chatmail relays</a>,
like a video chat or a different messenger, it is impossible to receive or send messages without end-to-end encryption.</p>
you can generate an invite link.</p>
<p>If you are together in person, <p>If you instead create a profile using a classic e-mail server,
you can show a QR code to your chat partner.</p> you can send and receive messages without end-to-end encryption.
Such messages lacking end-to-end encryption are marked with an e-mail icon
<img style="vertical-align:middle; width:1.2em; margin:1px" src="../email-icon.png" alt="email" />.</p>
<h3 id="howtoe2ee">
How can I establish a chat with a new contact? <a href="#howtoe2ee" class="anchor"></a>
</h3>
<p>You can send an invite link through another private chat,
show an invitation QR code when next to each other or in a video call,
or click on a “contact” that was shared in a chat.</p>
<ul> <ul>
<li> <li>
@ -797,135 +811,54 @@ on the Delta Chat app main screen.</p>
</li> </li>
</ul> </ul>
<p>Let your chat partner scan the QR image <p>Ask your chat partner to scan the QR image
with their Delta Chat app, with their Delta Chat app,
or click “Copy” or “Share” to create an invite link or click “Copy” or “Share” to create an invite link
and share it with your chat partner.</p> and share it with your chat partner.</p>
<p>Now wait while <a href="https://securejoin.delta.chat/en/latest/new.html#setup-contact-protocol">Secure-Join network messages are exchanged</a> between both devices.</p> <p>Now wait while <a href="https://securejoin.delta.chat/en/latest/new.html#setup-contact-protocol">end-to-end encryption is getting established</a>.</p>
<ul> <ul>
<li> <li>
<p>If both devices are online, <p>If both sides are online, they will soon see a (group or direct) chat
both sides will eventually see a (group or direct) chat with a green checkmark and can start messaging securely.</p>
<img style="vertical-align:middle; width:1.5em; margin:1px" src="../green-checkmark.png" alt="green checkmark" />
next to the title.</p>
</li> </li>
<li> <li>
<p>If one of the devices is offline, the green checkmarks will only <p>If one side is offline or in bad network,
appear later when the device is internet-connected again the ability to chat is delayed until connectivity is restored.</p>
and the Secure-Join network protocol completed.</p>
</li> </li>
</ul> </ul>
<p>Congratulations! <p>Congratulations!
You now will automatically use guaranteed end-to-end encryption You now will automatically use end-to-end encryption
with this contact and both of you can add each other to green-checkmarked groups with this contact.
<img style="vertical-align:middle; width:1.5em; margin:1px" src="../green-checkmark.png" alt="green checkmark" />, If you add each other to chat groups,
thereby automatically spreading guaranteed end-to-end encryption among its members.</p> end-to-end encryption will be established among all members.</p>
<h3 id="e2eeguarantee"> <h3 id="e2eeguarantee">
What does the green checkmark and “guaranteed end-to-end encryption” mean? <a href="#e2eeguarantee" class="anchor"></a> What does the green checkmark in a contact profile mean? <a href="#e2eeguarantee" class="anchor"></a>
</h3> </h3>
<p>Chat titles with green checkmarks <p>A contact profile might show a green checkmark
<img style="vertical-align:middle; width:1.5em; margin:1px" src="../green-checkmark.png" alt="green checkmark" /> <img style="vertical-align:middle; width:1.5em; margin:1px" src="../green-checkmark.png" alt="green checkmark" />
mean that all messages in the chat will be end-to-end encrypted and an “Introduced by” line.
and can not be read or altered by compromised e-mail servers or Internet providers.
Joining green-checkmarked group chats
safely spreads everybody’s encryption information (and green checkmarks)
in a manner that guarantees end-to-end encryption in the group and among members.</p>
<p>Contact profiles with green checkmarks
<img style="vertical-align:middle; width:1.5em; margin:1px" src="../green-checkmark.png" alt="green checkmark" />
mean that messaging a contact is currently guaranteed to be end-to-end encrypted.
Every green-checkmarked contact either did a direct <a href="#howtoe2ee">QR-scan</a> with you Every green-checkmarked contact either did a direct <a href="#howtoe2ee">QR-scan</a> with you
or was introduced by a another green-checkmarked contact. or was introduced by a another green-checkmarked contact.
Introductions happen automatically when adding members to groups. Introductions happen automatically when adding members to groups.
Whoever adds a contact to a green-checkmarked group becomes an introducer Whoever adds a green-checkmarked contact to a group with only green-checkmarked members
to those members who didn’t yet know about the added contact. becomes an introducer.
In a contact profile you can tap on the “Introduced by …” text repeatedly In a contact profile you can tap on the “Introduced by …” text repeatedly
until you get to the one with whom you directly did a <a href="#howtoe2ee">QR-scan</a>.</p> until you get to the one with whom you directly did a <a href="#howtoe2ee">QR-scan</a>.</p>
<p>Note that in a contact profile you may see and tap introducers
but there is no green checkmark in the profile title.
This usually means that the contact <a href="#nocryptanymore">“sent a message from another device”</a>.</p>
<p>For more in-depth discussion of “guaranteed end-to-end encryption” <p>For more in-depth discussion of “guaranteed end-to-end encryption”
please see <a href="https://securejoin.delta.chat/en/latest/new.html">Secure-Join protocols</a> please see <a href="https://securejoin.delta.chat/en/latest/new.html">Secure-Join protocols</a>
and specifically read about “Verified Groups”, the technical term and specifically read about “Verified Groups”, the technical term
of what is called here “green-checkmarked” or “guaranteed end-to-end encrypted” chats.</p> of what is called here “green-checkmarked” or “guaranteed end-to-end encrypted” chats.</p>
<h3 id="nocryptanymore">
A contact “sent a message from another device”, what can i do? <a href="#nocryptanymore" class="anchor"></a>
</h3>
<p>Your chat with a contact lost guaranteed end-to-end encryption.
The green checkmark was removed for this chat and contact when you see this warning.
<strong>If you find the sudden drop of guaranteed end-to-end encryption
surprising for this contact then don’t accept the warning!</strong>
Instead check with your contact through a second channel
like a video call, other messenger or a phone call,
to find out what happened.</p>
<p>If your contact actually caused the drop of guaranteed end-to-end encryption
please see the next paragraphs for common reasons and their mitigations.
Regardless, all other green-checkmarked chats remain guaranteed end-to-end encrypted
even if the contact is a member there.</p>
<p><strong>Your contact is using Delta Chat on a second device (phone or laptop)</strong></p>
<p>If they have another device with a Delta Chat app running,
they should remove the profile from the new device
and add it <a href="#multiclient">as a second device as described here</a>.
As soon as they message you afterwards, the warning will be gone
and guaranteed encryption is established with both devices of your contact.</p>
<p><strong>Your contact reinstalled Delta Chat using their old account login</strong></p>
<p>If they have <a href="#backup">a backup file</a>,
they should remove the profile from the new device
and rather import the backup file to re-create their profile.
As soon as they message you afterwards, the warning will be gone
and guaranteed encryption is re-established for this contact.</p>
<p>If they don’t have a backup file, it’s best to perform a <a href="#howtoe2ee">QR scan</a>
with your chat partner to re-establish guaranteed end-to-end encryption.</p>
<p><strong>Your contact sent a mail through a webmail interface or another e-mail app
and will get back to using Delta Chat soon again.</strong></p>
<p>If you are sure that the contact sometimes uses webmail,
or another mail app lacking end-to-end encryption,
then you may accept the warning.
As soon as your contact uses Delta Chat again,
guaranteed end-to-end encryption will be automatically re-established.</p>
<p><strong>Your contact stopped using Delta Chat entirely</strong></p>
<p>Sometimes remaining in contact is more important than end-to-end encryption.
<a href="#tls">“Transport Layer Encryption” (TLS)</a> may still meaningfully protect
the confidentiality of your messages between your device and the e-mail server.
But without end-to-end encryption you and your contact are trusting your e-mail server
to not read or manipulate your messages, and to not hand them to third parties.</p>
<p>In any case, you can not do much else than accept the warning.
Please also remove the contact from any active green-checkmarked group
which you can find in “Chats in Common” in the Contact profile.
This spares your contact from getting “unreadable” messages.</p>
<p>If the contact removed Delta Chat because of buggy or undesirable behaviour,
please consider posting to our <a href="https://support.delta.chat">support forum</a>
to help us identify and address common problems. Thanks!</p>
<h3 id="are-attachments-pictures-files-audio-etc-end-to-end-encrypted"> <h3 id="are-attachments-pictures-files-audio-etc-end-to-end-encrypted">
@ -950,8 +883,7 @@ and attachment metadata such as filenames.</p>
</h3> </h3>
<p>Yes, Delta Chat uses a secure subset of OpenPGP <p>Yes, Delta Chat uses a secure subset of OpenPGP
and only displays a padlock security indicator on a message requiring the whole message to be properly encrypted and signed.
if the whole message is properly encrypted and signed.
For example, “Detached signatures” are not treated as secure.</p> For example, “Detached signatures” are not treated as secure.</p>
<p>OpenPGP is not insecure by itself. <p>OpenPGP is not insecure by itself.
@ -972,7 +904,7 @@ which was thankfully adopted in summer 2023.</p>
<h3 id="openpgp-alternatives"> <h3 id="openpgp-alternatives">
Did you consider using alternatives to OpenPGP for end-to-end -encryption? <a href="#openpgp-alternatives" class="anchor"></a> Did you consider using alternatives to OpenPGP for end-to-end-encryption? <a href="#openpgp-alternatives" class="anchor"></a>
</h3> </h3>
@ -1015,17 +947,15 @@ as defined by the Autocrypt Level 1 specification.</p>
<h3 id="tls"> <h3 id="tls">
Is a message exposed in cleartext if end-to-end encryption is not available? <a href="#tls" class="anchor"></a> Are messages marked with the mail icon exposed on the Internet? <a href="#tls" class="anchor"></a>
</h3> </h3>
<p>Even if your messages are not guaranteed to be end-to-end encrypted, <p>If you are sending or receiving e-mail messages without end-to-end encryption (using a classic e-mail server),
they are still protected from Internet providers like cell or cable companies. they are still protected from cell or cable companies who can not read or modify your e-mail messages.
However, your and your recipient’s e-mail providers But both your and your recipient’s e-mail providers
may read, analyze or even modify your messages, may read, analyze or modify your messages, including any attachments.</p>
including any attachments,
if they are not end-to-end encrypted.</p>
<p>Delta Chat by default uses strict <p>Delta Chat by default uses strict
<a href="https://en.wikipedia.org/wiki/Transport_Layer_Security">TLS encryption</a> <a href="https://en.wikipedia.org/wiki/Transport_Layer_Security">TLS encryption</a>
@ -1038,10 +968,6 @@ then transport encryption will be enforced between e-mail providers
in which case Delta Chat communications will never be exposed in cleartext to the Internet in which case Delta Chat communications will never be exposed in cleartext to the Internet
even if the message was not end-to-end encrypted.</p> even if the message was not end-to-end encrypted.</p>
<p>Note that <a href="#howtoe2ee">maintaining guaranteed end-to-end encryption</a> on top of TLS encryption
provides pervasive safety between your and the recipient’s devices.
Not even your e-mail or Internet provider will be able to read or modify your messages.</p>
<h3 id="message-metadata"> <h3 id="message-metadata">
@ -1050,25 +976,25 @@ Not even your e-mail or Internet provider will be able to read or modify your me
</h3> </h3>
<p>Delta Chat protects most message metadata by putting the following information <p>Unlike most other messengers,
into the end-to-end encrypted part of messages:</p> Delta Chat apps do not store any metadata about contacts or groups on servers, also not in encrypted form.
Instead, all group metadata is end-to-end encrypted and stored on end-user devices, only.</p>
<p>E-mail Servers can therefore only see</p>
<ul> <ul>
<li>Rresht subjekti</li> <li>
<li>Avatar dhe emër grupi</li> <p>the message date,</p>
<li>Kërkesa MDN (dëftesë leximi) (<code class="language-plaintext highlighter-rouge">Chat-Disposition-Notification-To</code>)</li> </li>
<li>Afatmatës mesazhesh që zhduken (<code class="language-plaintext highlighter-rouge">Ephemeral-Timer</code>)</li> <li>
<li><code class="language-plaintext highlighter-rouge">Chat-Group-Member-Removed</code>, <code class="language-plaintext highlighter-rouge">Chat-Group-Member-Added</code></li> <p>sender and receiver addresses</p>
<li>Krye <code class="language-plaintext highlighter-rouge">Secure-Join</code> që përmban urdhra për pjesëmarrje të siguruar</li> </li>
<li>Njoftim mbi aktivizim tregimi vendndodhjeje</li> <li>
<li>URL dhome WebRTC</li> <p>and message size.</p>
</li>
</ul> </ul>
<p>E-Mail servers do not get access to this protected metadata <p>All other message, contact and group metadata resides in the end-to-end encrypted part of messages.</p>
but they do see the message date as well as the message size,
and, more importantly, the sender and receiver addresses.
E-mail servers need receiver addresses to route and
deliver messages to recipient’s devices.</p>
<h3 id="device-seizure"> <h3 id="device-seizure">
@ -1080,96 +1006,34 @@ deliver messages to recipient’s devices.</p>
<p>Both for protecting against metadata-collecting e-mail servers <p>Both for protecting against metadata-collecting e-mail servers
as well as against the threat of device seizure as well as against the threat of device seizure
we recommend to use a <a href="https://delta.chat/chatmail">chatmail server</a> we recommend to use a <a href="https://chatmail.at/relays">chatmail relay</a>
to create pseudonymous temporary profiles through QR-code scans. to create chat profiles using random e-mail addresses for transport.
Note that Delta Chat apps on all platforms support multiple profiles Note that Delta Chat apps on all platforms support multiple profiles
so you can easily use situation-specific profiles next to your “main” profile so you can easily use situation-specific profiles next to your “main” profile
with the knowledge that all their data, along with all metadata, will be deleted. with the knowledge that all their data, along with all metadata, will be deleted.
Moreover, if a device is seized then contacts using temporary profiles Moreover, if a device is seized then chat contacts using short-lived profiles
can not be identified easily, as compared to messengers which reveal can not be identified easily.</p>
phone numbers in chat groups which in turn are often associated with legal identities.</p>
<h3 id="how-can-i-check-encryption-information"> <h3 id="sealedsender">
How can i check encryption information? <a href="#how-can-i-check-encryption-information" class="anchor"></a> Does Delta Chat support “Sealed Sender”? <a href="#sealedsender" class="anchor"></a>
</h3> </h3>
<p>You may check the end-to-end encryption status manually in the “Encryption” dialog <p>No, not yet.</p>
(user profile on Android/iOS or right-click a user’s chat-list item on desktop).
Delta Chat shows two fingerprints there.
If the same fingerprints appear on your own and your contact’s device,
the connection is safe.</p>
<h3 id="si-mund-ta-kontrolloj-gjendjen-e-fshehtëzimit-të-mesazheve"> <p>The Signal messenger introduced <a href="https://signal.org/blog/sealed-sender/">“Sealed Sender” in 2018</a>
to keep their server infrastructure ignorant of who is sending a message to a set of recipients.
It is particularly important because the Signal server knows the mobile number of each account,
which is usually associated with a passport identity.</p>
<p>Even if <a href="https://chatmail.at/relays">chatmail relays</a>
Si mund ta kontrolloj gjendjen e fshehtëzimit të mesazheve? <a href="#si-mund-ta-kontrolloj-gjendjen-e-fshehtëzimit-të-mesazheve" class="anchor"></a> do not ask for any private data (including no phone numbers),
it might still be worthwhile to protect relational metadata between addresses.
We don’t foresee bigger problems in using random throw-away e-mail addresses for sealed sending
</h3> but an implementation has not been agreed as a priority yet.</p>
<p>A little <strong>padlock</strong> in a message bubble denotes
that the message was properly end-to-end encrypted from the given sender.
If there is <strong>no padlock</strong>, the message was not properly end-to-end encrypted
most likely because the sender uses an app or webmail interface
without support for end-to-end–encryption.</p>
<h3 id="pse-shoh-mesazhe-të-pafshehtëzuar">
Pse shoh mesazhe të pafshehtëzuar? <a href="#pse-shoh-mesazhe-të-pafshehtëzuar" class="anchor"></a>
</h3>
<p>If a contact uses a non-Autocrypt e-mail app,
all messages involving this contact (in a group or 1:1 chat)
will not be end-to-end encrypted, and thus not show a “padlock” with messages.
Note that even if your contacts use Delta Chat on their account,
they might also use a non-Autocrypt e-mail app on that account
which then may cause intermittently unencrypted messages.
Replying unencrypted to unencrypted messages is mandated by Autocrypt
to prevent unreadable messages on the side of your contacts
and their non-Autocrypt e-mail app.</p>
<h3 id="how-can-i-get-an-end-to-end-encrypted-chat-with-a-delta-chat-contact-who-sometimes-uses-webmail-or-another-non-autocrypt-e-mail-app">
How can i get an end-to-end encrypted chat with a Delta Chat contact who sometimes uses webmail or another non-Autocrypt e-mail app? <a href="#how-can-i-get-an-end-to-end-encrypted-chat-with-a-delta-chat-contact-who-sometimes-uses-webmail-or-another-non-autocrypt-e-mail-app" class="anchor"></a>
</h3>
<p>If you need a safely end-to-end encrypted chat with a contact
who is using their e-mail account both with Delta Chat and non-Autocrypt apps (e.g. webmail),
it’s best to setup <a href="#howtoe2ee">guaranteed end-to-end encryption with them</a>
and then create a guaranteed end-to-end encrypted group chat with you two as members.
In this group chat all messages will be end-to-end encrypted
even if the direct chat between you two has a
<a href="#nocryptanymore">“… sent a message from another device”</a> warning.</p>
<h3 id="how-can-i-ensure-message-end-to-end-encryption-and-deletion">
How can I ensure message end-to-end encryption and deletion? <a href="#how-can-i-ensure-message-end-to-end-encryption-and-deletion" class="anchor"></a>
</h3>
<p>The best way to ensure every message is end-to-end encrypted,
and metadata deleted as quickly as possible
is <a href="#howtoe2ee">using chats with guaranteed end-to-end encryption</a>
and turning on <a href="#ephemeralmsgs">disappearing messages</a>.</p>
<p>Guaranteed end-to-end encrypted chats protect against <a href="https://en.wikipedia.org/wiki/Man-in-the-middle_attack">MITM attacks</a>
and turning on disappearing messages deletes the messages
on the server after a user-configured time.</p>
<p>Nëse s’ju duhet te shërbyesi një kopje jetëgjatë e mesazheve tuaj,
mund edhe të aktivizoni <a href="#delold">“fshiji automatikisht nga shërbyesi mesazhe”</a>.</p>
<h3 id="pfs"> <h3 id="pfs">
@ -1179,45 +1043,52 @@ mund edhe të aktivizoni <a href="#delold">“fshiji automatikisht nga shërbyes
</h3> </h3>
<p>No, Delta Chat doesn’t support Perfect Forward Secrecy (PFS). <p>No, not yet.</p>
This means that if your Delta Chat private decryption key is leaked,
<p>Delta Chat today doesn’t support Perfect Forward Secrecy (PFS).
This means that if your private decryption key is leaked,
and someone has collected your prior in-transit messages, and someone has collected your prior in-transit messages,
they will be able to decrypt and read them using the leaked decryption key.</p> they will be able to decrypt and read them using the leaked decryption key.
Note that Forward Secrecy only increases security if you delete messages.
Otherwise, someone obtaining your decryption keys
is typically also able to get all your non-deleted messages
and doesn’t even need to decrypt any previously collected messages.</p>
<p>Note, however, that if anyone obtains to your decryption keys, <p>We designed a Forward Secrecy approach that withstood
they will typically also be able to obtain your messages, initial examination from some cryptographers and implementation experts
irrespective if Perfect Forward Secrecy is in place or not. but is pending a more formal write up
The typical real-world situation for leaked decryption keys is device seizure to ascertain it reliably works in federated messaging and with multi-device usage,
which we discuss in our answer <a href="#device-seizure">on metadata and device seizure</a>.</p> before it could be implemented in <a href="https://github.com/chatmail/core">chatmail core</a>,
which would make it available in all <a href="https://chatmail.at/clients">chatmail clients</a>.</p>
<p>It is possible that Delta Chat evolves to support Perfect Forward Secrecy, <h3 id="pqc">
because OpenPGP is just a container for encrypted messages
but encryption key management (and thus key rotation or key “ratcheting”)
could be organized in flexible ways.
See <a href="https://gitlab.com/sequoia-pgp/openpgp-dr">Seqouia’s PFS prototype</a>
for existing experiments in the OpenPGP implementor community.</p>
<h3 id="is-end-to-end-encryption-of-delta-chat-as-safe-as-signal">
Is end-to-end encryption of Delta Chat as safe as Signal? <a href="#is-end-to-end-encryption-of-delta-chat-as-safe-as-signal" class="anchor"></a> Does Delta Chat support Post-Quantum-Cryptography? <a href="#pqc" class="anchor"></a>
</h3> </h3>
<p>It depends on what is important to you. <p>No, not yet.</p>
Delta Chat <a href="#pfs">does not support PFS</a> like Signal does
but it provides <a href="#e2eeguarantee">guaranteed end-to-end encrypted chats</a>
that are safe against compromised servers or corrupted networks.
Signal and most other PFS-supporting messengers do not provide
a practical scheme for protecting chat groups from network attacks
which are arguably more worrisome
than a potential attacker who seizes your phone and private encryption setup
but somehow not your messages, yet has a full record of all
past encrypted messages.</p>
<p>In any case, Delta Chat’s end-to-end encryption uses a <a href="#openpgp-secure">secure subset of OpenPGP</a> <p>Delta Chat uses the Rust OpenPGP library <a href="https://github.com/rpgp/rpgp">rPGP</a>
which has been <a href="https://delta.chat/assets/blog/2019-first-security-review.pdf">independently security-audited</a>.</p> which supports the latest <a href="https://datatracker.ietf.org/doc/draft-ietf-openpgp-pqc/">IETF Post-Quantum-Cryptography OpenPGP draft</a>.
We aim to add PQC support in <a href="https://github.com/chatmail/core">chatmail core</a> after the draft is finalized at the IETF
in collaboration with other OpenPGP implementers.</p>
<h3 id="how-can-i-manually-check-encryption-information">
How can I manually check encryption information? <a href="#how-can-i-manually-check-encryption-information" class="anchor"></a>
</h3>
<p>You may check the end-to-end encryption status manually in the “Encryption” dialog
(user profile on Android/iOS or right-click a user’s chat-list item on desktop).
Delta Chat shows two fingerprints there.
If the same fingerprints appear on your own and your contact’s device,
the connection is safe.</p>
<h3 id="importkey"> <h3 id="importkey">
@ -1252,7 +1123,7 @@ from most recent to older:</p>
<li> <li>
<p>2024 December, an <a href="https://github.com/rpgp/docs/blob/main/audits/NGI%20Core%20rPGP%20penetration%20test%20report%202024%201.0.pdf">NLNET-commissioned Evaluation of <p>2024 December, an <a href="https://github.com/rpgp/docs/blob/main/audits/NGI%20Core%20rPGP%20penetration%20test%20report%202024%201.0.pdf">NLNET-commissioned Evaluation of
rPGP</a> by <a href="https://www.radicallyopensecurity.com/">Radically Open Security</a> took place. rPGP</a> by <a href="https://www.radicallyopensecurity.com/">Radically Open Security</a> took place.
rPGP serves as the end-to-end encyption <a href="https://openpgp.org">OpenPGP</a> engine of Delta Chat. rPGP serves as the end-to-end encryption <a href="https://openpgp.org">OpenPGP</a> engine of Delta Chat.
Two advisories were released related to the findings of this audit:</p> Two advisories were released related to the findings of this audit:</p>
<ul> <ul>
@ -1645,6 +1516,11 @@ DeltaChat. Zakonisht kjo do të bëhej nga aplikacioni Delta Chat.</p>
</h3> </h3>
<p>Note:
Changing email addresses is temporarily disabled
because of ongoing changes to the DeltaChat core.
It should be available again in a few months.</p>
<ol> <ol>
<li> <li>
<p>Change your address in “Settings → Advanced → Password and Account” and <p>Change your address in “Settings → Advanced → Password and Account” and

309
src/main/assets/help/uk/help.html
View file

@ -36,27 +36,24 @@
<li><a href="#чому-delta-chat-інтегрується-з-централізованими-пропрієтарними-push-сервісами-applegoogle">Чому Delta Chat інтегрується з централізованими пропрієтарними push-сервісами Apple/Google?</a></li> <li><a href="#чому-delta-chat-інтегрується-з-централізованими-пропрієтарними-push-сервісами-applegoogle">Чому Delta Chat інтегрується з централізованими пропрієтарними push-сервісами Apple/Google?</a></li>
</ul> </ul>
</li> </li>
<li><a href="#шифрування-та-безпека">Шифрування та безпека</a> <li><a href="#e2ee">Шифрування та безпека</a>
<ul> <ul>
<li><a href="#які-стандарти-використовуються-для-наскрізного-шифрування">Які стандарти використовуються для наскрізного шифрування?</a></li> <li><a href="#які-стандарти-використовуються-для-наскрізного-шифрування">Які стандарти використовуються для наскрізного шифрування?</a></li>
<li><a href="#whene2e">Як дізнатися, чи повідомлення зашифровано наскрізним шифруванням?</a></li> <li><a href="#whene2e">Як дізнатися, чи повідомлення зашифровано наскрізним шифруванням?</a></li>
<li><a href="#howtoe2ee">Як отримати гарантоване наскрізне шифрування та зелені галочки?</a></li> <li><a href="#can-i-still-receive-or-send-mails-without-end-to-end-encryption">Can i still receive or send mails without end-to-end encryption?</a></li>
<li><a href="#e2eeguarantee">Що означає зелена галочка і “гарантоване наскрізне шифрування”?</a></li> <li><a href="#howtoe2ee">How can I establish a chat with a new contact?</a></li>
<li><a href="#nocryptanymore">Контакт “надіслав повідомлення з іншого пристрою”, що робити?</a></li> <li><a href="#e2eeguarantee">What does the green checkmark in a contact profile mean?</a></li>
<li><a href="#чи-зашифровані-наскрізно-вкладення-зображення-файли-аудіо-тощо">Чи зашифровані наскрізно вкладення (зображення, файли, аудіо тощо)?</a></li> <li><a href="#чи-зашифровані-наскрізно-вкладення-зображення-файли-аудіо-тощо">Чи зашифровані наскрізно вкладення (зображення, файли, аудіо тощо)?</a></li>
<li><a href="#openpgp-secure">Чи безпечний OpenPGP?</a></li> <li><a href="#openpgp-secure">Чи безпечний OpenPGP?</a></li>
<li><a href="#openpgp-alternatives">Чи розглядали ви можливість використання альтернатив OpenPGP для наскрізного шифрування?</a></li> <li><a href="#openpgp-alternatives">Did you consider using alternatives to OpenPGP for end-to-end-encryption?</a></li>
<li><a href="#чи-вразливий-delta-chat-до-efail">Чи вразливий Delta Chat до EFAIL?</a></li> <li><a href="#чи-вразливий-delta-chat-до-efail">Чи вразливий Delta Chat до EFAIL?</a></li>
<li><a href="#tls">Чи буде показано повідомлення відкритим текстом, якщо наскрізне шифрування недоступне?</a></li> <li><a href="#tls">Are messages marked with the mail icon exposed on the Internet?</a></li>
<li><a href="#message-metadata">Як Delta Chat захищає метадані у повідомленнях?</a></li> <li><a href="#message-metadata">Як Delta Chat захищає метадані у повідомленнях?</a></li>
<li><a href="#device-seizure">Як захистити метадані та контакти якщо пристрій вилучено?</a></li> <li><a href="#device-seizure">Як захистити метадані та контакти якщо пристрій вилучено?</a></li>
<li><a href="#як-перевірити-інформацію-про-шифрування">Як перевірити інформацію про шифрування?</a></li> <li><a href="#sealedsender">Does Delta Chat support “Sealed Sender”?</a></li>
<li><a href="#як-перевірити-стан-шифрування-повідомлень">Як перевірити стан шифрування повідомлень?</a></li>
<li><a href="#чому-я-бачу-незашифровані-повідомлення">Чому я бачу незашифровані повідомлення?</a></li>
<li><a href="#як-я-можу-отримати-наскрізно-зашифрований-чат-з-контактом-delta-chat-який-іноді-користується-веб-поштою-або-іншим-додатком-електронної-пошти-що-не-підтримує-autocrypt">Як я можу отримати наскрізно зашифрований чат з контактом Delta Chat, який іноді користується веб-поштою або іншим додатком електронної пошти, що не підтримує Autocrypt?</a></li>
<li><a href="#як-забезпечити-наскрізне-шифрування-та-видалення-повідомлень">Як забезпечити наскрізне шифрування та видалення повідомлень?</a></li>
<li><a href="#pfs">Чи підтримує Delta Chat цілковиту пряму секретність (Perfect Forward Secrecy)?</a></li> <li><a href="#pfs">Чи підтримує Delta Chat цілковиту пряму секретність (Perfect Forward Secrecy)?</a></li>
<li><a href="#чи-є-наскрізне-шифрування-delta-chat-таким-же-безпечним-як-signal">Чи є наскрізне шифрування Delta Chat таким же безпечним, як Signal?</a></li> <li><a href="#pqc">Does Delta Chat support Post-Quantum-Cryptography?</a></li>
<li><a href="#how-can-i-manually-check-encryption-information">How can I manually check encryption information?</a></li>
<li><a href="#importkey">Чи можна повторно використовувати існуючий закритий ключ?</a></li> <li><a href="#importkey">Чи можна повторно використовувати існуючий закритий ключ?</a></li>
<li><a href="#security-audits">Чи проходив Delta Chat незалежний аудит на наявність вразливостей у безпеці?</a></li> <li><a href="#security-audits">Чи проходив Delta Chat незалежний аудит на наявність вразливостей у безпеці?</a></li>
</ul> </ul>
@ -593,10 +590,10 @@ Push-сповіщення автоматично активуються для
<p>Зверніть увагу, що Delta Chat має <a href="#privacy-notifications">невелику систему push-повідомлень, що зберігає конфіденційність</a> яка забезпечує “миттєву доставку” повідомлень на всі chatmail-сервери включаючи потенційний <a href="https://delta.chat/chatmail#selfhosted">який ви можете налаштувати самостійно без нашого дозволу</a>. Ласкаво просимо до потужності сумісної та масової системи чат-пошти та електронної пошти :)</p> <p>Зверніть увагу, що Delta Chat має <a href="#privacy-notifications">невелику систему push-повідомлень, що зберігає конфіденційність</a> яка забезпечує “миттєву доставку” повідомлень на всі chatmail-сервери включаючи потенційний <a href="https://delta.chat/chatmail#selfhosted">який ви можете налаштувати самостійно без нашого дозволу</a>. Ласкаво просимо до потужності сумісної та масової системи чат-пошти та електронної пошти :)</p>
<h2 id="шифрування-та-безпека"> <h2 id="e2ee">
Шифрування та безпека <a href="#шифрування-та-безпека" class="anchor"></a> Шифрування та безпека <a href="#e2ee" class="anchor"></a>
</h2> </h2>
@ -609,10 +606,26 @@ Push-сповіщення автоматично активуються для
</h3> </h3>
<p><a href="https://autocrypt.org">Autocrypt</a> використовується для автоматичного встановлення наскрізного шифрування з контактами та груповими чатами. <p>Delta Chat uses a <a href="#openpgp-secure">secure subset of the OpenPGP standard</a>
Autocrypt використовує обмежену і <a href="#openpgp-secure">безпечну підмножину стандарту OpenPGP</a>. Зашифровані наскрізним шифруванням повідомлення позначаються замком <img style="vertical-align:middle; width:1.2em; margin:1px" src="../lock-icon.png" alt="padlock" />.</p> to provide automatic end-to-end encryption using these protocols:</p>
<p><a href="https://securejoin.delta.chat/en/latest/new.html">Протоколи Secure-Join</a> використовуються для створення чатів з гарантованим наскрізним шифруванням що захищає від мережевих атак і скомпрометованих серверів. Чати, відмічені зеленою галочкою <img style="vertical-align:middle; width:1.5em; margin:1px" src="../green-checkmark.png" alt="green checkmark" /> гарантують наскрізне шифрування повідомлень.</p> <ul>
<li>
<p><a href="https://securejoin.delta.chat/en/latest/new.html">Secure-Join</a>
to exchange encryption setup information through QR-code scanning or “invite links”.</p>
</li>
<li>
<p><a href="https://autocrypt.org">Autocrypt</a> is used for automatically
establishing end-to-end encryption between contacts and all members of a group chat.</p>
</li>
<li>
<p><a href="https://github.com/chatmail/core/blob/main/spec.md#attaching-a-contact-to-a-message">Sharing a contact to a
chat</a>
enables receivers to use end-to-end encryption with the contact.</p>
</li>
</ul>
<p>Delta Chat does not query, publish or interact with any OpenPGP key servers.</p>
<h3 id="whene2e"> <h3 id="whene2e">
@ -622,102 +635,94 @@ Autocrypt використовує обмежену і <a href="#openpgp-secure"
</h3> </h3>
<p>Всі наскрізні зашифровані повідомлення мають навісний замок:</p> <p>All messages in Delta Chat are <strong>end-to-end encrypted by default</strong>.
Since the Delta Chat Version 2 release series (July 2025)
there are no lock or similar markers on end-to-end encrypted messages, anymore.</p>
<p><img style="width:160px; margin:1px" src="../lock-screenshot.png" alt="padlock in bubble" /></p> <h3 id="can-i-still-receive-or-send-mails-without-end-to-end-encryption">
<p>Наскрізне шифрування гарантується, якщо поруч із заголовком чату стоїть зелена галочка:</p>
<p><img style="width:211px; margin:1px" src="../green-checkmark-screenshot.png" alt="green checkmark in title" /></p>
<h3 id="howtoe2ee">
Як отримати гарантоване наскрізне шифрування та зелені галочки? <a href="#howtoe2ee" class="anchor"></a> Can i still receive or send mails without end-to-end encryption? <a href="#can-i-still-receive-or-send-mails-without-end-to-end-encryption" class="anchor"></a>
</h3> </h3>
<p>Якщо у вас є другий канал зв’язку з вашим партнером по чату, наприклад, відеочат або інший месенджер, ви можете згенерувати посилання-запрошення.</p> <p>If you use default <a href="https://chatmail.at/relays">chatmail relays</a>,
it is impossible to receive or send messages without end-to-end encryption.</p>
<p>Якщо ви разом особисто, ви можете показати QR-код своєму співрозмовнику.</p> <p>If you instead create a profile using a classic e-mail server,
you can send and receive messages without end-to-end encryption.
Such messages lacking end-to-end encryption are marked with an e-mail icon
<img style="vertical-align:middle; width:1.2em; margin:1px" src="../email-icon.png" alt="email" />.</p>
<h3 id="howtoe2ee">
How can I establish a chat with a new contact? <a href="#howtoe2ee" class="anchor"></a>
</h3>
<p>You can send an invite link through another private chat,
show an invitation QR code when next to each other or in a video call,
or click on a “contact” that was shared in a chat.</p>
<ul> <ul>
<li> <li>
<p>Для <strong>Запрошення до групи</strong>, торкніться назви групи чату, щоб побачити список її учасників, і виберіть “QR-код запрошення”.</p> <p>Для <strong>Запрошення до групи</strong>, торкніться назви групи чату, щоб побачити список її учасників, і виберіть “QR-код запрошення”.</p>
</li> </li>
<li> <li>
<p>Для <strong>прямих запрошень у чат 1:1</strong>, торкніться іконки QR-коду <img style="vertical-align:middle; width:1.8em; margin:1px" src="../qr-icon.png" /> на головному екрані програми Delta Chat.</p> <p>For <strong>direct 1:1 chat invitations</strong>,
tap the QR Code icon <img style="vertical-align:middle; width:1.8em; margin:1px" src="../qr-icon.png" />
on the Delta Chat app main screen.</p>
</li> </li>
</ul> </ul>
<p>Дозвольте вашому партнеру по чату відсканувати QR-зображення <p>Ask your chat partner to scan the QR image
у своєму додатку Delta Chat, або натисніть “Копіювати” чи “Поділитися”, щоб створити посилання-запрошення і поділитися ним з вашим співрозмовником.</p> with their Delta Chat app,
or click “Copy” or “Share” to create an invite link
and share it with your chat partner.</p>
<p>Тепер зачекайте, поки між обома пристроями <a href="https://securejoin.delta.chat/en/latest/new.html#setup-contact-protocol">відбудеться обмін мережевими повідомленнями Secure-Join</a>.</p> <p>Now wait while <a href="https://securejoin.delta.chat/en/latest/new.html#setup-contact-protocol">end-to-end encryption is getting established</a>.</p>
<ul> <ul>
<li> <li>
<p>Якщо обидва пристрої онлайн, обидві сторони зрештою побачать (груповий або прямий) чат із зеленою галочкою <img style="vertical-align:middle; width:1.5em; margin:1px" src="../green-checkmark.png" alt="green checkmark" /> поруч із заголовком.</p> <p>If both sides are online, they will soon see a (group or direct) chat
and can start messaging securely.</p>
</li> </li>
<li> <li>
<p>Якщо один з пристроїв не в мережі, зелені галочки з’являться пізніше, коли пристрій знову буде підключено до Інтернету а мережевий протокол Secure-Join буде завершено.</p> <p>If one side is offline or in bad network,
the ability to chat is delayed until connectivity is restored.</p>
</li> </li>
</ul> </ul>
<p>Вітаємо! Тепер ви автоматично використовуватимете гарантоване наскрізне шифрування з цим контактом, і ви обидва можете додавати один одного в групи, позначені зеленою галочкою <img style="vertical-align:middle; width:1.5em; margin:1px" src="../green-checkmark.png" alt="green checkmark" />, таким чином автоматично поширюючи гарантоване наскрізне шифрування серед її членів.</p> <p>Congratulations!
You now will automatically use end-to-end encryption
with this contact.
If you add each other to chat groups,
end-to-end encryption will be established among all members.</p>
<h3 id="e2eeguarantee"> <h3 id="e2eeguarantee">
Що означає зелена галочка і “гарантоване наскрізне шифрування”? <a href="#e2eeguarantee" class="anchor"></a> What does the green checkmark in a contact profile mean? <a href="#e2eeguarantee" class="anchor"></a>
</h3> </h3>
<p>Назви чатів із зеленими галочками <img style="vertical-align:middle; width:1.5em; margin:1px" src="../green-checkmark.png" alt="green checkmark" /> означають, що всі повідомлення в чаті будуть наскрізно зашифровані і не можуть бути прочитані або змінені скомпрометованими поштовими серверами або інтернет-провайдерами. <p>A contact profile might show a green checkmark
Приєднання до групових чатів із зеленими галочками безпечно поширює інформацію про шифрування (і зелені галочки) всіх учасників таким чином, що гарантує наскрізне шифрування в групі та між її учасниками.</p> <img style="vertical-align:middle; width:1.5em; margin:1px" src="../green-checkmark.png" alt="green checkmark" />
and an “Introduced by” line.
<p>Профілі контактів із зеленими галочками <img style="vertical-align:middle; width:1.5em; margin:1px" src="../green-checkmark.png" alt="green checkmark" /> означають, що повідомлення контакту наразі гарантовано зашифровані наскрізним шифруванням. Кожен контакт із зеленою галочкою або зробив пряме <a href="#howtoe2ee">QR-сканування</a> з вами або був представлений іншим контактом, позначеним зеленою галочкою. Знайомство відбувається автоматично під час додавання учасників до груп. Той, хто додає контакт до групи, позначеної зеленою галочкою, стає представником для тих учасників, які ще не знали про доданий контакт. У профілі контакту ви можете кілька разів натиснути на текст “Представлений …” поки не потрапите до того, з ким ви безпосередньо зробили <a href="#howtoe2ee">QR-сканування</a>.</p> Every green-checkmarked contact either did a direct <a href="#howtoe2ee">QR-scan</a> with you
or was introduced by a another green-checkmarked contact.
<p>Зверніть увагу, що в профілі контакту ви можете бачити і натискати рекомендувачів але в заголовку профілю немає зеленої галочки. Зазвичай це означає, що контакт <a href="#nocryptanymore">“надіслав повідомлення з іншого пристрою”</a>.</p> Introductions happen automatically when adding members to groups.
Whoever adds a green-checkmarked contact to a group with only green-checkmarked members
becomes an introducer.
In a contact profile you can tap on the “Introduced by …” text repeatedly
until you get to the one with whom you directly did a <a href="#howtoe2ee">QR-scan</a>.</p>
<p>Для більш детального обговорення “гарантованого наскрізного шифрування” будь ласка, перегляньте <a href="https://securejoin.delta.chat/en/latest/new.html">Протоколи безпечного приєднання</a> і, зокрема, прочитайте про “Перевірені групи”, технічний термін того, що тут називається чатами з “зеленою галочкою” або “гарантованим наскрізним шифруванням”.</p> <p>Для більш детального обговорення “гарантованого наскрізного шифрування” будь ласка, перегляньте <a href="https://securejoin.delta.chat/en/latest/new.html">Протоколи безпечного приєднання</a> і, зокрема, прочитайте про “Перевірені групи”, технічний термін того, що тут називається чатами з “зеленою галочкою” або “гарантованим наскрізним шифруванням”.</p>
<h3 id="nocryptanymore">
Контакт “надіслав повідомлення з іншого пристрою”, що робити? <a href="#nocryptanymore" class="anchor"></a>
</h3>
<p>Ваш чат з контактом втратив гарантоване наскрізне шифрування. Зелену галочку було знято для цього чату та контакту, коли ви побачили це попередження. **Якщо ви вважаєте раптове зникнення гарантованого наскрізного шифрування несподіваним для цього контакту, не приймайте попередження! Замість цього зв’яжіться з контактом через другий канал наприклад, відеодзвінок, інший месенджер або телефонний дзвінок, щоб з’ясувати, що сталося.</p>
<p>Якщо ваш контакт дійсно спричинив втрату гарантованого наскрізного шифрування будь ласка, зверніться до наступних параграфів, щоб дізнатися про типові причини та способи їх усунення. Незважаючи на це, всі інші чати, позначені зеленою галочкою, залишаються гарантовано зашифрованими з кінця в кінець навіть якщо контакт є їхнім учасником.</p>
<p><strong>Ваш контакт використовує Delta Chat на другому пристрої (телефоні або ноутбуці)</strong>.</p>
<p>Якщо у них є інший пристрій із запущеним додатком Delta Chat, вони повинні видалити профіль з нового пристрою і додати його <a href="#multiclient">як другий пристрій, як описано тут</a>. Як тільки вони напишуть вам повідомлення, попередження зникне і гарантоване шифрування буде встановлено на обох пристроях вашого контакту.</p>
<p><strong>Ваш контакт перевстановив Delta Chat, використовуючи свій старий логін</strong></p>
<p>Якщо у них є <a href="#backup">файл резервної копії</a>, вони повинні видалити профіль з нового пристрою і, замість цього, імпортувати файл резервної копії для відновлення свого профілю. Як тільки вони напишуть вам повідомлення, попередження зникне і гарантоване шифрування буде відновлено для цього контакту.</p>
<p>Якщо у них немає резервної копії файлу, найкраще виконати <a href="#howtoe2ee">QR-сканування</a> з вашим співрозмовником, щоб відновити гарантоване кінцеве шифрування.</p>
<p><strong>Ваш контакт надіслав листа через веб-інтерфейс або іншу поштову програму і незабаром повернеться до використання Delta Chat.</strong></p>
<p>Якщо ви впевнені, що контакт іноді користується веб-поштою, або іншу поштову програму без наскрізного шифрування, ви можете прийняти попередження. Як тільки ваш контакт знову скористається Delta Chat, гарантоване наскрізне шифрування буде автоматично відновлено.</p>
<p><strong>Ваш контакт повністю припинив користуватися Delta Chat</strong>.</p>
<p>Іноді залишатися на зв’язку важливіше, ніж наскрізне шифрування. <a href="#tls">“Шифрування на транспортному рівні” (TLS)</a> все ще може ефективно захищати конфіденційність ваших повідомлень між вашим пристроєм і сервером електронної пошти. Але без наскрізного шифрування ви та ваш контакт довіряєте серверу електронної пошти не читати і не маніпулювати вашими повідомленнями, а також не передавати їх третім особам.</p>
<p>У будь-якому випадку, ви не можете зробити нічого іншого, окрім як прийняти попередження. Будь ласка, також видаліть контакт з будь-якої активної групи, позначеної зеленою галочкою які ви можете знайти в розділі “Загальні чати” в профілі контакту. Це позбавить ваш контакт від отримання “нечитабельних” повідомлень.</p>
<p>Якщо контакт видалив Delta Chat через помилки або небажану поведінку, будь ласка, розгляньте можливість написати повідомлення на нашому <a href="https://support.delta.chat">форумі підтримки</a> щоб допомогти нам виявити та вирішити загальні проблеми. Дякуємо!</p>
<h3 id="чи-зашифровані-наскрізно-вкладення-зображення-файли-аудіо-тощо"> <h3 id="чи-зашифровані-наскрізно-вкладення-зображення-файли-аудіо-тощо">
@ -738,7 +743,9 @@ Autocrypt використовує обмежену і <a href="#openpgp-secure"
</h3> </h3>
<p>Так, Delta Chat використовує безпечну підмножину OpenPGP і відображає індикатор безпеки у вигляді замка в повідомленні лише тоді, коли все повідомлення належним чином зашифровано і підписано. Наприклад, “Відокремлені підписи” не вважаються безпечними.</p> <p>Yes, Delta Chat uses a secure subset of OpenPGP
requiring the whole message to be properly encrypted and signed.
For example, “Detached signatures” are not treated as secure.</p>
<p>OpenPGP сам по собі не є небезпечним. Більшість публічно обговорюваних проблем безпеки OpenPGP насправді виникають через недостатню зручність використання або погану реалізацію інструментів чи програм (або обох). <p>OpenPGP сам по собі не є небезпечним. Більшість публічно обговорюваних проблем безпеки OpenPGP насправді виникають через недостатню зручність використання або погану реалізацію інструментів чи програм (або обох).
Особливо важливо розрізняти OpenPGP, стандарт шифрування IETF, і GnuPG (GPG), інструмент командного рядка, що реалізує OpenPGP. Особливо важливо розрізняти OpenPGP, стандарт шифрування IETF, і GnuPG (GPG), інструмент командного рядка, що реалізує OpenPGP.
@ -750,7 +757,7 @@ Delta Chat скоріше використовує реалізацію OpenPGP
<h3 id="openpgp-alternatives"> <h3 id="openpgp-alternatives">
Чи розглядали ви можливість використання альтернатив OpenPGP для наскрізного шифрування? <a href="#openpgp-alternatives" class="anchor"></a> Did you consider using alternatives to OpenPGP for end-to-end-encryption? <a href="#openpgp-alternatives" class="anchor"></a>
</h3> </h3>
@ -774,17 +781,18 @@ Delta Chat скоріше використовує реалізацію OpenPGP
<h3 id="tls"> <h3 id="tls">
Чи буде показано повідомлення відкритим текстом, якщо наскрізне шифрування недоступне? <a href="#tls" class="anchor"></a> Are messages marked with the mail icon exposed on the Internet? <a href="#tls" class="anchor"></a>
</h3> </h3>
<p>Навіть якщо ваші повідомлення не гарантовано зашифровані наскрізним шифруванням, вони все одно захищені від інтернет-провайдерів, таких як мобільні або кабельні компанії. Однак, ваші провайдери та провайдери електронної пошти одержувача можуть читати, аналізувати або навіть змінювати ваші повідомлення, включаючи будь-які вкладення, якщо вони не зашифровані наскрізним шифруванням.</p> <p>If you are sending or receiving e-mail messages without end-to-end encryption (using a classic e-mail server),
they are still protected from cell or cable companies who can not read or modify your e-mail messages.
But both your and your recipient’s e-mail providers
may read, analyze or modify your messages, including any attachments.</p>
<p>За замовчуванням Delta Chat використовує суворе <a href="https://en.wikipedia.org/wiki/Transport_Layer_Security">TLS-шифрування</a> яке захищає з’єднання між вашим пристроєм і провайдером електронної пошти. Вся робота з TLS-шифруванням Delta Chat пройшла незалежний <a href="#security-audits">аудит безпеки</a>. Крім того, з’єднання між вашим провайдером та провайдером електронної пошти одержувача зазвичай також шифрується при передачі даних. Якщо задіяні поштові сервери підтримують <a href="https://datatracker.ietf.org/doc/html/rfc8461">MTA-STS</a> то між провайдерами електронної пошти буде застосовуватися транспортне шифрування в цьому випадку повідомлення Delta Chat ніколи не будуть доступні в Інтернеті у вигляді відкритого тексту навіть якщо повідомлення не було наскрізь зашифровано.</p> <p>За замовчуванням Delta Chat використовує суворе <a href="https://en.wikipedia.org/wiki/Transport_Layer_Security">TLS-шифрування</a> яке захищає з’єднання між вашим пристроєм і провайдером електронної пошти. Вся робота з TLS-шифруванням Delta Chat пройшла незалежний <a href="#security-audits">аудит безпеки</a>. Крім того, з’єднання між вашим провайдером та провайдером електронної пошти одержувача зазвичай також шифрується при передачі даних. Якщо задіяні поштові сервери підтримують <a href="https://datatracker.ietf.org/doc/html/rfc8461">MTA-STS</a> то між провайдерами електронної пошти буде застосовуватися транспортне шифрування в цьому випадку повідомлення Delta Chat ніколи не будуть доступні в Інтернеті у вигляді відкритого тексту навіть якщо повідомлення не було наскрізь зашифровано.</p>
<p>Зверніть увагу, що <a href="#howtoe2ee">підтримка гарантованого наскрізного шифрування</a>, на додаток до шифрування TLS, забезпечує повну безпеку між вашим пристроєм і пристроєм одержувача. Навіть ваш провайдер електронної пошти або інтернет-провайдер не зможуть прочитати або змінити ваші повідомлення.</p>
<h3 id="message-metadata"> <h3 id="message-metadata">
@ -793,20 +801,25 @@ Delta Chat скоріше використовує реалізацію OpenPGP
</h3> </h3>
<p>Delta Chat захищає більшість метаданих повідомлень, поміщаючи наступну інформацію в наскрізно зашифровану частину повідомлень:</p> <p>Unlike most other messengers,
Delta Chat apps do not store any metadata about contacts or groups on servers, also not in encrypted form.
Instead, all group metadata is end-to-end encrypted and stored on end-user devices, only.</p>
<p>E-mail Servers can therefore only see</p>
<ul> <ul>
<li>Тема повідомлення</li> <li>
<li>Аватар та назва групи</li> <p>the message date,</p>
<li>Запити MDN (підтвердження прочитання) (<code class="language-plaintext highlighter-rouge">Chat-Disposition-Notification-To</code>)</li> </li>
<li>Таймер зникнення повідомлень (<code class="language-plaintext highlighter-rouge">Ephemeral-Timer</code>)</li> <li>
<li><code class="language-plaintext highlighter-rouge">Chat-Group-Member-Removed</code>, <code class="language-plaintext highlighter-rouge">Chat-Group-Member-Added</code>, <code class="language-plaintext highlighter-rouge">Chat-Group-Member-Added</code>, <code class="language-plaintext highlighter-rouge">Chat-Group-Member-Removed-Member-Added</code>.</li> <p>sender and receiver addresses</p>
<li>Заголовок <code class="language-plaintext highlighter-rouge">Secure-Join</code>, що містить команди безпечного приєднання</li> </li>
<li>Сповіщення про увімкнення потокового передавання місцезнаходження</li> <li>
<li>URL-адреса кімнати WebRTC</li> <p>and message size.</p>
</li>
</ul> </ul>
<p>Поштові сервери не мають доступу до цих захищених метаданих але вони бачать дату і розмір повідомлення, і, що важливіше, адреси відправника та отримувача. Поштовим серверам потрібні адреси одержувачів, щоб маршрутизувати і доставляти повідомлення на пристрої одержувача.</p> <p>All other message, contact and group metadata resides in the end-to-end encrypted part of messages.</p>
<h3 id="device-seizure"> <h3 id="device-seizure">
@ -816,62 +829,36 @@ Delta Chat скоріше використовує реалізацію OpenPGP
</h3> </h3>
<p>Як для захисту від поштових серверів, що збирають метадані а також для захисту від загрози вилучення пристрою ми рекомендуємо використовувати <a href="https://delta.chat/chatmail">chatmail-сервер</a> для створення псевдонімних тимчасових профілів за допомогою сканування QR-коду. Зверніть увагу, що додатки Delta Chat на всіх платформах підтримують кілька профілів тому ви можете легко використовувати ситуативні профілі поруч з вашим “основним” профілем знаючи, що всі їхні дані, разом з усіма метаданими, будуть видалені. Більше того, якщо пристрій вилучено, то контакти, які використовують тимчасові профілі не можна буде легко ідентифікувати, на відміну від месенджерів, які розкривають номери телефонів у групах чату, які, в свою чергу, часто пов’язані з юридичними особами.</p> <p>Both for protecting against metadata-collecting e-mail servers
as well as against the threat of device seizure
we recommend to use a <a href="https://chatmail.at/relays">chatmail relay</a>
to create chat profiles using random e-mail addresses for transport.
Note that Delta Chat apps on all platforms support multiple profiles
so you can easily use situation-specific profiles next to your “main” profile
with the knowledge that all their data, along with all metadata, will be deleted.
Moreover, if a device is seized then chat contacts using short-lived profiles
can not be identified easily.</p>
<h3 id="як-перевірити-інформацію-про-шифрування"> <h3 id="sealedsender">
Як перевірити інформацію про шифрування? <a href="#як-перевірити-інформацію-про-шифрування" class="anchor"></a> Does Delta Chat support “Sealed Sender”? <a href="#sealedsender" class="anchor"></a>
</h3> </h3>
<p>Ви можете перевірити стан наскрізного шифрування вручну в діалоговому вікні “Шифрування” (профіль користувача на Android/iOS або клацніть правою кнопкою миші на елементі списку чату користувача на робочому столі). Delta Chat показує там два відбитки. Якщо на вашому пристрої та пристрої вашого співрозмовника з’являються однакові відбитки, з’єднання безпечне.</p> <p>No, not yet.</p>
<h3 id="як-перевірити-стан-шифрування-повідомлень"> <p>The Signal messenger introduced <a href="https://signal.org/blog/sealed-sender/">“Sealed Sender” in 2018</a>
to keep their server infrastructure ignorant of who is sending a message to a set of recipients.
It is particularly important because the Signal server knows the mobile number of each account,
which is usually associated with a passport identity.</p>
<p>Even if <a href="https://chatmail.at/relays">chatmail relays</a>
Як перевірити стан шифрування повідомлень? <a href="#як-перевірити-стан-шифрування-повідомлень" class="anchor"></a> do not ask for any private data (including no phone numbers),
it might still be worthwhile to protect relational metadata between addresses.
We don’t foresee bigger problems in using random throw-away e-mail addresses for sealed sending
</h3> but an implementation has not been agreed as a priority yet.</p>
<p>Маленький <strong>замок</strong> в бульбашці повідомлення позначає, що повідомлення було належним чином наскрізно зашифроване від відправника. Якщо <strong>немає замка</strong>, повідомлення не було належним чином наскрізно зашифровано, найімовірніше, тому що відправник використовує додаток або інтерфейс веб-пошти без підтримки кінцевого шифрування.</p>
<h3 id="чому-я-бачу-незашифровані-повідомлення">
Чому я бачу незашифровані повідомлення? <a href="#чому-я-бачу-незашифровані-повідомлення" class="anchor"></a>
</h3>
<p>Якщо контакт використовує поштову програму, яка не підтримує Autocrypt всі повідомлення за участю цього контакту (в групі або чаті 1:1) не будуть наскрізно зашифровані, а отже, не показуватимуть “висячого замка” з повідомленнями. Зверніть увагу, що навіть якщо ваші контакти використовують Delta Chat у своєму акаунті, вони також можуть використовувати програму електронної пошти без функції шифрування, що може спричинити періодичні незашифровані повідомлення. Відповідати незашифрованими на незашифровані повідомлення вимагає Autocrypt щоб запобігти отриманню нечитабельних повідомлень на стороні ваших контактів та їхніх поштових програм, які не підтримують Autocrypt.</p>
<h3 id="як-я-можу-отримати-наскрізно-зашифрований-чат-з-контактом-delta-chat-який-іноді-користується-веб-поштою-або-іншим-додатком-електронної-пошти-що-не-підтримує-autocrypt">
Як я можу отримати наскрізно зашифрований чат з контактом Delta Chat, який іноді користується веб-поштою або іншим додатком електронної пошти, що не підтримує Autocrypt? <a href="#як-я-можу-отримати-наскрізно-зашифрований-чат-з-контактом-delta-chat-який-іноді-користується-веб-поштою-або-іншим-додатком-електронної-пошти-що-не-підтримує-autocrypt" class="anchor"></a>
</h3>
<p>Якщо вам потрібен безпечний наскрізно зашифрований чат з контактом який використовує свій акаунт як у Delta Chat, так і в інших додатках (наприклад, веб-пошті), що не підтримують автошифрування, найкраще налаштувати <a href="#howtoe2ee">гарантоване наскрізне шифрування з ними</a>, а потім створити груповий чат з гарантованим наскрізним шифруванням, учасниками якого будете ви двоє. У цьому груповому чаті всі повідомлення будуть наскрізно зашифровані навіть якщо в прямому чаті між вами буде <a href="#nocryptanymore">“… надіслано повідомлення з іншого пристрою”</a>.</p>
<h3 id="як-забезпечити-наскрізне-шифрування-та-видалення-повідомлень">
Як забезпечити наскрізне шифрування та видалення повідомлень? <a href="#як-забезпечити-наскрізне-шифрування-та-видалення-повідомлень" class="anchor"></a>
</h3>
<p>Найкращий спосіб забезпечити наскрізне шифрування кожного повідомлення, а метадані видалялися якнайшвидше, це <a href="#howtoe2ee">використання чатів з гарантованим наскрізним шифруванням</a>
та увімкнення <a href="#ephemeralmsgs">зникаючих повідомлень</a>.</p>
<p>Гарантований наскрізно шифрований чат захищає від <a href="https://en.wikipedia.org/wiki/Man-in-the-middle_attack">MITM-атак</a>, а увімкнення функції зникнення повідомлень видаляє повідомлення на сервері через певний час, налаштований користувачем.</p>
<p>Якщо вам не потрібне більш довготривале зберігання копій ваших повідомлень на сервері, ви також можете увімкнути <a href="#delold">“автоматично видаляти повідомлення з сервера”</a>.</p>
<h3 id="pfs"> <h3 id="pfs">
@ -881,23 +868,48 @@ Delta Chat скоріше використовує реалізацію OpenPGP
</h3> </h3>
<p>Ні, Delta Chat не підтримує ідеальну пряму секретність (PFS). Це означає, що якщо ваш приватний ключ дешифрування Delta Chat витік, і хтось зібрав ваші попередні транзитні повідомлення, він зможе розшифрувати і прочитати їх за допомогою витоку ключа розшифрування.</p> <p>No, not yet.</p>
<p>Зауважте, однак, що якщо хтось отримає ваші ключі розшифрування, вони, як правило, також зможуть отримати ваші повідомлення, незалежно від того, чи працює Perfect Forward Secrecy чи ні. Типовою реальною ситуацією для витоку ключів дешифрування є вилучення пристрою яку ми обговорюємо в нашій відповіді <a href="#device-seizure">про метадані та вилучення пристрою</a>.</p> <p>Delta Chat today doesn’t support Perfect Forward Secrecy (PFS).
This means that if your private decryption key is leaked,
and someone has collected your prior in-transit messages,
they will be able to decrypt and read them using the leaked decryption key.
Note that Forward Secrecy only increases security if you delete messages.
Otherwise, someone obtaining your decryption keys
is typically also able to get all your non-deleted messages
and doesn’t even need to decrypt any previously collected messages.</p>
<p>Можливо, що Delta Chat розвивається для підтримки Perfect Forward Secrecy, тому що OpenPGP - це лише контейнер для зашифрованих повідомлень, але керування ключами шифрування (і, відповідно, ротація ключів або “храповик” ключів) може бути організоване у гнучкий спосіб. Дивіться <a href="https://gitlab.com/sequoia-pgp/openpgp-dr">Прототип PFS від Seqouia</a> щодо існуючих експериментів у спільноті реалізаторів OpenPGP.</p> <p>We designed a Forward Secrecy approach that withstood
initial examination from some cryptographers and implementation experts
but is pending a more formal write up
to ascertain it reliably works in federated messaging and with multi-device usage,
before it could be implemented in <a href="https://github.com/chatmail/core">chatmail core</a>,
which would make it available in all <a href="https://chatmail.at/clients">chatmail clients</a>.</p>
<h3 id="чи-є-наскрізне-шифрування-delta-chat-таким-же-безпечним-як-signal"> <h3 id="pqc">
Чи є наскрізне шифрування Delta Chat таким же безпечним, як Signal? <a href="#чи-є-наскрізне-шифрування-delta-chat-таким-же-безпечним-як-signal" class="anchor"></a> Does Delta Chat support Post-Quantum-Cryptography? <a href="#pqc" class="anchor"></a>
</h3> </h3>
<p>Це залежить від того, що для вас важливо. Delta Chat <a href="#pfs">не підтримує PFS</a>, як Signal але він забезпечує <a href="#e2eeguarantee">гарантовано наскрізні зашифровані чати</a> які захищені від скомпрометованих серверів або пошкоджених мереж. Signal та більшість інших месенджерів, що підтримують PFS, не надають практичної схеми захисту чат-груп від мережевих атак які, можливо, викликають більше занепокоєння ніж потенційний зловмисник, який заволодіє вашим телефоном і приватними налаштуваннями шифрування, але чомусь не ваші повідомлення, але має повний запис усіх минулих зашифрованих повідомлень.</p> <p>No, not yet.</p>
<p>У будь-якому випадку, наскрізне шифрування Delta Chat використовує <a href="#openpgp-secure">безпечну підмножину OpenPGP</a> який пройшов <a href="https://delta.chat/assets/blog/2019-first-security-review.pdf">незалежний аудит безпеки</a>.</p> <p>Delta Chat uses the Rust OpenPGP library <a href="https://github.com/rpgp/rpgp">rPGP</a>
which supports the latest <a href="https://datatracker.ietf.org/doc/draft-ietf-openpgp-pqc/">IETF Post-Quantum-Cryptography OpenPGP draft</a>.
We aim to add PQC support in <a href="https://github.com/chatmail/core">chatmail core</a> after the draft is finalized at the IETF
in collaboration with other OpenPGP implementers.</p>
<h3 id="how-can-i-manually-check-encryption-information">
How can I manually check encryption information? <a href="#how-can-i-manually-check-encryption-information" class="anchor"></a>
</h3>
<p>Ви можете перевірити стан наскрізного шифрування вручну в діалоговому вікні “Шифрування” (профіль користувача на Android/iOS або клацніть правою кнопкою миші на елементі списку чату користувача на робочому столі). Delta Chat показує там два відбитки. Якщо на вашому пристрої та пристрої вашого співрозмовника з’являються однакові відбитки, з’єднання безпечне.</p>
<h3 id="importkey"> <h3 id="importkey">
@ -1223,6 +1235,11 @@ and will very probably be replaced by something else, stay tuned :)</p>
</h3> </h3>
<p>Note:
Changing email addresses is temporarily disabled
because of ongoing changes to the DeltaChat core.
It should be available again in a few months.</p>
<ol> <ol>
<li> <li>
<p>Змініть свою адресу в розділі “Налаштування → Додатково → Пароль та обліковий запис” та введіть пароль вашого нового поштового акаунта (і, за необхідності, налаштування сервера). Ви отримаєте інформаційне повідомлення про те, що ви переїжджаєте на нову адресу. Додаткове повідомлення також з’явиться у вашому чаті “Повідомлення пристрою”.</p> <p>Змініть свою адресу в розділі “Налаштування → Додатково → Пароль та обліковий запис” та введіть пароль вашого нового поштового акаунта (і, за необхідності, налаштування сервера). Ви отримаєте інформаційне повідомлення про те, що ви переїжджаєте на нову адресу. Додаткове повідомлення також з’явиться у вашому чаті “Повідомлення пристрою”.</p>

446
src/main/assets/help/zh_CN/help.html
View file

@ -36,27 +36,24 @@
<li><a href="#为什么-delta-chat-与集中式专有的-applegoogle-推送服务集成">为什么 Delta Chat 与集中式专有的 Apple/Google 推送服务集成？</a></li> <li><a href="#为什么-delta-chat-与集中式专有的-applegoogle-推送服务集成">为什么 Delta Chat 与集中式专有的 Apple/Google 推送服务集成？</a></li>
</ul> </ul>
</li> </li>
<li><a href="#加密和安全">加密和安全</a> <li><a href="#e2ee">加密和安全</a>
<ul> <ul>
<li><a href="#端到端加密使用了哪些标准-">端到端加密使用了哪些标准 ？</a></li> <li><a href="#端到端加密使用了哪些标准-">端到端加密使用了哪些标准 ？</a></li>
<li><a href="#whene2e">我如何知道信息是否经过端到端加密？</a></li> <li><a href="#whene2e">我如何知道信息是否经过端到端加密？</a></li>
<li><a href="#howtoe2ee">如何获得保证的端到端加密和绿色复选标记？</a></li> <li><a href="#can-i-still-receive-or-send-mails-without-end-to-end-encryption">Can i still receive or send mails without end-to-end encryption?</a></li>
<li><a href="#e2eeguarantee">绿色复选标记和“保证的端到端加密”是什么意思？</a></li> <li><a href="#howtoe2ee">How can I establish a chat with a new contact?</a></li>
<li><a href="#nocryptanymore">联系人“从另一台设备发送了消息”，我该怎么办？</a></li> <li><a href="#e2eeguarantee">What does the green checkmark in a contact profile mean?</a></li>
<li><a href="#附件图片文件音频等是否已端到端加密">附件（图片、文件、音频等）是否已端到端加密？</a></li> <li><a href="#附件图片文件音频等是否已端到端加密">附件（图片、文件、音频等）是否已端到端加密？</a></li>
<li><a href="#openpgp-secure">OpenPGP 安全吗？</a></li> <li><a href="#openpgp-secure">OpenPGP 安全吗？</a></li>
<li><a href="#openpgp-alternatives">你们是否考虑过使用 OpenPGP 的替代方案进行端到端加密？</a></li> <li><a href="#openpgp-alternatives">Did you consider using alternatives to OpenPGP for end-to-end-encryption?</a></li>
<li><a href="#delta-chat-是否容易受到-efail-攻击">Delta Chat 是否容易受到 EFAIL 攻击？</a></li> <li><a href="#delta-chat-是否容易受到-efail-攻击">Delta Chat 是否容易受到 EFAIL 攻击？</a></li>
<li><a href="#tls">如果端到端加密不可用，消息是否会以明文形式暴露？</a></li> <li><a href="#tls">Are messages marked with the mail icon exposed on the Internet?</a></li>
<li><a href="#message-metadata">Delta Chat 如何保护消息中的元数据？</a></li> <li><a href="#message-metadata">Delta Chat 如何保护消息中的元数据？</a></li>
<li><a href="#device-seizure">当设备被查封时，如何保护元数据和联系人？</a></li> <li><a href="#device-seizure">当设备被查封时，如何保护元数据和联系人？</a></li>
<li><a href="#如何检查加密信息">如何检查加密信息？</a></li> <li><a href="#sealedsender">Does Delta Chat support “Sealed Sender”?</a></li>
<li><a href="#如何检查消息的加密状态">如何检查消息的加密状态？</a></li>
<li><a href="#为什么我会看到未加密的消息">为什么我会看到未加密的消息？</a></li>
<li><a href="#如何与有时使用-webmail-或其他非-autocrypt-电子邮件应用的-delta-chat-联系人获得端到端加密的聊天">如何与有时使用 Webmail 或其他非 Autocrypt 电子邮件应用的 Delta Chat 联系人获得端到端加密的聊天？</a></li>
<li><a href="#如何确保消息端到端加密和删除">如何确保消息端到端加密和删除？</a></li>
<li><a href="#pfs">Delta Chat 是否支持完美前向保密？</a></li> <li><a href="#pfs">Delta Chat 是否支持完美前向保密？</a></li>
<li><a href="#delta-chat-的端到端加密是否与-signal-一样安全">Delta Chat 的端到端加密是否与 Signal 一样安全？</a></li> <li><a href="#pqc">Does Delta Chat support Post-Quantum-Cryptography?</a></li>
<li><a href="#how-can-i-manually-check-encryption-information">How can I manually check encryption information?</a></li>
<li><a href="#importkey">我可以重复使用现有的私钥吗？</a></li> <li><a href="#importkey">我可以重复使用现有的私钥吗？</a></li>
<li><a href="#security-audits">Delta Chat 是否已进行独立的安全漏洞审计？</a></li> <li><a href="#security-audits">Delta Chat 是否已进行独立的安全漏洞审计？</a></li>
</ul> </ul>
@ -686,10 +683,10 @@ Delta Chat 收到的所有电子邮件都将在此期限后从服务器中删除
包括<a href="https://delta.chat/chatmail#selfhosted">你可能在未经我们许可的情况下自行设置的服务器</a>。 包括<a href="https://delta.chat/chatmail#selfhosted">你可能在未经我们许可的情况下自行设置的服务器</a>。
欢迎来到可互操作且庞大的 Chatmail 和电子邮件系统的力量 :)</p> 欢迎来到可互操作且庞大的 Chatmail 和电子邮件系统的力量 :)</p>
<h2 id="加密和安全"> <h2 id="e2ee">
加密和安全 <a href="#加密和安全" class="anchor"></a> 加密和安全 <a href="#e2ee" class="anchor"></a>
</h2> </h2>
@ -702,18 +699,26 @@ Delta Chat 收到的所有电子邮件都将在此期限后从服务器中删除
</h3> </h3>
<p><a href="https://autocrypt.org">Autocrypt</a> 用于自动 <p>Delta Chat uses a <a href="#openpgp-secure">secure subset of the OpenPGP standard</a>
与联系人和群组聊天建立端到端加密。 to provide automatic end-to-end encryption using these protocols:</p>
Autocrypt 使用 OpenPGP 标准的有限且<a href="#openpgp-secure">安全子集</a>。
端到端加密消息标有挂锁
<img style="vertical-align:middle; width:1.2em; margin:1px" src="../lock-icon.png" alt="padlock" />。</p>
<p><a href="https://securejoin.delta.chat/en/latest/new.html">安全加入协议</a> <ul>
用于建立具有保证的端到端加密的聊天， <li>
从而防止网络攻击和受损服务器。 <p><a href="https://securejoin.delta.chat/en/latest/new.html">Secure-Join</a>
标有绿色复选标记的聊天 to exchange encryption setup information through QR-code scanning or “invite links”.</p>
<img style="vertical-align:middle; width:1.5em; margin:1px" src="../green-checkmark.png" alt="green checkmark" /> </li>
保证端到端加密消息。</p> <li>
<p><a href="https://autocrypt.org">Autocrypt</a> is used for automatically
establishing end-to-end encryption between contacts and all members of a group chat.</p>
</li>
<li>
<p><a href="https://github.com/chatmail/core/blob/main/spec.md#attaching-a-contact-to-a-message">Sharing a contact to a
chat</a>
enables receivers to use end-to-end encryption with the contact.</p>
</li>
</ul>
<p>Delta Chat does not query, publish or interact with any OpenPGP key servers.</p>
<h3 id="whene2e"> <h3 id="whene2e">
@ -723,28 +728,37 @@ Autocrypt 使用 OpenPGP 标准的有限且<a href="#openpgp-secure">安全子
</h3> </h3>
<p>所有端到端加密的消息都带有挂锁：</p> <p>All messages in Delta Chat are <strong>end-to-end encrypted by default</strong>.
Since the Delta Chat Version 2 release series (July 2025)
there are no lock or similar markers on end-to-end encrypted messages, anymore.</p>
<p><img style="width:160px; margin:1px" src="../lock-screenshot.png" alt="padlock in bubble" /></p> <h3 id="can-i-still-receive-or-send-mails-without-end-to-end-encryption">
<p>如果聊天标题旁边有绿色复选标记，则保证端到端加密：</p>
<p><img style="width:211px; margin:1px" src="../green-checkmark-screenshot.png" alt="green checkmark in title" /></p>
<h3 id="howtoe2ee">
如何获得保证的端到端加密和绿色复选标记？ <a href="#howtoe2ee" class="anchor"></a> Can i still receive or send mails without end-to-end encryption? <a href="#can-i-still-receive-or-send-mails-without-end-to-end-encryption" class="anchor"></a>
</h3> </h3>
<p>如果你与你的聊天伙伴有第二个通信渠道， <p>If you use default <a href="https://chatmail.at/relays">chatmail relays</a>,
例如视频聊天或不同的即时通讯应用， it is impossible to receive or send messages without end-to-end encryption.</p>
你可以生成邀请链接。</p>
<p>如果你们面对面在一起， <p>If you instead create a profile using a classic e-mail server,
你可以向你的聊天伙伴展示二维码。</p> you can send and receive messages without end-to-end encryption.
Such messages lacking end-to-end encryption are marked with an e-mail icon
<img style="vertical-align:middle; width:1.2em; margin:1px" src="../email-icon.png" alt="email" />.</p>
<h3 id="howtoe2ee">
How can I establish a chat with a new contact? <a href="#howtoe2ee" class="anchor"></a>
</h3>
<p>You can send an invite link through another private chat,
show an invitation QR code when next to each other or in a video call,
or click on a “contact” that was shared in a chat.</p>
<ul> <ul>
<li> <li>
@ -753,132 +767,60 @@ Autocrypt 使用 OpenPGP 标准的有限且<a href="#openpgp-secure">安全子
然后选择“QR 邀请码”。</p> 然后选择“QR 邀请码”。</p>
</li> </li>
<li> <li>
<p>对于<strong>直接 1:1 聊天邀请</strong>， <p>For <strong>direct 1:1 chat invitations</strong>,
点击 Delta Chat 应用主屏幕上的二维码图标 <img style="vertical-align:middle; width:1.8em; margin:1px" src="../qr-icon.png" />。</p> tap the QR Code icon <img style="vertical-align:middle; width:1.8em; margin:1px" src="../qr-icon.png" />
on the Delta Chat app main screen.</p>
</li> </li>
</ul> </ul>
<p>让你的聊天伙伴用他们的 Delta Chat 应用扫描二维码图像， <p>Ask your chat partner to scan the QR image
或点击“复制”或“分享”以创建邀请链接 with their Delta Chat app,
并与你的聊天伙伴分享。</p> or click “Copy” or “Share” to create an invite link
and share it with your chat partner.</p>
<p>现在等待 <a href="https://securejoin.delta.chat/en/latest/new.html#setup-contact-protocol">安全加入网络消息在两个设备之间交换</a>。</p> <p>Now wait while <a href="https://securejoin.delta.chat/en/latest/new.html#setup-contact-protocol">end-to-end encryption is getting established</a>.</p>
<ul> <ul>
<li> <li>
<p>如果两个设备都处于在线状态， <p>If both sides are online, they will soon see a (group or direct) chat
双方最终都会看到一个（群组或直接）聊天，标题旁边带有绿色复选标记 and can start messaging securely.</p>
<img style="vertical-align:middle; width:1.5em; margin:1px" src="../green-checkmark.png" alt="green checkmark" />。</p>
</li> </li>
<li> <li>
<p>如果其中一个设备处于离线状态，则只有当设备再次连接互联网且安全加入网络协议完成时，绿色复选标记才会出现。</p> <p>If one side is offline or in bad network,
the ability to chat is delayed until connectivity is restored.</p>
</li> </li>
</ul> </ul>
<p>恭喜！ <p>Congratulations!
从现在开始您将会自动使用安全的端到端加密与此联系人联系，并且双方都可以将对方添加到绿色复选标记的群组 You now will automatically use end-to-end encryption
<img style="vertical-align:middle; width:1.5em; margin:1px" src="../green-checkmark.png" alt="green checkmark" />，从而自动在其成员之间传播有保障的端到端加密。</p> with this contact.
If you add each other to chat groups,
end-to-end encryption will be established among all members.</p>
<h3 id="e2eeguarantee"> <h3 id="e2eeguarantee">
绿色复选标记和“保证的端到端加密”是什么意思？ <a href="#e2eeguarantee" class="anchor"></a> What does the green checkmark in a contact profile mean? <a href="#e2eeguarantee" class="anchor"></a>
</h3> </h3>
<p>带有绿色复选标记的聊天标题 <p>A contact profile might show a green checkmark
<img style="vertical-align:middle; width:1.5em; margin:1px" src="../green-checkmark.png" alt="绿色复选标记" /> <img style="vertical-align:middle; width:1.5em; margin:1px" src="../green-checkmark.png" alt="green checkmark" />
表示聊天中的所有消息都将进行端到端加密， and an “Introduced by” line.
并且不会被受损的电子邮件服务器或互联网提供商读取或更改。 Every green-checkmarked contact either did a direct <a href="#howtoe2ee">QR-scan</a> with you
加入带有绿色复选标记的群组聊天 or was introduced by a another green-checkmarked contact.
可以安全地传播每个人的加密信息（和绿色复选标记）， Introductions happen automatically when adding members to groups.
从而保证群组和成员之间的端到端加密。</p> Whoever adds a green-checkmarked contact to a group with only green-checkmarked members
becomes an introducer.
<p>带有绿色复选标记的联系人配置文件 In a contact profile you can tap on the “Introduced by …” text repeatedly
<img style="vertical-align:middle; width:1.5em; margin:1px" src="../green-checkmark.png" alt="绿色复选标记" /> until you get to the one with whom you directly did a <a href="#howtoe2ee">QR-scan</a>.</p>
表示当前保证与联系人的消息传递是端到端加密的。
每个带有绿色复选标记的联系人要么直接与你进行了 <a href="#howtoe2ee">二维码扫描</a>，
要么由另一个带有绿色复选标记的联系人介绍。
当向群组添加成员时，介绍会自动发生。
任何将联系人添加到带有绿色复选标记的群组的人都成为
那些还不认识添加的联系人的成员的介绍人。
在联系人配置文件中，你可以反复点击“由…介绍”文本
，直到你到达直接与你进行 <a href="#howtoe2ee">二维码扫描</a> 的那个人。</p>
<p>请注意，在联系人配置文件中，你可能会看到并点击介绍人，<br />但在配置文件标题中没有绿色复选标记。<br />这通常意味着联系人“<a href="#nocryptanymore">从另一台设备发送了消息</a>”。</p>
<p>有关“保证的端到端加密”的更深入讨论， <p>有关“保证的端到端加密”的更深入讨论，
请参阅 <a href="https://securejoin.delta.chat/en/latest/new.html">安全加入协议</a>， 请参阅 <a href="https://securejoin.delta.chat/en/latest/new.html">安全加入协议</a>，
并专门阅读有关“已验证群组”的内容，这是 并专门阅读有关“已验证群组”的内容，这是
此处所谓的“带有绿色复选标记”或“保证的端到端加密”聊天的技术术语。</p> 此处所谓的“带有绿色复选标记”或“保证的端到端加密”聊天的技术术语。</p>
<h3 id="nocryptanymore">
联系人“从另一台设备发送了消息”，我该怎么办？ <a href="#nocryptanymore" class="anchor"></a>
</h3>
<p>你与联系人的聊天失去了保证的端到端加密。
当你看到此警告时，此聊天的绿色复选标记和联系人已被删除。
<strong>如果你发现保证的端到端加密突然下降
对于此联系人来说很意外，请不要接受警告！</strong>
相反，请通过第二个渠道（
如视频通话、其他即时通讯应用或电话）与你的联系人核实
，以找出发生了什么。</p>
<p>如果你的联系人实际上导致了保证的端到端加密下降，
请参阅以下段落，了解常见原因及其缓解措施。
无论如何，所有其他带有绿色复选标记的聊天都保持保证的端到端加密，
即使该联系人是那里的成员。</p>
<p><strong>你的联系人在第二台设备（手机或笔记本电脑）上使用 Delta Chat</strong></p>
<p>如果他们有另一台运行 Delta Chat 应用的设备，
他们应该从新设备中删除配置文件，
并<a href="#multiclient">按照此处所述将其添加为第二台设备</a>。
在他们之后给你发消息后，警告将消失，
并且保证的加密将在你的联系人的两台设备之间建立。</p>
<p><strong>你的联系人使用他们的旧帐户登录名重新安装了 Delta Chat</strong></p>
<p>如果他们有<a href="#backup">备份文件</a>，
他们应该从新设备中删除配置文件，
而是导入备份文件以重新创建他们的配置文件。
在他们之后给你发消息后，警告将消失，
并且保证的加密将为此联系人重新建立。</p>
<p>如果他们没有备份文件，最好与你的聊天伙伴执行 <a href="#howtoe2ee">二维码扫描</a>，
以重新建立保证的端到端加密。</p>
<p><strong>你的联系人通过 Webmail 界面或其他电子邮件应用发送了邮件，
并且将很快恢复使用 Delta Chat。</strong></p>
<p>如果你确定联系人有时使用 Webmail，
或其他缺少端到端加密的邮件应用，
那么你可以接受警告。
一旦你的联系人再次使用 Delta Chat，
保证的端到端加密将自动重新建立。</p>
<p><strong>你的联系人完全停止使用 Delta Chat</strong></p>
<p>有时保持联系比端到端加密更重要。
<a href="#tls">“传输层加密” (TLS)</a> 可能仍然有意义地保护
你的设备和电子邮件服务器之间消息的机密性。
但是，如果没有端到端加密，你和你的联系人将信任你的电子邮件服务器
不会读取或操纵你的消息，也不会将其交给第三方。</p>
<p>在任何情况下，你都无法做太多其他事情，只能接受警告。
另请从任何活动的带有绿色复选标记的群组中删除该联系人，
你可以在联系人配置文件中的“共享聊天”中找到这些群组。
这可以避免你的联系人收到“无法读取”的消息。</p>
<p>如果联系人因为错误或不良行为而删除了 Delta Chat，
请考虑发布到我们的 <a href="https://support.delta.chat">支持论坛</a>，
以帮助我们识别和解决常见问题。 谢谢！</p>
<h3 id="附件图片文件音频等是否已端到端加密"> <h3 id="附件图片文件音频等是否已端到端加密">
@ -901,10 +843,9 @@ Autocrypt 使用 OpenPGP 标准的有限且<a href="#openpgp-secure">安全子
</h3> </h3>
<p>是的，Delta Chat 使用 OpenPGP 的安全子集， <p>Yes, Delta Chat uses a secure subset of OpenPGP
并且仅在消息上显示挂锁安全指示器 requiring the whole message to be properly encrypted and signed.
，前提是整个消息都已正确加密和签名。 For example, “Detached signatures” are not treated as secure.</p>
例如，“分离签名”不被视为安全。</p>
<p>OpenPGP 加密标准本身不存在安全隐患。 <p>OpenPGP 加密标准本身不存在安全隐患。
目前公众讨论中涉及的 OpenPGP 安全问题， 目前公众讨论中涉及的 OpenPGP 安全问题，
@ -923,7 +864,7 @@ Delta Chat 实际使用的是 Rust 语言编写的 OpenPGP 实现库 <a href="ht
<h3 id="openpgp-alternatives"> <h3 id="openpgp-alternatives">
你们是否考虑过使用 OpenPGP 的替代方案进行端到端加密？ <a href="#openpgp-alternatives" class="anchor"></a> Did you consider using alternatives to OpenPGP for end-to-end-encryption? <a href="#openpgp-alternatives" class="anchor"></a>
</h3> </h3>
@ -965,17 +906,15 @@ Delta Chat 实际使用的是 Rust 语言编写的 OpenPGP 实现库 <a href="ht
<h3 id="tls"> <h3 id="tls">
如果端到端加密不可用，消息是否会以明文形式暴露？ <a href="#tls" class="anchor"></a> Are messages marked with the mail icon exposed on the Internet? <a href="#tls" class="anchor"></a>
</h3> </h3>
<p>即使你的消息未保证端到端加密， <p>If you are sending or receiving e-mail messages without end-to-end encryption (using a classic e-mail server),
它们仍然受到互联网提供商（如手机或有线电视公司）的保护。 they are still protected from cell or cable companies who can not read or modify your e-mail messages.
但是，你的和你的接收者的电子邮件提供商 But both your and your recipient’s e-mail providers
可能会读取、分析甚至修改你的消息， may read, analyze or modify your messages, including any attachments.</p>
包括任何附件，
如果它们未进行端到端加密。</p>
<p>Delta Chat 默认使用严格的 <p>Delta Chat 默认使用严格的
<a href="https://en.wikipedia.org/wiki/Transport_Layer_Security">TLS 加密</a>， <a href="https://en.wikipedia.org/wiki/Transport_Layer_Security">TLS 加密</a>，
@ -987,10 +926,6 @@ Delta Chat 的所有 TLS 处理都经过了独立的 <a href="#security-audits">
则将在电子邮件提供商之间强制执行传输加密， 则将在电子邮件提供商之间强制执行传输加密，
在这种情况下，即使消息未进行端到端加密，Delta Chat 通信也永远不会以明文形式暴露给互联网。</p> 在这种情况下，即使消息未进行端到端加密，Delta Chat 通信也永远不会以明文形式暴露给互联网。</p>
<p>请注意，<a href="#howtoe2ee">在 TLS 加密之上保持保证的端到端加密</a>
可在你的和接收者的设备之间提供普遍的安全性。
即使你的电子邮件或互联网提供商也无法读取或修改你的消息。</p>
<h3 id="message-metadata"> <h3 id="message-metadata">
@ -999,24 +934,25 @@ Delta Chat 的所有 TLS 处理都经过了独立的 <a href="#security-audits">
</h3> </h3>
<p>Delta Chat 通过将以下信息放入消息的端到端加密部分来保护大多数消息元数据：</p> <p>Unlike most other messengers,
Delta Chat apps do not store any metadata about contacts or groups on servers, also not in encrypted form.
Instead, all group metadata is end-to-end encrypted and stored on end-user devices, only.</p>
<p>E-mail Servers can therefore only see</p>
<ul> <ul>
<li>主题行</li> <li>
<li>群组头像和名称</li> <p>the message date,</p>
<li>MDN（已读回执）请求 (<code class="language-plaintext highlighter-rouge">Chat-Disposition-Notification-To</code>)</li> </li>
<li>阅后即焚消息计时器 (<code class="language-plaintext highlighter-rouge">Ephemeral-Timer</code>)</li> <li>
<li><code class="language-plaintext highlighter-rouge">Chat-Group-Member-Removed</code>, <code class="language-plaintext highlighter-rouge">Chat-Group-Member-Added</code></li> <p>sender and receiver addresses</p>
<li>包含安全加入命令的 <code class="language-plaintext highlighter-rouge">Secure-Join</code> 标头</li> </li>
<li>关于启用位置流式传输的通知</li> <li>
<li>WebRTC 房间 URL</li> <p>and message size.</p>
</li>
</ul> </ul>
<p>电子邮件服务器无法访问此受保护的元数据， <p>All other message, contact and group metadata resides in the end-to-end encrypted part of messages.</p>
但它们可以看到消息日期以及消息大小，
更重要的是，可以看到发件人和收件人地址。
电子邮件服务器需要收件人地址来路由和
将消息传递到接收者的设备。</p>
<h3 id="device-seizure"> <h3 id="device-seizure">
@ -1026,96 +962,36 @@ Delta Chat 的所有 TLS 处理都经过了独立的 <a href="#security-audits">
</h3> </h3>
<p>为了防止收集元数据的电子邮件服务器 <p>Both for protecting against metadata-collecting e-mail servers
以及设备查封的威胁， as well as against the threat of device seizure
我们建议使用 <a href="https://delta.chat/chatmail">Chatmail 服务器</a> we recommend to use a <a href="https://chatmail.at/relays">chatmail relay</a>
通过二维码扫描创建匿名临时配置文件。 to create chat profiles using random e-mail addresses for transport.
请注意，所有平台上的 Delta Chat 应用都支持多配置文件， Note that Delta Chat apps on all platforms support multiple profiles
因此你可以轻松地在你“主要”配置文件旁边使用特定于情况的配置文件， so you can easily use situation-specific profiles next to your “main” profile
并且知道它们的所有数据以及所有元数据都将被删除。 with the knowledge that all their data, along with all metadata, will be deleted.
此外，如果设备被查封，则与使用临时配置文件的联系人 Moreover, if a device is seized then chat contacts using short-lived profiles
相比，无法轻易识别，因为即时通讯应用会在聊天群组中显示 can not be identified easily.</p>
电话号码，而电话号码通常与合法身份相关联。</p>
<h3 id="如何检查加密信息"> <h3 id="sealedsender">
如何检查加密信息？ <a href="#如何检查加密信息" class="anchor"></a> Does Delta Chat support “Sealed Sender”? <a href="#sealedsender" class="anchor"></a>
</h3> </h3>
<p>你可以在“加密”对话框中手动检查端到端加密状态 <p>No, not yet.</p>
（Android/iOS 上的用户配置文件或桌面上的用户聊天列表项上右键单击）。
Delta Chat 在此处显示两个指纹。
如果相同的指纹出现在你自己的设备和你联系人的设备上，
则连接是安全的。</p>
<h3 id="如何检查消息的加密状态"> <p>The Signal messenger introduced <a href="https://signal.org/blog/sealed-sender/">“Sealed Sender” in 2018</a>
to keep their server infrastructure ignorant of who is sending a message to a set of recipients.
It is particularly important because the Signal server knows the mobile number of each account,
which is usually associated with a passport identity.</p>
<p>Even if <a href="https://chatmail.at/relays">chatmail relays</a>
如何检查消息的加密状态？ <a href="#如何检查消息的加密状态" class="anchor"></a> do not ask for any private data (including no phone numbers),
it might still be worthwhile to protect relational metadata between addresses.
We don’t foresee bigger problems in using random throw-away e-mail addresses for sealed sending
</h3> but an implementation has not been agreed as a priority yet.</p>
<p>消息气泡中的小<strong>挂锁</strong>表示
消息已从给定的发件人正确进行端到端加密。
如果<strong>没有挂锁</strong>，则消息未正确进行端到端加密，
最可能是因为发件人使用的应用或 Webmail 界面
不支持端到端加密。</p>
<h3 id="为什么我会看到未加密的消息">
为什么我会看到未加密的消息？ <a href="#为什么我会看到未加密的消息" class="anchor"></a>
</h3>
<p>如果联系人使用非 Autocrypt 电子邮件应用，
则涉及此联系人（在群组或 1:1 聊天中）的所有消息
将不会进行端到端加密，因此消息中不会显示“挂锁”。
请注意，即使你的联系人在其帐户上使用 Delta Chat，
他们也可能在该帐户上使用非 Autocrypt 电子邮件应用，
这可能会导致间歇性未加密的消息。
回复未加密的消息是 Autocrypt 强制执行的
，以防止你的联系人及其非 Autocrypt 电子邮件应用端出现无法读取的消息。</p>
<h3 id="如何与有时使用-webmail-或其他非-autocrypt-电子邮件应用的-delta-chat-联系人获得端到端加密的聊天">
如何与有时使用 Webmail 或其他非 Autocrypt 电子邮件应用的 Delta Chat 联系人获得端到端加密的聊天？ <a href="#如何与有时使用-webmail-或其他非-autocrypt-电子邮件应用的-delta-chat-联系人获得端到端加密的聊天" class="anchor"></a>
</h3>
<p>如果你需要与
同时使用 Delta Chat 和非 Autocrypt 应用（例如 Webmail）的电子邮件帐户的联系人进行安全端到端加密的聊天，
最好与他们设置 <a href="#howtoe2ee">保证的端到端加密</a>，
然后创建一个由你二人作为成员的保证的端到端加密的群组聊天。
在此群组聊天中，所有消息都将进行端到端加密，
即使你二人之间的直接聊天有
<a href="#nocryptanymore">“…从另一台设备发送了消息”</a> 警告</p>
<h3 id="如何确保消息端到端加密和删除">
如何确保消息端到端加密和删除？ <a href="#如何确保消息端到端加密和删除" class="anchor"></a>
</h3>
<p>确保每条消息都进行端到端加密，
并尽快删除元数据的最佳方法是
<a href="#howtoe2ee">使用具有保证的端到端加密的聊天</a>
并开启 <a href="#ephemeralmsgs">阅后即焚消息</a>。</p>
<p>保证的端到端加密聊天可防止 <a href="https://en.wikipedia.org/wiki/Man-in-the-middle_attack">MITM 攻击</a>，
而开启阅后即焚消息会在用户配置的时间后删除服务器上的消息。</p>
<p>如果你不需要在服务器上保留消息的长期副本，
你还可以开启 <a href="#delold">“自动从服务器删除消息”</a>。</p>
<h3 id="pfs"> <h3 id="pfs">
@ -1125,45 +1001,52 @@ Delta Chat 在此处显示两个指纹。
</h3> </h3>
<p>不，Delta Chat 不支持完美前向保密 (PFS)。 <p>No, not yet.</p>
这意味着，如果您的 Delta Chat 私人解密密钥泄露，
并且有人收集了您之前传输的消息，
他们将能够使用泄露的解密密钥解密并阅读这些消息。</p>
<p>但请注意，如果有人获得您的解密密钥， <p>Delta Chat today doesn’t support Perfect Forward Secrecy (PFS).
他们通常也能够获得您的消息， This means that if your private decryption key is leaked,
无论是否实施了完全前向保密。 and someone has collected your prior in-transit messages,
泄露解密密钥的典型现实情况是设备扣押， they will be able to decrypt and read them using the leaked decryption key.
我们在<a href="#device-seizure">关于元数据和设备扣押</a>的回答中讨论了这一点。</p> Note that Forward Secrecy only increases security if you delete messages.
Otherwise, someone obtaining your decryption keys
is typically also able to get all your non-deleted messages
and doesn’t even need to decrypt any previously collected messages.</p>
<p>Delta Chat 可能会发展为支持完美前向保密， <p>We designed a Forward Secrecy approach that withstood
因为 OpenPGP 只是加密消息的容器， initial examination from some cryptographers and implementation experts
但密钥管理（以及密钥轮换或密钥“棘轮”） but is pending a more formal write up
可以以灵活的方式组织。 to ascertain it reliably works in federated messaging and with multi-device usage,
请参阅 <a href="https://gitlab.com/sequoia-pgp/openpgp-dr">Seqouia 的 PFS 原型</a>， before it could be implemented in <a href="https://github.com/chatmail/core">chatmail core</a>,
了解 OpenPGP 实现者社区中现有的实验。</p> which would make it available in all <a href="https://chatmail.at/clients">chatmail clients</a>.</p>
<h3 id="delta-chat-的端到端加密是否与-signal-一样安全"> <h3 id="pqc">
Delta Chat 的端到端加密是否与 Signal 一样安全？ <a href="#delta-chat-的端到端加密是否与-signal-一样安全" class="anchor"></a> Does Delta Chat support Post-Quantum-Cryptography? <a href="#pqc" class="anchor"></a>
</h3> </h3>
<p>这取决于对你而言重要的是什么。 <p>No, not yet.</p>
Delta Chat <a href="#pfs">不支持像 Signal 那样的 PFS</a>，
但它提供了 <a href="#e2eeguarantee">保证的端到端加密聊天</a>，
可以安全地抵御受损的服务器或损坏的网络。
Signal 和大多数其他支持 PFS 的即时通讯应用
没有提供实用的方案来保护聊天群组免受网络攻击，
而网络攻击可以说比
潜在的攻击者查封你的手机和私有加密设置
但不知何故没有你的消息，却完整记录了所有
过去的加密消息更令人担忧。</p>
<p>在任何情况下，Delta Chat 的端到端加密都使用 <a href="#openpgp-secure">OpenPGP 的安全子集</a>， <p>Delta Chat uses the Rust OpenPGP library <a href="https://github.com/rpgp/rpgp">rPGP</a>
该子集已 <a href="https://delta.chat/assets/blog/2019-first-security-review.pdf">通过独立的安全审计</a>。</p> which supports the latest <a href="https://datatracker.ietf.org/doc/draft-ietf-openpgp-pqc/">IETF Post-Quantum-Cryptography OpenPGP draft</a>.
We aim to add PQC support in <a href="https://github.com/chatmail/core">chatmail core</a> after the draft is finalized at the IETF
in collaboration with other OpenPGP implementers.</p>
<h3 id="how-can-i-manually-check-encryption-information">
How can I manually check encryption information? <a href="#how-can-i-manually-check-encryption-information" class="anchor"></a>
</h3>
<p>你可以在“加密”对话框中手动检查端到端加密状态
（Android/iOS 上的用户配置文件或桌面上的用户聊天列表项上右键单击）。
Delta Chat 在此处显示两个指纹。
如果相同的指纹出现在你自己的设备和你联系人的设备上，
则连接是安全的。</p>
<h3 id="importkey"> <h3 id="importkey">
@ -1571,6 +1454,11 @@ and will very probably be replaced by something else, stay tuned :)</p>
</h3> </h3>
<p>Note:
Changing email addresses is temporarily disabled
because of ongoing changes to the DeltaChat core.
It should be available again in a few months.</p>
<ol> <ol>
<li> <li>
<p>在“设置 → 高级 → 密码和帐户”中更改你的地址， <p>在“设置 → 高级 → 密码和帐户”中更改你的地址，

5
src/main/java/com/b44t/messenger/DcChat.java
View file

@ -45,7 +45,6 @@ public class DcChat {
public native boolean isDeviceTalk (); public native boolean isDeviceTalk ();
public native boolean canSend (); public native boolean canSend ();
public native boolean isProtected (); public native boolean isProtected ();
public native boolean isProtectionBroken();
public native boolean isSendingLocations(); public native boolean isSendingLocations();
public native boolean isMuted (); public native boolean isMuted ();
public native boolean isContactRequest (); public native boolean isContactRequest ();
@ -69,10 +68,6 @@ public class DcChat {
return getType() == DC_CHAT_TYPE_OUT_BROADCAST; return getType() == DC_CHAT_TYPE_OUT_BROADCAST;
} }
public boolean isHalfBlocked() {
return isProtectionBroken() || isContactRequest();
}
// working with raw c-data // working with raw c-data
private long chatCPtr; // CAVE: the name is referenced in the JNI private long chatCPtr; // CAVE: the name is referenced in the JNI

1
src/main/java/com/b44t/messenger/DcContact.java
View file

@ -12,6 +12,7 @@ public class DcContact {
public final static int DC_CONTACT_ID_QR_INVITE = -4; // - " - public final static int DC_CONTACT_ID_QR_INVITE = -4; // - " -
public final static int DC_CONTACT_ID_NEW_BROADCAST = -5; // - " - public final static int DC_CONTACT_ID_NEW_BROADCAST = -5; // - " -
public final static int DC_CONTACT_ID_ADD_ACCOUNT = -6; // - " - public final static int DC_CONTACT_ID_ADD_ACCOUNT = -6; // - " -
public final static int DC_CONTACT_ID_NEW_UNENCRYPTED_GROUP = -7; // - " -
public DcContact(long contactCPtr) { public DcContact(long contactCPtr) {
this.contactCPtr = contactCPtr; this.contactCPtr = contactCPtr;

1
src/main/java/com/b44t/messenger/DcContext.java
View file

@ -39,6 +39,7 @@ public class DcContext {
public final static int DC_GCL_VERIFIED_ONLY = 1; public final static int DC_GCL_VERIFIED_ONLY = 1;
public final static int DC_GCL_ADD_SELF = 2; public final static int DC_GCL_ADD_SELF = 2;
public final static int DC_GCL_ADDRESS = 0x04;
public final static int DC_GCL_ARCHIVED_ONLY = 0x01; public final static int DC_GCL_ARCHIVED_ONLY = 0x01;
public final static int DC_GCL_NO_SPECIALS = 0x02; public final static int DC_GCL_NO_SPECIALS = 0x02;
public final static int DC_GCL_ADD_ALLDONE_HINT = 0x04; public final static int DC_GCL_ADD_ALLDONE_HINT = 0x04;

2
src/main/java/com/b44t/messenger/DcMsg.java
View file

@ -33,9 +33,9 @@ public class DcMsg {
public final static int DC_INFO_LOCATION_ONLY = 9; public final static int DC_INFO_LOCATION_ONLY = 9;
public final static int DC_INFO_EPHEMERAL_TIMER_CHANGED = 10; public final static int DC_INFO_EPHEMERAL_TIMER_CHANGED = 10;
public final static int DC_INFO_PROTECTION_ENABLED = 11; public final static int DC_INFO_PROTECTION_ENABLED = 11;
public final static int DC_INFO_PROTECTION_DISABLED = 12;
public final static int DC_INFO_INVALID_UNENCRYPTED_MAIL = 13; public final static int DC_INFO_INVALID_UNENCRYPTED_MAIL = 13;
public final static int DC_INFO_WEBXDC_INFO_MESSAGE = 32; public final static int DC_INFO_WEBXDC_INFO_MESSAGE = 32;
public final static int DC_INFO_CHAT_E2EE = 50;
public final static int DC_STATE_UNDEFINED = 0; public final static int DC_STATE_UNDEFINED = 0;
public final static int DC_STATE_IN_FRESH = 10; public final static int DC_STATE_IN_FRESH = 10;

4
src/main/java/com/b44t/messenger/rpc/Rpc.java
View file

@ -164,6 +164,10 @@ public class Rpc {
return gson.fromJson(getResult("create_broadcast", accountId, chatName), Integer.class); return gson.fromJson(getResult("create_broadcast", accountId, chatName), Integer.class);
} }
public int createGroupChatUnencrypted(int accountId, String chatName) throws RpcException {
return gson.fromJson(getResult("create_group_chat_unencrypted", accountId, chatName), Integer.class);
}
public void setAccountsOrder(List<Integer> order) throws RpcException { public void setAccountsOrder(List<Integer> order) throws RpcException {
getResult("set_accounts_order", order); getResult("set_accounts_order", order);
} }

36
src/main/java/org/thoughtcrime/securesms/ApplicationContext.java
View file

@ -197,30 +197,30 @@ public class ApplicationContext extends MultiDexApplication {
} }
}, filter); }, filter);
// MAYBE TODO: i think the ApplicationContext is also created
// when the app is stated by FetchWorker timeouts.
// in this case, the normal threads shall not be started.
Constraints constraints = new Constraints.Builder()
.setRequiredNetworkType(NetworkType.CONNECTED)
.build();
PeriodicWorkRequest fetchWorkRequest = new PeriodicWorkRequest.Builder(
FetchWorker.class,
PeriodicWorkRequest.MIN_PERIODIC_INTERVAL_MILLIS, // usually 15 minutes
TimeUnit.MILLISECONDS,
PeriodicWorkRequest.MIN_PERIODIC_FLEX_MILLIS, // the start may be preferred by up to 5 minutes, so we run every 10-15 minutes
TimeUnit.MILLISECONDS)
.setConstraints(constraints)
.build();
WorkManager.getInstance(this).enqueueUniquePeriodicWork(
"FetchWorker",
ExistingPeriodicWorkPolicy.KEEP,
fetchWorkRequest);
AppCompatDelegate.setCompatVectorFromResourcesEnabled(true); AppCompatDelegate.setCompatVectorFromResourcesEnabled(true);
if (Prefs.isPushEnabled(this)) { if (Prefs.isPushEnabled(this)) {
FcmReceiveService.register(this); FcmReceiveService.register(this);
} else { } else {
Log.i(TAG, "FCM disabled at build time"); Log.i(TAG, "FCM disabled at build time");
// MAYBE TODO: i think the ApplicationContext is also created
// when the app is stated by FetchWorker timeouts.
// in this case, the normal threads shall not be started.
Constraints constraints = new Constraints.Builder()
.setRequiredNetworkType(NetworkType.CONNECTED)
.build();
PeriodicWorkRequest fetchWorkRequest = new PeriodicWorkRequest.Builder(
FetchWorker.class,
PeriodicWorkRequest.MIN_PERIODIC_INTERVAL_MILLIS, // usually 15 minutes
TimeUnit.MILLISECONDS,
PeriodicWorkRequest.MIN_PERIODIC_FLEX_MILLIS, // the start may be preferred by up to 5 minutes, so we run every 10-15 minutes
TimeUnit.MILLISECONDS)
.setConstraints(constraints)
.build();
WorkManager.getInstance(this).enqueueUniquePeriodicWork(
"FetchWorker",
ExistingPeriodicWorkPolicy.KEEP,
fetchWorkRequest);
} }
} }

6
src/main/java/org/thoughtcrime/securesms/BaseConversationItem.java
View file

@ -81,7 +81,7 @@ public abstract class BaseConversationItem extends LinearLayout
protected boolean shouldInterceptClicks(DcMsg messageRecord) { protected boolean shouldInterceptClicks(DcMsg messageRecord) {
return batchSelected.isEmpty() return batchSelected.isEmpty()
&& (messageRecord.isFailed() && (messageRecord.isFailed()
|| messageRecord.getInfoType() == DcMsg.DC_INFO_PROTECTION_DISABLED || messageRecord.getInfoType() == DcMsg.DC_INFO_CHAT_E2EE
|| messageRecord.getInfoType() == DcMsg.DC_INFO_PROTECTION_ENABLED || messageRecord.getInfoType() == DcMsg.DC_INFO_PROTECTION_ENABLED
|| messageRecord.getInfoType() == DcMsg.DC_INFO_INVALID_UNENCRYPTED_MAIL); || messageRecord.getInfoType() == DcMsg.DC_INFO_INVALID_UNENCRYPTED_MAIL);
} }
@ -129,9 +129,7 @@ public abstract class BaseConversationItem extends LinearLayout
.setPositiveButton(R.string.ok, null) .setPositiveButton(R.string.ok, null)
.create(); .create();
d.show(); d.show();
} else if (messageRecord.getInfoType() == DcMsg.DC_INFO_PROTECTION_DISABLED) { } else if (messageRecord.getInfoType() == DcMsg.DC_INFO_CHAT_E2EE || messageRecord.getInfoType() == DcMsg.DC_INFO_PROTECTION_ENABLED) {
DcHelper.showVerificationBrokenDialog(context, conversationRecipient.getName());
} else if (messageRecord.getInfoType() == DcMsg.DC_INFO_PROTECTION_ENABLED) {
DcHelper.showProtectionEnabledDialog(context); DcHelper.showProtectionEnabledDialog(context);
} else if (messageRecord.getInfoType() == DcMsg.DC_INFO_INVALID_UNENCRYPTED_MAIL) { } else if (messageRecord.getInfoType() == DcMsg.DC_INFO_INVALID_UNENCRYPTED_MAIL) {
DcHelper.showInvalidUnencryptedDialog(context); DcHelper.showInvalidUnencryptedDialog(context);

9
src/main/java/org/thoughtcrime/securesms/ContactSelectionListFragment.java
View file

@ -83,6 +83,7 @@ public class ContactSelectionListFragment extends Fragment
public static final String MULTI_SELECT = "multi_select"; public static final String MULTI_SELECT = "multi_select";
public static final String SELECT_VERIFIED_EXTRA = "select_verified"; public static final String SELECT_VERIFIED_EXTRA = "select_verified";
public static final String SELECT_UNENCRYPTED_EXTRA = "select_unencrypted_extra";
public static final String ALLOW_CREATION = "allow_creation"; public static final String ALLOW_CREATION = "allow_creation";
public static final String PRESELECTED_CONTACTS = "preselected_contacts"; public static final String PRESELECTED_CONTACTS = "preselected_contacts";
public static final int CONTACT_ADDR_RESULT_CODE = 61123; public static final int CONTACT_ADDR_RESULT_CODE = 61123;
@ -251,6 +252,10 @@ public class ContactSelectionListFragment extends Fragment
return getActivity().getIntent().getBooleanExtra(SELECT_VERIFIED_EXTRA, false); return getActivity().getIntent().getBooleanExtra(SELECT_VERIFIED_EXTRA, false);
} }
private boolean isUnencrypted() {
return getActivity().getIntent().getBooleanExtra(SELECT_UNENCRYPTED_EXTRA, false);
}
private void initializeCursor() { private void initializeCursor() {
ContactSelectionListAdapter adapter = new ContactSelectionListAdapter(getActivity(), ContactSelectionListAdapter adapter = new ContactSelectionListAdapter(getActivity(),
GlideApp.with(this), GlideApp.with(this),
@ -273,11 +278,11 @@ public class ContactSelectionListFragment extends Fragment
@Override @Override
public Loader<DcContactsLoader.Ret> onCreateLoader(int id, Bundle args) { public Loader<DcContactsLoader.Ret> onCreateLoader(int id, Bundle args) {
final boolean allowCreation = getActivity().getIntent().getBooleanExtra(ALLOW_CREATION, true); final boolean allowCreation = getActivity().getIntent().getBooleanExtra(ALLOW_CREATION, true);
final boolean addCreateContactLink = allowCreation && !isSelectVerfied(); final boolean addCreateContactLink = allowCreation && isUnencrypted();
final boolean addCreateGroupLinks = allowCreation && !isRelayingMessageContent(getActivity()) && !isMulti(); final boolean addCreateGroupLinks = allowCreation && !isRelayingMessageContent(getActivity()) && !isMulti();
final boolean addScanQRLink = allowCreation && !isMulti(); final boolean addScanQRLink = allowCreation && !isMulti();
final int listflags = DcContext.DC_GCL_ADD_SELF; final int listflags = DcContext.DC_GCL_ADD_SELF | (isUnencrypted()? DcContext.DC_GCL_ADDRESS : 0);
return new DcContactsLoader(getActivity(), listflags, cursorFilter, addCreateGroupLinks, addCreateContactLink, addScanQRLink, false); return new DcContactsLoader(getActivity(), listflags, cursorFilter, addCreateGroupLinks, addCreateContactLink, addScanQRLink, false);
} }

14
src/main/java/org/thoughtcrime/securesms/ConversationActivity.java
View file

@ -442,7 +442,7 @@ public class ConversationActivity extends PassphraseRequiredActionBarActivity
menu.findItem(R.id.menu_show_map).setVisible(false); menu.findItem(R.id.menu_show_map).setVisible(false);
} }
if (!dcChat.canSend() || dcChat.isMailingList() ) { if (!dcChat.isEncrypted() || !dcChat.canSend() || dcChat.isMailingList() ) {
menu.findItem(R.id.menu_ephemeral_messages).setVisible(false); menu.findItem(R.id.menu_ephemeral_messages).setVisible(false);
} }
@ -1610,7 +1610,7 @@ public class ConversationActivity extends PassphraseRequiredActionBarActivity
} }
public void initializeContactRequest() { public void initializeContactRequest() {
if (!dcChat.isHalfBlocked()) { if (!dcChat.isContactRequest()) {
messageRequestBottomView.setVisibility(View.GONE); messageRequestBottomView.setVisibility(View.GONE);
return; return;
} }
@ -1623,15 +1623,7 @@ public class ConversationActivity extends PassphraseRequiredActionBarActivity
}); });
if (dcChat.isProtectionBroken()) { if (dcChat.getType() == DcChat.DC_CHAT_TYPE_GROUP) {
messageRequestBottomView.setBlockText(R.string.more_info_desktop);
String name = dcContext.getContact(recipient.getDcContact().getId()).getDisplayName();
messageRequestBottomView.setBlockOnClickListener(v -> DcHelper.showVerificationBrokenDialog(this, name));
messageRequestBottomView.setQuestion(getString(R.string.chat_protection_broken, name));
messageRequestBottomView.setAcceptText(R.string.ok);
} else if (dcChat.getType() == DcChat.DC_CHAT_TYPE_GROUP) {
// We don't support blocking groups yet, so offer to delete it instead // We don't support blocking groups yet, so offer to delete it instead
messageRequestBottomView.setBlockText(R.string.delete); messageRequestBottomView.setBlockText(R.string.delete);
messageRequestBottomView.setBlockOnClickListener(v -> handleDeleteChat()); messageRequestBottomView.setBlockOnClickListener(v -> handleDeleteChat());

5
src/main/java/org/thoughtcrime/securesms/ConversationFragment.java
View file

@ -331,8 +331,7 @@ public class ConversationFragment extends MessageSelectorFragment
menu.findItem(R.id.menu_context_share).setVisible(messageRecord.hasFile()); menu.findItem(R.id.menu_context_share).setVisible(messageRecord.hasFile());
boolean canReply = canReplyToMsg(messageRecord); boolean canReply = canReplyToMsg(messageRecord);
menu.findItem(R.id.menu_context_reply).setVisible(chat.canSend() && canReply); menu.findItem(R.id.menu_context_reply).setVisible(chat.canSend() && canReply);
boolean canEdit = canEditMsg(messageRecord); menu.findItem(R.id.menu_context_edit).setVisible(chat.isEncrypted() && chat.canSend() && canEditMsg(messageRecord));
menu.findItem(R.id.menu_context_edit).setVisible(chat.canSend() && canEdit);
boolean showReplyPrivately = chat.isMultiUser() && !messageRecord.isOutgoing() && canReply; boolean showReplyPrivately = chat.isMultiUser() && !messageRecord.isOutgoing() && canReply;
menu.findItem(R.id.menu_context_reply_privately).setVisible(showReplyPrivately); menu.findItem(R.id.menu_context_reply_privately).setVisible(showReplyPrivately);
menu.findItem(R.id.menu_add_to_home_screen).setVisible(messageRecord.getType() == DcMsg.DC_MSG_WEBXDC); menu.findItem(R.id.menu_add_to_home_screen).setVisible(messageRecord.getType() == DcMsg.DC_MSG_WEBXDC);
@ -825,7 +824,7 @@ public class ConversationFragment extends MessageSelectorFragment
public void onShowFullClicked(DcMsg messageRecord) { public void onShowFullClicked(DcMsg messageRecord) {
Intent intent = new Intent(getActivity(), FullMsgActivity.class); Intent intent = new Intent(getActivity(), FullMsgActivity.class);
intent.putExtra(FullMsgActivity.MSG_ID_EXTRA, messageRecord.getId()); intent.putExtra(FullMsgActivity.MSG_ID_EXTRA, messageRecord.getId());
intent.putExtra(FullMsgActivity.BLOCK_LOADING_REMOTE, getListAdapter().getChat().isHalfBlocked()); intent.putExtra(FullMsgActivity.BLOCK_LOADING_REMOTE, getListAdapter().getChat().isContactRequest());
startActivity(intent); startActivity(intent);
getActivity().overridePendingTransition(R.anim.slide_from_right, R.anim.fade_scale_out); getActivity().overridePendingTransition(R.anim.slide_from_right, R.anim.fade_scale_out);
} }

17
src/main/java/org/thoughtcrime/securesms/ConversationListActivity.java
View file

@ -109,7 +109,7 @@ public class ConversationListActivity extends PassphraseRequiredActionBarActivit
// it is not needed to keep all past update messages, however, when deleted, also the strings should be deleted. // it is not needed to keep all past update messages, however, when deleted, also the strings should be deleted.
try { try {
DcContext dcContext = DcHelper.getContext(this); DcContext dcContext = DcHelper.getContext(this);
final String deviceMsgLabel = "update_1_50_0_android"; final String deviceMsgLabel = "update_2_0_0_android-h";
if (!dcContext.wasDeviceMsgEverAdded(deviceMsgLabel)) { if (!dcContext.wasDeviceMsgEverAdded(deviceMsgLabel)) {
DcMsg msg = null; DcMsg msg = null;
if (!getIntent().getBooleanExtra(FROM_WELCOME, false)) { if (!getIntent().getBooleanExtra(FROM_WELCOME, false)) {
@ -120,7 +120,7 @@ public class ConversationListActivity extends PassphraseRequiredActionBarActivit
// Util.copy(inputStream, new FileOutputStream(outputFile)); // Util.copy(inputStream, new FileOutputStream(outputFile));
// msg.setFile(outputFile, "image/jpeg"); // msg.setFile(outputFile, "image/jpeg");
msg.setText(getString(R.string.update_1_50_android, "https://get.delta.chat/#changelogs")); msg.setText(getString(R.string.update_2_0, "https://delta.chat/donate"));
} }
dcContext.addDeviceMsg(deviceMsgLabel, msg); dcContext.addDeviceMsg(deviceMsgLabel, msg);
@ -133,19 +133,6 @@ public class ConversationListActivity extends PassphraseRequiredActionBarActivit
Prefs.setStringPreference(this, Prefs.LAST_DEVICE_MSG_LABEL, deviceMsgLabel); Prefs.setStringPreference(this, Prefs.LAST_DEVICE_MSG_LABEL, deviceMsgLabel);
} }
// add info about moved "switch profile" option; added 2024-08, can be removed after ~3 months
if (!Prefs.getBooleanPreference(this, "info_about_switch_profile_added", false)) {
final DcAccounts dcAccounts = DcHelper.getAccounts(this);
if (dcAccounts.getAll().length >= 2) {
DcMsg msg = new DcMsg(dcContext, DcMsg.DC_MSG_TEXT);
msg.setText(getString(R.string.update_switch_profile_placement));
dcContext.addDeviceMsg("info_about_switch_profile", msg);
}
Prefs.setBooleanPreference(this, "info_about_switch_profile_added", true);
}
// /add info
// remove gmail oauth2 // remove gmail oauth2
final int serverFlags = dcContext.getConfigInt(CONFIG_SERVER_FLAGS); final int serverFlags = dcContext.getConfigInt(CONFIG_SERVER_FLAGS);
if ((serverFlags & DcContext.DC_LP_AUTH_OAUTH2)!=0) { if ((serverFlags & DcContext.DC_LP_AUTH_OAUTH2)!=0) {

6
src/main/java/org/thoughtcrime/securesms/ConversationListItem.java
View file

@ -134,6 +134,7 @@ public class ConversationListItem extends RelativeLayout
this.fromView.setText(recipient, state!=DcMsg.DC_STATE_IN_FRESH); this.fromView.setText(recipient, state!=DcMsg.DC_STATE_IN_FRESH);
} }
subjectView.setVisibility(chatId == DcChat.DC_CHAT_ID_ARCHIVED_LINK? GONE : VISIBLE);
this.subjectView.setText(thread.getDisplayBody()); this.subjectView.setText(thread.getDisplayBody());
this.subjectView.setTypeface(state==DcMsg.DC_STATE_IN_FRESH ? BOLD_TYPEFACE : LIGHT_TYPEFACE); this.subjectView.setTypeface(state==DcMsg.DC_STATE_IN_FRESH ? BOLD_TYPEFACE : LIGHT_TYPEFACE);
this.subjectView.setTextColor(state==DcMsg.DC_STATE_IN_FRESH ? ThemeUtil.getThemedColor(getContext(), R.attr.conversation_list_item_unread_color) this.subjectView.setTextColor(state==DcMsg.DC_STATE_IN_FRESH ? ThemeUtil.getThemedColor(getContext(), R.attr.conversation_list_item_unread_color)
@ -164,7 +165,7 @@ public class ConversationListItem extends RelativeLayout
fromView.setCompoundDrawablesWithIntrinsicBounds( fromView.setCompoundDrawablesWithIntrinsicBounds(
thread.isMuted()? R.drawable.ic_volume_off_grey600_18dp : 0, thread.isMuted()? R.drawable.ic_volume_off_grey600_18dp : 0,
0, 0,
thread.isProtected()? R.drawable.ic_verified : 0, 0,
0); 0);
} }
@ -177,7 +178,7 @@ public class ConversationListItem extends RelativeLayout
fromView.setText(getHighlightedSpan(contact.getDisplayName(), highlightSubstring)); fromView.setText(getHighlightedSpan(contact.getDisplayName(), highlightSubstring));
fromView.setCompoundDrawablesWithIntrinsicBounds(0, 0, 0, 0); fromView.setCompoundDrawablesWithIntrinsicBounds(0, 0, 0, 0);
subjectView.setText(getHighlightedSpan(contact.getAddr(), highlightSubstring)); subjectView.setVisibility(GONE);
dateView.setText(""); dateView.setText("");
dateView.setCompoundDrawablesWithIntrinsicBounds(0, 0, 0, 0); dateView.setCompoundDrawablesWithIntrinsicBounds(0, 0, 0, 0);
archivedBadgeView.setVisibility(GONE); archivedBadgeView.setVisibility(GONE);
@ -201,6 +202,7 @@ public class ConversationListItem extends RelativeLayout
fromView.setText(recipient, true); fromView.setText(recipient, true);
fromView.setCompoundDrawablesWithIntrinsicBounds(0, 0, 0, 0); fromView.setCompoundDrawablesWithIntrinsicBounds(0, 0, 0, 0);
subjectView.setVisibility(VISIBLE);
subjectView.setText(getHighlightedSpan(messageResult.getSummarytext(512), highlightSubstring)); subjectView.setText(getHighlightedSpan(messageResult.getSummarytext(512), highlightSubstring));
long timestamp = messageResult.getTimestamp(); long timestamp = messageResult.getTimestamp();

20
src/main/java/org/thoughtcrime/securesms/ConversationTitleView.java
View file

@ -68,17 +68,6 @@ public class ConversationTitleView extends RelativeLayout {
title.setText(dcChat.getName()); title.setText(dcChat.getName());
String subtitleStr = null; String subtitleStr = null;
// set icons etc.
int imgLeft = 0;
int imgRight = 0;
if (dcChat.isMuted()) {
imgLeft = R.drawable.ic_volume_off_white_18dp;
}
if (dcChat.isProtected()) {
imgRight = R.drawable.ic_verified;
}
boolean isOnline = false; boolean isOnline = false;
int[] chatContacts = dcContext.getChatContacts(chatId); int[] chatContacts = dcContext.getChatContacts(chatId);
if (dcChat.isMailingList()) { if (dcChat.isMailingList()) {
@ -117,7 +106,8 @@ public class ConversationTitleView extends RelativeLayout {
avatar.setAvatar(glideRequests, new Recipient(getContext(), dcChat), false); avatar.setAvatar(glideRequests, new Recipient(getContext(), dcChat), false);
avatar.setSeenRecently(isOnline); avatar.setSeenRecently(isOnline);
title.setCompoundDrawablesWithIntrinsicBounds(imgLeft, 0, imgRight, 0); int imgLeft = dcChat.isMuted()? R.drawable.ic_volume_off_white_18dp : 0;
title.setCompoundDrawablesWithIntrinsicBounds(imgLeft, 0, 0, 0);
if (!TextUtils.isEmpty(subtitleStr)) { if (!TextUtils.isEmpty(subtitleStr)) {
subtitle.setText(subtitleStr); subtitle.setText(subtitleStr);
subtitle.setVisibility(View.VISIBLE); subtitle.setVisibility(View.VISIBLE);
@ -135,13 +125,7 @@ public class ConversationTitleView extends RelativeLayout {
avatar.setAvatar(glideRequests, new Recipient(getContext(), contact), false); avatar.setAvatar(glideRequests, new Recipient(getContext(), contact), false);
avatar.setSeenRecently(contact.wasSeenRecently()); avatar.setSeenRecently(contact.wasSeenRecently());
int imgRight = 0;
if (contact.isVerified()) {
imgRight = R.drawable.ic_verified;
}
title.setText(contact.getDisplayName()); title.setText(contact.getDisplayName());
title.setCompoundDrawablesWithIntrinsicBounds(0, 0, imgRight, 0);
subtitle.setText(contact.getAddr()); subtitle.setText(contact.getAddr());
subtitle.setVisibility(View.VISIBLE); subtitle.setVisibility(View.VISIBLE);
} }

12
src/main/java/org/thoughtcrime/securesms/ConversationUpdateItem.java
View file

@ -26,7 +26,6 @@ public class ConversationUpdateItem extends BaseConversationItem
{ {
private DeliveryStatusView deliveryStatusView; private DeliveryStatusView deliveryStatusView;
private AppCompatImageView appIcon; private AppCompatImageView appIcon;
private AppCompatImageView verifiedIcon;
private int textColor; private int textColor;
public ConversationUpdateItem(Context context) { public ConversationUpdateItem(Context context) {
@ -46,7 +45,6 @@ public class ConversationUpdateItem extends BaseConversationItem
bodyText = findViewById(R.id.conversation_update_body); bodyText = findViewById(R.id.conversation_update_body);
deliveryStatusView = new DeliveryStatusView(findViewById(R.id.delivery_indicator)); deliveryStatusView = new DeliveryStatusView(findViewById(R.id.delivery_indicator));
appIcon = findViewById(R.id.app_icon); appIcon = findViewById(R.id.app_icon);
verifiedIcon = findViewById(R.id.verified_icon);
bodyText.setOnLongClickListener(passthroughClickListener); bodyText.setOnLongClickListener(passthroughClickListener);
@ -113,16 +111,6 @@ public class ConversationUpdateItem extends BaseConversationItem
appIcon.setVisibility(GONE); appIcon.setVisibility(GONE);
} }
if (infoType == DcMsg.DC_INFO_PROTECTION_ENABLED) {
verifiedIcon.setVisibility(VISIBLE);
verifiedIcon.setImageResource(R.drawable.ic_verified);
} else if (infoType == DcMsg.DC_INFO_PROTECTION_DISABLED) {
verifiedIcon.setVisibility(VISIBLE);
verifiedIcon.setImageResource(R.drawable.ic_verified_broken);
} else {
verifiedIcon.setVisibility(GONE);
}
bodyText.setText(messageRecord.getDisplayBody()); bodyText.setText(messageRecord.getDisplayBody());
bodyText.setVisibility(VISIBLE); bodyText.setVisibility(VISIBLE);

27
src/main/java/org/thoughtcrime/securesms/GroupCreateActivity.java
View file

@ -50,6 +50,7 @@ public class GroupCreateActivity extends PassphraseRequiredActionBarActivity
public static final String EDIT_GROUP_CHAT_ID = "edit_group_chat_id"; public static final String EDIT_GROUP_CHAT_ID = "edit_group_chat_id";
public static final String CREATE_BROADCAST = "create_broadcast"; public static final String CREATE_BROADCAST = "create_broadcast";
public static final String UNENCRYPTED = "unencrypted";
public static final String CLONE_CHAT_EXTRA = "clone_chat"; public static final String CLONE_CHAT_EXTRA = "clone_chat";
private static final int PICK_CONTACT = 1; private static final int PICK_CONTACT = 1;
@ -59,6 +60,7 @@ public class GroupCreateActivity extends PassphraseRequiredActionBarActivity
private DcContext dcContext; private DcContext dcContext;
private boolean verified; private boolean verified;
private boolean unencrypted;
private boolean broadcast; private boolean broadcast;
private EditText groupName; private EditText groupName;
private ListView lv; private ListView lv;
@ -76,6 +78,7 @@ public class GroupCreateActivity extends PassphraseRequiredActionBarActivity
setContentView(R.layout.group_create_activity); setContentView(R.layout.group_create_activity);
verified = false; verified = false;
broadcast = getIntent().getBooleanExtra(CREATE_BROADCAST, false); broadcast = getIntent().getBooleanExtra(CREATE_BROADCAST, false);
unencrypted = getIntent().getBooleanExtra(UNENCRYPTED, false);
Objects.requireNonNull(getSupportActionBar()).setDisplayHomeAsUpEnabled(true); Objects.requireNonNull(getSupportActionBar()).setDisplayHomeAsUpEnabled(true);
getSupportActionBar().setHomeAsUpIndicator(R.drawable.ic_close_white_24dp); getSupportActionBar().setHomeAsUpIndicator(R.drawable.ic_close_white_24dp);
@ -90,11 +93,14 @@ public class GroupCreateActivity extends PassphraseRequiredActionBarActivity
DcChat dcChat = dcContext.getChat(groupChatId); DcChat dcChat = dcContext.getChat(groupChatId);
verified = dcChat.isProtected(); verified = dcChat.isProtected();
broadcast = dcChat.isOutBroadcast(); broadcast = dcChat.isOutBroadcast();
unencrypted = !dcChat.isEncrypted();
} }
int chatId = getIntent().getIntExtra(CLONE_CHAT_EXTRA, 0); int chatId = getIntent().getIntExtra(CLONE_CHAT_EXTRA, 0);
if (chatId != 0) { if (chatId != 0) {
broadcast = dcContext.getChat(chatId).isOutBroadcast(); DcChat dcChat = dcContext.getChat(chatId);
broadcast = dcChat.isOutBroadcast();
unencrypted = !dcChat.isEncrypted();
} }
initializeResources(); initializeResources();
@ -123,6 +129,9 @@ public class GroupCreateActivity extends PassphraseRequiredActionBarActivity
else if(broadcast) { else if(broadcast) {
title = getString(R.string.new_channel); title = getString(R.string.new_channel);
} }
else if(unencrypted) {
title = getString(R.string.new_email);
}
else { else {
title = getString(R.string.menu_new_group); title = getString(R.string.menu_new_group);
} }
@ -137,7 +146,7 @@ public class GroupCreateActivity extends PassphraseRequiredActionBarActivity
initializeAvatarView(); initializeAvatarView();
SelectedContactsAdapter adapter = new SelectedContactsAdapter(this, GlideApp.with(this), broadcast); SelectedContactsAdapter adapter = new SelectedContactsAdapter(this, GlideApp.with(this), broadcast, unencrypted);
adapter.setItemClickListener(this); adapter.setItemClickListener(this);
lv.setAdapter(adapter); lv.setAdapter(adapter);
@ -163,6 +172,10 @@ public class GroupCreateActivity extends PassphraseRequiredActionBarActivity
if (broadcast) { if (broadcast) {
groupName.setHint(R.string.channel_name); groupName.setHint(R.string.channel_name);
chatHints.setVisibility(View.VISIBLE); chatHints.setVisibility(View.VISIBLE);
} else if (unencrypted) {
avatar.setVisibility(View.GONE);
groupName.setHint(R.string.subject);
chatHints.setVisibility(View.GONE);
} else { } else {
chatHints.setVisibility(View.GONE); chatHints.setVisibility(View.GONE);
} }
@ -219,7 +232,7 @@ public class GroupCreateActivity extends PassphraseRequiredActionBarActivity
if (groupChatId != 0) { if (groupChatId != 0) {
updateGroup(groupName); updateGroup(groupName);
} else { } else {
verified = !broadcast && allMembersVerified(); verified = !unencrypted && !broadcast && allMembersVerified();
createGroup(groupName); createGroup(groupName);
} }
@ -244,6 +257,7 @@ public class GroupCreateActivity extends PassphraseRequiredActionBarActivity
if (contactId == DcContact.DC_CONTACT_ID_ADD_MEMBER) { if (contactId == DcContact.DC_CONTACT_ID_ADD_MEMBER) {
Intent intent = new Intent(this, ContactMultiSelectionActivity.class); Intent intent = new Intent(this, ContactMultiSelectionActivity.class);
intent.putExtra(ContactSelectionListFragment.SELECT_VERIFIED_EXTRA, verified); intent.putExtra(ContactSelectionListFragment.SELECT_VERIFIED_EXTRA, verified);
intent.putExtra(ContactSelectionListFragment.SELECT_UNENCRYPTED_EXTRA, unencrypted);
ArrayList<Integer> preselectedContacts = new ArrayList<>(getAdapter().getContacts()); ArrayList<Integer> preselectedContacts = new ArrayList<>(getAdapter().getContacts());
intent.putExtra(ContactSelectionListFragment.PRESELECTED_CONTACTS, preselectedContacts); intent.putExtra(ContactSelectionListFragment.PRESELECTED_CONTACTS, preselectedContacts);
startActivityForResult(intent, PICK_CONTACT); startActivityForResult(intent, PICK_CONTACT);
@ -263,6 +277,13 @@ public class GroupCreateActivity extends PassphraseRequiredActionBarActivity
e.printStackTrace(); e.printStackTrace();
return; return;
} }
} else if (unencrypted) {
try {
groupChatId = DcHelper.getRpc(this).createGroupChatUnencrypted(dcContext.getAccountId(), groupName);
} catch (RpcException e) {
e.printStackTrace();
return;
}
} else { } else {
groupChatId = dcContext.createGroupChat(verified, groupName); groupChatId = dcContext.createGroupChat(verified, groupName);
} }

2
src/main/java/org/thoughtcrime/securesms/MediaPreviewActivity.java
View file

@ -359,7 +359,7 @@ public class MediaPreviewActivity extends PassphraseRequiredActionBarActivity
finish(); finish();
}); });
if(dcChat.canSend() && !dcChat.isSelfTalk() && dcMsg.isOutgoing()) { if(dcChat.isEncrypted() && dcChat.canSend() && !dcChat.isSelfTalk() && dcMsg.isOutgoing()) {
builder.setNegativeButton(R.string.delete_for_everyone, (d, which) -> { builder.setNegativeButton(R.string.delete_for_everyone, (d, which) -> {
Util.runOnAnyBackgroundThread(() -> dcContext.sendDeleteRequest(messageIds)); Util.runOnAnyBackgroundThread(() -> dcContext.sendDeleteRequest(messageIds));
finish(); finish();

2
src/main/java/org/thoughtcrime/securesms/MessageSelectorFragment.java
View file

@ -64,7 +64,7 @@ public abstract class MessageSelectorFragment
protected void handleDeleteMessages(int chatId, final int[] messageIds) { protected void handleDeleteMessages(int chatId, final int[] messageIds) {
DcChat dcChat = dcContext.getChat(chatId); DcChat dcChat = dcContext.getChat(chatId);
boolean canDeleteForAll = true; boolean canDeleteForAll = true;
if (dcChat.canSend() && !dcChat.isSelfTalk()) { if (dcChat.isEncrypted() && dcChat.canSend() && !dcChat.isSelfTalk()) {
for(int msgId : messageIds) { for(int msgId : messageIds) {
DcMsg msg = dcContext.getMsg(msgId); DcMsg msg = dcContext.getMsg(msgId);
if (!msg.isOutgoing() || msg.isInfo()) { if (!msg.isOutgoing() || msg.isInfo()) {

4
src/main/java/org/thoughtcrime/securesms/NewConversationActivity.java
View file

@ -102,6 +102,10 @@ public class NewConversationActivity extends ContactSelectionActivity {
public void onContactSelected(int contactId) { public void onContactSelected(int contactId) {
if(contactId == DcContact.DC_CONTACT_ID_NEW_GROUP) { if(contactId == DcContact.DC_CONTACT_ID_NEW_GROUP) {
startActivity(new Intent(this, GroupCreateActivity.class)); startActivity(new Intent(this, GroupCreateActivity.class));
} else if(contactId == DcContact.DC_CONTACT_ID_NEW_UNENCRYPTED_GROUP) {
Intent intent = new Intent(this, GroupCreateActivity.class);
intent.putExtra(GroupCreateActivity.UNENCRYPTED, true);
startActivity(intent);
} else if(contactId == DcContact.DC_CONTACT_ID_NEW_BROADCAST) { } else if(contactId == DcContact.DC_CONTACT_ID_NEW_BROADCAST) {
Intent intent = new Intent(this, GroupCreateActivity.class); Intent intent = new Intent(this, GroupCreateActivity.class);
intent.putExtra(GroupCreateActivity.CREATE_BROADCAST, true); intent.putExtra(GroupCreateActivity.CREATE_BROADCAST, true);

11
src/main/java/org/thoughtcrime/securesms/ProfileActivity.java
View file

@ -315,10 +315,12 @@ public class ProfileActivity extends PassphraseRequiredActionBarActivity
String profileImagePath; String profileImagePath;
String title; String title;
Uri profileImageUri; Uri profileImageUri;
boolean enlargeAvatar = true;
if(chatId!=0) { if(chatId!=0) {
DcChat dcChat = dcContext.getChat(chatId); DcChat dcChat = dcContext.getChat(chatId);
profileImagePath = dcChat.getProfileImage(); profileImagePath = dcChat.getProfileImage();
title = dcChat.getName(); title = dcChat.getName();
enlargeAvatar = dcChat.isEncrypted() && !dcChat.isSelfTalk() && !dcChat.isDeviceTalk();
} else { } else {
DcContact dcContact = dcContext.getContact(contactId); DcContact dcContact = dcContext.getContact(contactId);
profileImagePath = dcContact.getProfileImage(); profileImagePath = dcContact.getProfileImage();
@ -327,7 +329,7 @@ public class ProfileActivity extends PassphraseRequiredActionBarActivity
File file = new File(profileImagePath); File file = new File(profileImagePath);
if (file.exists()) { if (enlargeAvatar && file.exists()) {
profileImageUri = Uri.fromFile(file); profileImageUri = Uri.fromFile(file);
String type = "image/" + profileImagePath.substring(profileImagePath.lastIndexOf(".") + 1); String type = "image/" + profileImagePath.substring(profileImagePath.lastIndexOf(".") + 1);
@ -388,7 +390,12 @@ public class ProfileActivity extends PassphraseRequiredActionBarActivity
private void onShare() { private void onShare() {
Intent composeIntent = new Intent(); Intent composeIntent = new Intent();
RelayUtil.setSharedContactId(composeIntent, contactId); DcContact dcContact = dcContext.getContact(contactId);
if (dcContact.isKeyContact()) {
RelayUtil.setSharedContactId(composeIntent, contactId);
} else {
RelayUtil.setSharedText(composeIntent, dcContact.getAddr());
}
ConversationListRelayingActivity.start(this, composeIntent); ConversationListRelayingActivity.start(this, composeIntent);
} }

8
src/main/java/org/thoughtcrime/securesms/ProfileAdapter.java
View file

@ -210,7 +210,8 @@ public class ProfileAdapter extends RecyclerView.Adapter
else if(holder.itemView instanceof ProfileTextItem) { else if(holder.itemView instanceof ProfileTextItem) {
ProfileTextItem item = (ProfileTextItem) holder.itemView; ProfileTextItem item = (ProfileTextItem) holder.itemView;
item.setOnClickListener(view -> clickListener.onSettingsClicked(data.viewType)); item.setOnClickListener(view -> clickListener.onSettingsClicked(data.viewType));
item.set(data.label, data.icon); boolean tintIcon = data.viewType != ITEM_INTRODUCED_BY;
item.set(data.label, data.icon, tintIcon);
if (data.viewType == ITEM_LAST_SEEN || data.viewType == ITEM_ADDRESS) { if (data.viewType == ITEM_LAST_SEEN || data.viewType == ITEM_ADDRESS) {
int padding = (int)((float)context.getResources().getDimensionPixelSize(R.dimen.contact_list_normal_padding) * 1.2); int padding = (int)((float)context.getResources().getDimensionPixelSize(R.dimen.contact_list_normal_padding) * 1.2);
item.setPadding(item.getPaddingLeft(), item.getPaddingTop(), item.getPaddingRight(), padding); item.setPadding(item.getPaddingLeft(), item.getPaddingTop(), item.getPaddingRight(), padding);
@ -339,7 +340,10 @@ public class ProfileAdapter extends RecyclerView.Adapter
} else { } else {
introducedBy = context.getString(R.string.verified_by, dcContext.getContact(verifierId).getDisplayName()); introducedBy = context.getString(R.string.verified_by, dcContext.getContact(verifierId).getDisplayName());
} }
itemData.add(new ItemData(ITEM_INTRODUCED_BY, introducedBy, 0)); itemData.add(new ItemData(ITEM_INTRODUCED_BY, introducedBy, dcContact.isVerified()? R.drawable.ic_verified : 0));
} else if (dcContact.isVerified()) {
String introducedBy = context.getString(R.string.verified_by_unknown);
itemData.add(new ItemData(ITEM_INTRODUCED_BY, introducedBy, R.drawable.ic_verified));
} }
if (dcContact != null) { if (dcContact != null) {

4
src/main/java/org/thoughtcrime/securesms/ProfileAvatarItem.java
View file

@ -50,12 +50,10 @@ public class ProfileAvatarItem extends LinearLayout implements RecipientModified
this.glideRequests = glideRequests; this.glideRequests = glideRequests;
String name = ""; String name = "";
boolean greenCheckmark = false;
String subtitle = null; String subtitle = null;
if (dcChat != null) { if (dcChat != null) {
recipient = new Recipient(getContext(), dcChat); recipient = new Recipient(getContext(), dcChat);
name = dcChat.getName(); name = dcChat.getName();
greenCheckmark = dcChat.isProtected();
if (dcChat.isMailingList()) { if (dcChat.isMailingList()) {
subtitle = dcChat.getMailinglistAddr(); subtitle = dcChat.getMailinglistAddr();
@ -67,7 +65,6 @@ public class ProfileAvatarItem extends LinearLayout implements RecipientModified
} else if (dcContact != null) { } else if (dcContact != null) {
recipient = new Recipient(getContext(), dcContact); recipient = new Recipient(getContext(), dcContact);
name = dcContact.getDisplayName(); name = dcContact.getDisplayName();
greenCheckmark = dcContact.isVerified();
} }
recipient.addListener(this); recipient.addListener(this);
@ -75,7 +72,6 @@ public class ProfileAvatarItem extends LinearLayout implements RecipientModified
avatarView.setSeenRecently(dcContact != null && dcContact.wasSeenRecently()); avatarView.setSeenRecently(dcContact != null && dcContact.wasSeenRecently());
nameView.setText(name); nameView.setText(name);
nameView.setCompoundDrawablesWithIntrinsicBounds(0,0, greenCheckmark ? R.drawable.ic_verified : 0, 0);
if (subtitle != null) { if (subtitle != null) {
subtitleView.setVisibility(View.VISIBLE); subtitleView.setVisibility(View.VISIBLE);

6
src/main/java/org/thoughtcrime/securesms/ProfileTextItem.java
View file

@ -34,7 +34,7 @@ public class ProfileTextItem extends LinearLayout {
valueView = findViewById(R.id.value); valueView = findViewById(R.id.value);
} }
public void set(String label, int icon) { public void set(String label, int icon, boolean tint) {
labelView.setText(label); labelView.setText(label);
if (icon != 0) { if (icon != 0) {
@ -42,7 +42,9 @@ public class ProfileTextItem extends LinearLayout {
if (orgDrawable != null) { if (orgDrawable != null) {
Drawable drawable = orgDrawable.mutate(); // avoid global state modification and showing eg. app-icon tinted also elsewhere Drawable drawable = orgDrawable.mutate(); // avoid global state modification and showing eg. app-icon tinted also elsewhere
drawable = DrawableCompat.wrap(drawable); drawable = DrawableCompat.wrap(drawable);
DrawableCompat.setTint(drawable, getResources().getColor(R.color.delta_accent)); if (tint) {
DrawableCompat.setTint(drawable, getResources().getColor(R.color.delta_accent));
}
labelView.setCompoundDrawablesWithIntrinsicBounds(drawable, null, null, null); labelView.setCompoundDrawablesWithIntrinsicBounds(drawable, null, null, null);
} }
} }

5
src/main/java/org/thoughtcrime/securesms/connect/DcContactsLoader.java
View file

@ -51,8 +51,13 @@ public class DcContactsLoader extends AsyncLoader<DcContactsLoader.Ret> {
} }
if (query == null && addCreateGroupLinks) { if (query == null && addCreateGroupLinks) {
additional_items = Util.appendInt(additional_items, DcContact.DC_CONTACT_ID_NEW_GROUP); additional_items = Util.appendInt(additional_items, DcContact.DC_CONTACT_ID_NEW_GROUP);
final boolean broadcastsEnabled = Prefs.isNewBroadcastAvailable(getContext()); final boolean broadcastsEnabled = Prefs.isNewBroadcastAvailable(getContext());
if (broadcastsEnabled) additional_items = Util.appendInt(additional_items, DcContact.DC_CONTACT_ID_NEW_BROADCAST); if (broadcastsEnabled) additional_items = Util.appendInt(additional_items, DcContact.DC_CONTACT_ID_NEW_BROADCAST);
if (!dcContext.isChatmail()) {
additional_items = Util.appendInt(additional_items, DcContact.DC_CONTACT_ID_NEW_UNENCRYPTED_GROUP);
}
} }
int[] all_ids = new int[contact_ids.length + additional_items.length]; int[] all_ids = new int[contact_ids.length + additional_items.length];
System.arraycopy(additional_items, 0, all_ids, 0, additional_items.length); System.arraycopy(additional_items, 0, all_ids, 0, additional_items.length);

23
src/main/java/org/thoughtcrime/securesms/connect/DcHelper.java
View file

@ -152,11 +152,8 @@ public class DcHelper {
dcContext.setStockTranslation(11, context.getString(R.string.audio)); dcContext.setStockTranslation(11, context.getString(R.string.audio));
dcContext.setStockTranslation(12, context.getString(R.string.file)); dcContext.setStockTranslation(12, context.getString(R.string.file));
dcContext.setStockTranslation(23, context.getString(R.string.gif)); dcContext.setStockTranslation(23, context.getString(R.string.gif));
dcContext.setStockTranslation(24, context.getString(R.string.encrypted_message));
dcContext.setStockTranslation(29, context.getString(R.string.systemmsg_cannot_decrypt)); dcContext.setStockTranslation(29, context.getString(R.string.systemmsg_cannot_decrypt));
dcContext.setStockTranslation(35, context.getString(R.string.contact_verified)); dcContext.setStockTranslation(35, context.getString(R.string.contact_verified));
dcContext.setStockTranslation(36, context.getString(R.string.contact_not_verified));
dcContext.setStockTranslation(37, context.getString(R.string.contact_setup_changed));
dcContext.setStockTranslation(40, context.getString(R.string.chat_archived_label)); dcContext.setStockTranslation(40, context.getString(R.string.chat_archived_label));
dcContext.setStockTranslation(60, context.getString(R.string.login_error_cannot_login)); dcContext.setStockTranslation(60, context.getString(R.string.login_error_cannot_login));
dcContext.setStockTranslation(66, context.getString(R.string.location)); dcContext.setStockTranslation(66, context.getString(R.string.location));
@ -190,7 +187,6 @@ public class DcHelper {
dcContext.setStockTranslation(112, context.getString(R.string.error_x)); dcContext.setStockTranslation(112, context.getString(R.string.error_x));
dcContext.setStockTranslation(113, context.getString(R.string.not_supported_by_provider)); dcContext.setStockTranslation(113, context.getString(R.string.not_supported_by_provider));
dcContext.setStockTranslation(114, context.getString(R.string.messages)); dcContext.setStockTranslation(114, context.getString(R.string.messages));
dcContext.setStockTranslation(115, context.getString(R.string.channel));
dcContext.setStockTranslation(116, context.getString(R.string.part_of_total_used)); dcContext.setStockTranslation(116, context.getString(R.string.part_of_total_used));
dcContext.setStockTranslation(117, context.getString(R.string.secure_join_started)); dcContext.setStockTranslation(117, context.getString(R.string.secure_join_started));
dcContext.setStockTranslation(118, context.getString(R.string.secure_join_replies)); dcContext.setStockTranslation(118, context.getString(R.string.secure_join_replies));
@ -236,22 +232,15 @@ public class DcHelper {
// cmp. https://github.com/deltachat/deltachat-android/issues/2187 // cmp. https://github.com/deltachat/deltachat-android/issues/2187
dcContext.setStockTranslation(120, context.getString(R.string.qrshow_join_group_hint).replace("\"", "")); dcContext.setStockTranslation(120, context.getString(R.string.qrshow_join_group_hint).replace("\"", ""));
dcContext.setStockTranslation(121, context.getString(R.string.connectivity_not_connected)); dcContext.setStockTranslation(121, context.getString(R.string.connectivity_not_connected));
dcContext.setStockTranslation(122, context.getString(R.string.aeap_addr_changed));
dcContext.setStockTranslation(162, context.getString(R.string.multidevice_qr_subtitle)); dcContext.setStockTranslation(162, context.getString(R.string.multidevice_qr_subtitle));
dcContext.setStockTranslation(163, context.getString(R.string.multidevice_transfer_done_devicemsg)); dcContext.setStockTranslation(163, context.getString(R.string.multidevice_transfer_done_devicemsg));
// The next two strings should only be set if the UI actually shows more info when the user clicks on the
// DC_INFO_PROTECTION_{EN|DIS}ABLED info message
dcContext.setStockTranslation(170, context.getString(R.string.chat_protection_enabled_tap_to_learn_more)); dcContext.setStockTranslation(170, context.getString(R.string.chat_protection_enabled_tap_to_learn_more));
dcContext.setStockTranslation(171, context.getString(R.string.chat_protection_broken_tap_to_learn_more));
dcContext.setStockTranslation(172, context.getString(R.string.chat_new_group_hint)); dcContext.setStockTranslation(172, context.getString(R.string.chat_new_group_hint));
dcContext.setStockTranslation(173, context.getString(R.string.member_x_added)); dcContext.setStockTranslation(173, context.getString(R.string.member_x_added));
dcContext.setStockTranslation(174, context.getString(R.string.invalid_unencrypted_tap_to_learn_more)); dcContext.setStockTranslation(174, context.getString(R.string.invalid_unencrypted_tap_to_learn_more));
dcContext.setStockTranslation(176, context.getString(R.string.reaction_by_you)); dcContext.setStockTranslation(176, context.getString(R.string.reaction_by_you));
dcContext.setStockTranslation(177, context.getString(R.string.reaction_by_other)); dcContext.setStockTranslation(177, context.getString(R.string.reaction_by_other));
dcContext.setStockTranslation(190, context.getString(R.string.secure_join_wait)); dcContext.setStockTranslation(190, context.getString(R.string.secure_join_wait));
dcContext.setStockTranslation(192, context.getString(R.string.secure_join_takes_longer));
dcContext.setStockTranslation(193, context.getString(R.string.donate_device_msg)); dcContext.setStockTranslation(193, context.getString(R.string.donate_device_msg));
} }
@ -464,20 +453,10 @@ public class DcHelper {
} }
} }
public static void showVerificationBrokenDialog(Context context, String name) {
new AlertDialog.Builder(context)
.setMessage(context.getString(R.string.chat_protection_broken_explanation, name))
.setNeutralButton(R.string.learn_more, (d, w) -> openHelp(context, "#nocryptanymore"))
.setNegativeButton(R.string.qrscan_title, (d, w) -> context.startActivity(new Intent(context, QrActivity.class)))
.setPositiveButton(R.string.ok, null)
.setCancelable(true)
.show();
}
public static void showProtectionEnabledDialog(Context context) { public static void showProtectionEnabledDialog(Context context) {
new AlertDialog.Builder(context) new AlertDialog.Builder(context)
.setMessage(context.getString(R.string.chat_protection_enabled_explanation)) .setMessage(context.getString(R.string.chat_protection_enabled_explanation))
.setNeutralButton(R.string.learn_more, (d, w) -> openHelp(context, "#e2eeguarantee")) .setNeutralButton(R.string.learn_more, (d, w) -> openHelp(context, "#e2ee"))
.setPositiveButton(R.string.ok, null) .setPositiveButton(R.string.ok, null)
.setCancelable(true) .setCancelable(true)
.show(); .show();

2
src/main/java/org/thoughtcrime/securesms/contacts/ContactSelectionListAdapter.java
View file

@ -268,6 +268,8 @@ public class ContactSelectionListAdapter extends RecyclerView.Adapter<ContactSel
itemMultiSelect = false; // the item creates a new contact in the list that will be selected instead itemMultiSelect = false; // the item creates a new contact in the list that will be selected instead
} else if (id == DcContact.DC_CONTACT_ID_NEW_GROUP) { } else if (id == DcContact.DC_CONTACT_ID_NEW_GROUP) {
name = context.getString(R.string.menu_new_group); name = context.getString(R.string.menu_new_group);
} else if (id == DcContact.DC_CONTACT_ID_NEW_UNENCRYPTED_GROUP) {
name = context.getString(R.string.new_email);
} else if (id == DcContact.DC_CONTACT_ID_NEW_BROADCAST) { } else if (id == DcContact.DC_CONTACT_ID_NEW_BROADCAST) {
name = context.getString(R.string.new_channel); name = context.getString(R.string.new_channel);
} else if (id == DcContact.DC_CONTACT_ID_QR_INVITE) { } else if (id == DcContact.DC_CONTACT_ID_QR_INVITE) {

12
src/main/java/org/thoughtcrime/securesms/contacts/ContactSelectionListItem.java
View file

@ -64,9 +64,12 @@ public class ContactSelectionListItem extends LinearLayout implements RecipientM
this.name = name; this.name = name;
this.number = number; this.number = number;
if (specialId==DcContact.DC_CONTACT_ID_NEW_CLASSIC_CONTACT || specialId==DcContact.DC_CONTACT_ID_NEW_GROUP if (specialId==DcContact.DC_CONTACT_ID_NEW_CLASSIC_CONTACT
|| specialId==DcContact.DC_CONTACT_ID_NEW_GROUP
|| specialId==DcContact.DC_CONTACT_ID_NEW_UNENCRYPTED_GROUP
|| specialId==DcContact.DC_CONTACT_ID_NEW_BROADCAST || specialId==DcContact.DC_CONTACT_ID_NEW_BROADCAST
|| specialId==DcContact.DC_CONTACT_ID_ADD_MEMBER || specialId==DcContact.DC_CONTACT_ID_QR_INVITE) { || specialId==DcContact.DC_CONTACT_ID_ADD_MEMBER
|| specialId==DcContact.DC_CONTACT_ID_QR_INVITE) {
this.nameView.setTypeface(null, Typeface.BOLD); this.nameView.setTypeface(null, Typeface.BOLD);
} }
else { else {
@ -120,11 +123,6 @@ public class ContactSelectionListItem extends LinearLayout implements RecipientM
else { else {
this.numberContainer.setVisibility(View.GONE); this.numberContainer.setVisibility(View.GONE);
} }
if (contact != null && contact.isVerified()) {
nameView.setCompoundDrawablesWithIntrinsicBounds(0,0,R.drawable.ic_verified,0);
} else {
nameView.setCompoundDrawablesWithIntrinsicBounds(0,0, 0,0);
}
} }
public int getSpecialId() { public int getSpecialId() {

7
src/main/java/org/thoughtcrime/securesms/util/LongClickCopySpan.java
View file

@ -58,7 +58,12 @@ public class LongClickCopySpan extends ClickableSpan {
String addr = prepareUrl(url); String addr = prepareUrl(url);
Activity activity = (Activity) widget.getContext(); Activity activity = (Activity) widget.getContext();
DcContext dcContext = DcHelper.getContext(activity); DcContext dcContext = DcHelper.getContext(activity);
DcContact contact = dcContext.getContact(dcContext.createContact(null, addr));
int contactId = dcContext.lookupContactIdByAddr(addr);
if (contactId == 0 && dcContext.mayBeValidAddr(addr)) {
contactId = dcContext.createContact(null, addr);
}
DcContact contact = dcContext.getContact(contactId);
if (contact.getId() != 0 && !contact.isBlocked() && dcContext.getChatIdByContactId(contact.getId()) != 0) { if (contact.getId() != 0 && !contact.isBlocked() && dcContext.getChatIdByContactId(contact.getId()) != 0) {
openChat(activity, contact); openChat(activity, contact);
} else { } else {

9
src/main/java/org/thoughtcrime/securesms/util/SelectedContactsAdapter.java
View file

@ -37,16 +37,18 @@ public class SelectedContactsAdapter extends BaseAdapter {
@Nullable private ItemClickListener itemClickListener; @Nullable private ItemClickListener itemClickListener;
@NonNull private final List<Integer> contacts = new LinkedList<>(); @NonNull private final List<Integer> contacts = new LinkedList<>();
private final boolean isBroadcast; private final boolean isBroadcast;
private final boolean isUnencrypted;
@NonNull private final DcContext dcContext; @NonNull private final DcContext dcContext;
@NonNull private final GlideRequests glideRequests; @NonNull private final GlideRequests glideRequests;
public SelectedContactsAdapter(@NonNull Context context, public SelectedContactsAdapter(@NonNull Context context,
@NonNull GlideRequests glideRequests, @NonNull GlideRequests glideRequests,
boolean isBroadcast) boolean isBroadcast, boolean isUnencrypted)
{ {
this.context = context; this.context = context;
this.glideRequests = glideRequests; this.glideRequests = glideRequests;
this.isBroadcast = isBroadcast; this.isBroadcast = isBroadcast;
this.isUnencrypted = isUnencrypted;
this.dcContext = DcHelper.getContext(context); this.dcContext = DcHelper.getContext(context);
} }
@ -109,10 +111,9 @@ public class SelectedContactsAdapter extends BaseAdapter {
final int contactId = (int)getItem(position); final int contactId = (int)getItem(position);
final boolean modifiable = contactId != DC_CONTACT_ID_ADD_MEMBER && contactId != DC_CONTACT_ID_SELF; final boolean modifiable = contactId != DC_CONTACT_ID_ADD_MEMBER && contactId != DC_CONTACT_ID_SELF;
Recipient recipient = null; Recipient recipient = null;
boolean verified = false;
if(contactId == DcContact.DC_CONTACT_ID_ADD_MEMBER) { if(contactId == DcContact.DC_CONTACT_ID_ADD_MEMBER) {
name.setText(context.getString(isBroadcast? R.string.add_recipients : R.string.group_add_members)); name.setText(context.getString(isBroadcast || isUnencrypted? R.string.add_recipients : R.string.group_add_members));
name.setTypeface(null, Typeface.BOLD); name.setTypeface(null, Typeface.BOLD);
phone.setVisibility(View.GONE); phone.setVisibility(View.GONE);
} else { } else {
@ -122,12 +123,10 @@ public class SelectedContactsAdapter extends BaseAdapter {
name.setTypeface(null, Typeface.NORMAL); name.setTypeface(null, Typeface.NORMAL);
phone.setText(dcContact.getAddr()); phone.setText(dcContact.getAddr());
phone.setVisibility(View.VISIBLE); phone.setVisibility(View.VISIBLE);
verified = dcContact.isVerified();
} }
avatar.clear(glideRequests); avatar.clear(glideRequests);
avatar.setAvatar(glideRequests, recipient, false); avatar.setAvatar(glideRequests, recipient, false);
name.setCompoundDrawablesWithIntrinsicBounds(0, 0, verified? R.drawable.ic_verified : 0, 0);
delete.setVisibility(modifiable ? View.VISIBLE : View.GONE); delete.setVisibility(modifiable ? View.VISIBLE : View.GONE);
delete.setColorFilter(DynamicTheme.isDarkTheme(context)? Color.WHITE : Color.BLACK); delete.setColorFilter(DynamicTheme.isDarkTheme(context)? Color.WHITE : Color.BLACK);
delete.setOnClickListener(view -> { delete.setOnClickListener(view -> {

11
src/main/res/drawable/ic_verified_broken.xml
View file

@ -1,11 +0,0 @@
<vector android:height="18sp" android:viewportHeight="1304.4"
android:viewportWidth="1325.6" android:width="18sp" xmlns:android="http://schemas.android.com/apk/res/android">
<path android:fillColor="#ffffff"
android:pathData="M259.8,272.4L1072.6,272.4A0,0 0,0 1,1072.7 272.4L1072.7,1032.2A0,0 0,0 1,1072.6 1032.3L259.8,1032.3A0,0 0,0 1,259.7 1032.2L259.7,272.4A0,0 0,0 1,259.8 272.4z" android:strokeWidth="178.139"/>
<path android:fillColor="#b9b9b9"
android:pathData="M643.6,1303C555.7,1295.1 479.5,1229.9 452.5,1146.8 365.5,1173.3 257.1,1169.4 192.1,1098 135.6,1041.4 126.1,954.9 133.2,879.5 28,840.4 -23.6,710.9 10.9,606.9 31.5,539.3 89.5,491.4 151,461.3 132.5,383.7 109.5,287.3 176.8,208.6 245.9,117.6 351.5,123.1 457,148.5 487.4,54.1 587.2,-8.2 685.1,1.1 768.6,4.6 848,60.7 874.9,140.6c74.6,-12.9 160.9,-20.5 223.1,31.8 50.7,39.9 88.8,99.2 87.8,165.5 0.9,40.1 -11.3,80.4 -17.3,118.5 91,17 150.8,110.4 156,198.8 -1.4,112 -39.9,161.5 -142.2,226.4 -23.1,9.2 -7.6,-23.6 0.1,0.2 15,101.5 -12.8,196.7 -94.3,247 -61.8,38 -138.4,38.2 -207.8,25.9 -31.3,91.2 -125,155 -221.5,149.4 -5.1,0.5 -10.1,-0.7 -15.1,-1.1zM1035.6,509.5 L915.2,385.5 612.9,685.4 411,498.7 289.1,614.8 603.1,931.9Z" android:strokeWidth="1.33333"/>
<path android:fillColor="#00000000"
android:pathData="M64.6,1240 L1265.3,65.5"
android:strokeColor="#ff0c16" android:strokeLineCap="butt"
android:strokeLineJoin="miter" android:strokeWidth="178.139"/>
</vector>

31
src/main/res/layout/conversation_item_footer.xml
View file

@ -1,6 +1,7 @@
<?xml version="1.0" encoding="utf-8"?> <?xml version="1.0" encoding="utf-8"?>
<merge <merge
xmlns:android="http://schemas.android.com/apk/res/android" xmlns:android="http://schemas.android.com/apk/res/android"
xmlns:app="http://schemas.android.com/apk/res-auto"
xmlns:tools="http://schemas.android.com/tools" xmlns:tools="http://schemas.android.com/tools"
android:layout_width="wrap_content" android:layout_width="wrap_content"
android:layout_height="wrap_content" android:layout_height="wrap_content"
@ -15,8 +16,7 @@
android:layout_gravity="center_vertical|end" android:layout_gravity="center_vertical|end"
android:importantForAccessibility="no" android:importantForAccessibility="no"
android:visibility="gone" android:visibility="gone"
tools:visibility="visible" tools:visibility="visible" />
/>
<ImageView <ImageView
android:id="@+id/footer_email_indicator" android:id="@+id/footer_email_indicator"
@ -24,9 +24,10 @@
android:layout_height="11sp" android:layout_height="11sp"
android:src="@drawable/ic_outline_email" android:src="@drawable/ic_outline_email"
android:visibility="gone" android:visibility="gone"
android:layout_marginEnd="5dp"
android:layout_gravity="center_vertical|end" android:layout_gravity="center_vertical|end"
android:importantForAccessibility="no" android:importantForAccessibility="no"
tools:visibility="visible"/> tools:visibility="visible" />
<TextView <TextView
android:id="@+id/footer_edited" android:id="@+id/footer_edited"
@ -37,9 +38,9 @@
style="@style/Signal.Text.Caption.MessageSent" style="@style/Signal.Text.Caption.MessageSent"
android:textColor="?conversation_item_outgoing_text_secondary_color" android:textColor="?conversation_item_outgoing_text_secondary_color"
android:text="@string/edited" android:text="@string/edited"
android:paddingEnd="5dp" android:layout_marginEnd="5dp"
android:visibility="gone" android:visibility="gone"
tools:visibility="visible"/> tools:visibility="visible" />
<TextView <TextView
android:id="@+id/footer_date" android:id="@+id/footer_date"
@ -49,7 +50,7 @@
android:linksClickable="false" android:linksClickable="false"
style="@style/Signal.Text.Caption.MessageSent" style="@style/Signal.Text.Caption.MessageSent"
android:textColor="?conversation_item_outgoing_text_secondary_color" android:textColor="?conversation_item_outgoing_text_secondary_color"
tools:text="30 mins"/> tools:text="30 mins" />
<ImageView <ImageView
android:id="@+id/footer_location_indicator" android:id="@+id/footer_location_indicator"
@ -59,14 +60,16 @@
android:visibility="gone" android:visibility="gone"
android:layout_gravity="center_vertical|end" android:layout_gravity="center_vertical|end"
android:contentDescription="@string/location" android:contentDescription="@string/location"
tools:visibility="gone"/> tools:visibility="gone" />
<ImageView android:id="@+id/delivery_indicator" <ImageView
android:layout_width="wrap_content" android:id="@+id/delivery_indicator"
android:layout_height="wrap_content" android:layout_width="wrap_content"
android:layout_gravity="center_vertical|end" android:layout_height="wrap_content"
android:layout_marginLeft="6dp" android:layout_gravity="center_vertical|end"
android:tint="?attr/conversation_item_outgoing_text_secondary_color" android:layout_marginStart="6dp"
android:visibility="gone" /> android:contentDescription="@null"
android:visibility="gone"
app:tint="?attr/conversation_item_outgoing_text_secondary_color" />
</merge> </merge>

9
src/main/res/layout/conversation_item_update.xml
View file

@ -13,15 +13,6 @@
android:paddingLeft="28dp" android:paddingLeft="28dp"
android:paddingRight="28dp"> android:paddingRight="28dp">
<androidx.appcompat.widget.AppCompatImageView
android:id="@+id/verified_icon"
android:layout_width="match_parent"
android:layout_height="70dp"
android:layout_gravity="center_vertical"
tools:src="@drawable/ic_verified"
android:padding="7dp"
android:visibility="gone" />
<LinearLayout <LinearLayout
android:layout_width="wrap_content" android:layout_width="wrap_content"
android:layout_height="wrap_content" android:layout_height="wrap_content"

1
src/main/res/layout/profile_text_item_small.xml
View file

@ -16,6 +16,7 @@
android:layout_height="wrap_content" android:layout_height="wrap_content"
android:layout_weight="1" android:layout_weight="1"
android:gravity="start|center_vertical" android:gravity="start|center_vertical"
android:drawablePadding="5dp"
android:textSize="16sp" android:textSize="16sp"
android:textColor="?attr/conversation_list_item_contact_color" /> android:textColor="?attr/conversation_list_item_contact_color" />

2
src/main/res/menu/group_create.xml
View file

@ -2,7 +2,7 @@
<menu xmlns:android="http://schemas.android.com/apk/res/android" xmlns:app="http://schemas.android.com/apk/res-auto"> <menu xmlns:android="http://schemas.android.com/apk/res/android" xmlns:app="http://schemas.android.com/apk/res-auto">
<item android:title="@string/group_create_button" <item android:title="@string/perm_continue"
android:id="@+id/menu_create_group" android:id="@+id/menu_create_group"
android:icon="?menu_accept_icon" android:icon="?menu_accept_icon"
app:showAsAction="always|withText"/> app:showAsAction="always|withText"/>

2
src/main/res/values-ar/strings.xml
View file

@ -205,7 +205,7 @@
<!-- permissions --> <!-- permissions -->
<string name="perm_required_title">منح إحدى الأذونات مطلو</string> <string name="perm_required_title">منح إحدى الأذونات مطلو</string>
<string name="perm_continue">استمر</string> <string name="perm_continue">استمر</string>
<!-- dc_str_* resources --> <!-- deprecated, use string "E-Mail" for non-encrypted messages instead -->
<string name="encrypted_message">رسالة مشفرة</string> <string name="encrypted_message">رسالة مشفرة</string>
<string name="global_menu_preferences_language_desktop">اختر اللغة…</string> <string name="global_menu_preferences_language_desktop">اختر اللغة…</string>

5
src/main/res/values-az/strings.xml
View file

@ -396,8 +396,9 @@
<string name="qrshow_join_contact_hint">%1$silə əlaqə qurmaq üçün bunu skan edin</string> <string name="qrshow_join_contact_hint">%1$silə əlaqə qurmaq üçün bunu skan edin</string>
<string name="qrshow_join_contact_no_connection_toast">İnternet bağlantısı yoxdur, QR kodunu qura bilmir.</string> <string name="qrshow_join_contact_no_connection_toast">İnternet bağlantısı yoxdur, QR kodunu qura bilmir.</string>
<string name="contact_verified">%1$s yoxlanıldı.</string> <string name="contact_verified">%1$s yoxlanıldı.</string>
<!-- deprecated, was stock string -->
<string name="contact_not_verified">%1$sDoğrula bilmir</string> <string name="contact_not_verified">%1$sDoğrula bilmir</string>
<!-- translators: "setup" is the "encryption setup" here, as in "Autocrypt Setup Message" --> <!-- deprecated, was stock string -->
<string name="contact_setup_changed">%1$süçün quraşdırma dəyişdirildi</string> <string name="contact_setup_changed">%1$süçün quraşdırma dəyişdirildi</string>
<!-- notifications --> <!-- notifications -->
<string name="notify_reply_button">Cavab ver</string> <string name="notify_reply_button">Cavab ver</string>
@ -416,7 +417,7 @@
<string name="perm_explain_access_to_mic_denied">Delta Chat yer əlavə etmək üçün yer icazə tələb edir, lakin daimi olaraq rədd edilmişdir. \"İcazələr\"-i seçin və\"Yerləşmə\" izni verin. </string> <string name="perm_explain_access_to_mic_denied">Delta Chat yer əlavə etmək üçün yer icazə tələb edir, lakin daimi olaraq rədd edilmişdir. \"İcazələr\"-i seçin və\"Yerləşmə\" izni verin. </string>
<string name="perm_explain_access_to_storage_denied">Delta Chat, fotoşəkilləri, videoları və ya səsləri əlavə etmək və ya ixrac etmək üçün saxlama icazəsini tələb edir, lakin bu daimi olaraq rədd edildi. Xahiş edirik tətbiq ayarları menyusuna davam edin, \"İzinlər\" seçin və \"Yaddaş\" funksiyasını aktivləşdirin.</string> <string name="perm_explain_access_to_storage_denied">Delta Chat, fotoşəkilləri, videoları və ya səsləri əlavə etmək və ya ixrac etmək üçün saxlama icazəsini tələb edir, lakin bu daimi olaraq rədd edildi. Xahiş edirik tətbiq ayarları menyusuna davam edin, \"İzinlər\" seçin və \"Yaddaş\" funksiyasını aktivləşdirin.</string>
<string name="perm_explain_access_to_location_denied">Delta Chat yer əlavə etmək üçün yer icazə tələb edir, lakin daimi olaraq rədd edilmişdir. \"İcazələr\"-i seçin və\"Yerləşmə\" izni verin. </string> <string name="perm_explain_access_to_location_denied">Delta Chat yer əlavə etmək üçün yer icazə tələb edir, lakin daimi olaraq rədd edilmişdir. \"İcazələr\"-i seçin və\"Yerləşmə\" izni verin. </string>
<!-- dc_str_* resources --> <!-- deprecated, use string "E-Mail" for non-encrypted messages instead -->
<string name="encrypted_message">Şifrələnmiş mesaj</string> <string name="encrypted_message">Şifrələnmiş mesaj</string>
<string name="global_menu_preferences_language_desktop">Dil səç</string> <string name="global_menu_preferences_language_desktop">Dil səç</string>

12
src/main/res/values-bg/strings.xml
View file

@ -294,7 +294,6 @@
<!-- Menu item beside an app/chat that adds an icon to the system's home screen. If the user taps that icon, the app/chat is opened directly. --> <!-- Menu item beside an app/chat that adds an icon to the system's home screen. If the user taps that icon, the app/chat is opened directly. -->
<string name="add_to_home_screen">Добавяне към началния екран</string> <string name="add_to_home_screen">Добавяне към началния екран</string>
<string name="donate">Дарение</string> <string name="donate">Дарение</string>
<string name="mute_for_one_hour">Спиране на звука за 1 час</string> <string name="mute_for_one_hour">Спиране на звука за 1 час</string>
<string name="mute_for_eight_hours">Спиране на звука за 8 часа</string> <string name="mute_for_eight_hours">Спиране на звука за 8 часа</string>
<string name="mute_for_one_day">Спиране на звука за 1 ден</string> <string name="mute_for_one_day">Спиране на звука за 1 ден</string>
@ -474,7 +473,7 @@
<!-- option to show images in the gallery as square (instead of using correct width/height) --> <!-- option to show images in the gallery as square (instead of using correct width/height) -->
<string name="square_grid">Мрежа от квадрати</string> <string name="square_grid">Мрежа от квадрати</string>
<string name="send_message">Изпращане на съобщение</string> <string name="send_message">Изпращане на съобщение</string>
<!-- Placeholder %1$s will be replaced by the name of the contact changing their address. Placeholders %2$s and %3$s will be replaced by old/new addresses. --> <!-- deprecated, was stock string -->
<string name="aeap_addr_changed">%1$s промени своя адрес от %2$s на %3$s</string> <string name="aeap_addr_changed">%1$s промени своя адрес от %2$s на %3$s</string>
<!-- deprecated --> <!-- deprecated -->
<string name="aeap_explanation">Променихте своя email адрес от %1$s на %2$s.\n\nАко от тук нататък изпратите съобщение до проверена група, контактите в нея автоматично ще заменят стария с новия Ви адрес.\n\nСилно се препоръчва да извършите настройка в предишния си доставчик на електронна поща така, че всички email съобщения да се препращат към новия Ви email адрес. В противен случай е възможно да не получавате съобщения от контакти, които все още не са получили новия Ви адрес.</string> <string name="aeap_explanation">Променихте своя email адрес от %1$s на %2$s.\n\nАко от тук нататък изпратите съобщение до проверена група, контактите в нея автоматично ще заменят стария с новия Ви адрес.\n\nСилно се препоръчва да извършите настройка в предишния си доставчик на електронна поща така, че всички email съобщения да се препращат към новия Ви email адрес. В противен случай е възможно да не получавате съобщения от контакти, които все още не са получили новия Ви адрес.</string>
@ -845,11 +844,13 @@
<string name="ephemeral_timer_weeks_by_you">Установихте таймера на изчезващите съобщения на %1$s седмици.</string> <string name="ephemeral_timer_weeks_by_you">Установихте таймера на изчезващите съобщения на %1$s седмици.</string>
<!-- %1$s will be replaced by the number of weeks (always >1) the timer is set to, %2$s will be replaced by name and address of the contact --> <!-- %1$s will be replaced by the number of weeks (always >1) the timer is set to, %2$s will be replaced by name and address of the contact -->
<string name="ephemeral_timer_weeks_by_other">Таймерът на изчезващите съобщения е установен на %1$s седмици от %2$s.</string> <string name="ephemeral_timer_weeks_by_other">Таймерът на изчезващите съобщения е установен на %1$s седмици от %2$s.</string>
<!-- this may be shown instead of the chat's input field, with buttons "More Info" and "OK" --> <!-- deprecated -->
<string name="chat_protection_broken">%1$s изпрати съобщение от друго устройство.</string> <string name="chat_protection_broken">%1$s изпрати съобщение от друго устройство.</string>
<string name="chat_protection_enabled_tap_to_learn_more">От тук нататък е гарантирано, че съобщенията ще бъдат криптирани от край до край. Докоснете, за да научите повече.</string> <string name="chat_protection_enabled_tap_to_learn_more">От тук нататък е гарантирано, че съобщенията ще бъдат криптирани от край до край. Докоснете, за да научите повече.</string>
<string name="chat_protection_enabled_explanation">От тук нататък е гарантирано, че всички съобщения в този чат са криптирани от край до край.\n\nКриптирането от край до край запазва поверителността на съобщенията между вас и вашите партньори в чата. Дори Вашият e-mail доставчик не може да ги прочете.</string> <string name="chat_protection_enabled_explanation">От тук нататък е гарантирано, че всички съобщения в този чат са криптирани от край до край.\n\nКриптирането от край до край запазва поверителността на съобщенията между вас и вашите партньори в чата. Дори Вашият e-mail доставчик не може да ги прочете.</string>
<!-- deprecated -->
<string name="chat_protection_broken_tap_to_learn_more">%1$s изпрати съобщение от друго съобщение. Докоснете, за да научите повече.</string> <string name="chat_protection_broken_tap_to_learn_more">%1$s изпрати съобщение от друго съобщение. Докоснете, за да научите повече.</string>
<!-- deprecated -->
<string name="chat_protection_broken_explanation">Криптирането от край до край повече не може да бъде гарантирано, вероятно защото %1$s преинсталира Delta Chat или изпрати съобщение от друго устройство.\n\nБихте могли да се срещнете с него/нея лично, да сканирате неговия/нейния QR код отново и отново да установите гарантирано криптиране от край до край.</string> <string name="chat_protection_broken_explanation">Криптирането от край до край повече не може да бъде гарантирано, вероятно защото %1$s преинсталира Delta Chat или изпрати съобщение от друго устройство.\n\nБихте могли да се срещнете с него/нея лично, да сканирате неговия/нейния QR код отново и отново да установите гарантирано криптиране от край до край.</string>
<string name="invalid_unencrypted_tap_to_learn_more">⚠️%1$s изисква криптиране от край до край, което все още не е установено за този чат. Докоснете, за да научите повече.</string> <string name="invalid_unencrypted_tap_to_learn_more">⚠️%1$s изисква криптиране от край до край, което все още не е установено за този чат. Докоснете, за да научите повече.</string>
<string name="invalid_unencrypted_explanation">За да установите криптиране от край до край, бихте могли да се срещате с лицата, с които желаете да контактувате, лично и да сканирате техните QR кодове, за да ги въведете.</string> <string name="invalid_unencrypted_explanation">За да установите криптиране от край до край, бихте могли да се срещате с лицата, с които желаете да контактувате, лично и да сканирате техните QR кодове, за да ги въведете.</string>
@ -912,11 +913,12 @@
<!-- deprecated --> <!-- deprecated -->
<string name="secure_join_wait_timeout">Все още не може да бъде установено гарантирано криптиране от край до край, но вече можете да пратите съобщение.</string> <string name="secure_join_wait_timeout">Все още не може да бъде установено гарантирано криптиране от край до край, но вече можете да пратите съобщение.</string>
<string name="contact_verified">%1$s е проверен.</string> <string name="contact_verified">%1$s е проверен.</string>
<!-- deprecated, was stock string -->
<string name="contact_not_verified">Не може да бъде проверен %1$s.</string> <string name="contact_not_verified">Не може да бъде проверен %1$s.</string>
<!-- Shown in contact profile. The placeholder will be replaced by the name of the contact that introduced the contact. --> <!-- Shown in contact profile. The placeholder will be replaced by the name of the contact that introduced the contact. -->
<string name="verified_by">Проверен от%1$s</string> <string name="verified_by">Проверен от%1$s</string>
<string name="verified_by_you">Представен от мен</string> <string name="verified_by_you">Представен от мен</string>
<!-- translators: "setup" is the "encryption setup" here, as in "Autocrypt Setup Message" --> <!-- deprecated, was stock string -->
<string name="contact_setup_changed">Настройката за %1$s е сменена.</string> <string name="contact_setup_changed">Настройката за %1$s е сменена.</string>
<string name="verified_contact_required_explain">За да се гарантира криптирането от край до край, можете да добавяте в тази група само контакти, отбелязани със зелена отметка.\n\nБихте могли да се срещнете с лицата, с които желаете да контактувате, лично и да сканирате техните QR кодове, за да ги въведете.</string> <string name="verified_contact_required_explain">За да се гарантира криптирането от край до край, можете да добавяте в тази група само контакти, отбелязани със зелена отметка.\n\nБихте могли да се срещнете с лицата, с които желаете да контактувате, лично и да сканирате техните QR кодове, за да ги въведете.</string>
<string name="mailto_dialog_header_select_chat">Изберете чат, към който да бъде пратено съобщението</string> <string name="mailto_dialog_header_select_chat">Изберете чат, към който да бъде пратено съобщението</string>
@ -960,7 +962,7 @@
<string name="ImageEditorHud_flip">Обръщане</string> <string name="ImageEditorHud_flip">Обръщане</string>
<string name="ImageEditorHud_rotate">Завъртане</string> <string name="ImageEditorHud_rotate">Завъртане</string>
<!-- dc_str_* resources --> <!-- deprecated, use string "E-Mail" for non-encrypted messages instead -->
<string name="encrypted_message">Криптирано съобщение</string> <string name="encrypted_message">Криптирано съобщение</string>
<!-- strings introduced on desktop. we want to share strings between the os, in general, please do not add generic strings here --> <!-- strings introduced on desktop. we want to share strings between the os, in general, please do not add generic strings here -->

15
src/main/res/values-ca/strings.xml
View file

@ -332,7 +332,6 @@
<!-- Menu item beside an app/chat that adds an icon to the system's home screen. If the user taps that icon, the app/chat is opened directly. --> <!-- Menu item beside an app/chat that adds an icon to the system's home screen. If the user taps that icon, the app/chat is opened directly. -->
<string name="add_to_home_screen">Afegeix a la pantalla d\'inici</string> <string name="add_to_home_screen">Afegeix a la pantalla d\'inici</string>
<string name="donate">Feu un donatiu</string> <string name="donate">Feu un donatiu</string>
<string name="mute_for_one_hour">Silencia 1 hora</string> <string name="mute_for_one_hour">Silencia 1 hora</string>
<string name="mute_for_eight_hours">Silencia 8 hores</string> <string name="mute_for_eight_hours">Silencia 8 hores</string>
<string name="mute_for_one_day">Silencia 1 dia</string> <string name="mute_for_one_day">Silencia 1 dia</string>
@ -532,7 +531,7 @@
<!-- option to show images in the gallery as square (instead of using correct width/height) --> <!-- option to show images in the gallery as square (instead of using correct width/height) -->
<string name="square_grid">Graella quadrada</string> <string name="square_grid">Graella quadrada</string>
<string name="send_message">Envia el missatge</string> <string name="send_message">Envia el missatge</string>
<!-- Placeholder %1$s will be replaced by the name of the contact changing their address. Placeholders %2$s and %3$s will be replaced by old/new addresses. --> <!-- deprecated, was stock string -->
<string name="aeap_addr_changed">%1$s ha canviat la seva adreça de %2$s a %3$s</string> <string name="aeap_addr_changed">%1$s ha canviat la seva adreça de %2$s a %3$s</string>
<!-- deprecated --> <!-- deprecated -->
<string name="aeap_explanation">Heu canviat la vostra adreça de correu electrònic de %1$s a %2$s.\n\nSi ara envieu un missatge a un grup verificat, els contactes del grup canviaran de forma automàtica l\'adreça antiga per la nova.\n\nUs recomanem que configureu el compte antic a fi que us reenvïi els missatges a l\'adreça nova. Si no ho feu, podríeu perdre missatges de contactes que encara no hagin actualitzat la vostra adreça.</string> <string name="aeap_explanation">Heu canviat la vostra adreça de correu electrònic de %1$s a %2$s.\n\nSi ara envieu un missatge a un grup verificat, els contactes del grup canviaran de forma automàtica l\'adreça antiga per la nova.\n\nUs recomanem que configureu el compte antic a fi que us reenvïi els missatges a l\'adreça nova. Si no ho feu, podríeu perdre missatges de contactes que encara no hagin actualitzat la vostra adreça.</string>
@ -932,11 +931,13 @@
<string name="ephemeral_timer_weeks_by_you">Heu definit el temporitzador dels missatges fonedissos a %1$s setmanes.</string> <string name="ephemeral_timer_weeks_by_you">Heu definit el temporitzador dels missatges fonedissos a %1$s setmanes.</string>
<!-- %1$s will be replaced by the number of weeks (always >1) the timer is set to, %2$s will be replaced by name and address of the contact --> <!-- %1$s will be replaced by the number of weeks (always >1) the timer is set to, %2$s will be replaced by name and address of the contact -->
<string name="ephemeral_timer_weeks_by_other">%2$s ha definit el temporitzador dels missatges efímers a %1$s setmanes.</string> <string name="ephemeral_timer_weeks_by_other">%2$s ha definit el temporitzador dels missatges efímers a %1$s setmanes.</string>
<!-- this may be shown instead of the chat's input field, with buttons "More Info" and "OK" --> <!-- deprecated -->
<string name="chat_protection_broken">%1$s ha enviat un missatge des d\'un altre dispositiu.</string> <string name="chat_protection_broken">%1$s ha enviat un missatge des d\'un altre dispositiu.</string>
<string name="chat_protection_enabled_tap_to_learn_more">Us garantim que a partir d\'ara els missatges són xifrats d\'extrem a extrem. Toqueu per a obtenir més informació.</string> <string name="chat_protection_enabled_tap_to_learn_more">Us garantim que a partir d\'ara els missatges són xifrats d\'extrem a extrem. Toqueu per a obtenir més informació.</string>
<string name="chat_protection_enabled_explanation">Ara es garanteix que tots els missatges d\'aquest xat són xifrats d\'extrem a extrem.\n\nEl xifratge d\'extrem a extrem manté privats els missatges entre vós i els companys de xat. Ni tan sols el vostre proveïdor de correu electrònic pot llegir-los.</string> <string name="chat_protection_enabled_explanation">Ara es garanteix que tots els missatges d\'aquest xat són xifrats d\'extrem a extrem.\n\nEl xifratge d\'extrem a extrem manté privats els missatges entre vós i els companys de xat. Ni tan sols el vostre proveïdor de correu electrònic pot llegir-los.</string>
<!-- deprecated -->
<string name="chat_protection_broken_tap_to_learn_more">%1$s ha enviat un missatge des d\'un altre dispositiu. Toqueu per a obtenir més informació.</string> <string name="chat_protection_broken_tap_to_learn_more">%1$s ha enviat un missatge des d\'un altre dispositiu. Toqueu per a obtenir més informació.</string>
<!-- deprecated -->
<string name="chat_protection_broken_explanation">No es pot garantir el xifrat d\'extrem a extrem, probablement perquè %1$s ha reinstal·lat Delta Chat o ha enviat un missatge des d\'un altre dispositiu.\n\n Podeu trobar-vos físicament amb la persona i tornar a escanejar el seu codi QR per tomar-hi a tenir xifrat d\'extrem a extrem.</string> <string name="chat_protection_broken_explanation">No es pot garantir el xifrat d\'extrem a extrem, probablement perquè %1$s ha reinstal·lat Delta Chat o ha enviat un missatge des d\'un altre dispositiu.\n\n Podeu trobar-vos físicament amb la persona i tornar a escanejar el seu codi QR per tomar-hi a tenir xifrat d\'extrem a extrem.</string>
<string name="invalid_unencrypted_tap_to_learn_more">%1$srequereix xifratge d\'extrem a extrem, que encara no s\'ha configurat per a aquest xat. Toqueu per a obtenir més informació.</string> <string name="invalid_unencrypted_tap_to_learn_more">%1$srequereix xifratge d\'extrem a extrem, que encara no s\'ha configurat per a aquest xat. Toqueu per a obtenir més informació.</string>
<string name="invalid_unencrypted_explanation">Per a establir xifratge d\'extrem a extrem, heu de trobar-vos amb els contactes en persona i escanejar el seu codi QR per a poder afegir-los.</string> <string name="invalid_unencrypted_explanation">Per a establir xifratge d\'extrem a extrem, heu de trobar-vos amb els contactes en persona i escanejar el seu codi QR per a poder afegir-los.</string>
@ -999,11 +1000,12 @@
<!-- deprecated --> <!-- deprecated -->
<string name="secure_join_wait_timeout">Encara no es pot garantir el xifrat punt-a-punt, però ja podeu enviar un missatge.</string> <string name="secure_join_wait_timeout">Encara no es pot garantir el xifrat punt-a-punt, però ja podeu enviar un missatge.</string>
<string name="contact_verified">%1$s verificat.</string> <string name="contact_verified">%1$s verificat.</string>
<!-- deprecated, was stock string -->
<string name="contact_not_verified">No es pot verificar%1$s</string> <string name="contact_not_verified">No es pot verificar%1$s</string>
<!-- Shown in contact profile. The placeholder will be replaced by the name of the contact that introduced the contact. --> <!-- Shown in contact profile. The placeholder will be replaced by the name of the contact that introduced the contact. -->
<string name="verified_by">Afegit per %1$s</string> <string name="verified_by">Afegit per %1$s</string>
<string name="verified_by_you">Afegit per mi</string> <string name="verified_by_you">Afegit per mi</string>
<!-- translators: "setup" is the "encryption setup" here, as in "Autocrypt Setup Message" --> <!-- deprecated, was stock string -->
<string name="contact_setup_changed">Configuració canviada per %1$s</string> <string name="contact_setup_changed">Configuració canviada per %1$s</string>
<string name="verified_contact_required_explain">Per a garantir el xifrat extrem a extrem, només podeu afegir a aquest grup contactes que tinguin la marca verda.\n\nPodeu trobar-vos en persona amb els contactes per a escanejar els seus codis QR i poder-los afegir. </string> <string name="verified_contact_required_explain">Per a garantir el xifrat extrem a extrem, només podeu afegir a aquest grup contactes que tinguin la marca verda.\n\nPodeu trobar-vos en persona amb els contactes per a escanejar els seus codis QR i poder-los afegir. </string>
<string name="mailto_dialog_header_select_chat">Trieu el xat on enviar el missatge</string> <string name="mailto_dialog_header_select_chat">Trieu el xat on enviar el missatge</string>
@ -1047,7 +1049,7 @@
<string name="ImageEditorHud_flip">Capgira</string> <string name="ImageEditorHud_flip">Capgira</string>
<string name="ImageEditorHud_rotate">Gira</string> <string name="ImageEditorHud_rotate">Gira</string>
<!-- dc_str_* resources --> <!-- deprecated, use string "E-Mail" for non-encrypted messages instead -->
<string name="encrypted_message">Missatge encriptat</string> <string name="encrypted_message">Missatge encriptat</string>
<!-- strings introduced on desktop. we want to share strings between the os, in general, please do not add generic strings here --> <!-- strings introduced on desktop. we want to share strings between the os, in general, please do not add generic strings here -->
@ -1177,7 +1179,8 @@
<string name="perm_enable_bg_reminder_title">Prem aquí per rebre missatges mentre Delta Chat és en segon pla.</string> <string name="perm_enable_bg_reminder_title">Prem aquí per rebre missatges mentre Delta Chat és en segon pla.</string>
<string name="perm_enable_bg_already_done">Ja heu autoritzat Delta Chat a rebre missatges en segon pla.\n\nSi encara no us arriben els missatge, reviseu els paràmetres de sistema.</string> <string name="perm_enable_bg_already_done">Ja heu autoritzat Delta Chat a rebre missatges en segon pla.\n\nSi encara no us arriben els missatge, reviseu els paràmetres de sistema.</string>
<!-- device messages for updates --> <!-- deprecated -->
<string name="update_1_50_android">Què hi ha de nou?\n\n❤️‍🔥 Un selector d\'emojis nou amb més emojis\n\n🎮 Aplicacions al xat millorades: rebeu notificacions i obriu les aplicacions suportades segons el context. P. ex. obriu una entrada afegida al calendari directament.\n\n👍 Rebeu notificacions de les reaccions dels vostres missatges\n\n... 🛠️ Correccions i moltes coses més a %1$s</string> <string name="update_1_50_android">Què hi ha de nou?\n\n❤️‍🔥 Un selector d\'emojis nou amb més emojis\n\n🎮 Aplicacions al xat millorades: rebeu notificacions i obriu les aplicacions suportades segons el context. P. ex. obriu una entrada afegida al calendari directament.\n\n👍 Rebeu notificacions de les reaccions dels vostres missatges\n\n... 🛠️ Correccions i moltes coses més a %1$s</string>
<!-- deprecated -->
<string name="update_switch_profile_placement">ℹ️ S\'ha mogut l\'opció «Canvia el perfil»: toqueu en la vostra imatge de perfil en la cantonada superior de la finestra principal per a afegir o canviar perfils 💡</string> <string name="update_switch_profile_placement">ℹ️ S\'ha mogut l\'opció «Canvia el perfil»: toqueu en la vostra imatge de perfil en la cantonada superior de la finestra principal per a afegir o canviar perfils 💡</string>
</resources> </resources>

5
src/main/res/values-ckb/strings.xml
View file

@ -495,8 +495,9 @@
<string name="qraccount_ask_create_and_login">دەتەوێت ناونیشانی ئیمەیلێکی نوێ لەسەر \"%1$s\" درووست بکەیت و لەوێ بچیتە ژوورەوە؟</string> <string name="qraccount_ask_create_and_login">دەتەوێت ناونیشانی ئیمەیلێکی نوێ لەسەر \"%1$s\" درووست بکەیت و لەوێ بچیتە ژوورەوە؟</string>
<string name="qraccount_qr_code_cannot_be_used">ناتوانی لە کۆدی QRە سکان کراوەکە کەڵک بگریت بۆ پێکهێنانی هەژمارێکی نوێ.</string> <string name="qraccount_qr_code_cannot_be_used">ناتوانی لە کۆدی QRە سکان کراوەکە کەڵک بگریت بۆ پێکهێنانی هەژمارێکی نوێ.</string>
<string name="contact_verified">%1$s پشتڕاست کرایەوە</string> <string name="contact_verified">%1$s پشتڕاست کرایەوە</string>
<!-- deprecated, was stock string -->
<string name="contact_not_verified">%1$s پشتڕاست ناکرێتەوە.</string> <string name="contact_not_verified">%1$s پشتڕاست ناکرێتەوە.</string>
<!-- translators: "setup" is the "encryption setup" here, as in "Autocrypt Setup Message" --> <!-- deprecated, was stock string -->
<string name="contact_setup_changed">ڕێکخستن بۆ %1$s گۆڕا.</string> <string name="contact_setup_changed">ڕێکخستن بۆ %1$s گۆڕا.</string>
<!-- notifications --> <!-- notifications -->
<string name="notify_reply_button">وەڵام دانەوە</string> <string name="notify_reply_button">وەڵام دانەوە</string>
@ -515,7 +516,7 @@
<string name="perm_explain_access_to_mic_denied">بۆ هەناردنی پەیامی دەنگی، بچۆ بەشی ڕێکخستنەکانی نەرمامێرەکە، لە بەشی \"ڕێگەپێدان\"دا، \"مایک\" چالاک بکەوە.</string> <string name="perm_explain_access_to_mic_denied">بۆ هەناردنی پەیامی دەنگی، بچۆ بەشی ڕێکخستنەکانی نەرمامێرەکە، لە بەشی \"ڕێگەپێدان\"دا، \"مایک\" چالاک بکەوە.</string>
<string name="perm_explain_access_to_storage_denied">بۆ هەناردن و وەرگرتنی پەڕگەکان، بچۆ بەشی ڕێکخستنەکانی نەرمامێرەکە، لە بەشی \"ڕێگەپێدان\"دا، \"بیرگە\" چالاک بکەوە.</string> <string name="perm_explain_access_to_storage_denied">بۆ هەناردن و وەرگرتنی پەڕگەکان، بچۆ بەشی ڕێکخستنەکانی نەرمامێرەکە، لە بەشی \"ڕێگەپێدان\"دا، \"بیرگە\" چالاک بکەوە.</string>
<string name="perm_explain_access_to_location_denied">بۆ لکاندنی شوێنێک، بچۆ بەشی ڕێکخستنەکانی نەرمامێرەکە، لە بەشی \"ڕێگەپێدان\"دا، \"شوێن\" چالاک بکەوە.</string> <string name="perm_explain_access_to_location_denied">بۆ لکاندنی شوێنێک، بچۆ بەشی ڕێکخستنەکانی نەرمامێرەکە، لە بەشی \"ڕێگەپێدان\"دا، \"شوێن\" چالاک بکەوە.</string>
<!-- dc_str_* resources --> <!-- deprecated, use string "E-Mail" for non-encrypted messages instead -->
<string name="encrypted_message">پەیامی شفرەکراو</string> <string name="encrypted_message">پەیامی شفرەکراو</string>
<!-- strings introduced on desktop. we want to share strings between the os, in general, please do not add generic strings here --> <!-- strings introduced on desktop. we want to share strings between the os, in general, please do not add generic strings here -->

16
src/main/res/values-cs/strings.xml
View file

@ -357,7 +357,6 @@
<!-- Menu item beside an app/chat that adds an icon to the system's home screen. If the user taps that icon, the app/chat is opened directly. --> <!-- Menu item beside an app/chat that adds an icon to the system's home screen. If the user taps that icon, the app/chat is opened directly. -->
<string name="add_to_home_screen">Přidat na domovskou obrazovku</string> <string name="add_to_home_screen">Přidat na domovskou obrazovku</string>
<string name="donate">Darovat</string> <string name="donate">Darovat</string>
<string name="mute_for_one_hour">Ztlumit na 1 hodinu</string> <string name="mute_for_one_hour">Ztlumit na 1 hodinu</string>
<string name="mute_for_eight_hours">Ztlumit na 8 hodin</string> <string name="mute_for_eight_hours">Ztlumit na 8 hodin</string>
<string name="mute_for_one_day">Ztlumit na 1 den</string> <string name="mute_for_one_day">Ztlumit na 1 den</string>
@ -571,7 +570,7 @@
<!-- option to show images in the gallery as square (instead of using correct width/height) --> <!-- option to show images in the gallery as square (instead of using correct width/height) -->
<string name="square_grid">Mřížka čtverců</string> <string name="square_grid">Mřížka čtverců</string>
<string name="send_message">Odeslat zprávu</string> <string name="send_message">Odeslat zprávu</string>
<!-- Placeholder %1$s will be replaced by the name of the contact changing their address. Placeholders %2$s and %3$s will be replaced by old/new addresses. --> <!-- deprecated, was stock string -->
<string name="aeap_addr_changed">Uživatel %1$s změnil svou adresu z %2$s na %3$s</string> <string name="aeap_addr_changed">Uživatel %1$s změnil svou adresu z %2$s na %3$s</string>
<!-- deprecated --> <!-- deprecated -->
<string name="aeap_explanation">Změnili jste svou e-mailovou adresu z %1$s na %2$s.\n\nPokud nyní pošlete zprávu ověřené skupině, všem kontaktům v ní se vaše adresa aktualizuje na novou.\n\nJe důrazně doporučeno, abyste u svého starého poskytovatele nastavili přesměrování všech e-mailů na novou adresu, jinak byste mohli přijít o zprávy od kontaktů, které vaši novou adresu dosud nedostaly. </string> <string name="aeap_explanation">Změnili jste svou e-mailovou adresu z %1$s na %2$s.\n\nPokud nyní pošlete zprávu ověřené skupině, všem kontaktům v ní se vaše adresa aktualizuje na novou.\n\nJe důrazně doporučeno, abyste u svého starého poskytovatele nastavili přesměrování všech e-mailů na novou adresu, jinak byste mohli přijít o zprávy od kontaktů, které vaši novou adresu dosud nedostaly. </string>
@ -971,11 +970,13 @@
<string name="ephemeral_timer_weeks_by_you">Samomazací zprávy vyprší po %1$s týdnech ode mě.</string> <string name="ephemeral_timer_weeks_by_you">Samomazací zprávy vyprší po %1$s týdnech ode mě.</string>
<!-- %1$s will be replaced by the number of weeks (always >1) the timer is set to, %2$s will be replaced by name and address of the contact --> <!-- %1$s will be replaced by the number of weeks (always >1) the timer is set to, %2$s will be replaced by name and address of the contact -->
<string name="ephemeral_timer_weeks_by_other">Uživatel %2$s změnil časovač mizejících zpráv na %1$s týdnů.</string> <string name="ephemeral_timer_weeks_by_other">Uživatel %2$s změnil časovač mizejících zpráv na %1$s týdnů.</string>
<!-- this may be shown instead of the chat's input field, with buttons "More Info" and "OK" --> <!-- deprecated -->
<string name="chat_protection_broken">Uživatel %1$s odeslal zprávu z jiného zařízení.</string> <string name="chat_protection_broken">Uživatel %1$s odeslal zprávu z jiného zařízení.</string>
<string name="chat_protection_enabled_tap_to_learn_more">Nyní je garantováno koncové šifrování vašich zpráv. Stiskněte pro více informací.</string> <string name="chat_protection_enabled_tap_to_learn_more">Nyní je garantováno koncové šifrování vašich zpráv. Stiskněte pro více informací.</string>
<string name="chat_protection_enabled_explanation">Nyní je garantováno, že všechny zprávy v tomto chatu jsou koncově šifrovány.\n\nKoncové šifrování zajišťuje soukromí mezi vámi a vašimi kontakty. Nedokáže je přečíst ani váš poskytovatel e-mailu.</string> <string name="chat_protection_enabled_explanation">Nyní je garantováno, že všechny zprávy v tomto chatu jsou koncově šifrovány.\n\nKoncové šifrování zajišťuje soukromí mezi vámi a vašimi kontakty. Nedokáže je přečíst ani váš poskytovatel e-mailu.</string>
<!-- deprecated -->
<string name="chat_protection_broken_tap_to_learn_more">Uživatel %1$s odeslal zprávu z jiného zařízení. Stiskněte pro více informací.</string> <string name="chat_protection_broken_tap_to_learn_more">Uživatel %1$s odeslal zprávu z jiného zařízení. Stiskněte pro více informací.</string>
<!-- deprecated -->
<string name="chat_protection_broken_explanation">Koncové šifrování již nemůže být garantováno, pravděpodobně protože uživatel %1$s přeinstaloval Delta Chat nebo odeslal zprávu z jiného zařízení.\n\nPro obnovení garantovaného koncového šifrování se sejděte osobně a naskenujte si své QR kódy.</string> <string name="chat_protection_broken_explanation">Koncové šifrování již nemůže být garantováno, pravděpodobně protože uživatel %1$s přeinstaloval Delta Chat nebo odeslal zprávu z jiného zařízení.\n\nPro obnovení garantovaného koncového šifrování se sejděte osobně a naskenujte si své QR kódy.</string>
<string name="invalid_unencrypted_tap_to_learn_more">⚠️%1$s vyžaduje koncové šifrování, které pro tento chat ještě není nastaveno. Stiskněte pro více informací. </string> <string name="invalid_unencrypted_tap_to_learn_more">⚠️%1$s vyžaduje koncové šifrování, které pro tento chat ještě není nastaveno. Stiskněte pro více informací. </string>
<string name="invalid_unencrypted_explanation">Pro navázání koncově šifrovaného spojení se můžete se svými kontakty setkat osobně a naskenovat jejich QR kódy.</string> <string name="invalid_unencrypted_explanation">Pro navázání koncově šifrovaného spojení se můžete se svými kontakty setkat osobně a naskenovat jejich QR kódy.</string>
@ -1037,13 +1038,15 @@
<string name="secure_join_wait">Navazování koncově šifrovaného spojení, prosím, čekejte...</string> <string name="secure_join_wait">Navazování koncově šifrovaného spojení, prosím, čekejte...</string>
<!-- deprecated --> <!-- deprecated -->
<string name="secure_join_wait_timeout">Zatím nebylo navázáno koncově šifrované spojení, ale již nyní můžete posílat zprávy.</string> <string name="secure_join_wait_timeout">Zatím nebylo navázáno koncově šifrované spojení, ale již nyní můžete posílat zprávy.</string>
<!-- deprecated, was stock string -->
<string name="secure_join_takes_longer">Vypadá to, že to trvá trochu déle. Možná jste vy nebo váš kontakt offline.\n\nProces však pokračuje na pozadí. Zatím můžete dělat něco jiného...</string> <string name="secure_join_takes_longer">Vypadá to, že to trvá trochu déle. Možná jste vy nebo váš kontakt offline.\n\nProces však pokračuje na pozadí. Zatím můžete dělat něco jiného...</string>
<string name="contact_verified">Uživatel %1$s ověřen.</string> <string name="contact_verified">Uživatel %1$s ověřen.</string>
<!-- deprecated, was stock string -->
<string name="contact_not_verified">Navázání garantovaného koncově šifrovaného spojení s uživatelem %1$s selhalo.</string> <string name="contact_not_verified">Navázání garantovaného koncově šifrovaného spojení s uživatelem %1$s selhalo.</string>
<!-- Shown in contact profile. The placeholder will be replaced by the name of the contact that introduced the contact. --> <!-- Shown in contact profile. The placeholder will be replaced by the name of the contact that introduced the contact. -->
<string name="verified_by">Ověřeni uživatelem %1$s.</string> <string name="verified_by">Ověřeni uživatelem %1$s.</string>
<string name="verified_by_you">Ověřeni mnou</string> <string name="verified_by_you">Ověřeni mnou</string>
<!-- translators: "setup" is the "encryption setup" here, as in "Autocrypt Setup Message" --> <!-- deprecated, was stock string -->
<string name="contact_setup_changed">Nastavení pro uživatele %1$s změněno.</string> <string name="contact_setup_changed">Nastavení pro uživatele %1$s změněno.</string>
<string name="verified_contact_required_explain">Aby mohlo být garantováno koncové šifrování, můžete do této skupiny přidávat pouze uživatele se zeleným zaškrtávátkem.\n\nSe svými kontakty se můžete setkat osobně a naskenovat jejich QR kód, abyste je ověřili.</string> <string name="verified_contact_required_explain">Aby mohlo být garantováno koncové šifrování, můžete do této skupiny přidávat pouze uživatele se zeleným zaškrtávátkem.\n\nSe svými kontakty se můžete setkat osobně a naskenovat jejich QR kód, abyste je ověřili.</string>
<string name="mailto_dialog_header_select_chat">Vyberte chat, do kterého chcete zprávu poslat</string> <string name="mailto_dialog_header_select_chat">Vyberte chat, do kterého chcete zprávu poslat</string>
@ -1087,7 +1090,7 @@
<string name="ImageEditorHud_flip">Zrcadlení</string> <string name="ImageEditorHud_flip">Zrcadlení</string>
<string name="ImageEditorHud_rotate">Otočení</string> <string name="ImageEditorHud_rotate">Otočení</string>
<!-- dc_str_* resources --> <!-- deprecated, use string "E-Mail" for non-encrypted messages instead -->
<string name="encrypted_message">Šifrovaná zpráva</string> <string name="encrypted_message">Šifrovaná zpráva</string>
<!-- strings introduced on desktop. we want to share strings between the os, in general, please do not add generic strings here --> <!-- strings introduced on desktop. we want to share strings between the os, in general, please do not add generic strings here -->
@ -1217,7 +1220,8 @@
<string name="perm_enable_bg_reminder_title">Stiskem nastavíte přijímání zpráv, když je aplikace Delta Chat na pozadí.</string> <string name="perm_enable_bg_reminder_title">Stiskem nastavíte přijímání zpráv, když je aplikace Delta Chat na pozadí.</string>
<string name="perm_enable_bg_already_done">Přijímání zpráv na pozadí jste již aplikaci Delta Chat povolili.\n\nV případě, že vám zprávy na pozadí stále nechodí, prosím zkontrolujte svá systémová nastavení.</string> <string name="perm_enable_bg_already_done">Přijímání zpráv na pozadí jste již aplikaci Delta Chat povolili.\n\nV případě, že vám zprávy na pozadí stále nechodí, prosím zkontrolujte svá systémová nastavení.</string>
<!-- device messages for updates --> <!-- deprecated -->
<string name="update_1_50_android">Co je nového?\n\n❤️‍🔥 Nová nabídka emoji s více druhy emoji\n\n🎮 Vylepšené aplikace v chatu: Oznámení a podpůrné aplikace přímo v kontextu chatu, např. odkaz na novou nové položky z kalendáři\n\n👍 Oznámení o reakcích na zprávy\n\n... 🛠️ OPRAVY a DALŠÍ na %1$s</string> <string name="update_1_50_android">Co je nového?\n\n❤️‍🔥 Nová nabídka emoji s více druhy emoji\n\n🎮 Vylepšené aplikace v chatu: Oznámení a podpůrné aplikace přímo v kontextu chatu, např. odkaz na novou nové položky z kalendáři\n\n👍 Oznámení o reakcích na zprávy\n\n... 🛠️ OPRAVY a DALŠÍ na %1$s</string>
<!-- deprecated -->
<string name="update_switch_profile_placement">ℹ️ Volba \"Přepnout profil\" byla přesunuta: Pro přidávání či přepínání profilů stiskněte svůj profilový obrázek v horním rohu hlavní obrazovky.</string> <string name="update_switch_profile_placement">ℹ️ Volba \"Přepnout profil\" byla přesunuta: Pro přidávání či přepínání profilů stiskněte svůj profilový obrázek v horním rohu hlavní obrazovky.</string>
</resources> </resources>

5
src/main/res/values-da/strings.xml
View file

@ -631,8 +631,9 @@
<string name="qraccount_ask_create_and_login_another">Opret ny e-mail adresse på \"%1$s\" og log ind der?\n\nDin eksisterende konto bliver ikke slettet. Brug \"Skift konto\" for at skifte imellem dine konti.</string> <string name="qraccount_ask_create_and_login_another">Opret ny e-mail adresse på \"%1$s\" og log ind der?\n\nDin eksisterende konto bliver ikke slettet. Brug \"Skift konto\" for at skifte imellem dine konti.</string>
<string name="qraccount_qr_code_cannot_be_used">Den skannede QR-kode kan ikke bruges til at opsætte en ny konto.</string> <string name="qraccount_qr_code_cannot_be_used">Den skannede QR-kode kan ikke bruges til at opsætte en ny konto.</string>
<string name="contact_verified">%1$s bekræftet.</string> <string name="contact_verified">%1$s bekræftet.</string>
<!-- deprecated, was stock string -->
<string name="contact_not_verified">Kan ikke bekræfte %1$s</string> <string name="contact_not_verified">Kan ikke bekræfte %1$s</string>
<!-- translators: "setup" is the "encryption setup" here, as in "Autocrypt Setup Message" --> <!-- deprecated, was stock string -->
<string name="contact_setup_changed">Ændret opsætning for %1$s</string> <string name="contact_setup_changed">Ændret opsætning for %1$s</string>
<!-- notifications --> <!-- notifications -->
<string name="notify_reply_button">Svar</string> <string name="notify_reply_button">Svar</string>
@ -655,7 +656,7 @@
<string name="ImageEditorHud_draw_anywhere_to_blur">Tegn hvor som helst for at sløre</string> <string name="ImageEditorHud_draw_anywhere_to_blur">Tegn hvor som helst for at sløre</string>
<string name="ImageEditorHud_rotate">Roter</string> <string name="ImageEditorHud_rotate">Roter</string>
<!-- dc_str_* resources --> <!-- deprecated, use string "E-Mail" for non-encrypted messages instead -->
<string name="encrypted_message">Krypteret besked</string> <string name="encrypted_message">Krypteret besked</string>
<!-- strings introduced on desktop. we want to share strings between the os, in general, please do not add generic strings here --> <!-- strings introduced on desktop. we want to share strings between the os, in general, please do not add generic strings here -->

26
src/main/res/values-de/strings.xml
View file

@ -261,6 +261,7 @@
<string name="please_enter_broadcast_list_name">Bitten einen Namen für die Broadcast-Liste eingeben.</string> <string name="please_enter_broadcast_list_name">Bitten einen Namen für die Broadcast-Liste eingeben.</string>
<!-- consider keeping the term "channel" as in WhatsApp or Telegram --> <!-- consider keeping the term "channel" as in WhatsApp or Telegram -->
<string name="channel_name">Name des Kanals</string> <string name="channel_name">Name des Kanals</string>
<string name="email">E-Mail</string>
<!-- "New" as in "Create New E-Mail"; shown together with "New Group" and "New Channel" --> <!-- "New" as in "Create New E-Mail"; shown together with "New Group" and "New Channel" -->
<string name="new_email">Neue E-Mail</string> <string name="new_email">Neue E-Mail</string>
<!-- the "Subject" of an e-mail, use the term common in classic e-mail apps --> <!-- the "Subject" of an e-mail, use the term common in classic e-mail apps -->
@ -359,6 +360,7 @@
<!-- Menu item beside an app/chat that adds an icon to the system's home screen. If the user taps that icon, the app/chat is opened directly. --> <!-- Menu item beside an app/chat that adds an icon to the system's home screen. If the user taps that icon, the app/chat is opened directly. -->
<string name="add_to_home_screen">Zum Startbildschirm hinzufügen</string> <string name="add_to_home_screen">Zum Startbildschirm hinzufügen</string>
<string name="donate">Spenden</string> <string name="donate">Spenden</string>
<string name="donate_device_msg">❤️ Delta Chat gefällt Ihnen anscheinend sehr gut!\n\nBitte spenden Sie, damit Delta Chat weiterhin kostenlos bleibt.\n\nDelta Chat ist zwar kostenlos und Open Source, die Entwicklung kostet jedoch Geld. Helfen Sie uns, Delta Chat unabhängig zu halten und in Zukunft noch besser zu machen.\n\nhttps://delta.chat/donate</string>
<string name="mute_for_one_hour">Stumm für 1 Stunde</string> <string name="mute_for_one_hour">Stumm für 1 Stunde</string>
<string name="mute_for_eight_hours">Stumm für 8 Stunden</string> <string name="mute_for_eight_hours">Stumm für 8 Stunden</string>
@ -567,7 +569,7 @@
<!-- option to show images in the gallery as square (instead of using correct width/height) --> <!-- option to show images in the gallery as square (instead of using correct width/height) -->
<string name="square_grid">Quadratisches Raster</string> <string name="square_grid">Quadratisches Raster</string>
<string name="send_message">Nachricht senden</string> <string name="send_message">Nachricht senden</string>
<!-- Placeholder %1$s will be replaced by the name of the contact changing their address. Placeholders %2$s and %3$s will be replaced by old/new addresses. --> <!-- deprecated, was stock string -->
<string name="aeap_addr_changed">%1$s hat die E-Mail-Adresse von %2$s nach %3$s geändert</string> <string name="aeap_addr_changed">%1$s hat die E-Mail-Adresse von %2$s nach %3$s geändert</string>
<!-- deprecated --> <!-- deprecated -->
<string name="aeap_explanation">Sie haben Ihre E-Mail-Adresse von %1$s auf %2$s geändert.\n\nWenn Sie jetzt eine Nachricht an eine verifizierte Gruppe senden, wird dort automatisch die alte durch die neue Adresse ersetzt.\n\nEs wird dringend empfohlen, Ihren alten E-Mail-Anbieter so einzurichten, dass er alle E-Mails an Ihre neue E-Mail-Adresse weiterleitet. Andernfalls könnten Sie Nachrichten von Kontakten verpassen, die Ihre neue E-Mail-Adresse noch nicht erhalten haben.</string> <string name="aeap_explanation">Sie haben Ihre E-Mail-Adresse von %1$s auf %2$s geändert.\n\nWenn Sie jetzt eine Nachricht an eine verifizierte Gruppe senden, wird dort automatisch die alte durch die neue Adresse ersetzt.\n\nEs wird dringend empfohlen, Ihren alten E-Mail-Anbieter so einzurichten, dass er alle E-Mails an Ihre neue E-Mail-Adresse weiterleitet. Andernfalls könnten Sie Nachrichten von Kontakten verpassen, die Ihre neue E-Mail-Adresse noch nicht erhalten haben.</string>
@ -970,11 +972,13 @@
<string name="ephemeral_timer_weeks_by_you">Sie haben die Ablaufzeit verschwindender Nachrichten auf %1$s Wochen gesetzt.</string> <string name="ephemeral_timer_weeks_by_you">Sie haben die Ablaufzeit verschwindender Nachrichten auf %1$s Wochen gesetzt.</string>
<!-- %1$s will be replaced by the number of weeks (always >1) the timer is set to, %2$s will be replaced by name and address of the contact --> <!-- %1$s will be replaced by the number of weeks (always >1) the timer is set to, %2$s will be replaced by name and address of the contact -->
<string name="ephemeral_timer_weeks_by_other">Ablaufzeit verschwindender Nachrichten auf %1$s Wochen gesetzt von %2$s.</string> <string name="ephemeral_timer_weeks_by_other">Ablaufzeit verschwindender Nachrichten auf %1$s Wochen gesetzt von %2$s.</string>
<!-- this may be shown instead of the chat's input field, with buttons "More Info" and "OK" --> <!-- deprecated -->
<string name="chat_protection_broken">%1$s hat eine Nachricht von einem anderen Gerät gesendet.</string> <string name="chat_protection_broken">%1$s hat eine Nachricht von einem anderen Gerät gesendet.</string>
<string name="chat_protection_enabled_tap_to_learn_more">Nachrichten sind von nun an garantiert Ende-zu-Ende-verschlüsselt. Tippen, um mehr zu erfahren.</string> <string name="chat_protection_enabled_tap_to_learn_more">Nachrichten sind Ende-zu-Ende-verschlüsselt. Tippen, um mehr zu erfahren.</string>
<string name="chat_protection_enabled_explanation">Es ist nun garantiert, dass alle Nachrichten in diesem Chat Ende-zu-Ende verschlüsselt sind.\n\nDurch die Ende-zu-Ende-Verschlüsselung bleiben die Nachrichten zwischen Ihnen und Ihren Chat-Partnern privat. Nicht einmal Server, Provider order Relays können sie lesen.</string> <string name="chat_protection_enabled_explanation">Alle Nachrichten in diesem Chat sind Ende-zu-Ende verschlüsselt.\n\nDurch die Ende-zu-Ende-Verschlüsselung bleiben die Nachrichten zwischen Ihnen und Ihren Chat-Partnern privat. Nicht einmal Server, Provider oder Relays können sie lesen.</string>
<!-- deprecated -->
<string name="chat_protection_broken_tap_to_learn_more">%1$s hat eine Nachricht von einem anderen Gerät gesendet. Tippen, um mehr zu erfahren.</string> <string name="chat_protection_broken_tap_to_learn_more">%1$s hat eine Nachricht von einem anderen Gerät gesendet. Tippen, um mehr zu erfahren.</string>
<!-- deprecated -->
<string name="chat_protection_broken_explanation">Die Ende-zu-Ende-Verschlüsselung kann nicht mehr garantiert werden, wahrscheinlich weil %1$s Delta Chat neu installiert oder eine Nachricht von einem anderen Gerät gesendet hat.\n\nSie können sich persönlich treffen und den QR-Code erneut scannen, um die garantierte Ende-zu-Ende-Verschlüsselung wiederherzustellen.</string> <string name="chat_protection_broken_explanation">Die Ende-zu-Ende-Verschlüsselung kann nicht mehr garantiert werden, wahrscheinlich weil %1$s Delta Chat neu installiert oder eine Nachricht von einem anderen Gerät gesendet hat.\n\nSie können sich persönlich treffen und den QR-Code erneut scannen, um die garantierte Ende-zu-Ende-Verschlüsselung wiederherzustellen.</string>
<string name="invalid_unencrypted_tap_to_learn_more">⚠️ %1$s verlangt eine Ende-zu-Ende-Verschlüsselung, die für diesen Chat noch nicht hergestellt wurde. Tippen, um mehr zu erfahren.</string> <string name="invalid_unencrypted_tap_to_learn_more">⚠️ %1$s verlangt eine Ende-zu-Ende-Verschlüsselung, die für diesen Chat noch nicht hergestellt wurde. Tippen, um mehr zu erfahren.</string>
<string name="invalid_unencrypted_explanation">Um eine Ende-zu-Ende-Verschlüsselung herzustellen, können Sie Kontakte persönlich treffen und ihren QR-Code scannen.</string> <string name="invalid_unencrypted_explanation">Um eine Ende-zu-Ende-Verschlüsselung herzustellen, können Sie Kontakte persönlich treffen und ihren QR-Code scannen.</string>
@ -1033,16 +1037,19 @@
<string name="secure_join_started">%1$s hat dich zu dieser Gruppe eingeladen.\n\nWarte auf die Antwort des Gerätes von %2$s...</string> <string name="secure_join_started">%1$s hat dich zu dieser Gruppe eingeladen.\n\nWarte auf die Antwort des Gerätes von %2$s...</string>
<!-- placeholder will be replaced by the name of the inviter. --> <!-- placeholder will be replaced by the name of the inviter. -->
<string name="secure_join_replies">%1$s antwortet. Warte, zur Gruppe hinzugefügt zu werden...</string> <string name="secure_join_replies">%1$s antwortet. Warte, zur Gruppe hinzugefügt zu werden...</string>
<string name="secure_join_wait">Garantierte Ende-zu-Ende-Verschlüsselung wird aufgebaut, bitte warten...</string> <string name="secure_join_wait">Ende-zu-Ende-Verschlüsselung wird aufgebaut, bitte warten...</string>
<!-- deprecated --> <!-- deprecated -->
<string name="secure_join_wait_timeout">Noch konnte keine garantierte Ende-zu-Ende-Verschlüsselung aufgebaut werden, aber Sie können bereits eine Nachricht senden.</string> <string name="secure_join_wait_timeout">Noch konnte keine garantierte Ende-zu-Ende-Verschlüsselung aufgebaut werden, aber Sie können bereits eine Nachricht senden.</string>
<!-- deprecated, was stock string -->
<string name="secure_join_takes_longer">Der Kontakt muss online sein, um fortzufahren.\n\nDieser Vorgang wird automatisch im Hintergrund fortgesetzt.</string> <string name="secure_join_takes_longer">Der Kontakt muss online sein, um fortzufahren.\n\nDieser Vorgang wird automatisch im Hintergrund fortgesetzt.</string>
<string name="contact_verified">%1$s eingeführt.</string> <string name="contact_verified">%1$s eingeführt.</string>
<string name="contact_not_verified">Kann keine garantierte Ende-zu-Ende-Verschlüsselung mit %1$s herstellen.</string> <!-- deprecated, was stock string -->
<string name="contact_not_verified">Kann keine Ende-zu-Ende-Verschlüsselung mit %1$s herstellen.</string>
<!-- Shown in contact profile. The placeholder will be replaced by the name of the contact that introduced the contact. --> <!-- Shown in contact profile. The placeholder will be replaced by the name of the contact that introduced the contact. -->
<string name="verified_by">Eingeführt von %1$s</string> <string name="verified_by">Eingeführt von %1$s</string>
<string name="verified_by_you">Durch mich eingeführt</string> <string name="verified_by_you">Durch mich eingeführt</string>
<!-- translators: "setup" is the "encryption setup" here, as in "Autocrypt Setup Message" --> <string name="verified_by_unknown">Eingeführt</string>
<!-- deprecated, was stock string -->
<string name="contact_setup_changed">Geändertes Setup für %1$s</string> <string name="contact_setup_changed">Geändertes Setup für %1$s</string>
<string name="verified_contact_required_explain">Um Ende-zu-Ende-Verschlüsselung zu gewährleisten, können nur Kontakte mit grünem Häkchen zu dieser Gruppe hinzugefügt werden.\n\nSie könne Kontakte persönlich treffen und ihren QR-Code scannen, um sie einzuführen.</string> <string name="verified_contact_required_explain">Um Ende-zu-Ende-Verschlüsselung zu gewährleisten, können nur Kontakte mit grünem Häkchen zu dieser Gruppe hinzugefügt werden.\n\nSie könne Kontakte persönlich treffen und ihren QR-Code scannen, um sie einzuführen.</string>
<string name="mailto_dialog_header_select_chat">Wählen Sie den Chat, an den die Nachricht gesendet werden soll</string> <string name="mailto_dialog_header_select_chat">Wählen Sie den Chat, an den die Nachricht gesendet werden soll</string>
@ -1086,7 +1093,7 @@
<string name="ImageEditorHud_flip">Spiegeln</string> <string name="ImageEditorHud_flip">Spiegeln</string>
<string name="ImageEditorHud_rotate">Drehen</string> <string name="ImageEditorHud_rotate">Drehen</string>
<!-- dc_str_* resources --> <!-- deprecated, use string "E-Mail" for non-encrypted messages instead -->
<string name="encrypted_message">Verschlüsselte Nachricht</string> <string name="encrypted_message">Verschlüsselte Nachricht</string>
<!-- strings introduced on desktop. we want to share strings between the os, in general, please do not add generic strings here --> <!-- strings introduced on desktop. we want to share strings between the os, in general, please do not add generic strings here -->
@ -1217,6 +1224,9 @@
<string name="perm_enable_bg_already_done">Sie haben Delta Chat bereits erlaubt, Nachrichten im Hintergrund zu empfangen.\n\nFalls keine Nachrichten eingehen, überprüfen Sie bitte auch Ihre Systemeinstellungen.</string> <string name="perm_enable_bg_already_done">Sie haben Delta Chat bereits erlaubt, Nachrichten im Hintergrund zu empfangen.\n\nFalls keine Nachrichten eingehen, überprüfen Sie bitte auch Ihre Systemeinstellungen.</string>
<!-- device messages for updates --> <!-- device messages for updates -->
<string name="update_2_0">Was ist neu?\n\n💯 Die Ende-zu-Ende-Verschlüsselung ist jetzt dauerhaft. Vorhängeschlösser 🔒 gibt es nicht mehr!\n\n✉️ Klassische E-Mails ohne Ende-zu-Ende-Verschlüsselung sind mit einem Umschlag-Symbol gekennzeichnet\n\n😻 Neues, verbessertes Profil für alle Kontakte\n\n🔲 Neue Schaltfläche für den schnellen Zugriff auf Apps, die in einem Chat verwendet werden\n\n❤️ Bitte Spenden Sie und helfen uns, unabhängig zu bleiben und weiterhin Verbesserungen zu bringen: %1$s</string>
<!-- deprecated -->
<string name="update_1_50_android">Was ist neu?\n\n❤️‍🔥 Neuer Emoji-icker mit mehr Emojis\n\n🎮 In-Chat-App Verbesserungen: Benachrichtigungen erhalten und Apps im Kontext öffnen, z.B. einen hinzugefügten Kalendereintrag direkt anzeigen\n\n👍 Lassen Sie sich über Reaktionen auf Ihre Nachrichten benachrichtigen\n\n... 🛠️ FIXES und NOCH MEHR unter %1$s</string> <string name="update_1_50_android">Was ist neu?\n\n❤️‍🔥 Neuer Emoji-icker mit mehr Emojis\n\n🎮 In-Chat-App Verbesserungen: Benachrichtigungen erhalten und Apps im Kontext öffnen, z.B. einen hinzugefügten Kalendereintrag direkt anzeigen\n\n👍 Lassen Sie sich über Reaktionen auf Ihre Nachrichten benachrichtigen\n\n... 🛠️ FIXES und NOCH MEHR unter %1$s</string>
<!-- deprecated -->
<string name="update_switch_profile_placement">ℹ️ \"Profil wechseln\" verschoben: Tippen Sie auf Ihr Profilbild in der oberen Ecke des Hauptbildschirms, um Profile hinzuzufügen oder zu wechseln 💡.</string> <string name="update_switch_profile_placement">ℹ️ \"Profil wechseln\" verschoben: Tippen Sie auf Ihr Profilbild in der oberen Ecke des Hauptbildschirms, um Profile hinzuzufügen oder zu wechseln 💡.</string>
</resources> </resources>

7
src/main/res/values-el/strings.xml
View file

@ -427,7 +427,7 @@
<string name="all_apps_empty_hint">Οι ιδιωτικές εφαρμογές που λαμβάνονται ή αποστέλλονται σε οποιαδήποτε συνομιλία θα εμφανίζονται εδώ.</string> <string name="all_apps_empty_hint">Οι ιδιωτικές εφαρμογές που λαμβάνονται ή αποστέλλονται σε οποιαδήποτε συνομιλία θα εμφανίζονται εδώ.</string>
<string name="media_preview">Προεπισκόπιση</string> <string name="media_preview">Προεπισκόπιση</string>
<string name="send_message">Αποστολή μηνύματος</string> <string name="send_message">Αποστολή μηνύματος</string>
<!-- Placeholder %1$s will be replaced by the name of the contact changing their address. Placeholders %2$s and %3$s will be replaced by old/new addresses. --> <!-- deprecated, was stock string -->
<string name="aeap_addr_changed">%1$s άλλαξαν την διεύθυνσή τους από %2$s σε %3$s</string> <string name="aeap_addr_changed">%1$s άλλαξαν την διεύθυνσή τους από %2$s σε %3$s</string>
<!-- deprecated --> <!-- deprecated -->
<string name="aeap_explanation">Αλλάξατε την διεύθυνσή σας από %1$s σε %2$s.\n\nΤώρα, εάν στείλετε ένα μήνυμα σε μια επαληθευμένη ομάδα, οι επαφές εκεί θα αντικαταστήσουν αυτόματα την παλιά με τη νέα σας διεύθυνση.\n\nΣυνιστάται ιδιαίτερα να ρυθμίσετε τον παλιό σας πάροχο email ώστε να προωθεί όλα τα μηνύματα ηλεκτρονικού ταχυδρομείου στη νέα σας διεύθυνση ηλεκτρονικού ταχυδρομείου. Διαφορετικά, ενδέχεται να χάσετε μηνύματα επαφών που δεν έχουν λάβει ακόμη τη νέα σας διεύθυνση.</string> <string name="aeap_explanation">Αλλάξατε την διεύθυνσή σας από %1$s σε %2$s.\n\nΤώρα, εάν στείλετε ένα μήνυμα σε μια επαληθευμένη ομάδα, οι επαφές εκεί θα αντικαταστήσουν αυτόματα την παλιά με τη νέα σας διεύθυνση.\n\nΣυνιστάται ιδιαίτερα να ρυθμίσετε τον παλιό σας πάροχο email ώστε να προωθεί όλα τα μηνύματα ηλεκτρονικού ταχυδρομείου στη νέα σας διεύθυνση ηλεκτρονικού ταχυδρομείου. Διαφορετικά, ενδέχεται να χάσετε μηνύματα επαφών που δεν έχουν λάβει ακόμη τη νέα σας διεύθυνση.</string>
@ -773,8 +773,9 @@
<!-- placeholder will be replaced by the name of the inviter. --> <!-- placeholder will be replaced by the name of the inviter. -->
<string name="secure_join_replies">%1$s απάντησε, αναμονή για να προστεθεί στην ομάδα…</string> <string name="secure_join_replies">%1$s απάντησε, αναμονή για να προστεθεί στην ομάδα…</string>
<string name="contact_verified">%1$s επαληθεύτηκε.</string> <string name="contact_verified">%1$s επαληθεύτηκε.</string>
<!-- deprecated, was stock string -->
<string name="contact_not_verified">Αδυναμία επαλήθευσης %1$s.</string> <string name="contact_not_verified">Αδυναμία επαλήθευσης %1$s.</string>
<!-- translators: "setup" is the "encryption setup" here, as in "Autocrypt Setup Message" --> <!-- deprecated, was stock string -->
<string name="contact_setup_changed">Άλλαξε η ρύθμιση για %1$s.</string> <string name="contact_setup_changed">Άλλαξε η ρύθμιση για %1$s.</string>
<string name="mailto_dialog_header_select_chat">Επιλέξτε συνομιλία για να στείλετε το μήνυμα</string> <string name="mailto_dialog_header_select_chat">Επιλέξτε συνομιλία για να στείλετε το μήνυμα</string>
<!-- first placeholder is the name of the chat --> <!-- first placeholder is the name of the chat -->
@ -808,7 +809,7 @@
<string name="ImageEditorHud_flip">Εναλλαγή</string> <string name="ImageEditorHud_flip">Εναλλαγή</string>
<string name="ImageEditorHud_rotate">Περιστροφή</string> <string name="ImageEditorHud_rotate">Περιστροφή</string>
<!-- dc_str_* resources --> <!-- deprecated, use string "E-Mail" for non-encrypted messages instead -->
<string name="encrypted_message">Κρυπτογραφημένο μήνυμα</string> <string name="encrypted_message">Κρυπτογραφημένο μήνυμα</string>
<!-- strings introduced on desktop. we want to share strings between the os, in general, please do not add generic strings here --> <!-- strings introduced on desktop. we want to share strings between the os, in general, please do not add generic strings here -->

30
src/main/res/values-es/strings.xml
View file

@ -58,7 +58,7 @@
<string name="save">Guardar</string> <string name="save">Guardar</string>
<string name="chat">Chat</string> <string name="chat">Chat</string>
<string name="media">Multimedia</string> <string name="media">Multimedia</string>
<string name="apps_and_media">Apps y medias</string> <string name="apps_and_media">Apps y multimedia</string>
<string name="profile">Perfil</string> <string name="profile">Perfil</string>
<string name="all_profiles">Todos perfiles</string> <string name="all_profiles">Todos perfiles</string>
<string name="current_profile">Perfil actual</string> <string name="current_profile">Perfil actual</string>
@ -270,6 +270,11 @@
<string name="please_enter_broadcast_list_name">Por favor, introduce un nombre para la difusión.</string> <string name="please_enter_broadcast_list_name">Por favor, introduce un nombre para la difusión.</string>
<!-- consider keeping the term "channel" as in WhatsApp or Telegram --> <!-- consider keeping the term "channel" as in WhatsApp or Telegram -->
<string name="channel_name">Nombre del canal</string> <string name="channel_name">Nombre del canal</string>
<string name="email">Correo electrónico</string>
<!-- "New" as in "Create New E-Mail"; shown together with "New Group" and "New Channel" -->
<string name="new_email">Nuevo correo electrónico</string>
<!-- the "Subject" of an e-mail, use the term common in classic e-mail apps -->
<string name="subject">Asunto</string>
<string name="menu_send">Enviar</string> <string name="menu_send">Enviar</string>
<string name="menu_toggle_keyboard">Alternar teclado emoji</string> <string name="menu_toggle_keyboard">Alternar teclado emoji</string>
<string name="menu_edit_group">Editar grupo</string> <string name="menu_edit_group">Editar grupo</string>
@ -279,7 +284,7 @@
<string name="menu_unarchive_chat">Des-archivar chat</string> <string name="menu_unarchive_chat">Des-archivar chat</string>
<string name="menu_add_attachment">Añadir adjunto</string> <string name="menu_add_attachment">Añadir adjunto</string>
<string name="menu_leave_group">Abandonar grupo</string> <string name="menu_leave_group">Abandonar grupo</string>
<string name="menu_leave_channel">Salir del canal</string> <string name="menu_leave_channel">Abandonar canal</string>
<string name="menu_delete_chat">Eliminar chat</string> <string name="menu_delete_chat">Eliminar chat</string>
<!-- Command to delete all messages in a chat. The chat itself will not be deleted but will be empty afterwards, so make sure to be different from "Delete Chat" here. "Clear" is a verb here, "Empty Chat" would also be fine (eg. in German "Chat leeren") --> <!-- Command to delete all messages in a chat. The chat itself will not be deleted but will be empty afterwards, so make sure to be different from "Delete Chat" here. "Clear" is a verb here, "Empty Chat" would also be fine (eg. in German "Chat leeren") -->
<string name="clear_chat">Vaciar chat</string> <string name="clear_chat">Vaciar chat</string>
@ -306,7 +311,7 @@
<string name="menu_export_attachment">Exportar adjunto</string> <string name="menu_export_attachment">Exportar adjunto</string>
<string name="menu_export_attachments">Exportar adjuntos</string> <string name="menu_export_attachments">Exportar adjuntos</string>
<string name="menu_all_media">Toda la multimedia</string> <string name="menu_all_media">Toda la multimedia</string>
<string name="all_apps_and_media">Todas apps y medias</string> <string name="all_apps_and_media">Todas las apps y multimedia</string>
<!-- Command to jump to the original message corresponding to a gallery image or document --> <!-- Command to jump to the original message corresponding to a gallery image or document -->
<string name="show_in_chat">Mostrar en el chat</string> <string name="show_in_chat">Mostrar en el chat</string>
<string name="show_app_in_chat">Mostrar en el chat</string> <string name="show_app_in_chat">Mostrar en el chat</string>
@ -364,6 +369,7 @@
<!-- Menu item beside an app/chat that adds an icon to the system's home screen. If the user taps that icon, the app/chat is opened directly. --> <!-- Menu item beside an app/chat that adds an icon to the system's home screen. If the user taps that icon, the app/chat is opened directly. -->
<string name="add_to_home_screen">Añadir a la pantalla principal</string> <string name="add_to_home_screen">Añadir a la pantalla principal</string>
<string name="donate">Donar</string> <string name="donate">Donar</string>
<string name="donate_device_msg">❤️ ¡Parece que disfrutas de Delta Chat!\n\nPor favor, considera donar para ayudar a garantizar que Delta Chat siga siendo gratuito para todos.\n\nAunque Delta Chat es gratuito y de código abierto, su desarrollo cuesta dinero. Ayúdanos a mantener la independencia de Delta Chat y a hacerlo aún mejor en el futuro.\n\nhttps://delta.chat/donate</string>
<string name="mute_for_one_hour">Silenciar por 1 hora</string> <string name="mute_for_one_hour">Silenciar por 1 hora</string>
<string name="mute_for_eight_hours">Silenciar por 8 horas</string> <string name="mute_for_eight_hours">Silenciar por 8 horas</string>
@ -554,7 +560,7 @@
<string name="group_add_members">Añadir miembros</string> <string name="group_add_members">Añadir miembros</string>
<string name="group_self_not_in_group">Debes ser un miembro del grupo para realizar esta acción.</string> <string name="group_self_not_in_group">Debes ser un miembro del grupo para realizar esta acción.</string>
<string name="profile_encryption">Cifrado</string> <string name="profile_encryption">Cifrado</string>
<string name="profile_shared_chats">Chats compartidos</string> <string name="profile_shared_chats">Chats en común</string>
<string name="related_chats">Chats similares</string> <string name="related_chats">Chats similares</string>
<!-- Separator between the list of actual members and past members --> <!-- Separator between the list of actual members and past members -->
<string name="past_members">Miembros anteriores</string> <string name="past_members">Miembros anteriores</string>
@ -579,7 +585,7 @@
<!-- option to show images in the gallery as square (instead of using correct width/height) --> <!-- option to show images in the gallery as square (instead of using correct width/height) -->
<string name="square_grid">Cuadrícula cuadrada</string> <string name="square_grid">Cuadrícula cuadrada</string>
<string name="send_message">Enviar mensaje</string> <string name="send_message">Enviar mensaje</string>
<!-- Placeholder %1$s will be replaced by the name of the contact changing their address. Placeholders %2$s and %3$s will be replaced by old/new addresses. --> <!-- deprecated, was stock string -->
<string name="aeap_addr_changed">%1$s cambió su dirección de %2$s a %3$s</string> <string name="aeap_addr_changed">%1$s cambió su dirección de %2$s a %3$s</string>
<!-- deprecated --> <!-- deprecated -->
<string name="aeap_explanation">Has cambiado tu dirección de correo electrónico de %1$s a %2$s.\n\nSi ahora envías un mensaje a un grupo verificado, los contactos de éste sustituirán automáticamente la antigua por tu nueva dirección.\n\nEs muy recomendable que configures tu antiguo proveedor de correo electrónico para que reenvíe todos los mensajes a tu nueva dirección. De lo contrario, podrías perderte los mensajes de los contactos que aún no han recibido tu nueva dirección.</string> <string name="aeap_explanation">Has cambiado tu dirección de correo electrónico de %1$s a %2$s.\n\nSi ahora envías un mensaje a un grupo verificado, los contactos de éste sustituirán automáticamente la antigua por tu nueva dirección.\n\nEs muy recomendable que configures tu antiguo proveedor de correo electrónico para que reenvíe todos los mensajes a tu nueva dirección. De lo contrario, podrías perderte los mensajes de los contactos que aún no han recibido tu nueva dirección.</string>
@ -982,11 +988,13 @@
<string name="ephemeral_timer_weeks_by_you">Estableciste el temporizador de la desaparición de mensajes en %1$s semanas.</string> <string name="ephemeral_timer_weeks_by_you">Estableciste el temporizador de la desaparición de mensajes en %1$s semanas.</string>
<!-- %1$s will be replaced by the number of weeks (always >1) the timer is set to, %2$s will be replaced by name and address of the contact --> <!-- %1$s will be replaced by the number of weeks (always >1) the timer is set to, %2$s will be replaced by name and address of the contact -->
<string name="ephemeral_timer_weeks_by_other">Temporizador de la desaparición de mensajes establecido en %1$s semanas por %2$s.</string> <string name="ephemeral_timer_weeks_by_other">Temporizador de la desaparición de mensajes establecido en %1$s semanas por %2$s.</string>
<!-- this may be shown instead of the chat's input field, with buttons "More Info" and "OK" --> <!-- deprecated -->
<string name="chat_protection_broken">%1$s envió un mensaje desde otro dispositivo.</string> <string name="chat_protection_broken">%1$s envió un mensaje desde otro dispositivo.</string>
<string name="chat_protection_enabled_tap_to_learn_more">A partir de ahora se garantiza que los mensajes están cifrados de extremo a extremo . Toca para obtener más información.</string> <string name="chat_protection_enabled_tap_to_learn_more">A partir de ahora se garantiza que los mensajes están cifrados de extremo a extremo . Toca para obtener más información.</string>
<string name="chat_protection_enabled_explanation">Ahora se garantiza que todos los mensajes en este chat están cifrados de extremo a extremo.\n\nEl cifrado de extremo a extremo mantiene los mensajes privados entre tú y tus compañeros de chat. Ni siquiera tu proveedor de correo electrónico puede leerlos.</string> <string name="chat_protection_enabled_explanation">Ahora se garantiza que todos los mensajes en este chat están cifrados de extremo a extremo.\n\nEl cifrado de extremo a extremo mantiene los mensajes privados entre tú y tus compañeros de chat. Ni siquiera tu proveedor de correo electrónico puede leerlos.</string>
<!-- deprecated -->
<string name="chat_protection_broken_tap_to_learn_more">%1$s envió un mensaje desde otro dispositivo. Toca para obtener más información.</string> <string name="chat_protection_broken_tap_to_learn_more">%1$s envió un mensaje desde otro dispositivo. Toca para obtener más información.</string>
<!-- deprecated -->
<string name="chat_protection_broken_explanation">El cifrado de extremo a extremo ya no se puede garantizar, probablemente porque %1$s reinstaló Delta Chat o envió un mensaje desde otro dispositivo.\n\nPueden encontrarse en persona y escanear su código QR nuevamente para restablecer el cifrado de extremo a extremo garantizado.</string> <string name="chat_protection_broken_explanation">El cifrado de extremo a extremo ya no se puede garantizar, probablemente porque %1$s reinstaló Delta Chat o envió un mensaje desde otro dispositivo.\n\nPueden encontrarse en persona y escanear su código QR nuevamente para restablecer el cifrado de extremo a extremo garantizado.</string>
<string name="invalid_unencrypted_tap_to_learn_more">⚠️ %1$s requiere cifrado de extremo a extremo que aún no está configurado para este chat. Toca para obtener más información.</string> <string name="invalid_unencrypted_tap_to_learn_more">⚠️ %1$s requiere cifrado de extremo a extremo que aún no está configurado para este chat. Toca para obtener más información.</string>
<string name="invalid_unencrypted_explanation">Para establecer un cifrado de extremo a extremo, puede reunirse con los contactos en persona y escanear su código QR.</string> <string name="invalid_unencrypted_explanation">Para establecer un cifrado de extremo a extremo, puede reunirse con los contactos en persona y escanear su código QR.</string>
@ -1048,13 +1056,16 @@
<string name="secure_join_wait">Estableciendo cifrado de extremo a extremo garantizado, por favor, espere...</string> <string name="secure_join_wait">Estableciendo cifrado de extremo a extremo garantizado, por favor, espere...</string>
<!-- deprecated --> <!-- deprecated -->
<string name="secure_join_wait_timeout">No se pudo aún establecer el cifrado de extremo a extremo garantizado, pero ya puede enviar mensajes.</string> <string name="secure_join_wait_timeout">No se pudo aún establecer el cifrado de extremo a extremo garantizado, pero ya puede enviar mensajes.</string>
<!-- deprecated, was stock string -->
<string name="secure_join_takes_longer">El contacto debe estar en línea para continuar.\n\nEste proceso continuará automáticamente en segundo plano.</string> <string name="secure_join_takes_longer">El contacto debe estar en línea para continuar.\n\nEste proceso continuará automáticamente en segundo plano.</string>
<string name="contact_verified">%1$s verificado.</string> <string name="contact_verified">%1$s verificado.</string>
<!-- deprecated, was stock string -->
<string name="contact_not_verified">No se pudo verificar %1$s.</string> <string name="contact_not_verified">No se pudo verificar %1$s.</string>
<!-- Shown in contact profile. The placeholder will be replaced by the name of the contact that introduced the contact. --> <!-- Shown in contact profile. The placeholder will be replaced by the name of the contact that introduced the contact. -->
<string name="verified_by">Verificado por %1$s</string> <string name="verified_by">Verificado por %1$s</string>
<string name="verified_by_you">Verificado por ti</string> <string name="verified_by_you">Verificado por ti</string>
<!-- translators: "setup" is the "encryption setup" here, as in "Autocrypt Setup Message" --> <string name="verified_by_unknown">Introducido</string>
<!-- deprecated, was stock string -->
<string name="contact_setup_changed">Configuración cambiada para %1$s.</string> <string name="contact_setup_changed">Configuración cambiada para %1$s.</string>
<string name="verified_contact_required_explain">Para garantizar el cifrado de extremo a extremo, solo puedes añadir contactos con una marca de verificación verde</string> <string name="verified_contact_required_explain">Para garantizar el cifrado de extremo a extremo, solo puedes añadir contactos con una marca de verificación verde</string>
<string name="mailto_dialog_header_select_chat">Seleccione el chat para enviar el mensaje</string> <string name="mailto_dialog_header_select_chat">Seleccione el chat para enviar el mensaje</string>
@ -1098,7 +1109,7 @@
<string name="ImageEditorHud_flip">Voltear</string> <string name="ImageEditorHud_flip">Voltear</string>
<string name="ImageEditorHud_rotate">Rotar</string> <string name="ImageEditorHud_rotate">Rotar</string>
<!-- dc_str_* resources --> <!-- deprecated, use string "E-Mail" for non-encrypted messages instead -->
<string name="encrypted_message">Mensaje cifrado</string> <string name="encrypted_message">Mensaje cifrado</string>
<!-- strings introduced on desktop. we want to share strings between the os, in general, please do not add generic strings here --> <!-- strings introduced on desktop. we want to share strings between the os, in general, please do not add generic strings here -->
@ -1229,6 +1240,9 @@
<string name="perm_enable_bg_already_done">Ya has permitido que Delta Chat reciba mensajes en segundo plano.\n\nSi los mensajes aún no llegan en segundo plano, compruebe también la configuración de su sistema.</string> <string name="perm_enable_bg_already_done">Ya has permitido que Delta Chat reciba mensajes en segundo plano.\n\nSi los mensajes aún no llegan en segundo plano, compruebe también la configuración de su sistema.</string>
<!-- device messages for updates --> <!-- device messages for updates -->
<string name="update_2_0">¿Qué hay de nuevo?\n\n💯 El cifrado de extremo a extremo es fiable y para siempre. ¡Se acabaron los candados 🔒!\n\n✉️ El correo electrónico clásico sin cifrado de extremo a extremo es marcado con un símbolo de carta.\n\n😻 Nueva pantalla de perfil mejorada para todos tus contactos.\n\n🔲 Nuevo botón para acceder rápidamente a las apps usadas en el chat.\n\n❤️ Dona para ayudarnos a mantener nuestra independencia y seguir mejorando: %1$s</string>
<!-- deprecated -->
<string name="update_1_50_android">¿Qué hay de nuevo?\n\n❤️‍🔥 Nuevo selector de emojis con más emojis\n\n🎮 Aplicaciones de chat mejoradas: recibe notificaciones y abre aplicaciones en contexto, por ejemplo, abre una entrada de calendario agregada directamente\n\n👍 Recibe notificaciones sobre las reacciones a tus mensajes\n\n... 🛠️ CORRECCIONES y AÚN MÁS en %1$s</string> <string name="update_1_50_android">¿Qué hay de nuevo?\n\n❤️‍🔥 Nuevo selector de emojis con más emojis\n\n🎮 Aplicaciones de chat mejoradas: recibe notificaciones y abre aplicaciones en contexto, por ejemplo, abre una entrada de calendario agregada directamente\n\n👍 Recibe notificaciones sobre las reacciones a tus mensajes\n\n... 🛠️ CORRECCIONES y AÚN MÁS en %1$s</string>
<!-- deprecated -->
<string name="update_switch_profile_placement">ℹ️ Se movió la opción \"Cambiar perfil\": toca tu imagen de perfil en la esquina superior de la pantalla principal para agregar o cambiar perfiles 💡</string> <string name="update_switch_profile_placement">ℹ️ Se movió la opción \"Cambiar perfil\": toca tu imagen de perfil en la esquina superior de la pantalla principal para agregar o cambiar perfiles 💡</string>
</resources> </resources>

5
src/main/res/values-eu/strings.xml
View file

@ -447,8 +447,9 @@
<string name="qraccount_ask_create_and_login">Sortu kontu berria \"%1$s\" zerbitzarian eta saioa han hasi?</string> <string name="qraccount_ask_create_and_login">Sortu kontu berria \"%1$s\" zerbitzarian eta saioa han hasi?</string>
<string name="qraccount_qr_code_cannot_be_used">Eskaneatutako QR kodea ezin da kontu berri bat ezartzeko erabili.</string> <string name="qraccount_qr_code_cannot_be_used">Eskaneatutako QR kodea ezin da kontu berri bat ezartzeko erabili.</string>
<string name="contact_verified">%1$s egiaztatuta.</string> <string name="contact_verified">%1$s egiaztatuta.</string>
<!-- deprecated, was stock string -->
<string name="contact_not_verified">Ezin da %1$s egiaztatu</string> <string name="contact_not_verified">Ezin da %1$s egiaztatu</string>
<!-- translators: "setup" is the "encryption setup" here, as in "Autocrypt Setup Message" --> <!-- deprecated, was stock string -->
<string name="contact_setup_changed">Aldatu %1$s(r)en ezarpena</string> <string name="contact_setup_changed">Aldatu %1$s(r)en ezarpena</string>
<!-- notifications --> <!-- notifications -->
<string name="notify_reply_button">Erantzun</string> <string name="notify_reply_button">Erantzun</string>
@ -467,7 +468,7 @@
<string name="perm_explain_access_to_mic_denied">Delta Chat-ek mikrofonoa erabiltzeko baimena behar du ahots-mezuak bidali ahal izateko, baina behin betiko ukatu zaio. Joan aplikazioaren ezarpenetara, hautatu \"Baimenak\" eta gaitu \"Mikrofonoa\".</string> <string name="perm_explain_access_to_mic_denied">Delta Chat-ek mikrofonoa erabiltzeko baimena behar du ahots-mezuak bidali ahal izateko, baina behin betiko ukatu zaio. Joan aplikazioaren ezarpenetara, hautatu \"Baimenak\" eta gaitu \"Mikrofonoa\".</string>
<string name="perm_explain_access_to_storage_denied">Delta Chat-ek biltegiratze baimena behar du argazkiak, bideoak edo audioa erantsi edo esportatzeko, baina behin betiko ukatu zaio. Joan aplikazioaren ezarpen menura, hautatu \"baimenak\", eta gaitu \"Biltegiratzea\"</string> <string name="perm_explain_access_to_storage_denied">Delta Chat-ek biltegiratze baimena behar du argazkiak, bideoak edo audioa erantsi edo esportatzeko, baina behin betiko ukatu zaio. Joan aplikazioaren ezarpen menura, hautatu \"baimenak\", eta gaitu \"Biltegiratzea\"</string>
<string name="perm_explain_access_to_location_denied">Delta Chat-ek kokaleku aatzitzeko baimena behar du kokalekua eransteko, baina behin betiko ukatu zaio. Joan aplikazioaren ezarpen menura, hautatu \"baimenak\", eta gaitu \"Kokalekua\".</string> <string name="perm_explain_access_to_location_denied">Delta Chat-ek kokaleku aatzitzeko baimena behar du kokalekua eransteko, baina behin betiko ukatu zaio. Joan aplikazioaren ezarpen menura, hautatu \"baimenak\", eta gaitu \"Kokalekua\".</string>
<!-- dc_str_* resources --> <!-- deprecated, use string "E-Mail" for non-encrypted messages instead -->
<string name="encrypted_message">Zifratutako mezua</string> <string name="encrypted_message">Zifratutako mezua</string>
<string name="welcome_desktop">Ongi etorri Delta Chat-era</string> <string name="welcome_desktop">Ongi etorri Delta Chat-era</string>

54
src/main/res/values-fa/strings.xml
View file

@ -34,6 +34,8 @@
<string name="update">به‌‌روزرسانی</string> <string name="update">به‌‌روزرسانی</string>
<string name="emoji">شکلک</string> <string name="emoji">شکلک</string>
<string name="attachment">پیوست</string> <string name="attachment">پیوست</string>
<!-- the placeholder will be replaced by the name of the image or file to attach -->
<string name="ask_attach">پیوست کردن «%1$s»؟</string>
<string name="back">بازگشت</string> <string name="back">بازگشت</string>
<string name="close">بستن</string> <string name="close">بستن</string>
<string name="close_window">بستن پنجره</string> <string name="close_window">بستن پنجره</string>
@ -58,6 +60,8 @@
<string name="media">رسانه</string> <string name="media">رسانه</string>
<string name="apps_and_media">برنامه‌ها و رسانه‌ها</string> <string name="apps_and_media">برنامه‌ها و رسانه‌ها</string>
<string name="profile">نمایه</string> <string name="profile">نمایه</string>
<string name="all_profiles">تمام نمایه‌ها</string>
<string name="current_profile">نمایهٔ فعلی</string>
<string name="main_menu">فهرست اصلی</string> <string name="main_menu">فهرست اصلی</string>
<string name="start_chat">شروع گپ</string> <string name="start_chat">شروع گپ</string>
<string name="show_full_message">نمایش پیام کامل...</string> <string name="show_full_message">نمایش پیام کامل...</string>
@ -92,6 +96,8 @@
<string name="no_app_to_handle_data">نرم‌افزاری برای باز کردن این نوع داده یافت نشد</string> <string name="no_app_to_handle_data">نرم‌افزاری برای باز کردن این نوع داده یافت نشد</string>
<string name="no_browser_installed">هیچ مرورگری نصب نیست.</string> <string name="no_browser_installed">هیچ مرورگری نصب نیست.</string>
<string name="file_not_found">عدم یافتن %1$s</string> <string name="file_not_found">عدم یافتن %1$s</string>
<!-- the placeholder will be replaced by the name of a file -->
<string name="cannot_save_file">نمی‌توان %1$s را ذخیره کرد.</string>
<string name="copied_to_clipboard">در حافظه کپی شد.</string> <string name="copied_to_clipboard">در حافظه کپی شد.</string>
<string name="contacts_headline">مخاطبین</string> <string name="contacts_headline">مخاطبین</string>
<string name="email_address">نشانی رایانامه</string> <string name="email_address">نشانی رایانامه</string>
@ -151,6 +157,7 @@
<item quantity="one">تعداد %d انتخاب شده است</item> <item quantity="one">تعداد %d انتخاب شده است</item>
<item quantity="other">تعداد %dانتخاب شده است</item> <item quantity="other">تعداد %dانتخاب شده است</item>
</plurals> </plurals>
<string name="selected_colon">انتخاب شده‌ها:</string>
<string name="self">من</string> <string name="self">من</string>
<string name="draft">پیش‌نویس</string> <string name="draft">پیش‌نویس</string>
<string name="image">تصویر</string> <string name="image">تصویر</string>
@ -238,6 +245,12 @@
<string name="broadcast_lists">لیست‌های Broadcast</string> <string name="broadcast_lists">لیست‌های Broadcast</string>
<!-- deprecated --> <!-- deprecated -->
<string name="new_broadcast_list">لیست Broadcast جدید</string> <string name="new_broadcast_list">لیست Broadcast جدید</string>
<!-- consider keeping the term "channel" as in WhatsApp or Telegram -->
<string name="channel">کانال</string>
<!-- consider keeping the term "channel" as in WhatsApp or Telegram -->
<string name="channels">کانال‌ها</string>
<!-- consider keeping the term "channel" as in WhatsApp or Telegram -->
<string name="new_channel">کانال جدید</string>
<string name="add_recipients">افزودن گیرنده</string> <string name="add_recipients">افزودن گیرنده</string>
<!-- deprecated --> <!-- deprecated -->
<string name="edit_broadcast_list">ویرایش فهرست Broadcast</string> <string name="edit_broadcast_list">ویرایش فهرست Broadcast</string>
@ -245,6 +258,12 @@
<string name="broadcast_list_name">نام فهرست BroadCast</string> <string name="broadcast_list_name">نام فهرست BroadCast</string>
<!-- deprecated --> <!-- deprecated -->
<string name="please_enter_broadcast_list_name">وارد کردن نام برای فهرست Broadcast.</string> <string name="please_enter_broadcast_list_name">وارد کردن نام برای فهرست Broadcast.</string>
<!-- consider keeping the term "channel" as in WhatsApp or Telegram -->
<string name="channel_name">نام کانال</string>
<!-- "New" as in "Create New E-Mail"; shown together with "New Group" and "New Channel" -->
<string name="new_email">رایانامه جدید</string>
<!-- the "Subject" of an e-mail, use the term common in classic e-mail apps -->
<string name="subject">موضوع</string>
<string name="menu_send">ارسال</string> <string name="menu_send">ارسال</string>
<string name="menu_toggle_keyboard">تعییر صفحه کلید شکلک‌ها</string> <string name="menu_toggle_keyboard">تعییر صفحه کلید شکلک‌ها</string>
<string name="menu_edit_group">ویرایش گروه</string> <string name="menu_edit_group">ویرایش گروه</string>
@ -254,6 +273,7 @@
<string name="menu_unarchive_chat">خروج چت از بایگانی</string> <string name="menu_unarchive_chat">خروج چت از بایگانی</string>
<string name="menu_add_attachment">افزودن ضمیمه</string> <string name="menu_add_attachment">افزودن ضمیمه</string>
<string name="menu_leave_group">ترک گروه</string> <string name="menu_leave_group">ترک گروه</string>
<string name="menu_leave_channel">ترک کانال</string>
<string name="menu_delete_chat">حذف گپ</string> <string name="menu_delete_chat">حذف گپ</string>
<!-- Command to delete all messages in a chat. The chat itself will not be deleted but will be empty afterwards, so make sure to be different from "Delete Chat" here. "Clear" is a verb here, "Empty Chat" would also be fine (eg. in German "Chat leeren") --> <!-- Command to delete all messages in a chat. The chat itself will not be deleted but will be empty afterwards, so make sure to be different from "Delete Chat" here. "Clear" is a verb here, "Empty Chat" would also be fine (eg. in German "Chat leeren") -->
<string name="clear_chat">پاک کردن چت</string> <string name="clear_chat">پاک کردن چت</string>
@ -340,6 +360,7 @@
<!-- Menu item beside an app/chat that adds an icon to the system's home screen. If the user taps that icon, the app/chat is opened directly. --> <!-- Menu item beside an app/chat that adds an icon to the system's home screen. If the user taps that icon, the app/chat is opened directly. -->
<string name="add_to_home_screen">افزودن به صفحه خانه</string> <string name="add_to_home_screen">افزودن به صفحه خانه</string>
<string name="donate">حمایت مالی</string> <string name="donate">حمایت مالی</string>
<string name="donate_device_msg">❤️ بنظر می‌آید شما در حال لذت بردن از دلتاچت هستید!\n\nلطفا هدیه دهید تا مطمئن باشیم دلتاچت برای همه آزاد باقی می‌ماند.\n\nبا وجودی که دلتاچت برای استفاده رایگان است و یک نرم‌افزار آزاد نیز هست، توسعهٔ آن هزینه دارد. به ما کمک کنید تا دلتاچت را مستقل نگه‌داریم و در آینده حتی آن‌را خفن‌تر کنیم. هدایا از طریق رمزارز نیز پذیرفته می‌شوند.\n\nhttps://delta.chat/donate</string>
<string name="mute_for_one_hour">ساکت کردن به مدت۱ ساعت</string> <string name="mute_for_one_hour">ساکت کردن به مدت۱ ساعت</string>
<string name="mute_for_eight_hours">بی‌صدا کردن به مدت ۸ ساعت</string> <string name="mute_for_eight_hours">بی‌صدا کردن به مدت ۸ ساعت</string>
@ -378,6 +399,9 @@ https://meet.jit.si/$ROOM
<string name="videochat_invitation">دعوت به مکالمه تصویری.</string> <string name="videochat_invitation">دعوت به مکالمه تصویری.</string>
<string name="videochat_invitation_body">شما به مکالمه تصویری دعوت شده اید برای پیوستن%1$s را بزنید.</string> <string name="videochat_invitation_body">شما به مکالمه تصویری دعوت شده اید برای پیوستن%1$s را بزنید.</string>
<!-- get confirmations -->
<!-- confirmation for leaving groups, channels, broadcasts or a mailinglists. If a subject is needed, "Are you sure you want to leave the chat?" would work as well -->
<string name="ask_leave_group">آیا مطمئنید می‌خواهید بروید؟</string>
<plurals name="ask_delete_chat"> <plurals name="ask_delete_chat">
<item quantity="one">آیا می‌خواهید از روی همهٔ دستگاه‌هایتان %d گپ را حذف کنید؟</item> <item quantity="one">آیا می‌خواهید از روی همهٔ دستگاه‌هایتان %d گپ را حذف کنید؟</item>
<item quantity="other">آیا می‌خواهید از روی همهٔ دستگاه‌هایتان %d گپ را حذف کنید؟</item> <item quantity="other">آیا می‌خواهید از روی همهٔ دستگاه‌هایتان %d گپ را حذف کنید؟</item>
@ -407,6 +431,8 @@ https://meet.jit.si/$ROOM
<string name="ask_remove_members">حذف %1$s از گروه؟</string> <string name="ask_remove_members">حذف %1$s از گروه؟</string>
<!-- deprecated --> <!-- deprecated -->
<string name="ask_remove_from_broadcast">آيا%1$s از لیست Broadcast پاک شود؟ </string> <string name="ask_remove_from_broadcast">آيا%1$s از لیست Broadcast پاک شود؟ </string>
<!-- %1$s is replaced by a comma-separated list of names -->
<string name="ask_remove_from_channel">حذف %1$s از کانال؟</string>
<string name="open_url_confirmation">آیا می‌خواهید این لینک را باز کنید؟</string> <string name="open_url_confirmation">آیا می‌خواهید این لینک را باز کنید؟</string>
@ -438,6 +464,8 @@ https://meet.jit.si/$ROOM
<string name="chat_new_one_to_one_hint">ارسال پیام. مشکلی نیست اگر %1$s از دلتاچت استفاده نمی‌کند.</string> <string name="chat_new_one_to_one_hint">ارسال پیام. مشکلی نیست اگر %1$s از دلتاچت استفاده نمی‌کند.</string>
<!-- deprecated --> <!-- deprecated -->
<string name="chat_new_broadcast_hint">در یک فهرست Broadcast گیرنده‌ها در یک گپ فقط خواندنی با شما، پیام‌ها را دریافت می‌کنند.</string> <string name="chat_new_broadcast_hint">در یک فهرست Broadcast گیرنده‌ها در یک گپ فقط خواندنی با شما، پیام‌ها را دریافت می‌کنند.</string>
<!-- consider keeping the term "channel" as in WhatsApp or Telegram -->
<string name="chat_new_channel_hint">کانال‌ها یک ابزار یک به چند برای اعلام عمومی پیام‌هایتان هستند.</string>
<string name="chat_new_group_hint">نوشتن اولین پیام به دیگران امکان می‌دهد در این گروه پاسخ دهند. \n\n• مشکلی نیست اگر همه اعضا از دلتاچت استفاده نکنند\n\n• دریافت اولین پیام ممکن است به زمان بیشتری نیاز داشته باشد. </string> <string name="chat_new_group_hint">نوشتن اولین پیام به دیگران امکان می‌دهد در این گروه پاسخ دهند. \n\n• مشکلی نیست اگر همه اعضا از دلتاچت استفاده نکنند\n\n• دریافت اولین پیام ممکن است به زمان بیشتری نیاز داشته باشد. </string>
<string name="chat_record_slide_to_cancel">برای لغو بکشید.</string> <string name="chat_record_slide_to_cancel">برای لغو بکشید.</string>
<string name="chat_record_explain">برای ضبط پیام صوتی فشار داده و نگهدارید، برای ارسال رها کنید. </string> <string name="chat_record_explain">برای ضبط پیام صوتی فشار داده و نگهدارید، برای ارسال رها کنید. </string>
@ -447,6 +475,7 @@ https://meet.jit.si/$ROOM
<string name="chat_input_placeholder">پیام</string> <string name="chat_input_placeholder">پیام</string>
<string name="chat_archived_label">بایگانی شد</string> <string name="chat_archived_label">بایگانی شد</string>
<string name="chat_request_label">درخواست</string> <string name="chat_request_label">درخواست</string>
<string name="chat_request_label_explain">حساب کردن درخواست‌ها در شمارنده‌ها و اعلان‌ها</string>
<string name="chat_no_messages">پیامی نیست. </string> <string name="chat_no_messages">پیامی نیست. </string>
<string name="chat_self_talk_subtitle">پیام‌هایی که برای خودم ارسال کرده‌ام. </string> <string name="chat_self_talk_subtitle">پیام‌هایی که برای خودم ارسال کرده‌ام. </string>
<string name="archive_empty_hint">اگر گپ‌ها را بایگانی کنید در اینجا نمایش داده می‌شوند. </string> <string name="archive_empty_hint">اگر گپ‌ها را بایگانی کنید در اینجا نمایش داده می‌شوند. </string>
@ -537,6 +566,7 @@ https://meet.jit.si/$ROOM
<string name="tab_audio_empty_hint">پرونده‌های صوتی و پیام‌های صوتی هم‌رسانده در این گپ اینجا نمایش داده می‌شوند.</string> <string name="tab_audio_empty_hint">پرونده‌های صوتی و پیام‌های صوتی هم‌رسانده در این گپ اینجا نمایش داده می‌شوند.</string>
<string name="tab_webxdc_empty_hint">برنامه‌هایی که در این گپ به اشتراک گذاشته شده‌اند، این‌جا نمایش داده خواهند شد.</string> <string name="tab_webxdc_empty_hint">برنامه‌هایی که در این گپ به اشتراک گذاشته شده‌اند، این‌جا نمایش داده خواهند شد.</string>
<string name="tab_all_media_empty_hint">رسانه‌های به اشتراک گذاشته شده همهٔ چت‌ها در اینجا ظاهر می‌شود.</string> <string name="tab_all_media_empty_hint">رسانه‌های به اشتراک گذاشته شده همهٔ چت‌ها در اینجا ظاهر می‌شود.</string>
<string name="all_files_empty_hint">سند‌ها و دیگر پرونده‌هایی که در هر چپ پیوست شده‌اند این‌جا ظاهر خواهند شد.</string>
<string name="all_apps_empty_hint">برنامه‌های ارسال شده در همهٔ گپ‌ها اینجا ظاهر خواهند شد.</string> <string name="all_apps_empty_hint">برنامه‌های ارسال شده در همهٔ گپ‌ها اینجا ظاهر خواهند شد.</string>
<string name="media_preview">نمایش رسانه</string> <string name="media_preview">نمایش رسانه</string>
<!-- option to show images in the gallery with the correct width/height aspect (instead of square); other gallery apps may be a source of inspiration for translation :) --> <!-- option to show images in the gallery with the correct width/height aspect (instead of square); other gallery apps may be a source of inspiration for translation :) -->
@ -544,7 +574,7 @@ https://meet.jit.si/$ROOM
<!-- option to show images in the gallery as square (instead of using correct width/height) --> <!-- option to show images in the gallery as square (instead of using correct width/height) -->
<string name="square_grid">جدول مربعی</string> <string name="square_grid">جدول مربعی</string>
<string name="send_message">ارسال پیام</string> <string name="send_message">ارسال پیام</string>
<!-- Placeholder %1$s will be replaced by the name of the contact changing their address. Placeholders %2$s and %3$s will be replaced by old/new addresses. --> <!-- deprecated, was stock string -->
<string name="aeap_addr_changed">مخاطب %1$s نشانی خود را از %2$s به %3$s تغییر داده است. </string> <string name="aeap_addr_changed">مخاطب %1$s نشانی خود را از %2$s به %3$s تغییر داده است. </string>
<!-- deprecated --> <!-- deprecated -->
<string name="aeap_explanation">شما نشانی رایانامهٔ خود را از %1$s به %2$s تغییر دادید.\n\nاگر به یک گروه تأیید شده پیام بفرستید، مخاطبان آن به صورت خودکار نشانی جدید را جایگزین نشانی پیشین می‌کنند.\n\nبه شدت توصیه می‌شود که نشانی رایانامهٔ پیشین خود را به نحوی تنظیم کنید که تمام رایانامه‌ها را به نشانی جدید شما هدایت کند؛ در غیر این صورت ممکن است پیام‌های مخاطبانی که از تغییر نشانی شما مطلع نشده‌اند را از دست بدهید. </string> <string name="aeap_explanation">شما نشانی رایانامهٔ خود را از %1$s به %2$s تغییر دادید.\n\nاگر به یک گروه تأیید شده پیام بفرستید، مخاطبان آن به صورت خودکار نشانی جدید را جایگزین نشانی پیشین می‌کنند.\n\nبه شدت توصیه می‌شود که نشانی رایانامهٔ پیشین خود را به نحوی تنظیم کنید که تمام رایانامه‌ها را به نشانی جدید شما هدایت کند؛ در غیر این صورت ممکن است پیام‌های مخاطبانی که از تغییر نشانی شما مطلع نشده‌اند را از دست بدهید. </string>
@ -563,6 +593,8 @@ https://meet.jit.si/$ROOM
<string name="multidevice_receiver_title">افزودن به عنوان دستگاه دوم</string> <string name="multidevice_receiver_title">افزودن به عنوان دستگاه دوم</string>
<string name="multidevice_open_settings_on_other_device">در دستگاه اول، به \"تنظیم‌ها / افزودن دستگاه دوم\" بروید و کد نشان داده شده در آنجا را اسکن کنید</string> <string name="multidevice_open_settings_on_other_device">در دستگاه اول، به \"تنظیم‌ها / افزودن دستگاه دوم\" بروید و کد نشان داده شده در آنجا را اسکن کنید</string>
<string name="multidevice_receiver_scanning_ask">از حساب دستگاه دیگر رونوشتی برای این دستگاه گرفته شود؟</string> <string name="multidevice_receiver_scanning_ask">از حساب دستگاه دیگر رونوشتی برای این دستگاه گرفته شود؟</string>
<string name="multidevice_receiver_needs_update">نمایه‌ای که می‌خواهید وارد کنید از یک نسخهٔ جدید‌تر دلتاچت است.\n\n
برای پیکره‌بندی یک دستگاه دوم، لطفا این دستگاه را به جدیدترین نسخهٔ دلتاچت بروزرسانی کنید.</string>
<string name="multidevice_abort">راه اندازی دستگاه دوم لغو شود؟</string> <string name="multidevice_abort">راه اندازی دستگاه دوم لغو شود؟</string>
<string name="multidevice_abort_will_invalidate_copied_qr">این کار رمزینهٔ پاس رونوشت شده در تخته‌گیره را باطل می کند.</string> <string name="multidevice_abort_will_invalidate_copied_qr">این کار رمزینهٔ پاس رونوشت شده در تخته‌گیره را باطل می کند.</string>
<string name="multidevice_transfer_done_devicemsg">ℹ️ حساب به دستگاه دوم شما منتقل شد.</string> <string name="multidevice_transfer_done_devicemsg">ℹ️ حساب به دستگاه دوم شما منتقل شد.</string>
@ -679,6 +711,8 @@ https://meet.jit.si/$ROOM
<string name="profile_tag">برچسب حساب</string> <string name="profile_tag">برچسب حساب</string>
<string name="profile_tag_hint">مثل «کار» یا «خانواده»</string> <string name="profile_tag_hint">مثل «کار» یا «خانواده»</string>
<string name="profile_tag_explain">یک برچسب انتخاب کنید که تنها به شما نمایش داده می‌شود. این به شما کمک می‌کند حساب‌های مختلف خود را از هم تشخیص دهید.</string> <string name="profile_tag_explain">یک برچسب انتخاب کنید که تنها به شما نمایش داده می‌شود. این به شما کمک می‌کند حساب‌های مختلف خود را از هم تشخیص دهید.</string>
<!-- Menu entry to sort an item to the beginning of a list. Only "To Top" may do as well in some translations, if that helps to stay shorter. -->
<string name="move_to_top">رفتن به بالا</string>
<string name="delete_account">حذف حساب کاربری</string> <string name="delete_account">حذف حساب کاربری</string>
<string name="delete_account_ask">آیا از حذف حساب کاربری اطمینان دارید؟</string> <string name="delete_account_ask">آیا از حذف حساب کاربری اطمینان دارید؟</string>
<string name="delete_account_explain_with_name">همه اطلاعات حساب مربوط به «%s» روی این دستگاه پاک می‌شود. این شامل تنظیم‌های رمزگذاری سراسری، مخاطبین، گفتگوها، پیام‌ها و رسانه‌ها می‌شود. این عمل قابل بازگردانی نیست.</string> <string name="delete_account_explain_with_name">همه اطلاعات حساب مربوط به «%s» روی این دستگاه پاک می‌شود. این شامل تنظیم‌های رمزگذاری سراسری، مخاطبین، گفتگوها، پیام‌ها و رسانه‌ها می‌شود. این عمل قابل بازگردانی نیست.</string>
@ -812,6 +846,7 @@ https://meet.jit.si/$ROOM
<string name="n_bytes_message">پیام %1$s </string> <string name="n_bytes_message">پیام %1$s </string>
<!-- %1$s will be replaced by human-readable date and time --> <!-- %1$s will be replaced by human-readable date and time -->
<string name="download_max_available_until">سقف دانلود تا %1$s فعال خواهد بود</string> <string name="download_max_available_until">سقف دانلود تا %1$s فعال خواهد بود</string>
<string name="select_profile">انتخاب نمایه</string>
<string name="profile_image_select">انتخاب تصویر نمایه</string> <string name="profile_image_select">انتخاب تصویر نمایه</string>
<string name="select_your_new_profile_image">تصویر نمایهٔ جدیدتان را برگزینید</string> <string name="select_your_new_profile_image">تصویر نمایهٔ جدیدتان را برگزینید</string>
<string name="profile_image_delete">حذف تصویر نمایه</string> <string name="profile_image_delete">حذف تصویر نمایه</string>
@ -897,6 +932,8 @@ https://meet.jit.si/$ROOM
<string name="remove_member_by_you">شما عضو گروه، %1$s، را حذف کردید. </string> <string name="remove_member_by_you">شما عضو گروه، %1$s، را حذف کردید. </string>
<!-- %1$s will be replaced by name and address of the contact removed from the group, %2$s will be replaced by name and address of the contact who did the action --> <!-- %1$s will be replaced by name and address of the contact removed from the group, %2$s will be replaced by name and address of the contact who did the action -->
<string name="remove_member_by_other">عضو گروه، %1$s، توسط %2$s حذف شد. </string> <string name="remove_member_by_other">عضو گروه، %1$s، توسط %2$s حذف شد. </string>
<!-- "left" in the meaning of "exited". This string is added to a chat after groups, channels, broadcasts or mailinglists are left. If a subject is needed, "You left the chat." would work as well. -->
<string name="group_left_by_you">شما این‌جا را ترک کردید.</string>
<!-- "left" in the meaning of "exited"; %1$s will be replaced by name and address of the contact leaving the group --> <!-- "left" in the meaning of "exited"; %1$s will be replaced by name and address of the contact leaving the group -->
<string name="group_left_by_other">ترک گروه توسط %1$s.</string> <string name="group_left_by_other">ترک گروه توسط %1$s.</string>
<string name="group_image_deleted_by_you">شما تصویر گروه را حذف کردید.</string> <string name="group_image_deleted_by_you">شما تصویر گروه را حذف کردید.</string>
@ -940,12 +977,14 @@ https://meet.jit.si/$ROOM
<string name="ephemeral_timer_weeks_by_you">زمان‌سنج ناپدید شدن پیام‌ها را روی %1$s هفته تنظیم کردید.</string> <string name="ephemeral_timer_weeks_by_you">زمان‌سنج ناپدید شدن پیام‌ها را روی %1$s هفته تنظیم کردید.</string>
<!-- %1$s will be replaced by the number of weeks (always >1) the timer is set to, %2$s will be replaced by name and address of the contact --> <!-- %1$s will be replaced by the number of weeks (always >1) the timer is set to, %2$s will be replaced by name and address of the contact -->
<string name="ephemeral_timer_weeks_by_other">زمان‌سنج ناپدید شدن پیام‌ها توسط %2$s روی %1$s هفته تنظیم شد.</string> <string name="ephemeral_timer_weeks_by_other">زمان‌سنج ناپدید شدن پیام‌ها توسط %2$s روی %1$s هفته تنظیم شد.</string>
<!-- this may be shown instead of the chat's input field, with buttons "More Info" and "OK" --> <!-- deprecated -->
<string name="chat_protection_broken">%1$s پیامی را از دستگاه دیگری ارسال کرد.</string> <string name="chat_protection_broken">%1$s پیامی را از دستگاه دیگری ارسال کرد.</string>
<string name="chat_protection_enabled_tap_to_learn_more">رمزنگاری سرتاسر پیام ها از این به بعد تضمین می شود. برای اطلاعات بیشتر ضربه بزنید.</string> <string name="chat_protection_enabled_tap_to_learn_more">رمزنگاری سرتاسر پیام ها از این به بعد تضمین می شود. برای اطلاعات بیشتر ضربه بزنید.</string>
<string name="chat_protection_enabled_explanation">رمزنگاری سراسری پیام‌های این گفتگو اکنون تضمین می‌شود. رمزنگاری سراسری باعث می‌شود پیام‌هایتان بین شما و مخاطبین شما محرمانه بماند. حتی ارائه‌دهندهٔ رایانامه شما هم نمی‌تواند آن‌ها را بخواند.</string> <string name="chat_protection_enabled_explanation">رمزنگاری سراسری پیام‌های این گفتگو اکنون تضمین می‌شود. رمزنگاری سراسری باعث می‌شود پیام‌هایتان بین شما و مخاطبین شما محرمانه بماند. حتی ارائه‌دهندهٔ رایانامه شما هم نمی‌تواند آن‌ها را بخواند.</string>
<!-- deprecated -->
<string name="chat_protection_broken_tap_to_learn_more">%1$s پیامی را از دستگاه دیگری ارسال کرد. برای اطلاعات بیشتر ضربه بزنید.</string> <string name="chat_protection_broken_tap_to_learn_more">%1$s پیامی را از دستگاه دیگری ارسال کرد. برای اطلاعات بیشتر ضربه بزنید.</string>
<string name="invalid_unencrypted_tap_to_learn_more">⚠️ %1$s به رمزنگاری سراسری نیاز دارد که هنوز برای این گپ پیکره‌بندی نشده است. برای یادگیری بیش‌تر این‌جا بزنید.</string> <string name="invalid_unencrypted_tap_to_learn_more">⚠️ %1$s به رمزنگاری سراسری نیاز دارد که هنوز برای این گپ پیکره‌بندی نشده است. برای یادگیری بیش‌تر این‌جا بزنید.</string>
<string name="invalid_unencrypted_explanation">برای برقراری رمزنگاری سراسری، می‌توانید به صورت حضوری با مخاطب‌های خود دیدار کنید و کد کیوآر آن‌ها را برای معرفی اسکن کنید.</string>
<string name="learn_more">بیشتر بدانید</string> <string name="learn_more">بیشتر بدانید</string>
<string name="devicemsg_self_deleted">شما گپ «پیام‌های ذخیره شده» را پاک کردید.\n\nℹ️ برای استفادهٔ دوباره از «پیام‌های ذخیره شده» کافی است یک گپ جدید با خودتان درست کنید. </string> <string name="devicemsg_self_deleted">شما گپ «پیام‌های ذخیره شده» را پاک کردید.\n\nℹ️ برای استفادهٔ دوباره از «پیام‌های ذخیره شده» کافی است یک گپ جدید با خودتان درست کنید. </string>
@ -968,6 +1007,7 @@ https://meet.jit.si/$ROOM
<string name="load_qr_code_as_image">بارگیری کیو آر کد به صورت تصویر</string> <string name="load_qr_code_as_image">بارگیری کیو آر کد به صورت تصویر</string>
<string name="qrscan_title">اسکن کردن کد کیو آر</string> <string name="qrscan_title">اسکن کردن کد کیو آر</string>
<string name="qrscan_hint">دوربین خود را روی کد کیوآر نگه دارید. </string> <string name="qrscan_hint">دوربین خود را روی کد کیوآر نگه دارید. </string>
<string name="qrscan_hint_desktop">کد کیو‌آر را زیر دوربین بگیرید</string>
<string name="qrscan_failed">امکان رمزگشایی کد کیوآر وجود ندارد</string> <string name="qrscan_failed">امکان رمزگشایی کد کیوآر وجود ندارد</string>
<string name="qrscan_ask_join_group">آیا می خواهید به گروه\"%1$s\" ملحق شوید؟</string> <string name="qrscan_ask_join_group">آیا می خواهید به گروه\"%1$s\" ملحق شوید؟</string>
<string name="qrscan_fingerprint_mismatch">اثرانگشت اسکن شده با انچه که برای %1$sمشاهده شده بود انطباق ندارد. </string> <string name="qrscan_fingerprint_mismatch">اثرانگشت اسکن شده با انچه که برای %1$sمشاهده شده بود انطباق ندارد. </string>
@ -1010,12 +1050,15 @@ https://meet.jit.si/$ROOM
<string name="secure_join_wait">در حال برقراری رمزگذاری سراسری تضمین‌شده، لطفا صبر کنید...</string> <string name="secure_join_wait">در حال برقراری رمزگذاری سراسری تضمین‌شده، لطفا صبر کنید...</string>
<!-- deprecated --> <!-- deprecated -->
<string name="secure_join_wait_timeout">اکنون نمی توانیم رمزگذاری سراسری تضمین‌شده را برقرار کنیم. با این وجود می‌توانید پیام ارسال کنید.</string> <string name="secure_join_wait_timeout">اکنون نمی توانیم رمزگذاری سراسری تضمین‌شده را برقرار کنیم. با این وجود می‌توانید پیام ارسال کنید.</string>
<!-- deprecated, was stock string -->
<string name="secure_join_takes_longer">برای ادامه، مخاطب باید برخط باشد.\n\nاین فرآیند به صورت خودکار در پس‌زمینه ادامه خواهد داشت.</string>
<string name="contact_verified">%1$s تأیید شد.</string> <string name="contact_verified">%1$s تأیید شد.</string>
<!-- deprecated, was stock string -->
<string name="contact_not_verified">امکان تایید رمزگذاری در مبدا، برای %1$sوجود ندارد.</string> <string name="contact_not_verified">امکان تایید رمزگذاری در مبدا، برای %1$sوجود ندارد.</string>
<!-- Shown in contact profile. The placeholder will be replaced by the name of the contact that introduced the contact. --> <!-- Shown in contact profile. The placeholder will be replaced by the name of the contact that introduced the contact. -->
<string name="verified_by">احراز هویت شده توسط %1$s</string> <string name="verified_by">احراز هویت شده توسط %1$s</string>
<string name="verified_by_you">تأیید شده توسط من</string> <string name="verified_by_you">تأیید شده توسط من</string>
<!-- translators: "setup" is the "encryption setup" here, as in "Autocrypt Setup Message" --> <!-- deprecated, was stock string -->
<string name="contact_setup_changed">تنظیم‌ها برای %1$s تغییر کرد. </string> <string name="contact_setup_changed">تنظیم‌ها برای %1$s تغییر کرد. </string>
<string name="verified_contact_required_explain">برای تضمین رمزنگاری سراسری شما تنها می‌توانید مخاطب‌هایی که یک تیک سبز دارند به این گروه اضافه کنید.\n\nمی‌توانید با مخاطب‌هایتان حضوری ملاقات کنید و برای معرفی، کد QR آن‌ها را اسکن کنید.</string> <string name="verified_contact_required_explain">برای تضمین رمزنگاری سراسری شما تنها می‌توانید مخاطب‌هایی که یک تیک سبز دارند به این گروه اضافه کنید.\n\nمی‌توانید با مخاطب‌هایتان حضوری ملاقات کنید و برای معرفی، کد QR آن‌ها را اسکن کنید.</string>
<string name="mailto_dialog_header_select_chat">گپ را برای ارسال پیام انتخاب کنید</string> <string name="mailto_dialog_header_select_chat">گپ را برای ارسال پیام انتخاب کنید</string>
@ -1071,7 +1114,7 @@ https://meet.jit.si/$ROOM
<string name="ImageEditorHud_flip">برعکس کردن</string> <string name="ImageEditorHud_flip">برعکس کردن</string>
<string name="ImageEditorHud_rotate">چرخاندن</string> <string name="ImageEditorHud_rotate">چرخاندن</string>
<!-- dc_str_* resources --> <!-- deprecated, use string "E-Mail" for non-encrypted messages instead -->
<string name="encrypted_message">پیام رمزگذاری شده</string> <string name="encrypted_message">پیام رمزگذاری شده</string>
<!-- strings introduced on desktop. we want to share strings between the os, in general, please do not add generic strings here --> <!-- strings introduced on desktop. we want to share strings between the os, in general, please do not add generic strings here -->
@ -1180,6 +1223,9 @@ GNU GPL ورژن ۳
<string name="InfoPlist_NSMicrophoneUsageDescription">دلتاچت از میکروفون برای ذخیره و ارسال پیام صوتی یا فیلم دارای صدا استفاده می‌کند.</string> <string name="InfoPlist_NSMicrophoneUsageDescription">دلتاچت از میکروفون برای ذخیره و ارسال پیام صوتی یا فیلم دارای صدا استفاده می‌کند.</string>
<string name="InfoPlist_NSPhotoLibraryUsageDescription">دلتاچت به شما اجازه می دهد تصویر موردنظر برای ارسال را انتخاب کنید.</string> <string name="InfoPlist_NSPhotoLibraryUsageDescription">دلتاچت به شما اجازه می دهد تصویر موردنظر برای ارسال را انتخاب کنید.</string>
<string name="InfoPlist_NSPhotoLibraryAddUsageDescription">دلتاچت میخواهد تصاویر را در آلبوم شما ذخیره کند.</string> <string name="InfoPlist_NSPhotoLibraryAddUsageDescription">دلتاچت میخواهد تصاویر را در آلبوم شما ذخیره کند.</string>
<string name="InfoPlist_NSFaceIDUsageDescription">دلتاچت می‌تواند از عکس چهرهٔ شما برای محافظت از نمایهٔ محلی، ساخت نسخهٔ پشتیبان و پیکره‌بندی دستگاه دوم استفاده کند.</string>
<!-- android specific strings, developers: please take care to remove strings that are no longer used! --> <!-- android specific strings, developers: please take care to remove strings that are no longer used! -->
<string name="pref_instant_delivery">تحویل آنی</string> <string name="pref_instant_delivery">تحویل آنی</string>
<string name="pref_background_notifications">استفاده از اتصال پس‌زمینه</string> <string name="pref_background_notifications">استفاده از اتصال پس‌زمینه</string>

12
src/main/res/values-fi/strings.xml
View file

@ -294,7 +294,6 @@
<!-- Menu item beside an app/chat that adds an icon to the system's home screen. If the user taps that icon, the app/chat is opened directly. --> <!-- Menu item beside an app/chat that adds an icon to the system's home screen. If the user taps that icon, the app/chat is opened directly. -->
<string name="add_to_home_screen">Lisää aloitusnäytölle</string> <string name="add_to_home_screen">Lisää aloitusnäytölle</string>
<string name="donate">Lahjoita</string> <string name="donate">Lahjoita</string>
<string name="mute_for_one_hour">Mykistä 1 tunniksi</string> <string name="mute_for_one_hour">Mykistä 1 tunniksi</string>
<string name="mute_for_eight_hours">Mykistä 8 tunniksi</string> <string name="mute_for_eight_hours">Mykistä 8 tunniksi</string>
<string name="mute_for_one_day">Mykistä 1 päiväksi</string> <string name="mute_for_one_day">Mykistä 1 päiväksi</string>
@ -474,7 +473,7 @@
<!-- option to show images in the gallery as square (instead of using correct width/height) --> <!-- option to show images in the gallery as square (instead of using correct width/height) -->
<string name="square_grid">Neliöruudukko</string> <string name="square_grid">Neliöruudukko</string>
<string name="send_message">Lähetä viesti</string> <string name="send_message">Lähetä viesti</string>
<!-- Placeholder %1$s will be replaced by the name of the contact changing their address. Placeholders %2$s and %3$s will be replaced by old/new addresses. --> <!-- deprecated, was stock string -->
<string name="aeap_addr_changed">%1$s vaihtui osoitteesta %2$s osoitteeksi %3$s</string> <string name="aeap_addr_changed">%1$s vaihtui osoitteesta %2$s osoitteeksi %3$s</string>
<!-- deprecated --> <!-- deprecated -->
<string name="aeap_explanation">Vaihdoit sähköpostiosoitteesi osoitteesta %1$s osoitteeksi %2$s.\n\nJos lähetät viestin vahvistettuun ryhmään, ryhmän jäsenet saavat automaattisesti uuden osoitteesi.\n\nOn suositeltavaa asettaa vanha tilisi välittämään kaikki viestit uuteen osoitteeseesi. Muuten et välttämättä saa viestejä niiltä yhteystiedoiltasi, joilla ei ole uutta osoitettasi.</string> <string name="aeap_explanation">Vaihdoit sähköpostiosoitteesi osoitteesta %1$s osoitteeksi %2$s.\n\nJos lähetät viestin vahvistettuun ryhmään, ryhmän jäsenet saavat automaattisesti uuden osoitteesi.\n\nOn suositeltavaa asettaa vanha tilisi välittämään kaikki viestit uuteen osoitteeseesi. Muuten et välttämättä saa viestejä niiltä yhteystiedoiltasi, joilla ei ole uutta osoitettasi.</string>
@ -845,11 +844,13 @@
<string name="ephemeral_timer_weeks_by_you">Katoavien viestien ajastin asetettu %1$s viikkoon minun toimestani.</string> <string name="ephemeral_timer_weeks_by_you">Katoavien viestien ajastin asetettu %1$s viikkoon minun toimestani.</string>
<!-- %1$s will be replaced by the number of weeks (always >1) the timer is set to, %2$s will be replaced by name and address of the contact --> <!-- %1$s will be replaced by the number of weeks (always >1) the timer is set to, %2$s will be replaced by name and address of the contact -->
<string name="ephemeral_timer_weeks_by_other">Katoavien viestien ajastin asetettu %1$s viikkoon käyttäjän %2$s toimesta.</string> <string name="ephemeral_timer_weeks_by_other">Katoavien viestien ajastin asetettu %1$s viikkoon käyttäjän %2$s toimesta.</string>
<!-- this may be shown instead of the chat's input field, with buttons "More Info" and "OK" --> <!-- deprecated -->
<string name="chat_protection_broken">%1$s lähetti viestin toiselta laitteelta.</string> <string name="chat_protection_broken">%1$s lähetti viestin toiselta laitteelta.</string>
<string name="chat_protection_enabled_tap_to_learn_more">Tästä eteenpäin viestit on taatusti päästä-päähän salattuja. Lisätietoja napauttamalla.</string> <string name="chat_protection_enabled_tap_to_learn_more">Tästä eteenpäin viestit on taatusti päästä-päähän salattuja. Lisätietoja napauttamalla.</string>
<string name="chat_protection_enabled_explanation">Kaikki viestit tässä keskustelussa ovat taatusti päästä-päähän salattuja.\n\nPäästä-päähän -salaus pitää viestisi sinun ja keskustelukumppanisi välillä. Edes sähköpostipalveluntarjoaja ei pysty niitä lukemaan.</string> <string name="chat_protection_enabled_explanation">Kaikki viestit tässä keskustelussa ovat taatusti päästä-päähän salattuja.\n\nPäästä-päähän -salaus pitää viestisi sinun ja keskustelukumppanisi välillä. Edes sähköpostipalveluntarjoaja ei pysty niitä lukemaan.</string>
<!-- deprecated -->
<string name="chat_protection_broken_tap_to_learn_more">%1$s lähetti viestin toiselta laitteelta. Lue lisää napauttamalla.</string> <string name="chat_protection_broken_tap_to_learn_more">%1$s lähetti viestin toiselta laitteelta. Lue lisää napauttamalla.</string>
<!-- deprecated -->
<string name="chat_protection_broken_explanation">Päästä päähän salausta ei voida enää taata, todennäköisesti koska %1$s uudelleenasensi Delta Chatin tai lähetti viestin toiselta laitteelta.\n\nTapaamalla hänet voit skannata hänen QR -koodinsa uudelleen päästä-päähän salauksen palauttamiseksi.</string> <string name="chat_protection_broken_explanation">Päästä päähän salausta ei voida enää taata, todennäköisesti koska %1$s uudelleenasensi Delta Chatin tai lähetti viestin toiselta laitteelta.\n\nTapaamalla hänet voit skannata hänen QR -koodinsa uudelleen päästä-päähän salauksen palauttamiseksi.</string>
<string name="invalid_unencrypted_tap_to_learn_more">⚠️ %1$s vaatii päästä-päähän -salausta joka ei enää ole käytössä tässä keskustelussa. Lue lisää napauttamalla.</string> <string name="invalid_unencrypted_tap_to_learn_more">⚠️ %1$s vaatii päästä-päähän -salausta joka ei enää ole käytössä tässä keskustelussa. Lue lisää napauttamalla.</string>
<string name="invalid_unencrypted_explanation">Päästä-päähän salauksen saat käyttöön tapaamalla yhteystietosi ja skannaamalla hänen QR -koodinsa.</string> <string name="invalid_unencrypted_explanation">Päästä-päähän salauksen saat käyttöön tapaamalla yhteystietosi ja skannaamalla hänen QR -koodinsa.</string>
@ -912,11 +913,12 @@
<!-- deprecated --> <!-- deprecated -->
<string name="secure_join_wait_timeout">Taattua päästä päähän salausta ei vielä voitu ottaa käyttöön, mutta voit jo lähettää viestin.</string> <string name="secure_join_wait_timeout">Taattua päästä päähän salausta ei vielä voitu ottaa käyttöön, mutta voit jo lähettää viestin.</string>
<string name="contact_verified">%1$s varmistettu.</string> <string name="contact_verified">%1$s varmistettu.</string>
<!-- deprecated, was stock string -->
<string name="contact_not_verified">Keskustelun päästä-päähän -salausta ei voida taata henkilön %1$s kanssa.</string> <string name="contact_not_verified">Keskustelun päästä-päähän -salausta ei voida taata henkilön %1$s kanssa.</string>
<!-- Shown in contact profile. The placeholder will be replaced by the name of the contact that introduced the contact. --> <!-- Shown in contact profile. The placeholder will be replaced by the name of the contact that introduced the contact. -->
<string name="verified_by">%1$s lisäsi</string> <string name="verified_by">%1$s lisäsi</string>
<string name="verified_by_you">Lisäämäni</string> <string name="verified_by_you">Lisäämäni</string>
<!-- translators: "setup" is the "encryption setup" here, as in "Autocrypt Setup Message" --> <!-- deprecated, was stock string -->
<string name="contact_setup_changed">Asetukset muutettu kohteessa %1$s.</string> <string name="contact_setup_changed">Asetukset muutettu kohteessa %1$s.</string>
<string name="verified_contact_required_explain">Päästä-päähän -salauksen takaamiseksi, voit lisätä ryhmään ainoastaan yhteystietoja joilla on vihreä \"oikein\" -merkki.\n\nVoit tavata yhteystietoja kasvotusten ja skannata heidän QR -koodinsa niin saat lisättyä salauksen käyttöön</string> <string name="verified_contact_required_explain">Päästä-päähän -salauksen takaamiseksi, voit lisätä ryhmään ainoastaan yhteystietoja joilla on vihreä \"oikein\" -merkki.\n\nVoit tavata yhteystietoja kasvotusten ja skannata heidän QR -koodinsa niin saat lisättyä salauksen käyttöön</string>
<string name="mailto_dialog_header_select_chat">Valitse keskustelu viestien lähettämiseen</string> <string name="mailto_dialog_header_select_chat">Valitse keskustelu viestien lähettämiseen</string>
@ -960,7 +962,7 @@
<string name="ImageEditorHud_flip">Käännä</string> <string name="ImageEditorHud_flip">Käännä</string>
<string name="ImageEditorHud_rotate">Pyöritä</string> <string name="ImageEditorHud_rotate">Pyöritä</string>
<!-- dc_str_* resources --> <!-- deprecated, use string "E-Mail" for non-encrypted messages instead -->
<string name="encrypted_message">Salattu viesti</string> <string name="encrypted_message">Salattu viesti</string>
<!-- strings introduced on desktop. we want to share strings between the os, in general, please do not add generic strings here --> <!-- strings introduced on desktop. we want to share strings between the os, in general, please do not add generic strings here -->

12
src/main/res/values-fr/strings.xml
View file

@ -337,7 +337,6 @@
<!-- Menu item beside an app/chat that adds an icon to the system's home screen. If the user taps that icon, the app/chat is opened directly. --> <!-- Menu item beside an app/chat that adds an icon to the system's home screen. If the user taps that icon, the app/chat is opened directly. -->
<string name="add_to_home_screen">Ajouter à l\'écran d\'accueil</string> <string name="add_to_home_screen">Ajouter à l\'écran d\'accueil</string>
<string name="donate">Faire un don</string> <string name="donate">Faire un don</string>
<string name="mute_for_one_hour">Désactiver pour 1 heure</string> <string name="mute_for_one_hour">Désactiver pour 1 heure</string>
<string name="mute_for_eight_hours">Désactiver pour 8 heures</string> <string name="mute_for_eight_hours">Désactiver pour 8 heures</string>
<string name="mute_for_one_day">Désactiver pour 1 jour</string> <string name="mute_for_one_day">Désactiver pour 1 jour</string>
@ -537,7 +536,7 @@
<!-- option to show images in the gallery as square (instead of using correct width/height) --> <!-- option to show images in the gallery as square (instead of using correct width/height) -->
<string name="square_grid">Grille de photos carrées</string> <string name="square_grid">Grille de photos carrées</string>
<string name="send_message">Envoyer message</string> <string name="send_message">Envoyer message</string>
<!-- Placeholder %1$s will be replaced by the name of the contact changing their address. Placeholders %2$s and %3$s will be replaced by old/new addresses. --> <!-- deprecated, was stock string -->
<string name="aeap_addr_changed">%1$s a changé son adresse de %2$s à %3$s</string> <string name="aeap_addr_changed">%1$s a changé son adresse de %2$s à %3$s</string>
<!-- deprecated --> <!-- deprecated -->
<string name="aeap_explanation">Vous avez changé votre adresse courriel de %1$s à %2$s.\n\nSi vous envoyez maintenant un message à un groupe connu, votre ancienne adresse sera automatiquement remplacée par la nouvelle chez tous vos contacts dans ce groupe.\n\nIl est fortement conseillé de configurer votre ancien fournisseur de courriel de sorte à transférer tous vos courriels à votre nouvelle adresse. Sinon, vous risquez de manquer des messages de contacts qui n\'ont pas encore reçu votre nouvelle adresse.</string> <string name="aeap_explanation">Vous avez changé votre adresse courriel de %1$s à %2$s.\n\nSi vous envoyez maintenant un message à un groupe connu, votre ancienne adresse sera automatiquement remplacée par la nouvelle chez tous vos contacts dans ce groupe.\n\nIl est fortement conseillé de configurer votre ancien fournisseur de courriel de sorte à transférer tous vos courriels à votre nouvelle adresse. Sinon, vous risquez de manquer des messages de contacts qui n\'ont pas encore reçu votre nouvelle adresse.</string>
@ -929,11 +928,13 @@
<string name="ephemeral_timer_weeks_by_you">Vous avez réglé le temps d\'affichage des messages éphémères à %1$s semaines.</string> <string name="ephemeral_timer_weeks_by_you">Vous avez réglé le temps d\'affichage des messages éphémères à %1$s semaines.</string>
<!-- %1$s will be replaced by the number of weeks (always >1) the timer is set to, %2$s will be replaced by name and address of the contact --> <!-- %1$s will be replaced by the number of weeks (always >1) the timer is set to, %2$s will be replaced by name and address of the contact -->
<string name="ephemeral_timer_weeks_by_other">Minuterie des messages éphémères réglée à %1$s semaines par %2$s.</string> <string name="ephemeral_timer_weeks_by_other">Minuterie des messages éphémères réglée à %1$s semaines par %2$s.</string>
<!-- this may be shown instead of the chat's input field, with buttons "More Info" and "OK" --> <!-- deprecated -->
<string name="chat_protection_broken">%1$s a envoyé un message depuis un nouvel appareil.</string> <string name="chat_protection_broken">%1$s a envoyé un message depuis un nouvel appareil.</string>
<string name="chat_protection_enabled_tap_to_learn_more">Les messages sont désormais garantis chiffrés de bout en bout. Appuyer pour en savoir plus.</string> <string name="chat_protection_enabled_tap_to_learn_more">Les messages sont désormais garantis chiffrés de bout en bout. Appuyer pour en savoir plus.</string>
<string name="chat_protection_enabled_explanation">Il n\'est pas garanti que tous les messages de cette discussion sont chiffrés de bout en bout.\n\nLe chiffrement de bout en bout assure la confidentialité des messages échangés par les membres d\'une discussion. Même votre fournisseur de courriel ne peut pas les lire. </string> <string name="chat_protection_enabled_explanation">Il n\'est pas garanti que tous les messages de cette discussion sont chiffrés de bout en bout.\n\nLe chiffrement de bout en bout assure la confidentialité des messages échangés par les membres d\'une discussion. Même votre fournisseur de courriel ne peut pas les lire. </string>
<!-- deprecated -->
<string name="chat_protection_broken_tap_to_learn_more">%1$s a envoyé un message depuis un nouvel appareil. Appuyez pour en savoir plus.</string> <string name="chat_protection_broken_tap_to_learn_more">%1$s a envoyé un message depuis un nouvel appareil. Appuyez pour en savoir plus.</string>
<!-- deprecated -->
<string name="chat_protection_broken_explanation">Le chiffrement de bout en bout ne peut plus être garanti, probablement parce que %1$s a réinstallé Delta Chat ou envoyé un message depuis un nouvel appareil.\n\nVous pouvez convenir d\'une rencontre physique afin de scanner à nouveau son code QR pour ré-instaurer la garantie du chiffrement de bout en bout.</string> <string name="chat_protection_broken_explanation">Le chiffrement de bout en bout ne peut plus être garanti, probablement parce que %1$s a réinstallé Delta Chat ou envoyé un message depuis un nouvel appareil.\n\nVous pouvez convenir d\'une rencontre physique afin de scanner à nouveau son code QR pour ré-instaurer la garantie du chiffrement de bout en bout.</string>
<string name="invalid_unencrypted_tap_to_learn_more">⚠️ %1$s nécessite un chiffrement de bout en bout qui n\'est pas encore configuré sur cette discussion. Appuyez pour en savoir plus.</string> <string name="invalid_unencrypted_tap_to_learn_more">⚠️ %1$s nécessite un chiffrement de bout en bout qui n\'est pas encore configuré sur cette discussion. Appuyez pour en savoir plus.</string>
<string name="invalid_unencrypted_explanation">Pour établir un chiffrement de bout en bout vous pouvez rencontrer vos contacts en personne et scanner leur code QR.</string> <string name="invalid_unencrypted_explanation">Pour établir un chiffrement de bout en bout vous pouvez rencontrer vos contacts en personne et scanner leur code QR.</string>
@ -996,11 +997,12 @@
<!-- deprecated --> <!-- deprecated -->
<string name="secure_join_wait_timeout">Le chiffrement de bout en bout n\'est pas encore garanti, mais vous pouvez déjà envoyer un message.</string> <string name="secure_join_wait_timeout">Le chiffrement de bout en bout n\'est pas encore garanti, mais vous pouvez déjà envoyer un message.</string>
<string name="contact_verified">%1$s connu.</string> <string name="contact_verified">%1$s connu.</string>
<!-- deprecated, was stock string -->
<string name="contact_not_verified">Impossible de garantir le chiffrement de bout en bout avec %1$s.</string> <string name="contact_not_verified">Impossible de garantir le chiffrement de bout en bout avec %1$s.</string>
<!-- Shown in contact profile. The placeholder will be replaced by the name of the contact that introduced the contact. --> <!-- Shown in contact profile. The placeholder will be replaced by the name of the contact that introduced the contact. -->
<string name="verified_by">Connu par %1$s</string> <string name="verified_by">Connu par %1$s</string>
<string name="verified_by_you">Connu par vous</string> <string name="verified_by_you">Connu par vous</string>
<!-- translators: "setup" is the "encryption setup" here, as in "Autocrypt Setup Message" --> <!-- deprecated, was stock string -->
<string name="contact_setup_changed">Configuration modifiée pour %1$s</string> <string name="contact_setup_changed">Configuration modifiée pour %1$s</string>
<string name="verified_contact_required_explain">Pour garantir le chiffrement de bout en bout, vous pouvez ajouter à ce groupe uniquement les contacts avec un badge vert.\n\nVous pouvez rencontrer ces contacts en personne pour scanner leur code QR et les ajouter à votre liste de contacts connus.</string> <string name="verified_contact_required_explain">Pour garantir le chiffrement de bout en bout, vous pouvez ajouter à ce groupe uniquement les contacts avec un badge vert.\n\nVous pouvez rencontrer ces contacts en personne pour scanner leur code QR et les ajouter à votre liste de contacts connus.</string>
<string name="mailto_dialog_header_select_chat">Sélectionnez une discussion à qui envoyer le message</string> <string name="mailto_dialog_header_select_chat">Sélectionnez une discussion à qui envoyer le message</string>
@ -1044,7 +1046,7 @@
<string name="ImageEditorHud_flip">Tourner</string> <string name="ImageEditorHud_flip">Tourner</string>
<string name="ImageEditorHud_rotate">Pivoter</string> <string name="ImageEditorHud_rotate">Pivoter</string>
<!-- dc_str_* resources --> <!-- deprecated, use string "E-Mail" for non-encrypted messages instead -->
<string name="encrypted_message">Message chiffré</string> <string name="encrypted_message">Message chiffré</string>
<!-- strings introduced on desktop. we want to share strings between the os, in general, please do not add generic strings here --> <!-- strings introduced on desktop. we want to share strings between the os, in general, please do not add generic strings here -->

8
src/main/res/values-gl/strings.xml
View file

@ -325,7 +325,6 @@
<!-- Menu item beside an app/chat that adds an icon to the system's home screen. If the user taps that icon, the app/chat is opened directly. --> <!-- Menu item beside an app/chat that adds an icon to the system's home screen. If the user taps that icon, the app/chat is opened directly. -->
<string name="add_to_home_screen">Engadir á pantalla de Inicio</string> <string name="add_to_home_screen">Engadir á pantalla de Inicio</string>
<string name="donate">Doar</string> <string name="donate">Doar</string>
<string name="mute_for_one_hour">Acalar durante 1 h.</string> <string name="mute_for_one_hour">Acalar durante 1 h.</string>
<string name="mute_for_eight_hours">Acalar durante 8 horas</string> <string name="mute_for_eight_hours">Acalar durante 8 horas</string>
<string name="mute_for_one_day">Acalar durante 1 día</string> <string name="mute_for_one_day">Acalar durante 1 día</string>
@ -523,7 +522,7 @@
<!-- option to show images in the gallery as square (instead of using correct width/height) --> <!-- option to show images in the gallery as square (instead of using correct width/height) -->
<string name="square_grid">Grella cadrada</string> <string name="square_grid">Grella cadrada</string>
<string name="send_message">Enviar mensaxe</string> <string name="send_message">Enviar mensaxe</string>
<!-- Placeholder %1$s will be replaced by the name of the contact changing their address. Placeholders %2$s and %3$s will be replaced by old/new addresses. --> <!-- deprecated, was stock string -->
<string name="aeap_addr_changed">%1$s cambiou o seu enderezo de %2$s a %3$s</string> <string name="aeap_addr_changed">%1$s cambiou o seu enderezo de %2$s a %3$s</string>
<!-- deprecated --> <!-- deprecated -->
<string name="aeap_explanation">Cambiaches o teu enderezo de email de %1$s a %2$s.\n\nSe envías unha mensaxe a un grupo verificado os contactos cambiarán automáticamente o enderezo antigo polo novo.\n\nÉ moi recomendable que configures o email antigo para que che reenvíe todo o correo ao novo enderezo. De non facelo poderías perder mensaxes de contactos que aínda non coñezan o teu novo enderezo.</string> <string name="aeap_explanation">Cambiaches o teu enderezo de email de %1$s a %2$s.\n\nSe envías unha mensaxe a un grupo verificado os contactos cambiarán automáticamente o enderezo antigo polo novo.\n\nÉ moi recomendable que configures o email antigo para que che reenvíe todo o correo ao novo enderezo. De non facelo poderías perder mensaxes de contactos que aínda non coñezan o teu novo enderezo.</string>
@ -900,8 +899,9 @@
<!-- placeholder will be replaced by the name of the inviter. --> <!-- placeholder will be replaced by the name of the inviter. -->
<string name="secure_join_replies">%1$s respondeu, agardando a que sexa engadido ao grupo...</string> <string name="secure_join_replies">%1$s respondeu, agardando a que sexa engadido ao grupo...</string>
<string name="contact_verified">%1$s verificado.</string> <string name="contact_verified">%1$s verificado.</string>
<!-- deprecated, was stock string -->
<string name="contact_not_verified">Non se puido verificar %1$s.</string> <string name="contact_not_verified">Non se puido verificar %1$s.</string>
<!-- translators: "setup" is the "encryption setup" here, as in "Autocrypt Setup Message" --> <!-- deprecated, was stock string -->
<string name="contact_setup_changed">Cambiaron os axustes para %1$s.</string> <string name="contact_setup_changed">Cambiaron os axustes para %1$s.</string>
<string name="mailto_dialog_header_select_chat">Elexir chat ao que enviar a mensaxe</string> <string name="mailto_dialog_header_select_chat">Elexir chat ao que enviar a mensaxe</string>
<!-- first placeholder is the name of the chat --> <!-- first placeholder is the name of the chat -->
@ -935,7 +935,7 @@
<string name="ImageEditorHud_flip">Voltear</string> <string name="ImageEditorHud_flip">Voltear</string>
<string name="ImageEditorHud_rotate">Rotar</string> <string name="ImageEditorHud_rotate">Rotar</string>
<!-- dc_str_* resources --> <!-- deprecated, use string "E-Mail" for non-encrypted messages instead -->
<string name="encrypted_message">Mensaxe cifrada</string> <string name="encrypted_message">Mensaxe cifrada</string>
<!-- strings introduced on desktop. we want to share strings between the os, in general, please do not add generic strings here --> <!-- strings introduced on desktop. we want to share strings between the os, in general, please do not add generic strings here -->

22
src/main/res/values-hu/strings.xml
View file

@ -261,6 +261,11 @@
<string name="please_enter_broadcast_list_name">Adjon meg egy nevet az adáslistának</string> <string name="please_enter_broadcast_list_name">Adjon meg egy nevet az adáslistának</string>
<!-- consider keeping the term "channel" as in WhatsApp or Telegram --> <!-- consider keeping the term "channel" as in WhatsApp or Telegram -->
<string name="channel_name">Csatorna neve</string> <string name="channel_name">Csatorna neve</string>
<string name="email">E-mail</string>
<!-- "New" as in "Create New E-Mail"; shown together with "New Group" and "New Channel" -->
<string name="new_email">Új e-mail</string>
<!-- the "Subject" of an e-mail, use the term common in classic e-mail apps -->
<string name="subject">Tárgy</string>
<string name="menu_send">Küldés</string> <string name="menu_send">Küldés</string>
<string name="menu_toggle_keyboard">Váltás emodzsibillentyűzetre</string> <string name="menu_toggle_keyboard">Váltás emodzsibillentyűzetre</string>
<string name="menu_edit_group">Csoport szerkesztése</string> <string name="menu_edit_group">Csoport szerkesztése</string>
@ -355,6 +360,7 @@
<!-- Menu item beside an app/chat that adds an icon to the system's home screen. If the user taps that icon, the app/chat is opened directly. --> <!-- Menu item beside an app/chat that adds an icon to the system's home screen. If the user taps that icon, the app/chat is opened directly. -->
<string name="add_to_home_screen">Hozzáadás a kezdőképernyőhöz</string> <string name="add_to_home_screen">Hozzáadás a kezdőképernyőhöz</string>
<string name="donate">Adományozás</string> <string name="donate">Adományozás</string>
<string name="donate_device_msg">❤️ Úgy tűnik, hogy tetszik önnek a Delta Chat!\n\nFontolja meg az adományozást, hogy a Delta Chat mindenki számára ingyenes maradhasson.\n\nUgyan a Delta Chat szabadon használható és nyílt forráskódú, de a fejlesztés pénzbe kerül. Segítsen nekünk, hogy a Delta Chat független maradhasson, és a jövőben még fantasztikusabbá váljon.\n\nhttps://delta.chat/donate</string>
<string name="mute_for_one_hour">Némítás 1 órára</string> <string name="mute_for_one_hour">Némítás 1 órára</string>
<string name="mute_for_eight_hours">Némítás 8 órára</string> <string name="mute_for_eight_hours">Némítás 8 órára</string>
@ -563,7 +569,7 @@
<!-- option to show images in the gallery as square (instead of using correct width/height) --> <!-- option to show images in the gallery as square (instead of using correct width/height) -->
<string name="square_grid">Négyzetrács</string> <string name="square_grid">Négyzetrács</string>
<string name="send_message">Üzenet küldése</string> <string name="send_message">Üzenet küldése</string>
<!-- Placeholder %1$s will be replaced by the name of the contact changing their address. Placeholders %2$s and %3$s will be replaced by old/new addresses. --> <!-- deprecated, was stock string -->
<string name="aeap_addr_changed">%1$s megváltoztatta a címét következőről: %2$s, erre: %3$s </string> <string name="aeap_addr_changed">%1$s megváltoztatta a címét következőről: %2$s, erre: %3$s </string>
<!-- deprecated --> <!-- deprecated -->
<string name="aeap_explanation">Ön megváltoztatta a saját e-mail-címét erről: %1$s erre: %2$s.\n\nHa most üzenetet küld egy hitelesített csoportba, az ottani partnerei automatikusan lecserélik az Ön régi címét az új címére.\n\nEzért nagyon ajánlott beállítani, hogy a régi e-mail-szolgáltatója továbbítsa-e az összes e-mailt az e-mail-címére. Ellenkező esetben lemaradhat azoknak a partnereinek az üzeneteiről, akik még nem kapták meg az új címét.</string> <string name="aeap_explanation">Ön megváltoztatta a saját e-mail-címét erről: %1$s erre: %2$s.\n\nHa most üzenetet küld egy hitelesített csoportba, az ottani partnerei automatikusan lecserélik az Ön régi címét az új címére.\n\nEzért nagyon ajánlott beállítani, hogy a régi e-mail-szolgáltatója továbbítsa-e az összes e-mailt az e-mail-címére. Ellenkező esetben lemaradhat azoknak a partnereinek az üzeneteiről, akik még nem kapták meg az új címét.</string>
@ -966,11 +972,13 @@
<string name="ephemeral_timer_weeks_by_you">Ön az eltűnő üzenetek időzítőjét %1$s hétre állította be.</string> <string name="ephemeral_timer_weeks_by_you">Ön az eltűnő üzenetek időzítőjét %1$s hétre állította be.</string>
<!-- %1$s will be replaced by the number of weeks (always >1) the timer is set to, %2$s will be replaced by name and address of the contact --> <!-- %1$s will be replaced by the number of weeks (always >1) the timer is set to, %2$s will be replaced by name and address of the contact -->
<string name="ephemeral_timer_weeks_by_other">%2$s az eltűnő üzenetek időzítőjét%1$s hétre állította be.</string> <string name="ephemeral_timer_weeks_by_other">%2$s az eltűnő üzenetek időzítőjét%1$s hétre állította be.</string>
<!-- this may be shown instead of the chat's input field, with buttons "More Info" and "OK" --> <!-- deprecated -->
<string name="chat_protection_broken">%1$s egy másik eszközről küldött üzenetet.</string> <string name="chat_protection_broken">%1$s egy másik eszközről küldött üzenetet.</string>
<string name="chat_protection_enabled_tap_to_learn_more">Az üzenetek mostantól garantáltan titkosítva lesznek a végpontok között. Koppintson, ha többet szeretne tudni.</string> <string name="chat_protection_enabled_tap_to_learn_more">Az üzenetek mostantól garantáltan titkosítva lesznek a végpontok között. Koppintson, ha többet szeretne tudni.</string>
<string name="chat_protection_enabled_explanation">Mostantól garantált, hogy ebben a csevegésben az összes üzenet végpontok közötti titkosítással rendelkezik.\n\nA végpontok közötti titkosítással az üzenetek bizalmasak maradnak Ön és a partnerei között. Még az e-mail-szolgáltatója sem tudja elolvasni őket.</string> <string name="chat_protection_enabled_explanation">Mostantól garantált, hogy ebben a csevegésben az összes üzenet végpontok közötti titkosítással rendelkezik.\n\nA végpontok közötti titkosítással az üzenetek bizalmasak maradnak Ön és a partnerei között. Még az e-mail-szolgáltatója sem tudja elolvasni őket.</string>
<!-- deprecated -->
<string name="chat_protection_broken_tap_to_learn_more">%1$s egy másik eszközről küldött üzenetet. Koppintson, ha többet szeretne tudni.</string> <string name="chat_protection_broken_tap_to_learn_more">%1$s egy másik eszközről küldött üzenetet. Koppintson, ha többet szeretne tudni.</string>
<!-- deprecated -->
<string name="chat_protection_broken_explanation">A végpontok közötti titkosítás már nem garantálható, valószínűleg azért, mert %1$s újratelepítette a Delta Chatet, vagy egy másik eszközről küldött üzenetet.\n\n Személyesen találkozhat vele, és újra beolvashatja a QR-kódját a garantált végpontok közötti titkosítás visszaállításához.</string> <string name="chat_protection_broken_explanation">A végpontok közötti titkosítás már nem garantálható, valószínűleg azért, mert %1$s újratelepítette a Delta Chatet, vagy egy másik eszközről küldött üzenetet.\n\n Személyesen találkozhat vele, és újra beolvashatja a QR-kódját a garantált végpontok közötti titkosítás visszaállításához.</string>
<string name="invalid_unencrypted_tap_to_learn_more">⚠️ A(z) %1$s végpontok közötti titkosítást igényel, ami még nincs beállítva erre a csevegésre. Koppintson, ha többet szeretne megtudni.</string> <string name="invalid_unencrypted_tap_to_learn_more">⚠️ A(z) %1$s végpontok közötti titkosítást igényel, ami még nincs beállítva erre a csevegésre. Koppintson, ha többet szeretne megtudni.</string>
<string name="invalid_unencrypted_explanation">A végpontok közötti titkosítás létrehozásához személyesen is találkozhat a partnereivel, és a QR-kódjukat beolvasva bemutathatja őket.</string> <string name="invalid_unencrypted_explanation">A végpontok közötti titkosítás létrehozásához személyesen is találkozhat a partnereivel, és a QR-kódjukat beolvasva bemutathatja őket.</string>
@ -1032,13 +1040,16 @@
<string name="secure_join_wait">Garantált végpontok közötti titkosítás létrehozása, várjon…</string> <string name="secure_join_wait">Garantált végpontok közötti titkosítás létrehozása, várjon…</string>
<!-- deprecated --> <!-- deprecated -->
<string name="secure_join_wait_timeout">Még nem sikerült a garantált végpontok közötti titkosítást létrehozni, de már küldhet üzenetet.</string> <string name="secure_join_wait_timeout">Még nem sikerült a garantált végpontok közötti titkosítást létrehozni, de már küldhet üzenetet.</string>
<!-- deprecated, was stock string -->
<string name="secure_join_takes_longer">Úgy tűnik, hogy ez tovább tart, mint gondoltuk, talán a partnere vagy Ön offline állapotban van.\n\nMindenesetre a folyamat a háttérben folytatódik, eközben csinálhat valami mást…</string> <string name="secure_join_takes_longer">Úgy tűnik, hogy ez tovább tart, mint gondoltuk, talán a partnere vagy Ön offline állapotban van.\n\nMindenesetre a folyamat a háttérben folytatódik, eközben csinálhat valami mást…</string>
<string name="contact_verified">%1$s bemutatva.</string> <string name="contact_verified">%1$s bemutatva.</string>
<!-- deprecated, was stock string -->
<string name="contact_not_verified">Nem lehet garantált végpontok közötti titkosítást létrehozni vele: %1$s.</string> <string name="contact_not_verified">Nem lehet garantált végpontok közötti titkosítást létrehozni vele: %1$s.</string>
<!-- Shown in contact profile. The placeholder will be replaced by the name of the contact that introduced the contact. --> <!-- Shown in contact profile. The placeholder will be replaced by the name of the contact that introduced the contact. -->
<string name="verified_by">%1$s által bemutatva</string> <string name="verified_by">%1$s által bemutatva</string>
<string name="verified_by_you">Ön által bemutatva</string> <string name="verified_by_you">Ön által bemutatva</string>
<!-- translators: "setup" is the "encryption setup" here, as in "Autocrypt Setup Message" --> <string name="verified_by_unknown">Bemutatva</string>
<!-- deprecated, was stock string -->
<string name="contact_setup_changed">Megváltoztatta a beállításokat %1$s számára.</string> <string name="contact_setup_changed">Megváltoztatta a beállításokat %1$s számára.</string>
<string name="verified_contact_required_explain">A végpontok közötti titkosítás garantálása érdekében csak zöld jelöléssel rendelkező névjegyeket adhat hozzá ehhez a csoporthoz.\n\n Személyesen is találkozhat a partnereivel és beolvashatja a QR-kódjukat, hogy bemutassa őket.</string> <string name="verified_contact_required_explain">A végpontok közötti titkosítás garantálása érdekében csak zöld jelöléssel rendelkező névjegyeket adhat hozzá ehhez a csoporthoz.\n\n Személyesen is találkozhat a partnereivel és beolvashatja a QR-kódjukat, hogy bemutassa őket.</string>
<string name="mailto_dialog_header_select_chat">Válassza ki a csevegést az üzenet elküldéséhez</string> <string name="mailto_dialog_header_select_chat">Válassza ki a csevegést az üzenet elküldéséhez</string>
@ -1082,7 +1093,7 @@
<string name="ImageEditorHud_flip">Tükrözés</string> <string name="ImageEditorHud_flip">Tükrözés</string>
<string name="ImageEditorHud_rotate">Forgatás</string> <string name="ImageEditorHud_rotate">Forgatás</string>
<!-- dc_str_* resources --> <!-- deprecated, use string "E-Mail" for non-encrypted messages instead -->
<string name="encrypted_message">Titkosított üzenet</string> <string name="encrypted_message">Titkosított üzenet</string>
<!-- strings introduced on desktop. we want to share strings between the os, in general, please do not add generic strings here --> <!-- strings introduced on desktop. we want to share strings between the os, in general, please do not add generic strings here -->
@ -1213,7 +1224,10 @@
<string name="perm_enable_bg_already_done">Már engedélyezve van a Delta Chat számára, hogy a háttérben üzeneteket fogadjon.\n\nHa az üzenetek még mindig nem érkeznek meg a háttérben, ellenőrizze a rendszerbeállításokat is.</string> <string name="perm_enable_bg_already_done">Már engedélyezve van a Delta Chat számára, hogy a háttérben üzeneteket fogadjon.\n\nHa az üzenetek még mindig nem érkeznek meg a háttérben, ellenőrizze a rendszerbeállításokat is.</string>
<!-- device messages for updates --> <!-- device messages for updates -->
<string name="update_2_0">Újdonságok:\n\n💯 A végpontok közötti titkosítás most már megbízható és örökre megmarad. A lakatok 🔒 eltűntek!\n\n✉️ A végpontok közötti titkosítás nélküli klasszikus e-mailek betűszimbólummal vannak jelölve\n\n😻 Új, továbbfejlesztett profilképernyő az összes névjegyhez\n\n🔲 Új gomb a csevegésben használt alkalmazások gyors eléréséhez\n\n❤️ Ha teheti, adományozzon nekünk, hogy függetlenek maradhassunk és továbbra is fejlesztéseket tudjunk végrehajtani: %1$s</string>
<!-- deprecated -->
<string name="update_1_50_android">Mik az újdonságok?\n\n❤️‍🔥 Új emodzsi-választó még több emodzsival\n\n🎮 Továbbfejlesztett, a csevegésben használható alkalmazások: Értesítéseket kaphat és megnyithatja az azokat támogató alkalmazásokban, azaz közvetlenül megnyithat egy hozzáadott naptárbejegyzést\n\n👍 Értesítést kaphat az üzeneteire adott reakciókról\n\n… 🛠️ Egyéb javítások, tudjon meg többet itt: %1$s</string> <string name="update_1_50_android">Mik az újdonságok?\n\n❤️‍🔥 Új emodzsi-választó még több emodzsival\n\n🎮 Továbbfejlesztett, a csevegésben használható alkalmazások: Értesítéseket kaphat és megnyithatja az azokat támogató alkalmazásokban, azaz közvetlenül megnyithat egy hozzáadott naptárbejegyzést\n\n👍 Értesítést kaphat az üzeneteire adott reakciókról\n\n… 🛠️ Egyéb javítások, tudjon meg többet itt: %1$s</string>
<!-- deprecated -->
<string name="update_switch_profile_placement">ℹ️ A „Profilváltás” beállítás át lett helyezve: <string name="update_switch_profile_placement">ℹ️ A „Profilváltás” beállítás át lett helyezve:
Érintse meg a főképernyő felső sarkában lévő profilképet a profilok hozzáadásához vagy váltásához 💡</string> Érintse meg a főképernyő felső sarkában lévő profilképet a profilok hozzáadásához vagy váltásához 💡</string>
</resources> </resources>

5
src/main/res/values-in/strings.xml
View file

@ -566,8 +566,9 @@
<string name="qraccount_ask_create_and_login_another">Buat alamat email baru di\"%1$s\" dan masuk ke sana?\n\nAkun yang sudah ada tidak akan di hapus. Gunakankan item \"Ganti akun\" untuk mengganti akun anda</string> <string name="qraccount_ask_create_and_login_another">Buat alamat email baru di\"%1$s\" dan masuk ke sana?\n\nAkun yang sudah ada tidak akan di hapus. Gunakankan item \"Ganti akun\" untuk mengganti akun anda</string>
<string name="qraccount_qr_code_cannot_be_used">Kode QR yang dipindai tidak dapat digunakan untuk mengatur akun baru.</string> <string name="qraccount_qr_code_cannot_be_used">Kode QR yang dipindai tidak dapat digunakan untuk mengatur akun baru.</string>
<string name="contact_verified">%1$sdiverifikasi.</string> <string name="contact_verified">%1$sdiverifikasi.</string>
<!-- deprecated, was stock string -->
<string name="contact_not_verified">Tidak bisa memverifikasi %1$s.</string> <string name="contact_not_verified">Tidak bisa memverifikasi %1$s.</string>
<!-- translators: "setup" is the "encryption setup" here, as in "Autocrypt Setup Message" --> <!-- deprecated, was stock string -->
<string name="contact_setup_changed">Ubah pengaturan untuk %1$s.</string> <string name="contact_setup_changed">Ubah pengaturan untuk %1$s.</string>
<!-- notifications --> <!-- notifications -->
<string name="notify_reply_button">Balasan</string> <string name="notify_reply_button">Balasan</string>
@ -588,7 +589,7 @@
<string name="perm_explain_access_to_location_denied">Untuk melampirkan lokasi, lihat pengaturan aplikasi, pilih \"Perizinan\", dan aktifkan \"Lokasi\".</string> <string name="perm_explain_access_to_location_denied">Untuk melampirkan lokasi, lihat pengaturan aplikasi, pilih \"Perizinan\", dan aktifkan \"Lokasi\".</string>
<!-- ImageEditorHud --> <!-- ImageEditorHud -->
<string name="ImageEditorHud_draw_anywhere_to_blur">Gambar di mana saja untuk diburamkan</string> <string name="ImageEditorHud_draw_anywhere_to_blur">Gambar di mana saja untuk diburamkan</string>
<!-- dc_str_* resources --> <!-- deprecated, use string "E-Mail" for non-encrypted messages instead -->
<string name="encrypted_message">Pesan terenkripsi</string> <string name="encrypted_message">Pesan terenkripsi</string>
<!-- strings introduced on desktop. we want to share strings between the os, in general, please do not add generic strings here --> <!-- strings introduced on desktop. we want to share strings between the os, in general, please do not add generic strings here -->

40
src/main/res/values-it/strings.xml
View file

@ -255,6 +255,12 @@
<string name="broadcast_lists">Liste Trasmissioni</string> <string name="broadcast_lists">Liste Trasmissioni</string>
<!-- deprecated --> <!-- deprecated -->
<string name="new_broadcast_list">Nuova Lista Trasmissione</string> <string name="new_broadcast_list">Nuova Lista Trasmissione</string>
<!-- consider keeping the term "channel" as in WhatsApp or Telegram -->
<string name="channel">Canale</string>
<!-- consider keeping the term "channel" as in WhatsApp or Telegram -->
<string name="channels">Canali</string>
<!-- consider keeping the term "channel" as in WhatsApp or Telegram -->
<string name="new_channel">Nuovo Canale</string>
<string name="add_recipients">Aggiungi Destinatari</string> <string name="add_recipients">Aggiungi Destinatari</string>
<!-- deprecated --> <!-- deprecated -->
<string name="edit_broadcast_list">Modifica Lista Trasmissione</string> <string name="edit_broadcast_list">Modifica Lista Trasmissione</string>
@ -262,6 +268,13 @@
<string name="broadcast_list_name">Nome Lista Trasmissione</string> <string name="broadcast_list_name">Nome Lista Trasmissione</string>
<!-- deprecated --> <!-- deprecated -->
<string name="please_enter_broadcast_list_name">Per piacere inserisci un nome per la lista trasmissione.</string> <string name="please_enter_broadcast_list_name">Per piacere inserisci un nome per la lista trasmissione.</string>
<!-- consider keeping the term "channel" as in WhatsApp or Telegram -->
<string name="channel_name">Nome Canale</string>
<string name="email">E-Mail</string>
<!-- "New" as in "Create New E-Mail"; shown together with "New Group" and "New Channel" -->
<string name="new_email">Nuova E-Mail</string>
<!-- the "Subject" of an e-mail, use the term common in classic e-mail apps -->
<string name="subject">Oggetto</string>
<string name="menu_send">Invia</string> <string name="menu_send">Invia</string>
<string name="menu_toggle_keyboard">Attiva/Disattiva Tastiera Emoji</string> <string name="menu_toggle_keyboard">Attiva/Disattiva Tastiera Emoji</string>
<string name="menu_edit_group">Modifica Gruppo</string> <string name="menu_edit_group">Modifica Gruppo</string>
@ -271,6 +284,7 @@
<string name="menu_unarchive_chat">Ripristina Chat</string> <string name="menu_unarchive_chat">Ripristina Chat</string>
<string name="menu_add_attachment">Aggiungi Allegato</string> <string name="menu_add_attachment">Aggiungi Allegato</string>
<string name="menu_leave_group">Abbandona Gruppo</string> <string name="menu_leave_group">Abbandona Gruppo</string>
<string name="menu_leave_channel">Abbandona Canale</string>
<string name="menu_delete_chat">Elimina Chat</string> <string name="menu_delete_chat">Elimina Chat</string>
<!-- Command to delete all messages in a chat. The chat itself will not be deleted but will be empty afterwards, so make sure to be different from "Delete Chat" here. "Clear" is a verb here, "Empty Chat" would also be fine (eg. in German "Chat leeren") --> <!-- Command to delete all messages in a chat. The chat itself will not be deleted but will be empty afterwards, so make sure to be different from "Delete Chat" here. "Clear" is a verb here, "Empty Chat" would also be fine (eg. in German "Chat leeren") -->
<string name="clear_chat">Cancella Messaggi</string> <string name="clear_chat">Cancella Messaggi</string>
@ -355,6 +369,7 @@
<!-- Menu item beside an app/chat that adds an icon to the system's home screen. If the user taps that icon, the app/chat is opened directly. --> <!-- Menu item beside an app/chat that adds an icon to the system's home screen. If the user taps that icon, the app/chat is opened directly. -->
<string name="add_to_home_screen">Aggiungi alla Schermata Iniziale</string> <string name="add_to_home_screen">Aggiungi alla Schermata Iniziale</string>
<string name="donate">Dona</string> <string name="donate">Dona</string>
<string name="donate_device_msg">❤️ Sembra che Delta Chat ti piaccia!\n\nConsidera una donazione per contribuire a garantire che Delta Chat rimanga gratuita per tutti.\n\nSebbene Delta Chat sia gratuita e open source, lo sviluppo richiede soldi. Aiutaci a mantenere Delta Chat indipendente e a renderla ancora più fantastica in futuro.\n\nhttps://delta.chat/donate</string>
<string name="mute_for_one_hour">Silenzia per 1 ora</string> <string name="mute_for_one_hour">Silenzia per 1 ora</string>
<string name="mute_for_eight_hours">Silenzia per 8 ore</string> <string name="mute_for_eight_hours">Silenzia per 8 ore</string>
@ -391,6 +406,9 @@
<string name="videochat_invitation">Invito alla chat video</string> <string name="videochat_invitation">Invito alla chat video</string>
<string name="videochat_invitation_body">Sei invitato a una chat video, fai clic %1$s per partecipare.</string> <string name="videochat_invitation_body">Sei invitato a una chat video, fai clic %1$s per partecipare.</string>
<!-- get confirmations -->
<!-- confirmation for leaving groups, channels, broadcasts or a mailinglists. If a subject is needed, "Are you sure you want to leave the chat?" would work as well -->
<string name="ask_leave_group">Sei sicuro di voler uscire?</string>
<plurals name="ask_delete_chat"> <plurals name="ask_delete_chat">
<item quantity="one">Eliminare %d chat su tutti i tuoi dispositivi?</item> <item quantity="one">Eliminare %d chat su tutti i tuoi dispositivi?</item>
<item quantity="many">Eliminare %d chats su tutti i tuoi dispositivi?</item> <item quantity="many">Eliminare %d chats su tutti i tuoi dispositivi?</item>
@ -421,6 +439,8 @@
<string name="ask_remove_members">Rimuovere %1$s dal gruppo?</string> <string name="ask_remove_members">Rimuovere %1$s dal gruppo?</string>
<!-- deprecated --> <!-- deprecated -->
<string name="ask_remove_from_broadcast">Rimuovere %1$s dalla lista di trasmissione?</string> <string name="ask_remove_from_broadcast">Rimuovere %1$s dalla lista di trasmissione?</string>
<!-- %1$s is replaced by a comma-separated list of names -->
<string name="ask_remove_from_channel">Rimuovere %1$s dal canale?</string>
<string name="open_url_confirmation">Vuoi aprire questo collegamento?</string> <string name="open_url_confirmation">Vuoi aprire questo collegamento?</string>
@ -455,6 +475,8 @@
<string name="chat_new_one_to_one_hint">Invia un messaggio a %1$s.</string> <string name="chat_new_one_to_one_hint">Invia un messaggio a %1$s.</string>
<!-- deprecated --> <!-- deprecated -->
<string name="chat_new_broadcast_hint">In una lista di trasmissione, i destinatari riceveranno i messaggi in una chat di sola lettura con te.</string> <string name="chat_new_broadcast_hint">In una lista di trasmissione, i destinatari riceveranno i messaggi in una chat di sola lettura con te.</string>
<!-- consider keeping the term "channel" as in WhatsApp or Telegram -->
<string name="chat_new_channel_hint">I canali sono uno strumento uno-a-molti per trasmettere i tuoi messaggi.</string>
<string name="chat_new_group_hint">Gli altri vedranno questo gruppo solo dopo che avrai inviato un primo messaggio.</string> <string name="chat_new_group_hint">Gli altri vedranno questo gruppo solo dopo che avrai inviato un primo messaggio.</string>
<string name="chat_record_slide_to_cancel">Scorri per annullare</string> <string name="chat_record_slide_to_cancel">Scorri per annullare</string>
<string name="chat_record_explain">Tocca e mantieni per registrare un messaggio vocale, rilascia per inviare </string> <string name="chat_record_explain">Tocca e mantieni per registrare un messaggio vocale, rilascia per inviare </string>
@ -563,7 +585,7 @@
<!-- option to show images in the gallery as square (instead of using correct width/height) --> <!-- option to show images in the gallery as square (instead of using correct width/height) -->
<string name="square_grid">Griglia Quadrata</string> <string name="square_grid">Griglia Quadrata</string>
<string name="send_message">Invia Messaggio</string> <string name="send_message">Invia Messaggio</string>
<!-- Placeholder %1$s will be replaced by the name of the contact changing their address. Placeholders %2$s and %3$s will be replaced by old/new addresses. --> <!-- deprecated, was stock string -->
<string name="aeap_addr_changed">%1$s ha cambiato il suo indirizzo da %2$s a %3$s</string> <string name="aeap_addr_changed">%1$s ha cambiato il suo indirizzo da %2$s a %3$s</string>
<!-- deprecated --> <!-- deprecated -->
<string name="aeap_explanation">Hai cambiato il tuo indirizzo email da %1$s a %2$s.\n\nSe ora invii un messaggio a un gruppo verificato, i contatti sostituiranno automaticamente il vecchio indirizzo con il tuo nuovo indirizzo.\n\nSi consiglia vivamente di impostare il tuo vecchio fornitore email per inoltrare tutte le email al tuo nuovo indirizzo. Altrimenti potresti perdere i messaggi di contatti che non hanno ancora ricevuto il tuo nuovo indirizzo.</string> <string name="aeap_explanation">Hai cambiato il tuo indirizzo email da %1$s a %2$s.\n\nSe ora invii un messaggio a un gruppo verificato, i contatti sostituiranno automaticamente il vecchio indirizzo con il tuo nuovo indirizzo.\n\nSi consiglia vivamente di impostare il tuo vecchio fornitore email per inoltrare tutte le email al tuo nuovo indirizzo. Altrimenti potresti perdere i messaggi di contatti che non hanno ancora ricevuto il tuo nuovo indirizzo.</string>
@ -921,6 +943,8 @@
<string name="remove_member_by_you">Hai rimosso il membro %1$s.</string> <string name="remove_member_by_you">Hai rimosso il membro %1$s.</string>
<!-- %1$s will be replaced by name and address of the contact removed from the group, %2$s will be replaced by name and address of the contact who did the action --> <!-- %1$s will be replaced by name and address of the contact removed from the group, %2$s will be replaced by name and address of the contact who did the action -->
<string name="remove_member_by_other">Membro %1$s rimosso da %2$s.</string> <string name="remove_member_by_other">Membro %1$s rimosso da %2$s.</string>
<!-- "left" in the meaning of "exited". This string is added to a chat after groups, channels, broadcasts or mailinglists are left. If a subject is needed, "You left the chat." would work as well. -->
<string name="group_left_by_you">Sei uscito.</string>
<!-- "left" in the meaning of "exited"; %1$s will be replaced by name and address of the contact leaving the group --> <!-- "left" in the meaning of "exited"; %1$s will be replaced by name and address of the contact leaving the group -->
<string name="group_left_by_other">Gruppo lasciato da %1$s.</string> <string name="group_left_by_other">Gruppo lasciato da %1$s.</string>
<string name="group_image_deleted_by_you">Hai eliminato l\'immagine del gruppo.</string> <string name="group_image_deleted_by_you">Hai eliminato l\'immagine del gruppo.</string>
@ -964,11 +988,13 @@
<string name="ephemeral_timer_weeks_by_you">Hai impostato il timer dei messaggi a scomparsa su %1$s settimane.</string> <string name="ephemeral_timer_weeks_by_you">Hai impostato il timer dei messaggi a scomparsa su %1$s settimane.</string>
<!-- %1$s will be replaced by the number of weeks (always >1) the timer is set to, %2$s will be replaced by name and address of the contact --> <!-- %1$s will be replaced by the number of weeks (always >1) the timer is set to, %2$s will be replaced by name and address of the contact -->
<string name="ephemeral_timer_weeks_by_other">Timer messaggi a scomparsa impostato su %1$s settimane da %2$s.</string> <string name="ephemeral_timer_weeks_by_other">Timer messaggi a scomparsa impostato su %1$s settimane da %2$s.</string>
<!-- this may be shown instead of the chat's input field, with buttons "More Info" and "OK" --> <!-- deprecated -->
<string name="chat_protection_broken">%1$s ha inviato un messaggio da un altro dispositivo.</string> <string name="chat_protection_broken">%1$s ha inviato un messaggio da un altro dispositivo.</string>
<string name="chat_protection_enabled_tap_to_learn_more">D\'ora in poi i messaggi saranno garantiti crittografati end-to-end. Tocca per saperne di più.</string> <string name="chat_protection_enabled_tap_to_learn_more">D\'ora in poi i messaggi saranno garantiti crittografati end-to-end. Tocca per saperne di più.</string>
<string name="chat_protection_enabled_explanation">Ora è garantito che tutti i messaggi in questa chat siano cifrati end-to-end.\n\nLa crittografia end-to-end mantiene privati i messaggi ​​tra te e i tuoi partner di chat. Nemmeno il server, il fornitore o il trasmettitore di e-mail può leggerli.</string> <string name="chat_protection_enabled_explanation">Ora è garantito che tutti i messaggi in questa chat siano cifrati end-to-end.\n\nLa crittografia end-to-end mantiene privati i messaggi ​​tra te e i tuoi partner di chat. Nemmeno il server, il fornitore o il trasmettitore di e-mail può leggerli.</string>
<!-- deprecated -->
<string name="chat_protection_broken_tap_to_learn_more">%1$s ha inviato un messaggio da un altro dispositivo. Tocca per saperne di più.</string> <string name="chat_protection_broken_tap_to_learn_more">%1$s ha inviato un messaggio da un altro dispositivo. Tocca per saperne di più.</string>
<!-- deprecated -->
<string name="chat_protection_broken_explanation">La crittografia end-to-end non può più essere garantita, probabilmente perché %1$s ha reinstallato Delta Chat o inviato un messaggio da un altro dispositivo.\n\nPuoi incontrarlo di persona e scansionare nuovamente il suo Codice QR per ristabilire la crittografia end-to-end garantita.</string> <string name="chat_protection_broken_explanation">La crittografia end-to-end non può più essere garantita, probabilmente perché %1$s ha reinstallato Delta Chat o inviato un messaggio da un altro dispositivo.\n\nPuoi incontrarlo di persona e scansionare nuovamente il suo Codice QR per ristabilire la crittografia end-to-end garantita.</string>
<string name="invalid_unencrypted_tap_to_learn_more">⚠️ %1$s richiede la crittografia end-to-end che non è ancora configurata per questa chat. Tocca per saperne di più.</string> <string name="invalid_unencrypted_tap_to_learn_more">⚠️ %1$s richiede la crittografia end-to-end che non è ancora configurata per questa chat. Tocca per saperne di più.</string>
<string name="invalid_unencrypted_explanation">Per stabilire la crittografia end-to-end, potresti incontrare i contatti di persona e scansionare il loro Codice QR per verificarli.</string> <string name="invalid_unencrypted_explanation">Per stabilire la crittografia end-to-end, potresti incontrare i contatti di persona e scansionare il loro Codice QR per verificarli.</string>
@ -1030,13 +1056,16 @@
<string name="secure_join_wait">Creazione della crittografia end-to-end garantita, per piacere attendere...</string> <string name="secure_join_wait">Creazione della crittografia end-to-end garantita, per piacere attendere...</string>
<!-- deprecated --> <!-- deprecated -->
<string name="secure_join_wait_timeout">Non è ancora possibile stabilire la crittografia end-to-end garantita, ma potresti già inviare un messaggio.</string> <string name="secure_join_wait_timeout">Non è ancora possibile stabilire la crittografia end-to-end garantita, ma potresti già inviare un messaggio.</string>
<!-- deprecated, was stock string -->
<string name="secure_join_takes_longer">Il contatto deve essere in linea per proseguire.\n\nQuesto processo continuerà automaticamente in sottofondo.</string> <string name="secure_join_takes_longer">Il contatto deve essere in linea per proseguire.\n\nQuesto processo continuerà automaticamente in sottofondo.</string>
<string name="contact_verified">%1$s verificato.</string> <string name="contact_verified">%1$s verificato.</string>
<!-- deprecated, was stock string -->
<string name="contact_not_verified">Impossibile stabilire una crittografia end-to-end garantita con %1$s.</string> <string name="contact_not_verified">Impossibile stabilire una crittografia end-to-end garantita con %1$s.</string>
<!-- Shown in contact profile. The placeholder will be replaced by the name of the contact that introduced the contact. --> <!-- Shown in contact profile. The placeholder will be replaced by the name of the contact that introduced the contact. -->
<string name="verified_by">Verificato da %1$s</string> <string name="verified_by">Verificato da %1$s</string>
<string name="verified_by_you">Verificato da me</string> <string name="verified_by_you">Verificato da me</string>
<!-- translators: "setup" is the "encryption setup" here, as in "Autocrypt Setup Message" --> <string name="verified_by_unknown">Presentato</string>
<!-- deprecated, was stock string -->
<string name="contact_setup_changed">Impostazioni modificate per %1$s</string> <string name="contact_setup_changed">Impostazioni modificate per %1$s</string>
<string name="verified_contact_required_explain">Per garantire la crittografia end-to-end, puoi aggiungere a questo gruppo solo i contatti con un segno di spunta verde.\n\nPuoi incontrare i contatti di persona e scansionare il loro Codice QR per verificarli.</string> <string name="verified_contact_required_explain">Per garantire la crittografia end-to-end, puoi aggiungere a questo gruppo solo i contatti con un segno di spunta verde.\n\nPuoi incontrare i contatti di persona e scansionare il loro Codice QR per verificarli.</string>
<string name="mailto_dialog_header_select_chat">Seleziona la chat a cui inviare il messaggio</string> <string name="mailto_dialog_header_select_chat">Seleziona la chat a cui inviare il messaggio</string>
@ -1080,7 +1109,7 @@
<string name="ImageEditorHud_flip">Capovolgi</string> <string name="ImageEditorHud_flip">Capovolgi</string>
<string name="ImageEditorHud_rotate">Ruota</string> <string name="ImageEditorHud_rotate">Ruota</string>
<!-- dc_str_* resources --> <!-- deprecated, use string "E-Mail" for non-encrypted messages instead -->
<string name="encrypted_message">Messaggio cifrato</string> <string name="encrypted_message">Messaggio cifrato</string>
<!-- strings introduced on desktop. we want to share strings between the os, in general, please do not add generic strings here --> <!-- strings introduced on desktop. we want to share strings between the os, in general, please do not add generic strings here -->
@ -1211,6 +1240,9 @@
<string name="perm_enable_bg_already_done">Hai già autorizzato Delta Chat a ricevere messaggi in secondo piano.\n\nSe i messaggi non arrivano in secondo piano, per piacere controlla anche le impostazioni di sistema.</string> <string name="perm_enable_bg_already_done">Hai già autorizzato Delta Chat a ricevere messaggi in secondo piano.\n\nSe i messaggi non arrivano in secondo piano, per piacere controlla anche le impostazioni di sistema.</string>
<!-- device messages for updates --> <!-- device messages for updates -->
<string name="update_2_0">Novità?\n\n💯 La crittografia end-to-end è ora affidabile e definitiva. I lucchetti 🔒 sono spariti!\n\n✉️ Le email classiche senza crittografia end-to-end sono contrassegnate dal simbolo di una lettera\n\n😻 Nuova schermata del profilo migliorata per tutti i tuoi contatti\n\n🔲 Nuovo pulsante per l\'accesso rapido alle app utilizzate in una chat\n\n❤️ Dona per aiutarci a rimanere indipendenti e continuare a migliorare: %1$s</string>
<!-- deprecated -->
<string name="update_1_50_android">Novità?\n\n❤️‍🔥 Nuovo selettore di emoji con più emoji\n\n🎮 App in chat migliorate: ricevi notifiche e apri le app supportate nel contesto, es. apri una voce del calendario cliccando direttamente sul messaggio\n\n👍 Ricevi notifiche sulle reazioni ai tuoi messaggi...\n\n🛠️ CORREZIONI e ANCORA DI PIÙ su %1$s</string> <string name="update_1_50_android">Novità?\n\n❤️‍🔥 Nuovo selettore di emoji con più emoji\n\n🎮 App in chat migliorate: ricevi notifiche e apri le app supportate nel contesto, es. apri una voce del calendario cliccando direttamente sul messaggio\n\n👍 Ricevi notifiche sulle reazioni ai tuoi messaggi...\n\n🛠️ CORREZIONI e ANCORA DI PIÙ su %1$s</string>
<!-- deprecated -->
<string name="update_switch_profile_placement">ℹ️ Opzione \"Cambia Profilo\" spostata: Tocca l\'immagine del tuo profilo nell\'angolo superiore della schermata principale per aggiungere o cambiare profili 💡</string> <string name="update_switch_profile_placement">ℹ️ Opzione \"Cambia Profilo\" spostata: Tocca l\'immagine del tuo profilo nell\'angolo superiore della schermata principale per aggiungere o cambiare profili 💡</string>
</resources> </resources>

5
src/main/res/values-ja/strings.xml
View file

@ -595,8 +595,9 @@
<string name="qrshow_join_contact_no_connection_toast">インターネットに接続されていないので、QRコードの設定ができません。</string> <string name="qrshow_join_contact_no_connection_toast">インターネットに接続されていないので、QRコードの設定ができません。</string>
<string name="qraccount_ask_create_and_login">%1$sに新しいメールアドレスを作ってログしますか。</string> <string name="qraccount_ask_create_and_login">%1$sに新しいメールアドレスを作ってログしますか。</string>
<string name="contact_verified">%1$sを確認しました。</string> <string name="contact_verified">%1$sを確認しました。</string>
<!-- deprecated, was stock string -->
<string name="contact_not_verified">%1$sを確認できません。</string> <string name="contact_not_verified">%1$sを確認できません。</string>
<!-- translators: "setup" is the "encryption setup" here, as in "Autocrypt Setup Message" --> <!-- deprecated, was stock string -->
<string name="contact_setup_changed">設定が%1$sに変わりました。</string> <string name="contact_setup_changed">設定が%1$sに変わりました。</string>
<!-- notifications --> <!-- notifications -->
<string name="notify_reply_button">返信</string> <string name="notify_reply_button">返信</string>
@ -615,7 +616,7 @@
<string name="ImageEditorHud_flip">反転</string> <string name="ImageEditorHud_flip">反転</string>
<string name="ImageEditorHud_rotate">回転</string> <string name="ImageEditorHud_rotate">回転</string>
<!-- dc_str_* resources --> <!-- deprecated, use string "E-Mail" for non-encrypted messages instead -->
<string name="encrypted_message">暗号化されたメッセージ</string> <string name="encrypted_message">暗号化されたメッセージ</string>
<string name="welcome_desktop">Delta Chatにようこそ</string> <string name="welcome_desktop">Delta Chatにようこそ</string>

5
src/main/res/values-km/strings.xml
View file

@ -700,8 +700,9 @@
<string name="qraccount_ask_create_and_login_another">បង្កើតអស័យដ្ឋានអុីម៉េលថ្មីនៅលើ \"%1$s\" និងកត់ចូលនៅទីនោះ?\n\nគណនីរបស់អ្នកដែលមានស្រាប់ នឹងមិនត្រូវបានលុបចោលទេ។ ប្រើប្រាស់ ការ \"ឆ្លាស់ប្តូរគណនី\" ដើម្បីធាតុប្តូររវាងគណនីរបស់អ្នក។</string> <string name="qraccount_ask_create_and_login_another">បង្កើតអស័យដ្ឋានអុីម៉េលថ្មីនៅលើ \"%1$s\" និងកត់ចូលនៅទីនោះ?\n\nគណនីរបស់អ្នកដែលមានស្រាប់ នឹងមិនត្រូវបានលុបចោលទេ។ ប្រើប្រាស់ ការ \"ឆ្លាស់ប្តូរគណនី\" ដើម្បីធាតុប្តូររវាងគណនីរបស់អ្នក។</string>
<string name="qraccount_qr_code_cannot_be_used">កូដ QR ដែលបានស្គេន មិនអាចត្រូវបានប្រើប្រាស់ដើម្បីរៀបចំគណនីថ្មីមួយទេ។</string> <string name="qraccount_qr_code_cannot_be_used">កូដ QR ដែលបានស្គេន មិនអាចត្រូវបានប្រើប្រាស់ដើម្បីរៀបចំគណនីថ្មីមួយទេ។</string>
<string name="contact_verified">%1$s បានផ្ទៀងផ្ទាត់</string> <string name="contact_verified">%1$s បានផ្ទៀងផ្ទាត់</string>
<!-- deprecated, was stock string -->
<string name="contact_not_verified">មិនអាចផ្ទៀងផ្ទាត់ %1$s</string> <string name="contact_not_verified">មិនអាចផ្ទៀងផ្ទាត់ %1$s</string>
<!-- translators: "setup" is the "encryption setup" here, as in "Autocrypt Setup Message" --> <!-- deprecated, was stock string -->
<string name="contact_setup_changed">បានដូរការរៀបចំសម្រាប់ %1$s</string> <string name="contact_setup_changed">បានដូរការរៀបចំសម្រាប់ %1$s</string>
<string name="mailto_dialog_header_select_chat">ជ្រើសរើសការជជែក ដើម្បីផ្ញើសារទៅកាន់</string> <string name="mailto_dialog_header_select_chat">ជ្រើសរើសការជជែក ដើម្បីផ្ញើសារទៅកាន់</string>
<string name="mailto_link_could_not_be_decoded">សំបុត្រទៅតំណភ្ជាប់ មិនអាចឌិកូដទេ: %1$s</string> <string name="mailto_link_could_not_be_decoded">សំបុត្រទៅតំណភ្ជាប់ មិនអាចឌិកូដទេ: %1$s</string>
@ -733,7 +734,7 @@
<string name="ImageEditorHud_flip">ត្រឡប់</string> <string name="ImageEditorHud_flip">ត្រឡប់</string>
<string name="ImageEditorHud_rotate">បង្វិល</string> <string name="ImageEditorHud_rotate">បង្វិល</string>
<!-- dc_str_* resources --> <!-- deprecated, use string "E-Mail" for non-encrypted messages instead -->
<string name="encrypted_message">សារដែលបានធ្វើឲ្យសម្ងាត់</string> <string name="encrypted_message">សារដែលបានធ្វើឲ្យសម្ងាត់</string>
<!-- strings introduced on desktop. we want to share strings between the os, in general, please do not add generic strings here --> <!-- strings introduced on desktop. we want to share strings between the os, in general, please do not add generic strings here -->

7
src/main/res/values-ko/strings.xml
View file

@ -408,7 +408,7 @@
<string name="all_apps_empty_hint">채팅에서 보내거나 받은 개인 앱들이 여기에 나타납니다.</string> <string name="all_apps_empty_hint">채팅에서 보내거나 받은 개인 앱들이 여기에 나타납니다.</string>
<string name="media_preview">미디어 미리보기</string> <string name="media_preview">미디어 미리보기</string>
<string name="send_message">메시지 전송</string> <string name="send_message">메시지 전송</string>
<!-- Placeholder %1$s will be replaced by the name of the contact changing their address. Placeholders %2$s and %3$s will be replaced by old/new addresses. --> <!-- deprecated, was stock string -->
<string name="aeap_addr_changed">%1$s의 주소가 %2$s에서 %3$s로 변경됨.</string> <string name="aeap_addr_changed">%1$s의 주소가 %2$s에서 %3$s로 변경됨.</string>
<!-- deprecated --> <!-- deprecated -->
<string name="aeap_explanation">이메일 주소를 %1$s에서 %2$s로 바꿨습니다.\n\n확인된 그룹으로 메시지를 보내면 해당 그룹의 연락처가 자동으로 이전 주소를 새 주소로 대체합니다.\n\n모든 이메일을 새 이메일 주소로 전달하도록 이전 이메일 공급자를 설정하는 것이 좋습니다. 그렇지 않으면 새 주소를 받지 못한 연락처의 메시지를 놓칠 수 있습니다.</string> <string name="aeap_explanation">이메일 주소를 %1$s에서 %2$s로 바꿨습니다.\n\n확인된 그룹으로 메시지를 보내면 해당 그룹의 연락처가 자동으로 이전 주소를 새 주소로 대체합니다.\n\n모든 이메일을 새 이메일 주소로 전달하도록 이전 이메일 공급자를 설정하는 것이 좋습니다. 그렇지 않으면 새 주소를 받지 못한 연락처의 메시지를 놓칠 수 있습니다.</string>
@ -737,8 +737,9 @@
<!-- placeholder will be replaced by the name of the inviter. --> <!-- placeholder will be replaced by the name of the inviter. -->
<string name="secure_join_replies">%1$s이 응하여, 그룹에 추가되기를 기다리는 중입니다...</string> <string name="secure_join_replies">%1$s이 응하여, 그룹에 추가되기를 기다리는 중입니다...</string>
<string name="contact_verified">%1$s이 확인됨</string> <string name="contact_verified">%1$s이 확인됨</string>
<!-- deprecated, was stock string -->
<string name="contact_not_verified">%1$s 확인할 수 없음</string> <string name="contact_not_verified">%1$s 확인할 수 없음</string>
<!-- translators: "setup" is the "encryption setup" here, as in "Autocrypt Setup Message" --> <!-- deprecated, was stock string -->
<string name="contact_setup_changed">%1$s에 대한 설정이 변경되었습니다.</string> <string name="contact_setup_changed">%1$s에 대한 설정이 변경되었습니다.</string>
<string name="mailto_dialog_header_select_chat">메시지를 보내려면 채팅을 선택하십시오</string> <string name="mailto_dialog_header_select_chat">메시지를 보내려면 채팅을 선택하십시오</string>
<!-- first placeholder is the name of the chat --> <!-- first placeholder is the name of the chat -->
@ -772,7 +773,7 @@
<string name="ImageEditorHud_flip">뒤집기</string> <string name="ImageEditorHud_flip">뒤집기</string>
<string name="ImageEditorHud_rotate">돌리기</string> <string name="ImageEditorHud_rotate">돌리기</string>
<!-- dc_str_* resources --> <!-- deprecated, use string "E-Mail" for non-encrypted messages instead -->
<string name="encrypted_message">암호화된 메시지</string> <string name="encrypted_message">암호화된 메시지</string>
<!-- strings introduced on desktop. we want to share strings between the os, in general, please do not add generic strings here --> <!-- strings introduced on desktop. we want to share strings between the os, in general, please do not add generic strings here -->

11
src/main/res/values-lt/strings.xml
View file

@ -277,7 +277,6 @@
<string name="reply_privately">Atsakyti privačiai</string> <string name="reply_privately">Atsakyti privačiai</string>
<string name="source_code">Pirminis kodas</string> <string name="source_code">Pirminis kodas</string>
<string name="donate">Paaukoti</string> <string name="donate">Paaukoti</string>
<string name="mute_for_one_hour">Išjungti 1 valandai</string> <string name="mute_for_one_hour">Išjungti 1 valandai</string>
<string name="mute_for_eight_hours">Išjungti 8 valandoms</string> <string name="mute_for_eight_hours">Išjungti 8 valandoms</string>
<string name="mute_for_one_day">Išjungti 1 dienai</string> <string name="mute_for_one_day">Išjungti 1 dienai</string>
@ -416,7 +415,7 @@
<string name="tab_all_media_empty_hint">Čia bus rodoma bet kuriame pokalbyje bendrinama medija.</string> <string name="tab_all_media_empty_hint">Čia bus rodoma bet kuriame pokalbyje bendrinama medija.</string>
<string name="media_preview">Medijos peržiūra</string> <string name="media_preview">Medijos peržiūra</string>
<string name="send_message">Siųsti žinutę</string> <string name="send_message">Siųsti žinutę</string>
<!-- Placeholder %1$s will be replaced by the name of the contact changing their address. Placeholders %2$s and %3$s will be replaced by old/new addresses. --> <!-- deprecated, was stock string -->
<string name="aeap_addr_changed">%1$s pasikeitė adresą iš %2$s į %3$s</string> <string name="aeap_addr_changed">%1$s pasikeitė adresą iš %2$s į %3$s</string>
<!-- Multi Device --> <!-- Multi Device -->
<!-- "Second Device" can also be translated as "Another Device", if that is catchier in the destination language. However, make sure to use the term consistently. --> <!-- "Second Device" can also be translated as "Another Device", if that is catchier in the destination language. However, make sure to use the term consistently. -->
@ -708,8 +707,9 @@
<string name="ephemeral_timer_weeks_by_you">Jūs nustatėte išnykstančių žinučių laikmatį į %1$s sav.</string> <string name="ephemeral_timer_weeks_by_you">Jūs nustatėte išnykstančių žinučių laikmatį į %1$s sav.</string>
<!-- %1$s will be replaced by the number of weeks (always >1) the timer is set to, %2$s will be replaced by name and address of the contact --> <!-- %1$s will be replaced by the number of weeks (always >1) the timer is set to, %2$s will be replaced by name and address of the contact -->
<string name="ephemeral_timer_weeks_by_other">%2$s nustatė išnykstančių žinučių laikmatį į %1$s sav. </string> <string name="ephemeral_timer_weeks_by_other">%2$s nustatė išnykstančių žinučių laikmatį į %1$s sav. </string>
<!-- this may be shown instead of the chat's input field, with buttons "More Info" and "OK" --> <!-- deprecated -->
<string name="chat_protection_broken">%1$s išsiuntė žinutę iš kito įrenginio.</string> <string name="chat_protection_broken">%1$s išsiuntė žinutę iš kito įrenginio.</string>
<!-- deprecated -->
<string name="chat_protection_broken_tap_to_learn_more">%1$s išsiuntė žinutę iš kito įrenginio. Bakstelėkite norėdami sužinoti daugiau.</string> <string name="chat_protection_broken_tap_to_learn_more">%1$s išsiuntė žinutę iš kito įrenginio. Bakstelėkite norėdami sužinoti daugiau.</string>
<string name="learn_more">Sužinoti daugiau</string> <string name="learn_more">Sužinoti daugiau</string>
@ -746,8 +746,9 @@
<!-- the placeholder will be replaced by the address of the profile --> <!-- the placeholder will be replaced by the address of the profile -->
<string name="qrlogin_ask_login">Prisijungti prie „%1$s“?</string> <string name="qrlogin_ask_login">Prisijungti prie „%1$s“?</string>
<string name="contact_verified">%1$s patvirtintas.</string> <string name="contact_verified">%1$s patvirtintas.</string>
<!-- deprecated, was stock string -->
<string name="contact_not_verified">Nepavyksta patvirtinti %1$s</string> <string name="contact_not_verified">Nepavyksta patvirtinti %1$s</string>
<!-- translators: "setup" is the "encryption setup" here, as in "Autocrypt Setup Message" --> <!-- deprecated, was stock string -->
<string name="contact_setup_changed">Pakeista sąranka, skirta %1$s.</string> <string name="contact_setup_changed">Pakeista sąranka, skirta %1$s.</string>
<string name="mailto_dialog_header_select_chat">Pasirinkite pokalbį, į kurį siųsti žinutę</string> <string name="mailto_dialog_header_select_chat">Pasirinkite pokalbį, į kurį siųsti žinutę</string>
<string name="mailto_link_could_not_be_decoded">nepavyko dekoduoti mailto nuorodos: %1$s</string> <string name="mailto_link_could_not_be_decoded">nepavyko dekoduoti mailto nuorodos: %1$s</string>
@ -776,7 +777,7 @@
<string name="ImageEditorHud_flip">Apversti</string> <string name="ImageEditorHud_flip">Apversti</string>
<string name="ImageEditorHud_rotate">Pasukti</string> <string name="ImageEditorHud_rotate">Pasukti</string>
<!-- dc_str_* resources --> <!-- deprecated, use string "E-Mail" for non-encrypted messages instead -->
<string name="encrypted_message">Šifruota žinutė</string> <string name="encrypted_message">Šifruota žinutė</string>
<string name="about_licensed_under_desktop">Ši programinė įranga yra licencijuota pagal GNU GPL versiją 3, o pirminis kodas yra prieinamas „GitHub“ internetinėje svetainėje.</string> <string name="about_licensed_under_desktop">Ši programinė įranga yra licencijuota pagal GNU GPL versiją 3, o pirminis kodas yra prieinamas „GitHub“ internetinėje svetainėje.</string>

2
src/main/res/values-nb/strings.xml
View file

@ -386,7 +386,7 @@
<!-- permissions --> <!-- permissions -->
<string name="perm_required_title">Tillatelse kreves</string> <string name="perm_required_title">Tillatelse kreves</string>
<string name="perm_continue">Fortsett</string> <string name="perm_continue">Fortsett</string>
<!-- dc_str_* resources --> <!-- deprecated, use string "E-Mail" for non-encrypted messages instead -->
<string name="encrypted_message">Kryptert melding</string> <string name="encrypted_message">Kryptert melding</string>
<string name="welcome_desktop">Velkommen til Delta Chat</string> <string name="welcome_desktop">Velkommen til Delta Chat</string>

26
src/main/res/values-nl/strings.xml
View file

@ -261,6 +261,11 @@
<string name="please_enter_broadcast_list_name">Geef de verzendlijst een naam.</string> <string name="please_enter_broadcast_list_name">Geef de verzendlijst een naam.</string>
<!-- consider keeping the term "channel" as in WhatsApp or Telegram --> <!-- consider keeping the term "channel" as in WhatsApp or Telegram -->
<string name="channel_name">Kanaalnaam</string> <string name="channel_name">Kanaalnaam</string>
<string name="email">E-mail</string>
<!-- "New" as in "Create New E-Mail"; shown together with "New Group" and "New Channel" -->
<string name="new_email">Nieuwe e-mail</string>
<!-- the "Subject" of an e-mail, use the term common in classic e-mail apps -->
<string name="subject">Onderwerp</string>
<string name="menu_send">Versturen</string> <string name="menu_send">Versturen</string>
<string name="menu_toggle_keyboard">Emojitoetsenbord tonen/verbergen</string> <string name="menu_toggle_keyboard">Emojitoetsenbord tonen/verbergen</string>
<string name="menu_edit_group">Groep aanpassen</string> <string name="menu_edit_group">Groep aanpassen</string>
@ -355,6 +360,7 @@
<!-- Menu item beside an app/chat that adds an icon to the system's home screen. If the user taps that icon, the app/chat is opened directly. --> <!-- Menu item beside an app/chat that adds an icon to the system's home screen. If the user taps that icon, the app/chat is opened directly. -->
<string name="add_to_home_screen">Toevoegen aan startscherm</string> <string name="add_to_home_screen">Toevoegen aan startscherm</string>
<string name="donate">Doneren</string> <string name="donate">Doneren</string>
<string name="donate_device_msg">❤️ Het lijkt er op dat je blij bent met Delta Chat!\n\nAls dat zo is, zouden we je vriendelijk willen vragen om een donatie, zodat Delta Chat gratis beschikbaar kan blijven.\n\n Ook al is Delta Chat gratis en opensource, de ontwikkeling ervan kost wél geld. Jouw donatie kan het verschil maken!\n\nhttps://delta.chat/donate</string>
<string name="mute_for_one_hour">1 uur lang uitschakelen</string> <string name="mute_for_one_hour">1 uur lang uitschakelen</string>
<string name="mute_for_eight_hours">8 uur lang uitschakelen</string> <string name="mute_for_eight_hours">8 uur lang uitschakelen</string>
@ -563,7 +569,7 @@
<!-- option to show images in the gallery as square (instead of using correct width/height) --> <!-- option to show images in the gallery as square (instead of using correct width/height) -->
<string name="square_grid">Vierkant rooster</string> <string name="square_grid">Vierkant rooster</string>
<string name="send_message">Bericht versturen</string> <string name="send_message">Bericht versturen</string>
<!-- Placeholder %1$s will be replaced by the name of the contact changing their address. Placeholders %2$s and %3$s will be replaced by old/new addresses. --> <!-- deprecated, was stock string -->
<string name="aeap_addr_changed">%1$s heeft zijn/haar adres veranderd van %2$s naar %3$s</string> <string name="aeap_addr_changed">%1$s heeft zijn/haar adres veranderd van %2$s naar %3$s</string>
<!-- deprecated --> <!-- deprecated -->
<string name="aeap_explanation">Je hebt je e-mailadres veranderd van %1$s naar %2$s.\n\nAls je een bericht stuurt aan een goedgekeurde groep, dan zien contactpersonen in de groep je nieuwe adres.\n\nWel raden we aan om bij je oude provider in te stellen dat je e-mails wilt doorsturen naar je nieuwe adres, anders missen sommige contactpersonen mogelijk je berichten.</string> <string name="aeap_explanation">Je hebt je e-mailadres veranderd van %1$s naar %2$s.\n\nAls je een bericht stuurt aan een goedgekeurde groep, dan zien contactpersonen in de groep je nieuwe adres.\n\nWel raden we aan om bij je oude provider in te stellen dat je e-mails wilt doorsturen naar je nieuwe adres, anders missen sommige contactpersonen mogelijk je berichten.</string>
@ -966,11 +972,13 @@
<string name="ephemeral_timer_weeks_by_you">Je hebt de tijdklok van verdwijnende berichten ingesteld op %1$s weken.</string> <string name="ephemeral_timer_weeks_by_you">Je hebt de tijdklok van verdwijnende berichten ingesteld op %1$s weken.</string>
<!-- %1$s will be replaced by the number of weeks (always >1) the timer is set to, %2$s will be replaced by name and address of the contact --> <!-- %1$s will be replaced by the number of weeks (always >1) the timer is set to, %2$s will be replaced by name and address of the contact -->
<string name="ephemeral_timer_weeks_by_other">De tijdklok van verdwijnende berichten is door %2$s ingesteld op %1$s weken.</string> <string name="ephemeral_timer_weeks_by_other">De tijdklok van verdwijnende berichten is door %2$s ingesteld op %1$s weken.</string>
<!-- this may be shown instead of the chat's input field, with buttons "More Info" and "OK" --> <!-- deprecated -->
<string name="chat_protection_broken">%1$s heeft een bericht verstuurd vanaf een ander apparaat.</string> <string name="chat_protection_broken">%1$s heeft een bericht verstuurd vanaf een ander apparaat.</string>
<string name="chat_protection_enabled_tap_to_learn_more">Berichten zijn vanaf nu gegarandeerd van eind-tot-eindversleuteling voorzien. Druk hier voor meer informatie.</string> <string name="chat_protection_enabled_tap_to_learn_more">Berichten zijn gegarandeerd van eind-tot-eindversleuteling voorzien. Druk hier voor meer informatie.</string>
<string name="chat_protection_enabled_explanation">Alle berichten in dit gesprek zijn vanaf nu gegarandeerd van eind-tot-eindversleuteling voorzien.\n\nMet behulp van deze versleuteling blijven berichten tussen jou en je gesprekspartners geheim - zelfs je e-mailprovider kan ze niet uitlezen.</string> <string name="chat_protection_enabled_explanation">Alle berichten in dit gesprek zijn gegarandeerd van eind-tot-eindversleuteling voorzien.\n\nMet behulp van deze versleuteling blijven berichten tussen jou en je gesprekspartners geheim - zelfs je e-mailprovider kan ze niet uitlezen.</string>
<!-- deprecated -->
<string name="chat_protection_broken_tap_to_learn_more">%1$s heeft een bericht verstuurd vanaf een ander apparaat. Druk hier voor meer informatie.</string> <string name="chat_protection_broken_tap_to_learn_more">%1$s heeft een bericht verstuurd vanaf een ander apparaat. Druk hier voor meer informatie.</string>
<!-- deprecated -->
<string name="chat_protection_broken_explanation">Eind-tot-eindversleuteling kan niet meer worden gegarandeerd, omdat %1$s Delta Chat opnieuw heeft geïnstalleerd of een bericht vanaf een ander apparaat heeft verstuurd.\n\nMaak een afspraak met hem/haar en scan de QR-code opnieuw om eind-tot-eindversleuteling weer in te schakelen.</string> <string name="chat_protection_broken_explanation">Eind-tot-eindversleuteling kan niet meer worden gegarandeerd, omdat %1$s Delta Chat opnieuw heeft geïnstalleerd of een bericht vanaf een ander apparaat heeft verstuurd.\n\nMaak een afspraak met hem/haar en scan de QR-code opnieuw om eind-tot-eindversleuteling weer in te schakelen.</string>
<string name="invalid_unencrypted_tap_to_learn_more">⚠️ Voor %1$s is eind-tot-eindversleuteling vereist, maar dit is nog niet ingesteld in het huidige gesprek. Druk voor meer informatie.</string> <string name="invalid_unencrypted_tap_to_learn_more">⚠️ Voor %1$s is eind-tot-eindversleuteling vereist, maar dit is nog niet ingesteld in het huidige gesprek. Druk voor meer informatie.</string>
<string name="invalid_unencrypted_explanation">Spreek met elkaar af en scan elkaars QR-code om eind-tot-eindversleuteling op te zetten.</string> <string name="invalid_unencrypted_explanation">Spreek met elkaar af en scan elkaars QR-code om eind-tot-eindversleuteling op te zetten.</string>
@ -1032,13 +1040,16 @@
<string name="secure_join_wait">Bezig met opzetten van eind-tot-eindversleuteling…</string> <string name="secure_join_wait">Bezig met opzetten van eind-tot-eindversleuteling…</string>
<!-- deprecated --> <!-- deprecated -->
<string name="secure_join_wait_timeout">Er kan nog geen eind-tot-eindversleuteling worden gegarandeerd, maar je kunt wel alvast een bericht sturen.</string> <string name="secure_join_wait_timeout">Er kan nog geen eind-tot-eindversleuteling worden gegarandeerd, maar je kunt wel alvast een bericht sturen.</string>
<!-- deprecated, was stock string -->
<string name="secure_join_takes_longer">Het lijkt langer te duren dan verwacht - wellicht is een van jullie offline.\n\nHet proces wordt echter op de achtergrond voortgezet.</string> <string name="secure_join_takes_longer">Het lijkt langer te duren dan verwacht - wellicht is een van jullie offline.\n\nHet proces wordt echter op de achtergrond voortgezet.</string>
<string name="contact_verified">%1$s is goedgekeurd.</string> <string name="contact_verified">%1$s is goedgekeurd.</string>
<!-- deprecated, was stock string -->
<string name="contact_not_verified">Er kan geen eind-tot-eindversleuteling met %1$s worden gegarandeerd.</string> <string name="contact_not_verified">Er kan geen eind-tot-eindversleuteling met %1$s worden gegarandeerd.</string>
<!-- Shown in contact profile. The placeholder will be replaced by the name of the contact that introduced the contact. --> <!-- Shown in contact profile. The placeholder will be replaced by the name of the contact that introduced the contact. -->
<string name="verified_by">Geïntroduceerd door %1$s</string> <string name="verified_by">Geïntroduceerd door %1$s</string>
<string name="verified_by_you">Geïntroduceerd door mij</string> <string name="verified_by_you">Geïntroduceerd door mij</string>
<!-- translators: "setup" is the "encryption setup" here, as in "Autocrypt Setup Message" --> <string name="verified_by_unknown">Geïntroduceerd</string>
<!-- deprecated, was stock string -->
<string name="contact_setup_changed">Gewijzigde instellingen voor %1$s</string> <string name="contact_setup_changed">Gewijzigde instellingen voor %1$s</string>
<string name="verified_contact_required_explain">Om de eind-tot-eindversleuteling te garanderen, kun je alleen contactpersonen met een groen vinkje toevoegen aan deze groep.\n\nVan niet-goedgekeurde contactpersonen kun je de QR-code scannen om ze goed te keuren.</string> <string name="verified_contact_required_explain">Om de eind-tot-eindversleuteling te garanderen, kun je alleen contactpersonen met een groen vinkje toevoegen aan deze groep.\n\nVan niet-goedgekeurde contactpersonen kun je de QR-code scannen om ze goed te keuren.</string>
<string name="mailto_dialog_header_select_chat">Kies in welk gesprek je dit bericht wilt delen</string> <string name="mailto_dialog_header_select_chat">Kies in welk gesprek je dit bericht wilt delen</string>
@ -1082,7 +1093,7 @@
<string name="ImageEditorHud_flip">Spiegelen</string> <string name="ImageEditorHud_flip">Spiegelen</string>
<string name="ImageEditorHud_rotate">Draaien</string> <string name="ImageEditorHud_rotate">Draaien</string>
<!-- dc_str_* resources --> <!-- deprecated, use string "E-Mail" for non-encrypted messages instead -->
<string name="encrypted_message">Versleuteld bericht</string> <string name="encrypted_message">Versleuteld bericht</string>
<!-- strings introduced on desktop. we want to share strings between the os, in general, please do not add generic strings here --> <!-- strings introduced on desktop. we want to share strings between the os, in general, please do not add generic strings here -->
@ -1213,6 +1224,9 @@
<string name="perm_enable_bg_already_done">Je hebt al toestemming gegeven voor het ophalen van berichten op de achtergrond.\n\nAls het nog steeds niet werkt, controleer dan de systeeminstellingen.</string> <string name="perm_enable_bg_already_done">Je hebt al toestemming gegeven voor het ophalen van berichten op de achtergrond.\n\nAls het nog steeds niet werkt, controleer dan de systeeminstellingen.</string>
<!-- device messages for updates --> <!-- device messages for updates -->
<string name="update_2_0">Wijzigingslog:\n\n💯 Eind-tot-eindversleuteling is voortaan betrouwbaarder én standaard. Slotjes 🔒 zijn verleden tijd!\n\n✉️ Klassieke e-mails zonder eind-tot-eindversleuteling worden voortaan gemarkeerd met een letter\n\n😻 Nieuwe, mooiere profielpagina\'s van al je contactpersonen\n\n🔲 Nieuwe knop voor snelle toegang tot apps in gesprekken\n\n❤️ Overweeg een donatie, zodat we onafhankelijk kunnen blijven en verbeteringen kunnen blijven aanbrengen: %1$s</string>
<!-- deprecated -->
<string name="update_1_50_android">Wijzigingslog:\n\n❤️‍🔥 Nieuwe emojikiezer met veel meer emojis\n\n🎮 Verbeterde apps in gesprekken: ontvang meldingen open ondersteunde apps met links, bijv. een agenda-uitnodiging\n\n👍 Ontvang meldingen bij reacties op berichten\n\n… 🛠️ Opgeloste fouten en VEEL MEER op %1$s</string> <string name="update_1_50_android">Wijzigingslog:\n\n❤️‍🔥 Nieuwe emojikiezer met veel meer emojis\n\n🎮 Verbeterde apps in gesprekken: ontvang meldingen open ondersteunde apps met links, bijv. een agenda-uitnodiging\n\n👍 Ontvang meldingen bij reacties op berichten\n\n… 🛠️ Opgeloste fouten en VEEL MEER op %1$s</string>
<!-- deprecated -->
<string name="update_switch_profile_placement">ℹ️ De optie om een ander profiel te kiezen is verplaatst: druk op je profielfoto op het hoofdscherm om het profielmenu te openen.💡</string> <string name="update_switch_profile_placement">ℹ️ De optie om een ander profiel te kiezen is verplaatst: druk op je profielfoto op het hoofdscherm om het profielmenu te openen.💡</string>
</resources> </resources>

38
src/main/res/values-pl/strings.xml
View file

@ -279,6 +279,11 @@
<string name="please_enter_broadcast_list_name">Wpisz nazwę listy rozgłoszeniowej</string> <string name="please_enter_broadcast_list_name">Wpisz nazwę listy rozgłoszeniowej</string>
<!-- consider keeping the term "channel" as in WhatsApp or Telegram --> <!-- consider keeping the term "channel" as in WhatsApp or Telegram -->
<string name="channel_name">Nazwa kanału</string> <string name="channel_name">Nazwa kanału</string>
<string name="email">E-mail</string>
<!-- "New" as in "Create New E-Mail"; shown together with "New Group" and "New Channel" -->
<string name="new_email">Nowy e-mail</string>
<!-- the "Subject" of an e-mail, use the term common in classic e-mail apps -->
<string name="subject">Temat</string>
<string name="menu_send">Wyślij</string> <string name="menu_send">Wyślij</string>
<string name="menu_toggle_keyboard">Przełącz klawiaturę emoji</string> <string name="menu_toggle_keyboard">Przełącz klawiaturę emoji</string>
<string name="menu_edit_group">Edytuj grupę</string> <string name="menu_edit_group">Edytuj grupę</string>
@ -373,6 +378,7 @@
<!-- Menu item beside an app/chat that adds an icon to the system's home screen. If the user taps that icon, the app/chat is opened directly. --> <!-- Menu item beside an app/chat that adds an icon to the system's home screen. If the user taps that icon, the app/chat is opened directly. -->
<string name="add_to_home_screen">Dodaj do ekranu głównego</string> <string name="add_to_home_screen">Dodaj do ekranu głównego</string>
<string name="donate">Wspomóż</string> <string name="donate">Wspomóż</string>
<string name="donate_device_msg">❤️ Wygląda na to, że podoba ci się Delta Chat!\n\nProsimy o przekazanie darowizny, abyśmy mogli zapewnić, że Delta Chat pozostanie darmowy dla wszystkich.\n\nChociaż Delta Chat jest darmowy i ma otwarte oprogramowanie, jego rozwój kosztuje. Pomóż nam zachować niezależność Delta Chat i uczynić go w przyszłości jeszcze lepszym.\n\nhttps://delta.chat/pl/donate</string>
<string name="mute_for_one_hour">Wyłącz na 1 godzinę</string> <string name="mute_for_one_hour">Wyłącz na 1 godzinę</string>
<string name="mute_for_eight_hours">Wyłącz na 8 godzin</string> <string name="mute_for_eight_hours">Wyłącz na 8 godzin</string>
@ -595,7 +601,7 @@
<!-- option to show images in the gallery as square (instead of using correct width/height) --> <!-- option to show images in the gallery as square (instead of using correct width/height) -->
<string name="square_grid">Siatka kwadratowa</string> <string name="square_grid">Siatka kwadratowa</string>
<string name="send_message">Wyślij wiadomość</string> <string name="send_message">Wyślij wiadomość</string>
<!-- Placeholder %1$s will be replaced by the name of the contact changing their address. Placeholders %2$s and %3$s will be replaced by old/new addresses. --> <!-- deprecated, was stock string -->
<string name="aeap_addr_changed">%1$s zmieniła swój adres z %2$s na %3$s</string> <string name="aeap_addr_changed">%1$s zmieniła swój adres z %2$s na %3$s</string>
<!-- deprecated --> <!-- deprecated -->
<string name="aeap_explanation">Zmieniłeś swój adres e-mail z %1$s na %2$s.\n\nJeśli teraz wyślesz wiadomość do zweryfikowanej grupy, kontakty tam zawarte automatycznie zastąpią stary adres Twoim nowym.\n\nBardzo zalecane jest, aby ustawić swojego starego dostawcę emaila tak, aby przekazywał wszystkie emaile na Twój nowy adres email. W przeciwnym razie możesz przegapić wiadomości od kontaktów, które jeszcze nie dostały Twojego nowego adresu.</string> <string name="aeap_explanation">Zmieniłeś swój adres e-mail z %1$s na %2$s.\n\nJeśli teraz wyślesz wiadomość do zweryfikowanej grupy, kontakty tam zawarte automatycznie zastąpią stary adres Twoim nowym.\n\nBardzo zalecane jest, aby ustawić swojego starego dostawcę emaila tak, aby przekazywał wszystkie emaile na Twój nowy adres email. W przeciwnym razie możesz przegapić wiadomości od kontaktów, które jeszcze nie dostały Twojego nowego adresu.</string>
@ -998,14 +1004,16 @@
<string name="ephemeral_timer_weeks_by_you">Ustawiono zegar znikających wiadomości na %1$s tyg.</string> <string name="ephemeral_timer_weeks_by_you">Ustawiono zegar znikających wiadomości na %1$s tyg.</string>
<!-- %1$s will be replaced by the number of weeks (always >1) the timer is set to, %2$s will be replaced by name and address of the contact --> <!-- %1$s will be replaced by the number of weeks (always >1) the timer is set to, %2$s will be replaced by name and address of the contact -->
<string name="ephemeral_timer_weeks_by_other"> Użytkownik %2$s ustawił zegar znikających wiadomości na %1$s tyg.</string> <string name="ephemeral_timer_weeks_by_other"> Użytkownik %2$s ustawił zegar znikających wiadomości na %1$s tyg.</string>
<!-- this may be shown instead of the chat's input field, with buttons "More Info" and "OK" --> <!-- deprecated -->
<string name="chat_protection_broken">Użytkownik %1$s wysłał wiadomość z innego urządzenia.</string> <string name="chat_protection_broken">Użytkownik %1$s wysłał wiadomość z innego urządzenia.</string>
<string name="chat_protection_enabled_tap_to_learn_more">Od teraz gwarantujemy, że wiadomości będą szyfrowane metodą end-to-end. Dotknij, aby przeczytać więcej.</string> <string name="chat_protection_enabled_tap_to_learn_more">Wiadomości będą szyfrowane metodą end-to-end. Dotknij, aby przeczytać więcej.</string>
<string name="chat_protection_enabled_explanation">Teraz gwarantujemy, że wszystkie wiadomości w tym czacie są szyfrowane metodą end-to-end.\n\nSzyfrowanie end-to-end zapewnia prywatność wiadomości między tobą a twoimi partnerami czatów. Nawet serwery, dostawcy i pośrednicy nie są w stanie ich odczytać.</string> <string name="chat_protection_enabled_explanation">Wszystkie wiadomości w tym czacie są szyfrowane metodą end-to-end.\n\nSzyfrowanie end-to-end zapewnia prywatność wiadomości między tobą a twoimi partnerami czatów. Nawet serwery, dostawcy i pośrednicy nie są w stanie ich odczytać.</string>
<!-- deprecated -->
<string name="chat_protection_broken_tap_to_learn_more">Użytkownik %1$s wysłał wiadomość z innego urządzenia. Dotknij, aby przeczytać więcej.</string> <string name="chat_protection_broken_tap_to_learn_more">Użytkownik %1$s wysłał wiadomość z innego urządzenia. Dotknij, aby przeczytać więcej.</string>
<!-- deprecated -->
<string name="chat_protection_broken_explanation">Nie można już zagwarantować szyfrowania end-to-end, prawdopodobnie z powodu ponownej instalacji Delta Chat przez %1$s lub wysłania wiadomości z innego urządzenia.\n\nMożesz spotkać się z tą osobą osobiście i ponownie zeskanować jej kod QR, aby przywrócić gwarantowane szyfrowanie end-to-end.</string> <string name="chat_protection_broken_explanation">Nie można już zagwarantować szyfrowania end-to-end, prawdopodobnie z powodu ponownej instalacji Delta Chat przez %1$s lub wysłania wiadomości z innego urządzenia.\n\nMożesz spotkać się z tą osobą osobiście i ponownie zeskanować jej kod QR, aby przywrócić gwarantowane szyfrowanie end-to-end.</string>
<string name="invalid_unencrypted_tap_to_learn_more">⚠️ %1$s wymaga szyfrowania end-to-end, które nie zostało jeszcze skonfigurowane dla tego czatu. Dotknij, aby dowiedzieć się więcej.</string> <string name="invalid_unencrypted_tap_to_learn_more">⚠️ %1$s wymaga szyfrowania end-to-end, które nie zostało jeszcze skonfigurowane dla tego czatu. Dotknij, aby dowiedzieć się więcej.</string>
<string name="invalid_unencrypted_explanation">Aby ustanowić szyfrowanie end-to-end, możesz spotkać się z kontaktami osobiście i zeskanować ich kod QR, żeby ich wprowadzić.</string> <string name="invalid_unencrypted_explanation">Aby ustanowić szyfrowanie end-to-end, możesz spotkać się z kontaktami osobiście i zeskanować ich kod QR, żeby ich zweryfikować.</string>
<string name="learn_more">Czytaj więcej</string> <string name="learn_more">Czytaj więcej</string>
<string name="devicemsg_self_deleted">Usunięto czat „Zapisane wiadomości”.\n\nℹ️ Aby ponownie użyć funkcji „Zapisane wiadomości”, utwórz nowy czat ze sobą.</string> <string name="devicemsg_self_deleted">Usunięto czat „Zapisane wiadomości”.\n\nℹ️ Aby ponownie użyć funkcji „Zapisane wiadomości”, utwórz nowy czat ze sobą.</string>
@ -1061,18 +1069,21 @@
<string name="secure_join_started">Użytkownik %1$s zaprosił cię do dołączenia do tej grupy.\n\nCzekam na odpowiedź urządzenia %2$s…</string> <string name="secure_join_started">Użytkownik %1$s zaprosił cię do dołączenia do tej grupy.\n\nCzekam na odpowiedź urządzenia %2$s…</string>
<!-- placeholder will be replaced by the name of the inviter. --> <!-- placeholder will be replaced by the name of the inviter. -->
<string name="secure_join_replies">Użytkownik %1$s odpowiedział, czekając na dodanie do grupy…</string> <string name="secure_join_replies">Użytkownik %1$s odpowiedział, czekając na dodanie do grupy…</string>
<string name="secure_join_wait">Ustanawiam gwarantowane szyfrowanie typu end-to-end, proszę czekać…</string> <string name="secure_join_wait">Ustanawiam szyfrowanie typu end-to-end, proszę czekać…</string>
<!-- deprecated --> <!-- deprecated -->
<string name="secure_join_wait_timeout">Nie można jeszcze ustanowić gwarantowanego szyfrowania typu end-to-end, ale być może już wysłałeś wiadomość.</string> <string name="secure_join_wait_timeout">Nie można jeszcze ustanowić gwarantowanego szyfrowania typu end-to-end, ale być może już wysłałeś wiadomość.</string>
<!-- deprecated, was stock string -->
<string name="secure_join_takes_longer">Aby kontynuować, kontakt musi być online.\n\nTen proces będzie kontynuowany automatycznie w tle.</string> <string name="secure_join_takes_longer">Aby kontynuować, kontakt musi być online.\n\nTen proces będzie kontynuowany automatycznie w tle.</string>
<string name="contact_verified">Kontakt %1$s zweryfikowany.</string> <string name="contact_verified">Kontakt %1$s zweryfikowany.</string>
<string name="contact_not_verified">Nie można zweryfikować szyfrowania typu end-to-end %1$s</string> <!-- deprecated, was stock string -->
<string name="contact_not_verified">Nie można ustanowić szyfrowania typu end-to-end z %1$s</string>
<!-- Shown in contact profile. The placeholder will be replaced by the name of the contact that introduced the contact. --> <!-- Shown in contact profile. The placeholder will be replaced by the name of the contact that introduced the contact. -->
<string name="verified_by">Zweryfikowano przez %1$s</string> <string name="verified_by">Kontakt zweryfikowany przez %1$s</string>
<string name="verified_by_you">Zweryfikowane przez ciebie</string> <string name="verified_by_you">Kontakt zweryfikowany przez ciebie</string>
<!-- translators: "setup" is the "encryption setup" here, as in "Autocrypt Setup Message" --> <string name="verified_by_unknown">Zweryfikowano</string>
<!-- deprecated, was stock string -->
<string name="contact_setup_changed">Zmieniono konfigurację dla %1$s</string> <string name="contact_setup_changed">Zmieniono konfigurację dla %1$s</string>
<string name="verified_contact_required_explain">Aby zagwarantować szyfrowanie end-to-end, do tej grupy możesz dodawać wyłącznie kontakty oznaczone zielonym znacznikiem wyboru.\n\nMożesz spotkać się z kontaktami osobiście i zeskanować ich kod QR, aby je przedstawić.</string> <string name="verified_contact_required_explain">Aby zagwarantować szyfrowanie end-to-end, do tej grupy możesz dodawać wyłącznie kontakty oznaczone zielonym znacznikiem wyboru.\n\nMożesz spotkać się z kontaktami osobiście i zeskanować ich kod QR, aby je zweryfikować.</string>
<string name="mailto_dialog_header_select_chat">Wybierz czat, do którego chcesz wysłać wiadomość</string> <string name="mailto_dialog_header_select_chat">Wybierz czat, do którego chcesz wysłać wiadomość</string>
<!-- first placeholder is the name of the chat --> <!-- first placeholder is the name of the chat -->
<string name="confirm_replace_draft">Na czacie %1$s jest już wersja robocza wiadomości, czy chcesz ją zastąpić?</string> <string name="confirm_replace_draft">Na czacie %1$s jest już wersja robocza wiadomości, czy chcesz ją zastąpić?</string>
@ -1114,7 +1125,7 @@
<string name="ImageEditorHud_flip">Przełącz</string> <string name="ImageEditorHud_flip">Przełącz</string>
<string name="ImageEditorHud_rotate">Obróć</string> <string name="ImageEditorHud_rotate">Obróć</string>
<!-- dc_str_* resources --> <!-- deprecated, use string "E-Mail" for non-encrypted messages instead -->
<string name="encrypted_message">Zaszyfrowana wiadomość</string> <string name="encrypted_message">Zaszyfrowana wiadomość</string>
<!-- strings introduced on desktop. we want to share strings between the os, in general, please do not add generic strings here --> <!-- strings introduced on desktop. we want to share strings between the os, in general, please do not add generic strings here -->
@ -1245,6 +1256,9 @@
<string name="perm_enable_bg_already_done">Pozwolono już Delta Chat na odbieranie wiadomości w tle.\n\nJeśli wiadomości nadal nie docierają w tle, sprawdź też ustawienia systemu.</string> <string name="perm_enable_bg_already_done">Pozwolono już Delta Chat na odbieranie wiadomości w tle.\n\nJeśli wiadomości nadal nie docierają w tle, sprawdź też ustawienia systemu.</string>
<!-- device messages for updates --> <!-- device messages for updates -->
<string name="update_2_0">Co nowego?\n\n💯 Szyfrowanie end-to-end jest niezawodne i na zawsze. Kłódki 🔒 odchodzą w zapomnienie!\n\n✉️ Klasyczna poczta e-mail bez szyfrowania end-to-end jest oznaczona symbolem litery.\n\n😻 Nowy, ulepszony ekran profilu dla wszystkich kontaktów.\n\n🔲 Nowy przycisk szybkiego dostępu do aplikacji używanych na czacie.\n\n❤️ Prosimy o darowizny, które pomogą nam zachować niezależność i stale wprowadzać ulepszenia: %1$s</string>
<!-- deprecated -->
<string name="update_1_50_android">Co nowego?\n\n❤️‍🔥 Nowy selektor emoji z większą liczbą emoji\n\n🎮 Ulepszone aplikacje czatu: Otrzymuj powiadomienia i otwieraj aplikacje pomocnicze w kontekście, np. otwieraj dodany wpis kalendarza bezpośrednio\n\n👍 Otrzymuj powiadomienia o reakcjach na swoje wiadomości\n\n... 🛠️ POPRAWKI i JESZCZE WIĘCEJ na %1$s</string> <string name="update_1_50_android">Co nowego?\n\n❤️‍🔥 Nowy selektor emoji z większą liczbą emoji\n\n🎮 Ulepszone aplikacje czatu: Otrzymuj powiadomienia i otwieraj aplikacje pomocnicze w kontekście, np. otwieraj dodany wpis kalendarza bezpośrednio\n\n👍 Otrzymuj powiadomienia o reakcjach na swoje wiadomości\n\n... 🛠️ POPRAWKI i JESZCZE WIĘCEJ na %1$s</string>
<!-- deprecated -->
<string name="update_switch_profile_placement">ℹ️ Opcja „Przełącz profil” została przeniesiona: Dotknij swojego zdjęcia profilowego w górnym rogu ekranu głównego, aby dodać lub przełączyć profile 💡</string> <string name="update_switch_profile_placement">ℹ️ Opcja „Przełącz profil” została przeniesiona: Dotknij swojego zdjęcia profilowego w górnym rogu ekranu głównego, aby dodać lub przełączyć profile 💡</string>
</resources> </resources>

7
src/main/res/values-pt-rBR/strings.xml
View file

@ -463,7 +463,7 @@
<string name="all_apps_empty_hint">Apps recebidas ou enviadas em qualquer bate-papo aparecerão aqui.</string> <string name="all_apps_empty_hint">Apps recebidas ou enviadas em qualquer bate-papo aparecerão aqui.</string>
<string name="media_preview">Pré-visualização.</string> <string name="media_preview">Pré-visualização.</string>
<string name="send_message">Enviar mensagem</string> <string name="send_message">Enviar mensagem</string>
<!-- Placeholder %1$s will be replaced by the name of the contact changing their address. Placeholders %2$s and %3$s will be replaced by old/new addresses. --> <!-- deprecated, was stock string -->
<string name="aeap_addr_changed">%1$s mudou seu endereço de %2$s para %3$s</string> <string name="aeap_addr_changed">%1$s mudou seu endereço de %2$s para %3$s</string>
<!-- deprecated --> <!-- deprecated -->
<string name="aeap_explanation">Você mudou seu endereço de e-mail de %1$s para %2$s.\n\nSe você agora enviar uma mensagem para um grupo verificado, os contatos lá substituirão automaticamente o antigo por seu novo endereço.\n\nÉ altamente recomendável configurar seu antigo provedor de e-mail para encaminhar todos os e-mails para seu novo endereço de e-mail. Caso contrário, você pode perder mensagens de contatos que ainda não receberam seu novo endereço.</string> <string name="aeap_explanation">Você mudou seu endereço de e-mail de %1$s para %2$s.\n\nSe você agora enviar uma mensagem para um grupo verificado, os contatos lá substituirão automaticamente o antigo por seu novo endereço.\n\nÉ altamente recomendável configurar seu antigo provedor de e-mail para encaminhar todos os e-mails para seu novo endereço de e-mail. Caso contrário, você pode perder mensagens de contatos que ainda não receberam seu novo endereço.</string>
@ -831,10 +831,11 @@
<!-- placeholder will be replaced by the name of the inviter. --> <!-- placeholder will be replaced by the name of the inviter. -->
<string name="secure_join_replies">%1$srespondeu, esperando para ser adicionado ao grupo...</string> <string name="secure_join_replies">%1$srespondeu, esperando para ser adicionado ao grupo...</string>
<string name="contact_verified">%1$s verificado.</string> <string name="contact_verified">%1$s verificado.</string>
<!-- deprecated, was stock string -->
<string name="contact_not_verified">Impossível verificar %1$s</string> <string name="contact_not_verified">Impossível verificar %1$s</string>
<!-- Shown in contact profile. The placeholder will be replaced by the name of the contact that introduced the contact. --> <!-- Shown in contact profile. The placeholder will be replaced by the name of the contact that introduced the contact. -->
<string name="verified_by">Verificado por %1$s</string> <string name="verified_by">Verificado por %1$s</string>
<!-- translators: "setup" is the "encryption setup" here, as in "Autocrypt Setup Message" --> <!-- deprecated, was stock string -->
<string name="contact_setup_changed">A configuração Autocrypt mudou para %1$s</string> <string name="contact_setup_changed">A configuração Autocrypt mudou para %1$s</string>
<string name="mailto_dialog_header_select_chat">Selecione o bate-papo para enviar a mensagem</string> <string name="mailto_dialog_header_select_chat">Selecione o bate-papo para enviar a mensagem</string>
<!-- first placeholder is the name of the chat --> <!-- first placeholder is the name of the chat -->
@ -868,7 +869,7 @@
<string name="ImageEditorHud_flip">Girar</string> <string name="ImageEditorHud_flip">Girar</string>
<string name="ImageEditorHud_rotate">Rodar</string> <string name="ImageEditorHud_rotate">Rodar</string>
<!-- dc_str_* resources --> <!-- deprecated, use string "E-Mail" for non-encrypted messages instead -->
<string name="encrypted_message">Mensagem criptografada</string> <string name="encrypted_message">Mensagem criptografada</string>
<!-- strings introduced on desktop. we want to share strings between the os, in general, please do not add generic strings here --> <!-- strings introduced on desktop. we want to share strings between the os, in general, please do not add generic strings here -->

5
src/main/res/values-pt/strings.xml
View file

@ -329,8 +329,9 @@
<!-- This text is shown inside the "QR code card" with very limited space; please formulate the text as short as possible therefore. The placeholder will be replaced by name and address eg. "Scan to chat with Alice (alice@example.org)" --> <!-- This text is shown inside the "QR code card" with very limited space; please formulate the text as short as possible therefore. The placeholder will be replaced by name and address eg. "Scan to chat with Alice (alice@example.org)" -->
<string name="qrshow_join_contact_hint">Digitalize para configurar um contato com %1$s</string> <string name="qrshow_join_contact_hint">Digitalize para configurar um contato com %1$s</string>
<string name="contact_verified">%1$s verificado.</string> <string name="contact_verified">%1$s verificado.</string>
<!-- deprecated, was stock string -->
<string name="contact_not_verified">Não é possível verificar %1$s</string> <string name="contact_not_verified">Não é possível verificar %1$s</string>
<!-- translators: "setup" is the "encryption setup" here, as in "Autocrypt Setup Message" --> <!-- deprecated, was stock string -->
<string name="contact_setup_changed">Configuração alterada para %1$s</string> <string name="contact_setup_changed">Configuração alterada para %1$s</string>
<!-- notifications --> <!-- notifications -->
<string name="notify_reply_button">Responder</string> <string name="notify_reply_button">Responder</string>
@ -349,7 +350,7 @@
<string name="perm_explain_access_to_mic_denied">O Delta Chat necessita de permissão de acesso ao microfone para enviar mensagens de áudio, mas foi negado. Por favor, continue com as configurações do aplicativo, selecione \"Permissões\" e active \"Microfone\".</string> <string name="perm_explain_access_to_mic_denied">O Delta Chat necessita de permissão de acesso ao microfone para enviar mensagens de áudio, mas foi negado. Por favor, continue com as configurações do aplicativo, selecione \"Permissões\" e active \"Microfone\".</string>
<string name="perm_explain_access_to_storage_denied">O Delta Chat necessita da permissão de armazenamento para anexar ou exportar fotos, vídeos ou áudio, mas foi negado. Por favor, continue no menu de configurações do aplicativo, seleccione \"Permissões\" e active \"Armazenamento\".</string> <string name="perm_explain_access_to_storage_denied">O Delta Chat necessita da permissão de armazenamento para anexar ou exportar fotos, vídeos ou áudio, mas foi negado. Por favor, continue no menu de configurações do aplicativo, seleccione \"Permissões\" e active \"Armazenamento\".</string>
<string name="perm_explain_access_to_location_denied">O Delta Chat necessita permissão de acesso à localização para anexar um local, mas ele negado. Por favor, continue no menu de configurações do aplicativo, selecione \"Permissões \"e ative \"Localização\".</string> <string name="perm_explain_access_to_location_denied">O Delta Chat necessita permissão de acesso à localização para anexar um local, mas ele negado. Por favor, continue no menu de configurações do aplicativo, selecione \"Permissões \"e ative \"Localização\".</string>
<!-- dc_str_* resources --> <!-- deprecated, use string "E-Mail" for non-encrypted messages instead -->
<string name="encrypted_message">Mensagem encriptada</string> <string name="encrypted_message">Mensagem encriptada</string>
<string name="global_menu_preferences_language_desktop">Escolha o seu idioma...</string> <string name="global_menu_preferences_language_desktop">Escolha o seu idioma...</string>

2
src/main/res/values-ro/strings.xml
View file

@ -448,7 +448,7 @@
<string name="tab_all_media_empty_hint">Materialele media partajate în orice chat vor apărea aici.</string> <string name="tab_all_media_empty_hint">Materialele media partajate în orice chat vor apărea aici.</string>
<string name="media_preview">Previzualizare Media</string> <string name="media_preview">Previzualizare Media</string>
<string name="send_message">Trimiteți Mesaj</string> <string name="send_message">Trimiteți Mesaj</string>
<!-- Placeholder %1$s will be replaced by the name of the contact changing their address. Placeholders %2$s and %3$s will be replaced by old/new addresses. --> <!-- deprecated, was stock string -->
<string name="aeap_addr_changed">%1$s și-au schimbat adresa de la %2$s la %3$s</string> <string name="aeap_addr_changed">%1$s și-au schimbat adresa de la %2$s la %3$s</string>
<!-- deprecated --> <!-- deprecated -->
<string name="aeap_explanation">V-ați schimbat adresa de e-mail de la %1$s la %2$s.\n\nDacă trimiteți acum un mesaj către un grup verificat, contactele de acolo vor înlocui automat vechea adresă cu noua dumneavoastră adresă.\n\nSe recomandă să vă configurați vechiul furnizor de e-mail pentru a redirecționa toate e-mailurile către noua dumneavoastră adresă de e-mail. În caz contrar, s-ar putea să pierdeți mesaje ale contactelor care nu au primit încă noua dumneavoastră adresă.</string> <string name="aeap_explanation">V-ați schimbat adresa de e-mail de la %1$s la %2$s.\n\nDacă trimiteți acum un mesaj către un grup verificat, contactele de acolo vor înlocui automat vechea adresă cu noua dumneavoastră adresă.\n\nSe recomandă să vă configurați vechiul furnizor de e-mail pentru a redirecționa toate e-mailurile către noua dumneavoastră adresă de e-mail. În caz contrar, s-ar putea să pierdeți mesaje ale contactelor care nu au primit încă noua dumneavoastră adresă.</string>

48
src/main/res/values-ru/strings.xml
View file

@ -279,6 +279,11 @@
<string name="please_enter_broadcast_list_name">Введите название списка рассылки.</string> <string name="please_enter_broadcast_list_name">Введите название списка рассылки.</string>
<!-- consider keeping the term "channel" as in WhatsApp or Telegram --> <!-- consider keeping the term "channel" as in WhatsApp or Telegram -->
<string name="channel_name">Название канала</string> <string name="channel_name">Название канала</string>
<string name="email">Электронная почта</string>
<!-- "New" as in "Create New E-Mail"; shown together with "New Group" and "New Channel" -->
<string name="new_email">Новое письмо</string>
<!-- the "Subject" of an e-mail, use the term common in classic e-mail apps -->
<string name="subject">Тема</string>
<string name="menu_send">Отправить</string> <string name="menu_send">Отправить</string>
<string name="menu_toggle_keyboard">Эмодзи клавиатура</string> <string name="menu_toggle_keyboard">Эмодзи клавиатура</string>
<string name="menu_edit_group">Редактировать группу</string> <string name="menu_edit_group">Редактировать группу</string>
@ -373,6 +378,7 @@
<!-- Menu item beside an app/chat that adds an icon to the system's home screen. If the user taps that icon, the app/chat is opened directly. --> <!-- Menu item beside an app/chat that adds an icon to the system's home screen. If the user taps that icon, the app/chat is opened directly. -->
<string name="add_to_home_screen">Добавить на главный экран</string> <string name="add_to_home_screen">Добавить на главный экран</string>
<string name="donate">Пожертвовать</string> <string name="donate">Пожертвовать</string>
<string name="donate_device_msg">❤️ Кажется, вам нравится Delta Chat!\n\nРассмотрите возможность сделать пожертвование, чтобы Delta Chat и дальше оставался бесплатным для всех пользователей.\n\nDelta Chat — это бесплатное приложение с открытым исходным кодом, но его разработка требует денег. Поддержите нас, чтобы сохранить независимость Delta Chat и сделать его ещё более крутым в будущем.\n\nhttps://delta.chat/donate</string>
<string name="mute_for_one_hour">На 1 час</string> <string name="mute_for_one_hour">На 1 час</string>
<string name="mute_for_eight_hours">На 8 часов</string> <string name="mute_for_eight_hours">На 8 часов</string>
@ -595,7 +601,7 @@
<!-- option to show images in the gallery as square (instead of using correct width/height) --> <!-- option to show images in the gallery as square (instead of using correct width/height) -->
<string name="square_grid">Сетка квадратов</string> <string name="square_grid">Сетка квадратов</string>
<string name="send_message">Отправить сообщение</string> <string name="send_message">Отправить сообщение</string>
<!-- Placeholder %1$s will be replaced by the name of the contact changing their address. Placeholders %2$s and %3$s will be replaced by old/new addresses. --> <!-- deprecated, was stock string -->
<string name="aeap_addr_changed">%1$s меняет адрес с %2$s на %3$s</string> <string name="aeap_addr_changed">%1$s меняет адрес с %2$s на %3$s</string>
<!-- deprecated --> <!-- deprecated -->
<string name="aeap_explanation">Вы изменили свой адрес электронной почты с %1$s на %2$s.\n\nЕсли вы отправите сообщение в подтвержденную группу, контакты в ней автоматически обновят ваш старый адрес на новый.\n\nНастоятельно рекомендуется настроить старого поставщика электронной почты на пересылку всех писем на новый адрес. Иначе вы можете пропустить сообщения от контактов, которые еще не получили ваш новый адрес.</string> <string name="aeap_explanation">Вы изменили свой адрес электронной почты с %1$s на %2$s.\n\nЕсли вы отправите сообщение в подтвержденную группу, контакты в ней автоматически обновят ваш старый адрес на новый.\n\nНастоятельно рекомендуется настроить старого поставщика электронной почты на пересылку всех писем на новый адрес. Иначе вы можете пропустить сообщения от контактов, которые еще не получили ваш новый адрес.</string>
@ -969,40 +975,42 @@
<!-- %1$s will be replaced by the number of seconds (always >1) the timer is set to --> <!-- %1$s will be replaced by the number of seconds (always >1) the timer is set to -->
<string name="ephemeral_timer_seconds_by_you">Вы включили автоудаление сообщений через %1$s сек</string> <string name="ephemeral_timer_seconds_by_you">Вы включили автоудаление сообщений через %1$s сек</string>
<!-- %1$s will be replaced by the number of seconds (always >1) the timer is set to, %2$s will be replaced by name and address of the contact --> <!-- %1$s will be replaced by the number of seconds (always >1) the timer is set to, %2$s will be replaced by name and address of the contact -->
<string name="ephemeral_timer_seconds_by_other">%2$s включил(а) автоудаление сообщений через %1$s сек</string> <string name="ephemeral_timer_seconds_by_other">%2$s включает автоудаление сообщений через %1$s сек</string>
<string name="ephemeral_timer_1_minute_by_you">Вы включили автоудаление сообщений через 1 минуту.</string> <string name="ephemeral_timer_1_minute_by_you">Вы включили автоудаление сообщений через 1 минуту.</string>
<!-- %1$s will be replaced by name and address of the contact --> <!-- %1$s will be replaced by name and address of the contact -->
<string name="ephemeral_timer_1_minute_by_other">%1$s включил(а) автоудаление сообщений через 1 минуту.</string> <string name="ephemeral_timer_1_minute_by_other">%1$s включает автоудаление сообщений через 1 минуту.</string>
<string name="ephemeral_timer_1_hour_by_you">Вы включили автоудаление сообщений через 1 час.</string> <string name="ephemeral_timer_1_hour_by_you">Вы включили автоудаление сообщений через 1 час.</string>
<!-- %1$s will be replaced by name and address of the contact --> <!-- %1$s will be replaced by name and address of the contact -->
<string name="ephemeral_timer_1_hour_by_other">%1$s включил(а) автоудаление сообщений через 1 час.</string> <string name="ephemeral_timer_1_hour_by_other">%1$s включает автоудаление сообщений через 1 час.</string>
<string name="ephemeral_timer_1_day_by_you">Вы включили автоудаление сообщений через 1 день.</string> <string name="ephemeral_timer_1_day_by_you">Вы включили автоудаление сообщений через 1 день.</string>
<!-- %1$s will be replaced by name and address of the contact --> <!-- %1$s will be replaced by name and address of the contact -->
<string name="ephemeral_timer_1_day_by_other">%1$s включил(а) автоудаление сообщений через 1 день.</string> <string name="ephemeral_timer_1_day_by_other">%1$s включает автоудаление сообщений через 1 день.</string>
<string name="ephemeral_timer_1_week_by_you">Вы включили автоудаление сообщений через 1 неделю.</string> <string name="ephemeral_timer_1_week_by_you">Вы включили автоудаление сообщений через 1 неделю.</string>
<!-- %1$s will be replaced by name and address of the contact --> <!-- %1$s will be replaced by name and address of the contact -->
<string name="ephemeral_timer_1_week_by_other">%1$s включил(а) автоудаление сообщений через 1 неделю.</string> <string name="ephemeral_timer_1_week_by_other">%1$s включает автоудаление сообщений через 1 неделю.</string>
<!-- %1$s will be replaced by the number of minutes (always >1) the timer is set to --> <!-- %1$s will be replaced by the number of minutes (always >1) the timer is set to -->
<string name="ephemeral_timer_minutes_by_you">Вы включили автоудаление сообщений через %1$s минут.</string> <string name="ephemeral_timer_minutes_by_you">Вы включили автоудаление сообщений через %1$s минут.</string>
<!-- %1$s will be replaced by the number of minutes (always >1) the timer is set to, %2$s will be replaced by name and address of the contact --> <!-- %1$s will be replaced by the number of minutes (always >1) the timer is set to, %2$s will be replaced by name and address of the contact -->
<string name="ephemeral_timer_minutes_by_other">%2$s включил(а) автоудаление сообщений через %1$s минут.</string> <string name="ephemeral_timer_minutes_by_other">%2$s включает автоудаление сообщений через %1$s минут.</string>
<!-- %1$s will be replaced by the number of hours (always >1) the timer is set to --> <!-- %1$s will be replaced by the number of hours (always >1) the timer is set to -->
<string name="ephemeral_timer_hours_by_you">Вы включили автоудаление сообщений через %1$s часов.</string> <string name="ephemeral_timer_hours_by_you">Вы включили автоудаление сообщений через %1$s часов.</string>
<!-- %1$s will be replaced by the number of hours (always >1) the timer is set to, %2$s will be replaced by name and address of the contact --> <!-- %1$s will be replaced by the number of hours (always >1) the timer is set to, %2$s will be replaced by name and address of the contact -->
<string name="ephemeral_timer_hours_by_other">%2$s включил(а) автоудаление сообщений через %1$s часов.</string> <string name="ephemeral_timer_hours_by_other">%2$s включает автоудаление сообщений через %1$s часов.</string>
<!-- %1$s will be replaced by the number of days (always >1) the timer is set to --> <!-- %1$s will be replaced by the number of days (always >1) the timer is set to -->
<string name="ephemeral_timer_days_by_you">Вы включили автоудаление сообщений через %1$s дней.</string> <string name="ephemeral_timer_days_by_you">Вы включили автоудаление сообщений через %1$s дней.</string>
<!-- %1$s will be replaced by the number of days (always >1) the timer is set to, %2$s will be replaced by name and address of the contact --> <!-- %1$s will be replaced by the number of days (always >1) the timer is set to, %2$s will be replaced by name and address of the contact -->
<string name="ephemeral_timer_days_by_other">%2$s включил(а) автоудаление сообщений через %1$s дней.</string> <string name="ephemeral_timer_days_by_other">%2$s включает автоудаление сообщений через %1$s дней.</string>
<!-- %1$s will be replaced by the number of weeks (always >1) the timer is set to --> <!-- %1$s will be replaced by the number of weeks (always >1) the timer is set to -->
<string name="ephemeral_timer_weeks_by_you">Вы включили автоудаление сообщений через %1$s недель.</string> <string name="ephemeral_timer_weeks_by_you">Вы включили автоудаление сообщений через %1$s недель.</string>
<!-- %1$s will be replaced by the number of weeks (always >1) the timer is set to, %2$s will be replaced by name and address of the contact --> <!-- %1$s will be replaced by the number of weeks (always >1) the timer is set to, %2$s will be replaced by name and address of the contact -->
<string name="ephemeral_timer_weeks_by_other">%2$s включил(а) автоудаление сообщений через %1$s недель.</string> <string name="ephemeral_timer_weeks_by_other">%2$s включает автоудаление сообщений через %1$s недель.</string>
<!-- this may be shown instead of the chat's input field, with buttons "More Info" and "OK" --> <!-- deprecated -->
<string name="chat_protection_broken">%1$s отправил сообщение с другого устройства.</string> <string name="chat_protection_broken">%1$s отправил сообщение с другого устройства.</string>
<string name="chat_protection_enabled_tap_to_learn_more">Теперь сообщения гарантированно шифруются сквозным шифрованием. Нажмите, чтобы узнать больше.</string> <string name="chat_protection_enabled_tap_to_learn_more">Сообщения защищены сквозным шифрованием. Нажмите, чтобы узнать больше.</string>
<string name="chat_protection_enabled_explanation">Теперь сообщения в этом чате гарантированно шифруются сквозным шифрованием.\n\nСквозное шифрование гарантирует, что сообщения остаются конфиденциальными между вами и вашими собеседниками. Даже ваш провайдер электронной почты не имеет доступа к ним.</string> <string name="chat_protection_enabled_explanation">Все сообщения в этом чате защищены сквозным шифрованием.\n\nСквозное шифрование гарантирует, что сообщения остаются конфиденциальными между вами и вашими собеседниками. Ни серверы, ни провайдеры, ни ретрансляторы не смогут их прочитать.</string>
<!-- deprecated -->
<string name="chat_protection_broken_tap_to_learn_more">%1$s отправил сообщение с другого устройства. Нажмите, чтобы узнать больше.</string> <string name="chat_protection_broken_tap_to_learn_more">%1$s отправил сообщение с другого устройства. Нажмите, чтобы узнать больше.</string>
<!-- deprecated -->
<string name="chat_protection_broken_explanation">Сквозное шифрование больше не может быть гарантировано, вероятно, потому что %1$s переустановил Delta Chat или отправил сообщение с другого устройства.\n\nВы можете встретиться с ним лично и отсканировать QR-код снова чтобы восстановить гарантированное сквозное шифрование.</string> <string name="chat_protection_broken_explanation">Сквозное шифрование больше не может быть гарантировано, вероятно, потому что %1$s переустановил Delta Chat или отправил сообщение с другого устройства.\n\nВы можете встретиться с ним лично и отсканировать QR-код снова чтобы восстановить гарантированное сквозное шифрование.</string>
<string name="invalid_unencrypted_tap_to_learn_more">⚠️ %1$s требуется сквозное шифрование, которое ещё не настроено для данного чата. Нажмите, чтобы узнать больше.</string> <string name="invalid_unencrypted_tap_to_learn_more">⚠️ %1$s требуется сквозное шифрование, которое ещё не настроено для данного чата. Нажмите, чтобы узнать больше.</string>
<string name="invalid_unencrypted_explanation">Чтобы установить сквозное шифрование, вы можете встретиться с контактами лично и отсканировать их QR-код, чтобы подтвердить их личность.</string> <string name="invalid_unencrypted_explanation">Чтобы установить сквозное шифрование, вы можете встретиться с контактами лично и отсканировать их QR-код, чтобы подтвердить их личность.</string>
@ -1061,16 +1069,19 @@
<string name="secure_join_started">%1$s приглашает вас в группу.\n\nОжидаем ответ от %2$s…</string> <string name="secure_join_started">%1$s приглашает вас в группу.\n\nОжидаем ответ от %2$s…</string>
<!-- placeholder will be replaced by the name of the inviter. --> <!-- placeholder will be replaced by the name of the inviter. -->
<string name="secure_join_replies">%1$s ответил(а), ожидаем добавления в группу…</string> <string name="secure_join_replies">%1$s ответил(а), ожидаем добавления в группу…</string>
<string name="secure_join_wait">Устанавливается гарантированное сквозное шифрование, пожалуйста, подождите...</string> <string name="secure_join_wait">Устанавливается сквозное шифрование, пожалуйста, подождите…</string>
<!-- deprecated --> <!-- deprecated -->
<string name="secure_join_wait_timeout">Не удалось установить гарантированное сквозное шифрование, но вы уже можете отправить сообщение.</string> <string name="secure_join_wait_timeout">Не удалось установить гарантированное сквозное шифрование, но вы уже можете отправить сообщение.</string>
<!-- deprecated, was stock string -->
<string name="secure_join_takes_longer">Контакт должен быть в режиме онлайн, чтобы продолжить.\n\nЭтот процесс будет автоматически продолжен в фоновом режиме.</string> <string name="secure_join_takes_longer">Контакт должен быть в режиме онлайн, чтобы продолжить.\n\nЭтот процесс будет автоматически продолжен в фоновом режиме.</string>
<string name="contact_verified">%1$s подтверждён.</string> <string name="contact_verified">%1$s подтверждён.</string>
<string name="contact_not_verified">Невозможно установить гарантированное сквозное шифрование с %1$s.</string> <!-- deprecated, was stock string -->
<string name="contact_not_verified">Невозможно установить сквозное шифрование с %1$s.</string>
<!-- Shown in contact profile. The placeholder will be replaced by the name of the contact that introduced the contact. --> <!-- Shown in contact profile. The placeholder will be replaced by the name of the contact that introduced the contact. -->
<string name="verified_by">Подтверждён: %1$s</string> <string name="verified_by">Подтверждён: %1$s</string>
<string name="verified_by_you">Подтверждён: Лично</string> <string name="verified_by_you">Подтверждён: Лично</string>
<!-- translators: "setup" is the "encryption setup" here, as in "Autocrypt Setup Message" --> <string name="verified_by_unknown">Подтверждён</string>
<!-- deprecated, was stock string -->
<string name="contact_setup_changed">Изменены настройки для %1$s</string> <string name="contact_setup_changed">Изменены настройки для %1$s</string>
<string name="verified_contact_required_explain">Чтобы обеспечить сквозное шифрование, вы можете добавлять в эту группу только контакты с зеленой галочкой.\n\nВы можете встретиться с контактами лично и отсканировать их QR-код, чтобы подтвердить их личность.</string> <string name="verified_contact_required_explain">Чтобы обеспечить сквозное шифрование, вы можете добавлять в эту группу только контакты с зеленой галочкой.\n\nВы можете встретиться с контактами лично и отсканировать их QR-код, чтобы подтвердить их личность.</string>
<string name="mailto_dialog_header_select_chat">Выберите чат, чтобы отправить сообщение</string> <string name="mailto_dialog_header_select_chat">Выберите чат, чтобы отправить сообщение</string>
@ -1114,7 +1125,7 @@
<string name="ImageEditorHud_flip">Отразить</string> <string name="ImageEditorHud_flip">Отразить</string>
<string name="ImageEditorHud_rotate">Вращать</string> <string name="ImageEditorHud_rotate">Вращать</string>
<!-- dc_str_* resources --> <!-- deprecated, use string "E-Mail" for non-encrypted messages instead -->
<string name="encrypted_message">Зашифрованное сообщение</string> <string name="encrypted_message">Зашифрованное сообщение</string>
<!-- strings introduced on desktop. we want to share strings between the os, in general, please do not add generic strings here --> <!-- strings introduced on desktop. we want to share strings between the os, in general, please do not add generic strings here -->
@ -1245,6 +1256,9 @@
<string name="perm_enable_bg_already_done">Вы уже разрешили Delta Chat получать сообщения в фоновом режиме.\n\nЕсли сообщения не приходят в фоновом режиме, проверьте также системные настройки.</string> <string name="perm_enable_bg_already_done">Вы уже разрешили Delta Chat получать сообщения в фоновом режиме.\n\nЕсли сообщения не приходят в фоновом режиме, проверьте также системные настройки.</string>
<!-- device messages for updates --> <!-- device messages for updates -->
<string name="update_2_0">Что нового?\n\n💯 Сквозное шифрование стало постоянной и надёжной функцией. 🔒 Замков больше нет!\n\n✉️ Обычные письма без сквозного шифрования помечены значком конверта\n\n😻 Обновлённый экран профиля для всех контактов\n\n🔲 Новая кнопка быстрого доступа к приложениям, используемым в чате\n\n❤️ Поддержите нас финансово, чтобы мы сохранили независимость и продолжали вносить улучшения: %1$s</string>
<!-- deprecated -->
<string name="update_1_50_android">Что нового?\n\n❤️‍🔥 Обновленный выбор эмодзи с еще большим выбором эмодзи\n\n🎮 Расширенные приложения в чате: получайте уведомления и открывайте поддерживаемые приложения в нужном контексте, например, открывайте добавленную запись в календаре напрямую\n\n👍 Получайте уведомления о реакциях на ваши сообщения\n\n... 🛠️ ИСПРАВЛЕНИЯ и ЕЩЁ БОЛЬШЕ в %1$s</string> <string name="update_1_50_android">Что нового?\n\n❤️‍🔥 Обновленный выбор эмодзи с еще большим выбором эмодзи\n\n🎮 Расширенные приложения в чате: получайте уведомления и открывайте поддерживаемые приложения в нужном контексте, например, открывайте добавленную запись в календаре напрямую\n\n👍 Получайте уведомления о реакциях на ваши сообщения\n\n... 🛠️ ИСПРАВЛЕНИЯ и ЕЩЁ БОЛЬШЕ в %1$s</string>
<!-- deprecated -->
<string name="update_switch_profile_placement">ℹ️ \"Сменить профиль\" перемещено: Нажмите на изображение вашего профиля в верхнем углу главного экрана, чтобы добавить или переключить профили. 💡</string> <string name="update_switch_profile_placement">ℹ️ \"Сменить профиль\" перемещено: Нажмите на изображение вашего профиля в верхнем углу главного экрана, чтобы добавить или переключить профили. 💡</string>
</resources> </resources>

226
src/main/res/values-sk/strings.xml
View file

@ -5,6 +5,10 @@
<string name="ok">OK</string> <string name="ok">OK</string>
<string name="cancel">Zrušiť</string> <string name="cancel">Zrušiť</string>
<string name="clear_search">Zrušiť hľadanie</string> <string name="clear_search">Zrušiť hľadanie</string>
<!-- a noun, used on a button, short for "show link" -->
<string name="link">Odkaz</string>
<!-- "scan" in the meaning of "scan QR code" -->
<string name="scan">Skenovať</string>
<string name="yes">Áno</string> <string name="yes">Áno</string>
<string name="no">Nie</string> <string name="no">Nie</string>
<string name="select">Vybrať</string> <string name="select">Vybrať</string>
@ -24,15 +28,24 @@
<string name="join">Spojiť</string> <string name="join">Spojiť</string>
<string name="rejoin">Znovu spojiť</string> <string name="rejoin">Znovu spojiť</string>
<string name="delete">Odstrániť</string> <string name="delete">Odstrániť</string>
<string name="delete_for_me">Odstrániť pre mňa</string>
<string name="delete_for_everyone">Odstrániť pre všetkých</string>
<string name="info">Informácia</string> <string name="info">Informácia</string>
<string name="update">Aktualizovať</string> <string name="update">Aktualizovať</string>
<string name="emoji">Smajlíci</string> <string name="emoji">Smajlíci</string>
<string name="attachment">Príloha</string> <string name="attachment">Príloha</string>
<!-- the placeholder will be replaced by the name of the image or file to attach -->
<string name="ask_attach">Priložiť „%1$s“?</string>
<string name="back">Späť</string> <string name="back">Späť</string>
<string name="close">Zatvoriť</string> <string name="close">Zatvoriť</string>
<string name="close_window">Zavrieť okno</string>
<string name="forward">Vpred</string> <string name="forward">Vpred</string>
<string name="create">Vytvoriť</string>
<string name="later">Neskôr</string>
<!-- "Resend" means "Sending the selected message(s) again to the same chat". The string is used in a menu and should be as short as possible. Resending may be needed after failures or to repost old messages to new members. --> <!-- "Resend" means "Sending the selected message(s) again to the same chat". The string is used in a menu and should be as short as possible. Resending may be needed after failures or to repost old messages to new members. -->
<string name="resend">Znovu poslať</string> <string name="resend">Znovu poslať</string>
<string name="edited">Upravená</string>
<string name="edit_message">Upraviť správu</string>
<!-- Verb "to archive", as in "put a chat in the archive", not a noun "The Archive". --> <!-- Verb "to archive", as in "put a chat in the archive", not a noun "The Archive". -->
<string name="archive">Archivovať</string> <string name="archive">Archivovať</string>
<!-- Verb "to unarchive", as in "remove a chat from the archive", opposite of the previous string --> <!-- Verb "to unarchive", as in "remove a chat from the archive", opposite of the previous string -->
@ -43,10 +56,18 @@
<string name="save">Uložiť</string> <string name="save">Uložiť</string>
<string name="chat">Konverzácia</string> <string name="chat">Konverzácia</string>
<string name="media">Médiá</string> <string name="media">Médiá</string>
<string name="profile">Profil</string> <string name="apps_and_media">Aplikácie a médiá</string>
<string name="profile">Účet</string>
<string name="all_profiles">Všetky účty</string>
<string name="current_profile">Aktuálny účet</string>
<string name="main_menu">Hlavné menu</string> <string name="main_menu">Hlavné menu</string>
<string name="start_chat">Začať konverzáciu</string> <string name="start_chat">Začať konverzáciu</string>
<string name="show_full_message">Zobraziť celú správu ...</string> <string name="show_full_message">Zobraziť celú správu ...</string>
<!-- Stay short here, say ~16 characters. The source string could also be "All Read", maybe that hint can make translations easier :) -->
<string name="mark_all_as_read">Všetko prečítané</string>
<string name="mark_as_read">Označiť ako prečítané</string>
<!-- Shortest text for "Mark as being read". In english, this could be "Read" (past tense of "to read"), in german, this could be "Gelesen". -->
<string name="mark_as_read_short">Prečítané</string>
<!-- Placeholder text when something is loading --> <!-- Placeholder text when something is loading -->
<string name="loading">Načítam…</string> <string name="loading">Načítam…</string>
<string name="hide">Skryť</string> <string name="hide">Skryť</string>
@ -56,6 +77,7 @@
<string name="load_remote_content_ask">Na sledovanie vás možno použiť obrázky nadiaľku.\n\nToto nastavenie tiež umožňuje načítať písma a ďalší obsah. Aj keď je vypnutá, stále sa vám môžu zobrazovať vložené alebo uložené obrázky.\n\nNačítať vzdialené obrázky?</string> <string name="load_remote_content_ask">Na sledovanie vás možno použiť obrázky nadiaľku.\n\nToto nastavenie tiež umožňuje načítať písma a ďalší obsah. Aj keď je vypnutá, stále sa vám môžu zobrazovať vložené alebo uložené obrázky.\n\nNačítať vzdialené obrázky?</string>
<string name="always">Vždy</string> <string name="always">Vždy</string>
<string name="once">Raz</string> <string name="once">Raz</string>
<string name="show_warning">Zobraziť varovanie</string>
<string name="show_password">Ukáž heslo</string> <string name="show_password">Ukáž heslo</string>
<string name="hide_password">Skryť heslo</string> <string name="hide_password">Skryť heslo</string>
<string name="not_now">Teraz nie</string> <string name="not_now">Teraz nie</string>
@ -71,9 +93,11 @@
<string name="no_app_to_handle_data">Nemôžem nájsť aplikáciu na spracovanie tohto typu údajov.</string> <string name="no_app_to_handle_data">Nemôžem nájsť aplikáciu na spracovanie tohto typu údajov.</string>
<string name="no_browser_installed">Nie je nainštalovaný žiadny prehliadač.</string> <string name="no_browser_installed">Nie je nainštalovaný žiadny prehliadač.</string>
<string name="file_not_found">Nemohol nájsť %1$s.</string> <string name="file_not_found">Nemohol nájsť %1$s.</string>
<!-- the placeholder will be replaced by the name of a file -->
<string name="cannot_save_file">Nepodarilo sa uložiť %1$s.</string>
<string name="copied_to_clipboard">Skopírované do schránky.</string> <string name="copied_to_clipboard">Skopírované do schránky.</string>
<string name="contacts_headline">Kontakty</string> <string name="contacts_headline">Kontakty</string>
<string name="email_address">Emailová adresa</string> <string name="email_address">E-mailová adresa</string>
<string name="bad_email_address">Zlá e-mailová adresa</string> <string name="bad_email_address">Zlá e-mailová adresa</string>
<string name="password">Heslo</string> <string name="password">Heslo</string>
<string name="existing_password">Existujúce heslo</string> <string name="existing_password">Existujúce heslo</string>
@ -88,6 +112,8 @@
<string name="last_month">Minulý mesiac</string> <string name="last_month">Minulý mesiac</string>
<!-- Refers to the time a contact was last seen. Shown below contact name in the profile. The placeholder will be replaced by date or time, resulting in "Last seen at 12:13 AM" or "Last seen Nov 12" --> <!-- Refers to the time a contact was last seen. Shown below contact name in the profile. The placeholder will be replaced by date or time, resulting in "Last seen at 12:13 AM" or "Last seen Nov 12" -->
<string name="last_seen_at">Naposledy videné o%1$s</string> <string name="last_seen_at">Naposledy videné o%1$s</string>
<!-- Refers to the time a contact was last seen. Shown below contact name in the profile. The placeholder will be replaced by a relative point in time as "3 minutes ago" (see https://momentjs.com for more examples and languages)-->
<string name="last_seen_relative">Naposledy online %1$s</string>
<string name="last_seen_unknown">Naposledy videné: Neznáme</string> <string name="last_seen_unknown">Naposledy videné: Neznáme</string>
<!-- Shown beside messages that are "N minutes old". Prefer short strings, or well-known abbreviations. --> <!-- Shown beside messages that are "N minutes old". Prefer short strings, or well-known abbreviations. -->
<plurals name="n_minutes"> <plurals name="n_minutes">
@ -121,6 +147,12 @@
<item quantity="many">%d správy</item> <item quantity="many">%d správy</item>
<item quantity="other">%d správa</item> <item quantity="other">%d správa</item>
</plurals> </plurals>
<plurals name="n_reactions">
<item quantity="one">%d reakcia</item>
<item quantity="few">%d reakcie</item>
<item quantity="many">%d reakcií</item>
<item quantity="other">%d reakcií</item>
</plurals>
<plurals name="n_members"> <plurals name="n_members">
<item quantity="one">%d používateľ</item> <item quantity="one">%d používateľ</item>
<item quantity="few">%d používatelia</item> <item quantity="few">%d používatelia</item>
@ -140,6 +172,7 @@
<item quantity="many">%d vybraných</item> <item quantity="many">%d vybraných</item>
<item quantity="other">%d vybraných</item> <item quantity="other">%d vybraných</item>
</plurals> </plurals>
<string name="selected_colon">Vybrané:</string>
<string name="self">Ja</string> <string name="self">Ja</string>
<string name="draft">Návrh</string> <string name="draft">Návrh</string>
<string name="image">Obrázok</string> <string name="image">Obrázok</string>
@ -148,6 +181,9 @@
<string name="gif">Gif</string> <string name="gif">Gif</string>
<!-- "Stickers" as known from other messengers; in some languages, the English "Sticker" is fine. --> <!-- "Stickers" as known from other messengers; in some languages, the English "Sticker" is fine. -->
<string name="sticker">Nálepka</string> <string name="sticker">Nálepka</string>
<string name="add_to_sticker_collection">Pridať do zbierky nálepiek</string>
<string name="add_stickers_instructions">Pre pridanie nálepiek, ťuknite na \"Otvoriť priečinok s nálepkami\", vytvorte priečinok pre svoju sadu nálepiek a prekopírujte doň nálepky</string>
<string name="open_sticker_folder">Otvoriť priečinok s nálepkami</string>
<string name="images">Snímky</string> <string name="images">Snímky</string>
<string name="audio">Zvuk</string> <string name="audio">Zvuk</string>
<string name="voice_message">Hlasová správa</string> <string name="voice_message">Hlasová správa</string>
@ -158,6 +194,7 @@
<string name="video">Video</string> <string name="video">Video</string>
<string name="documents">Dokumenty</string> <string name="documents">Dokumenty</string>
<string name="contact">Kontakt</string> <string name="contact">Kontakt</string>
<string name="bot">Bot</string>
<string name="camera">Fotoaparát</string> <string name="camera">Fotoaparát</string>
<!-- As in "start a video recording" or "take a photo"; eg. the description of the "shutter button" in cameras --> <!-- As in "start a video recording" or "take a photo"; eg. the description of the "shutter button" in cameras -->
<string name="capture">Zachytiť</string> <string name="capture">Zachytiť</string>
@ -168,10 +205,18 @@
<string name="images_and_videos">Obrázky a videá</string> <string name="images_and_videos">Obrázky a videá</string>
<string name="file">Súbor</string> <string name="file">Súbor</string>
<string name="files">Súbory</string> <string name="files">Súbory</string>
<!-- "Files" here means the "Files Selector App" or "Files Manager App" -->
<string name="choose_from_files">Vybrať zo súborov</string>
<string name="choose_from_gallery">Vybrať z galérie</string>
<!-- "App" is used to present "Webxdc App" (https://webxdc.org) in a user friendly way. Please stay close to the original term and keep it short (it is used in menus with few screen space). --> <!-- "App" is used to present "Webxdc App" (https://webxdc.org) in a user friendly way. Please stay close to the original term and keep it short (it is used in menus with few screen space). -->
<string name="webxdc_app">Súkromná aplikácia</string> <string name="webxdc_app">Súkromná aplikácia</string>
<!-- plural of "App"; used to present "Webxdc App" (https://webxdc.org) in a user friendly way. Please stay close to the original term and keep it short (it is used in menus with few screen space). --> <!-- plural of "App"; used to present "Webxdc App" (https://webxdc.org) in a user friendly way. Please stay close to the original term and keep it short (it is used in menus with few screen space). -->
<string name="webxdc_apps">Súkromné aplikácie</string> <string name="webxdc_apps">Súkromné aplikácie</string>
<string name="home">Domov</string>
<string name="games">Hry</string>
<string name="tools">Nástroje</string>
<string name="app_size">Veľkosť</string>
<string name="add_to_chat">Pridať do konverzácie</string>
<string name="unknown">Neznáme</string> <string name="unknown">Neznáme</string>
<string name="green">Zelená</string> <string name="green">Zelená</string>
@ -195,15 +240,30 @@
<!-- menu labels (or icon, buttons...) --> <!-- menu labels (or icon, buttons...) -->
<string name="menu_new_contact">Nový kontakt</string> <string name="menu_new_contact">Nový kontakt</string>
<string name="menu_new_classic_contact">Pridať kontakt ručne</string>
<string name="menu_new_chat">Nová konverzácia</string> <string name="menu_new_chat">Nová konverzácia</string>
<string name="menu_new_group">Nová skupina</string> <string name="menu_new_group">Nová skupina</string>
<string name="clone_chat">Kopírovať konverzáciu</string>
<!-- deprecated --> <!-- deprecated -->
<string name="broadcast_list">Zoznam Rozosielania</string> <string name="broadcast_list">Zoznam Rozosielania</string>
<!-- deprecated --> <!-- deprecated -->
<string name="broadcast_lists">Zoznamy Rozosielania</string> <string name="broadcast_lists">Zoznamy Rozosielania</string>
<!-- deprecated --> <!-- deprecated -->
<string name="new_broadcast_list">Nový Zoznam Rozosielania</string> <string name="new_broadcast_list">Nový Zoznam Rozosielania</string>
<!-- consider keeping the term "channel" as in WhatsApp or Telegram -->
<string name="channel">Kanál</string>
<!-- consider keeping the term "channel" as in WhatsApp or Telegram -->
<string name="channels">Kanály</string>
<!-- consider keeping the term "channel" as in WhatsApp or Telegram -->
<string name="new_channel">Nový kanál</string>
<string name="add_recipients">Pridať Príjemcov</string> <string name="add_recipients">Pridať Príjemcov</string>
<!-- consider keeping the term "channel" as in WhatsApp or Telegram -->
<string name="channel_name">Názov kanálu</string>
<string name="email">E-mail</string>
<!-- "New" as in "Create New E-Mail"; shown together with "New Group" and "New Channel" -->
<string name="new_email">Nový e-mail</string>
<!-- the "Subject" of an e-mail, use the term common in classic e-mail apps -->
<string name="subject">Predmet</string>
<string name="menu_send">Poslať</string> <string name="menu_send">Poslať</string>
<string name="menu_toggle_keyboard">Prepnúť klávesnicu emodži</string> <string name="menu_toggle_keyboard">Prepnúť klávesnicu emodži</string>
<string name="menu_edit_group">Upraviť skupinu</string> <string name="menu_edit_group">Upraviť skupinu</string>
@ -213,17 +273,25 @@
<string name="menu_unarchive_chat">Zrušiť archiváciu konverzácie</string> <string name="menu_unarchive_chat">Zrušiť archiváciu konverzácie</string>
<string name="menu_add_attachment">Pridať prílohu</string> <string name="menu_add_attachment">Pridať prílohu</string>
<string name="menu_leave_group">Opustiť skupinu</string> <string name="menu_leave_group">Opustiť skupinu</string>
<string name="menu_leave_channel">Opustiť kanál</string>
<string name="menu_delete_chat">Odstrániť konverzáciu</string> <string name="menu_delete_chat">Odstrániť konverzáciu</string>
<!-- Command to delete all messages in a chat. The chat itself will not be deleted but will be empty afterwards, so make sure to be different from "Delete Chat" here. "Clear" is a verb here, "Empty Chat" would also be fine (eg. in German "Chat leeren") -->
<string name="clear_chat">Vyčistiť konverzáciu</string>
<string name="delete_contact">Odstrániť kontakt</string> <string name="delete_contact">Odstrániť kontakt</string>
<string name="menu_delete_location">Odstrániť toto miesto?</string> <string name="menu_delete_location">Odstrániť toto miesto?</string>
<string name="menu_message_details">Podrobnosti správy</string> <string name="menu_message_details">Podrobnosti správy</string>
<string name="menu_copy_to_clipboard">Skopírovať do schránky</string> <string name="menu_copy_to_clipboard">Skopírovať do schránky</string>
<string name="invite_friends">Pozvať priateľov</string>
<!-- %1$s is replaced by the user's invitation link ("https://i.delta.chat/...") -->
<string name="invite_friends_text">Kontaktujte ma na Delta Chat:
%1$s</string>
<string name="menu_copy_selection_to_clipboard">Kopírovať výber</string> <string name="menu_copy_selection_to_clipboard">Kopírovať výber</string>
<string name="menu_copy_link_to_clipboard">Skopírovať odkaz</string> <string name="menu_copy_link_to_clipboard">Skopírovať odkaz</string>
<string name="menu_copy_text_to_clipboard">Kopírovať text</string> <string name="menu_copy_text_to_clipboard">Kopírovať text</string>
<string name="menu_copy_image_to_clipboard">Kopírovať obrázok</string> <string name="menu_copy_image_to_clipboard">Kopírovať obrázok</string>
<string name="menu_copy_email_to_clipboard">Kopírovať E-Mail</string> <string name="menu_copy_email_to_clipboard">Kopírovať e-mail</string>
<string name="paste_from_clipboard">Prilepiť zo schránky</string> <string name="paste_from_clipboard">Prilepiť zo schránky</string>
<string name="ask_copy_unopenable_link_to_clipboard">Odkaz \"%1$d\" nie je možné otvoriť vo webovom prehliadači. Chcete ho skopírovať do schránky?</string>
<string name="menu_forward">Preposlať správu</string> <string name="menu_forward">Preposlať správu</string>
<string name="menu_reply">Odpovedať na správu</string> <string name="menu_reply">Odpovedať na správu</string>
<string name="menu_mute">Ignorovať upozornenia</string> <string name="menu_mute">Ignorovať upozornenia</string>
@ -231,8 +299,10 @@
<string name="menu_export_attachment">Exportovať prílohu</string> <string name="menu_export_attachment">Exportovať prílohu</string>
<string name="menu_export_attachments">Exportovať príloh</string> <string name="menu_export_attachments">Exportovať príloh</string>
<string name="menu_all_media">Všetky médiá</string> <string name="menu_all_media">Všetky médiá</string>
<string name="all_apps_and_media">Všetky aplikácie a médiá</string>
<!-- Command to jump to the original message corresponding to a gallery image or document --> <!-- Command to jump to the original message corresponding to a gallery image or document -->
<string name="show_in_chat">Zobraziť v konverzácií</string> <string name="show_in_chat">Zobraziť v konverzácií</string>
<string name="show_app_in_chat">Zobraziť aplikáciu v konverzácii</string>
<string name="menu_share">Zdieľam</string> <string name="menu_share">Zdieľam</string>
<!-- Verb "to block sth." usually a mailing list or a contact, not a noun --> <!-- Verb "to block sth." usually a mailing list or a contact, not a noun -->
<string name="block">Blokovať</string> <string name="block">Blokovať</string>
@ -244,13 +314,19 @@
<string name="menu_scroll_to_bottom">Posuňte sa nadol</string> <string name="menu_scroll_to_bottom">Posuňte sa nadol</string>
<string name="menu_scroll_to_top">Prejdite hore</string> <string name="menu_scroll_to_top">Prejdite hore</string>
<string name="menu_help">Pomocník</string> <string name="menu_help">Pomocník</string>
<string name="what_is_webxdc">Čo je Webxdc?</string>
<string name="privacy_policy">Zásady súkromia</string> <string name="privacy_policy">Zásady súkromia</string>
<string name="menu_select_all">Vybrať všetko</string> <string name="menu_select_all">Vybrať všetko</string>
<string name="select_chat">Vybrať konverzáciu</string>
<string name="select_more">Vyberte viac</string> <string name="select_more">Vyberte viac</string>
<string name="menu_edit_name">Upraviť meno</string> <string name="menu_edit_name">Upraviť meno</string>
<!-- The placeholder will be replaced by the name the contact gave themself -->
<string name="edit_name_explain">Nastavte prezývku, ktorá sa vám bude zobrazovať miesto \"%1$s\". Ak neuvediete prezývku, použije sa meno kontaktu.</string>
<!-- The placeholder will be replaced by the name the contact gave themself -->
<string name="edit_name_placeholder">Prezývka pre \"%1$s\"</string>
<string name="menu_settings">Nastavenia</string> <string name="menu_settings">Nastavenia</string>
<string name="menu_advanced">Pokročilé</string> <string name="menu_advanced">Pokročilé</string>
<string name="menu_view_profile">Prezrieť profil</string> <string name="menu_view_profile">Zobraziť účet</string>
<string name="menu_zoom_in">Priblížiť</string> <string name="menu_zoom_in">Priblížiť</string>
<string name="menu_zoom_out">Oddialiť</string> <string name="menu_zoom_out">Oddialiť</string>
<string name="menu_save_log">Uložiť záznam</string> <string name="menu_save_log">Uložiť záznam</string>
@ -258,6 +334,7 @@
<string name="menu_learn_spelling">Naučiť sa pravopis</string> <string name="menu_learn_spelling">Naučiť sa pravopis</string>
<string name="menu_chat_audit_log">Auditovací protokol konverzácie</string> <string name="menu_chat_audit_log">Auditovací protokol konverzácie</string>
<string name="jump_to_message">Prejsť na správu</string> <string name="jump_to_message">Prejsť na správu</string>
<string name="jump_to_original_message">Zobraziť pôvodnú správu</string>
<string name="copy_json">Kopírovať JSON</string> <string name="copy_json">Kopírovať JSON</string>
<string name="replace_draft">Nahradiť koncept</string> <string name="replace_draft">Nahradiť koncept</string>
<string name="title_share_location">Zdieľať polohu so všetkými členmi skupiny</string> <string name="title_share_location">Zdieľať polohu so všetkými členmi skupiny</string>
@ -278,6 +355,7 @@
<string name="source_code">Zdrojový kód</string> <string name="source_code">Zdrojový kód</string>
<!-- Menu item beside an app/chat that adds an icon to the system's home screen. If the user taps that icon, the app/chat is opened directly. --> <!-- Menu item beside an app/chat that adds an icon to the system's home screen. If the user taps that icon, the app/chat is opened directly. -->
<string name="add_to_home_screen">Pridať na domovskú obrazovku</string> <string name="add_to_home_screen">Pridať na domovskú obrazovku</string>
<string name="donate">Prispieť</string>
<string name="mute_for_one_hour">Stíšiť na 1 hodinu</string> <string name="mute_for_one_hour">Stíšiť na 1 hodinu</string>
<string name="mute_for_eight_hours">Stíšiť na 8 hodiny</string> <string name="mute_for_eight_hours">Stíšiť na 8 hodiny</string>
<string name="mute_for_one_day">Stíšiť na 1 deň</string> <string name="mute_for_one_day">Stíšiť na 1 deň</string>
@ -314,6 +392,20 @@
<string name="videochat_invitation">Pozvánka na videohovor</string> <string name="videochat_invitation">Pozvánka na videohovor</string>
<string name="videochat_invitation_body">Ste pozvaní na videohovor, kliknutím %1$s sa pripojíte.</string> <string name="videochat_invitation_body">Ste pozvaní na videohovor, kliknutím %1$s sa pripojíte.</string>
<plurals name="ask_delete_chat">
<item quantity="one">Odstrániť %d konverzáciu zo všetkých vašich zariadení?</item>
<item quantity="few">Odstrániť %d konverzácie zo všetkých vašich zariadení?</item>
<item quantity="many">Odstrániť %d konverzácii zo všetkých vašich zariadení?</item>
<item quantity="other">Odstrániť %d konverzácii zo všetkých vašich zariadení?</item>
</plurals>
<string name="ask_delete_named_chat">Odstrániť konverzáciu \"%1$s\" zo všetkých vašich zariadení?</string>
<string name="ask_delete_message">Odstrániť túto správu zo všetkých vašich zariadení?</string>
<plurals name="ask_delete_messages">
<item quantity="one">Odstrániť %d správu zo všetkých vašich zariadení?</item>
<item quantity="few">Odstrániť %d správy zo všetkých vašich zariadení?</item>
<item quantity="many">Odstrániť %d správ zo všetkých vašich zariadení?</item>
<item quantity="other">Odstrániť %d správ zo všetkých vašich zariadení?</item>
</plurals>
<!-- Used for the deletion of Device messages --> <!-- Used for the deletion of Device messages -->
<plurals name="ask_delete_messages_simple"> <plurals name="ask_delete_messages_simple">
<item quantity="one">Odstrániť %d správu?</item> <item quantity="one">Odstrániť %d správu?</item>
@ -333,6 +425,8 @@
<string name="ask_remove_members">Odstrániť %1$s zo skupiny?</string> <string name="ask_remove_members">Odstrániť %1$s zo skupiny?</string>
<!-- deprecated --> <!-- deprecated -->
<string name="ask_remove_from_broadcast">Odstrániť %1$s zo zoznamu rozosielania?</string> <string name="ask_remove_from_broadcast">Odstrániť %1$s zo zoznamu rozosielania?</string>
<!-- %1$s is replaced by a comma-separated list of names -->
<string name="ask_remove_from_channel">Odstrániť %1$s z kanálu?</string>
<string name="open_url_confirmation">Chcete otvoriť tento odkaz?</string> <string name="open_url_confirmation">Chcete otvoriť tento odkaz?</string>
@ -403,6 +497,10 @@
<string name="start_app">Spustiť...</string> <string name="start_app">Spustiť...</string>
<!-- this is a warning that is shown when one tries to send something to a chat that is not yet accepted. --> <!-- this is a warning that is shown when one tries to send something to a chat that is not yet accepted. -->
<string name="accept_request_first">Prosím, najprv prijmite požiadavku na konverzáciu.</string> <string name="accept_request_first">Prosím, najprv prijmite požiadavku na konverzáciu.</string>
<!-- title shown above a list of chats where one should be selected (eg. when sharing files from a webxdc). the placeholder will be replaced by a file name -->
<string name="send_file_to">Poslať \"%1$s\"...</string>
<!-- title shown above a list contacts where one should be selected (eg. when a webxdc attempts to send a message to a chat) -->
<string name="send_message_to">Poslať správu...</string>
<!-- map --> <!-- map -->
<string name="filter_map_on_time">Zobraziť polohy v časovom rámci</string> <string name="filter_map_on_time">Zobraziť polohy v časovom rámci</string>
<string name="show_location_traces">Zobraziť stopy</string> <string name="show_location_traces">Zobraziť stopy</string>
@ -425,8 +523,14 @@
<!-- search --> <!-- search -->
<string name="search">Vyhľadávanie</string> <string name="search">Vyhľadávanie</string>
<string name="search_in_chat">Hľadať v konverzácii</string>
<string name="search_files">Hľadať súbory</string>
<string name="search_explain">Vyhľadajte konverzácie, kontakty a správy</string> <string name="search_explain">Vyhľadajte konverzácie, kontakty a správy</string>
<string name="search_no_result_for_x">Neboli nájdené žiadne výsledky pre \"%s\"</string> <string name="search_no_result_for_x">Neboli nájdené žiadne výsledky pre \"%s\"</string>
<!-- Adjective, as in "Show Unread Messages" -->
<string name="search_unread">Neprečítané</string>
<!-- create/edit groups, contact/group profile --> <!-- create/edit groups, contact/group profile -->
<string name="group_name">Názov skupiny</string> <string name="group_name">Názov skupiny</string>
<string name="group_avatar">Obrázok skupiny</string> <string name="group_avatar">Obrázok skupiny</string>
@ -452,8 +556,31 @@
<string name="tab_webxdc_empty_hint">Tu sú zobrazené súkromné aplikácie zdieľané v rámci tejto konverzácie.</string> <string name="tab_webxdc_empty_hint">Tu sú zobrazené súkromné aplikácie zdieľané v rámci tejto konverzácie.</string>
<string name="media_preview">Ukážka pre médiá</string> <string name="media_preview">Ukážka pre médiá</string>
<string name="send_message">Odoslanie správy</string> <string name="send_message">Odoslanie správy</string>
<!-- Placeholder %1$s will be replaced by the name of the contact changing their address. Placeholders %2$s and %3$s will be replaced by old/new addresses. --> <!-- deprecated, was stock string -->
<string name="aeap_addr_changed">%1$s zmenil(a) svoju adresu z %2$s na %3$s</string> <string name="aeap_addr_changed">%1$s zmenil(a) svoju adresu z %2$s na %3$s</string>
<!-- Multi Device -->
<!-- "Second Device" can also be translated as "Another Device", if that is catchier in the destination language. However, make sure to use the term consistently. -->
<string name="multidevice_title">Pridať ďalšie zariadenie</string>
<string name="multidevice_same_network_hint">Uistite sa, že obe zariadenia sú na rovnakej Wi-Fi sieti.</string>
<string name="multidevice_install_dc_on_other_device">Nainštalujte Delta Chat na vašom ďalšom zariadení (https://get.delta.chat)</string>
<!-- "I Already Have a Profile / Add as Second Device” should be the same text as defined by the keys onboarding_alternative_logins and multidevice_receiver_title -->
<string name="multidevice_tap_scan_on_other_device">Otvorte Delta Chat, ťuknite na \"Existujúci účet / Pridať ako ďalšie zariadenie\" a naskenujte zobrazený kód</string>
<!-- Shown inside a "QR code card" with very limited space; please formulate the text as short as possible therefore. The placeholder will be replaced by name and/or address eg. "Scan to set up second device for Alice (alice@example.org)" -->
<string name="multidevice_qr_subtitle">Naskenujte pre nastavenie ďalšieho zariadenia pre %1$s</string>
<string name="multidevice_receiver_title">Pridať ako ďalšie zariadenie</string>
<string name="multidevice_open_settings_on_other_device">Na pôvodnom zariadení, choďte do \"Nastavenia / Pridať ďalšie zariadenie\" a naskenujte zobrazený kód</string>
<string name="multidevice_receiver_scanning_ask">Skopírovať účet na toto zariadenie?</string>
<string name="multidevice_receiver_needs_update">Účet, ktorý sa snažíte importovať bol vytvorený novšou verziou Delta Chat.
Ak chcete pokračovať, aktualizujte toto zariadenie na najnovšiu verziu Delta Chat.</string>
<string name="multidevice_abort">Zrušiť pridávanie nového zariadenia?</string>
<string name="multidevice_transfer_done_devicemsg">ℹ️ Účet pridaný do ďalšieho zariadenia.</string>
<!-- Shown beside progress bar, stay short -->
<string name="preparing_account">Pripravuje sa účet...</string>
<!-- Shown beside progress bar, stay short -->
<string name="transferring">Prenos dát...</string>
<string name="troubleshooting">Riešenie problémov</string>
<!-- Connectivity --> <!-- Connectivity -->
<!-- Headline for the "Inbox" eg. in the "Connectivity" view --> <!-- Headline for the "Inbox" eg. in the "Connectivity" view -->
<string name="incoming_messages">Prichádzajúce Správy</string> <string name="incoming_messages">Prichádzajúce Správy</string>
@ -479,6 +606,26 @@
<string name="part_of_total_used">%1$s z %2$svyužitých </string> <string name="part_of_total_used">%1$s z %2$svyužitých </string>
<!-- welcome and login -->
<!-- Primary button on the welcome screen, allows to create an instant profile -->
<string name="onboarding_create_instant_account">Nový účet</string>
<!-- Secondary button on the welcome screen, allows to "Add as Second Device", "Restore from Backup" -->
<string name="onboarding_alternative_logins">Existujúci účet</string>
<!-- Button, allows to log in to existing email accounts, setting ports, passwords and so on -->
<string name="manual_account_setup_option">Použiť bežné e-mailové konto</string>
<!-- Instant onboarding title (there is not more to do than to set name and avatar) -->
<string name="instant_onboarding_title">Váš účet</string>
<!-- The placeholder will be replaced by the default onboarding server -->
<string name="instant_onboarding_agree_default2">Zásady ochrany osobných údajov na %1$s</string>
<!-- The placeholder will be replaced by instance name, the whole text will link to the instance page -->
<string name="instant_onboarding_agree_instance">O účtoch na %1$s</string>
<!-- Confirmation button on the instant onboarding screen -->
<string name="instant_onboarding_create">Súhlasím, vytvoriť účet</string>
<!-- Secondary, link-like button to open a page with other possible instances -->
<string name="instant_onboarding_show_more_instances">Použiť iný server</string>
<string name="instant_onboarding_other_server">Zoznam Chatmail serverov</string>
<!-- Question shown when another user's QR code is scanned from onboarding screen -->
<string name="instant_onboarding_confirm_contact">Chcete vytvoriť nový účet a začať konverzáciu s %1$s?</string>
<string name="scan_invitation_code">Skenovať kód pozvánky</string> <string name="scan_invitation_code">Skenovať kód pozvánky</string>
<string name="login_title">Prihlásiť sa</string> <string name="login_title">Prihlásiť sa</string>
<string name="login_header">Prihláste sa na server</string> <string name="login_header">Prihláste sa na server</string>
@ -497,6 +644,20 @@
<string name="login_smtp_port">Port SMTP</string> <string name="login_smtp_port">Port SMTP</string>
<string name="login_smtp_security">Zabezpečenie SMTP</string> <string name="login_smtp_security">Zabezpečenie SMTP</string>
<string name="login_auth_method">Metóda autorizácie</string> <string name="login_auth_method">Metóda autorizácie</string>
<!-- the word "Proxy" might be left untranslated unless the destination language has a well-known term for a "Proxy Server", acting intermediary between the app and the server -->
<string name="proxy_settings">Proxy</string>
<string name="proxy_use_proxy">Použiť proxy</string>
<string name="proxy_add">Pridať proxy</string>
<string name="proxy_add_explain">Podporované typy proxy serverov: HTTP(S), SOCKS5 and Shadowsocks.</string>
<string name="proxy_add_url_hint">Sem vložte odkaz na proxy server</string>
<string name="proxy_invalid">Neplatný alebo nepodporovaný proxy server</string>
<string name="proxy_list_header">Uložené proxy servery</string>
<string name="proxy_delete">Odstrániť proxy</string>
<string name="proxy_delete_explain">Naozaj chcete odstrániť \"%1$s\"?</string>
<string name="proxy_use_proxy_confirm">Chcete použiť proxy \"%1$s\"?</string>
<string name="proxy_share_explain">Vaši priatelia si môžu pridať túto proxy naskenovaním QR kódu.</string>
<string name="proxy_share_link">Zdieľať odkaz</string>
<string name="login_info_oauth2_title">Pokračovať v zjednodušenom nastavovaní?</string> <string name="login_info_oauth2_title">Pokračovať v zjednodušenom nastavovaní?</string>
<string name="login_info_oauth2_text">Zadaná e-mailová adresa podporuje zjednodušené nastavenie (OAuth 2.0).\n\nV ďalšom kroku povoľte aplikácii Delta Chat, aby fungovala ako vaša aplikácia Chat cez e-mail.\n\nNie sú k dispozícii servery Delta Chat, vaše dáta zostanú vo vašom zariadení .</string> <string name="login_info_oauth2_text">Zadaná e-mailová adresa podporuje zjednodušené nastavenie (OAuth 2.0).\n\nV ďalšom kroku povoľte aplikácii Delta Chat, aby fungovala ako vaša aplikácia Chat cez e-mail.\n\nNie sú k dispozícii servery Delta Chat, vaše dáta zostanú vo vašom zariadení .</string>
<string name="login_certificate_checks">Osvedčovacie kontroly</string> <string name="login_certificate_checks">Osvedčovacie kontroly</string>
@ -516,8 +677,8 @@
<string name="delete_account">Odstrániť účet</string> <string name="delete_account">Odstrániť účet</string>
<string name="delete_account_ask">Naozaj chcete odstrániť údaje svojho účtu?</string> <string name="delete_account_ask">Naozaj chcete odstrániť údaje svojho účtu?</string>
<string name="delete_account_explain_with_name">Budú odstránené všetky údaje účtu používateľa „%s“ z tohto zariadenia vrátane vášho kompletného nastavenia šifrovania, kontaktov, konverzácií, správ a médií. Túto akciu nie je možné vrátiť späť.</string> <string name="delete_account_explain_with_name">Budú odstránené všetky údaje účtu používateľa „%s“ z tohto zariadenia vrátane vášho kompletného nastavenia šifrovania, kontaktov, konverzácií, správ a médií. Túto akciu nie je možné vrátiť späť.</string>
<string name="unconfigured_account">Nekonfigurovaný účet</string> <string name="unconfigured_account">Nenastavený účet</string>
<string name="unconfigured_account_hint">Otvorte účet aby ste ho nakonfigurovali.</string> <string name="unconfigured_account_hint">Otvoriť účet pre nastavenie.</string>
<string name="try_connect_now">Skúste sa teraz pripojiť</string> <string name="try_connect_now">Skúste sa teraz pripojiť</string>
<string name="sync_all">Synchronizovať Všetko </string> <string name="sync_all">Synchronizovať Všetko </string>
<!-- Translations: %1$s will be replaced by a more detailed error message --> <!-- Translations: %1$s will be replaced by a more detailed error message -->
@ -534,7 +695,7 @@
<!-- preferences --> <!-- preferences -->
<string name="pref_using_custom">Používa sa vlastné: %s</string> <string name="pref_using_custom">Používa sa vlastné: %s</string>
<string name="pref_using_default">Používa sa predvolené nastavenie: %s</string> <string name="pref_using_default">Používa sa predvolené nastavenie: %s</string>
<string name="pref_profile_info_headline">Informácie o vašom profile</string> <string name="pref_profile_info_headline">Informácie o vašom účte</string>
<string name="pref_profile_photo">Profilový obrázok</string> <string name="pref_profile_photo">Profilový obrázok</string>
<string name="pref_blocked_contacts">Blokované kontakty</string> <string name="pref_blocked_contacts">Blokované kontakty</string>
<string name="blocked_empty_hint">Ak zablokujete kontakty, zobrazia sa tu.</string> <string name="blocked_empty_hint">Ak zablokujete kontakty, zobrazia sa tu.</string>
@ -571,11 +732,14 @@
<string name="pref_appearance">Vzhľad</string> <string name="pref_appearance">Vzhľad</string>
<string name="pref_theme">Motív</string> <string name="pref_theme">Motív</string>
<string name="pref_language">Jazyk</string> <string name="pref_language">Jazyk</string>
<string name="pref_use_system_ui_font">Používať systémový štýl písma</string>
<string name="pref_incognito_keyboard">Inkognito klávesnica</string> <string name="pref_incognito_keyboard">Inkognito klávesnica</string>
<!-- Translators: Must indicate that there is no guarantee as the system may not honor our request. --> <!-- Translators: Must indicate that there is no guarantee as the system may not honor our request. -->
<string name="pref_incognito_keyboard_explain">Požiadajte o klávesnicu, aby deaktivovala prispôsobené učenie</string> <string name="pref_incognito_keyboard_explain">Požiadajte o klávesnicu, aby deaktivovala prispôsobené učenie</string>
<string name="pref_read_receipts">Prečítajte si potvrdenia</string> <string name="pref_read_receipts">Prečítajte si potvrdenia</string>
<string name="pref_read_receipts_explain">Ak sú potvrdenia o prečítaní zakázané, neuvidíte potvrdenia o prečítaní od ostatných.</string> <string name="pref_read_receipts_explain">Ak sú potvrdenia o prečítaní zakázané, neuvidíte potvrdenia o prečítaní od ostatných.</string>
<string name="pref_server">Server</string>
<string name="pref_encryption">Šifrovanie</string>
<string name="pref_manage_keys">Správa kľúčov</string> <string name="pref_manage_keys">Správa kľúčov</string>
<string name="pref_use_system_emoji">Používajte systémové emodži</string> <string name="pref_use_system_emoji">Používajte systémové emodži</string>
<string name="pref_use_system_emoji_explain">Vypnite vstavanú podporu emodži v aplikácii Delta Chat</string> <string name="pref_use_system_emoji_explain">Vypnite vstavanú podporu emodži v aplikácii Delta Chat</string>
@ -589,6 +753,10 @@
<string name="pref_backup">Zálohovanie</string> <string name="pref_backup">Zálohovanie</string>
<string name="pref_backup_explain">Zálohujte konverzácie na externé úložisko</string> <string name="pref_backup_explain">Zálohujte konverzácie na externé úložisko</string>
<string name="pref_backup_export_explain">Záloha vám pomôže nastaviť novú inštaláciu na tomto alebo na inom zariadení.\n\nZáloha bude obsahovať všetky správy, kontakty a konverzácie a vaše úplné nastavenie automatického šifrovania. Uložte záložný súbor na bezpečnom mieste alebo ho čo najskôr odstráňte.</string> <string name="pref_backup_export_explain">Záloha vám pomôže nastaviť novú inštaláciu na tomto alebo na inom zariadení.\n\nZáloha bude obsahovať všetky správy, kontakty a konverzácie a vaše úplné nastavenie automatického šifrovania. Uložte záložný súbor na bezpečnom mieste alebo ho čo najskôr odstráňte.</string>
<!-- the placeholder will be replaced by the profile name -->
<string name="pref_backup_export_x">Exportovať %1$s</string>
<!-- the placeholder will be replaced by the number of profiles to export; the number is always larger than 1 -->
<string name="pref_backup_export_all">Exportovať %1$d účty/účtov</string>
<string name="pref_backup_export_start_button">Spustiť zálohovanie</string> <string name="pref_backup_export_start_button">Spustiť zálohovanie</string>
<string name="pref_backup_written_to_x">Záloha bola úspešne zapísaná do priečinka „%1$s“.</string> <string name="pref_backup_written_to_x">Záloha bola úspešne zapísaná do priečinka „%1$s“.</string>
<string name="pref_managekeys_menu_title">Správa kľúčov</string> <string name="pref_managekeys_menu_title">Správa kľúčov</string>
@ -634,11 +802,15 @@
<string name="n_bytes_message">%1$s správa</string> <string name="n_bytes_message">%1$s správa</string>
<!-- %1$s will be replaced by human-readable date and time --> <!-- %1$s will be replaced by human-readable date and time -->
<string name="download_max_available_until">Maximálny počet stiahnutí k dispozícii do %1$s</string> <string name="download_max_available_until">Maximálny počet stiahnutí k dispozícii do %1$s</string>
<string name="select_profile">Vybrať účet</string>
<string name="profile_image_select">Vyberte profilový obrázok</string> <string name="profile_image_select">Vyberte profilový obrázok</string>
<string name="select_your_new_profile_image">Vyberte svoj nový profilový obrázok</string> <string name="select_your_new_profile_image">Vyberte svoj nový profilový obrázok</string>
<string name="profile_image_delete">Odstrániť profilový obrázok</string> <string name="profile_image_delete">Odstrániť profilový obrázok</string>
<string name="pref_show_tray_icon">Zobraziť ikonu v systémovej lište</string> <string name="pref_show_tray_icon">Zobraziť ikonu v systémovej lište</string>
<string name="pref_edit_profile">Upraviť profil</string> <string name="pref_edit_profile">Upraviť účet</string>
<string name="send_stats_to_devs">Zasielať štatistické údaje Delta Chat vývojárom</string>
<!-- Emoji picker and categories --> <!-- Emoji picker and categories -->
<string name="emoji_search_results">Výsledky vyhľadávania</string> <string name="emoji_search_results">Výsledky vyhľadávania</string>
<string name="emoji_not_found">Nenašli sa žiadne emodži</string> <string name="emoji_not_found">Nenašli sa žiadne emodži</string>
@ -652,6 +824,15 @@
<string name="emoji_symbols">Symboly</string> <string name="emoji_symbols">Symboly</string>
<string name="emoji_flags">Vlajky</string> <string name="emoji_flags">Vlajky</string>
<!-- Reactions -->
<string name="reactions">Reakcie</string>
<!-- Verb, the action of adding a "Reaction" to a message. Used eg. in context menus, similar to "Reply" or "Forward" -->
<string name="react">Pridať reakciu</string>
<!-- %1$s will be replaced by an emoji. %2$s will be replaced by message summary (the summary is often long and whole string gets truncated; words after %2$s will often not being visible). Eg. 'You reacted 👍 to "Found my suitcase"'. Use less than 20 characters, otherwise the string will be truncated too soon and too few information are shown. Do not try to translate "reacted to" too strict. Depending on the language, "added 👍 to" or "gave 👍 to" or just "👍 to" may be shorter and/or clearer and work as well. -->
<string name="reaction_by_you">Reagovali ste %1$s na \"%2$s\"</string>
<!-- %1$s will be replaced a name. %2$s will be replaced by an emoji. %3$s will be replaced by message summary (the summary is often long and whole string gets truncated; words after %3$s will often not being visible). Eg. 'Alice reacted 👍 to "Nice photos"'. Use less than 20 characters, otherwise the string will be truncated too soon and too few information are shown. Do not try to translate "reacted to" too strict. Depending on the language, "added 👍 to" or "gave 👍 to" or just "👍 to" may be shorter and/or clearer work as well. -->
<string name="reaction_by_other">%1$s reagoval/a %2$s na \"%3$s\"</string>
<!-- automatically delete message --> <!-- automatically delete message -->
<string name="delete_old_messages">Odstraňovať staré správy</string> <string name="delete_old_messages">Odstraňovať staré správy</string>
<string name="autodel_device_title">Odstráňte správy zo zariadenia</string> <string name="autodel_device_title">Odstráňte správy zo zariadenia</string>
@ -700,6 +881,8 @@
<string name="remove_member_by_you">Člen %1$s bol odstránený mnou.</string> <string name="remove_member_by_you">Člen %1$s bol odstránený mnou.</string>
<!-- %1$s will be replaced by name and address of the contact removed from the group, %2$s will be replaced by name and address of the contact who did the action --> <!-- %1$s will be replaced by name and address of the contact removed from the group, %2$s will be replaced by name and address of the contact who did the action -->
<string name="remove_member_by_other">Člen %1$s bol odstránený od %2$s.</string> <string name="remove_member_by_other">Člen %1$s bol odstránený od %2$s.</string>
<!-- "left" in the meaning of "exited". This string is added to a chat after groups, channels, broadcasts or mailinglists are left. If a subject is needed, "You left the chat." would work as well. -->
<string name="group_left_by_you">Opustili ste konverzáciu.</string>
<!-- "left" in the meaning of "exited"; %1$s will be replaced by name and address of the contact leaving the group --> <!-- "left" in the meaning of "exited"; %1$s will be replaced by name and address of the contact leaving the group -->
<string name="group_left_by_other">Skupinu opustil(a) %1$s.</string> <string name="group_left_by_other">Skupinu opustil(a) %1$s.</string>
<string name="group_image_deleted_by_you">Odstránili ste obrázok skupiny.</string> <string name="group_image_deleted_by_you">Odstránili ste obrázok skupiny.</string>
@ -743,6 +926,9 @@
<string name="ephemeral_timer_weeks_by_you">Časovač zmiznutia správ nastavený na %1$s týždne mnou.</string> <string name="ephemeral_timer_weeks_by_you">Časovač zmiznutia správ nastavený na %1$s týždne mnou.</string>
<!-- %1$s will be replaced by the number of weeks (always >1) the timer is set to, %2$s will be replaced by name and address of the contact --> <!-- %1$s will be replaced by the number of weeks (always >1) the timer is set to, %2$s will be replaced by name and address of the contact -->
<string name="ephemeral_timer_weeks_by_other">Časovač zmiznutia správ nastavený na %1$s týždne od %2$s.</string> <string name="ephemeral_timer_weeks_by_other">Časovač zmiznutia správ nastavený na %1$s týždne od %2$s.</string>
<string name="chat_protection_enabled_tap_to_learn_more">Správy sú šifrované. Ťuknite pre viac informácií.</string>
<string name="learn_more">Zistiť viac</string>
<string name="devicemsg_self_deleted">Odstránili ste konverzáciu \"Uložené správy\".\n\nℹ️ Aby ste využili funkciu \"Uložené správy\" znova, vytvorte novú konverzáciu so sebou.</string> <string name="devicemsg_self_deleted">Odstránili ste konverzáciu \"Uložené správy\".\n\nℹ️ Aby ste využili funkciu \"Uložené správy\" znova, vytvorte novú konverzáciu so sebou.</string>
<!-- %1$s will be replaced by the amount of storage already used, sth. as '500 MB'. If you want to use a percentage sign, type in two of them, eg. %1$s %% --> <!-- %1$s will be replaced by the amount of storage already used, sth. as '500 MB'. If you want to use a percentage sign, type in two of them, eg. %1$s %% -->
<string name="devicemsg_storage_exceeding">⚠️ Úložisko vašeho poskytovateľa čoskoro prekročí limit, už%1$s%% sú využité.\n\n Je možné, že nebudete môcť prijímať správy, ak bude úložisko 100 %% využité.\n\n👉 Prosím skontrolujte, či môžete vo webovom rozhraní poskytovateľa vymazať staré údaje, a zvážte aktiváciu „Nastavenia / Odstrániť Staré Správy“. Aktuálne využitie úložiska si môžete kedykoľvek skontrolovať v časti „Nastavenia / Pripojenie“. </string> <string name="devicemsg_storage_exceeding">⚠️ Úložisko vašeho poskytovateľa čoskoro prekročí limit, už%1$s%% sú využité.\n\n Je možné, že nebudete môcť prijímať správy, ak bude úložisko 100 %% využité.\n\n👉 Prosím skontrolujte, či môžete vo webovom rozhraní poskytovateľa vymazať staré údaje, a zvážte aktiváciu „Nastavenia / Odstrániť Staré Správy“. Aktuálne využitie úložiska si môžete kedykoľvek skontrolovať v časti „Nastavenia / Pripojenie“. </string>
@ -782,18 +968,27 @@
<!-- This text is shown inside the "QR code card" with very limited space; please formulate the text as short as possible therefore. The placeholder will be replaced by name and address eg. "Scan to chat with Alice (alice@example.org)" --> <!-- This text is shown inside the "QR code card" with very limited space; please formulate the text as short as possible therefore. The placeholder will be replaced by name and address eg. "Scan to chat with Alice (alice@example.org)" -->
<string name="qrshow_join_contact_hint">Naskenujte a vytvorte kontakt s %1$s .</string> <string name="qrshow_join_contact_hint">Naskenujte a vytvorte kontakt s %1$s .</string>
<string name="qrshow_join_contact_no_connection_toast">Nie je pripojenie na internet, nedá sa nastaviť kód QR.</string> <string name="qrshow_join_contact_no_connection_toast">Nie je pripojenie na internet, nedá sa nastaviť kód QR.</string>
<string name="qraccount_ask_create_and_login">Vytvoriť novú e-mailovú adresu na „%1$s“ a prihlásiť sa tam?</string> <string name="qraccount_ask_create_and_login">Vytvoriť nový účet na „%1$s“ a prihlásiť sa?</string>
<string name="qraccount_ask_create_and_login_another">Vytvorte novú e-mailovú adresu na „%1$s“ a prihláste sa tam?\n\nVáš existujúci účet nebude odstránený. Medzi položkami môžete prepínať pomocou položky „Prepnúť účet“.</string> <string name="qraccount_ask_create_and_login_another">Vytvoriť nový účet na „%1$s“ a prihlásiť sa?
Váš existujúci účet nebude odstránený. Medzi účtami môžete prepínať pomocou „Prepnúť účet“.</string>
<string name="please_enter_name">Prosím, zadajte meno.</string>
<string name="qraccount_qr_code_cannot_be_used">Naskenovaný QR kód nie je možné použiť na založenie nového účtu.</string> <string name="qraccount_qr_code_cannot_be_used">Naskenovaný QR kód nie je možné použiť na založenie nového účtu.</string>
<!-- the placeholder will be replaced by the address of the profile --> <!-- the placeholder will be replaced by the address of the profile -->
<string name="qrlogin_ask_login">Prihlásiť sa na \"%1$s\"?</string> <string name="qrlogin_ask_login">Prihlásiť sa na \"%1$s\"?</string>
<!-- the placeholder will be replaced by the address of the profile -->
<string name="qrlogin_ask_login_another">Prihlásiť sa do „%1$s“?
Váš existujúci účet nebude odstránený. Medzi účtami môžete prepínať pomocou „Prepnúť účet“.</string>
<!-- first placeholder will be replaced by name and address of the inviter, second placeholder will be replaced by the name of the inviter. --> <!-- first placeholder will be replaced by name and address of the inviter, second placeholder will be replaced by the name of the inviter. -->
<string name="secure_join_started">%1$s vás pozval, aby ste sa pripojili k tejto skupine.\n\nČaká sa na odpoveď zo zariadenia používateľa %2$s...</string> <string name="secure_join_started">%1$s vás pozval, aby ste sa pripojili k tejto skupine.\n\nČaká sa na odpoveď zo zariadenia používateľa %2$s...</string>
<!-- placeholder will be replaced by the name of the inviter. --> <!-- placeholder will be replaced by the name of the inviter. -->
<string name="secure_join_replies">%1$sodpovedal a čaká sa na pridanie do skupiny...</string> <string name="secure_join_replies">%1$sodpovedal a čaká sa na pridanie do skupiny...</string>
<string name="secure_join_wait">Nadväzovanie šifrovaného spojenia, počkajte prosím...</string>
<string name="contact_verified">%1$s overené.</string> <string name="contact_verified">%1$s overené.</string>
<!-- deprecated, was stock string -->
<string name="contact_not_verified">Cannot verify %1$s.</string> <string name="contact_not_verified">Cannot verify %1$s.</string>
<!-- translators: "setup" is the "encryption setup" here, as in "Autocrypt Setup Message" --> <!-- deprecated, was stock string -->
<string name="contact_setup_changed">Zmena nastavenia pre %1$s.</string> <string name="contact_setup_changed">Zmena nastavenia pre %1$s.</string>
<string name="mailto_dialog_header_select_chat">Vyberte konverzáciu, kam bude správa odoslaná</string> <string name="mailto_dialog_header_select_chat">Vyberte konverzáciu, kam bude správa odoslaná</string>
<!-- first placeholder is the name of the chat --> <!-- first placeholder is the name of the chat -->
@ -809,6 +1004,9 @@
<string name="notify_name_and_message">Meno a správa</string> <string name="notify_name_and_message">Meno a správa</string>
<string name="notify_name_only">Iba meno</string> <string name="notify_name_only">Iba meno</string>
<string name="notify_no_name_or_message">Žiadne meno ani správa</string> <string name="notify_no_name_or_message">Žiadne meno ani správa</string>
<string name="new_messages">Nové správy</string>
<!-- Body text for a generic "New messages" notification. Shown if we do not have more information about a new messages. Note, that the string is also referenced at https://github.com/deltachat/notifiers -->
<string name="new_messages_body">Máte nové správy</string>
<!-- permissions --> <!-- permissions -->
<string name="perm_required_title">Vyžaduje sa povolenie</string> <string name="perm_required_title">Vyžaduje sa povolenie</string>
<string name="perm_continue">ďalej</string> <string name="perm_continue">ďalej</string>
@ -827,7 +1025,7 @@
<string name="ImageEditorHud_flip">Preklopiť</string> <string name="ImageEditorHud_flip">Preklopiť</string>
<string name="ImageEditorHud_rotate">Otočiť</string> <string name="ImageEditorHud_rotate">Otočiť</string>
<!-- dc_str_* resources --> <!-- deprecated, use string "E-Mail" for non-encrypted messages instead -->
<string name="encrypted_message">Zašifrovaná správa</string> <string name="encrypted_message">Zašifrovaná správa</string>
<!-- strings introduced on desktop. we want to share strings between the os, in general, please do not add generic strings here --> <!-- strings introduced on desktop. we want to share strings between the os, in general, please do not add generic strings here -->
@ -848,6 +1046,7 @@
<string name="global_menu_view_developer_desktop">Vývojár</string> <string name="global_menu_view_developer_desktop">Vývojár</string>
<string name="global_menu_view_developer_tools_desktop">Nástroje pre vývojárov</string> <string name="global_menu_view_developer_tools_desktop">Nástroje pre vývojárov</string>
<string name="global_menu_help_desktop">Pomocník</string> <string name="global_menu_help_desktop">Pomocník</string>
<string name="delta_chat_homepage">Stránka Delta Chat</string>
<string name="global_menu_help_report_desktop">Nahlásiť problém</string> <string name="global_menu_help_report_desktop">Nahlásiť problém</string>
<string name="global_menu_help_about_desktop">O spoločnosti Delta Chat</string> <string name="global_menu_help_about_desktop">O spoločnosti Delta Chat</string>
<string name="global_menu_file_open_desktop">Otvoriť Delta Chat</string> <string name="global_menu_file_open_desktop">Otvoriť Delta Chat</string>
@ -918,6 +1117,7 @@
<string name="notifications_avg_minutes">V priemere každých %1$d minút</string> <string name="notifications_avg_minutes">V priemere každých %1$d minút</string>
<string name="notifications_avg_hours">V priemere každých %1$d hodín</string> <string name="notifications_avg_hours">V priemere každých %1$d hodín</string>
<string name="last_check_at">Skontrolované %1$s</string> <string name="last_check_at">Skontrolované %1$s</string>
<string name="system_settings">Systémové nastavenia</string>
<!-- iOS permissions, copy from "deltachat-ios/Info.plist", which is used on missing translations in "deltachat-ios/LANG.lproj/InfoPlist.strings" --> <!-- iOS permissions, copy from "deltachat-ios/Info.plist", which is used on missing translations in "deltachat-ios/LANG.lproj/InfoPlist.strings" -->
<string name="InfoPlist_NSCameraUsageDescription">Delta Chat používa váš fotoaparát na snímanie a odosielanie fotografií a videí a na skenovanie QR kódov.</string> <string name="InfoPlist_NSCameraUsageDescription">Delta Chat používa váš fotoaparát na snímanie a odosielanie fotografií a videí a na skenovanie QR kódov.</string>
<string name="InfoPlist_NSContactsUsageDescription">Delta Chat používa vaše kontakty na zobrazenie zoznamu e-mailových adries, na ktoré môžete písať. Delta Chat nemá žiadny server, vaše kontakty sa nikam neposielajú.</string> <string name="InfoPlist_NSContactsUsageDescription">Delta Chat používa vaše kontakty na zobrazenie zoznamu e-mailových adries, na ktoré môžete písať. Delta Chat nemá žiadny server, vaše kontakty sa nikam neposielajú.</string>

16
src/main/res/values-sq/strings.xml
View file

@ -342,7 +342,6 @@
<!-- Menu item beside an app/chat that adds an icon to the system's home screen. If the user taps that icon, the app/chat is opened directly. --> <!-- Menu item beside an app/chat that adds an icon to the system's home screen. If the user taps that icon, the app/chat is opened directly. -->
<string name="add_to_home_screen">Shtoje te Skena e Kreut</string> <string name="add_to_home_screen">Shtoje te Skena e Kreut</string>
<string name="donate">Dhuroni</string> <string name="donate">Dhuroni</string>
<string name="mute_for_one_hour">Heshtoji për 1 orë</string> <string name="mute_for_one_hour">Heshtoji për 1 orë</string>
<string name="mute_for_eight_hours">Heshtoje për 8 orë</string> <string name="mute_for_eight_hours">Heshtoje për 8 orë</string>
<string name="mute_for_one_day">Heshtoji për 1 ditë</string> <string name="mute_for_one_day">Heshtoji për 1 ditë</string>
@ -542,7 +541,7 @@
<!-- option to show images in the gallery as square (instead of using correct width/height) --> <!-- option to show images in the gallery as square (instead of using correct width/height) -->
<string name="square_grid">Mozaik Katror</string> <string name="square_grid">Mozaik Katror</string>
<string name="send_message">Dërgo Mesazh</string> <string name="send_message">Dërgo Mesazh</string>
<!-- Placeholder %1$s will be replaced by the name of the contact changing their address. Placeholders %2$s and %3$s will be replaced by old/new addresses. --> <!-- deprecated, was stock string -->
<string name="aeap_addr_changed">%1$s ndryshoi adresën e vet nga %2$s në %3$s</string> <string name="aeap_addr_changed">%1$s ndryshoi adresën e vet nga %2$s në %3$s</string>
<!-- deprecated --> <!-- deprecated -->
<string name="aeap_explanation">Ndryshuat adresën tuaj nga %1$s në %2$s.\n\nNëse dërgoni tani një mesazh te një grup i verifikuar, kontaktet atje do të zëvendësojnë automatikisht adresën tuaj të vjetër me të renë.\n\nËshtë tejet e këshillueshme të ujdisni shërbimin tuaj të vjetër të email-it të përcjellë krejt email-et te adresa juaj e re email. Përndryshe, mund të humbni mesazhe të kontakteve që s’e kanë marrë ende adresën tuaj të re.</string> <string name="aeap_explanation">Ndryshuat adresën tuaj nga %1$s në %2$s.\n\nNëse dërgoni tani një mesazh te një grup i verifikuar, kontaktet atje do të zëvendësojnë automatikisht adresën tuaj të vjetër me të renë.\n\nËshtë tejet e këshillueshme të ujdisni shërbimin tuaj të vjetër të email-it të përcjellë krejt email-et te adresa juaj e re email. Përndryshe, mund të humbni mesazhe të kontakteve që s’e kanë marrë ende adresën tuaj të re.</string>
@ -942,11 +941,13 @@
<string name="ephemeral_timer_weeks_by_you">E vutë kohëmatësin e zhdukjes së mesazheve në %1$s javë.</string> <string name="ephemeral_timer_weeks_by_you">E vutë kohëmatësin e zhdukjes së mesazheve në %1$s javë.</string>
<!-- %1$s will be replaced by the number of weeks (always >1) the timer is set to, %2$s will be replaced by name and address of the contact --> <!-- %1$s will be replaced by the number of weeks (always >1) the timer is set to, %2$s will be replaced by name and address of the contact -->
<string name="ephemeral_timer_weeks_by_other">Kohëmatësi i zhdukjes së mesazheve u vu në %1$s javë nga %2$s.</string> <string name="ephemeral_timer_weeks_by_other">Kohëmatësi i zhdukjes së mesazheve u vu në %1$s javë nga %2$s.</string>
<!-- this may be shown instead of the chat's input field, with buttons "More Info" and "OK" --> <!-- deprecated -->
<string name="chat_protection_broken">%1$s dërgoi një mesazh nga një pajisje tjetër.</string> <string name="chat_protection_broken">%1$s dërgoi një mesazh nga një pajisje tjetër.</string>
<string name="chat_protection_enabled_tap_to_learn_more">Nga sot e tutje për mesazhet garantohet fshehtëzimi skaj-më-skaj. Prekeni, që të mësoni më tepër.</string> <string name="chat_protection_enabled_tap_to_learn_more">Nga sot e tutje për mesazhet garantohet fshehtëzimi skaj-më-skaj. Prekeni, që të mësoni më tepër.</string>
<string name="chat_protection_enabled_explanation">Tanimë për mesazhet në këtë fjalosje garantohet fshehtëzimi skaj-më-skaj.\n\nFshehtëzimi skaj-më-skaj i mban private mesazhet mes jush dhe partnerëve tuaj të fjalosjes. Ato s’mund t’i lexojë as furnizuesi i shërbimit tuaj email.</string> <string name="chat_protection_enabled_explanation">Tanimë për mesazhet në këtë fjalosje garantohet fshehtëzimi skaj-më-skaj.\n\nFshehtëzimi skaj-më-skaj i mban private mesazhet mes jush dhe partnerëve tuaj të fjalosjes. Ato s’mund t’i lexojë as furnizuesi i shërbimit tuaj email.</string>
<!-- deprecated -->
<string name="chat_protection_broken_tap_to_learn_more">%1$s dërgoi një mesazh nga një pajisje tjetër. Prekeni, që të mësoni më tepër.</string> <string name="chat_protection_broken_tap_to_learn_more">%1$s dërgoi një mesazh nga një pajisje tjetër. Prekeni, që të mësoni më tepër.</string>
<!-- deprecated -->
<string name="chat_protection_broken_explanation">Fshehtëzimi skaj-më-skaj s’mund të garantohet më, ngaqë, sipas gjasash, %1$s riinstaloi Delta Chat-in, ose dërgoi një mesazh nga një tjetër pajisje.\n\nMund ta takoni dhe të skanoni sërish KODIN e tij QR, që të rivendoset fshehtëzim skaj-më-skaj i garantuar.</string> <string name="chat_protection_broken_explanation">Fshehtëzimi skaj-më-skaj s’mund të garantohet më, ngaqë, sipas gjasash, %1$s riinstaloi Delta Chat-in, ose dërgoi një mesazh nga një tjetër pajisje.\n\nMund ta takoni dhe të skanoni sërish KODIN e tij QR, që të rivendoset fshehtëzim skaj-më-skaj i garantuar.</string>
<string name="invalid_unencrypted_tap_to_learn_more">⚠️ %1$s lyp fshehtëzim, i cili s’është ujdisur ende për këtë fjalosje. Që të mësoni më tepër, prekeni.</string> <string name="invalid_unencrypted_tap_to_learn_more">⚠️ %1$s lyp fshehtëzim, i cili s’është ujdisur ende për këtë fjalosje. Që të mësoni më tepër, prekeni.</string>
<string name="invalid_unencrypted_explanation">Për të vendosur fshehtëzim skaj-më-skaj, mund të takoheni personalisht me kontaktet dhe të skanoni kodin e tyre QR, për t’i pranuar.</string> <string name="invalid_unencrypted_explanation">Për të vendosur fshehtëzim skaj-më-skaj, mund të takoheni personalisht me kontaktet dhe të skanoni kodin e tyre QR, për t’i pranuar.</string>
@ -1008,13 +1009,15 @@
<string name="secure_join_wait">Po vendoset fshehtëzim skaj-më-skaj i garantuar, ju lutemi, pritni…</string> <string name="secure_join_wait">Po vendoset fshehtëzim skaj-më-skaj i garantuar, ju lutemi, pritni…</string>
<!-- deprecated --> <!-- deprecated -->
<string name="secure_join_wait_timeout">S’u vendos dot fshehtëzim skaj-më-skaj i garantuar, por mundeni tashmë të dërgoni një mesazh.</string> <string name="secure_join_wait_timeout">S’u vendos dot fshehtëzim skaj-më-skaj i garantuar, por mundeni tashmë të dërgoni një mesazh.</string>
<!-- deprecated, was stock string -->
<string name="secure_join_takes_longer">Duket se po zgjat ca, mos ndoshta kontakti juaj, ose vetë ju s’jeni lidhur në internet.\n\nSidoqoftë, procesi vazhdon në prapaskenë, mund të merreni me diçka tjetër…</string> <string name="secure_join_takes_longer">Duket se po zgjat ca, mos ndoshta kontakti juaj, ose vetë ju s’jeni lidhur në internet.\n\nSidoqoftë, procesi vazhdon në prapaskenë, mund të merreni me diçka tjetër…</string>
<string name="contact_verified">%1$s u verifikua.</string> <string name="contact_verified">%1$s u verifikua.</string>
<!-- deprecated, was stock string -->
<string name="contact_not_verified">S’vendoset dot fshehtëzim i garantuar skaj-më-skaj me %1$s.</string> <string name="contact_not_verified">S’vendoset dot fshehtëzim i garantuar skaj-më-skaj me %1$s.</string>
<!-- Shown in contact profile. The placeholder will be replaced by the name of the contact that introduced the contact. --> <!-- Shown in contact profile. The placeholder will be replaced by the name of the contact that introduced the contact. -->
<string name="verified_by">Sjellë nga %1$s</string> <string name="verified_by">Sjellë nga %1$s</string>
<string name="verified_by_you">Sjellë nga unë</string> <string name="verified_by_you">Sjellë nga unë</string>
<!-- translators: "setup" is the "encryption setup" here, as in "Autocrypt Setup Message" --> <!-- deprecated, was stock string -->
<string name="contact_setup_changed">U ndryshua udjisja për %1$s</string> <string name="contact_setup_changed">U ndryshua udjisja për %1$s</string>
<string name="verified_contact_required_explain">Që të garantohet fshehtëzim skaj-më-skaj, mund të shtoni në këtë grup vetëm kontakte me shenjën e gjelbër të verifikimit.\n\nMund të takoheni drejtpërsëdrejti me kontakte të paverifikuar dhe të skanoni kodin e tyre QR për t’i verifikuar ata.</string> <string name="verified_contact_required_explain">Që të garantohet fshehtëzim skaj-më-skaj, mund të shtoni në këtë grup vetëm kontakte me shenjën e gjelbër të verifikimit.\n\nMund të takoheni drejtpërsëdrejti me kontakte të paverifikuar dhe të skanoni kodin e tyre QR për t’i verifikuar ata.</string>
<string name="mailto_dialog_header_select_chat">Përzgjidhni fjalosje ku të dërgohet mesazhi</string> <string name="mailto_dialog_header_select_chat">Përzgjidhni fjalosje ku të dërgohet mesazhi</string>
@ -1058,7 +1061,7 @@
<string name="ImageEditorHud_flip">Ktheje në anë tjetër</string> <string name="ImageEditorHud_flip">Ktheje në anë tjetër</string>
<string name="ImageEditorHud_rotate">Rrotulloje</string> <string name="ImageEditorHud_rotate">Rrotulloje</string>
<!-- dc_str_* resources --> <!-- deprecated, use string "E-Mail" for non-encrypted messages instead -->
<string name="encrypted_message">Mesazh i fshehtëzuar</string> <string name="encrypted_message">Mesazh i fshehtëzuar</string>
<!-- strings introduced on desktop. we want to share strings between the os, in general, please do not add generic strings here --> <!-- strings introduced on desktop. we want to share strings between the os, in general, please do not add generic strings here -->
@ -1184,7 +1187,8 @@
<string name="perm_enable_bg_reminder_title">Prekeni këtu që të merrni mesazhe, teksa Delta Chat rri në prapaskenë.</string> <string name="perm_enable_bg_reminder_title">Prekeni këtu që të merrni mesazhe, teksa Delta Chat rri në prapaskenë.</string>
<string name="perm_enable_bg_already_done">E keni lejuar tashmë Delta Chat-in të marrë mesazhe në prapaskenë.\n\nNëse mesazhet prapë nuk mbërrijnë në prapaskenë, ju lutemi, kontrolloni edhe rregullimet e sistemit tuaj.</string> <string name="perm_enable_bg_already_done">E keni lejuar tashmë Delta Chat-in të marrë mesazhe në prapaskenë.\n\nNëse mesazhet prapë nuk mbërrijnë në prapaskenë, ju lutemi, kontrolloni edhe rregullimet e sistemit tuaj.</string>
<!-- device messages for updates --> <!-- deprecated -->
<string name="update_1_50_android">Ç’ka të re?\n\n❤️‍🔥 Zgjedhës i ri emoji-sh, me më shumë të tillë\n\n🎮 Zgjerim aplikacionesh brenda fjalosjesh: Merrni njoftim dhe hapni aplikacionet përkatës sipas kontekstit, p.sh., hapni drejtpërdrejt një zë të saposhtuar kalendari\n\n👍 Merrni njoftim mbi reagime te mesazhet tuaj\n\n… 🛠️ NDREQJE DHE MË TEPËR te %1$s</string> <string name="update_1_50_android">Ç’ka të re?\n\n❤️‍🔥 Zgjedhës i ri emoji-sh, me më shumë të tillë\n\n🎮 Zgjerim aplikacionesh brenda fjalosjesh: Merrni njoftim dhe hapni aplikacionet përkatës sipas kontekstit, p.sh., hapni drejtpërdrejt një zë të saposhtuar kalendari\n\n👍 Merrni njoftim mbi reagime te mesazhet tuaj\n\n… 🛠️ NDREQJE DHE MË TEPËR te %1$s</string>
<!-- deprecated -->
<string name="update_switch_profile_placement">ℹ️ Mundësia “Ndërroni Profil” u hoq: Që të shtoni, ose ndërroni profile, prekni figurën e profilit tuaj në cepin e sipërm të skenës kryesore 💡</string> <string name="update_switch_profile_placement">ℹ️ Mundësia “Ndërroni Profil” u hoq: Që të shtoni, ose ndërroni profile, prekni figurën e profilit tuaj në cepin e sipërm të skenës kryesore 💡</string>
</resources> </resources>

7
src/main/res/values-sr/strings.xml
View file

@ -451,7 +451,7 @@
<string name="all_apps_empty_hint">Приватне апликације примљене или послате у било ком ћаскању ће се појавити овде.</string> <string name="all_apps_empty_hint">Приватне апликације примљене или послате у било ком ћаскању ће се појавити овде.</string>
<string name="media_preview">Преглед медијума</string> <string name="media_preview">Преглед медијума</string>
<string name="send_message">Пошаљи поруку</string> <string name="send_message">Пошаљи поруку</string>
<!-- Placeholder %1$s will be replaced by the name of the contact changing their address. Placeholders %2$s and %3$s will be replaced by old/new addresses. --> <!-- deprecated, was stock string -->
<string name="aeap_addr_changed">%1$sје променио њихову адресу %2$sу %3$s</string> <string name="aeap_addr_changed">%1$sје променио њихову адресу %2$sу %3$s</string>
<!-- deprecated --> <!-- deprecated -->
<string name="aeap_explanation">Ви сте променили вашу имејл адресу %1$sу %2$s.\n\nАко сада пошаљете поруку провереној групи, тамошњи контакти ће аутоматски заменити стару адресу новом.\n\nПрепоручљиво је да подесите свог предходног имејл провајдера да прослеђује све имејл поруке на вашу нову имејл адресу. У супротном бисте могли да пропустите поруке од контаката који још нису добили вашу нову адресу.</string> <string name="aeap_explanation">Ви сте променили вашу имејл адресу %1$sу %2$s.\n\nАко сада пошаљете поруку провереној групи, тамошњи контакти ће аутоматски заменити стару адресу новом.\n\nПрепоручљиво је да подесите свог предходног имејл провајдера да прослеђује све имејл поруке на вашу нову имејл адресу. У супротном бисте могли да пропустите поруке од контаката који још нису добили вашу нову адресу.</string>
@ -797,10 +797,11 @@
<!-- placeholder will be replaced by the name of the inviter. --> <!-- placeholder will be replaced by the name of the inviter. -->
<string name="secure_join_replies">%1$s је одговорио и чека да буде додат у групу...</string> <string name="secure_join_replies">%1$s је одговорио и чека да буде додат у групу...</string>
<string name="contact_verified">%1$s потврђен.</string> <string name="contact_verified">%1$s потврђен.</string>
<!-- deprecated, was stock string -->
<string name="contact_not_verified">Немогуће је проверити %1$s.</string> <string name="contact_not_verified">Немогуће је проверити %1$s.</string>
<!-- Shown in contact profile. The placeholder will be replaced by the name of the contact that introduced the contact. --> <!-- Shown in contact profile. The placeholder will be replaced by the name of the contact that introduced the contact. -->
<string name="verified_by">Проверено од %1$s</string> <string name="verified_by">Проверено од %1$s</string>
<!-- translators: "setup" is the "encryption setup" here, as in "Autocrypt Setup Message" --> <!-- deprecated, was stock string -->
<string name="contact_setup_changed">Подешавања су се променила за %1$s.</string> <string name="contact_setup_changed">Подешавања су се променила за %1$s.</string>
<string name="mailto_dialog_header_select_chat">Изабери ћаскање у које желите да пошаљете поруку</string> <string name="mailto_dialog_header_select_chat">Изабери ћаскање у које желите да пошаљете поруку</string>
<!-- first placeholder is the name of the chat --> <!-- first placeholder is the name of the chat -->
@ -834,7 +835,7 @@
<string name="ImageEditorHud_flip">Окрени</string> <string name="ImageEditorHud_flip">Окрени</string>
<string name="ImageEditorHud_rotate">Обрни</string> <string name="ImageEditorHud_rotate">Обрни</string>
<!-- dc_str_* resources --> <!-- deprecated, use string "E-Mail" for non-encrypted messages instead -->
<string name="encrypted_message">Шифрована порука</string> <string name="encrypted_message">Шифрована порука</string>
<!-- strings introduced on desktop. we want to share strings between the os, in general, please do not add generic strings here --> <!-- strings introduced on desktop. we want to share strings between the os, in general, please do not add generic strings here -->

13
src/main/res/values-sv/strings.xml
View file

@ -300,7 +300,6 @@
<!-- Menu item beside an app/chat that adds an icon to the system's home screen. If the user taps that icon, the app/chat is opened directly. --> <!-- Menu item beside an app/chat that adds an icon to the system's home screen. If the user taps that icon, the app/chat is opened directly. -->
<string name="add_to_home_screen">Lägg till på hemskärmen</string> <string name="add_to_home_screen">Lägg till på hemskärmen</string>
<string name="donate">Donera</string> <string name="donate">Donera</string>
<string name="mute_for_one_hour">Tysta 1 timma</string> <string name="mute_for_one_hour">Tysta 1 timma</string>
<string name="mute_for_eight_hours">Tysta 8 timmar</string> <string name="mute_for_eight_hours">Tysta 8 timmar</string>
<string name="mute_for_one_day">Tysta 1 dag</string> <string name="mute_for_one_day">Tysta 1 dag</string>
@ -480,7 +479,7 @@
<!-- option to show images in the gallery as square (instead of using correct width/height) --> <!-- option to show images in the gallery as square (instead of using correct width/height) -->
<string name="square_grid">Kvadratiskt rutnät</string> <string name="square_grid">Kvadratiskt rutnät</string>
<string name="send_message">Skicka meddelande</string> <string name="send_message">Skicka meddelande</string>
<!-- Placeholder %1$s will be replaced by the name of the contact changing their address. Placeholders %2$s and %3$s will be replaced by old/new addresses. --> <!-- deprecated, was stock string -->
<string name="aeap_addr_changed">%1$s ändrade sin adress från %2$s till %3$s</string> <string name="aeap_addr_changed">%1$s ändrade sin adress från %2$s till %3$s</string>
<!-- deprecated --> <!-- deprecated -->
<string name="aeap_explanation">Du har ändrat din e-postadress från %1$s till %2$s.\n\nOm du nu skickar ett meddelande till en verifierad grupp kommer kontakterna där automatiskt att ersätta den gamla med din nya adress. Vi rekommenderar starkt att du ställer in din gamla e-postleverantör så att den vidarebefordrar alla e-postmeddelanden till din nya e-postadress. Annars kan du missa meddelanden från kontakter som inte har fått din nya adress ännu.</string> <string name="aeap_explanation">Du har ändrat din e-postadress från %1$s till %2$s.\n\nOm du nu skickar ett meddelande till en verifierad grupp kommer kontakterna där automatiskt att ersätta den gamla med din nya adress. Vi rekommenderar starkt att du ställer in din gamla e-postleverantör så att den vidarebefordrar alla e-postmeddelanden till din nya e-postadress. Annars kan du missa meddelanden från kontakter som inte har fått din nya adress ännu.</string>
@ -853,11 +852,13 @@
<string name="ephemeral_timer_weeks_by_you">Du satte tiduret för meddelandeborttagning till %1$s veckor.</string> <string name="ephemeral_timer_weeks_by_you">Du satte tiduret för meddelandeborttagning till %1$s veckor.</string>
<!-- %1$s will be replaced by the number of weeks (always >1) the timer is set to, %2$s will be replaced by name and address of the contact --> <!-- %1$s will be replaced by the number of weeks (always >1) the timer is set to, %2$s will be replaced by name and address of the contact -->
<string name="ephemeral_timer_weeks_by_other">Tiduret för meddelandeborttagning är satt till %1$s veckor av %2$s.</string> <string name="ephemeral_timer_weeks_by_other">Tiduret för meddelandeborttagning är satt till %1$s veckor av %2$s.</string>
<!-- this may be shown instead of the chat's input field, with buttons "More Info" and "OK" --> <!-- deprecated -->
<string name="chat_protection_broken">%1$s skickade ett meddelande från en annan enhet.</string> <string name="chat_protection_broken">%1$s skickade ett meddelande från en annan enhet.</string>
<string name="chat_protection_enabled_tap_to_learn_more">Meddelanden är garanterat totalsträckskrypterade från och med nu. Tryck för att få veta mer.</string> <string name="chat_protection_enabled_tap_to_learn_more">Meddelanden är garanterat totalsträckskrypterade från och med nu. Tryck för att få veta mer.</string>
<string name="chat_protection_enabled_explanation">Det är nu garanterat att alla meddelanden i den här chatten är totalsträckskrypterade.\n\nTotalsträckskryptering håller meddelanden privata mellan dig och dina chattpartners. Inte ens din e-postleverantör kan läsa dem.</string> <string name="chat_protection_enabled_explanation">Det är nu garanterat att alla meddelanden i den här chatten är totalsträckskrypterade.\n\nTotalsträckskryptering håller meddelanden privata mellan dig och dina chattpartners. Inte ens din e-postleverantör kan läsa dem.</string>
<!-- deprecated -->
<string name="chat_protection_broken_tap_to_learn_more">%1$s skickade ett meddelande från en annan enhet. Tryck för att läsa mer.</string> <string name="chat_protection_broken_tap_to_learn_more">%1$s skickade ett meddelande från en annan enhet. Tryck för att läsa mer.</string>
<!-- deprecated -->
<string name="chat_protection_broken_explanation">Totalsträckskryptering kan inte garanteras längre, troligen för att %1$s installerade om Delta Chat eller skickade ett meddelande från en annan enhet.\n\nDu kan träffa dem personligen och skanna deras QR-kod igen för att återupprätta garanterad totalsträckskryptering.</string> <string name="chat_protection_broken_explanation">Totalsträckskryptering kan inte garanteras längre, troligen för att %1$s installerade om Delta Chat eller skickade ett meddelande från en annan enhet.\n\nDu kan träffa dem personligen och skanna deras QR-kod igen för att återupprätta garanterad totalsträckskryptering.</string>
<string name="invalid_unencrypted_tap_to_learn_more">⚠️ %1$s kräver totalsträckskryptering som inte är kofigurerad för den här chatten ännu. Tryck för att lära dig mer.</string> <string name="invalid_unencrypted_tap_to_learn_more">⚠️ %1$s kräver totalsträckskryptering som inte är kofigurerad för den här chatten ännu. Tryck för att lära dig mer.</string>
<string name="invalid_unencrypted_explanation">För att skapa totalsträckskryptering kan du träffa kontakter personligen och skanna deras QR-kod för att introducera dem.</string> <string name="invalid_unencrypted_explanation">För att skapa totalsträckskryptering kan du träffa kontakter personligen och skanna deras QR-kod för att introducera dem.</string>
@ -920,11 +921,12 @@
<!-- deprecated --> <!-- deprecated -->
<string name="secure_join_wait_timeout">Kunde ännu inte upprätta garanterad totalsträckskryptering, men du kan redan skicka ett meddelande.</string> <string name="secure_join_wait_timeout">Kunde ännu inte upprätta garanterad totalsträckskryptering, men du kan redan skicka ett meddelande.</string>
<string name="contact_verified">%1$s verifierad.</string> <string name="contact_verified">%1$s verifierad.</string>
<!-- deprecated, was stock string -->
<string name="contact_not_verified">Kan inte verifiera %1$s.</string> <string name="contact_not_verified">Kan inte verifiera %1$s.</string>
<!-- Shown in contact profile. The placeholder will be replaced by the name of the contact that introduced the contact. --> <!-- Shown in contact profile. The placeholder will be replaced by the name of the contact that introduced the contact. -->
<string name="verified_by">Introducerad av %1$s</string> <string name="verified_by">Introducerad av %1$s</string>
<string name="verified_by_you">Introducerad av mig</string> <string name="verified_by_you">Introducerad av mig</string>
<!-- translators: "setup" is the "encryption setup" here, as in "Autocrypt Setup Message" --> <!-- deprecated, was stock string -->
<string name="contact_setup_changed">Ändrade inställningarna för %1$s.</string> <string name="contact_setup_changed">Ändrade inställningarna för %1$s.</string>
<string name="verified_contact_required_explain">För att garantera totalsträckskryptering kan du bara lägga till kontakter med en grön bock i den här gruppen.\n\nDu kan träffa kontakter personligen och skanna deras QR-kod för att introducera dem.</string> <string name="verified_contact_required_explain">För att garantera totalsträckskryptering kan du bara lägga till kontakter med en grön bock i den här gruppen.\n\nDu kan träffa kontakter personligen och skanna deras QR-kod för att introducera dem.</string>
<string name="mailto_dialog_header_select_chat">Välj chatt för att skicka meddelandet till</string> <string name="mailto_dialog_header_select_chat">Välj chatt för att skicka meddelandet till</string>
@ -968,7 +970,7 @@
<string name="ImageEditorHud_flip">Vänd</string> <string name="ImageEditorHud_flip">Vänd</string>
<string name="ImageEditorHud_rotate">Rotera</string> <string name="ImageEditorHud_rotate">Rotera</string>
<!-- dc_str_* resources --> <!-- deprecated, use string "E-Mail" for non-encrypted messages instead -->
<string name="encrypted_message">Krypterat meddelande</string> <string name="encrypted_message">Krypterat meddelande</string>
<!-- strings introduced on desktop. we want to share strings between the os, in general, please do not add generic strings here --> <!-- strings introduced on desktop. we want to share strings between the os, in general, please do not add generic strings here -->
@ -1079,5 +1081,6 @@
<string name="perm_enable_bg_reminder_title">Tryck här för att ta emot meddelanden medan Delta Chat är i bakgrunden.</string> <string name="perm_enable_bg_reminder_title">Tryck här för att ta emot meddelanden medan Delta Chat är i bakgrunden.</string>
<string name="perm_enable_bg_already_done">Du har redan gett Delta Chatt tillstånd att ta emot meddelanden i bakgrunden.\n\nKontrollera dina systeminställningar också, om det fortfarande inte kommer några meddelanden i bakgrunden.</string> <string name="perm_enable_bg_already_done">Du har redan gett Delta Chatt tillstånd att ta emot meddelanden i bakgrunden.\n\nKontrollera dina systeminställningar också, om det fortfarande inte kommer några meddelanden i bakgrunden.</string>
<!-- deprecated -->
<string name="update_switch_profile_placement">ℹ️ Alternativet \"Byt profil\" har flyttats: Tryck på din profilbild i det övre hörnet av huvudskärmen för att lägga till eller byta profil 💡</string> <string name="update_switch_profile_placement">ℹ️ Alternativet \"Byt profil\" har flyttats: Tryck på din profilbild i det övre hörnet av huvudskärmen för att lägga till eller byta profil 💡</string>
</resources> </resources>

2
src/main/res/values-ta/strings.xml
View file

@ -226,7 +226,7 @@
<!-- permissions --> <!-- permissions -->
<string name="perm_required_title">அனுமதி தேவை</string> <string name="perm_required_title">அனுமதி தேவை</string>
<string name="perm_continue">தொடர்</string> <string name="perm_continue">தொடர்</string>
<!-- dc_str_* resources --> <!-- deprecated, use string "E-Mail" for non-encrypted messages instead -->
<string name="encrypted_message">மறைகுறியாக்கப்பட்ட செய்தி</string> <string name="encrypted_message">மறைகுறியாக்கப்பட்ட செய்தி</string>
<string name="welcome_desktop">Delta Chat க்கு வரவேற்கிறது.</string> <string name="welcome_desktop">Delta Chat க்கு வரவேற்கிறது.</string>

2
src/main/res/values-te/strings.xml
View file

@ -195,7 +195,7 @@
<!-- permissions --> <!-- permissions -->
<string name="perm_required_title">అనుమతి అవసరం</string> <string name="perm_required_title">అనుమతి అవసరం</string>
<string name="perm_continue">కొనసాగించు</string> <string name="perm_continue">కొనసాగించు</string>
<!-- dc_str_* resources --> <!-- deprecated, use string "E-Mail" for non-encrypted messages instead -->
<string name="encrypted_message">ఎంక్రిప్ట్ చెసిన సందేశం</string> <string name="encrypted_message">ఎంక్రిప్ట్ చెసిన సందేశం</string>
<string name="welcome_desktop">Delta Chat కి స్వాగతం.</string> <string name="welcome_desktop">Delta Chat కి స్వాగతం.</string>

48
src/main/res/values-tr/strings.xml
View file

@ -246,6 +246,12 @@
<string name="broadcast_lists">Yayın Listeleri</string> <string name="broadcast_lists">Yayın Listeleri</string>
<!-- deprecated --> <!-- deprecated -->
<string name="new_broadcast_list">Yeni Yayın Listesi</string> <string name="new_broadcast_list">Yeni Yayın Listesi</string>
<!-- consider keeping the term "channel" as in WhatsApp or Telegram -->
<string name="channel">Kanal</string>
<!-- consider keeping the term "channel" as in WhatsApp or Telegram -->
<string name="channels">Kanallar</string>
<!-- consider keeping the term "channel" as in WhatsApp or Telegram -->
<string name="new_channel">Yeni Kanal</string>
<string name="add_recipients">Alıcılar Ekle</string> <string name="add_recipients">Alıcılar Ekle</string>
<!-- deprecated --> <!-- deprecated -->
<string name="edit_broadcast_list">Yayın Listesini Düzenle</string> <string name="edit_broadcast_list">Yayın Listesini Düzenle</string>
@ -253,6 +259,13 @@
<string name="broadcast_list_name">Yayın Listesi Adı</string> <string name="broadcast_list_name">Yayın Listesi Adı</string>
<!-- deprecated --> <!-- deprecated -->
<string name="please_enter_broadcast_list_name">Lütfen yayın listesi için bir ad girin.</string> <string name="please_enter_broadcast_list_name">Lütfen yayın listesi için bir ad girin.</string>
<!-- consider keeping the term "channel" as in WhatsApp or Telegram -->
<string name="channel_name">Kanal Adı</string>
<string name="email">E-Posta</string>
<!-- "New" as in "Create New E-Mail"; shown together with "New Group" and "New Channel" -->
<string name="new_email">Yeni E-Posta</string>
<!-- the "Subject" of an e-mail, use the term common in classic e-mail apps -->
<string name="subject">Konu</string>
<string name="menu_send">Gönder</string> <string name="menu_send">Gönder</string>
<string name="menu_toggle_keyboard">Emoji Klavyesine Geç</string> <string name="menu_toggle_keyboard">Emoji Klavyesine Geç</string>
<string name="menu_edit_group">Öbeği Düzenle</string> <string name="menu_edit_group">Öbeği Düzenle</string>
@ -262,6 +275,7 @@
<string name="menu_unarchive_chat">Sohbeti Arşivleme</string> <string name="menu_unarchive_chat">Sohbeti Arşivleme</string>
<string name="menu_add_attachment">İlişik Ekle</string> <string name="menu_add_attachment">İlişik Ekle</string>
<string name="menu_leave_group">Öbekten Ayrıl</string> <string name="menu_leave_group">Öbekten Ayrıl</string>
<string name="menu_leave_channel">Kanaldan Ayrıl</string>
<string name="menu_delete_chat">Sohbeti Sil</string> <string name="menu_delete_chat">Sohbeti Sil</string>
<!-- Command to delete all messages in a chat. The chat itself will not be deleted but will be empty afterwards, so make sure to be different from "Delete Chat" here. "Clear" is a verb here, "Empty Chat" would also be fine (eg. in German "Chat leeren") --> <!-- Command to delete all messages in a chat. The chat itself will not be deleted but will be empty afterwards, so make sure to be different from "Delete Chat" here. "Clear" is a verb here, "Empty Chat" would also be fine (eg. in German "Chat leeren") -->
<string name="clear_chat">Sohbeti Temizle</string> <string name="clear_chat">Sohbeti Temizle</string>
@ -346,6 +360,7 @@
<!-- Menu item beside an app/chat that adds an icon to the system's home screen. If the user taps that icon, the app/chat is opened directly. --> <!-- Menu item beside an app/chat that adds an icon to the system's home screen. If the user taps that icon, the app/chat is opened directly. -->
<string name="add_to_home_screen">Ana Ekrana Ekle</string> <string name="add_to_home_screen">Ana Ekrana Ekle</string>
<string name="donate">Bağış</string> <string name="donate">Bağış</string>
<string name="donate_device_msg">❤️ Delta Chat\'in tadını çıkarıyor gibisiniz!\n\nDelta Chat\'in herkes için ücretsiz kalmasını sağlamak için lütfen bağış yapmayı düşünün.\n\nDelta Chat, kullanımı ücretsiz ve açık kaynaklıdır, geliştirme paraya mâl olur. Delta Chat\'in bağımsızlığını korumak ve onu gelecekte daha da harika yapmak için bize yardımcı olun.\n\nhttps://delta.chat/donate</string>
<string name="mute_for_one_hour">1 saatliğine sessize al</string> <string name="mute_for_one_hour">1 saatliğine sessize al</string>
<string name="mute_for_eight_hours">8 saatliğine sessize al</string> <string name="mute_for_eight_hours">8 saatliğine sessize al</string>
@ -381,6 +396,9 @@
<string name="videochat_invitation">Video sohbeti çağrısı</string> <string name="videochat_invitation">Video sohbeti çağrısı</string>
<string name="videochat_invitation_body">Bir video sohbetine çağrıldınız; katılmak için %1$s öğesini tıklayın.</string> <string name="videochat_invitation_body">Bir video sohbetine çağrıldınız; katılmak için %1$s öğesini tıklayın.</string>
<!-- get confirmations -->
<!-- confirmation for leaving groups, channels, broadcasts or a mailinglists. If a subject is needed, "Are you sure you want to leave the chat?" would work as well -->
<string name="ask_leave_group">Ayrılmak istediğinizden emin misiniz?</string>
<plurals name="ask_delete_chat"> <plurals name="ask_delete_chat">
<item quantity="one">Tüm aygıtlarınızdaki %d sohbet silinsin mi?</item> <item quantity="one">Tüm aygıtlarınızdaki %d sohbet silinsin mi?</item>
<item quantity="other">Tüm aygıtlarınızdaki %d sohbet silinsin mi?</item> <item quantity="other">Tüm aygıtlarınızdaki %d sohbet silinsin mi?</item>
@ -408,6 +426,8 @@
<string name="ask_remove_members">%1$s öbekten kaldırılsın mı?</string> <string name="ask_remove_members">%1$s öbekten kaldırılsın mı?</string>
<!-- deprecated --> <!-- deprecated -->
<string name="ask_remove_from_broadcast">%1$s yayın listesinden kaldırılsın mı?</string> <string name="ask_remove_from_broadcast">%1$s yayın listesinden kaldırılsın mı?</string>
<!-- %1$s is replaced by a comma-separated list of names -->
<string name="ask_remove_from_channel">%1$s kanaldan kaldırılsın mı?</string>
<string name="open_url_confirmation">Bu bağlantıyı açmak istiyor musunuz?</string> <string name="open_url_confirmation">Bu bağlantıyı açmak istiyor musunuz?</string>
@ -439,6 +459,8 @@
<string name="chat_new_one_to_one_hint">%1$s kişisine bir ileti gönderin.</string> <string name="chat_new_one_to_one_hint">%1$s kişisine bir ileti gönderin.</string>
<!-- deprecated --> <!-- deprecated -->
<string name="chat_new_broadcast_hint">Bir yayın listesinde, alıcılar sizinle salt okunur bir sohbette iletiler alacak.</string> <string name="chat_new_broadcast_hint">Bir yayın listesinde, alıcılar sizinle salt okunur bir sohbette iletiler alacak.</string>
<!-- consider keeping the term "channel" as in WhatsApp or Telegram -->
<string name="chat_new_channel_hint">Kanallar, iletilerinizi yayınlamak için birden çoğa bir araçtır.</string>
<string name="chat_new_group_hint">Diğerleri, yalnızca siz bir ilk ileti gönderdikten sonra bu öbeği görecek.</string> <string name="chat_new_group_hint">Diğerleri, yalnızca siz bir ilk ileti gönderdikten sonra bu öbeği görecek.</string>
<string name="chat_record_slide_to_cancel">İptal etmek için kaydırın</string> <string name="chat_record_slide_to_cancel">İptal etmek için kaydırın</string>
<string name="chat_record_explain">Bir sesli ileti kaydetmek için dokunun ve basılı tutun, göndermek için bırakın</string> <string name="chat_record_explain">Bir sesli ileti kaydetmek için dokunun ve basılı tutun, göndermek için bırakın</string>
@ -547,7 +569,7 @@
<!-- option to show images in the gallery as square (instead of using correct width/height) --> <!-- option to show images in the gallery as square (instead of using correct width/height) -->
<string name="square_grid">Kare Izgara</string> <string name="square_grid">Kare Izgara</string>
<string name="send_message">İleti Gönder</string> <string name="send_message">İleti Gönder</string>
<!-- Placeholder %1$s will be replaced by the name of the contact changing their address. Placeholders %2$s and %3$s will be replaced by old/new addresses. --> <!-- deprecated, was stock string -->
<string name="aeap_addr_changed">%1$s, %2$s adresini %3$s olarak değiştirdi</string> <string name="aeap_addr_changed">%1$s, %2$s adresini %3$s olarak değiştirdi</string>
<!-- deprecated --> <!-- deprecated -->
<string name="aeap_explanation">%1$s e-posta adresinizi %2$s olarak değiştirdiniz.\n\nŞimdi bir doğrulanan öbeğe ileti gönderirseniz, oradaki kişiler yeni adresinizle eskisini otomatik olarak değiştirecek.\n\nTüm e-postaları yeni e-posta adresinize iletmek için eski e-posta sağlayıcınızı ayarlamanız önemle önerilir. Yoksa henüz yeni adresinizi almamış olan kişilerin iletilerini kaçırabilirsiniz.</string> <string name="aeap_explanation">%1$s e-posta adresinizi %2$s olarak değiştirdiniz.\n\nŞimdi bir doğrulanan öbeğe ileti gönderirseniz, oradaki kişiler yeni adresinizle eskisini otomatik olarak değiştirecek.\n\nTüm e-postaları yeni e-posta adresinize iletmek için eski e-posta sağlayıcınızı ayarlamanız önemle önerilir. Yoksa henüz yeni adresinizi almamış olan kişilerin iletilerini kaçırabilirsiniz.</string>
@ -905,6 +927,8 @@
<string name="remove_member_by_you">%1$s üyesini kaldırdınız.</string> <string name="remove_member_by_you">%1$s üyesini kaldırdınız.</string>
<!-- %1$s will be replaced by name and address of the contact removed from the group, %2$s will be replaced by name and address of the contact who did the action --> <!-- %1$s will be replaced by name and address of the contact removed from the group, %2$s will be replaced by name and address of the contact who did the action -->
<string name="remove_member_by_other">%2$s tarafından %1$s üyesi kaldırıldı.</string> <string name="remove_member_by_other">%2$s tarafından %1$s üyesi kaldırıldı.</string>
<!-- "left" in the meaning of "exited". This string is added to a chat after groups, channels, broadcasts or mailinglists are left. If a subject is needed, "You left the chat." would work as well. -->
<string name="group_left_by_you">Ayrıldınız.</string>
<!-- "left" in the meaning of "exited"; %1$s will be replaced by name and address of the contact leaving the group --> <!-- "left" in the meaning of "exited"; %1$s will be replaced by name and address of the contact leaving the group -->
<string name="group_left_by_other">%1$s tarafından öbekten ayrılındı.</string> <string name="group_left_by_other">%1$s tarafından öbekten ayrılındı.</string>
<string name="group_image_deleted_by_you">Öbek görselini sildiniz.</string> <string name="group_image_deleted_by_you">Öbek görselini sildiniz.</string>
@ -948,11 +972,13 @@
<string name="ephemeral_timer_weeks_by_you">Kaybolan iletiler zamanlayıcısını %1$s hafta olarak ayarladınız.</string> <string name="ephemeral_timer_weeks_by_you">Kaybolan iletiler zamanlayıcısını %1$s hafta olarak ayarladınız.</string>
<!-- %1$s will be replaced by the number of weeks (always >1) the timer is set to, %2$s will be replaced by name and address of the contact --> <!-- %1$s will be replaced by the number of weeks (always >1) the timer is set to, %2$s will be replaced by name and address of the contact -->
<string name="ephemeral_timer_weeks_by_other">%2$s tarafından kaybolan iletiler zamanlayıcısı %1$s hafta olarak ayarlandı.</string> <string name="ephemeral_timer_weeks_by_other">%2$s tarafından kaybolan iletiler zamanlayıcısı %1$s hafta olarak ayarlandı.</string>
<!-- this may be shown instead of the chat's input field, with buttons "More Info" and "OK" --> <!-- deprecated -->
<string name="chat_protection_broken">%1$s başka bir aygıttan bir ileti gönderdi.</string> <string name="chat_protection_broken">%1$s başka bir aygıttan bir ileti gönderdi.</string>
<string name="chat_protection_enabled_tap_to_learn_more">Bundan böyle iletiler uçtan uca şifreleme güvencelidir. Daha fazlasını öğrenmek için dokunun.</string> <string name="chat_protection_enabled_tap_to_learn_more">İletiler uçtan uca şifreleniyor. Daha fazlasını öğrenmek için dokunun.</string>
<string name="chat_protection_enabled_explanation">Artık bu sohbetteki tüm iletiler uçtan uca şifreleme güvencelidir.\n\nUçtan uca şifreleme, iletilerinizi sizin ve sohbet ortaklarınızın arasında özel tutar. Sunucular, sağlayıcılar ya da aktarıcılar bile onları okuyamaz.</string> <string name="chat_protection_enabled_explanation">Bu sohbetteki tüm iletiler uçtan uca şifreleniyor.\n\nUçtan uca şifreleme, iletilerinizi sizin ve sohbet ortaklarınızın arasında özel tutar. Sunucular, sağlayıcılar ya da aktarıcılar bile onları okuyamaz.</string>
<!-- deprecated -->
<string name="chat_protection_broken_tap_to_learn_more">%1$s başka bir aygıttan bir ileti gönderdi. Daha fazlasını öğrenmek için dokunun.</string> <string name="chat_protection_broken_tap_to_learn_more">%1$s başka bir aygıttan bir ileti gönderdi. Daha fazlasını öğrenmek için dokunun.</string>
<!-- deprecated -->
<string name="chat_protection_broken_explanation">Uçtan uca şifreleme artık güvencelenemiyor; çünkü büyük olasılıkla %1$s Delta Chat\'i yeniden yükledi ya da başka bir aygıttan ileti gönderdi.\n\nOnlarla kişisel olarak tanışabilir ve güvenceli uçtan uca şifrelemeyi yeniden kurmak için onların QR kodunu yeniden tarayabilirsiniz.</string> <string name="chat_protection_broken_explanation">Uçtan uca şifreleme artık güvencelenemiyor; çünkü büyük olasılıkla %1$s Delta Chat\'i yeniden yükledi ya da başka bir aygıttan ileti gönderdi.\n\nOnlarla kişisel olarak tanışabilir ve güvenceli uçtan uca şifrelemeyi yeniden kurmak için onların QR kodunu yeniden tarayabilirsiniz.</string>
<string name="invalid_unencrypted_tap_to_learn_more">⚠️ %1$s, bu sohbet için henüz ayarlanmayan uçtan uca şifrelemeyi gerektirir. Daha fazlasını öğrenmek için dokunun.</string> <string name="invalid_unencrypted_tap_to_learn_more">⚠️ %1$s, bu sohbet için henüz ayarlanmayan uçtan uca şifrelemeyi gerektirir. Daha fazlasını öğrenmek için dokunun.</string>
<string name="invalid_unencrypted_explanation">Uçtan uca şifrelemeyi kurmak için kişilerle kişisel olarak tanışabilir ve onları tanıtmak için onların QR kodunu tarayabilirsiniz.</string> <string name="invalid_unencrypted_explanation">Uçtan uca şifrelemeyi kurmak için kişilerle kişisel olarak tanışabilir ve onları tanıtmak için onların QR kodunu tarayabilirsiniz.</string>
@ -1011,16 +1037,19 @@
<string name="secure_join_started">%1$s sizi bu öbeğe katılmaya çağırdı.\n\n%2$s kişisinin aygıtının yanıt vermesi bekleniyor…</string> <string name="secure_join_started">%1$s sizi bu öbeğe katılmaya çağırdı.\n\n%2$s kişisinin aygıtının yanıt vermesi bekleniyor…</string>
<!-- placeholder will be replaced by the name of the inviter. --> <!-- placeholder will be replaced by the name of the inviter. -->
<string name="secure_join_replies">%1$s yanıtladı; öbeğe eklenmesi bekleniyor…</string> <string name="secure_join_replies">%1$s yanıtladı; öbeğe eklenmesi bekleniyor…</string>
<string name="secure_join_wait">Güvencelenen uçtan uca şifreleme kuruluyor, lütfen bekleyin…</string> <string name="secure_join_wait">Uçtan uca şifreleme kuruluyor, lütfen bekleyin…</string>
<!-- deprecated --> <!-- deprecated -->
<string name="secure_join_wait_timeout">Henüz güvencelenen uçtan uca şifreleme kurulamadı; ama zaten bir ileti gönderebilirsiniz.</string> <string name="secure_join_wait_timeout">Henüz güvencelenen uçtan uca şifreleme kurulamadı; ama zaten bir ileti gönderebilirsiniz.</string>
<!-- deprecated, was stock string -->
<string name="secure_join_takes_longer">Sürdürmek için kişi çevrimiçi olmalıdır.\n\nBu işlem, arka planda otomatik olarak sürecek.</string> <string name="secure_join_takes_longer">Sürdürmek için kişi çevrimiçi olmalıdır.\n\nBu işlem, arka planda otomatik olarak sürecek.</string>
<string name="contact_verified">%1$s tanıtıldı.</string> <string name="contact_verified">%1$s tanıtıldı.</string>
<string name="contact_not_verified">%1$s ile güvencelenen uçtan uca şifreleme kurulamıyor.</string> <!-- deprecated, was stock string -->
<string name="contact_not_verified">%1$s ile uçtan uca şifreleme kurulamıyor.</string>
<!-- Shown in contact profile. The placeholder will be replaced by the name of the contact that introduced the contact. --> <!-- Shown in contact profile. The placeholder will be replaced by the name of the contact that introduced the contact. -->
<string name="verified_by">%1$s tarafından tanıtıldı</string> <string name="verified_by">%1$s tarafından tanıtıldı</string>
<string name="verified_by_you">Benim tarafımdan tanıtıldı</string> <string name="verified_by_you">Benim tarafımdan tanıtıldı</string>
<!-- translators: "setup" is the "encryption setup" here, as in "Autocrypt Setup Message" --> <string name="verified_by_unknown">Tanıtıldı</string>
<!-- deprecated, was stock string -->
<string name="contact_setup_changed">%1$s için ayarlama değiştirildi.</string> <string name="contact_setup_changed">%1$s için ayarlama değiştirildi.</string>
<string name="verified_contact_required_explain">Uçtan uca şifrelemeyi güvencelemek için bu öbeğe yalnızca yeşil bir onay imi olan kişileri ekleyebilirsiniz.\n\nDoğrulanmayan kişilerle kişisel olarak tanışabilir ve onları tanıtmak için onların QR kodunu tarayabilirsiniz.</string> <string name="verified_contact_required_explain">Uçtan uca şifrelemeyi güvencelemek için bu öbeğe yalnızca yeşil bir onay imi olan kişileri ekleyebilirsiniz.\n\nDoğrulanmayan kişilerle kişisel olarak tanışabilir ve onları tanıtmak için onların QR kodunu tarayabilirsiniz.</string>
<string name="mailto_dialog_header_select_chat">İletiyi göndermek için sohbet seçin</string> <string name="mailto_dialog_header_select_chat">İletiyi göndermek için sohbet seçin</string>
@ -1064,7 +1093,7 @@
<string name="ImageEditorHud_flip">Çevir</string> <string name="ImageEditorHud_flip">Çevir</string>
<string name="ImageEditorHud_rotate">Döndür</string> <string name="ImageEditorHud_rotate">Döndür</string>
<!-- dc_str_* resources --> <!-- deprecated, use string "E-Mail" for non-encrypted messages instead -->
<string name="encrypted_message">Şifrelenen ileti</string> <string name="encrypted_message">Şifrelenen ileti</string>
<!-- strings introduced on desktop. we want to share strings between the os, in general, please do not add generic strings here --> <!-- strings introduced on desktop. we want to share strings between the os, in general, please do not add generic strings here -->
@ -1195,6 +1224,9 @@
<string name="perm_enable_bg_already_done">Delta Chat\'in arka planda iletileri almasına zaten izin verdiniz.\n\nİletiler arka planda hâlâ gelmiyorsa, lütfen sistem ayarlarınızı da denetleyin.</string> <string name="perm_enable_bg_already_done">Delta Chat\'in arka planda iletileri almasına zaten izin verdiniz.\n\nİletiler arka planda hâlâ gelmiyorsa, lütfen sistem ayarlarınızı da denetleyin.</string>
<!-- device messages for updates --> <!-- device messages for updates -->
<string name="update_2_0">Ne yeni?\n\n💯 Uçtan uca şifreleme artık güvenilir ve sonsuza kadar geçerli. Asma kilitlerle 🔒 anlaşılabilir!\n\n✉️ Uçtan uca şifrelemeli olmayan klasik e-posta bir mektup sembolü olarak işaretlenir\n\n😻 Tüm kişileriniz için yeni geliştirilen profil ekranı\n\n🔲 Bir sohbette kullanılan uygulamalara hızlı erişim için yeni düğme\n\n❤️ Bağımsız kalmamız ve yeni geliştirmeler getirmemiz için lütfen bize yardım edin: %1$s</string>
<!-- deprecated -->
<string name="update_1_50_android">Ne yeni?\n\n❤️‍🔥 Daha fazla emojiyle yeni emoji seçicisi\n\n🎮 Geliştirilen sohbet içi uygulamalar: Bildirimler alın ve destekleyen uygulamaları bağlamda açın, yani eklenen bir takvim girdisini doğrudan açın\n\n👍 İletilerinize verilen tepkiler hakkında bildirimler alın\n\n... 🛠️ DÜZELTMELER ve HATTA DAHA FAZLASI için %1$s</string> <string name="update_1_50_android">Ne yeni?\n\n❤️‍🔥 Daha fazla emojiyle yeni emoji seçicisi\n\n🎮 Geliştirilen sohbet içi uygulamalar: Bildirimler alın ve destekleyen uygulamaları bağlamda açın, yani eklenen bir takvim girdisini doğrudan açın\n\n👍 İletilerinize verilen tepkiler hakkında bildirimler alın\n\n... 🛠️ DÜZELTMELER ve HATTA DAHA FAZLASI için %1$s</string>
<!-- deprecated -->
<string name="update_switch_profile_placement">ℹ️ “Profili Değiştir” seçeneği taşındı: Yeni profil eklemek ya da profilleri değiştirmek için ana ekranın üst köşesindeki profil görselinize dokunun 💡</string> <string name="update_switch_profile_placement">ℹ️ “Profili Değiştir” seçeneği taşındı: Yeni profil eklemek ya da profilleri değiştirmek için ana ekranın üst köşesindeki profil görselinize dokunun 💡</string>
</resources> </resources>

45
src/main/res/values-uk/strings.xml
View file

@ -28,8 +28,8 @@
<string name="join">Долучитися</string> <string name="join">Долучитися</string>
<string name="rejoin">Передолучитися</string> <string name="rejoin">Передолучитися</string>
<string name="delete">Видалити</string> <string name="delete">Видалити</string>
<string name="delete_for_me">Видалить у мене</string> <string name="delete_for_me">Видалити для мене</string>
<string name="delete_for_everyone">Видалити в усіх</string> <string name="delete_for_everyone">Видалити для всіх</string>
<string name="info">Відомості</string> <string name="info">Відомості</string>
<string name="update">Оновити</string> <string name="update">Оновити</string>
<string name="emoji">Емодзі</string> <string name="emoji">Емодзі</string>
@ -264,6 +264,12 @@
<string name="broadcast_lists">Списки трансляцій</string> <string name="broadcast_lists">Списки трансляцій</string>
<!-- deprecated --> <!-- deprecated -->
<string name="new_broadcast_list">Новий Список трансляцій</string> <string name="new_broadcast_list">Новий Список трансляцій</string>
<!-- consider keeping the term "channel" as in WhatsApp or Telegram -->
<string name="channel">Канал</string>
<!-- consider keeping the term "channel" as in WhatsApp or Telegram -->
<string name="channels">Канали</string>
<!-- consider keeping the term "channel" as in WhatsApp or Telegram -->
<string name="new_channel">Новий Канал</string>
<string name="add_recipients">Додати одержувачів</string> <string name="add_recipients">Додати одержувачів</string>
<!-- deprecated --> <!-- deprecated -->
<string name="edit_broadcast_list">Редагувати список трансляцій</string> <string name="edit_broadcast_list">Редагувати список трансляцій</string>
@ -271,6 +277,13 @@
<string name="broadcast_list_name">Назва списку трансляцій</string> <string name="broadcast_list_name">Назва списку трансляцій</string>
<!-- deprecated --> <!-- deprecated -->
<string name="please_enter_broadcast_list_name">Будь ласка, введіть назву для списку трансляцій.</string> <string name="please_enter_broadcast_list_name">Будь ласка, введіть назву для списку трансляцій.</string>
<!-- consider keeping the term "channel" as in WhatsApp or Telegram -->
<string name="channel_name">Назва Каналу</string>
<string name="email">E-Mail</string>
<!-- "New" as in "Create New E-Mail"; shown together with "New Group" and "New Channel" -->
<string name="new_email">Новий E-Mail</string>
<!-- the "Subject" of an e-mail, use the term common in classic e-mail apps -->
<string name="subject">Тема</string>
<string name="menu_send">Послати</string> <string name="menu_send">Послати</string>
<string name="menu_toggle_keyboard">Увімкнути емодзі-клавіатуру</string> <string name="menu_toggle_keyboard">Увімкнути емодзі-клавіатуру</string>
<string name="menu_edit_group">Редагувати групу</string> <string name="menu_edit_group">Редагувати групу</string>
@ -280,6 +293,7 @@
<string name="menu_unarchive_chat">Розархівувати чат</string> <string name="menu_unarchive_chat">Розархівувати чат</string>
<string name="menu_add_attachment">Додати вкладення</string> <string name="menu_add_attachment">Додати вкладення</string>
<string name="menu_leave_group">Залишити групу</string> <string name="menu_leave_group">Залишити групу</string>
<string name="menu_leave_channel">Покинути Канал</string>
<string name="menu_delete_chat">Видалити чат</string> <string name="menu_delete_chat">Видалити чат</string>
<!-- Command to delete all messages in a chat. The chat itself will not be deleted but will be empty afterwards, so make sure to be different from "Delete Chat" here. "Clear" is a verb here, "Empty Chat" would also be fine (eg. in German "Chat leeren") --> <!-- Command to delete all messages in a chat. The chat itself will not be deleted but will be empty afterwards, so make sure to be different from "Delete Chat" here. "Clear" is a verb here, "Empty Chat" would also be fine (eg. in German "Chat leeren") -->
<string name="clear_chat">Очистити чат</string> <string name="clear_chat">Очистити чат</string>
@ -364,6 +378,7 @@
<!-- Menu item beside an app/chat that adds an icon to the system's home screen. If the user taps that icon, the app/chat is opened directly. --> <!-- Menu item beside an app/chat that adds an icon to the system's home screen. If the user taps that icon, the app/chat is opened directly. -->
<string name="add_to_home_screen">Додати на стартовий екран</string> <string name="add_to_home_screen">Додати на стартовий екран</string>
<string name="donate">Задонатити</string> <string name="donate">Задонатити</string>
<string name="donate_device_msg">❤️ Здається, вам подобається Delta Chat!\n\nПодумайте про пожертвування, щоб допомогти забезпечити безкоштовність Delta Chat для всіх.\n\nХоча Delta Chat є безкоштовним у використанні та з відкритим вихідним кодом, розробка коштує грошей. Допоможіть нам зберегти незалежність Delta Chat і зробити його ще більш чудовим у майбутньому.\n\nhttps://delta.chat/donate</string>
<string name="mute_for_one_hour">Вимкнути сповіщення на годину</string> <string name="mute_for_one_hour">Вимкнути сповіщення на годину</string>
<string name="mute_for_eight_hours">Вимкнути сповіщення на 8 годин</string> <string name="mute_for_eight_hours">Вимкнути сповіщення на 8 годин</string>
@ -401,6 +416,9 @@
<string name="videochat_invitation">Запрошення до відео чату</string> <string name="videochat_invitation">Запрошення до відео чату</string>
<string name="videochat_invitation_body">Вас запрошено у відео-чат, клікніть %1$s аби приєднатися.</string> <string name="videochat_invitation_body">Вас запрошено у відео-чат, клікніть %1$s аби приєднатися.</string>
<!-- get confirmations -->
<!-- confirmation for leaving groups, channels, broadcasts or a mailinglists. If a subject is needed, "Are you sure you want to leave the chat?" would work as well -->
<string name="ask_leave_group">Ви впевнені, що хочете піти?</string>
<plurals name="ask_delete_chat"> <plurals name="ask_delete_chat">
<item quantity="one">¿Видалити %d чат на всіх Ваших пристроях?</item> <item quantity="one">¿Видалити %d чат на всіх Ваших пристроях?</item>
<item quantity="few">¿Видалити %d чати на всіх Ваших пристроях?</item> <item quantity="few">¿Видалити %d чати на всіх Ваших пристроях?</item>
@ -434,6 +452,8 @@
<string name="ask_remove_members">Видалити %1$s із групи?</string> <string name="ask_remove_members">Видалити %1$s із групи?</string>
<!-- deprecated --> <!-- deprecated -->
<string name="ask_remove_from_broadcast">Видалити %1$s зі списку трансляцій?</string> <string name="ask_remove_from_broadcast">Видалити %1$s зі списку трансляцій?</string>
<!-- %1$s is replaced by a comma-separated list of names -->
<string name="ask_remove_from_channel">Видалити %1$s з каналу?</string>
<string name="open_url_confirmation">Ви впевнені, що хочете відкрити це посилання?</string> <string name="open_url_confirmation">Ви впевнені, що хочете відкрити це посилання?</string>
@ -471,6 +491,8 @@
<string name="chat_new_one_to_one_hint">Відправити повідомлення → %1$s.</string> <string name="chat_new_one_to_one_hint">Відправити повідомлення → %1$s.</string>
<!-- deprecated --> <!-- deprecated -->
<string name="chat_new_broadcast_hint">У списку трансляцій одержувачі будуть отримувати повідомлення в чаті з Вами в режимі тільки-для-читання.</string> <string name="chat_new_broadcast_hint">У списку трансляцій одержувачі будуть отримувати повідомлення в чаті з Вами в режимі тільки-для-читання.</string>
<!-- consider keeping the term "channel" as in WhatsApp or Telegram -->
<string name="chat_new_channel_hint">Канали - це інструмент \"один до багатьох\" для трансляції ваших повідомлень.</string>
<string name="chat_new_group_hint">Інші побачать цю групу лише після того, як ви надішлете перше повідомлення.</string> <string name="chat_new_group_hint">Інші побачать цю групу лише після того, як ви надішлете перше повідомлення.</string>
<string name="chat_record_slide_to_cancel">Рухайте для скасування</string> <string name="chat_record_slide_to_cancel">Рухайте для скасування</string>
<string name="chat_record_explain">Натиснувши втримуйте, щоби записати голосове повідомлення, а для відправки відпустіть</string> <string name="chat_record_explain">Натиснувши втримуйте, щоби записати голосове повідомлення, а для відправки відпустіть</string>
@ -480,6 +502,7 @@
<string name="chat_input_placeholder">Повідомлення</string> <string name="chat_input_placeholder">Повідомлення</string>
<string name="chat_archived_label">Заархівовано</string> <string name="chat_archived_label">Заархівовано</string>
<string name="chat_request_label">Запит</string> <string name="chat_request_label">Запит</string>
<string name="chat_request_label_explain">Включайте запити в лічильники та сповіщення</string>
<string name="chat_no_messages">Немає повідомлень.</string> <string name="chat_no_messages">Немає повідомлень.</string>
<string name="chat_self_talk_subtitle">Повідомлення, відправлені самому собі</string> <string name="chat_self_talk_subtitle">Повідомлення, відправлені самому собі</string>
<string name="archive_empty_hint">Заархівовані Вами чати будуть відображені тут.</string> <string name="archive_empty_hint">Заархівовані Вами чати будуть відображені тут.</string>
@ -578,7 +601,7 @@
<!-- option to show images in the gallery as square (instead of using correct width/height) --> <!-- option to show images in the gallery as square (instead of using correct width/height) -->
<string name="square_grid">Квадратна сітка</string> <string name="square_grid">Квадратна сітка</string>
<string name="send_message">Надіслати повідомлення</string> <string name="send_message">Надіслати повідомлення</string>
<!-- Placeholder %1$s will be replaced by the name of the contact changing their address. Placeholders %2$s and %3$s will be replaced by old/new addresses. --> <!-- deprecated, was stock string -->
<string name="aeap_addr_changed">%1$s змінили їх адресу з %2$s на %3$s</string> <string name="aeap_addr_changed">%1$s змінили їх адресу з %2$s на %3$s</string>
<!-- deprecated --> <!-- deprecated -->
<string name="aeap_explanation">Ви змінили свою електронну поштову адресу з %1$s на %2$s.\n\nЯкщо тепер відправите повідомлення в підтверджену групу, контакти в ній автоматично замінять стару адресу новою.\n\nРекомендується налаштувати стару поштову скриньку на пересилання всіх електронних листів на Вашу нову скриньку. Інакше Ви можете пропустити повідомлення від контактних осіб, які ще не довідалися вашої нової адреси.</string> <string name="aeap_explanation">Ви змінили свою електронну поштову адресу з %1$s на %2$s.\n\nЯкщо тепер відправите повідомлення в підтверджену групу, контакти в ній автоматично замінять стару адресу новою.\n\nРекомендується налаштувати стару поштову скриньку на пересилання всіх електронних листів на Вашу нову скриньку. Інакше Ви можете пропустити повідомлення від контактних осіб, які ще не довідалися вашої нової адреси.</string>
@ -936,6 +959,8 @@
<string name="remove_member_by_you">Ви видалили учасника %1$s.</string> <string name="remove_member_by_you">Ви видалили учасника %1$s.</string>
<!-- %1$s will be replaced by name and address of the contact removed from the group, %2$s will be replaced by name and address of the contact who did the action --> <!-- %1$s will be replaced by name and address of the contact removed from the group, %2$s will be replaced by name and address of the contact who did the action -->
<string name="remove_member_by_other">%2$s видалив (-ла) учасника %1$s.</string> <string name="remove_member_by_other">%2$s видалив (-ла) учасника %1$s.</string>
<!-- "left" in the meaning of "exited". This string is added to a chat after groups, channels, broadcasts or mailinglists are left. If a subject is needed, "You left the chat." would work as well. -->
<string name="group_left_by_you">Ви пішли</string>
<!-- "left" in the meaning of "exited"; %1$s will be replaced by name and address of the contact leaving the group --> <!-- "left" in the meaning of "exited"; %1$s will be replaced by name and address of the contact leaving the group -->
<string name="group_left_by_other">%1$s залишив (-ла) групу.</string> <string name="group_left_by_other">%1$s залишив (-ла) групу.</string>
<string name="group_image_deleted_by_you">Ви видалили емблему групи.</string> <string name="group_image_deleted_by_you">Ви видалили емблему групи.</string>
@ -979,11 +1004,13 @@
<string name="ephemeral_timer_weeks_by_you">Ви встановили таймер зникнення повідомлень на %1$s тижнів.</string> <string name="ephemeral_timer_weeks_by_you">Ви встановили таймер зникнення повідомлень на %1$s тижнів.</string>
<!-- %1$s will be replaced by the number of weeks (always >1) the timer is set to, %2$s will be replaced by name and address of the contact --> <!-- %1$s will be replaced by the number of weeks (always >1) the timer is set to, %2$s will be replaced by name and address of the contact -->
<string name="ephemeral_timer_weeks_by_other">%2$s встановив (-ла) таймер зникнення повідомлень на %1$s тижнів.</string> <string name="ephemeral_timer_weeks_by_other">%2$s встановив (-ла) таймер зникнення повідомлень на %1$s тижнів.</string>
<!-- this may be shown instead of the chat's input field, with buttons "More Info" and "OK" --> <!-- deprecated -->
<string name="chat_protection_broken">%1$s тепер шле повідомлення з іншого пристрою.</string> <string name="chat_protection_broken">%1$s тепер шле повідомлення з іншого пристрою.</string>
<string name="chat_protection_enabled_tap_to_learn_more">Відтепер повідомлення гарантовано будуть мати наскрізне шифрування. Торкніться, щоб дізнатися більше.</string> <string name="chat_protection_enabled_tap_to_learn_more">Відтепер повідомлення гарантовано будуть мати наскрізне шифрування. Торкніться, щоб дізнатися більше.</string>
<string name="chat_protection_enabled_explanation">Тепер гарантовано, що всі повідомлення в цьому чаті наскрізь зашифровані.\n\nНаскрізне шифрування зберігає конфіденційність повідомлень між вами і вашими партнерами по чату. Навіть сервери, провайдери або ретранслятори не можуть їх прочитати.</string> <string name="chat_protection_enabled_explanation">Тепер гарантовано, що всі повідомлення в цьому чаті наскрізь зашифровані.\n\nНаскрізне шифрування зберігає конфіденційність повідомлень між вами і вашими партнерами по чату. Навіть сервери, провайдери або ретранслятори не можуть їх прочитати.</string>
<!-- deprecated -->
<string name="chat_protection_broken_tap_to_learn_more">%1$s відправив (-ла) повідомлення з іншого пристрою. Торкніться, щоб дізнатися більше.</string> <string name="chat_protection_broken_tap_to_learn_more">%1$s відправив (-ла) повідомлення з іншого пристрою. Торкніться, щоб дізнатися більше.</string>
<!-- deprecated -->
<string name="chat_protection_broken_explanation">Наскрізне шифрування більше не гарантується, імовірно, через те, що %1$s перевстановив (-ла) Delta Chat або надіслав (-ла) повідомлення з іншого пристрою.\n\nВи можете зустрітися з ним (нею) особисто та знову відсканувати його (її) QR-код, щоб відновити гарантоване наскрізне шифрування.</string> <string name="chat_protection_broken_explanation">Наскрізне шифрування більше не гарантується, імовірно, через те, що %1$s перевстановив (-ла) Delta Chat або надіслав (-ла) повідомлення з іншого пристрою.\n\nВи можете зустрітися з ним (нею) особисто та знову відсканувати його (її) QR-код, щоб відновити гарантоване наскрізне шифрування.</string>
<string name="invalid_unencrypted_tap_to_learn_more">⚠️ %1$s вимагає наскрізного шифрування, яке ще не налаштоване для цього чату. Натисніть, щоб дізнатися більше.</string> <string name="invalid_unencrypted_tap_to_learn_more">⚠️ %1$s вимагає наскрізного шифрування, яке ще не налаштоване для цього чату. Натисніть, щоб дізнатися більше.</string>
<string name="invalid_unencrypted_explanation">Для налагодження наскрізного шифрування можна зустрітись із контактною особою та відсканувати баркод із її пристрою, щоби представити її.</string> <string name="invalid_unencrypted_explanation">Для налагодження наскрізного шифрування можна зустрітись із контактною особою та відсканувати баркод із її пристрою, щоби представити її.</string>
@ -1045,13 +1072,16 @@
<string name="secure_join_wait">Встановлення гарантованого наскрізного шифрування, будь ласка, зачекайте...</string> <string name="secure_join_wait">Встановлення гарантованого наскрізного шифрування, будь ласка, зачекайте...</string>
<!-- deprecated --> <!-- deprecated -->
<string name="secure_join_wait_timeout">Ще не вдалося встановити гарантоване наскрізне шифрування, але ви вже можете надсилати повідомлення.</string> <string name="secure_join_wait_timeout">Ще не вдалося встановити гарантоване наскрізне шифрування, але ви вже можете надсилати повідомлення.</string>
<!-- deprecated, was stock string -->
<string name="secure_join_takes_longer">Щоб продовжити, контакт повинен бути онлайн.\n\nЦей процес продовжиться автоматично у фоновому режимі.</string> <string name="secure_join_takes_longer">Щоб продовжити, контакт повинен бути онлайн.\n\nЦей процес продовжиться автоматично у фоновому режимі.</string>
<string name="contact_verified">%1$s представлено!</string> <string name="contact_verified">%1$s представлено!</string>
<!-- deprecated, was stock string -->
<string name="contact_not_verified">Не вдається встановити гарантоване наскрізне шифрування з %1$s</string> <string name="contact_not_verified">Не вдається встановити гарантоване наскрізне шифрування з %1$s</string>
<!-- Shown in contact profile. The placeholder will be replaced by the name of the contact that introduced the contact. --> <!-- Shown in contact profile. The placeholder will be replaced by the name of the contact that introduced the contact. -->
<string name="verified_by">Представни·ця: %1$s</string> <string name="verified_by">Представни·ця: %1$s</string>
<string name="verified_by_you">Представлено мною</string> <string name="verified_by_you">Представлено мною</string>
<!-- translators: "setup" is the "encryption setup" here, as in "Autocrypt Setup Message" --> <string name="verified_by_unknown">Представлено</string>
<!-- deprecated, was stock string -->
<string name="contact_setup_changed">Змінені параметри для %1$s</string> <string name="contact_setup_changed">Змінені параметри для %1$s</string>
<string name="verified_contact_required_explain">Аби наскрізне шифрування лишалося ґарантованим, у цю групу можна додавати лише контактних осіб із зеленою галочкою.\n\nМожна зустрітись із контактною особою та відсканувати баркод із її пристрою, щоби представити її.</string> <string name="verified_contact_required_explain">Аби наскрізне шифрування лишалося ґарантованим, у цю групу можна додавати лише контактних осіб із зеленою галочкою.\n\nМожна зустрітись із контактною особою та відсканувати баркод із її пристрою, щоби представити її.</string>
<string name="mailto_dialog_header_select_chat">Виберіть чат, куди потрібно надіслати повідомлення</string> <string name="mailto_dialog_header_select_chat">Виберіть чат, куди потрібно надіслати повідомлення</string>
@ -1095,7 +1125,7 @@
<string name="ImageEditorHud_flip">Обернути</string> <string name="ImageEditorHud_flip">Обернути</string>
<string name="ImageEditorHud_rotate">Обертати</string> <string name="ImageEditorHud_rotate">Обертати</string>
<!-- dc_str_* resources --> <!-- deprecated, use string "E-Mail" for non-encrypted messages instead -->
<string name="encrypted_message">Зашифроване повідомлення</string> <string name="encrypted_message">Зашифроване повідомлення</string>
<!-- strings introduced on desktop. we want to share strings between the os, in general, please do not add generic strings here --> <!-- strings introduced on desktop. we want to share strings between the os, in general, please do not add generic strings here -->
@ -1226,6 +1256,9 @@
<string name="perm_enable_bg_already_done">Ви вже дозволили Delta Chat отримувати повідомлення у фоновому режимі.\n\nЯкщо повідомлення досі не приходять у фоновому режимі, перевірте налаштування системи.</string> <string name="perm_enable_bg_already_done">Ви вже дозволили Delta Chat отримувати повідомлення у фоновому режимі.\n\nЯкщо повідомлення досі не приходять у фоновому режимі, перевірте налаштування системи.</string>
<!-- device messages for updates --> <!-- device messages for updates -->
<string name="update_2_0">Що нового?\n\n💯 Наскрізне шифрування тепер надійне і завжди. Навісні замки 🔒 зникли!\n\n✉️ Класична електронна пошта без наскрізного шифрування позначається символом листа\n\n😻 Новий покращений екран профілю для всіх ваших контактів\n\n🔲 Нова кнопка для швидкого доступу до додатків, що використовуються в чаті\n\n❤️ Будь ласка, пожертвуйте, щоб допомогти нам залишатися незалежними та продовжувати вдосконалюватися: %1$s</string>
<!-- deprecated -->
<string name="update_1_50_android">Що нового? \n\n❤️‍🔥 Новий вибірник емодзі з більшою кількістю смайликів \n\n🎮 Покращені програми в чаті: отримуйте сповіщення та відкривайте додатки безпосередньо в контексті, наприклад, доданий запис у календарі \n\n👍 Отримуйте сповіщення про реакції на ваші повідомлення \n\n... 🛠️ ВИПРАВЛЕННЯ та ЩЕ БІЛЬШЕ на %1$s</string> <string name="update_1_50_android">Що нового? \n\n❤️‍🔥 Новий вибірник емодзі з більшою кількістю смайликів \n\n🎮 Покращені програми в чаті: отримуйте сповіщення та відкривайте додатки безпосередньо в контексті, наприклад, доданий запис у календарі \n\n👍 Отримуйте сповіщення про реакції на ваші повідомлення \n\n... 🛠️ ВИПРАВЛЕННЯ та ЩЕ БІЛЬШЕ на %1$s</string>
<!-- deprecated -->
<string name="update_switch_profile_placement">ℹ️ Опцію \"Перемкнути профіль\" переміщено: Торкніться зображення свого профілю у верхньому кутку головного екрану, щоб додати або перемкнути профіль 💡.</string> <string name="update_switch_profile_placement">ℹ️ Опцію \"Перемкнути профіль\" переміщено: Торкніться зображення свого профілю у верхньому кутку головного екрану, щоб додати або перемкнути профіль 💡.</string>
</resources> </resources>

12
src/main/res/values-vi/strings.xml
View file

@ -283,7 +283,6 @@
<!-- Menu item beside an app/chat that adds an icon to the system's home screen. If the user taps that icon, the app/chat is opened directly. --> <!-- Menu item beside an app/chat that adds an icon to the system's home screen. If the user taps that icon, the app/chat is opened directly. -->
<string name="add_to_home_screen">Thêm vào Màn hình chính</string> <string name="add_to_home_screen">Thêm vào Màn hình chính</string>
<string name="donate">Quyên tặng</string> <string name="donate">Quyên tặng</string>
<string name="mute_for_one_hour">Tắt tiếng trong 1 giờ</string> <string name="mute_for_one_hour">Tắt tiếng trong 1 giờ</string>
<string name="mute_for_eight_hours">Tắt tiếng trong 8 giờ</string> <string name="mute_for_eight_hours">Tắt tiếng trong 8 giờ</string>
<string name="mute_for_one_day">Tắt tiếng trong 1 ngày</string> <string name="mute_for_one_day">Tắt tiếng trong 1 ngày</string>
@ -458,7 +457,7 @@
<!-- option to show images in the gallery as square (instead of using correct width/height) --> <!-- option to show images in the gallery as square (instead of using correct width/height) -->
<string name="square_grid">Lưới vuông</string> <string name="square_grid">Lưới vuông</string>
<string name="send_message">Gửi tin nhắn</string> <string name="send_message">Gửi tin nhắn</string>
<!-- Placeholder %1$s will be replaced by the name of the contact changing their address. Placeholders %2$s and %3$s will be replaced by old/new addresses. --> <!-- deprecated, was stock string -->
<string name="aeap_addr_changed">%1$s đã thay đổi địa chỉ của họ từ %2$s thành %3$s</string> <string name="aeap_addr_changed">%1$s đã thay đổi địa chỉ của họ từ %2$s thành %3$s</string>
<!-- deprecated --> <!-- deprecated -->
<string name="aeap_explanation">Bạn đã thay đổi địa chỉ email của mình từ %1$s thành %2$s.\n\nNếu bây giờ bạn gửi thư đến một nhóm đã được xác minh, những người liên hệ ở đó sẽ tự động thay thế địa chỉ cũ bằng địa chỉ mới của bạn.\n\nĐiều đó thật tuyệt vời khuyên bạn nên thiết lập nhà cung cấp email cũ để chuyển tiếp tất cả email đến địa chỉ email mới của bạn. Nếu không, bạn có thể bỏ lỡ tin nhắn của những người chưa nhận được địa chỉ mới của bạn.</string> <string name="aeap_explanation">Bạn đã thay đổi địa chỉ email của mình từ %1$s thành %2$s.\n\nNếu bây giờ bạn gửi thư đến một nhóm đã được xác minh, những người liên hệ ở đó sẽ tự động thay thế địa chỉ cũ bằng địa chỉ mới của bạn.\n\nĐiều đó thật tuyệt vời khuyên bạn nên thiết lập nhà cung cấp email cũ để chuyển tiếp tất cả email đến địa chỉ email mới của bạn. Nếu không, bạn có thể bỏ lỡ tin nhắn của những người chưa nhận được địa chỉ mới của bạn.</string>
@ -787,11 +786,13 @@
<string name="ephemeral_timer_weeks_by_you">Bạn đặt bộ hẹn giờ cho tin nhắn biến mất thành %1$s tuần.</string> <string name="ephemeral_timer_weeks_by_you">Bạn đặt bộ hẹn giờ cho tin nhắn biến mất thành %1$s tuần.</string>
<!-- %1$s will be replaced by the number of weeks (always >1) the timer is set to, %2$s will be replaced by name and address of the contact --> <!-- %1$s will be replaced by the number of weeks (always >1) the timer is set to, %2$s will be replaced by name and address of the contact -->
<string name="ephemeral_timer_weeks_by_other">Bộ hẹn giờ cho tin nhắn biến mất được %2$s đặt thành %1$s tuần.</string> <string name="ephemeral_timer_weeks_by_other">Bộ hẹn giờ cho tin nhắn biến mất được %2$s đặt thành %1$s tuần.</string>
<!-- this may be shown instead of the chat's input field, with buttons "More Info" and "OK" --> <!-- deprecated -->
<string name="chat_protection_broken">%1$s đã gửi tin nhắn từ một thiết bị khác.</string> <string name="chat_protection_broken">%1$s đã gửi tin nhắn từ một thiết bị khác.</string>
<string name="chat_protection_enabled_tap_to_learn_more">Tin nhắn được đảm bảo sẽ được mã hóa hai đầu kể từ bây giờ. Nhấn để tìm hiểu thêm.</string> <string name="chat_protection_enabled_tap_to_learn_more">Tin nhắn được đảm bảo sẽ được mã hóa hai đầu kể từ bây giờ. Nhấn để tìm hiểu thêm.</string>
<string name="chat_protection_enabled_explanation">Hiện tại, chúng tôi đảm bảo rằng tất cả tin nhắn trong cuộc trò chuyện này đều được mã hóa hai đầu.\n\nMã hóa hai đầu giúp giữ tin nhắn giữa bạn và đối tác trò chuyện của bạn ở chế độ riêng tư. Ngay cả nhà cung cấp email của bạn cũng không thể đọc được chúng.</string> <string name="chat_protection_enabled_explanation">Hiện tại, chúng tôi đảm bảo rằng tất cả tin nhắn trong cuộc trò chuyện này đều được mã hóa hai đầu.\n\nMã hóa hai đầu giúp giữ tin nhắn giữa bạn và đối tác trò chuyện của bạn ở chế độ riêng tư. Ngay cả nhà cung cấp email của bạn cũng không thể đọc được chúng.</string>
<!-- deprecated -->
<string name="chat_protection_broken_tap_to_learn_more">%1$s đã gửi tin nhắn từ một thiết bị khác. Nhấn để tìm hiểu thêm.</string> <string name="chat_protection_broken_tap_to_learn_more">%1$s đã gửi tin nhắn từ một thiết bị khác. Nhấn để tìm hiểu thêm.</string>
<!-- deprecated -->
<string name="chat_protection_broken_explanation">Mã hóa hai đầu không còn được đảm bảo nữa, có thể vì %1$s đã cài đặt lại Delta Chat hoặc đã gửi tin nhắn từ một thiết bị khác.\n\nBạn có thể gặp trực tiếp họ và quét lại mã QR của họ để thiết lập lại tính năng mã hóa hai đầu được đảm bảo kết thúc mã hóa.</string> <string name="chat_protection_broken_explanation">Mã hóa hai đầu không còn được đảm bảo nữa, có thể vì %1$s đã cài đặt lại Delta Chat hoặc đã gửi tin nhắn từ một thiết bị khác.\n\nBạn có thể gặp trực tiếp họ và quét lại mã QR của họ để thiết lập lại tính năng mã hóa hai đầu được đảm bảo kết thúc mã hóa.</string>
<string name="learn_more">Tìm hiểu thêm</string> <string name="learn_more">Tìm hiểu thêm</string>
@ -846,11 +847,12 @@
<!-- placeholder will be replaced by the name of the inviter. --> <!-- placeholder will be replaced by the name of the inviter. -->
<string name="secure_join_replies">%1$s đã trả lời, đang chờ được thêm vào nhóm…</string> <string name="secure_join_replies">%1$s đã trả lời, đang chờ được thêm vào nhóm…</string>
<string name="contact_verified">%1$s đã được giới thiệu.</string> <string name="contact_verified">%1$s đã được giới thiệu.</string>
<!-- deprecated, was stock string -->
<string name="contact_not_verified">Không thể thiết lập mã hóa đầu cuối được đảm bảo với %1$s.</string> <string name="contact_not_verified">Không thể thiết lập mã hóa đầu cuối được đảm bảo với %1$s.</string>
<!-- Shown in contact profile. The placeholder will be replaced by the name of the contact that introduced the contact. --> <!-- Shown in contact profile. The placeholder will be replaced by the name of the contact that introduced the contact. -->
<string name="verified_by">Được giới thiệu bởi %1$s</string> <string name="verified_by">Được giới thiệu bởi %1$s</string>
<string name="verified_by_you">Được tôi giới thiệu</string> <string name="verified_by_you">Được tôi giới thiệu</string>
<!-- translators: "setup" is the "encryption setup" here, as in "Autocrypt Setup Message" --> <!-- deprecated, was stock string -->
<string name="contact_setup_changed">Đã thay đổi thiết lập cho %1$s.</string> <string name="contact_setup_changed">Đã thay đổi thiết lập cho %1$s.</string>
<string name="verified_contact_required_explain">Để đảm bảo mã hóa hai đầu, bạn chỉ có thể thêm những người liên hệ có dấu kiểm màu xanh lục vào nhóm này.\n\nBạn có thể gặp trực tiếp những người liên hệ và quét Mã QR của họ để giới thiệu họ.</string> <string name="verified_contact_required_explain">Để đảm bảo mã hóa hai đầu, bạn chỉ có thể thêm những người liên hệ có dấu kiểm màu xanh lục vào nhóm này.\n\nBạn có thể gặp trực tiếp những người liên hệ và quét Mã QR của họ để giới thiệu họ.</string>
<string name="mailto_dialog_header_select_chat">Chọn trò chuyện để gửi tin nhắn tới</string> <string name="mailto_dialog_header_select_chat">Chọn trò chuyện để gửi tin nhắn tới</string>
@ -892,7 +894,7 @@
<string name="ImageEditorHud_flip">Lật</string> <string name="ImageEditorHud_flip">Lật</string>
<string name="ImageEditorHud_rotate">Xoay</string> <string name="ImageEditorHud_rotate">Xoay</string>
<!-- dc_str_* resources --> <!-- deprecated, use string "E-Mail" for non-encrypted messages instead -->
<string name="encrypted_message">Tin nhắn được mã hóa</string> <string name="encrypted_message">Tin nhắn được mã hóa</string>
<!-- strings introduced on desktop. we want to share strings between the os, in general, please do not add generic strings here --> <!-- strings introduced on desktop. we want to share strings between the os, in general, please do not add generic strings here -->

56
src/main/res/values-zh-rCN/strings.xml
View file

@ -158,7 +158,7 @@
<!-- "Stickers" as known from other messengers; in some languages, the English "Sticker" is fine. --> <!-- "Stickers" as known from other messengers; in some languages, the English "Sticker" is fine. -->
<string name="sticker">贴纸</string> <string name="sticker">贴纸</string>
<string name="add_to_sticker_collection">添加到贴纸收藏集</string> <string name="add_to_sticker_collection">添加到贴纸收藏集</string>
<string name="add_stickers_instructions">要添加贴纸，请点击“打开贴纸文件夹”，为贴纸包创建一个子文件夹，然后将图片和贴纸文件拖动到那里</string> <string name="add_stickers_instructions">要添加贴纸，请点按“打开贴纸文件夹”，为贴纸包创建一个子文件夹，然后将图片和贴纸文件拖动到那里</string>
<string name="open_sticker_folder">打开贴纸文件夹</string> <string name="open_sticker_folder">打开贴纸文件夹</string>
<string name="images">图片</string> <string name="images">图片</string>
<string name="audio">音频</string> <string name="audio">音频</string>
@ -192,7 +192,7 @@
<string name="webxdc_apps">私人应用</string> <string name="webxdc_apps">私人应用</string>
<string name="webxdc_store_url">应用选择器 URL</string> <string name="webxdc_store_url">应用选择器 URL</string>
<string name="webxdc_store_url_explain">设置后，该 URL 而不是默认的 URL 将被用作“应用选择器”</string> <string name="webxdc_store_url_explain">设置后，该 URL 而不是默认的 URL 将被用作“应用选择器”</string>
<string name="webxdc_draft_hint">轻按“发送”分享</string> <string name="webxdc_draft_hint">点按“发送”即可分享</string>
<string name="home">首页</string> <string name="home">首页</string>
<string name="games">游戏</string> <string name="games">游戏</string>
<string name="tools">工具</string> <string name="tools">工具</string>
@ -242,16 +242,21 @@
<!-- consider keeping the term "channel" as in WhatsApp or Telegram --> <!-- consider keeping the term "channel" as in WhatsApp or Telegram -->
<string name="channels">频道</string> <string name="channels">频道</string>
<!-- consider keeping the term "channel" as in WhatsApp or Telegram --> <!-- consider keeping the term "channel" as in WhatsApp or Telegram -->
<string name="new_channel">新频道</string> <string name="new_channel">新建频道</string>
<string name="add_recipients">添加接收者</string> <string name="add_recipients">添加接收者</string>
<!-- deprecated --> <!-- deprecated -->
<string name="edit_broadcast_list">编辑广播列表</string> <string name="edit_broadcast_list">编辑广播列表</string>
<!-- deprecated --> <!-- deprecated -->
<string name="broadcast_list_name">广播列表名称</string> <string name="broadcast_list_name">广播列表名称</string>
<!-- deprecated --> <!-- deprecated -->
<string name="please_enter_broadcast_list_name">请属于广播列表的名称</string> <string name="please_enter_broadcast_list_name">请输入广播列表的名称。</string>
<!-- consider keeping the term "channel" as in WhatsApp or Telegram --> <!-- consider keeping the term "channel" as in WhatsApp or Telegram -->
<string name="channel_name">频道名称</string> <string name="channel_name">频道名称</string>
<string name="email">邮件</string>
<!-- "New" as in "Create New E-Mail"; shown together with "New Group" and "New Channel" -->
<string name="new_email">新建邮件</string>
<!-- the "Subject" of an e-mail, use the term common in classic e-mail apps -->
<string name="subject">主题</string>
<string name="menu_send">发送</string> <string name="menu_send">发送</string>
<string name="menu_toggle_keyboard">切换表情符号键盘</string> <string name="menu_toggle_keyboard">切换表情符号键盘</string>
<string name="menu_edit_group">编辑群组</string> <string name="menu_edit_group">编辑群组</string>
@ -346,6 +351,7 @@
<!-- Menu item beside an app/chat that adds an icon to the system's home screen. If the user taps that icon, the app/chat is opened directly. --> <!-- Menu item beside an app/chat that adds an icon to the system's home screen. If the user taps that icon, the app/chat is opened directly. -->
<string name="add_to_home_screen">添加到主屏幕</string> <string name="add_to_home_screen">添加到主屏幕</string>
<string name="donate">捐赠</string> <string name="donate">捐赠</string>
<string name="donate_device_msg">❤️ 看起来您很喜欢 Delta Chat！\n\n恳请您考虑捐款支持，让 Delta Chat 始终保持自由开放。\n\n虽然 Delta Chat 是自由且开源的，但开发仍需资金支持。请帮助我们保持 Delta Chat 的独立性，并在未来让它变得更加出色。\n\nhttps://delta.chat/donate</string>
<string name="mute_for_one_hour">静音 1 小时</string> <string name="mute_for_one_hour">静音 1 小时</string>
<string name="mute_for_eight_hours">静音 8 小时</string> <string name="mute_for_eight_hours">静音 8 小时</string>
@ -369,8 +375,8 @@
<string name="videochat_invite_user_hint">需要双方均装有兼容的应用或浏览器。</string> <string name="videochat_invite_user_hint">需要双方均装有兼容的应用或浏览器。</string>
<string name="videochat_contact_invited_hint">%1$s 发出了视频聊天邀请。</string> <string name="videochat_contact_invited_hint">%1$s 发出了视频聊天邀请。</string>
<string name="videochat_you_invited_hint">您发出了视频聊天邀请。</string> <string name="videochat_you_invited_hint">您发出了视频聊天邀请。</string>
<string name="videochat_tap_to_join">点击来加入</string> <string name="videochat_tap_to_join">点按即可加入</string>
<string name="videochat_tap_to_open">点击来打开</string> <string name="videochat_tap_to_open">点按即可打开</string>
<string name="videochat_instance">视频聊天实例</string> <string name="videochat_instance">视频聊天实例</string>
<string name="videochat_instance_placeholder">您的视频聊天实例</string> <string name="videochat_instance_placeholder">您的视频聊天实例</string>
<!-- Do not translate "$ROOM", since it is a fixed token Delta Chat will replace with a generated room ID like "aOclju5eCky" --> <!-- Do not translate "$ROOM", since it is a fixed token Delta Chat will replace with a generated room ID like "aOclju5eCky" -->
@ -441,7 +447,7 @@
<string name="chat_new_channel_hint">频道是广播消息的一对多工具。</string> <string name="chat_new_channel_hint">频道是广播消息的一对多工具。</string>
<string name="chat_new_group_hint">在您发出第一条消息后，其他人才会看到此群组。</string> <string name="chat_new_group_hint">在您发出第一条消息后，其他人才会看到此群组。</string>
<string name="chat_record_slide_to_cancel">滑动来取消</string> <string name="chat_record_slide_to_cancel">滑动来取消</string>
<string name="chat_record_explain">按住来录制语音消息，松开来发送</string> <string name="chat_record_explain">按住即可录制语音消息，松开即可发送</string>
<string name="chat_no_chats_yet_title">收件箱为空。\n按“+”来开始新聊天。</string> <string name="chat_no_chats_yet_title">收件箱为空。\n按“+”来开始新聊天。</string>
<string name="chat_all_archived">所有聊天已归档。\n按“+”来开始新聊天。</string> <string name="chat_all_archived">所有聊天已归档。\n按“+”来开始新聊天。</string>
<string name="chat_share_with_title">分享给</string> <string name="chat_share_with_title">分享给</string>
@ -547,7 +553,7 @@
<!-- option to show images in the gallery as square (instead of using correct width/height) --> <!-- option to show images in the gallery as square (instead of using correct width/height) -->
<string name="square_grid">方形网格</string> <string name="square_grid">方形网格</string>
<string name="send_message">发送消息</string> <string name="send_message">发送消息</string>
<!-- Placeholder %1$s will be replaced by the name of the contact changing their address. Placeholders %2$s and %3$s will be replaced by old/new addresses. --> <!-- deprecated, was stock string -->
<string name="aeap_addr_changed">%1$s 将邮箱从 %2$s 更改为 %3$s</string> <string name="aeap_addr_changed">%1$s 将邮箱从 %2$s 更改为 %3$s</string>
<!-- deprecated --> <!-- deprecated -->
<string name="aeap_explanation">你将邮箱从 %1$s 改为了 %2$s。\n\n如果你现在发送一条消息到已验证群组，那里的联系人将自动用你的新邮箱替换旧邮箱。\n\n我们建议你将旧邮箱配置为转发所有邮件到新邮箱。否则，你可能收不到还不知道你新邮箱的联系人发过来的消息。</string> <string name="aeap_explanation">你将邮箱从 %1$s 改为了 %2$s。\n\n如果你现在发送一条消息到已验证群组，那里的联系人将自动用你的新邮箱替换旧邮箱。\n\n我们建议你将旧邮箱配置为转发所有邮件到新邮箱。否则，你可能收不到还不知道你新邮箱的联系人发过来的消息。</string>
@ -560,7 +566,7 @@
<string name="multidevice_this_creates_a_qr_code">这将创建一个二维码，第二台设备可以扫描该二维码来复制配置文件。\n\n请确保没有不必要的观察者或摄像机可以看到以下屏幕。</string> <string name="multidevice_this_creates_a_qr_code">这将创建一个二维码，第二台设备可以扫描该二维码来复制配置文件。\n\n请确保没有不必要的观察者或摄像机可以看到以下屏幕。</string>
<string name="multidevice_install_dc_on_other_device">在你的其他设备上安装 Delta Chat (https://get.delta.chat)</string> <string name="multidevice_install_dc_on_other_device">在你的其他设备上安装 Delta Chat (https://get.delta.chat)</string>
<!-- "I Already Have a Profile / Add as Second Device” should be the same text as defined by the keys onboarding_alternative_logins and multidevice_receiver_title --> <!-- "I Already Have a Profile / Add as Second Device” should be the same text as defined by the keys onboarding_alternative_logins and multidevice_receiver_title -->
<string name="multidevice_tap_scan_on_other_device">启动 Delta Chat，点击“我已有账号/添加为第二台设备”，扫描此处显示的二维码</string> <string name="multidevice_tap_scan_on_other_device">启动 Delta Chat，点按“我已有账号/添加为第二台设备”，然后扫描此处显示的二维码</string>
<!-- Shown inside a "QR code card" with very limited space; please formulate the text as short as possible therefore. The placeholder will be replaced by name and/or address eg. "Scan to set up second device for Alice (alice@example.org)" --> <!-- Shown inside a "QR code card" with very limited space; please formulate the text as short as possible therefore. The placeholder will be replaced by name and/or address eg. "Scan to set up second device for Alice (alice@example.org)" -->
<string name="multidevice_qr_subtitle">扫描此处为 %1$s 设置第二台设备</string> <string name="multidevice_qr_subtitle">扫描此处为 %1$s 设置第二台设备</string>
<string name="multidevice_receiver_title">添加为第二台设备</string> <string name="multidevice_receiver_title">添加为第二台设备</string>
@ -950,13 +956,15 @@
<string name="ephemeral_timer_weeks_by_you">你将消息定时销毁计时器设为 %1$s 周</string> <string name="ephemeral_timer_weeks_by_you">你将消息定时销毁计时器设为 %1$s 周</string>
<!-- %1$s will be replaced by the number of weeks (always >1) the timer is set to, %2$s will be replaced by name and address of the contact --> <!-- %1$s will be replaced by the number of weeks (always >1) the timer is set to, %2$s will be replaced by name and address of the contact -->
<string name="ephemeral_timer_weeks_by_other">%2$s 将消息定时销毁计时器设为 %1$s 周</string> <string name="ephemeral_timer_weeks_by_other">%2$s 将消息定时销毁计时器设为 %1$s 周</string>
<!-- this may be shown instead of the chat's input field, with buttons "More Info" and "OK" --> <!-- deprecated -->
<string name="chat_protection_broken">%1$s 从另一台设备发送了消息</string> <string name="chat_protection_broken">%1$s 从另一台设备发送了消息</string>
<string name="chat_protection_enabled_tap_to_learn_more">从现在起，消息保证都是端到端加密。轻按了解更多。</string> <string name="chat_protection_enabled_tap_to_learn_more">消息是端到端加密的。点按即可了解详情。</string>
<string name="chat_protection_enabled_explanation">现在可以保证此聊天中的所有消息都是端到端加密的。\n\n端到端加密可确保您和您的聊天伙伴之间的消息私密性。即使是服务器、提供者或中继也无法读取它们。</string> <string name="chat_protection_enabled_explanation">此聊天中的所有消息都经过端到端加密。\n\n端到端加密可确保您与聊天对象之间的消息保持私密。即使是服务器、提供者或中继也无法读取。</string>
<string name="chat_protection_broken_tap_to_learn_more">%1$s 从另一台设备发送了一则消息。轻按了解更多。</string> <!-- deprecated -->
<string name="chat_protection_broken_tap_to_learn_more">%1$s 从另一台设备发送了一条消息。点按即可了解详情。</string>
<!-- deprecated -->
<string name="chat_protection_broken_explanation">无法再确保端到端加密，可能的原因是 %1$s 重新安装了 Delta Chat 或从其他设备发送了一则消息。\n\n你可以和联系人线下见面并再次扫描联系人的二维码重新建立端到端加密的通信。</string> <string name="chat_protection_broken_explanation">无法再确保端到端加密，可能的原因是 %1$s 重新安装了 Delta Chat 或从其他设备发送了一则消息。\n\n你可以和联系人线下见面并再次扫描联系人的二维码重新建立端到端加密的通信。</string>
<string name="invalid_unencrypted_tap_to_learn_more">⚠️ %1$s要求端到端加密，而此聊天尚未建立端到端加密。轻按了解更多。</string> <string name="invalid_unencrypted_tap_to_learn_more">⚠️ %1$s 需要端到端加密，但此聊天尚未设置。点按即可了解详情。</string>
<string name="invalid_unencrypted_explanation">要建立端到端加密，你可以亲自和联系人碰面并扫描联系人的二维码</string> <string name="invalid_unencrypted_explanation">要建立端到端加密，你可以亲自和联系人碰面并扫描联系人的二维码</string>
<string name="learn_more">了解更多</string> <string name="learn_more">了解更多</string>
@ -1013,16 +1021,19 @@
<string name="secure_join_started">%1$s 邀请你加入此群组。\n\n等待 %2$s 的设备回复…</string> <string name="secure_join_started">%1$s 邀请你加入此群组。\n\n等待 %2$s 的设备回复…</string>
<!-- placeholder will be replaced by the name of the inviter. --> <!-- placeholder will be replaced by the name of the inviter. -->
<string name="secure_join_replies">%1$s 已回复，等待被加入群组…</string> <string name="secure_join_replies">%1$s 已回复，等待被加入群组…</string>
<string name="secure_join_wait">正在建立有保证的端到端加密，请稍候…</string> <string name="secure_join_wait">正在建立端到端加密，请稍候…</string>
<!-- deprecated --> <!-- deprecated -->
<string name="secure_join_wait_timeout">无法建立有保证的端到端加密，但您可能已经发送了一条消息。</string> <string name="secure_join_wait_timeout">无法建立有保证的端到端加密，但您可能已经发送了一条消息。</string>
<!-- deprecated, was stock string -->
<string name="secure_join_takes_longer">联系人必须在线才能继续。\n\n此过程将在后台自动继续。</string> <string name="secure_join_takes_longer">联系人必须在线才能继续。\n\n此过程将在后台自动继续。</string>
<string name="contact_verified">%1$s 已验证。</string> <string name="contact_verified">%1$s 已验证。</string>
<string name="contact_not_verified">无法与 %1$s 建立有保证的端到端加密。</string> <!-- deprecated, was stock string -->
<string name="contact_not_verified">无法与 %1$s 建立端到端加密。</string>
<!-- Shown in contact profile. The placeholder will be replaced by the name of the contact that introduced the contact. --> <!-- Shown in contact profile. The placeholder will be replaced by the name of the contact that introduced the contact. -->
<string name="verified_by">验证人 %1$s</string> <string name="verified_by">验证人 %1$s</string>
<string name="verified_by_you">由您验证</string> <string name="verified_by_you">由您验证</string>
<!-- translators: "setup" is the "encryption setup" here, as in "Autocrypt Setup Message" --> <string name="verified_by_unknown">已验证</string>
<!-- deprecated, was stock string -->
<string name="contact_setup_changed">%1$s 的加密设置已更改。</string> <string name="contact_setup_changed">%1$s 的加密设置已更改。</string>
<string name="verified_contact_required_explain">要确保端到端加密，你只能将带有绿色验证标识的联系人到此群中。\n\n你可以亲自和未验证联系人线下碰面并扫描联系人二维码来验证。</string> <string name="verified_contact_required_explain">要确保端到端加密，你只能将带有绿色验证标识的联系人到此群中。\n\n你可以亲自和未验证联系人线下碰面并扫描联系人二维码来验证。</string>
<string name="mailto_dialog_header_select_chat">选择要发送消息的聊天</string> <string name="mailto_dialog_header_select_chat">选择要发送消息的聊天</string>
@ -1066,7 +1077,7 @@
<string name="ImageEditorHud_flip">翻转</string> <string name="ImageEditorHud_flip">翻转</string>
<string name="ImageEditorHud_rotate">旋转</string> <string name="ImageEditorHud_rotate">旋转</string>
<!-- dc_str_* resources --> <!-- deprecated, use string "E-Mail" for non-encrypted messages instead -->
<string name="encrypted_message">加密的消息</string> <string name="encrypted_message">加密的消息</string>
<!-- strings introduced on desktop. we want to share strings between the os, in general, please do not add generic strings here --> <!-- strings introduced on desktop. we want to share strings between the os, in general, please do not add generic strings here -->
@ -1141,8 +1152,8 @@
<!-- iOS specific strings, developers: please take care to remove strings that are no longer used! --> <!-- iOS specific strings, developers: please take care to remove strings that are no longer used! -->
<string name="stop_sharing_location">停止共享位置</string> <string name="stop_sharing_location">停止共享位置</string>
<string name="a11y_voice_message_hint_ios">录音后轻按两次发送。要丢弃录音，用两根手指左右滑动。</string> <string name="a11y_voice_message_hint_ios">录制后，点按两次即可发送。如需舍弃录制内容，请双指滑动。</string>
<string name="a11y_connectivity_hint">轻按两次查看连接详情</string> <string name="a11y_connectivity_hint">点按两次即可查看连接详情</string>
<string name="login_error_no_internet_connection">无互联网连接，登录失败。</string> <string name="login_error_no_internet_connection">无互联网连接，登录失败。</string>
<string name="share_account_not_configured">账号未配置。</string> <string name="share_account_not_configured">账号未配置。</string>
<string name="cannot_play_audio_file">无法播放音频文件。</string> <string name="cannot_play_audio_file">无法播放音频文件。</string>
@ -1193,10 +1204,13 @@
<string name="pref_background_notifications_rationale">为了保持连接并在后台接收消息，请在下一步中忽略电池优化。\n\nDelta Chat 使用的资源很少，并且会注意不去耗尽电池电量。</string> <string name="pref_background_notifications_rationale">为了保持连接并在后台接收消息，请在下一步中忽略电池优化。\n\nDelta Chat 使用的资源很少，并且会注意不去耗尽电池电量。</string>
<!-- disabling "Reliable service" will hide a the maybe annoying permanent-notification with the drawback that new-message-notifications get potentially unreliable --> <!-- disabling "Reliable service" will hide a the maybe annoying permanent-notification with the drawback that new-message-notifications get potentially unreliable -->
<string name="perm_enable_bg_reminder_title">点击此处以在 Delta Chat 处于后台时接收消息。</string> <string name="perm_enable_bg_reminder_title">点按此处即可在 Delta Chat 处于后台时接收消息。</string>
<string name="perm_enable_bg_already_done">您已允许 Delta Chat 在后台接收消息。\n\n若 Delta Chat 在后台时消息仍未到达，请检查系统设置。</string> <string name="perm_enable_bg_already_done">您已允许 Delta Chat 在后台接收消息。\n\n若 Delta Chat 在后台时消息仍未到达，请检查系统设置。</string>
<!-- device messages for updates --> <!-- device messages for updates -->
<string name="update_2_0">新版变化?\n\n💯 端到端加密现在可靠且永久。挂锁图标 🔒 没有了!\n\n✉️ 没有端到端加密的经典电子邮件用字母符号标记l\n\n😻 所有联系人的新的增强的个人资料屏\n\n🔲 新增快速访问聊天中所用应用的按钮\n\n❤️ 请捐赠帮助我们保持独立并继续带来改进: %1$s</string>
<!-- deprecated -->
<string name="update_1_50_android">有什么新功能？\n\n❤️‍🔥 新的表情符号选择器，包含更多表情符号\n\n🎮 增强的聊天应用：获取通知并在上下文中打开支持应用，即直接打开添加的日历条目\n\n👍 收到有关对您的消息的回应的通知\n\n…🛠️ %1$s 上的修复和更多内容</string> <string name="update_1_50_android">有什么新功能？\n\n❤️‍🔥 新的表情符号选择器，包含更多表情符号\n\n🎮 增强的聊天应用：获取通知并在上下文中打开支持应用，即直接打开添加的日历条目\n\n👍 收到有关对您的消息的回应的通知\n\n…🛠️ %1$s 上的修复和更多内容</string>
<!-- deprecated -->
<string name="update_switch_profile_placement">ℹ️ “切换账号”选项已移动：点击主屏幕上角的个人资料图片以添加或切换账号 💡</string> <string name="update_switch_profile_placement">ℹ️ “切换账号”选项已移动：点击主屏幕上角的个人资料图片以添加或切换账号 💡</string>
</resources> </resources>

16
src/main/res/values-zh-rTW/strings.xml
View file

@ -337,7 +337,6 @@
<!-- Menu item beside an app/chat that adds an icon to the system's home screen. If the user taps that icon, the app/chat is opened directly. --> <!-- Menu item beside an app/chat that adds an icon to the system's home screen. If the user taps that icon, the app/chat is opened directly. -->
<string name="add_to_home_screen">新增至主畫面</string> <string name="add_to_home_screen">新增至主畫面</string>
<string name="donate">捐贈</string> <string name="donate">捐贈</string>
<string name="mute_for_one_hour">靜音1小時</string> <string name="mute_for_one_hour">靜音1小時</string>
<string name="mute_for_eight_hours">靜音8小時</string> <string name="mute_for_eight_hours">靜音8小時</string>
<string name="mute_for_one_day">靜音1天</string> <string name="mute_for_one_day">靜音1天</string>
@ -531,7 +530,7 @@
<!-- option to show images in the gallery as square (instead of using correct width/height) --> <!-- option to show images in the gallery as square (instead of using correct width/height) -->
<string name="square_grid">方形網格</string> <string name="square_grid">方形網格</string>
<string name="send_message">傳送訊息</string> <string name="send_message">傳送訊息</string>
<!-- Placeholder %1$s will be replaced by the name of the contact changing their address. Placeholders %2$s and %3$s will be replaced by old/new addresses. --> <!-- deprecated, was stock string -->
<string name="aeap_addr_changed">%1$s 已將他的位址從 %2$s更改 為 %3$s</string> <string name="aeap_addr_changed">%1$s 已將他的位址從 %2$s更改 為 %3$s</string>
<!-- deprecated --> <!-- deprecated -->
<string name="aeap_explanation">您已將電子郵件位址從%1$s更改為%2$s 。\n\n如果您現在向已驗證的群組發送消息，那裡的聯絡人會自動將舊位址替換為您的新位址。\n\n強烈建議您將舊電子郵件供應商設置為將所有電子郵件轉發到您的新電子郵件位址。否則，您可能會錯過尚未獲得新地址的聯絡人的消息。</string> <string name="aeap_explanation">您已將電子郵件位址從%1$s更改為%2$s 。\n\n如果您現在向已驗證的群組發送消息，那裡的聯絡人會自動將舊位址替換為您的新位址。\n\n強烈建議您將舊電子郵件供應商設置為將所有電子郵件轉發到您的新電子郵件位址。否則，您可能會錯過尚未獲得新地址的聯絡人的消息。</string>
@ -932,11 +931,13 @@
<string name="ephemeral_timer_weeks_by_you">您將自動刪除訊息計時器設置為%1$s週。</string> <string name="ephemeral_timer_weeks_by_you">您將自動刪除訊息計時器設置為%1$s週。</string>
<!-- %1$s will be replaced by the number of weeks (always >1) the timer is set to, %2$s will be replaced by name and address of the contact --> <!-- %1$s will be replaced by the number of weeks (always >1) the timer is set to, %2$s will be replaced by name and address of the contact -->
<string name="ephemeral_timer_weeks_by_other">%2$s將自動刪除訊息計時器設置為%1$s週。</string> <string name="ephemeral_timer_weeks_by_other">%2$s將自動刪除訊息計時器設置為%1$s週。</string>
<!-- this may be shown instead of the chat's input field, with buttons "More Info" and "OK" --> <!-- deprecated -->
<string name="chat_protection_broken">%1$s從另一台裝置傳送了一條訊息。</string> <string name="chat_protection_broken">%1$s從另一台裝置傳送了一條訊息。</string>
<string name="chat_protection_enabled_tap_to_learn_more">從現在開始，保證消息進行端到端加密。輕觸以瞭解更多資訊。</string> <string name="chat_protection_enabled_tap_to_learn_more">從現在開始，保證消息進行端到端加密。輕觸以瞭解更多資訊。</string>
<string name="chat_protection_enabled_explanation">現在可以保證此聊天中的所有消息都是端到端加密的。\n\n端到端加密使您和您的聊天夥伴之間的消息保持私密。甚至您的電子郵件供應商也無法讀取它們。</string> <string name="chat_protection_enabled_explanation">現在可以保證此聊天中的所有消息都是端到端加密的。\n\n端到端加密使您和您的聊天夥伴之間的消息保持私密。甚至您的電子郵件供應商也無法讀取它們。</string>
<!-- deprecated -->
<string name="chat_protection_broken_tap_to_learn_more">%1$s從另一台裝置傳送了一條訊息。輕觸以瞭解更多資訊。</string> <string name="chat_protection_broken_tap_to_learn_more">%1$s從另一台裝置傳送了一條訊息。輕觸以瞭解更多資訊。</string>
<!-- deprecated -->
<string name="chat_protection_broken_explanation">無法再保證端到端加密，可能是因為%1$s重新安裝了 Delta Chat 或從其他裝置傳送了訊息\n\n您可以再次當面掃描他們的QR碼，以重新建立有保證的端到端加密。</string> <string name="chat_protection_broken_explanation">無法再保證端到端加密，可能是因為%1$s重新安裝了 Delta Chat 或從其他裝置傳送了訊息\n\n您可以再次當面掃描他們的QR碼，以重新建立有保證的端到端加密。</string>
<string name="invalid_unencrypted_tap_to_learn_more">⚠️ %1$s需要端到端加密，但尚未為此聊天設置。輕觸以瞭解更多資訊。</string> <string name="invalid_unencrypted_tap_to_learn_more">⚠️ %1$s需要端到端加密，但尚未為此聊天設置。輕觸以瞭解更多資訊。</string>
<string name="invalid_unencrypted_explanation">要建立端到端加密，您可以當面掃描聯絡人的QR碼。</string> <string name="invalid_unencrypted_explanation">要建立端到端加密，您可以當面掃描聯絡人的QR碼。</string>
@ -998,13 +999,15 @@
<string name="secure_join_wait">正在建立有保證的端到端加密，請稍候...</string> <string name="secure_join_wait">正在建立有保證的端到端加密，請稍候...</string>
<!-- deprecated --> <!-- deprecated -->
<string name="secure_join_wait_timeout">尚無法建立有保證的端到端加密，但您可能已經送出了一條訊息。</string> <string name="secure_join_wait_timeout">尚無法建立有保證的端到端加密，但您可能已經送出了一條訊息。</string>
<!-- deprecated, was stock string -->
<string name="secure_join_takes_longer">聯繫人必須處於連線狀態才能繼續。\n\n此過程將在後台自動繼續。</string> <string name="secure_join_takes_longer">聯繫人必須處於連線狀態才能繼續。\n\n此過程將在後台自動繼續。</string>
<string name="contact_verified">%1$s已介紹。</string> <string name="contact_verified">%1$s已介紹。</string>
<!-- deprecated, was stock string -->
<string name="contact_not_verified">無法與%1$s建立有保證的端到端加密。</string> <string name="contact_not_verified">無法與%1$s建立有保證的端到端加密。</string>
<!-- Shown in contact profile. The placeholder will be replaced by the name of the contact that introduced the contact. --> <!-- Shown in contact profile. The placeholder will be replaced by the name of the contact that introduced the contact. -->
<string name="verified_by">由%1$s介紹</string> <string name="verified_by">由%1$s介紹</string>
<string name="verified_by_you">由我介紹</string> <string name="verified_by_you">由我介紹</string>
<!-- translators: "setup" is the "encryption setup" here, as in "Autocrypt Setup Message" --> <!-- deprecated, was stock string -->
<string name="contact_setup_changed">已爲%1$s更改設定。</string> <string name="contact_setup_changed">已爲%1$s更改設定。</string>
<string name="verified_contact_required_explain">為了保證端到端加密，您只能將帶有綠色驗證標識的聯絡人添加到此群組。\n\n您可以當面掃描聯絡人的QR碼以介紹他們。</string> <string name="verified_contact_required_explain">為了保證端到端加密，您只能將帶有綠色驗證標識的聯絡人添加到此群組。\n\n您可以當面掃描聯絡人的QR碼以介紹他們。</string>
<string name="mailto_dialog_header_select_chat">選擇要將消息發送到的聊天</string> <string name="mailto_dialog_header_select_chat">選擇要將消息發送到的聊天</string>
@ -1048,7 +1051,7 @@
<string name="ImageEditorHud_flip">翻轉</string> <string name="ImageEditorHud_flip">翻轉</string>
<string name="ImageEditorHud_rotate">旋轉</string> <string name="ImageEditorHud_rotate">旋轉</string>
<!-- dc_str_* resources --> <!-- deprecated, use string "E-Mail" for non-encrypted messages instead -->
<string name="encrypted_message">已加密的訊息</string> <string name="encrypted_message">已加密的訊息</string>
<!-- strings introduced on desktop. we want to share strings between the os, in general, please do not add generic strings here --> <!-- strings introduced on desktop. we want to share strings between the os, in general, please do not add generic strings here -->
@ -1178,7 +1181,8 @@
<string name="perm_enable_bg_reminder_title">點擊此處可在 Delta Chat 處於後台時接收訊息。</string> <string name="perm_enable_bg_reminder_title">點擊此處可在 Delta Chat 處於後台時接收訊息。</string>
<string name="perm_enable_bg_already_done">您已經允許 Delta Chat 在後台接收訊息。\n\n如果消息仍未在後台到達，請同時檢查您的系統設定。</string> <string name="perm_enable_bg_already_done">您已經允許 Delta Chat 在後台接收訊息。\n\n如果消息仍未在後台到達，請同時檢查您的系統設定。</string>
<!-- device messages for updates --> <!-- deprecated -->
<string name="update_1_50_android">新功能\n\n❤️ 🔥 新的表情符號選擇器，包含更多表情符號\n\n🎮 增強的聊天應用程式：在上下文中獲取通知並打開支援應用程式，即直接打開添加的日曆條目\n\n👍獲取有關對您的消訊息的回應的通知\n\n...🛠️ 修復以及更多在%1$s</string> <string name="update_1_50_android">新功能\n\n❤️ 🔥 新的表情符號選擇器，包含更多表情符號\n\n🎮 增強的聊天應用程式：在上下文中獲取通知並打開支援應用程式，即直接打開添加的日曆條目\n\n👍獲取有關對您的消訊息的回應的通知\n\n...🛠️ 修復以及更多在%1$s</string>
<!-- deprecated -->
<string name="update_switch_profile_placement">ℹ️「切換賬戶」選項已移動：點擊主螢幕右上角的賬戶大頭貼以添加或切換賬戶 💡</string> <string name="update_switch_profile_placement">ℹ️「切換賬戶」選項已移動：點擊主螢幕右上角的賬戶大頭貼以添加或切換賬戶 💡</string>
</resources> </resources>

25
src/main/res/values/strings.xml
View file

@ -261,6 +261,7 @@
<string name="please_enter_broadcast_list_name">Please enter a name for the broadcast list.</string> <string name="please_enter_broadcast_list_name">Please enter a name for the broadcast list.</string>
<!-- consider keeping the term "channel" as in WhatsApp or Telegram --> <!-- consider keeping the term "channel" as in WhatsApp or Telegram -->
<string name="channel_name">Channel Name</string> <string name="channel_name">Channel Name</string>
<string name="email">E-Mail</string>
<!-- "New" as in "Create New E-Mail"; shown together with "New Group" and "New Channel" --> <!-- "New" as in "Create New E-Mail"; shown together with "New Group" and "New Channel" -->
<string name="new_email">New E-Mail</string> <string name="new_email">New E-Mail</string>
<!-- the "Subject" of an e-mail, use the term common in classic e-mail apps --> <!-- the "Subject" of an e-mail, use the term common in classic e-mail apps -->
@ -568,7 +569,7 @@
<!-- option to show images in the gallery as square (instead of using correct width/height) --> <!-- option to show images in the gallery as square (instead of using correct width/height) -->
<string name="square_grid">Square Grid</string> <string name="square_grid">Square Grid</string>
<string name="send_message">Send Message</string> <string name="send_message">Send Message</string>
<!-- Placeholder %1$s will be replaced by the name of the contact changing their address. Placeholders %2$s and %3$s will be replaced by old/new addresses. --> <!-- deprecated, was stock string -->
<string name="aeap_addr_changed">%1$s changed their address from %2$s to %3$s</string> <string name="aeap_addr_changed">%1$s changed their address from %2$s to %3$s</string>
<!-- deprecated --> <!-- deprecated -->
<string name="aeap_explanation">You changed your email address from %1$s to %2$s.\n\nIf you now send a message to a verified group, contacts there will automatically replace the old with your new address.\n\nIt\'s highly advised to set up your old email provider to forward all emails to your new email address. Otherwise you might miss messages of contacts who did not get your new address yet.</string> <string name="aeap_explanation">You changed your email address from %1$s to %2$s.\n\nIf you now send a message to a verified group, contacts there will automatically replace the old with your new address.\n\nIt\'s highly advised to set up your old email provider to forward all emails to your new email address. Otherwise you might miss messages of contacts who did not get your new address yet.</string>
@ -971,11 +972,13 @@
<string name="ephemeral_timer_weeks_by_you">You set disappearing messages timer to %1$s weeks.</string> <string name="ephemeral_timer_weeks_by_you">You set disappearing messages timer to %1$s weeks.</string>
<!-- %1$s will be replaced by the number of weeks (always >1) the timer is set to, %2$s will be replaced by name and address of the contact --> <!-- %1$s will be replaced by the number of weeks (always >1) the timer is set to, %2$s will be replaced by name and address of the contact -->
<string name="ephemeral_timer_weeks_by_other">Disappearing messages timer set to %1$s weeks by %2$s.</string> <string name="ephemeral_timer_weeks_by_other">Disappearing messages timer set to %1$s weeks by %2$s.</string>
<!-- this may be shown instead of the chat's input field, with buttons "More Info" and "OK" --> <!-- deprecated -->
<string name="chat_protection_broken">%1$s sent a message from another device.</string> <string name="chat_protection_broken">%1$s sent a message from another device.</string>
<string name="chat_protection_enabled_tap_to_learn_more">Messages are guaranteed to be end-to-end encrypted from now on. Tap to learn more.</string> <string name="chat_protection_enabled_tap_to_learn_more">Messages are end-to-end encrypted. Tap to learn more.</string>
<string name="chat_protection_enabled_explanation">It is now guaranteed that all messages in this chat are end-to-end encrypted.\n\nEnd-to-end encryption keeps messages private between you and your chat partners. Not even servers, providers or relays can read them.</string> <string name="chat_protection_enabled_explanation">All messages in this chat are end-to-end encrypted.\n\nEnd-to-end encryption keeps messages private between you and your chat partners. Not even servers, providers or relays can read them.</string>
<!-- deprecated -->
<string name="chat_protection_broken_tap_to_learn_more">%1$s sent a message from another device. Tap to learn more.</string> <string name="chat_protection_broken_tap_to_learn_more">%1$s sent a message from another device. Tap to learn more.</string>
<!-- deprecated -->
<string name="chat_protection_broken_explanation">End-to-end encryption cannot be guaranteed anymore, likely because %1$s reinstalled Delta Chat or sent a message from another device.\n\nYou may meet them in person and scan their QR code again to reestablish guaranteed end-to-end encryption.</string> <string name="chat_protection_broken_explanation">End-to-end encryption cannot be guaranteed anymore, likely because %1$s reinstalled Delta Chat or sent a message from another device.\n\nYou may meet them in person and scan their QR code again to reestablish guaranteed end-to-end encryption.</string>
<string name="invalid_unencrypted_tap_to_learn_more">⚠️ %1$s requires end-to-end encryption which is not setup for this chat yet. Tap to learn more.</string> <string name="invalid_unencrypted_tap_to_learn_more">⚠️ %1$s requires end-to-end encryption which is not setup for this chat yet. Tap to learn more.</string>
<string name="invalid_unencrypted_explanation">To establish end-to-end-encryption, you may meet contacts in person and scan their QR Code to introduce them.</string> <string name="invalid_unencrypted_explanation">To establish end-to-end-encryption, you may meet contacts in person and scan their QR Code to introduce them.</string>
@ -1034,16 +1037,19 @@
<string name="secure_join_started">%1$s invited you to join this group.\n\nWaiting for the device of %2$s to reply…</string> <string name="secure_join_started">%1$s invited you to join this group.\n\nWaiting for the device of %2$s to reply…</string>
<!-- placeholder will be replaced by the name of the inviter. --> <!-- placeholder will be replaced by the name of the inviter. -->
<string name="secure_join_replies">%1$s replied, waiting for being added to the group…</string> <string name="secure_join_replies">%1$s replied, waiting for being added to the group…</string>
<string name="secure_join_wait">Establishing guaranteed end-to-end encryption, please wait…</string> <string name="secure_join_wait">Establishing end-to-end encryption, please wait…</string>
<!-- deprecated --> <!-- deprecated -->
<string name="secure_join_wait_timeout">Could not yet establish guaranteed end-to-end encryption, but you may already send a message.</string> <string name="secure_join_wait_timeout">Could not yet establish guaranteed end-to-end encryption, but you may already send a message.</string>
<!-- deprecated, was stock string -->
<string name="secure_join_takes_longer">The contact must be online to proceed.\n\nThis process will continue automatically in background.</string> <string name="secure_join_takes_longer">The contact must be online to proceed.\n\nThis process will continue automatically in background.</string>
<string name="contact_verified">%1$s introduced.</string> <string name="contact_verified">%1$s introduced.</string>
<string name="contact_not_verified">Cannot establish guaranteed end-to-end encryption with %1$s.</string> <!-- deprecated, was stock string -->
<string name="contact_not_verified">Cannot establish end-to-end encryption with %1$s.</string>
<!-- Shown in contact profile. The placeholder will be replaced by the name of the contact that introduced the contact. --> <!-- Shown in contact profile. The placeholder will be replaced by the name of the contact that introduced the contact. -->
<string name="verified_by">Introduced by %1$s</string> <string name="verified_by">Introduced by %1$s</string>
<string name="verified_by_you">Introduced by me</string> <string name="verified_by_you">Introduced by me</string>
<!-- translators: "setup" is the "encryption setup" here, as in "Autocrypt Setup Message" --> <string name="verified_by_unknown">Introduced</string>
<!-- deprecated, was stock string -->
<string name="contact_setup_changed">Changed setup for %1$s.</string> <string name="contact_setup_changed">Changed setup for %1$s.</string>
<string name="verified_contact_required_explain">To guarantee end-to-end-encryption, you can only add contacts with a green checkmark to this group.\n\nYou may meet contacts in person and scan their QR Code to introduce them.</string> <string name="verified_contact_required_explain">To guarantee end-to-end-encryption, you can only add contacts with a green checkmark to this group.\n\nYou may meet contacts in person and scan their QR Code to introduce them.</string>
<string name="mailto_dialog_header_select_chat">Select chat to send the message to</string> <string name="mailto_dialog_header_select_chat">Select chat to send the message to</string>
@ -1087,7 +1093,7 @@
<string name="ImageEditorHud_flip">Flip</string> <string name="ImageEditorHud_flip">Flip</string>
<string name="ImageEditorHud_rotate">Rotate</string> <string name="ImageEditorHud_rotate">Rotate</string>
<!-- dc_str_* resources --> <!-- deprecated, use string "E-Mail" for non-encrypted messages instead -->
<string name="encrypted_message">Encrypted message</string> <string name="encrypted_message">Encrypted message</string>
<!-- strings introduced on desktop. we want to share strings between the os, in general, please do not add generic strings here --> <!-- strings introduced on desktop. we want to share strings between the os, in general, please do not add generic strings here -->
@ -1218,6 +1224,9 @@
<string name="perm_enable_bg_already_done">You already allowed Delta Chat to receive messages in the background.\n\nIf messages still do not arrive in background, please also check your system settings.</string> <string name="perm_enable_bg_already_done">You already allowed Delta Chat to receive messages in the background.\n\nIf messages still do not arrive in background, please also check your system settings.</string>
<!-- device messages for updates --> <!-- device messages for updates -->
<string name="update_2_0">What\'s new?\n\n💯 End-to-end encryption is reliable and forever now. Padlocks 🔒 are gone!\n\n✉️ Classic email without end-to-end encryption is marked with a letter symbol\n\n😻 New enhanced profile screen for all your contacts\n\n🔲 New button for quick access to apps used in a chat\n\n❤️ Please donate to help us remain independent and continue to bring improvements: %1$s</string>
<!-- deprecated -->
<string name="update_1_50_android">What\'s new?\n\n❤️‍🔥 New emojis picker with more emoji\n\n🎮 Enhanced in-chat apps: Get notifications and open supporting apps in context, i.e. open an added calendar entry directly\n\n👍 Get notified about reactions to your messages\n\n... 🛠️ FIXES and EVEN MORE at %1$s</string> <string name="update_1_50_android">What\'s new?\n\n❤️‍🔥 New emojis picker with more emoji\n\n🎮 Enhanced in-chat apps: Get notifications and open supporting apps in context, i.e. open an added calendar entry directly\n\n👍 Get notified about reactions to your messages\n\n... 🛠️ FIXES and EVEN MORE at %1$s</string>
<!-- deprecated -->
<string name="update_switch_profile_placement">ℹ️ \"Switch Profile\" option moved: Tap your profile image in the upper corner of the main screen to add or switch profiles 💡</string> <string name="update_switch_profile_placement">ℹ️ \"Switch Profile\" option moved: Tap your profile image in the upper corner of the main screen to add or switch profiles 💡</string>
</resources> </resources>