+
+# WebXDC
+
+This app has some extended support for WebXDC apps:
+
+- `window.webxdc.arcanechat` a string with the ArcaneChat version and can be used by app developers
+ to detect when they can use the ArcaneChat-specific features.
+- `sendToChat()`: extra property `subject` can be set to a text string to set message/email's subject.
+- `sendToChat()`: extra property `html` can be set to a string of html markup to set the HTML part of the email/message.
+- `sendToChat()`: the file object parameter also accepts a `type` field that can be one of:
+ * `"sticker"`
+ * `"image"`
+ * `"audio"`
+ * `"video"`
+ * `"file"` (default if `type` field is not present)
+- Inside apps, clicking external links is supported, ex. to open in browser, so you can include links to your website or donation pages.
+- `manifest.toml` field: `orientation`, if you set it to `"landscape"` your app will be launched in landscape mode.
+
+# Credits
+
+This app is based on the [official Delta Chat client](https://github.com/deltachat/deltachat-android) with several improvements.
+
+This app uses a [modified](https://github.com/ArcaneChat/core) version of the [Chatmail Core Library](https://github.com/chatmail/core).
diff --git a/RELEASE.md b/RELEASE.md
new file mode 100644
index 0000000000000000000000000000000000000000..32410514989603ca072e285549e415227c51826e
--- /dev/null
+++ b/RELEASE.md
@@ -0,0 +1,148 @@
+# Android Release Checklist
+
+
+## Generate APKs
+
+### Update core and translations
+
+on the command-line, in a PR called "update-core-and-stuff-DATE":
+
+1. update core:
+ ```
+ ./scripts/update-core.sh # shows used branch
+ ./scripts/update-core.sh BRANCH_OR_TAG # update to tag or latest commit of branch
+ ./scripts/clean-core.sh # helps on weird issues, do also "Build / Clean"
+ ./scripts/ndk-make.sh
+ ```
+
+a) Update `CHANGELOG.md`
+ from abc@example.org (and maybe ask whether a chat should be created if it does not exist already)abc@example.org and fill testing mailto uris; as we created the chat in the previous step, it should not ask Chat with … but directly open the chatabc@example.org, draft this is a testabc@example.org, draft testing mailto uris <newline> this is a testinfo@example.orgsimplebot@example.org, draft !web https://duckduckgo.com/lite?q=duck%20itbla <newline> blub thereDelta Chat is a reliable, decentralized and secure instant messaging app, +available for mobile and desktop platforms.
+ +Instant creation of private chat profiles +with secure and interoperable chatmail relays +that offer instant message delivery, and Push Notifications for iOS and Android devices.
+Pervasive multi-profile and +multi-device support on all platforms +and between different chatmail apps.
+Interactive in-chat apps for gaming and collaboration
+Audited end-to-end encryption +safe against network and server attacks.
+Free and Open Source software, both app and server side, +built on Internet Standards.
+First, note that Delta Chat is a private messenger. +There is no public discovery, you decide about your contacts.
+ +If you are face to face with your friend or family,
+tap the QR Code icon
+on the main screen.
+Ask your chat partner to scan the QR image
+with their Delta Chat app.
For a remote contact setup, +from the same screen, +click “Copy” or “Share” and send the invite link +through another private chat.
+Now wait while connection gets established.
+ +If both sides are online, they will soon see a chat +and can start messaging securely.
+If one side is offline or in bad network, +the ability to chat is delayed until connectivity is restored.
+Congratulations! +You now will automatically use end-to-end encryption with this contact. +If you add each other to groups, end-to-end encryption will be established among all members.
+ +As being a private messenger, +only friends and family you share your QR code or invite link with can write to you.
+ +Your friends may share your contact with other friends, this appears as a request.
+ +You need to accept the request before you can reply.
+You can also delete it if you don’t want to chat with them for now.
+If you delete a request, future messages from that contact will still appear +as message request, so you can change your mind. If you really don’t want to +receive messages from this person, consider blocking them.
+Attach the first contact to the chat of the second using
Attachment Button → Contact.
+You can also add a little introduction message.
The second contact will receive a card then +and can tap it to start chatting with the first contact.
+ +Yes. Images, videos, files, voice messages etc. can be sent using the
Attachment-
+or
Voice Message buttons
For performance, images are optimized and sent at a smaller size by default, but you can send it as a “file” to preserve the original.
+A profile is a name, a picture and some additional information for encrypting messages. +A profile lives on your device(s) only +and uses the server only to relay messages.
+ +On first installation of Delta Chat a first profile is created.
+ +Later, you can tap your profile image in the upper left corner to Add Profiles +or to Switch Profiles.
+ +You may want to use separate profiles for political, family or work related activities.
+ +You may also wish to learn how to use the same profile on multiple devices.
+ +Profilový obrázek lze zvolit v nastavení. Když napíšeš svému kontaktu, +nebo přidáš nový vyfocením QR kódu, tyto kontakty automaticky uvidí tvůj profilový obrázek.
+Z důvodu soukromí nikdo nevidí tvůj profilový obrázek dokud jim nenapíšeš.
+Yes, +you can do so under Settings → Profile → Bio. +Once you sent a message to a contact, +they will see it when they view your contact details.
+ +Use these tools to organize your chats and keep everything in its place:
+ +Pinned chats always stay atop of the chat list. You can use them to access your most loved chats quickly or temporarily to not forget about things.
+Mute chats if you do not want to get notifications for them. Muted chats stay in place and you can also pin a muted chat.
+Archive chats if you do not want to see them in your chat list any longer. +Archived chats remain accessible above the chat list or via search.
+When an archived chat gets a new message, unless muted, it will pop out of the archive and back into your chat list. +Muted chats stay archived until you unarchive them manually.
+To use the functions, long tap or right click a chat in the chat list.
+ +Saved Messages is a chat that you can use to easily remember and find messages.
+ +In any chat, long tap or right click a message and select Save
+Saved messages are marked by the symbol
+
+next to the timestamp
Later, open the “Saved Messages” chat - and you will see the saved messages there.
+By tapping
,
+you can go back to the original message in the original chat
Finally, you can also use “Save Messages” to take personal notes - open the chat, type something, add a photo or a voice message etc.
+As “Saved Message” are synced, they can become very handy for transferring data between devices
+Messages stay saved even if they are edited or deleted - +may it be by sender, by device cleanup or by disappearing messages of other chats.
+ +You can sometimes see a green dot
+next to the avatar of a contact.
+It means they were recently seen by you in the last 10 minutes,
+e.g. because they messaged you or sent a read receipt.
So this is not a real time online status +and others will as well not always see that you are “online”.
+ +One tick
+means that the message was sent successfully to your provider.
Two ticks
+mean that at least one recipient’s device
+reported back to having received the message.
Recipients may have disabled read-receipts, +so even if you see only one tick, the message may have been read.
+The other way round, two ticks do not automatically mean +that a human has read or understood the message ;)
+You can edit the text of your messages after sending.
+For that, long tap or right click the message and select Edit
+or
.
If you have sent a message accidentally, +from the same menu, select Delete and then Delete for Everyone.
+While edited messages will have the word “Edited” next to the timestamp, +deleted messages will be removed without a marker in the chat. +Notifications are not sent and there is no time limit.
+ +Note, that the original message may still be received by chat members +who could have already replied, forwarded, saved, screenshotted or otherwise copied the message.
+ +You can turn on “disappearing messages” +in the settings of a chat, +at the top right of the chat window, +by selecting a time span +between 5 minutes and 1 year.
+ +Until the setting is turned off again, +each chat member’s Delta Chat app takes care +of deleting the messages +after the selected time span. +The time span begins +when the receiver first sees the message in Delta Chat. +The messages are deleted both, +on the servers, +and in the apps itself.
+ +Note that you can rely on disappearing messages +only as long as you trust your chat partners; +malicious chat partners can take photos, +or otherwise save, copy or forward messages before deletion.
+ +Apart from that, +if one chat partner uninstalls Delta Chat, +the (anyway encrypted) messages may take longer to get deleted from their server.
+ +If you are using more than one chat profile, +you can remove single ones in the top profile switcher menu (on Android and iOS), +or in the sidebar with a right click (in the Desktop app). +Chat profiles are only removed on the device where deletion was triggered. +Chat profiles on other devices will continue to fully function.
+ +If you use a single default chat profile you can simply uninstall the app. +This will still automatically trigger deletion of all associated address data on the chatmail server. +For more info, please refer to nine.testrun.org address-deletion +or the respective page from your chosen 3rd party chatmail server.
+ +Groups let several people chat together privately with equal rights.
+ +Anyone can +change the group name or avatar, +add or remove members, +set disappearing messages, +and delete their own messages from all member’s devices.
+ +Because all members have the same rights, groups work best among trusted friends and family.
+ +All group members have the same rights. +For this reason, everyone can delete any member or add new ones.
+To add or delete members, tap the group name in the chat and select the member to add or remove.
+If the member is not yet in your contact list, but face to face with you,
+from the same screen, show a QR code.
+Ask your chat partner to scan the QR image with their Delta Chat app by tapping
+
on the main screen.
For a remote member addition, +click “Copy” or “Share” and send the invite link +through another private chat to the new member.
+QR code and invite link can be used to add several members. +However, since groups are meant for trusted people, avoid sharing them publicly.
+ +Buď se odeber ze seznamu členů a nebo vymaž celý skupinový hovor. +K opětovnému připojení v budoucnu požádej nějakého člena skupiny o znovupřidání.
+Jiná možnost je “Umlčení” skupiny, což znamená nadále přijímat a také posílat zprávy, +ale nebudeš dostávat upozrnění na nově příchozí zprávy.
+You can duplicate a group to start a separate discussion +or to exclude members without them noticing.
+ +Open the group profile and tap Clone Chat (Android/iOS), +or right-click the group in the chat list (Desktop).
+Set a new name, choose an avatar, and adjust the member list if needed.
+The new group is fully independent from the original, +which continues to work as before.
+ +You can send apps to a chat - games, editors, polls and other tools. +This makes Delta Chat a truly extensible messenger.
+ +In a chat, using
Attachment Button → Apps
You can also create your own app and attach it using
Attachment Button → File
In-chat apps can not send data to the Internet, or download anything.
+An in-chat app can only exchange data within a chat, with its +copies on the devices of your chat partners. Other than that, it’s completely +isolated from the Internet.
+The privacy an in-chat app offers is the privacy of your chat - as long as you +trust the people you chat with, you can trust the in-chat app as well.
+This also means: Just like for web links, do not open apps from untrusted contacts.
+In-chat apps are zip files with .xdc extension containing html, css, and javascript code.
You can extend the Hello World example app +to get started.
+All else you need to know is written in the +Webxdc documentation.
+If you have question, you can ask others with experience +in the Delta Chat Forum.
+Push Notifications are sent by Apple and Google “Push services” to a user’s device +so that an inactive Delta Chat app can fetch messages in the background +and show notifications on a user’s phone if needed.
+ +Push Notifications work with all chatmail servers on
+ +iOS devices, by integrating with Apple Push services.
+Android devices, by integrating with the Google FCM Push service, +including on devices that use microG +instead of proprietary Google code on the phone.
+Yes, Delta Chat automatically uses Push Notifications for chatmail profiles. +And no, there is no alternative on Apple’s phones to achieve instant message delivery +because Apple devices do not allow Delta Chat to fetch data in the background. +Push notifications are automatically activated for iOS users because +Delta Chat’s privacy-preserving Push Notification system +does not expose data to Apple that it doesn’t already have.
+ +If a “Push Service” is available, Delta Chat enables Push Notifications +to achieve instant message delivery for all chatmail users.
+ +In the Delta Chat “Notifications” settings for “Instant delivery” +you can change the following settings effecting all chat profiles:
+ +Use Background Connection: If you are not using a Push service, +you may disable “battery optimizations” for Delta Chat, +allowing it to fetch messages in the background. +However, there could be delays from minutes to hours. +Some Android vendors even restrict apps completely +(see dontkillmyapp.com) +and Delta Chat might not show incoming messages +until you manually open the app again.
+Force Background Connection: This is the fallback option +if the previous options are not available or do not achieve “instant delivery”. +Enabling it causes a permanent notification on your phone +which may sometimes be “minified” with recent Android phones.
+Both “Background Connection” options are energy-efficient and +safe to try if you experience messages arrive only with long delays.
+ +Delta Chat Push Notification support avoids leakage of private information. +It does not leak profile data, IP address or message content (not even encrypted) +to any system involved in the delivery of Push Notifications.
+ +Here is how Delta Chat apps perform Push Notification delivery:
+ +A Delta Chat app obtains a “device token” locally, encrypts it and stores it +on the chatmail server.
+When a chatmail server receives a message for a Delta Chat user +it forwards the encrypted device token to the central Delta Chat notification proxy.
+The central Delta Chat notification proxy decrypts the device token +and forwards it to the respective Push service (Apple, Google, etc.), +without ever knowing the IP or profile data of Delta Chat users.
+The central Push Service (Apple, Google, etc.) +wakes up the Delta Chat app on your device +to check for new messages in the background. +It does not know about the profile data of the device it wakes up. +The central Apple/Google Push services never see any profile data (sender or receiver) +and also never see any message content (also not in encrypted forms).
+The central Delta Chat notification proxy is small and fully implemented in Rust +and forgets about device-tokens as soon as Apple/Google/etc processed them, +usually in a matter of milliseconds.
+ +Note that the device token is encrypted between apps and notification proxy +but it is not signed. +The notification proxy thus never sees profile data, IP-addresses or +any cryptographic identity information associated with a user’s device (token).
+ +Resulting from this overall privacy design, even the seizure of a chatmail server, +or the full seizure of the central Delta Chat notification proxy +would not reveal private information that Push services do not already have.
+ +Delta Chat is a free and open source decentralized messenger with free server choice, +but we want users to reliably experience “instant delivery” of messages, +like they experience from WhatsApp, Signal or Telegram apps, +without asking questions up-front that are more suited to expert users or developers.
+ +Note that Delta Chat has a small and privacy-preserving Push Notification system +that achieves “instant delivery” of messages for all chatmail servers +including a potential one you might setup yourself without our permission. +Welcome to the power of the interoperable chatmail relay network :)
+ +Yes. You can use the same profile on different devices:
+ +Make sure both devices are on the same Wi-Fi or network
+On the first device, go to Settings → Add Second Device, unlock the screen if needed +and wait a moment until a QR code is shown
+On the second device, install Delta Chat
+On the second device, start Delta Chat, select Add as Second Device, and scan the QR code from the old device
+Transfer should start after a few seconds and during transfer both devices will show the progress. +Wait until it is finished on both devices.
+In contrast to many other messengers, after successful transfer, +both devices are completely independent. +One device is not needed for the other to work.
+ +Double-check both devices are in the same Wi-Fi or network
+On Windows, go to Control Panel / Network and Internet +and make sure, Private Network is selected as “Network profile type” +(after transfer, you can change back to the original value)
+On iOS, make sure “System Settings / Apps / Delta Chat / Local Network” access is granted
+On macOS, enable “System Settings / Privacy & Security / Local Network / Delta Chat”
+Your system might have a “personal firewall”, +which is known to cause problems (especially on Windows). +Disable the personal firewall for Delta Chat on both ends and try again
+Guest Networks may not allow devices to communicate with each other. +If possible, use a non-guest network.
+If you still have troubles using the same network, +try to open Mobile Hotspot on one device and join that Wi-Fi from the other one
+Ensure there is enough storage on the destination device
+If transfer started, make sure, the devices stay active and do not fall asleep. +Do not exit Delta Chat. +(we try hard to make the app work in background, but systems tend to kill apps, unfortunately)
+Delta Chat is already logged in on the destination device? +You can use multiple profiles per device, just add another profile
+If you still have problems or if you cannot scan a QR code +try the manual transfer described below
+This method is only recommended if “Add Second Device” as described above does not work.
+ +At Settings → Advanced → Experimental Features +you can try out features we are working on.
+ +The features may be unstable and may be changed or removed.
+ +You can find more information +and give feedback in the Forum.
+ +We would like to improve Delta Chat with your help, +which is why Delta Chat for Android asks whether you want +to send anonymous usage statistics.
+ +You can turn it on and off at +Settings → Advanced → Send statistics to Delta Chat’s developers.
+ +When you turn it on, +weekly statistics will be automatically sent to a bot.
+ +We are interested e.g. in statistics like:
+ +We will not collect any personally identifiable information about you.
+ +Yes, but only if the email address is used exclusively by chatmail clients.
+ +It is not supported to share usage of an email address with non-chatmail apps or web-based mailers, +for the following reasons:
+ +Non-chatmail apps are largely not accomplishing automatic end-to-end email encryption for their users, +while chatmail apps and relays pervasively enforce end-to-end encryption and security standards.
+Non-chatmail apps use email servers as a long-term message archive +while chatmail clients use email servers for ephemeral instant message relay.
+Supporting the full variety of classic email setups +would require considerable development and maintenance efforts, +and complicate making chatmail-based messaging more resilient, reliable and fast.
+First off, please do not use the same classic email address also from non-chatmail classic email apps +unless you are prepared to deal with encrypted messages in the inbox, +double notifications, accidentally deleted emails or similar annoyances.
+ +You can configure a email address for chatting at New Profile → Use Other Server → Use Classic Mail as Relay.
+Note that classic email providers will generally not support Push Notifications
+and have other limitations, see Provider Overview.
+Chatmail uses the default INBOX for relay; ensure the provider setup does too.
+A chat profile using a classic email address allows to to send and receive unencrypted messages.
+These messages, and the chats they appear in, are marked with an email icon
+
.
Any well behaving email server setup will do fine +except if your users’ devices require Google/Apple Push Notifications to work properly.
+ +We generally recommend to set up a chatmail relay. +Chatmail is a community-driven project that encompasses both the setup of relays +and core Rust developments +that power chatmail clients of which Delta Chat is the most well known.
+ +Delta Chat uses a secure subset of the OpenPGP standard +to provide automatic end-to-end encryption using these protocols:
+ +Secure-Join +to exchange encryption setup information through QR-code scanning or “invite links”.
+Autocrypt is used for automatically +establishing end-to-end encryption between contacts and all members of a group chat.
+Sharing a contact to a +chat +enables receivers to use end-to-end encryption with the contact.
+Delta Chat does not query, publish or interact with any OpenPGP key servers.
+ +All messages in Delta Chat are end-to-end encrypted by default. +Since the Delta Chat Version 2 release series (July 2025) +there are no lock or similar markers on end-to-end encrypted messages, anymore.
+ +If you use default chatmail relays, +it is impossible to receive or send messages without end-to-end encryption.
+ +If you instead use a classic email server,
+you can send and receive messages with or without end-to-end encryption.
+Messages lacking end-to-end encryption are marked with an email icon
+
.
A contact profile might show a green checkmark
+
+and an “Introduced by” line.
+Every green-checkmarked contact either did a direct QR-scan with you
+or was introduced by a another green-checkmarked contact.
+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 QR-scan.
For more in-depth discussion of “guaranteed end-to-end encryption” +please see Secure-Join protocols +and specifically read about “Verified Groups”, the technical term +of what is called here “green-checkmarked” or “guaranteed end-to-end encrypted” chats.
+ +Yes.
+ +When we talk about an “end-to-end encrypted message” +we always mean a whole message is encrypted, +including all the attachments +and attachment metadata such as filenames.
+ +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.
+ +OpenPGP is not insecure by itself. +Most publicly discussed OpenPGP security problems +actually stem from bad usability or bad implementations of tools or apps (or both). +It is particularly important to distinguish between OpenPGP, the IETF encryption standard, +and GnuPG (GPG), a command line tool implementing OpenPGP. +Many public critiques of OpenPGP actually discuss GnuPG which Delta Chat has never used. +Delta Chat rather uses the OpenPGP Rust implementation rPGP, +available as an independent “pgp” package, +and security-audited in 2019 and 2024.
+ +We aim, along with other OpenPGP implementors, +to further improve security characteristics by implementing the +new IETF OpenPGP Crypto-Refresh +which was thankfully adopted in summer 2023.
+ +Yes, we are following efforts like MLS +but adopting them would mean breaking end-to-end encryption interoperability. +So it would not be a light decision to take +and there must be tangible improvements for users.
+ +Delta Chat takes a holistic “usable security” approach +and works with a wide range of activist groupings as well as +renowned researchers such as TeamUSEC +to improve actual user outcomes against security threats. +The wire protocol and standard for establishing end-to-end encryption is +only one part of “user outcomes”, +see also our answers to device-seizure +and message-metadata questions.
+ +No, Delta Chat never was vulnerable to EFAIL +because its OpenPGP implementation rPGP +uses Modification Detection Code when encrypting messages +and returns an error +if the Modification Detection Code is incorrect.
+ +Delta Chat also never was vulnerable to the “Direct Exfiltration” EFAIL attack
+because it only decrypts multipart/encrypted messages
+which contain exactly one encrypted and signed part,
+as defined by the Autocrypt Level 1 specification.
If you are sending or receiving email messages without end-to-end encryption (using a classic email server), +they are still protected from cell or cable companies who can not read or modify your email messages. +But both your and your recipient’s email providers +may read, analyze or modify your messages, including any attachments.
+ +Delta Chat by default uses strict +TLS encryption +which secures connections between your device and your email provider. +All of Delta Chat’s TLS-handling has been independently security audited. +Moreover, the connection between your and the recipient’s email provider +will typically be transport-encrypted as well. +If the involved email servers support MTA-STS +then transport encryption will be enforced between email providers +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.
+ +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.
+ +Servers can therefore only see:
+ +By default, the addresses are randomly generated.
+ +All other message, contact and group metadata resides in the end-to-end encrypted part of messages.
+ +Both for protecting against metadata-collecting servers +as well as against the threat of device seizure +we recommend to use a chatmail relay +to create chat profiles using random 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.
+ +No, not yet.
+ +The Signal messenger introduced “Sealed Sender” in 2018 +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.
+ +Even if chatmail relays +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 addresses for sealed sending +but an implementation has not been agreed as a priority yet.
+ +No, not yet.
+ +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.
+ +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 chatmail core, +which would make it available in all chatmail clients.
+ +No, not yet.
+ +Delta Chat uses the Rust OpenPGP library rPGP +which supports the latest IETF Post-Quantum-Cryptography OpenPGP draft. +We aim to add PQC support in chatmail core after the draft is finalized at the IETF +in collaboration with other OpenPGP implementers.
+ +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.
+ +No.
+ +Delta Chat generates secure OpenPGP keys according to the Autocrypt specification 1.1. +We do not recommend or offer users to perform manual key management. +We want to ensure that security audits can focus on a few proven cryptographic algorithms +instead of the full breadth of possible algorithms allowed with OpenPGP. +If you want to extract your OpenPGP key, there only is an expert method: +you need to look it up in the “keypairs” SQLite table of a profile backup tar-file.
+ +Yes, multiple times. +The Delta Chat project continuously undergoes independent security audits and analysis, +from most recent to older:
+ +2024 December, an NLNET-commissioned Evaluation of +rPGP by Radically Open Security took place. +rPGP serves as the end-to-end encryption OpenPGP engine of Delta Chat. +Two advisories were released related to the findings of this audit:
+ +The issues outlined in these advisories have been fixed and are part of Delta Chat +releases on all appstores since December 2024.
+2024 March, we received a deep security analysis from the Applied Cryptography +research group at ETH Zuerich and addressed all raised issues. +See our blog post about Hardening Guaranteed End-to-End encryption for more detailed information and the +Cryptographic Analysis of Delta Chat +research paper published afterwards.
+2023 April, we fixed security and privacy issues with the “web +apps shared in a chat” feature, related to failures of sandboxing +especially with Chromium. We subsequently got an independent security +audit from Cure53 and all issues found were fixed in the 1.36 app series released in April 2023. +See here for the full background story on end-to-end security in the web.
+2023 March, Cure53 analyzed both the transport encryption of +Delta Chat’s network connections and a reproducible mail server setup as +recommended on this site. +You can read more about the audit on our blog +or read the full report here.
+2020, Include Security analyzed Delta +Chat’s Rust core, +IMAP, +SMTP, and +TLS libraries. +It did not find any critical or high-severity issues. +The report raised a few medium-severity weaknesses - +they are no threat to Delta Chat users on their own +because they depend on the environment in which Delta Chat is used. +For usability and compatibility reasons, +we can not mitigate all of them +and decided to provide security recommendations to threatened users. +You can read the full report here.
+2019, Include Security analyzed Delta +Chat’s PGP and +RSA libraries. +It found no critical issues, +but two high-severity issues that we subsequently fixed. +It also revealed one medium-severity and some less severe issues, +but there was no way to exploit these vulnerabilities in the Delta Chat implementation. +Some of them we nevertheless fixed since the audit was concluded. +You can read the full report here.
+Some features require certain permissions, +e.g. you need to grant camera permission if you want to scan an invite QR code.
+ +See Privacy Policy for a detailed overview.
+ +Delta Chat is available for all major and some minor platforms:
+ +The official website, https://delta.chat/download shows all options in detail
+If unavailable, use the mirror at https://deltachat.github.io/deltachat-pages
+Open one of the following app stores and search for “Delta Chat”: +Google Play Store, F-Droid, Huawei App Gallery, iOS and macOS App Store, Microsoft Store
+Check the package manager of your Linux distributions
+Android APKs are also available on https://github.com/deltachat/deltachat-android/releases
+Delta Chat does not receive any Venture Capital and +is not indebted, and under no pressure to produce huge profits, or to +sell users and their friends and family to advertisers (or worse). +We rather use public funding sources, so far from EU and US origins, to help +our efforts in instigating a decentralized and diverse chat messaging eco-system +based on Free and Open-Source community developments.
+ +Concretely, Delta Chat developments have so far been funded from these sources, +ordered chronologically:
+ +The NEXTLEAP EU project funded the research +and implementation of verified groups and setup contact protocols +in 2017 and 2018 and also helped to integrate end-to-end Encryption +through Autocrypt.
+The Open Technology Fund gave us a +first 2018/2019 grant (~$200K) during which we majorly improved the Android app +and released a first Desktop app beta version, and which moreover +moored our feature developments in UX research in human rights contexts, +see our concluding Needfinding and UX report. +The second 2019/2020 grant (~$300K) helped us to +release Delta/iOS versions, to convert our core library to Rust, and +to provide new features for all platforms.
+The NLnet foundation granted in 2019/2020 EUR 46K for +completing Rust/Python bindings and instigating a Chat-bot eco-system.
+In 2021 we received further EU funding for two Next-Generation-Internet +proposals, namely for EPPD - email provider portability directory (~97K EUR) and AEAP - email address porting (~90K EUR) which resulted in better multi-profile support, improved QR-code contact and group setups and many networking improvements on all platforms.
+From End 2021 till March 2023 we received Internet Freedom funding (500K USD) from the +U.S. Bureau of Democracy, Human Rights and Labor (DRL). +This funding supported our long-running goals to make Delta Chat more usable +and compatible with a wide range of email servers world-wide, and more resilient and secure +in places often affected by internet censorship and shutdowns.
+2023-2024 we successfully completed the OTF-funded +Secure Chatmail project, +allowing us to introduce guaranteed encryption, +creating a chatmail server network +and providing “instant onboarding” in all apps released from April 2024 on.
+In 2023 and 2024 we got accepted in the Next Generation Internet (NGI) +program for our work in webxdc PUSH, +along with collaboration partners working on +webxdc evolve, +webxdc XMPP, +DeltaTouch and +DeltaTauri. +All of these projects are partially completed or to be completed in early 2025.
+Sometimes we receive one-time donations from private individuals. +For example, in 2021 a generous individual bank-wired us 4K EUR +with the subject “keep up the good developments!”. 💜 +We use such money to fund development gatherings or to care for ad-hoc expenses +that can not easily be predicted for, or reimbursed from, public funding grants. +Receiving more donations also helps us to become more independent and long-term viable +as a contributor community.
+ + +Velice významnou pomocí je práce expertů a nadšenců prováděná bez nároku +na honorář či za minimální odměnu ve prospěch veřejného dobra. Je třeba +zdůraznit, že bez nich by se Delta Chat nepřibližoval ani zdaleka současnému +stavu.
+The monetary funding mentioned above is mostly organized by merlinux GmbH in +Freiburg (Germany), and is distributed to more than a dozen contributors world-wide.
+ +Please see Delta Chat Contribution channels +for both monetary and other contribution possibilities.
+ + + + + \ No newline at end of file diff --git a/src/main/assets/help/de/help.html b/src/main/assets/help/de/help.html new file mode 100644 index 0000000000000000000000000000000000000000..aa018f512c980156eb66b64e0d117f60f8aed135 --- /dev/null +++ b/src/main/assets/help/de/help.html @@ -0,0 +1,1532 @@ + +Delta Chat ist eine zuverlässige, dezentralisierte und sichere Instant-Messaging-App, verfügbar für Mobile- und Desktop-Plattformen.
+ +Einfache Erstellung von privaten Chat-Profile mit sicheren, schnellen und interoperablen Chatmail-Servern, +die sofortige Push-Benachrichtigungen für iOS- und Android-Geräte bieten.
+Durchgängige Mehrprofil- und Mehrgeräte-Unterstützung auf allen Plattformen und zwischen verschiedenen Chatmail Apps
+Interaktive In-Chats-Apps zum Spielen und für die Zusammenarbeit
+Geprüfte Ende-zu-Ende-Verschlüsselung, +sicher gegen Netzwerk- und Serverangriffe.
+Freie und quelloffene Software, sowohl app- als auch serverseitig, +basierend auf Internet-Standards.
+Beachte zunächst, dass Delta Chat ein privater Messenger ist. +Es gibt keine öffentliches Verzeichnis, du entscheiden selbst über deine Kontakte.
+ +Für eine Kontaktaufnahme aus der Ferne, klicke im selben Bildschirm auf “Kopieren” oder “Teilen” und sende den Einladungslink über einen anderen privaten Chat.
+ +Wartet nun, bis die Verbindung hergestellt ist.
+ +Wenn beide Seiten online sind, wird ein Chat angezeigt und ihr könnt sicher miteinander chatten.
+Wenn eine Seite offline ist oder eine schlechte Netzwerkverbindung hat, +wird die Chat-Funktion verzögert, bis die Verbindung wiederhergestellt ist.
+Glückwunsch! +Du verwendest jetzt automatisch eine Ende-zu-Ende-Verschlüsselung +mit deinem Kontakt. +Wenn man sich gegenseitig zu Gruppen hinzufügt, +wird eine Ende-zu-Ende-Verschlüsselung zwischen allen Mitgliedern eingerichtet.
+ +Da Delta Chat ein privater Messenger ist, können dir zunächst nur Freunde und Familienmitglieder, denen du deinen QR-Code oder Einladungslink schickst, schreiben.
+ +Deine Freunde können deine Kontaktdaten dann mit anderen Freunden teilen. Dies wird als Anfrage angezeigt.
+ +Du musst die Anfrage akzeptieren, bevor du antworten kannst.
+Du kannst sie auch “löschen”, wenn du vorerst nicht mit ihm chatten möchten.
+If you delete a request, future messages from that contact will still appear +as message request, so you can change your mind. If you really don’t want to +receive messages from this person, consider blocking them.
+Füge den ersten Kontakt zum Chat des zweiten Kontakts hinzu, indem du auf
Anhängen → Kontakt klickst.
+Du kannst auch eine kurze Nachricht hinzufügen.
Der zweite Kontakt erhält dann die Kontaktdaten und +kann darauf tippen, um mit dem ersten Kontakt zu chatten.
+ +Ja. Bilder, Videos, Dateien, Sprachnachrichten und mehr können über die
Anhang-
+bzw.
Sprachnachricht-Buttons hinzugefügt werden
Um die Leistung zu verbessern, werden die Bilder standardmäßig optimiert und in einer kleineren Größe gesendet, aber du kannst sie auch als “Datei” senden, um das Original zu erhalten.
+Ein Profil besteht aus einem Namen, einem Bild und einigen zusätzlichen Informationen zum Verschlüsseln von Nachrichten. +Ein Profil existiert nur auf Ihren Geräten +und verwendet den Server nur für den Transport von Nachrichten.
+ +Bei der Installation von Delta Chat wird ein erstes Profil erstellt.
+ +Später kannst du auf dein Profilbild in der oberen linken Ecke tippen, um Profile hinzuzufügen +oder Profile zu wechseln.
+ +Du kannst separate Profile für politische, familiäre oder berufliche Aktivitäten verwenden.
+ +Vielleicht möchtest due auch erfahren, wie du Profile auf mehreren Geräten verwenden kannst.
+ +Du kannst ein Profilbild in den Einstellungen hinzufügen. Wenn du deinen Kontakten eine Nachricht sendest oder sie über einen QR-Code hinzufügst, sehen diese automatisch dein Profilbild.
+Aus Datenschutzgründen sieht niemand dein Profilbild, dem du nicht zuvor eine Nachricht gesendet hast.
+Ja, +Du kannst dies unter “Einstellungen → Profil → Signatur” tun. +Sobald du eine Nachricht an einen Kontakt sendest, kann dieser deine Signatur in deinem Profil sehen.
+ +Verwende diese Tools, um deine Chats zu organisieren:
+ +Angeheftete Chats bleiben immer ganz oben in der Chatliste. So kannst du schnell auf deine Lieblingschats zugreifen oder du verwendest vorübergehend angeheftete Chats um Dinge nicht zu vergessen.
+Stummgeschaltete Chats erhalten keine Benachrichtigungen, bleiben ansonsten aber an ihrem Platz. Du kannst auch stummgeschaltete Chats anheften.
+Archiviere Chats, wenn du diese nicht mehr in deiner Chatliste sehen möchtest. Archivierte Chats bleiben oberhalb der Chatliste oder über die Suche zugänglich.
+Wenn ein archivierter Chat eine neue Nachricht erhält, wird er, sofern er nicht stummgeschaltet ist, wieder in die normale Chatliste verschoben. Stummgeschaltete Chats bleiben archiviert, bis du sie manuell aus dem Archiv entfernst.
+Um die Funktionen zu nutzen, lang auf einen Chat in der Chatliste tippen oder den Chat mit der rechten Maustaste anklicken.
+ +Gespeicherte Nachrichten ist ein Chat, den du verwenden kannst, um dir Nachrichten zu merken und wiederzufinden.
+ +Tippen in einem beliebigen Chat lange auf eine Nachricht oder klicken mit der rechten Maustaste darauf und wähle Speichern.
+Gespeicherte Nachrichten werden mit dem Symbol
+
+neben dem Datum markiert
Öffnen später den Chat „Gespeicherte Nachrichten“; dort siehst du die gespeicherten Nachrichten.
+Durch Tippen auf
,
+kannst du zu der ursprünglichen Nachricht im ursprünglichen Chat zurückkehren
Schließlich kannst du auch „Gespeicherte Nachrichten“ verwenden, um persönliche Notizen zu machen - öffnen den Chat, gib etwas ein, fügen ein Foto oder eine Sprachnachricht hinzu usw.
+Da „Gespeicherte Nachrichten“ synchronisiert werden, können sie sehr praktisch für die Übertragung von Daten zwischen Geräten sein
+Nachrichten bleiben gespeichert, auch wenn sie bearbeitet oder gelöscht werden - +sei es durch den Absender, durch Automatisches Löschen oder durch verschwindende Nachrichten anderer Chats.
+ +Manchmal ist ein “grüner Punkt”
neben dem Avatar eines Kontakts. Er bedeutet, dass der Kontakt kürzlich von dir gesehen wurde, in den letzten 10 Minuten, z.B. da du eine Nachricht oder eine Lesebestätigung empfangen hast.
Dies ist also kein Echtzeit-Online-Status - und auch andere werden nicht immer sehen, wenn du online bist.
+ +Ein Häkchen
bedeutet, dass die Nachricht erfolgreich versandt wurde.
Zwei Häkchen
bedeuten, dass mindestens ein Gerät des Empfängers zurückgemeldet hat, die Nachricht empfangen zu haben.
Lesebestätigungen können deaktiviert werden. D.h. auch wenn Sie nur ein Häkchen sehen, kann die Nachricht gelesen worden sein.
+Umgekehrt bedeuten zwei Häkchen nicht automatisch, dass ein Mensch die Nachricht gelesen oder verstanden hat ;)
+Du kannst den Text deiner Nachrichten nach dem Senden bearbeiten.
+Tippen dazu lange auf die Nachricht oder klicke mit der rechten Maustaste auf die Nachricht und wähle Bearbeiten oder ![]()
Wenn du versehentlich eine Nachricht gesendet hast, +wähle im selben Menü Löschen und dann Für alle löschen.
+Während bei bearbeiteten Nachrichten das „Bearbeitet“ neben dem Datum erscheint, +werden gelöschte Nachrichten ohne Markierung im Chat entfernt. +Es werden keine Benachrichtigungen verschickt und es gibt kein Zeitlimit.
+ +Beachten, dass die ursprüngliche Nachricht dennoch von Chatteilnehmern empfangen worden sein könnte, +die die Nachricht bereits beantwortet, weitergeleitet, gespeichert, mit einem Screenshot versehen oder anderweitig kopiert haben könnten.
+ +Schalte “Verschwindende Nachrichten” +oben rechts im Chatfenster, +durch Auswahl einer Zeitspanne +zwischen 5 Minuten und 1 Jahr ein.
+ +Bis die Einstellung wieder ausgeschaltet wird, +kümmern sich die Delta-Chat-Apps der Chat-Teilnehmer +um das Löschen der Nachrichten +nach der gewählten Zeitspanne. +Die Zeitspanne beginnt, +wenn der Empfänger die Nachricht zum ersten Mal in Delta Chat ansieht. +Die Nachrichten werden dann +sowohl auf den Servers, +als auch in den Apps selbst gelöscht.
+ +Beachte, dass du dich auf verschwindende Nachrichten nur so lange verlassen kannst, wie du deinen Chat-Partnern vertraust; +böswillige Chatpartner können Fotos machen, +oder auf andere Weise Nachrichten vor dem Löschen speichern, kopieren oder weiterleiten.
+ +Abgesehen davon, wenn ein Chat-Partner Delta Chat deinstalliert, kann es länger dauern, bis die (ohnehin verschlüsselten) Nachrichten vom Server gelöscht werden.
+ +If you are using more than one chat profile, +you can remove single ones in the top profile switcher menu (on Android and iOS), +or in the sidebar with a right click (in the Desktop app). +Chat profiles are only removed on the device where deletion was triggered. +Chat profiles on other devices will continue to fully function.
+ +If you use a single default chat profile you can simply uninstall the app. +This will still automatically trigger deletion of all associated address data on the chatmail server. +For more info, please refer to nine.testrun.org address-deletion +or the respective page from your chosen 3rd party chatmail server.
+ +Groups let several people chat together privately with equal rights.
+ +Anyone can +change the group name or avatar, +add or remove members, +set disappearing messages, +and delete their own messages from all member’s devices.
+ +Because all members have the same rights, groups work best among trusted friends and family.
+ +All group members have the same rights. +For this reason, everyone can delete any member or add new ones.
+To add or delete members, tap the group name in the chat and select the member to add or remove.
+If the member is not yet in your contact list, but face to face with you,
+from the same screen, show a QR code.
+Ask your chat partner to scan the QR image with their Delta Chat app by tapping
+
on the main screen.
For a remote member addition, +click “Copy” or “Share” and send the invite link +through another private chat to the new member.
+QR code and invite link can be used to add several members. +However, since groups are meant for trusted people, avoid sharing them publicly.
+ +Lösche dich entweder aus der Mitgliederliste oder lösche den gesamten Chat. +Wenn du der Gruppe später erneut beitreten möchtest, bitten ein anderes Gruppenmitglied, dich hinzuzufügen.
+Alternativ kannst du eine Gruppe auch “stummschalten” - dies bedeutet, dass du weiterhin alle Nachrichten erhälst und neue schreiben kannst, aber nicht mehr über neue Nachrichten informiert wirst.
+You can duplicate a group to start a separate discussion +or to exclude members without them noticing.
+ +Open the group profile and tap Clone Chat (Android/iOS), +or right-click the group in the chat list (Desktop).
+Set a new name, choose an avatar, and adjust the member list if needed.
+The new group is fully independent from the original, +which continues to work as before.
+ +You can send apps to a chat - games, editors, polls and other tools. +This makes Delta Chat a truly extensible messenger.
+ +In a chat, using
Attachment Button → Apps
You can also create your own app and attach it using
Attachment Button → File
In-chat apps can not send data to the Internet, or download anything.
+An in-chat app can only exchange data within a chat, with its +copies on the devices of your chat partners. Other than that, it’s completely +isolated from the Internet.
+The privacy an in-chat app offers is the privacy of your chat - as long as you +trust the people you chat with, you can trust the in-chat app as well.
+This also means: Just like for web links, do not open apps from untrusted contacts.
+In-chat apps are zip files with .xdc extension containing html, css, and javascript code.
You can extend the Hello World example app +to get started.
+All else you need to know is written in the +Webxdc documentation.
+If you have question, you can ask others with experience +in the Delta Chat Forum.
+Push-Benachrichtigungen werden von Apples und Googles „Push-Diensten“ an das Gerät des Benutzers gesendet, +so dass eine inaktive Delta-Chat-App im Hintergrund Nachrichten erhalten +und Benachrichtigungen auf dem Telefon des Nutzers anzeigen kann.
+ +Push-Benachrichtigungen funktionieren mit allen Chatmail-Servern auf
+ +iOS-Geräten, durch die Integration mit den Apple-Push-Diensten.
+Android-Geräten, durch die Integration des Google-FCM-Push-Dienstes, +auch auf Geräten, die microG +anstelle von proprietärem Google-Code auf dem Telefon.
+Ja, Delta Chat verwendet automatisch Push-Benachrichtigungen für Chatmail-Profile. +Und nein, es gibt für Apple-Telefonen keine Alternative, Push-Benachrichten zuzustellen; +Apple-Geräte erlauben es Delta Chat nicht, Daten im Hintergrund abzurufen. +Push-Benachrichtigungen werden für iOS-Nutzer automatisch aktiviert, da +Delta Chats datenschutzwahrendes Push-Benachrichtigungssystem +keine Daten an Apple weitergibt, die Apple nicht bereits hat.
+ +If a “Push Service” is available, Delta Chat enables Push Notifications +to achieve instant message delivery for all chatmail users.
+ +In den Delta-Chat-Einstellungen „Benachrichtigungen“ für „Sofortige Benachrichtigungen“ +kannst du die folgenden Einstellungen ändern, die alle Chat-Profile betreffen:
+ +Hintergrundverbindung verwenden: Wenn du keinen Push-Dienst verwendest, kannst du die „Batterie-Optimierung“ für Delta Chat deaktivieren, damit Nachrichten im Hintergrund abgerufen werden können. Dabei kann es jedoch zu Verzögerungen von Minuten bis Stunden kommen. +Einige Android-Hersteller schränken Apps sogar vollständig ein +(siehe dontkillmyapp.com) +und Delta Chat zeigt möglicherweise keine eingehenden Nachrichten an, bis du die App erneut manuell öffnest.
+Hintergrundverbindung erzwingen: Dies ist die Ausweichoption wenn die vorherigen Optionen nicht verfügbar sind oder keine „sofortige Zustellung“ erreichen. Die Aktivierung dieser Option führt zu einer permanenten Benachrichtigung auf Ihrem Telefon, die bei neueren Android-Telefonen manchmal „verkleinert“ werden kann.
+Beide „Hintergrundverbindung“-Optionen sind energiesparend und +können sicher ausprobiert werden, wenn du feststellst, dass Nachrichten nur mit großer Verzögerung ankommen.
+ +Delta Chat Push Notification support avoids leakage of private information. +It does not leak profile data, IP address or message content (not even encrypted) +to any system involved in the delivery of Push Notifications.
+ +So verwendet Delta Chat Push-Benachrichtigungen:
+ +Eine Delta-Chat-Anwendung erhält lokal ein „Geräte-Token“, verschlüsselt und speichert es +auf dem Chatmail-Server.
+When a chatmail server receives a message for a Delta Chat user +it forwards the encrypted device token to the central Delta Chat notification proxy.
+The central Delta Chat notification proxy decrypts the device token +and forwards it to the respective Push service (Apple, Google, etc.), +without ever knowing the IP or profile data of Delta Chat users.
+The central Push Service (Apple, Google, etc.) +wakes up the Delta Chat app on your device +to check for new messages in the background. +It does not know about the profile data of the device it wakes up. +The central Apple/Google Push services never see any profile data (sender or receiver) +and also never see any message content (also not in encrypted forms).
+Der zentrale Delta-Chat-Benachrichtigungs-Proxy ist klein und vollständig in Rust implementiert +und vergisst die Geräte-Token, sobald Apple/Google/etc. sie verarbeitet hat, +normalerweise innerhalb weniger Millisekunden.
+ +Note that the device token is encrypted between apps and notification proxy +but it is not signed. +The notification proxy thus never sees profile data, IP-addresses or +any cryptographic identity information associated with a user’s device (token).
+ +Aufgrund dieses umfassenden Datenschutzkonzepts würde sogar die Beschlagnahmung eines Chatmail-Servers, +oder die vollständige Beschlagnahmung des zentralen Delta-Chat-Benachrichtigungsproxys +keine privaten Informationen preisgeben, die den zentralen Push-Diensten nicht bereits vorliegen.
+ +Delta Chat ist ein freier, quelloffener, dezentraler Messenger mit freier Serverwahl, +aber wir wollen, dass die Nutzer eine zuverlässige „Sofortzustellung“ von Nachrichten haben, +wie sie es von WhatsApp, Signal oder Telegram kennen, +ohne im Vorfeld Fragen zu stellen, die eher für erfahrene Nutzer oder Entwickler geeignet sind.
+ +Note that Delta Chat has a small and privacy-preserving Push Notification system +that achieves “instant delivery” of messages for all chatmail servers +including a potential one you might setup yourself without our permission. +Welcome to the power of the interoperable chatmail relay network :)
+ +Ja. Du kannst dasselbe Profil auf mehreren Geräten verwenden:
+ +Stelle sicher, dass sich beide Geräte im selben Wi-Fi oder Netzwerk befinden
+Gehen auf dem ersten Gerät zu Einstellungen → Zweites Gerät hinzufügen, entsperre den Bildschirm, falls erforderlich, und warte einen Moment, bis ein QR-Code angezeigt wird
+Auf dem zweiten Gerät Delta Chat installieren
+Auf dem zweiten Gerät Delta Chat starten, “Als Zweitgerät hinzufügen” wählen und den QR-Code vom ersten Gerät scannen
+Die Übertragung sollte nach ein paar Sekunden beginnen und während der Übertragung zeigen beide Geräte den Fortschritt an. Warte, bis der Vorgang auf beiden Geräten abgeschlossen ist.
+Im Gegensatz zu vielen anderen Messengern, sind nach erfolgreicher Übertragung beide **Geräte völlig unabhängig voneinander. Das eine Gerät wird nicht benötigt, damit das Andere funktioniert.
+ +Vergewissere dich, dass beide Geräte mit dem gleichen Wi-Fi, WLAN oder Netzwerk verbunden sind.
+Unter Windows, Systemsteuerung / Netzwerk und Internet öffnen +und sicherstellen, dass Privates Netzwerk als “Netzwerkprofiltyp” ausgewählt ist. +(nach der Übertragung kann wieder der ursprüngliche Wert verwendet werden)
+Auf iOS, sicherstellen, dass „Systemeinstellungen / Apps / Delta Chat / Lokales Netzwerk“ eingeschaltet ist
+Auf macOS, „Systemeinstellungen / Datenschutz & Sicherheit / Lokales Netzwerk / Delta Chat“ aktivieren
+Dein System verfügt möglicherweise über eine “Personal Firewall”; diese sind dafür bekannt, Probleme zu verursachen (insbesondere bei Windows). Deaktiviere die Personal Firewall für Delta Chat auf beiden Seiten und versuch es erneut
+In Gastnetzwerken z.B. der Fritz!Box, können Geräte möglicherweise nicht miteinander kommunizieren. +Verwende nach Möglichkeit ein Nicht-Gast-Netzwerk. Wenn du Zugriff auf den Router hast, kannst du auch die Kommunikation der Geräte untereinander für die Dauer der Übertragung erlauben.
+Wenn du immer noch Probleme bei der Verwendung desselben Netzwerks hast, +versuche, einen Mobilen Hotspot auf einem Gerät zu öffnen und dich mit dem anderen Gerät in dieses WLAN einzuwählen.
+Vergewissere dich, dass das Zielgerät über genügend Speicher verfügt
+Wenn die Übertragung begonnen hat, stelle sicher, dass die Geräte aktiv bleiben und nicht ausgehen. Beende Delta Chat nicht. (wir bemühen uns, die App im Hintergrund laufen zu lassen, aber Systeme neigen dazu, Apps zu beenden, leider)
+Du bist auf dem Zielgerät bereits eingeloggt? Du kannst mehrere Profile pro Gerät verwenden, füge einfach ein weiteres Konto hinzu
+Wenn du immer noch Probleme hast oder wenn du keinen QR-Code scannen kannst, versuche die manuelle Übertragung wie unten beschrieben
+Diese Methode wird nur empfohlen, wenn “Zweites Gerät hinzufügen”, wie oben beschrieben, nicht funktioniert.
+ +Unter Einstellungen → Erweitert → Experimentelle Features +kannst du unfertige Features ausprobieren, an denen gearbeitet wird.
+ +Die Features können instabil sein und geändert oder entfernt werden.
+ +You can find more information +and give feedback in the Forum.
+ +We would like to improve Delta Chat with your help, +which is why Delta Chat for Android asks whether you want +to send anonymous usage statistics.
+ +You can turn it on and off at +Settings → Advanced → Send statistics to Delta Chat’s developers.
+ +When you turn it on, +weekly statistics will be automatically sent to a bot.
+ +We are interested e.g. in statistics like:
+ +We will not collect any personally identifiable information about you.
+ +Yes, but only if the email address is used exclusively by chatmail clients.
+ +It is not supported to share usage of an email address with non-chatmail apps or web-based mailers, +for the following reasons:
+ +Non-chatmail apps are largely not accomplishing automatic end-to-end email encryption for their users, +while chatmail apps and relays pervasively enforce end-to-end encryption and security standards.
+Non-chatmail apps use email servers as a long-term message archive +while chatmail clients use email servers for ephemeral instant message relay.
+Supporting the full variety of classic email setups +would require considerable development and maintenance efforts, +and complicate making chatmail-based messaging more resilient, reliable and fast.
+First off, please do not use the same classic email address also from non-chatmail classic email apps +unless you are prepared to deal with encrypted messages in the inbox, +double notifications, accidentally deleted emails or similar annoyances.
+ +You can configure a email address for chatting at New Profile → Use Other Server → Use Classic Mail as Relay.
+Note that classic email providers will generally not support Push Notifications
+and have other limitations, see Provider Overview.
+Chatmail uses the default INBOX for relay; ensure the provider setup does too.
+A chat profile using a classic email address allows to to send and receive unencrypted messages.
+These messages, and the chats they appear in, are marked with an email icon
+
.
Any well behaving email server setup will do fine +except if your users’ devices require Google/Apple Push Notifications to work properly.
+ +We generally recommend to set up a chatmail relay. +Chatmail is a community-driven project that encompasses both the setup of relays +and core Rust developments +that power chatmail clients of which Delta Chat is the most well known.
+ +Delta Chat verwendet eine sichere Teilmenge des OpenPGP-Standards, um eine automatische End-to-End-Verschlüsselung mit folgenden Protokollen bereitzustellen:
+ +Secure-Join +zum Austausch von Verschlüsselungsinformationen durch Scannen von QR-Codes oder „Einladungslinks“.
+Autocrypt wird verwendet, um automatisch eine Ende-zu-Ende-Verschlüsselung zwischen Kontakten und allen Mitgliedern einer Gruppe herzustellen.
+Teilen eines Kontakts im Chat +ermöglicht es den Empfängern, eine Ende-zu-Ende-Verschlüsselung mit dem Kontakt zu verwenden.
+Delta Chat fragt keine OpenPGP-Keyserver ab, veröffentlicht dort keine Daten und interagiert auch sonst nicht mit diesen.
+ +Alle Nachrichten in Delta Chat sind standardmäßig Ende-zu-Ende-verschlüsselt. +Seit der Veröffentlichung von Delta Chat Version 2 (Juli 2025) gibt es keine Schlösser oder ähnliche Markierungen mehr an Ende‑zu‑Ende-verschlüsselten Nachrichten.
+ +Wenn du die Standard-Chatmail-Relays verwendest, ist es unmöglich, Nachrichten ohne End-to-End-Verschlüsselung zu empfangen oder zu senden.
+ +If you instead use a classic email server,
+you can send and receive messages with or without end-to-end encryption.
+Messages lacking end-to-end encryption are marked with an email icon
+
.
A contact profile might show a green checkmark
+
+and an “Introduced by” line.
+Every green-checkmarked contact either did a direct QR-scan with you
+or was introduced by a another green-checkmarked contact.
+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 QR-scan.
Für eine ausführlichere Diskussion der “Garantierten Ende-zu-Ende-Verschlüsselung”, +siehe Secure-Join-Protokolle +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”.
+ +Ja.
+ +Wenn wir von einer “Ende-zu-Ende-verschlüsselten Nachricht” sprechen +meinen wir immer, dass eine ganze Nachricht verschlüsselt ist, +einschließlich aller Anhänge +und Anhang-Metadaten wie Dateinamen.
+ +Ja, Delta Chat verwendet ein sicheres subset von OpenPGP +das verlangt, dass die gesamte Nachricht ordnungsgemäß verschlüsselt und signiert wurde. +Als Beispiel, werden “angehängte Signaturen” nicht als sicher behandelt.
+ +Die meisten öffentlich diskutierten OpenPGP-Probleme +resultieren in Wirklichkeit aus schlechter Usability oder schlechter Implementierung von Tools oder Anwendungen - oder beidem. +Es ist besonders wichtig, zwischen OpenPGP, dem IETF-Verschlüsselungsstandard +und GnuPG (GPG), einem Kommandozeilenprogramm, das OpenPGP implementiert, zu unterscheiden. +In vielen öffentlichen Kritiken zu OpenPGP wird GnuPG diskutiert, das Delta Chat nie verwendet hat. +Delta Chat verwendet stattdessen die OpenPGP-Rust-Implementierung rPGP, +die als ein unabhängiges “pgp”-Paket, +verfügbar ist und 2019 und 2024 sicherheitsgeprüft wurde.
+ +Unser Ziel ist, zusammen mit anderen OpenPGP-Implementierungen, +die Sicherheitseigenschaften durch das im Sommer 2023 angenommene +IETF OpenPGP Crypto-Refresh weiter zu verbessern.
+ +Yes, we are following efforts like MLS +but adopting them would mean breaking end-to-end encryption interoperability. +So it would not be a light decision to take +and there must be tangible improvements for users.
+ +Delta Chat verfolgt einen ganzheitlichen Ansatz bei der “nutzbaren Sicherheit”: +Wir arbeiteten mit vielen Aktivistengruppen sowie mit +renommierten Forschern wie TeamUSEC zusammen, +um die tatsächlichen Ergebnisse der Benutzer gegen Sicherheitsbedrohungen zu verbessern. +Das Wire-Protokoll und der Standard für die Einrichtung der Ende-zu-Ende-Verschlüsselung ist +nur ein Teil der Ergebnisse, +siehe auch unsere Antworten auf Gerätebeschlagnahmung +und Metadaten Fragen.
+ +Nein, Delta Chat war nie anfällig für EFAIL. +Delta Chats OpenPGP-Implementierung rPGP +verwendet beim Verschlüsseln von Nachrichten “Modification Detection Codes” +und gibt Fehler zurück, +wenn dieser falsch ist.
+ +Delta Chat war auch nie anfällig für den EFAIL-Angriff “Direct Exfiltration”,
+da nur multipart/encrypted Nachrichten entschlüsselt werden,
+die genau einen verschlüsselten und signierten Teil enthalten;
+so wie in der Autocrypt-Level-1-Spezifikation definiert.
If you are sending or receiving email messages without end-to-end encryption (using a classic email server), +they are still protected from cell or cable companies who can not read or modify your email messages. +But both your and your recipient’s email providers +may read, analyze or modify your messages, including any attachments.
+ +Delta Chat by default uses strict +TLS encryption +which secures connections between your device and your email provider. +All of Delta Chat’s TLS-handling has been independently security audited. +Moreover, the connection between your and the recipient’s email provider +will typically be transport-encrypted as well. +If the involved email servers support MTA-STS +then transport encryption will be enforced between email providers +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.
+ +Anders als die meisten anderen Messenger +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.
+ +Servers can therefore only see:
+ +By default, the addresses are randomly generated.
+ +Alle anderen Metadaten zu Nachrichten, Kontakten und Gruppen befinden sich im Ende-zu-Ende-verschlüsselten Teil der Nachrichten.
+ +Both for protecting against metadata-collecting servers +as well as against the threat of device seizure +we recommend to use a chatmail relay +to create chat profiles using random 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.
+ +Nein, noch nichts.
+ +Der Signal-Messenger führte 2018 “Sealed Sender” ein +um seine Serverinfrastruktur darüber im Unklaren zu lassen, wer eine Nachricht an eine Gruppe von Empfängern sendet. +Dies ist besonders wichtig, weil der Signal-Server die Handynummer jedes Kontos kennt, +die in der Regel mit einer Passidentität verbunden ist.
+ +Even if chatmail relays +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 addresses for sealed sending +but an implementation has not been agreed as a priority yet.
+ +Nein, noch nichts.
+ +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.
+ +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 chatmail core, +which would make it available in all chatmail clients.
+ +Nein, noch nichts.
+ +Delta Chat verwendet die Rust OpenPGP-Bibliothek rPGP +die den neuesten IETF Post-Quantum-Cryptography OpenPGP Entwurf unterstützt. +Wir beabsichtigen, PQC-Unterstützung zum chatmail core hinzuzufügen, sobald der Entwurf bei der IETF in Zusammenarbeit mit anderen OpenPGP-Implementierern fertiggestellt ist.
+ +Du kannst 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.
+ +Nein.
+ +Delta Chat generates secure OpenPGP keys according to the Autocrypt specification 1.1. +We do not recommend or offer users to perform manual key management. +We want to ensure that security audits can focus on a few proven cryptographic algorithms +instead of the full breadth of possible algorithms allowed with OpenPGP. +If you want to extract your OpenPGP key, there only is an expert method: +you need to look it up in the “keypairs” SQLite table of a profile backup tar-file.
+ +Ja, mehrfach. +Das Delta-Chat-Projekt wird kontinuierlich unabhängigen Sicherheitsaudits und -analysen unterzogen:
+ +Im Dezember 2024 fand eine von NLNET in Auftrag gegebene Bewertung von rPGP durch Radically Open Security statt. +rPGP wird für die OpenPGP-Ende-zu-Ende-Verschlüsselung verwendet. +Im Zusammenhang mit den Ergebnissen dieser Prüfung wurden zwei Hinweise veröffentlicht:
+ +Die in diesen Hinweisen beschriebenen Probleme wurden behoben und sind Bestandteil der Delta Chat Veröffentlichungen in allen Appstores seit Dezember 2024.
+Im März 2024 erhielten wir von der Forschungsgruppe “Applied Cryptography” der ETH Zürich eine umfassende Sicherheitsanalyse und haben alle aufgeworfenen Fragen adressiert. +Weitere Informationen findest du in unserem Blogbeitrag über Hardening Guaranteed End-to-End encryption und in der hinterher publizierten Kryptografischen Analyse von Delta Chat
+Im April 2023 haben wir Sicherheits- und Datenschutzprobleme mit dem “In Chats geteilten Apps”-Feature behoben, die mit Fehlern beim Sandboxing, insbesondere mit Chromium zusammenhängen. Wir haben daraufhin eine unabhängige Sicherheitsprüfung von Cure53 durchführen lassen, und alle gefundenen Probleme wurden mit den im April 2023 veröffentlichten 1.36 Releases behoben. Siehe hier für die vollständige Hintergrundgeschichte.
+Im März 2023 analysierte Cure53 sowohl die Transportverschlüsselung von Delta Chats Netzwerkverbindungen als auch das reproduzierbare Mailserver-Setup wie auf dieser Seite empfohlen. Du kannst mehr über das Audit in unserem Blog lesen oder du liest den vollständigen Bericht hier.
+Im Jahr 2020 analysierte Include Security Delta Chats Rust core, IMAP,SMTP, und TLS Bibliotheken. +Es wurden keine kritischen oder hochgradig gefährlichen Probleme gefunden. Der Bericht wies auf einige Schwachstellen mittlerer Schwere hin - sie stellen für sich genommen keine Bedrohung für Delta-Chat-Benutzer dar, da sie von der Umgebung abhängen, in der Delta Chat verwendet wird. Aus Gründen der Benutzerfreundlichkeit und der Kompatibilität können wir nicht alle Schwachstellen beseitigen und haben beschlossen, Sicherheitsempfehlungen für bedrohte Benutzer zu geben. Du kannst den vollständigen Bericht hier lesen.
+Im Jahr 2019 analysierte Include Security die von Delta Chat verwendeten PGP- und RSA- Bibliotheken. +Es wurden keine kritischen Probleme gefunden, aber zwei Probleme mit hohem Schweregrad, die wir anschließend behoben haben. Außerdem wurden ein mittelschweres und einige weniger schwerwiegende Probleme gefunden, aber es gab keine Möglichkeit, diese Schwachstellen in der Delta-Chat-Implementierung auszunutzen. Einige dieser Schwachstellen haben wir dennoch nach Abschluss des Audits behoben. Du kannst den vollständigen Bericht hier lesen.
+Some features require certain permissions, +e.g. you need to grant camera permission if you want to scan an invite QR code.
+ +See Privacy Policy for a detailed overview.
+ +Delta Chat ist für alle großen und einige kleinere Plattformen verfügbar:
+ +Die offizielle Website, https://delta.chat/download zeigt alle Optionen im Detail
+Falls nicht verfügbar, verwende den Mirror auf https://deltachat.github.io/deltachat-pages
+Öffne einen der folgenden App-Stores und suchen Sie nach „Delta Chat“: Google Play Store, F-Droid, Huawei App Gallery, iOS und macOS App Store, Microsoft Store
+Im Paketmanager Ihrer Linux-Distribution nachschauen
+Android-APKs sind auch auf https://github.com/deltachat/deltachat-android/releases verfügbar.
+Delta Chat erhält kein Risikokapital, ist nicht verschuldet und steht unter keinem Druck, große Gewinne zu erzielen oder Nutzer, deren Freunde und Familie an Werbekunden zu verkaufen (oder Schlimmeres). +Wir nutzen vielmehr öffentliche Finanzierungsquellen, die bisher aus der EU und den USA stammen, um ein dezentrales und diverses Chat-Messaging-Ökosystem zu schaffen, basierend auf freien und quelloffenen Entwicklungen der Gemeinschaft.
+ +Konkret wurden die Delta-Chat-Entwicklungen bisher aus diesen Quellen finanziert:
+ +Das EU-Projekt NEXTLEAP finanzierte 2017 und 2018 die Entwicklung und Implementierung von “Verifizierten Gruppen” und “Setup Kontakt” und half auch bei der Integration der Ende-zu-Ende-Verschlüsselung durch Autocrypt.
+Der Open Technology Fund hat Delta Chat erstmals 2018/2019 bezuschusst; mit dieser Förderung (~$200K) wurden hauptsächlich die Android-App verbessert sowie das Release der Desktop-App in einer Betaversion ermöglicht. Basierend auf Nutzererfahrungen im Menschenrechtskontext wurden zudem verschiedene Funktionen entwickelt, siehe unseren Bericht Needfinding and UX report. +Die zweite Förderung 2019/2020 (~$300K) half uns bei der Erstellung der iOS-Version, unsere Kernbibliothek in die Programmiersprache “Rust” zu konvertieren und neue Funktionen für alle Plattformen bereitzustellen.
+Die NLnet-Stiftung bewilligte 2019/2020 46K EUR für die Fertigstellung von Rust-/Python-Bindungs und die Einrichtung eines Chat-Bot-Ökosystems.
+Im Jahr 2021 erhielten wir weitere EU-Mittel für zwei “Next-Generation-Internet”-Anträge, nämlich für EPPD - E-Mail-Provider-Portabilitätsverzeichnis (~97K EUR) und AEAP - E-Mail-Adressportierung (~90K EUR). Ziel sind bessere Unterstützung von Mehrfachkonten, verbesserten QR-Code-Kontakt- und -Gruppen-Setups sowie Netzwerkverbesserungen auf allen Plattformen.
+Von Ende 2021 bis März 2023 erhielten wir eine Internet-Freedom-Finanzierung (500K USD) vom U.S. Bureau of Democracy, Human Rights and Labor (DRL). Diese Finanzierung unterstützte unsere langjährigen Ziele, Delta Chat benutzerfreundlicher und kompatibel mit einer breiten Palette von E-Mail-Servern weltweit zu machen, sowie widerstandsfähiger und sicherer an Orten, die häufig von Internetzensur und Abschaltungen betroffen sind.
+2023-2024 schlossen wir erfolgreich das vom OTF finanzierte +Secure-Chatmail-Projekt ab. +Dieses fügt “Garantierte Verschlüsselung”, +das Chatmail-Server-Netzwerk +und „Instant Onboarding“ allen ab April 2024 veröffentlichten Anwendungen hinzu.
+2023 und 2024 wurden wir in das Next-Generation-Internet-Programm (NGI) +für unsere Arbeit an Webxdc-PUSH aufgenommen, +zusammen mit Kooperationspartnern, die an +Webxdc-Evolve, +Webxdc-XMPP, +DeltaTouch und +DeltaTauri. +Alle diese Projekte sind teilweise abgeschlossen oder sollen Anfang 2025 abgeschlossen werden.
+Manchmal erhalten wir einmalige Spenden von Privatpersonen, wofür wir sehr dankbar sind. Im Jahr 2021 hat uns zum Beispiel eine großzügige Privatperson 4000 EUR überwiesen mit dem Betreff “Weiter so!” 💜 Wir verwenden dieses Geld zur Finanzierung von Entwicklungstreffen oder zur Deckung von Ad-hoc-Ausgaben, die nicht ohne weiteres vorhersehbar sind oder nicht aus öffentlichen Fördermitteln erstattet werden können. +Der Erhalt von Spenden hilft uns auch, unabhängiger und langfristig lebensfähig zu werden, als Gemeinschaft.
+ + +Last but by far not least beteiligen sich verschiedene ExpertInnen und Engagierte pro bono an Delta Chat. Sie erhalten dafür teils nur wenig, oftmals sogar überhaupt kein Geld. Ohne sie wäre Delta Chat nicht im entferntesten das, was es heute ist!
+Die oben aufgeführte finanzielle Förderung wird hauptsächlich von der merlinux GmbH in Freiburg (Deutschland) organisiert und an mehr als ein Dutzend Mitwirkende weltweit verteilt.
+ +Möglichkeiten mitzuwirken findest du auf der Delta-Chat-Seite “Mitwirken”.
+ + + + + \ No newline at end of file diff --git a/src/main/assets/help/edit-icon.png b/src/main/assets/help/edit-icon.png new file mode 100644 index 0000000000000000000000000000000000000000..6da58203587a4e3b6b8d5c72a311e63202f7422c Binary files /dev/null and b/src/main/assets/help/edit-icon.png differ diff --git a/src/main/assets/help/email-icon.png b/src/main/assets/help/email-icon.png new file mode 100644 index 0000000000000000000000000000000000000000..ea1cf1d8fe3dc0bd3829d0a418710b03b22eefeb Binary files /dev/null and b/src/main/assets/help/email-icon.png differ diff --git a/src/main/assets/help/en/help.html b/src/main/assets/help/en/help.html new file mode 100644 index 0000000000000000000000000000000000000000..fe024d151c606b6b1764cf77b14951b34ae81302 --- /dev/null +++ b/src/main/assets/help/en/help.html @@ -0,0 +1,1674 @@ + +Delta Chat is a reliable, decentralized and secure instant messaging app, +available for mobile and desktop platforms.
+ +Instant creation of private chat profiles +with secure and interoperable chatmail relays +that offer instant message delivery, and Push Notifications for iOS and Android devices.
+Pervasive multi-profile and +multi-device support on all platforms +and between different chatmail apps.
+Interactive in-chat apps for gaming and collaboration
+Audited end-to-end encryption +safe against network and server attacks.
+Free and Open Source software, both app and server side, +built on Internet Standards.
+First, note that Delta Chat is a private messenger. +There is no public discovery, you decide about your contacts.
+ +If you are face to face with your friend or family,
+tap the QR Code icon
+on the main screen.
+Ask your chat partner to scan the QR image
+with their Delta Chat app.
For a remote contact setup, +from the same screen, +click “Copy” or “Share” and send the invite link +through another private chat.
+Now wait while connection gets established.
+ +If both sides are online, they will soon see a chat +and can start messaging securely.
+If one side is offline or in bad network, +the ability to chat is delayed until connectivity is restored.
+Congratulations! +You now will automatically use end-to-end encryption with this contact. +If you add each other to groups, end-to-end encryption will be established among all members.
+ +As being a private messenger, +only friends and family you share your QR code or invite link with can write to you.
+ +Your friends may share your contact with other friends, this appears as a request.
+ +You need to accept the request before you can reply.
+You can also delete it if you don’t want to chat with them for now.
+If you delete a request, future messages from that contact will still appear +as message request, so you can change your mind. If you really don’t want to +receive messages from this person, consider blocking them.
+Attach the first contact to the chat of the second using
Attachment Button → Contact.
+You can also add a little introduction message.
The second contact will receive a card then +and can tap it to start chatting with the first contact.
+ +Yes. Images, videos, files, voice messages etc. can be sent using the
Attachment-
+or
Voice Message buttons
For performance, images are optimized and sent at a smaller size by default, but you can send it as a “file” to preserve the original.
+A profile is a name, a picture and some additional information for encrypting messages. +A profile lives on your device(s) only +and uses the server only to relay messages.
+ +On first installation of Delta Chat a first profile is created.
+ +Later, you can tap your profile image in the upper left corner to Add Profiles +or to Switch Profiles.
+ +You may want to use separate profiles for political, family or work related activities.
+ +You may also wish to learn how to use the same profile on multiple devices.
+ +You can add a profile picture in your settings. If you write to your contacts +or add them via QR code, they automatically see it as your profile picture.
+For privacy reasons, no one sees your profile picture until you write a +message to them.
+Yes, +you can do so under Settings → Profile → Bio. +Once you sent a message to a contact, +they will see it when they view your contact details.
+ +Use these tools to organize your chats and keep everything in its place:
+ +Pinned chats always stay atop of the chat list. You can use them to access your most loved chats quickly or temporarily to not forget about things.
+Mute chats if you do not want to get notifications for them. Muted chats stay in place and you can also pin a muted chat.
+Archive chats if you do not want to see them in your chat list any longer. +Archived chats remain accessible above the chat list or via search.
+When an archived chat gets a new message, unless muted, it will pop out of the archive and back into your chat list. +Muted chats stay archived until you unarchive them manually.
+To use the functions, long tap or right click a chat in the chat list.
+ +Saved Messages is a chat that you can use to easily remember and find messages.
+ +In any chat, long tap or right click a message and select Save
+Saved messages are marked by the symbol
+
+next to the timestamp
Later, open the “Saved Messages” chat - and you will see the saved messages there.
+By tapping
,
+you can go back to the original message in the original chat
Finally, you can also use “Save Messages” to take personal notes - open the chat, type something, add a photo or a voice message etc.
+As “Saved Message” are synced, they can become very handy for transferring data between devices
+Messages stay saved even if they are edited or deleted - +may it be by sender, by device cleanup or by disappearing messages of other chats.
+ +You can sometimes see a green dot
+next to the avatar of a contact.
+It means they were recently seen by you in the last 10 minutes,
+e.g. because they messaged you or sent a read receipt.
So this is not a real time online status +and others will as well not always see that you are “online”.
+ +One tick
+means that the message was sent successfully to your provider.
Two ticks
+mean that at least one recipient’s device
+reported back to having received the message.
Recipients may have disabled read-receipts, +so even if you see only one tick, the message may have been read.
+The other way round, two ticks do not automatically mean +that a human has read or understood the message ;)
+You can edit the text of your messages after sending.
+For that, long tap or right click the message and select Edit
+or
.
If you have sent a message accidentally, +from the same menu, select Delete and then Delete for Everyone.
+While edited messages will have the word “Edited” next to the timestamp, +deleted messages will be removed without a marker in the chat. +Notifications are not sent and there is no time limit.
+ +Note, that the original message may still be received by chat members +who could have already replied, forwarded, saved, screenshotted or otherwise copied the message.
+ +You can turn on “disappearing messages” +in the settings of a chat, +at the top right of the chat window, +by selecting a time span +between 5 minutes and 1 year.
+ +Until the setting is turned off again, +each chat member’s Delta Chat app takes care +of deleting the messages +after the selected time span. +The time span begins +when the receiver first sees the message in Delta Chat. +The messages are deleted both, +on the servers, +and in the apps itself.
+ +Note that you can rely on disappearing messages +only as long as you trust your chat partners; +malicious chat partners can take photos, +or otherwise save, copy or forward messages before deletion.
+ +Apart from that, +if one chat partner uninstalls Delta Chat, +the (anyway encrypted) messages may take longer to get deleted from their server.
+ +If you are using more than one chat profile, +you can remove single ones in the top profile switcher menu (on Android and iOS), +or in the sidebar with a right click (in the Desktop app). +Chat profiles are only removed on the device where deletion was triggered. +Chat profiles on other devices will continue to fully function.
+ +If you use a single default chat profile you can simply uninstall the app. +This will still automatically trigger deletion of all associated address data on the chatmail server. +For more info, please refer to nine.testrun.org address-deletion +or the respective page from your chosen 3rd party chatmail server.
+ +Groups let several people chat together privately with equal rights.
+ +Anyone can +change the group name or avatar, +add or remove members, +set disappearing messages, +and delete their own messages from all member’s devices.
+ +Because all members have the same rights, groups work best among trusted friends and family.
+ +All group members have the same rights. +For this reason, everyone can delete any member or add new ones.
+To add or delete members, tap the group name in the chat and select the member to add or remove.
+If the member is not yet in your contact list, but face to face with you,
+from the same screen, show a QR code.
+Ask your chat partner to scan the QR image with their Delta Chat app by tapping
+
on the main screen.
For a remote member addition, +click “Copy” or “Share” and send the invite link +through another private chat to the new member.
+QR code and invite link can be used to add several members. +However, since groups are meant for trusted people, avoid sharing them publicly.
+ +Either delete yourself from the member list or delete the whole chat. +If you want to join the group again later on, ask another group member to add you again.
+As an alternative, you can also “Mute” a group - doing so means you get all messages and +can still write, but are no longer notified of any new messages.
+You can duplicate a group to start a separate discussion +or to exclude members without them noticing.
+ +Open the group profile and tap Clone Chat (Android/iOS), +or right-click the group in the chat list (Desktop).
+Set a new name, choose an avatar, and adjust the member list if needed.
+The new group is fully independent from the original, +which continues to work as before.
+ +You can send apps to a chat - games, editors, polls and other tools. +This makes Delta Chat a truly extensible messenger.
+ +In a chat, using
Attachment Button → Apps
You can also create your own app and attach it using
Attachment Button → File
In-chat apps can not send data to the Internet, or download anything.
+An in-chat app can only exchange data within a chat, with its +copies on the devices of your chat partners. Other than that, it’s completely +isolated from the Internet.
+The privacy an in-chat app offers is the privacy of your chat - as long as you +trust the people you chat with, you can trust the in-chat app as well.
+This also means: Just like for web links, do not open apps from untrusted contacts.
+In-chat apps are zip files with .xdc extension containing html, css, and javascript code.
You can extend the Hello World example app +to get started.
+All else you need to know is written in the +Webxdc documentation.
+If you have question, you can ask others with experience +in the Delta Chat Forum.
+Push Notifications are sent by Apple and Google “Push services” to a user’s device +so that an inactive Delta Chat app can fetch messages in the background +and show notifications on a user’s phone if needed.
+ +Push Notifications work with all chatmail servers on
+ +iOS devices, by integrating with Apple Push services.
+Android devices, by integrating with the Google FCM Push service, +including on devices that use microG +instead of proprietary Google code on the phone.
+Yes, Delta Chat automatically uses Push Notifications for chatmail profiles. +And no, there is no alternative on Apple’s phones to achieve instant message delivery +because Apple devices do not allow Delta Chat to fetch data in the background. +Push notifications are automatically activated for iOS users because +Delta Chat’s privacy-preserving Push Notification system +does not expose data to Apple that it doesn’t already have.
+ +If a “Push Service” is available, Delta Chat enables Push Notifications +to achieve instant message delivery for all chatmail users.
+ +In the Delta Chat “Notifications” settings for “Instant delivery” +you can change the following settings effecting all chat profiles:
+ +Use Background Connection: If you are not using a Push service, +you may disable “battery optimizations” for Delta Chat, +allowing it to fetch messages in the background. +However, there could be delays from minutes to hours. +Some Android vendors even restrict apps completely +(see dontkillmyapp.com) +and Delta Chat might not show incoming messages +until you manually open the app again.
+Force Background Connection: This is the fallback option +if the previous options are not available or do not achieve “instant delivery”. +Enabling it causes a permanent notification on your phone +which may sometimes be “minified” with recent Android phones.
+Both “Background Connection” options are energy-efficient and +safe to try if you experience messages arrive only with long delays.
+ +Delta Chat Push Notification support avoids leakage of private information. +It does not leak profile data, IP address or message content (not even encrypted) +to any system involved in the delivery of Push Notifications.
+ +Here is how Delta Chat apps perform Push Notification delivery:
+ +A Delta Chat app obtains a “device token” locally, encrypts it and stores it +on the chatmail server.
+When a chatmail server receives a message for a Delta Chat user +it forwards the encrypted device token to the central Delta Chat notification proxy.
+The central Delta Chat notification proxy decrypts the device token +and forwards it to the respective Push service (Apple, Google, etc.), +without ever knowing the IP or profile data of Delta Chat users.
+The central Push Service (Apple, Google, etc.) +wakes up the Delta Chat app on your device +to check for new messages in the background. +It does not know about the profile data of the device it wakes up. +The central Apple/Google Push services never see any profile data (sender or receiver) +and also never see any message content (also not in encrypted forms).
+The central Delta Chat notification proxy is small and fully implemented in Rust +and forgets about device-tokens as soon as Apple/Google/etc processed them, +usually in a matter of milliseconds.
+ +Note that the device token is encrypted between apps and notification proxy +but it is not signed. +The notification proxy thus never sees profile data, IP-addresses or +any cryptographic identity information associated with a user’s device (token).
+ +Resulting from this overall privacy design, even the seizure of a chatmail server, +or the full seizure of the central Delta Chat notification proxy +would not reveal private information that Push services do not already have.
+ +Delta Chat is a free and open source decentralized messenger with free server choice, +but we want users to reliably experience “instant delivery” of messages, +like they experience from WhatsApp, Signal or Telegram apps, +without asking questions up-front that are more suited to expert users or developers.
+ +Note that Delta Chat has a small and privacy-preserving Push Notification system +that achieves “instant delivery” of messages for all chatmail servers +including a potential one you might setup yourself without our permission. +Welcome to the power of the interoperable chatmail relay network :)
+ +Yes. You can use the same profile on different devices:
+ +Make sure both devices are on the same Wi-Fi or network
+On the first device, go to Settings → Add Second Device, unlock the screen if needed +and wait a moment until a QR code is shown
+On the second device, install Delta Chat
+On the second device, start Delta Chat, select Add as Second Device, and scan the QR code from the old device
+Transfer should start after a few seconds and during transfer both devices will show the progress. +Wait until it is finished on both devices.
+In contrast to many other messengers, after successful transfer, +both devices are completely independent. +One device is not needed for the other to work.
+ +Double-check both devices are in the same Wi-Fi or network
+On Windows, go to Control Panel / Network and Internet +and make sure, Private Network is selected as “Network profile type” +(after transfer, you can change back to the original value)
+On iOS, make sure “System Settings / Apps / Delta Chat / Local Network” access is granted
+On macOS, enable “System Settings / Privacy & Security / Local Network / Delta Chat”
+Your system might have a “personal firewall”, +which is known to cause problems (especially on Windows). +Disable the personal firewall for Delta Chat on both ends and try again
+Guest Networks may not allow devices to communicate with each other. +If possible, use a non-guest network.
+If you still have troubles using the same network, +try to open Mobile Hotspot on one device and join that Wi-Fi from the other one
+Ensure there is enough storage on the destination device
+If transfer started, make sure, the devices stay active and do not fall asleep. +Do not exit Delta Chat. +(we try hard to make the app work in background, but systems tend to kill apps, unfortunately)
+Delta Chat is already logged in on the destination device? +You can use multiple profiles per device, just add another profile
+If you still have problems or if you cannot scan a QR code +try the manual transfer described below
+This method is only recommended if “Add Second Device” as described above does not work.
+ +At Settings → Advanced → Experimental Features +you can try out features we are working on.
+ +The features may be unstable and may be changed or removed.
+ +You can find more information +and give feedback in the Forum.
+ +Yes, but only if the email address is used exclusively by chatmail clients.
+ +It is not supported to share usage of an email address with non-chatmail apps or web-based mailers, +for the following reasons:
+ +Non-chatmail apps are largely not accomplishing automatic end-to-end email encryption for their users, +while chatmail apps and relays pervasively enforce end-to-end encryption and security standards.
+Non-chatmail apps use email servers as a long-term message archive +while chatmail clients use email servers for ephemeral instant message relay.
+Supporting the full variety of classic email setups +would require considerable development and maintenance efforts, +and complicate making chatmail-based messaging more resilient, reliable and fast.
+First off, please do not use the same classic email address also from non-chatmail classic email apps +unless you are prepared to deal with encrypted messages in the inbox, +double notifications, accidentally deleted emails or similar annoyances.
+ +You can configure a email address for chatting at New Profile → Use Other Server → Use Classic Mail as Relay.
+Note that classic email providers will generally not support Push Notifications
+and have other limitations, see Provider Overview.
+Chatmail uses the default INBOX for relay; ensure the provider setup does too.
+A chat profile using a classic email address allows to to send and receive unencrypted messages.
+These messages, and the chats they appear in, are marked with an email icon
+
.
Any well behaving email server setup will do fine +except if your users’ devices require Google/Apple Push Notifications to work properly.
+ +We generally recommend to set up a chatmail relay. +Chatmail is a community-driven project that encompasses both the setup of relays +and core Rust developments +that power chatmail clients of which Delta Chat is the most well known.
+ +We would like to improve Delta Chat with your help, +which is why Delta Chat for Android asks whether you want +to send anonymous usage statistics.
+ +You can turn it on and off at +Settings → Advanced → Send statistics to Delta Chat’s developers.
+ +When you turn it on, +weekly statistics will be automatically sent to a bot.
+ +We are interested e.g. in statistics like:
+ +How many contacts are introduced by personally scanning a QR code?
+Which versions of Delta Chat are being used?
+What errors occur for users?
+We will not collect any personally identifiable information about you.
+ +Delta Chat uses a secure subset of the OpenPGP standard +to provide automatic end-to-end encryption using these protocols:
+ +Secure-Join +to exchange encryption setup information through QR-code scanning or “invite links”.
+Autocrypt is used for automatically +establishing end-to-end encryption between contacts and all members of a group chat.
+Sharing a contact to a +chat +enables receivers to use end-to-end encryption with the contact.
+Delta Chat does not query, publish or interact with any OpenPGP key servers.
+ +All messages in Delta Chat are end-to-end encrypted by default. +Since the Delta Chat Version 2 release series (July 2025) +there are no lock or similar markers on end-to-end encrypted messages, anymore.
+ +If you use default chatmail relays, +it is impossible to receive or send messages without end-to-end encryption.
+ +If you instead use a classic email server,
+you can send and receive messages with or without end-to-end encryption.
+Messages lacking end-to-end encryption are marked with an email icon
+
.
A contact profile might show a green checkmark
+
+and an “Introduced by” line.
+Every green-checkmarked contact either did a direct QR-scan with you
+or was introduced by a another green-checkmarked contact.
+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 QR-scan.
For more in-depth discussion of “guaranteed end-to-end encryption” +please see Secure-Join protocols +and specifically read about “Verified Groups”, the technical term +of what is called here “green-checkmarked” or “guaranteed end-to-end encrypted” chats.
+ +Yes.
+ +When we talk about an “end-to-end encrypted message” +we always mean a whole message is encrypted, +including all the attachments +and attachment metadata such as filenames.
+ +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.
+ +OpenPGP is not insecure by itself. +Most publicly discussed OpenPGP security problems +actually stem from bad usability or bad implementations of tools or apps (or both). +It is particularly important to distinguish between OpenPGP, the IETF encryption standard, +and GnuPG (GPG), a command line tool implementing OpenPGP. +Many public critiques of OpenPGP actually discuss GnuPG which Delta Chat has never used. +Delta Chat rather uses the OpenPGP Rust implementation rPGP, +available as an independent “pgp” package, +and security-audited in 2019 and 2024.
+ +We aim, along with other OpenPGP implementors, +to further improve security characteristics by implementing the +new IETF OpenPGP Crypto-Refresh +which was thankfully adopted in summer 2023.
+ +Yes, we are following efforts like MLS +but adopting them would mean breaking end-to-end encryption interoperability. +So it would not be a light decision to take +and there must be tangible improvements for users.
+ +Delta Chat takes a holistic “usable security” approach +and works with a wide range of activist groupings as well as +renowned researchers such as TeamUSEC +to improve actual user outcomes against security threats. +The wire protocol and standard for establishing end-to-end encryption is +only one part of “user outcomes”, +see also our answers to device-seizure +and message-metadata questions.
+ +No, Delta Chat never was vulnerable to EFAIL +because its OpenPGP implementation rPGP +uses Modification Detection Code when encrypting messages +and returns an error +if the Modification Detection Code is incorrect.
+ +Delta Chat also never was vulnerable to the “Direct Exfiltration” EFAIL attack
+because it only decrypts multipart/encrypted messages
+which contain exactly one encrypted and signed part,
+as defined by the Autocrypt Level 1 specification.
If you are sending or receiving email messages without end-to-end encryption (using a classic email server), +they are still protected from cell or cable companies who can not read or modify your email messages. +But both your and your recipient’s email providers +may read, analyze or modify your messages, including any attachments.
+ +Delta Chat by default uses strict +TLS encryption +which secures connections between your device and your email provider. +All of Delta Chat’s TLS-handling has been independently security audited. +Moreover, the connection between your and the recipient’s email provider +will typically be transport-encrypted as well. +If the involved email servers support MTA-STS +then transport encryption will be enforced between email providers +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.
+ +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.
+ +Servers can therefore only see:
+ +By default, the addresses are randomly generated.
+ +All other message, contact and group metadata resides in the end-to-end encrypted part of messages.
+ +Both for protecting against metadata-collecting servers +as well as against the threat of device seizure +we recommend to use a chatmail relay +to create chat profiles using random 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.
+ +No, not yet.
+ +The Signal messenger introduced “Sealed Sender” in 2018 +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.
+ +Even if chatmail relays +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 addresses for sealed sending +but an implementation has not been agreed as a priority yet.
+ +No, not yet.
+ +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.
+ +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 chatmail core, +which would make it available in all chatmail clients.
+ +No, not yet.
+ +Delta Chat uses the Rust OpenPGP library rPGP +which supports the latest IETF Post-Quantum-Cryptography OpenPGP draft. +We aim to add PQC support in chatmail core after the draft is finalized at the IETF +in collaboration with other OpenPGP implementers.
+ +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.
+ +No.
+ +Delta Chat generates secure OpenPGP keys according to the Autocrypt specification 1.1. +We do not recommend or offer users to perform manual key management. +We want to ensure that security audits can focus on a few proven cryptographic algorithms +instead of the full breadth of possible algorithms allowed with OpenPGP. +If you want to extract your OpenPGP key, there only is an expert method: +you need to look it up in the “keypairs” SQLite table of a profile backup tar-file.
+ +Yes, multiple times. +The Delta Chat project continuously undergoes independent security audits and analysis, +from most recent to older:
+ +2024 December, an NLNET-commissioned Evaluation of +rPGP by Radically Open Security took place. +rPGP serves as the end-to-end encryption OpenPGP engine of Delta Chat. +Two advisories were released related to the findings of this audit:
+ +The issues outlined in these advisories have been fixed and are part of Delta Chat +releases on all appstores since December 2024.
+2024 March, we received a deep security analysis from the Applied Cryptography +research group at ETH Zuerich and addressed all raised issues. +See our blog post about Hardening Guaranteed End-to-End encryption for more detailed information and the +Cryptographic Analysis of Delta Chat +research paper published afterwards.
+2023 April, we fixed security and privacy issues with the “web +apps shared in a chat” feature, related to failures of sandboxing +especially with Chromium. We subsequently got an independent security +audit from Cure53 and all issues found were fixed in the 1.36 app series released in April 2023. +See here for the full background story on end-to-end security in the web.
+2023 March, Cure53 analyzed both the transport encryption of +Delta Chat’s network connections and a reproducible mail server setup as +recommended on this site. +You can read more about the audit on our blog +or read the full report here.
+2020, Include Security analyzed Delta +Chat’s Rust core, +IMAP, +SMTP, and +TLS libraries. +It did not find any critical or high-severity issues. +The report raised a few medium-severity weaknesses - +they are no threat to Delta Chat users on their own +because they depend on the environment in which Delta Chat is used. +For usability and compatibility reasons, +we can not mitigate all of them +and decided to provide security recommendations to threatened users. +You can read the full report here.
+2019, Include Security analyzed Delta +Chat’s PGP and +RSA libraries. +It found no critical issues, +but two high-severity issues that we subsequently fixed. +It also revealed one medium-severity and some less severe issues, +but there was no way to exploit these vulnerabilities in the Delta Chat implementation. +Some of them we nevertheless fixed since the audit was concluded. +You can read the full report here.
+Some features require certain permissions, +e.g. you need to grant camera permission if you want to scan an invite QR code.
+ +See Privacy Policy for a detailed overview.
+ +Delta Chat is available for all major and some minor platforms:
+ +The official website, https://delta.chat/download shows all options in detail
+If unavailable, use the mirror at https://deltachat.github.io/deltachat-pages
+Open one of the following app stores and search for “Delta Chat”: +Google Play Store, F-Droid, Huawei App Gallery, iOS and macOS App Store, Microsoft Store
+Check the package manager of your Linux distributions
+Android APKs are also available on https://github.com/deltachat/deltachat-android/releases
+Delta Chat does not receive any Venture Capital and +is not indebted, and under no pressure to produce huge profits, or to +sell users and their friends and family to advertisers (or worse). +We rather use public funding sources, so far from EU and US origins, to help +our efforts in instigating a decentralized and diverse chat messaging eco-system +based on Free and Open-Source community developments.
+ +Concretely, Delta Chat developments have so far been funded from these sources, +ordered chronologically:
+ +The NEXTLEAP EU project funded the research +and implementation of verified groups and setup contact protocols +in 2017 and 2018 and also helped to integrate end-to-end Encryption +through Autocrypt.
+The Open Technology Fund gave us a +first 2018/2019 grant (~$200K) during which we majorly improved the Android app +and released a first Desktop app beta version, and which moreover +moored our feature developments in UX research in human rights contexts, +see our concluding Needfinding and UX report. +The second 2019/2020 grant (~$300K) helped us to +release Delta/iOS versions, to convert our core library to Rust, and +to provide new features for all platforms.
+The NLnet foundation granted in 2019/2020 EUR 46K for +completing Rust/Python bindings and instigating a Chat-bot eco-system.
+In 2021 we received further EU funding for two Next-Generation-Internet +proposals, namely for EPPD - email provider portability directory (~97K EUR) and AEAP - email address porting (~90K EUR) which resulted in better multi-profile support, improved QR-code contact and group setups and many networking improvements on all platforms.
+From End 2021 till March 2023 we received Internet Freedom funding (500K USD) from the +U.S. Bureau of Democracy, Human Rights and Labor (DRL). +This funding supported our long-running goals to make Delta Chat more usable +and compatible with a wide range of email servers world-wide, and more resilient and secure +in places often affected by internet censorship and shutdowns.
+2023-2024 we successfully completed the OTF-funded +Secure Chatmail project, +allowing us to introduce guaranteed encryption, +creating a chatmail server network +and providing “instant onboarding” in all apps released from April 2024 on.
+In 2023 and 2024 we got accepted in the Next Generation Internet (NGI) +program for our work in webxdc PUSH, +along with collaboration partners working on +webxdc evolve, +webxdc XMPP, +DeltaTouch and +DeltaTauri. +All of these projects are partially completed or to be completed in early 2025.
+Sometimes we receive one-time donations from private individuals. +For example, in 2021 a generous individual bank-wired us 4K EUR +with the subject “keep up the good developments!”. 💜 +We use such money to fund development gatherings or to care for ad-hoc expenses +that can not easily be predicted for, or reimbursed from, public funding grants. +Receiving more donations also helps us to become more independent and long-term viable +as a contributor community.
+ + +Last but by far not least, several pro-bono experts and enthusiasts contributed +and contribute to Delta Chat developments without receiving money, or only +small amounts. Without them, Delta Chat would not be where it is today, not +even close.
+The monetary funding mentioned above is mostly organized by merlinux GmbH in +Freiburg (Germany), and is distributed to more than a dozen contributors world-wide.
+ +Please see Delta Chat Contribution channels +for both monetary and other contribution possibilities.
+ + + + + \ No newline at end of file diff --git a/src/main/assets/help/es/help.html b/src/main/assets/help/es/help.html new file mode 100644 index 0000000000000000000000000000000000000000..974cca980fc3e0059a7957a522382df8b606e8ac --- /dev/null +++ b/src/main/assets/help/es/help.html @@ -0,0 +1,1657 @@ + +Delta Chat is a reliable, decentralized and secure instant messaging app, +available for mobile and desktop platforms.
+ +Instant creation of private chat profiles +with secure and interoperable chatmail relays +that offer instant message delivery, and Push Notifications for iOS and Android devices.
+Pervasive multi-profile and +multi-device support on all platforms +and between different chatmail apps.
+Interactive in-chat apps for gaming and collaboration
+Audited end-to-end encryption +safe against network and server attacks.
+Free and Open Source software, both app and server side, +built on Internet Standards.
+First, note that Delta Chat is a private messenger. +There is no public discovery, you decide about your contacts.
+ +If you are face to face with your friend or family,
+tap the QR Code icon
+on the main screen.
+Ask your chat partner to scan the QR image
+with their Delta Chat app.
For a remote contact setup, +from the same screen, +click “Copy” or “Share” and send the invite link +through another private chat.
+Now wait while connection gets established.
+ +If both sides are online, they will soon see a chat +and can start messaging securely.
+If one side is offline or in bad network, +the ability to chat is delayed until connectivity is restored.
+Congratulations! +You now will automatically use end-to-end encryption with this contact. +If you add each other to groups, end-to-end encryption will be established among all members.
+ +As being a private messenger, +only friends and family you share your QR code or invite link with can write to you.
+ +Your friends may share your contact with other friends, this appears as a request.
+ +Necesitas aceptar la solicitud antes de poder responder.
+También puedes eliminarlo si no quieres chatear con ellos por ahora.
+Si eliminas una solicitud, los mensajes futuros de ese contacto seguirán apareciendo como solicitud de mensaje, por lo que puedes cambiar de opinión. Si realmente no quieres recibir mensajes de esta persona, considera bloquearlos.
+Attach the first contact to the chat of the second using
Attachment Button → Contact.
+You can also add a little introduction message.
The second contact will receive a card then +and can tap it to start chatting with the first contact.
+ +Yes. Images, videos, files, voice messages etc. can be sent using the
Attachment-
+or
Voice Message buttons
Para mejorar el rendimiento, las imágenes se optimizan y se envían en un tamaño más pequeño de forma predeterminada, pero puedes enviarla como un “archivo” para conservar la original.
+A profile is a name, a picture and some additional information for encrypting messages. +A profile lives on your device(s) only +and uses the server only to relay messages.
+ +En la primera instalación de Delta Chat se crea un primer perfil.
+ +Después, puedes tocar la imagen de tu perfil en la esquina superior izquierda para Añadir perfiles +o para Cambiar perfiles.
+ +You may want to use separate profiles for political, family or work related activities.
+ +Quizás quieres aprender cómo se usa el mismo perfil en múltiples dispositivos.
+ +Puede agregar una foto de perfil en su configuración. Si escribe a sus contactos +o los agrega a través de un código QR, ellos lo verán automáticamente como su foto de perfil.
+Por cuestiones de privacidad, nadie verá su foto de perfil hasta que les escriba un mensaje.
+Yes, +you can do so under Settings → Profile → Bio. +Once you sent a message to a contact, +they will see it when they view your contact details.
+ +Usa estas herramientas para organizar tus chats y mantener todo en su lugar:
+ +Chats fijados siempre se mantienen al frente de tu listado. Puedes usarlos para acceder a tus chats preferidos de forma rápida o temporal para no olvidarte de tus cosas.
+Chats muteados si no quieres recibir notificaciones de ellos. Chats muteados se mantienen en su lugar e inclusive puedes fijarlos.
+Archivar chats si no deseas verlos en tu lista de chats. +Los chats archivados siguen siendo accesibles arriba de la lista de chats o a través de la búsqueda.
+Cuando un chat archivado recibe un nuevo mensaje, a menos que esté silenciado, saldrá del archivo y volverá a aparecer en tu lista de chats. +Los chats silenciados permanecen archivados hasta que los desarchivas manualmente.
+Para archivar o fijar un chat, toque prolongadamente (Android), use el menú del chat (Android/Escritorio) o deslícese hacia la izquierda (iOS); +para silenciar un chat, use el menú del chat (Android/Escritorio) o el perfil del chat (iOS).
+ +Mensajes guardados es un chat que puedes utilizar para recordar y encontrar mensajes fácilmente.
+ +En cualquier chat, mantén pulsado o haz clic con el botón derecho en un mensaje y selecciona Guardar
+Los mensajes guardados se marcan con el símbolo
+
+junto a la marca de tiempo
Después puedes abrir el chat “Mensajes guardados” - y allí verás los mensajes guardados.
+Con pulsar a
,
+puedes volver al mensaje original en el chat original
Finalmente, también se puede utilizar “Mensajes guardados” para tomar notas personales - abre el chat, escribe algo, añade una foto o un mensaje de voz, etc.
+Como los “mensajes guardados” se sincronizan, pueden ser muy útiles para transferir datos entre dispositivos.
+Los mensajes se quedan guardados, también si se han cambiado o están borrados - +Sea por el remitente, por la limpieza del dispositivo o por la desaparición de mensajes de otros chats.
+ +You can sometimes see a green dot
+next to the avatar of a contact.
+It means they were recently seen by you in the last 10 minutes,
+e.g. because they messaged you or sent a read receipt.
So this is not a real time online status +and others will as well not always see that you are “online”.
+ +One tick
+means that the message was sent successfully to your provider.
Two ticks
+mean that at least one recipient’s device
+reported back to having received the message.
Recipients may have disabled read-receipts, +so even if you see only one tick, the message may have been read.
+The other way round, two ticks do not automatically mean +that a human has read or understood the message ;)
+Se puede editar el texto de los mensajes después de enviarlos.
+Para ello, mantenga pulsado o haz clic con el botón derecho en el mensaje y seleccione Editar
+o
.
Si has enviado un mensaje accidentalmente +desde el mismo menú, seleccione Borrar y después Borrar para todos.
+Mientras que los mensajes editados tendrán la palabra “Editado” junto a la marca de tiempo, +los mensajes borrados serán eliminados sin un marcador en el chat. +No se envían notificaciones y no hay límite de tiempo.
+ +Note, that the original message may still be received by chat members +who could have already replied, forwarded, saved, screenshotted or otherwise copied the message.
+ +You can turn on “disappearing messages” +in the settings of a chat, +at the top right of the chat window, +by selecting a time span +between 5 minutes and 1 year.
+ +Until the setting is turned off again, +each chat member’s Delta Chat app takes care +of deleting the messages +after the selected time span. +The time span begins +when the receiver first sees the message in Delta Chat. +The messages are deleted both, +on the servers, +and in the apps itself.
+ +Tenga en cuenta que puede confiar en los mensajes que desaparecen +sólo mientras confíes en tus compañeros de chat; +compañeros de chat maliciosos pueden tomar fotos, +o guardar, copiar o reenviar mensajes antes de eliminarlos.
+ +Apart from that, +if one chat partner uninstalls Delta Chat, +the (anyway encrypted) messages may take longer to get deleted from their server.
+ +If you are using more than one chat profile, +you can remove single ones in the top profile switcher menu (on Android and iOS), +or in the sidebar with a right click (in the Desktop app). +Chat profiles are only removed on the device where deletion was triggered. +Chat profiles on other devices will continue to fully function.
+ +If you use a single default chat profile you can simply uninstall the app. +This will still automatically trigger deletion of all associated address data on the chatmail server. +For more info, please refer to nine.testrun.org address-deletion +or the respective page from your chosen 3rd party chatmail server.
+ +Groups let several people chat together privately with equal rights.
+ +Anyone can +change the group name or avatar, +add or remove members, +set disappearing messages, +and delete their own messages from all member’s devices.
+ +Because all members have the same rights, groups work best among trusted friends and family.
+ +All group members have the same rights. +For this reason, everyone can delete any member or add new ones.
+To add or delete members, tap the group name in the chat and select the member to add or remove.
+If the member is not yet in your contact list, but face to face with you,
+from the same screen, show a QR code.
+Ask your chat partner to scan the QR image with their Delta Chat app by tapping
+
on the main screen.
For a remote member addition, +click “Copy” or “Share” and send the invite link +through another private chat to the new member.
+QR code and invite link can be used to add several members. +However, since groups are meant for trusted people, avoid sharing them publicly.
+ +Elimínate de la lista de miembros o elimina todo el chat. +Si desea unirse al grupo nuevamente más tarde, pídale a otro miembro del grupo que lo agregue nuevamente.
+Como alternativa, también puede “silenciar” a un grupo, lo que significa que recibirá todos los mensajes y +aún puede escribir, pero ya no se le notifican nuevos mensajes.
+You can duplicate a group to start a separate discussion +or to exclude members without them noticing.
+ +Open the group profile and tap Clone Chat (Android/iOS), +or right-click the group in the chat list (Desktop).
+Set a new name, choose an avatar, and adjust the member list if needed.
+The new group is fully independent from the original, +which continues to work as before.
+ +You can send apps to a chat - games, editors, polls and other tools. +This makes Delta Chat a truly extensible messenger.
+ +In a chat, using
Attachment Button → Apps
You can also create your own app and attach it using
Attachment Button → File
In-chat apps can not send data to the Internet, or download anything.
+An in-chat app can only exchange data within a chat, with its +copies on the devices of your chat partners. Other than that, it’s completely +isolated from the Internet.
+The privacy an in-chat app offers is the privacy of your chat - as long as you +trust the people you chat with, you can trust the in-chat app as well.
+This also means: Just like for web links, do not open apps from untrusted contacts.
+In-chat apps are zip files with .xdc extension containing html, css, and javascript code.
You can extend the Hello World example app +to get started.
+All else you need to know is written in the +Webxdc documentation.
+If you have question, you can ask others with experience +in the Delta Chat Forum.
+Push Notifications are sent by Apple and Google “Push services” to a user’s device +so that an inactive Delta Chat app can fetch messages in the background +and show notifications on a user’s phone if needed.
+ +Las notificaciones push funcionan con todos los servidores de chatmail en
+ +dispositivos iOS, por la integración de los servicios Push de Apple.
+Android devices, by integrating with the Google FCM Push service, +including on devices that use microG +instead of proprietary Google code on the phone.
+Yes, Delta Chat automatically uses Push Notifications for chatmail profiles. +And no, there is no alternative on Apple’s phones to achieve instant message delivery +because Apple devices do not allow Delta Chat to fetch data in the background. +Push notifications are automatically activated for iOS users because +Delta Chat’s privacy-preserving Push Notification system +does not expose data to Apple that it doesn’t already have.
+ +If a “Push Service” is available, Delta Chat enables Push Notifications +to achieve instant message delivery for all chatmail users.
+ +In the Delta Chat “Notifications” settings for “Instant delivery” +you can change the following settings effecting all chat profiles:
+ +Use Background Connection: If you are not using a Push service, +you may disable “battery optimizations” for Delta Chat, +allowing it to fetch messages in the background. +However, there could be delays from minutes to hours. +Some Android vendors even restrict apps completely +(see dontkillmyapp.com) +and Delta Chat might not show incoming messages +until you manually open the app again.
+Force Background Connection: This is the fallback option +if the previous options are not available or do not achieve “instant delivery”. +Enabling it causes a permanent notification on your phone +which may sometimes be “minified” with recent Android phones.
+Both “Background Connection” options are energy-efficient and +safe to try if you experience messages arrive only with long delays.
+ +Delta Chat Push Notification support avoids leakage of private information. +It does not leak profile data, IP address or message content (not even encrypted) +to any system involved in the delivery of Push Notifications.
+ +Así es como las aplicaciones Delta Chat realizan la entrega de Notificaciones Push:
+ +A Delta Chat app obtains a “device token” locally, encrypts it and stores it +on the chatmail server.
+When a chatmail server receives a message for a Delta Chat user +it forwards the encrypted device token to the central Delta Chat notification proxy.
+The central Delta Chat notification proxy decrypts the device token +and forwards it to the respective Push service (Apple, Google, etc.), +without ever knowing the IP or profile data of Delta Chat users.
+The central Push Service (Apple, Google, etc.) +wakes up the Delta Chat app on your device +to check for new messages in the background. +It does not know about the profile data of the device it wakes up. +The central Apple/Google Push services never see any profile data (sender or receiver) +and also never see any message content (also not in encrypted forms).
+The central Delta Chat notification proxy is small and fully implemented in Rust +and forgets about device-tokens as soon as Apple/Google/etc processed them, +usually in a matter of milliseconds.
+ +Note that the device token is encrypted between apps and notification proxy +but it is not signed. +The notification proxy thus never sees profile data, IP-addresses or +any cryptographic identity information associated with a user’s device (token).
+ +Resulting from this overall privacy design, even the seizure of a chatmail server, +or the full seizure of the central Delta Chat notification proxy +would not reveal private information that Push services do not already have.
+ +Delta Chat is a free and open source decentralized messenger with free server choice, +but we want users to reliably experience “instant delivery” of messages, +like they experience from WhatsApp, Signal or Telegram apps, +without asking questions up-front that are more suited to expert users or developers.
+ +Note that Delta Chat has a small and privacy-preserving Push Notification system +that achieves “instant delivery” of messages for all chatmail servers +including a potential one you might setup yourself without our permission. +Welcome to the power of the interoperable chatmail relay network :)
+ +Yes. You can use the same profile on different devices:
+ +Asegurate que ambos dispositivos estén en la misma Wi-Fi o red
+On the first device, go to Settings → Add Second Device, unlock the screen if needed +and wait a moment until a QR code is shown
+En el otro dispositivo, instala Delta Chat
+On the second device, start Delta Chat, select Add as Second Device, and scan the QR code from the old device
+La transferencia debería comenzar después de unos segundos y durante la transferencia ambos dispositivos mostrarán el progreso. +Espere hasta que termine en ambos dispositivos.
+A diferencia de muchas otras aplicaciones de mensajería, después de una transferencia exitosa, +ambos dispositivos son completamente independientes. +No es necesario un dispositivo para que el otro funcione.
+ +Vuelve a verificar que ambos dispositivos estén en la misma Wi-Fi o red
+On Windows, go to Control Panel / Network and Internet +and make sure, Private Network is selected as “Network profile type” +(after transfer, you can change back to the original value)
+On iOS, make sure “System Settings / Apps / Delta Chat / Local Network” access is granted
+On macOS, enable “System Settings / Privacy & Security / Local Network / Delta Chat”
+Your system might have a “personal firewall”, +which is known to cause problems (especially on Windows). +Disable the personal firewall for Delta Chat on both ends and try again
+Guest Networks may not allow devices to communicate with each other. +If possible, use a non-guest network.
+If you still have troubles using the same network, +try to open Mobile Hotspot on one device and join that Wi-Fi from the other one
+Asegurate que haya suficiente espacio en el dispositivo destino
+If transfer started, make sure, the devices stay active and do not fall asleep. +Do not exit Delta Chat. +(we try hard to make the app work in background, but systems tend to kill apps, unfortunately)
+Delta Chat is already logged in on the destination device? +You can use multiple profiles per device, just add another profile
+If you still have problems or if you cannot scan a QR code +try the manual transfer described below
+This method is only recommended if “Add Second Device” as described above does not work.
+ +At Settings → Advanced → Experimental Features +you can try out features we are working on.
+ +The features may be unstable and may be changed or removed.
+ +You can find more information +and give feedback in the Forum.
+ +We would like to improve Delta Chat with your help, +which is why Delta Chat for Android asks whether you want +to send anonymous usage statistics.
+ +You can turn it on and off at +Settings → Advanced → Send statistics to Delta Chat’s developers.
+ +When you turn it on, +weekly statistics will be automatically sent to a bot.
+ +We are interested e.g. in statistics like:
+ +We will not collect any personally identifiable information about you.
+ +Yes, but only if the email address is used exclusively by chatmail clients.
+ +It is not supported to share usage of an email address with non-chatmail apps or web-based mailers, +for the following reasons:
+ +Non-chatmail apps are largely not accomplishing automatic end-to-end email encryption for their users, +while chatmail apps and relays pervasively enforce end-to-end encryption and security standards.
+Non-chatmail apps use email servers as a long-term message archive +while chatmail clients use email servers for ephemeral instant message relay.
+Supporting the full variety of classic email setups +would require considerable development and maintenance efforts, +and complicate making chatmail-based messaging more resilient, reliable and fast.
+First off, please do not use the same classic email address also from non-chatmail classic email apps +unless you are prepared to deal with encrypted messages in the inbox, +double notifications, accidentally deleted emails or similar annoyances.
+ +You can configure a email address for chatting at New Profile → Use Other Server → Use Classic Mail as Relay.
+Note that classic email providers will generally not support Push Notifications
+and have other limitations, see Provider Overview.
+Chatmail uses the default INBOX for relay; ensure the provider setup does too.
+A chat profile using a classic email address allows to to send and receive unencrypted messages.
+These messages, and the chats they appear in, are marked with an email icon
+
.
Any well behaving email server setup will do fine +except if your users’ devices require Google/Apple Push Notifications to work properly.
+ +We generally recommend to set up a chatmail relay. +Chatmail is a community-driven project that encompasses both the setup of relays +and core Rust developments +that power chatmail clients of which Delta Chat is the most well known.
+ +Delta Chat uses a secure subset of the OpenPGP standard +to provide automatic end-to-end encryption using these protocols:
+ +Secure-Join +to exchange encryption setup information through QR-code scanning or “invite links”.
+Autocrypt is used for automatically +establishing end-to-end encryption between contacts and all members of a group chat.
+Sharing a contact to a +chat +enables receivers to use end-to-end encryption with the contact.
+Delta Chat does not query, publish or interact with any OpenPGP key servers.
+ +All messages in Delta Chat are end-to-end encrypted by default. +Since the Delta Chat Version 2 release series (July 2025) +there are no lock or similar markers on end-to-end encrypted messages, anymore.
+ +If you use default chatmail relays, +it is impossible to receive or send messages without end-to-end encryption.
+ +If you instead use a classic email server,
+you can send and receive messages with or without end-to-end encryption.
+Messages lacking end-to-end encryption are marked with an email icon
+
.
A contact profile might show a green checkmark
+
+and an “Introduced by” line.
+Every green-checkmarked contact either did a direct QR-scan with you
+or was introduced by a another green-checkmarked contact.
+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 QR-scan.
Para obtener una discusión más detallada sobre “cifrado de extremo a extremo garantizado”, por favor consulta los protocolos Secure-Join 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”.
+ +Yes.
+ +Cuando hablamos de un mensaje “cifrado de extremo a extremo”, +siempre nos referimos a que todo el mensaje está cifrado, +incluyendo todos los archivos adjuntos +y los metadatos de los archivos adjuntos, como los nombres de archivo.
+ +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.
+ +OpenPGP is not insecure by itself. +Most publicly discussed OpenPGP security problems +actually stem from bad usability or bad implementations of tools or apps (or both). +It is particularly important to distinguish between OpenPGP, the IETF encryption standard, +and GnuPG (GPG), a command line tool implementing OpenPGP. +Many public critiques of OpenPGP actually discuss GnuPG which Delta Chat has never used. +Delta Chat rather uses the OpenPGP Rust implementation rPGP, +available as an independent “pgp” package, +and security-audited in 2019 and 2024.
+ +We aim, along with other OpenPGP implementors, +to further improve security characteristics by implementing the +new IETF OpenPGP Crypto-Refresh +which was thankfully adopted in summer 2023.
+ +Yes, we are following efforts like MLS +but adopting them would mean breaking end-to-end encryption interoperability. +So it would not be a light decision to take +and there must be tangible improvements for users.
+ +Delta Chat takes a holistic “usable security” approach +and works with a wide range of activist groupings as well as +renowned researchers such as TeamUSEC +to improve actual user outcomes against security threats. +The wire protocol and standard for establishing end-to-end encryption is +only one part of “user outcomes”, +see also our answers to device-seizure +and message-metadata questions.
+ +No, Delta Chat never was vulnerable to EFAIL +because its OpenPGP implementation rPGP +uses Modification Detection Code when encrypting messages +and returns an error +if the Modification Detection Code is incorrect.
+ +Delta Chat also never was vulnerable to the “Direct Exfiltration” EFAIL attack
+because it only decrypts multipart/encrypted messages
+which contain exactly one encrypted and signed part,
+as defined by the Autocrypt Level 1 specification.
If you are sending or receiving email messages without end-to-end encryption (using a classic email server), +they are still protected from cell or cable companies who can not read or modify your email messages. +But both your and your recipient’s email providers +may read, analyze or modify your messages, including any attachments.
+ +Delta Chat by default uses strict +TLS encryption +which secures connections between your device and your email provider. +All of Delta Chat’s TLS-handling has been independently security audited. +Moreover, the connection between your and the recipient’s email provider +will typically be transport-encrypted as well. +If the involved email servers support MTA-STS +then transport encryption will be enforced between email providers +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.
+ +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.
+ +Servers can therefore only see:
+ +By default, the addresses are randomly generated.
+ +All other message, contact and group metadata resides in the end-to-end encrypted part of messages.
+ +Both for protecting against metadata-collecting servers +as well as against the threat of device seizure +we recommend to use a chatmail relay +to create chat profiles using random 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.
+ +No, not yet.
+ +The Signal messenger introduced “Sealed Sender” in 2018 +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.
+ +Even if chatmail relays +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 addresses for sealed sending +but an implementation has not been agreed as a priority yet.
+ +No, not yet.
+ +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.
+ +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 chatmail core, +which would make it available in all chatmail clients.
+ +No, not yet.
+ +Delta Chat uses the Rust OpenPGP library rPGP +which supports the latest IETF Post-Quantum-Cryptography OpenPGP draft. +We aim to add PQC support in chatmail core after the draft is finalized at the IETF +in collaboration with other OpenPGP implementers.
+ +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.
+ +No.
+ +Delta Chat generates secure OpenPGP keys according to the Autocrypt specification 1.1. +We do not recommend or offer users to perform manual key management. +We want to ensure that security audits can focus on a few proven cryptographic algorithms +instead of the full breadth of possible algorithms allowed with OpenPGP. +If you want to extract your OpenPGP key, there only is an expert method: +you need to look it up in the “keypairs” SQLite table of a profile backup tar-file.
+ +Yes, multiple times. +The Delta Chat project continuously undergoes independent security audits and analysis, +from most recent to older:
+ +2024 December, an NLNET-commissioned Evaluation of +rPGP by Radically Open Security took place. +rPGP serves as the end-to-end encryption OpenPGP engine of Delta Chat. +Two advisories were released related to the findings of this audit:
+ +The issues outlined in these advisories have been fixed and are part of Delta Chat +releases on all appstores since December 2024.
+2024 March, we received a deep security analysis from the Applied Cryptography +research group at ETH Zuerich and addressed all raised issues. +See our blog post about Hardening Guaranteed End-to-End encryption for more detailed information and the +Cryptographic Analysis of Delta Chat +research paper published afterwards.
+2023 April, we fixed security and privacy issues with the “web +apps shared in a chat” feature, related to failures of sandboxing +especially with Chromium. We subsequently got an independent security +audit from Cure53 and all issues found were fixed in the 1.36 app series released in April 2023. +See here for the full background story on end-to-end security in the web.
+2023 March, Cure53 analyzed both the transport encryption of +Delta Chat’s network connections and a reproducible mail server setup as +recommended on this site. +You can read more about the audit on our blog +or read the full report here.
+2020, Include Security analyzed Delta +Chat’s Rust core, +IMAP, +SMTP, and +TLS libraries. +It did not find any critical or high-severity issues. +The report raised a few medium-severity weaknesses - +they are no threat to Delta Chat users on their own +because they depend on the environment in which Delta Chat is used. +For usability and compatibility reasons, +we can not mitigate all of them +and decided to provide security recommendations to threatened users. +You can read the full report here.
+2019, Include Security analyzed Delta +Chat’s PGP and +RSA libraries. +It found no critical issues, +but two high-severity issues that we subsequently fixed. +It also revealed one medium-severity and some less severe issues, +but there was no way to exploit these vulnerabilities in the Delta Chat implementation. +Some of them we nevertheless fixed since the audit was concluded. +You can read the full report here.
+Some features require certain permissions, +e.g. you need to grant camera permission if you want to scan an invite QR code.
+ +See Privacy Policy for a detailed overview.
+ +Delta Chat is available for all major and some minor platforms:
+ +The official website, https://delta.chat/download shows all options in detail
+If unavailable, use the mirror at https://deltachat.github.io/deltachat-pages
+Open one of the following app stores and search for “Delta Chat”: +Google Play Store, F-Droid, Huawei App Gallery, iOS and macOS App Store, Microsoft Store
+Check the package manager of your Linux distributions
+Android APKs are also available on https://github.com/deltachat/deltachat-android/releases
+Delta Chat does not receive any Venture Capital and +is not indebted, and under no pressure to produce huge profits, or to +sell users and their friends and family to advertisers (or worse). +We rather use public funding sources, so far from EU and US origins, to help +our efforts in instigating a decentralized and diverse chat messaging eco-system +based on Free and Open-Source community developments.
+ +Concretely, Delta Chat developments have so far been funded from these sources, +ordered chronologically:
+ +El proyecto de la UE NEXTLEAP financió la investigación +e implementación de grupos verificados y protocolos de contacto +en 2017 y 2018 y también ayudó a integrar el cifrado de extremo a extremo +a través de Autocrypt.
+The Open Technology Fund gave us a +first 2018/2019 grant (~$200K) during which we majorly improved the Android app +and released a first Desktop app beta version, and which moreover +moored our feature developments in UX research in human rights contexts, +see our concluding Needfinding and UX report. +The second 2019/2020 grant (~$300K) helped us to +release Delta/iOS versions, to convert our core library to Rust, and +to provide new features for all platforms.
+The NLnet foundation granted in 2019/2020 EUR 46K for +completing Rust/Python bindings and instigating a Chat-bot eco-system.
+In 2021 we received further EU funding for two Next-Generation-Internet +proposals, namely for EPPD - email provider portability directory (~97K EUR) and AEAP - email address porting (~90K EUR) which resulted in better multi-profile support, improved QR-code contact and group setups and many networking improvements on all platforms.
+From End 2021 till March 2023 we received Internet Freedom funding (500K USD) from the +U.S. Bureau of Democracy, Human Rights and Labor (DRL). +This funding supported our long-running goals to make Delta Chat more usable +and compatible with a wide range of email servers world-wide, and more resilient and secure +in places often affected by internet censorship and shutdowns.
+2023-2024 we successfully completed the OTF-funded +Secure Chatmail project, +allowing us to introduce guaranteed encryption, +creating a chatmail server network +and providing “instant onboarding” in all apps released from April 2024 on.
+In 2023 and 2024 we got accepted in the Next Generation Internet (NGI) +program for our work in webxdc PUSH, +along with collaboration partners working on +webxdc evolve, +webxdc XMPP, +DeltaTouch and +DeltaTauri. +All of these projects are partially completed or to be completed in early 2025.
+Sometimes we receive one-time donations from private individuals. +For example, in 2021 a generous individual bank-wired us 4K EUR +with the subject “keep up the good developments!”. 💜 +We use such money to fund development gatherings or to care for ad-hoc expenses +that can not easily be predicted for, or reimbursed from, public funding grants. +Receiving more donations also helps us to become more independent and long-term viable +as a contributor community.
+ + +Por último, pero no por ello menos importante, varios expertos pro-bono y entusiastas contribuyeron +y contribuyen a los desarrollos de Delta Chat sin recibir dinero, o sólo +pequeñas cantidades. Sin ellos, Delta Chat no estaría donde está hoy, ni +siquiera cerca.
+La financiación monetaria mencionada anteriormente es principalmente organizada por merlinux GmbH en Freiburg (Alemania), y se distribuye a más de una docena de colaboradores en todo el mundo.
+ +Por favor, consulta Canales de contribución de Delta Chat para conocer las posibilidades de contribución tanto monetarias como otras.
+ + + + + \ No newline at end of file diff --git a/src/main/assets/help/fr/help.html b/src/main/assets/help/fr/help.html new file mode 100644 index 0000000000000000000000000000000000000000..bca19599ab1a0afce57b044a58a11ee003ec4e31 --- /dev/null +++ b/src/main/assets/help/fr/help.html @@ -0,0 +1,1619 @@ + +Delta Chat is a reliable, decentralized and secure instant messaging app, +available for mobile and desktop platforms.
+ +Instant creation of private chat profiles +with secure and interoperable chatmail relays +that offer instant message delivery, and Push Notifications for iOS and Android devices.
+Pervasive multi-profile and +multi-device support on all platforms +and between different chatmail apps.
+Interactive in-chat apps for gaming and collaboration
+Audited end-to-end encryption +safe against network and server attacks.
+Free and Open Source software, both app and server side, +built on Internet Standards.
+First, note that Delta Chat is a private messenger. +There is no public discovery, you decide about your contacts.
+ +If you are face to face with your friend or family,
+tap the QR Code icon
+on the main screen.
+Ask your chat partner to scan the QR image
+with their Delta Chat app.
For a remote contact setup, +from the same screen, +click “Copy” or “Share” and send the invite link +through another private chat.
+Now wait while connection gets established.
+ +If both sides are online, they will soon see a chat +and can start messaging securely.
+If one side is offline or in bad network, +the ability to chat is delayed until connectivity is restored.
+Congratulations! +You now will automatically use end-to-end encryption with this contact. +If you add each other to groups, end-to-end encryption will be established among all members.
+ +As being a private messenger, +only friends and family you share your QR code or invite link with can write to you.
+ +Your friends may share your contact with other friends, this appears as a request.
+ +Vous devez d’abord accepter pour pouvoir répondre au message.
+Vous pouvez également choisir de supprimer l’invitation si vous ne souhaitez pas discuter avec cet inconnu maintenant.
+Si vous supprimez une invitation, les futurs messages de ce contact apparaîtront +de nouveau comme des invitations, de sorte que vous pouvez changer d’avis par la suite. Si vous ne voulez vraiment pas +recevoir de messages de cette personne, nous vous conseillons de la bloquer.
+Attach the first contact to the chat of the second using
Attachment Button → Contact.
+You can also add a little introduction message.
The second contact will receive a card then +and can tap it to start chatting with the first contact.
+ +Oui. Images, videos, files, voice messages etc. can be sent using the
Attachment-
+or
Voice Message buttons
Pour améliorer les performances, les images sont redimensionnées et envoyées en taille réduite par défaut ; mais vous pouvez les envoyer en tant que “fichier” pour en conserver la taille originale.
+A profile is a name, a picture and some additional information for encrypting messages. +A profile lives on your device(s) only +and uses the server only to relay messages.
+ +On first installation of Delta Chat a first profile is created.
+ +Later, you can tap your profile image in the upper left corner to Add Profiles +or to Switch Profiles.
+ +You may want to use separate profiles for political, family or work related activities.
+ +You may also wish to learn how to use the same profile on multiple devices.
+ +Dans les paramètres vous pouvez ajouter une photo de profil. Si vous écrivez à vos contacts ou que vous les ajoutez via le QR code, ils la verront automatiquement comme votre photo de profil.
+ +Yes, +you can do so under Settings → Profile → Bio. +Once you sent a message to a contact, +they will see it when they view your contact details.
+ +Ces options vous permettent d’organiser et trier vos discussions :
+ +Les discussions épinglées restent en haut de votre liste de discussions. Vous pouvez ainsi retrouver plus rapidement vos discussions favorites ou éviter d’oublier des messages importants.
+Utilisez la sourdine pour les discussions dont vous ne voulez pas recevoir les notifications. Les discussions en sourdine figurent toujours dans votre liste et peuvent aussi être les épinglées.
+Archivez les discussions si vous ne voulez plus les voir apparaître dans votre liste de discussions. +Les discussions archivées restent accessibles au-dessus de la liste de discussions ou via la recherche.
+Lorsqu’un nouveau message est envoyé sur une discussion que vous avez archivée, et que vous n’avez pas mise en sourdine, la discussion sort des archives et reprend sa place dans votre liste de discussions. +Les discussions en sourdine restent archivées tant que vous ne les désarchivez pas manuellement.
+Pour archiver ou épingler une discussion, faites un appui long sur la discussion concernée (Android), ouvrez le menu de la conversation (Android/application de bureau), ou balayez vers la gauche (iOS) ; +pour mettre une discussion en sourdine, ouvrez le menu de la conversation (Android/application de bureau) ou le profil de la discussion (iOS).
+ +Saved Messages is a chat that you can use to easily remember and find messages.
+ +In any chat, long tap or right click a message and select Save
+Saved messages are marked by the symbol
+
+next to the timestamp
Later, open the “Saved Messages” chat - and you will see the saved messages there.
+By tapping
,
+you can go back to the original message in the original chat
Finally, you can also use “Save Messages” to take personal notes - open the chat, type something, add a photo or a voice message etc.
+As “Saved Message” are synced, they can become very handy for transferring data between devices
+Messages stay saved even if they are edited or deleted - +may it be by sender, by device cleanup or by disappearing messages of other chats.
+ +You can sometimes see a green dot
+next to the avatar of a contact.
+It means they were recently seen by you in the last 10 minutes,
+e.g. because they messaged you or sent a read receipt.
So this is not a real time online status +and others will as well not always see that you are “online”.
+ +One tick
+means that the message was sent successfully to your provider.
Two ticks
+mean that at least one recipient’s device
+reported back to having received the message.
Recipients may have disabled read-receipts, +so even if you see only one tick, the message may have been read.
+The other way round, two ticks do not automatically mean +that a human has read or understood the message ;)
+You can edit the text of your messages after sending.
+For that, long tap or right click the message and select Edit
+or
.
If you have sent a message accidentally, +from the same menu, select Delete and then Delete for Everyone.
+While edited messages will have the word “Edited” next to the timestamp, +deleted messages will be removed without a marker in the chat. +Notifications are not sent and there is no time limit.
+ +Note, that the original message may still be received by chat members +who could have already replied, forwarded, saved, screenshotted or otherwise copied the message.
+ +You can turn on “disappearing messages” +in the settings of a chat, +at the top right of the chat window, +by selecting a time span +between 5 minutes and 1 year.
+ +Until the setting is turned off again, +each chat member’s Delta Chat app takes care +of deleting the messages +after the selected time span. +The time span begins +when the receiver first sees the message in Delta Chat. +The messages are deleted both, +on the servers, +and in the apps itself.
+ +Note that you can rely on disappearing messages +only as long as you trust your chat partners; +malicious chat partners can take photos, +or otherwise save, copy or forward messages before deletion.
+ +Apart from that, +if one chat partner uninstalls Delta Chat, +the (anyway encrypted) messages may take longer to get deleted from their server.
+ +If you are using more than one chat profile, +you can remove single ones in the top profile switcher menu (on Android and iOS), +or in the sidebar with a right click (in the Desktop app). +Chat profiles are only removed on the device where deletion was triggered. +Chat profiles on other devices will continue to fully function.
+ +If you use a single default chat profile you can simply uninstall the app. +This will still automatically trigger deletion of all associated address data on the chatmail server. +For more info, please refer to nine.testrun.org address-deletion +or the respective page from your chosen 3rd party chatmail server.
+ +Groups let several people chat together privately with equal rights.
+ +Anyone can +change the group name or avatar, +add or remove members, +set disappearing messages, +and delete their own messages from all member’s devices.
+ +Because all members have the same rights, groups work best among trusted friends and family.
+ +All group members have the same rights. +For this reason, everyone can delete any member or add new ones.
+To add or delete members, tap the group name in the chat and select the member to add or remove.
+If the member is not yet in your contact list, but face to face with you,
+from the same screen, show a QR code.
+Ask your chat partner to scan the QR image with their Delta Chat app by tapping
+
on the main screen.
For a remote member addition, +click “Copy” or “Share” and send the invite link +through another private chat to the new member.
+QR code and invite link can be used to add several members. +However, since groups are meant for trusted people, avoid sharing them publicly.
+ +Supprimez-vous de la liste des membres ou supprimez la discussion entière. +Si souhaitez rejoindre le groupe plus tard, demandez à un autre membre du groupe de vous ré-inviter.
+Vous pouvez également mettre un groupe en “Sourdine” : vous recevrez tous les messages et pourrez toujours écrire, mais n’aurez plus les notifications des nouveaux messages.
+You can duplicate a group to start a separate discussion +or to exclude members without them noticing.
+ +Open the group profile and tap Clone Chat (Android/iOS), +or right-click the group in the chat list (Desktop).
+Set a new name, choose an avatar, and adjust the member list if needed.
+The new group is fully independent from the original, +which continues to work as before.
+ +You can send apps to a chat - games, editors, polls and other tools. +This makes Delta Chat a truly extensible messenger.
+ +In a chat, using
Attachment Button → Apps
You can also create your own app and attach it using
Attachment Button → File
In-chat apps can not send data to the Internet, or download anything.
+An in-chat app can only exchange data within a chat, with its +copies on the devices of your chat partners. Other than that, it’s completely +isolated from the Internet.
+The privacy an in-chat app offers is the privacy of your chat - as long as you +trust the people you chat with, you can trust the in-chat app as well.
+This also means: Just like for web links, do not open apps from untrusted contacts.
+In-chat apps are zip files with .xdc extension containing html, css, and javascript code.
You can extend the Hello World example app +to get started.
+All else you need to know is written in the +Webxdc documentation.
+If you have question, you can ask others with experience +in the Delta Chat Forum.
+Push Notifications are sent by Apple and Google “Push services” to a user’s device +so that an inactive Delta Chat app can fetch messages in the background +and show notifications on a user’s phone if needed.
+ +Push Notifications work with all chatmail servers on
+ +iOS devices, by integrating with Apple Push services.
+Android devices, by integrating with the Google FCM Push service, +including on devices that use microG +instead of proprietary Google code on the phone.
+Yes, Delta Chat automatically uses Push Notifications for chatmail profiles. +And no, there is no alternative on Apple’s phones to achieve instant message delivery +because Apple devices do not allow Delta Chat to fetch data in the background. +Push notifications are automatically activated for iOS users because +Delta Chat’s privacy-preserving Push Notification system +does not expose data to Apple that it doesn’t already have.
+ +If a “Push Service” is available, Delta Chat enables Push Notifications +to achieve instant message delivery for all chatmail users.
+ +In the Delta Chat “Notifications” settings for “Instant delivery” +you can change the following settings effecting all chat profiles:
+ +Use Background Connection: If you are not using a Push service, +you may disable “battery optimizations” for Delta Chat, +allowing it to fetch messages in the background. +However, there could be delays from minutes to hours. +Some Android vendors even restrict apps completely +(see dontkillmyapp.com) +and Delta Chat might not show incoming messages +until you manually open the app again.
+Force Background Connection: This is the fallback option +if the previous options are not available or do not achieve “instant delivery”. +Enabling it causes a permanent notification on your phone +which may sometimes be “minified” with recent Android phones.
+Both “Background Connection” options are energy-efficient and +safe to try if you experience messages arrive only with long delays.
+ +Delta Chat Push Notification support avoids leakage of private information. +It does not leak profile data, IP address or message content (not even encrypted) +to any system involved in the delivery of Push Notifications.
+ +Here is how Delta Chat apps perform Push Notification delivery:
+ +A Delta Chat app obtains a “device token” locally, encrypts it and stores it +on the chatmail server.
+When a chatmail server receives a message for a Delta Chat user +it forwards the encrypted device token to the central Delta Chat notification proxy.
+The central Delta Chat notification proxy decrypts the device token +and forwards it to the respective Push service (Apple, Google, etc.), +without ever knowing the IP or profile data of Delta Chat users.
+The central Push Service (Apple, Google, etc.) +wakes up the Delta Chat app on your device +to check for new messages in the background. +It does not know about the profile data of the device it wakes up. +The central Apple/Google Push services never see any profile data (sender or receiver) +and also never see any message content (also not in encrypted forms).
+The central Delta Chat notification proxy is small and fully implemented in Rust +and forgets about device-tokens as soon as Apple/Google/etc processed them, +usually in a matter of milliseconds.
+ +Note that the device token is encrypted between apps and notification proxy +but it is not signed. +The notification proxy thus never sees profile data, IP-addresses or +any cryptographic identity information associated with a user’s device (token).
+ +Resulting from this overall privacy design, even the seizure of a chatmail server, +or the full seizure of the central Delta Chat notification proxy +would not reveal private information that Push services do not already have.
+ +Delta Chat is a free and open source decentralized messenger with free server choice, +but we want users to reliably experience “instant delivery” of messages, +like they experience from WhatsApp, Signal or Telegram apps, +without asking questions up-front that are more suited to expert users or developers.
+ +Note that Delta Chat has a small and privacy-preserving Push Notification system +that achieves “instant delivery” of messages for all chatmail servers +including a potential one you might setup yourself without our permission. +Welcome to the power of the interoperable chatmail relay network :)
+ +Oui. You can use the same profile on different devices:
+ +Make sure both devices are on the same Wi-Fi or network
+Sur le premier appareil, allez dans Paramètres → Ajouter un deuxième appareil, déverrouillez l’écran si nécessaire, et patientez un peu jusqu’à ce qu’un code QR s’affiche.
+Sur le deuxième appareil, installez Delta Chat.
+Sur le deuxième appareil, ouvrez Delta Chat, sélectionnez Ajouter comme deuxième appareil, et scannez le code QR du premier appareil.
+Le transfert devrait commencer quelques secondes après et, pendant l’opération, les deux appareils affichent l’état d’avancement. +Patientez jusqu’à ce que le transfert soit terminé sur les deux appareils.
+Contrairement à de nombreuses autres messageries, une fois le transfert terminé, les deux appareils sont complètement indépendants. +L’un n’a pas besoin de l’autre pour pouvoir fonctionner.
+ +Vérifier à nouveau que les deux appareils sont sur le même réseau ou le même Wi-Fi.
+On Windows, go to Control Panel / Network and Internet +and make sure, Private Network is selected as “Network profile type” +(after transfer, you can change back to the original value)
+On iOS, make sure “System Settings / Apps / Delta Chat / Local Network” access is granted
+On macOS, enable “System Settings / Privacy & Security / Local Network / Delta Chat”
+Il se peut que votre système dispose d’un “pare-feu personnalisé”, +source bien connue de dysfonctionnements (en particulier sur Windows). +Désactivez le pare-feu personnalisé sur chaque appareil pour Delta Chat et réessayez.
+Guest Networks may not allow devices to communicate with each other. +If possible, use a non-guest network.
+If you still have troubles using the same network, +try to open Mobile Hotspot on one device and join that Wi-Fi from the other one
+Assurez-vous de disposer d’un espace de stockage suffisant sur l’appareil de destination.
+Une fois que le transfert a commencé, assurez-vous que les appareils restent actifs et ne se mettent pas en veille. +Ne quittez pas Delta Chat ! +(Nous faisons de notre mieux pour que l’application fonctionne en arrière-plan, mais les systèmes ont une fâcheuse tendance à tuer les applis.)
+Si Delta Chat est déjà connecté sur l’appareil de destination. +Vous pouvez utiliser plusieurs comptes par appareil : ajoutez un nouveau compte.
+Si les problèmes persistent, ou si vous ne pouvez pas scanner de code QR, essayez la méthode de transfert manuel décrite ci-dessous.
+Recourez à cette méthode uniquement si les instructions ci-dessus pour “Ajouter un deuxième appareil” ont échoué.
+ +At Settings → Advanced → Experimental Features +you can try out features we are working on.
+ +The features may be unstable and may be changed or removed.
+ +You can find more information +and give feedback in the Forum.
+ +We would like to improve Delta Chat with your help, +which is why Delta Chat for Android asks whether you want +to send anonymous usage statistics.
+ +You can turn it on and off at +Settings → Advanced → Send statistics to Delta Chat’s developers.
+ +When you turn it on, +weekly statistics will be automatically sent to a bot.
+ +We are interested e.g. in statistics like:
+ +We will not collect any personally identifiable information about you.
+ +Yes, but only if the email address is used exclusively by chatmail clients.
+ +It is not supported to share usage of an email address with non-chatmail apps or web-based mailers, +for the following reasons:
+ +Non-chatmail apps are largely not accomplishing automatic end-to-end email encryption for their users, +while chatmail apps and relays pervasively enforce end-to-end encryption and security standards.
+Non-chatmail apps use email servers as a long-term message archive +while chatmail clients use email servers for ephemeral instant message relay.
+Supporting the full variety of classic email setups +would require considerable development and maintenance efforts, +and complicate making chatmail-based messaging more resilient, reliable and fast.
+First off, please do not use the same classic email address also from non-chatmail classic email apps +unless you are prepared to deal with encrypted messages in the inbox, +double notifications, accidentally deleted emails or similar annoyances.
+ +You can configure a email address for chatting at New Profile → Use Other Server → Use Classic Mail as Relay.
+Note that classic email providers will generally not support Push Notifications
+and have other limitations, see Provider Overview.
+Chatmail uses the default INBOX for relay; ensure the provider setup does too.
+A chat profile using a classic email address allows to to send and receive unencrypted messages.
+These messages, and the chats they appear in, are marked with an email icon
+
.
Any well behaving email server setup will do fine +except if your users’ devices require Google/Apple Push Notifications to work properly.
+ +We generally recommend to set up a chatmail relay. +Chatmail is a community-driven project that encompasses both the setup of relays +and core Rust developments +that power chatmail clients of which Delta Chat is the most well known.
+ +Delta Chat uses a secure subset of the OpenPGP standard +to provide automatic end-to-end encryption using these protocols:
+ +Secure-Join +to exchange encryption setup information through QR-code scanning or “invite links”.
+Autocrypt is used for automatically +establishing end-to-end encryption between contacts and all members of a group chat.
+Sharing a contact to a +chat +enables receivers to use end-to-end encryption with the contact.
+Delta Chat does not query, publish or interact with any OpenPGP key servers.
+ +All messages in Delta Chat are end-to-end encrypted by default. +Since the Delta Chat Version 2 release series (July 2025) +there are no lock or similar markers on end-to-end encrypted messages, anymore.
+ +If you use default chatmail relays, +it is impossible to receive or send messages without end-to-end encryption.
+ +If you instead use a classic email server,
+you can send and receive messages with or without end-to-end encryption.
+Messages lacking end-to-end encryption are marked with an email icon
+
.
A contact profile might show a green checkmark
+
+and an “Introduced by” line.
+Every green-checkmarked contact either did a direct QR-scan with you
+or was introduced by a another green-checkmarked contact.
+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 QR-scan.
For more in-depth discussion of “guaranteed end-to-end encryption” +please see Secure-Join protocols +and specifically read about “Verified Groups”, the technical term +of what is called here “green-checkmarked” or “guaranteed end-to-end encrypted” chats.
+ +Oui.
+ +When we talk about an “end-to-end encrypted message” +we always mean a whole message is encrypted, +including all the attachments +and attachment metadata such as filenames.
+ +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.
+ +OpenPGP is not insecure by itself. +Most publicly discussed OpenPGP security problems +actually stem from bad usability or bad implementations of tools or apps (or both). +It is particularly important to distinguish between OpenPGP, the IETF encryption standard, +and GnuPG (GPG), a command line tool implementing OpenPGP. +Many public critiques of OpenPGP actually discuss GnuPG which Delta Chat has never used. +Delta Chat rather uses the OpenPGP Rust implementation rPGP, +available as an independent “pgp” package, +and security-audited in 2019 and 2024.
+ +We aim, along with other OpenPGP implementors, +to further improve security characteristics by implementing the +new IETF OpenPGP Crypto-Refresh +which was thankfully adopted in summer 2023.
+ +Yes, we are following efforts like MLS +but adopting them would mean breaking end-to-end encryption interoperability. +So it would not be a light decision to take +and there must be tangible improvements for users.
+ +Delta Chat takes a holistic “usable security” approach +and works with a wide range of activist groupings as well as +renowned researchers such as TeamUSEC +to improve actual user outcomes against security threats. +The wire protocol and standard for establishing end-to-end encryption is +only one part of “user outcomes”, +see also our answers to device-seizure +and message-metadata questions.
+ +No, Delta Chat never was vulnerable to EFAIL +because its OpenPGP implementation rPGP +uses Modification Detection Code when encrypting messages +and returns an error +if the Modification Detection Code is incorrect.
+ +Delta Chat also never was vulnerable to the “Direct Exfiltration” EFAIL attack
+because it only decrypts multipart/encrypted messages
+which contain exactly one encrypted and signed part,
+as defined by the Autocrypt Level 1 specification.
If you are sending or receiving email messages without end-to-end encryption (using a classic email server), +they are still protected from cell or cable companies who can not read or modify your email messages. +But both your and your recipient’s email providers +may read, analyze or modify your messages, including any attachments.
+ +Delta Chat by default uses strict +TLS encryption +which secures connections between your device and your email provider. +All of Delta Chat’s TLS-handling has been independently security audited. +Moreover, the connection between your and the recipient’s email provider +will typically be transport-encrypted as well. +If the involved email servers support MTA-STS +then transport encryption will be enforced between email providers +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.
+ +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.
+ +Servers can therefore only see:
+ +By default, the addresses are randomly generated.
+ +All other message, contact and group metadata resides in the end-to-end encrypted part of messages.
+ +Both for protecting against metadata-collecting servers +as well as against the threat of device seizure +we recommend to use a chatmail relay +to create chat profiles using random 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.
+ +No, not yet.
+ +The Signal messenger introduced “Sealed Sender” in 2018 +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.
+ +Even if chatmail relays +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 addresses for sealed sending +but an implementation has not been agreed as a priority yet.
+ +No, not yet.
+ +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.
+ +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 chatmail core, +which would make it available in all chatmail clients.
+ +No, not yet.
+ +Delta Chat uses the Rust OpenPGP library rPGP +which supports the latest IETF Post-Quantum-Cryptography OpenPGP draft. +We aim to add PQC support in chatmail core after the draft is finalized at the IETF +in collaboration with other OpenPGP implementers.
+ +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.
+ +No.
+ +Delta Chat generates secure OpenPGP keys according to the Autocrypt specification 1.1. +We do not recommend or offer users to perform manual key management. +We want to ensure that security audits can focus on a few proven cryptographic algorithms +instead of the full breadth of possible algorithms allowed with OpenPGP. +If you want to extract your OpenPGP key, there only is an expert method: +you need to look it up in the “keypairs” SQLite table of a profile backup tar-file.
+ +Yes, multiple times. +The Delta Chat project continuously undergoes independent security audits and analysis, +from most recent to older:
+ +2024 December, an NLNET-commissioned Evaluation of +rPGP by Radically Open Security took place. +rPGP serves as the end-to-end encryption OpenPGP engine of Delta Chat. +Two advisories were released related to the findings of this audit:
+ +The issues outlined in these advisories have been fixed and are part of Delta Chat +releases on all appstores since December 2024.
+2024 March, we received a deep security analysis from the Applied Cryptography +research group at ETH Zuerich and addressed all raised issues. +See our blog post about Hardening Guaranteed End-to-End encryption for more detailed information and the +Cryptographic Analysis of Delta Chat +research paper published afterwards.
+Début 2023, nous avons réparé les failles de sécurité et de confidentialité de la fonctionnalité “partage d’appli web dans une discussion” liées à des dysfonctionnements en mode bac à sable, en particulier avec Chromium. Après quoi, nous avons soumis Delta Chat à un nouvel audit de sécurité indépendant par Cure53, puis effectué les réparations de toutes les failles découvertes pour la version 1.36 de nos applications, publiée en avril 2023. +Vous trouverez ici un article de fond complet à propos de la sécurité du chiffrement de bout-en-bout sur internet.
+Début 2023, Cure53 a analysé le chiffrement d’acheminement des connexions réseau de Delta Chat et testé une configuration de serveur de courriel reproductible, telle que recommandée sur ce site. +Vous trouverez plus d’informations sur cet audit sur notre blog ou dans le rapport complet ici.
+En 2020, Include Security a analysé les bibliothèques principales Rust de Delta Chat, ainsi que ses bibliothèques IMAP, SMTP et TLS. +Aucun problème grave ou critique n’a été découvert. +Le rapport a tout de même révélé quelques vulnérabilités de gravité moyenne, qui ne représentent pas une menace en elles-mêmes pour les utilisateurs et les utilisatrices de Delta Chat, car elles dépendent de l’environnement dans lequel Delta Chat est utilisé. +Pour des raison de compatibilité et de facilité d’utilisation, nous ne pouvons pas les pallier toutes et avons préféré fournir des préconisations de sécurité aux personnes exposées. +Le rapport complet est consultable ici.
+En 2019, Include Security a analysé les bibliothèques PGP et +RSA de Delta Chat. +Aucune faille critique n’a été trouvée, mais deux failles sévères ont été identifiées et immédiatement réparées par nos soins. +Une faille de gravité moyenne ainsi que quelques failles de gravité moindre ont également été découvertes, sans qu’il soit toutefois possible de les exploiter dans le fonctionnement de Delta Chat. +Nous en avons néanmoins réparées certaines depuis le rapport d’audit. +Le rapport complet est consultable ici.
+Some features require certain permissions, +e.g. you need to grant camera permission if you want to scan an invite QR code.
+ +See Privacy Policy for a detailed overview.
+ +Delta Chat is available for all major and some minor platforms:
+ +The official website, https://delta.chat/download shows all options in detail
+If unavailable, use the mirror at https://deltachat.github.io/deltachat-pages
+Open one of the following app stores and search for “Delta Chat”: +Google Play Store, F-Droid, Huawei App Gallery, iOS and macOS App Store, Microsoft Store
+Check the package manager of your Linux distributions
+Android APKs are also available on https://github.com/deltachat/deltachat-android/releases
+Delta Chat ne reçoit par de fonds en capital-risque, n’est pas endetté et ne subit aucune pression pour générer de gros profits ou vendre ses utilisateurs et utilisatrices - en même temps que leurs amis et leur famille - à des annonceurs (ou pire). +Nous préférons utiliser des fonds provenant d’institutions publiques, jusqu’à présent basées en Europe ou aux États-Unis, pour soutenir nos efforts de développement d’un système de messagerie diversifié et décentralisé, basé sur les contributions de la communauté du libre et de l’open-source.
+ +Concretely, Delta Chat developments have so far been funded from these sources, +ordered chronologically:
+ +The NEXTLEAP EU project funded the research +and implementation of verified groups and setup contact protocols +in 2017 and 2018 and also helped to integrate end-to-end Encryption +through Autocrypt.
+L’association Open Technology Fund nous a octroyé une première subvention en 2018/2019 (de 200.000$ environ), grâce à laquelle nous avons pu apporter des améliorations majeures à l’application Android et publier une première version Beta de l’application de bureau. Elle nous a aussi permis d’ancrer notre recherche UX de développement de fonctionnalités dans des contextes de droits humains.
+À ce sujet, vous pouvez consulter notre rapport en anglais “Needfinding and UX report”.
+La seconde subvention de 2019/2020 (environ 300.000$) nous a permis de publier des version iOS de Delta Chat, de convertir notre bibliothèque principale en Rust et de créer de nouvelles fonctionnalités pour toutes les plateformes.
The NLnet foundation granted in 2019/2020 EUR 46K for +completing Rust/Python bindings and instigating a Chat-bot eco-system.
+In 2021 we received further EU funding for two Next-Generation-Internet +proposals, namely for EPPD - email provider portability directory (~97K EUR) and AEAP - email address porting (~90K EUR) which resulted in better multi-profile support, improved QR-code contact and group setups and many networking improvements on all platforms.
+From End 2021 till March 2023 we received Internet Freedom funding (500K USD) from the +U.S. Bureau of Democracy, Human Rights and Labor (DRL). +This funding supported our long-running goals to make Delta Chat more usable +and compatible with a wide range of email servers world-wide, and more resilient and secure +in places often affected by internet censorship and shutdowns.
+2023-2024 we successfully completed the OTF-funded +Secure Chatmail project, +allowing us to introduce guaranteed encryption, +creating a chatmail server network +and providing “instant onboarding” in all apps released from April 2024 on.
+In 2023 and 2024 we got accepted in the Next Generation Internet (NGI) +program for our work in webxdc PUSH, +along with collaboration partners working on +webxdc evolve, +webxdc XMPP, +DeltaTouch and +DeltaTauri. +All of these projects are partially completed or to be completed in early 2025.
+Nous recevons parfois des dons ponctuels de la part de personnes privées. + En 2021 par exemple, une généreuse personne nous a envoyé 4000€ par virement bancaire, avec l’intitulé “continuez votre super travail de développement !”. 💜 + Nous utilisons l’argent de ces dons pour financer des rencontres entre développeurs et développeuses ou pour des dépenses ponctuelles difficiles à anticiper ou à rembourser avec des subventions publiques. +Recevoir plus de dons aide notre communauté de contributrices et contributeurs à devenir plus indépendante et à rester viable sur le long terme.
+ + +Dernier point, mais certainement pas des moindres : quelques personnes passionnées et expertes ont apporté, et apportent toujours, leur contribution bénévole au développement de Delta Chat sans contrepartie financière - ou seulement de petites sommes. Sans leur énergie, Delta Chat n’en serait pas là aujourd’hui… et de très loin.
+Les financements mentionnés précédemment sont gérés principalement par merlinux GmbH à Fribourg (Allemagne) et redistribués à plus d’une douzaine de contributeurs et contributrices du monde entier.
+ +N’hésitez pas à consulter les Canaux de contribution à Delta Chat Contribution pour en savoir plus sur les différentes manières de contribuer, financières ou non.
+ + + + + \ No newline at end of file diff --git a/src/main/assets/help/go-to-original.png b/src/main/assets/help/go-to-original.png new file mode 100644 index 0000000000000000000000000000000000000000..88fcbe13eadae1fc984439956fc57f50c7f7a4b9 Binary files /dev/null and b/src/main/assets/help/go-to-original.png differ diff --git a/src/main/assets/help/green-checkmark.png b/src/main/assets/help/green-checkmark.png new file mode 100644 index 0000000000000000000000000000000000000000..8f42caaf2e2366baf8c37025d78233098233c1cc Binary files /dev/null and b/src/main/assets/help/green-checkmark.png differ diff --git a/src/main/assets/help/green-dot.png b/src/main/assets/help/green-dot.png new file mode 100644 index 0000000000000000000000000000000000000000..6419864b32be0ccc95800172324be64cf784539b Binary files /dev/null and b/src/main/assets/help/green-dot.png differ diff --git a/src/main/assets/help/help.css b/src/main/assets/help/help.css new file mode 100644 index 0000000000000000000000000000000000000000..b2770e33cdf8b1cf42a0ea67ee698ee6774229cb --- /dev/null +++ b/src/main/assets/help/help.css @@ -0,0 +1,36 @@ +html { + color-scheme: dark light; +} + +a { + text-decoration: none; +} + +h2, h3, h4 { + margin-top: 2rem; +} + +ul#top { + list-style-type: none; + margin: 1.2rem 0 0 0; + padding: 0; +} + +ul#top > li { + font-weight: bold !important; + font-size: 1.1rem !important; +} + +ul#top li { + margin-top: .7rem; + margin-bottom: .7rem; + font-weight: normal; + font-size: 1rem; +} + + +/* ---------- colors ---------- */ + +a { + color: #0078f1; +} diff --git a/src/main/assets/help/id/help.html b/src/main/assets/help/id/help.html new file mode 100644 index 0000000000000000000000000000000000000000..efc132aedb97a6a6ec45779817ca76996a46d571 --- /dev/null +++ b/src/main/assets/help/id/help.html @@ -0,0 +1,1668 @@ + +Delta Chat is a reliable, decentralized and secure instant messaging app, +available for mobile and desktop platforms.
+ +Instant creation of private chat profiles +with secure and interoperable chatmail relays +that offer instant message delivery, and Push Notifications for iOS and Android devices.
+Pervasive multi-profile and +multi-device support on all platforms +and between different chatmail apps.
+Interactive in-chat apps for gaming and collaboration
+Audited end-to-end encryption +safe against network and server attacks.
+Free and Open Source software, both app and server side, +built on Internet Standards.
+First, note that Delta Chat is a private messenger. +There is no public discovery, you decide about your contacts.
+ +If you are face to face with your friend or family,
+tap the QR Code icon
+on the main screen.
+Ask your chat partner to scan the QR image
+with their Delta Chat app.
For a remote contact setup, +from the same screen, +click “Copy” or “Share” and send the invite link +through another private chat.
+Now wait while connection gets established.
+ +If both sides are online, they will soon see a chat +and can start messaging securely.
+If one side is offline or in bad network, +the ability to chat is delayed until connectivity is restored.
+Congratulations! +You now will automatically use end-to-end encryption with this contact. +If you add each other to groups, end-to-end encryption will be established among all members.
+ +As being a private messenger, +only friends and family you share your QR code or invite link with can write to you.
+ +Your friends may share your contact with other friends, this appears as a request.
+ +You need to accept the request before you can reply.
+You can also delete it if you don’t want to chat with them for now.
+If you delete a request, future messages from that contact will still appear +as message request, so you can change your mind. If you really don’t want to +receive messages from this person, consider blocking them.
+Attach the first contact to the chat of the second using
Attachment Button → Contact.
+You can also add a little introduction message.
The second contact will receive a card then +and can tap it to start chatting with the first contact.
+ +Yes. Images, videos, files, voice messages etc. can be sent using the
Attachment-
+or
Voice Message buttons
For performance, images are optimized and sent at a smaller size by default, but you can send it as a “file” to preserve the original.
+A profile is a name, a picture and some additional information for encrypting messages. +A profile lives on your device(s) only +and uses the server only to relay messages.
+ +On first installation of Delta Chat a first profile is created.
+ +Later, you can tap your profile image in the upper left corner to Add Profiles +or to Switch Profiles.
+ +You may want to use separate profiles for political, family or work related activities.
+ +You may also wish to learn how to use the same profile on multiple devices.
+ +Anda dapat menambahkan gambar profil di pengaturan Anda. Jika Anda menulis ke kontak Anda +atau menambahkannya melalui kode QR, mereka secara otomatis melihatnya sebagai gambar profil Anda.
+Untuk alasan kerahasiaan, tidak ada satupun yang dapat melihat Foto Profil anda hingga anda menulis +sebuah pesan kepada mereka.
+Yes, +you can do so under Settings → Profile → Bio. +Once you sent a message to a contact, +they will see it when they view your contact details.
+ +Use these tools to organize your chats and keep everything in its place:
+ +Pinned chats always stay atop of the chat list. You can use them to access your most loved chats quickly or temporarily to not forget about things.
+Mute chats if you do not want to get notifications for them. Muted chats stay in place and you can also pin a muted chat.
+Archive chats if you do not want to see them in your chat list any longer. +Archived chats remain accessible above the chat list or via search.
+When an archived chat gets a new message, unless muted, it will pop out of the archive and back into your chat list. +Muted chats stay archived until you unarchive them manually.
+To use the functions, long tap or right click a chat in the chat list.
+ +Saved Messages is a chat that you can use to easily remember and find messages.
+ +In any chat, long tap or right click a message and select Save
+Saved messages are marked by the symbol
+
+next to the timestamp
Later, open the “Saved Messages” chat - and you will see the saved messages there.
+By tapping
,
+you can go back to the original message in the original chat
Finally, you can also use “Save Messages” to take personal notes - open the chat, type something, add a photo or a voice message etc.
+As “Saved Message” are synced, they can become very handy for transferring data between devices
+Messages stay saved even if they are edited or deleted - +may it be by sender, by device cleanup or by disappearing messages of other chats.
+ +You can sometimes see a green dot
+next to the avatar of a contact.
+It means they were recently seen by you in the last 10 minutes,
+e.g. because they messaged you or sent a read receipt.
So this is not a real time online status +and others will as well not always see that you are “online”.
+ +One tick
+means that the message was sent successfully to your provider.
Two ticks
+mean that at least one recipient’s device
+reported back to having received the message.
Recipients may have disabled read-receipts, +so even if you see only one tick, the message may have been read.
+The other way round, two ticks do not automatically mean +that a human has read or understood the message ;)
+You can edit the text of your messages after sending.
+For that, long tap or right click the message and select Edit
+or
.
If you have sent a message accidentally, +from the same menu, select Delete and then Delete for Everyone.
+While edited messages will have the word “Edited” next to the timestamp, +deleted messages will be removed without a marker in the chat. +Notifications are not sent and there is no time limit.
+ +Note, that the original message may still be received by chat members +who could have already replied, forwarded, saved, screenshotted or otherwise copied the message.
+ +You can turn on “disappearing messages” +in the settings of a chat, +at the top right of the chat window, +by selecting a time span +between 5 minutes and 1 year.
+ +Until the setting is turned off again, +each chat member’s Delta Chat app takes care +of deleting the messages +after the selected time span. +The time span begins +when the receiver first sees the message in Delta Chat. +The messages are deleted both, +on the servers, +and in the apps itself.
+ +Note that you can rely on disappearing messages +only as long as you trust your chat partners; +malicious chat partners can take photos, +or otherwise save, copy or forward messages before deletion.
+ +Apart from that, +if one chat partner uninstalls Delta Chat, +the (anyway encrypted) messages may take longer to get deleted from their server.
+ +If you are using more than one chat profile, +you can remove single ones in the top profile switcher menu (on Android and iOS), +or in the sidebar with a right click (in the Desktop app). +Chat profiles are only removed on the device where deletion was triggered. +Chat profiles on other devices will continue to fully function.
+ +If you use a single default chat profile you can simply uninstall the app. +This will still automatically trigger deletion of all associated address data on the chatmail server. +For more info, please refer to nine.testrun.org address-deletion +or the respective page from your chosen 3rd party chatmail server.
+ +Groups let several people chat together privately with equal rights.
+ +Anyone can +change the group name or avatar, +add or remove members, +set disappearing messages, +and delete their own messages from all member’s devices.
+ +Because all members have the same rights, groups work best among trusted friends and family.
+ +All group members have the same rights. +For this reason, everyone can delete any member or add new ones.
+To add or delete members, tap the group name in the chat and select the member to add or remove.
+If the member is not yet in your contact list, but face to face with you,
+from the same screen, show a QR code.
+Ask your chat partner to scan the QR image with their Delta Chat app by tapping
+
on the main screen.
For a remote member addition, +click “Copy” or “Share” and send the invite link +through another private chat to the new member.
+QR code and invite link can be used to add several members. +However, since groups are meant for trusted people, avoid sharing them publicly.
+ +Either delete yourself from the member list or delete the whole chat. +If you want to join the group again later on, ask another group member to add you again.
+As an alternative, you can also “Mute” a group - doing so means you get all messages and +can still write, but are no longer notified of any new messages.
+You can duplicate a group to start a separate discussion +or to exclude members without them noticing.
+ +Open the group profile and tap Clone Chat (Android/iOS), +or right-click the group in the chat list (Desktop).
+Set a new name, choose an avatar, and adjust the member list if needed.
+The new group is fully independent from the original, +which continues to work as before.
+ +You can send apps to a chat - games, editors, polls and other tools. +This makes Delta Chat a truly extensible messenger.
+ +In a chat, using
Attachment Button → Apps
You can also create your own app and attach it using
Attachment Button → File
In-chat apps can not send data to the Internet, or download anything.
+An in-chat app can only exchange data within a chat, with its +copies on the devices of your chat partners. Other than that, it’s completely +isolated from the Internet.
+The privacy an in-chat app offers is the privacy of your chat - as long as you +trust the people you chat with, you can trust the in-chat app as well.
+This also means: Just like for web links, do not open apps from untrusted contacts.
+In-chat apps are zip files with .xdc extension containing html, css, and javascript code.
You can extend the Hello World example app +to get started.
+All else you need to know is written in the +Webxdc documentation.
+If you have question, you can ask others with experience +in the Delta Chat Forum.
+Push Notifications are sent by Apple and Google “Push services” to a user’s device +so that an inactive Delta Chat app can fetch messages in the background +and show notifications on a user’s phone if needed.
+ +Push Notifications work with all chatmail servers on
+ +iOS devices, by integrating with Apple Push services.
+Android devices, by integrating with the Google FCM Push service, +including on devices that use microG +instead of proprietary Google code on the phone.
+Yes, Delta Chat automatically uses Push Notifications for chatmail profiles. +And no, there is no alternative on Apple’s phones to achieve instant message delivery +because Apple devices do not allow Delta Chat to fetch data in the background. +Push notifications are automatically activated for iOS users because +Delta Chat’s privacy-preserving Push Notification system +does not expose data to Apple that it doesn’t already have.
+ +If a “Push Service” is available, Delta Chat enables Push Notifications +to achieve instant message delivery for all chatmail users.
+ +In the Delta Chat “Notifications” settings for “Instant delivery” +you can change the following settings effecting all chat profiles:
+ +Use Background Connection: If you are not using a Push service, +you may disable “battery optimizations” for Delta Chat, +allowing it to fetch messages in the background. +However, there could be delays from minutes to hours. +Some Android vendors even restrict apps completely +(see dontkillmyapp.com) +and Delta Chat might not show incoming messages +until you manually open the app again.
+Force Background Connection: This is the fallback option +if the previous options are not available or do not achieve “instant delivery”. +Enabling it causes a permanent notification on your phone +which may sometimes be “minified” with recent Android phones.
+Both “Background Connection” options are energy-efficient and +safe to try if you experience messages arrive only with long delays.
+ +Delta Chat Push Notification support avoids leakage of private information. +It does not leak profile data, IP address or message content (not even encrypted) +to any system involved in the delivery of Push Notifications.
+ +Here is how Delta Chat apps perform Push Notification delivery:
+ +A Delta Chat app obtains a “device token” locally, encrypts it and stores it +on the chatmail server.
+When a chatmail server receives a message for a Delta Chat user +it forwards the encrypted device token to the central Delta Chat notification proxy.
+The central Delta Chat notification proxy decrypts the device token +and forwards it to the respective Push service (Apple, Google, etc.), +without ever knowing the IP or profile data of Delta Chat users.
+The central Push Service (Apple, Google, etc.) +wakes up the Delta Chat app on your device +to check for new messages in the background. +It does not know about the profile data of the device it wakes up. +The central Apple/Google Push services never see any profile data (sender or receiver) +and also never see any message content (also not in encrypted forms).
+The central Delta Chat notification proxy is small and fully implemented in Rust +and forgets about device-tokens as soon as Apple/Google/etc processed them, +usually in a matter of milliseconds.
+ +Note that the device token is encrypted between apps and notification proxy +but it is not signed. +The notification proxy thus never sees profile data, IP-addresses or +any cryptographic identity information associated with a user’s device (token).
+ +Resulting from this overall privacy design, even the seizure of a chatmail server, +or the full seizure of the central Delta Chat notification proxy +would not reveal private information that Push services do not already have.
+ +Delta Chat is a free and open source decentralized messenger with free server choice, +but we want users to reliably experience “instant delivery” of messages, +like they experience from WhatsApp, Signal or Telegram apps, +without asking questions up-front that are more suited to expert users or developers.
+ +Note that Delta Chat has a small and privacy-preserving Push Notification system +that achieves “instant delivery” of messages for all chatmail servers +including a potential one you might setup yourself without our permission. +Welcome to the power of the interoperable chatmail relay network :)
+ +Yes. You can use the same profile on different devices:
+ +Make sure both devices are on the same Wi-Fi or network
+On the first device, go to Settings → Add Second Device, unlock the screen if needed +and wait a moment until a QR code is shown
+On the second device, install Delta Chat
+On the second device, start Delta Chat, select Add as Second Device, and scan the QR code from the old device
+Transfer should start after a few seconds and during transfer both devices will show the progress. +Wait until it is finished on both devices.
+In contrast to many other messengers, after successful transfer, +both devices are completely independent. +One device is not needed for the other to work.
+ +Double-check both devices are in the same Wi-Fi or network
+On Windows, go to Control Panel / Network and Internet +and make sure, Private Network is selected as “Network profile type” +(after transfer, you can change back to the original value)
+On iOS, make sure “System Settings / Apps / Delta Chat / Local Network” access is granted
+On macOS, enable “System Settings / Privacy & Security / Local Network / Delta Chat”
+Your system might have a “personal firewall”, +which is known to cause problems (especially on Windows). +Disable the personal firewall for Delta Chat on both ends and try again
+Guest Networks may not allow devices to communicate with each other. +If possible, use a non-guest network.
+If you still have troubles using the same network, +try to open Mobile Hotspot on one device and join that Wi-Fi from the other one
+Ensure there is enough storage on the destination device
+If transfer started, make sure, the devices stay active and do not fall asleep. +Do not exit Delta Chat. +(we try hard to make the app work in background, but systems tend to kill apps, unfortunately)
+Delta Chat is already logged in on the destination device? +You can use multiple profiles per device, just add another profile
+If you still have problems or if you cannot scan a QR code +try the manual transfer described below
+This method is only recommended if “Add Second Device” as described above does not work.
+ +At Settings → Advanced → Experimental Features +you can try out features we are working on.
+ +The features may be unstable and may be changed or removed.
+ +You can find more information +and give feedback in the Forum.
+ +We would like to improve Delta Chat with your help, +which is why Delta Chat for Android asks whether you want +to send anonymous usage statistics.
+ +You can turn it on and off at +Settings → Advanced → Send statistics to Delta Chat’s developers.
+ +When you turn it on, +weekly statistics will be automatically sent to a bot.
+ +We are interested e.g. in statistics like:
+ +We will not collect any personally identifiable information about you.
+ +Yes, but only if the email address is used exclusively by chatmail clients.
+ +It is not supported to share usage of an email address with non-chatmail apps or web-based mailers, +for the following reasons:
+ +Non-chatmail apps are largely not accomplishing automatic end-to-end email encryption for their users, +while chatmail apps and relays pervasively enforce end-to-end encryption and security standards.
+Non-chatmail apps use email servers as a long-term message archive +while chatmail clients use email servers for ephemeral instant message relay.
+Supporting the full variety of classic email setups +would require considerable development and maintenance efforts, +and complicate making chatmail-based messaging more resilient, reliable and fast.
+First off, please do not use the same classic email address also from non-chatmail classic email apps +unless you are prepared to deal with encrypted messages in the inbox, +double notifications, accidentally deleted emails or similar annoyances.
+ +You can configure a email address for chatting at New Profile → Use Other Server → Use Classic Mail as Relay.
+Note that classic email providers will generally not support Push Notifications
+and have other limitations, see Provider Overview.
+Chatmail uses the default INBOX for relay; ensure the provider setup does too.
+A chat profile using a classic email address allows to to send and receive unencrypted messages.
+These messages, and the chats they appear in, are marked with an email icon
+
.
Any well behaving email server setup will do fine +except if your users’ devices require Google/Apple Push Notifications to work properly.
+ +We generally recommend to set up a chatmail relay. +Chatmail is a community-driven project that encompasses both the setup of relays +and core Rust developments +that power chatmail clients of which Delta Chat is the most well known.
+ +Delta Chat uses a secure subset of the OpenPGP standard +to provide automatic end-to-end encryption using these protocols:
+ +Secure-Join +to exchange encryption setup information through QR-code scanning or “invite links”.
+Autocrypt is used for automatically +establishing end-to-end encryption between contacts and all members of a group chat.
+Sharing a contact to a +chat +enables receivers to use end-to-end encryption with the contact.
+Delta Chat does not query, publish or interact with any OpenPGP key servers.
+ +All messages in Delta Chat are end-to-end encrypted by default. +Since the Delta Chat Version 2 release series (July 2025) +there are no lock or similar markers on end-to-end encrypted messages, anymore.
+ +If you use default chatmail relays, +it is impossible to receive or send messages without end-to-end encryption.
+ +If you instead use a classic email server,
+you can send and receive messages with or without end-to-end encryption.
+Messages lacking end-to-end encryption are marked with an email icon
+
.
A contact profile might show a green checkmark
+
+and an “Introduced by” line.
+Every green-checkmarked contact either did a direct QR-scan with you
+or was introduced by a another green-checkmarked contact.
+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 QR-scan.
For more in-depth discussion of “guaranteed end-to-end encryption” +please see Secure-Join protocols +and specifically read about “Verified Groups”, the technical term +of what is called here “green-checkmarked” or “guaranteed end-to-end encrypted” chats.
+ +Yes.
+ +When we talk about an “end-to-end encrypted message” +we always mean a whole message is encrypted, +including all the attachments +and attachment metadata such as filenames.
+ +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.
+ +OpenPGP is not insecure by itself. +Most publicly discussed OpenPGP security problems +actually stem from bad usability or bad implementations of tools or apps (or both). +It is particularly important to distinguish between OpenPGP, the IETF encryption standard, +and GnuPG (GPG), a command line tool implementing OpenPGP. +Many public critiques of OpenPGP actually discuss GnuPG which Delta Chat has never used. +Delta Chat rather uses the OpenPGP Rust implementation rPGP, +available as an independent “pgp” package, +and security-audited in 2019 and 2024.
+ +We aim, along with other OpenPGP implementors, +to further improve security characteristics by implementing the +new IETF OpenPGP Crypto-Refresh +which was thankfully adopted in summer 2023.
+ +Yes, we are following efforts like MLS +but adopting them would mean breaking end-to-end encryption interoperability. +So it would not be a light decision to take +and there must be tangible improvements for users.
+ +Delta Chat takes a holistic “usable security” approach +and works with a wide range of activist groupings as well as +renowned researchers such as TeamUSEC +to improve actual user outcomes against security threats. +The wire protocol and standard for establishing end-to-end encryption is +only one part of “user outcomes”, +see also our answers to device-seizure +and message-metadata questions.
+ +No, Delta Chat never was vulnerable to EFAIL +because its OpenPGP implementation rPGP +uses Modification Detection Code when encrypting messages +and returns an error +if the Modification Detection Code is incorrect.
+ +Delta Chat also never was vulnerable to the “Direct Exfiltration” EFAIL attack
+because it only decrypts multipart/encrypted messages
+which contain exactly one encrypted and signed part,
+as defined by the Autocrypt Level 1 specification.
If you are sending or receiving email messages without end-to-end encryption (using a classic email server), +they are still protected from cell or cable companies who can not read or modify your email messages. +But both your and your recipient’s email providers +may read, analyze or modify your messages, including any attachments.
+ +Delta Chat by default uses strict +TLS encryption +which secures connections between your device and your email provider. +All of Delta Chat’s TLS-handling has been independently security audited. +Moreover, the connection between your and the recipient’s email provider +will typically be transport-encrypted as well. +If the involved email servers support MTA-STS +then transport encryption will be enforced between email providers +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.
+ +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.
+ +Servers can therefore only see:
+ +By default, the addresses are randomly generated.
+ +All other message, contact and group metadata resides in the end-to-end encrypted part of messages.
+ +Both for protecting against metadata-collecting servers +as well as against the threat of device seizure +we recommend to use a chatmail relay +to create chat profiles using random 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.
+ +No, not yet.
+ +The Signal messenger introduced “Sealed Sender” in 2018 +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.
+ +Even if chatmail relays +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 addresses for sealed sending +but an implementation has not been agreed as a priority yet.
+ +No, not yet.
+ +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.
+ +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 chatmail core, +which would make it available in all chatmail clients.
+ +No, not yet.
+ +Delta Chat uses the Rust OpenPGP library rPGP +which supports the latest IETF Post-Quantum-Cryptography OpenPGP draft. +We aim to add PQC support in chatmail core after the draft is finalized at the IETF +in collaboration with other OpenPGP implementers.
+ +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.
+ +No.
+ +Delta Chat generates secure OpenPGP keys according to the Autocrypt specification 1.1. +We do not recommend or offer users to perform manual key management. +We want to ensure that security audits can focus on a few proven cryptographic algorithms +instead of the full breadth of possible algorithms allowed with OpenPGP. +If you want to extract your OpenPGP key, there only is an expert method: +you need to look it up in the “keypairs” SQLite table of a profile backup tar-file.
+ +Yes, multiple times. +The Delta Chat project continuously undergoes independent security audits and analysis, +from most recent to older:
+ +2024 December, an NLNET-commissioned Evaluation of +rPGP by Radically Open Security took place. +rPGP serves as the end-to-end encryption OpenPGP engine of Delta Chat. +Two advisories were released related to the findings of this audit:
+ +The issues outlined in these advisories have been fixed and are part of Delta Chat +releases on all appstores since December 2024.
+2024 March, we received a deep security analysis from the Applied Cryptography +research group at ETH Zuerich and addressed all raised issues. +See our blog post about Hardening Guaranteed End-to-End encryption for more detailed information and the +Cryptographic Analysis of Delta Chat +research paper published afterwards.
+2023 April, we fixed security and privacy issues with the “web +apps shared in a chat” feature, related to failures of sandboxing +especially with Chromium. We subsequently got an independent security +audit from Cure53 and all issues found were fixed in the 1.36 app series released in April 2023. +See here for the full background story on end-to-end security in the web.
+2023 March, Cure53 analyzed both the transport encryption of +Delta Chat’s network connections and a reproducible mail server setup as +recommended on this site. +You can read more about the audit on our blog +or read the full report here.
+2020, Include Security analyzed Delta +Chat’s Rust core, +IMAP, +SMTP, and +TLS libraries. +It did not find any critical or high-severity issues. +The report raised a few medium-severity weaknesses - +they are no threat to Delta Chat users on their own +because they depend on the environment in which Delta Chat is used. +For usability and compatibility reasons, +we can not mitigate all of them +and decided to provide security recommendations to threatened users. +You can read the full report here.
+2019, Include Security analyzed Delta +Chat’s PGP and +RSA libraries. +It found no critical issues, +but two high-severity issues that we subsequently fixed. +It also revealed one medium-severity and some less severe issues, +but there was no way to exploit these vulnerabilities in the Delta Chat implementation. +Some of them we nevertheless fixed since the audit was concluded. +You can read the full report here.
+Some features require certain permissions, +e.g. you need to grant camera permission if you want to scan an invite QR code.
+ +See Privacy Policy for a detailed overview.
+ +Delta Chat is available for all major and some minor platforms:
+ +The official website, https://delta.chat/download shows all options in detail
+If unavailable, use the mirror at https://deltachat.github.io/deltachat-pages
+Open one of the following app stores and search for “Delta Chat”: +Google Play Store, F-Droid, Huawei App Gallery, iOS and macOS App Store, Microsoft Store
+Check the package manager of your Linux distributions
+Android APKs are also available on https://github.com/deltachat/deltachat-android/releases
+Delta Chat does not receive any Venture Capital and +is not indebted, and under no pressure to produce huge profits, or to +sell users and their friends and family to advertisers (or worse). +We rather use public funding sources, so far from EU and US origins, to help +our efforts in instigating a decentralized and diverse chat messaging eco-system +based on Free and Open-Source community developments.
+ +Concretely, Delta Chat developments have so far been funded from these sources, +ordered chronologically:
+ +The NEXTLEAP EU project funded the research +and implementation of verified groups and setup contact protocols +in 2017 and 2018 and also helped to integrate end-to-end Encryption +through Autocrypt.
+The Open Technology Fund gave us a +first 2018/2019 grant (~$200K) during which we majorly improved the Android app +and released a first Desktop app beta version, and which moreover +moored our feature developments in UX research in human rights contexts, +see our concluding Needfinding and UX report. +The second 2019/2020 grant (~$300K) helped us to +release Delta/iOS versions, to convert our core library to Rust, and +to provide new features for all platforms.
+The NLnet foundation granted in 2019/2020 EUR 46K for +completing Rust/Python bindings and instigating a Chat-bot eco-system.
+In 2021 we received further EU funding for two Next-Generation-Internet +proposals, namely for EPPD - email provider portability directory (~97K EUR) and AEAP - email address porting (~90K EUR) which resulted in better multi-profile support, improved QR-code contact and group setups and many networking improvements on all platforms.
+From End 2021 till March 2023 we received Internet Freedom funding (500K USD) from the +U.S. Bureau of Democracy, Human Rights and Labor (DRL). +This funding supported our long-running goals to make Delta Chat more usable +and compatible with a wide range of email servers world-wide, and more resilient and secure +in places often affected by internet censorship and shutdowns.
+2023-2024 we successfully completed the OTF-funded +Secure Chatmail project, +allowing us to introduce guaranteed encryption, +creating a chatmail server network +and providing “instant onboarding” in all apps released from April 2024 on.
+In 2023 and 2024 we got accepted in the Next Generation Internet (NGI) +program for our work in webxdc PUSH, +along with collaboration partners working on +webxdc evolve, +webxdc XMPP, +DeltaTouch and +DeltaTauri. +All of these projects are partially completed or to be completed in early 2025.
+Terkadang kami menerima sumbangan satu kali dari perorangan. +Misalnya, pada tahun 2021, seorang dermawan perorangan mengirimi kami dana sebesar 4K EUR +dengan subjek “ikuti perkembangan yang baik!”. 💜 +Kami menggunakan uang tersebut untuk mendanai pertemuan pengembangan atau untuk biaya ad-hoc +yang tidak dapat dengan mudah diprediksi, atau diganti dari hibah dana publik. +Menerima lebih banyak donasi juga membantu kami untuk menjadi lebih mandiri dan +sebagai komunitas penyumbang.
+ + +Terakhir, beberapa ahli dan penggemar pro-bono turut berkontribusi +dan berkontribusi pada pengembangan Delta Chat tanpa menerima uang, atau hanya +hanya dalam jumlah kecil. Tanpa mereka, Delta Chat tidak akan berada di tempat seperti sekarang ini, bahkan tidak +bahkan tidak mendekati.
+Pendanaan moneter yang disebutkan di atas sebagian besar dikelola oleh merlinux GmbH di +Freiburg (Jerman), dan didistribusikan ke lebih dari selusin kontributor di seluruh dunia.
+ +Silakan lihat Saluran Kontribusi Delta Chat +untuk mengetahui kemungkinan kontribusi moneter dan kontribusi lainnya.
+ + + + + \ No newline at end of file diff --git a/src/main/assets/help/it/help.html b/src/main/assets/help/it/help.html new file mode 100644 index 0000000000000000000000000000000000000000..1ace4a16ccd8ee2c6cd3ad6a33ce8bcb820b4b69 --- /dev/null +++ b/src/main/assets/help/it/help.html @@ -0,0 +1,1662 @@ + +Delta Chat è un’app di messaggistica istantanea affidabile, decentralizzata e sicura, +disponibile per piattaforme mobili e desktop.
+ +Creazione istantanea di profili chat privati +con relay di chat +sicuri e interoperabili che offrono l’invio di messaggi istantanei e notifiche push per dispositivi iOS e Android.
+Supporto pervasivo multi-profilo e +multi-dispositivo su tutte le piattaforme +e tra diverse app di chatmail.
+Applicazioni interattive in-chat per giochi e collaborazione
+Crittografia end-to-end verificata +sicura contro gli attacchi alla rete e al server.
+Software Libero e Open Source, sia lato app che lato server, +basato su standard Internet.
+Innanzitutto, tieni presente che Delta Chat è un servizio di messaggistica privato. +Non c’è accesso pubblico, sei tu a decidere quali sono i tuoi contatti.
+ +Se ti trovi faccia a faccia con un amico o un familiare,
+tocca l’icona del Codice QR
+nella schermata principale.
+Chiedi al tuo interlocutore di scansionare l’immagine QR
+con la sua app Delta Chat.
Per impostare un contatto remoto, +dalla stessa schermata, +clicca su “Copia” o “Condividi” e invia il link di invito +tramite un’altra chat privata.
+Ora attendi che la connessione venga stabilita.
+ +Se entrambe le parti sono online, vedranno presto una chat +e potranno iniziare a inviare messaggi in modo sicuro.
+Se una delle due parti è offline o ha una rete scadente, +la possibilità di chattare viene ritardata finché la connettività non viene ripristinata.
+Congratulazioni! +Ora utilizzerai automaticamente la crittografia end-to-end con questo contatto. +Se vi aggiungete a vicenda a gruppi, la crittografia end-to-end verrà stabilita tra tutti i membri.
+ +Essendo un messenger privato, +solo gli amici e i familiari con cui condividi il tuo codice QR o il link di invito possono scriverti.
+ +I tuoi amici potrebbero condividere i tuoi contatti con altri amici; ciò apparirà come una richiesta.
+ +È necessario accettare la richiesta prima di poter rispondere.
+Si può anche cancellare il messaggio se non si vuole più chattare con esso.
+Se si elimina una richiesta, i futuri messaggi di quel contatto continueranno a essere visualizzati come richieste di contatto +in modo da poter cambiare idea. Se non si vuole davvero ricevere +messaggi da questa persona, prendete in considerazione la possibilità di bloccarla.
+Collega il primo contatto alla chat del secondo utilizzando
Pulsante Allegato → Contatto.
+Puoi anche aggiungere un breve messaggio di presentazione.
Il secondo contatto riceverà una scheda +e potrà toccarla per iniziare a chattare con il primo contatto.
+ +Sì. Immagini, video, files, messaggi vocali ecc. possono essere inviati utilizzando
Allegato-
+o
pulsanti Messaggio Vocale
Per le prestazioni, le immagini sono ottimizzate e inviate in dimensioni inferiori per impostazione predefinita, ma è possibile inviarle come “file” per preservare l’originale.
+Un profilo è costituito da un nome, un’immagine e alcune informazioni aggiuntive per la crittografia dei messaggi. +Un profilo è memorizzato solo sui tuoi dispositivo(i) +e utilizza il server solo per inoltrare i messaggi.
+ +Alla prima installazione di Delta Chat viene creato un primo profilo.
+ +Successivamente, puoi toccare l’immagine del tuo profilo nell’angolo in alto a sinistra per Aggiungere Profili +o Cambiare Profili.
+ +Potresti voler utilizzare profili separati per le attività politiche, familiari o lavorative.
+ +Potresti anche voler imparare come utilizzare lo stesso profilo su più dispositivi.
+ +Puoi aggiungere un’immagine del profilo nelle tue impostazioni. Se scrivi ai tuoi contatti +o li aggiungi tramite codice QR, la vedranno automaticamente come immagine del tuo profilo.
+Per motivi di privacy, nessuno vede la tua immagine del profilo finché non scrivi un +messaggio a loro.
+Sì, +puoi farlo in Impostazioni → Profilo → Biografia. +Una volta inviato un messaggio a un contatto, +lo vedrà quando visualizzerà i tuoi dati di contatto.
+ +Usa questi strumenti per organizzare le tue chat e tenere tutto in ordine:
+ +Chat fissate restano sempre in cima all’elenco. Puoi usarlo per accedere velocemente alle tue chat preferite o temporaneamente per non dimenticare alcune cose.
+Silenzia chat se non vuoi ricevere notifiche da queste. Le chat silenziate restano al loro posto e puoi anche fissare una chat silenziata.
+Archivia chats se non vuoi più vederle nel tuo elenco chat. +Le chat archiviate rimangono accessibili sopra l’elenco delle chat o tramite la ricerca.
+Quando una chat archiviata riceve un nuovo messaggio, a meno che non sia silenziata, salterà fuori dall’archivio e tornerà nell’elenco delle chat. +Le chat silenziate restano archiviate fino a che non le estrai manualmente.
+Per archiviare o fissare una chat, premi a lungo (Android), usa il menu della chat (Android/Desktop) o striscia verso sinistra (iOS); +per silenziare una chat, usa il menu della chat (Android/Desktop) o il profilo della chat (iOS).
+ +Messaggi Salvati è una chat che puoi usare per ricordare e trovare facilmente i messaggi.
+ +in qualunque chat, premi a lungo o click destro sul messaggio e seleziona Salva
+I messaggi salvati sono marcati col simbolo
+
+accanto all’ora d’invio
Successivamente, apri la chat “Messaggi Salvati” - e vedrai là i messaggi che hai salvato.
+Toccando
,
+puoi tornare al messaggio originale nella chat di provenienza.
Infine, puoi anche usare “Messaggi Salvati” per prendere appunti - apri la chat, digita qualcosa, aggiungi una foto o un messaggio vocale, ecc.
+Dato che i “Messaggi Salvati” sono sincronizzati, possono essere molto comodi per trasferire dati tra i dispositivi
+I messaggi restano salvati anche se vengono modificati o eliminati - +che sia dal mittente, ripulendo il dispositivo o per i messaggi a scomparsa di altre chat.
+ +A volte puoi vedere un punto verde
+accanto all’avatar di un contatto.
+Significa che sono stati visti di recente negli ultimi 10 minuti,
+ad es. perché ti hanno inviato un messaggio o una conferma di lettura.
Quindi questo non è uno stato online in tempo reale +e anche gli altri non sempre vedranno che sei “online”.
+ +Un segno di spunta
+significa che il messaggio è stato inviato correttamente al tuo fornitore.
Due spunte
+significa che almeno il dispositivo di un destinatario
+ha segnalato di aver ricevuto il messaggio.
I destinatari potrebbero aver disattivato le conferme di lettura, +quindi anche se vedi solo un segno di spunta, il messaggio potrebbe essere stato letto.
+Al contrario, due spunte non significano automaticamente +che un essere umano abbia letto o compreso il messaggio ;)
+Puoi modificare il testo dei tuoi messaggi già inviati.
+Per farlo, premi a lungo o click destro sul messaggio e seleziona Edit
+o
.
Se hai inviato un messaggio accidentalmente, +dallo stesso menu, seleziona Elimina e quindi Cancella per Tutti.
+Una volta modificati i messaggi avranno scritto “Modificato” accanto all’orario d’invio, +i messaggi eliminati saranno rimossi senza alcun avviso in chat. +Non vengono inviate notifiche e non c’è limite di tempo.
+ +Nota che il messaggio originale potrebbe essere ancora sui dispositivi dei membri della chat +che avrebbero già potuto rispondere, inoltrare, salvare, scattare una schermata o copiare il messaggio in altri modi.
+ +Puoi attivare i “messaggi a scomparsa” +nelle impostazioni di una chat, +in alto a destra nella finestra della chat, +selezionando un intervallo di tempo +compreso tra 5 minuti e 1 anno.
+ +Finché l’impostazione non viene disattivata nuovamente, +l’app Delta Chat di ciascun membro della chat si occupa +di eliminare i messaggidopo l’intervallo di tempo selezionato. +L’intervallo di tempo inizia +quando il destinatario vede per la prima volta il messaggio in Delta Chat. +I messaggi vengono eliminati sia +sui server +che nell’app stessa.
+ +Tieni presente che puoi fare affidamento sui messaggi che scompaiono +solo finché ti fidi dei tuoi partner di chat; +i partner di chat dannosi possono scattare foto, +o altrimenti salvare, copiare o inoltrare messaggi prima della cancellazione.
+ +Oltre a ciò, +se uno dei partecipanti alla chat disinstalla Delta Chat, +i messaggi (comunque crittografati) potrebbero richiedere più tempo per essere eliminati dal server.
+ +Se utilizzi più di un profilo chat, +puoi rimuoverne uno solo dal menu di selezione profilo in alto (su Android e iOS) +o dalla barra laterale con un clic destro (nell’app Desktop). +I profili chat vengono rimossi solo sul dispositivo in cui è stata attivata l’eliminazione. +I profili chat sugli altri dispositivi continueranno a funzionare correttamente.
+ +Se utilizzi un singolo profilo chat predefinito, puoi semplicemente disinstallare l’app. +Ciò attiverà comunque l’eliminazione automatica di tutti i dati di indirizzo associati sul server di chatmail. +Per maggiori informazioni, consulta nine.testrun.org cancellazione dell’indirizzo +o la pagina corrispondente del server chatmail di 3e parti da te scelto.
+ +I gruppi consentono a più persone di chattare insieme in privato con uguali diritti.
+ +Chiunque può +modificare il nome o l’avatar del gruppo, +aggiungere o rimuovere membri, +impostare messaggi che scompaiono +ed eliminare i propri messaggi dai dispositivi di tutti i membri.
+ +Poiché tutti i membri hanno gli stessi diritti, i gruppi funzionano meglio se formati da amici e familiari fidati.
+ +Tutti i membri del gruppo hanno gli stessi diritti. +Per questo motivo, tutti possono eliminare qualsiasi membro o aggiungerne di nuovi.
+Per aggiungere o eliminare membri, tocca il nome del gruppo nella chat e seleziona il membro da aggiungere o rimuovere.
+Se il membro non è ancora nella tua lista contatti, ma è faccia a faccia con te,
+dalla stessa schermata, mostra un codice QR.
+Chiedi al tuo interlocutore di scansionare l’immagine QR con la sua app Delta Chat toccando
+
nella schermata principale.
Per aggiungere un membro da remoto, +clicca su “Copia” o “Condividi” e invia il link di invito +tramite un’altra chat privata al nuovo membro.
+Il codice QR e il link di invito possono essere utilizzati per aggiungere più membri. +Tuttavia, poiché i gruppi sono destinati a persone fidate, evita di condividerli pubblicamente.
+ +Elimina te stesso dall’elenco dei membri o elimina l’intera chat. +Se vuoi unirti di nuovo al gruppo in un secondo momento, chiedi a un altro membro del gruppo di aggiungerti di nuovo.
+In alternativa, puoi anche “Silenziare” un gruppo - così facendo riceverai tutti i messaggi e +puoi ancora scrivere, ma non viene più notificato alcun nuovo messaggio.
+Puoi duplicare un gruppo per avviare una discussione separata +o per escludere membri senza che se ne accorgano.
+ +Apri il profilo del gruppo e tocca Clona Chat (Android/iOS), +oppure fai clic con il pulsante destro del mouse sul gruppo nell’elenco delle chat (Desktop).
+Imposta un nuovo nome, scegli un avatar e modifica l’elenco dei membri, se necessario.
+Il nuovo gruppo è completamente indipendente dall’originale, +che continua a funzionare come prima.
+ +È possibile inviare apps a una chat: giochi, editor, sondaggi e altri strumenti. +Questo rende Delta Chat un servizio di messaggistica davvero espandibile.
+ +In una chat, utilizzando
Pulsante Allegato → Apps
Puoi anche creare la tua app e allegarla usando
Pulsante Allegato → File
Le apps di chat non possono inviare dati a Internet né scaricare nulla.
+Un’app in-chat può scambiare dati solo all’interno di una chat Delta Chat, con le sue +copie sui dispositivi dei tuoi interlocutori. A parte questo, è completamente +isolata da Internet.
+La privacy offerta da un’app di chat è la privacy della tua chat: finché +ti fidi delle persone con cui chatti, puoi fidarti anche dell’app di chat.
+questo significa anche: proprio come per i link web, non aprire app provenienti da contatti non attendibili.
+In-chat apps are zip files with .xdc extension containing html, css, and javascript code.
You can extend the Hello World example app +to get started.
+All else you need to know is written in the +Webxdc documentation.
+If you have question, you can ask others with experience +in the Delta Chat Forum.
+Le Notifiche Push vengono inviate dai “Servizi push” di Apple e Google al dispositivo di un utente +in modo che un’app Delta Chat inattiva possa recuperare i messaggi in background +e mostrare le notifiche sul telefono di un utente, se necessario.
+ +Le Notifiche Push funzionano con tutti i server chatmail attivi
+ +Dispositivi iOS, attraverso l’integrazione con i servizi Push di Apple.
+Dispositivi Android, attraverso l’integrazione con il servizio Google FCM Push, +anche sui dispositivi che utilizzano microG +invece del codice proprietario di Google sul telefono.
+Sì, Delta Chat utilizza automaticamente le notifiche push per i profili chatmail. +E no, non esiste alcuna alternativa sui telefoni Apple per ottenere la consegna dei messaggi istantanei +perché i dispositivi Apple non consentono a Delta Chat di recuperare i dati in background. +Le notifiche push vengono attivate automaticamente per gli utenti iOS perché +Sistema di notifiche push che tutela la privacy di Delta Chat +non espone ad Apple i dati che non possiede già.
+ +If a “Push Service” is available, Delta Chat enables Push Notifications +to achieve instant message delivery for all chatmail users.
+ +Nelle impostazioni “Notifiche” di Delta Chat per “Consegna istantanea” +puoi modificare le seguenti impostazioni che interessano tutti i profili chat:
+ +Utilizza Connessione in Background: se non stai utilizzando un servizio Push, +puoi disattivare le “ottimizzazioni della batteria” per Delta Chat, +permettendogli di recuperare i messaggi in background. +Tuttavia potrebbero verificarsi ritardi da minuti ad ore. +Alcuni fornitori Android limitano addirittura completamente le app +(vedi dontkillmyapp.com) +e Delta Chat potrebbe non mostrare i messaggi in arrivo +finché non riapri manualmente l’app.
+Forza Connessione Background: questa è l’opzione di ripiego +se le opzioni precedenti non sono disponibili o non raggiungono la “consegna immediata”. +Abilitandolo si genera una notifica permanente sul tuo telefono +che a volte può essere “minimizzato” con i recenti telefoni Android.
+Entrambe le opzioni “Connessione in Background” sono efficienti dal punto di vista energetico ed +è sicuro provarlo se riscontri che i messaggi arrivano solo con lunghi ritardi.
+ +Delta Chat Push Notification support avoids leakage of private information. +It does not leak profile data, IP address or message content (not even encrypted) +to any system involved in the delivery of Push Notifications.
+ +Ecco come le app Delta Chat eseguono l’invio delle Notifiche Push:
+ +Un’app Delta Chat ottiene un “token del dispositivo” localmente, lo crittografa e lo memorizza sul server chatmail.
+When a chatmail server receives a message for a Delta Chat user +it forwards the encrypted device token to the central Delta Chat notification proxy.
+The central Delta Chat notification proxy decrypts the device token +and forwards it to the respective Push service (Apple, Google, etc.), +without ever knowing the IP or profile data of Delta Chat users.
+The central Push Service (Apple, Google, etc.) +wakes up the Delta Chat app on your device +to check for new messages in the background. +It does not know about the profile data of the device it wakes up. +The central Apple/Google Push services never see any profile data (sender or receiver) +and also never see any message content (also not in encrypted forms).
+Il proxy di notifica centrale di Delta Chat è piccolo e completamente implementato in Rust +e si dimentica dei gettoni del dispositivo non appena Apple/Google/ecc li elabora, +di solito nel giro di pochi millisecondi.
+ +Note that the device token is encrypted between apps and notification proxy +but it is not signed. +The notification proxy thus never sees profile data, IP-addresses or +any cryptographic identity information associated with a user’s device (token).
+ +Come risultato di questo disegno complessivo sulla riservatezza, anche il sequestro di un server chatmail, +o il sequestro totale del proxy di notifica centrale di Delta Chat +non rivelerebbe informazioni private che i servizi Push non abbiano già.
+ +Delta Chat è un messenger decentralizzato gratuito e open source con scelta libera del server, +ma vogliamo che gli utenti sperimentino in modo affidabile la “consegna istantanea” dei messaggi, +come sperimentano dalle app Whatsapp, Signal o Telegram, +senza porre domande in anticipo, più adatte a utenti esperti o sviluppatori.
+ +Note that Delta Chat has a small and privacy-preserving Push Notification system +that achieves “instant delivery” of messages for all chatmail servers +including a potential one you might setup yourself without our permission. +Welcome to the power of the interoperable chatmail relay network :)
+ +Sì. Puoi usare lo stesso profilo su diversi dispositivi:
+ +Assicurati che entrambi i dispositivi siano collegati alla stessa rete Wi-Fi o network
+Sul primo dispositivo, andare su Impostazioni → Aggiungi Secondo Dispositivo, sbloccare lo schermo se necessario +e attendere un attimo fino a quando non viene visualizzato un codice QR
+Sul secondo dispositivo, installare Delta Chat
+Sul secondo dispositivo, avviare Delta Chat, selezionare Aggiungi Come Secondo Dispositivo e scansionare il codice QR del vecchio dispositivo.
+Il trasferimento dovrebbe iniziare dopo pochi secondi e durante il trasferimento entrambi i dispositivi mostreranno il progresso. + Attendere il termine del trasferimento su entrambi i dispositivi.
+A differenza di molti altri messengers, dopo un trasferimento riuscito, +entrambi i dispositivi sono completamente indipendenti. +Un dispositivo non è necessario perché l’altro funzioni.
+ +Verificare che entrambi i dispositivi siano nella stessa rete o Wi-Fi.
+Su Windows, vai su Pannello di controllo / Rete e Internet +e assicurati che Rete Privata sia selezionata come “Tipo di profilo di rete” +(dopo il trasferimento è possibile ripristinare il valore originale)
+Su iOS, assicurati che l’accesso a “Impostazioni di Sistema / App / Delta Chat / Rete locale” sia concesso
+Su macOS, abilita “Impostazioni di Sistema / Privacy & Sicurezza / Rete locale / Delta Chat”
+Il sistema potrebbe avere un “personal firewall”, +che è noto per causare problemi (soprattutto su Windows). +Disattivare il firewall personale per Delta Chat su entrambe le estremità e riprovare.
+Reti Ospite potrebbero non consentire ai dispositivi di comunicare tra loro. +Se possibile, utilizza una rete non ospite.
+Se continui ad aver problemi usando la stessa rete, +prova ad aprire l’ Hotspot su uno dei dispositivi e collegati al quel Wi-Fi con l’altro
+Assicurarsi che sul dispositivo di destinazione ci sia disponibilità di memoria sufficiente.
+Se il trasferimento è iniziato, assicurarsi che i dispositivi rimangano attivi e non si addormentino. +Non uscire da Delta Chat. +(cerchiamo di far funzionare l’applicazione in background, ma i sistemi tendono a uccidere le applicazioni, purtroppo).
+Delta Chat è già connesso sul dispositivo di destinazione? +È possibile utilizzare più profili per dispositivo, basta aggiungere un altro profilo
+Se si riscontrano ancora problemi o se non si riesce a scansionare un codice QR +provate il trasferimento manuale descritto di seguito
+Questo metodo è consigliato solo se “Aggiungi Secondo Dispositivo” come descritto sopra non funziona.
+ +At Settings → Advanced → Experimental Features +you can try out features we are working on.
+ +The features may be unstable and may be changed or removed.
+ +You can find more information +and give feedback in the Forum.
+ +We would like to improve Delta Chat with your help, +which is why Delta Chat for Android asks whether you want +to send anonymous usage statistics.
+ +You can turn it on and off at +Settings → Advanced → Send statistics to Delta Chat’s developers.
+ +When you turn it on, +weekly statistics will be automatically sent to a bot.
+ +We are interested e.g. in statistics like:
+ +We will not collect any personally identifiable information about you.
+ +Yes, but only if the email address is used exclusively by chatmail clients.
+ +It is not supported to share usage of an email address with non-chatmail apps or web-based mailers, +for the following reasons:
+ +Non-chatmail apps are largely not accomplishing automatic end-to-end email encryption for their users, +while chatmail apps and relays pervasively enforce end-to-end encryption and security standards.
+Non-chatmail apps use email servers as a long-term message archive +while chatmail clients use email servers for ephemeral instant message relay.
+Supporting the full variety of classic email setups +would require considerable development and maintenance efforts, +and complicate making chatmail-based messaging more resilient, reliable and fast.
+First off, please do not use the same classic email address also from non-chatmail classic email apps +unless you are prepared to deal with encrypted messages in the inbox, +double notifications, accidentally deleted emails or similar annoyances.
+ +You can configure a email address for chatting at New Profile → Use Other Server → Use Classic Mail as Relay.
+Note that classic email providers will generally not support Push Notifications
+and have other limitations, see Provider Overview.
+Chatmail uses the default INBOX for relay; ensure the provider setup does too.
+A chat profile using a classic email address allows to to send and receive unencrypted messages.
+These messages, and the chats they appear in, are marked with an email icon
+
.
Any well behaving email server setup will do fine +except if your users’ devices require Google/Apple Push Notifications to work properly.
+ +We generally recommend to set up a chatmail relay. +Chatmail is a community-driven project that encompasses both the setup of relays +and core Rust developments +that power chatmail clients of which Delta Chat is the most well known.
+ +Delta Chat utilizza un sottoinsieme sicuro dello standard OpenPGP +per fornire la crittografia end-to-end automatica utilizzando questi protocolli:
+ +Secure-Join +per scambiare informazioni sulla configurazione della crittografia tramite la scansione del codice QR o i “link di invito”.
+Autocrypt viene utilizzato per stabilire +automaticamente la crittografia end-to-end tra i contatti e tutti i membri di una chat di gruppo.
+Condivisione di un contatto con una +chat +consente ai destinatari di utilizzare la crittografia end-to-end con il contatto.
+Delta Chat non esegue query, pubblica o interagisce con alcun server di chiavi OpenPGP.
+ +Tutti i messaggi in Delta Chat sono crittografati end-to-end per impostazione predefinita. +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.
+ +Se si utilizzano i relays di chatmail, +è impossibile ricevere o inviare messaggi senza la crittografia end-to-end.
+ +If you instead use a classic email server,
+you can send and receive messages with or without end-to-end encryption.
+Messages lacking end-to-end encryption are marked with an email icon
+
.
Il profilo di un contatto potrebbe mostrare una spunta verde
+
+e una linea “Verificato da”.
+Ogni contatto con la spunta verde ha fatto un QR-scan con te
+o è stato verificato da un altro contatto con la spunta verde.
+La verifica si ha automaticamente all’aggiunta dei membri nei gruppi.
+Chiunque aggiunga un contatto con spunta verde a un gruppo con solo membri con la spunta verde
+diventa colui che l’ha verificato.
+Nel profilo di un contatto puoi premere sul campo “Verificato da …” ripetutamente
+fino a che vedi con chi hai avuto un QR-scan.
Per una discussione più approfondita sulla “crittografia end-to-end garantita” +consultare Protocolli Secure-Join +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”.
+ +Sì.
+ +Quando parliamo di “messaggio crittografato end-to-end” +intendiamo sempre che l’intero messaggio è crittografato, +compresi tutti gli allegati +e metadati degli allegati come i nomi dei file.
+ +Sì, Delta Chat utilizza un sottoinsieme sicuro di OpenPGP +che richiede che l’intero messaggio sia correttamente crittografato e firmato. +Ad esempio, le “Firme staccate” non sono considerate sicure.
+ +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). +È particolarmente importante distinguere tra OpenPGP, lo standard di crittografia IETF, +e GnuPG (GPG), uno strumento da riga di comando che implementa OpenPGP. +Molte critiche pubbliche di OpenPGP in realtà discutono di GnuPG che Delta Chat non ha mai utilizzato. +Delta Chat utilizza piuttosto l’implementazione Rust di OpenPGP rPGP, +disponibile come un pacchetto “pgp” indipendente, +e verificato per la sicurezza nel 2019 e nel 2024.
+ +Puntiamo, insieme ad altri implementatori di OpenPGP, +per migliorare ulteriormente le caratteristiche di sicurezza implementando il +nuovo aggiornamento crittografico IETF OpenPGP che per fortuna è stato adottato nell’estate 2023.
+ +Yes, we are following efforts like MLS +but adopting them would mean breaking end-to-end encryption interoperability. +So it would not be a light decision to take +and there must be tangible improvements for users.
+ +Delta Chat adotta un approccio olistico di “sicurezza utilizzabile”. +e lavora anche con una vasta gamma di gruppi di attivisti +ricercatori rinomati come TeamUSEC +per migliorare i risultati effettivi degli utenti contro le minacce alla sicurezza. +Il protocollo dei messaggi e lo standard per stabilire la crittografia end-to-end è +solo una parte dei “risultati utente”, +vedi anche le nostre risposte a device-seizure +e domande su metadati-messaggio.
+ +No, Delta Chat non è mai stato vulnerabile all’EFAIL +perché la sua implementazione OpenPGP rPGP +utilizza il codice di rilevamento delle modifiche durante la crittografia dei messaggi +e restituisce un errore +se il codice di rilevamento della modifica non è corretto.
+ +Inoltre, Delta Chat non è mai stata vulnerabile all’attacco EFAIL “Direct Exfiltration” +perché decodifica solo i messaggi “multipart/encrypted”. +che contengono esattamente una parte crittografata e firmata, +come definito dalla specifica Autocrypt Level 1.
+ +If you are sending or receiving email messages without end-to-end encryption (using a classic email server), +they are still protected from cell or cable companies who can not read or modify your email messages. +But both your and your recipient’s email providers +may read, analyze or modify your messages, including any attachments.
+ +Delta Chat by default uses strict +TLS encryption +which secures connections between your device and your email provider. +All of Delta Chat’s TLS-handling has been independently security audited. +Moreover, the connection between your and the recipient’s email provider +will typically be transport-encrypted as well. +If the involved email servers support MTA-STS +then transport encryption will be enforced between email providers +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.
+ +A differenza della maggior parte degli altri servizi di messaggistica, +le apps Delta Chat non memorizzano alcun metadato sui contatti o sui gruppi sui server, né in forma crittografata. +Tutti i metadati dei gruppi sono invece crittografati end-to-end e memorizzati esclusivamente sui dispositivi degli utenti finali.
+ +Servers can therefore only see:
+ +By default, the addresses are randomly generated.
+ +Tutti gli altri metadati dei messaggi, dei contatti e dei gruppi risiedono nella parte crittografata end-to-end dei messaggi.
+ +Both for protecting against metadata-collecting servers +as well as against the threat of device seizure +we recommend to use a chatmail relay +to create chat profiles using random 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.
+ +No, non ancora.
+ +Il messenger Signal ha introdotto “Mittente Sigillato” nel 2018 +per impedire che la propria infrastruttura server venga a conoscenza di chi sta inviando un messaggio a un insieme di destinatari. +È particolarmente importante perché il server Signal conosce il numero di cellulare di ciascun profilo, +che di solito è associato a un’identità tramite passaporto.
+ +Even if chatmail relays +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 addresses for sealed sending +but an implementation has not been agreed as a priority yet.
+ +No, non ancora.
+ +Delta Chat al momento non supporta la tecnologia Perfect Forward Secrecy (PFS). +Ciò significa che se la tua chiave di decrittazione privata viene divulgata +e qualcuno ha raccolto i tuoi messaggi in transito precedenti, +sarà in grado di decifrarli e leggerli utilizzando la chiave di decrittazione divulgata. +Tieni presente che la tecnologia Forward Secrecy aumenta la sicurezza solo se elimini i messaggi. +In caso contrario, chi ottiene le tue chiavi di decrittazione +in genere è in grado di ottenere anche tutti i tuoi messaggi non eliminati +e non ha nemmeno bisogno di decifrare i messaggi raccolti in precedenza.
+ +Abbiamo progettato un approccio Forward Secrecy che ha superato +l’esame iniziale di alcuni crittografi ed esperti di implementazione +ma è in attesa di una stesura più formale +per accertarne l’affidabilità nella messaggistica federata e nell’utilizzo su più dispositivi, +prima di poter essere implementato in chatmail core, +che lo renderebbe disponibile in tutti i clients di chatmail.
+ +No, non ancora.
+ +Delta Chat utilizza la libreria Rust OpenPGP rPGP +che supporta l’ultima bozza IETF Post-Quantum-Cryptography OpenPGP. +Il nostro obiettivo è aggiungere il supporto PQC nel core di chatmail dopo che la bozza sarà stata finalizzata dall’IETF +in collaborazione con altri implementatori di OpenPGP.
+ +È 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.
+ +No.
+ +Delta Chat generates secure OpenPGP keys according to the Autocrypt specification 1.1. +We do not recommend or offer users to perform manual key management. +We want to ensure that security audits can focus on a few proven cryptographic algorithms +instead of the full breadth of possible algorithms allowed with OpenPGP. +If you want to extract your OpenPGP key, there only is an expert method: +you need to look it up in the “keypairs” SQLite table of a profile backup tar-file.
+ +Sì, più volte. +Il progetto Delta Chat è sottoposto costantemente a verifiche e analisi di sicurezza indipendenti, +dal più recente al più vecchio:
+ +Dicembre 2024, un Valutazione commissionata da NLNET di +rPGP di Radically Open Security ha preso parte. +rPGP serves as the end-to-end encyption OpenPGP engine of Delta Chat. +Sono stati rilasciati due avvisi relativi ai risultati di questa verifica:
+ +I problemi descritti in questi avvisi sono stati risolti e fanno +parte delle versioni di Delta Chat +su tutti gli appstore da Dicembre 2024.
+Marzo 2024, abbiamo ricevuto un’analisi approfondita della sicurezza dalla Crittografia Applicata +gruppo di ricerca dell’ETH di Zurigo e ha affrontato tutte le questioni sollevate. +Consulta il nostro post sul blog su Rafforzamento della crittografia end-to-end garantita per informazioni più dettagliate e +Analisi crittografica di Delta Chat +articolo di ricerca pubblicato successivamente.
+A partire dal 2023, abbiamo risolto i problemi di sicurezza e privacy con il servizio “web +app condivise in una chat”, relativa ai guasti del sandboxing +soprattutto con Chromium. Successivamente abbiamo ottenuto una sicurezza indipendente +audit da Cure53 e tutti i problemi rilevati sono stati risolti nella serie di app 1.36 rilasciata nell’aprile 2023. +Vedi qui per la storia completa sulla sicurezza end-to-end nel web.
+A partire dal 2023, Cure53 ha analizzato sia la crittografia del trasporto delle +Connessioni di rete di Delta Chat e una configurazione del server di posta riproducibile come +consigliato su questo sito. +Puoi leggere ulteriori informazioni sull’audit sul nostro blog +o leggere il rapporto completo qui.
+Nel 2020, Include Security ha analizzato il Delta +Chat’s Rust core, +IMAP, +SMTP e +TLS librerie. +Non ha rilevato problemi critici o di elevata gravità. +Il rapporto ha sollevato alcuni punti deboli di media gravità: +da soli non rappresentano una minaccia per gli utenti di Delta Chat +perché dipendono dall’ambiente in cui viene utilizzato Delta Chat. +Per motivi di usabilità e compatibilità, +non possiamo mitigarli tutti +e ha deciso di fornire consigli sulla sicurezza agli utenti minacciati. +Puoi leggere il rapporto completo qui.
+Nel 2019, Include Security ha analizzato le librerie +PGP e +RSA di Delta Chat. +Non ha riscontrato criticità, +ma due problemi di elevata gravità che abbiamo successivamente risolto. +Ne sono emersi anche uno di media gravità e alcuni problemi meno gravi, +ma non c’era modo di sfruttare queste vulnerabilità nell’implementazione di Delta Chat. +Alcuni di essi sono stati comunque corretti dopo la conclusione dell’audit. +Puoi leggere il rapporto completo qui.
+Some features require certain permissions, +e.g. you need to grant camera permission if you want to scan an invite QR code.
+ +See Privacy Policy for a detailed overview.
+ +Delta Chat è disponibile per tutte le piattaforme principali e alcune minori:
+ +Il sito ufficiale, https://delta.chat/download mostra tutte le opzioni in dettaglio
+Se non disponibile, utilizzare mirror su https://deltachat.github.io/deltachat-pages
+Open one of the following app stores and search for “Delta Chat”: +Google Play Store, F-Droid, Huawei App Gallery, iOS and macOS App Store, Microsoft Store
+Controlla il gestore pacchetti delle tue distribuzioni Linux
+APK Android sono disponibili anche su https://github.com/deltachat/deltachat-android/releases
+Delta Chat non riceve alcun capitale di rischio e +non è indebitato e non è sotto pressione per produrre enormi profitti, o per farlo +vendere utenti e i loro amici e familiari agli inserzionisti (o peggio). +Utilizziamo piuttosto fonti di finanziamento pubblico, così lontane dalle origini dell’UE e degli Stati Uniti, per aiutare +i nostri sforzi nell’istigare un ecosistema di messaggistica di chat decentralizzato e diversificato +basato sugli sviluppi della comunità Free e Open-Source.
+ +Concretamente, lo sviluppo di Delta Chat è stato finora finanziato da queste fonti, +ordinate cronologicamente:
+ +Il progetto UE NEXTLEAP ha finanziato la ricerca +e implementazione di gruppi verificati e impostazione di protocolli di contatto +nel 2017 e nel 2018 e ha anche contribuito a integrare la crittografia end-to-end +tramite Autocrypt.
+L’Open Technology Fund ci ha dato una +prima sovvenzione 2018/2019 (~$200K) durante la quale abbiamo notevolmente migliorato l’app Android +e ha rilasciato una prima versione beta dell’app desktop, e che inoltre +ancorato i nostri sviluppi delle funzionalità nella ricerca sulla UX nei contesti dei diritti umani, +vedete il nostro Rapporto Needfinding e UX conclusivo. +La seconda sovvenzione 2019/2020 (~$300K) ci ha aiutato a farlo +rilasciare nelle versioni Delta/iOS, per convertire la nostra libreria principale in Rust, e +per fornire nuove funzionalità per tutte le piattaforme.
+La fondazione NLnet ha concesso nel 2019/2020 46.000 EUR per +completando i collegamenti Rust/Python e avviando un ecosistema Chat-bot.
+In 2021 we received further EU funding for two Next-Generation-Internet +proposals, namely for EPPD - email provider portability directory (~97K EUR) and AEAP - email address porting (~90K EUR) which resulted in better multi-profile support, improved QR-code contact and group setups and many networking improvements on all platforms.
+From End 2021 till March 2023 we received Internet Freedom funding (500K USD) from the +U.S. Bureau of Democracy, Human Rights and Labor (DRL). +This funding supported our long-running goals to make Delta Chat more usable +and compatible with a wide range of email servers world-wide, and more resilient and secure +in places often affected by internet censorship and shutdowns.
+2023-2024 abbiamo completato con successo il progetto Chatmail Sicuro finanziato da OTF, +consentendoci di introdurre la crittografia garantita, +creando una rete di server di chatmail +e fornendo “inserimento immediato” in tutte le app rilasciate da aprile 2024 in poi.
+Nel 2023 e nel 2024 siamo stati accettati nel programma Next Generation Internet (NGI) +per il nostro lavoro in webxdc PUSH, +insieme ai partner di collaborazione che lavorano su +webxdc evolve, +webxdc XMPP, +DeltaTouch e +DeltaTauri. +Tutti questi progetti sono parzialmente completati o saranno completati all’inizio del 2025.
+A volte riceviamo donazioni una tantum da privati. +Ad esempio, nel 2021 un generoso individuo ci ha trasferito in banca 4K EUR +con l’oggetto “continuate il buon sviluppo!”. 💜 +Usiamo questi soldi per finanziare incontri di sviluppo o per sostenere spese ad hoc +che non possono essere facilmente previsti o rimborsati da finanziamenti pubblici. +Ricevere più donazioni ci aiuta anche a diventare più indipendenti e vitali a lungo termine +come comunità di contributori.
+ + +Ultimo ma non meno importante, hanno contribuito diversi esperti e appassionati pro-bono +e contribuito allo sviluppo di Delta Chat senza ricevere denaro, o solo +piccole quantità. Senza di loro, Delta Chat non sarebbe dove è oggi, nemmeno +vicino.
+Il finanziamento monetario di cui sopra è per lo più organizzato da merlinux GmbH in +Friburgo (Germania) ed è distribuito a più di una dozzina di contributori in tutto il mondo.
+ +Consulta Canali contribuzione di Delta Chat +sia per le possibilità monetarie che contributive.
+ + + + + \ No newline at end of file diff --git a/src/main/assets/help/mic.png b/src/main/assets/help/mic.png new file mode 100644 index 0000000000000000000000000000000000000000..ed5d44845a84e008da9a5e54c2f4bb335791e132 Binary files /dev/null and b/src/main/assets/help/mic.png differ diff --git a/src/main/assets/help/nl/help.html b/src/main/assets/help/nl/help.html new file mode 100644 index 0000000000000000000000000000000000000000..969f7da2a53671c64d33dc9a01c4aa602310c902 --- /dev/null +++ b/src/main/assets/help/nl/help.html @@ -0,0 +1,1665 @@ + +Delta Chat is a reliable, decentralized and secure instant messaging app, +available for mobile and desktop platforms.
+ +Instant creation of private chat profiles +with secure and interoperable chatmail relays +that offer instant message delivery, and Push Notifications for iOS and Android devices.
+Pervasive multi-profile and +multi-device support on all platforms +and between different chatmail apps.
+Interactive in-chat apps for gaming and collaboration
+Audited end-to-end encryption +safe against network and server attacks.
+Free and Open Source software, both app and server side, +built on Internet Standards.
+First, note that Delta Chat is a private messenger. +There is no public discovery, you decide about your contacts.
+ +If you are face to face with your friend or family,
+tap the QR Code icon
+on the main screen.
+Ask your chat partner to scan the QR image
+with their Delta Chat app.
For a remote contact setup, +from the same screen, +click “Copy” or “Share” and send the invite link +through another private chat.
+Now wait while connection gets established.
+ +If both sides are online, they will soon see a chat +and can start messaging securely.
+If one side is offline or in bad network, +the ability to chat is delayed until connectivity is restored.
+Congratulations! +You now will automatically use end-to-end encryption with this contact. +If you add each other to groups, end-to-end encryption will be established among all members.
+ +As being a private messenger, +only friends and family you share your QR code or invite link with can write to you.
+ +Your friends may share your contact with other friends, this appears as a request.
+ +Accepteer het verzoek om te kunnen antwoorden.
+Ook kun je het verzoek verwijderen als je op dat moment geen gesprek met ze wilt voeren.
+Als je een verzoek verwijderd, dan worden toekomstige berichten nog steeds als verzoek getoond, +zodat je te allen tijde kunt bepalen of je het alsnog wilt accepteren. Als je écht geen contact wilt leggen, overweeg dan +om de persoon in kwestie te blokkeren.
+Attach the first contact to the chat of the second using
Attachment Button → Contact.
+You can also add a little introduction message.
The second contact will receive a card then +and can tap it to start chatting with the first contact.
+ +Yes. Images, videos, files, voice messages etc. can be sent using the
Attachment-
+or
Voice Message buttons
Om de prestaties te verhogen, worden afbeeldingen standaard geoptimaliseerd en verkleind verstuurd, maar je kunt ze als een bestand verzenden om het origineel te sturen.
+A profile is a name, a picture and some additional information for encrypting messages. +A profile lives on your device(s) only +and uses the server only to relay messages.
+ +On first installation of Delta Chat a first profile is created.
+ +Later, you can tap your profile image in the upper left corner to Add Profiles +or to Switch Profiles.
+ +You may want to use separate profiles for political, family or work related activities.
+ +You may also wish to learn how to use the same profile on multiple devices.
+ +In de instellingen kun je een profielfoto toevoegen. Als je een bericht stuurt aan +je contactpersonen of ze toevoegt middels hun QR-code, dan krijgen ze je profielfoto te zien.
+Omwille van je privacy, krijgen anderen je profielfoto pas te zien +als je ze een bericht stuurt.
+Yes, +you can do so under Settings → Profile → Bio. +Once you sent a message to a contact, +they will see it when they view your contact details.
+ +Met deze hulpmiddelen kun je je gesprekken geordend houden:
+ +Vastgemaakte gesprekken vind je te allen tijde bovenaan de gesprekslijst terug. Zo kun je je belangrijste gesprekken permanent of tijdelijk bij de hand houden, zodat je niets vergeet.
+Stel gesprekken in op Negeren als je geen meldingen meer wilt ontvangen. Wel blijven genegeerde gesprekken op de lijst staan en kun je ze te allen tijde vastmaken.
+Archiveer gesprekken als je ze niet meer op de gesprekslijst wilt zien. +Gearchiveerde gesprekken zijn te allen tijde te bekijken boven de lijst of via een zoekopdracht.
+Als er een nieuw bericht in een gearchiveerd gesprek wordt ontvangen, dan wordt het gesprek in kwestie ge-dearchiveerd en dus weer op de gesprekslijst geplaatst. +Genegeerde gesprekken blijven in het archief staan totdat je ze er zelf uithaalt.
+Archiveer of maak een gesprek vast door het gesprek in kwestie lang ingedrukt te houden (Android), via het gespreksmenu (Android/computer) of door het naar links te vegen (iOS). +Negeer een gesprek via het gespreksmenu (Android/computer) of het gespreksprofiel (iOS).
+ +Saved Messages is a chat that you can use to easily remember and find messages.
+ +In any chat, long tap or right click a message and select Save
+Saved messages are marked by the symbol
+
+next to the timestamp
Later, open the “Saved Messages” chat - and you will see the saved messages there.
+By tapping
,
+you can go back to the original message in the original chat
Finally, you can also use “Save Messages” to take personal notes - open the chat, type something, add a photo or a voice message etc.
+As “Saved Message” are synced, they can become very handy for transferring data between devices
+Messages stay saved even if they are edited or deleted - +may it be by sender, by device cleanup or by disappearing messages of other chats.
+ +You can sometimes see a green dot
+next to the avatar of a contact.
+It means they were recently seen by you in the last 10 minutes,
+e.g. because they messaged you or sent a read receipt.
So this is not a real time online status +and others will as well not always see that you are “online”.
+ +One tick
+means that the message was sent successfully to your provider.
Two ticks
+mean that at least one recipient’s device
+reported back to having received the message.
Recipients may have disabled read-receipts, +so even if you see only one tick, the message may have been read.
+The other way round, two ticks do not automatically mean +that a human has read or understood the message ;)
+You can edit the text of your messages after sending.
+For that, long tap or right click the message and select Edit
+or
.
If you have sent a message accidentally, +from the same menu, select Delete and then Delete for Everyone.
+While edited messages will have the word “Edited” next to the timestamp, +deleted messages will be removed without a marker in the chat. +Notifications are not sent and there is no time limit.
+ +Note, that the original message may still be received by chat members +who could have already replied, forwarded, saved, screenshotted or otherwise copied the message.
+ +You can turn on “disappearing messages” +in the settings of a chat, +at the top right of the chat window, +by selecting a time span +between 5 minutes and 1 year.
+ +Until the setting is turned off again, +each chat member’s Delta Chat app takes care +of deleting the messages +after the selected time span. +The time span begins +when the receiver first sees the message in Delta Chat. +The messages are deleted both, +on the servers, +and in the apps itself.
+ +Note that you can rely on disappearing messages +only as long as you trust your chat partners; +malicious chat partners can take photos, +or otherwise save, copy or forward messages before deletion.
+ +Apart from that, +if one chat partner uninstalls Delta Chat, +the (anyway encrypted) messages may take longer to get deleted from their server.
+ +If you are using more than one chat profile, +you can remove single ones in the top profile switcher menu (on Android and iOS), +or in the sidebar with a right click (in the Desktop app). +Chat profiles are only removed on the device where deletion was triggered. +Chat profiles on other devices will continue to fully function.
+ +If you use a single default chat profile you can simply uninstall the app. +This will still automatically trigger deletion of all associated address data on the chatmail server. +For more info, please refer to nine.testrun.org address-deletion +or the respective page from your chosen 3rd party chatmail server.
+ +Groups let several people chat together privately with equal rights.
+ +Anyone can +change the group name or avatar, +add or remove members, +set disappearing messages, +and delete their own messages from all member’s devices.
+ +Because all members have the same rights, groups work best among trusted friends and family.
+ +All group members have the same rights. +For this reason, everyone can delete any member or add new ones.
+To add or delete members, tap the group name in the chat and select the member to add or remove.
+If the member is not yet in your contact list, but face to face with you,
+from the same screen, show a QR code.
+Ask your chat partner to scan the QR image with their Delta Chat app by tapping
+
on the main screen.
For a remote member addition, +click “Copy” or “Share” and send the invite link +through another private chat to the new member.
+QR code and invite link can be used to add several members. +However, since groups are meant for trusted people, avoid sharing them publicly.
+ +Verwijder jezelf van de groepslijst of verwijder het hele groepsgesprek. +Als je later weer wilt deelnemen, vraag dan iemand anders of hij/zij je weer wilt toevoegen.
+Wat ook kan doen is groepsmeldingen uitschakelen. Zo blijf je in de groep, maar ontvang je +geen meldingen meer als er nieuwe berichten zijn.
+You can duplicate a group to start a separate discussion +or to exclude members without them noticing.
+ +Open the group profile and tap Clone Chat (Android/iOS), +or right-click the group in the chat list (Desktop).
+Set a new name, choose an avatar, and adjust the member list if needed.
+The new group is fully independent from the original, +which continues to work as before.
+ +You can send apps to a chat - games, editors, polls and other tools. +This makes Delta Chat a truly extensible messenger.
+ +In a chat, using
Attachment Button → Apps
You can also create your own app and attach it using
Attachment Button → File
In-chat apps can not send data to the Internet, or download anything.
+An in-chat app can only exchange data within a chat, with its +copies on the devices of your chat partners. Other than that, it’s completely +isolated from the Internet.
+The privacy an in-chat app offers is the privacy of your chat - as long as you +trust the people you chat with, you can trust the in-chat app as well.
+This also means: Just like for web links, do not open apps from untrusted contacts.
+In-chat apps are zip files with .xdc extension containing html, css, and javascript code.
You can extend the Hello World example app +to get started.
+All else you need to know is written in the +Webxdc documentation.
+If you have question, you can ask others with experience +in the Delta Chat Forum.
+Push Notifications are sent by Apple and Google “Push services” to a user’s device +so that an inactive Delta Chat app can fetch messages in the background +and show notifications on a user’s phone if needed.
+ +Push Notifications work with all chatmail servers on
+ +iOS devices, by integrating with Apple Push services.
+Android devices, by integrating with the Google FCM Push service, +including on devices that use microG +instead of proprietary Google code on the phone.
+Yes, Delta Chat automatically uses Push Notifications for chatmail profiles. +And no, there is no alternative on Apple’s phones to achieve instant message delivery +because Apple devices do not allow Delta Chat to fetch data in the background. +Push notifications are automatically activated for iOS users because +Delta Chat’s privacy-preserving Push Notification system +does not expose data to Apple that it doesn’t already have.
+ +If a “Push Service” is available, Delta Chat enables Push Notifications +to achieve instant message delivery for all chatmail users.
+ +In the Delta Chat “Notifications” settings for “Instant delivery” +you can change the following settings effecting all chat profiles:
+ +Use Background Connection: If you are not using a Push service, +you may disable “battery optimizations” for Delta Chat, +allowing it to fetch messages in the background. +However, there could be delays from minutes to hours. +Some Android vendors even restrict apps completely +(see dontkillmyapp.com) +and Delta Chat might not show incoming messages +until you manually open the app again.
+Force Background Connection: This is the fallback option +if the previous options are not available or do not achieve “instant delivery”. +Enabling it causes a permanent notification on your phone +which may sometimes be “minified” with recent Android phones.
+Both “Background Connection” options are energy-efficient and +safe to try if you experience messages arrive only with long delays.
+ +Delta Chat Push Notification support avoids leakage of private information. +It does not leak profile data, IP address or message content (not even encrypted) +to any system involved in the delivery of Push Notifications.
+ +Here is how Delta Chat apps perform Push Notification delivery:
+ +A Delta Chat app obtains a “device token” locally, encrypts it and stores it +on the chatmail server.
+When a chatmail server receives a message for a Delta Chat user +it forwards the encrypted device token to the central Delta Chat notification proxy.
+The central Delta Chat notification proxy decrypts the device token +and forwards it to the respective Push service (Apple, Google, etc.), +without ever knowing the IP or profile data of Delta Chat users.
+The central Push Service (Apple, Google, etc.) +wakes up the Delta Chat app on your device +to check for new messages in the background. +It does not know about the profile data of the device it wakes up. +The central Apple/Google Push services never see any profile data (sender or receiver) +and also never see any message content (also not in encrypted forms).
+The central Delta Chat notification proxy is small and fully implemented in Rust +and forgets about device-tokens as soon as Apple/Google/etc processed them, +usually in a matter of milliseconds.
+ +Note that the device token is encrypted between apps and notification proxy +but it is not signed. +The notification proxy thus never sees profile data, IP-addresses or +any cryptographic identity information associated with a user’s device (token).
+ +Resulting from this overall privacy design, even the seizure of a chatmail server, +or the full seizure of the central Delta Chat notification proxy +would not reveal private information that Push services do not already have.
+ +Delta Chat is a free and open source decentralized messenger with free server choice, +but we want users to reliably experience “instant delivery” of messages, +like they experience from WhatsApp, Signal or Telegram apps, +without asking questions up-front that are more suited to expert users or developers.
+ +Note that Delta Chat has a small and privacy-preserving Push Notification system +that achieves “instant delivery” of messages for all chatmail servers +including a potential one you might setup yourself without our permission. +Welcome to the power of the interoperable chatmail relay network :)
+ +Yes. You can use the same profile on different devices:
+ +Controleer of beide apparaten verbonden zijn met hetzelfde (wifi)netwerk
+Ga op het eerste apparaat naar Instellingen → Tweede apparaat toevoegen, ontgrendel - indien nodig - het scherm +en wacht totdat de QR-code in beeld verschijnt.
+Installeer Delta Chat op het tweede apparaat.
+Start Delta Chat op het tweede apparaat, kies Toevoegen als tweede apparaat en scan de QR-code met het eerste apparaat.
+De overdracht zou na een paar seconden moeten beginnen en beide apparaten zouden de voortgang moeten tonen. +Wacht vervolgens tot de overdracht op beide apparaten is afgerond.
+In tegenstelling tot veel andere gespreksapps, werkt Delta Chat onafhankelijk +op beide apparaten. Hierdoor hoef je niet het ene apparaat bij de hand te hebben om het andere te laten werken.
+ +Controleer of beide apparaten verbonden zijn met hetzelfde (wifi)netwerk
+On Windows, go to Control Panel / Network and Internet +and make sure, Private Network is selected as “Network profile type” +(after transfer, you can change back to the original value)
+On iOS, make sure “System Settings / Apps / Delta Chat / Local Network” access is granted
+On macOS, enable “System Settings / Privacy & Security / Local Network / Delta Chat”
+Wellicht is een firewall actief op je apparaat, +welke problemen kan veroorzaken (met name op Windows). +Schakel de firewall op beide apparaten uit of voeg een uitzondering voor Delta Chat toe en probeer het opnieuw.
+Guest Networks may not allow devices to communicate with each other. +If possible, use a non-guest network.
+If you still have troubles using the same network, +try to open Mobile Hotspot on one device and join that Wi-Fi from the other one
+Zorg voor voldoende ruimte op het bestemmingsapparaat
+Zorg dat beide apparaten tijdens de overdracht ingeschakeld blijven en niet op zwart/in de slaapstand gaan. +Sluit Delta Chat niet af. +(We proberen om de app zo goed als mogelijk op de achtergrond te laten werken, maar systemen sluiten apps helaas wel eens eigenhandig af).
+Ben je al ingelogd op het bestemmingsapparaat? +Je kunt meerdere accounts per apparaat gebruiken - voeg dus een tweede account toe.
+Als je nog steeds problemen ervaart of je de QR-code niet kunt scannen, +volg dan onderstaande stappen omtrent handmatige overzetting
+Deze methode is vooral bedoeld voor situaties waarin ‘Tweede apparaat toevoegen’ niet lukt.
+ +At Settings → Advanced → Experimental Features +you can try out features we are working on.
+ +The features may be unstable and may be changed or removed.
+ +You can find more information +and give feedback in the Forum.
+ +We would like to improve Delta Chat with your help, +which is why Delta Chat for Android asks whether you want +to send anonymous usage statistics.
+ +You can turn it on and off at +Settings → Advanced → Send statistics to Delta Chat’s developers.
+ +When you turn it on, +weekly statistics will be automatically sent to a bot.
+ +We are interested e.g. in statistics like:
+ +We will not collect any personally identifiable information about you.
+ +Yes, but only if the email address is used exclusively by chatmail clients.
+ +It is not supported to share usage of an email address with non-chatmail apps or web-based mailers, +for the following reasons:
+ +Non-chatmail apps are largely not accomplishing automatic end-to-end email encryption for their users, +while chatmail apps and relays pervasively enforce end-to-end encryption and security standards.
+Non-chatmail apps use email servers as a long-term message archive +while chatmail clients use email servers for ephemeral instant message relay.
+Supporting the full variety of classic email setups +would require considerable development and maintenance efforts, +and complicate making chatmail-based messaging more resilient, reliable and fast.
+First off, please do not use the same classic email address also from non-chatmail classic email apps +unless you are prepared to deal with encrypted messages in the inbox, +double notifications, accidentally deleted emails or similar annoyances.
+ +You can configure a email address for chatting at New Profile → Use Other Server → Use Classic Mail as Relay.
+Note that classic email providers will generally not support Push Notifications
+and have other limitations, see Provider Overview.
+Chatmail uses the default INBOX for relay; ensure the provider setup does too.
+A chat profile using a classic email address allows to to send and receive unencrypted messages.
+These messages, and the chats they appear in, are marked with an email icon
+
.
Any well behaving email server setup will do fine +except if your users’ devices require Google/Apple Push Notifications to work properly.
+ +We generally recommend to set up a chatmail relay. +Chatmail is a community-driven project that encompasses both the setup of relays +and core Rust developments +that power chatmail clients of which Delta Chat is the most well known.
+ +Delta Chat uses a secure subset of the OpenPGP standard +to provide automatic end-to-end encryption using these protocols:
+ +Secure-Join +to exchange encryption setup information through QR-code scanning or “invite links”.
+Autocrypt is used for automatically +establishing end-to-end encryption between contacts and all members of a group chat.
+Sharing a contact to a +chat +enables receivers to use end-to-end encryption with the contact.
+Delta Chat does not query, publish or interact with any OpenPGP key servers.
+ +All messages in Delta Chat are end-to-end encrypted by default. +Since the Delta Chat Version 2 release series (July 2025) +there are no lock or similar markers on end-to-end encrypted messages, anymore.
+ +If you use default chatmail relays, +it is impossible to receive or send messages without end-to-end encryption.
+ +If you instead use a classic email server,
+you can send and receive messages with or without end-to-end encryption.
+Messages lacking end-to-end encryption are marked with an email icon
+
.
A contact profile might show a green checkmark
+
+and an “Introduced by” line.
+Every green-checkmarked contact either did a direct QR-scan with you
+or was introduced by a another green-checkmarked contact.
+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 QR-scan.
For more in-depth discussion of “guaranteed end-to-end encryption” +please see Secure-Join protocols +and specifically read about “Verified Groups”, the technical term +of what is called here “green-checkmarked” or “guaranteed end-to-end encrypted” chats.
+ +Yes.
+ +When we talk about an “end-to-end encrypted message” +we always mean a whole message is encrypted, +including all the attachments +and attachment metadata such as filenames.
+ +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.
+ +OpenPGP is not insecure by itself. +Most publicly discussed OpenPGP security problems +actually stem from bad usability or bad implementations of tools or apps (or both). +It is particularly important to distinguish between OpenPGP, the IETF encryption standard, +and GnuPG (GPG), a command line tool implementing OpenPGP. +Many public critiques of OpenPGP actually discuss GnuPG which Delta Chat has never used. +Delta Chat rather uses the OpenPGP Rust implementation rPGP, +available as an independent “pgp” package, +and security-audited in 2019 and 2024.
+ +We aim, along with other OpenPGP implementors, +to further improve security characteristics by implementing the +new IETF OpenPGP Crypto-Refresh +which was thankfully adopted in summer 2023.
+ +Yes, we are following efforts like MLS +but adopting them would mean breaking end-to-end encryption interoperability. +So it would not be a light decision to take +and there must be tangible improvements for users.
+ +Delta Chat takes a holistic “usable security” approach +and works with a wide range of activist groupings as well as +renowned researchers such as TeamUSEC +to improve actual user outcomes against security threats. +The wire protocol and standard for establishing end-to-end encryption is +only one part of “user outcomes”, +see also our answers to device-seizure +and message-metadata questions.
+ +No, Delta Chat never was vulnerable to EFAIL +because its OpenPGP implementation rPGP +uses Modification Detection Code when encrypting messages +and returns an error +if the Modification Detection Code is incorrect.
+ +Delta Chat also never was vulnerable to the “Direct Exfiltration” EFAIL attack
+because it only decrypts multipart/encrypted messages
+which contain exactly one encrypted and signed part,
+as defined by the Autocrypt Level 1 specification.
If you are sending or receiving email messages without end-to-end encryption (using a classic email server), +they are still protected from cell or cable companies who can not read or modify your email messages. +But both your and your recipient’s email providers +may read, analyze or modify your messages, including any attachments.
+ +Delta Chat by default uses strict +TLS encryption +which secures connections between your device and your email provider. +All of Delta Chat’s TLS-handling has been independently security audited. +Moreover, the connection between your and the recipient’s email provider +will typically be transport-encrypted as well. +If the involved email servers support MTA-STS +then transport encryption will be enforced between email providers +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.
+ +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.
+ +Servers can therefore only see:
+ +By default, the addresses are randomly generated.
+ +All other message, contact and group metadata resides in the end-to-end encrypted part of messages.
+ +Both for protecting against metadata-collecting servers +as well as against the threat of device seizure +we recommend to use a chatmail relay +to create chat profiles using random 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.
+ +No, not yet.
+ +The Signal messenger introduced “Sealed Sender” in 2018 +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.
+ +Even if chatmail relays +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 addresses for sealed sending +but an implementation has not been agreed as a priority yet.
+ +No, not yet.
+ +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.
+ +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 chatmail core, +which would make it available in all chatmail clients.
+ +No, not yet.
+ +Delta Chat uses the Rust OpenPGP library rPGP +which supports the latest IETF Post-Quantum-Cryptography OpenPGP draft. +We aim to add PQC support in chatmail core after the draft is finalized at the IETF +in collaboration with other OpenPGP implementers.
+ +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.
+ +No.
+ +Delta Chat generates secure OpenPGP keys according to the Autocrypt specification 1.1. +We do not recommend or offer users to perform manual key management. +We want to ensure that security audits can focus on a few proven cryptographic algorithms +instead of the full breadth of possible algorithms allowed with OpenPGP. +If you want to extract your OpenPGP key, there only is an expert method: +you need to look it up in the “keypairs” SQLite table of a profile backup tar-file.
+ +Yes, multiple times. +The Delta Chat project continuously undergoes independent security audits and analysis, +from most recent to older:
+ +2024 December, an NLNET-commissioned Evaluation of +rPGP by Radically Open Security took place. +rPGP serves as the end-to-end encryption OpenPGP engine of Delta Chat. +Two advisories were released related to the findings of this audit:
+ +The issues outlined in these advisories have been fixed and are part of Delta Chat +releases on all appstores since December 2024.
+2024 March, we received a deep security analysis from the Applied Cryptography +research group at ETH Zuerich and addressed all raised issues. +See our blog post about Hardening Guaranteed End-to-End encryption for more detailed information and the +Cryptographic Analysis of Delta Chat +research paper published afterwards.
+Sinds begin 2023 hebben we diverse beveiligings- en privacyproblemen met ‘webapps +gedeeld in een gesprek’. Deze waren allen te wijten aan fouten in de sandboxing, +vooral die van Chromium. Daarna is er een beveiligings- +onderzoek van Cure53 geweest en zijn alle problemen opgelost in versie 1.36 van de uit april 2023. +Lees hier het volledige verhaal omtrent E2E-beveiliging op het web.
+Aan het begin van 2023 heeft Cure53 de transportversleuteling van +Delta Chats netwerkverbindingen getest, evenals de e-mailserveropzet zoals +beschreven op onze site. +Meer informatie over deze test is te lezen op ons blog +of in het volledige verslag.
+In 2020 heeft Include Security Delta Chats +Rust-kern, +imap-, +smtp- en +tls-bibliotheken geanalyseerd. +Er werden geen grote problemen aangetroffen. +Wél werden er een paar redelijk belangrijke zwakheden aangetroffen, +maar geen die de meeste Delta Chat-gebruikers direct trof +omdat ze afhankelijk waren van de gebruikte omgeving. +Omwille van gebruiks- en compatibiliteitsredenen, +konden we ze niet allemaal oplossen +en besloten we om beveiligingsaanbevelingen aan getroffen gebruikers te doen. +Het volledige verslag is hier na te lezen.
+In 2019 heeft Include Security Delta Chats +PGP- en +RSA-bibliotheken geanalyseerd. +Er werden geen grote problemen aangetroffen, +maar wel twee belangrijke die nadien werden opgelost. +Ook werden enkele redelijk belangrijke en minder belangrijke aan het licht gebracht, +maar die konden in Delta Chats specifieke implementatie niet worden misbruikt. +Ondanks dat zijn enkele daarvan nadien alsnog opgelost. +Het volledige verslag is hier na te lezen.
+Some features require certain permissions, +e.g. you need to grant camera permission if you want to scan an invite QR code.
+ +See Privacy Policy for a detailed overview.
+ +Delta Chat is available for all major and some minor platforms:
+ +The official website, https://delta.chat/download shows all options in detail
+If unavailable, use the mirror at https://deltachat.github.io/deltachat-pages
+Open one of the following app stores and search for “Delta Chat”: +Google Play Store, F-Droid, Huawei App Gallery, iOS and macOS App Store, Microsoft Store
+Check the package manager of your Linux distributions
+Android APKs are also available on https://github.com/deltachat/deltachat-android/releases
+Delta Chat ontvangt geen risicokapitalen, +staat niet onder bewindvoering en ervaart geen enkele druk om winst te maken of om +gebruikers en hun vrienden door te verkopen aan adverteerders (of erger). +We maken gebruik van publieke financieringsprocessen, zoals EU- en VS-financiering, om ons doel, +het opzetten van een gedecentraliseerd en divers gesprekssysteem, te verwezenlijken, +op basis van vrije en opensource-gemeenschapsontwikkelingen.
+ +Concretely, Delta Chat developments have so far been funded from these sources, +ordered chronologically:
+ +The NEXTLEAP EU project funded the research +and implementation of verified groups and setup contact protocols +in 2017 and 2018 and also helped to integrate end-to-end Encryption +through Autocrypt.
+Open Technology Fund heeft twee subsidies toegekend. +De eerste subsidie, voor 2018/2019, ter waarde van ong. $200,000, heeft enorm geholpen om de Android-app +te verbeteren en een bètaversie van de computerclient vrij te geven. +Verder hebben we onderzoek kunnen doen naar het uiterlijk in relatie tot mensenrechten - +bekijk onze conclusie hier: Needfinding and UX report. +De tweede subsidie, voor 2019/2020, ter waarde van ong. $300,000, loopt nog en ondersteunt ons bij het +vrijgeven van de iOS-client, het overzetten van de code van de kernbibliotheek naar Rust en +het implementeren van nieuwe functies op alle platformen.
+The NLnet foundation granted in 2019/2020 EUR 46K for +completing Rust/Python bindings and instigating a Chat-bot eco-system.
+In 2021 we received further EU funding for two Next-Generation-Internet +proposals, namely for EPPD - email provider portability directory (~97K EUR) and AEAP - email address porting (~90K EUR) which resulted in better multi-profile support, improved QR-code contact and group setups and many networking improvements on all platforms.
+From End 2021 till March 2023 we received Internet Freedom funding (500K USD) from the +U.S. Bureau of Democracy, Human Rights and Labor (DRL). +This funding supported our long-running goals to make Delta Chat more usable +and compatible with a wide range of email servers world-wide, and more resilient and secure +in places often affected by internet censorship and shutdowns.
+2023-2024 we successfully completed the OTF-funded +Secure Chatmail project, +allowing us to introduce guaranteed encryption, +creating a chatmail server network +and providing “instant onboarding” in all apps released from April 2024 on.
+In 2023 and 2024 we got accepted in the Next Generation Internet (NGI) +program for our work in webxdc PUSH, +along with collaboration partners working on +webxdc evolve, +webxdc XMPP, +DeltaTouch and +DeltaTauri. +All of these projects are partially completed or to be completed in early 2025.
+Soms ontvangen we eenmalige donaties van privépersonen, waar we +uiteraard zeer dankbaar voor zijn. Zo ontvingen we in 2021 een zeer royaal bedrag op onze rekening, te weten €4000, +met als bijschrift “Ga zo door met dit goede project!”. We gebruiken dit soort bedragen om +ontmoetingen tussen ontwikkelaars te organiseren of voor ad-hoc-uitgaven die niet voorzien waren. +Ook kunnen we zo onafhankelijk blijven en lang blijven +voortbestaan.
+ + +Ook hebben verschillende experts en enthousiastelingen op vrijwillige basis bijgedragen +aan Delta Chat, en sommige doen dat nog steeds. Zij hebben geen of bijna geen +geld ontvangen. Zonder hen zou Delta Chat niet zo geweldig zijn als het vandaag +de dag is.
+Bovenstaande fiancieringen zijn opgezet door merlinux GmbH in +Freiburg (Duitsland) en daarna toegekend aan meer dan 12 vrijwilligers wereldwijd.
+ +Bekijk Delta Chats bijdraagmogelijkheden +om te zien hoe je een financiële of andere bijdrage kunt leveren.
+ + + + + \ No newline at end of file diff --git a/src/main/assets/help/paperclip.png b/src/main/assets/help/paperclip.png new file mode 100644 index 0000000000000000000000000000000000000000..01d4e15f0c25ddafc457a45aee7e920ee3ebd523 Binary files /dev/null and b/src/main/assets/help/paperclip.png differ diff --git a/src/main/assets/help/pl/help.html b/src/main/assets/help/pl/help.html new file mode 100644 index 0000000000000000000000000000000000000000..a01da3e67f674d74aa7c5716b894709ed0b0d862 --- /dev/null +++ b/src/main/assets/help/pl/help.html @@ -0,0 +1,1435 @@ + +Delta Chat is a reliable, decentralized and secure instant messaging app, +available for mobile and desktop platforms.
+ +Instant creation of private chat profiles +with secure and interoperable chatmail relays +that offer instant message delivery, and Push Notifications for iOS and Android devices.
+Pervasive multi-profile and +multi-device support on all platforms +and between different chatmail apps.
+Interactive in-chat apps for gaming and collaboration
+Audited end-to-end encryption +safe against network and server attacks.
+Free and Open Source software, both app and server side, +built on Internet Standards.
+First, note that Delta Chat is a private messenger. +There is no public discovery, you decide about your contacts.
+ +If you are face to face with your friend or family,
+tap the QR Code icon
+on the main screen.
+Ask your chat partner to scan the QR image
+with their Delta Chat app.
For a remote contact setup, +from the same screen, +click “Copy” or “Share” and send the invite link +through another private chat.
+Now wait while connection gets established.
+ +If both sides are online, they will soon see a chat +and can start messaging securely.
+If one side is offline or in bad network, +the ability to chat is delayed until connectivity is restored.
+Congratulations! +You now will automatically use end-to-end encryption with this contact. +If you add each other to groups, end-to-end encryption will be established among all members.
+ +As being a private messenger, +only friends and family you share your QR code or invite link with can write to you.
+ +Your friends may share your contact with other friends, this appears as a request.
+ +Musisz zaakceptować prośbę, zanim będziesz mógł odpowiedzieć.
+Możesz także usunąć wiadomość, jeśli nie chcesz w tej chwili z nią rozmawiać.
+Jeśli usuniesz prośbę, przyszłe wiadomości od tego kontaktu nadal będą wyświetlane jako prośba o wiadomość, więc możesz zmienić zdanie. Jeśli naprawdę nie chcesz otrzymywać wiadomości od tej osoby, rozważ zablokowanie jej.
+Attach the first contact to the chat of the second using
Attachment Button → Contact.
+You can also add a little introduction message.
The second contact will receive a card then +and can tap it to start chatting with the first contact.
+ +Tak. Images, videos, files, voice messages etc. can be sent using the
Attachment-
+or
Voice Message buttons
Ze względu na wydajność obrazy są domyślnie optymalizowane i wysyłane w mniejszym rozmiarze, ale można je wysłać jako „plik”, aby zachować oryginał.
+A profile is a name, a picture and some additional information for encrypting messages. +A profile lives on your device(s) only +and uses the server only to relay messages.
+ +Podczas pierwszej instalacji Delta Chat tworzony jest pierwszy profil.
+ +Później możesz dotknąć swojego zdjęcia profilowego w lewym górnym rogu, aby Dodać profile lub Przełączyć profile.
+ +You may want to use separate profiles for political, family or work related activities.
+ +Możesz także dowiedzieć się, jak używać tego samego profilu na wielu urządzeniach.
+ +Możesz dodać zdjęcie profilowe w swoich ustawieniach. Jeśli napiszesz do swoich kontaktów lub dodasz je za pomocą kodu QR, automatycznie zobaczą je jako Twoje zdjęcie profilowe.
+Ze względów prywatności nikt nie widzi Twojego zdjęcia profilowego, dopóki nie napiszesz do niego wiadomości.
+Yes, +you can do so under Settings → Profile → Bio. +Once you sent a message to a contact, +they will see it when they view your contact details.
+ +Użyj tych narzędzi, aby uporządkować swoje czaty i mieć wszystko na swoim miejscu:
+ +Przypięte czaty zawsze pozostają na szczycie listy czatów. Możesz ich używać, aby szybko lub tymczasowo uzyskać dostęp do swoich ulubionych czatów, aby o czymś nie zapomnieć.
+Wycisz czaty, jeśli nie chcesz otrzymywać z nich powiadomień. Wyciszone czaty pozostają na swoim miejscu i możesz też przypiąć wyciszony czat.
+Archiwizuj czaty, jeśli nie chcesz ich już widzieć na liście czatów. Zarchiwizowane czaty pozostają dostępne nad listą czatów lub poprzez wyszukiwanie.
+Gdy zarchiwizowany czat otrzyma nową wiadomość, o ile nie zostanie wyciszony, wyskoczy z archiwum i wróci na twoją listę czatów. +Wyciszone czaty pozostają zarchiwizowane do czasu ich ręcznego przywrócenia.
+Aby skorzystać z tych funkcji, przytrzymaj dłużej lub kliknij prawym przyciskiem myszy czat na liście czatów.
+ +Zapisane wiadomości to czat, którego możesz użyć, aby łatwo zapisać i znaleźć wiadomości.
+ +W dowolnym czacie naciśnij i przytrzymaj lub kliknij prawym przyciskiem myszy wiadomość i wybierz Zapisz
+Zapisane wiadomości są oznaczone symbolem
obok znacznika czasu
Później otwórz czat „Zapisane wiadomości” — zobaczysz tam zapisane wiadomości. Naciskając
, możesz wrócić do oryginalnej wiadomości w oryginalnym czacie
Na koniec możesz również użyć „Zapisz wiadomości”, aby robić osobiste notatki — otwórz czat, wpisz coś, dodaj zdjęcie lub wiadomość głosową itp.
+Ponieważ „Zapisane wiadomości” są zsynchronizowane, mogą być bardzo przydatne do przesyłania danych między urządzeniami
+Wiadomości pozostają zapisane, nawet jeśli zostaną edytowane lub usunięte — może to być przez nadawcę, czyszczenie urządzenia lub znikające wiadomości z innych czatów.
+ +You can sometimes see a green dot
+next to the avatar of a contact.
+It means they were recently seen by you in the last 10 minutes,
+e.g. because they messaged you or sent a read receipt.
So this is not a real time online status +and others will as well not always see that you are “online”.
+ +One tick
+means that the message was sent successfully to your provider.
Two ticks
+mean that at least one recipient’s device
+reported back to having received the message.
Recipients may have disabled read-receipts, +so even if you see only one tick, the message may have been read.
+The other way round, two ticks do not automatically mean +that a human has read or understood the message ;)
+Możesz edytować tekst wiadomości po wysłaniu. W tym celu naciśnij i przytrzymaj lub kliknij prawym przyciskiem myszy wiadomość i wybierz Edytuj, lub
.
Jeśli wysłałeś wiadomość przypadkowo, z tego samego menu wybierz Usuń, a następnie Usuń u wszystkich.
+Podczas gdy edytowane wiadomości będą miały słowo „Edytowana” obok znacznika czasu, usunięte wiadomości zostaną usunięte bez znacznika na czacie. Powiadomienia nie są wysyłane i nie ma limitu czasowego.
+ +Pamiętaj, że oryginalną wiadomość nadal mogą otrzymać członkowie czatu, którzy mogli już odpowiedzieć, przesłać dalej, zapisać, wykonać zrzut ekranu lub w inny sposób skopiować wiadomość.
+ +Możesz włączyć „znikające wiadomości” w ustawieniach czatu, w prawym górnym rogu okna czatu, wybierając przedział czasu od 5 minut do 1 roku.
+ +Until the setting is turned off again, +each chat member’s Delta Chat app takes care +of deleting the messages +after the selected time span. +The time span begins +when the receiver first sees the message in Delta Chat. +The messages are deleted both, +on the servers, +and in the apps itself.
+ +Pamiętaj, że na znikających wiadomościach możesz polegać tylko wtedy, gdy ufasz swoim partnerom czatu; złośliwi partnerzy czatu mogą robić zdjęcia lub w inny sposób zapisywać, kopiować lub przesyłać dalej wiadomości przed usunięciem.
+ +Apart from that, +if one chat partner uninstalls Delta Chat, +the (anyway encrypted) messages may take longer to get deleted from their server.
+ +If you are using more than one chat profile, +you can remove single ones in the top profile switcher menu (on Android and iOS), +or in the sidebar with a right click (in the Desktop app). +Chat profiles are only removed on the device where deletion was triggered. +Chat profiles on other devices will continue to fully function.
+ +If you use a single default chat profile you can simply uninstall the app. +This will still automatically trigger deletion of all associated address data on the chatmail server. +For more info, please refer to nine.testrun.org address-deletion +or the respective page from your chosen 3rd party chatmail server.
+ +Groups let several people chat together privately with equal rights.
+ +Anyone can +change the group name or avatar, +add or remove members, +set disappearing messages, +and delete their own messages from all member’s devices.
+ +Because all members have the same rights, groups work best among trusted friends and family.
+ +All group members have the same rights. +For this reason, everyone can delete any member or add new ones.
+To add or delete members, tap the group name in the chat and select the member to add or remove.
+If the member is not yet in your contact list, but face to face with you,
+from the same screen, show a QR code.
+Ask your chat partner to scan the QR image with their Delta Chat app by tapping
+
on the main screen.
For a remote member addition, +click “Copy” or “Share” and send the invite link +through another private chat to the new member.
+QR code and invite link can be used to add several members. +However, since groups are meant for trusted people, avoid sharing them publicly.
+ +Usuń siebie z listy członków lub usuń cały czat. +Jeśli później będziesz chciał ponownie dołączyć do grupy, poproś innego członka grupy, aby dodał cię do grupy.
+Alternatywnie możesz też „Wyłączyć powiadomienia” dla grupy dzięki temu otrzymasz wszystkie wiadomości i +nadal będziesz mógł pisać, ale nie będziesz już powiadamiany o żadnych nowych wiadomościach.
+You can duplicate a group to start a separate discussion +or to exclude members without them noticing.
+ +Open the group profile and tap Clone Chat (Android/iOS), +or right-click the group in the chat list (Desktop).
+Set a new name, choose an avatar, and adjust the member list if needed.
+The new group is fully independent from the original, +which continues to work as before.
+ +You can send apps to a chat - games, editors, polls and other tools. +This makes Delta Chat a truly extensible messenger.
+ +In a chat, using
Attachment Button → Apps
You can also create your own app and attach it using
Attachment Button → File
In-chat apps can not send data to the Internet, or download anything.
+An in-chat app can only exchange data within a chat, with its +copies on the devices of your chat partners. Other than that, it’s completely +isolated from the Internet.
+The privacy an in-chat app offers is the privacy of your chat - as long as you +trust the people you chat with, you can trust the in-chat app as well.
+This also means: Just like for web links, do not open apps from untrusted contacts.
+In-chat apps are zip files with .xdc extension containing html, css, and javascript code.
You can extend the Hello World example app +to get started.
+All else you need to know is written in the +Webxdc documentation.
+If you have question, you can ask others with experience +in the Delta Chat Forum.
+Powiadomienia push są wysyłane przez „usługi push” Apple i Google do urządzenia użytkownika, dzięki czemu nieaktywna aplikacja Delta Chat może pobierać wiadomości w tle i w razie potrzeby wyświetlać powiadomienia na telefonie użytkownika.
+ +Powiadomienia push działają na wszystkich włączonych serwerach chatmail
+ +Urządzeń z iOS, poprzez integrację z usługami Apple Push.
+Urządzenia z Androidem, poprzez integrację z usługą Google FCM Push, w tym na urządzeniach korzystających z microG zamiast autorskiego kodu Google w telefonie.
+Tak, Delta Chat automatycznie korzysta z powiadomień push dla profili chatmail +. I nie, w telefonach Apple nie ma alternatywy umożliwiającej natychmiastowe dostarczanie wiadomości, ponieważ urządzenia Apple nie pozwalają Delta Chat na pobieranie danych w tle. Powiadomienia push są automatycznie aktywowane dla użytkowników iOS, ponieważ system prywatności powiadomień Delta Chat nie udostępnia Apple danych, których jeszcze nie posiada.
+ +If a “Push Service” is available, Delta Chat enables Push Notifications +to achieve instant message delivery for all chatmail users.
+ +W ustawieniach „Powiadomień” Delta Chat dla „Natychmiastowej dostawy” możesz zmienić następujące ustawienia wpływające na wszystkie profile czatu:
+ +Wymuś połączenie w tle: Jest to opcja awaryjna, jeśli poprzednie opcje nie są dostępne lub nie zapewniają „natychmiastowej dostawy”. Włączenie tej opcji powoduje stałe powiadomienie na twoim telefonie, które czasami może zostać „minifikowane” w przypadku najnowszych telefonów z Androidem.
+ +Obie opcje „Połączenia w tle” są energooszczędne i można je bezpiecznie wypróbować, jeśli wiadomości docierają do ciebie z dużym opóźnieniem.
+ +Delta Chat Push Notification support avoids leakage of private information. +It does not leak profile data, IP address or message content (not even encrypted) +to any system involved in the delivery of Push Notifications.
+ +Oto jak aplikacje Delta Chat realizują dostarczanie powiadomień push:
+ +Aplikacja Delta Chat uzyskuje lokalnie „token urządzenia”, szyfruje i przechowuje go na serwerze chatmail.
+When a chatmail server receives a message for a Delta Chat user +it forwards the encrypted device token to the central Delta Chat notification proxy.
+The central Delta Chat notification proxy decrypts the device token +and forwards it to the respective Push service (Apple, Google, etc.), +without ever knowing the IP or profile data of Delta Chat users.
+The central Push Service (Apple, Google, etc.) +wakes up the Delta Chat app on your device +to check for new messages in the background. +It does not know about the profile data of the device it wakes up. +The central Apple/Google Push services never see any profile data (sender or receiver) +and also never see any message content (also not in encrypted forms).
+Centralny serwer proxy powiadomień Delta Chat jest mały i w pełni zaimplementowany w Rust i zapomina o tokenach urządzeń zaraz po ich przetworzeniu przez Apple/Google/itp, zwykle w ciągu kilku milisekund.
+ +Note that the device token is encrypted between apps and notification proxy +but it is not signed. +The notification proxy thus never sees profile data, IP-addresses or +any cryptographic identity information associated with a user’s device (token).
+ +W wyniku tego ogólnego projektu ochrony prywatności nawet przejęcie serwera chatmail lub pełne przejęcie centralnego serwera proxy powiadomień Delta Chat nie spowodowałoby ujawnienia prywatnych informacji, których usługi Push jeszcze nie posiadają.
+ +Delta Chat to darmowy i otwartoźródłowy zdecentralizowany komunikator z możliwością wyboru serwera, ale chcemy, aby użytkownicy mogli niezawodnie doświadczać „natychmiastowego dostarczania” wiadomości, tak jak w przypadku aplikacji Whatsapp, Signal lub Telegram, bez zadawania z góry pytań, które są bardziej odpowiednie dla doświadczonych użytkowników lub programistów.
+ +Note that Delta Chat has a small and privacy-preserving Push Notification system +that achieves “instant delivery” of messages for all chatmail servers +including a potential one you might setup yourself without our permission. +Welcome to the power of the interoperable chatmail relay network :)
+ +Tak. Możesz używać tego samego profilu na różnych urządzeniach:
+ +Upewnij się, że oba urządzenia są połączone z tego samego Wi-Fi lub sieci
+Na pierwszym urządzeniu przejdź do Ustawienia → Dodaj kolejne urządzenie, w razie potrzeby odblokuj ekran i poczekaj chwilę, aż pojawi się kod QR
+Na drugim urządzeniu zainstaluj Delta Chat
+Na drugim urządzeniu uruchom Delta Chat, wybierz Dodaj jako kolejne urządzenie i zeskanuj kod QR z pierwszego urządzenia
+Przenoszenie powinno rozpocząć się po kilku sekundach, a podczas przenoszenia oba urządzenia będą pokazywać postęp. Poczekaj, aż zakończy się na obu urządzeniach.
+ +W przeciwieństwie do wielu innych komunikatorów, po udanym przenoszeniu oba urządzenia są całkowicie niezależne. Jedno urządzenie nie jest potrzebne do działania drugiego.
+ +Sprawdź dokładnie, czy oba urządzenia są w tym samym Wi-Fi lub tej samej sieci
+Na Windowsie, przejdź do Panel sterowania / Sieć i internet i upewnij się, że Sieć prywatna jest wybrana jako “Typ profilu sieci” +(po przeniesieniu możesz wrócić do pierwotnej wartości)
+W systemie iOS upewnij się, że jest przydzielony dostęp do opcji „Ustawienia » Aplikacje » Delta Chat » Sieć lokalna”
+W systemie macOS włącz „Preferencje systemowe » Ochrona i prywatność » Sieć lokalna » Delta Chat”
+Twój system może mieć „zaporę ogniową”, o której wiadomo, że powoduje problemy (szczególnie w systemie Windows). +Wyłącz zaporę dla Delta Chat po obu stronach i spróbuj ponownie
+Sieci dla gości mogą nie pozwalać urządzeniom na komunikację między sobą. Jeśli to możliwe, korzystaj z sieci innej niż gość.
+Jeśli nadal masz problemy z korzystaniem z tej samej sieci, spróbuj otworzyć Hotspot na jednym urządzeniu i połączyć się z tą siecią Wi-Fi z drugiego urządzenia
+Upewnij się, że na urządzeniu docelowym jest wystarczająca ilość miejsca
+Jeśli przenoszenie się rozpoczęło, upewnij się, że urządzenia pozostają aktywne i nie zasypiają. Nie wychodź z Delta Chat. (dokładamy wszelkich starań, aby aplikacja działała w tle, ale systemy mają tendencję do ubijania aplikacji, niestety)
+Delta Chat jest już zalogowany na urządzeniu docelowym? Możesz używać wielu kont na urządzeniu, po prostu dodaj kolejne konto
+Jeśli nadal masz problemy lub nie możesz zeskanować kodu QR, wypróbuj ręczne przenoszenie opisane poniżej
+Ta metoda jest zalecana tylko wtedy, gdy opisana powyżej opcja „Dodaj kolejne urządzenie” nie działa.
+ +At Settings → Advanced → Experimental Features +you can try out features we are working on.
+ +The features may be unstable and may be changed or removed.
+ +You can find more information +and give feedback in the Forum.
+ +We would like to improve Delta Chat with your help, +which is why Delta Chat for Android asks whether you want +to send anonymous usage statistics.
+ +You can turn it on and off at +Settings → Advanced → Send statistics to Delta Chat’s developers.
+ +When you turn it on, +weekly statistics will be automatically sent to a bot.
+ +We are interested e.g. in statistics like:
+ +We will not collect any personally identifiable information about you.
+ +Yes, but only if the email address is used exclusively by chatmail clients.
+ +It is not supported to share usage of an email address with non-chatmail apps or web-based mailers, +for the following reasons:
+ +Non-chatmail apps are largely not accomplishing automatic end-to-end email encryption for their users, +while chatmail apps and relays pervasively enforce end-to-end encryption and security standards.
+Non-chatmail apps use email servers as a long-term message archive +while chatmail clients use email servers for ephemeral instant message relay.
+Supporting the full variety of classic email setups +would require considerable development and maintenance efforts, +and complicate making chatmail-based messaging more resilient, reliable and fast.
+First off, please do not use the same classic email address also from non-chatmail classic email apps +unless you are prepared to deal with encrypted messages in the inbox, +double notifications, accidentally deleted emails or similar annoyances.
+ +You can configure a email address for chatting at New Profile → Use Other Server → Use Classic Mail as Relay.
+Note that classic email providers will generally not support Push Notifications
+and have other limitations, see Provider Overview.
+Chatmail uses the default INBOX for relay; ensure the provider setup does too.
+A chat profile using a classic email address allows to to send and receive unencrypted messages.
+These messages, and the chats they appear in, are marked with an email icon
+
.
Any well behaving email server setup will do fine +except if your users’ devices require Google/Apple Push Notifications to work properly.
+ +We generally recommend to set up a chatmail relay. +Chatmail is a community-driven project that encompasses both the setup of relays +and core Rust developments +that power chatmail clients of which Delta Chat is the most well known.
+ +Delta Chat wykorzystuje bezpieczny podzbiór standardu OpenPGP do automatycznego szyfrowania typu end-to-end za pomocą następujących protokołów:
+ +Secure-Join do wymiany informacji o konfiguracji szyfrowania poprzez skanowanie kodów QR lub „linki zaproszeń”.
+Autocrypt służy do automatycznego ustanawiania szyfrowania typu end-to-end między kontaktami a wszystkimi członkami czatu grupowego.
+Udostępnienie kontaktu na czacie umożliwia odbiorcom korzystanie z szyfrowania typu end-to-end z tym kontaktem.
+Delta Chat nie wysyła zapytań, nie publikuje ani nie wchodzi w interakcję z żadnymi serwerami kluczy OpenPGP.
+ +Wszystkie wiadomości w Delta Chat są domyślnie szyfrowane metodą end-to-end. 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.
+ +Jeśli korzystasz z domyślnych przekaźników chatmail, odbieranie ani wysyłanie wiadomości bez szyfrowania end-to-end jest niemożliwe.
+ +If you instead use a classic email server,
+you can send and receive messages with or without end-to-end encryption.
+Messages lacking end-to-end encryption are marked with an email icon
+
.
Profil kontaktu może wyświetlać zielony znacznik wyboru
i wiersz „Zweryfikowano przez…”. Każdy kontakt oznaczony zielonym znacznikiem albo wykonał z tobą bezpośrednie skanowanie QR, 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ś skanowanie QR.
Aby uzyskać bardziej szczegółowe omówienie „gwarantowanego szyfrowania typu end-to-end”, zobacz Protokoły Secure-Join, 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.
+ +Tak.
+ +Kiedy mówimy o „wiadomości zaszyfrowanej metodą end-to-end”, zawsze mamy na myśli, że zaszyfrowana jest cała wiadomość, łącznie ze wszystkimi załącznikami i metadanymi załączników, takimi jak nazwy plików.
+ +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.
+ +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 rPGP, dostępnej jako niezależny pakiet „pgp” i poddanej audytowi bezpieczeństwa w 2019 i 2024 roku.
+ +Naszym celem, wraz z innymi wdrażającymi OpenPGP, jest dalsza poprawa parametrów bezpieczeństwa poprzez wdrożenie nowego IETF OpenPGP Crypto-Refresh, który na szczęście został przyjęty latem 2023 roku.
+ +Yes, we are following efforts like MLS +but adopting them would mean breaking end-to-end encryption interoperability. +So it would not be a light decision to take +and there must be tangible improvements for users.
+ +Delta Chat przyjmuje holistyczne podejście do „użytecznego bezpieczeństwa” i współpracuje z szeroką gamą grup aktywistów, a także renomowanymi badaczami, takimi jak TeamUSEC, aby poprawić rzeczywiste wyniki użytkowników przed zagrożeniami bezpieczeństwa. Protokół przewodowy i standard ustanawiania szyfrowania end-to-end to tylko jedna część „wyników użytkownika”. Zobacz także nasze odpowiedzi na pytania dotyczące przejęcia urządzenia i metadanych wiadomości.
+ +Nie, Delta Chat nigdy nie był podatny na atak EFAIL, ponieważ jego implementacja OpenPGP rPGP używa kodu wykrywania modyfikacji podczas szyfrowania wiadomości i zwraca błąd, jeśli kod wykrywania modyfikacji jest nieprawidłowy.
+ +Delta Chat również nigdy nie był podatny na atak EFAIL „Direct Exfiltration”, ponieważ odszyfrowuje jedynie wiadomości multipart/encrypted, które zawierają dokładnie jedną zaszyfrowaną i podpisaną część, zgodnie ze specyfikacją Autocrypt Level 1.
If you are sending or receiving email messages without end-to-end encryption (using a classic email server), +they are still protected from cell or cable companies who can not read or modify your email messages. +But both your and your recipient’s email providers +may read, analyze or modify your messages, including any attachments.
+ +Delta Chat by default uses strict +TLS encryption +which secures connections between your device and your email provider. +All of Delta Chat’s TLS-handling has been independently security audited. +Moreover, the connection between your and the recipient’s email provider +will typically be transport-encrypted as well. +If the involved email servers support MTA-STS +then transport encryption will be enforced between email providers +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.
+ +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.
+ +Servers can therefore only see:
+ +By default, the addresses are randomly generated.
+ +Wszystkie pozostałe metadane dotyczące wiadomości, kontaktów i grup znajdują się w zaszyfrowanej metodą end-to-end części wiadomości.
+ +Both for protecting against metadata-collecting servers +as well as against the threat of device seizure +we recommend to use a chatmail relay +to create chat profiles using random 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.
+ +Nie, jeszcze nie.
+ +Komunikator Signal wprowadził funkcję „Sealed Sender” w 2018 roku, aby infrastruktura serwerowa nie wiedziała, kto wysyła wiadomość do grupy odbiorców. Jest to szczególnie ważne, ponieważ serwer Signal zna numer telefonu komórkowego każdego konta, który zazwyczaj jest powiązany z identyfikatorem paszportu.
+ +Even if chatmail relays +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 addresses for sealed sending +but an implementation has not been agreed as a priority yet.
+ +Nie, jeszcze nie.
+ +Delta Chat obecnie nie obsługuje mechanizmu Perfect Forward Secrecy (PFS). Oznacza to, że jeśli twój prywatny klucz deszyfrujący zostanie ujawniony, a ktoś zdobędzie twoje wcześniejsze wiadomości w trakcie transmisji, będzie mógł je odszyfrować i odczytać za pomocą ujawnionego klucza deszyfrującego. Należy pamiętać, że mechanizm Forward Secrecy zwiększa bezpieczeństwo tylko w przypadku usuwania wiadomości. W przeciwnym razie osoba, która uzyska twoje klucze deszyfrujące, zazwyczaj będzie mogła uzyskać dostęp do wszystkich nieusuniętych wiadomości i nie będzie musiała odszyfrowywać żadnych wcześniej zebranych wiadomości.
+ +Opracowaliśmy metodę Forward Secrecy, która przeszła wstępną analizę niektórych kryptografów i ekspertów ds. wdrożeń, ale oczekuje na bardziej formalne opracowanie, które potwierdzi jej niezawodne działanie w federacyjnym przesyłaniu wiadomości i w przypadku korzystania z wielu urządzeń, zanim zostanie zaimplementowana w rdzeniu chatmail, co uczyniłoby ją dostępną we wszystkich klientach chatmail.
+ +Nie, jeszcze nie.
+ +Delta Chat korzysta z biblioteki Rust OpenPGP rPGP, która obsługuje najnowszy projekt OpenPGP IETF Post-Quantum-Cryptography. Planujemy dodać obsługę PQC do rdzenia chatmail po sfinalizowaniu projektu w IETF we współpracy z innymi implementatorami OpenPGP.
+ +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.
+ +Nie.
+ +Delta Chat generates secure OpenPGP keys according to the Autocrypt specification 1.1. +We do not recommend or offer users to perform manual key management. +We want to ensure that security audits can focus on a few proven cryptographic algorithms +instead of the full breadth of possible algorithms allowed with OpenPGP. +If you want to extract your OpenPGP key, there only is an expert method: +you need to look it up in the “keypairs” SQLite table of a profile backup tar-file.
+ +Tak, wielokrotnie. +Projekt Delta Chat stale przechodzi niezależne audyty bezpieczeństwa i analizy, +od najnowszych do najstarszych:
+ +W grudniu 2024 r. NLNET wykonała ocenę rPGP zleconą przez Radically Open Security. rPGP służy jako kompleksowy silnik szyfrowania OpenPGP w Delta Chat. Wydano dwa ostrzeżenia związane z wynikami tego audytu:
+ +Problemy opisane w tych ostrzeżeniach zostały naprawione i są częścią wydań Delta Chat we wszystkich sklepach z aplikacjami od grudnia 2024 r.
+ +W marcu 2024 r. otrzymaliśmy dogłębną analizę bezpieczeństwa od grupy badawczej ds. kryptografii stosowanej w ETH Zuerich i zajęliśmy się wszystkimi poruszonymi kwestiami. Więcej szczegółowych informacji można znaleźć na naszym blogu na temat szyfrowania typu End-to-End z gwarancją Hardening oraz opublikowanym później artykule badawczym Cryptographic Analysis of Delta Chat.
+W kwietniu 2023 r. naprawiliśmy problemy z bezpieczeństwem i prywatnością w funkcji „aplikacje internetowe udostępniane na czacie”, związane z awariami piaskownicy, szczególnie w przypadku Chromium. Następnie przeprowadziliśmy niezależny audyt bezpieczeństwa od Cure53 i wszystkie wykryte problemy zostały naprawione w aplikacji z serii 1.36 wydanej w kwietniu 2023 r. Pełną historię bezpieczeństwa end-to-end w sieci można znaleźć tutaj.
+W marcu 2023 r. firma Cure53 przeanalizowała zarówno szyfrowanie transportu połączeń sieciowych Delta Chat, jak i powtarzalną konfigurację serwera pocztowego zgodnie z zaleceniami na tej stronie. Możesz przeczytać więcej o audycie na naszym blogu lub przeczytać pełny raport tutaj.
+W 2020 r. firma Include Security przeanalizowała biblioteki Rust core, IMAP, SMTP i TLS Delta Chat. Nie znalazła żadnych problemów krytycznych ani poważnych. W raporcie zwrócono uwagę na kilka słabych punktów o średniej wadze – same w sobie nie stanowią zagrożenia dla użytkowników Delta Chat, ponieważ zależą od środowiska, w którym używany jest Delta Chat. Ze względu na użyteczność i kompatybilność nie możemy złagodzić wszystkich z nich i zdecydowaliśmy się przedstawić zalecenia dotyczące bezpieczeństwa zagrożonym użytkownikom. Pełny raport można przeczytać tutaj.
+W 2019 r. firma Include Security przeanalizowała biblioteki PGP i RSA Delta Chat. Nie znaleziono żadnych krytycznych problemów, ale dwa poważne problemy, które później naprawiliśmy. Ujawniła również jeden problem o średniej wadze i kilka mniej poważnych, ale nie było możliwości wykorzystania tych luk w implementacji Delta Chat. Niektóre z nich jednak naprawiliśmy od czasu zakończenia kontroli. Pełny raport można przeczytać tutaj.
+Some features require certain permissions, +e.g. you need to grant camera permission if you want to scan an invite QR code.
+ +See Privacy Policy for a detailed overview.
+ +Delta Chat jest dostępny na wszystkich głównych i niektórych mniejszych platformach:
+ +Oficjalna strona internetowa https://delta.chat/download pokazuje wszystkie opcje szczegółowo
+Jeśli nie jest dostępna, użyj kopii strony pod adresem https://deltachat.github.io/deltachat-pages
+Open one of the following app stores and search for “Delta Chat”: +Google Play Store, F-Droid, Huawei App Gallery, iOS and macOS App Store, Microsoft Store
+Sprawdź menedżera pakietów swoich dystrybucji Linuksa
+Aplikacje na Androida są również dostępne na https://github.com/deltachat/deltachat-android/releases
+Delta Chat nie otrzymuje żadnego kapitału wysokiego ryzyka, nie jest zadłużony i nie jest pod presją generowania ogromnych zysków lub sprzedawania reklamodawcom użytkowników i ich przyjaciół oraz rodziny (lub gorzej). +Raczej korzystamy z publicznych źródeł finansowania, jak dotąd pochodzących z UE i USA, aby wspomóc nasze wysiłki w inicjowaniu zdecentralizowanego i zróżnicowanego ekosystemu komunikatora, opartego na rozwoju społeczności Free i Open-Source.
+ +Konkretnie, rozwój Delta Chat był dotychczas finansowany z tych źródeł, uporządkowanych chronologicznie:
+ +Unijny projekt NEXTLEAP sfinansował badania i wdrożenie zweryfikowanych grup i ustawień protokołów kontaktowych w latach 2017 i 2018, a także pomógł zintegrować szyfrowanie end-to-end poprzez Autocrypt.
+Open Technology Fund przyznał nam pierwszy grant w 2018/2019 (~200 000 $), dzięki któremu znacznie ulepszyliśmy aplikację na Androida i wydaliśmy pierwszą wersję beta aplikacji na komputery stacjonarne, a także ugruntował rozwój naszych funkcji w badaniach UX w kontekście praw człowieka, zobacz nasz końcowy raport Needfinding and UX. +Druga dotacja w 2019/2020 (~300 000 4) pomogła nam wydać wersje Delta/iOS, przekonwertować naszą podstawową bibliotekę na Rust i zapewnić nowe funkcje dla wszystkich platform.
+Fundacja NLnet przekazała w latach 2019/2020 kwotę 46 tys. EUR na wykonanie wiązań Rust/Python i uruchomienie ekosystemu Chat-bot.
+In 2021 we received further EU funding for two Next-Generation-Internet +proposals, namely for EPPD - email provider portability directory (~97K EUR) and AEAP - email address porting (~90K EUR) which resulted in better multi-profile support, improved QR-code contact and group setups and many networking improvements on all platforms.
+From End 2021 till March 2023 we received Internet Freedom funding (500K USD) from the +U.S. Bureau of Democracy, Human Rights and Labor (DRL). +This funding supported our long-running goals to make Delta Chat more usable +and compatible with a wide range of email servers world-wide, and more resilient and secure +in places often affected by internet censorship and shutdowns.
+W latach 2023-2024 pomyślnie ukończyliśmy finansowany przez OTF projekt Secure Chatmail, co pozwoliło nam wprowadzić gwarantowane szyfrowanie, stworzyć sieć serwerów chatmail i zapewnić „natychmiastowe wdrażanie” we wszystkich aplikacjach wydanych od kwietnia 2024 r.
+W latach 2023 i 2024 zostaliśmy przyjęci do programu Next Generation Internet (NGI) za naszą pracę w webxdc PUSH, wraz z partnerami współpracującymi pracującymi nad webxdc evolve, webxdc XMPP, DeltaTouch i DeltaTauri. Wszystkie te projekty są częściowo ukończone lub zostaną ukończone na początku 2025 r.
+Czasami otrzymujemy jednorazowe darowizny od osób prywatnych. Na przykład w 2021 roku pewna hojna osoba przekazała nam 4K EUR w formie przelewu bankowego tytułem “kontynuujcie dobry rozwój!”. 💜 Takie pieniądze przeznaczamy na finansowanie spotkań rozwojowych lub na doraźne wydatki, których nie da się łatwo przewidzieć lub zrefundować z publicznych dotacji. Otrzymywanie większej ilości darowizn pomaga nam również stać się bardziej niezależnymi i długoterminowo rentownymi jako społeczność współpracowników.
+ + +Wreszcie, ale zdecydowanie nie najmniej ważne, kilku ekspertów i entuzjastów pro-bono wniosło wkład i przyczyniło się do rozwoju Delta Chat bez otrzymywania pieniędzy lub tylko niewielkich kwot. Bez nich Delta Chat nie byłby tam, gdzie jest dzisiaj, nawet w pobliżu.
+Wspomniane powyżej finansowanie pieniężne jest w większości organizowane przez merlinux GmbH we Freiburgu (Niemcy) i jest dystrybuowane do kilkunastu podmiotów na całym świecie.
+ +Zapoznaj się z kanałami wpłat dla Delta Chat, aby uzyskać informacje o możliwościach wpłat zarówno pieniężnych, jak i innych.
+ + + + + \ No newline at end of file diff --git a/src/main/assets/help/pt/help.html b/src/main/assets/help/pt/help.html new file mode 100644 index 0000000000000000000000000000000000000000..0333d189f98cfe2e199c192c380b2113023a68ad --- /dev/null +++ b/src/main/assets/help/pt/help.html @@ -0,0 +1,1664 @@ + +Delta Chat is a reliable, decentralized and secure instant messaging app, +available for mobile and desktop platforms.
+ +Instant creation of private chat profiles +with secure and interoperable chatmail relays +that offer instant message delivery, and Push Notifications for iOS and Android devices.
+Pervasive multi-profile and +multi-device support on all platforms +and between different chatmail apps.
+Interactive in-chat apps for gaming and collaboration
+Audited end-to-end encryption +safe against network and server attacks.
+Free and Open Source software, both app and server side, +built on Internet Standards.
+First, note that Delta Chat is a private messenger. +There is no public discovery, you decide about your contacts.
+ +If you are face to face with your friend or family,
+tap the QR Code icon
+on the main screen.
+Ask your chat partner to scan the QR image
+with their Delta Chat app.
For a remote contact setup, +from the same screen, +click “Copy” or “Share” and send the invite link +through another private chat.
+Now wait while connection gets established.
+ +If both sides are online, they will soon see a chat +and can start messaging securely.
+If one side is offline or in bad network, +the ability to chat is delayed until connectivity is restored.
+Congratulations! +You now will automatically use end-to-end encryption with this contact. +If you add each other to groups, end-to-end encryption will be established among all members.
+ +As being a private messenger, +only friends and family you share your QR code or invite link with can write to you.
+ +Your friends may share your contact with other friends, this appears as a request.
+ +You need to accept the request before you can reply.
+You can also delete it if you don’t want to chat with them for now.
+If you delete a request, future messages from that contact will still appear +as message request, so you can change your mind. If you really don’t want to +receive messages from this person, consider blocking them.
+Attach the first contact to the chat of the second using
Attachment Button → Contact.
+You can also add a little introduction message.
The second contact will receive a card then +and can tap it to start chatting with the first contact.
+ +Sim. Images, videos, files, voice messages etc. can be sent using the
Attachment-
+or
Voice Message buttons
For performance, images are optimized and sent at a smaller size by default, but you can send it as a “file” to preserve the original.
+A profile is a name, a picture and some additional information for encrypting messages. +A profile lives on your device(s) only +and uses the server only to relay messages.
+ +On first installation of Delta Chat a first profile is created.
+ +Later, you can tap your profile image in the upper left corner to Add Profiles +or to Switch Profiles.
+ +You may want to use separate profiles for political, family or work related activities.
+ +You may also wish to learn how to use the same profile on multiple devices.
+ +Você pode adicionar uma imagem de perfil nas suas configurações. Se você escrever aos seus contatos ou adicioná-los via código QR, eles automaticamente verão a imagem do seu perfil.
+Por motivos de privacidade, ninguém pode ver a imagem do seu ṕerfil até que você escreva para as pessoas.
+Yes, +you can do so under Settings → Profile → Bio. +Once you sent a message to a contact, +they will see it when they view your contact details.
+ +Use these tools to organize your chats and keep everything in its place:
+ +Pinned chats always stay atop of the chat list. You can use them to access your most loved chats quickly or temporarily to not forget about things.
+Mute chats if you do not want to get notifications for them. Muted chats stay in place and you can also pin a muted chat.
+Archive chats if you do not want to see them in your chat list any longer. +Archived chats remain accessible above the chat list or via search.
+When an archived chat gets a new message, unless muted, it will pop out of the archive and back into your chat list. +Muted chats stay archived until you unarchive them manually.
+To use the functions, long tap or right click a chat in the chat list.
+ +Saved Messages is a chat that you can use to easily remember and find messages.
+ +In any chat, long tap or right click a message and select Save
+Saved messages are marked by the symbol
+
+next to the timestamp
Later, open the “Saved Messages” chat - and you will see the saved messages there.
+By tapping
,
+you can go back to the original message in the original chat
Finally, you can also use “Save Messages” to take personal notes - open the chat, type something, add a photo or a voice message etc.
+As “Saved Message” are synced, they can become very handy for transferring data between devices
+Messages stay saved even if they are edited or deleted - +may it be by sender, by device cleanup or by disappearing messages of other chats.
+ +You can sometimes see a green dot
+next to the avatar of a contact.
+It means they were recently seen by you in the last 10 minutes,
+e.g. because they messaged you or sent a read receipt.
So this is not a real time online status +and others will as well not always see that you are “online”.
+ +One tick
+means that the message was sent successfully to your provider.
Two ticks
+mean that at least one recipient’s device
+reported back to having received the message.
Recipients may have disabled read-receipts, +so even if you see only one tick, the message may have been read.
+The other way round, two ticks do not automatically mean +that a human has read or understood the message ;)
+You can edit the text of your messages after sending.
+For that, long tap or right click the message and select Edit
+or
.
If you have sent a message accidentally, +from the same menu, select Delete and then Delete for Everyone.
+While edited messages will have the word “Edited” next to the timestamp, +deleted messages will be removed without a marker in the chat. +Notifications are not sent and there is no time limit.
+ +Note, that the original message may still be received by chat members +who could have already replied, forwarded, saved, screenshotted or otherwise copied the message.
+ +You can turn on “disappearing messages” +in the settings of a chat, +at the top right of the chat window, +by selecting a time span +between 5 minutes and 1 year.
+ +Until the setting is turned off again, +each chat member’s Delta Chat app takes care +of deleting the messages +after the selected time span. +The time span begins +when the receiver first sees the message in Delta Chat. +The messages are deleted both, +on the servers, +and in the apps itself.
+ +Note that you can rely on disappearing messages +only as long as you trust your chat partners; +malicious chat partners can take photos, +or otherwise save, copy or forward messages before deletion.
+ +Apart from that, +if one chat partner uninstalls Delta Chat, +the (anyway encrypted) messages may take longer to get deleted from their server.
+ +If you are using more than one chat profile, +you can remove single ones in the top profile switcher menu (on Android and iOS), +or in the sidebar with a right click (in the Desktop app). +Chat profiles are only removed on the device where deletion was triggered. +Chat profiles on other devices will continue to fully function.
+ +If you use a single default chat profile you can simply uninstall the app. +This will still automatically trigger deletion of all associated address data on the chatmail server. +For more info, please refer to nine.testrun.org address-deletion +or the respective page from your chosen 3rd party chatmail server.
+ +Groups let several people chat together privately with equal rights.
+ +Anyone can +change the group name or avatar, +add or remove members, +set disappearing messages, +and delete their own messages from all member’s devices.
+ +Because all members have the same rights, groups work best among trusted friends and family.
+ +All group members have the same rights. +For this reason, everyone can delete any member or add new ones.
+To add or delete members, tap the group name in the chat and select the member to add or remove.
+If the member is not yet in your contact list, but face to face with you,
+from the same screen, show a QR code.
+Ask your chat partner to scan the QR image with their Delta Chat app by tapping
+
on the main screen.
For a remote member addition, +click “Copy” or “Share” and send the invite link +through another private chat to the new member.
+QR code and invite link can be used to add several members. +However, since groups are meant for trusted people, avoid sharing them publicly.
+ +Ou você se exclui do grupo ou apaga a conversa inteira do grupo. +Se você quiser entrar mais tarde no grupo novamente, peça a outra pessoa do grupo para adicioná-la novamente.
+Uma alternativa é “silenciar” um grupo. Fazendo isso, você receberá todas as mensagens e ainda poderá escrever, mas não será receberá mais notificações d enovas mensagens.
+You can duplicate a group to start a separate discussion +or to exclude members without them noticing.
+ +Open the group profile and tap Clone Chat (Android/iOS), +or right-click the group in the chat list (Desktop).
+Set a new name, choose an avatar, and adjust the member list if needed.
+The new group is fully independent from the original, +which continues to work as before.
+ +You can send apps to a chat - games, editors, polls and other tools. +This makes Delta Chat a truly extensible messenger.
+ +In a chat, using
Attachment Button → Apps
You can also create your own app and attach it using
Attachment Button → File
In-chat apps can not send data to the Internet, or download anything.
+An in-chat app can only exchange data within a chat, with its +copies on the devices of your chat partners. Other than that, it’s completely +isolated from the Internet.
+The privacy an in-chat app offers is the privacy of your chat - as long as you +trust the people you chat with, you can trust the in-chat app as well.
+This also means: Just like for web links, do not open apps from untrusted contacts.
+In-chat apps are zip files with .xdc extension containing html, css, and javascript code.
You can extend the Hello World example app +to get started.
+All else you need to know is written in the +Webxdc documentation.
+If you have question, you can ask others with experience +in the Delta Chat Forum.
+Push Notifications are sent by Apple and Google “Push services” to a user’s device +so that an inactive Delta Chat app can fetch messages in the background +and show notifications on a user’s phone if needed.
+ +Push Notifications work with all chatmail servers on
+ +iOS devices, by integrating with Apple Push services.
+Android devices, by integrating with the Google FCM Push service, +including on devices that use microG +instead of proprietary Google code on the phone.
+Yes, Delta Chat automatically uses Push Notifications for chatmail profiles. +And no, there is no alternative on Apple’s phones to achieve instant message delivery +because Apple devices do not allow Delta Chat to fetch data in the background. +Push notifications are automatically activated for iOS users because +Delta Chat’s privacy-preserving Push Notification system +does not expose data to Apple that it doesn’t already have.
+ +If a “Push Service” is available, Delta Chat enables Push Notifications +to achieve instant message delivery for all chatmail users.
+ +In the Delta Chat “Notifications” settings for “Instant delivery” +you can change the following settings effecting all chat profiles:
+ +Use Background Connection: If you are not using a Push service, +you may disable “battery optimizations” for Delta Chat, +allowing it to fetch messages in the background. +However, there could be delays from minutes to hours. +Some Android vendors even restrict apps completely +(see dontkillmyapp.com) +and Delta Chat might not show incoming messages +until you manually open the app again.
+Force Background Connection: This is the fallback option +if the previous options are not available or do not achieve “instant delivery”. +Enabling it causes a permanent notification on your phone +which may sometimes be “minified” with recent Android phones.
+Both “Background Connection” options are energy-efficient and +safe to try if you experience messages arrive only with long delays.
+ +Delta Chat Push Notification support avoids leakage of private information. +It does not leak profile data, IP address or message content (not even encrypted) +to any system involved in the delivery of Push Notifications.
+ +Here is how Delta Chat apps perform Push Notification delivery:
+ +A Delta Chat app obtains a “device token” locally, encrypts it and stores it +on the chatmail server.
+When a chatmail server receives a message for a Delta Chat user +it forwards the encrypted device token to the central Delta Chat notification proxy.
+The central Delta Chat notification proxy decrypts the device token +and forwards it to the respective Push service (Apple, Google, etc.), +without ever knowing the IP or profile data of Delta Chat users.
+The central Push Service (Apple, Google, etc.) +wakes up the Delta Chat app on your device +to check for new messages in the background. +It does not know about the profile data of the device it wakes up. +The central Apple/Google Push services never see any profile data (sender or receiver) +and also never see any message content (also not in encrypted forms).
+The central Delta Chat notification proxy is small and fully implemented in Rust +and forgets about device-tokens as soon as Apple/Google/etc processed them, +usually in a matter of milliseconds.
+ +Note that the device token is encrypted between apps and notification proxy +but it is not signed. +The notification proxy thus never sees profile data, IP-addresses or +any cryptographic identity information associated with a user’s device (token).
+ +Resulting from this overall privacy design, even the seizure of a chatmail server, +or the full seizure of the central Delta Chat notification proxy +would not reveal private information that Push services do not already have.
+ +Delta Chat is a free and open source decentralized messenger with free server choice, +but we want users to reliably experience “instant delivery” of messages, +like they experience from WhatsApp, Signal or Telegram apps, +without asking questions up-front that are more suited to expert users or developers.
+ +Note that Delta Chat has a small and privacy-preserving Push Notification system +that achieves “instant delivery” of messages for all chatmail servers +including a potential one you might setup yourself without our permission. +Welcome to the power of the interoperable chatmail relay network :)
+ +Sim. You can use the same profile on different devices:
+ +Make sure both devices are on the same Wi-Fi or network
+On the first device, go to Settings → Add Second Device, unlock the screen if needed +and wait a moment until a QR code is shown
+On the second device, install Delta Chat
+On the second device, start Delta Chat, select Add as Second Device, and scan the QR code from the old device
+Transfer should start after a few seconds and during transfer both devices will show the progress. +Wait until it is finished on both devices.
+In contrast to many other messengers, after successful transfer, +both devices are completely independent. +One device is not needed for the other to work.
+ +Double-check both devices are in the same Wi-Fi or network
+On Windows, go to Control Panel / Network and Internet +and make sure, Private Network is selected as “Network profile type” +(after transfer, you can change back to the original value)
+On iOS, make sure “System Settings / Apps / Delta Chat / Local Network” access is granted
+On macOS, enable “System Settings / Privacy & Security / Local Network / Delta Chat”
+Your system might have a “personal firewall”, +which is known to cause problems (especially on Windows). +Disable the personal firewall for Delta Chat on both ends and try again
+Guest Networks may not allow devices to communicate with each other. +If possible, use a non-guest network.
+If you still have troubles using the same network, +try to open Mobile Hotspot on one device and join that Wi-Fi from the other one
+Ensure there is enough storage on the destination device
+If transfer started, make sure, the devices stay active and do not fall asleep. +Do not exit Delta Chat. +(we try hard to make the app work in background, but systems tend to kill apps, unfortunately)
+Delta Chat is already logged in on the destination device? +You can use multiple profiles per device, just add another profile
+If you still have problems or if you cannot scan a QR code +try the manual transfer described below
+This method is only recommended if “Add Second Device” as described above does not work.
+ +At Settings → Advanced → Experimental Features +you can try out features we are working on.
+ +The features may be unstable and may be changed or removed.
+ +You can find more information +and give feedback in the Forum.
+ +We would like to improve Delta Chat with your help, +which is why Delta Chat for Android asks whether you want +to send anonymous usage statistics.
+ +You can turn it on and off at +Settings → Advanced → Send statistics to Delta Chat’s developers.
+ +When you turn it on, +weekly statistics will be automatically sent to a bot.
+ +We are interested e.g. in statistics like:
+ +We will not collect any personally identifiable information about you.
+ +Yes, but only if the email address is used exclusively by chatmail clients.
+ +It is not supported to share usage of an email address with non-chatmail apps or web-based mailers, +for the following reasons:
+ +Non-chatmail apps are largely not accomplishing automatic end-to-end email encryption for their users, +while chatmail apps and relays pervasively enforce end-to-end encryption and security standards.
+Non-chatmail apps use email servers as a long-term message archive +while chatmail clients use email servers for ephemeral instant message relay.
+Supporting the full variety of classic email setups +would require considerable development and maintenance efforts, +and complicate making chatmail-based messaging more resilient, reliable and fast.
+First off, please do not use the same classic email address also from non-chatmail classic email apps +unless you are prepared to deal with encrypted messages in the inbox, +double notifications, accidentally deleted emails or similar annoyances.
+ +You can configure a email address for chatting at New Profile → Use Other Server → Use Classic Mail as Relay.
+Note that classic email providers will generally not support Push Notifications
+and have other limitations, see Provider Overview.
+Chatmail uses the default INBOX for relay; ensure the provider setup does too.
+A chat profile using a classic email address allows to to send and receive unencrypted messages.
+These messages, and the chats they appear in, are marked with an email icon
+
.
Any well behaving email server setup will do fine +except if your users’ devices require Google/Apple Push Notifications to work properly.
+ +We generally recommend to set up a chatmail relay. +Chatmail is a community-driven project that encompasses both the setup of relays +and core Rust developments +that power chatmail clients of which Delta Chat is the most well known.
+ +Delta Chat uses a secure subset of the OpenPGP standard +to provide automatic end-to-end encryption using these protocols:
+ +Secure-Join +to exchange encryption setup information through QR-code scanning or “invite links”.
+Autocrypt is used for automatically +establishing end-to-end encryption between contacts and all members of a group chat.
+Sharing a contact to a +chat +enables receivers to use end-to-end encryption with the contact.
+Delta Chat does not query, publish or interact with any OpenPGP key servers.
+ +All messages in Delta Chat are end-to-end encrypted by default. +Since the Delta Chat Version 2 release series (July 2025) +there are no lock or similar markers on end-to-end encrypted messages, anymore.
+ +If you use default chatmail relays, +it is impossible to receive or send messages without end-to-end encryption.
+ +If you instead use a classic email server,
+you can send and receive messages with or without end-to-end encryption.
+Messages lacking end-to-end encryption are marked with an email icon
+
.
A contact profile might show a green checkmark
+
+and an “Introduced by” line.
+Every green-checkmarked contact either did a direct QR-scan with you
+or was introduced by a another green-checkmarked contact.
+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 QR-scan.
For more in-depth discussion of “guaranteed end-to-end encryption” +please see Secure-Join protocols +and specifically read about “Verified Groups”, the technical term +of what is called here “green-checkmarked” or “guaranteed end-to-end encrypted” chats.
+ +Sim.
+ +When we talk about an “end-to-end encrypted message” +we always mean a whole message is encrypted, +including all the attachments +and attachment metadata such as filenames.
+ +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.
+ +OpenPGP is not insecure by itself. +Most publicly discussed OpenPGP security problems +actually stem from bad usability or bad implementations of tools or apps (or both). +It is particularly important to distinguish between OpenPGP, the IETF encryption standard, +and GnuPG (GPG), a command line tool implementing OpenPGP. +Many public critiques of OpenPGP actually discuss GnuPG which Delta Chat has never used. +Delta Chat rather uses the OpenPGP Rust implementation rPGP, +available as an independent “pgp” package, +and security-audited in 2019 and 2024.
+ +We aim, along with other OpenPGP implementors, +to further improve security characteristics by implementing the +new IETF OpenPGP Crypto-Refresh +which was thankfully adopted in summer 2023.
+ +Yes, we are following efforts like MLS +but adopting them would mean breaking end-to-end encryption interoperability. +So it would not be a light decision to take +and there must be tangible improvements for users.
+ +Delta Chat takes a holistic “usable security” approach +and works with a wide range of activist groupings as well as +renowned researchers such as TeamUSEC +to improve actual user outcomes against security threats. +The wire protocol and standard for establishing end-to-end encryption is +only one part of “user outcomes”, +see also our answers to device-seizure +and message-metadata questions.
+ +No, Delta Chat never was vulnerable to EFAIL +because its OpenPGP implementation rPGP +uses Modification Detection Code when encrypting messages +and returns an error +if the Modification Detection Code is incorrect.
+ +Delta Chat also never was vulnerable to the “Direct Exfiltration” EFAIL attack
+because it only decrypts multipart/encrypted messages
+which contain exactly one encrypted and signed part,
+as defined by the Autocrypt Level 1 specification.
If you are sending or receiving email messages without end-to-end encryption (using a classic email server), +they are still protected from cell or cable companies who can not read or modify your email messages. +But both your and your recipient’s email providers +may read, analyze or modify your messages, including any attachments.
+ +Delta Chat by default uses strict +TLS encryption +which secures connections between your device and your email provider. +All of Delta Chat’s TLS-handling has been independently security audited. +Moreover, the connection between your and the recipient’s email provider +will typically be transport-encrypted as well. +If the involved email servers support MTA-STS +then transport encryption will be enforced between email providers +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.
+ +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.
+ +Servers can therefore only see:
+ +By default, the addresses are randomly generated.
+ +All other message, contact and group metadata resides in the end-to-end encrypted part of messages.
+ +Both for protecting against metadata-collecting servers +as well as against the threat of device seizure +we recommend to use a chatmail relay +to create chat profiles using random 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.
+ +No, not yet.
+ +The Signal messenger introduced “Sealed Sender” in 2018 +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.
+ +Even if chatmail relays +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 addresses for sealed sending +but an implementation has not been agreed as a priority yet.
+ +No, not yet.
+ +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.
+ +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 chatmail core, +which would make it available in all chatmail clients.
+ +No, not yet.
+ +Delta Chat uses the Rust OpenPGP library rPGP +which supports the latest IETF Post-Quantum-Cryptography OpenPGP draft. +We aim to add PQC support in chatmail core after the draft is finalized at the IETF +in collaboration with other OpenPGP implementers.
+ +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.
+ +No.
+ +Delta Chat generates secure OpenPGP keys according to the Autocrypt specification 1.1. +We do not recommend or offer users to perform manual key management. +We want to ensure that security audits can focus on a few proven cryptographic algorithms +instead of the full breadth of possible algorithms allowed with OpenPGP. +If you want to extract your OpenPGP key, there only is an expert method: +you need to look it up in the “keypairs” SQLite table of a profile backup tar-file.
+ +Yes, multiple times. +The Delta Chat project continuously undergoes independent security audits and analysis, +from most recent to older:
+ +2024 December, an NLNET-commissioned Evaluation of +rPGP by Radically Open Security took place. +rPGP serves as the end-to-end encryption OpenPGP engine of Delta Chat. +Two advisories were released related to the findings of this audit:
+ +The issues outlined in these advisories have been fixed and are part of Delta Chat +releases on all appstores since December 2024.
+2024 March, we received a deep security analysis from the Applied Cryptography +research group at ETH Zuerich and addressed all raised issues. +See our blog post about Hardening Guaranteed End-to-End encryption for more detailed information and the +Cryptographic Analysis of Delta Chat +research paper published afterwards.
+2023 April, we fixed security and privacy issues with the “web +apps shared in a chat” feature, related to failures of sandboxing +especially with Chromium. We subsequently got an independent security +audit from Cure53 and all issues found were fixed in the 1.36 app series released in April 2023. +See here for the full background story on end-to-end security in the web.
+2023 March, Cure53 analyzed both the transport encryption of +Delta Chat’s network connections and a reproducible mail server setup as +recommended on this site. +You can read more about the audit on our blog +or read the full report here.
+2020, Include Security analyzed Delta +Chat’s Rust core, +IMAP, +SMTP, and +TLS libraries. +It did not find any critical or high-severity issues. +The report raised a few medium-severity weaknesses - +they are no threat to Delta Chat users on their own +because they depend on the environment in which Delta Chat is used. +For usability and compatibility reasons, +we can not mitigate all of them +and decided to provide security recommendations to threatened users. +You can read the full report here.
+2019, Include Security analyzed Delta +Chat’s PGP and +RSA libraries. +It found no critical issues, +but two high-severity issues that we subsequently fixed. +It also revealed one medium-severity and some less severe issues, +but there was no way to exploit these vulnerabilities in the Delta Chat implementation. +Some of them we nevertheless fixed since the audit was concluded. +You can read the full report here.
+Some features require certain permissions, +e.g. you need to grant camera permission if you want to scan an invite QR code.
+ +See Privacy Policy for a detailed overview.
+ +Delta Chat is available for all major and some minor platforms:
+ +The official website, https://delta.chat/download shows all options in detail
+If unavailable, use the mirror at https://deltachat.github.io/deltachat-pages
+Open one of the following app stores and search for “Delta Chat”: +Google Play Store, F-Droid, Huawei App Gallery, iOS and macOS App Store, Microsoft Store
+Check the package manager of your Linux distributions
+Android APKs are also available on https://github.com/deltachat/deltachat-android/releases
+Delta Chat does not receive any Venture Capital and +is not indebted, and under no pressure to produce huge profits, or to +sell users and their friends and family to advertisers (or worse). +We rather use public funding sources, so far from EU and US origins, to help +our efforts in instigating a decentralized and diverse chat messaging eco-system +based on Free and Open-Source community developments.
+ +Concretely, Delta Chat developments have so far been funded from these sources, +ordered chronologically:
+ +The NEXTLEAP EU project funded the research +and implementation of verified groups and setup contact protocols +in 2017 and 2018 and also helped to integrate end-to-end Encryption +through Autocrypt.
+The Open Technology Fund gave us a +first 2018/2019 grant (~$200K) during which we majorly improved the Android app +and released a first Desktop app beta version, and which moreover +moored our feature developments in UX research in human rights contexts, +see our concluding Needfinding and UX report. +The second 2019/2020 grant (~$300K) helped us to +release Delta/iOS versions, to convert our core library to Rust, and +to provide new features for all platforms.
+The NLnet foundation granted in 2019/2020 EUR 46K for +completing Rust/Python bindings and instigating a Chat-bot eco-system.
+In 2021 we received further EU funding for two Next-Generation-Internet +proposals, namely for EPPD - email provider portability directory (~97K EUR) and AEAP - email address porting (~90K EUR) which resulted in better multi-profile support, improved QR-code contact and group setups and many networking improvements on all platforms.
+From End 2021 till March 2023 we received Internet Freedom funding (500K USD) from the +U.S. Bureau of Democracy, Human Rights and Labor (DRL). +This funding supported our long-running goals to make Delta Chat more usable +and compatible with a wide range of email servers world-wide, and more resilient and secure +in places often affected by internet censorship and shutdowns.
+2023-2024 we successfully completed the OTF-funded +Secure Chatmail project, +allowing us to introduce guaranteed encryption, +creating a chatmail server network +and providing “instant onboarding” in all apps released from April 2024 on.
+In 2023 and 2024 we got accepted in the Next Generation Internet (NGI) +program for our work in webxdc PUSH, +along with collaboration partners working on +webxdc evolve, +webxdc XMPP, +DeltaTouch and +DeltaTauri. +All of these projects are partially completed or to be completed in early 2025.
+Sometimes we receive one-time donations from private individuals. +For example, in 2021 a generous individual bank-wired us 4K EUR +with the subject “keep up the good developments!”. 💜 +We use such money to fund development gatherings or to care for ad-hoc expenses +that can not easily be predicted for, or reimbursed from, public funding grants. +Receiving more donations also helps us to become more independent and long-term viable +as a contributor community.
+ + +Por último, mas não menos importante, vários especialistas pró-bono e entusiastas contribuíram +e contribuir aos desenvolvimentos do Delta Chat sem receber dinheiro, ou apenas +pequenas quantidades. Sem elas, o Delta Chat não estaria onde está hoje, não +mesmo perto.
+The monetary funding mentioned above is mostly organized by merlinux GmbH in +Freiburg (Germany), and is distributed to more than a dozen contributors world-wide.
+ +Please see Delta Chat Contribution channels +for both monetary and other contribution possibilities.
+ + + + + \ No newline at end of file diff --git a/src/main/assets/help/qr-icon.png b/src/main/assets/help/qr-icon.png new file mode 100644 index 0000000000000000000000000000000000000000..b012184661df7ec8c177040752045dee8d6d23b3 Binary files /dev/null and b/src/main/assets/help/qr-icon.png differ diff --git a/src/main/assets/help/ru/help.html b/src/main/assets/help/ru/help.html new file mode 100644 index 0000000000000000000000000000000000000000..fb5339d39e073d73443e06307e3be50ad75b70f7 --- /dev/null +++ b/src/main/assets/help/ru/help.html @@ -0,0 +1,1659 @@ + +Delta Chat — надежное, децентрализованное и безопасное приложение для мгновенных сообщений, +доступное для мобильных и настольных платформ.
+ +Мгновенное создание приватных профилей чата +с безопасными и совместимыми релеями chatmail +которые обеспечивают мгновенную доставку сообщений, а также Push-уведомления для устройств iOS и Android.
+Повсеместная поддержка мультипрофиля и +поддержка multi-device на всех платформах +и между различными приложениями chatmail.
+Интерактивные приложения чата для игр и совместной работы
+Проверенное сквозное шифрование +защита от сетевых и серверных атак.
+Бесплатное программное обеспечение с открытым исходным кодом, как на стороне приложений, так и на стороне сервера, +построенное на Интернет-стандартах.
+Во-первых, обратите внимание, что Delta Chat — это приватный мессенджер. +Публичного поиска контактов нет, вы сами решаете, с кем общаться.
+ +Если вы находитесь рядом с другом или членом семьи,
+нажмите значок QR-код
+на главном экране.
+Попросите вашего собеседника отсканировать QR-код
+с помощью приложения Delta Chat.
Для удалённой настройки контакта, +на том же экране, +нажмите “Копировать” или “Поделиться” и отправьте ссылку-приглашение +через другой приватный чат.
+Теперь подождите, пока устанавливается соединение.
+ +Если оба пользователя онлайн, вскоре они увидят чат +и смогут начать безопасное общение.
+Если один из пользователей не в сети или имеет плохое соединение, +возможность общаться появится после восстановления соединения.
+Поздравляем! +Теперь вы будете автоматически использовать сквозное шифрование с этим контактом. +Если вы добавите друг друга в группы, сквозное шифрование будет установлено между всеми участниками.
+ +Поскольку это приватный мессенджер, +писать вам могут только друзья и члены семьи, с которыми вы поделились QR-кодом или ссылкой-приглашением.
+ +Ваши друзья могут поделиться вашим контактом с другими друзьями, это отображается как запрос.
+ +— Нужно принять запрос, прежде чем ответить.
+ +— Вы также можете удалить его, если не хотите общаться с этим человеком.
+ +Прикрепите первый контакт к чату второго используя кнопку
Вложение → Контакт.
+Вы также можете добавить небольшое вступительное сообщение.
Второй контакт получит карточку +на которую можно нажать, чтобы начать общение с первым контактом.
+ +Да. Изображения, видео, файлы, голосовые сообщения и т.д. можно отправлять с помощью кнопок
Вложение
+или
Голосовое сообщение.
Для лучшей производительности изображения по умолчанию оптимизируются и отправляются в меньшем размере, но вы можете отправить их как “файл”, чтобы сохранить оригинал.
+Профиль - это имя, фотография и некоторая дополнительная информация для шифрования сообщений. +Профиль живет только на вашем устройстве (устройствах) +и использует сервер только для передачи сообщений.
+ +При первой установке Delta Chat создаётся первый профиль.
+ +Позже, вы можете нажать на изображение вашего профиля в верхнем левом углу, чтобы Добавить профили +или Сменить профили.
+ +Возможно, вы захотите использовать разные профили для политической деятельности, общения с семьёй или работы.
+ +Вы также можете изучить как использовать один и тот же профиль на нескольких устройствах.
+ +Вы можете добавить изображение профиля в настройках. Если вы пишете своим контактам +или добавляете их с помощью QR-кода, они автоматически видят его как изображение вашего профиля.
+По соображениям конфиденциальности, никто не увидит изображение вашего профиля, +пока вы не напишете им сообщение.
+Да, +вы можете сделать это в разделе Настройки → Профиль → О себе. +После отправки сообщения контакту, +они увидят его при просмотре ваших контактных данных.
+ +Используйте эти инструменты, чтобы организовать чаты и поддерживать порядок во всём:
+ +Закрепленные чаты всегда находятся наверху списка чатов. Вы можете использовать их чтобы быстро получать доступ к вашим любимым чатам или чтобы не забыть о важных вещах.
+Отключить уведомления в чатах необходимо, если вы не хотите получать уведомления от них. Чаты с отключенными уведомлениями остаются на месте, и вы также можете закрепить такой чат.
+Отправить в архив необходимо, если вы не хотите больше видеть их в списке чатов. +Архивные чаты остаются доступными над списком чатов или через поиск.
+Когда в чат, находящийся в архиве, приходит новое сообщение, если не включена опция Отключить уведомления, он Возвращается из архива в ваш список чатов. +Чаты с Отключенными уведомлениями остаются в архиве до тех пор, пока вы не разархивируете их вручную.
+Чтобы использовать функции, нажмите долгим нажатием или щелкните правой кнопкой мыши по чату в списке чатов.
+ +Сохраненные сообщения - это чат, который можно использовать, чтобы легко запоминать и находить сообщения.
+ +В любом чате нажмите и удерживайте или щелкните правой кнопкой мыши на сообщении и выберите Сохранить
+Сохраненные сообщения отмечаются символом
+
+рядом с меткой времени
Затем, зайдите в чат “Сохраненные сообщения” - и вы увидите там все сохраненные сообщения.
+Нажав
,
+вы можете вернуться к этому сообщению в исходном чате
Наконец, вы также можете использовать “Сохраненные сообщения” для создания личных заметок - откройте чат, введите что-то, добавьте фото или голосовое сообщение и т.д.
+Поскольку “Сохраненные сообщения” синхронизируются, они могут стать удобным способом передачи данных между устройствами
+Сообщения остаются сохраненными, даже если они были отредактированы или удалены - +будь то отправителем, очисткой устройства или исчезающими сообщениями из других чатов.
+ +Иногда рядом с аватаром контакта можно увидеть зелёную точку.
+Это означает, что вы недавно видели этого человека в течение последних 10 минут,
+например, потому что он вам написал или отправил подтверждение прочтения.
Таким образом, это не индикатор онлайн-статуса в реальном времени +и другие пользователи не всегда будут видеть, что вы “онлайн”.
+ +Одна галочка
+означает, что сообщение было успешно отправлено вашему провайдеру.
Две галочки
+означают, что по крайней мере одно устройство получателя
+сообщило об успешном получении сообщения.
Получатели могли отключить подтверждения прочтения, +поэтому даже если вы видите только одну галочку, сообщение могло быть прочитано.
+И наоборот, две галочки не обязательно означают +что человек прочитал или понял сообщение ;)
+Вы можете редактировать текст сообщений после отправки.
+Для этого нажмите и удерживайте или щелкните правой кнопкой мыши сообщение и выберите Редактировать
+или
.
Если вы отправили сообщение случайно, +в том же меню выберите Удалить и затем Удалить для всех.
+При этом отредактированные сообщения будут иметь слово “Отредактировано” рядом с временной меткой, +удаленные сообщения будут удалены без каких-либо маркеров в чате. +Уведомления не отправляются, и нет ограничений по времени.
+ +Обратите внимание, что исходное сообщение все еще может быть получено участниками чата +которые могли уже ответить, переслать, сохранить, сделать скриншот или иным образом скопировать сообщение.
+ +Вы можете включить “исчезающие сообщения” +в настройках чата, +в правом верхнем углу окна чата, +выбрав временной интервал +от 5 минут до 1 года.
+ +Пока эта настройка не будет отключена, +приложение Delta Chat каждого участника чата позаботится +об удалении сообщений +по истечении выбранного периода времени. +Отсчёт времени начинается +с момента первого просмотра сообщения получателем в Delta Chat. +Сообщения будут удалены +как на серверах, +так и в самих приложениях.
+ +Обратите внимание, что на исчезающие сообщения можно полагаться +только до тех пор, пока вы доверяете своим собеседникам; +злонамеренные собеседники могут делать фотографии, +или иным образом сохранить, скопировать или переслать сообщения перед удалением.
+ +Кроме того, +если один из собеседников удалит Delta Chat, +(зашифрованные) сообщения могут дольше оставаться на сервере перед удалением.
+ +Если вы используете несколько профилей чата, +вы можете удалить отдельные из них в верхнем переключателе профилей (на Android и iOS), +или в боковой панели щелчком правой кнопкой мыши (в настольном приложении). +Профили чата удаляются только с устройства, на котором была запущена операция удаления. +Профили чата на других устройствах будут продолжать полностью функционировать.
+ +Если вы используете один профиль чата по умолчанию, вы можете просто удалить приложение. +Это автоматически инициирует удаление всех связанных данных об адресе на сервере chatmail. +Подробную информацию смотрите на странице nine.testrun.org address-deletion +или на соответствующей странице выбранного вами стороннего сервера chatmail.
+ +Группы позволяют нескольким пользователям общаться друг с другом конфиденциально на равных правах.
+ +Любой может +изменить название группы или аватар, +добавить или удалить участников, +включить исчезающие сообщения, +и удалять собственные сообщения со всех устройств участников.
+ +Поскольку все участники имеют одинаковые права, группы лучше всего подходят для общения с проверенными друзьями и семьёй.
+ +У всех участников группы одинаковые права. +Поэтому каждый может удалить любого участника или добавить новых.
+Чтобы добавлять или удалять участников, коснитесь названия группы в чате и выберите участника, которого нужно добавить или удалить.
+Если участника еще нет в вашем списке контактов, но он находится с вами лично,
+на том же экране покажите QR-код.
+Попросите его отсканировать QR-код приложением Delta Chat, нажав
+
на главном экране.
Для удалённого добавления участника, +нажмите “Копировать” или “Поделиться” и отправьте ссылку-приглашение +через другой приватный чат новому участнику.
+QR-код и ссылку-приглашение можно использовать для добавления нескольких участников. +Однако, поскольку группы предназначены для проверенных людей, не распространяйте их публично.
+ +Либо удалите себя из списка участников, либо удалите весь чат. +Если позже вы снова захотите присоединиться к группе, попросите другого участника группы добавить вас.
+Или, вместо этого, вы можете “отключить уведомления” для группы — это означает, что вы будете получать все сообщения и сможете их писать, но больше не будете получать уведомления о новых сообщениях.
+Вы можете дублировать группу, чтобы начать отдельное обсуждение +или исключить участников, незаметно для них.
+ +Откройте профиль группы и нажмите Клонировать чат (Android/iOS), +или щелкните правой кнопкой мыши по группе в списке чатов (приложение для ПК).
+Установите новое имя, выберите аватар и при необходимости отредактируйте список участников.
+Новая группа полностью независима от исходной, +которая продолжает работать как прежде.
+ +Вы можете отправлять приложения в чат - игры, редакторы, опросы и другие инструменты. +Это делает Delta Chat по-настоящему расширяемым мессенджером.
+ +В чате используйте кнопку
Вложение → Приложения.
Вы также можете создать собственное приложение и прикрепить его с помощью кнопки
Вложение → Файл.
Встроенные приложения не могут отправлять данные в Интернет или что-либо загружать.
+Встроенное приложение может обмениваться данными только внутри чата Delta Chat с его +копиями на устройствах ваших собеседников. В остальном оно полностью +изолировано от Интернета.
+Конфиденциальность встроенного приложения соответствует конфиденциальности вашего чата +— пока вы доверяете людям, с которыми общаетесь, можете доверять и встроенному приложению.
+Это также означает: как и в случае с веб-ссылками, не открывайте приложения от ненадежных контактов.
+Встроенные приложения - это ZIP-файлы с расширением .xdc, содержащие HTML-, CSS- и JavaScript-код.
+Вы можете расширить пример приложения Hello World +чтобы начать работу.
+Всю остальную информацию вы найдёте в +документации Webxdc.
+Если у вас есть вопросы, вы можете обратиться к другим пользователям с опытом +на форуме Delta Chat.
+Push-уведомления отправляются “Push-сервисами” Apple и Google на устройство пользователя, чтобы неактивное приложение Delta Chat могло получать сообщения в фоновом режиме +и при необходимости показывать уведомления на телефоне пользователя.
+ +Push-уведомления работают со всеми серверами chatmail на
+ +iOS устройствах, путем интеграции с сервисами Apple Push.
+Android устройствах, путем интеграции с сервисом Google FCM Push, +в том числе на устройствах, использующих microG +вместо проприетарного кода Google на телефоне.
+Да, Delta Chat автоматически использует Push-уведомления для профилей chatmail. +И нет, на устройствах Apple нет альтернативы для обеспечения мгновенной доставки сообщений, +поскольку устройства Apple не позволяют Delta Chat запрашивать данные в фоновом режиме. +Push-уведомления автоматически активируются для пользователей iOS, потому что +Система Push-уведомлений Delta Chat, обеспечивающая конфиденциальность +не передает данные Apple, которых у нее еще нет.
+ +Если доступен “push-сервис” Delta Chat включает push-уведомления, +чтобы обеспечить мгновенную доставку сообщений для всех пользователей chatmail.
+ +В настройках Delta Chat “Уведомления”, раздел “Мгновенная доставка” +вы можете изменить следующие настройки, которые влияют на все профили чата:
+ +“Использовать соединение в фоновом режиме”: если вы не используете сервис Push, +вы можете отключить “оптимизацию батареи” для Delta Chat, +позволяя ему получать сообщения в фоновом режиме. +Однако могут быть задержки от нескольких минут до нескольких часов. +Некоторые производители Android даже полностью ограничивают приложения +(см. dontkillmyapp.com) +и Delta Chat может не показывать входящие сообщения, +пока вы снова не откроете приложение вручную.
+Принудительное соединение в фоновом режиме: это запасной вариант +если предыдущие варианты недоступны или не обеспечивают “мгновенную доставку”. +Включение этого параметра вызывает постоянное уведомление на вашем телефоне, +которое иногда может быть “сжато” на последних телефонах Android.
+Оба варианта “Фонового соединения” являются энергосберегающими и +безопасными для использования, если вы заметили, что сообщения приходят только с большой задержкой.
+ +Поддержка push-уведомлений в Delta Chat предотвращает утечку личной информации. +Она не передаёт данные профиля, IP-адрес или содержимое сообщений (даже зашифрованных) +ни одной системе, участвующей в доставке уведомлений.
+ +Вот как приложения Delta Chat выполняют доставку Push-уведомлений:
+ +Приложение Delta Chat локально получает “токен устройства” шифрует его и сохраняет +на сервере chatmail.
+Когда сервер chatmail получает сообщение для пользователя Delta Chat, +он пересылает зашифрованный токен устройства центральному прокси-серверу уведомлений Delta Chat.
+Центральный прокси-сервер уведомлений Delta Chat расшифровывает токен устройства +и пересылает его соответствующему сервису push-уведомлений (Apple, Google и т.д.), +не зная IP-адреса или данных профиля пользователей Delta Chat.
+Центральный сервис push-уведомлений (Apple, Google и т.д.) +пробуждает приложение Delta Chat на вашем устройстве +для проверки новых сообщений в фоновом режиме. +Он не знает о данных профиля устройства, которое он пробуждает. +Центральные сервисы Apple/Google Push никогда не видят никаких данных профиля (отправителя или получателя), +а также не видят содержимого сообщений (в том числе в зашифрованном виде).
+Центральный прокси-сервер уведомлений Delta Chat небольшой и полностью реализован на Rust +забывает о токенах устройств, как только Apple/Google/и т. д. обработали их, +обычно за несколько миллисекунд.
+ +Обратите внимание, что токен устройства шифруется при передаче между приложениями и прокси-сервером уведомлений +но не подписывается. +Таким образом, прокси-сервер уведомлений никогда не видит данные профиля, IP-адреса или +какую-либо криптографическую идентификационную информацию, связанную с устройством (токеном) пользователя.
+ +В результате такого общего подхода к обеспечению конфиденциальности, даже захват почтового сервера chatmail, +или полный захват центрального прокси-сервера уведомлений Delta Chat +не раскроет конфиденциальную информацию, которой сервисы Push уже не обладают.
+ +Delta Chat — это бесплатный децентрализованный мессенджер с открытым исходным кодом и возможностью выбора сервера, +но мы хотим, чтобы пользователи гарантированно получали “мгновенную доставку” сообщений, +такую же, что и в приложениях WhatsApp, Signal или Telegram, +не задавая вопросов, которые больше подходят для опытных пользователей или разработчиков.
+ +Обратите внимание, что в Delta Chat используется компактная и приватная система push-уведомлений +которая обеспечивает “мгновенную доставку” сообщений для всех серверов chatmail +включая тот, который вы можете настроить сами без нашего разрешения. +Добро пожаловать в мощную интероперабельную сеть релеев chatmail :)
+ +Да. Вы можете использовать один и тот же профиль на разных устройствах:
+ +Убедитесь, что оба устройства подключены к одному и тому же Wi-Fi или локальной сети
+На первом устройстве перейдите в Настройки → Добавить второе устройство, при необходимости разблокируйте экран +и подождите немного, пока не появится QR-код
+На втором устройстве, установите Delta Chat
+На втором устройстве запустите Delta Chat, выберите Добавить как второе устройство и отсканируйте QR-код со старого устройства
+Передача должна начаться через несколько секунд и во время передачи на обоих устройствах будет показан прогресс. +Подождите, пока передача не завершится на обоих устройствах.
+В отличие от многих других мессенджеров, после успешной передачи, +оба устройства полностью независимы. +Одно устройство не требуется для работы другого.
+ +Перепроверьте, что оба устройства находятся в одной Wi-Fi или локальной сети.
+В Windows перейдите в Панель управления / Сеть и Интернет +и убедитесь, что в качестве “Типа сетевого профиля” выбрана Частная сеть. +(после передачи, вы можете изменить обратно на исходное значение)
+На iOS, убедитесь, что предоставлен доступ “Настройки системы / Приложения / Delta Chat / Локальная сеть”
+На macOS, включите “Системные настройки / Конфиденциальность и безопасность / Локальная сеть / Delta Chat”
+В вашей системе может быть установлен “персональный брандмауэр”, +который может вызвать проблемы (особенно на Windows). +Отключите персональный брандмауэр для Delta Chat на обоих сторонах и попробуйте снова
+Гостевые сети могут блокировать взаимодействие между устройствами. +Если возможно, используйте не гостевую сеть.
+Если у вас всё ещё возникают проблемы с использованием одной и той же сети, +попробуйте создать Мобильную точку доступа на одном устройстве и подключиться к этой сети Wi-Fi с другого устройства
+Убедитесь, что на устройстве-приемнике имеется достаточно места
+Если передача началась, убедитесь, что устройства остаются активными и не переходят в режим сна. +Не выходите из Delta Chat. +(мы стараемся сделать так, чтобы приложение работало в фоновом режиме, но системы склонны убивать приложения, к сожалению)
+Delta Chat уже авторизован на устройстве-приемнике? +Вы можете использовать несколько профилей на одном устройстве, просто добавьте еще один профиль
+Если у вас всё ещё возникают проблемы или вы не можете отсканировать QR-код +попробуйте ручную передачу, описанную ниже
+Этот метод рекомендуется использовать только в том случае, если функция “Добавить второе устройство”, описанная выше, не работает.
+ +В разделе Настройки → Дополнительно → Экспериментальные функции +вы можете опробовать функции, над которыми мы работаем.
+ +Эти функции могут быть нестабильными и могут быть изменены или удалены.
+ +Вы можете найти дополнительную информацию +и оставить отзыв на Форуме.
+ +Мы хотели бы улучшить Delta Chat с вашей помощью, +поэтому Delta Chat для Android спрашивает, хотите ли вы +отправлять анонимную статистику использования.
+ +Вы можете включить или отключить эту функцию +в разделе Настройки → Дополнительно → Отправить статистику разработчикам Delta Chat.
+ +При включении +еженедельная статистика будет автоматически отправляться боту.
+ +Нас интересует, например, следующая статистика:
+ +Мы не собираем какую-либо информацию, позволяющую идентифицировать вас лично.
+ +Да, но только если адрес электронной почты используется исключительно chatmail клиентами.
+ +Не поддерживается совместное использование адреса электронной почты с приложениями, не являющимися клиентами chatmail или веб-интерфейсами для работы с почтой, +по следующим причинам:
+ +Приложения, не являющиеся клиентами chatmail, в основном не обеспечивают автоматическое сквозное шифрование электронной почты для своих пользователей, +тогда как приложения и релеи chatmail повсеместно применяют сквозное шифрование и стандарты безопасности.
+Приложения, не являющиеся клиентами chatmail, используют серверы электронной почты в качестве долгосрочного архива сообщений, +тогда как клиенты chatmail используют почтовые серверы для передачи мгновенных сообщений с коротким сроком жизни.
+Поддержка всего разнообразия классических настроек электронной почты +потребует значительных усилий по разработке и сопровождению, +а также усложнит повышение устойчивости, надёжности и скорости обмена сообщениями на основе chatmail.
+Прежде всего, не используйте те же классические адреса электронной почты, которые используются в обычных приложениях для отправки писем +если вы не готовы к зашифрованным сообщениям во входящих, +двойным уведомлениям, случайному удалению писем или подобным неудобствам.
+ +Вы можете настроить адрес электронной почты для чата в разделе Новый профиль → Использовать другой сервер → Использовать классическую почту в качестве транспорта.
+Обратите внимание, что классические почтовые провайдеры обычно не поддерживают Push-уведомления
+и имеют другие ограничения, см. раздел Обзор провайдеров.
+Chatmail использует INBOX по умолчанию для ретрансляции; убедитесь, что провайдер также настроен.
+Профиль чата, использующий классический адрес электронной почты, позволяет отправлять и получать незашифрованные сообщения.
+Эти сообщения и чаты, в которых они появляются, помечаются значком электронной почты
+
.
Подойдет любая корректная настройка почтового сервера, за исключением случаев, когда для корректной работы устройств ваших пользователей требуются Push-уведомления Google/Apple.
+ +Мы обычно рекомендуем настроить chatmail релей. +Chatmail — это проект, поддерживаемый сообществом который охватывает как настройку релеев, так +и основные разработки на Rust +которые обеспечивают работу клиентов chatmail наиболее известным из которых является Delta Chat.
+ +Delta Chat использует безопасное подмножество стандарта OpenPGP +для реализации автоматического сквозного шифрования c помощью следующих протоколов:
+ +Secure-Join +для обмена информацией о настройке шифрования через сканирование QR-кода или “ссылок-приглашений”.
+Autocrypt используется для автоматической +настройки сквозного шифрования между контактами и всеми членами группового чата.
+Обмен контактом в +чате +позволяет получателям настроить сквозное шифрование с этим контактом.
+Delta Chat не запрашивает, не публикует и не взаимодействует с какими-либо серверами ключей OpenPGP.
+ +Все сообщения в Delta Chat по умолчанию шифруются сквозным шифрованием. +С момента выхода серии релизов Delta Chat версии 2 (июль 2025 года) +на сообщениях со сквозным шифрованием больше не отображаются замки или другие подобные индикаторы.
+ +Если вы используете стандартные релеи chatmail, +невозможно получать или отправлять сообщения без сквозного шифрования.
+ +Если вы вместо этого используете классический почтовый сервер,
+вы можете отправлять и получать сообщения с использованием или без сквозного шифрования.
+Сообщения, не имеющие сквозного шифрования, отмечены значком электронной почты
+
.
В профиле контакта может отображаться зелёная галочка
+
+и строка “Подтверждён пользователем”.
+Каждый контакт с зелёной галочкой либо выполнил непосредственное сканирование QR-кода с вами,
+либо был подтверждён другим контактом с зелёной галочкой.
+Подтверждения происходят автоматически при добавлении участников в группы.
+Тот, кто добавляет контакт с зелёной галочкой в группу, где только участники с зелёными галочками,
+становится подтверждающим.
+В профиле контакта вы можете последовательно нажимать на текст “Подтверждён …” до тех пор,
+пока не дойдёте до того, с кем вы напрямую выполнили сканирование QR-кода.
Для более подробного обсуждения “гарантированного сквозного шифрования” +пожалуйста, обратитесь к протоколам Secure-Join +и прочитайте о “Проверенных группах”, техническом термине, +который здесь называется “группами с зелёной галочкой” или чатами с “гарантированным сквозным шифрованием”.
+ +Да.
+ +Когда мы говорим о “сообщении, зашифрованном сквозным шифрованием” +мы всегда имеем в виду, что всё сообщение зашифровано, +включая все вложения +и метаданные вложений, такие как имена файлов.
+ +Да, Delta Chat использует безопасное подмножество OpenPGP +требующее, чтобы всё сообщение было правильно зашифровано и подписано. +Например, “Отделённые подписи” не считаются безопасными.
+ +OpenPGP сам по себе не является небезопасным. +Большинство обсуждаемых в публичной сфере проблем безопасности OpenPGP +на самом деле возникают из-за плохого удобства использования или плохой реализации инструментов или приложений (или того и другого). +Особенно важно различать OpenPGP, стандарт шифрования IETF, +и GnuPG (GPG), инструмент командной строки, реализующий OpenPGP. +Многие публичные критические замечания по OpenPGP фактически касаются GnuPG, который Delta Chat никогда не использовал. +Delta Chat вместо этого использует реализацию OpenPGP на Rust rPGP, +доступную как независимый пакет “pgp”, +и проверенную на безопасность в 2019 и 2024 годах.
+ +Вместе с другими разработчиками OpenPGP мы стремимся, +повысить характеристики безопасности путём реализации +нового стандарта IETF OpenPGP Crypto-Refresh, +который был успешно принят летом 2023 года.
+ +Да, мы следим за разработками, такими как MLS +но их внедрение означало бы потерю совместимости сквозного шифрования. +Так что это будет непростое решение +и оно должно принести пользователям ощутимые улучшения.
+ +Delta Chat использует комплексный подход “удобной безопасности” +и работает с широким кругом групп активистов, а также +известными исследователями, такими как TeamUSEC, +для улучшения фактических результатов пользователей в борьбе с угрозами безопасности. +Протокол передачи данных и стандарт для установления сквозного шифрования: +только одна часть “результатов пользователя”, +см. также наши ответы на захват устройства +и метаданные сообщения.
+ +Нет, Delta Chat никогда не был уязвим к EFAIL +потому что его реализация OpenPGP rPGP +использует код обнаружения модификации при шифровании сообщений +и возвращает ошибку +если код обнаружения модификаций не совпадает.
+ +Delta Chat также никогда не был уязвим к атаке “Direct Exfiltration” EFAIL,
+потому что он расшифровывает только многочастные/зашифрованные сообщения,
+которые содержат ровно одну зашифрованную и подписанную часть,
+как определено спецификацией Autocrypt Level 1.
Если вы отправляете или получаете электронные сообщения без сквозного шифрования (используя классический почтовый сервер), +они всё равно защищены от операторов сотовой связи или интернет-провайдеров, которые не могут прочитать или изменить ваши электронные сообщения. +Однако и ваш почтовый провайдер, и почтовый провайдер вашего получателя +могут читать, анализировать или изменять ваши сообщения, включая любые вложения.
+ +Delta Chat по умолчанию использует строгое +TLS-шифрование, +которое защищает соединения между вашим устройством и провайдером электронной почты. +Вся обработка TLS в Delta Chat прошла независимый аудит безопасности. +Более того, соединение между вашим устройством и провайдером электронной почты получателя +как правило, также будет зашифровано. +Если задействованные серверы электронной почты поддерживают MTA-STS, +то между провайдерами электронной почты будет применяться протокол защиты транспортного уровня. +В этом случае сообщения Delta Chat никогда не будут переданы в открытом виде через Интернет, +даже если сообщение не было зашифровано сквозным шифрованием.
+ +В отличие от большинства других мессенджеров, +приложения Delta Chat не сохраняют никакие метаданные о контактах или группах на серверах, даже в зашифрованной форме. +Вместо этого все групповые метаданные шифруются сквозным шифрованием и хранятся исключительно на устройствах конечных пользователей.
+ +Таким образом, серверы могут видеть только:
+ +По умолчанию адреса генерируются случайным образом.
+ +Все прочие метаданные сообщений, контактов и групп содержатся в части сообщений, защищённой сквозным шифрованием.
+ +Для защиты от серверов электронной почты, собирающих метаданные, +а также от угрозы конфискации устройства, +мы рекомендуем использовать релей chatmail +для создания чат-профилей с использованием случайных электронных адресов для передачи сообщений. +Обратите внимание, что приложения Delta Chat на всех платформах поддерживают несколько профилей, +так что вы можете легко использовать отдельные профили, для конкретной ситуации, помимо вашего “основного” профиля, +зная, что все их данные, вместе с метаданными, будут удалены. +Кроме того, если устройство изъято, контакты, использующие временные профили, +не могут быть легко идентифицированы.
+ +Нет, пока нет.
+ +Мессенджер Signal внедрил функцию “Sealed Sender” (Засекреченный отправитель) в 2018 году, +чтобы их серверная инфраструктура не имела информации о том, кто отправляет сообщение группе получателей. +Это особенно важно, поскольку сервер Signal знает мобильный номер каждого аккаунта, +который обычно привязан к паспортным данным.
+ +Даже если релеи chatmail +не запрашивают никаких личных данных (включая телефонные номера), +всё равно может быть полезно защитить реляционные метаданные между адресами +Мы не видим серьёзных проблем в использовании случайных одноразовых электронных адресов для функции sealed sender, +но реализация пока не определена как приоритетная задача.
+ +Нет, пока нет.
+ +На данный момент, Delta Chat не поддерживает Perfect Forward Secrecy (PFS) (Совершенную прямую секретность). +Это означает, что если ваш приватный ключ дешифрования будет скомпрометирован, +и кто-то собрал ваши предыдущие сообщения во время передачи, +они смогут расшифровать и прочитать их, используя скомпрометированный ключ дешифрования. +Обратите внимание, что Forward Secrecy (Прямая секретность) повышает безопасность только если вы удаляете сообщения. +В противном случае, тот, кто получает ваши ключи дешифрования +также может получить все ваши не удалённые сообщения +и ему даже не нужно расшифровывать какие-либо ранее собранные сообщения.
+ +Мы разработали подход к Forward Secrecy (Прямой секретности), который прошёл +первичную проверку некоторыми криптографами и экспертами по реализации +но требует более формального описания +чтобы убедиться, что он надёжно работает в федеративном обмене сообщениями и при использовании нескольких устройств, +прежде чем он может быть внедрён в ядро chatmail, +что сделает его доступным во всех клиентах clients.
+ +Нет, пока нет.
+ +Delta Chat использует библиотеку OpenPGP на Rust rPGP, +которая поддерживает последний черновик IETF Post-Quantum-Cryptography OpenPGP. +Мы планируем добавить поддержку PQC в ядро chatmail после того, как черновик будет окончательно утвержден в IETF +в сотрудничестве с другими разработчиками OpenPGP.
+ +Вы можете проверить статус сквозного шифрования вручную в диалоговом окне “Шифрование” +(профиль пользователя на Android/iOS или щелкните правой кнопкой мыши элемент списка чата пользователя в приложении для ПК). +Delta Chat показывает там два отпечатка. +Если на вашем устройстве и на устройстве вашего контакта показаны одинаковые отпечатки, +соединение безопасно.
+ +Нет.
+ +Delta Chat генерирует безопасные ключи OpenPGP в соответствии со спецификацией Autocrypt 1.1. +Мы не рекомендуем и не предлагаем пользователям управлять ключами вручную. +Мы хотим, чтобы аудиты безопасности могли сосредоточиться на нескольких проверенных криптографических алгоритмах +а не на всем многообразии возможных алгоритмов, разрешенных в OpenPGP. +Если вы хотите извлечь свой ключ OpenPGP, существует только экспертный метод: +вам нужно найти его в SQLite-таблице “keypairs” в tar-файле резервной копии профиля.
+ +Да, множество раз. +Проект Delta Chat находится в постоянном режиме аудита безопасности и анализа, +от последних до более ранних:
+ +Декабрь 2024 года, экспертиза rPGP, организованная + NLNET выполненная Radically Open Security. +rPGP является движком сквозного шифрования OpenPGP OpenPGP в Delta Chat. +В результате этого аудита были подготовлены два отчета по безопасности:
+ +Проблемы, описанные в этих рекомендациях, были исправлены и включены в релизы Delta Chat, +во всех магазинах приложений с декабря 2024 года.
+В марте 2024 года мы получили подробный анализ безопасности от исследовательской группы +Applied Cryptography в ETH Цюрихе и устранили все выявленные проблемы. +Читайте наш пост в блоге о Hardening Guaranteed End-to-End encryption для более подробной информации и +Cryptographic Analysis of Delta Chat +научной статьи, опубликованной позже.
+В Апреле 2023 года мы исправили проблемы безопасности и конфиденциальности в веб-интерфейсе, +функция “приложения, которыми делятся в чате”, связанная со сбоями в песочнице +особенно с Chromium. После этого мы провели независимый аудит +безопасности с Cure53, и все выявленные проблемы были исправлены в серии приложений 1.36, выпущенной в апреле 2023 года. +См. здесь полную информацию о безопасности сквозного шифрования в Интернете.
+В Марте 2023 года, Cure53 проанализировал как протокол защиты транспортного уровня +сетевого соединения Delta Chat, так и воспроизводимую установку почтового сервера, +рекомендуемую на этом сайте. +Подробнее об аудите можно узнать в нашем блоге +или прочитать полный отчёт здесь.
+2020 год, Include Security проанализировала Delta +Chat Rust ядро, +IMAP, +SMTP и +Библиотеки TLS. +Никаких критических или серьёзных проблем обнаружено не было. +В отчете выявлено несколько слабых мест средней серьёзности: +они не представляют угрозы для пользователей Delta Chat сами по себе, +поскольку они зависят от окружения, в котором используется Delta Chat. +По соображениям удобства использования и совместимости, +мы не можем устранить их все +и решили предоставить рекомендации по безопасности для пользователей, которым угрожают эти уязвимости. +Вы можете прочитать полный отчет здесь.
+2019 год Include Security проанализировало библиотеки Delta +Chat PGP и +RSA. +Не было обнаружено критических проблем, +но были выявлены две серьёзные проблемы, которые мы впоследствии исправили. +Также были выявлены, одна проблема средней серьёзности и несколько менее опасных проблем, +но не было возможности эксплуатировать эти уязвимости в реализации Delta Chat. +Некоторые из них мы исправили после завершения аудита. +Вы можете прочитать полный отчёт здесь.
+Некоторые функции требуют определенных разрешений, +например, вам нужно предоставить разрешение на использование камеры, если вы хотите отсканировать QR-код приглашения.
+ +Подробную информацию можно найти в Политике конфиденциальности.
+ +Delta Chat доступен на всех популярных и некоторых менее известных платформах:
+ +На официальной странице загрузки, https://delta.chat/download можно найти подробную информацию о всех вариантах
+Если основной сайт недоступен, используйте зеркало https://deltachat.github.io/deltachat-pages
+Откройте один из следующих магазинов приложений и найдите “Delta Chat”: +Google Play Store, F-Droid, Huawei App Gallery, iOS и macOS App Store, Microsoft Store
+Проверьте менеджер пакетов вашего дистрибутива Linux
+Файлы APK для Android доступны на https://github.com/deltachat/deltachat-android/releases
+Delta Chat не получает никакого венчурного капитала, +не имеет долгов, и не ставит целью заработать огромную прибыль или +продавать пользователей, их друзей и семью рекламодателям (или ещё кому-либо). +Мы предпочитаем использовать государственные источники финансирования далёкие от Евросоюза и США, чтобы +продолжить создавать децентрализованную экосистему обмена сообщениями, +основанную на Свободном и Открытом исходном коде.
+ +В частности, разработка Delta Chat финансировалась из следующих источников, +перечислены в хронологическом порядке:
+ +Проект ЕС NEXTLEAP финансировал исследование +и внедрение проверенных групп и настройку протоколов контактов +в 2017 и 2018 годах, а также помог интегрировать сквозное шифрование +через Autocrypt.
+Фонд Open Technology Fund предоставил нам +первый грант в 2018/2019 году (~$200 тыс.), благодаря которому мы существенно улучшили приложение для Android +и выпустили первую бета-версию приложения для настольных систем, а также провели +исследования в области UX в контексте прав человека, + см. наш заключительный отчет Needfinding and UX report. +Второй грант, полученный в 2019/2020 году (~$300 тыс.), помог нам +выпустить версии Delta/iOS, перевести наш основной код на Rust и +предоставить новые функции для всех платформ.
+Фонд NLnet выделил в 2019/2020 году 46 тыс. евро на +завершение привязки Rust/Python и создание экосистемы чат-ботов.
+В 2021 г. мы получили дополнительное финансирование из ЕС для двух Next-Generation-Internet +целей, а именно для EPPD - e-mail provider portability directory (~97 тыс. евро) и AEAP - email address porting (~90 тыс. евро). Это привело к улучшению поддержки нескольких профилей, улучшению настройки контактов и групп с помощью QR-кода и многим улучшениям в сетевом взаимодействии на всех платформах.
+С конца 2021 года по март 2023 года мы получили финансирование в размере ($500 тыс.) от +U.S. Bureau of Democracy, Human Rights and Labor (DRL) для поддержки свободы интернета. +Это финансирование поддержало наши долгосрочные цели, сделать Delta Chat более удобным для использования +и совместимым с широким спектром электронных почтовых серверов по всему миру, а также более устойчивым +и безопасным в местах, часто подвергающихся интернет-цензуре и отключениям.
+2023-2024 мы завершили проект финансируемый OTF +Secure Chatmail project, +что позволило нам внедрить гарантированное шифрование, +создать сеть серверов chatmail +и обеспечить “немедленную регистрацию” во всех приложениях, выпущенных с апреля 2024 года.
+В 2023 и 2024 годах мы были приняты в программу Next Generation Internet (NGI) +за нашу работу над webxdc PUSH, +в сотрудничестве с партнерами, работающими над +webxdc evolve, +webxdc XMPP, +DeltaTouch и +DeltaTauri. +Все эти проекты частично завершены или будут завершены в начале 2025 года.
+Иногда мы получаем разовые пожертвования от физических лиц. +Например, в 2021 году один щедрый человек перевел нам 4 тыс. евро банковским переводом +с подписью “Продолжайте хорошие разработки!”. 💜 +Мы используем такие деньги для финансирования собраний разработчиков или для покрытия непредвиденных расходов, +которые не могут быть легко предсказаны или возмещены из грантов общественного финансирования. +Получение большего количества пожертвований также помогает нам стать более независимыми и жизнеспособными в долгосрочной перспективе +как сообщество участников.
+ + +И последнее, но далеко не менее важное: несколько экспертов и энтузиастов безвозмездно внесли +и вносят свой вклад в развитие Delta Chat, не получая за это денег или получая +только небольшие суммы. Без них Delta Chat не был бы там, где он находится сегодня, +даже близко.
+Финансирование, упомянутое выше, в основном организовано компанией merlinux GmbH в +Фрайбурге (Германия) и распределяется среди более чем десятка участников по всему миру.
+ +Пожалуйста, обратите внимание на Каналы пожертвований в Delta Chat +для финансовых взносов и других возможностей участия.
+ + + + + \ No newline at end of file diff --git a/src/main/assets/help/saved-icon.png b/src/main/assets/help/saved-icon.png new file mode 100644 index 0000000000000000000000000000000000000000..27c2812ef2f39c3138c6f46ad561850d7cd1a977 Binary files /dev/null and b/src/main/assets/help/saved-icon.png differ diff --git a/src/main/assets/help/sk/help.html b/src/main/assets/help/sk/help.html new file mode 100644 index 0000000000000000000000000000000000000000..ef2afecae766f92b3801599b2984428a88f6e9b9 --- /dev/null +++ b/src/main/assets/help/sk/help.html @@ -0,0 +1,1668 @@ + +Delta Chat is a reliable, decentralized and secure instant messaging app, +available for mobile and desktop platforms.
+ +Instant creation of private chat profiles +with secure and interoperable chatmail relays +that offer instant message delivery, and Push Notifications for iOS and Android devices.
+Pervasive multi-profile and +multi-device support on all platforms +and between different chatmail apps.
+Interactive in-chat apps for gaming and collaboration
+Audited end-to-end encryption +safe against network and server attacks.
+Free and Open Source software, both app and server side, +built on Internet Standards.
+First, note that Delta Chat is a private messenger. +There is no public discovery, you decide about your contacts.
+ +If you are face to face with your friend or family,
+tap the QR Code icon
+on the main screen.
+Ask your chat partner to scan the QR image
+with their Delta Chat app.
For a remote contact setup, +from the same screen, +click “Copy” or “Share” and send the invite link +through another private chat.
+Now wait while connection gets established.
+ +If both sides are online, they will soon see a chat +and can start messaging securely.
+If one side is offline or in bad network, +the ability to chat is delayed until connectivity is restored.
+Congratulations! +You now will automatically use end-to-end encryption with this contact. +If you add each other to groups, end-to-end encryption will be established among all members.
+ +As being a private messenger, +only friends and family you share your QR code or invite link with can write to you.
+ +Your friends may share your contact with other friends, this appears as a request.
+ +You need to accept the request before you can reply.
+You can also delete it if you don’t want to chat with them for now.
+If you delete a request, future messages from that contact will still appear +as message request, so you can change your mind. If you really don’t want to +receive messages from this person, consider blocking them.
+Attach the first contact to the chat of the second using
Attachment Button → Contact.
+You can also add a little introduction message.
The second contact will receive a card then +and can tap it to start chatting with the first contact.
+ +Yes. Images, videos, files, voice messages etc. can be sent using the
Attachment-
+or
Voice Message buttons
For performance, images are optimized and sent at a smaller size by default, but you can send it as a “file” to preserve the original.
+A profile is a name, a picture and some additional information for encrypting messages. +A profile lives on your device(s) only +and uses the server only to relay messages.
+ +On first installation of Delta Chat a first profile is created.
+ +Later, you can tap your profile image in the upper left corner to Add Profiles +or to Switch Profiles.
+ +You may want to use separate profiles for political, family or work related activities.
+ +You may also wish to learn how to use the same profile on multiple devices.
+ +V nastaveniach si môžete pridať profilový obrázok. Ak napíšete svojim kontaktom +alebo si ich pridáte pomocou QR kódu, automaticky to vidia ako váš profilový obrázok.
+Z dôvodu ochrany osobných údajov nikto nevidí váš profilový obrázok, kým im nenapíšete +správu.
+Yes, +you can do so under Settings → Profile → Bio. +Once you sent a message to a contact, +they will see it when they view your contact details.
+ +Use these tools to organize your chats and keep everything in its place:
+ +Pinned chats always stay atop of the chat list. You can use them to access your most loved chats quickly or temporarily to not forget about things.
+Mute chats if you do not want to get notifications for them. Muted chats stay in place and you can also pin a muted chat.
+Archive chats if you do not want to see them in your chat list any longer. +Archived chats remain accessible above the chat list or via search.
+When an archived chat gets a new message, unless muted, it will pop out of the archive and back into your chat list. +Muted chats stay archived until you unarchive them manually.
+To use the functions, long tap or right click a chat in the chat list.
+ +Saved Messages is a chat that you can use to easily remember and find messages.
+ +In any chat, long tap or right click a message and select Save
+Saved messages are marked by the symbol
+
+next to the timestamp
Later, open the “Saved Messages” chat - and you will see the saved messages there.
+By tapping
,
+you can go back to the original message in the original chat
Finally, you can also use “Save Messages” to take personal notes - open the chat, type something, add a photo or a voice message etc.
+As “Saved Message” are synced, they can become very handy for transferring data between devices
+Messages stay saved even if they are edited or deleted - +may it be by sender, by device cleanup or by disappearing messages of other chats.
+ +You can sometimes see a green dot
+next to the avatar of a contact.
+It means they were recently seen by you in the last 10 minutes,
+e.g. because they messaged you or sent a read receipt.
So this is not a real time online status +and others will as well not always see that you are “online”.
+ +One tick
+means that the message was sent successfully to your provider.
Two ticks
+mean that at least one recipient’s device
+reported back to having received the message.
Recipients may have disabled read-receipts, +so even if you see only one tick, the message may have been read.
+The other way round, two ticks do not automatically mean +that a human has read or understood the message ;)
+You can edit the text of your messages after sending.
+For that, long tap or right click the message and select Edit
+or
.
If you have sent a message accidentally, +from the same menu, select Delete and then Delete for Everyone.
+While edited messages will have the word “Edited” next to the timestamp, +deleted messages will be removed without a marker in the chat. +Notifications are not sent and there is no time limit.
+ +Note, that the original message may still be received by chat members +who could have already replied, forwarded, saved, screenshotted or otherwise copied the message.
+ +You can turn on “disappearing messages” +in the settings of a chat, +at the top right of the chat window, +by selecting a time span +between 5 minutes and 1 year.
+ +Until the setting is turned off again, +each chat member’s Delta Chat app takes care +of deleting the messages +after the selected time span. +The time span begins +when the receiver first sees the message in Delta Chat. +The messages are deleted both, +on the servers, +and in the apps itself.
+ +Note that you can rely on disappearing messages +only as long as you trust your chat partners; +malicious chat partners can take photos, +or otherwise save, copy or forward messages before deletion.
+ +Apart from that, +if one chat partner uninstalls Delta Chat, +the (anyway encrypted) messages may take longer to get deleted from their server.
+ +If you are using more than one chat profile, +you can remove single ones in the top profile switcher menu (on Android and iOS), +or in the sidebar with a right click (in the Desktop app). +Chat profiles are only removed on the device where deletion was triggered. +Chat profiles on other devices will continue to fully function.
+ +If you use a single default chat profile you can simply uninstall the app. +This will still automatically trigger deletion of all associated address data on the chatmail server. +For more info, please refer to nine.testrun.org address-deletion +or the respective page from your chosen 3rd party chatmail server.
+ +Groups let several people chat together privately with equal rights.
+ +Anyone can +change the group name or avatar, +add or remove members, +set disappearing messages, +and delete their own messages from all member’s devices.
+ +Because all members have the same rights, groups work best among trusted friends and family.
+ +All group members have the same rights. +For this reason, everyone can delete any member or add new ones.
+To add or delete members, tap the group name in the chat and select the member to add or remove.
+If the member is not yet in your contact list, but face to face with you,
+from the same screen, show a QR code.
+Ask your chat partner to scan the QR image with their Delta Chat app by tapping
+
on the main screen.
For a remote member addition, +click “Copy” or “Share” and send the invite link +through another private chat to the new member.
+QR code and invite link can be used to add several members. +However, since groups are meant for trusted people, avoid sharing them publicly.
+ +Vymažte sa zo zoznamu členov alebo odstráňte celý chat. + Ak sa chcete neskôr znova pripojiť k skupine, požiadajte iného člena skupiny, aby vás znova pridal.
+Ako alternatívu môžete tiež “Stlmiť” skupinu - znamená to, že budete dostávať všetky správy a +môžete stále písať, ale už nebudete upozorňovaní na žiadne nové správy.
+You can duplicate a group to start a separate discussion +or to exclude members without them noticing.
+ +Open the group profile and tap Clone Chat (Android/iOS), +or right-click the group in the chat list (Desktop).
+Set a new name, choose an avatar, and adjust the member list if needed.
+The new group is fully independent from the original, +which continues to work as before.
+ +You can send apps to a chat - games, editors, polls and other tools. +This makes Delta Chat a truly extensible messenger.
+ +In a chat, using
Attachment Button → Apps
You can also create your own app and attach it using
Attachment Button → File
In-chat apps can not send data to the Internet, or download anything.
+An in-chat app can only exchange data within a chat, with its +copies on the devices of your chat partners. Other than that, it’s completely +isolated from the Internet.
+The privacy an in-chat app offers is the privacy of your chat - as long as you +trust the people you chat with, you can trust the in-chat app as well.
+This also means: Just like for web links, do not open apps from untrusted contacts.
+In-chat apps are zip files with .xdc extension containing html, css, and javascript code.
You can extend the Hello World example app +to get started.
+All else you need to know is written in the +Webxdc documentation.
+If you have question, you can ask others with experience +in the Delta Chat Forum.
+Push Notifications are sent by Apple and Google “Push services” to a user’s device +so that an inactive Delta Chat app can fetch messages in the background +and show notifications on a user’s phone if needed.
+ +Push Notifications work with all chatmail servers on
+ +iOS devices, by integrating with Apple Push services.
+Android devices, by integrating with the Google FCM Push service, +including on devices that use microG +instead of proprietary Google code on the phone.
+Yes, Delta Chat automatically uses Push Notifications for chatmail profiles. +And no, there is no alternative on Apple’s phones to achieve instant message delivery +because Apple devices do not allow Delta Chat to fetch data in the background. +Push notifications are automatically activated for iOS users because +Delta Chat’s privacy-preserving Push Notification system +does not expose data to Apple that it doesn’t already have.
+ +If a “Push Service” is available, Delta Chat enables Push Notifications +to achieve instant message delivery for all chatmail users.
+ +In the Delta Chat “Notifications” settings for “Instant delivery” +you can change the following settings effecting all chat profiles:
+ +Use Background Connection: If you are not using a Push service, +you may disable “battery optimizations” for Delta Chat, +allowing it to fetch messages in the background. +However, there could be delays from minutes to hours. +Some Android vendors even restrict apps completely +(see dontkillmyapp.com) +and Delta Chat might not show incoming messages +until you manually open the app again.
+Force Background Connection: This is the fallback option +if the previous options are not available or do not achieve “instant delivery”. +Enabling it causes a permanent notification on your phone +which may sometimes be “minified” with recent Android phones.
+Both “Background Connection” options are energy-efficient and +safe to try if you experience messages arrive only with long delays.
+ +Delta Chat Push Notification support avoids leakage of private information. +It does not leak profile data, IP address or message content (not even encrypted) +to any system involved in the delivery of Push Notifications.
+ +Here is how Delta Chat apps perform Push Notification delivery:
+ +A Delta Chat app obtains a “device token” locally, encrypts it and stores it +on the chatmail server.
+When a chatmail server receives a message for a Delta Chat user +it forwards the encrypted device token to the central Delta Chat notification proxy.
+The central Delta Chat notification proxy decrypts the device token +and forwards it to the respective Push service (Apple, Google, etc.), +without ever knowing the IP or profile data of Delta Chat users.
+The central Push Service (Apple, Google, etc.) +wakes up the Delta Chat app on your device +to check for new messages in the background. +It does not know about the profile data of the device it wakes up. +The central Apple/Google Push services never see any profile data (sender or receiver) +and also never see any message content (also not in encrypted forms).
+The central Delta Chat notification proxy is small and fully implemented in Rust +and forgets about device-tokens as soon as Apple/Google/etc processed them, +usually in a matter of milliseconds.
+ +Note that the device token is encrypted between apps and notification proxy +but it is not signed. +The notification proxy thus never sees profile data, IP-addresses or +any cryptographic identity information associated with a user’s device (token).
+ +Resulting from this overall privacy design, even the seizure of a chatmail server, +or the full seizure of the central Delta Chat notification proxy +would not reveal private information that Push services do not already have.
+ +Delta Chat is a free and open source decentralized messenger with free server choice, +but we want users to reliably experience “instant delivery” of messages, +like they experience from WhatsApp, Signal or Telegram apps, +without asking questions up-front that are more suited to expert users or developers.
+ +Note that Delta Chat has a small and privacy-preserving Push Notification system +that achieves “instant delivery” of messages for all chatmail servers +including a potential one you might setup yourself without our permission. +Welcome to the power of the interoperable chatmail relay network :)
+ +Yes. You can use the same profile on different devices:
+ +Make sure both devices are on the same Wi-Fi or network
+On the first device, go to Settings → Add Second Device, unlock the screen if needed +and wait a moment until a QR code is shown
+On the second device, install Delta Chat
+On the second device, start Delta Chat, select Add as Second Device, and scan the QR code from the old device
+Transfer should start after a few seconds and during transfer both devices will show the progress. +Wait until it is finished on both devices.
+In contrast to many other messengers, after successful transfer, +both devices are completely independent. +One device is not needed for the other to work.
+ +Double-check both devices are in the same Wi-Fi or network
+On Windows, go to Control Panel / Network and Internet +and make sure, Private Network is selected as “Network profile type” +(after transfer, you can change back to the original value)
+On iOS, make sure “System Settings / Apps / Delta Chat / Local Network” access is granted
+On macOS, enable “System Settings / Privacy & Security / Local Network / Delta Chat”
+Your system might have a “personal firewall”, +which is known to cause problems (especially on Windows). +Disable the personal firewall for Delta Chat on both ends and try again
+Guest Networks may not allow devices to communicate with each other. +If possible, use a non-guest network.
+If you still have troubles using the same network, +try to open Mobile Hotspot on one device and join that Wi-Fi from the other one
+Ensure there is enough storage on the destination device
+If transfer started, make sure, the devices stay active and do not fall asleep. +Do not exit Delta Chat. +(we try hard to make the app work in background, but systems tend to kill apps, unfortunately)
+Delta Chat is already logged in on the destination device? +You can use multiple profiles per device, just add another profile
+If you still have problems or if you cannot scan a QR code +try the manual transfer described below
+This method is only recommended if “Add Second Device” as described above does not work.
+ +Neexistujú žiadne okamžité plány, ale niekoľko predbežných myšlienok.
+At Settings → Advanced → Experimental Features +you can try out features we are working on.
+ +The features may be unstable and may be changed or removed.
+ +You can find more information +and give feedback in the Forum.
+ +We would like to improve Delta Chat with your help, +which is why Delta Chat for Android asks whether you want +to send anonymous usage statistics.
+ +You can turn it on and off at +Settings → Advanced → Send statistics to Delta Chat’s developers.
+ +When you turn it on, +weekly statistics will be automatically sent to a bot.
+ +We are interested e.g. in statistics like:
+ +We will not collect any personally identifiable information about you.
+ +Yes, but only if the email address is used exclusively by chatmail clients.
+ +It is not supported to share usage of an email address with non-chatmail apps or web-based mailers, +for the following reasons:
+ +Non-chatmail apps are largely not accomplishing automatic end-to-end email encryption for their users, +while chatmail apps and relays pervasively enforce end-to-end encryption and security standards.
+Non-chatmail apps use email servers as a long-term message archive +while chatmail clients use email servers for ephemeral instant message relay.
+Supporting the full variety of classic email setups +would require considerable development and maintenance efforts, +and complicate making chatmail-based messaging more resilient, reliable and fast.
+First off, please do not use the same classic email address also from non-chatmail classic email apps +unless you are prepared to deal with encrypted messages in the inbox, +double notifications, accidentally deleted emails or similar annoyances.
+ +You can configure a email address for chatting at New Profile → Use Other Server → Use Classic Mail as Relay.
+Note that classic email providers will generally not support Push Notifications
+and have other limitations, see Provider Overview.
+Chatmail uses the default INBOX for relay; ensure the provider setup does too.
+A chat profile using a classic email address allows to to send and receive unencrypted messages.
+These messages, and the chats they appear in, are marked with an email icon
+
.
Any well behaving email server setup will do fine +except if your users’ devices require Google/Apple Push Notifications to work properly.
+ +We generally recommend to set up a chatmail relay. +Chatmail is a community-driven project that encompasses both the setup of relays +and core Rust developments +that power chatmail clients of which Delta Chat is the most well known.
+ +Delta Chat uses a secure subset of the OpenPGP standard +to provide automatic end-to-end encryption using these protocols:
+ +Secure-Join +to exchange encryption setup information through QR-code scanning or “invite links”.
+Autocrypt is used for automatically +establishing end-to-end encryption between contacts and all members of a group chat.
+Sharing a contact to a +chat +enables receivers to use end-to-end encryption with the contact.
+Delta Chat does not query, publish or interact with any OpenPGP key servers.
+ +All messages in Delta Chat are end-to-end encrypted by default. +Since the Delta Chat Version 2 release series (July 2025) +there are no lock or similar markers on end-to-end encrypted messages, anymore.
+ +If you use default chatmail relays, +it is impossible to receive or send messages without end-to-end encryption.
+ +If you instead use a classic email server,
+you can send and receive messages with or without end-to-end encryption.
+Messages lacking end-to-end encryption are marked with an email icon
+
.
A contact profile might show a green checkmark
+
+and an “Introduced by” line.
+Every green-checkmarked contact either did a direct QR-scan with you
+or was introduced by a another green-checkmarked contact.
+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 QR-scan.
For more in-depth discussion of “guaranteed end-to-end encryption” +please see Secure-Join protocols +and specifically read about “Verified Groups”, the technical term +of what is called here “green-checkmarked” or “guaranteed end-to-end encrypted” chats.
+ +Yes.
+ +When we talk about an “end-to-end encrypted message” +we always mean a whole message is encrypted, +including all the attachments +and attachment metadata such as filenames.
+ +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.
+ +OpenPGP is not insecure by itself. +Most publicly discussed OpenPGP security problems +actually stem from bad usability or bad implementations of tools or apps (or both). +It is particularly important to distinguish between OpenPGP, the IETF encryption standard, +and GnuPG (GPG), a command line tool implementing OpenPGP. +Many public critiques of OpenPGP actually discuss GnuPG which Delta Chat has never used. +Delta Chat rather uses the OpenPGP Rust implementation rPGP, +available as an independent “pgp” package, +and security-audited in 2019 and 2024.
+ +We aim, along with other OpenPGP implementors, +to further improve security characteristics by implementing the +new IETF OpenPGP Crypto-Refresh +which was thankfully adopted in summer 2023.
+ +Yes, we are following efforts like MLS +but adopting them would mean breaking end-to-end encryption interoperability. +So it would not be a light decision to take +and there must be tangible improvements for users.
+ +Delta Chat takes a holistic “usable security” approach +and works with a wide range of activist groupings as well as +renowned researchers such as TeamUSEC +to improve actual user outcomes against security threats. +The wire protocol and standard for establishing end-to-end encryption is +only one part of “user outcomes”, +see also our answers to device-seizure +and message-metadata questions.
+ +No, Delta Chat never was vulnerable to EFAIL +because its OpenPGP implementation rPGP +uses Modification Detection Code when encrypting messages +and returns an error +if the Modification Detection Code is incorrect.
+ +Delta Chat also never was vulnerable to the “Direct Exfiltration” EFAIL attack
+because it only decrypts multipart/encrypted messages
+which contain exactly one encrypted and signed part,
+as defined by the Autocrypt Level 1 specification.
If you are sending or receiving email messages without end-to-end encryption (using a classic email server), +they are still protected from cell or cable companies who can not read or modify your email messages. +But both your and your recipient’s email providers +may read, analyze or modify your messages, including any attachments.
+ +Delta Chat by default uses strict +TLS encryption +which secures connections between your device and your email provider. +All of Delta Chat’s TLS-handling has been independently security audited. +Moreover, the connection between your and the recipient’s email provider +will typically be transport-encrypted as well. +If the involved email servers support MTA-STS +then transport encryption will be enforced between email providers +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.
+ +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.
+ +Servers can therefore only see:
+ +By default, the addresses are randomly generated.
+ +All other message, contact and group metadata resides in the end-to-end encrypted part of messages.
+ +Both for protecting against metadata-collecting servers +as well as against the threat of device seizure +we recommend to use a chatmail relay +to create chat profiles using random 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.
+ +No, not yet.
+ +The Signal messenger introduced “Sealed Sender” in 2018 +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.
+ +Even if chatmail relays +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 addresses for sealed sending +but an implementation has not been agreed as a priority yet.
+ +No, not yet.
+ +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.
+ +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 chatmail core, +which would make it available in all chatmail clients.
+ +No, not yet.
+ +Delta Chat uses the Rust OpenPGP library rPGP +which supports the latest IETF Post-Quantum-Cryptography OpenPGP draft. +We aim to add PQC support in chatmail core after the draft is finalized at the IETF +in collaboration with other OpenPGP implementers.
+ +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.
+ +No.
+ +Delta Chat generates secure OpenPGP keys according to the Autocrypt specification 1.1. +We do not recommend or offer users to perform manual key management. +We want to ensure that security audits can focus on a few proven cryptographic algorithms +instead of the full breadth of possible algorithms allowed with OpenPGP. +If you want to extract your OpenPGP key, there only is an expert method: +you need to look it up in the “keypairs” SQLite table of a profile backup tar-file.
+ +Yes, multiple times. +The Delta Chat project continuously undergoes independent security audits and analysis, +from most recent to older:
+ +2024 December, an NLNET-commissioned Evaluation of +rPGP by Radically Open Security took place. +rPGP serves as the end-to-end encryption OpenPGP engine of Delta Chat. +Two advisories were released related to the findings of this audit:
+ +The issues outlined in these advisories have been fixed and are part of Delta Chat +releases on all appstores since December 2024.
+2024 March, we received a deep security analysis from the Applied Cryptography +research group at ETH Zuerich and addressed all raised issues. +See our blog post about Hardening Guaranteed End-to-End encryption for more detailed information and the +Cryptographic Analysis of Delta Chat +research paper published afterwards.
+2023 April, we fixed security and privacy issues with the “web +apps shared in a chat” feature, related to failures of sandboxing +especially with Chromium. We subsequently got an independent security +audit from Cure53 and all issues found were fixed in the 1.36 app series released in April 2023. +See here for the full background story on end-to-end security in the web.
+2023 March, Cure53 analyzed both the transport encryption of +Delta Chat’s network connections and a reproducible mail server setup as +recommended on this site. +You can read more about the audit on our blog +or read the full report here.
+2020, Include Security analyzed Delta +Chat’s Rust core, +IMAP, +SMTP, and +TLS libraries. +It did not find any critical or high-severity issues. +The report raised a few medium-severity weaknesses - +they are no threat to Delta Chat users on their own +because they depend on the environment in which Delta Chat is used. +For usability and compatibility reasons, +we can not mitigate all of them +and decided to provide security recommendations to threatened users. +You can read the full report here.
+2019, Include Security analyzed Delta +Chat’s PGP and +RSA libraries. +It found no critical issues, +but two high-severity issues that we subsequently fixed. +It also revealed one medium-severity and some less severe issues, +but there was no way to exploit these vulnerabilities in the Delta Chat implementation. +Some of them we nevertheless fixed since the audit was concluded. +You can read the full report here.
+Some features require certain permissions, +e.g. you need to grant camera permission if you want to scan an invite QR code.
+ +See Privacy Policy for a detailed overview.
+ +Delta Chat is available for all major and some minor platforms:
+ +The official website, https://delta.chat/download shows all options in detail
+If unavailable, use the mirror at https://deltachat.github.io/deltachat-pages
+Open one of the following app stores and search for “Delta Chat”: +Google Play Store, F-Droid, Huawei App Gallery, iOS and macOS App Store, Microsoft Store
+Check the package manager of your Linux distributions
+Android APKs are also available on https://github.com/deltachat/deltachat-android/releases
+Delta Chat does not receive any Venture Capital and +is not indebted, and under no pressure to produce huge profits, or to +sell users and their friends and family to advertisers (or worse). +We rather use public funding sources, so far from EU and US origins, to help +our efforts in instigating a decentralized and diverse chat messaging eco-system +based on Free and Open-Source community developments.
+ +Concretely, Delta Chat developments have so far been funded from these sources, +ordered chronologically:
+ +The NEXTLEAP EU project funded the research +and implementation of verified groups and setup contact protocols +in 2017 and 2018 and also helped to integrate end-to-end Encryption +through Autocrypt.
+The Open Technology Fund gave us a +first 2018/2019 grant (~$200K) during which we majorly improved the Android app +and released a first Desktop app beta version, and which moreover +moored our feature developments in UX research in human rights contexts, +see our concluding Needfinding and UX report. +The second 2019/2020 grant (~$300K) helped us to +release Delta/iOS versions, to convert our core library to Rust, and +to provide new features for all platforms.
+The NLnet foundation granted in 2019/2020 EUR 46K for +completing Rust/Python bindings and instigating a Chat-bot eco-system.
+In 2021 we received further EU funding for two Next-Generation-Internet +proposals, namely for EPPD - email provider portability directory (~97K EUR) and AEAP - email address porting (~90K EUR) which resulted in better multi-profile support, improved QR-code contact and group setups and many networking improvements on all platforms.
+From End 2021 till March 2023 we received Internet Freedom funding (500K USD) from the +U.S. Bureau of Democracy, Human Rights and Labor (DRL). +This funding supported our long-running goals to make Delta Chat more usable +and compatible with a wide range of email servers world-wide, and more resilient and secure +in places often affected by internet censorship and shutdowns.
+2023-2024 we successfully completed the OTF-funded +Secure Chatmail project, +allowing us to introduce guaranteed encryption, +creating a chatmail server network +and providing “instant onboarding” in all apps released from April 2024 on.
+In 2023 and 2024 we got accepted in the Next Generation Internet (NGI) +program for our work in webxdc PUSH, +along with collaboration partners working on +webxdc evolve, +webxdc XMPP, +DeltaTouch and +DeltaTauri. +All of these projects are partially completed or to be completed in early 2025.
+Sometimes we receive one-time donations from private individuals. +For example, in 2021 a generous individual bank-wired us 4K EUR +with the subject “keep up the good developments!”. 💜 +We use such money to fund development gatherings or to care for ad-hoc expenses +that can not easily be predicted for, or reimbursed from, public funding grants. +Receiving more donations also helps us to become more independent and long-term viable +as a contributor community.
+ + +V neposlednom rade k vývoju Delta Chat prispelo a prispieva viacero pro-bono odborníkov a nadšencov + bez toho, aby dostávali peniaze alebo dostávali iba + malé množstvá. Bez nich by Delta Chat nebol tam, kde je dnes + ani zďaleka.
+The monetary funding mentioned above is mostly organized by merlinux GmbH in +Freiburg (Germany), and is distributed to more than a dozen contributors world-wide.
+ +Please see Delta Chat Contribution channels +for both monetary and other contribution possibilities.
+ + + + + \ No newline at end of file diff --git a/src/main/assets/help/sq/help.html b/src/main/assets/help/sq/help.html new file mode 100644 index 0000000000000000000000000000000000000000..370c28483068fc3d9404196cbd890b5f29c16f75 --- /dev/null +++ b/src/main/assets/help/sq/help.html @@ -0,0 +1,1672 @@ + +Delta Chat is a reliable, decentralized and secure instant messaging app, +available for mobile and desktop platforms.
+ +Instant creation of private chat profiles +with secure and interoperable chatmail relays +that offer instant message delivery, and Push Notifications for iOS and Android devices.
+Pervasive multi-profile and +multi-device support on all platforms +and between different chatmail apps.
+Interactive in-chat apps for gaming and collaboration
+Audited end-to-end encryption +safe against network and server attacks.
+Free and Open Source software, both app and server side, +built on Internet Standards.
+First, note that Delta Chat is a private messenger. +There is no public discovery, you decide about your contacts.
+ +If you are face to face with your friend or family,
+tap the QR Code icon
+on the main screen.
+Ask your chat partner to scan the QR image
+with their Delta Chat app.
For a remote contact setup, +from the same screen, +click “Copy” or “Share” and send the invite link +through another private chat.
+Now wait while connection gets established.
+ +If both sides are online, they will soon see a chat +and can start messaging securely.
+If one side is offline or in bad network, +the ability to chat is delayed until connectivity is restored.
+Congratulations! +You now will automatically use end-to-end encryption with this contact. +If you add each other to groups, end-to-end encryption will be established among all members.
+ +As being a private messenger, +only friends and family you share your QR code or invite link with can write to you.
+ +Your friends may share your contact with other friends, this appears as a request.
+ +Duhet të pranoni kërkesën, para se të mund të përgjigjeni.
+Mundeni edhe ta fshini, nëse s’doni të bisedoni me të tani.
+Nëse fshini një kërkesë, mesazhet e ardhshëm prej atij kontakti do të shfaqen +ende si kërkesë për mesazh, që të mund të ndërroni mendje. Nëse vërtet +s’doni të merrni mesazhe prej këtij personi, shihni mundësinë e bllokimit të tij.
+Attach the first contact to the chat of the second using
Attachment Button → Contact.
+You can also add a little introduction message.
The second contact will receive a card then +and can tap it to start chatting with the first contact.
+ +Po Images, videos, files, voice messages etc. can be sent using the
Attachment-
+or
Voice Message buttons
Si parazgjedhje, për funksionim më të mirë, figurat optimizohen dhe dërgohen në madhësi më të vogël, por mund ta dërgoni si një “kartelë”, që të ruhet origjinali.
+A profile is a name, a picture and some additional information for encrypting messages. +A profile lives on your device(s) only +and uses the server only to relay messages.
+ +On first installation of Delta Chat a first profile is created.
+ +Later, you can tap your profile image in the upper left corner to Add Profiles +or to Switch Profiles.
+ +You may want to use separate profiles for political, family or work related activities.
+ +You may also wish to learn how to use the same profile on multiple devices.
+ +Mund të shtoni një foto profili te rregullimet tuaja. Nëse u shkruani kontakteve +tuaja ose i shtoni përmes kodi QR, e shohin automatikisht si foton e profilit tuaj.
+Për arsye privatësie, askush s’e sheh foton tuaj të profilit, deri sa + t’u shkruani një mesazh.
+Yes, +you can do so under Settings → Profile → Bio. +Once you sent a message to a contact, +they will see it when they view your contact details.
+ +Përdorini këto mjete për të sistemuar fjalosjet tuaja dhe për ta mbajtur gjithçka në vendin e vet:
+ +Fjalosjet e fiksuara qëndrojnë përherë në krye të listës së fjalosjeve. Mund t’i përdorni për të hyrë shpejt, ose përkohësisht te fjalosjet tuaja më të dashura, për të mos harruar gjëra.
+Heshtoni fjalosje, nëse s’doni të merrni njoftime mbi to. Fjalosjet e heshtuara qëndrojnë në vend dhe mundeni edhe të fiksoni një fjalosje të heshtuar.
+Arkivoni fjalosje, nëse s’doni t’i shihni më në listën tuaj të fjalosjeve. +Fjalosjet e arkivuara mbesin të përdorshme mbi listën e fjalosjeve, ose përmes kërkimit.
+Kur te një fjalosje e arkivuar vjen një mesazh i ri, do të hapet jashtë arkivit dhe kalojë te lista juaj e fjalosjeve, veç në mos qoftë e heshtuar. +Fjalosjet e heshtuara mbeten të arkivuara, veç në i çarkivofshi dorazi.
+Që të arkivoni ose fiksoni një fjalosje, prekeni gjatë (në Android), përdorni menunë e fjalosjes (në Android/Desktop), ose fërkojeni për majtas (në iOS); +që të heshtoni një fjalosje, përdorni menunë e fjalosjes (në Android/Desktop), ose profilin e fjalosjes (në iOS).
+ +Saved Messages is a chat that you can use to easily remember and find messages.
+ +In any chat, long tap or right click a message and select Save
+Saved messages are marked by the symbol
+
+next to the timestamp
Later, open the “Saved Messages” chat - and you will see the saved messages there.
+By tapping
,
+you can go back to the original message in the original chat
Finally, you can also use “Save Messages” to take personal notes - open the chat, type something, add a photo or a voice message etc.
+As “Saved Message” are synced, they can become very handy for transferring data between devices
+Messages stay saved even if they are edited or deleted - +may it be by sender, by device cleanup or by disappearing messages of other chats.
+ +You can sometimes see a green dot
+next to the avatar of a contact.
+It means they were recently seen by you in the last 10 minutes,
+e.g. because they messaged you or sent a read receipt.
So this is not a real time online status +and others will as well not always see that you are “online”.
+ +One tick
+means that the message was sent successfully to your provider.
Two ticks
+mean that at least one recipient’s device
+reported back to having received the message.
Recipients may have disabled read-receipts, +so even if you see only one tick, the message may have been read.
+The other way round, two ticks do not automatically mean +that a human has read or understood the message ;)
+You can edit the text of your messages after sending.
+For that, long tap or right click the message and select Edit
+or
.
If you have sent a message accidentally, +from the same menu, select Delete and then Delete for Everyone.
+While edited messages will have the word “Edited” next to the timestamp, +deleted messages will be removed without a marker in the chat. +Notifications are not sent and there is no time limit.
+ +Note, that the original message may still be received by chat members +who could have already replied, forwarded, saved, screenshotted or otherwise copied the message.
+ +You can turn on “disappearing messages” +in the settings of a chat, +at the top right of the chat window, +by selecting a time span +between 5 minutes and 1 year.
+ +Until the setting is turned off again, +each chat member’s Delta Chat app takes care +of deleting the messages +after the selected time span. +The time span begins +when the receiver first sees the message in Delta Chat. +The messages are deleted both, +on the servers, +and in the apps itself.
+ +Note that you can rely on disappearing messages +only as long as you trust your chat partners; +malicious chat partners can take photos, +or otherwise save, copy or forward messages before deletion.
+ +Apart from that, +if one chat partner uninstalls Delta Chat, +the (anyway encrypted) messages may take longer to get deleted from their server.
+ +If you are using more than one chat profile, +you can remove single ones in the top profile switcher menu (on Android and iOS), +or in the sidebar with a right click (in the Desktop app). +Chat profiles are only removed on the device where deletion was triggered. +Chat profiles on other devices will continue to fully function.
+ +If you use a single default chat profile you can simply uninstall the app. +This will still automatically trigger deletion of all associated address data on the chatmail server. +For more info, please refer to nine.testrun.org address-deletion +or the respective page from your chosen 3rd party chatmail server.
+ +Groups let several people chat together privately with equal rights.
+ +Anyone can +change the group name or avatar, +add or remove members, +set disappearing messages, +and delete their own messages from all member’s devices.
+ +Because all members have the same rights, groups work best among trusted friends and family.
+ +All group members have the same rights. +For this reason, everyone can delete any member or add new ones.
+To add or delete members, tap the group name in the chat and select the member to add or remove.
+If the member is not yet in your contact list, but face to face with you,
+from the same screen, show a QR code.
+Ask your chat partner to scan the QR image with their Delta Chat app by tapping
+
on the main screen.
For a remote member addition, +click “Copy” or “Share” and send the invite link +through another private chat to the new member.
+QR code and invite link can be used to add several members. +However, since groups are meant for trusted people, avoid sharing them publicly.
+ +Ose fshini veten si anëtar i listës, ose fshini krejt bisedën. +Nëse më vonë doni të ribëheni pjesë e grupit, kërkojini një anëtari tjetër të grupit t’ju shtojë sërish.
+Ndryshe, mundeni edhe ta “Heshtoni” një grup - duke bërë këtë, do të merrni +krejt mesazhet dhe prapë mund të shkruani, por nuk njoftoheni më, +për çfarëdo mesazhesh të rinj.
+You can duplicate a group to start a separate discussion +or to exclude members without them noticing.
+ +Open the group profile and tap Clone Chat (Android/iOS), +or right-click the group in the chat list (Desktop).
+Set a new name, choose an avatar, and adjust the member list if needed.
+The new group is fully independent from the original, +which continues to work as before.
+ +You can send apps to a chat - games, editors, polls and other tools. +This makes Delta Chat a truly extensible messenger.
+ +In a chat, using
Attachment Button → Apps
You can also create your own app and attach it using
Attachment Button → File
In-chat apps can not send data to the Internet, or download anything.
+An in-chat app can only exchange data within a chat, with its +copies on the devices of your chat partners. Other than that, it’s completely +isolated from the Internet.
+The privacy an in-chat app offers is the privacy of your chat - as long as you +trust the people you chat with, you can trust the in-chat app as well.
+This also means: Just like for web links, do not open apps from untrusted contacts.
+In-chat apps are zip files with .xdc extension containing html, css, and javascript code.
You can extend the Hello World example app +to get started.
+All else you need to know is written in the +Webxdc documentation.
+If you have question, you can ask others with experience +in the Delta Chat Forum.
+Push Notifications are sent by Apple and Google “Push services” to a user’s device +so that an inactive Delta Chat app can fetch messages in the background +and show notifications on a user’s phone if needed.
+ +Push Notifications work with all chatmail servers on
+ +iOS devices, by integrating with Apple Push services.
+Android devices, by integrating with the Google FCM Push service, +including on devices that use microG +instead of proprietary Google code on the phone.
+Yes, Delta Chat automatically uses Push Notifications for chatmail profiles. +And no, there is no alternative on Apple’s phones to achieve instant message delivery +because Apple devices do not allow Delta Chat to fetch data in the background. +Push notifications are automatically activated for iOS users because +Delta Chat’s privacy-preserving Push Notification system +does not expose data to Apple that it doesn’t already have.
+ +If a “Push Service” is available, Delta Chat enables Push Notifications +to achieve instant message delivery for all chatmail users.
+ +In the Delta Chat “Notifications” settings for “Instant delivery” +you can change the following settings effecting all chat profiles:
+ +Use Background Connection: If you are not using a Push service, +you may disable “battery optimizations” for Delta Chat, +allowing it to fetch messages in the background. +However, there could be delays from minutes to hours. +Some Android vendors even restrict apps completely +(see dontkillmyapp.com) +and Delta Chat might not show incoming messages +until you manually open the app again.
+Force Background Connection: This is the fallback option +if the previous options are not available or do not achieve “instant delivery”. +Enabling it causes a permanent notification on your phone +which may sometimes be “minified” with recent Android phones.
+Both “Background Connection” options are energy-efficient and +safe to try if you experience messages arrive only with long delays.
+ +Delta Chat Push Notification support avoids leakage of private information. +It does not leak profile data, IP address or message content (not even encrypted) +to any system involved in the delivery of Push Notifications.
+ +Here is how Delta Chat apps perform Push Notification delivery:
+ +A Delta Chat app obtains a “device token” locally, encrypts it and stores it +on the chatmail server.
+When a chatmail server receives a message for a Delta Chat user +it forwards the encrypted device token to the central Delta Chat notification proxy.
+The central Delta Chat notification proxy decrypts the device token +and forwards it to the respective Push service (Apple, Google, etc.), +without ever knowing the IP or profile data of Delta Chat users.
+The central Push Service (Apple, Google, etc.) +wakes up the Delta Chat app on your device +to check for new messages in the background. +It does not know about the profile data of the device it wakes up. +The central Apple/Google Push services never see any profile data (sender or receiver) +and also never see any message content (also not in encrypted forms).
+The central Delta Chat notification proxy is small and fully implemented in Rust +and forgets about device-tokens as soon as Apple/Google/etc processed them, +usually in a matter of milliseconds.
+ +Note that the device token is encrypted between apps and notification proxy +but it is not signed. +The notification proxy thus never sees profile data, IP-addresses or +any cryptographic identity information associated with a user’s device (token).
+ +Resulting from this overall privacy design, even the seizure of a chatmail server, +or the full seizure of the central Delta Chat notification proxy +would not reveal private information that Push services do not already have.
+ +Delta Chat is a free and open source decentralized messenger with free server choice, +but we want users to reliably experience “instant delivery” of messages, +like they experience from WhatsApp, Signal or Telegram apps, +without asking questions up-front that are more suited to expert users or developers.
+ +Note that Delta Chat has a small and privacy-preserving Push Notification system +that achieves “instant delivery” of messages for all chatmail servers +including a potential one you might setup yourself without our permission. +Welcome to the power of the interoperable chatmail relay network :)
+ +Po You can use the same profile on different devices:
+ +Siguroni që të dyja pajisjet të gjenden në të njëjtin rrjet Wi-Fi, ose me fill
+Te pajisja e parë, kaloni te Rregullime → Shtoni Pajisje të Dytë, shkyçni ekranin, në u dashtë +dhe prisni një çast sa të shfaqet një kod QR
+Te pajisja e dytë, instaloni Delta Chat-in
+Në pajisjen e dytë, nisni Delta Chat-in, përzgjidhni Shtoje si Pajisje të Dytë dhe skanoni kodin QR që nga pajisja e vjetër
+Shpërngulja duhet të fillojë pas pak sekondash dhe, gjatë shpërnguljes, të dyja pajisjet do të shfaqin +ecurinë. Prisni deri sa të përfundojë në të dyja pajisjet.
+Ndryshe nga mjaft shkëmbyes të tjerë mesazhesh, pas një +shpërngulje të suksesshme, që të dyja pajisjet janë plotësisht të pavarura. +Njëra pajisja s’ka nevojë për tjetrën që të funksionojë.
+ +Kontrolloni sërish që të dyja pajisjet të gjenden në të njëjtin rrjet Wi-Fi ose klasik
+On Windows, go to Control Panel / Network and Internet +and make sure, Private Network is selected as “Network profile type” +(after transfer, you can change back to the original value)
+On iOS, make sure “System Settings / Apps / Delta Chat / Local Network” access is granted
+On macOS, enable “System Settings / Privacy & Security / Local Network / Delta Chat”
+Sistemi juaj mund të ketë një “firewall personal”, +që dihet se shkakton probleme (veçanërisht në Windows). +Çaktivizoni firewall-in personal për Delta Chat-in në të dy anët dhe riprovoni
+Guest Networks may not allow devices to communicate with each other. +If possible, use a non-guest network.
+If you still have troubles using the same network, +try to open Mobile Hotspot on one device and join that Wi-Fi from the other one
+Garantoni se ka depozitë të mjaftueshme te pajisja vendmbërritje
+Nëse shpërngulja nisni, siguroni që pajisja mbetet aktive dhe nuk bie në gjumë. +Mos mbyllni Delta Chat-in. +(po punojmë fort për ta bërë aplikacionin të funksionojë në prapaskenë, por sistemet priren t’i asgjësojnë aplikacionet, për fat të keq)
+A është bërë tashmë hyrja te llogaria Delta Chat në pajisjen vendmbërritje? +Mund të përdorni llogari të shumta për pajisje, thjesht shtoni llogari tjetër
+Nëse keni ende probleme, ose s’mundeni të skanoni një kod QR +provoni shpërnguljen dorazi të përshkruar më poshtë
+Kjo metodë rekomandohet vetëm nëse “Shtoni Pajisje të Dytë” si përshkruhet më sipër s’funksionon.
+ +At Settings → Advanced → Experimental Features +you can try out features we are working on.
+ +The features may be unstable and may be changed or removed.
+ +You can find more information +and give feedback in the Forum.
+ +We would like to improve Delta Chat with your help, +which is why Delta Chat for Android asks whether you want +to send anonymous usage statistics.
+ +You can turn it on and off at +Settings → Advanced → Send statistics to Delta Chat’s developers.
+ +When you turn it on, +weekly statistics will be automatically sent to a bot.
+ +We are interested e.g. in statistics like:
+ +We will not collect any personally identifiable information about you.
+ +Yes, but only if the email address is used exclusively by chatmail clients.
+ +It is not supported to share usage of an email address with non-chatmail apps or web-based mailers, +for the following reasons:
+ +Non-chatmail apps are largely not accomplishing automatic end-to-end email encryption for their users, +while chatmail apps and relays pervasively enforce end-to-end encryption and security standards.
+Non-chatmail apps use email servers as a long-term message archive +while chatmail clients use email servers for ephemeral instant message relay.
+Supporting the full variety of classic email setups +would require considerable development and maintenance efforts, +and complicate making chatmail-based messaging more resilient, reliable and fast.
+First off, please do not use the same classic email address also from non-chatmail classic email apps +unless you are prepared to deal with encrypted messages in the inbox, +double notifications, accidentally deleted emails or similar annoyances.
+ +You can configure a email address for chatting at New Profile → Use Other Server → Use Classic Mail as Relay.
+Note that classic email providers will generally not support Push Notifications
+and have other limitations, see Provider Overview.
+Chatmail uses the default INBOX for relay; ensure the provider setup does too.
+A chat profile using a classic email address allows to to send and receive unencrypted messages.
+These messages, and the chats they appear in, are marked with an email icon
+
.
Any well behaving email server setup will do fine +except if your users’ devices require Google/Apple Push Notifications to work properly.
+ +We generally recommend to set up a chatmail relay. +Chatmail is a community-driven project that encompasses both the setup of relays +and core Rust developments +that power chatmail clients of which Delta Chat is the most well known.
+ +Delta Chat uses a secure subset of the OpenPGP standard +to provide automatic end-to-end encryption using these protocols:
+ +Secure-Join +to exchange encryption setup information through QR-code scanning or “invite links”.
+Autocrypt is used for automatically +establishing end-to-end encryption between contacts and all members of a group chat.
+Sharing a contact to a +chat +enables receivers to use end-to-end encryption with the contact.
+Delta Chat does not query, publish or interact with any OpenPGP key servers.
+ +All messages in Delta Chat are end-to-end encrypted by default. +Since the Delta Chat Version 2 release series (July 2025) +there are no lock or similar markers on end-to-end encrypted messages, anymore.
+ +If you use default chatmail relays, +it is impossible to receive or send messages without end-to-end encryption.
+ +If you instead use a classic email server,
+you can send and receive messages with or without end-to-end encryption.
+Messages lacking end-to-end encryption are marked with an email icon
+
.
A contact profile might show a green checkmark
+
+and an “Introduced by” line.
+Every green-checkmarked contact either did a direct QR-scan with you
+or was introduced by a another green-checkmarked contact.
+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 QR-scan.
For more in-depth discussion of “guaranteed end-to-end encryption” +please see Secure-Join protocols +and specifically read about “Verified Groups”, the technical term +of what is called here “green-checkmarked” or “guaranteed end-to-end encrypted” chats.
+ +Po
+ +When we talk about an “end-to-end encrypted message” +we always mean a whole message is encrypted, +including all the attachments +and attachment metadata such as filenames.
+ +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.
+ +OpenPGP is not insecure by itself. +Most publicly discussed OpenPGP security problems +actually stem from bad usability or bad implementations of tools or apps (or both). +It is particularly important to distinguish between OpenPGP, the IETF encryption standard, +and GnuPG (GPG), a command line tool implementing OpenPGP. +Many public critiques of OpenPGP actually discuss GnuPG which Delta Chat has never used. +Delta Chat rather uses the OpenPGP Rust implementation rPGP, +available as an independent “pgp” package, +and security-audited in 2019 and 2024.
+ +We aim, along with other OpenPGP implementors, +to further improve security characteristics by implementing the +new IETF OpenPGP Crypto-Refresh +which was thankfully adopted in summer 2023.
+ +Yes, we are following efforts like MLS +but adopting them would mean breaking end-to-end encryption interoperability. +So it would not be a light decision to take +and there must be tangible improvements for users.
+ +Delta Chat takes a holistic “usable security” approach +and works with a wide range of activist groupings as well as +renowned researchers such as TeamUSEC +to improve actual user outcomes against security threats. +The wire protocol and standard for establishing end-to-end encryption is +only one part of “user outcomes”, +see also our answers to device-seizure +and message-metadata questions.
+ +Jo, Delta Chat s’qe kurrë i cenueshëm nga EFAIL +ngaqë sendërtimi në të i OpenPGP-së rPGP +përdor Kod Pikasje Ndryshimesh, kur fshehtëzohen mesazhe +dhe shfaq një gabim +nëse Kodi i Pikasjes së Ndryshimeve është i pasaktë.
+ +Delta Chat also never was vulnerable to the “Direct Exfiltration” EFAIL attack
+because it only decrypts multipart/encrypted messages
+which contain exactly one encrypted and signed part,
+as defined by the Autocrypt Level 1 specification.
If you are sending or receiving email messages without end-to-end encryption (using a classic email server), +they are still protected from cell or cable companies who can not read or modify your email messages. +But both your and your recipient’s email providers +may read, analyze or modify your messages, including any attachments.
+ +Delta Chat by default uses strict +TLS encryption +which secures connections between your device and your email provider. +All of Delta Chat’s TLS-handling has been independently security audited. +Moreover, the connection between your and the recipient’s email provider +will typically be transport-encrypted as well. +If the involved email servers support MTA-STS +then transport encryption will be enforced between email providers +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.
+ +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.
+ +Servers can therefore only see:
+ +By default, the addresses are randomly generated.
+ +All other message, contact and group metadata resides in the end-to-end encrypted part of messages.
+ +Both for protecting against metadata-collecting servers +as well as against the threat of device seizure +we recommend to use a chatmail relay +to create chat profiles using random 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.
+ +No, not yet.
+ +The Signal messenger introduced “Sealed Sender” in 2018 +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.
+ +Even if chatmail relays +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 addresses for sealed sending +but an implementation has not been agreed as a priority yet.
+ +No, not yet.
+ +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.
+ +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 chatmail core, +which would make it available in all chatmail clients.
+ +No, not yet.
+ +Delta Chat uses the Rust OpenPGP library rPGP +which supports the latest IETF Post-Quantum-Cryptography OpenPGP draft. +We aim to add PQC support in chatmail core after the draft is finalized at the IETF +in collaboration with other OpenPGP implementers.
+ +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.
+ +No.
+ +Delta Chat generates secure OpenPGP keys according to the Autocrypt specification 1.1. +We do not recommend or offer users to perform manual key management. +We want to ensure that security audits can focus on a few proven cryptographic algorithms +instead of the full breadth of possible algorithms allowed with OpenPGP. +If you want to extract your OpenPGP key, there only is an expert method: +you need to look it up in the “keypairs” SQLite table of a profile backup tar-file.
+ +Yes, multiple times. +The Delta Chat project continuously undergoes independent security audits and analysis, +from most recent to older:
+ +2024 December, an NLNET-commissioned Evaluation of +rPGP by Radically Open Security took place. +rPGP serves as the end-to-end encryption OpenPGP engine of Delta Chat. +Two advisories were released related to the findings of this audit:
+ +The issues outlined in these advisories have been fixed and are part of Delta Chat +releases on all appstores since December 2024.
+2024 March, we received a deep security analysis from the Applied Cryptography +research group at ETH Zuerich and addressed all raised issues. +See our blog post about Hardening Guaranteed End-to-End encryption for more detailed information and the +Cryptographic Analysis of Delta Chat +research paper published afterwards.
+Në fillim të 2023-shit, ndreqëm probleme sigurie dhe privatësie me +veçorinë “aplikacione web dhënë në një fjalosje”, të lidhura me dështime +në izolimin e tyre, veçanërisht nën Chromium. Në vazhdim kaluam një auditim +të pavarur sigurie prej Cure53 dhe krejt problemet e gjetura u ndreqën në +seritë 1.36 të hedhura në qarkullim në prill të 2023-shit. +Shihni këtu, për shpjegim të plotë të sfondit për sigurinë lidhur me E2E në web.
+Në fillim të 2023-it, Cure53 analizoi qoftë fshehtëzimin +e transporteve për lidhje rrjeti të Delta Chat-it, qoftë një formësim të riprodhueshëm +shërbyesi poste si të rekomanduarin në këtë sajt. +Mund të lexoni më tepër rreth auditimit në blogun tonë, +ose të lexoni raportin e plotë këtu.
+Më 2020-n, Include Security analizoi bazën +në Rust të Delta Chat-it, si dhe bibliotekat IMAP, SMTP +dhe TLS. +S’gjeti ndonjë problem kritik apo të rëndësisë së madhe. +Raporti ngriti pak dobësi të rëndësisë mesatare - +ato në vetvete s’përbëjnë kërcënim për përdoruesit e Delta Chat-it +ngaqë varen në mjedisin në të cilin përdoret Delta Chat-i. +Për arsye përputhjeje dhe përdorimi, +s’mund t’i shmangim krejt ato +dhe vendosëm të ofrojmë rekomandime sigurie për përdoruesit e kërcënuar. +Mund të lexoni raportin e plotë këtu.
+Më 2019-n, Include Security analizoi libraritë +PGP dhe +RSA të Delta Chat-it. +S’gjeti probleme kritike, +por dy çështje me rëndësi të lartë që i ndreqim në vazhdim. +Nxori gjithashtu një çështje të rëndësisë mesatare dhe disa çështje me më pak rëndësi, +por s’kishte ndonjë rrugë për t’i shfrytëzuar këto cenueshmëri në sendërtimin e Delta Chat-it. +Pavarësisht, disa nga këto i ndreqëm që kur përfundoi auditimi. +Mund të lexoni raportin e plotë këtu.
+Some features require certain permissions, +e.g. you need to grant camera permission if you want to scan an invite QR code.
+ +See Privacy Policy for a detailed overview.
+ +Delta Chat is available for all major and some minor platforms:
+ +The official website, https://delta.chat/download shows all options in detail
+If unavailable, use the mirror at https://deltachat.github.io/deltachat-pages
+Open one of the following app stores and search for “Delta Chat”: +Google Play Store, F-Droid, Huawei App Gallery, iOS and macOS App Store, Microsoft Store
+Check the package manager of your Linux distributions
+Android APKs are also available on https://github.com/deltachat/deltachat-android/releases
+Delta Chat nuk përfiton ndonjë financim të llojit Venture Capital dhe s’ka +borxhe, as gjendet nën trysni për të prodhuar fitime të mëdha, apo për të +shitur përdoruesit, shokët dhe familjen e tyre reklamuesve (apo më keq). +Në vend të kësaj, përdorim burime financimi publik, deri sot me origjinë nga +BE dhe ShBA, si ndihmë të përpjekjeve tona për lulëzimin e një ekosistemi të +decentralizuar dhe të larmishëm shkëmbimi mesazhesh bazuar në zhvillime +bashkësie të Lirë dhe Me Burim të Hapët.
+ +Concretely, Delta Chat developments have so far been funded from these sources, +ordered chronologically:
+ +The NEXTLEAP EU project funded the research +and implementation of verified groups and setup contact protocols +in 2017 and 2018 and also helped to integrate end-to-end Encryption +through Autocrypt.
+Open Technology Fund na dha grantin e parë +për 2018/2019 (~200 mijë dollarë) me të cilin përmirësuam ndjeshëm aplikacionin +për Android dhe hodhëm në qarkullim një version të parë beta aplikacioni për Desktop, +si dhe i afroi më tepër zhvillimet tona për veçori me kërkime UX në kontekste të drejtash të njeriut, +shihni raportin tonë përfundimtar “Needfinding and UX”. +Granti i dytë për 2019/2020 (~$300K) na ndihmoi të hedhim në qarkullim +versione Delta/iOS, për të shndërruar bibliotekën tonë bazë në Rust, si dhe +për të sjellë veçori të reja për krejt platformat.
+The NLnet foundation granted in 2019/2020 EUR 46K for +completing Rust/Python bindings and instigating a Chat-bot eco-system.
+In 2021 we received further EU funding for two Next-Generation-Internet +proposals, namely for EPPD - email provider portability directory (~97K EUR) and AEAP - email address porting (~90K EUR) which resulted in better multi-profile support, improved QR-code contact and group setups and many networking improvements on all platforms.
+From End 2021 till March 2023 we received Internet Freedom funding (500K USD) from the +U.S. Bureau of Democracy, Human Rights and Labor (DRL). +This funding supported our long-running goals to make Delta Chat more usable +and compatible with a wide range of email servers world-wide, and more resilient and secure +in places often affected by internet censorship and shutdowns.
+2023-2024 we successfully completed the OTF-funded +Secure Chatmail project, +allowing us to introduce guaranteed encryption, +creating a chatmail server network +and providing “instant onboarding” in all apps released from April 2024 on.
+In 2023 and 2024 we got accepted in the Next Generation Internet (NGI) +program for our work in webxdc PUSH, +along with collaboration partners working on +webxdc evolve, +webxdc XMPP, +DeltaTouch and +DeltaTauri. +All of these projects are partially completed or to be completed in early 2025.
+Ndonjëherë marrim dhurime unike nga individë privatë. +Për shembull, më 2021-shin një individ bujar na dërgoi një dërgesë +bankare prej 4K eurosh me subjektin “vazhdoni zhvillimin e mbarë!”. 💜 +Këto para i përdorim për të zhvilluar takime, ose mbuluar shpenzime ad-hoc +që s’mund të parashikohen kollaj, ose të rimbursohen nga grante financimesh publike. +Marrja e më shumë dhurimeve na ndihmon gjithashtu të bëhemi më të pavarur dhe +të jetëgjatë, si bashkësi kontribuesish.
+ + +E fundit, por aspak për nga rëndësia, disa ekspertë dhe entuziastë kanë dhënë +dhe japin ndihmesë pro-bono në zhvillimin e Delta Chat-it pa përfituar para, +ose vetëm shuma të vogla. Pa ta, Delta Chat-i s’do të ish atje ku është sot, +madje as afër asaj.
+Financimi monetar i përmendur më sipër është kryesisht i organizuar nga GmbH në +Frajburg (Gjermani) dhe u shpërndahet më tepër se një duzine kontribuesish nga e gjithë bota.
+ +Për mundësi kontributesh monetare ose lloji tjetër, ju lutemi, shihni +kanale kontributi te Delta Chat.
+ + + + + \ No newline at end of file diff --git a/src/main/assets/help/tick1.png b/src/main/assets/help/tick1.png new file mode 100644 index 0000000000000000000000000000000000000000..986201dfbbcb9171b6a5c4680c848e12693b754b Binary files /dev/null and b/src/main/assets/help/tick1.png differ diff --git a/src/main/assets/help/tick2.png b/src/main/assets/help/tick2.png new file mode 100644 index 0000000000000000000000000000000000000000..ea6f08f0b62773b87dbee724d264cfad7ec19fca Binary files /dev/null and b/src/main/assets/help/tick2.png differ diff --git a/src/main/assets/help/uk/help.html b/src/main/assets/help/uk/help.html new file mode 100644 index 0000000000000000000000000000000000000000..30c8aedb0c9f1fc7068ff5117b31a3d7b0f0da7e --- /dev/null +++ b/src/main/assets/help/uk/help.html @@ -0,0 +1,1435 @@ + +Delta Chat це надійний, децентралізований застосунок, для безпечного та миттєвого спілкування, +доступний на мобільних та настільних платформах.
+ +Миттєве створення приватних профілів чату + за допомогою безпечних та сумісних ретрансляторів чат-пошти + які пропонують миттєву доставку повідомлень та push-сповіщення для пристроїв iOS та Android.
+Повсюдна підтримка багатьох профілів та пристроїв на всіх платформах та між різними поштовими програмами.
+Інтерактивні веб-застосунки у чатах для ігор та співпраці
+Аудитоване наскрізне шифрування + захищене від мережевих та серверних атак.
+Вільне програмне забезпечення з відкритим вихідним кодом, як застосунок, так серверна частина, побудоване на основі Інтернет-стандартів.
+По-перше, зверніть увагу, що Delta Chat - це приватний месенджер. Тут немає публічного розкриття, ви самі вирішуєте, з ким спілкуватися.
+ +If you are face to face with your friend or family,
+tap the QR Code icon
+on the main screen.
+Ask your chat partner to scan the QR image
+with their Delta Chat app.
For a remote contact setup, +from the same screen, +click “Copy” or “Share” and send the invite link +through another private chat.
+Зараз зачекайте, поки встановлюється з’єднання.
+ +If both sides are online, they will soon see a chat +and can start messaging securely.
+If one side is offline or in bad network, +the ability to chat is delayed until connectivity is restored.
+Вітаємо! +Тепер Ви автоматично використовуватимете наскрізне шифрування з цим контактом. +Якщо ви додасте один одного у групи, наскрізне шифрування буде встановлено між усіма учасниками.
+ +As being a private messenger, +only friends and family you share your QR code or invite link with can write to you.
+ +Your friends may share your contact with other friends, this appears as a request.
+ +ви потрібно прийняти запит, перш ніж ви зможете відповісти.
+Ви також можете “видалити” його, якщо ви не хочете зараз спілкуватися з ними.
+Якщо ви видалите запит, майбутні повідомлення від цього контакту все одно відображатимуться як запит на повідомлення, щоб ви могли змінити свою думку. Якщо дуже не хочеться отримувати повідомлення від цієї особи, подумайте про її блокування.
+Attach the first contact to the chat of the second using
Attachment Button → Contact.
+You can also add a little introduction message.
The second contact will receive a card then +and can tap it to start chatting with the first contact.
+ +Так. Images, videos, files, voice messages etc. can be sent using the
Attachment-
+or
Voice Message buttons
З міркувань продуктивності, зображення оптимізовані та надсилаються в меншому розмірі за замовчуванням, але ви можете надіслати їх як «файл», щоб зберегти оригінал.
+A profile is a name, a picture and some additional information for encrypting messages. +A profile lives on your device(s) only +and uses the server only to relay messages.
+ +Під час першого встановлення Delta Chat створюється перший профіль.
+ +Пізніше ви можете натиснути на зображення вашого профілю у верхньому лівому кутку, щоб вибрати Додати профілі або Переключити профілі.
+ +Ви можете використовувати окремі профілі для політичної, сімейної або робочої діяльності.
+ +Ви також можете дізнатися як використовувати один і той самий профіль на декількох пристроях.
+ +Ви можете додати зображення профілю в ваших налаштуваннях. Якщо ви пишете комусь із ваших контактів чи додаєте їх через QR код, вони автоматично побачать ваше зображення профілю.
+Із міркувань приватності, ніхто не бачить ваше зображення профілю доки ви їм не напишете.
+Yes, +you can do so under Settings → Profile → Bio. +Once you sent a message to a contact, +they will see it when they view your contact details.
+ +Використовуйте ці інструменти, щоб організувати ваші чати і тримати все на своєму місці:
+ +Закріплені чати завжди залишаються першими в списку чатів. Ви можете використовувати їх, щоб мати швидкий доступ до ваших найулюбленіших чат або тимчасово аби про щось не забути.
+Приглушіть чати якщо ви не хочете отримувати сповіщення для них. Приглушені чати залишаються на місці і ви також можете закріпити приглушений чат.
+Архівуйте чати, якщо ви більше не хочете бачити їх у своєму списку чатів. +Заархівовані чати залишаються доступними над списком чатів або через пошук.
+Коли архівний чат отримує нове повідомлення, якщо не приглушений, він вискочить з архіву і повернеться у ваш список чатів. +Приглушені чати залишаються заархівованим доки ви не розархівуєте їх вручну.
+Щоб скористатися функціями, утримуйте натиснутою клавішу або клацніть правою кнопкою миші на чаті у списку чатів.
+ +Збережені повідомлення - це чат, за допомогою якого ви можете легко запам’ятовувати та знаходити повідомлення.
+ +У будь-якому чаті натисніть і утримуйте повідомлення або клацніть правою кнопкою миші та виберіть Зберегти.
+Збережені повідомлення позначені символом
поруч з міткою часу
Пізніше відкрийте чат “Збережені повідомлення” - і ви побачите там збережені повідомлення. Натиснувши
, ви можете повернутися до початкового повідомлення в оригінальному чаті
Нарешті, ви також можете використовувати “Зберегти повідомлення”, щоб робити особисті нотатки - відкрити чат, набрати щось, додати фотографію або голосове повідомлення тощо.
+Оскільки “Збережені повідомлення” синхронізуються, вони можуть стати дуже зручними для передачі даних між пристроями
+Повідомлення залишаються збереженими, навіть якщо вони були відредаговані або видалені - чи то через відправника, чи то через очищення пристрою, чи то через зникнення повідомлень інших чатів.
+ +You can sometimes see a green dot
+next to the avatar of a contact.
+It means they were recently seen by you in the last 10 minutes,
+e.g. because they messaged you or sent a read receipt.
So this is not a real time online status +and others will as well not always see that you are “online”.
+ +One tick
+means that the message was sent successfully to your provider.
Two ticks
+mean that at least one recipient’s device
+reported back to having received the message.
Recipients may have disabled read-receipts, +so even if you see only one tick, the message may have been read.
+The other way round, two ticks do not automatically mean +that a human has read or understood the message ;)
+Ви можете редагувати текст ваших повідомлень після відправлення. Для цього натисніть на повідомлення довгим натисканням або правою кнопкою миші і виберіть Редагувати або
.
Якщо ви випадково надіслали повідомлення, в тому ж меню виберіть Видалити, а потім Видалити для всіх.
+Відредаговані повідомлення матимуть позначку “Відредаговано” поруч з міткою часу, видалені повідомлення будуть видалені без позначки в чаті. Сповіщення не надсилаються і відсутнє часове обмеження.
+ +Зауважте, що початкове повідомлення все ще може бути отримане учасниками чату які могли вже відповісти, переслати, зберегти, зробити знімок екрану або іншим чином скопіювати повідомлення.
+ +You can turn on “disappearing messages” +in the settings of a chat, +at the top right of the chat window, +by selecting a time span +between 5 minutes and 1 year.
+ +Until the setting is turned off again, +each chat member’s Delta Chat app takes care +of deleting the messages +after the selected time span. +The time span begins +when the receiver first sees the message in Delta Chat. +The messages are deleted both, +on the servers, +and in the apps itself.
+ +Зверніть увагу, що ви можете покладатися на зникнення повідомлень лише доти, доки ви довіряєте своїм співрозмовникам; зловмисники можуть робити фотографії, або іншим чином зберігати, копіювати або пересилати повідомлення перед видаленням.
+ +Apart from that, +if one chat partner uninstalls Delta Chat, +the (anyway encrypted) messages may take longer to get deleted from their server.
+ +Як я можу видалити свій профіль у Delta Chat? {#remove-account}
+ +If you are using more than one chat profile, +you can remove single ones in the top profile switcher menu (on Android and iOS), +or in the sidebar with a right click (in the Desktop app). +Chat profiles are only removed on the device where deletion was triggered. +Chat profiles on other devices will continue to fully function.
+ +If you use a single default chat profile you can simply uninstall the app. +This will still automatically trigger deletion of all associated address data on the chatmail server. +For more info, please refer to nine.testrun.org address-deletion +or the respective page from your chosen 3rd party chatmail server.
+ +Групи дозволяють кільком людям спілкуватися у приватному чаті з рівними правами.
+ +Anyone can +change the group name or avatar, +add or remove members, +set disappearing messages, +and delete their own messages from all member’s devices.
+ +Оскільки усі учасники мають однакові права, групи найкраще працюють серед довірених друзів та родичів.
+ +Усі учасники групи мають однакові права. +Тому кожен може видалити будь-якого учасника або додати нових.
+To add or delete members, tap the group name in the chat and select the member to add or remove.
+If the member is not yet in your contact list, but face to face with you,
+from the same screen, show a QR code.
+Ask your chat partner to scan the QR image with their Delta Chat app by tapping
+
on the main screen.
For a remote member addition, +click “Copy” or “Share” and send the invite link +through another private chat to the new member.
+QR code and invite link can be used to add several members. +However, since groups are meant for trusted people, avoid sharing them publicly.
+ +Або видаліть себе із списку учасників групи, або видаліть весь чат. Якщо ви хочете повернутись до чату пізніше, попросіть іншого учасника групи додати вас знову.
+Ви також можете “Заглушити” групу - це означає, що ви будете отримувати усі повідомлення та можете писати у групу, але ви більше не будете отримувати сповіщення про нові повідомлення.
+You can duplicate a group to start a separate discussion +or to exclude members without them noticing.
+ +Open the group profile and tap Clone Chat (Android/iOS), +or right-click the group in the chat list (Desktop).
+Set a new name, choose an avatar, and adjust the member list if needed.
+Нова група є цілком незалежною від оригінальної, +котра продовжує працювати як раніше.
+ +You can send apps to a chat - games, editors, polls and other tools. +This makes Delta Chat a truly extensible messenger.
+ +In a chat, using
Attachment Button → Apps
You can also create your own app and attach it using
Attachment Button → File
In-chat apps can not send data to the Internet, or download anything.
+An in-chat app can only exchange data within a chat, with its +copies on the devices of your chat partners. Other than that, it’s completely +isolated from the Internet.
+The privacy an in-chat app offers is the privacy of your chat - as long as you +trust the people you chat with, you can trust the in-chat app as well.
+This also means: Just like for web links, do not open apps from untrusted contacts.
+In-chat apps are zip files with .xdc extension containing html, css, and javascript code.
You can extend the Hello World example app +to get started.
+Все інше, що Вам потрібно знати, написано у +документації Webxdc.
+If you have question, you can ask others with experience +in the Delta Chat Forum.
+Push-повідомлення надсилаються “Push-сервісами” Apple та Google на пристрій користувача щоб неактивний додаток Delta Chat міг отримувати повідомлення у фоновому режимі і показувати сповіщення на телефоні користувача, якщо це необхідно.
+ +Push-сповіщення працюють з усіма chatmail-серверами на
+ +iOS-пристроях, інтегруючись із сервісами Apple Push.
+Android-пристроях, шляхом інтеграції з сервісом Google FCM Push, в тому числі на пристроях, які використовують microG замість пропрієтарного коду Google на телефоні.
+Так, Delta Chat автоматично використовує push-повідомлення для профілів chatmail. +І ні, на телефонах Apple немає альтернативи миттєвій доставці повідомлень тому, що пристрої Apple не дозволяють Delta Chat отримувати дані у фоновому режимі. +Push-сповіщення автоматично активуються для користувачів iOS, тому що система push-сповіщень Delta Chat, що зберігає конфіденційність не передає Apple дані, якими вона ще не володіє.
+ +If a “Push Service” is available, Delta Chat enables Push Notifications +to achieve instant message delivery for all chatmail users.
+ +У налаштуваннях “Сповіщення” Delta Chat для “Миттєва доставка” ви можете змінити наступні налаштування, які впливають на всі профілі чату:
+ +Використовувати фонове підключення: Якщо ви не використовуєте Push-сервіс, ви можете вимкнути “оптимізацію батареї” для Delta Chat, що дозволить йому отримувати повідомлення у фоновому режимі. Однак це може призвести до затримок від декількох хвилин до декількох годин. Деякі постачальники Android навіть повністю обмежують додатки (див. dontkillmyapp.com) і Delta Chat може не показувати вхідні повідомлення доки ви не відкриєте програму вручну.
+Примусове фонове підключення: Це запасний варіант якщо попередні опції недоступні або не досягають “миттєвої доставки”. Увімкнення цієї опції спричиняє постійне сповіщення на вашому телефоні яке іноді може бути “мінімізоване” на останніх версіях телефонів Android.
+Обидва варіанти “Фонового з’єднання” є енергоефективними та безпечні, якщо ви відчуваєте, що повідомлення надходять із великими затримками.
+ +Delta Chat Push Notification support avoids leakage of private information. +It does not leak profile data, IP address or message content (not even encrypted) +to any system involved in the delivery of Push Notifications.
+ +Ось як програми Delta Chat здійснюють доставку push-сповіщень:
+ +Додаток Delta Chat отримує “токен пристрою” локально, шифрує його і зберігає на сервері chatmail.
+When a chatmail server receives a message for a Delta Chat user +it forwards the encrypted device token to the central Delta Chat notification proxy.
+The central Delta Chat notification proxy decrypts the device token +and forwards it to the respective Push service (Apple, Google, etc.), +without ever knowing the IP or profile data of Delta Chat users.
+The central Push Service (Apple, Google, etc.) +wakes up the Delta Chat app on your device +to check for new messages in the background. +It does not know about the profile data of the device it wakes up. +The central Apple/Google Push services never see any profile data (sender or receiver) +and also never see any message content (also not in encrypted forms).
+Центральний проксі для сповіщень Delta Chat невеликий і повністю реалізований на Rust забуває про токени пристроїв, як тільки Apple/Google/etc обробили їх, зазвичай за лічені мілісекунди.
+ +Note that the device token is encrypted between apps and notification proxy +but it is not signed. +The notification proxy thus never sees profile data, IP-addresses or +any cryptographic identity information associated with a user’s device (token).
+ +В результаті цього загального дизайну конфіденційності, навіть захоплення chatmail-сервера, або повне вилучення центрального проксі-сервера повідомлень Delta Chat не призведе до розкриття приватної інформації, якої ще не мають Push-сервіси.
+ +Delta Chat - це безкоштовний децентралізований месенджер з відкритим вихідним кодом і вільним вибором сервера, але ми хочемо, щоб користувачі отримували надійну “миттєву доставку” повідомлень, як у додатках WhatsApp, Signal або Telegram, без попередніх запитань, які більше підходять для досвідчених користувачів або розробників.
+ +Note that Delta Chat has a small and privacy-preserving Push Notification system +that achieves “instant delivery” of messages for all chatmail servers +including a potential one you might setup yourself without our permission. +Welcome to the power of the interoperable chatmail relay network :)
+ +Так, ви можете використовувати один і той самий профіль на різних пристроях:
+ +Упевніться, що обидва пристрої підключені до одного Wi-Fi або мережі
+На першому пристрої перейдіть до Налаштування → Додати другий пристрій, розблокуйте екран, якщо потрібно і трохи зачекайте, поки не з’явиться QR-код
+На другому пристрої встановіть Delta Chat
+На другому пристрої запустіть Delta Chat, виберіть Додати як другий пристрій і відскануйте QR-код зі старого пристрою
+Передача має розпочатися через кілька секунд, і під час передачі обидва пристрої відображатимуть прогрес. Дочекайтеся завершення на обох пристроях.
+На відміну від багатьох інших месенджерів, після успішної передачі, обидва пристрої повністю незалежні. Один пристрій не потрібен для роботи іншого.
+ +Ще раз упевніться, що обидва пристрої підключені до одного Wi-Fi або мережі
+У Windows перейдіть до Панель керування / Мережа та Інтернет і переконайтеся, що Приватна мережа вибрано як “Тип мережевого профілю” (після перенесення ви можете повернути початкове значення)
+На iOS переконайтеся, що доступ до “Системні налаштування / Програми / Delta Chat / Локальна мережа” дозволено
+У macOS увімкніть “Системні налаштування / Конфіденційність і безпека / Локальна мережа / Delta Chat”
+Ваша система може мати “персональний брандмауер”, який, як відомо, викликає проблеми (особливо у Windows). Вимкніть персональний брандмауер для Delta Chat на обох кінцях і повторіть спробу
+Гостьові мережі можуть не дозволяти пристроям зв’язуватися один з одним. Якщо можливо, використовуйте негостьову мережу.
+Якщо у вас все ще виникають проблеми з використанням однієї мережі, спробуйте відкрити Мобільну точку доступу на одному пристрої та приєднатися до цього Wi-Fi з іншого
+Переконайтеся, що на цільовому пристрої достатньо пам’яті
+Якщо передача почалася, переконайтеся, що пристрої залишаються активними і не засинають. Не виходьте з Delta Chat. (ми докладаємо всіх зусиль, щоб програма працювала у фоновому режимі, але системи, як правило, вбивають програми, на жаль)
+Delta Chat вже зареєстрований на цільовому пристрої? Ви можете використовувати кілька профілів на одному пристрої, просто додайте ще один профіль
+Якщо у вас усе ще виникають проблеми або якщо ви не можете відсканувати QR-код спробуйте перенесення вручну, описане нижче
+Цей спосіб рекомендований, лише якщо «Додати другий пристрій», як описано вище, не працює.
+ +At Settings → Advanced → Experimental Features +you can try out features we are working on.
+ +Ці функції можуть бути нестабільними та можуть бути змінені або видалені.
+ +Ви можете знайти додаткову інформацію +та залишити відгук на форумі.
+ +We would like to improve Delta Chat with your help, +which is why Delta Chat for Android asks whether you want +to send anonymous usage statistics.
+ +You can turn it on and off at +Settings → Advanced → Send statistics to Delta Chat’s developers.
+ +Коли Ви увімкнете цю функцію, +щотижнева статистика буде автоматично надсилатися боту.
+ +We are interested e.g. in statistics like:
+ +Ми не будемо збирати жодних персональних даних, які б могли ідентифікувати Вас особисто.
+ +Yes, but only if the email address is used exclusively by chatmail clients.
+ +It is not supported to share usage of an email address with non-chatmail apps or web-based mailers, +for the following reasons:
+ +Non-chatmail apps are largely not accomplishing automatic end-to-end email encryption for their users, +while chatmail apps and relays pervasively enforce end-to-end encryption and security standards.
+Non-chatmail apps use email servers as a long-term message archive +while chatmail clients use email servers for ephemeral instant message relay.
+Supporting the full variety of classic email setups +would require considerable development and maintenance efforts, +and complicate making chatmail-based messaging more resilient, reliable and fast.
+First off, please do not use the same classic email address also from non-chatmail classic email apps +unless you are prepared to deal with encrypted messages in the inbox, +double notifications, accidentally deleted emails or similar annoyances.
+ +You can configure a email address for chatting at New Profile → Use Other Server → Use Classic Mail as Relay.
+Note that classic email providers will generally not support Push Notifications
+and have other limitations, see Provider Overview.
+Chatmail uses the default INBOX for relay; ensure the provider setup does too.
+A chat profile using a classic email address allows to to send and receive unencrypted messages.
+These messages, and the chats they appear in, are marked with an email icon
+
.
Any well behaving email server setup will do fine +except if your users’ devices require Google/Apple Push Notifications to work properly.
+ +We generally recommend to set up a chatmail relay. +Chatmail is a community-driven project that encompasses both the setup of relays +and core Rust developments +that power chatmail clients of which Delta Chat is the most well known.
+ +Delta Chat використовує безпечну підмножину стандарту OpenPGP для забезпечення автоматичного наскрізного шифрування за допомогою цих протоколів:
+ +Використовуйте Secure-Join щоб обмінюватися інформацією про налаштування шифрування, через сканування QR-коду або “посилання-запрошення”.
+Autocrypt використовується для автоматичного встановлення наскрізного шифрування між контактами і всіма учасниками групового чату.
+Поширення контакту в чаті дозволяє отримувачам використовувати наскрізне шифрування з контактом.
+Delta Chat не запитує, не публікує і не взаємодіє з будь-якими серверами ключів OpenPGP.
+ +Всі повідомлення в Delta Chat за замовчуванням наскрізно зашифровані. Починаючи з версії 2 Delta Chat (липень 2025 року) на наскрізних зашифрованих повідомленнях більше немає замків або інших подібних маркерів.
+ +Якщо ви використовуєте стандартні ретранслятори чату, неможливо отримувати або надсилати повідомлення без наскрізного шифрування.
+ +If you instead use a classic email server,
+you can send and receive messages with or without end-to-end encryption.
+Messages lacking end-to-end encryption are marked with an email icon
+
.
У профілі контакту може відображатися зелена галочка
і рядок “Представлений”. Кожен контакт із зеленою галочкою або зробив пряме QR-сканування з вами або був представлений іншим контактом, позначеним зеленою галочкою. Знайомство відбувається автоматично під час додавання учасників до груп. Той, хто додає контакт із зеленою галочкою до групи, в якій є лише учасники із зеленою галочкою стає представником. У профілі контакту ви можете кілька разів натиснути на текст “Представлений …” поки не потрапите до того, з ким ви безпосередньо зробили QR-сканування.
Для більш детального обговорення “гарантованого наскрізного шифрування” будь ласка, перегляньте Протоколи безпечного приєднання і, зокрема, прочитайте про “Перевірені групи”, технічний термін того, що тут називається чатами з “зеленою галочкою” або “гарантованим наскрізним шифруванням”.
+ +Так.
+ +Коли ми говоримо про “наскрізно зашифроване повідомлення” ми завжди маємо на увазі, що зашифровано все повідомлення, включно з усіма вкладеннями і метадані вкладень, такі як імена файлів.
+ +Так, Delta Chat використовує безпечну підмножину OpenPGP яка вимагає, щоб все повідомлення було належним чином зашифровано і підписано. Наприклад, “відокремлені підписи” не вважаються безпечними.
+ +OpenPGP сам по собі не є небезпечним. Більшість публічно обговорюваних проблем безпеки OpenPGP насправді виникають через недостатню зручність використання або погану реалізацію інструментів чи програм (або обох). +Особливо важливо розрізняти OpenPGP, стандарт шифрування IETF, і GnuPG (GPG), інструмент командного рядка, що реалізує OpenPGP. +Багато публічних критиків OpenPGP насправді обговорюють GnuPG, який Delta Chat ніколи не використовував. +Delta Chat скоріше використовує реалізацію OpenPGP Rust rPGP, доступну як незалежний пакет «pgp» і перевірку безпеки в 2019 і 2024 роках.
+ +Ми прагнемо, разом з іншими розробниками OpenPGP, подальше покращення характеристик безпеки шляхом впровадження нового IETF OpenPGP Crypto-Refresh який, на щастя, був прийнятий влітку 2023 року.
+ +Yes, we are following efforts like MLS +but adopting them would mean breaking end-to-end encryption interoperability. +So it would not be a light decision to take +and there must be tangible improvements for users.
+ +Delta Chat застосовує цілісний підхід “корисної безпеки” і працює з широким спектром активістських груп, а також відомими дослідниками, такими як TeamUSEC щоб покращити реальний захист користувачів від загроз безпеці. Протокол і стандарт для створення наскрізного шифрування - це лише одна частина “результатів для користувача”, див. також наші відповіді на вилучення пристрою та метадані повідомлення.
+ +Ні, Delta Chat ніколи не був вразливим до EFAIL тому що його реалізація OpenPGP rPGP використовує код виявлення модифікацій при шифруванні повідомлень і повертає помилку якщо код виявлення модифікацій невірний.
+ +Delta Chat також ніколи не був вразливим до EFAIL-атаки “Пряма ексфільтрація” тому що він розшифровує лише “багатокомпонентні/зашифровані” повідомлення, які містять рівно одну зашифровану і підписану частину, як визначено специфікацією Autocrypt Level 1.
+ +If you are sending or receiving email messages without end-to-end encryption (using a classic email server), +they are still protected from cell or cable companies who can not read or modify your email messages. +But both your and your recipient’s email providers +may read, analyze or modify your messages, including any attachments.
+ +Delta Chat by default uses strict +TLS encryption +which secures connections between your device and your email provider. +All of Delta Chat’s TLS-handling has been independently security audited. +Moreover, the connection between your and the recipient’s email provider +will typically be transport-encrypted as well. +If the involved email servers support MTA-STS +then transport encryption will be enforced between email providers +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.
+ +На відміну від більшості інших месенджерів, додатки Delta Chat не зберігають жодних метаданих про контакти чи групи на серверах, навіть у зашифрованому вигляді. Натомість усі метадані груп наскрізно зашифровані та зберігаються виключно на пристроях користувачів.
+ +Servers can therefore only see:
+ +За замовчуванням адреси генеруються випадковим чином.
+ +Усі інші метадані повідомлень, контактів і груп містяться в наскрізно зашифрованій частині повідомлень.
+ +Both for protecting against metadata-collecting servers +as well as against the threat of device seizure +we recommend to use a chatmail relay +to create chat profiles using random 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.
+ +Ні, поки ще ні.
+ +Месенджер Signal запровадив “Запечатаного відправника” у 2018 році щоб їхня серверна інфраструктура не знала, хто надсилає повідомлення певній групі одержувачів. Це особливо важливо, оскільки сервер Signal знає номер мобільного телефону кожного акаунта, який зазвичай асоціюється з паспортними даними.
+ +Even if chatmail relays +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 addresses for sealed sending +but an implementation has not been agreed as a priority yet.
+ +Ні, поки ще ні.
+ +Delta Chat наразі не підтримує ідеальну пряму секретність (Perfect Forward Secrecy, PFS). Це означає, що якщо ваш приватний ключ для розшифрування буде скомпрометовано, а хтось заздалегідь зібрав ваші повідомлення під час передачі, він зможе розшифрувати та прочитати їх, використовуючи зламаний ключ. Зверніть увагу, що пряма секретність підвищує рівень безпеки лише в тому разі, якщо ви видаляєте повідомлення. Інакше, якщо хтось отримує доступ до ваших ключів розшифрування, він зазвичай також має доступ до всіх ваших невидалених повідомлень і навіть не потребує розшифровувати заздалегідь перехоплені дані.
+ +Ми розробили підхід Forward Secrecy, який витримав початкову експертизу від деяких криптографів та експертів з реалізації але чекає на більш офіційний звіт щоб переконатися, що він надійно працює в об’єднаних системах обміну повідомленнями та при використанні декількох пристроїв, перш ніж його можна буде реалізувати в ядрі чату, що зробить його доступним у всіх клієнтах чату.
+ +Ні, поки ще ні.
+ +Delta Chat використовує бібліотеку Rust OpenPGP rPGP яка підтримує останню версію IETF Post-Quantum-Cryptography OpenPGP draft. Ми плануємо додати підтримку PQC у chatmail core після того, як проект буде завершено у IETF у співпраці з іншими розробниками OpenPGP.
+ +Ви можете перевірити стан наскрізного шифрування вручну в діалоговому вікні “Шифрування” (профіль користувача на Android/iOS або клацніть правою кнопкою миші на елементі списку чату користувача на робочому столі). Delta Chat показує там два відбитки. Якщо на вашому пристрої та пристрої вашого співрозмовника з’являються однакові відбитки, з’єднання безпечне.
+ +Ні.
+ +Delta Chat generates secure OpenPGP keys according to the Autocrypt specification 1.1. +We do not recommend or offer users to perform manual key management. +We want to ensure that security audits can focus on a few proven cryptographic algorithms +instead of the full breadth of possible algorithms allowed with OpenPGP. +If you want to extract your OpenPGP key, there only is an expert method: +you need to look it up in the “keypairs” SQLite table of a profile backup tar-file.
+ +Так, багаторазово. Проект Delta Chat постійно проходить незалежні перевірки та аналіз безпеки, а саме, від останніх і закінчуючи старішими:
+ +2024 грудня відбулася оцінка rPGP на замовлення NLNET від Radically Open Security. rPGP слугує рушієм наскрізного шифрування OpenPGP для Delta Chat. За результатами цього аудиту було випущено дві рекомендації:
+Проблеми, описані в цих рекомендаціях, виправлено, і вони є частиною випусків Delta Chat у всіх магазинах додатків з грудня 2024 року.
+ +2024 березня ми отримали глибокий аналіз безпеки від дослідницької групи Applied Cryptography дослідницької групи з прикладної криптографії в ETH Zuerich і вирішили всі порушені питання. Більш детальну інформацію можна знайти в нашому блозі в статті Hardening Guaranteed End-to-end encryption, а також в дослідженні Cryptographic Analysis of Delta Chat, опублікованому пізніше.
+Починаючи з 2023 року, ми виправили проблеми з безпекою та конфіденційністю у функції “веб застосунків, що поширені у чаті”, пов’язані зі збоями в роботі пісочниці особливо в Chromium. Згодом ми отримали незалежний аудит безпеки аудит безпеки від Cure53, і всі знайдені проблеми були виправлені в серії додатків 1.36, випущених у квітні 2023 року. Повну історію про наскрізну безпеку в Інтернеті дивіться тут.
+Починаючи з 2023 року Cure53 проаналізував транспортне шифрування мережевих з’єднань Delta Chat і відтворюване налаштування поштового сервера як рекомендовано на цьому сайті. Ви можете прочитати більше про аудит у нашому блозі або прочитайте повний звіт тут.
+У 2020 році Include Security проаналізувала Rust-ядро Delta Chat і бібліотеки IMAP, SMTP та TLS. Він не виявив критичних або серйозних проблем. У звіті виявлено кілька слабких місць середнього ступеня тяжкості – вони самі по собі не становлять загрози для користувачів Delta Chat оскільки вони залежать від середовища, у якому використовується Delta Chat. З міркувань зручності використання та сумісності ми не можемо пом’якшити їх усі тому вирішили надати рекомендації щодо безпеки користувачам, яким загрожує небезпека. Ви можете прочитати повний звіт тут.
+У 2019 році Include Security проаналізувала бібліотеки PGP і RSA із Delta Chat. Він не виявив критичних проблем, лише дві серйозні проблеми, які ми згодом виправили. Він також виявив одну проблему середньої тяжкості та кілька менш серйозних, але не було можливості використати ці вразливості в реалізації Delta Chat. Деякі з них ми все ж усунули після завершення аудиту. Ви можете прочитати повний звіт тут.
+Some features require certain permissions, +e.g. you need to grant camera permission if you want to scan an invite QR code.
+ +Дивіться політику конфіденційності для детального огляду.
+ +Delta Chat доступний для всіх основних і деяких другорядних платформ:
+ +На офіційному сайті, https://delta.chat/download детально описані всі варіанти
+Якщо вона недоступна, скористайтеся дзеркалом за адресою https://deltachat.github.io/deltachat-pages
+Open one of the following app stores and search for “Delta Chat”: +Google Play Store, F-Droid, Huawei App Gallery, iOS and macOS App Store, Microsoft Store
+Перевірте менеджер пакунків вашого дистрибутива Linux
+APK для Android також доступні на https://github.com/deltachat/deltachat-android/releases
+Delta Chat не отримує жодного Венчурного Капіталу і не є в боргу, не знаходиться під тиском отримання значних прибутків, або продажу користувачів і їхніх друзів з родиною рекламодавцям (або гірше). Ми скоріше використовуємо джерела державного фінансування поки що від ЄС та США, щоб допомогти нашим зусиллям у створенні децентралізованої та різноманітної екосистеми обміну повідомленнями на основі вільного та відкритого коду спільноти розробників
+ +Конкретно, розробка Delta Chat на сьогодні фінансувалися з наступних джерел, в хронологічному порядку:
+ +Проект ЄС NEXTLEAP фінансував дослідження та впровадження верифікованих груп і протоколів встановлення контактів у 2017 та 2018 роках, а також допоміг інтегрувати наскрізне шифрування через Autocrypt.
+Open Technology Fund надав нам два гранти. +Перший грант 2018/2019 року (~$200K), допоміг значно покращили додаток для Android +і випустили першу бета-версію додатка для ПК, і який до того ж +закріпив наші розробки функцій у дослідженнях UX у контексті прав людини, +дивіться наш підсумковий звіт Needfinding and UX report. +Другий грант 2019/2020 року (~$300K) допоміг нам +випустити Delta/iOS версію, конвертувати нашу основному бібліотеку на Rust, +і додати нові функції для всіх платформ.
+Фонд NLnet виділив у 2019/2020 роках 46 тисяч євро на +завершення прив’язок Rust/Python та запуск екосистеми чат-ботів.
+In 2021 we received further EU funding for two Next-Generation-Internet +proposals, namely for EPPD - email provider portability directory (~97K EUR) and AEAP - email address porting (~90K EUR) which resulted in better multi-profile support, improved QR-code contact and group setups and many networking improvements on all platforms.
+From End 2021 till March 2023 we received Internet Freedom funding (500K USD) from the +U.S. Bureau of Democracy, Human Rights and Labor (DRL). +This funding supported our long-running goals to make Delta Chat more usable +and compatible with a wide range of email servers world-wide, and more resilient and secure +in places often affected by internet censorship and shutdowns.
+У 2023-2024 роках ми успішно завершили проєкт Secure Chatmail, що фінансувався OTF, що дозволило нам запровадити гарантоване шифрування, створити мережу серверів chatmail та забезпечити “миттєву реєстрацію” у всіх застосунках, випущених з квітня 2024 року.
+У 2023 та 2024 роках нас прийняли до програми Next Generation Internet (NGI) за нашу роботу над webxdc PUSH, а також у співпраці з партнерами, які працюють над webxdc evolve, webxdc XMPP, DeltaTouch та DeltaTauri. Усі ці проєкти частково завершені або будуть завершені на початку 2025 року.
+Іноді ми отримуємо одноразові пожертви від приватних осіб. Наприклад, у 2021 році щедра приватна особа перерахував нам 4 тис. євро з повідомленням «так тримати!». 💜 Ми використовуємо такі пожертви для фінансування зборів на розвиток або для тимчасових витрат, які важко передбачити або відшкодувати за рахунок грантів державного фінансування. Отримання більшої кількості пожертв також допомагає нам стати більш незалежними та довгостроково життєздатними як спільнота контриб’юторів.
+ + +Кілька експертів та ентузіастів, які працюють на громадських засадах, сприяли розробці програми Delta Chat, не отримуючи грошей або лише невеликі суми. Без них Delta Chat не був би там, де є сьогодні, навіть близько.
+Зазначене вище грошове фінансування в основному організовано компанією merlinux GmbH у Фрайбурзі (Німеччина) і розподілено між більше ніж дюжиною розробників по всьому світу.
+ +Перегляньте канали контрибуції Delta Chat як для грошових, так і для інших можливостей допомоги.
+ + + + + \ No newline at end of file diff --git a/src/main/assets/help/zh_CN/help.html b/src/main/assets/help/zh_CN/help.html new file mode 100644 index 0000000000000000000000000000000000000000..b70b0e936e6ab70e23b34e8699659e657a04afb0 --- /dev/null +++ b/src/main/assets/help/zh_CN/help.html @@ -0,0 +1,1610 @@ + +Delta Chat is a reliable, decentralized and secure instant messaging app, +available for mobile and desktop platforms.
+ +Instant creation of private chat profiles +with secure and interoperable chatmail relays +that offer instant message delivery, and Push Notifications for iOS and Android devices.
+Pervasive multi-profile and +multi-device support on all platforms +and between different chatmail apps.
+Interactive in-chat apps for gaming and collaboration
+Audited end-to-end encryption +safe against network and server attacks.
+Free and Open Source software, both app and server side, +built on Internet Standards.
+First, note that Delta Chat is a private messenger. +There is no public discovery, you decide about your contacts.
+ +If you are face to face with your friend or family,
+tap the QR Code icon
+on the main screen.
+Ask your chat partner to scan the QR image
+with their Delta Chat app.
For a remote contact setup, +from the same screen, +click “Copy” or “Share” and send the invite link +through another private chat.
+Now wait while connection gets established.
+ +If both sides are online, they will soon see a chat +and can start messaging securely.
+If one side is offline or in bad network, +the ability to chat is delayed until connectivity is restored.
+Congratulations! +You now will automatically use end-to-end encryption with this contact. +If you add each other to groups, end-to-end encryption will be established among all members.
+ +As being a private messenger, +only friends and family you share your QR code or invite link with can write to you.
+ +Your friends may share your contact with other friends, this appears as a request.
+ +需先通过该验证请求,用户方可发送回复。
+若你暂无交流意愿,可直接删除该请求以终止对话。
+若您选择删除某条消息请求,对方后续发来的消息仍会以「消息请求」形式显示, +以便您保留重新考虑的机会。若需彻底拒收该联系人消息, +建议直接启用 Block 功能进行屏蔽。
+Attach the first contact to the chat of the second using
Attachment Button → Contact.
+You can also add a little introduction message.
The second contact will receive a card then +and can tap it to start chatting with the first contact.
+ +是的。 Images, videos, files, voice messages etc. can be sent using the
Attachment-
+or
Voice Message buttons
为了提高性能,默认情况下会对图像进行优化并以较小的尺寸发送,但您也可以将其作为 “文件 “发送,以保留原始图像。
+A profile is a name, a picture and some additional information for encrypting messages. +A profile lives on your device(s) only +and uses the server only to relay messages.
+ +首次安装Delta Chat 时,会创建第一个账户资料文件。
+ +之后,您可以点击左上角的个人资料图像,添加个人账户 +或切换账户。
+ +You may want to use separate profiles for political, family or work related activities.
+ +您可能还想了解 如何在多台设备上使用同一账户资料。
+ +您可以在设置中添加个人资料图片。如果您给您的联系人发消息或者通过二维码添加他们,他们会自动看到您的个人资料图片。
+出于隐私原因,在您向他们发送消息之前,没有人会看到您的个人资料照片。
+Yes, +you can do so under Settings → Profile → Bio. +Once you sent a message to a contact, +they will see it when they view your contact details.
+ +使用这些工具来管理您的聊天,让其井然有序:
+ +已固定聊天会呆在聊天列表顶部。您可以利用其快速访问最喜欢的聊天或临时记下某些东西。
+静音聊天,如果您不想再得到关于它们的通知。被静音的聊天会呆在原地,并且您可以固定被静音的聊天。
+如果您不想再在聊天列表中看到聊天记录,请归档聊天。 +已归档的聊天仍可在聊天列表上方或通过搜索访问。
+当被归档的聊天接收到一条新消息,除非其被静音,它会从归档中弹出并返回聊天列表。 +被静音的聊天会保持被归档的状态,除非您手动解档它们。
+要归档或固定一个聊天,可以长按(Android)、使用聊天内部的菜单(Android/桌面版)或者左滑(iOS); +要静音一个聊天,可以使用聊天内部的菜单(Android/桌面版)或者通过聊天概要(iOS)。
+ +Saved Messages 是专用于存储消息的专属对话窗口,可帮助您便捷存储和快速检索重要信息。
+ +在任何聊天中,长按或右键单击消息并选择 ** 保存 **
+已保存的消息会显示专属标识符号。
+
+在时间戳右侧
后续操作时,进入「Saved Messages」对话窗口即可查看所有已保存内容。
+轻触
按钮,
+系统将带您快速跳转回原始聊天中的对应消息。
您还可以将「Save Messages」作为个人记事本使用:进入该对话窗口后,既可编辑文字内容,也能添加图片、语音录音等多媒体素材。
+“Saved Message” 的同步特性使其成为设备间数据迁移的实用方案——用户通过该功能可轻松实现手机、电脑等多终端信息流转。
+即使消息遭到修改或删除 - 无论是发送者编辑、设备清理操作,还是其他聊天中的临时消息功能所触发 - 这些信息仍将保留在系统中。
+ +You can sometimes see a green dot
+next to the avatar of a contact.
+It means they were recently seen by you in the last 10 minutes,
+e.g. because they messaged you or sent a read receipt.
So this is not a real time online status +and others will as well not always see that you are “online”.
+ +One tick
+means that the message was sent successfully to your provider.
Two ticks
+mean that at least one recipient’s device
+reported back to having received the message.
Recipients may have disabled read-receipts, +so even if you see only one tick, the message may have been read.
+The other way round, two ticks do not automatically mean +that a human has read or understood the message ;)
+已发送消息支持文本内容修改。操作时,用户只需长按(移动端)或右键单击(电脑端)目标消息,调出功能菜单后点选Edit或
即可进入编辑模式。
若发生消息误发情况, +可通过以下路径撤回:在当前操作菜单中,依次选择删除和为所有人删除选项。
+在聊天场景中,经过编辑的消息会在时间戳旁标注“Edited”提示, +而被删除的信息则会彻底消失且不显示任何痕迹。 +相关操作既不会触发系统通知,也没有规定必须在时限内完成修改。
+ +需特别提示:若聊天成员已对消息进行过回复、转发、保存本地、截图留存或其他形式的复制操作, +即使您后续编辑了原始消息,对方设备上仍可能留存原内容。
+ +You can turn on “disappearing messages” +in the settings of a chat, +at the top right of the chat window, +by selecting a time span +between 5 minutes and 1 year.
+ +Until the setting is turned off again, +each chat member’s Delta Chat app takes care +of deleting the messages +after the selected time span. +The time span begins +when the receiver first sees the message in Delta Chat. +The messages are deleted both, +on the servers, +and in the apps itself.
+ +请注意,只有当您信任您的聊天伙伴时,您才可以依赖“消息定时销毁”; +不怀好意的人可能会拍照,或者在删除之前以其他方式保存、复制或转发消息。
+ +Apart from that, +if one chat partner uninstalls Delta Chat, +the (anyway encrypted) messages may take longer to get deleted from their server.
+ +If you are using more than one chat profile, +you can remove single ones in the top profile switcher menu (on Android and iOS), +or in the sidebar with a right click (in the Desktop app). +Chat profiles are only removed on the device where deletion was triggered. +Chat profiles on other devices will continue to fully function.
+ +If you use a single default chat profile you can simply uninstall the app. +This will still automatically trigger deletion of all associated address data on the chatmail server. +For more info, please refer to nine.testrun.org address-deletion +or the respective page from your chosen 3rd party chatmail server.
+ +Groups let several people chat together privately with equal rights.
+ +Anyone can +change the group name or avatar, +add or remove members, +set disappearing messages, +and delete their own messages from all member’s devices.
+ +Because all members have the same rights, groups work best among trusted friends and family.
+ +All group members have the same rights. +For this reason, everyone can delete any member or add new ones.
+To add or delete members, tap the group name in the chat and select the member to add or remove.
+If the member is not yet in your contact list, but face to face with you,
+from the same screen, show a QR code.
+Ask your chat partner to scan the QR image with their Delta Chat app by tapping
+
on the main screen.
For a remote member addition, +click “Copy” or “Share” and send the invite link +through another private chat to the new member.
+QR code and invite link can be used to add several members. +However, since groups are meant for trusted people, avoid sharing them publicly.
+ +从成员列表中删除自己,或者删除整个聊天。如果您之后想再加入该群组,请让其他群组成员添加您。
+另外,您也可以“静音”群组——这样做意味着您会收到所有消息并且仍可以编写消息,但不会再收到任何新消息的通知。
+You can duplicate a group to start a separate discussion +or to exclude members without them noticing.
+ +Open the group profile and tap Clone Chat (Android/iOS), +or right-click the group in the chat list (Desktop).
+Set a new name, choose an avatar, and adjust the member list if needed.
+The new group is fully independent from the original, +which continues to work as before.
+ +You can send apps to a chat - games, editors, polls and other tools. +This makes Delta Chat a truly extensible messenger.
+ +In a chat, using
Attachment Button → Apps
You can also create your own app and attach it using
Attachment Button → File
In-chat apps can not send data to the Internet, or download anything.
+An in-chat app can only exchange data within a chat, with its +copies on the devices of your chat partners. Other than that, it’s completely +isolated from the Internet.
+The privacy an in-chat app offers is the privacy of your chat - as long as you +trust the people you chat with, you can trust the in-chat app as well.
+This also means: Just like for web links, do not open apps from untrusted contacts.
+In-chat apps are zip files with .xdc extension containing html, css, and javascript code.
You can extend the Hello World example app +to get started.
+All else you need to know is written in the +Webxdc documentation.
+If you have question, you can ask others with experience +in the Delta Chat Forum.
+推送通知由 Apple 和 Google 的“推送服务”发送到用户的设备,以便非活动状态的 Delta Chat 应用可以在后台获取消息,并在需要时在用户的手机上显示通知。
+ +推送通知适用于以下所有 chatmail 服务器:
+ +iOS 设备通过与 Apple Push 服务集成。
+Android 设备,通过与 Google FCM Push 服务集成, +包括使用 microG +而不是手机上专有 Google 代码的设备。
+是的,Delta Chat 会自动使用推送通知来接收 chatmail 个人资料。 +而且,Apple 手机上没有其他方式可以实现即时消息传递 +因为 Apple 设备不允许 Delta Chat 在后台获取数据。 +推送通知会自动为 iOS 用户激活,因为 +Delta Chat 的隐私保护推送通知系统 +不会向 Apple 泄露其尚未拥有的数据。
+ +If a “Push Service” is available, Delta Chat enables Push Notifications +to achieve instant message delivery for all chatmail users.
+ +在 Delta Chat“通知”的“推送通知”设置中,您可以更改以下影响所有聊天配置文件的设置:
+ +使用后台连接:如果你没有使用推送服务, +你可以禁用 Delta Chat 的“电池优化”, +允许它在后台获取消息。 +但是,可能会有几分钟到几小时的延迟。 +一些 Android 供应商甚至完全限制应用 +(请参阅 dontkillmyapp.com), +并且 Delta Chat 可能不会显示传入的消息, +直到你手动再次打开应用为止。
+强制后台连接:如果之前的选项不可用或无法实现“即时传递”, +这是后备选项。 +启用它会在你的手机上导致永久通知, +这有时可能会被最新的 Android 手机“最小化”。
+如果消息到达时间延迟较长, +则“后台连接”选项都节能且安全,可以尝试。
+ +Delta Chat Push Notification support avoids leakage of private information. +It does not leak profile data, IP address or message content (not even encrypted) +to any system involved in the delivery of Push Notifications.
+ +以下是 Delta Chat 应用如何执行推送通知传递:
+ +Delta Chat 应用在本地获取“设备令牌”,对其进行加密并将其存储在 +Chatmail 服务器上。
+When a chatmail server receives a message for a Delta Chat user +it forwards the encrypted device token to the central Delta Chat notification proxy.
+The central Delta Chat notification proxy decrypts the device token +and forwards it to the respective Push service (Apple, Google, etc.), +without ever knowing the IP or profile data of Delta Chat users.
+The central Push Service (Apple, Google, etc.) +wakes up the Delta Chat app on your device +to check for new messages in the background. +It does not know about the profile data of the device it wakes up. +The central Apple/Google Push services never see any profile data (sender or receiver) +and also never see any message content (also not in encrypted forms).
+中央 Delta Chat 通知代理体积小,完全用 Rust 实现 +,并在 Apple/Google 等处理设备令牌后立即忘记它们, +通常在几毫秒内。
+ +Note that the device token is encrypted between apps and notification proxy +but it is not signed. +The notification proxy thus never sees profile data, IP-addresses or +any cryptographic identity information associated with a user’s device (token).
+ +由此产生的整体隐私设计,即使查封 Chatmail 服务器, +或完全查封中央 Delta Chat 通知代理 +也不会泄露推送服务尚未拥有的私人信息。
+ +Delta Chat 是一款免费且开源的去中心化即时通讯应用,用户可以自由选择服务器, +但我们希望用户可靠地体验到“即时消息传递”, +就像他们从 Whatsapp、Signal 或 Telegram 应用体验到的那样, +而无需预先提出更适合专家用户或开发人员的问题。
+ +Note that Delta Chat has a small and privacy-preserving Push Notification system +that achieves “instant delivery” of messages for all chatmail servers +including a potential one you might setup yourself without our permission. +Welcome to the power of the interoperable chatmail relay network :)
+ +是的,您可以在不同设备上使用相同的配置文件:
+ +确保两台设备都在同一个 Wi-Fi 或网络中
+在第一台设备上,转到设置 → 添加第二台设备,如果需要,解锁屏幕 +并稍等片刻,直到显示二维码
+在第二台设备上,安装 Delta Chat
+在第二台设备上,启动 Delta Chat,选择添加为第二台设备,然后扫描旧设备上的二维码
+传输应在几秒钟后开始,并且在传输过程中,两台设备都将显示进度。 +等待直到两台设备都完成。
+与其他许多即时通讯应用不同,在成功传输后, +两台设备完全独立。 +一台设备不是另一台设备工作的必要条件。
+ +仔细检查两台设备是否在同一个 Wi-Fi 或网络中
+在 Windows 上,转到控制面板 / 网络和 Internet +并确保专用网络被选为“网络配置文件类型” +(传输后,你可以更改回原始值)
+在 iOS 上,确保授予“系统设置 / 应用 / Delta Chat / 本地网络”访问权限
+在 macOS 上,启用“系统设置 / 隐私和安全 / 本地网络 / Delta Chat”
+你的系统可能具有“个人防火墙”, +已知这会引起问题(尤其是在 Windows 上)。 +在两端禁用个人防火墙以用于 Delta Chat,然后重试
+访客网络可能不允许设备相互通信。 +如果可能,请使用非访客网络。
+当设备间网络通信持续异常时, +建议采取设备直连方案:在一台终端开启 Mobile Hotspot(移动热点),另一台设备通过扫描 Wi-Fi 接入该临时网络。
+确保目标设备上有足够的存储空间
+如果传输已开始,请确保设备保持活动状态,并且不会进入睡眠状态。 +不要退出 Delta Chat。 +(我们努力使应用在后台工作,但不幸的是,系统倾向于杀死应用)
+目标设备上已登录 Delta Chat? +你可以在每台设备上使用多个配置文件,只需添加另一个配置文件
+如果你仍然遇到问题,或者无法扫描二维码 +,请尝试下面描述的手动传输
+仅当上述“添加第二台设备”方法不起作用时,才建议使用此方法。
+ +At Settings → Advanced → Experimental Features +you can try out features we are working on.
+ +The features may be unstable and may be changed or removed.
+ +You can find more information +and give feedback in the Forum.
+ +We would like to improve Delta Chat with your help, +which is why Delta Chat for Android asks whether you want +to send anonymous usage statistics.
+ +You can turn it on and off at +Settings → Advanced → Send statistics to Delta Chat’s developers.
+ +When you turn it on, +weekly statistics will be automatically sent to a bot.
+ +We are interested e.g. in statistics like:
+ +We will not collect any personally identifiable information about you.
+ +Yes, but only if the email address is used exclusively by chatmail clients.
+ +It is not supported to share usage of an email address with non-chatmail apps or web-based mailers, +for the following reasons:
+ +Non-chatmail apps are largely not accomplishing automatic end-to-end email encryption for their users, +while chatmail apps and relays pervasively enforce end-to-end encryption and security standards.
+Non-chatmail apps use email servers as a long-term message archive +while chatmail clients use email servers for ephemeral instant message relay.
+Supporting the full variety of classic email setups +would require considerable development and maintenance efforts, +and complicate making chatmail-based messaging more resilient, reliable and fast.
+First off, please do not use the same classic email address also from non-chatmail classic email apps +unless you are prepared to deal with encrypted messages in the inbox, +double notifications, accidentally deleted emails or similar annoyances.
+ +You can configure a email address for chatting at New Profile → Use Other Server → Use Classic Mail as Relay.
+Note that classic email providers will generally not support Push Notifications
+and have other limitations, see Provider Overview.
+Chatmail uses the default INBOX for relay; ensure the provider setup does too.
+A chat profile using a classic email address allows to to send and receive unencrypted messages.
+These messages, and the chats they appear in, are marked with an email icon
+
.
Any well behaving email server setup will do fine +except if your users’ devices require Google/Apple Push Notifications to work properly.
+ +We generally recommend to set up a chatmail relay. +Chatmail is a community-driven project that encompasses both the setup of relays +and core Rust developments +that power chatmail clients of which Delta Chat is the most well known.
+ +Delta Chat 使用 OpenPGP 标准的安全子集 +使用以下协议提供自动端到端加密:
+ +安全加入 +通过二维码扫描或“邀请链接”交换加密设置信息。
+Autocrypt is used for automatically +用于在联系人和群聊的所有成员之间自动建立端到端加密。
+将联系人分享到聊天中 + +接收者可以与该联系人使用端到端加密。
+Delta Chat 不会查询、发布或与任何 OpenPGP 密钥服务器交互。
+ +Delta Chat 中的所有消息 默认都采用端到端加密。 +自 Delta Chat 版本 2 发布系列(2025 年 7 月)起, +端到端加密消息上不再有锁或类似的标记。
+ +如果您使用默认的 chatmail 中继, +则不可能在没有端到端加密的情况下接收或发送消息。
+ +If you instead use a classic email server,
+you can send and receive messages with or without end-to-end encryption.
+Messages lacking end-to-end encryption are marked with an email icon
+
.
A contact profile might show a green checkmark
+
+and an “Introduced by” line.
+Every green-checkmarked contact either did a direct QR-scan with you
+or was introduced by a another green-checkmarked contact.
+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 QR-scan.
有关“保证的端到端加密”的更深入讨论, +请参阅 安全加入协议, +并专门阅读有关“已验证群组”的内容,这是 +此处所谓的“带有绿色复选标记”或“保证的端到端加密”聊天的技术术语。
+ +是的。
+ +当我们谈论“端到端加密消息”时, +我们始终指的是整个消息都已加密, +包括所有附件和附件元数据,例如文件名。
+ +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.
+ +OpenPGP 加密标准本身不存在安全隐患。 +目前公众讨论中涉及的 OpenPGP 安全问题, +大多源自相关工具或应用的用户体验缺陷或技术实现漏洞(或二者叠加)。 +需特别澄清的是:OpenPGP 作为 IETF 制定的加密标准, +与基于命令行操作的 GnuPG(GPG)工具不可混为一谈。 +诸多对 OpenPGP 的质疑实际指向 GnuPG 工具,而 Delta Chat 即时通讯应用从未采用该工具。 +Delta Chat 实际使用的是 Rust 语言编写的 OpenPGP 实现库 rPGP, +该库以独立 “pgp” 组件包形式提供, +且已通过 2019 和 2024 年两次安全审计。
+ +我们的目标是与其他 OpenPGP 实现者一起, +通过实施 新的 IETF OpenPGP Crypto-Refresh +来进一步提高安全特性,该标准已于 2023 年夏季获得通过,令人欣慰。
+ +Yes, we are following efforts like MLS +but adopting them would mean breaking end-to-end encryption interoperability. +So it would not be a light decision to take +and there must be tangible improvements for users.
+ +Delta Chat 采用整体“可用安全性”方法, +并与广泛的活动家团体以及 +TeamUSEC 等知名研究人员合作 +,以改进针对安全威胁的实际用户结果。 +用于建立端到端加密的线路协议和标准 +只是“用户结果”的一部分, +另请参阅我们对 设备查封 +和 消息元数据 问题的回答。
+ +不,Delta Chat 从未受到任何 EFAIL 攻击 +因为所使用的 OpenPGP 实现了 rPGP +在加密消息时“修改检测代码” +并且如果“修改检测代码”不正确则返回 错误。
+ +Delta Chat 也从未容易受到“直接泄露”EFAIL 攻击,
+因为它只解密 multipart/encrypted 消息,
+这些消息正好包含一个加密和签名的部分,
+如 Autocrypt Level 1 规范所定义。
If you are sending or receiving email messages without end-to-end encryption (using a classic email server), +they are still protected from cell or cable companies who can not read or modify your email messages. +But both your and your recipient’s email providers +may read, analyze or modify your messages, including any attachments.
+ +Delta Chat by default uses strict +TLS encryption +which secures connections between your device and your email provider. +All of Delta Chat’s TLS-handling has been independently security audited. +Moreover, the connection between your and the recipient’s email provider +will typically be transport-encrypted as well. +If the involved email servers support MTA-STS +then transport encryption will be enforced between email providers +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.
+ +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.
+ +Servers can therefore only see:
+ +By default, the addresses are randomly generated.
+ +All other message, contact and group metadata resides in the end-to-end encrypted part of messages.
+ +Both for protecting against metadata-collecting servers +as well as against the threat of device seizure +we recommend to use a chatmail relay +to create chat profiles using random 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.
+ +No, not yet.
+ +The Signal messenger introduced “Sealed Sender” in 2018 +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.
+ +Even if chatmail relays +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 addresses for sealed sending +but an implementation has not been agreed as a priority yet.
+ +No, not yet.
+ +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.
+ +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 chatmail core, +which would make it available in all chatmail clients.
+ +No, not yet.
+ +Delta Chat uses the Rust OpenPGP library rPGP +which supports the latest IETF Post-Quantum-Cryptography OpenPGP draft. +We aim to add PQC support in chatmail core after the draft is finalized at the IETF +in collaboration with other OpenPGP implementers.
+ +你可以在“加密”对话框中手动检查端到端加密状态 +(Android/iOS 上的用户配置文件或桌面上的用户聊天列表项上右键单击)。 +Delta Chat 在此处显示两个指纹。 +如果相同的指纹出现在你自己的设备和你联系人的设备上, +则连接是安全的。
+ +不。
+ +Delta Chat generates secure OpenPGP keys according to the Autocrypt specification 1.1. +We do not recommend or offer users to perform manual key management. +We want to ensure that security audits can focus on a few proven cryptographic algorithms +instead of the full breadth of possible algorithms allowed with OpenPGP. +If you want to extract your OpenPGP key, there only is an expert method: +you need to look it up in the “keypairs” SQLite table of a profile backup tar-file.
+ +确实如此,且已进行多次。 +Delta Chat 长期接受第三方独立机构的安全审计与漏洞分析, +以下按时间倒序列出历年检测记录:
+ +2024年12月,网络安全机构Radically Open Security 受NLNET委托,完成了对加密协议rPGP的专项审计。 +作为即时通讯工具Delta Chat的核心加密引擎,rPGP采用OpenPGP 标准实现端到端加密。 +基于审计发现,研究团队同步公开了两份技术通告:
+自 2024 年 12 月之后,各应用商店发布的 Delta Chat 版本均已修复上述安全公告提及的问题。 +相关更新作为常规版本升级的一部分,现已全面覆盖所有 appstore 平台。
+ +2024 年 3 月,我们收到了苏黎世联邦理工学院应用密码学 +研究小组的深入安全性分析,并解决了所有提出的问题。 +有关更多详细信息,请参阅我们关于 加强保证的端到端加密 的博客文章以及 +之后发表的 Delta Chat 密码学分析 +研究论文。
+2023 年 4 月,我们修复了“在聊天中共享的 Web 应用”的安全性 +和隐私问题,这些问题与沙箱故障有关,尤其是在 Chromium 中。 随后,我们获得了 Cure53 的独立安全 +审计,并且在 2023 年 4 月发布的 1.36 应用系列中修复了发现的所有问题。 +请参阅 此处,了解有关 Web 中端到端安全性的完整背景故事。
+2023 年 3 月,Cure53 分析了 Delta Chat 网络连接的传输加密和一个可重现的邮件服务器设置,如 +本网站 推荐的那样。 +你可以在 我们的博客 上阅读有关审计的更多信息 +,或在此处阅读 完整报告。
+2020 年,Include Security 分析了 Delta Chat 的 Rust 核心、 +IMAP、 +SMTP 和 +TLS 库。 +它没有发现任何严重或高严重性问题。 +该报告提出了一些中等严重性的弱点 - +它们本身不会对 Delta Chat 用户构成威胁, +因为它们取决于 Delta Chat 使用的环境。 +出于可用性和兼容性原因, +我们无法减轻所有这些弱点, +并决定向受威胁的用户提供安全建议。 +你可以在 此处阅读完整报告。
+2019 年,Include Security 分析了 Delta +Chat 的 PGP 和 +RSA 库。 +它没有发现任何严重问题, +但发现了两个高严重性问题,我们随后修复了这些问题。 +它还揭示了一个中等严重性和一些不太严重的问题, +但在 Delta Chat 实现中无法利用这些漏洞。 +尽管如此,自审计结束以来,我们仍然修复了其中一些问题。 +你可以在 此处阅读完整报告。
+Some features require certain permissions, +e.g. you need to grant camera permission if you want to scan an invite QR code.
+ +See Privacy Policy for a detailed overview.
+ +Delta Chat 适用于所有主要平台和一些次要平台:
+ +官方网站,https://delta.chat/download 详细显示所有选项
+如果不可用,请使用 镜像 https://deltachat.github.io/deltachat-pages
+Open one of the following app stores and search for “Delta Chat”: +Google Play Store, F-Droid, Huawei App Gallery, iOS and macOS App Store, Microsoft Store
+检查你的 Linux 发行版的 软件包管理器
+Android APK 也可在 https://github.com/deltachat/deltachat-android/releases 上获得
+Delta Chat 没有接受风险投资,也没有负债累累,更没有承受产生巨额利润或将用户及其朋友和家人卖给广告商(或更糟)的压力。我们宁愿使用目前来自欧盟和美国的公共资金,来帮助我们努力建立一个基于自由开源社区开发的、去中心化的、多样化的聊天消息软件生态系统。
+ +具体而言,Delta Chat 的开发迄今为止已从以下来源获得资金, +按时间顺序排列:
+ +NEXTLEAP欧盟项目资助了以下研究和实施工作:在 2017 年和 2018 年实施的验证组和设置联系协议和通过 Autocrypt整合了端到端加密。
+在开放技术基金 2018/2019 年提供的第一笔赠款(约 20 万美元)期间,我们显著改善了安卓应用,发布了第一个桌面测试版,并根据人权方面的用户体验研究进行了功能开发,请参阅我们的结论《需求发现与用户体验报告》。2019/2020 年的第二笔赠款(约 30 万美元)对发布 Delta/iOS 版本,将核心库转换到 Rust ,以及为所有平台开发新功能提供了帮助。
+NLnet 基金会 2019/2020 年拨款 4.6 万欧元,用于完成 Rust/Python 绑定并建立聊天机器人生态系统。
+In 2021 we received further EU funding for two Next-Generation-Internet +proposals, namely for EPPD - email provider portability directory (~97K EUR) and AEAP - email address porting (~90K EUR) which resulted in better multi-profile support, improved QR-code contact and group setups and many networking improvements on all platforms.
+From End 2021 till March 2023 we received Internet Freedom funding (500K USD) from the +U.S. Bureau of Democracy, Human Rights and Labor (DRL). +This funding supported our long-running goals to make Delta Chat more usable +and compatible with a wide range of email servers world-wide, and more resilient and secure +in places often affected by internet censorship and shutdowns.
+2023-2024 年,我们成功完成了 OTF 资助的 +安全 Chatmail 项目, +使我们能够引入保证的加密, +创建一个 Chatmail 服务器网络, +并在 2024 年 4 月起发布的所有应用中提供“即时入职”。
+在 2023 年和 2024 年,我们的 WebXDC PUSH 工作已在下一代互联网 (NGI) 中获得认可, +并与致力于 +WebXDC evolve、 +WebXDC XMPP、 +DeltaTouch 和 +DeltaTauri 的合作伙伴合作。 +所有这些项目都已部分完成或将在 2025 年初完成。
+我们有时会收到个人的一次性捐款。 例如,2021 年,一位慷慨的人士以 “继续保持良好的发展态势!”为主题通过银行向我们捐赠了4千欧元💜。 我们用这些钱来资助发展活动或支付不容易预测或从公共基金中报销的临时费用。收到更多的捐款也有助于我们作为一个贡献者社区变得更加独立和长期可持续。
+ + +最后但并非最不重要的是,数位专家与热心人在没有收到或仅收到少量金钱的情况下为 Delta Chat 的开发做出了贡献。没有他们,Delta Chat 不会发展到、甚至无法接近目前的状况。
+上面提到的钱款资助主要是由在弗赖堡(德国)的 merlinux GmbH 组织的,分发给了来自世界各地的十多位贡献者。
+ +请参阅 Delta Chat 捐款渠道 +以了解货币捐款和其他捐款的可能性。
+ + + + + \ No newline at end of file diff --git a/src/main/assets/webxdc/maps.xdc b/src/main/assets/webxdc/maps.xdc new file mode 100644 index 0000000000000000000000000000000000000000..b62f13a460f24147e6b815372d8ec1b341a2a104 Binary files /dev/null and b/src/main/assets/webxdc/maps.xdc differ diff --git a/src/main/ic_launcher-playstore.png b/src/main/ic_launcher-playstore.png new file mode 100644 index 0000000000000000000000000000000000000000..9ef22ffea785afb4e2742ab2ae8478cd535c6e82 Binary files /dev/null and b/src/main/ic_launcher-playstore.png differ diff --git a/src/main/java/chat/delta/rpc/BaseTransport.java b/src/main/java/chat/delta/rpc/BaseTransport.java new file mode 100644 index 0000000000000000000000000000000000000000..971bb130fcf234ae93762e5fb74e7dd8c7a4d593 --- /dev/null +++ b/src/main/java/chat/delta/rpc/BaseTransport.java @@ -0,0 +1,124 @@ +/* Autogenerated file, do not edit manually */ +package chat.delta.rpc; + +import chat.delta.util.SettableFuture; + +import com.fasterxml.jackson.core.JsonProcessingException; +import com.fasterxml.jackson.core.type.TypeReference; +import com.fasterxml.jackson.databind.JsonNode; +import com.fasterxml.jackson.databind.ObjectMapper; + +import java.io.IOException; +import java.util.Map; +import java.util.concurrent.ConcurrentHashMap; +import java.util.concurrent.ExecutionException; + +/* Basic RPC Transport implementation */ +public abstract class BaseTransport implements Rpc.Transport { + private final Map+ * If no events have happened since the last `get_next_event` + * (i.e. if the event queue is empty), the response will be returned + * only when a new event fires. + *
+ * Note that if you are using the `BaseDeltaChat` JavaScript class
+ * or the `Rpc` Python class, this function will be invoked
+ * by those classes internally and should not be used manually.
+ */
+ public Event getNextEvent() throws RpcException {
+ return transport.callForResult(new TypeReference
+ * The `AccountsBackgroundFetchDone` event is emitted at the end even in case of timeout.
+ * Process all events until you get this one and you can safely return to the background
+ * without forgetting to create notifications caused by timing race conditions.
+ */
+ public void backgroundFetch(Float timeoutInSeconds) throws RpcException {
+ transport.call("background_fetch", mapper.valueToTree(timeoutInSeconds));
+ }
+
+ public void stopBackgroundFetch() throws RpcException {
+ transport.call("stop_background_fetch");
+ }
+
+ /* Starts background tasks for a single account. */
+ public void startIo(Integer accountId) throws RpcException {
+ transport.call("start_io", mapper.valueToTree(accountId));
+ }
+
+ /* Stops background tasks for a single account. */
+ public void stopIo(Integer accountId) throws RpcException {
+ transport.call("stop_io", mapper.valueToTree(accountId));
+ }
+
+ /* Get top-level info for an account. */
+ public Account getAccountInfo(Integer accountId) throws RpcException {
+ return transport.callForResult(new TypeReference
+ * This function looks up domain in offline database.
+ *
+ * For compatibility, email address can be passed to this function
+ * instead of the domain.
+ */
+ public ProviderInfo getProviderInfo(Integer accountId, String email) throws RpcException {
+ return transport.callForResult(new TypeReference
+ * This function is useful because the key-contacts migration could fail due to bugs
+ * and then the account will not work properly.
+ *
+ * After opening an account, the UI should call this function
+ * and show the error string if one is returned.
+ */
+ public String getMigrationError(Integer accountId) throws RpcException {
+ return transport.callForResult(new TypeReference
+ * Internally, the function will call dc_set_config() with the appropriate keys,
+ */
+ public void setConfigFromQr(Integer accountId, String qrContent) throws RpcException {
+ transport.call("set_config_from_qr", mapper.valueToTree(accountId), mapper.valueToTree(qrContent));
+ }
+
+ public Qr checkQr(Integer accountId, String qrContent) throws RpcException {
+ return transport.callForResult(new TypeReference
+ * Deprecated as of 2025-02; use `add_transport_from_qr()`
+ * or `add_or_update_transport()` instead.
+ */
+ public void configure(Integer accountId) throws RpcException {
+ transport.call("configure", mapper.valueToTree(accountId));
+ }
+
+ /**
+ * Configures a new email account using the provided parameters
+ * and adds it as a transport.
+ *
+ * If the email address is the same as an existing transport,
+ * then this existing account will be reconfigured instead of a new one being added.
+ *
+ * This function stops and starts IO as needed.
+ *
+ * Usually it will be enough to only set `addr` and `password`,
+ * and all the other settings will be autoconfigured.
+ *
+ * During configuration, ConfigureProgress events are emitted;
+ * they indicate a successful configuration as well as errors
+ * and may be used to create a progress bar.
+ * This function will return after configuration is finished.
+ *
+ * If configuration is successful,
+ * the working server parameters will be saved
+ * and used for connecting to the server.
+ * The parameters entered by the user will be saved separately
+ * so that they can be prefilled when the user opens the server-configuration screen again.
+ *
+ * See also:
+ * - [Self::is_configured()] to check whether there is
+ * at least one working transport.
+ * - [Self::add_transport_from_qr()] to add a transport
+ * from a server encoded in a QR code.
+ * - [Self::list_transports()] to get a list of all configured transports.
+ * - [Self::delete_transport()] to remove a transport.
+ */
+ public void addOrUpdateTransport(Integer accountId, EnteredLoginParam param) throws RpcException {
+ transport.call("add_or_update_transport", mapper.valueToTree(accountId), mapper.valueToTree(param));
+ }
+
+ /* Deprecated 2025-04. Alias for [Self::add_or_update_transport()]. */
+ public void addTransport(Integer accountId, EnteredLoginParam param) throws RpcException {
+ transport.call("add_transport", mapper.valueToTree(accountId), mapper.valueToTree(param));
+ }
+
+ /**
+ * Adds a new email account as a transport
+ * using the server encoded in the QR code.
+ * See [Self::add_or_update_transport].
+ */
+ public void addTransportFromQr(Integer accountId, String qr) throws RpcException {
+ transport.call("add_transport_from_qr", mapper.valueToTree(accountId), mapper.valueToTree(qr));
+ }
+
+ /**
+ * Returns the list of all email accounts that are used as a transport in the current profile.
+ * Use [Self::add_or_update_transport()] to add or change a transport
+ * and [Self::delete_transport()] to delete a transport.
+ */
+ public java.util.List
+ * Messages belonging to muted chats or to the contact requests are not returned;
+ * these messages should not be notified
+ * and also badge counters should not include these messages.
+ *
+ * To get the number of fresh messages for a single chat, muted or not,
+ * use `get_fresh_msg_cnt()`.
+ */
+ public java.util.List
+ * If the specified chat is muted,
+ * the UI should show the badge counter "less obtrusive",
+ * e.g. using "gray" instead of "red" color.
+ */
+ public Integer getFreshMsgCnt(Integer accountId, Integer chatId) throws RpcException {
+ return transport.callForResult(new TypeReference
+ * Only messages with database ID higher than `last_msg_id` config value
+ * are returned. After processing the messages, the bot should
+ * update `last_msg_id` by calling [`markseen_msgs`]
+ * or manually updating the value to avoid getting already
+ * processed messages.
+ *
+ * [`markseen_msgs`]: Self::markseen_msgs
+ */
+ public java.util.List
+ * This function is similar to [`get_next_msgs`],
+ * but waits for internal new message notification before returning.
+ * New message notification is sent when new message is added to the database,
+ * on initialization, when I/O is started and when I/O is stopped.
+ * This allows bots to use `wait_next_msgs` in a loop to process
+ * old messages after initialization and during the bot runtime.
+ * To shutdown the bot, stopping I/O can be used to interrupt
+ * pending or next `wait_next_msgs` call.
+ *
+ * [`get_next_msgs`]: Self::get_next_msgs
+ */
+ public java.util.List
+ * Experimental API, subject to change without notice.
+ */
+ public java.util.List
+ * Messages are deleted from the device and the chat database entry is deleted.
+ * After that, the event #DC_EVENT_MSGS_CHANGED is posted.
+ *
+ * Things that are _not done_ implicitly:
+ *
+ * - Messages are **not deleted from the server**.
+ * - The chat or the contact is **not blocked**, so new messages from the user/the group may appear as a contact request
+ * and the user may create the chat again.
+ * - **Groups are not left** - this would
+ * be unexpected as (1) deleting a normal chat also does not prevent new mails
+ * from arriving, (2) leaving a group requires sending a message to
+ * all group members - especially for groups not used for a longer time, this is
+ * really unexpected when deletion results in contacting all members again,
+ * (3) only leaving groups is also a valid usecase.
+ *
+ * To leave a chat explicitly, use leave_group()
+ */
+ public void deleteChat(Integer accountId, Integer chatId) throws RpcException {
+ transport.call("delete_chat", mapper.valueToTree(accountId), mapper.valueToTree(chatId));
+ }
+
+ /**
+ * Get encryption info for a chat.
+ * Get a multi-line encryption info, containing encryption preferences of all members.
+ * Can be used to find out why messages sent to group are not encrypted.
+ *
+ * returns Multi-line text
+ */
+ public String getChatEncryptionInfo(Integer accountId, Integer chatId) throws RpcException {
+ return transport.callForResult(new TypeReference
+ * If `chat_id` is a group chat ID, SecureJoin QR code for the group is returned.
+ * If `chat_id` is unset, setup contact QR code is returned.
+ */
+ public String getChatSecurejoinQrCode(Integer accountId, Integer chatId) throws RpcException {
+ return transport.callForResult(new TypeReference
+ * The scanning device will pass the scanned content to `checkQr()` then;
+ * if `checkQr()` returns `askVerifyContact` or `askVerifyGroup`
+ * an out-of-band-verification can be joined using `secure_join()`
+ *
+ * chat_id: If set to a group-chat-id,
+ * the Verified-Group-Invite protocol is offered in the QR code;
+ * works for protected groups as well as for normal groups.
+ * If not set, the Setup-Contact protocol is offered in the QR code.
+ * See https://securejoin.delta.chat/ for details about both protocols.
+ *
+ * return format: `[code, svg]`
+ */
+ public Pair
+ * The function returns immediately and the handshake runs in background,
+ * sending and receiving several messages.
+ * During the handshake, info messages are added to the chat,
+ * showing progress, success or errors.
+ *
+ * Subsequent calls of `secure_join()` will abort previous, unfinished handshakes.
+ *
+ * See https://securejoin.delta.chat/ for details about both protocols.
+ *
+ * **qr**: The text of the scanned QR code. Typically, the same string as given
+ * to `check_qr()`.
+ *
+ * **returns**: The chat ID of the joined chat, the UI may redirect to the this chat.
+ * A returned chat ID does not guarantee that the chat is protected or the belonging contact is verified.
+ *
+ */
+ public Integer secureJoin(Integer accountId, String qr) throws RpcException {
+ return transport.callForResult(new TypeReference
+ * **source**: The source where the QR code came from.
+ * E.g. a link that was clicked inside or outside Delta Chat,
+ * the "Paste from Clipboard" action,
+ * the "Load QR code as image" action,
+ * or a QR code scan.
+ *
+ * **uipath**: Which UI path did the user use to arrive at the QR code screen.
+ * If the SecurejoinSource was ExternalLink or InternalLink,
+ * pass `None` here, because the QR code screen wasn't even opened.
+ * ```
+ */
+ public Integer secureJoinWithUxInfo(Integer accountId, String qr, SecurejoinSource source, SecurejoinUiPath uipath) throws RpcException {
+ return transport.callForResult(new TypeReference
+ * If the group is already _promoted_ (any message was sent to the group),
+ * all group members are informed by a special status message that is sent automatically by this function.
+ *
+ * Sends out #DC_EVENT_CHAT_MODIFIED and #DC_EVENT_MSGS_CHANGED if a status message was sent.
+ */
+ public void removeContactFromChat(Integer accountId, Integer chatId, Integer contactId) throws RpcException {
+ transport.call("remove_contact_from_chat", mapper.valueToTree(accountId), mapper.valueToTree(chatId), mapper.valueToTree(contactId));
+ }
+
+ /**
+ * Add a member to a group.
+ *
+ * If the group is already _promoted_ (any message was sent to the group),
+ * all group members are informed by a special status message that is sent automatically by this function.
+ *
+ * If the group has group protection enabled, only verified contacts can be added to the group.
+ *
+ * Sends out #DC_EVENT_CHAT_MODIFIED and #DC_EVENT_MSGS_CHANGED if a status message was sent.
+ */
+ public void addContactToChat(Integer accountId, Integer chatId, Integer contactId) throws RpcException {
+ transport.call("add_contact_to_chat", mapper.valueToTree(accountId), mapper.valueToTree(chatId), mapper.valueToTree(contactId));
+ }
+
+ /**
+ * Get the contact IDs belonging to a chat.
+ *
+ * - for normal chats, the function always returns exactly one contact,
+ * DC_CONTACT_ID_SELF is returned only for SELF-chats.
+ *
+ * - for group chats all members are returned, DC_CONTACT_ID_SELF is returned
+ * explicitly as it may happen that oneself gets removed from a still existing
+ * group
+ *
+ * - for broadcast channels, all recipients are returned, DC_CONTACT_ID_SELF is not included
+ *
+ * - for mailing lists, the behavior is not documented currently, we will decide on that later.
+ * for now, the UI should not show the list for mailing lists.
+ * (we do not know all members and there is not always a global mailing list address,
+ * so we could return only SELF or the known members; this is not decided yet)
+ */
+ public java.util.List
+ * After creation,
+ * the group has one member with the ID DC_CONTACT_ID_SELF
+ * and is in _unpromoted_ state.
+ * This means, you can add or remove members, change the name,
+ * the group image and so on without messages being sent to all group members.
+ *
+ * This changes as soon as the first message is sent to the group members
+ * and the group becomes _promoted_.
+ * After that, all changes are synced with all group members
+ * by sending status message.
+ *
+ * To check, if a chat is still unpromoted, you can look at the `is_unpromoted` property of `BasicChat` or `FullChat`.
+ * This may be useful if you want to show some help for just created groups.
+ *
+ * `protect` argument is deprecated as of 2025-10-22 and is left for compatibility.
+ * Pass `false` here.
+ */
+ public Integer createGroupChat(Integer accountId, String name, Boolean protect) throws RpcException {
+ return transport.callForResult(new TypeReference
+ * Same as [`Self::create_group_chat`], but the chat is unencrypted and can only have
+ * address-contacts.
+ */
+ public Integer createGroupChatUnencrypted(Integer accountId, String name) throws RpcException {
+ return transport.callForResult(new TypeReference
+ * Broadcast channels are similar to groups on the sending device,
+ * however, recipients get the messages in a read-only chat
+ * and will not see who the other members are.
+ *
+ * Called `broadcast` here rather than `channel`,
+ * because the word "channel" already appears a lot in the code,
+ * which would make it hard to grep for it.
+ *
+ * After creation, the chat contains no recipients and is in _unpromoted_ state;
+ * see [`CommandApi::create_group_chat`] for more information on the unpromoted state.
+ *
+ * Returns the created chat's id.
+ */
+ public Integer createBroadcast(Integer accountId, String chatName) throws RpcException {
+ return transport.callForResult(new TypeReference
+ * If the group is already _promoted_ (any message was sent to the group),
+ * all group members are informed by a special status message that is sent automatically by this function.
+ *
+ * Sends out #DC_EVENT_CHAT_MODIFIED and #DC_EVENT_MSGS_CHANGED if a status message was sent.
+ */
+ public void setChatName(Integer accountId, Integer chatId, String newName) throws RpcException {
+ transport.call("set_chat_name", mapper.valueToTree(accountId), mapper.valueToTree(chatId), mapper.valueToTree(newName));
+ }
+
+ /**
+ * Set group profile image.
+ *
+ * If the group is already _promoted_ (any message was sent to the group),
+ * all group members are informed by a special status message that is sent automatically by this function.
+ *
+ * Sends out #DC_EVENT_CHAT_MODIFIED and #DC_EVENT_MSGS_CHANGED if a status message was sent.
+ *
+ * To find out the profile image of a chat, use dc_chat_get_profile_image()
+ *
+ * @param image_path Full path of the image to use as the group image. The image will immediately be copied to the
+ * `blobdir`; the original image will not be needed anymore.
+ * If you pass null here, the group image is deleted (for promoted groups, all members are informed about
+ * this change anyway).
+ */
+ public void setChatProfileImage(Integer accountId, Integer chatId, String imagePath) throws RpcException {
+ transport.call("set_chat_profile_image", mapper.valueToTree(accountId), mapper.valueToTree(chatId), mapper.valueToTree(imagePath));
+ }
+
+ public void setChatVisibility(Integer accountId, Integer chatId, ChatVisibility visibility) throws RpcException {
+ transport.call("set_chat_visibility", mapper.valueToTree(accountId), mapper.valueToTree(chatId), mapper.valueToTree(visibility));
+ }
+
+ public void setChatEphemeralTimer(Integer accountId, Integer chatId, Integer timer) throws RpcException {
+ transport.call("set_chat_ephemeral_timer", mapper.valueToTree(accountId), mapper.valueToTree(chatId), mapper.valueToTree(timer));
+ }
+
+ public Integer getChatEphemeralTimer(Integer accountId, Integer chatId) throws RpcException {
+ return transport.callForResult(new TypeReference
+ * Sends the `MsgsChanged` event on success.
+ *
+ * Setting msg to None will prevent the device message with this label from being added in the future.
+ */
+ public Integer addDeviceMessage(Integer accountId, String label, MessageData msg) throws RpcException {
+ return transport.callForResult(new TypeReference
+ * Calling this function usually results in the event #DC_EVENT_MSGS_NOTICED.
+ * See also markseen_msgs().
+ */
+ public void marknoticedChat(Integer accountId, Integer chatId) throws RpcException {
+ transport.call("marknoticed_chat", mapper.valueToTree(accountId), mapper.valueToTree(chatId));
+ }
+
+ /**
+ * Returns the message that is immediately followed by the last seen
+ * message.
+ * From the point of view of the user this is effectively
+ * "first unread", but in reality in the database a seen message
+ * _can_ be followed by a fresh (unseen) message
+ * if that message has not been individually marked as seen.
+ */
+ public Integer getFirstUnreadMessageOfChat(Integer accountId, Integer chatId) throws RpcException {
+ return transport.callForResult(new TypeReference
+ * The UI can then call is_chat_muted() when receiving a new message
+ * to decide whether it should trigger an notification.
+ *
+ * Muted chats should not sound or vibrate
+ * and should not show a visual notification in the system area.
+ * Moreover, muted chats should be excluded from global badge counter
+ * (get_fresh_msgs() skips muted chats therefore)
+ * and the in-app, per-chat badge counter should use a less obtrusive color.
+ *
+ * Sends out #DC_EVENT_CHAT_MODIFIED.
+ */
+ public void setChatMuteDuration(Integer accountId, Integer chatId, MuteDuration duration) throws RpcException {
+ transport.call("set_chat_mute_duration", mapper.valueToTree(accountId), mapper.valueToTree(chatId), mapper.valueToTree(duration));
+ }
+
+ /**
+ * Check whether the chat is currently muted (can be changed by set_chat_mute_duration()).
+ *
+ * This is available as a standalone function outside of fullchat, because it might be only needed for notification
+ */
+ public Boolean isChatMuted(Integer accountId, Integer chatId) throws RpcException {
+ return transport.callForResult(new TypeReference
+ * - For normal chats, the IMAP state is updated, MDN is sent
+ * (if set_config()-options `mdns_enabled` is set)
+ * and the internal state is changed to @ref DC_STATE_IN_SEEN to reflect these actions.
+ *
+ * - For contact requests, no IMAP or MDNs is done
+ * and the internal state is not changed therefore.
+ * See also marknoticed_chat().
+ *
+ * Moreover, timer is started for incoming ephemeral messages.
+ * This also happens for contact requests chats.
+ *
+ * This function updates `last_msg_id` configuration value
+ * to the maximum of the current value and IDs passed to this function.
+ * Bots which mark messages as seen can rely on this side effect
+ * to avoid updating `last_msg_id` value manually.
+ *
+ * One #DC_EVENT_MSGS_NOTICED event is emitted per modified chat.
+ */
+ public void markseenMsgs(Integer accountId, java.util.List
+ * * `add_daymarker` - If `true`, add day markers as `DC_MSG_ID_DAYMARKER` to the result,
+ * e.g. [1234, 1237, 9, 1239]. The day marker timestamp is the midnight one for the
+ * corresponding (following) day in the local timezone.
+ */
+ public java.util.List
+ * Returns IDs of existing messages.
+ */
+ public java.util.List
+ * this is the batch variant of [get_message]
+ */
+ public java.util.Map
+ * The max. text returned is typically longer (about 100000 characters) than the
+ * max. text returned by dc_msg_get_text() (about 30000 characters).
+ */
+ public String getMessageInfo(Integer accountId, Integer messageId) throws RpcException {
+ return transport.callForResult(new TypeReference
+ * On success, the @ref DC_MSG "view type of the message" may change
+ * or the message may be replaced completely by one or more messages with other message IDs.
+ * That may happen e.g. in cases where the message was encrypted
+ * and the type could not be determined without fully downloading.
+ * Downloaded content can be accessed as usual after download.
+ *
+ * To reflect these changes a @ref DC_EVENT_MSGS_CHANGED event will be emitted.
+ */
+ public void downloadFullMessage(Integer accountId, Integer messageId) throws RpcException {
+ transport.call("download_full_message", mapper.valueToTree(accountId), mapper.valueToTree(messageId));
+ }
+
+ /**
+ * Search messages containing the given query string.
+ * Searching can be done globally (chat_id=None) or in a specified chat only (chat_id set).
+ *
+ * Global search results are typically displayed using dc_msg_get_summary(), chat
+ * search results may just highlight the corresponding messages and present a
+ * prev/next button.
+ *
+ * For the global search, the result is limited to 1000 messages,
+ * this allows an incremental search done fast.
+ * So, when getting exactly 1000 messages, the result actually may be truncated;
+ * the UIs may display sth. like "1000+ messages found" in this case.
+ * The chat search (if chat_id is set) is not limited.
+ */
+ public java.util.List
+ * This will always create or look up an address-contact,
+ * i.e. a contact identified by an email address,
+ * with all messages sent to and from this contact being unencrypted.
+ * If the user just clicked on an email address,
+ * you should first check [`Self::lookup_contact_id_by_addr`]/`lookupContactIdByAddr.`,
+ * and only if there is no contact yet, call this function here.
+ *
+ * Returns contact id of the created or existing contact.
+ */
+ public Integer createContact(Integer accountId, String email, String name) throws RpcException {
+ return transport.callForResult(new TypeReference
+ * By default, key-contacts are listed.
+ *
+ * * `list_flags` - A combination of flags:
+ * - `DC_GCL_ADD_SELF` - Add SELF unless filtered by other parameters.
+ * - `DC_GCL_ADDRESS` - List address-contacts instead of key-contacts.
+ * * `query` - A string to filter the list.
+ */
+ public java.util.List
+ * Formerly called `getContacts2` in Desktop.
+ * See [`Self::get_contact_ids`] for parameters and more info.
+ */
+ public java.util.List
+ * **POTENTIAL SECURITY ISSUE**: If there are multiple contacts with this address
+ * (e.g. an address-contact and a key-contact),
+ * this looks up the most recently seen contact,
+ * i.e. which contact is returned depends on which contact last sent a message.
+ * If the user just clicked on a mailto: link, then this is the best thing you can do.
+ * But **DO NOT** internally represent contacts by their email address
+ * and do not use this function to look them up;
+ * otherwise this function will sometimes look up the wrong contact.
+ * Instead, you should internally represent contacts by their ids.
+ *
+ * To validate an e-mail address independently of the contact database
+ * use check_email_validity().
+ */
+ public Integer lookupContactIdByAddr(Integer accountId, String addr) throws RpcException {
+ return transport.callForResult(new TypeReference
+ * Returns the ids of created/modified contacts in the order they appear in the vCard.
+ */
+ public java.util.List
+ * Returns the ids of created/modified contacts in the order they appear in the vCard.
+ */
+ public java.util.List
+ * If it does not exist, `None` is returned.
+ */
+ public Integer getChatIdByContactId(Integer accountId, Integer contactId) throws RpcException {
+ return transport.callForResult(new TypeReference
+ * The list is already sorted and starts with the oldest message.
+ * Clients should not try to re-sort the list as this would be an expensive action
+ * and would result in inconsistencies between clients.
+ *
+ * Setting `chat_id` to `None` (`null` in typescript) means get messages with media
+ * from any chat of the currently used account.
+ */
+ public java.util.List
+ * Can be canceled by stopping the ongoing process. Success or failure can be tracked
+ * via the `ImexProgress` event which should either reach `1000` for success or `0` for
+ * failure.
+ *
+ * This **stops IO** while it is running.
+ *
+ * Returns once a remote device has retrieved the backup, or is canceled.
+ */
+ public void provideBackup(Integer accountId) throws RpcException {
+ transport.call("provide_backup", mapper.valueToTree(accountId));
+ }
+
+ /**
+ * Returns the text of the QR code for the running [`CommandApi::provide_backup`].
+ *
+ * This QR code text can be used in [`CommandApi::get_backup`] on a second device to
+ * retrieve the backup and setup this second device.
+ *
+ * This call will block until the QR code is ready,
+ * even if there is no concurrent call to [`CommandApi::provide_backup`],
+ * but will fail after 60 seconds to avoid deadlocks.
+ */
+ public String getBackupQr(Integer accountId) throws RpcException {
+ return transport.callForResult(new TypeReference
+ * This QR code can be used in [`CommandApi::get_backup`] on a second device to
+ * retrieve the backup and setup this second device.
+ *
+ * This call will block until the QR code is ready,
+ * even if there is no concurrent call to [`CommandApi::provide_backup`],
+ * but will fail after 60 seconds to avoid deadlocks.
+ *
+ * Returns the QR code rendered as an SVG image.
+ */
+ public String getBackupQrSvg(Integer accountId) throws RpcException {
+ return transport.callForResult(new TypeReference
+ * This retrieves the backup from a remote device over the network and imports it into
+ * the current device.
+ *
+ * Can be canceled by stopping the ongoing process.
+ *
+ * Do not forget to call start_io on the account after a successful import,
+ * otherwise it will not connect to the email server.
+ */
+ public void getBackup(Integer accountId, String qrText) throws RpcException {
+ transport.call("get_backup", mapper.valueToTree(accountId), mapper.valueToTree(qrText));
+ }
+
+ /**
+ * Indicate that the network likely has come back.
+ * or just that the network conditions might have changed
+ */
+ public void maybeNetwork() throws RpcException {
+ transport.call("maybe_network");
+ }
+
+ /**
+ * Get the current connectivity, i.e. whether the device is connected to the IMAP server.
+ * One of:
+ * - DC_CONNECTIVITY_NOT_CONNECTED (1000-1999): Show e.g. the string "Not connected" or a red dot
+ * - DC_CONNECTIVITY_CONNECTING (2000-2999): Show e.g. the string "Connecting…" or a yellow dot
+ * - DC_CONNECTIVITY_WORKING (3000-3999): Show e.g. the string "Getting new messages" or a spinning wheel
+ * - DC_CONNECTIVITY_CONNECTED (>=4000): Show e.g. the string "Connected" or a green dot
+ *
+ * We don't use exact values but ranges here so that we can split up
+ * states into multiple states in the future.
+ *
+ * Meant as a rough overview that can be shown
+ * e.g. in the title of the main screen.
+ *
+ * If the connectivity changes, a #DC_EVENT_CONNECTIVITY_CHANGED will be emitted.
+ */
+ public Integer getConnectivity(Integer accountId) throws RpcException {
+ return transport.callForResult(new TypeReference
+ * If this page changes, a #DC_EVENT_CONNECTIVITY_CHANGED will be emitted.
+ *
+ * This comes as an HTML from the core so that we can easily improve it
+ * and the improvement instantly reaches all UIs.
+ */
+ public String getConnectivityHtml(Integer accountId) throws RpcException {
+ return transport.callForResult(new TypeReference
+ * NB: When this is called before closing a webxdc app in UIs, it must be guaranteed that
+ * `send_webxdc_realtime_*()` functions aren't called for the given `instance_message_id`
+ * anymore until the app is open again.
+ */
+ public void leaveWebxdcRealtime(Integer accountId, Integer instanceMessageId) throws RpcException {
+ transport.call("leave_webxdc_realtime", mapper.valueToTree(accountId), mapper.valueToTree(instanceMessageId));
+ }
+
+ public String getWebxdcStatusUpdates(Integer accountId, Integer instanceMsgId, Integer lastKnownSerial) throws RpcException {
+ return transport.callForResult(new TypeReference
+ * path is the path of the file within webxdc archive
+ */
+ public String getWebxdcBlob(Integer accountId, Integer instanceMsgId, String path) throws RpcException {
+ return transport.callForResult(new TypeReference
+ * `url` is the HTTP or HTTPS URL.
+ */
+ public HttpResponse getHttpResponse(Integer accountId, String url) throws RpcException {
+ return transport.callForResult(new TypeReference
+ * All types of messages can be forwarded,
+ * however, they will be flagged as such (dc_msg_is_forwarded() is set).
+ *
+ * Original sender, info-state and webxdc updates are not forwarded on purpose.
+ */
+ public void forwardMessages(Integer accountId, java.util.List
+ * Some messages cannot be resent, eg. info-messages, drafts, already pending messages or messages that are not sent by SELF.
+ *
+ * message_ids all message IDs that should be resend. All messages must belong to the same chat.
+ */
+ public void resendMessages(Integer accountId, java.util.List
+ * Reaction is a string of emojis separated by spaces. Reaction to a
+ * single message can be sent multiple times. The last reaction
+ * received overrides all previously received reactions. It is
+ * possible to remove all reactions by sending an empty string.
+ */
+ public Integer sendReaction(Integer accountId, Integer messageId, java.util.List
+ * Fails if file already exists at the provided path.
+ */
+ public void saveMsgFile(Integer accountId, Integer msgId, String path) throws RpcException {
+ transport.call("save_msg_file", mapper.valueToTree(accountId), mapper.valueToTree(msgId), mapper.valueToTree(path));
+ }
+
+ public void removeDraft(Integer accountId, Integer chatId) throws RpcException {
+ transport.call("remove_draft", mapper.valueToTree(accountId), mapper.valueToTree(chatId));
+ }
+
+ /* Get draft for a chat, if any. */
+ public Message getDraft(Integer accountId, Integer chatId) throws RpcException {
+ return transport.callForResult(new TypeReference
+ * This function returns after the message has been placed in the sending queue.
+ * This does not imply that the message was really sent out yet.
+ * However, from your view, you're done with the message.
+ * Sooner or later it will find its way.
+ *
+ * **Attaching files:**
+ *
+ * Pass the file path in the `file` parameter.
+ * If `file` is not in the blob directory yet,
+ * it will be copied into the blob directory.
+ * If you want, you can delete the file immediately after this function returns.
+ *
+ * You can also write the attachment directly into the blob directory
+ * and then pass the path as the `file` parameter;
+ * this will prevent an unnecessary copying of the file.
+ *
+ * In `filename`, you can pass the original name of the file,
+ * which will then be shown in the UI.
+ * in this case the current name of `file` on the filesystem will be ignored.
+ *
+ * In order to deduplicate files that contain the same data,
+ * the file will be named `
+ * NOTE:
+ * - This function will rename the file. To get the new file path, call `get_file()`.
+ * - The file must not be modified after this function was called.
+ * - Images etc. will NOT be recoded.
+ * In order to recode images,
+ * use `misc_set_draft` and pass `Image` as the viewtype.
+ */
+ public Pair
+ * used when you only need the basic metadata of a chat like type, name, profile picture
+ */
+public class BasicChat {
+ public Boolean archived;
+ public ChatType chatType;
+ public String color;
+ public Integer id;
+ public Boolean isContactRequest;
+ public Boolean isDeviceChat;
+ /**
+ * True if the chat is encrypted. This means that all messages in the chat are encrypted, and all contacts in the chat are "key-contacts", i.e. identified by the PGP key fingerprint.
+ *
+ * False if the chat is unencrypted. This means that all messages in the chat are unencrypted, and all contacts in the chat are "address-contacts", i.e. identified by the email address. The UI should mark this chat e.g. with a mail-letter icon.
+ *
+ * Unencrypted groups are called "ad-hoc groups" and the user can't add/remove members, create a QR invite code, or set an avatar. These options should therefore be disabled in the UI.
+ *
+ * Note that it can happen that an encrypted chat contains unencrypted messages that were received in core <= v1.159.* and vice versa.
+ *
+ * See also `is_key_contact` on `Contact`.
+ */
+ public Boolean isEncrypted;
+ public Boolean isMuted;
+ public Boolean isSelfTalk;
+ public Boolean isUnpromoted;
+ public String name;
+ public Boolean pinned;
+ @com.fasterxml.jackson.annotation.JsonSetter(nulls = com.fasterxml.jackson.annotation.Nulls.SET)
+ public String profileImage;
+}
\ No newline at end of file
diff --git a/src/main/java/chat/delta/rpc/types/CallInfo.java b/src/main/java/chat/delta/rpc/types/CallInfo.java
new file mode 100644
index 0000000000000000000000000000000000000000..dd177c186c8456df0496bd0b0a9910deca274d92
--- /dev/null
+++ b/src/main/java/chat/delta/rpc/types/CallInfo.java
@@ -0,0 +1,19 @@
+/* Autogenerated file, do not edit manually */
+package chat.delta.rpc.types;
+
+public class CallInfo {
+ /* True if SDP offer has a video. */
+ public Boolean hasVideo;
+ /**
+ * SDP offer.
+ *
+ * Can be used to manually answer the call even if incoming call event was missed.
+ */
+ public String sdpOffer;
+ /**
+ * Call state.
+ *
+ * For example, if the call is accepted, active, canceled, declined etc.
+ */
+ public CallState state;
+}
\ No newline at end of file
diff --git a/src/main/java/chat/delta/rpc/types/CallState.java b/src/main/java/chat/delta/rpc/types/CallState.java
new file mode 100644
index 0000000000000000000000000000000000000000..b18577053f1d8a59d128216c6c329f0694c08131
--- /dev/null
+++ b/src/main/java/chat/delta/rpc/types/CallState.java
@@ -0,0 +1,48 @@
+/* Autogenerated file, do not edit manually */
+package chat.delta.rpc.types;
+
+import com.fasterxml.jackson.annotation.JsonSubTypes;
+import com.fasterxml.jackson.annotation.JsonSubTypes.Type;
+import com.fasterxml.jackson.annotation.JsonTypeInfo;
+import com.fasterxml.jackson.annotation.JsonTypeInfo.Id;
+import com.fasterxml.jackson.annotation.JsonTypeInfo.As;
+
+@JsonTypeInfo(use=Id.NAME, include=As.PROPERTY, property="kind")
+@JsonSubTypes({@Type(value = CallState.Alerting.class, name="Alerting"), @Type(value = CallState.Active.class, name="Active"), @Type(value = CallState.Completed.class, name="Completed"), @Type(value = CallState.Missed.class, name="Missed"), @Type(value = CallState.Declined.class, name="Declined"), @Type(value = CallState.Canceled.class, name="Canceled")})
+public abstract class CallState {
+
+/**
+ * Fresh incoming or outgoing call that is still ringing.
+ *
+ * There is no separate state for outgoing call that has been dialled but not ringing on the other side yet as we don't know whether the other side received our call.
+ */
+ public static class Alerting extends CallState {
+ }
+
+/* Active call. */
+ public static class Active extends CallState {
+ }
+
+/* Completed call that was once active and then was terminated for any reason. */
+ public static class Completed extends CallState {
+ /* Call duration in seconds. */
+ public Integer duration;
+ }
+
+/* Incoming call that was not picked up within a timeout or was explicitly ended by the caller before we picked up. */
+ public static class Missed extends CallState {
+ }
+
+/* Incoming call that was explicitly ended on our side before picking up or outgoing call that was declined before the timeout. */
+ public static class Declined extends CallState {
+ }
+
+/**
+ * Outgoing call that has been canceled on our side before receiving a response.
+ *
+ * Incoming calls cannot be canceled, on the receiver side canceled calls usually result in missed calls.
+ */
+ public static class Canceled extends CallState {
+ }
+
+}
\ No newline at end of file
diff --git a/src/main/java/chat/delta/rpc/types/ChatListItemFetchResult.java b/src/main/java/chat/delta/rpc/types/ChatListItemFetchResult.java
new file mode 100644
index 0000000000000000000000000000000000000000..687aa35be846c07ee6b7ff6110a391a38a921701
--- /dev/null
+++ b/src/main/java/chat/delta/rpc/types/ChatListItemFetchResult.java
@@ -0,0 +1,71 @@
+/* Autogenerated file, do not edit manually */
+package chat.delta.rpc.types;
+
+import com.fasterxml.jackson.annotation.JsonSubTypes;
+import com.fasterxml.jackson.annotation.JsonSubTypes.Type;
+import com.fasterxml.jackson.annotation.JsonTypeInfo;
+import com.fasterxml.jackson.annotation.JsonTypeInfo.Id;
+import com.fasterxml.jackson.annotation.JsonTypeInfo.As;
+
+@JsonTypeInfo(use=Id.NAME, include=As.PROPERTY, property="kind")
+@JsonSubTypes({@Type(value = ChatListItemFetchResult.ChatListItem.class, name="ChatListItem"), @Type(value = ChatListItemFetchResult.ArchiveLink.class, name="ArchiveLink"), @Type(value = ChatListItemFetchResult.Error.class, name="Error")})
+public abstract class ChatListItemFetchResult {
+
+ public static class ChatListItem extends ChatListItemFetchResult {
+ @com.fasterxml.jackson.annotation.JsonSetter(nulls = com.fasterxml.jackson.annotation.Nulls.SET)
+ public String avatarPath;
+ public ChatType chatType;
+ public String color;
+ /* contact id if this is a dm chat (for view profile entry in context menu) */
+ @com.fasterxml.jackson.annotation.JsonSetter(nulls = com.fasterxml.jackson.annotation.Nulls.SET)
+ public Integer dmChatContact;
+ public Integer freshMessageCounter;
+ public Integer id;
+ public Boolean isArchived;
+ public Boolean isContactRequest;
+ public Boolean isDeviceTalk;
+ /**
+ * True if the chat is encrypted. This means that all messages in the chat are encrypted, and all contacts in the chat are "key-contacts", i.e. identified by the PGP key fingerprint.
+ *
+ * False if the chat is unencrypted. This means that all messages in the chat are unencrypted, and all contacts in the chat are "address-contacts", i.e. identified by the email address. The UI should mark this chat e.g. with a mail-letter icon.
+ *
+ * Unencrypted groups are called "ad-hoc groups" and the user can't add/remove members, create a QR invite code, or set an avatar. These options should therefore be disabled in the UI.
+ *
+ * Note that it can happen that an encrypted chat contains unencrypted messages that were received in core <= v1.159.* and vice versa.
+ *
+ * See also `is_key_contact` on `Contact`.
+ */
+ public Boolean isEncrypted;
+ /* deprecated 2025-07, use chat_type instead */
+ public Boolean isGroup;
+ public Boolean isMuted;
+ public Boolean isPinned;
+ public Boolean isSelfInGroup;
+ public Boolean isSelfTalk;
+ public Boolean isSendingLocation;
+ @com.fasterxml.jackson.annotation.JsonSetter(nulls = com.fasterxml.jackson.annotation.Nulls.SET)
+ public Integer lastMessageId;
+ @com.fasterxml.jackson.annotation.JsonSetter(nulls = com.fasterxml.jackson.annotation.Nulls.SET)
+ public Viewtype lastMessageType;
+ @com.fasterxml.jackson.annotation.JsonSetter(nulls = com.fasterxml.jackson.annotation.Nulls.SET)
+ public Integer lastUpdated;
+ public String name;
+ /* showing preview if last chat message is image */
+ @com.fasterxml.jackson.annotation.JsonSetter(nulls = com.fasterxml.jackson.annotation.Nulls.SET)
+ public String summaryPreviewImage;
+ public Integer summaryStatus;
+ public String summaryText1;
+ public String summaryText2;
+ public Boolean wasSeenRecently;
+ }
+
+ public static class ArchiveLink extends ChatListItemFetchResult {
+ public Integer freshMessageCounter;
+ }
+
+ public static class Error extends ChatListItemFetchResult {
+ public String error;
+ public Integer id;
+ }
+
+}
\ No newline at end of file
diff --git a/src/main/java/chat/delta/rpc/types/ChatType.java b/src/main/java/chat/delta/rpc/types/ChatType.java
new file mode 100644
index 0000000000000000000000000000000000000000..ef7d360e94c0ce4a40867b4578a247a091f73069
--- /dev/null
+++ b/src/main/java/chat/delta/rpc/types/ChatType.java
@@ -0,0 +1,10 @@
+/* Autogenerated file, do not edit manually */
+package chat.delta.rpc.types;
+
+public enum ChatType {
+ Single,
+ Group,
+ Mailinglist,
+ OutBroadcast,
+ InBroadcast,
+}
\ No newline at end of file
diff --git a/src/main/java/chat/delta/rpc/types/ChatVisibility.java b/src/main/java/chat/delta/rpc/types/ChatVisibility.java
new file mode 100644
index 0000000000000000000000000000000000000000..340595a61c979793676c93e3d8244302b8b2635d
--- /dev/null
+++ b/src/main/java/chat/delta/rpc/types/ChatVisibility.java
@@ -0,0 +1,8 @@
+/* Autogenerated file, do not edit manually */
+package chat.delta.rpc.types;
+
+public enum ChatVisibility {
+ Normal,
+ Archived,
+ Pinned,
+}
\ No newline at end of file
diff --git a/src/main/java/chat/delta/rpc/types/Contact.java b/src/main/java/chat/delta/rpc/types/Contact.java
new file mode 100644
index 0000000000000000000000000000000000000000..91ed6d273f75c457b6fdd46bc10222717c08b1a2
--- /dev/null
+++ b/src/main/java/chat/delta/rpc/types/Contact.java
@@ -0,0 +1,52 @@
+/* Autogenerated file, do not edit manually */
+package chat.delta.rpc.types;
+
+public class Contact {
+ public String address;
+ public String authName;
+ public String color;
+ public String displayName;
+ /**
+ * Is encryption available for this contact.
+ *
+ * This can only be true for key-contacts. However, it is possible to have a key-contact for which encryption is not available because we don't have a key yet, e.g. if we just scanned the fingerprint from a QR code.
+ */
+ public Boolean e2eeAvail;
+ public Integer id;
+ public Boolean isBlocked;
+ /* If the contact is a bot. */
+ public Boolean isBot;
+ /* Is the contact a key contact. */
+ public Boolean isKeyContact;
+ /**
+ * True if the contact can be added to protected chats because SELF and contact have verified their fingerprints in both directions.
+ *
+ * See [`Self::verifier_id`]/`Contact.verifierId` for a guidance how to display these information.
+ */
+ public Boolean isVerified;
+ /* the contact's last seen timestamp */
+ public Integer lastSeen;
+ public String name;
+ public String nameAndAddr;
+ @com.fasterxml.jackson.annotation.JsonSetter(nulls = com.fasterxml.jackson.annotation.Nulls.SET)
+ public String profileImage;
+ public String status;
+ /**
+ * The contact ID that verified a contact.
+ *
+ * As verifier may be unknown, use [`Self::is_verified`]/`Contact.isVerified` to check if a contact can be added to a protected chat.
+ *
+ * UI should display the information in the contact's profile as follows:
+ *
+ * - If `verifierId` != 0, display text "Introduced by ..." with the name and address of the contact formatted by `name_and_addr`/`nameAndAddr`. Prefix the text by a green checkmark.
+ *
+ * - If `verifierId` == 0 and `isVerified` != 0, display "Introduced" prefixed by a green checkmark.
+ *
+ * - if `verifierId` == 0 and `isVerified` == 0, display nothing
+ *
+ * This contains the contact ID of the verifier. If it is `DC_CONTACT_ID_SELF`, we verified the contact ourself. If it is None/Null, we don't have verifier information or the contact is not verified.
+ */
+ @com.fasterxml.jackson.annotation.JsonSetter(nulls = com.fasterxml.jackson.annotation.Nulls.SET)
+ public Integer verifierId;
+ public Boolean wasSeenRecently;
+}
\ No newline at end of file
diff --git a/src/main/java/chat/delta/rpc/types/DownloadState.java b/src/main/java/chat/delta/rpc/types/DownloadState.java
new file mode 100644
index 0000000000000000000000000000000000000000..4a8cbad3ce0d6f9de4e53a2bc3b8c3366ffdf6b6
--- /dev/null
+++ b/src/main/java/chat/delta/rpc/types/DownloadState.java
@@ -0,0 +1,10 @@
+/* Autogenerated file, do not edit manually */
+package chat.delta.rpc.types;
+
+public enum DownloadState {
+ Done,
+ Available,
+ Failure,
+ Undecipherable,
+ InProgress,
+}
\ No newline at end of file
diff --git a/src/main/java/chat/delta/rpc/types/EnteredCertificateChecks.java b/src/main/java/chat/delta/rpc/types/EnteredCertificateChecks.java
new file mode 100644
index 0000000000000000000000000000000000000000..77c8f9f850245cf15fae20b4a4c543731170d9cf
--- /dev/null
+++ b/src/main/java/chat/delta/rpc/types/EnteredCertificateChecks.java
@@ -0,0 +1,13 @@
+/* Autogenerated file, do not edit manually */
+package chat.delta.rpc.types;
+
+public enum EnteredCertificateChecks {
+ /* `Automatic` means that provider database setting should be taken. If there is no provider database setting for certificate checks, check certificates strictly. */
+ automatic,
+
+ /* Ensure that TLS certificate is valid for the server hostname. */
+ strict,
+
+ /* Accept certificates that are expired, self-signed or otherwise not valid for the server hostname. */
+ acceptInvalidCertificates,
+}
\ No newline at end of file
diff --git a/src/main/java/chat/delta/rpc/types/EnteredLoginParam.java b/src/main/java/chat/delta/rpc/types/EnteredLoginParam.java
new file mode 100644
index 0000000000000000000000000000000000000000..87c1c94271466051264d266e97b843326330b90a
--- /dev/null
+++ b/src/main/java/chat/delta/rpc/types/EnteredLoginParam.java
@@ -0,0 +1,51 @@
+/* Autogenerated file, do not edit manually */
+package chat.delta.rpc.types;
+
+/**
+ * Login parameters entered by the user.
+ *
+ * Usually it will be enough to only set `addr` and `password`, and all the other settings will be autoconfigured.
+ */
+public class EnteredLoginParam {
+ /* Email address. */
+ public String addr;
+ /* TLS options: whether to allow invalid certificates and/or invalid hostnames. Default: Automatic */
+ @com.fasterxml.jackson.annotation.JsonSetter(nulls = com.fasterxml.jackson.annotation.Nulls.SET)
+ public EnteredCertificateChecks certificateChecks;
+ /* Imap server port. */
+ @com.fasterxml.jackson.annotation.JsonSetter(nulls = com.fasterxml.jackson.annotation.Nulls.SET)
+ public Integer imapPort;
+ /* Imap socket security. */
+ @com.fasterxml.jackson.annotation.JsonSetter(nulls = com.fasterxml.jackson.annotation.Nulls.SET)
+ public Socket imapSecurity;
+ /* Imap server hostname or IP address. */
+ @com.fasterxml.jackson.annotation.JsonSetter(nulls = com.fasterxml.jackson.annotation.Nulls.SET)
+ public String imapServer;
+ /* Imap username. */
+ @com.fasterxml.jackson.annotation.JsonSetter(nulls = com.fasterxml.jackson.annotation.Nulls.SET)
+ public String imapUser;
+ /* If true, login via OAUTH2 (not recommended anymore). Default: false */
+ @com.fasterxml.jackson.annotation.JsonSetter(nulls = com.fasterxml.jackson.annotation.Nulls.SET)
+ public Boolean oauth2;
+ /* Password. */
+ public String password;
+ /**
+ * SMTP Password.
+ *
+ * Only needs to be specified if different than IMAP password.
+ */
+ @com.fasterxml.jackson.annotation.JsonSetter(nulls = com.fasterxml.jackson.annotation.Nulls.SET)
+ public String smtpPassword;
+ /* SMTP server port. */
+ @com.fasterxml.jackson.annotation.JsonSetter(nulls = com.fasterxml.jackson.annotation.Nulls.SET)
+ public Integer smtpPort;
+ /* SMTP socket security. */
+ @com.fasterxml.jackson.annotation.JsonSetter(nulls = com.fasterxml.jackson.annotation.Nulls.SET)
+ public Socket smtpSecurity;
+ /* SMTP server hostname or IP address. */
+ @com.fasterxml.jackson.annotation.JsonSetter(nulls = com.fasterxml.jackson.annotation.Nulls.SET)
+ public String smtpServer;
+ /* SMTP username. */
+ @com.fasterxml.jackson.annotation.JsonSetter(nulls = com.fasterxml.jackson.annotation.Nulls.SET)
+ public String smtpUser;
+}
\ No newline at end of file
diff --git a/src/main/java/chat/delta/rpc/types/EphemeralTimer.java b/src/main/java/chat/delta/rpc/types/EphemeralTimer.java
new file mode 100644
index 0000000000000000000000000000000000000000..fb4e34f72cceb9dbf36858a6580468c8ae2651cb
--- /dev/null
+++ b/src/main/java/chat/delta/rpc/types/EphemeralTimer.java
@@ -0,0 +1,28 @@
+/* Autogenerated file, do not edit manually */
+package chat.delta.rpc.types;
+
+import com.fasterxml.jackson.annotation.JsonSubTypes;
+import com.fasterxml.jackson.annotation.JsonSubTypes.Type;
+import com.fasterxml.jackson.annotation.JsonTypeInfo;
+import com.fasterxml.jackson.annotation.JsonTypeInfo.Id;
+import com.fasterxml.jackson.annotation.JsonTypeInfo.As;
+
+@JsonTypeInfo(use=Id.NAME, include=As.PROPERTY, property="kind")
+@JsonSubTypes({@Type(value = EphemeralTimer.Disabled.class, name="Disabled"), @Type(value = EphemeralTimer.Enabled.class, name="Enabled")})
+public abstract class EphemeralTimer {
+
+/* Timer is disabled. */
+ public static class Disabled extends EphemeralTimer {
+ }
+
+/* Timer is enabled. */
+ public static class Enabled extends EphemeralTimer {
+ /**
+ * Timer duration in seconds.
+ *
+ * The value cannot be 0.
+ */
+ public Integer duration;
+ }
+
+}
\ No newline at end of file
diff --git a/src/main/java/chat/delta/rpc/types/Event.java b/src/main/java/chat/delta/rpc/types/Event.java
new file mode 100644
index 0000000000000000000000000000000000000000..0d23609d74cfa36b97e28adf34495e59483b934e
--- /dev/null
+++ b/src/main/java/chat/delta/rpc/types/Event.java
@@ -0,0 +1,9 @@
+/* Autogenerated file, do not edit manually */
+package chat.delta.rpc.types;
+
+public class Event {
+ /* Account ID. */
+ public Integer contextId;
+ /* Event payload. */
+ public EventType event;
+}
\ No newline at end of file
diff --git a/src/main/java/chat/delta/rpc/types/EventType.java b/src/main/java/chat/delta/rpc/types/EventType.java
new file mode 100644
index 0000000000000000000000000000000000000000..04c80f632e36f5372172d391efd68ca8da4abab8
--- /dev/null
+++ b/src/main/java/chat/delta/rpc/types/EventType.java
@@ -0,0 +1,420 @@
+/* Autogenerated file, do not edit manually */
+package chat.delta.rpc.types;
+
+import com.fasterxml.jackson.annotation.JsonSubTypes;
+import com.fasterxml.jackson.annotation.JsonSubTypes.Type;
+import com.fasterxml.jackson.annotation.JsonTypeInfo;
+import com.fasterxml.jackson.annotation.JsonTypeInfo.Id;
+import com.fasterxml.jackson.annotation.JsonTypeInfo.As;
+
+@JsonTypeInfo(use=Id.NAME, include=As.PROPERTY, property="kind")
+@JsonSubTypes({@Type(value = EventType.Info.class, name="Info"), @Type(value = EventType.SmtpConnected.class, name="SmtpConnected"), @Type(value = EventType.ImapConnected.class, name="ImapConnected"), @Type(value = EventType.SmtpMessageSent.class, name="SmtpMessageSent"), @Type(value = EventType.ImapMessageDeleted.class, name="ImapMessageDeleted"), @Type(value = EventType.ImapMessageMoved.class, name="ImapMessageMoved"), @Type(value = EventType.ImapInboxIdle.class, name="ImapInboxIdle"), @Type(value = EventType.NewBlobFile.class, name="NewBlobFile"), @Type(value = EventType.DeletedBlobFile.class, name="DeletedBlobFile"), @Type(value = EventType.Warning.class, name="Warning"), @Type(value = EventType.Error.class, name="Error"), @Type(value = EventType.ErrorSelfNotInGroup.class, name="ErrorSelfNotInGroup"), @Type(value = EventType.MsgsChanged.class, name="MsgsChanged"), @Type(value = EventType.ReactionsChanged.class, name="ReactionsChanged"), @Type(value = EventType.IncomingReaction.class, name="IncomingReaction"), @Type(value = EventType.IncomingWebxdcNotify.class, name="IncomingWebxdcNotify"), @Type(value = EventType.IncomingMsg.class, name="IncomingMsg"), @Type(value = EventType.IncomingMsgBunch.class, name="IncomingMsgBunch"), @Type(value = EventType.MsgsNoticed.class, name="MsgsNoticed"), @Type(value = EventType.MsgDelivered.class, name="MsgDelivered"), @Type(value = EventType.MsgFailed.class, name="MsgFailed"), @Type(value = EventType.MsgRead.class, name="MsgRead"), @Type(value = EventType.MsgDeleted.class, name="MsgDeleted"), @Type(value = EventType.ChatModified.class, name="ChatModified"), @Type(value = EventType.ChatEphemeralTimerModified.class, name="ChatEphemeralTimerModified"), @Type(value = EventType.ChatDeleted.class, name="ChatDeleted"), @Type(value = EventType.ContactsChanged.class, name="ContactsChanged"), @Type(value = EventType.LocationChanged.class, name="LocationChanged"), @Type(value = EventType.ConfigureProgress.class, name="ConfigureProgress"), @Type(value = EventType.ImexProgress.class, name="ImexProgress"), @Type(value = EventType.ImexFileWritten.class, name="ImexFileWritten"), @Type(value = EventType.SecurejoinInviterProgress.class, name="SecurejoinInviterProgress"), @Type(value = EventType.SecurejoinJoinerProgress.class, name="SecurejoinJoinerProgress"), @Type(value = EventType.ConnectivityChanged.class, name="ConnectivityChanged"), @Type(value = EventType.SelfavatarChanged.class, name="SelfavatarChanged"), @Type(value = EventType.ConfigSynced.class, name="ConfigSynced"), @Type(value = EventType.WebxdcStatusUpdate.class, name="WebxdcStatusUpdate"), @Type(value = EventType.WebxdcRealtimeData.class, name="WebxdcRealtimeData"), @Type(value = EventType.WebxdcRealtimeAdvertisementReceived.class, name="WebxdcRealtimeAdvertisementReceived"), @Type(value = EventType.WebxdcInstanceDeleted.class, name="WebxdcInstanceDeleted"), @Type(value = EventType.AccountsBackgroundFetchDone.class, name="AccountsBackgroundFetchDone"), @Type(value = EventType.ChatlistChanged.class, name="ChatlistChanged"), @Type(value = EventType.ChatlistItemChanged.class, name="ChatlistItemChanged"), @Type(value = EventType.AccountsChanged.class, name="AccountsChanged"), @Type(value = EventType.AccountsItemChanged.class, name="AccountsItemChanged"), @Type(value = EventType.EventChannelOverflow.class, name="EventChannelOverflow"), @Type(value = EventType.IncomingCall.class, name="IncomingCall"), @Type(value = EventType.IncomingCallAccepted.class, name="IncomingCallAccepted"), @Type(value = EventType.OutgoingCallAccepted.class, name="OutgoingCallAccepted"), @Type(value = EventType.CallEnded.class, name="CallEnded"), @Type(value = EventType.TransportsModified.class, name="TransportsModified")})
+public abstract class EventType {
+
+/**
+ * The library-user may write an informational string to the log.
+ *
+ * This event should *not* be reported to the end-user using a popup or something like that.
+ */
+ public static class Info extends EventType {
+ public String msg;
+ }
+
+/* Emitted when SMTP connection is established and login was successful. */
+ public static class SmtpConnected extends EventType {
+ public String msg;
+ }
+
+/* Emitted when IMAP connection is established and login was successful. */
+ public static class ImapConnected extends EventType {
+ public String msg;
+ }
+
+/* Emitted when a message was successfully sent to the SMTP server. */
+ public static class SmtpMessageSent extends EventType {
+ public String msg;
+ }
+
+/* Emitted when an IMAP message has been marked as deleted */
+ public static class ImapMessageDeleted extends EventType {
+ public String msg;
+ }
+
+/* Emitted when an IMAP message has been moved */
+ public static class ImapMessageMoved extends EventType {
+ public String msg;
+ }
+
+/* Emitted before going into IDLE on the Inbox folder. */
+ public static class ImapInboxIdle extends EventType {
+ }
+
+/* Emitted when an new file in the $BLOBDIR was created */
+ public static class NewBlobFile extends EventType {
+ public String file;
+ }
+
+/* Emitted when an file in the $BLOBDIR was deleted */
+ public static class DeletedBlobFile extends EventType {
+ public String file;
+ }
+
+/**
+ * The library-user should write a warning string to the log.
+ *
+ * This event should *not* be reported to the end-user using a popup or something like that.
+ */
+ public static class Warning extends EventType {
+ public String msg;
+ }
+
+/**
+ * The library-user should report an error to the end-user.
+ *
+ * As most things are asynchronous, things may go wrong at any time and the user should not be disturbed by a dialog or so. Instead, use a bubble or so.
+ *
+ * However, for ongoing processes (eg. configure()) or for functions that are expected to fail (eg. autocryptContinueKeyTransfer()) it might be better to delay showing these events until the function has really failed (returned false). It should be sufficient to report only the *last* error in a message box then.
+ */
+ public static class Error extends EventType {
+ public String msg;
+ }
+
+/* An action cannot be performed because the user is not in the group. Reported eg. after a call to setChatName(), setChatProfileImage(), addContactToChat(), removeContactFromChat(), and messages sending functions. */
+ public static class ErrorSelfNotInGroup extends EventType {
+ public String msg;
+ }
+
+/* Messages or chats changed. One or more messages or chats changed for various reasons in the database: - Messages sent, received or removed - Chats created, deleted or archived - A draft has been set */
+ public static class MsgsChanged extends EventType {
+ /* Set if only a single chat is affected by the changes, otherwise 0. */
+ public Integer chatId;
+ /* Set if only a single message is affected by the changes, otherwise 0. */
+ public Integer msgId;
+ }
+
+/* Reactions for the message changed. */
+ public static class ReactionsChanged extends EventType {
+ /* ID of the chat which the message belongs to. */
+ public Integer chatId;
+ /* ID of the contact whose reaction set is changed. */
+ public Integer contactId;
+ /* ID of the message for which reactions were changed. */
+ public Integer msgId;
+ }
+
+/**
+ * A reaction to one's own sent message received. Typically, the UI will show a notification for that.
+ *
+ * In addition to this event, ReactionsChanged is emitted.
+ */
+ public static class IncomingReaction extends EventType {
+ /* ID of the chat which the message belongs to. */
+ public Integer chatId;
+ /* ID of the contact whose reaction set is changed. */
+ public Integer contactId;
+ /* ID of the message for which reactions were changed. */
+ public Integer msgId;
+ /* The reaction. */
+ public String reaction;
+ }
+
+/* Incoming webxdc info or summary update, should be notified. */
+ public static class IncomingWebxdcNotify extends EventType {
+ /* ID of the chat. */
+ public Integer chatId;
+ /* ID of the contact sending. */
+ public Integer contactId;
+ /* Link assigned to this notification, if any. */
+ @com.fasterxml.jackson.annotation.JsonSetter(nulls = com.fasterxml.jackson.annotation.Nulls.SET)
+ public String href;
+ /* ID of the added info message or webxdc instance in case of summary change. */
+ public Integer msgId;
+ /* Text to notify. */
+ public String text;
+ }
+
+/**
+ * There is a fresh message. Typically, the user will show a notification when receiving this message.
+ *
+ * There is no extra #DC_EVENT_MSGS_CHANGED event sent together with this event.
+ */
+ public static class IncomingMsg extends EventType {
+ /* ID of the chat where the message is assigned. */
+ public Integer chatId;
+ /* ID of the message. */
+ public Integer msgId;
+ }
+
+/* Downloading a bunch of messages just finished. This is an event to allow the UI to only show one notification per message bunch, instead of cluttering the user with many notifications. */
+ public static class IncomingMsgBunch extends EventType {
+ }
+
+/* Messages were seen or noticed. chat id is always set. */
+ public static class MsgsNoticed extends EventType {
+ public Integer chatId;
+ }
+
+/* A single message is sent successfully. State changed from DC_STATE_OUT_PENDING to DC_STATE_OUT_DELIVERED, see `Message.state`. */
+ public static class MsgDelivered extends EventType {
+ /* ID of the chat which the message belongs to. */
+ public Integer chatId;
+ /* ID of the message that was successfully sent. */
+ public Integer msgId;
+ }
+
+/* A single message could not be sent. State changed from DC_STATE_OUT_PENDING or DC_STATE_OUT_DELIVERED to DC_STATE_OUT_FAILED, see `Message.state`. */
+ public static class MsgFailed extends EventType {
+ /* ID of the chat which the message belongs to. */
+ public Integer chatId;
+ /* ID of the message that could not be sent. */
+ public Integer msgId;
+ }
+
+/* A single message is read by the receiver. State changed from DC_STATE_OUT_DELIVERED to DC_STATE_OUT_MDN_RCVD, see `Message.state`. */
+ public static class MsgRead extends EventType {
+ /* ID of the chat which the message belongs to. */
+ public Integer chatId;
+ /* ID of the message that was read. */
+ public Integer msgId;
+ }
+
+/**
+ * A single message was deleted.
+ *
+ * This event means that the message will no longer appear in the messagelist. UI should remove the message from the messagelist in response to this event if the message is currently displayed.
+ *
+ * The message may have been explicitly deleted by the user or expired. Internally the message may have been removed from the database, moved to the trash chat or hidden.
+ *
+ * This event does not indicate the message deletion from the server.
+ */
+ public static class MsgDeleted extends EventType {
+ /* ID of the chat where the message was prior to deletion. Never 0. */
+ public Integer chatId;
+ /* ID of the deleted message. Never 0. */
+ public Integer msgId;
+ }
+
+/**
+ * Chat changed. The name or the image of a chat group was changed or members were added or removed. See setChatName(), setChatProfileImage(), addContactToChat() and removeContactFromChat().
+ *
+ * This event does not include ephemeral timer modification, which is a separate event.
+ */
+ public static class ChatModified extends EventType {
+ public Integer chatId;
+ }
+
+/* Chat ephemeral timer changed. */
+ public static class ChatEphemeralTimerModified extends EventType {
+ /* Chat ID. */
+ public Integer chatId;
+ /* New ephemeral timer value. */
+ public Integer timer;
+ }
+
+/* Chat deleted. */
+ public static class ChatDeleted extends EventType {
+ /* Chat ID. */
+ public Integer chat_id;
+ }
+
+/* Contact(s) created, renamed, blocked or deleted. */
+ public static class ContactsChanged extends EventType {
+ /* If set, this is the contact_id of an added contact that should be selected. */
+ @com.fasterxml.jackson.annotation.JsonSetter(nulls = com.fasterxml.jackson.annotation.Nulls.SET)
+ public Integer contactId;
+ }
+
+/* Location of one or more contact has changed. */
+ public static class LocationChanged extends EventType {
+ /* contact_id of the contact for which the location has changed. If the locations of several contacts have been changed, this parameter is set to `None`. */
+ @com.fasterxml.jackson.annotation.JsonSetter(nulls = com.fasterxml.jackson.annotation.Nulls.SET)
+ public Integer contactId;
+ }
+
+/* Inform about the configuration progress started by configure(). */
+ public static class ConfigureProgress extends EventType {
+ /* Progress comment or error, something to display to the user. */
+ @com.fasterxml.jackson.annotation.JsonSetter(nulls = com.fasterxml.jackson.annotation.Nulls.SET)
+ public String comment;
+ /**
+ * Progress.
+ *
+ * 0=error, 1-999=progress in permille, 1000=success and done
+ */
+ public Integer progress;
+ }
+
+/* Inform about the import/export progress started by imex(). */
+ public static class ImexProgress extends EventType {
+ /* 0=error, 1-999=progress in permille, 1000=success and done */
+ public Integer progress;
+ }
+
+/**
+ * A file has been exported. A file has been written by imex(). This event may be sent multiple times by a single call to imex().
+ *
+ * A typical purpose for a handler of this event may be to make the file public to some system services.
+ *
+ * @param data2 0
+ */
+ public static class ImexFileWritten extends EventType {
+ public String path;
+ }
+
+/**
+ * Progress event sent when SecureJoin protocol has finished from the view of the inviter (Alice, the person who shows the QR code).
+ *
+ * These events are typically sent after a joiner has scanned the QR code generated by getChatSecurejoinQrCodeSvg().
+ */
+ public static class SecurejoinInviterProgress extends EventType {
+ /* ID of the chat in case of success. */
+ public Integer chatId;
+ /* The type of the joined chat. This can take the same values as `BasicChat.chatType` ([`crate::api::types::chat::BasicChat::chat_type`]). */
+ public ChatType chatType;
+ /* ID of the contact that wants to join. */
+ public Integer contactId;
+ /* Progress, always 1000. */
+ public Integer progress;
+ }
+
+/* Progress information of a secure-join handshake from the view of the joiner (Bob, the person who scans the QR code). The events are typically sent while secureJoin(), which may take some time, is executed. */
+ public static class SecurejoinJoinerProgress extends EventType {
+ /* ID of the inviting contact. */
+ public Integer contactId;
+ /* Progress as: 400=vg-/vc-request-with-auth sent, typically shown as "alice@addr verified, introducing myself." (Bob has verified alice and waits until Alice does the same for him) 1000=vg-member-added/vc-contact-confirm received */
+ public Integer progress;
+ }
+
+/* The connectivity to the server changed. This means that you should refresh the connectivity view and possibly the connectivtiy HTML; see getConnectivity() and getConnectivityHtml() for details. */
+ public static class ConnectivityChanged extends EventType {
+ }
+
+/* Deprecated by `ConfigSynced`. */
+ public static class SelfavatarChanged extends EventType {
+ }
+
+/* A multi-device synced config value changed. Maybe the app needs to refresh smth. For uniformity this is emitted on the source device too. The value isn't here, otherwise it would be logged which might not be good for privacy. */
+ public static class ConfigSynced extends EventType {
+ /* Configuration key. */
+ public String key;
+ }
+
+ public static class WebxdcStatusUpdate extends EventType {
+ /* Message ID. */
+ public Integer msgId;
+ /* Status update ID. */
+ public Integer statusUpdateSerial;
+ }
+
+/* Data received over an ephemeral peer channel. */
+ public static class WebxdcRealtimeData extends EventType {
+ /* Realtime data. */
+ public java.util.List
+ * This event is only emitted by the account manager
+ */
+ public static class AccountsBackgroundFetchDone extends EventType {
+ }
+
+/**
+ * Inform that set of chats or the order of the chats in the chatlist has changed.
+ *
+ * Sometimes this is emitted together with `UIChatlistItemChanged`.
+ */
+ public static class ChatlistChanged extends EventType {
+ }
+
+/* Inform that a single chat list item changed and needs to be rerendered. If `chat_id` is set to None, then all currently visible chats need to be rerendered, and all not-visible items need to be cleared from cache if the UI has a cache. */
+ public static class ChatlistItemChanged extends EventType {
+ /* ID of the changed chat */
+ @com.fasterxml.jackson.annotation.JsonSetter(nulls = com.fasterxml.jackson.annotation.Nulls.SET)
+ public Integer chatId;
+ }
+
+/**
+ * Inform that the list of accounts has changed (an account removed or added or (not yet implemented) the account order changes)
+ *
+ * This event is only emitted by the account manager
+ */
+ public static class AccountsChanged extends EventType {
+ }
+
+/**
+ * Inform that an account property that might be shown in the account list changed, namely: - is_configured (see is_configured()) - displayname - selfavatar - private_tag
+ *
+ * This event is emitted from the account whose property changed.
+ */
+ public static class AccountsItemChanged extends EventType {
+ }
+
+/* Inform than some events have been skipped due to event channel overflow. */
+ public static class EventChannelOverflow extends EventType {
+ /* Number of events skipped. */
+ public Integer n;
+ }
+
+/* Incoming call. */
+ public static class IncomingCall extends EventType {
+ /* ID of the chat which the message belongs to. */
+ public Integer chat_id;
+ /* True if incoming call is a video call. */
+ public Boolean has_video;
+ /* ID of the info message referring to the call. */
+ public Integer msg_id;
+ /* User-defined info as passed to place_outgoing_call() */
+ public String place_call_info;
+ }
+
+/* Incoming call accepted. This is esp. interesting to stop ringing on other devices. */
+ public static class IncomingCallAccepted extends EventType {
+ /* ID of the chat which the message belongs to. */
+ public Integer chat_id;
+ /* ID of the info message referring to the call. */
+ public Integer msg_id;
+ }
+
+/* Outgoing call accepted. */
+ public static class OutgoingCallAccepted extends EventType {
+ /* User-defined info passed to dc_accept_incoming_call( */
+ public String accept_call_info;
+ /* ID of the chat which the message belongs to. */
+ public Integer chat_id;
+ /* ID of the info message referring to the call. */
+ public Integer msg_id;
+ }
+
+/* Call ended. */
+ public static class CallEnded extends EventType {
+ /* ID of the chat which the message belongs to. */
+ public Integer chat_id;
+ /* ID of the info message referring to the call. */
+ public Integer msg_id;
+ }
+
+/**
+ * One or more transports has changed.
+ *
+ * This event is used for tests to detect when transport synchronization messages arrives. UIs don't need to use it, it is unlikely that user modifies transports on multiple devices simultaneously.
+ */
+ public static class TransportsModified extends EventType {
+ }
+
+}
\ No newline at end of file
diff --git a/src/main/java/chat/delta/rpc/types/FullChat.java b/src/main/java/chat/delta/rpc/types/FullChat.java
new file mode 100644
index 0000000000000000000000000000000000000000..141a57b02e141051111778779a4df08e010e5484
--- /dev/null
+++ b/src/main/java/chat/delta/rpc/types/FullChat.java
@@ -0,0 +1,42 @@
+/* Autogenerated file, do not edit manually */
+package chat.delta.rpc.types;
+
+public class FullChat {
+ public Boolean archived;
+ public Boolean canSend;
+ public ChatType chatType;
+ public String color;
+ public java.util.List