deploy: 937c79bc3c

2026-10-23 10:43:05 +00:00 · 2026-07-14 14:20:03 +00:00
1 parent 85890f8f2b
commit 033eed8a92
@@ -652,7 +652,7 @@
 &lt;h2 id=&quot;whats-the-problem&quot; tabindex=&quot;-1&quot;&gt;What&#39;s the problem?&lt;/h2&gt;
 &lt;p&gt;SimpleX network is fully decentralized, without any central component or bootstrap nodes — you could use your own servers from day one. While there is no full list of SimpleX network servers, we see many hundreds of servers in public groups.&lt;/p&gt;
 &lt;p&gt;But a large number of SimpleX app users use the servers pre-configured in the app. Even though the app randomly chooses 4 servers in each connection to improve privacy and security, prior to v6.2 for these users the servers were operated by the same company — ourselves.&lt;/p&gt;
-&lt;p&gt;Our open-source code that we are &lt;a href=&quot;https://simplex.chat/blog/20240426-simplex-legally-binding-transparency-v5-7-better-user-experience.html#legally-binding-transparency&quot;&gt;legally bound to use&lt;/a&gt; doesn&#39;t provide any metadata that could be used to learn who connects to whom. But the privacy of users&#39; connections still depends on us honouring our promises and &lt;a href=&quot;https://simplex.chat/blog/https%3A//github.com/simplex-chat/simplex-chat/blob/stable/simplex-chat/PRIVACY.md&quot;&gt;privacy policy&lt;/a&gt;. Flux servers in the app improve that.&lt;/p&gt;
+&lt;p&gt;Our open-source code that we are &lt;a href=&quot;https://simplex.chat/blog/20240426-simplex-legally-binding-transparency-v5-7-better-user-experience.html#legally-binding-transparency&quot;&gt;legally bound to use&lt;/a&gt; doesn&#39;t provide any metadata that could be used to learn who connects to whom. But the privacy of users&#39; connections still depends on us honouring our promises and &lt;a href=&quot;https://github.com/simplex-chat/simplex-chat/blob/stable/PRIVACY.md&quot;&gt;privacy policy&lt;/a&gt;. Flux servers in the app improve that.&lt;/p&gt;
 &lt;h2 id=&quot;using-two-operators-improves-connection-privacy&quot; tabindex=&quot;-1&quot;&gt;Using two operators improves connection privacy&lt;/h2&gt;
 &lt;img src=&quot;https://simplex.chat/blog/images/20241125-operators-2.png&quot; width=&quot;288&quot; class=&quot;float-to-right&quot; /&gt;
 &lt;p&gt;To ensure that the users&#39; metadata from different servers cannot be combined to discover who talks to whom, the servers in each connection have to be operated by different independent organizations.&lt;/p&gt;
@@ -1301,7 +1301,7 @@ See &lt;a href=&quot;https://simplex.chat/faq/index.html#does-simplex-protect-my
 &lt;p&gt;We are committed to open-source, privacy and security. Here are the recent changes we made:&lt;/p&gt;
 &lt;ul&gt;
 &lt;li&gt;We now have a &lt;a href=&quot;https://simplex.chat/transparency/index.html&quot;&gt;Transparency Reports&lt;/a&gt; page.&lt;/li&gt;
-&lt;li&gt;We updated our &lt;a href=&quot;https://simplex.chat/blog/https%3A//github.com/simplex-chat/simplex-chat/blob/stable/simplex-chat/PRIVACY.md&quot;&gt;Privacy Policy&lt;/a&gt; to remove undefined terms &amp;quot;impermissible&amp;quot; and &amp;quot;acceptable&amp;quot;, which would allow us to remove anything we don&#39;t like, without any clarity on what that is. You can see the edits &lt;a href=&quot;https://github.com/simplex-chat/simplex-chat/pull/4076/files&quot;&gt;here&lt;/a&gt;.&lt;/li&gt;
+&lt;li&gt;We updated our &lt;a href=&quot;https://github.com/simplex-chat/simplex-chat/blob/stable/PRIVACY.md&quot;&gt;Privacy Policy&lt;/a&gt; to remove undefined terms &amp;quot;impermissible&amp;quot; and &amp;quot;acceptable&amp;quot;, which would allow us to remove anything we don&#39;t like, without any clarity on what that is. You can see the edits &lt;a href=&quot;https://github.com/simplex-chat/simplex-chat/pull/4076/files&quot;&gt;here&lt;/a&gt;.&lt;/li&gt;
 &lt;li&gt;We published a new page with &lt;a href=&quot;https://simplex.chat/faq/index.html&quot;&gt;Frequently Asked Questions&lt;/a&gt;, thanks to the guidance from users.&lt;/li&gt;
 &lt;li&gt;We also have a new &lt;a href=&quot;https://simplex.chat/security/index.html&quot;&gt;Security Policy&lt;/a&gt; – we welcome your feedback on it.&lt;/li&gt;
 &lt;/ul&gt;
