Delta Chat 是一款可靠、去中心化和安全的消息应用程序、 适用于移动和桌面平台。
Delta Chat 感觉就像 Whatsapp 或 Telegram,但你也可以把它当作电子邮件应用程序来使用。 你可以匿名注册到各种可互操作的聊天邮件服务器 这些都是为快速安全运行而优化的最小电子邮件服务器。 您也可以使用传统的电子邮件服务器和现有的电子邮件账户 在这种情况下, Delta Chat 可充当邮件客户端。
要安全地与他人建立联系[扫描邀请二维码 或分享邀请链接](#howtoe2ee)。 使用(默认的)基于chatmail的聊天账户时需要这样做 因为chatmail会拒绝未加密的发送信息。
当使用经典电子邮件地址创建聊天配置文件时 如果您知道联系人的电子邮件地址,您可以手动创建联系人 然后给他们写信息 即使收件人没有使用Delta Chat 。
使用快速、安全、可互操作的 chatmail 服务器 创建匿名聊天账户 为 iOS 和 Android 设备提供即时推送通知。
跨平台支持 [多配置文件](#多账户)和多设备。
交互性 聊天中的网页小程序
经审计的端到端加密 安全地抵御网络和服务器攻击。
免费开源软件,包括应用程序和服务器端。 基于电子邮件和网络互联网标准、 避免 “又一个标准综合症(xkcd 927)”
是的。除纯文本外,所有电子邮件附件均显示为单独的消息。发出消息会根据需要自动获得附件。
为了提高性能,默认情况下会对图像进行优化并以较小的尺寸发送,但您也可以将其作为 “文件 “发送,以保留原始图像。
一份账户资料包括姓名、照片和一些额外的加密信息。 个人配置只存在于您的设备(们)中 并使用聊天邮件或传统电子邮件服务器传输信息。
首次安装Delta Chat 时,会创建第一个账户资料文件。
之后,您可以点击左上角的个人资料图像,添加个人账户 或切换账户。
您可能希望为政治、家庭或工作相关的活动使用不同的账户资料, 或者例如,为专门用于注册网站和平台的“垃圾邮件账户资料”, 这些网站和平台往往会早晚导致未经请求的消息(即“垃圾邮件”)
您可能还想了解 如何在多台设备上使用同一账户资料。
您可以在设置中添加个人资料图片。如果您给您的联系人发消息或者通过二维码添加他们,他们会自动看到您的个人资料图片。
不使用 Delta Chat 的联系人不会看到个人资料图片(不过,他们可以安装 Delta Chat :)
出于隐私原因,在您向他们发送消息之前,没有人会看到您的个人资料照片。
您的个人资料图片并非随每条消息一起发送,但发送的频率足够高。因此即使您的联系人添加了新设备,也能够重新收到您的个人资料图片。
是的, 您可以在“设置 > 个人资料 > 签名文本”下执行此操作。 使用 Delta Chat 的联系人查看您的联系方式时将会看到它。 对其他所有人来说, 它将显示为在您所有消息文本下方的电子邮件签名。
使用这些工具来管理您的聊天,让其井然有序:
已固定聊天会呆在聊天列表顶部。您可以利用其快速访问最喜欢的聊天或临时记下某些东西。
静音聊天,如果您不想再得到关于它们的通知。被静音的聊天会呆在原地,并且您可以固定被静音的聊天。
如果您不想再在聊天列表中看到聊天记录,请归档聊天。 已归档的聊天仍可在聊天列表上方或通过搜索访问。
当被归档的聊天接收到一条新消息,除非其被静音,它会从归档中弹出并返回聊天列表。 被静音的聊天会保持被归档的状态,除非您手动解档它们。
要归档或固定一个聊天,可以长按(Android)、使用聊天内部的菜单(Android/桌面版)或者左滑(iOS); 要静音一个聊天,可以使用聊天内部的菜单(Android/桌面版)或者通过聊天概要(iOS)。
您可以在聊天窗口右上角的聊天设置中通过选择 1 分钟到 5 周之间的时间跨度打开“消息定时销毁”。
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 in each email account on the server, and in the app itself.
请注意,只有当您信任您的聊天伙伴时,您才可以依赖“消息定时销毁”; 不怀好意的人可能会拍照,或者在删除之前以其他方式保存、复制或转发消息。
Apart from that, if one chat partner uninstalls Delta Chat, the messages will not get deleted from their email account. They will most likely also not be decryptable anymore (as long as they were encrypted in the first place).
从成员列表中删除自己,或者删除整个聊天。如果您之后想再加入该群组,请让其他群组成员添加您。
另外,您也可以“静音”群组——这样做意味着您会收到所有消息并且仍可以编写消息,但不会再收到任何新消息的通知。
默认情况下,Delta Chat 会在本地设备上存储您的所有消息。 如果您,例如,想要节省邮件提供商处的存储空间, 那么可以选择配置Delta Chat 以开启服务端自动删除旧消息。 这些消息还将保存在您的设备上,除非您在设备上删除它们。
要打开它,请转到 “聊天和媒体 “设置中的删除旧信息 → 从服务器删除信息。 您可以在 “立即 “和 “1 年后 “之间设置时限。 Delta Chat 收到的所有电子邮件都将在此期限后从服务器中删除。
注意:如果在多台设备上使用 Delta Chat,请将消息在服务器上保存足够长的时间,以便其他设备能够下载消息。在这种情况下,您应当根据其他设备(们)的使用频率,将自动删除设置到“一天后”或相似的选项上。
推送通知由 Apple 和 Google 的“推送服务”发送到用户的设备,以便非活动状态的 Delta Chat 应用可以在后台获取消息,并在需要时在用户的手机上显示通知。
推送通知适用于以下所有 chatmail 服务器:
iOS 设备通过与 Apple Push 服务集成。
Android 设备,通过与 Google FCM Push 服务集成, 包括使用 microG 而不是手机上专有 Google 代码的设备。
自 2024 年 5 月起,传统电子邮件服务器不再支持 Delta Chat 用户的推送通知。
是的,Delta Chat 会自动使用推送通知来接收 chatmail 个人资料。 而且,Apple 手机上没有其他方式可以实现即时消息传递 因为 Apple 设备不允许 Delta Chat 在后台获取数据。 推送通知会自动为 iOS 用户激活,因为 Delta Chat 的隐私保护推送通知系统 不会向 Apple 泄露其尚未拥有的数据。
如果有“推送服务”可用,Delta Chat 将启用推送通知, 以实现所有聊天邮件用户的即时消息传递。 如果您使用的是传统电子邮件提供商而不是 chatmail 服务器,则无法使用推送通知。
在 Delta Chat“通知”的“推送通知”设置中,您可以更改以下影响所有聊天配置文件的设置:
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 e-mail, 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 and stores it on the chatmail server.
When a chatmail server receives an e-mail for a Delta Chat user it forwards the “device token” to the central Delta Chat notification proxy.
The central Delta Chat notification proxy forwards the “device token” to the respective Push service (Apple, Google, etc.), without ever knowing the IP or e-mail address 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 chatmail or e-mail address of the device it wakes up. The central Apple/Google Push services never see an e-mail address (sender or receiver) and also never see any message content (also not in encrypted forms).
As of May 2024, chatmail servers know about “device tokens” but we plan to encrypt this information to the notification proxy such that the chatmail server never learns the device token.
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.
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 and massive chatmail and e-mail system :)
Autocrypt is used for automatically
establishing end-to-end encryption with contacts and group chats.
Autocrypt uses a limited and secure subset of the OpenPGP standard.
End-to-End encrypted messages are marked with a padlock
.
Secure-Join protocols
are used for establishing chats with guaranteed end-to-end encryption
which protects against network attacks and compromised servers.
Chats marked with a green checkmark
guarantee end-to-end encrypted messages.
All end-to-end encrypted messages carry a padlock:
End-to-end encryption is guaranteed if there is a green checkmark next to the chat title:
If you have a second communication channel with your chat partner, like a video chat or a different messenger, you can generate an invite link.
If you are together in person, you can show a QR code to your chat partner.
For Group invitations, tap the chat group title to see its member list, and select “QR Invite code”.
For direct 1:1 chat invitations,
tap the QR Code icon
on the Delta Chat app main screen.
Let your chat partner scan the QR image with their Delta Chat app, or click “Copy” or “Share” to create an invite link and share it with your chat partner.
Now wait while Secure-Join network messages are exchanged between both devices.
If both devices are online,
both sides will eventually see a (group or direct) chat with a green checkmark
next to the title.
如果其中一个设备处于离线状态,则只有当设备再次连接互联网且安全加入网络协议完成时,绿色复选标记才会出现。
恭喜!
从现在开始您将会自动使用安全的端到端加密与此联系人联系,并且双方都可以将对方添加到绿色复选标记的群组
,从而自动在其成员之间传播有保障的端到端加密。
Chat titles with green checkmarks
mean that all messages in the chat will be end-to-end encrypted
and can not be read or altered by compromised e-mail servers or Internet providers.
Joining green-checkmarked group chats
safely spreads everybody’s encryption information (and green checkmarks)
in a manner that guarantees end-to-end encryption in the group and among members.
Contact profiles with green checkmarks
mean that messaging a contact is currently guaranteed to be end-to-end encrypted.
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 contact to a green-checkmarked group becomes an introducer
to those members who didn’t yet know about the added contact.
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.
Note that in a contact profile you may see and tap introducers but there is no green checkmark in the profile title. This usually means that the contact “sent a message from another device”.
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.
Your chat with a contact lost guaranteed end-to-end encryption. The green checkmark was removed for this chat and contact when you see this warning. If you find the sudden drop of guaranteed end-to-end encryption surprising for this contact then don’t accept the warning! Instead check with your contact through a second channel like a video call, other messenger or a phone call, to find out what happened.
If your contact actually caused the drop of guaranteed end-to-end encryption please see the next paragraphs for common reasons and their mitigations. Regardless, all other green-checkmarked chats remain guaranteed end-to-end encrypted even if the contact is a member there.
Your contact is using Delta Chat on a second device (phone or laptop)
If they have another device with a Delta Chat app running, they should remove the profile from the new device and add it as a second device as described here. As soon as they message you afterwards, the warning will be gone and guaranteed encryption is established with both devices of your contact.
Your contact reinstalled Delta Chat using their old account login
If they have a backup file, they should remove the profile from the new device and rather import the backup file to re-create their profile. As soon as they message you afterwards, the warning will be gone and guaranteed encryption is re-established for this contact.
If they don’t have a backup file, it’s best to perform a QR scan with your chat partner to re-establish guaranteed end-to-end encryption.
Your contact sent a mail through a webmail interface or another e-mail app and will get back to using Delta Chat soon again.
If you are sure that the contact sometimes uses webmail, or another mail app lacking end-to-end encryption, then you may accept the warning. As soon as your contact uses Delta Chat again, guaranteed end-to-end encryption will be automatically re-established.
Your contact stopped using Delta Chat entirely
Sometimes remaining in contact is more important than end-to-end encryption. “Transport Layer Encryption” (TLS) may still meaningfully protect the confidentiality of your messages between your device and the e-mail server. But without end-to-end encryption you and your contact are trusting your e-mail server to not read or manipulate your messages, and to not hand them to third parties.
In any case, you can not do much else than accept the warning. Please also remove the contact from any active green-checkmarked group which you can find in “Shared chats” in the Contact profile. This spares your contact from getting “unreadable” messages.
If the contact removed Delta Chat because of buggy or undesirable behaviour, please consider posting to our support forum to help us identify and address common problems. Thanks!
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 and only displays a padlock security indicator on a message if the whole message is properly encrypted and signed. For example, “Detached signatures” are not treated as secure.
OpenPGP is not insecure by itself. Most publically 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.
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 or Saltpack but adopting them would mean breaking end-to-end encryption interoperability with all other e-mail apps that typically support OpenPGP encryption. 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.
不,Delta Chat 从未受到任何 EFAIL 攻击 因为所使用的 OpenPGP 实现了 rPGP 在加密消息时“修改检测代码” 并且如果“修改检测代码”不正确则返回 错误。
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.
Even if your messages are not guaranteed to be end-to-end encrypted, they are still protected from Internet providers like cell or cable companies. However, your and your recipient’s e-mail providers may read, analyze or even modify your messages, including any attachments, if they are not end-to-end encrypted.
Delta Chat by default uses strict TLS encryption which secures connections between your device and your e-mail provider. All of Delta Chat’s TLS-handling has been independently security audited. Moreover, the connection between your and the recipient’s e-mail provider will typically be transport-encrypted as well. If the involved e-mail servers support MTA-STS then transport encryption will be enforced between e-mail providers in which case Delta Chat communications will never be exposed in cleartext to the Internet even if the message was not end-to-end encrypted.
Note that maintaining guaranteed end-to-end encryption on top of TLS encryption provides pervasive safety between your and the recipient’s devices. Not even your e-mail or Internet provider will be able to read or modify your messages.
Delta Chat protects most message metadata by putting the following information into the end-to-end encrypted part of messages:
Chat-Disposition-Notification-To
)Ephemeral-Timer
)Chat-Group-Member-Removed
, Chat-Group-Member-Added
Secure-Join
header containing secure join commandsE-Mail servers do not get access to this protected metadata but they do see the message date as well as the message size, and, more importantly, the sender and receiver addresses. E-mail servers need receiver addresses to route and deliver messages to recipient’s devices.
Both for protecting against metadata-collecting e-mail servers as well as against the threat of device seizure we recommend to use a chatmail server to create pseudonymous temporary profiles through QR-code scans. 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 contacts using temporary profiles can not be identified easily, as compared to messengers which reveal phone numbers in chat groups which in turn are often associated with legal identities.
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.
A little padlock in a message bubble denotes that the message was properly end-to-end encrypted from the given sender. If there is no padlock, the message was not properly end-to-end encrypted most likely because the sender uses an app or webmail interface without support for end-to-end–encryption.
If a contact uses a non-Autocrypt e-mail app, all messages involving this contact (in a group or 1:1 chat) will not be end-to-end encrypted, and thus not show a “padlock” with messages. Note that even if your contacts use Delta Chat on their account, they might also use a non-Autocrypt e-mail app on that account which then may cause intermittently unencrypted messages. Replying unencrypted to unencrypted messages is mandated by Autocrypt to prevent unreadable messages on the side of your contacts and their non-Autocrypt e-mail app.
If you need a safely end-to-end encrypted chat with a contact who is using their e-mail account both with Delta Chat and non-Autocrypt apps (e.g. webmail), it’s best to setup guaranteed end-to-end encryption with them and then create a guaranteed end-to-end encrypted group chat with you two as members. In this group chat all messages will be end-to-end encrypted even if the direct chat between you two has a “… sent a message from another device” warning.
The best way to ensure every message is end-to-end encrypted, and metadata deleted as quickly as possible is using chats with guaranteed end-to-end encryption and turning on disappearing messages.
Guaranteed end-to-end encrypted chats protect against MITM attacks and turning on disappearing messages deletes the messages on the server after a user-configured time.
If you don’t need a longer-lived copy of your messages on the server, you can also turn on “delete messages from server automatically”.
不,Delta Chat 不支持完美前向保密 (PFS)。 这意味着,如果您的 Delta Chat 私人解密密钥泄露, 并且有人收集了您之前传输的消息, 他们将能够使用泄露的解密密钥解密并阅读这些消息。
但请注意,如果有人获得您的解密密钥, 他们通常也能够获得您的消息, 无论是否实施了完全前向保密。 泄露解密密钥的典型现实情况是设备扣押, 我们在关于元数据和设备扣押的回答中讨论了这一点。
It is possible that Delta Chat evolves to support Perfect Forward Secrecy, because OpenPGP is just a container for encrypted messages but encryption key management (and thus key rotation or key “ratcheting”) could be organized in flexible ways. See Seqouia’s PFS prototype for existing experiments in the OpenPGP implementor community.
It depends on what is important to you. Delta Chat does not support PFS like Signal does but it provides guaranteed end-to-end encrypted chats that are safe against compromised servers or corrupted networks. Signal and most other PFS-supporting messengers do not provide a practical scheme for protecting chat groups from network attacks which are arguably more worrysome than a potential attacker who seizes your phone and private encryption setup but somehow not your messages, yet has a full record of all past encrypted messages.
In any case, Delta Chat’s end-to-end encryption uses a secure subset of OpenPGP which has been independently security-audited.
Yes. The best way is to send an Autocrypt Setup Message from the other e-mail client. Look for something like Start Autocrypt Setup Transfer in the settings of the other client and follow the instructions shown there.
Alternatively, you can import the key manually in “Settings -> Advanced settings -> Import secret keys”. Caution: Make sure the key is not protected by a password, or remove the password beforehand.
If you don’t have a key or don’t even know you would need one - don’t worry: Delta Chat generates keys as needed, you don’t have to hit a button for it.
最可能的原因是您的密钥被加密了和/或使用了密码。Delta Chat 不支持这样的密钥。您可以移除密码,之后再尝试导入。如果想保留密码,您 需要创建电子邮件别名来使用 Delta Chat ,这样 Delta Chat 的密钥是绑定到这个电子邮件别名上的
Another common error is having the wrong file ending.
Use the ASCII armored format and an .asc
file ending.
Delta Chat 支持常见的 OpenPGP 私钥格式。然而,不可能使每种来源的私钥都被完整支持。这不是 Delta Chat 的主要目标。实际上,大多数新用户在使用 Delta Chat 之前根本没有密钥。不过,我们确实在尝试支持尽可能多的私钥来源。
移除私钥密码的操作取决于您用于管理 PGP 密钥的软件。对于 Enigmail,您可以在密钥管理窗口中将密码设为空值。 对于 GnuPG,您可以通过命令行来进行设置。对于其他程序,您应该能在网上找到解决方案。
The Delta Chat project underwent four independent security audits and one independent security analysis, from most recent to older:
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.
Yes. Delta Chat 1.36 comes with a new, experimental function for using 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.
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.
In Delta Chat, you can share webxdc apps, attachments with an .xdc
file
extension. They can do very different things, and make Delta Chat a truly
extendable messenger.
We are very grateful for feedback on these features - do you want to share your ideas? Join the Forum to contribute. You may conveniently login via Delta Chat and a QR code scan, another rather stable experiment we run on the side (sic!).
https://meet.jit.si/$ROOM
. The $ROOM
variable will be a random value;
this way, you will have a new random jitsi room every time you call someone.这是提供给尝试服务器端规则的人的实验性设置。在使用某些电子邮件提供商时,您可以将所有带有”Chat-Version”头的邮件移入 DeltaChat 文件夹。并不是所有的提供商都支持此操作;通常情况下,这是由 Delta Chat 应用完成的。
启用“只从 DeltaChat 文件夹获取”是有意义的,仅当您同时完成了:
在这种情况下,Delta Chat 不需要监视收件箱,只监视 DeltaChat 文件夹就足够了。
Change your address in “Settings → Advanced → Password and Account” and enter the password of your new e-mail account (and if necessary, server settings). You will get an information notice about the fact that you are moving to a new address. An additional notice will also show up in your “Device messages” chat.
If possible, let your old e-mail provider forward all messages to your new address.
Tell your contacts that you changed your address. Writing to guaranteed end-to-end encrypted chats and groups, will make them notice your move automatically and they will continue chatting with you using your new address.
Note that Delta Chat will not retrieve messages anymore from your old e-mail provider. If you didn’t configure your e-mail provider to forward messages (step 2.) only those contacts to whom you sent a message in a guaranteed end-to-end encrypted chat will send messages to your new address.
To learn more about this the details behind this, read our blogpost on it.
根据使用的操作系统,系统可能会要求您向本应用授予权限。下面 Delta Chat 使用各类权限进行的操作:
与其他电子邮件程序(比如 Thunderbird、K9-Mail 或 Outlook)一样,本程序需要您的密码来允许您通过它发送邮件。当然,密码仅储存在您的设备上,并只会在登录时发送给您的电子邮件提供商(无论如何,您的提供商总是能够访问您的邮件)。
由于 Delta Chat 是开源的,要验证您的凭据是否被安全地处理了,可以检查源代码。我们很高兴能收到使本应用对我们的所有用户更加安全的反馈。
默认情况下, Delta Chat 会显示所有电子邮件。
At “Settings → Advanced → Show Classic E-Mails”, you can change this. You have these options:
是的,收到的 HTML 邮件会有一个 “显示完整消息 “按钮。 发出的邮件始终使用纯文本。
Delta Chat sets (and encrypts!) the classic e-mail subject automatically to the group name or to the sender name.
So if you want to set the subject yourself, for example for a formal e-mail to a business contact, you can create a group with only yourself and the recipient(s). Set the Chat Title to the Subject you want, and then send your e-mail as the first message. If the recipients don’t use Delta Chat, it will look like a normal, formal e-mail to them. You will get bonus professionalism points if you set a signature text.
向自己发送消息的副本可以确保您在所有设备上收到自己的消息。如果您在使用多台设备时没有打开此设置,那么您将只能看到其他人发过来的消息和您从当前设备发出的消息。
副本会被发送到收件箱,然后会被移动到 DeltaChat 文件夹;它不会被放到“已发送”文件夹里。Delta Chat 从不 将东西上传到已发送文件夹,因为这意味着上传一条消息两次(一次通过 SMTP,一次通过 IMAP 到已发送文件夹)。
“给自己发送副本”的默认设置为 “开”。
监视已发送文件夹的唯一原因是:您在使用Delta Chat软件的同时也使用其他的邮件应用程序(比如 Thunderbird),并且想让邮件分发代理参与聊天对话。
不过,我们推荐使用 Delta Chat 桌面客户端;您可以在 get.delta.chat 下载它。监视“已发送”文件夹的选项是在还没有 Delta Chat 桌面客户端的时候引入的,这个选项可能会在未来消失。
有些人将 Delta Chat 用作常规电子邮件客户端并希望将收件箱文件夹用于其邮件,而不是使用 DeltaChat 文件夹。如果禁用了“监视 DeltaChat 文件夹”,则还应该禁用“将聊天消息移动到 DeltaChat”。否则,删除消息或多设备设置可能无法正常工作。
If you use a default chat profile you can simply uninstall the app. This will automatically trigger deletion of all associated account data on the chatmail server. For more info, please refer to nine.testrun.org account-deletion for the default onboarding server, or the respective page from your chosen 3rd party chatmail server.
If you have set up your chat profile on multiple devices you need to remove it from all devices.
If you are using more than one account, but don’t want to get rid of all of them, you can remove it in the account switcher menu (on android and iOS), or in the sidebar with a right click (in the desktop client).
Accounts on classic e-mail providers will not be deleted automatically; how you can delete your account depends on your e-mail provider. We don’t have any control over e-mail accounts at those providers, so unfortunately we can’t help you with that.
If you want to continue using a classic e-mail account with other apps, but uninstall Delta Chat, it is recommended to leave any group chat before uninstalling Delta Chat. Otherwise you might receive undecryptable messages from those group chats.
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, Amazon App Store, 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 没有接受风险投资,也没有负债累累,更没有承受产生巨额利润或将用户及其朋友和家人卖给广告商(或更糟)的压力。我们宁愿使用目前来自欧盟和美国的公共资金,来帮助我们努力建立一个基于自由开源社区开发的、去中心化的、多样化的聊天消息软件生态系统。
Concretely, Delta Chat developments have so far been funded from these sources, ordered chronologically:
NEXTLEAP欧盟项目资助了以下研究和实施工作:在 2017 年和 2018 年实施的验证组和设置联系协议和通过 Autocrypt整合了端到端加密。
在开放技术基金 2018/2019 年提供的第一笔赠款(约 20 万美元)期间,我们显著改善了安卓应用,发布了第一个桌面测试版,并根据人权方面的用户体验研究进行了功能开发,请参阅我们的结论《需求发现与用户体验报告》。2019/2020 年的第二笔赠款(约 30 万美元)对发布 Delta/iOS 版本,将核心库转换到 Rust ,以及为所有平台开发新功能提供了帮助。
NLnet 基金会 2019/2020 年拨款 4.6 万欧元,用于完成 Rust/Python 绑定并建立聊天机器人生态系统。
在 2021 年,我们从两项下一代互联网提案收到了欧盟的进一步资助,即 EPPD - 电子邮件提供商可移植性目录(约 9.7 万欧元)和 AEAP - 电子邮件地址移植(约 9 万欧元)。这带来了更好的多账户支持,改进的二维码联系人和群组设置,和所有平台上的多处网络改进。
从 2021 年底到 2023 年 3 月,我们从美国民主、人权和劳工局(DRL)获得了互联网自由资金(50 万美元)。这笔资金支持了我们的长期目标,即让Delta Chat 更好用,并与全球范围内的各种电子邮件服务器兼容,而且在经常受到互联网审查制度影响的地方更具弹性和安全性。
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.
我们有时会收到个人的一次性捐款。 例如,2021 年,一位慷慨的人士以 “继续保持良好的发展态势!”为主题通过银行向我们捐赠了4千欧元💜。 我们用这些钱来资助发展活动或支付不容易预测或从公共基金中报销的临时费用。收到更多的捐款也有助于我们作为一个贡献者社区变得更加独立和长期可持续。
最后但并非最不重要的是,数位专家与热心人在没有收到或仅收到少量金钱的情况下为 Delta Chat 的开发做出了贡献。没有他们,Delta Chat 不会发展到、甚至无法接近目前的状况。
上面提到的钱款资助主要是由在弗赖堡(德国)的 merlinux GmbH 组织的,分发给了来自世界各地的十多位贡献者。
请参阅 [Delta Chat 捐款渠道](捐款) 以了解货币捐款和其他捐款的可能性。