mirror of
https://github.com/ArcaneChat/android.git
synced 2026-07-03 14:05:24 +02:00
bjoern
1887 lines
89 KiB
HTML
1887 lines
89 KiB
HTML
<!DOCTYPE html>
|
||
<html><head><meta charset="UTF-8" /><meta name="viewport" content="initial-scale=1.0" /><link rel="stylesheet" href="../help.css" /></head><body><ul id="top">
|
||
<li><a href="#什么是-delta-chat">什么是 Delta Chat？</a>
|
||
<ul>
|
||
<li><a href="#如何找到可以聊天的人">如何找到可以聊天的人？</a></li>
|
||
<li><a href="#与其他通信软件相比delta-chat-有哪些优势">与其他通信软件相比，Delta Chat 有哪些优势？</a></li>
|
||
<li><a href="#如果希望收到我从未发送过消息的人的消息该怎么办">如果希望收到我从未发送过消息的人的消息，该怎么办?</a></li>
|
||
<li><a href="#delta-chat-支持图像视频和其他附件吗">Delta Chat 支持图像、视频和其他附件吗？</a></li>
|
||
<li><a href="#multiple-accounts">What are profiles? How can I switch between them?</a></li>
|
||
<li><a href="#谁会看见我的个人资料图片">谁会看见我的个人资料图片？</a></li>
|
||
<li><a href="#signature">我可以为 Delta Chat 设置签名文本/状态/格言吗？</a></li>
|
||
<li><a href="#固定静音归档是什么意思">固定、静音、归档是什么意思？</a></li>
|
||
<li><a href="#绿色圆点代表什么">绿色圆点代表什么？</a></li>
|
||
<li><a href="#ephemeralmsgs">消息定时销毁是如何工作的？</a></li>
|
||
</ul>
|
||
</li>
|
||
<li><a href="#群组">群组</a>
|
||
<ul>
|
||
<li><a href="#创建群组">创建群组</a></li>
|
||
<li><a href="#添加成员到群组">添加成员到群组</a></li>
|
||
<li><a href="#我不小心删除了我自己">我不小心删除了我自己。</a></li>
|
||
<li><a href="#我不想再收到某个群组中的消息了">我不想再收到某个群组中的消息了。</a></li>
|
||
<li><a href="#显示在发出消息旁边的对勾表示什么">显示在发出消息旁边的对勾表示什么？</a></li>
|
||
<li><a href="#打开从服务器删除旧消息后会发生什么">打开“从服务器删除旧消息”后，会发生什么？</a></li>
|
||
<li><a href="#delold">打开“从设备删除旧消息”后，会发生什么？</a></li>
|
||
</ul>
|
||
</li>
|
||
<li><a href="#instant-delivery">Instant message delivery and Push Notifications</a>
|
||
<ul>
|
||
<li><a href="#what-are-push-notifications-how-can-i-get-instant-message-delivery">What are Push Notifications? How can I get instant message delivery?</a></li>
|
||
<li><a href="#are-push-notifications-enabled-on-ios-devices-is-there-an-alternative">Are Push Notifications enabled on iOS devices? Is there an alternative?</a></li>
|
||
<li><a href="#android-push">Are Push notifications enabled / needed on Android devices?</a></li>
|
||
<li><a href="#privacy-notifications">How private are Delta Chat Push Notifications?</a></li>
|
||
<li><a href="#why-does-delta-chat-integrate-with-centralized-proprietary-applegoogle-push-services">Why does Delta Chat integrate with centralized proprietary Apple/Google push services?</a></li>
|
||
</ul>
|
||
</li>
|
||
<li><a href="#加密和安全">加密和安全</a>
|
||
<ul>
|
||
<li><a href="#端到端加密使用了哪些标准-">端到端加密使用了哪些标准 ？</a></li>
|
||
<li><a href="#我如何知道信息是否经过端到端加密whene2e">我如何知道信息是否经过端到端加密？{#whene2e}</a></li>
|
||
<li><a href="#howtoe2ee">How can I get guaranteed end-to-end encryption and green checkmarks?</a></li>
|
||
<li><a href="#e2eeguarantee">What does the green checkmark and “guaranteed end-to-end encryption” mean?</a></li>
|
||
<li><a href="#nocryptanymore">A contact “sent a message from another device”, what can i do?</a></li>
|
||
<li><a href="#are-attachments-pictures-files-audio-etc-end-to-end-encrypted">Are attachments (pictures, files, audio etc.) end-to-end encrypted?</a></li>
|
||
<li><a href="#openpgp-secure">Is OpenPGP secure?</a></li>
|
||
<li><a href="#openpgp-alternatives">Did you consider using alternatives to OpenPGP for end-to-end -encryption?</a></li>
|
||
<li><a href="#is-delta-chat-vulnerable-to-efail">Is Delta Chat vulnerable to EFAIL?</a></li>
|
||
<li><a href="#tls">Is a message exposed in cleartext if end-to-end encryption is not available?</a></li>
|
||
<li><a href="#message-metadata">How does Delta Chat protect metadata in messages?</a></li>
|
||
<li><a href="#device-seizure">How to protect metadata and contacts when a device is seized?</a></li>
|
||
<li><a href="#how-can-i-check-encryption-information">How can i check encryption information?</a></li>
|
||
<li><a href="#how-can-i-check-the-encryption-status-of-messages">How can I check the encryption status of messages?</a></li>
|
||
<li><a href="#why-do-i-see-unencrypted-messages">Why do I see unencrypted messages?</a></li>
|
||
<li><a href="#how-can-i-get-an-end-to-end-encrypted-chat-with-a-delta-chat-contact-who-sometimes-uses-webmail-or-another-non-autocrypt-e-mail-app">How can i get an end-to-end encrypted chat with a Delta Chat contact who sometimes uses webmail or another non-Autocrypt e-mail app?</a></li>
|
||
<li><a href="#how-can-i-ensure-message-end-to-end-encryption-and-deletion">How can I ensure message end-to-end encryption and deletion?</a></li>
|
||
<li><a href="#pfs">Does Delta Chat support Perfect Forward Secrecy?</a></li>
|
||
<li><a href="#is-end-to-end-encryption-of-delta-chat-as-safe-as-signal">Is end-to-end encryption of Delta Chat as safe as Signal?</a></li>
|
||
<li><a href="#我可以重复使用现有的私钥吗">我可以重复使用现有的私钥吗？</a></li>
|
||
<li><a href="#我无法将现有的-pgp-密钥导入-delta-chat">我无法将现有的 PGP 密钥导入 Delta Chat。</a></li>
|
||
<li><a href="#security-audits">Was Delta Chat independently audited for security vulnerabilities?</a></li>
|
||
</ul>
|
||
</li>
|
||
<li><a href="#multiclient">多客户端</a>
|
||
<ul>
|
||
<li><a href="#我能同时在多个设备上使用-delta-chat-吗">我能同时在多个设备上使用 Delta Chat 吗?</a></li>
|
||
<li><a href="#故障排除">故障排除</a></li>
|
||
<li><a href="#backup">Manual Transfer</a></li>
|
||
<li><a href="#有推出-delta-chat-web-客户端的计划吗">有推出 Delta Chat Web 客户端的计划吗？</a></li>
|
||
</ul>
|
||
</li>
|
||
<li><a href="#webxdc">webxdc apps</a>
|
||
<ul>
|
||
<li><a href="#how-private-are-webxdc-apps">How private are webxdc apps?</a></li>
|
||
<li><a href="#where-can-i-get-webxdc-apps">Where can I get webxdc apps?</a></li>
|
||
<li><a href="#how-can-i-create-my-own-webxdc-apps">How can I create my own webxdc apps?</a></li>
|
||
</ul>
|
||
</li>
|
||
<li><a href="#实验性功能">实验性功能</a>
|
||
<ul>
|
||
<li><a href="#怎样在-delta-chat-中使用音频视频通话">怎样在 Delta Chat 中使用音频/视频通话？</a></li>
|
||
<li><a href="#什么是广播列表怎样使用它们">什么是广播列表？怎样使用它们？</a></li>
|
||
<li><a href="#如何与聊天伙伴分享位置">如何与聊天伙伴分享位置？</a></li>
|
||
<li><a href="#实验性的数据库加密到底保护了什么">实验性的数据库加密到底保护了什么？</a></li>
|
||
<li><a href="#为什么我可以选择只监视-deltachat-文件夹">为什么我可以选择只监视 DeltaChat 文件夹？</a></li>
|
||
<li><a href="#如何将我的账户迁移到一个不同的电子邮件地址">如何将我的账户迁移到一个不同的电子邮件地址？</a></li>
|
||
</ul>
|
||
</li>
|
||
<li><a href="#杂项">杂项</a>
|
||
<ul>
|
||
<li><a href="#delta-chat-需要哪些权限">Delta Chat 需要哪些权限？</a></li>
|
||
<li><a href="#delta-chat-可用于-我的-电子邮件提供商吗">Delta Chat 可用于 <em>我的</em> 电子邮件提供商吗？</a></li>
|
||
<li><a href="#i-want-to-manage-my-own-e-mail-server-for-delta-chat-what-do-you-recommend">I want to manage my own e-mail server for Delta Chat. What do you recommend?</a></li>
|
||
<li><a href="#为什么我必须在-delta-chat-中输入我的电子邮件密码-这样安全吗">为什么我必须在 Delta Chat 中输入我的电子邮件密码？ 这样安全吗？</a></li>
|
||
<li><a href="#哪些消息会在-delta-chat-中出现">哪些消息会在 Delta Chat 中出现？</a></li>
|
||
<li><a href="#delta-chat-支持-html-电子邮件吗">Delta Chat 支持 HTML 电子邮件吗？</a></li>
|
||
<li><a href="#can-i-set-the-e-mail-subject-with-delta-chat">Can I set the E-Mail Subject with Delta Chat?</a></li>
|
||
<li><a href="#给自己发送副本设置有什么用处">“给自己发送副本”设置有什么用处？</a></li>
|
||
<li><a href="#为什么我可以选择监视已发送文件夹">为什么我可以选择监视“已发送”文件夹？</a></li>
|
||
<li><a href="#为什么我可以选择不监视-deltachat-文件夹">为什么我可以选择不监视 DeltaChat 文件夹？</a></li>
|
||
<li><a href="#delta-chat-与-protonmail--tutanota--criptext-兼容吗">Delta Chat 与 Protonmail / Tutanota / Criptext 兼容吗？</a></li>
|
||
<li><a href="#如何删除我的账户">如何删除我的账户？</a></li>
|
||
<li><a href="#我对技术细节很感兴趣能告诉我更多吗">我对技术细节很感兴趣。能告诉我更多吗？</a></li>
|
||
<li><a href="#delta-chat-的开发是如何被资助的">Delta Chat 的开发是如何被资助的?</a></li>
|
||
</ul>
|
||
</li>
|
||
</ul>
|
||
|
||
|
||
|
||
<h2 id="什么是-delta-chat">
|
||
|
||
|
||
什么是 Delta Chat？ <a href="#什么是-delta-chat" class="anchor"></a>
|
||
|
||
|
||
</h2>
|
||
|
||
<p>Delta Chat is a reliable, decentralized and secure messaging app,
|
||
available for mobile and desktop platforms.</p>
|
||
|
||
<p>Delta Chat feels like Whatsapp or Telegram but you can also use and regard it as an e-mail app.
|
||
You can signup anonymously to a variety of <a href="https://delta.chat/chatmail">interoperable chatmail servers</a>
|
||
which are minimal e-mail servers optimized for fast and secure operations.
|
||
Or you may use classic e-mail servers and an existing e-mail account
|
||
in which case Delta Chat acts as an e-mail app.</p>
|
||
|
||
<p><img style="float:right; width:50%; max-width:360%; margin:1em;" src="../delta-what-optim.png" /></p>
|
||
|
||
<h3 id="如何找到可以聊天的人">
|
||
|
||
|
||
如何找到可以聊天的人？ <a href="#如何找到可以聊天的人" class="anchor"></a>
|
||
|
||
|
||
</h3>
|
||
|
||
<p>To securely setup contact with others <a href="#howtoe2ee">scan an invite QR code
|
||
or share an invite link</a>.
|
||
This is required when using a (default) chatmail-based chat profile
|
||
because chatmail servers reject un-encrypted outgoing messages.</p>
|
||
|
||
<p>If you create a chat profile with a classic e-mail address
|
||
you may manually create a contact if you know their e-mail address
|
||
and then write a message to them
|
||
even if the recipient is not using Delta Chat.</p>
|
||
|
||
<h3 id="与其他通信软件相比delta-chat-有哪些优势">
|
||
|
||
|
||
与其他通信软件相比，Delta Chat 有哪些优势？ <a href="#与其他通信软件相比delta-chat-有哪些优势" class="anchor"></a>
|
||
|
||
|
||
</h3>
|
||
|
||
<ul>
|
||
<li>
|
||
<p>Anonymous chat profiles with fast, secure and interoperable <a href="https://delta.chat/chatmail">chatmail servers</a>
|
||
which offer instant Push Notifications for iOS and Android devices.</p>
|
||
</li>
|
||
<li>
|
||
<p>Pervasive <a href="#multiple-accounts">multi-profile</a> and multi-device support on all platforms.</p>
|
||
</li>
|
||
<li>
|
||
<p>Interactive <a href="https://webxdc.org/apps">web apps in chats</a> for gaming and collaboration</p>
|
||
</li>
|
||
<li>
|
||
<p><a href="#security-audits">Audited end-to-end encryption</a>
|
||
safe against network and server attacks.</p>
|
||
</li>
|
||
<li>
|
||
<p>Free and Open Source software, both app and server side.
|
||
Built on <a href="https://github.com/deltachat/deltachat-core-rust/blob/master/standards.md">E-mail and Web Internet Standards</a>,
|
||
<a href="https://xkcd.com/927/">to avoid “yet another standard syndrome (xkcd 927)”</a></p>
|
||
</li>
|
||
</ul>
|
||
|
||
<h3 id="如果希望收到我从未发送过消息的人的消息该怎么办">
|
||
|
||
|
||
如果希望收到我从未发送过消息的人的消息，该怎么办? <a href="#如果希望收到我从未发送过消息的人的消息该怎么办" class="anchor"></a>
|
||
|
||
|
||
</h3>
|
||
|
||
<ul>
|
||
<li>来自未知联系人的消息会作为<strong>请求</strong>出现。您需要在回复之前先接收他的请求。</li>
|
||
<li>如果现在不想和他聊天，您也可以“删除”请求。这只会在设备上而 <em>不会</em> 在服务器上删除这条消息。所以您仍可以使用其他电子邮件应用来处理它。</li>
|
||
<li>删除了请求后，来自同一联系人的后续消息仍会作为聊天请求出现，所以您有机会来改变主意。如果您真的不想收到那个人的消息，那么可以考虑 <em>屏蔽</em> 他。</li>
|
||
</ul>
|
||
|
||
<h3 id="delta-chat-支持图像视频和其他附件吗">
|
||
|
||
|
||
Delta Chat 支持图像、视频和其他附件吗？ <a href="#delta-chat-支持图像视频和其他附件吗" class="anchor"></a>
|
||
|
||
|
||
</h3>
|
||
|
||
<ul>
|
||
<li>
|
||
<p>是的。除纯文本外，所有电子邮件附件均显示为单独的消息。发出消息会根据需要自动获得附件。</p>
|
||
</li>
|
||
<li>
|
||
<p>为了提高性能，默认情况下会对图像进行优化并以较小的尺寸发送，但您也可以将其作为 “文件 “发送，以保留原始图像。</p>
|
||
</li>
|
||
</ul>
|
||
|
||
<h3 id="multiple-accounts">
|
||
|
||
|
||
What are profiles? How can I switch between them? <a href="#multiple-accounts" class="anchor"></a>
|
||
|
||
|
||
</h3>
|
||
|
||
<p>A profile is <strong>a name, a picture</strong> and some additional information for encrypting messages.
|
||
A profile lives on your device(s) only
|
||
and uses a chatmail or a classic e-mail server to transport messages.</p>
|
||
|
||
<p>On first installation of Delta Chat a first profile is created.</p>
|
||
|
||
<p>Later, you can tap your profile image in the upper left corner to <strong>Add Profiles</strong>
|
||
or to <strong>Switch Profiles</strong>.</p>
|
||
|
||
<p>You may want to use separate profiles for political, family or work related activities,
|
||
or e. g. for a dedicated “spam-profile” with which you register at websites and platforms
|
||
that tend to cause unsolicited messages (“spam”) sooner or later.</p>
|
||
|
||
<p>You may also wish to learn <a href="#multiclient">how to use the same profile on multiple devices</a>.</p>
|
||
|
||
<h3 id="谁会看见我的个人资料图片">
|
||
|
||
|
||
谁会看见我的个人资料图片？ <a href="#谁会看见我的个人资料图片" class="anchor"></a>
|
||
|
||
|
||
</h3>
|
||
|
||
<ul>
|
||
<li>
|
||
<p>您可以在设置中添加个人资料图片。如果您给您的联系人发消息或者通过二维码添加他们，他们会自动看到您的个人资料图片。</p>
|
||
</li>
|
||
<li>
|
||
<p>不使用 Delta Chat 的联系人不会看到个人资料图片（不过，他们可以安装 Delta Chat :）</p>
|
||
</li>
|
||
<li>
|
||
<p>出于隐私原因，在您向他们发送消息之前，没有人会看到您的个人资料照片。</p>
|
||
</li>
|
||
<li>
|
||
<p>您的个人资料图片并非随每条消息一起发送，但发送的频率足够高。因此即使您的联系人添加了新设备，也能够重新收到您的个人资料图片。</p>
|
||
</li>
|
||
</ul>
|
||
|
||
<h3 id="signature">
|
||
|
||
|
||
我可以为 Delta Chat 设置签名文本/状态/格言吗？ <a href="#signature" class="anchor"></a>
|
||
|
||
|
||
</h3>
|
||
|
||
<p>是的，
|
||
您可以在“设置 > 个人资料 > 签名文本”下执行此操作。
|
||
使用 Delta Chat 的联系人查看您的联系方式时将会看到它。
|
||
对其他所有人来说，
|
||
它将显示为在您所有消息文本下方的电子邮件签名。</p>
|
||
|
||
<h3 id="固定静音归档是什么意思">
|
||
|
||
|
||
固定、静音、归档是什么意思？ <a href="#固定静音归档是什么意思" class="anchor"></a>
|
||
|
||
|
||
</h3>
|
||
|
||
<p>使用这些工具来管理您的聊天，让其井然有序：</p>
|
||
|
||
<ul>
|
||
<li>
|
||
<p><strong>已固定聊天</strong>会呆在聊天列表顶部。您可以利用其快速访问最喜欢的聊天或临时记下某些东西。</p>
|
||
</li>
|
||
<li>
|
||
<p><strong>静音聊天</strong>，如果您不想再得到关于它们的通知。被静音的聊天会呆在原地，并且您可以固定被静音的聊天。</p>
|
||
</li>
|
||
<li>
|
||
<p>如果您不想再在聊天列表中看到聊天记录，请<strong>归档聊天</strong>。
|
||
已归档的聊天仍可在聊天列表上方或通过搜索访问。</p>
|
||
</li>
|
||
<li>
|
||
<p>当被归档的聊天接收到一条新消息，除非其被静音，它会<strong>从归档中弹出</strong>并返回聊天列表。
|
||
<strong>被静音的聊天会保持被归档的状态</strong>，除非您手动解档它们。</p>
|
||
</li>
|
||
</ul>
|
||
|
||
<p>要归档或固定一个聊天，可以长按（Android）、使用聊天内部的菜单（Android/桌面版）或者左滑（iOS）；
|
||
要静音一个聊天，可以使用聊天内部的菜单（Android/桌面版）或者通过聊天概要（iOS）。</p>
|
||
|
||
<h3 id="绿色圆点代表什么">
|
||
|
||
|
||
绿色圆点代表什么？ <a href="#绿色圆点代表什么" class="anchor"></a>
|
||
|
||
|
||
</h3>
|
||
|
||
<ul>
|
||
<li>自 Delta Chat 1.34 版起，您有时可以在联系人头像旁看到一个 “绿点”。
|
||
绿点。这意味着他们 “最近被看到”。</li>
|
||
<li>具体来说：这意味着在过去 10 分钟内，Delta Chat 看到过他们：
|
||
<ul>
|
||
<li>因为他们直接给你发了消息、</li>
|
||
<li>因为他们在你们都是成员的群组里写了什么、</li>
|
||
<li>因为他们向您发送了您所写信息的读取回执、</li>
|
||
</ul>
|
||
</li>
|
||
<li>或者因为他们通过使用 <a href="#webxdc">webxdc 应用程序</a> 向您的 Delta Chat 应用发送数据。</li>
|
||
<li>因此，这并不是实时在线状态 – 如果有人没有立即回复，即使他们看起来是在线的，也不要担心，给他们一些空间 ;-)</li>
|
||
<li>另一方面，别人也不会总是 “看到你在线”。如果您关闭了读取收据功能，他们就不会看到绿点，直到您给他们发消息或给他们所在的群组写信。</li>
|
||
</ul>
|
||
|
||
<h3 id="ephemeralmsgs">
|
||
|
||
|
||
消息定时销毁是如何工作的？ <a href="#ephemeralmsgs" class="anchor"></a>
|
||
|
||
|
||
</h3>
|
||
|
||
<p>您可以在聊天窗口右上角的聊天设置中通过选择 1 分钟到 5 周之间的时间跨度打开“消息定时销毁”。</p>
|
||
|
||
<p>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.</p>
|
||
|
||
<p>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.</p>
|
||
|
||
<p>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).</p>
|
||
|
||
<h2 id="群组">
|
||
|
||
|
||
群组 <a href="#群组" class="anchor"></a>
|
||
|
||
|
||
</h2>
|
||
|
||
<h3 id="创建群组">
|
||
|
||
|
||
创建群组 <a href="#创建群组" class="anchor"></a>
|
||
|
||
|
||
</h3>
|
||
|
||
<ul>
|
||
<li>从右上角的菜单中选择<strong>新建聊天</strong>，然后选择<strong>新建群组</strong>或在 Android/iOS 上点击相应的按钮。</li>
|
||
<li>在随后的屏幕上，选择<strong>群组成员</strong>并起一个<strong>群组名称</strong>。您也可以选择一个<strong>群组头像</strong>。</li>
|
||
<li>当您在群组中发送<strong>第一条消息</strong>时，所有成员都会被告知新群组的信息并可以在该群组中应答（只要您不在群组中发送第一条消息，那么群组对成员就是不可见的）。</li>
|
||
</ul>
|
||
|
||
<h3 id="添加成员到群组">
|
||
|
||
|
||
添加成员到群组 <a href="#添加成员到群组" class="anchor"></a>
|
||
|
||
|
||
</h3>
|
||
|
||
<ul>
|
||
<li>每个群组成员均拥有与其他成员<strong>相同的权限</strong>。因此，每个人都可以删除成员或添加新成员。</li>
|
||
<li>要添加或删除成员，请在聊天中点击群组名称。</li>
|
||
</ul>
|
||
|
||
<h3 id="我不小心删除了我自己">
|
||
|
||
|
||
我不小心删除了我自己。 <a href="#我不小心删除了我自己" class="anchor"></a>
|
||
|
||
|
||
</h3>
|
||
|
||
<ul>
|
||
<li>由于您不再是群组成员，您无法将自己加入到群组中。但是，问题不大，只需在普通聊天中请求其他群组成员将您重新加入即可。</li>
|
||
</ul>
|
||
|
||
<h3 id="我不想再收到某个群组中的消息了">
|
||
|
||
|
||
我不想再收到某个群组中的消息了。 <a href="#我不想再收到某个群组中的消息了" class="anchor"></a>
|
||
|
||
|
||
</h3>
|
||
|
||
<ul>
|
||
<li>
|
||
<p>从成员列表中删除自己，或者删除整个聊天。如果您之后想再加入该群组，请让其他群组成员添加您。</p>
|
||
</li>
|
||
<li>
|
||
<p>另外，您也可以“静音”群组——这样做意味着您会收到所有消息并且仍可以编写消息，但不会再收到任何新消息的通知。</p>
|
||
</li>
|
||
</ul>
|
||
|
||
<h3 id="显示在发出消息旁边的对勾表示什么">
|
||
|
||
|
||
显示在发出消息旁边的对勾表示什么？ <a href="#显示在发出消息旁边的对勾表示什么" class="anchor"></a>
|
||
|
||
|
||
</h3>
|
||
|
||
<ul>
|
||
<li><strong>一个对勾</strong>表示消息已成功发送给您的服务提供商。</li>
|
||
<li><strong>两个对勾</strong>表示至少一个接收者的设备对接收该消息进行了回报。</li>
|
||
<li>接收者或许会禁用已读回执，所以即使您只看见了一个对勾，消息也可能已被阅读。</li>
|
||
<li>反过来说，两个对勾也不一定表示某个人类已阅读或理解了该消息 ;)</li>
|
||
</ul>
|
||
|
||
<h3 id="打开从服务器删除旧消息后会发生什么">
|
||
|
||
|
||
打开“从服务器删除旧消息”后，会发生什么？ <a href="#打开从服务器删除旧消息后会发生什么" class="anchor"></a>
|
||
|
||
|
||
</h3>
|
||
|
||
<ul>
|
||
<li>
|
||
<p>默认情况下，Delta Chat 会在本地设备上存储您的所有消息。如果您，例如，想要节省邮件提供商处的存储空间，那么可以选择开启自动删除旧消息。这些消息还将保存在您的设备上（除非您在设备上删除它们）。</p>
|
||
</li>
|
||
<li>
|
||
<p>To turn it on, go to <strong>Delete Old Messages → Delete Messages from Server</strong>
|
||
in the “Chats and Media” settings.
|
||
You can set a timeframe between “At once” and “After 1 year”.
|
||
All e-mails received by Delta Chat will be deleted from the server after this timeframe.</p>
|
||
</li>
|
||
<li>
|
||
<p>注意：如果在多台设备上使用 Delta Chat，请将消息在服务器上保存足够长的时间，以便其他设备能够下载消息。在这种情况下，您应当根据其他设备的使用频率，将自动删除设置到“一天后”或相似的选项上。</p>
|
||
</li>
|
||
</ul>
|
||
|
||
<h3 id="delold">
|
||
|
||
|
||
打开“从设备删除旧消息”后，会发生什么？ <a href="#delold" class="anchor"></a>
|
||
|
||
|
||
</h3>
|
||
|
||
<ul>
|
||
<li>若要节省设备上的存储空间，可以开启自动删除旧消息。</li>
|
||
<li>找到“聊天与媒体”设置中的“从设备删除旧消息”，在从“一小时后”到“一年后”的一系列选项中选择一个。这样，设备上 <em>所有</em> 比所选择时间长度老的消息将被删除。</li>
|
||
</ul>
|
||
|
||
<h2 id="instant-delivery">
|
||
|
||
|
||
Instant message delivery and Push Notifications <a href="#instant-delivery" class="anchor"></a>
|
||
|
||
|
||
</h2>
|
||
|
||
<h3 id="what-are-push-notifications-how-can-i-get-instant-message-delivery">
|
||
|
||
|
||
What are Push Notifications? How can I get instant message delivery? <a href="#what-are-push-notifications-how-can-i-get-instant-message-delivery" class="anchor"></a>
|
||
|
||
|
||
</h3>
|
||
|
||
<p>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.</p>
|
||
|
||
<p>Push Notifications work with all <a href="https://delta.chat/chatmail">chatmail</a> servers on</p>
|
||
|
||
<ul>
|
||
<li>
|
||
<p>iOS devices, by integrating with Apple Push services.</p>
|
||
</li>
|
||
<li>
|
||
<p>Android devices, by integrating with the Google FCM Push service,
|
||
including on devices that use <a href="https://microg.org">microG</a>
|
||
instead of proprietary Google code on the phone.</p>
|
||
</li>
|
||
</ul>
|
||
|
||
<p>As of May 2024, classic e-mail servers do not support Push Notifications
|
||
for Delta Chat users.</p>
|
||
|
||
<h3 id="are-push-notifications-enabled-on-ios-devices-is-there-an-alternative">
|
||
|
||
|
||
Are Push Notifications enabled on iOS devices? Is there an alternative? <a href="#are-push-notifications-enabled-on-ios-devices-is-there-an-alternative" class="anchor"></a>
|
||
|
||
|
||
</h3>
|
||
|
||
<p>Yes, Delta Chat automatically uses Push Notifications for <a href="https://delta.chat/chatmail">chatmail</a> 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
|
||
<a href="#privacy-notifications">Delta Chat’s privacy-minimizing Push Notification system</a>
|
||
does not expose data to Apple that it doesn’t already have.</p>
|
||
|
||
<h3 id="android-push">
|
||
|
||
|
||
Are Push notifications enabled / needed on Android devices? <a href="#android-push" class="anchor"></a>
|
||
|
||
|
||
</h3>
|
||
|
||
<p>If a “Push Service” is available, Delta Chat enables Push Notifications
|
||
to achieve instant message delivery for all chatmail users.
|
||
If you are using a classic e-mail provider instead of <a href="https://delta.chat/chatmail">chatmail</a> servers,
|
||
Push Notifications are not available.</p>
|
||
|
||
<p>In the Delta Chat “Notifications” settings for “Instant delivery”
|
||
you can change the following settings effecting all chat profiles:</p>
|
||
|
||
<ul>
|
||
<li>
|
||
<p>Use Push Service: the default when using chatmail profiles and if
|
||
a Push service is available on the phone.
|
||
If you have both chatmail and classic e-mail profiles,
|
||
then Push Notification will only work
|
||
for incoming messages on chatmail profiles.</p>
|
||
</li>
|
||
<li>
|
||
<p>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 <a href="https://dontkillmyapp.com">dontkillmyapp.com</a>)
|
||
and Delta Chat might not show incoming messages
|
||
until you manually open the app again.</p>
|
||
</li>
|
||
<li>
|
||
<p>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.</p>
|
||
</li>
|
||
</ul>
|
||
|
||
<p>Both “Background Connection” options are energy-efficient and
|
||
safe to try if you experience messages arrive only with long delays.</p>
|
||
|
||
<h3 id="privacy-notifications">
|
||
|
||
|
||
How private are Delta Chat Push Notifications? <a href="#privacy-notifications" class="anchor"></a>
|
||
|
||
|
||
</h3>
|
||
|
||
<p>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.</p>
|
||
|
||
<p>Here is how Delta Chat apps perform Push Notification delivery:</p>
|
||
|
||
<ul>
|
||
<li>
|
||
<p>A Delta Chat app obtains a “device token” locally and stores it
|
||
on the <a href="https://delta.chat/chatmail">chatmail</a> server.</p>
|
||
</li>
|
||
<li>
|
||
<p>When a <a href="https://delta.chat/chatmail">chatmail</a> server receives an e-mail for a Delta Chat user
|
||
it forwards the “device token” to the central Delta Chat notification proxy.</p>
|
||
</li>
|
||
<li>
|
||
<p>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.</p>
|
||
</li>
|
||
<li>
|
||
<p>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).</p>
|
||
</li>
|
||
</ul>
|
||
|
||
<p>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.</p>
|
||
|
||
<p>The central Delta Chat notification proxy <a href="https://github.com/deltachat/notifiers">is small and fully implemented in Rust</a>
|
||
and forgets about device-tokens as soon as Apple/Google/etc processed them,
|
||
usually in a matter of milliseconds.</p>
|
||
|
||
<p>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.</p>
|
||
|
||
<h3 id="why-does-delta-chat-integrate-with-centralized-proprietary-applegoogle-push-services">
|
||
|
||
|
||
Why does Delta Chat integrate with centralized proprietary Apple/Google push services? <a href="#why-does-delta-chat-integrate-with-centralized-proprietary-applegoogle-push-services" class="anchor"></a>
|
||
|
||
|
||
</h3>
|
||
|
||
<p>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.</p>
|
||
|
||
<p>Note that Delta Chat has a <a href="#privacy-notifications">small and privacy-preserving Push Notification system</a>
|
||
that achieves “instant delivery” of messages for all chatmail servers
|
||
including a potential one <a href="https://delta.chat/chatmail#selfhosted">you might setup yourself without our permission</a>.
|
||
Welcome to the power of the interoperable and massive chatmail and e-mail system :)</p>
|
||
|
||
<h2 id="加密和安全">
|
||
|
||
|
||
加密和安全 <a href="#加密和安全" class="anchor"></a>
|
||
|
||
|
||
</h2>
|
||
|
||
<h3 id="端到端加密使用了哪些标准-">
|
||
|
||
|
||
端到端加密使用了哪些标准 ？ <a href="#端到端加密使用了哪些标准-" class="anchor"></a>
|
||
|
||
|
||
</h3>
|
||
|
||
<p><a href="https://autocrypt.org">Autocrypt</a> is used for automatically
|
||
establishing end-to-end encryption with contacts and group chats.
|
||
Autocrypt uses a limited and <a href="#openpgp-secure">secure subset of the OpenPGP standard</a>.
|
||
End-to-End encrypted messages are marked with a padlock
|
||
<img style="vertical-align:middle; width:1.2em; margin:1px" src="../lock-icon.png" alt="padlock" />.</p>
|
||
|
||
<p><a href="https://securejoin.delta.chat/en/latest/new.html">Secure-Join protocols</a>
|
||
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
|
||
<img style="vertical-align:middle; width:1.5em; margin:1px" src="../green-checkmark.png" alt="green checkmark" />
|
||
guarantee end-to-end encrypted messages.</p>
|
||
|
||
<h3 id="我如何知道信息是否经过端到端加密whene2e">
|
||
|
||
|
||
我如何知道信息是否经过端到端加密？{#whene2e} <a href="#我如何知道信息是否经过端到端加密whene2e" class="anchor"></a>
|
||
|
||
|
||
</h3>
|
||
|
||
<p>All end-to-end encrypted messages carry a padlock:</p>
|
||
|
||
<p><img style="width:160px; margin:1px" src="../lock-screenshot.png" alt="padlock in bubble" /></p>
|
||
|
||
<p>End-to-end encryption is guaranteed if there is a green checkmark next to the chat title:</p>
|
||
|
||
<p><img style="width:211px; margin:1px" src="../green-checkmark-screenshot.png" alt="green checkmark in title" /></p>
|
||
|
||
<h3 id="howtoe2ee">
|
||
|
||
|
||
How can I get guaranteed end-to-end encryption and green checkmarks? <a href="#howtoe2ee" class="anchor"></a>
|
||
|
||
|
||
</h3>
|
||
|
||
<p>Meet your chat partner outside Delta Chat, preferably in person
|
||
but a second channel like a video chat
|
||
or a different messenger is fine as well.
|
||
Perform the following QR show/scan procedure with your chat partner.
|
||
One of you is the “Inviter”, the other is the “Joiner”.</p>
|
||
|
||
<p><strong>Inviter side</strong>:</p>
|
||
|
||
<ul>
|
||
<li>
|
||
<p>Group invitation:
|
||
Tap the chat group title to see its member list, and select “QR Invite code”.
|
||
Share the QR image with the other side either in person or through a second channel.</p>
|
||
</li>
|
||
<li>
|
||
<p>Direct 1:1 chat invitation:
|
||
Tap the QR Code icon <img style="vertical-align:middle; width:1.8em; margin:1px" src="../qr-icon.png" />
|
||
on the Delta Chat app main screen.
|
||
Share the QR image with the other side either in person or through a second channel.</p>
|
||
</li>
|
||
</ul>
|
||
|
||
<p><strong>Joiner side</strong>:</p>
|
||
|
||
<ul>
|
||
<li>
|
||
<p>Tap the QR Code icon <img style="vertical-align:middle; width:1.8em; margin:1px" src="../qr-icon.png" />
|
||
on the Delta Chat app main screen.</p>
|
||
</li>
|
||
<li>
|
||
<p>Choose “SCAN QR CODE” and scan the QR Code
|
||
that you see from your chat partner in a second channel.</p>
|
||
</li>
|
||
<li>
|
||
<p>Tap “OK”</p>
|
||
</li>
|
||
</ul>
|
||
|
||
<p>If the QR code scanning doesn’t work in your situation,
|
||
you can also <strong>Share</strong> (or <strong>Copy to Clipboard</strong>) an equivalent invite link
|
||
to the other person through a second channel.</p>
|
||
|
||
<p><strong>Both Inviter and Joiner</strong>:</p>
|
||
|
||
<p>Wait while <a href="https://securejoin.delta.chat/en/latest/new.html#setup-contact-protocol">Secure-Join network messages are exchanged</a> between both devices.</p>
|
||
|
||
<ul>
|
||
<li>
|
||
<p>If both devices are online,
|
||
both sides will eventually see a (group or direct) chat with a green checkmark
|
||
<img style="vertical-align:middle; width:1.5em; margin:1px" src="../green-checkmark.png" alt="green checkmark" />
|
||
next to the title.</p>
|
||
</li>
|
||
<li>
|
||
<p>If one of the devices is offline, the green checkmarks will only
|
||
appear later when the device is internet-connected again
|
||
and the Secure-Join network protocol completed.</p>
|
||
</li>
|
||
</ul>
|
||
|
||
<p>Congratulations!
|
||
You now will automatically use guaranteed end-to-end encryption
|
||
with this contact and both of you can add each other to green-checkmarked groups
|
||
<img style="vertical-align:middle; width:1.5em; margin:1px" src="../green-checkmark.png" alt="green checkmark" />,
|
||
thereby automatically spreading guaranteed end-to-end encryption among its members.</p>
|
||
|
||
<h3 id="e2eeguarantee">
|
||
|
||
|
||
What does the green checkmark and “guaranteed end-to-end encryption” mean? <a href="#e2eeguarantee" class="anchor"></a>
|
||
|
||
|
||
</h3>
|
||
|
||
<p>Chat titles with green checkmarks
|
||
<img style="vertical-align:middle; width:1.5em; margin:1px" src="../green-checkmark.png" alt="green checkmark" />
|
||
mean that all messages in the chat will be end-to-end encrypted
|
||
and can not be read or altered by compromised e-mail servers or Internet providers.
|
||
Joining green-checkmarked group chats
|
||
safely spreads everybody’s encryption information (and green checkmarks)
|
||
in a manner that guarantees end-to-end encryption in the group and among members.</p>
|
||
|
||
<p>Contact profiles with green checkmarks
|
||
<img style="vertical-align:middle; width:1.5em; margin:1px" src="../green-checkmark.png" alt="green checkmark" />
|
||
mean that messaging a contact is currently guaranteed to be end-to-end encrypted.
|
||
Every green-checkmarked contact either did a direct <a href="#howtoe2ee">QR-scan</a> with you
|
||
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 <a href="#howtoe2ee">QR-scan</a>.</p>
|
||
|
||
<p>Note that in a contact profile you may see and tap introducers
|
||
but there is no green checkmark in the profile title.
|
||
This usually means that the contact <a href="#nocryptanymore">“sent a message from another device”</a>.</p>
|
||
|
||
<p>For more in-depth discussion of “guaranteed end-to-end encryption”
|
||
please see <a href="https://securejoin.delta.chat/en/latest/new.html">Secure-Join protocols</a>
|
||
and specifically read about “Verified Groups”, the technical term
|
||
of what is called here “green-checkmarked” or “guaranteed end-to-end encrypted” chats.</p>
|
||
|
||
<h3 id="nocryptanymore">
|
||
|
||
|
||
A contact “sent a message from another device”, what can i do? <a href="#nocryptanymore" class="anchor"></a>
|
||
|
||
|
||
</h3>
|
||
|
||
<p>Your chat with a contact lost guaranteed end-to-end encryption.
|
||
The green checkmark was removed for this chat and contact when you see this warning.
|
||
<strong>If you find the sudden drop of guaranteed end-to-end encryption
|
||
surprising for this contact then don’t accept the warning!</strong>
|
||
Instead check with your contact through a second channel
|
||
like a video call, other messenger or a phone call,
|
||
to find out what happened.</p>
|
||
|
||
<p>If your contact actually caused the drop of guaranteed end-to-end encryption
|
||
please see the next paragraphs for common reasons and their mitigations.
|
||
Regardless, all other green-checkmarked chats remain guaranteed end-to-end encrypted
|
||
even if the contact is a member there.</p>
|
||
|
||
<p><strong>Your contact is using Delta Chat on a second device (phone or laptop)</strong></p>
|
||
|
||
<p>If they have another device with a Delta Chat app running,
|
||
they should remove the account from the new device
|
||
and add it <a href="#multiclient">as a second device as described here</a>.
|
||
As soon as they message you afterwards, the warning will be gone
|
||
and guaranteed encryption is established with both devices of your contact.</p>
|
||
|
||
<p><strong>Your contact reinstalled Delta Chat using their old account login</strong></p>
|
||
|
||
<p>If they have <a href="#backup">a backup file</a>,
|
||
they should remove the account from the new device
|
||
and rather import the backup file to re-create their account.
|
||
As soon as they message you afterwards, the warning will be gone
|
||
and guaranteed encryption is re-established for this contact.</p>
|
||
|
||
<p>If they don’t have a backup file, it’s best to perform a <a href="#howtoe2ee">QR scan</a>
|
||
with your chat partner to re-establish guaranteed end-to-end encryption.</p>
|
||
|
||
<p><strong>Your contact sent a mail through a webmail interface or another e-mail app
|
||
and will get back to using Delta Chat soon again.</strong></p>
|
||
|
||
<p>If you are sure that the contact sometimes uses webmail,
|
||
or another mail app lacking end-to-end encryption,
|
||
then you may accept the warning.
|
||
As soon as your contact uses Delta Chat again,
|
||
guaranteed end-to-end encryption will be automatically re-established.</p>
|
||
|
||
<p><strong>Your contact stopped using Delta Chat entirely</strong></p>
|
||
|
||
<p>Sometimes remaining in contact is more important than end-to-end encryption.
|
||
<a href="#tls">“Transport Layer Encryption” (TLS)</a> may still meaningfully protect
|
||
the confidentiality of your messages between your device and the e-mail server.
|
||
But without end-to-end encryption you and your contact are trusting your e-mail server
|
||
to not read or manipulate your messages, and to not hand them to third parties.</p>
|
||
|
||
<p>In any case, you can not do much else than accept the warning.
|
||
Please also remove the contact from any active green-checkmarked group
|
||
which you can find in “Shared chats” in the Contact profile.
|
||
This spares your contact from getting “unreadable” messages.</p>
|
||
|
||
<p>If the contact removed Delta Chat because of buggy or undesirable behaviour,
|
||
please consider posting to our <a href="https://support.delta.chat">support forum</a>
|
||
to help us identify and address common problems. Thanks!</p>
|
||
|
||
<h3 id="are-attachments-pictures-files-audio-etc-end-to-end-encrypted">
|
||
|
||
|
||
Are attachments (pictures, files, audio etc.) end-to-end encrypted? <a href="#are-attachments-pictures-files-audio-etc-end-to-end-encrypted" class="anchor"></a>
|
||
|
||
|
||
</h3>
|
||
|
||
<p>Yes.</p>
|
||
|
||
<p>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.</p>
|
||
|
||
<h3 id="openpgp-secure">
|
||
|
||
|
||
Is OpenPGP secure? <a href="#openpgp-secure" class="anchor"></a>
|
||
|
||
|
||
</h3>
|
||
|
||
<p>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.</p>
|
||
|
||
<p>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 <a href="https://github.com/rpgp/rpgp">rPGP</a>,
|
||
available as <a href="https://crates.io/crates/pgp">an independent “pgp” package</a>,
|
||
and <a href="https://delta.chat/assets/blog/2019-first-security-review.pdf">security-audited in 2019</a>.</p>
|
||
|
||
<p>We aim, along with other OpenPGP implementors,
|
||
to further improve security characteristics by implementing the
|
||
<a href="https://datatracker.ietf.org/doc/draft-ietf-openpgp-crypto-refresh/">new IETF OpenPGP Crypto-Refresh</a>
|
||
which was thankfully adopted in summer 2023.</p>
|
||
|
||
<h3 id="openpgp-alternatives">
|
||
|
||
|
||
Did you consider using alternatives to OpenPGP for end-to-end -encryption? <a href="#openpgp-alternatives" class="anchor"></a>
|
||
|
||
|
||
</h3>
|
||
|
||
<p>Yes, we are following efforts like <a href="https://en.wikipedia.org/wiki/Messaging_Layer_Security">MLS</a>
|
||
or <a href="https://saltpack.org/">Saltpack</a>
|
||
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.</p>
|
||
|
||
<p>Delta Chat takes a holistic “usable security” approach
|
||
and works with a wide range of activist groupings as well as
|
||
renowned researchers such as <a href="https://teamusec.de">TeamUSEC</a>
|
||
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 <a href="#device-seizure">device-seizure</a>
|
||
and <a href="#message-metadata">message-metadata</a> questions.</p>
|
||
|
||
<h3 id="is-delta-chat-vulnerable-to-efail">
|
||
|
||
|
||
Is Delta Chat vulnerable to EFAIL? <a href="#is-delta-chat-vulnerable-to-efail" class="anchor"></a>
|
||
|
||
|
||
</h3>
|
||
|
||
<p>No, <a href="https://delta.chat/en/2018-05-15-delta-chat-not-vulnerable-to-efail">Delta Chat never was vulnerable to EFAIL</a>
|
||
because its OpenPGP implementation <a href="https://github.com/rpgp/rpgp">rPGP</a>
|
||
uses Modification Detection Code when encrypting messages
|
||
and returns <a href="https://docs.rs/pgp/latest/pgp/errors/enum.Error.html#variant.MdcError">an error</a>
|
||
if the Modification Detection Code is incorrect.</p>
|
||
|
||
<p>Delta Chat also never was vulnerable to the “Direct Exfiltration” EFAIL attack
|
||
because it only decrypts <code class="language-plaintext highlighter-rouge">multipart/encrypted</code> messages
|
||
which contain exactly one encrypted and signed part,
|
||
as defined by the Autocrypt Level 1 specification.</p>
|
||
|
||
<h3 id="tls">
|
||
|
||
|
||
Is a message exposed in cleartext if end-to-end encryption is not available? <a href="#tls" class="anchor"></a>
|
||
|
||
|
||
</h3>
|
||
|
||
<p>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.</p>
|
||
|
||
<p>Delta Chat by default uses strict
|
||
<a href="https://en.wikipedia.org/wiki/Transport_Layer_Security">TLS encryption</a>
|
||
which secures connections between your device and your e-mail provider.
|
||
All of Delta Chat’s TLS-handling has been independently <a href="#security-audits">security audited</a>.
|
||
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 <a href="https://datatracker.ietf.org/doc/html/rfc8461">MTA-STS</a>
|
||
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.</p>
|
||
|
||
<p>Note that <a href="#howtoe2ee">maintaining guaranteed end-to-end encryption</a> on top of TLS encryption
|
||
provides pervasive safety between your and the recipient’s devices.
|
||
Not even your e-mail or Internet provider will be able to read or modify your messages.</p>
|
||
|
||
<h3 id="message-metadata">
|
||
|
||
|
||
How does Delta Chat protect metadata in messages? <a href="#message-metadata" class="anchor"></a>
|
||
|
||
|
||
</h3>
|
||
|
||
<p>Delta Chat protects most message metadata by putting the following information
|
||
into the end-to-end encrypted part of messages:</p>
|
||
|
||
<ul>
|
||
<li>Subject line</li>
|
||
<li>Group avatar and name</li>
|
||
<li>MDN (read receipt) requests (<code class="language-plaintext highlighter-rouge">Chat-Disposition-Notification-To</code>)</li>
|
||
<li>Disappearing message timer (<code class="language-plaintext highlighter-rouge">Ephemeral-Timer</code>)</li>
|
||
<li><code class="language-plaintext highlighter-rouge">Chat-Group-Member-Removed</code>, <code class="language-plaintext highlighter-rouge">Chat-Group-Member-Added</code></li>
|
||
<li><code class="language-plaintext highlighter-rouge">Secure-Join</code> header containing secure join commands</li>
|
||
<li>Notification about enabling location streaming</li>
|
||
<li>WebRTC room URL</li>
|
||
</ul>
|
||
|
||
<p>E-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.</p>
|
||
|
||
<h3 id="device-seizure">
|
||
|
||
|
||
How to protect metadata and contacts when a device is seized? <a href="#device-seizure" class="anchor"></a>
|
||
|
||
|
||
</h3>
|
||
|
||
<p>Both for protecting against metadata-collecting e-mail servers
|
||
as well as against the threat of device seizure
|
||
we recommend to use a Delta Chat optimized <a href="https://delta.chat/serverguide">e-mail server instance</a>
|
||
to create pseudonymous temporary accounts through QR-code scans.
|
||
Note that Delta Chat apps on all platforms support multiple accounts
|
||
so you can easily use action-specific “1-week” or “1-month” accounts next to your “main” account
|
||
with the knowledge that all temporary account data, along with all metadata, will be deleted.
|
||
Moreover, if a device is seized then contacts using temporary e-mail accounts
|
||
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.</p>
|
||
|
||
<h3 id="how-can-i-check-encryption-information">
|
||
|
||
|
||
How can i check encryption information? <a href="#how-can-i-check-encryption-information" class="anchor"></a>
|
||
|
||
|
||
</h3>
|
||
|
||
<p>You may check the end-to-end encryption status manually in the “Encryption” dialog
|
||
(user profile on Android/iOS or right-click a user’s chat-list item on desktop).
|
||
Delta Chat shows two fingerprints there.
|
||
If the same fingerprints appear on your own and your contact’s device,
|
||
the connection is safe.</p>
|
||
|
||
<h3 id="how-can-i-check-the-encryption-status-of-messages">
|
||
|
||
|
||
How can I check the encryption status of messages? <a href="#how-can-i-check-the-encryption-status-of-messages" class="anchor"></a>
|
||
|
||
|
||
</h3>
|
||
|
||
<p>A little <strong>padlock</strong> in a message bubble denotes
|
||
that the message was properly end-to-end encrypted from the given sender.
|
||
If there is <strong>no padlock</strong>, the message was not properly end-to-end encrypted
|
||
most likely because the sender uses an app or webmail interface
|
||
without support for end-to-end–encryption.</p>
|
||
|
||
<h3 id="why-do-i-see-unencrypted-messages">
|
||
|
||
|
||
Why do I see unencrypted messages? <a href="#why-do-i-see-unencrypted-messages" class="anchor"></a>
|
||
|
||
|
||
</h3>
|
||
|
||
<p>If a contact uses a non-Autocrypt e-mail app,
|
||
all messages involving this contact (in a group or 1:1 chat)
|
||
will not be end-to-end encrypted, and thus not show a “padlock” with messages.
|
||
Note that even if your contacts use Delta Chat on their account,
|
||
they might also use a non-Autocrypt e-mail app on that account
|
||
which then may cause intermittently unencrypted messages.
|
||
Replying unencrypted to unencrypted messages is mandated by Autocrypt
|
||
to prevent unreadable messages on the side of your contacts
|
||
and their non-Autocrypt e-mail app.</p>
|
||
|
||
<h3 id="how-can-i-get-an-end-to-end-encrypted-chat-with-a-delta-chat-contact-who-sometimes-uses-webmail-or-another-non-autocrypt-e-mail-app">
|
||
|
||
|
||
How can i get an end-to-end encrypted chat with a Delta Chat contact who sometimes uses webmail or another non-Autocrypt e-mail app? <a href="#how-can-i-get-an-end-to-end-encrypted-chat-with-a-delta-chat-contact-who-sometimes-uses-webmail-or-another-non-autocrypt-e-mail-app" class="anchor"></a>
|
||
|
||
|
||
</h3>
|
||
|
||
<p>If you need a safely end-to-end encrypted chat with a contact
|
||
who is using their account both with Delta Chat and non-Autocrypt apps (e.g. webmail),
|
||
it’s best to setup <a href="#howtoe2ee">guaranteed end-to-end encryption with them</a>
|
||
and then create a guaranteed end-to-end encrypted group chat with you two as members.
|
||
In this group chat all messages will be end-to-end encrypted
|
||
even if the direct chat between you two has a
|
||
<a href="#nocryptanymore">“… sent a message from another device”</a> warning.</p>
|
||
|
||
<h3 id="how-can-i-ensure-message-end-to-end-encryption-and-deletion">
|
||
|
||
|
||
How can I ensure message end-to-end encryption and deletion? <a href="#how-can-i-ensure-message-end-to-end-encryption-and-deletion" class="anchor"></a>
|
||
|
||
|
||
</h3>
|
||
|
||
<p>The best way to ensure every message is end-to-end encrypted,
|
||
and metadata deleted as quickly as possible
|
||
is <a href="#howtoe2ee">using chats with guaranteed end-to-end encryption</a>
|
||
and turning on <a href="#ephemeralmsgs">disappearing messages</a>.</p>
|
||
|
||
<p>Guaranteed end-to-end encrypted chats protect against <a href="https://en.wikipedia.org/wiki/Man-in-the-middle_attack">MITM attacks</a>
|
||
and turning on disappearing messages deletes the messages
|
||
on the server after a user-configured time.</p>
|
||
|
||
<p>If you don’t need a longer-lived copy of your messages on the server,
|
||
you can also turn on <a href="#delold">“delete messages from server automatically”</a>.</p>
|
||
|
||
<h3 id="pfs">
|
||
|
||
|
||
Does Delta Chat support Perfect Forward Secrecy? <a href="#pfs" class="anchor"></a>
|
||
|
||
|
||
</h3>
|
||
|
||
<p>No, Delta Chat doesn’t support Perfect Forward Secrecy (PFS).
|
||
This means that if your Delta Chat 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.</p>
|
||
|
||
<p>Note, however, that if anyone obtains to your decryption keys,
|
||
they will typically also be able to obtain your messages,
|
||
irrespective if Perfect Forward Secrecy is in place or not.
|
||
The typical real-world situation for leaked decryption keys is device seizure
|
||
which we discuss in our answer <a href="#device-seizure">on metadata and device seizure</a>.</p>
|
||
|
||
<p>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 <a href="https://gitlab.com/sequoia-pgp/openpgp-dr">Seqouia’s PFS prototype</a>
|
||
for existing experiments in the OpenPGP implementor community.</p>
|
||
|
||
<h3 id="is-end-to-end-encryption-of-delta-chat-as-safe-as-signal">
|
||
|
||
|
||
Is end-to-end encryption of Delta Chat as safe as Signal? <a href="#is-end-to-end-encryption-of-delta-chat-as-safe-as-signal" class="anchor"></a>
|
||
|
||
|
||
</h3>
|
||
|
||
<p>It depends on what is important to you.
|
||
Delta Chat <a href="#pfs">does not support PFS</a> like Signal does
|
||
but it provides <a href="#e2eeguarantee">guaranteed end-to-end encrypted chats</a>
|
||
that are safe against compromised servers or corrupted networks.
|
||
Signal and most other PFS-supporting messengers do not provide
|
||
a practical scheme for protecting chat groups from network attacks
|
||
which are arguably more 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.</p>
|
||
|
||
<p>In any case, Delta Chat’s end-to-end encryption uses a <a href="#openpgp-secure">secure subset of OpenPGP</a>
|
||
which has been <a href="https://delta.chat/assets/blog/2019-first-security-review.pdf">independently security-audited</a>.</p>
|
||
|
||
<h3 id="我可以重复使用现有的私钥吗">
|
||
|
||
|
||
我可以重复使用现有的私钥吗？ <a href="#我可以重复使用现有的私钥吗" class="anchor"></a>
|
||
|
||
|
||
</h3>
|
||
|
||
<p>Yes.
|
||
The best way is to send an Autocrypt Setup Message from the other e-mail client.
|
||
Look for something like <strong>Start Autocrypt Setup Transfer</strong> in the settings of the other client and follow the instructions shown there.</p>
|
||
|
||
<p>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.</p>
|
||
|
||
<p>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.</p>
|
||
|
||
<h3 id="我无法将现有的-pgp-密钥导入-delta-chat">
|
||
|
||
|
||
我无法将现有的 PGP 密钥导入 Delta Chat。 <a href="#我无法将现有的-pgp-密钥导入-delta-chat" class="anchor"></a>
|
||
|
||
|
||
</h3>
|
||
|
||
<p>最可能的原因是您的密钥被加密了和/或使用了密码。Delta Chat 不支持这样的密钥。您可以移除密码，之后再尝试导入。如果想保留密码，您
|
||
需要创建电子邮件别名来使用 Delta Chat ，这样 Delta Chat 的密钥是绑定到这个电子邮件别名上的</p>
|
||
|
||
<p>Another common error is having the wrong file ending.
|
||
Use the ASCII armored format and an <code class="language-plaintext highlighter-rouge">.asc</code> file ending.</p>
|
||
|
||
<p>Delta Chat 支持常见的 OpenPGP 私钥格式。然而，不可能使每种来源的私钥都被完整支持。这不是 Delta Chat 的主要目标。实际上，大多数新用户在使用 Delta Chat 之前根本没有密钥。不过，我们确实在尝试支持尽可能多的私钥来源。</p>
|
||
|
||
<p>移除私钥密码的操作取决于您用于管理 PGP 密钥的软件。对于 Enigmail，您可以在密钥管理窗口中将密码设为空值。 对于 GnuPG，您可以<a href="https://github.com/deltachat/deltachat-android/issues/98#issuecomment-378383429">通过命令行</a>来进行设置。对于其他程序，您应该能在网上找到解决方案。</p>
|
||
|
||
<h3 id="security-audits">
|
||
|
||
|
||
Was Delta Chat independently audited for security vulnerabilities? <a href="#security-audits" class="anchor"></a>
|
||
|
||
|
||
</h3>
|
||
|
||
<p>The Delta Chat project underwent four independent security audits and one
|
||
independent security analysis, from most recent to older:</p>
|
||
|
||
<ul>
|
||
<li>
|
||
<p>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 <a href="https://delta.chat/en/2024-03-25-crypto-analysis-securejoin">Hardening Guaranteed End-to-End encryption</a> for more detailed information.</p>
|
||
</li>
|
||
<li>
|
||
<p>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 <a href="https://delta.chat/en/2023-05-22-webxdc-security">here for the full background story on end-to-end security in the web</a>.</p>
|
||
</li>
|
||
<li>
|
||
<p>2023 March, <a href="https://cure53.de">Cure53</a> analyzed both the transport encryption of
|
||
Delta Chat’s network connections and a reproducible mail server setup as
|
||
<a href="https://delta.chat/zh_CN/serverguide">recommended on this site</a>.
|
||
You can read more about the audit <a href="https://delta.chat/en/2023-03-27-third-independent-security-audit">on our blog</a>
|
||
or read the <a href="https://delta.chat/assets/blog/MER-01-report.pdf">full report here</a>.</p>
|
||
</li>
|
||
<li>
|
||
<p>2020, <a href="https://includesecurity.com">Include Security</a> analyzed Delta
|
||
Chat’s Rust <a href="https://github.com/deltachat/deltachat-core-rust/">core</a>,
|
||
<a href="https://github.com/async-email/async-imap">IMAP</a>,
|
||
<a href="https://github.com/async-email/async-smtp">SMTP</a>, and
|
||
<a href="https://github.com/async-email/async-native-tls">TLS</a> 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 <a href="https://delta.chat/assets/blog/2020-second-security-review.pdf">full report here</a>.</p>
|
||
</li>
|
||
<li>
|
||
<p>2019, <a href="https://includesecurity.com">Include Security</a> analyzed Delta
|
||
Chat’s <a href="https://github.com/rpgp/rpgp">PGP</a> and
|
||
<a href="https://github.com/RustCrypto/RSA">RSA</a> 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 <a href="https://delta.chat/assets/blog/2019-first-security-review.pdf">full report here</a>.</p>
|
||
</li>
|
||
</ul>
|
||
|
||
<h2 id="multiclient">
|
||
|
||
|
||
多客户端 <a href="#multiclient" class="anchor"></a>
|
||
|
||
|
||
</h2>
|
||
|
||
<h3 id="我能同时在多个设备上使用-delta-chat-吗">
|
||
|
||
|
||
我能同时在多个设备上使用 Delta Chat 吗? <a href="#我能同时在多个设备上使用-delta-chat-吗" class="anchor"></a>
|
||
|
||
|
||
</h3>
|
||
|
||
<p>Yes. Delta Chat 1.36 comes with a new, experimental function for using the same account on different devices:</p>
|
||
|
||
<ul>
|
||
<li>
|
||
<p>Make sure both devices are on the same Wi-Fi or network</p>
|
||
</li>
|
||
<li>
|
||
<p>On the first device, go to <strong>Settings → Add Second Device</strong>, unlock the screen if needed
|
||
and wait a moment until a QR code is shown</p>
|
||
</li>
|
||
<li>
|
||
<p>On the second device, <a href="https://get.delta.chat">install Delta Chat</a></p>
|
||
</li>
|
||
<li>
|
||
<p>On the second device, start Delta Chat, select <strong>Add as Second Device</strong>, and scan the QR code from the old device</p>
|
||
</li>
|
||
<li>
|
||
<p>Transfer should start after a few seconds and during transfer both devices will show the <strong>progress</strong>.
|
||
Wait until it is finished on both devices.</p>
|
||
</li>
|
||
</ul>
|
||
|
||
<p>In contrast to many other messengers, after successful transfer,
|
||
both <strong>devices are completely independent.</strong>
|
||
One device is not needed for the other to work.</p>
|
||
|
||
<h3 id="故障排除">
|
||
|
||
|
||
故障排除 <a href="#故障排除" class="anchor"></a>
|
||
|
||
|
||
</h3>
|
||
|
||
<ul>
|
||
<li>
|
||
<p>Double-check both devices are in the <strong>same Wi-Fi or network</strong></p>
|
||
</li>
|
||
<li>
|
||
<p>On <strong>Windows</strong>, go to <strong>Control Panel / Network and Internet</strong>
|
||
and make sure, <strong>Private Network</strong> is selected as “Network profile type”
|
||
(after transfer, you can change back to the original value)</p>
|
||
</li>
|
||
<li>
|
||
<p>Your system might have a “personal firewall”,
|
||
which is known to cause problems (especially on Windows).
|
||
<strong>Disable the personal firewall</strong> for Delta Chat on both ends and try again</p>
|
||
</li>
|
||
<li>
|
||
<p><strong>Guest Networks</strong> may not allow devices to communicate with each other.
|
||
If possible, use a non-guest network.</p>
|
||
</li>
|
||
<li>
|
||
<p>Ensure there is <strong>enough storage</strong> on the destination device</p>
|
||
</li>
|
||
<li>
|
||
<p>If transfer started, make sure, the devices <strong>stay active</strong> and do not fall asleep.
|
||
Do not exit Delta Chat.
|
||
(we try hard to make the app work in background, but <a href="https://dontkillmyapp.com">systems tend to kill apps</a>, unfortunately)</p>
|
||
</li>
|
||
<li>
|
||
<p>Delta Chat is <strong>already logged in</strong> on the destination device?
|
||
You can use multiple accounts per device, just <a href="#multiple-accounts">add another account</a></p>
|
||
</li>
|
||
<li>
|
||
<p>If you still have problems or if you <strong>cannot scan a QR code</strong>
|
||
try the <strong>manual transfer</strong> described below</p>
|
||
</li>
|
||
</ul>
|
||
|
||
<h3 id="backup">
|
||
|
||
|
||
Manual Transfer <a href="#backup" class="anchor"></a>
|
||
|
||
|
||
</h3>
|
||
|
||
<p>This method is only recommended if “Add Second Device” as described above does not work.</p>
|
||
|
||
<ul>
|
||
<li>On the old device, go to “Settings -> Chats and media -> Export Backup”. Enter your
|
||
screen unlock PIN, pattern, or password. Then you can click on “Start
|
||
Backup”. This saves the backup file to your device. Now you have to transfer
|
||
it to the other device somehow.</li>
|
||
<li>On the new device, on the login screen, instead of logging into your email
|
||
account, choose “Import Backup”. After import, your conversations, encryption
|
||
keys, and media should be copied to the new device.
|
||
<ul>
|
||
<li><strong>If you use iOS:</strong> and you encounter difficulties, maybe
|
||
<a href="https://support.delta.chat/t/import-backup-to-ios/1628">this guide</a> will
|
||
help you.</li>
|
||
</ul>
|
||
</li>
|
||
<li>You are now synchronized, and can use both devices for sending and receiving
|
||
end-to-end encrypted messages with your communication partners.</li>
|
||
</ul>
|
||
|
||
<h3 id="有推出-delta-chat-web-客户端的计划吗">
|
||
|
||
|
||
有推出 Delta Chat Web 客户端的计划吗？ <a href="#有推出-delta-chat-web-客户端的计划吗" class="anchor"></a>
|
||
|
||
|
||
</h3>
|
||
|
||
<ul>
|
||
<li>目前没有计划，但有一些初步的想法。</li>
|
||
<li>有 2-3 种途径来实现 Delta Chat Web 客户端，但是它们都需要巨大的工作量。目前，我们专注于将稳定的版本作为本地应用程序发布到所有应用程序商店（Google Play/iOS/Windows/macOS/Linux 仓库）。</li>
|
||
<li>如果是因为不能在工作的电脑上安装软件而需要一个 Web 客户端，您可以使用便携版的 Windows 桌面客户端，或者在 Linux 上使用 AppImage 版。您可以在 <a href="https://get.delta.chat">get.delta.chat</a> 找到它们。</li>
|
||
</ul>
|
||
|
||
<h2 id="webxdc">
|
||
|
||
|
||
webxdc apps <a href="#webxdc" class="anchor"></a>
|
||
|
||
|
||
</h2>
|
||
|
||
<p>In Delta Chat, you can share <a href="https://webxdc.org">webxdc apps</a>, attachments with an <code class="language-plaintext highlighter-rouge">.xdc</code> file
|
||
extension. They can do very different things, and make Delta Chat a truly
|
||
extendable messenger.</p>
|
||
|
||
<h3 id="how-private-are-webxdc-apps">
|
||
|
||
|
||
How private are webxdc apps? <a href="#how-private-are-webxdc-apps" class="anchor"></a>
|
||
|
||
|
||
</h3>
|
||
|
||
<ul>
|
||
<li>webxdc apps can not send data to the Internet, or download anything.</li>
|
||
<li>A webxdc app can only exchange data within a Delta Chat chat, with its
|
||
copies on the devices of your chat partners. Other than that, it’s completely
|
||
isolated from the Internet.</li>
|
||
<li>The privacy a webxdc app offers is the privacy of your chat - as long as you
|
||
trust the people you chat with, you can trust the webxdc app as well.</li>
|
||
<li>This also means: it can be a privacy risk to open webxdc apps in chats where
|
||
you don’t trust the members - as you know it from e-mail attachments, where
|
||
you only open attachments from senders you trust, and not from spammers.</li>
|
||
</ul>
|
||
|
||
<h3 id="where-can-i-get-webxdc-apps">
|
||
|
||
|
||
Where can I get webxdc apps? <a href="#where-can-i-get-webxdc-apps" class="anchor"></a>
|
||
|
||
|
||
</h3>
|
||
|
||
<ul>
|
||
<li>In general, anyone can share webxdc apps with each
|
||
other without restrictions.</li>
|
||
<li>You can <a href="https://delta.chat/en/2023-08-11-xstore">send ‘hi’ to xstore@testrun.org</a>
|
||
to see an experimental webxdc appstore.
|
||
All of the apps are open source and for free.</li>
|
||
<li>Many people write their own webxdc apps and post them to <a href="https://support.delta.chat/c/webxdc/20">the Delta Chat
|
||
forum</a>.</li>
|
||
</ul>
|
||
|
||
<h3 id="how-can-i-create-my-own-webxdc-apps">
|
||
|
||
|
||
How can I create my own webxdc apps? <a href="#how-can-i-create-my-own-webxdc-apps" class="anchor"></a>
|
||
|
||
|
||
</h3>
|
||
|
||
<ul>
|
||
<li>webxdc apps are just zip files containing html, css, and javascript code.</li>
|
||
<li>You can extend the <a href="https://github.com/webxdc/hello">Hello World example app</a>
|
||
to get started.</li>
|
||
<li>All else you need to know is written in the
|
||
<a href="https://docs.webxdc.org/">documentation</a>.</li>
|
||
<li>If you have question, you can ask others with experience in the <a href="https://support.delta.chat/c/webxdc/20">Delta Chat
|
||
Forum</a>.</li>
|
||
</ul>
|
||
|
||
<h2 id="实验性功能">
|
||
|
||
|
||
实验性功能 <a href="#实验性功能" class="anchor"></a>
|
||
|
||
|
||
</h2>
|
||
|
||
<p>We are very grateful for feedback on these features - do you want to share
|
||
your ideas? Join the <a href="https://support.delta.chat">Forum</a> to contribute.
|
||
You may conveniently login via Delta Chat and a QR code scan,
|
||
another rather stable experiment we run on the side (sic!).</p>
|
||
|
||
<h3 id="怎样在-delta-chat-中使用音频视频通话">
|
||
|
||
|
||
怎样在 Delta Chat 中使用音频/视频通话？ <a href="#怎样在-delta-chat-中使用音频视频通话" class="anchor"></a>
|
||
|
||
|
||
</h3>
|
||
|
||
<ul>
|
||
<li>To turn on audio/video calls, go to the “experimental features” section in
|
||
the advanced settings and choose a “Video Chat Instance”.</li>
|
||
<li>When you invite others to a video chat, it is opened in your browser/app at
|
||
once. The others receive an e-mail with a link to the video chat.
|
||
This way, it is also compatible if your chat partners don’t use Delta Chat.</li>
|
||
<li>Note that there is no ring tone on the other side, and your chat partners
|
||
will not get interrupted by a video chat invite.</li>
|
||
<li>You can use any video chat service which allows joining by link. Just add the
|
||
link in the settings.</li>
|
||
<li>For example, to use the flagship Jitsi Meet instance, you could enter
|
||
<code class="language-plaintext highlighter-rouge">https://meet.jit.si/$ROOM</code>. The <code class="language-plaintext highlighter-rouge">$ROOM</code> variable will be a random value;
|
||
this way, you will have a new random jitsi room every time you call someone.</li>
|
||
</ul>
|
||
|
||
<h3 id="什么是广播列表怎样使用它们">
|
||
|
||
|
||
什么是广播列表？怎样使用它们？ <a href="#什么是广播列表怎样使用它们" class="anchor"></a>
|
||
|
||
|
||
</h3>
|
||
|
||
<ul>
|
||
<li>使用广播列表，您可以一次性将一条消息发送给多个接收者；当他们回复您时，回复会出现在您与他们的直接 1 对 1 聊天中。 接收者之间无法相互看到。</li>
|
||
<li>从技术上讲，它是密件抄送了许多收件人的电子邮件。</li>
|
||
<li>您可以在高级设置的“实验性功能”部分启用该功能。启用后，您便能在“新建聊天”对话框中新建广播列表了。</li>
|
||
<li>在使用多台设备的情况下，目前广播列表不会在它们之间同步。</li>
|
||
<li>发送到广播列表的消息不会被加密。加密会使接收者们知道还有谁收到了消息，进而破坏了匿名性（出于发送速率限制和网络消耗的原因，向每个人发送单独的邮件会更糟）。</li>
|
||
</ul>
|
||
|
||
<h3 id="如何与聊天伙伴分享位置">
|
||
|
||
|
||
如何与聊天伙伴分享位置？ <a href="#如何与聊天伙伴分享位置" class="anchor"></a>
|
||
|
||
|
||
</h3>
|
||
|
||
<ul>
|
||
<li>You can turn on location streaming in the “experimental features” section of
|
||
the advanced settings.</li>
|
||
<li>Now, if you want to share your location in a chat, go to “attach” and select
|
||
“location”. You can now set a time frame in which your location will be
|
||
streamed to your chat partners, between 5 minutes and 6 hours.</li>
|
||
<li>When your location changes, the others in the chat can view it on a map in
|
||
the chat.</li>
|
||
<li>To see the map and view locations of others, you need to turn on the feature
|
||
in the advanced settings.</li>
|
||
<li>This feature will not share your location with anyone except your chat partners.
|
||
Map tiles are downloaded from <a href="https://openstreetmap.org">OpenStreetMap</a>.</li>
|
||
<li>On desktop, the OS typically can’t determine your location. Instead you can
|
||
right click on the map and describe a location, which is sent to the chat as
|
||
a message, but also appears on the map.</li>
|
||
</ul>
|
||
|
||
<h3 id="实验性的数据库加密到底保护了什么">
|
||
|
||
|
||
实验性的数据库加密到底保护了什么？ <a href="#实验性的数据库加密到底保护了什么" class="anchor"></a>
|
||
|
||
|
||
</h3>
|
||
|
||
<ul>
|
||
<li>目前，数据库加密仍处于高度试验性状态。不要依靠它来提供保护。如果操作系统提供了加密，您还应当使用它。</li>
|
||
<li>数据库加密目前只加密了数据库的行与列，没有加密二进制数据块。这多少意味着您的消息是安全的，但您的附件不是。</li>
|
||
<li>对于 iOS 和 Android，加密密钥存储在系统钥匙串中。这意味着加密安全性和所运行在的操作系统安全性一样。</li>
|
||
<li>由于没有标准方法在不同平台上存储加密密钥，Delta Chat 桌面客户端尚未提供数据库加密。</li>
|
||
</ul>
|
||
|
||
<h3 id="为什么我可以选择只监视-deltachat-文件夹">
|
||
|
||
|
||
为什么我可以选择只监视 DeltaChat 文件夹？ <a href="#为什么我可以选择只监视-deltachat-文件夹" class="anchor"></a>
|
||
|
||
|
||
</h3>
|
||
|
||
<p>这是提供给尝试服务器端规则的人的实验性设置。在使用某些电子邮件提供商时，您可以将所有带有”Chat-Version”头的邮件移入 DeltaChat 文件夹。并不是所有的提供商都支持此操作；通常情况下，这是由 Delta Chat 应用完成的。</p>
|
||
|
||
<p>启用“只从 DeltaChat 文件夹获取”是有意义的，仅当您<strong>同时</strong>完成了：</p>
|
||
|
||
<ul>
|
||
<li>已经启用了将带有 Chat-Version 头的所有消息移入 DeltaChat 文件夹的服务器端规则；和</li>
|
||
<li>已将“显示传统电子邮件”设置为“不显示，仅聊天”。</li>
|
||
</ul>
|
||
|
||
<p>在这种情况下，Delta Chat 不需要监视收件箱，只监视 DeltaChat 文件夹就足够了。</p>
|
||
|
||
<h3 id="如何将我的账户迁移到一个不同的电子邮件地址">
|
||
|
||
|
||
如何将我的账户迁移到一个不同的电子邮件地址？ <a href="#如何将我的账户迁移到一个不同的电子邮件地址" class="anchor"></a>
|
||
|
||
|
||
</h3>
|
||
|
||
<ol>
|
||
<li>
|
||
<p>Change your address in “Settings → Advanced → Password and Account” and
|
||
enter the password of your new 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.</p>
|
||
</li>
|
||
<li>
|
||
<p>If possible, let your old e-mail provider forward all messages to your new address.</p>
|
||
</li>
|
||
<li>
|
||
<p>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.</p>
|
||
</li>
|
||
</ol>
|
||
|
||
<p>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.</p>
|
||
|
||
<p>To learn more about this the details behind this, <a href="https://delta.chat/en/2022-09-14-aeap">read our blogpost on
|
||
it</a>.</p>
|
||
|
||
<h2 id="杂项">
|
||
|
||
|
||
杂项 <a href="#杂项" class="anchor"></a>
|
||
|
||
|
||
</h2>
|
||
|
||
<h3 id="delta-chat-需要哪些权限">
|
||
|
||
|
||
Delta Chat 需要哪些权限？ <a href="#delta-chat-需要哪些权限" class="anchor"></a>
|
||
|
||
|
||
</h3>
|
||
|
||
<p>根据使用的操作系统，系统可能会要求您向本应用授予权限。下面 Delta Chat 使用各类权限进行的操作：</p>
|
||
|
||
<ul>
|
||
<li>Camera <em>(can be disallowed)</em>
|
||
<ul>
|
||
<li>take pictures and videos: for sending Photos</li>
|
||
</ul>
|
||
</li>
|
||
<li>Contacts <em>(can be disallowed)</em>
|
||
<ul>
|
||
<li>read your contacts: to discover contacts to chat with</li>
|
||
</ul>
|
||
</li>
|
||
<li>Location <em>(can be disallowed)</em>
|
||
<ul>
|
||
<li>access approximate location (network location sources): for the location streaming feature</li>
|
||
<li>access precise location (GPS and network location sources): for the location streaming feature</li>
|
||
</ul>
|
||
</li>
|
||
<li>Microphone <em>(can be disallowed)</em>
|
||
<ul>
|
||
<li>record audio: for audio messages</li>
|
||
</ul>
|
||
</li>
|
||
<li>Storage <em>(can be disallowed)</em>
|
||
<ul>
|
||
<li>modify or delete the contents of your SD card: to download message attachments</li>
|
||
<li>read the contents of your SD card: to share files with your contacts</li>
|
||
</ul>
|
||
</li>
|
||
<li>Other app capabilities
|
||
<ul>
|
||
<li>change your audio settings: so you can choose ring tones and volume for notifications and audio messages</li>
|
||
<li>run at startup: so you don’t have to start Delta Chat manually</li>
|
||
<li>control vibration: for notifications</li>
|
||
<li>view network connections: to connect to your E-Mail provider</li>
|
||
<li>prevent phone from sleeping: so you can easier copy the security code during the Autocrypt Setup Message</li>
|
||
<li>have full network access: to connect to your E-Mail provider</li>
|
||
<li>view Wi-Fi connections: to connect to your E-Mail provider</li>
|
||
<li>ask to ignore battery optimisations: for achieving “instant message delivery”</li>
|
||
</ul>
|
||
</li>
|
||
</ul>
|
||
|
||
<h3 id="delta-chat-可用于-我的-电子邮件提供商吗">
|
||
|
||
|
||
Delta Chat 可用于 <em>我的</em> 电子邮件提供商吗？ <a href="#delta-chat-可用于-我的-电子邮件提供商吗" class="anchor"></a>
|
||
|
||
|
||
</h3>
|
||
|
||
<ul>
|
||
<li>有很大的可能性是：可以的 :)
|
||
不过，某些提供商需要一些特殊设置才能正常工作，请参阅<a href="https://providers.delta.chat">提供商概览</a></li>
|
||
</ul>
|
||
|
||
<h3 id="i-want-to-manage-my-own-e-mail-server-for-delta-chat-what-do-you-recommend">
|
||
|
||
|
||
I want to manage my own e-mail server for Delta Chat. What do you recommend? <a href="#i-want-to-manage-my-own-e-mail-server-for-delta-chat-what-do-you-recommend" class="anchor"></a>
|
||
|
||
|
||
</h3>
|
||
|
||
<ul>
|
||
<li>Most mail servers will work well. But what we personally recommend is a
|
||
combination of mailcow and mailadm, as described <a href="https://delta.chat/en/2023-01-27-upcoming-mail-server-workshops">in this
|
||
blogpost</a>.</li>
|
||
<li>You can find an <a href="https://delta.chat/zh_CN/serverguide">installation guide on our website</a>.</li>
|
||
</ul>
|
||
|
||
<h3 id="为什么我必须在-delta-chat-中输入我的电子邮件密码-这样安全吗">
|
||
|
||
|
||
为什么我必须在 Delta Chat 中输入我的电子邮件密码？ 这样安全吗？ <a href="#为什么我必须在-delta-chat-中输入我的电子邮件密码-这样安全吗" class="anchor"></a>
|
||
|
||
|
||
</h3>
|
||
|
||
<p>与其他电子邮件程序（比如 Thunderbird、K9-Mail 或 Outlook）一样，本程序需要您的密码来允许您通过它发送邮件。当然，密码仅储存在您的设备上，并只会在登录时发送给您的电子邮件提供商（无论如何，您的提供商总是能够访问您的邮件）。</p>
|
||
|
||
<p>如果您使用具有 OAuth2 支持的电子邮件提供商，例如 gmail.com 或 yandex.ru，则无需在设备上存储密码。在这种情况下，只有访问令牌被使用。</p>
|
||
|
||
<p>由于 Delta Chat 是开源的，要验证您的凭据是否被安全地处理了，可以检查<a href="https://github.com/deltachat/deltachat-core-rust/blob/master/src/login_param.rs">源代码</a>。我们很高兴能收到使本应用对我们的所有用户更加安全的反馈。</p>
|
||
|
||
<h3 id="哪些消息会在-delta-chat-中出现">
|
||
|
||
|
||
哪些消息会在 Delta Chat 中出现？ <a href="#哪些消息会在-delta-chat-中出现" class="anchor"></a>
|
||
|
||
|
||
</h3>
|
||
|
||
<p>默认情况下， Delta Chat 会显示所有电子邮件。</p>
|
||
|
||
<p>At “Settings → Advanced → Show Classic E-Mails”,
|
||
you can change this. You have these options:</p>
|
||
|
||
<ul>
|
||
<li>“不显示，仅聊天”：只显示由其他 Delta Chat 用户发送的消息和对您 Delta Chat 消息的回复。这在电子邮件地址同时用于处理普通邮件的情况下很有用。</li>
|
||
<li>“全部”：Delta Chat 会显示发送到您电子邮件地址的所有邮件。用于您希望使用 Delta Chat 处理所有电子邮件的情况，这样就不会有消息被落下了。默认设置。</li>
|
||
<li>“已接受的联系人”：Delta Chat 会显示已有聊天的联系人的所有电子邮件，而新聊天只会为 Delta Chat 消息弹出。可用于希望逐一决定是在 Delta Chat 中还是在“普通”电子邮件应用中对话的情况。</li>
|
||
</ul>
|
||
|
||
<h3 id="delta-chat-支持-html-电子邮件吗">
|
||
|
||
|
||
Delta Chat 支持 HTML 电子邮件吗？ <a href="#delta-chat-支持-html-电子邮件吗" class="anchor"></a>
|
||
|
||
|
||
</h3>
|
||
|
||
<p>是的，收到的 HTML 邮件会有一个 “显示完整消息 “按钮。
|
||
发出的邮件始终使用纯文本。</p>
|
||
|
||
<h3 id="can-i-set-the-e-mail-subject-with-delta-chat">
|
||
|
||
|
||
Can I set the E-Mail Subject with Delta Chat? <a href="#can-i-set-the-e-mail-subject-with-delta-chat" class="anchor"></a>
|
||
|
||
|
||
</h3>
|
||
|
||
<p>Delta Chat sets (and <a href="#message-metadata">encrypts</a>!) the classic e-mail subject
|
||
automatically to the group name or to the sender name.</p>
|
||
|
||
<p>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 <a href="#signature">signature text</a>.</p>
|
||
|
||
<h3 id="给自己发送副本设置有什么用处">
|
||
|
||
|
||
“给自己发送副本”设置有什么用处？ <a href="#给自己发送副本设置有什么用处" class="anchor"></a>
|
||
|
||
|
||
</h3>
|
||
|
||
<p>向自己发送消息的副本可以确保您在所有设备上收到自己的消息。如果您在使用多台设备时没有打开此设置，那么您将只能看到其他人发过来的消息和您从当前设备发出的消息。</p>
|
||
|
||
<p>副本会被发送到收件箱，然后会被移动到 DeltaChat 文件夹；它不会被放到“已发送”文件夹里。Delta Chat <em>从不</em> 将东西上传到已发送文件夹，因为这意味着上传一条消息两次（一次通过 SMTP，一次通过 IMAP 到已发送文件夹）。</p>
|
||
|
||
<p>The default setting for “Send Copy to Self” is “on”.</p>
|
||
|
||
<h3 id="为什么我可以选择监视已发送文件夹">
|
||
|
||
|
||
为什么我可以选择监视“已发送”文件夹？ <a href="#为什么我可以选择监视已发送文件夹" class="anchor"></a>
|
||
|
||
|
||
</h3>
|
||
|
||
<p>监视已发送文件夹的唯一原因是：您在同时使用其他的邮件应用程序（比如 Thunderbird），并且想让邮件分发代理参与聊天对话。</p>
|
||
|
||
<p>不过，我们推荐使用 Delta Chat 桌面客户端；您可以在 <a href="https://get.delta.chat">get.delta.chat</a> 下载它。监视“已发送”文件夹的选项是在还没有 Delta Chat 桌面客户端的时候引入的，这个选项可能会在未来消失。</p>
|
||
|
||
<h3 id="为什么我可以选择不监视-deltachat-文件夹">
|
||
|
||
|
||
为什么我可以选择不监视 DeltaChat 文件夹？ <a href="#为什么我可以选择不监视-deltachat-文件夹" class="anchor"></a>
|
||
|
||
|
||
</h3>
|
||
|
||
<p>有些人将 Delta Chat 用作常规电子邮件客户端并希望将收件箱文件夹用于其邮件，而不是使用 DeltaChat 文件夹。如果禁用了“监视 DeltaChat 文件夹”，则还应该禁用“将聊天消息移动到 DeltaChat”。否则，删除消息或多设备设置可能无法正常工作。</p>
|
||
|
||
<h3 id="delta-chat-与-protonmail--tutanota--criptext-兼容吗">
|
||
|
||
|
||
Delta Chat 与 Protonmail / Tutanota / Criptext 兼容吗？ <a href="#delta-chat-与-protonmail--tutanota--criptext-兼容吗" class="anchor"></a>
|
||
|
||
|
||
</h3>
|
||
|
||
<ul>
|
||
<li>Yes and No.</li>
|
||
<li>No, you can not use your Protonmail, Tutanota, or Criptext account with Delta
|
||
Chat; they do not offer receiving mails via IMAP.</li>
|
||
<li>In any case you can use Delta Chat to send Messages to people who use
|
||
Protonmail, Tutanota, or Criptext. Those messages will not be end-to-end
|
||
encrypted, though. The end-to-end encryption those providers offer is not
|
||
compatible with <a href="https://autocrypt.org/">Autocrypt</a>, the standard Delta Chat
|
||
uses.</li>
|
||
<li>Delta Chat can end-to-end-encrypt through any e-mail provider with any
|
||
<a href="https://autocrypt.org/dev-status.html">Autocrypt-enabled e-mail app</a>.</li>
|
||
</ul>
|
||
|
||
<h3 id="如何删除我的账户">
|
||
|
||
|
||
如何删除我的账户？ <a href="#如何删除我的账户" class="anchor"></a>
|
||
|
||
|
||
</h3>
|
||
|
||
<p>As you use an e-mail account for Delta Chat,
|
||
how you can delete your account depends on your e-mail provider.
|
||
We don’t have any control over your e-mail account,
|
||
so unfortunately we can’t help you with that.</p>
|
||
|
||
<p>If you want to keep the account,
|
||
but uninstall Delta Chat,
|
||
it is recommended to leave any group chat before uninstalling Delta Chat.</p>
|
||
|
||
<h3 id="我对技术细节很感兴趣能告诉我更多吗">
|
||
|
||
|
||
我对技术细节很感兴趣。能告诉我更多吗？ <a href="#我对技术细节很感兴趣能告诉我更多吗" class="anchor"></a>
|
||
|
||
|
||
</h3>
|
||
|
||
<ul>
|
||
<li>请参阅 <a href="https://github.com/deltachat/deltachat-core-rust/blob/master/standards.md#standards-used-in-delta-chat">Delta Chat 中使用的标准</a>。</li>
|
||
</ul>
|
||
|
||
<h3 id="delta-chat-的开发是如何被资助的">
|
||
|
||
|
||
Delta Chat 的开发是如何被资助的? <a href="#delta-chat-的开发是如何被资助的" class="anchor"></a>
|
||
|
||
|
||
</h3>
|
||
|
||
<p>Delta Chat 没有接受风险投资，也没有负债累累，更没有承受产生巨额利润或将用户及其朋友和家人卖给广告商（或更糟）的压力。我们宁愿使用（目前来自欧盟和美国的）公共资金，来帮助我们努力建立一个基于自由开源社区开发的、去中心化的、多样化的聊天消息（软件）生态系统。</p>
|
||
|
||
<p>具体来说，到目前为止，对 Delta Chat 开发的资助有这些来源：</p>
|
||
|
||
<ul>
|
||
<li>
|
||
<p>The <a href="https://nextleap.eu">NEXTLEAP</a> 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 <a href="https://autocrypt.org">Autocrypt</a>.</p>
|
||
</li>
|
||
<li>
|
||
<p>在<a href="https://opentechfund.org">开放技术基金</a> 2018/2019 年提供的第一笔赠款（约 20 万美元）期间，我们显著改善了安卓应用，发布了第一个桌面测试版，并根据人权方面的用户体验研究进行了功能开发，请参阅我们的结论<a href="https://delta.chat/en/2019-07-19-uxreport">《需求发现与用户体验报告》</a>。2019/2020 年的第二笔赠款（约 30 万美元）对发布 Delta/iOS 版本，将核心库转换到 Rust ，以及为所有平台开发新功能提供了帮助。</p>
|
||
</li>
|
||
<li>
|
||
<p>The <a href="https://nlnet.nl/">NLnet foundation</a> granted in 2019/2020 EUR 46K for
|
||
completing Rust/Python bindings and instigating a Chat-bot eco-system.</p>
|
||
</li>
|
||
<li>
|
||
<p>在 2021 年，我们从两项下一代互联网提案收到了欧盟的进一步资助，即 <a href="https://dapsi.ngi.eu/hall-of-fame/eppd/">EPPD - 电子邮件提供商可移植性目录</a>（约 9.7 万欧元）和 <a href="https://nlnet.nl/project/EmailPorting/">AEAP - 电子邮件地址移植</a>（约 9 万欧元）。这带来了更好的多账户支持，改进的二维码联系人和群组设置，和所有平台上的多处网络改进。</p>
|
||
</li>
|
||
<li>
|
||
<p>From End 2021 till March 2023 we received <em>Internet Freedom</em> 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 e-mail servers world-wide, and more resilient and secure
|
||
in places often affected by internet censorship and shutdowns.</p>
|
||
</li>
|
||
<li>
|
||
<p>Beginning 2023 we got accepted in the Next Generation Internet (NGI)
|
||
Entrust program for our “Private Decentralized Apps” proposals.
|
||
Exact amount is to be determined (around 100K EUR).
|
||
This funding supports further developments of <a href="https://webxdc.org">webxdc “apps shared in a chat”</a>.</p>
|
||
</li>
|
||
<li>
|
||
<p>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.</p>
|
||
|
||
|
||
</li>
|
||
<li>
|
||
<p>最后但并非最不重要的是，数位专家与热心人在没有收到或仅收到少量金钱的情况下为 Delta Chat 的开发做出了贡献。没有他们，Delta Chat 不会发展到、甚至无法接近目前的状况。</p>
|
||
</li>
|
||
</ul>
|
||
|
||
<p>上面提到的钱款资助主要是由在弗赖堡（德国）的 merlinux GmbH 组织的，分发给了来自世界各地的十多位贡献者。</p>
|
||
|
||
<p>Please see <a href="https://delta.chat/zh_CN/contribute">Delta Chat Contribution channels</a>
|
||
for both monetary and and other contribution possibilities.</p>
|
||
|
||
|
||
|
||
|
||
</body></html> |