@@ -2084,12 +2084,12 @@ See &lt;a href=&quot;https://simplex.chat/faq/index.html#does-simplex-protect-my
 &lt;h4 id=&quot;why-not-hosted-groups-with-mls&quot; tabindex=&quot;-1&quot;&gt;Why not hosted groups with MLS?&lt;/h4&gt;
 &lt;p&gt;Initially, we considered the design with the dedicated servers, potentially self-hosted, that host groups. This design would require adopting MLS (or similar) protocol for group-wide key agreement. Unfortunately, this design is not sufficiently resilient and easier to censor than decentralized design. Also, MLS protocol is very complex to implement, requires a centralized component, and reduces forward secrecy. So we decided against this approach.&lt;/p&gt;
 &lt;h4 id=&quot;why-not-fully-decentralized-groups&quot; tabindex=&quot;-1&quot;&gt;Why not fully decentralized groups?&lt;/h4&gt;
-&lt;p&gt;We also &lt;a href=&quot;https://simplex.chat/blog/https%3A//github.com/simplex-chat/simplex-chat/blob/stable/simplex-chat/docs/rfcs/2023-05-02-groups.md&quot;&gt;considered&lt;/a&gt; rumour-mongering protocol, where all members are equal and participate in message dissemination. The problem with this approach is that it adds a lot of traffic for all members, even those who mostly read messages. Also, it still requires establishing a fully connected graph, and with large groups it becomes prohibitively expensive and unreliable, given that many members join public groups for a limited time.&lt;/p&gt;
+&lt;p&gt;We also &lt;a href=&quot;https://github.com/simplex-chat/simplex-chat/blob/stable/docs/rfcs/2023-05-02-groups.md&quot;&gt;considered&lt;/a&gt; rumour-mongering protocol, where all members are equal and participate in message dissemination. The problem with this approach is that it adds a lot of traffic for all members, even those who mostly read messages. Also, it still requires establishing a fully connected graph, and with large groups it becomes prohibitively expensive and unreliable, given that many members join public groups for a limited time.&lt;/p&gt;
 &lt;h4 id=&quot;members-host-the-groups&quot; tabindex=&quot;-1&quot;&gt;Members host the groups&lt;/h4&gt;
 &lt;p&gt;We are now considering a middle-ground - the design where the owners and admins host the group, synchronising the state between them, receiving and re-broadcasting the messages between all members. This puts a higher burden on these members, but these clients can be hosted in the cloud, and also group owners have a larger incentive to maintain group integrity. At the same time, this design is better for the rest of the group members, as they don&#39;t need to establish connections with all other members, only with a limited number of &amp;quot;hosting&amp;quot; members, and it also better protects their privacy, due to the lack of direct connections between most members.&lt;/p&gt;
 &lt;p&gt;This approach avoids the need for a group-wide key agreement protocol, as hosting members are expected to have access to all content anyway, so pair-wise ratchets are sufficient. At the same time the content remains end-to-end encrypted, and protected from the outsiders.&lt;/p&gt;
 &lt;p&gt;This approach also simplifies moderation - the message that needs to be removed simply won&#39;t reach the members before it is moderated (in case of automatic or policy-based moderation).&lt;/p&gt;
-&lt;p&gt;Discovery and content search in such groups will be provided via a dedicated discovery server that will participate in the group, provide an always-online client, and also automatic content moderation functionality - a possible approach to moderation is &lt;a href=&quot;https://simplex.chat/blog/https%3A//github.com/simplex-chat/simplex-chat/blob/stable/simplex-chat/docs/rfcs/2023-05-22-groups-moderation.md&quot;&gt;described here&lt;/a&gt;.&lt;/p&gt;
+&lt;p&gt;Discovery and content search in such groups will be provided via a dedicated discovery server that will participate in the group, provide an always-online client, and also automatic content moderation functionality - a possible approach to moderation is &lt;a href=&quot;https://github.com/simplex-chat/simplex-chat/blob/stable/docs/rfcs/2023-05-22-groups-moderation.md&quot;&gt;described here&lt;/a&gt;.&lt;/p&gt;
 &lt;p&gt;We really look forward to your feedback on this design.&lt;/p&gt;
 &lt;h3 id=&quot;what-about-read-receipts&quot; tabindex=&quot;-1&quot;&gt;What about read receipts?&lt;/h3&gt;
 &lt;p&gt;We have an approximately equal number of users who ask us to add receipts, and those who ask not to add them, even as optional.&lt;/p&gt;
@@ -3631,10 +3631,10 @@ file ---&amp;gt; |   XFTP   | ------&amp;gt;           XFTP            ----&amp;
 &lt;h3 id=&quot;chat-groups&quot; tabindex=&quot;-1&quot;&gt;Chat groups&lt;/h3&gt;
 &lt;p&gt;To create a group use the &lt;code&gt;/g &amp;lt;group&amp;gt;&lt;/code&gt; command. You can then invite contacts to the group by entering the &lt;code&gt;/a &amp;lt;group&amp;gt; &amp;lt;name&amp;gt;&lt;/code&gt; command. Your contact(s) will need to use the &lt;code&gt;/j accept&lt;/code&gt; command to accept the invitation to the group. To send messages to the group, simply enter &lt;code&gt;#&amp;lt;group&amp;gt; &amp;lt;message&amp;gt;&lt;/code&gt;.&lt;/p&gt;
 &lt;p&gt;&lt;strong&gt;Please note:&lt;/strong&gt; Groups are not stored on any server; they are maintained as a list of members in the app database. Sending a message to the group sends a message to each member of the group.&lt;/p&gt;
-&lt;p&gt;&lt;img src=&quot;https://simplex.chat/blog/images/groups.gif&quot; alt=&quot;simplex-chat&quot; /&gt;&lt;/p&gt;
+&lt;p&gt;&lt;img src=&quot;https://simplex.chat/images/groups.gif&quot; alt=&quot;simplex-chat&quot; /&gt;&lt;/p&gt;
 &lt;h3 id=&quot;file-transfer&quot; tabindex=&quot;-1&quot;&gt;File transfer&lt;/h3&gt;
 &lt;p&gt;Sharing files is simple! To send a file to a contact, use the &lt;code&gt;/f @&amp;lt;contact&amp;gt; &amp;lt;file_path&amp;gt;&lt;/code&gt; command. The recipient will have to accept before the file is sent.&lt;/p&gt;
-&lt;p&gt;&lt;img src=&quot;https://simplex.chat/blog/images/files.gif&quot; alt=&quot;simplex-chat&quot; /&gt;&lt;/p&gt;
+&lt;p&gt;&lt;img src=&quot;https://simplex.chat/images/files.gif&quot; alt=&quot;simplex-chat&quot; /&gt;&lt;/p&gt;
 &lt;h2 id=&quot;were-always-looking-for-help&quot; tabindex=&quot;-1&quot;&gt;We&#39;re always looking for help!&lt;/h2&gt;
 &lt;p&gt;We&#39;d really appreciate your comments, criticism and support - a star on the GitHub repo, downloading and testing the chat or any contribution to the project will help a lot – thank you for all your support!&lt;/p&gt;
 &lt;p&gt;&lt;strong&gt;Please note:&lt;/strong&gt; SimpleX Chat is in early stage development: we are still iterating protocols, improving privacy and security, so if you have communication scenarios requiring high security, you should consider some other options for now.&lt;/p&gt;