deploy: ed3365bb6d

2026-08-06 23:39:54 +00:00 · 2024-05-16 17:17:36 +00:00
parent c27a8be2b2
commit dd6586fe9e
59 changed files with 998 additions and 231 deletions
@@ -390,10 +390,10 @@ window.addEventListener('scroll',changeHeaderBg);
 <h3 id="chat-groups" tabindex="-1">Chat groups</h3>
 <p>To create a group use the <code>/g &lt;group&gt;</code> command. You can then invite contacts to the group by entering the <code>/a &lt;group&gt; &lt;name&gt;</code> command. Your contact(s) will need to use the <code>/j accept</code> command to accept the invitation to the group. To send messages to the group, simply enter <code>#&lt;group&gt; &lt;message&gt;</code>.</p>
 <p><strong>Please note:</strong> 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.</p>
-<p><img src="../images/groups.gif" alt="simplex-chat"></p>
+<p><img src="images/groups.gif" alt="simplex-chat"></p>
 <h3 id="file-transfer" tabindex="-1">File transfer</h3>
 <p>Sharing files is simple! To send a file to a contact, use the <code>/f @&lt;contact&gt; &lt;file_path&gt;</code> command. The recipient will have to accept before the file is sent.</p>
-<p><img src="../images/files.gif" alt="simplex-chat"></p>
+<p><img src="images/files.gif" alt="simplex-chat"></p>
 <h2 id="were-always-looking-for-help" tabindex="-1">We're always looking for help!</h2>
 <p>We'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!</p>
 <p><strong>Please note:</strong> 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.</p>
@@ -389,7 +389,7 @@ window.addEventListener('scroll',changeHeaderBg);
 <li>additional layer of E2E encryption in each message queue (to prevent traffic correlation when multiple queues are used in a conversation - something we plan later this year).</li>
 <li>additional encryption of messages delivered from servers to recipients (also to prevent traffic correlation).</li>
 </ul>
-<p>You can read more details in our recent <a href="20220112-simplex-chat-v1-released.html">v1 announcement</a>.</p>
+<p>You can read more details in our recent <a href="/blog/20220112-simplex-chat-v1-released.html">v1 announcement</a>.</p>
 <h2 id="join-our-public-beta" tabindex="-1">Join our public beta!</h2>
 <p>Install the app <a href="https://testflight.apple.com/join/DWuT2LQu">via TestFlight</a>, connect to us (via <strong>Connect to SimpleX team</strong> link in the app) and to a couple of your friends you usually send messages to - and please let us know what you think!</p>
 <p>We would really appreciate any feedback to improve the app and to decide which additional features should be included in our public release in March.</p>
@@ -403,7 +403,7 @@ window.addEventListener('scroll',changeHeaderBg);
 <li>additional layer of E2E encryption in each message queue (to prevent traffic correlation when multiple queues are used in a conversation - something we plan later this year).</li>
 <li>additional encryption of messages delivered from servers to recipients (also to prevent traffic correlation).</li>
 </ul>
-<p>You can read more technical details in our recent <a href="20220112-simplex-chat-v1-released.html">v1 announcement</a>.</p>
+<p>You can read more technical details in our recent <a href="/blog/20220112-simplex-chat-v1-released.html">v1 announcement</a>.</p>
 <p>A big thank you to <a href="https://github.com/angerman">@angerman</a> for making it possible to compile our Haskell code to mobile platforms and getting it approved on app stores - it has been a non-trivial project, and it is still ongoing.</p>
 <h2 id="install-the-apps-and-make-a-private-connection" tabindex="-1">Install the apps and make a private connection!</h2>
 <p>Once you install the app, you can connect to anybody:</p>
@@ -381,7 +381,7 @@ window.addEventListener('scroll',changeHeaderBg);
      <div class="py-6 md:p-[60px]"><h1 id="instant-notifications-for-simplex-chat-mobile-apps" tabindex="-1">Instant notifications for SimpleX Chat mobile apps</h1>
 <p><strong>Published:</strong> April 04, 2022</p>
 <h2 id="simplex-chat-is-the-first-chat-platform-that-is-100percent-private-by-design-it-has-no-access-to-your-connections" tabindex="-1">SimpleX Chat is the first chat platform that is 100% private by design - it has no access to your connections</h2>
-<p>Since we released SimpleX Chat mobile apps couple of weeks ago we've had a lot of excitement from our users - nearly 2000 people downloaded the app after <a href="20220308-simplex-chat-mobile-apps.html">the announcement</a>!</p>
+<p>Since we released SimpleX Chat mobile apps couple of weeks ago we've had a lot of excitement from our users - nearly 2000 people downloaded the app after <a href="/blog/20220308-simplex-chat-mobile-apps.html">the announcement</a>!</p>
 <p>Huge thanks to everybody who downloaded and connected to us via the chat - there were many great questions and suggestions, and on some days I spent most of the time chatting to our users :)</p>
 <p>Since we released the app, we've added and released:</p>
 <ul>
@@ -420,7 +420,7 @@ window.addEventListener('scroll',changeHeaderBg);
 <p>iOS is much more protective of what apps are allowed to run on the devices, and the solution that worked on Android is not viable on iOS.</p>
 <p>We already have background refresh in the iOS app that periodically checks for new messages, and if you use the app every day it delivers notifications within 10 or 20 minutes. It is not instant, but it may be usable for some. If you use the app infrequently, however, this delay can become several hours, or your phone may stop checking for the new messages completely. This is not ideal!</p>
 <p>The only solution known to us is using Apple's push notifications service (APN) to deliver push notifications.</p>
-<p>We planned for it, so we added to <a href="20220112-simplex-chat-v1-released.html">v1 of SMP</a> (the protocol used by our servers) an extension allowing the client to subscribe to notifications from message queues, via separate queue addresses, and using separate cryptographic keys for each queue. This has to be enabled by the client for each queue separately. We haven't used this extension so far, and now we are building a SimpleX notification service based on it.</p>
+<p>We planned for it, so we added to <a href="/blog/20220112-simplex-chat-v1-released.html">v1 of SMP</a> (the protocol used by our servers) an extension allowing the client to subscribe to notifications from message queues, via separate queue addresses, and using separate cryptographic keys for each queue. This has to be enabled by the client for each queue separately. We haven't used this extension so far, and now we are building a SimpleX notification service based on it.</p>
 <p>If the user enables push notifications, then for each contact the app would enable a notification subscription and pass credentials to the notification server together with the device token required to deliver push notifications to user's device.</p>
 <p>The notification server will subscribe to these notifications from SMP servers. The notifications do not include any message content, only the signal that a message has arrived to the server. Notification server is only allowed to send 2-3 hidden notifications per hour to the device. The notification is end-to-end encrypted and contains information about which server has a message, so that the client can connect to the server, retrieve and decrypt the message, and show the notification to the users including sender name and the message content. None of this information is shared with any server.</p>
 <p>If the user receives more than 2-3 messages per hour, the notification server can send additional visible notifications that would simply say &quot;you have a new message&quot;, and the user will have to open the app to receive and see these messages. We are also investigating whether we can use &quot;mutable-content&quot; notifications that allow doing some processing when the notification arrives before showing it to the users.</p>
@@ -384,8 +384,8 @@ window.addEventListener('scroll',changeHeaderBg);
 <p>In this version you can irreversibly delete individual messages after they were deleted by a sender, and also completely clear the conversation.</p>
 <p>The only way to do it before this version was by deleting the contact, now you can keep the connection when you clear the conversation.</p>
 <p><img src="./images/20220524-clear-chat1.png" width="240"> <img src="./images/20220524-clear-chat2.png" width="240"></p>
-<p>See <a href="20220112-simplex-chat-v1-released.html">v1 announcement</a> for information on how SimpleX protects the security of the messages.</p>
-<p>See <a href="20220511-simplex-chat-v2-images-files.html">v2 announcement</a> for more information about SimpleX platform and how it works.</p>
+<p>See <a href="/blog/20220112-simplex-chat-v1-released.html">v1 announcement</a> for information on how SimpleX protects the security of the messages.</p>
+<p>See <a href="/blog/20220511-simplex-chat-v2-images-files.html">v2 announcement</a> for more information about SimpleX platform and how it works.</p>
 <p>Read about SimpleX design in <a href="https://github.com/simplex-chat/simplexmq/blob/master/protocol/overview-tjr.md">whitepaper</a>.</p>
 </div>
    </section>
@@ -380,7 +380,7 @@ window.addEventListener('scroll',changeHeaderBg);
    <section id="article" class="container mb-[75px] bg-white dark:bg-[#17203D] px-5">
      <div class="py-6 md:p-[60px]"><h1 id="simplex-chat-v22-the-new-privacy-and-security-features" tabindex="-1">SimpleX Chat v2.2 - the new privacy and security features</h1>
 <p><strong>Published:</strong> June 4, 2022</p>
-<p>See <a href="20220511-simplex-chat-v2-images-files.html">v2 announcement</a> for more information about SimpleX platform and how it protects your privacy by avoiding user identities of any kind in its design - SimpleX, unlike any other messaging platform, has no identity keys or any numbers that identify its users.</p>
+<p>See <a href="/blog/20220511-simplex-chat-v2-images-files.html">v2 announcement</a> for more information about SimpleX platform and how it protects your privacy by avoiding user identities of any kind in its design - SimpleX, unlike any other messaging platform, has no identity keys or any numbers that identify its users.</p>
 <h2 id="new-privacy-and-security-settings-in-version-22" tabindex="-1">New Privacy and Security settings in version 2.2</h2>
 <img src="./images/20220604-privacy-settings.png" width="480">
 <h3 id="protect-your-chats" tabindex="-1">Protect your chats</h3>
@@ -403,7 +403,7 @@ window.addEventListener('scroll',changeHeaderBg);
 <h3 id="there-is-more" tabindex="-1">There is more</h3>
 <p>You can discover additional features we are currently testing in Experimental Features - they will be announced later!</p>
 <h2 id="more-information" tabindex="-1">More information</h2>
-<p>See <a href="20220112-simplex-chat-v1-released.html">v1 announcement</a> for information on how SimpleX protects the security of the messages.</p>
+<p>See <a href="/blog/20220112-simplex-chat-v1-released.html">v1 announcement</a> for information on how SimpleX protects the security of the messages.</p>
 <p>Read about SimpleX design in <a href="https://github.com/simplex-chat/simplexmq/blob/master/protocol/overview-tjr.md">whitepaper</a>.</p>
 </div>
    </section>
@@ -388,7 +388,7 @@ window.addEventListener('scroll',changeHeaderBg);
 <li><a href="#protocol-privacy-and-performance-improvements">protocol privacy and performance improvements</a></li>
 </ul>
 <h3 id="instant-notifications-for-ios" tabindex="-1">Instant notifications for iOS</h3>
-<p>I wrote previously about <a href="20220404-simplex-chat-instant-notifications.html#problem---users-expect-to-be-instantly-notified-when-messages-arrive">our design for iOS notifications</a> - this is now released. The app will offer to migrate the database when updated, and then you need to choose notifications mode – instant or periodic push notifications, or previously available periodic background refresh that does not use push notifications.</p>
+<p>I wrote previously about <a href="/blog/20220404-simplex-chat-instant-notifications.html#problem---users-expect-to-be-instantly-notified-when-messages-arrive">our design for iOS notifications</a> - this is now released. The app will offer to migrate the database when updated, and then you need to choose notifications mode – instant or periodic push notifications, or previously available periodic background refresh that does not use push notifications.</p>
 <p>To deliver the notifications to iOS devices we use our notification server, as there is a single private key that Apple issues for the app. This server has minimal amount of information about your chat activity:</p>
 <ul>
 <li>it does not have the addresses of messaging queues used to send and receive messages - there is an additional address used for notification server to receive notifications from the messaging servers.</li>
@@ -418,7 +418,7 @@ window.addEventListener('scroll',changeHeaderBg);
 <h3 id="protocol-privacy-and-performance-improvements" tabindex="-1">Protocol privacy and performance improvements</h3>
 <p>Adding push notifications for iOS required SimpleX Messaging Protocol changes. We managed not just to keep the same level of meta-data privacy from passive observers, but to improve it - now all message meta-data that is passed from the server to the recipient is included into the same encrypted envelope as the message itself - as before, there is no identifiers or ciphertext in common inside TLS traffic between received and sent traffic of the server, and now there is no message timestamp inside TLS as well.</p>
 <p>We also improved the protocol flow for establishing bidirectional connection between two users - it is substantially faster now, consuming much less network traffic and battery. It improves the time it takes to connect to your contacts and to start delivering images and files.</p>
-<p>All these changes did not affect backward compatibility - if your contact has the previous version of the client, or you are connecting to a previous version of the server, the previous version of the protocol will be used - SimpleX has independent version negotiation in 4 protocol layers <a href="20220112-simplex-chat-v1-released.html#stable-protocol-implementation">since v1</a>, allowing us to evolve the protocols without any disruption to the users.</p>
+<p>All these changes did not affect backward compatibility - if your contact has the previous version of the client, or you are connecting to a previous version of the server, the previous version of the protocol will be used - SimpleX has independent version negotiation in 4 protocol layers <a href="/blog/20220112-simplex-chat-v1-released.html#stable-protocol-implementation">since v1</a>, allowing us to evolve the protocols without any disruption to the users.</p>
 <h2 id="simplex-platform" tabindex="-1">SimpleX platform</h2>
 <p>We are building a new platform for distributed Internet applications where privacy of the messages <em>and</em> the network matter. <a href="https://github.com/simplex-chat/simplex-chat">SimpleX Chat</a> is our first application, a messaging application built on the SimpleX platform.</p>
 <h3 id="the-first-and-we-believe-the-only-messaging-platform-without-user-identifiers-of-any-kind-100percent-private-by-design" tabindex="-1">The first (and we believe the only) messaging platform without user identifiers of any kind - 100% private by design!</h3>
@@ -428,7 +428,7 @@ window.addEventListener('scroll',changeHeaderBg);
 <p>SimpleX platform avoids these risks by not having any user identity in its design - so even if you talk to two different people from the same chat profile, they would not be able to prove they are talking to the same person - only that user profiles look the same. And we are planning to add a feature allowing to have a different display name for each contact you connect to - quite a few users asked for it.</p>
 <h3 id="how-does-it-work" tabindex="-1">How does it work</h3>
 <p>Many people asked: <em>if SimpleX has no user identifiers, how can it deliver messages?</em></p>
-<p>I wrote about it in <a href="20220511-simplex-chat-v2-images-files.html">v2 release announcement</a> and you can get more information about SimpleX platform objectives and technical design in <a href="https://github.com/simplex-chat/simplexmq/blob/master/protocol/overview-tjr.md">the whitepaper</a>.</p>
+<p>I wrote about it in <a href="/blog/20220511-simplex-chat-v2-images-files.html">v2 release announcement</a> and you can get more information about SimpleX platform objectives and technical design in <a href="https://github.com/simplex-chat/simplexmq/blob/master/protocol/overview-tjr.md">the whitepaper</a>.</p>
 <h2 id="we-ask-you-to-help-us-pay-for-3rd-party-security-audit" tabindex="-1">We ask you to help us pay for 3rd party security audit</h2>
 <p>I will get straight to the point: I ask you to support SimpleX Chat with donations.</p>
 <p>We are prioritizing users privacy and security - it would be impossible without your support we were lucky to have so far.</p>
@@ -420,9 +420,9 @@ window.addEventListener('scroll',changeHeaderBg);
 <h2 id="simplex-platform" tabindex="-1">SimpleX platform</h2>
 <p>We are building a new platform for distributed Internet applications where privacy of the messages <em>and</em> the network matter. <a href="https://github.com/simplex-chat/simplex-chat">SimpleX Chat</a> is our first application, a messaging application built on the SimpleX platform.</p>
 <h3 id="the-first-and-the-only-messaging-platform-without-user-identifiers-of-any-kind-100percent-private-by-design" tabindex="-1">The first (and the only?) messaging platform without user identifiers of any kind - 100% private by design!</h3>
-<p>To protect identities of users and their connections, instead of user identifiers visible to the servers and/or the network (that are used by all other messaging platforms), SimpleX Chat uses <a href="https://csrc.nist.gov/glossary/term/Pairwise_Pseudonymous_Identifier">pairwise identifiers</a> of connections between the users – there are two queues in each connection, each queue having 2 different identifiers to send and to receive the messages. It increases the number of used identifiers to the square of the number of users, making it more difficult (or impossible) to determine who is talking to whom. I <a href="20220711-simplex-chat-v3-released-ios-notifications-audio-video-calls-database-export-import-protocol-improvements.html#why-having-users-identifiers-is-bad-for-the-users">wrote previously</a> why it is bad for the users' privacy to have any identifiers, even random numbers, associated with their profiles.</p>
+<p>To protect identities of users and their connections, instead of user identifiers visible to the servers and/or the network (that are used by all other messaging platforms), SimpleX Chat uses <a href="https://csrc.nist.gov/glossary/term/Pairwise_Pseudonymous_Identifier">pairwise identifiers</a> of connections between the users – there are two queues in each connection, each queue having 2 different identifiers to send and to receive the messages. It increases the number of used identifiers to the square of the number of users, making it more difficult (or impossible) to determine who is talking to whom. I <a href="/blog/20220711-simplex-chat-v3-released-ios-notifications-audio-video-calls-database-export-import-protocol-improvements.html#why-having-users-identifiers-is-bad-for-the-users">wrote previously</a> why it is bad for the users' privacy to have any identifiers, even random numbers, associated with their profiles.</p>
 <h3 id="if-simplex-has-no-user-identifiers-how-can-it-deliver-messages" tabindex="-1">If SimpleX has no user identifiers, how can it deliver messages?</h3>
-<p>I wrote about it in <a href="20220511-simplex-chat-v2-images-files.html">v2 release announcement</a> and you can get more information about SimpleX platform objectives and technical design in <a href="https://github.com/simplex-chat/simplexmq/blob/master/protocol/overview-tjr.md">the whitepaper</a>.</p>
+<p>I wrote about it in <a href="/blog/20220511-simplex-chat-v2-images-files.html">v2 release announcement</a> and you can get more information about SimpleX platform objectives and technical design in <a href="https://github.com/simplex-chat/simplexmq/blob/master/protocol/overview-tjr.md">the whitepaper</a>.</p>
 <h3 id="privacy-technical-details-and-limitations" tabindex="-1">Privacy: technical details and limitations</h3>
 <p>SimpleX design follows &quot;defence in depth&quot; security principles having multiple overlapping defensive mechanisms to protect users privacy and security:</p>
 <ul>
@@ -396,7 +396,7 @@ window.addEventListener('scroll',changeHeaderBg);
 </ul>
 <h3 id="secret-chat-groups" tabindex="-1">Secret chat groups</h3>
 <p><img src="./images/20220808-group1.png" width="330"> <img src="./images/20220808-group2.png" width="330"> <img src="./images/20220808-group3.png" width="330"></p>
-<p>It's been <a href="20210914-simplex-chat-v0.4-released.html">nearly a year</a> since the users of SimpleX Chat terminal app started experimenting with the groups, and now it is available to mobile app users as well. Many bugs were fixed, the stability was improved, but there are both the features we need to add and the bugs we need to fix to make groups more useful - we really look forward to your feedback. You can send any suggestions via the app by choosing <code>Chat with the developers</code> via app Settings (or using <code>/simplex</code> command in the terminal app) – this would connect you to SimpleX team via its <a href="https://simplex.chat/contact#/?v=1&amp;smp=smp%3A%2F%2FPQUV2eL0t7OStZOoAsPEV2QYWt4-xilbakvGUGOItUo%3D%40smp6.simplex.im%2FK1rslx-m5bpXVIdMZg9NLUZ_8JBm8xTt%23MCowBQYDK2VuAyEALDeVe-sG8mRY22LsXlPgiwTNs9dbiLrNuA7f3ZMAJ2w%3D">fixed chat address</a>.</p>
+<p>It's been <a href="/blog/20210914-simplex-chat-v0.4-released.html">nearly a year</a> since the users of SimpleX Chat terminal app started experimenting with the groups, and now it is available to mobile app users as well. Many bugs were fixed, the stability was improved, but there are both the features we need to add and the bugs we need to fix to make groups more useful - we really look forward to your feedback. You can send any suggestions via the app by choosing <code>Chat with the developers</code> via app Settings (or using <code>/simplex</code> command in the terminal app) – this would connect you to SimpleX team via its <a href="https://simplex.chat/contact#/?v=1&amp;smp=smp%3A%2F%2FPQUV2eL0t7OStZOoAsPEV2QYWt4-xilbakvGUGOItUo%3D%40smp6.simplex.im%2FK1rslx-m5bpXVIdMZg9NLUZ_8JBm8xTt%23MCowBQYDK2VuAyEALDeVe-sG8mRY22LsXlPgiwTNs9dbiLrNuA7f3ZMAJ2w%3D">fixed chat address</a>.</p>
 <p>SimpleX network is decentralized, so how do groups work? Unlike Matrix or Signal that host the group profile and the list of group members on their servers, SimpleX servers have no information about the group's existence - only its members do. SimpleX network does not assign any globally unique identifiers to the group, there is only a local database identifier and the list of members stored on members' devices. A user has an independent connection to each member in a group. When a user sends a message to the group, the app sends this message independently to each member. You can read more about how groups work in <a href="https://github.com/simplex-chat/simplex-chat/blob/stable/docs/protocol/simplex-chat.md#sub-protocol-for-chat-groups">SimpleX Chat Protocol</a>.</p>
 <p>But how can it scale, you might ask? It simply won't, and the current design for the groups is only suitable for relatively small groups of people who know each other well, definitely not larger than few hundred members – this design prioritized privacy and security of the group over its size or performance. For example, to send a message to the group of 100 members a user would need to send a total of ~1.6mb of data (as each message uses a fixed size block of 16kb). And if you were to send a 1mb file then it would also require sending it 100 times (provided each member accepts it).</p>
 <p>What if you need to send many large files to group members? We will be developing a file hosting server where the users will be able to upload the file (or image) once, and only send the file link and credentials to all group members, without the need to send the actual file. A small hosting quota will be available to all users for free, paid for by donations, and for larger files or to increase the total quota the users would either have to pay a small hosting cost or to self-host this server – it will be available as an open-source code.</p>
@@ -432,12 +432,12 @@ window.addEventListener('scroll',changeHeaderBg);
 <p>The <a href="https://github.com/simplex-chat/simplexmq/blob/stable/protocol/">low level SimpleX protocols</a> were published long time ago, and updated to reflect the evolution of the protocols, the high level chat protocol was not published before. The reason for that was to allow us to iterate it quickly, without committing to any of the decisions.</p>
 <p>This is the <a href="https://github.com/simplex-chat/simplex-chat/blob/stable/docs/protocol/simplex-chat.md">first draft of SimpleX Chat Protocol</a> - let us know any questions or suggestions.</p>
 <h3 id="other-changes-since-v3" tabindex="-1">Other changes since v3</h3>
-<p>Since v3 release we also optimized battery and traffic usage - with up to 90x traffic reduction in some cases – and published two docker configurations for self-hosted SMP servers. Read more about it in the previous <a href="20220723-simplex-chat-v3.1-tor-groups-efficiency.html">beta version announcement</a>.</p>
+<p>Since v3 release we also optimized battery and traffic usage - with up to 90x traffic reduction in some cases – and published two docker configurations for self-hosted SMP servers. Read more about it in the previous <a href="/blog/20220723-simplex-chat-v3.1-tor-groups-efficiency.html">beta version announcement</a>.</p>
 <h2 id="simplex-platform" tabindex="-1">SimpleX platform</h2>
 <p>Some links to answer the most common questions:</p>
-<p><a href="20220511-simplex-chat-v2-images-files.html#the-first-messaging-platform-without-user-identifiers">How can SimpleX deliver messages without user identifiers</a>.</p>
-<p><a href="20220711-simplex-chat-v3-released-ios-notifications-audio-video-calls-database-export-import-protocol-improvements.html#why-having-users-identifiers-is-bad-for-the-users">What are the risks to have identifiers assigned to the users</a>.</p>
-<p><a href="20220723-simplex-chat-v3.1-tor-groups-efficiency.html#privacy-technical-details-and-limitations">Technical details and limitations</a>.</p>
+<p><a href="/blog/20220511-simplex-chat-v2-images-files.html#the-first-messaging-platform-without-user-identifiers">How can SimpleX deliver messages without user identifiers</a>.</p>
+<p><a href="/blog/20220711-simplex-chat-v3-released-ios-notifications-audio-video-calls-database-export-import-protocol-improvements.html#why-having-users-identifiers-is-bad-for-the-users">What are the risks to have identifiers assigned to the users</a>.</p>
+<p><a href="/blog/20220723-simplex-chat-v3.1-tor-groups-efficiency.html#privacy-technical-details-and-limitations">Technical details and limitations</a>.</p>
 <p><a href="https://github.com/simplex-chat/simplex-chat/blob/stable/README.md#frequently-asked-questions">How SimpleX is different from Session, Matrix, Signal, etc.</a>.</p>
 <h2 id="we-ask-you-to-help-us-pay-for-3rd-party-security-audit" tabindex="-1">We ask you to help us pay for 3rd party security audit</h2>
 <p>I will get straight to the point: I ask you to support SimpleX Chat with donations.</p>
@@ -426,9 +426,9 @@ window.addEventListener('scroll',changeHeaderBg);
 <p>And you can choose dark or light mode independently of the system settings.</p>
 <h2 id="simplex-platform" tabindex="-1">SimpleX platform</h2>
 <p>Some links to answer the most common questions:</p>
-<p><a href="20220511-simplex-chat-v2-images-files.html#the-first-messaging-platform-without-user-identifiers">How can SimpleX deliver messages without user identifiers</a>.</p>
-<p><a href="20220711-simplex-chat-v3-released-ios-notifications-audio-video-calls-database-export-import-protocol-improvements.html#why-having-users-identifiers-is-bad-for-the-users">What are the risks to have identifiers assigned to the users</a>.</p>
-<p><a href="20220723-simplex-chat-v3.1-tor-groups-efficiency.html#privacy-technical-details-and-limitations">Technical details and limitations</a>.</p>
+<p><a href="/blog/20220511-simplex-chat-v2-images-files.html#the-first-messaging-platform-without-user-identifiers">How can SimpleX deliver messages without user identifiers</a>.</p>
+<p><a href="/blog/20220711-simplex-chat-v3-released-ios-notifications-audio-video-calls-database-export-import-protocol-improvements.html#why-having-users-identifiers-is-bad-for-the-users">What are the risks to have identifiers assigned to the users</a>.</p>
+<p><a href="/blog/20220723-simplex-chat-v3.1-tor-groups-efficiency.html#privacy-technical-details-and-limitations">Technical details and limitations</a>.</p>
 <p><a href="https://github.com/simplex-chat/simplex-chat/blob/stable/README.md#frequently-asked-questions">How SimpleX is different from Session, Matrix, Signal, etc.</a>.</p>
 <h2 id="we-ask-you-to-help-us-pay-for-3rd-party-security-audit" tabindex="-1">We ask you to help us pay for 3rd party security audit</h2>
 <p>Our great news is that we have already signed the agreement and paid for the security audit!</p>
@@ -393,9 +393,9 @@ window.addEventListener('scroll',changeHeaderBg);
 <p>Also, this version adds German language to mobile apps UI - huge thanks to <a href="https://github.com/mlanp">Michael</a> who contributed them!</p>
 <p>Other new features since v3:</p>
 <ul>
-<li>secret chat groups (see details in <a href="20220808-simplex-chat-v3.1-chat-groups.html#secret-chat-groups">v3.1 announcement</a> - they are fully decentralized, only their members know these groups exist.</li>
-<li>accessing messaging servers via Tor with support for .onion server addresses (see details in <a href="20220808-simplex-chat-v3.1-chat-groups.html#access-messaging-servers-via-tor">v3.1</a> and <a href="20220901-simplex-chat-v3.2-incognito-mode.html#using-onion-server-addresses-with-tor">v3.2</a> announcements) - to protect users anonymity on the TCP transport level.</li>
-<li>Incognito mode - sharing a random profile name with each new contact, to completely eliminate any shared data between them (see details in <a href="20220901-simplex-chat-v3.2-incognito-mode.html#incognito-mode">v3.2</a> announcement).</li>
+<li>secret chat groups (see details in <a href="/blog/20220808-simplex-chat-v3.1-chat-groups.html#secret-chat-groups">v3.1 announcement</a> - they are fully decentralized, only their members know these groups exist.</li>
+<li>accessing messaging servers via Tor with support for .onion server addresses (see details in <a href="/blog/20220808-simplex-chat-v3.1-chat-groups.html#access-messaging-servers-via-tor">v3.1</a> and <a href="/blog/20220901-simplex-chat-v3.2-incognito-mode.html#using-onion-server-addresses-with-tor">v3.2</a> announcements) - to protect users anonymity on the TCP transport level.</li>
+<li>Incognito mode - sharing a random profile name with each new contact, to completely eliminate any shared data between them (see details in <a href="/blog/20220901-simplex-chat-v3.2-incognito-mode.html#incognito-mode">v3.2</a> announcement).</li>
 <li>endless scrolling and search in chats.</li>
 <li>reduced Android APK size for direct download and in F-Droid repo from 200 to 50Mb!</li>
 </ul>
@@ -408,7 +408,7 @@ window.addEventListener('scroll',changeHeaderBg);
 <p>For additional security of your messages you also have the option to remove the passphrase from the device. In this case you will need to enter the passphrase every time you start the app. The notifications will continue to work only while the app is in the background. For iOS it means that periodic and local notifications will work, but instant notifications will only show that there is a message available, but not message content or who it is from - you will need to open the app and enter the passphrase to see the messages. In this case, if you lose the passphrase, you will not be able to open the app or decrypt the database - so make sure you store it safely.</p>
 <h3 id="self-hosted-webrtc-ice-servers" tabindex="-1">Self-hosted WebRTC ICE servers</h3>
 <img src="./images/20220928-ice-servers.png" width="330">
-<p>You could make audio and video calls via SimpleX Chat WebRTC servers since <a href="20220711-simplex-chat-v3-released-ios-notifications-audio-video-calls-database-export-import-protocol-improvements.html#end-to-end-encrypted-audiovideo-calls">v3</a> - that meant that our servers could observe your IP addresses. This release adds configuration to use your own STUN/TURN servers, helping you protect your privacy.</p>
+<p>You could make audio and video calls via SimpleX Chat WebRTC servers since <a href="/blog/20220711-simplex-chat-v3-released-ios-notifications-audio-video-calls-database-export-import-protocol-improvements.html#end-to-end-encrypted-audiovideo-calls">v3</a> - that meant that our servers could observe your IP addresses. This release adds configuration to use your own STUN/TURN servers, helping you protect your privacy.</p>
 <p>See <a href="https://github.com/simplex-chat/simplex-chat/blob/stable/docs/WEBRTC.md">this guide</a> to learn how to deploy your own <code>coturn</code> server and to configure the mobile apps to use it.</p>
 <h3 id="improved-stability-of-creating-new-connections" tabindex="-1">Improved stability of creating new connections</h3>
 <p>Secret groups made SimpleX Chat much more useful, but because SimpleX groups are completely decentralized and for them to work each member should connect to all other members, sometimes these connections fail and the group becomes fragmented - some members do not receive all messages. That was more common for larger groups, as the number of required member connections is O(n^2) of the group size.</p>
@@ -448,9 +448,9 @@ window.addEventListener('scroll',changeHeaderBg);
 <p>We are really looking forward to seeing what applications you create - please submit your ideas and implementations, we will publish the links on a separate page on the website and GitHub repository.</p>
 <h2 id="simplex-platform" tabindex="-1">SimpleX platform</h2>
 <p>Some links to answer the most common questions:</p>
-<p><a href="20220511-simplex-chat-v2-images-files.html#the-first-messaging-platform-without-user-identifiers">How can SimpleX deliver messages without user identifiers</a>.</p>
-<p><a href="20220711-simplex-chat-v3-released-ios-notifications-audio-video-calls-database-export-import-protocol-improvements.html#why-having-users-identifiers-is-bad-for-the-users">What are the risks to have identifiers assigned to the users</a>.</p>
-<p><a href="20220723-simplex-chat-v3.1-tor-groups-efficiency.html#privacy-technical-details-and-limitations">Technical details and limitations</a>.</p>
+<p><a href="/blog/20220511-simplex-chat-v2-images-files.html#the-first-messaging-platform-without-user-identifiers">How can SimpleX deliver messages without user identifiers</a>.</p>
+<p><a href="/blog/20220711-simplex-chat-v3-released-ios-notifications-audio-video-calls-database-export-import-protocol-improvements.html#why-having-users-identifiers-is-bad-for-the-users">What are the risks to have identifiers assigned to the users</a>.</p>
+<p><a href="/blog/20220723-simplex-chat-v3.1-tor-groups-efficiency.html#privacy-technical-details-and-limitations">Technical details and limitations</a>.</p>
 <p><a href="https://github.com/simplex-chat/simplex-chat/blob/stable/README.md#frequently-asked-questions">How SimpleX is different from Session, Matrix, Signal, etc.</a>.</p>
 <h2 id="we-ask-you-to-help-us-pay-for-3rd-party-security-audit" tabindex="-1">We ask you to help us pay for 3rd party security audit</h2>
 <p>We have already signed the agreement and paid for the security audit!</p>
@@ -477,9 +477,9 @@ window.addEventListener('scroll',changeHeaderBg);
 <p>This functionality was created for the future voice messages, as they need to be sent without acceptance, so that the recipients can listen to them even when the sender is offline.</p>
 <h2 id="simplex-platform" tabindex="-1">SimpleX platform</h2>
 <p>Some links to answer the most common questions:</p>
-<p><a href="20220511-simplex-chat-v2-images-files.html#the-first-messaging-platform-without-user-identifiers">How can SimpleX deliver messages without user identifiers</a>.</p>
-<p><a href="20220711-simplex-chat-v3-released-ios-notifications-audio-video-calls-database-export-import-protocol-improvements.html#why-having-users-identifiers-is-bad-for-the-users">What are the risks to have identifiers assigned to the users</a>.</p>
-<p><a href="20220723-simplex-chat-v3.1-tor-groups-efficiency.html#privacy-technical-details-and-limitations">Technical details and limitations</a>.</p>
+<p><a href="/blog/20220511-simplex-chat-v2-images-files.html#the-first-messaging-platform-without-user-identifiers">How can SimpleX deliver messages without user identifiers</a>.</p>
+<p><a href="/blog/20220711-simplex-chat-v3-released-ios-notifications-audio-video-calls-database-export-import-protocol-improvements.html#why-having-users-identifiers-is-bad-for-the-users">What are the risks to have identifiers assigned to the users</a>.</p>
+<p><a href="/blog/20220723-simplex-chat-v3.1-tor-groups-efficiency.html#privacy-technical-details-and-limitations">Technical details and limitations</a>.</p>
 <p><a href="https://github.com/simplex-chat/simplex-chat/blob/stable/README.md#frequently-asked-questions">How SimpleX is different from Session, Matrix, Signal, etc.</a>.</p>
 <p>Please also see the information on our <a href="https://simplex.chat">new website</a> - it also answers all these questions.</p>
 <h2 id="help-us-with-donations" tabindex="-1">Help us with donations</h2>
@@ -381,7 +381,7 @@ window.addEventListener('scroll',changeHeaderBg);
      <div class="py-6 md:p-[60px]"><h1 id="simplex-chat-reviews-and-v43-released-with-instant-voice-messages-irreversible-deletion-of-sent-messages-and-improved-server-configuration" tabindex="-1">SimpleX Chat reviews and v4.3 released – with instant voice messages, irreversible deletion of sent messages and improved server configuration.</h1>
 <p><strong>Published:</strong> Dec 6, 2022</p>
 <h2 id="simplex-chat-reviews" tabindex="-1">SimpleX Chat reviews</h2>
-<p>Since we published <a href="https://simplex.chat/blog/20221108-simplex-chat-v4.2-security-audit-new-website.html">the security assessment of SimpleX Chat</a> completed by Trail of Bits in November, several sites published the reviews and included it in their recommendations:</p>
+<p>Since we published <a href="/blog/20221108-simplex-chat-v4.2-security-audit-new-website.html">the security assessment of SimpleX Chat</a> completed by Trail of Bits in November, several sites published the reviews and included it in their recommendations:</p>
 <ul>
 <li>Privacy Guides added SimpleX Chat to <a href="https://www.privacyguides.org/real-time-communication/#simplex-chat">the recommended private and secure messengers</a>.</li>
 <li>Mike Kuketz – a well-known security expert – published <a href="https://www.kuketz-blog.de/simplex-eindruecke-vom-messenger-ohne-identifier/">the review of SimpleX Chat</a> and added it to <a href="https://www.messenger-matrix.de">the messenger matrix</a>.</li>
@@ -440,9 +440,9 @@ window.addEventListener('scroll',changeHeaderBg);
 <p>The new version does not allow them by default, but it can be enabled by group owners in the group settings when the group is created or at any later moment.</p>
 <h2 id="simplex-platform" tabindex="-1">SimpleX platform</h2>
 <p>Some links to answer the most common questions:</p>
-<p><a href="20220511-simplex-chat-v2-images-files.html#the-first-messaging-platform-without-user-identifiers">How can SimpleX deliver messages without user identifiers</a>.</p>
-<p><a href="20220711-simplex-chat-v3-released-ios-notifications-audio-video-calls-database-export-import-protocol-improvements.html#why-having-users-identifiers-is-bad-for-the-users">What are the risks to have identifiers assigned to the users</a>.</p>
-<p><a href="20220723-simplex-chat-v3.1-tor-groups-efficiency.html#privacy-technical-details-and-limitations">Technical details and limitations</a>.</p>
+<p><a href="/blog/20220511-simplex-chat-v2-images-files.html#the-first-messaging-platform-without-user-identifiers">How can SimpleX deliver messages without user identifiers</a>.</p>
+<p><a href="/blog/20220711-simplex-chat-v3-released-ios-notifications-audio-video-calls-database-export-import-protocol-improvements.html#why-having-users-identifiers-is-bad-for-the-users">What are the risks to have identifiers assigned to the users</a>.</p>
+<p><a href="/blog/20220723-simplex-chat-v3.1-tor-groups-efficiency.html#privacy-technical-details-and-limitations">Technical details and limitations</a>.</p>
 <p><a href="https://github.com/simplex-chat/simplex-chat/blob/stable/README.md#frequently-asked-questions">How SimpleX is different from Session, Matrix, Signal, etc.</a>.</p>
 <p>Please also see the information on our <a href="https://simplex.chat">new website</a> - it also answers all these questions.</p>
 <h2 id="help-us-with-donations" tabindex="-1">Help us with donations</h2>
@@ -391,7 +391,7 @@ window.addEventListener('scroll',changeHeaderBg);
 <h3 id="disappearing-messages" tabindex="-1">Disappearing messages</h3>
 <p><img src="./images/20230103-disappearing1.png" width="288">    <img src="./images/20230103-disappearing2.png" width="288"></p>
 <p>It is now possible to send the messages that will be deleted from both sender and recipient device after set time – for the sender from the time they were sent, and for the recipient - from the time they were read.</p>
-<p>Unlike in most other messengers, it requires agreement of both sides, not just the sender decision. I <a href="20221206-simplex-chat-v4.3-voice-messages.html#irreversible-message-deletion">wrote previously</a> why we believe it is wrong to allow the senders to delete their messages without recipient consent, and the same logic applies here – if you want to send the message that will disappear after some time, your contact should be ok with that too.</p>
+<p>Unlike in most other messengers, it requires agreement of both sides, not just the sender decision. I <a href="/blog/20221206-simplex-chat-v4.3-voice-messages.html#irreversible-message-deletion">wrote previously</a> why we believe it is wrong to allow the senders to delete their messages without recipient consent, and the same logic applies here – if you want to send the message that will disappear after some time, your contact should be ok with that too.</p>
 <p>In group conversations disappearing messages can be enabled by the group owners, by default they are disabled.</p>
 <h3 id="live-messages" tabindex="-1">&quot;Live&quot; messages</h3>
 <img src="./images/20230103-live.png" width="288">
@@ -411,8 +411,8 @@ window.addEventListener('scroll',changeHeaderBg);
 <p>Please get in touch if you want to translate the interface into your language!</p>
 <h2 id="simplex-platform" tabindex="-1">SimpleX platform</h2>
 <p>Some links to answer the most common questions:</p>
-<p><a href="20220511-simplex-chat-v2-images-files.html#the-first-messaging-platform-without-user-identifiers">How can SimpleX deliver messages without user identifiers</a>.</p>
-<p><a href="20220711-simplex-chat-v3-released-ios-notifications-audio-video-calls-database-export-import-protocol-improvements.html#why-having-users-identifiers-is-bad-for-the-users">What are the risks to have identifiers assigned to the users</a>.</p>
+<p><a href="/blog/20220511-simplex-chat-v2-images-files.html#the-first-messaging-platform-without-user-identifiers">How can SimpleX deliver messages without user identifiers</a>.</p>
+<p><a href="/blog/20220711-simplex-chat-v3-released-ios-notifications-audio-video-calls-database-export-import-protocol-improvements.html#why-having-users-identifiers-is-bad-for-the-users">What are the risks to have identifiers assigned to the users</a>.</p>
 <p><a href="https://github.com/simplex-chat/simplex-chat#privacy-technical-details-and-limitations">Technical details and limitations</a>.</p>
 <p><a href="https://github.com/simplex-chat/simplex-chat/blob/stable/README.md#frequently-asked-questions">How SimpleX is different from Session, Matrix, Signal, etc.</a>.</p>
 <p>Please also see our <a href="https://simplex.chat">website</a>.</p>
@@ -434,8 +434,8 @@ window.addEventListener('scroll',changeHeaderBg);
 <p>You can <a href="https://github.com/simplex-chat/simplex-chat/tree/stable#translate-the-apps">contribute the translation</a> of the apps to your language too!</p>
 <h2 id="simplex-platform" tabindex="-1">SimpleX platform</h2>
 <p>Some links to answer the most common questions:</p>
-<p><a href="20220511-simplex-chat-v2-images-files.html#the-first-messaging-platform-without-user-identifiers">How can SimpleX deliver messages without user identifiers</a>.</p>
-<p><a href="20220711-simplex-chat-v3-released-ios-notifications-audio-video-calls-database-export-import-protocol-improvements.html#why-having-users-identifiers-is-bad-for-the-users">What are the risks to have identifiers assigned to the users</a>.</p>
+<p><a href="/blog/20220511-simplex-chat-v2-images-files.html#the-first-messaging-platform-without-user-identifiers">How can SimpleX deliver messages without user identifiers</a>.</p>
+<p><a href="/blog/20220711-simplex-chat-v3-released-ios-notifications-audio-video-calls-database-export-import-protocol-improvements.html#why-having-users-identifiers-is-bad-for-the-users">What are the risks to have identifiers assigned to the users</a>.</p>
 <p><a href="https://github.com/simplex-chat/simplex-chat#privacy-technical-details-and-limitations">Technical details and limitations</a>.</p>
 <p><a href="https://github.com/simplex-chat/simplex-chat/blob/stable/README.md#frequently-asked-questions">How SimpleX is different from Session, Matrix, Signal, etc.</a>.</p>
 <p>Please also see our <a href="https://simplex.chat">website</a>.</p>
@@ -462,11 +462,11 @@ file ---&gt; |   XFTP   | ------&gt;           XFTP            ----&gt;  |  Rela
 <p>We are currently integrating support for sending large files using XFTP protocol into SimpleX Chat clients. SimpleX Chat v5.0 will have support for receiving files sent via XFTP protocol (you will be able to send a file description via a SimpleX Chat CLI app, so that mobile apps will be able to receive them as normal files, only much faster), and v5.1 will fully support for sending large files (up to 1gb) in the mobile apps.</p>
 <p>We will also publish a formal specification for XFTP protocol and overview of its security qualities and threat model. For now you can learn more about the protocol design and motivations from this internal <a href="https://github.com/simplex-chat/simplexmq/blob/stable/rfcs/2022-12-26-simplex-file-transfer.md">XFTP protocol RFC</a>.</p>
 <p>Using and sending files with the available XFTP CLI will hugely help us stabilizing both the protocol and implementations. What we really like about this design is that it is completely independent from SimpleX Chat - you can use it on its own, sending files and passing file descriptions to your contacts via any other messenger - e.g. via Signal, – without this messenger being able to observe that you are in fact sending a large file.</p>
-<p>We did not yet decide whether we will be making a separate security audit of XFTP implementation, or if we combine it with the next security audit of SimpleX Chat. The latter seems more likely, as XFTP uses the same cryptographic primitives that were reviewed during <a href="20221108-simplex-chat-v4.2-security-audit-new-website.html">SimpleX Chat security assessment by Trail of Bits</a> in November 2022.</p>
+<p>We did not yet decide whether we will be making a separate security audit of XFTP implementation, or if we combine it with the next security audit of SimpleX Chat. The latter seems more likely, as XFTP uses the same cryptographic primitives that were reviewed during <a href="/blog/20221108-simplex-chat-v4.2-security-audit-new-website.html">SimpleX Chat security assessment by Trail of Bits</a> in November 2022.</p>
 <h2 id="simplex-platform" tabindex="-1">SimpleX platform</h2>
 <p>Some links to answer the most common questions:</p>
-<p><a href="20220511-simplex-chat-v2-images-files.html#the-first-messaging-platform-without-user-identifiers">How can SimpleX deliver messages without user identifiers</a>.</p>
-<p><a href="20220711-simplex-chat-v3-released-ios-notifications-audio-video-calls-database-export-import-protocol-improvements.html#why-having-users-identifiers-is-bad-for-the-users">What are the risks to have identifiers assigned to the users</a>.</p>
+<p><a href="/blog/20220511-simplex-chat-v2-images-files.html#the-first-messaging-platform-without-user-identifiers">How can SimpleX deliver messages without user identifiers</a>.</p>
+<p><a href="/blog/20220711-simplex-chat-v3-released-ios-notifications-audio-video-calls-database-export-import-protocol-improvements.html#why-having-users-identifiers-is-bad-for-the-users">What are the risks to have identifiers assigned to the users</a>.</p>
 <p><a href="https://github.com/simplex-chat/simplex-chat#privacy-technical-details-and-limitations">Technical details and limitations</a>.</p>
 <p><a href="https://github.com/simplex-chat/simplex-chat/blob/stable/README.md#frequently-asked-questions">How SimpleX is different from Session, Matrix, Signal, etc.</a>.</p>
 <p>Please also see our <a href="https://simplex.chat">website</a>.</p>
@@ -428,7 +428,7 @@ window.addEventListener('scroll',changeHeaderBg);
 <p>The app now supports 8 languages in addition to English - Czech, German, Spanish, French, Italian, Dutch, Russian and Chinese. You can now choose the language via the app settings (Appearance page), independently from the system settings.</p>
 <h2 id="simplex-platform" tabindex="-1">SimpleX platform</h2>
 <p>Some links to answer the most common questions:</p>
-<p><a href="20221108-simplex-chat-v4.2-security-audit-new-website.html">SimpleX Chat security assessment</a>.</p>
+<p><a href="/blog/20221108-simplex-chat-v4.2-security-audit-new-website.html">SimpleX Chat security assessment</a>.</p>
 <p><a href="https://simplex.chat/#how-simplex-works">How can SimpleX deliver messages without user identifiers</a>.</p>
 <p><a href="https://simplex.chat/#why-ids-bad-for-privacy">What are the risks to have identifiers assigned to the users</a>.</p>
 <p><a href="https://github.com/simplex-chat/simplex-chat#privacy-technical-details-and-limitations">Technical details and limitations</a>.</p>
@@ -402,7 +402,7 @@ window.addEventListener('scroll',changeHeaderBg);
 <p>Many large tech companies prioritizing value extraction over value creation earned a bad reputation for all businesses, particularly in the communities that value decentralization and privacy. But commercial objectives do not have to result in exploitation. Our goal is to build a new kind of communication network, and also an application platform, that is private by design, fully decentralized and not owned by any single entity, where SimpleX Chat Ltd is one of many organizations that operate the network. I shared my thoughts about how the Internet and privacy might evolve in the interview in <a href="https://optoutpod.com/episodes/s3e02-simplexchat/">Opt Out Podcast</a>.</p>
 <h3 id="how-is-it-funded-and-what-is-the-business-model" tabindex="-1">How is it funded and what is the business model?</h3>
 <p>We started working full-time on the project in 2021 when <a href="https://www.linkedin.com/in/portmanwills/">Portman Wills</a> and <a href="https://www.linkedin.com/in/peterbriffett/">Peter Briffett</a> (the founders of <a href="https://wagestream.com/en/">Wagestream</a> where I led the engineering team) supported the company very early on, and several other angel investors joined later. In July 2022 SimpleX Chat raised a pre-seed funding from the VC fund <a href="https://www.villageglobal.vc">Village Global</a> - its co-founder <a href="https://casnocha.com">Ben Casnocha</a> was very excited about our vision of privacy-first fully decentralized messaging and community platform, both for the individual users and for the companies, independent of any crypto-currencies, that might grow to replace large centralized platforms, such as WhatsApp, Telegram and Signal.</p>
-<p>Overall we raised from our investors approximately $370,000 for a small share of the company to allow the project team working full time for almost two years, funding product design and development, infrastructure, and also <a href="https://simplex.chat/blog/20221108-simplex-chat-v4.2-security-audit-new-website.html">the security assessment by Trail of Bits</a>. A large part of this money is not spent yet.</p>
+<p>Overall we raised from our investors approximately $370,000 for a small share of the company to allow the project team working full time for almost two years, funding product design and development, infrastructure, and also <a href="/blog/20221108-simplex-chat-v4.2-security-audit-new-website.html">the security assessment by Trail of Bits</a>. A large part of this money is not spent yet.</p>
 <p>The project was hugely supported by the users as well - collectively, <a href="https://github.com/simplex-chat/simplex-chat#help-us-with-donations">you donated</a> over $25,000. Without these donations the investment we raised would not be possible, because we believe that voluntary user donations can sustain the project in the long term – it already covers all infrastructure costs. There are only two ways an Internet service can exist - either users are paying for it, or the users data becomes the product for the real customers, as happened with many large Internet companies. In the latter case the users are losing much more money than they are saving by giving away their privacy and the rights to the content they create on the centralized platforms.</p>
 <p>Going forward we plan to keep the basic usage of the platform free, and at the same time we will be providing the benefits to the project sponsors. For example, there will be additional app icons and user profile badges. There also will be higher file transfer limits – currently we don't limit it at all, only limiting the file size, but it's unlikely to be sustainable. In any case, the app will remain highly usable for everyone for free, and fully open-source. Several other apps are already being developed based on our app core, leading to a fully decentralized network.</p>
 <h3 id="what-is-next" tabindex="-1">What is next?</h3>
@@ -410,14 +410,14 @@ window.addEventListener('scroll',changeHeaderBg);
 <ul>
 <li>more reliable and resilient, by adding redundancy into the message delivery and delivery receipts,</li>
 <li>more private, by automating rotation of the servers used to deliver messages and by adding delivery relays to better protect IP addresses of the users,</li>
-<li>more usable by adding and improving the functions users are expecting in messengers, and also adding some unique functions, like we did with <a href="20220901-simplex-chat-v3.2-incognito-mode.html#incognito-mode">incognito mode</a>, <a href="20230103-simplex-chat-v4.4-disappearing-messages.html#live-messages">live messages</a> and <a href="20230328-simplex-chat-v4-6-hidden-profiles.html#hidden-chat-profiles">hidden profiles</a>.</li>
+<li>more usable by adding and improving the functions users are expecting in messengers, and also adding some unique functions, like we did with <a href="/blog/20220901-simplex-chat-v3.2-incognito-mode.html#incognito-mode">incognito mode</a>, <a href="/blog/20230103-simplex-chat-v4.4-disappearing-messages.html#live-messages">live messages</a> and <a href="/blog/20230328-simplex-chat-v4-6-hidden-profiles.html#hidden-chat-profiles">hidden profiles</a>.</li>
 </ul>
 <p>One major initiative we will kick-off this year is the support for large, fully decentralized and private communities and groups not hosted on any servers – something that no Internet platform achieved so far in as private and efficient way as we plan to build it.</p>
 <p>To accelerate product development and growth we will be raising a seed funding this year, both from the VCs and angel investors, and we also might offer our users an opportunity to participate in the crowd funding round on the same terms as other investors, allowing to both support the project and to benefit from its future growth. <a href="https://simplex.chat#join-simplex">Subscribe to our updates</a> not to miss it, connect to the team in SimpleX Chat and <a href="https://github.com/simplex-chat/simplex-chat#join-user-groups">join users' groups</a>.</p>
 <h2 id="whats-new-in-v50" tabindex="-1">What's new in v5.0</h2>
 <h3 id="send-videos-and-files-up-to-1gb" tabindex="-1">Send videos and files up to 1gb!</h3>
 <img src="./images/20230422-video.png" width="288" class="float-to-left">
-<p>In the beginning of March <a href="20230301-simplex-file-transfer-protocol.html">we released servers and command-line utility to send and receive files via XFTP protocol</a> - a very private and secure protocol that sends end-to-end encrypted files in chunks, protecting meta-data better than any alternatives we know of.</p>
+<p>In the beginning of March <a href="/blog/20230301-simplex-file-transfer-protocol.html">we released servers and command-line utility to send and receive files via XFTP protocol</a> - a very private and secure protocol that sends end-to-end encrypted files in chunks, protecting meta-data better than any alternatives we know of.</p>
 <p>Now this protocol is fully integrated in SimpleX Chat, and all files except small voice messages are sent using this protocol (small voice messages are sent as usual messages). Not only it is much faster than before - with the fast Internet connection I can send 25Mb file in 3 seconds and 1gb file in 2 minutes (for most users it's capped at the available Internet bandwidth), it has two other major advantages making it more usable:</p>
 <ul>
 <li>the file sent to a group has to be uploaded only once, regardless of the group size.</li>
@@ -437,7 +437,7 @@ window.addEventListener('scroll',changeHeaderBg);
 <p>Secondly, Android client now supports configuring host and port of the SOCKS proxy, allowing to use apps other than Orbot and also to run SOCKS proxy in the local network, to save mobile device battery.</p>
 <h2 id="simplex-platform" tabindex="-1">SimpleX platform</h2>
 <p>Some links to answer the most common questions:</p>
-<p><a href="20221108-simplex-chat-v4.2-security-audit-new-website.html">SimpleX Chat security assessment</a>.</p>
+<p><a href="/blog/20221108-simplex-chat-v4.2-security-audit-new-website.html">SimpleX Chat security assessment</a>.</p>
 <p><a href="https://simplex.chat/#how-simplex-works">How can SimpleX deliver messages without user identifiers</a>.</p>
 <p><a href="https://simplex.chat/#why-ids-bad-for-privacy">What are the risks to have identifiers assigned to the users</a>.</p>
 <p><a href="https://github.com/simplex-chat/simplex-chat#privacy-technical-details-and-limitations">Technical details and limitations</a>.</p>
@@ -413,20 +413,20 @@ window.addEventListener('scroll',changeHeaderBg);
 <h2 id="improved-messages" tabindex="-1">Improved messages</h2>
 <h3 id="voice-messages-up-to-5-minutes-better-quality-playback-control" tabindex="-1">Voice messages: up to 5 minutes, better quality, playback control</h3>
 <img src="./images/20230523-voice.png" width="288" class="float-to-left">
-<p>Since <a href="20221206-simplex-chat-v4.3-voice-messages.html#instant-voice-messages">v4.3</a> voice messages were sent in small 16kb chunks, so we had to limit them to 30-40 seconds for better user experience, as sending larger files would require the sender to be online.</p>
+<p>Since <a href="/blog/20221206-simplex-chat-v4.3-voice-messages.html#instant-voice-messages">v4.3</a> voice messages were sent in small 16kb chunks, so we had to limit them to 30-40 seconds for better user experience, as sending larger files would require the sender to be online.</p>
 <p>With the new XFTP protocol that allows sending files up to 1gb it is now possible to increase the message size - we decided to limit it at 5 min, increasing their quality 2x (the bitrate is increased from 16 to 32kbps). We also added a slider to control the playback.</p>
 <h3 id="disappearing-messages-choose-any-time" tabindex="-1">Disappearing messages: choose any time!</h3>
 <p><img src="./images/20230523-disappearing1.png" width="288">    <img src="./images/20230523-disappearing2.png" width="288"></p>
-<p>Since <a href="20230103-simplex-chat-v4.4-disappearing-messages.html#disappearing-messages">v4.4</a> disappearing messages were only configurable for the whole conversation, with a limited choice of allowed times between 30 seconds and 1 month.</p>
+<p>Since <a href="/blog/20230103-simplex-chat-v4.4-disappearing-messages.html#disappearing-messages">v4.4</a> disappearing messages were only configurable for the whole conversation, with a limited choice of allowed times between 30 seconds and 1 month.</p>
 <p>This version allows to configure the time for messages to disappear more granularly, in the range from 1 second to 3 months. You can also set a different time to disappear when you send the message (hold the Send button), as long as disappearing messages are enabled in the conversation.</p>
 <h3 id="message-editing-history" tabindex="-1">Message editing history</h3>
 <img src="./images/20230523-info.png" width="288" class="float-to-left">
-<p>I <a href="20221206-simplex-chat-v4.3-voice-messages.html#irreversible-message-deletion">wrote previously</a> why we decided to require the recipient concent before the messages can be fully deleted by the sender - in short, it is to support recipient's data sovereignty and prevent the possibility of offensive messages being removed without any trace. By default, when the sender deletes the message it is marked as deleted, rather than fully deleted, and you can reveal the original message.</p>
+<p>I <a href="/blog/20221206-simplex-chat-v4.3-voice-messages.html#irreversible-message-deletion">wrote previously</a> why we decided to require the recipient concent before the messages can be fully deleted by the sender - in short, it is to support recipient's data sovereignty and prevent the possibility of offensive messages being removed without any trace. By default, when the sender deletes the message it is marked as deleted, rather than fully deleted, and you can reveal the original message.</p>
 <p>You've found the workaround for it of course - it's enough to simply edit the message to hide the original content. This version adds a visible message editing history, together with other detailed information about when the message was sent, received or deleted, that wasn't visible in the conversation.</p>
 <h2 id="customize-and-share-color-themes" tabindex="-1">Customize and share color themes</h2>
 <img src="./images/20230523-theme.png" width="288" class="float-to-left">
 <p>Android app now allows choosing between three color themes - Light, Dark and SimpleX (a dark blue theme). You can customize any theme by setting 9 different colors used in the app, including titles, menus, accent colors and colors for sent and received messages.</p>
-<p>You can share your theme with other users by exporting it to a file and sending to them. You can also <a href="docs/themes.html">contribute your favorite themes</a> to our GitHub repository.</p>
+<p>You can share your theme with other users by exporting it to a file and sending to them. You can also <a href="/docs/themes.html">contribute your favorite themes</a> to our GitHub repository.</p>
 <h2 id="self-destruct-passcode" tabindex="-1">Self-destruct passcode</h2>
 <img src="./images/20230523-self-destruct.png" width="288" class="float-to-left">
 <p>This is something many of you asked before - when asked to enter the app passcode under duress, to be able to enter a special self-destruct code that would remove the app data. This feature is offered in many security tools, and now you can configure it in SimpleX Chat as well.</p>
@@ -439,7 +439,7 @@ window.addEventListener('scroll',changeHeaderBg);
 </ul>
 <h2 id="simplex-platform" tabindex="-1">SimpleX platform</h2>
 <p>Some links to answer the most common questions:</p>
-<p><a href="20221108-simplex-chat-v4.2-security-audit-new-website.html">SimpleX Chat security assessment</a>.</p>
+<p><a href="/blog/20221108-simplex-chat-v4.2-security-audit-new-website.html">SimpleX Chat security assessment</a>.</p>
 <p><a href="https://simplex.chat/#how-simplex-works">How can SimpleX deliver messages without user identifiers</a>.</p>
 <p><a href="https://simplex.chat/#why-ids-bad-for-privacy">What are the risks to have identifiers assigned to the users</a>.</p>
 <p><a href="https://github.com/simplex-chat/simplex-chat#privacy-technical-details-and-limitations">Technical details and limitations</a>.</p>
@@ -422,7 +422,7 @@ window.addEventListener('scroll',changeHeaderBg);
 <img src="./images/20230722-receipts.png" width="330" class="float-to-left">
 <p>Most messaging apps add two ticks to sent messages – the first one to show that the message is accepted by the server, and the second – that it is delivered to the recipient's device. It confirms that the network is functioning, and that the message is not lost or delayed. SimpleX Chat now has this feature too!</p>
 <p>In some cases it may compromise recipients' privacy, as they show that the recipient is online, so we made sending delivery receipts optional – it can be disabled separately for each chat profile or contact. For the new chat profiles this feature is enabled by default.</p>
-<p>To avoid compromising your privacy, sending delivery receipts is disabled for all your existing chat profiles. The first time you start the app after the update, you will be offered to enable them for all <a href="20230328-simplex-chat-v4-6-hidden-profiles.html#hidden-chat-profiles">visible profiles</a>, and they can be enabled later via Privacy and Security settings.</p>
+<p>To avoid compromising your privacy, sending delivery receipts is disabled for all your existing chat profiles. The first time you start the app after the update, you will be offered to enable them for all <a href="/blog/20230328-simplex-chat-v4-6-hidden-profiles.html#hidden-chat-profiles">visible profiles</a>, and they can be enabled later via Privacy and Security settings.</p>
 <h3 id="filter-favorite-and-unread-chats" tabindex="-1">Filter favorite and unread chats</h3>
 <img src="./images/20230722-filter.png" width="288" class="float-to-left">
 <p>You can now mark your contacts and groups as <em>favorite</em>, to be able to find them faster. With filter enabled, you will only see favorite chats, chats that contain unread messages and also any unaccepted group invitations and contact requests.</p>
@@ -441,8 +441,8 @@ window.addEventListener('scroll',changeHeaderBg);
 <p>Please report the cases when messages are not delivered – delivery receipts should help with that.</p>
 <h4 id="messages-failed-to-decrypt-problem-solved" tabindex="-1">Messages failed to decrypt? Problem solved!</h4>
 <p>Previously, a growing number of users had the issue when after restoring the chat database from backup, messages from some contacts failed to decrypt and were showing an error in the app.</p>
-<p>This happens due to double ratchet protocol protecting the integrity of end-to-end encryption after the compromise - <a href="docs/glossary.html#post-compromise-security">post-compromise security</a>. The protocol logic does not allow to use the old version of the database to decrypt the message.</p>
-<p>v5.2 added the extension to the messaging protocol allowing to negotiate the new ratchet keys in such cases - both with the contacts and the group members. This requires a user action, and it resets the security code verification status for this contact or member – you need to verify it again to have the additional protection from <a href="docs/glossary.html#man-in-the-middle-attack">man-in-the-middle attacks</a>.</p>
+<p>This happens due to double ratchet protocol protecting the integrity of end-to-end encryption after the compromise - <a href="/docs/glossary.html#post-compromise-security">post-compromise security</a>. The protocol logic does not allow to use the old version of the database to decrypt the message.</p>
+<p>v5.2 added the extension to the messaging protocol allowing to negotiate the new ratchet keys in such cases - both with the contacts and the group members. This requires a user action, and it resets the security code verification status for this contact or member – you need to verify it again to have the additional protection from <a href="/docs/glossary.html#man-in-the-middle-attack">man-in-the-middle attacks</a>.</p>
 <p>The negotiation of the new ratchet keys still happens via the end-to-end encrypted messages, as the protocol has two layers of end-to-end encryption, so it cannot be compromised by the messaging relays.</p>
 <p>You may still lose connection if you or your contact changed the receiving address after you made the backup, so make sure to make a new backup after any receiving address changes.</p>
 <h4 id="reconnect-the-servers" tabindex="-1">Reconnect the servers</h4>
@@ -462,12 +462,12 @@ window.addEventListener('scroll',changeHeaderBg);
 <h4 id="why-not-hosted-groups-with-mls" tabindex="-1">Why not hosted groups with MLS?</h4>
 <p>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.</p>
 <h4 id="why-not-fully-decentralized-groups" tabindex="-1">Why not fully decentralized groups?</h4>
-<p>We also <a href="docs/rfcs/2023-05-02-groups.html">considered</a> 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.</p>
+<p>We also <a href="https%3A//github.com/simplex-chat/simplex-chat/blob/stable/simplex-chat/docs/rfcs/2023-05-02-groups.md">considered</a> 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.</p>
 <h4 id="members-host-the-groups" tabindex="-1">Members host the groups</h4>
 <p>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't need to establish connections with all other members, only with a limited number of &quot;hosting&quot; members, and it also better protects their privacy, due to the lack of direct connections between most members.</p>
 <p>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.</p>
 <p>This approach also simplifies moderation - the message that needs to be removed simply won't reach the members before it is moderated (in case of automatic or policy-based moderation).</p>
-<p>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 <a href="docs/rfcs/2023-05-22-groups-moderation.html">described here</a>.</p>
+<p>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 <a href="https%3A//github.com/simplex-chat/simplex-chat/blob/stable/simplex-chat/docs/rfcs/2023-05-22-groups-moderation.md">described here</a>.</p>
 <p>We really look forward to your feedback on this design.</p>
 <h3 id="what-about-read-receipts" tabindex="-1">What about read receipts?</h3>
 <p>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.</p>
@@ -477,7 +477,7 @@ window.addEventListener('scroll',changeHeaderBg);
 <p>There is also no discounting that the presense of read receipts functionality, even as opt-in, creates a social pressure to enable them, with the same consequences – there are many scenarios when they become non-optional in some relationships. So many users belive, and we share this view, that it is better not to have these features at all. We will be re-assessing this view.</p>
 <h2 id="simplex-platform" tabindex="-1">SimpleX platform</h2>
 <p>Some links to answer the most common questions:</p>
-<p><a href="20221108-simplex-chat-v4.2-security-audit-new-website.html">SimpleX Chat security assessment</a>.</p>
+<p><a href="/blog/20221108-simplex-chat-v4.2-security-audit-new-website.html">SimpleX Chat security assessment</a>.</p>
 <p><a href="https://simplex.chat/#how-simplex-works">How can SimpleX deliver messages without user identifiers</a>.</p>
 <p><a href="https://simplex.chat/#why-ids-bad-for-privacy">What are the risks to have identifiers assigned to the users</a>.</p>
 <p><a href="https://github.com/simplex-chat/simplex-chat#privacy-technical-details-and-limitations">Technical details and limitations</a>.</p>
@@ -415,11 +415,11 @@ window.addEventListener('scroll',changeHeaderBg);
 <li>you cannot send voice messages.</li>
 <li>there is no support for calls yet.</li>
 </ul>
-<p>You can download the desktop app for Linux and Mac via <a href="https://simplex.chat/downloads">downloads page</a>. Windows version will be available soon.</p>
+<p>You can download the desktop app for Linux and Mac via <a href="/downloads/index.html">downloads page</a>. Windows version will be available soon.</p>
 <h2 id="group-directory-service-and-other-group-improvements" tabindex="-1">Group directory service and other group improvements</h2>
 <img src="./images/20230925-directory.png" width="330" class="float-to-left">
 <p>Directory service provides a way to search for public groups submitted by the users. To use it, you need to connect to it via SimpleX Chat, as you would connect to any other contact, and type some words to search.</p>
-<p>You can also create and register your group, with some limitations explained <a href="docs/directory.html">here</a>.</p>
+<p>You can also create and register your group, with some limitations explained <a href="/docs/directory.html">here</a>.</p>
 <p>Other group improvements in this release:</p>
 <ul>
 <li>
@@ -436,7 +436,7 @@ window.addEventListener('scroll',changeHeaderBg);
 <h2 id="encrypted-local-files-and-media-with-forward-secrecy" tabindex="-1">Encrypted local files and media with forward secrecy</h2>
 <img src="./images/20230925-encrypted.png" width="330" class="float-to-left">
 <p>All messages, files and media sent via SimpleX Chat were always end-to-end encrypted from the very beginning. SimpleX Chat uses double-ratchet algorithm with encrypted message headers, for the best possible meta-data protection.</p>
-<p>You contacts, groups and messages are stored in the local database on your device, and this database was encrypted from <a href="20220928-simplex-chat-v4-encrypted-database.html">v4.0 released a year ago</a>.</p>
+<p>You contacts, groups and messages are stored in the local database on your device, and this database was encrypted from <a href="/blog/20220928-simplex-chat-v4-encrypted-database.html">v4.0 released a year ago</a>.</p>
 <p>But until this version all files and media in the app storage were not encrypted, and when you exported the chat archive, they were unencrypted there as well.</p>
 <p>From v5.3 all files and media (except videos, for now) are encrypted with a random symmetric key - in many cases they are encrypted before they are written to the storage. Local file encryption can be disabled via Privacy &amp; Security settings, for example, if you need to access the files from the storage outside of the app.</p>
 <p>In addition to the videos that are stored unencrypted, there are other rare scenarios when the received files may be unencrypted in this release. Files have an open or closed lock icons to indicate whether they were encrypted locally. These limitations will be addressed in the next release. In any case, all files and media are always sent end-to-end encrypted, without any exceptions.</p>
@@ -444,12 +444,12 @@ window.addEventListener('scroll',changeHeaderBg);
 <p>This approach provides forward secrecy for locally stored files, unlike file encryption schemes used in some other apps when the same passphrase is used for all files.</p>
 <h2 id="simplified-incognito-mode" tabindex="-1">Simplified incognito mode</h2>
 <img src="./images/20230925-incognito.png" width="330" class="float-to-left">
-<p>Incognito mode was <a href="20220901-simplex-chat-v3.2-incognito-mode.html">added a year ago</a> to improve anonymity of your profile, but it was confusing for some users - it was a global setting, but it only affected the new connections.</p>
+<p>Incognito mode was <a href="/blog/20220901-simplex-chat-v3.2-incognito-mode.html">added a year ago</a> to improve anonymity of your profile, but it was confusing for some users - it was a global setting, but it only affected the new connections.</p>
 <p>It is now simpler to use - you can decide whether to connect to a contact or join a group using your main profile at a point when you create an invitation link or connect via a link or QR code.</p>
 <p>When you are connecting to people you know you usually want to share your main profile, and when connecting to public groups or strangers, you may prefer to use a random profile.</p>
 <h2 id="simplex-platform" tabindex="-1">SimpleX platform</h2>
 <p>Some links to answer the most common questions:</p>
-<p><a href="20221108-simplex-chat-v4.2-security-audit-new-website.html">SimpleX Chat security assessment</a>.</p>
+<p><a href="/blog/20221108-simplex-chat-v4.2-security-audit-new-website.html">SimpleX Chat security assessment</a>.</p>
 <p><a href="https://simplex.chat/#how-simplex-works">How can SimpleX deliver messages without user identifiers</a>.</p>
 <p><a href="https://simplex.chat/#why-ids-bad-for-privacy">What are the risks to have identifiers assigned to the users</a>.</p>
 <p><a href="https://github.com/simplex-chat/simplex-chat#privacy-technical-details-and-limitations">Technical details and limitations</a>.</p>
@@ -415,7 +415,7 @@ window.addEventListener('scroll',changeHeaderBg);
 <p>This is only possible when both devices are connected to the same local network. To send and receive messages mobile app has to be connected to the Internet.</p>
 <h3 id="quick-start-how-to-use-it" tabindex="-1">⚡️ Quick start - how to use it</h3>
 <p><strong>On desktop</strong></p>
-<p>If you don't have desktop app installed yet, <a href="https://simplex.chat/downloads/">download it</a> and create any chat profile - you don't need to use it, and when you create it there are no server requests sent and no accounts are created. Think about it as about user profile on your computer.</p>
+<p>If you don't have desktop app installed yet, <a href="/downloads/index.html">download it</a> and create any chat profile - you don't need to use it, and when you create it there are no server requests sent and no accounts are created. Think about it as about user profile on your computer.</p>
 <p>Then in desktop app settings choose <em>Link a mobile</em> - it will show a QR code.</p>
 <p><img src="./images/20231125-desktop1.png" width="170"> <img src="./images/arrow.png" width="24"> <img src="./images/20231125-desktop2.png" width="170"> <img src="./images/arrow.png" width="24"> <img src="./images/20231125-desktop3.png" width="170"> <img src="./images/arrow.png" width="24"> <img src="./images/20231125-desktop4.png" width="510"></p>
 <p><strong>On mobile</strong></p>
@@ -425,7 +425,7 @@ window.addEventListener('scroll',changeHeaderBg);
 <p>If it is an Android app, you can move the app to background, but iOS app has to remain open. In both cases, while you are using mobile profiles from desktop, you won't be able to use mobile app.</p>
 <p>The subsequent connections happen much faster - by default, the desktop app broadcasts its session address to the network, in encrypted form, and mobile app connects to it once you choose <em>Use from desktop</em> in mobile app settings.</p>
 <h3 id="how-does-it-work" tabindex="-1">How does it work?</h3>
-<p>The way we designed this solution avoided any security compromises, and the end-to-end encryption remained as secure as it was - it uses <a href="docs/glossary.html#double-ratchet-algorithm">double-ratchet algorithm</a>, with <a href="docs/glossary.html#forward-secrecy">perfect forward secrecy</a>, <a href="docs/glossary.html#post-compromise-security">post-compromise security</a> and deniability.</p>
+<p>The way we designed this solution avoided any security compromises, and the end-to-end encryption remained as secure as it was - it uses <a href="/docs/glossary.html#double-ratchet-algorithm">double-ratchet algorithm</a>, with <a href="/docs/glossary.html#forward-secrecy">perfect forward secrecy</a>, <a href="/docs/glossary.html#post-compromise-security">post-compromise security</a> and deniability.</p>
 <p>This solution is similar to WhatsApp and WeChat. But unlike these apps, no server is involved in the connection between mobile and desktop. The connection itself uses a new SimpleX Remote Control Protocol (XRCP) based on secure TLS 1.3 and additional quantum-resistant encryption inside TLS. You can read XRCP protocol specification and threat model in <a href="https://github.com/simplex-chat/simplexmq/blob/master/rfcs/2023-10-25-remote-control.md">this document</a>. We will soon be <a href="https://github.com/simplex-chat/simplex-chat/blob/master/docs/rfcs/2023-09-30-pq-double-ratchet.md">augmenting double ratchet</a> to be resistant to quantum computers as well.</p>
 <p>The downside of this approach is that mobile device has to be connected to the same local network as desktop. But the upside is that the connection is secure, and you do not need to have a copy of all your data on desktop, which usually has lower security than mobile.</p>
 <p>Please note, that the files you send, save or play from desktop app, and also images you view are automatically saved on your desktop device (encrypted by default except videos). To remove all these files you can unlink the paired mobile device from the desktop app settings – there will be an option soon allowing to remove the files without unlinking the mobile.</p>
@@ -465,8 +465,8 @@ window.addEventListener('scroll',changeHeaderBg);
 <p>You can find the full list of fixed bugs and small improvements in the <a href="https://github.com/simplex-chat/simplex-chat/releases/tag/v5.4.0">release notes</a>.</p>
 <h2 id="simplex-platform" tabindex="-1">SimpleX platform</h2>
 <p>Some links to answer the most common questions:</p>
-<p><a href="20220511-simplex-chat-v2-images-files.html#the-first-messaging-platform-without-user-identifiers">How can SimpleX deliver messages without user identifiers</a>.</p>
-<p><a href="20220711-simplex-chat-v3-released-ios-notifications-audio-video-calls-database-export-import-protocol-improvements.html#why-having-users-identifiers-is-bad-for-the-users">What are the risks to have identifiers assigned to the users</a>.</p>
+<p><a href="/blog/20220511-simplex-chat-v2-images-files.html#the-first-messaging-platform-without-user-identifiers">How can SimpleX deliver messages without user identifiers</a>.</p>
+<p><a href="/blog/20220711-simplex-chat-v3-released-ios-notifications-audio-video-calls-database-export-import-protocol-improvements.html#why-having-users-identifiers-is-bad-for-the-users">What are the risks to have identifiers assigned to the users</a>.</p>
 <p><a href="https://github.com/simplex-chat/simplex-chat#privacy-technical-details-and-limitations">Technical details and limitations</a>.</p>
 <p><a href="https://github.com/simplex-chat/simplex-chat/blob/stable/README.md#frequently-asked-questions">How SimpleX is different from Session, Matrix, Signal, etc.</a>.</p>
 <p>Please also see our <a href="https://simplex.chat">website</a>.</p>
@@ -417,7 +417,7 @@ window.addEventListener('scroll',changeHeaderBg);
 <p><img src="./images/20240124-notes1.png" width="220" class="float-to-left"> <img src="./images/20240124-notes2.png" width="220" class="float-to-left"></p>
 <p><em>&quot;Where do I put notes for myself?&quot;</em> was a very common support question. There was a workaround - you could create an empty group, just with yourself, and use it to save notes, but it was not very convenient, and you could accidentally add members there.</p>
 <p>This version has a more convenient and private alternative - the Private notes. It looks like an ordinary conversation where you can put text messages, links with previews, and any media and files, but they are not sent anywhere - they are stored locally, only on your device, with encrypted files.</p>
-<p>You can access the Private notes created in mobile app from desktop app too, by linking a mobile and desktop apps - the feature <a href="20231125-simplex-chat-v5-4-link-mobile-desktop-quantum-resistant-better-groups.html">added in the previous version</a>. It allows to conveniently share files between the devices without sending them over the Internet.</p>
+<p>You can access the Private notes created in mobile app from desktop app too, by linking a mobile and desktop apps - the feature <a href="/blog/20231125-simplex-chat-v5-4-link-mobile-desktop-quantum-resistant-better-groups.html">added in the previous version</a>. It allows to conveniently share files between the devices without sending them over the Internet.</p>
 <h3 id="group-history" tabindex="-1">Group history</h3>
 <p><img src="./images/20240124-history1.png" width="220" class="float-to-left"> <img src="./images/20240124-history2.png" width="220" class="float-to-left"></p>
 <p>In the previous version, when users joined groups, they only saw an empty conversation, and the notifications of being connected to other members. This version allows group admins sending recent group history to the new members - this option is enabled by default for new groups, and can be enabled for the existing groups in the preferences. So now new members can join the conversation as soon as they join.</p>
@@ -434,12 +434,12 @@ window.addEventListener('scroll',changeHeaderBg);
 <p>Other improvements in this version:</p>
 <ul>
 <li>you can now reveal secret messages by tapping. To send a secret message wrap in &quot;#&quot; characters, e.g. &quot;#password#&quot;.</li>
-<li>you can delete the last user profile, simplifying account deletion. If you have <a href="20230328-simplex-chat-v4-6-hidden-profiles.html">hidden user profiles</a>, they won't be deleted in this case, and will be accessible again once you create a new profile.</li>
+<li>you can delete the last user profile, simplifying account deletion. If you have <a href="/blog/20230328-simplex-chat-v4-6-hidden-profiles.html">hidden user profiles</a>, they won't be deleted in this case, and will be accessible again once you create a new profile.</li>
 </ul>
 <h2 id="simplex-platform" tabindex="-1">SimpleX platform</h2>
 <p>Some links to answer the most common questions:</p>
-<p><a href="20220511-simplex-chat-v2-images-files.html#the-first-messaging-platform-without-user-identifiers">How can SimpleX deliver messages without user identifiers</a>.</p>
-<p><a href="20220711-simplex-chat-v3-released-ios-notifications-audio-video-calls-database-export-import-protocol-improvements.html#why-having-users-identifiers-is-bad-for-the-users">What are the risks to have identifiers assigned to the users</a>.</p>
+<p><a href="/blog/20220511-simplex-chat-v2-images-files.html#the-first-messaging-platform-without-user-identifiers">How can SimpleX deliver messages without user identifiers</a>.</p>
+<p><a href="/blog/20220711-simplex-chat-v3-released-ios-notifications-audio-video-calls-database-export-import-protocol-improvements.html#why-having-users-identifiers-is-bad-for-the-users">What are the risks to have identifiers assigned to the users</a>.</p>
 <p><a href="https://github.com/simplex-chat/simplex-chat#privacy-technical-details-and-limitations">Technical details and limitations</a>.</p>
 <p><a href="https://github.com/simplex-chat/simplex-chat/blob/stable/README.md#frequently-asked-questions">How SimpleX is different from Session, Matrix, Signal, etc.</a>.</p>
 <p>Please also see our <a href="https://simplex.chat">website</a>.</p>
@@ -379,6 +379,7 @@ window.addEventListener('scroll',changeHeaderBg);

    <section id="article" class="container mb-[75px] bg-white dark:bg-[#17203D] px-5">
      <div class="py-6 md:p-[60px]"><h1 id="simplex-chat-v56-beta-adding-quantum-resistance-to-signal-double-ratchet-algorithm" tabindex="-1">SimpleX Chat v5.6 beta: adding quantum resistance to Signal double ratchet algorithm</h1>
+<p><strong>Published:</strong> Mar 14, 2024</p>
 <p>This is a major upgrade for SimpleX messaging protocols, we are really proud to present the results of the hard work of our whole team on the <a href="https://en.wikipedia.org/wiki/Pi_Day">Pi day</a>.</p>
 <p>This post also covers various aspects of end-to-end encryption, compares different messengers, and explains why and how quantum-resistant encryption is added to SimpleX Chat:</p>
 <ul>
@@ -430,7 +431,7 @@ window.addEventListener('scroll',changeHeaderBg);
 <p>The only effective mitigation to these attacks is to pad all messages to a fixed size. Using space-efficient schemes like Padme, or padding to encryption block size is ineffective for mitigating these attacks, as they still allow differentiating message sizes.</p>
 <p>To the best of our knowledge, the only messengers other than SimpleX Chat that pad all messages to a fixed packet size are Cwtch and no longer developed <a href="https://github.com/agl/pond">Pond</a> - SimpleX design can be seen as an evolution of Pond design.</p>
 <h3 id="2-compromised-confidential-messages-mitigated-by-repudiation-deniability" tabindex="-1">2. Compromised confidential messages - mitigated by repudiation (deniability)</h3>
-<p>Many users are very interested in having ability to irreversibly delete sent messages from the recipients devices. But not only would this ability violate data sovereignty of device owners, it is also completely ineffective, as the recipients could simply put the device offline or use a modified client app to ignore message deletion requests. While SimpleX Chat provides such features as <a href="20230103-simplex-chat-v4.4-disappearing-messages.html#disappearing-messages">disappearing messages</a> and the ability to <a href="20221206-simplex-chat-v4.3-voice-messages.html#irreversible-message-deletion">irreversibly delete sent messages</a> provided both parties agree to that, these are convenience features, and they cannot be considered security measures.</p>
+<p>Many users are very interested in having ability to irreversibly delete sent messages from the recipients devices. But not only would this ability violate data sovereignty of device owners, it is also completely ineffective, as the recipients could simply put the device offline or use a modified client app to ignore message deletion requests. While SimpleX Chat provides such features as <a href="/blog/20230103-simplex-chat-v4.4-disappearing-messages.html#disappearing-messages">disappearing messages</a> and the ability to <a href="/blog/20221206-simplex-chat-v4.3-voice-messages.html#irreversible-message-deletion">irreversibly delete sent messages</a> provided both parties agree to that, these are convenience features, and they cannot be considered security measures.</p>
 <p>The solution to that is well known to cryptographers - it is the quality of the encryption algorithms called &quot;repudiation&quot;, sometimes also called &quot;deniability&quot;. This is the ability of the senders to plausibly deny having sent any messages, because cryptographic algorithms used to encrypt allow recipients forging these messages on their devices, so while the encryption proves authenticity of the message to the recipient, it cannot be used as a proof to any third party.</p>
 <p>Putting it all in a simpler language - a sender can claim that the recipient forged messages on their device, and deny ever having sent them. The recipient will not be able to provide any cryptographic proof. This quality makes digital conversation having the same qualities as private off-the-record conversation - that's why the family of algorithms that provide these qualities are called off-the-record (OTR) encryption.</p>
 <p>Repudiation is still a rather new concept - the first off-the-record algorithms were proposed in 2004 and were only offered to a wide range of users in Signal messenger. This concept is still quite badly understood by users and society, and yet to have been used as the defense in any public court cases, as legal systems evolve much slower than technology. In high profile cases repudiation can be used as an effective evidence for the defense.</p>
@@ -441,18 +442,18 @@ window.addEventListener('scroll',changeHeaderBg);
 <h3 id="4-compromised-long-term-or-session-mitigated-by-break-in-recovery" tabindex="-1">4. Compromised long-term or session - mitigated by break-in recovery</h3>
 <p>This attack is much less understood by the users, and forward secrecy does not protect from it. Arguably, it's almost impossible to compromise individual message keys without compromising long-term or session keys. So the ability of the encryption to recover from break-in (attacker making a copy of the device data without retaining the ongoing access) is both very important and pragmatic - break-in attacks are simpler to execute on mobile devices during short-term device access than long-term ongoing compromise.</p>
 <p>Out of all encryption algorithms known to us only <em>Signal double ratchet algorithm</em> (also referred to as <em>Signal algorithm</em> or <em>double ratchet algorithm</em>, which is not the same as Signal messaging platform and protocols) provides the ability for the encryption security to recover after break-ins attacks. This recovery happens automatically and transparently to the users, without them doing anything special or even knowing about break-in, by simply sending messages. Every time one of the communication parties replies to another party message, new random keys are generated and previously stolen keys become useless.</p>
-<p>Double ratchet algorithm is used in Signal, Cwtch and SimpleX Chat. This is why you cannot use SimpleX Chat profile on more than one device at the same time - the encryption scheme rotates the long term keys, randomly, and keys on another device become useless, as they would become useless for the attacker who stole them. Security always has some costs to the convenience.</p>
+<p>Double ratchet algorithm is used in Signal, Cwtch and SimpleX Chat. But Signal app by allowing to use the same profile on multiple devices compromises the break-in recovery function of Signal algorithm, as explained in <a href="https://eprint.iacr.org/2021/626.pdf">this paper</a>. Because of break-in recovery you cannot use SimpleX Chat profile on more than one device at the same time - the encryption scheme rotates the long term keys, randomly, and keys on another device become useless, as they would become useless for the attacker who stole them. Security always has some costs to the convenience.</p>
 <h3 id="5-man-in-the-middle-attack-mitigated-by-two-factor-key-exchange" tabindex="-1">5. Man-in-the-middle attack - mitigated by two-factor key exchange</h3>
 <p>Many people incorrectly believe that security of end-to-end encryption cannot be broken by communication provider. But end-to-end encryption is only as secure as key exchange. While any intermediary passing the keys between senders and recipients cannot recover the private keys from the public keys, they can simply replace the passed public keys with their own and then proxy all communication between the users having full access to the original messages. So instead of having an end-to-end encrypted channel, users would have two half-way encrypted channels - between users and their communication intermediary.</p>
 <p>Pictures below illustrate how this attack works for RSA encryption.</p>
 <h4 id="1-alice-sends-the-key-to-bob-eg-via-p2p-network-or-via-the-messaging-server" tabindex="-1">1) Alice sends the key to Bob (e.g. via p2p network or via the messaging server).</h4>
-<p><img src="./images/20240314-mitm1.jpg" alt="Public key is shared"></p>
+<p><img src="images/20240314-mitm1.jpg" alt="Public key is shared"></p>
 <h4 id="2-now-bob-can-send-encrypted-messages-to-alice-he-believes-they-are-secure" tabindex="-1">2) Now Bob can send encrypted messages to Alice - he believes they are secure!</h4>
-<p><img src="./images/20240314-mitm2.jpg" alt="Message is encrypted"></p>
+<p><img src="images/20240314-mitm2.jpg" alt="Message is encrypted"></p>
 <h4 id="3-but-the-key-could-have-been-intercepted-and-substituted-by-tom-the-attacker-or-a-service-provider" tabindex="-1">3) But the key could have been intercepted and substituted by Tom (the attacker, or a service provider).</h4>
-<p><img src="./images/20240314-mitm3.jpg" alt="Key is intercepted and replaced"></p>
+<p><img src="images/20240314-mitm3.jpg" alt="Key is intercepted and replaced"></p>
 <h4 id="4-now-the-attacker-can-read-the-messages-without-alice-and-bob-knowing" tabindex="-1">4) Now the attacker can read the messages without Alice and Bob knowing.</h4>
-<p><img src="./images/20240314-mitm4.jpg" alt="End-to-end encryption is compromised"></p>
+<p><img src="images/20240314-mitm4.jpg" alt="End-to-end encryption is compromised"></p>
 <p>The attack on Diffie-Hellman (or on quantum-resistant) key exchange, when both parties send their public keys (or public key and ciphertext), requires the attacker to intercept and replace both keys, but the outcome remains the same - if all communication is passed via a single channel, as it is usually the case with communication services, then any attacker that has inside access to the service can selectively compromise some of the conversations. Two years ago I wrote the post about this <a href="https://www.poberezkin.com/posts/2022-12-07-why-privacy-needs-to-be-redefined.html#e2e-encryption-is-not-bulletproof">vulnerability of end-to-end encryption to MITM attacks</a>.</p>
 <p>All known mitigations of this attack require using the secondary communication channel to ensure that the keys have not been substituted. The most secure approach is to make user's key (or key fingerprint) a part of the user's address or connection link, thus making two-factor key exchange non-optional. This approach is used in Session, Cwtch and SimpleX Chat.</p>
 <p>A less secure approach is to provide users an optional way to compare security codes - this is what is done by Signal, Element and many other messengers. The problem with this post-key-exchange verification is that it is optional, and is usually skipped by the majority of the users. Also, this security code can change because the user changed the device, or as a result of the attack via the service provider. When you see in the client app the notification that the security code changed, it's pointless to ask in the same messenger whether the device was changed, as if it were an attack, the attacker would simply confirm it. Instead, the security code needs to be re-validated again via another channel. A good security practice for the users would be to warn their communication partners about the intention to switch the device in advance, before the security code is changed.</p>
@@ -472,7 +473,7 @@ window.addEventListener('scroll',changeHeaderBg);
 <h2 id="how-secure-is-end-to-end-encryption-in-different-messengers" tabindex="-1">How secure is end-to-end encryption in different messengers?</h2>
 <p>This comparison may be incorrect in some of the columns. We apologize if some of the points are incorrect, please let us know about any mistakes so we can amend them!</p>
 <p>The main objective here is to establish the framework for comparing the security of end-to-end encryption schemes, and to highlight any areas for improvement, not to criticize any implementations.</p>
-<p><img src="./images/20240314-comparison.jpg" alt="Messengers comparison"></p>
+<p><img src="images/20240314-comparison.jpg" alt="Messengers comparison"></p>
 <p><sup>1</sup> Repudiation in SimpleX Chat will include client-server protocol from v5.7 or v5.8. Currently it is implemented but not enabled yet, as its support requires releasing the relay protocol that breaks backward compatibility.</p>
 <p><sup>2</sup> Post-quantum cryptography is available in beta version, as opt-in only for direct conversations. See below how it will be rolled-out further.</p>
 <p>Some columns are marked with a yellow checkmark:</p>
@@ -517,15 +518,15 @@ window.addEventListener('scroll',changeHeaderBg);
 <h2 id="next-for-post-quantum-crypto-all-direct-chats-small-groups-and-security-audit" tabindex="-1">Next for post-quantum crypto - all direct chats, small groups and security audit</h2>
 <p>We will be making quantum resistance default for all direct chats in v5.7, and we plan that all existing direct chats will be automatically upgraded when both contacts install v5.7.</p>
 <p>We will also be adding quantum resistance to small groups up to 10-20 members. Computing cryptographic keys is much slower, in comparison, and it would be very inefficient (and completely unnecessary) for large public groups.</p>
-<p>We have also arranged a 3rd party cryptographic review of our protocol and encryption schemes design for June/July 2024 - it will cover the additions to SimpleX protocols since <a href="20221108-simplex-chat-v4.2-security-audit-new-website.html">the previous security audit</a> in November 2022, including <a href="20230301-simplex-file-transfer-protocol.html">XFTP protocol</a> we use for file transfers and quantum resistant Signal double ratchet algorithm we just released in this beta version.</p>
+<p>We have also arranged a 3rd party cryptographic review of our protocol and encryption schemes design for June/July 2024 - it will cover the additions to SimpleX protocols since <a href="/blog/20221108-simplex-chat-v4.2-security-audit-new-website.html">the previous security audit</a> in November 2022, including <a href="/blog/20230301-simplex-file-transfer-protocol.html">XFTP protocol</a> we use for file transfers and quantum resistant Signal double ratchet algorithm we just released in this beta version.</p>
 <p>In November 2024 we will be conducting further implementation audit, with double the scope of our 2022 audit.</p>
 <p>Security audits are very expensive, as they require employing exceptionally competent engineers and cryptographers, and it does stretch our budgets - so any donations to help us cover the costs would be hugely helpful.</p>
 <p>That's it for now!</p>
 <p>Thank you for helping us improve the app, and look forward to your feedback.</p>
 <h2 id="simplex-network" tabindex="-1">SimpleX network</h2>
 <p>Some links to answer the most common questions:</p>
-<p><a href="20220511-simplex-chat-v2-images-files.html#the-first-messaging-platform-without-user-identifiers">How can SimpleX deliver messages without user identifiers</a>.</p>
-<p><a href="20220711-simplex-chat-v3-released-ios-notifications-audio-video-calls-database-export-import-protocol-improvements.html#why-having-users-identifiers-is-bad-for-the-users">What are the risks to have identifiers assigned to the users</a>.</p>
+<p><a href="/blog/20220511-simplex-chat-v2-images-files.html#the-first-messaging-platform-without-user-identifiers">How can SimpleX deliver messages without user identifiers</a>.</p>
+<p><a href="/blog/20220711-simplex-chat-v3-released-ios-notifications-audio-video-calls-database-export-import-protocol-improvements.html#why-having-users-identifiers-is-bad-for-the-users">What are the risks to have identifiers assigned to the users</a>.</p>
 <p><a href="https://github.com/simplex-chat/simplex-chat#privacy-technical-details-and-limitations">Technical details and limitations</a>.</p>
 <p><a href="https://github.com/simplex-chat/simplex-chat/blob/stable/README.md#frequently-asked-questions">How SimpleX is different from Session, Matrix, Signal, etc.</a>.</p>
 <p>Please also see our <a href="https://simplex.chat">website</a>.</p>
@@ -413,7 +413,7 @@ window.addEventListener('scroll',changeHeaderBg);
 <h2 id="whats-new-in-v56" tabindex="-1">What's new in v5.6</h2>
 <h3 id="quantum-resistant-end-to-end-encryption-beta" tabindex="-1">Quantum resistant end-to-end encryption (BETA)</h3>
 <p>Adding post-quantum resistance to the double ratchet end-to-end encryption algorithm in SimpleX Chat is a major upgrade to messaging protocols, and it creates the security against the future quantum computers.</p>
-<p>I wrote in detail in the previous post about various properties of end-to-end encryption and how exactly quantum resistance is implemented in SimpleX Chat - currently SimpleX Chat has <a href="20240314-simplex-chat-v5-6-quantum-resistance-signal-double-ratchet-algorithm.html#how-secure-is-end-to-end-encryption-in-different-messengers">the most secure end-to-end encryption design</a> against the present and future attacks.</p>
+<p>I wrote in detail in the previous post about various properties of end-to-end encryption and how exactly quantum resistance is implemented in SimpleX Chat - currently SimpleX Chat has <a href="/blog/20240314-simplex-chat-v5-6-quantum-resistance-signal-double-ratchet-algorithm.html#how-secure-is-end-to-end-encryption-in-different-messengers">the most secure end-to-end encryption design</a> against the present and future attacks.</p>
 <p>We plan to perform a security audit of this design and implementation later this year.</p>
 <p>Post-quantum encryption is currently added as opt-in and has to be separately enabled to be active for the new contacts, and, additionally, can be enabled for the existing contacts.</p>
 <p><img src="./images/20240314-pq1.png" width="288"> <img src="./images/20240314-pq2.png" width="288"> <img src="./images/20240314-pq3.png" width="288"></p>
@@ -438,7 +438,7 @@ window.addEventListener('scroll',changeHeaderBg);
 <p>Since we added the audio and video calls in 2022 a lot of work was done to improve the stability of calls. One of the usability downsides until this release was that it was impossible to use the app during the call.</p>
 <p>This version solved this problem - now you can return back to the app without interrupting the call and use any of the app functions - for example, you can send the messages or files to the person you are in the call with. If this is a video call, you will continue seeing your contact in a small picture-in-picture view.</p>
 <h3 id="migrate-all-app-data-to-another-device-via-qr-code" tabindex="-1">Migrate all app data to another device via QR code</h3>
-<p>We always believed that cross-platform data portability is very important for any software. Users own their data, and they should have a way to export it from any software they use. So from the version of SimpleX Chat <a href="20220711-simplex-chat-v3-released-ios-notifications-audio-video-calls-database-export-import-protocol-improvements.html#database-export-and-import">released in July 2022</a> it was possible to export the database as a self-contained file, including all contacts, messages and files, and import it on a new device.</p>
+<p>We always believed that cross-platform data portability is very important for any software. Users own their data, and they should have a way to export it from any software they use. So from the version of SimpleX Chat <a href="/blog/20220711-simplex-chat-v3-released-ios-notifications-audio-video-calls-database-export-import-protocol-improvements.html#database-export-and-import">released in July 2022</a> it was possible to export the database as a self-contained file, including all contacts, messages and files, and import it on a new device.</p>
 <p><em>&quot;How can I migrate my data to another device?&quot;</em> was one of the most frequent user questions, but until this release this process was <a href="">quite complex</a>, requiring too many steps, and most non-technical users were not willing to try it, as even though it was reliable, it appeared risky.</p>
 <p>This release made the app data migration very simple, see the steps below.</p>
 <p><strong>Start the migration on the source device</strong></p>
@@ -464,8 +464,8 @@ window.addEventListener('scroll',changeHeaderBg);
 <p>The database cannot be used on two devices at the same time, doing so would make it impossible to decrypt the received messages. This is a security measure - the break-in recovery property of double ratchet algorithm.</p>
 <h2 id="simplex-network" tabindex="-1">SimpleX network</h2>
 <p>Some links to answer the most common questions:</p>
-<p><a href="20220511-simplex-chat-v2-images-files.html#the-first-messaging-platform-without-user-identifiers">How can SimpleX deliver messages without user identifiers</a>.</p>
-<p><a href="20220711-simplex-chat-v3-released-ios-notifications-audio-video-calls-database-export-import-protocol-improvements.html#why-having-users-identifiers-is-bad-for-the-users">What are the risks to have identifiers assigned to the users</a>.</p>
+<p><a href="/blog/20220511-simplex-chat-v2-images-files.html#the-first-messaging-platform-without-user-identifiers">How can SimpleX deliver messages without user identifiers</a>.</p>
+<p><a href="/blog/20220711-simplex-chat-v3-released-ios-notifications-audio-video-calls-database-export-import-protocol-improvements.html#why-having-users-identifiers-is-bad-for-the-users">What are the risks to have identifiers assigned to the users</a>.</p>
 <p><a href="https://github.com/simplex-chat/simplex-chat#privacy-technical-details-and-limitations">Technical details and limitations</a>.</p>
 <p><a href="https://github.com/simplex-chat/simplex-chat/blob/stable/README.md#frequently-asked-questions">How SimpleX is different from Session, Matrix, Signal, etc.</a>.</p>
 <p>Please also see our <a href="https://simplex.chat">website</a>.</p>
@@ -391,7 +391,7 @@ window.addEventListener('scroll',changeHeaderBg);
 <p>Some of the world’s top engineers often go to these companies because of the benefits and financial opportunities. We can question their ethics all day long, but we also need to question if the web would look significantly different if there were as many opportunities at privacy-first companies with purpose and strong, proven moral boundaries, set up in a way that can guarantee operational independence from any shareholders and VCs.</p>
 <p>SimpleX could have taken the route of other companies in the privacy space, whether it’s Skiff which rushed to take a large amount of <a href="https://techcrunch.com/2022/03/30/skiff-series-a-encrypted-workspaces/">VC money</a> only to <a href="https://www.techradar.com/computing/cyber-security/skiff-gets-bought-by-notion-raising-privacy-concerns">shutter its doors</a> after an acquisition, leaving its users hanging with many unanswered questions, or giving up control of the company, which would puts its future solely in the hands of VCs with majority ownership. SimpleX aims to prevent this, and in fact has left money on the table to ensure that it does not occur. Had it not been for this information, I would not have joined, and I would have remained a user of the product, albeit a very cautious one, constantly wondering whether it will be sold or corrupted.</p>
 <p>It’s worth noting that some private foundations operate on the VC model in supporting nonprofits, either by requiring Board seats or requesting that their funding be used towards very specific objectives not always in alignment with the organization’s values and mission. It’s also worth noting that <a href="https://www.engadget.com/2019-05-31-sex-lies-and-surveillance-fosta-privacy.html">some nonprofits</a> actually operate on the models of surveillance and censorship. Therefore, whether an organization or company is VC-backed or a nonprofit should not be the sole factor in deciding whether or not it is trustworthy. Actions are important, with full transparency being one of the most critical factors, and being fully open source being another to attract valid criticisms and audits to ensure any product or protocol lives up to its privacy and security promise. SimpleX Chat prides itself on being both transparent and open, on top of also being fully decentralized. If you’re new to it and eager to know more, you can start with <a href="https://github.com/simplex-chat/simplexmq/blob/stable/protocol/overview-tjr.md">this overview</a>.</p>
-<p>Another important consideration is that the SimpleX network does have a plan that would rely on users' payments for specific or tailored services, and not on some other sources of revenue or funds (ads, etc.). Building anything that users would be willing to pay for requires substantially more time and resources, hence the VC route to establish a business model that doesn’t translate to the user being the product. But any business services need to be separate from SimpleX as a public interest technology. As outlined in this <a href="20240323-simplex-network-privacy-non-profit-v5-6-quantum-resistant-e2e-encryption-simple-migration.html">recent post</a>, I’ll be using my background in nonprofit governance structures to ensure that the SimpleX network protocols evolve under the stewardship of nonprofit entities in various jurisdictions, so that its continued evolution aligns more closely with the vision of community-driven, independent and decentralized governance. This would help create a necessary balance between different structures, in the same way many tech nonprofits also have for-profit subsidiaries to attract fee-for-service agreements to sustain their operations.</p>
+<p>Another important consideration is that the SimpleX network does have a plan that would rely on users' payments for specific or tailored services, and not on some other sources of revenue or funds (ads, etc.). Building anything that users would be willing to pay for requires substantially more time and resources, hence the VC route to establish a business model that doesn’t translate to the user being the product. But any business services need to be separate from SimpleX as a public interest technology. As outlined in this <a href="/blog/20240323-simplex-network-privacy-non-profit-v5-6-quantum-resistant-e2e-encryption-simple-migration.html">recent post</a>, I’ll be using my background in nonprofit governance structures to ensure that the SimpleX network protocols evolve under the stewardship of nonprofit entities in various jurisdictions, so that its continued evolution aligns more closely with the vision of community-driven, independent and decentralized governance. This would help create a necessary balance between different structures, in the same way many tech nonprofits also have for-profit subsidiaries to attract fee-for-service agreements to sustain their operations.</p>
 <p>In summary: My decision to join Simplex Chat, despite my deep-rooted beliefs and skepticism towards VC funding, reflects a broader realization: that the fight for privacy, security, and decentralization in today’s web is multifaceted and sometimes requires us to depart from our comfort zones to explore sustainable paths for continuous growth and impact so that open source privacy tools and protocols are no longer “niche”, but universally accessible standards. As long as nothing in this journey compromises our moral principles and integrity, this will remain a very worthwhile goal to pursue.</p>
 </div>
    </section>
@@ -396,15 +396,15 @@ window.addEventListener('scroll',changeHeaderBg);
 <li>Personal info (email address, user IDs, phone number)</li>
 </ul>
 <p>This is called <a href="https://en.wikipedia.org/wiki/Metadata">metadata</a>. It reveals a wealth of information about you and your connections, and in the hands of a centralized monopoly, this can and does get misused in incredibly dangerous ways. Once such metadata is logged, it can create very detailed profiles about who you are, everywhere you’ve been, and everyone you’ve ever spoken to. In settling for apps that normalize this while giving you the illusion of privacy in their marketing, we are doing ourselves a disservice by accepting this as the default. Collectively, we aren’t doing enough to protect ourselves and our social graph from this invasive overreach.</p>
-<p>When stored, aggregated and analyzed, this metadata provides ample information that could potentially incriminate someone or be submitted to authorities. When WhatsApp and Facebook Messenger enabled end-to-end encryption for messages, of course it was a welcome and widely celebrated change. But it’s important to remember that not all end-to-end encryption utilizes the same standards, <a href="https://simplex.chat/blog/20240314-simplex-chat-v5-6-quantum-resistance-signal-double-ratchet-algorithm.html#how-secure-is-end-to-end-encryption-in-different-messengers">some implementations are more secure</a> than others, so it’s something that shouldn’t necessarily be accepted at face value. More importantly: collecting and storing an obscene amount of metadata should invite global scrutiny, considering this data is often combined with whatever other information companies like Meta harvest about your identity (which is <a href="https://www.vox.com/recode/23172691/meta-tracking-privacy-hospitals">a lot</a>.)</p>
+<p>When stored, aggregated and analyzed, this metadata provides ample information that could potentially incriminate someone or be submitted to authorities. When WhatsApp and Facebook Messenger enabled end-to-end encryption for messages, of course it was a welcome and widely celebrated change. But it’s important to remember that not all end-to-end encryption utilizes the same standards, <a href="/blog/20240314-simplex-chat-v5-6-quantum-resistance-signal-double-ratchet-algorithm.html#how-secure-is-end-to-end-encryption-in-different-messengers">some implementations are more secure</a> than others, so it’s something that shouldn’t necessarily be accepted at face value. More importantly: collecting and storing an obscene amount of metadata should invite global scrutiny, considering this data is often combined with whatever other information companies like Meta harvest about your identity (which is <a href="https://www.vox.com/recode/23172691/meta-tracking-privacy-hospitals">a lot</a>.)</p>
 <img src="./images/20240416-metadata.png" class="float-to-right" width="38%">
 <p>This is one of the many reasons why we need to resist giving out our phone numbers just to access an app, especially to do something as personal and intimate as private messaging. Even though users can sometimes mask their numbers with a username, their identity on the app is still fundamentally tied to their phone number. App operators have access to this, as well as user contacts. Additionally, with a simple modification to the app's source code, the contacts may also gain access in some cases. This should raise more concerns about privacy, and it makes the need for anonymity difficult to achieve.</p>
 <p>Everyone has a different threat model (and if you don’t yet, now is a good time to <a href="https://www.privacyguides.org/en/basics/threat-modeling/#creating-your-threat-model">create one</a>). For many users today, WhatsApp and other apps may be sufficient for their specific needs, especially in connecting with families and friends who are already on the app and unlikely to migrate elsewhere. If that suits your life and needs, and if you’re aware and consciously accept the risks, great.</p>
 <p>But we also need to acknowledge that the world is becoming increasingly dangerous in the way AI is being used to <a href="https://www.forbes.com/sites/forbestechcouncil/2024/02/02/artificial-intelligence-the-new-eyes-of-surveillance/?sh=cd57bc214f27">supercharge surveillance</a>, and we need to be educated and aware of the risks this is already having on our lives and what it subjects others in your network to when you choose metadata-heavy apps as your primary form of communication. Having alternatives will always be important, even if it’s not what you default to for everyday messaging. Recognize who in your social circles might require the extra privacy, anonymity and security, so that you can play a role in protecting vulnerable individuals who need it most. The messaging app you choose implicates others as well, not just yourself, and while you personally may not require complete privacy, others might have their lives depend on it.</p>
 <p>End-to-end encryption is a solid start, but it's just the beginning of our pursuit for true privacy and security. True privacy means that even when legal demands come knocking, there's no useful metadata to hand over. It's not enough to just protect the content of messages; we need consistent innovation in protecting metadata too.</p>
-<p>Changing ingrained habits is tough, but your privacy is always worth the fight. Although giants like WhatsApp and Telegram may dominate global messaging for now, increasing concerns about data harvesting and AI-driven surveillance are fueling demand for alternatives. SimpleX Chat aims to be one of those strong alternatives, hence its radical focus on a decentralized framework with no user identifiers (in other words, nothing that uniquely identifies users on the protocol level to their contacts or to the relays) and extra optionality (self-hosting an <a href="https://simplex.chat/docs/server.html">SMP server</a> or <a href="https://simplex.chat/docs/xftp-server.html">XFTP server</a>, access via Tor, <a href="https://simplex.chat/docs/guide/chat-profiles.html">chat profiles</a> with incognito mode, etc.)</p>
+<p>Changing ingrained habits is tough, but your privacy is always worth the fight. Although giants like WhatsApp and Telegram may dominate global messaging for now, increasing concerns about data harvesting and AI-driven surveillance are fueling demand for alternatives. SimpleX Chat aims to be one of those strong alternatives, hence its radical focus on a decentralized framework with no user identifiers (in other words, nothing that uniquely identifies users on the protocol level to their contacts or to the relays) and extra optionality (self-hosting an <a href="/docs/server.html">SMP server</a> or <a href="/docs/xftp-server.html">XFTP server</a>, access via Tor, <a href="/docs/guide/chat-profiles.html">chat profiles</a> with incognito mode, etc.)</p>
 <p>As of today, most messaging alternatives, including SimpleX, will have some limitations. But with the limited resources we have, we are committed to daily progress towards creating a truly private messenger that anyone can use while maintaining the features that users have come to know and love in messaging interfaces. We want to be the prime example of a messenger that achieves genuine privacy without compromising it for convenience. We need to be able to reliably move away from small and niche use cases to endorsing and enforcing global standards for privacy and making it accessible for all users regardless of their technical expertise.</p>
-<p>We’re grateful for the users and <a href="https://github.com/simplex-chat/simplex-chat#help-us-with-donations">donors</a> who have been following along on this journey thus far and helping with feedback, anything from bug reports to identifying potential risks. Building in the open has always been a necessity for transparency and ongoing <a href="https://simplex.chat/blog/20221108-simplex-chat-v4.2-security-audit-new-website.html">auditability</a>, because we don’t want anyone to just take our word for it. <a href="https://github.com/simplex-chat">See for yourself</a> and engage in the discussions. We fully expect you to hold us accountable to our word.</p>
+<p>We’re grateful for the users and <a href="https://github.com/simplex-chat/simplex-chat#help-us-with-donations">donors</a> who have been following along on this journey thus far and helping with feedback, anything from bug reports to identifying potential risks. Building in the open has always been a necessity for transparency and ongoing <a href="/blog/20221108-simplex-chat-v4.2-security-audit-new-website.html">auditability</a>, because we don’t want anyone to just take our word for it. <a href="https://github.com/simplex-chat">See for yourself</a> and engage in the discussions. We fully expect you to hold us accountable to our word.</p>
 </div>
    </section>

@@ -379,6 +379,7 @@ window.addEventListener('scroll',changeHeaderBg);

    <section id="article" class="container mb-[75px] bg-white dark:bg-[#17203D] px-5">
      <div class="py-6 md:p-[60px]"><h1 id="simplex-network-legally-binding-transparency-v57-released-with-better-calls-and-messages" tabindex="-1">SimpleX network: legally binding transparency, v5.7 released with better calls and messages</h1>
+<p><strong>Published:</strong> Apr 26, 2024</p>
 <p>What's new in v5.7:</p>
 <ul>
 <li><a href="#quantum-resistant-end-to-end-encryption">quantum resistant end-to-end encryption</a> with all contacts.</li>
@@ -391,10 +392,10 @@ window.addEventListener('scroll',changeHeaderBg);
 <h2 id="legally-binding-transparency" tabindex="-1">Legally binding transparency</h2>
 <p>We are committed to open-source, privacy and security. Here are the recent changes we made:</p>
 <ul>
-<li>We now have a <a href="https://simplex.chat/transparency/">Transparency Reports</a> page.</li>
-<li>We updated our <a href="https://github.com/simplex-chat/simplex-chat/blob/stable/PRIVACY.md">Privacy Policy</a> to remove undefined terms &quot;impermissible&quot; and &quot;acceptable&quot;, which would allow us to remove anything we don't like, without any clarity on what that is. You can see the edits <a href="https://github.com/simplex-chat/simplex-chat/pull/4076/files">here</a>.</li>
-<li>We published a new page with <a href="https://simplex.chat/faq/">Frequently Asked Questions</a>, thanks to the guidance from users.</li>
-<li>We also have a new <a href="https://simplex.chat/security/">Security Policy</a> – we welcome your feedback on it.</li>
+<li>We now have a <a href="/transparency/index.html">Transparency Reports</a> page.</li>
+<li>We updated our <a href="https%3A//github.com/simplex-chat/simplex-chat/blob/stable/simplex-chat/PRIVACY.md">Privacy Policy</a> to remove undefined terms &quot;impermissible&quot; and &quot;acceptable&quot;, which would allow us to remove anything we don't like, without any clarity on what that is. You can see the edits <a href="https://github.com/simplex-chat/simplex-chat/pull/4076/files">here</a>.</li>
+<li>We published a new page with <a href="/faq/index.html">Frequently Asked Questions</a>, thanks to the guidance from users.</li>
+<li>We also have a new <a href="/security/index.html">Security Policy</a> – we welcome your feedback on it.</li>
 </ul>
 <p>What do we mean by “legally binding transparency?”. It includes these principles:</p>
 <ul>
@@ -411,7 +412,7 @@ window.addEventListener('scroll',changeHeaderBg);
 <p>This release focus is improving the app usability, and preparing the foundation for v5.8 that will provide an in-built protection of user IP addresses when connecting to unknown file and messaging servers, reducing the need to use Tor (which would still remain supported via SOCKS proxy, for additional privacy).</p>
 <h3 id="quantum-resistant-end-to-end-encryption" tabindex="-1">Quantum resistant end-to-end encryption</h3>
 <img src="./images/20240426-pq.png" width="288" class="float-right">
-<p>We <a href="20240314-simplex-chat-v5-6-quantum-resistance-signal-double-ratchet-algorithm.html">wrote before</a> about how quantum resistant encryption was added to SimpleX Chat and also about other properties of end-to-end encryption, possible attacks on its security and known mitigations.</p>
+<p>We <a href="/blog/20240314-simplex-chat-v5-6-quantum-resistance-signal-double-ratchet-algorithm.html">wrote before</a> about how quantum resistant encryption was added to SimpleX Chat and also about other properties of end-to-end encryption, possible attacks on its security and known mitigations.</p>
 <p>Quantum resistant encryption will now be enabled by default in all direct chats. For the new conversations it will be enabled from the beginning, and for the existing conversations it will be agreed after you exchange several messages with your contacts - you will see a notice in the conversation when it happens.</p>
 <p>You can still safely downgrade the app to an earlier version if needed, as v5.6 already supports quantum resistant encryption.</p>
 <p>With the users who have an earlier version, the app will work using the conventional encryption, which is still very secure. It's important that we augmented the conventional encryption with post-quantum cryptographic algorithm rather than replaced it, using a hybrid construction as recommended by the cryptography experts.</p>
@@ -430,10 +431,10 @@ window.addEventListener('scroll',changeHeaderBg);
 <p><img src="./images/20240426-profile1.png" width="288"> <img src="./images/20240426-profile2.png" width="288"> <img src="./images/20240426-profile3.png" width="288"></p>
 <h2 id="simplex-network" tabindex="-1">SimpleX network</h2>
 <p>Some links to answer the most common questions:</p>
-<p><a href="20220511-simplex-chat-v2-images-files.html#the-first-messaging-platform-without-user-identifiers">How can SimpleX deliver messages without user identifiers</a>.</p>
-<p><a href="20220711-simplex-chat-v3-released-ios-notifications-audio-video-calls-database-export-import-protocol-improvements.html#why-having-users-identifiers-is-bad-for-the-users">What are the risks to have identifiers assigned to the users</a>.</p>
+<p><a href="/blog/20220511-simplex-chat-v2-images-files.html#the-first-messaging-platform-without-user-identifiers">How can SimpleX deliver messages without user identifiers</a>.</p>
+<p><a href="/blog/20220711-simplex-chat-v3-released-ios-notifications-audio-video-calls-database-export-import-protocol-improvements.html#why-having-users-identifiers-is-bad-for-the-users">What are the risks to have identifiers assigned to the users</a>.</p>
 <p><a href="https://github.com/simplex-chat/simplex-chat#privacy-technical-details-and-limitations">Technical details and limitations</a>.</p>
-<p><a href="docs/faq.html">Frequently asked questions</a>.</p>
+<p><a href="/faq/index.html">Frequently asked questions</a>.</p>
 <p>Please also see our <a href="https://simplex.chat">website</a>.</p>
 <h2 id="help-us-with-donations" tabindex="-1">Help us with donations</h2>
 <p>Huge thank you to everybody who donates to SimpleX Chat!</p>
@@ -0,0 +1,82 @@
+<svg width="539" height="399" viewBox="0 0 539 399" fill="none" xmlns="http://www.w3.org/2000/svg">
+<circle cx="268.083" cy="80.9476" r="32.1985" fill="url(#paint0_linear_651_6627)"/>
+<circle cx="268.082" cy="80.9513" r="39.3169" stroke="url(#paint1_linear_651_6627)" stroke-width="0.956242"/>
+<circle cx="267.428" cy="73.3473" r="5.65297" fill="white"/>
+<path fill-rule="evenodd" clip-rule="evenodd" d="M256.025 90.0869H278.595C277.039 85.3429 272.575 81.917 267.31 81.917C262.046 81.917 257.582 85.3429 256.025 90.0869Z" fill="white"/>
+<circle cx="40.5779" cy="218.884" r="32.1985" fill="url(#paint2_linear_651_6627)"/>
+<circle cx="40.5777" cy="218.888" r="39.3169" stroke="url(#paint3_linear_651_6627)" stroke-width="0.956242"/>
+<circle cx="39.9227" cy="211.284" r="5.65297" fill="white"/>
+<path fill-rule="evenodd" clip-rule="evenodd" d="M51.0904 228.023H28.5205C30.0767 223.279 34.541 219.854 39.8054 219.854C45.0699 219.854 49.5341 223.279 51.0904 228.023Z" fill="white"/>
+<circle cx="268.083" cy="358.611" r="32.1985" fill="url(#paint4_linear_651_6627)"/>
+<circle cx="268.082" cy="358.614" r="39.3169" stroke="url(#paint5_linear_651_6627)" stroke-width="0.956242"/>
+<circle cx="267.428" cy="351.01" r="5.65297" fill="white"/>
+<path fill-rule="evenodd" clip-rule="evenodd" d="M256.025 367.75H278.595C277.039 363.006 272.575 359.58 267.31 359.58C262.046 359.58 257.582 363.006 256.025 367.75Z" fill="white"/>
+<circle cx="499.17" cy="217.092" r="32.1985" fill="url(#paint6_linear_651_6627)"/>
+<circle cx="499.17" cy="217.096" r="39.3169" stroke="url(#paint7_linear_651_6627)" stroke-width="0.956242"/>
+<circle cx="498.515" cy="209.492" r="5.65297" fill="white"/>
+<path fill-rule="evenodd" clip-rule="evenodd" d="M509.683 226.231H487.113C488.669 221.487 493.133 218.062 498.398 218.062C503.662 218.062 508.126 221.487 509.683 226.231Z" fill="white"/>
+<path d="M79.8735 192.248L224.526 103.265" stroke="#0197FF" stroke-width="2.99282" stroke-linecap="round" stroke-dasharray="5.99 8.98"/>
+<path d="M455.16 192.248L310.507 103.265" stroke="#CD5CAE" stroke-width="2.99282" stroke-linecap="round" stroke-dasharray="5.99 8.98"/>
+<path d="M222.747 338.695L78.0943 249.712" stroke="#9B90FB" stroke-width="2.99282" stroke-linecap="round" stroke-dasharray="5.99 8.98"/>
+<path d="M268.016 301.529L268.016 137.652" stroke="#1BC3BF" stroke-width="2.99282" stroke-linecap="round" stroke-dasharray="5.99 8.98"/>
+<rect x="87.3558" y="63.0347" width="42.9204" height="42.9204" rx="2.99282" stroke="#0197FF" stroke-width="1.99521"/>
+<path d="M108.408 76.2031H111.281V92.9629H107.977V79.6987L104.817 80.5846L104.002 77.7594L108.408 76.2031Z" fill="#0197FF"/>
+<rect x="167.228" y="198.131" width="42.9204" height="42.9204" rx="2.99282" stroke="#0197FF" stroke-width="1.99521"/>
+<path d="M190.169 218.101C191.303 218.437 192.22 219.027 192.923 219.873C193.641 220.703 194 221.709 194 222.89C194 224.614 193.417 225.963 192.252 226.936C191.103 227.91 189.69 228.397 188.014 228.397C186.706 228.397 185.532 228.101 184.495 227.511C183.473 226.904 182.731 226.018 182.268 224.853L185.093 223.225C185.508 224.518 186.482 225.164 188.014 225.164C188.86 225.164 189.515 224.965 189.978 224.566C190.457 224.151 190.696 223.592 190.696 222.89C190.696 222.204 190.457 221.653 189.978 221.238C189.515 220.823 188.86 220.615 188.014 220.615H187.296L186.027 218.7L189.331 214.39H182.771V211.302H193.306V214.031L190.169 218.101Z" fill="#0197FF"/>
+<rect x="86.9073" y="326.685" width="42.9204" height="42.9204" rx="2.99282" stroke="#0197FF" stroke-width="1.99521"/>
+<path d="M108.065 345.96C109.677 345.96 111.034 346.447 112.136 347.42C113.237 348.378 113.788 349.719 113.788 351.443C113.788 353.167 113.205 354.515 112.04 355.489C110.891 356.463 109.478 356.949 107.802 356.949C106.445 356.949 105.248 356.646 104.211 356.04C103.173 355.433 102.423 354.539 101.96 353.358L104.785 351.706C105.2 353.047 106.206 353.717 107.802 353.717C108.648 353.717 109.302 353.518 109.765 353.119C110.244 352.704 110.484 352.145 110.484 351.443C110.484 350.756 110.252 350.206 109.789 349.791C109.326 349.376 108.696 349.168 107.898 349.168H102.822L103.492 339.854H112.997V342.943H106.557L106.341 345.96H108.065Z" fill="#0197FF"/>
+<path d="M72.9777 331.097C72.8728 331.917 72.1232 332.497 71.3035 332.392L57.9447 330.682C57.125 330.577 56.5455 329.828 56.6504 329.008C56.7553 328.188 57.5049 327.609 58.3246 327.714L70.199 329.233L71.7186 317.359C71.8235 316.539 72.5731 315.959 73.3928 316.064C74.2126 316.169 74.7921 316.919 74.6872 317.739L72.9777 331.097ZM38.6697 271.837C44.3979 288.6 58.4045 311.53 72.6773 329.992L70.3095 331.823C55.9494 313.248 41.7191 290.016 35.8377 272.805L38.6697 271.837Z" fill="#9B90FB"/>
+<path d="M215.639 371.664C216.25 372.22 216.295 373.167 215.738 373.778L206.672 383.737C206.115 384.348 205.169 384.392 204.558 383.836C203.947 383.279 203.902 382.333 204.459 381.722L212.518 372.87L203.666 364.811C203.054 364.254 203.01 363.308 203.566 362.697C204.123 362.085 205.069 362.041 205.68 362.597L215.639 371.664ZM147.42 365.75C164.435 370.679 191.252 372.369 214.562 371.276L214.702 374.265C191.249 375.365 164.057 373.686 146.587 368.625L147.42 365.75Z" fill="#9B90FB"/>
+<path d="M186.13 264.557C186.388 263.772 187.233 263.344 188.018 263.601L200.815 267.8C201.6 268.057 202.028 268.903 201.77 269.688C201.513 270.473 200.667 270.901 199.882 270.644L188.507 266.912L184.775 278.286C184.518 279.072 183.672 279.499 182.887 279.242C182.102 278.984 181.674 278.139 181.932 277.353L186.13 264.557ZM228.079 319.816C211.627 305.232 196.047 285.13 186.217 265.699L188.887 264.348C198.544 283.436 213.89 303.238 230.065 317.576L228.079 319.816Z" fill="#9B90FB"/>
+<path d="M101.379 249.32C100.828 248.704 100.881 247.758 101.497 247.208L111.539 238.233C112.155 237.682 113.101 237.736 113.652 238.352C114.203 238.968 114.149 239.914 113.533 240.465L104.607 248.442L112.584 257.368C113.135 257.984 113.082 258.93 112.466 259.481C111.85 260.032 110.904 259.978 110.353 259.362L101.379 249.32ZM162.973 242.498C143.252 249.825 124.069 251.033 102.41 249.817L102.578 246.829C124.02 248.033 142.745 246.821 161.931 239.692L162.973 242.498Z" fill="#9B90FB"/>
+<rect x="325.884" y="198.131" width="42.9204" height="42.9204" rx="2.99282" stroke="#0197FF" stroke-width="1.99521"/>
+<path d="M353.504 222.148V225.212H351.708V228.062H348.38V225.212H340.455V222.148L346.034 211.302H349.577L344.022 222.148H348.38V218.173H351.708V222.148H353.504Z" fill="#0197FF"/>
+<path d="M317.746 191.65C318.511 191.964 319.385 191.599 319.699 190.835L324.815 178.376C325.129 177.612 324.764 176.738 323.999 176.424C323.235 176.11 322.36 176.475 322.046 177.24L317.499 188.313L306.425 183.766C305.661 183.452 304.786 183.817 304.472 184.582C304.158 185.346 304.524 186.221 305.288 186.535L317.746 191.65ZM283.185 132.538C294.926 145.802 307.938 169.311 316.934 190.843L319.696 189.689C310.645 168.026 297.481 144.173 285.425 130.554L283.185 132.538Z" fill="#1BC3BF"/>
+<path d="M302.485 317.64C302.635 318.453 303.416 318.99 304.228 318.839L317.472 316.393C318.284 316.243 318.822 315.462 318.671 314.649C318.521 313.837 317.741 313.3 316.928 313.45L305.156 315.625L302.981 303.853C302.831 303.04 302.05 302.503 301.238 302.653C300.425 302.803 299.888 303.584 300.038 304.396L302.485 317.64ZM333.458 256.571C328.667 273.625 315.952 297.296 302.724 316.52L305.189 318.216C318.498 298.875 331.42 274.89 336.339 257.38L333.458 256.571Z" fill="#1BC3BF"/>
+<path d="M214.41 250.543C213.646 250.228 212.771 250.592 212.456 251.356L207.324 263.807C207.009 264.571 207.373 265.446 208.137 265.761C208.902 266.076 209.776 265.712 210.091 264.948L214.653 253.88L225.721 258.442C226.485 258.757 227.36 258.393 227.675 257.629C227.99 256.864 227.626 255.99 226.862 255.675L214.41 250.543ZM248.894 309.7C237.17 296.421 224.189 272.895 215.221 251.351L212.458 252.501C221.481 274.177 234.613 298.046 246.651 311.681L248.894 309.7Z" fill="#1BC3BF"/>
+<path d="M252.992 138.384C252.581 137.667 251.666 137.42 250.949 137.832L239.272 144.542C238.556 144.954 238.309 145.868 238.72 146.585C239.132 147.302 240.047 147.549 240.763 147.137L251.143 141.172L257.107 151.552C257.519 152.269 258.434 152.516 259.15 152.104C259.867 151.692 260.114 150.778 259.702 150.061L252.992 138.384ZM223.657 201.324C235.535 186.647 247.194 161.53 253.14 139.52L250.25 138.739C244.379 160.474 232.874 185.176 221.331 199.442L223.657 201.324Z" fill="#1BC3BF"/>
+<rect x="398.022" y="63.0347" width="42.9204" height="42.9204" rx="2.99282" stroke="#0197FF" stroke-width="1.99521"/>
+<path d="M413.321 92.9629V90.4968L419.044 84.607C420.321 83.2662 420.959 82.1489 420.959 81.255C420.959 80.6006 420.752 80.0738 420.337 79.6748C419.938 79.2757 419.419 79.0762 418.78 79.0762C417.519 79.0762 416.586 79.7307 415.979 81.0395L413.202 79.4114C413.728 78.2622 414.487 77.3843 415.476 76.7777C416.466 76.1712 417.551 75.8679 418.732 75.8679C420.249 75.8679 421.55 76.3468 422.635 77.3045C423.721 78.2462 424.263 79.5232 424.263 81.1353C424.263 82.8751 423.345 84.6628 421.51 86.4984L418.23 89.7785H424.527V92.9629H413.321Z" fill="#0197FF"/>
+<path d="M77.1479 111.221C77.253 110.401 76.6737 109.651 75.854 109.546L62.4958 107.833C61.676 107.727 60.9263 108.307 60.8211 109.126C60.716 109.946 61.2953 110.696 62.115 110.801L73.989 112.324L72.4659 124.198C72.3607 125.018 72.94 125.768 73.7598 125.873C74.5795 125.978 75.3292 125.399 75.4344 124.579L77.1479 111.221ZM42.3631 168.218C46.7014 146.722 60.4086 124.708 76.5785 112.214L74.7487 109.846C57.9918 122.793 43.9057 145.446 39.4294 167.626L42.3631 168.218Z" fill="#0197FF"/>
+<path d="M215.45 70.1934C216.205 69.8575 216.545 68.973 216.209 68.2179L210.734 55.9134C210.398 55.1584 209.513 54.8186 208.758 55.1546C208.003 55.4906 207.663 56.3751 207.999 57.1301L212.866 68.0675L201.929 72.9343C201.174 73.2703 200.834 74.1548 201.17 74.9098C201.506 75.6649 202.391 76.0046 203.146 75.6686L215.45 70.1934ZM148.677 70.0794C169.298 62.6197 195.23 62.8963 214.305 70.2232L215.378 67.4294C195.611 59.8365 168.936 59.5682 147.659 67.2651L148.677 70.0794Z" fill="#0197FF"/>
+<path d="M203.562 181.745C203.705 182.559 204.482 183.102 205.295 182.959L218.558 180.62C219.372 180.476 219.916 179.7 219.772 178.886C219.629 178.072 218.852 177.529 218.039 177.672L206.249 179.752L204.17 167.962C204.027 167.148 203.25 166.605 202.436 166.749C201.623 166.892 201.079 167.668 201.223 168.482L203.562 181.745ZM235.03 120.93C230.101 137.944 217.194 161.511 203.81 180.627L206.261 182.343C219.727 163.111 232.843 139.232 237.905 121.762L235.03 120.93Z" fill="#0197FF"/>
+<path d="M86.7735 223.138C86.1511 223.682 86.0872 224.627 86.6309 225.249L95.4903 235.393C96.034 236.015 96.9793 236.079 97.6018 235.535C98.2242 234.992 98.2881 234.046 97.7444 233.424L89.8693 224.408L98.8857 216.533C99.5081 215.989 99.572 215.044 99.0283 214.421C98.4846 213.799 97.5393 213.735 96.9169 214.279L86.7735 223.138ZM155.1 218.631C137.987 223.208 111.141 224.345 87.8588 222.772L87.657 225.758C111.082 227.341 138.303 226.222 155.873 221.522L155.1 218.631Z" fill="#0197FF"/>
+<path d="M383.345 66.4144C384.119 66.1236 384.51 65.2608 384.219 64.4872L379.481 51.8806C379.19 51.107 378.327 50.7156 377.554 51.0064C376.78 51.2971 376.389 52.16 376.679 52.9336L380.891 64.1394L369.686 68.3513C368.912 68.6421 368.521 69.505 368.811 70.2786C369.102 71.0522 369.965 71.4436 370.739 71.1528L383.345 66.4144ZM316.695 62.3541C337.722 56.1262 363.592 57.9349 382.2 66.3764L383.437 63.6509C364.152 54.903 337.54 53.0586 315.845 59.4845L316.695 62.3541Z" fill="#CD5CAE"/>
+<path d="M484.334 169.427C484.984 169.937 485.925 169.823 486.435 169.173L494.746 158.575C495.256 157.925 495.142 156.984 494.491 156.474C493.841 155.964 492.901 156.078 492.391 156.728L485.003 166.149L475.583 158.761C474.933 158.251 473.992 158.365 473.482 159.016C472.972 159.666 473.086 160.607 473.736 161.117L484.334 169.427ZM453.18 110.367C469.425 125.098 481.318 148.143 483.772 168.429L486.743 168.07C484.2 147.047 471.952 123.35 455.191 108.15L453.18 110.367Z" fill="#CD5CAE"/>
+<path d="M381.01 219.006C380.358 219.514 380.241 220.455 380.749 221.107L389.024 231.732C389.532 232.384 390.472 232.501 391.124 231.993C391.776 231.485 391.893 230.545 391.386 229.893L384.03 220.448L393.475 213.093C394.127 212.585 394.244 211.645 393.736 210.993C393.228 210.341 392.288 210.224 391.636 210.731L381.01 219.006ZM449.482 218.349C432.139 221.957 405.272 221.582 382.115 218.702L381.745 221.672C405.044 224.57 432.285 224.983 450.091 221.279L449.482 218.349Z" fill="#CD5CAE"/>
+<path d="M305.2 125.099C304.379 125.194 303.791 125.937 303.886 126.758L305.439 140.136C305.534 140.957 306.277 141.545 307.098 141.45C307.919 141.355 308.507 140.612 308.412 139.791L307.032 127.9L318.923 126.52C319.744 126.424 320.332 125.682 320.237 124.861C320.142 124.04 319.399 123.451 318.578 123.547L305.2 125.099ZM342.253 184.234C340.61 174.231 335.593 162.688 329.05 152.113C322.503 141.531 314.345 131.783 306.302 125.413L304.444 127.759C312.143 133.857 320.086 143.312 326.505 153.687C332.928 164.069 337.742 175.237 339.299 184.719L342.253 184.234Z" fill="#CD5CAE"/>
+<defs>
+<linearGradient id="paint0_linear_651_6627" x1="299.334" y1="48.749" x2="222.184" y2="75.0796" gradientUnits="userSpaceOnUse">
+<stop stop-color="#53C1FF"/>
+<stop offset="1" stop-color="#0053D0"/>
+</linearGradient>
+<linearGradient id="paint1_linear_651_6627" x1="306.707" y1="41.1562" x2="211.356" y2="73.6989" gradientUnits="userSpaceOnUse">
+<stop stop-color="#53C1FF"/>
+<stop offset="1" stop-color="#0053D0"/>
+</linearGradient>
+<linearGradient id="paint2_linear_651_6627" x1="71.8294" y1="186.686" x2="-5.32023" y2="213.016" gradientUnits="userSpaceOnUse">
+<stop stop-color="#53C1FF"/>
+<stop offset="1" stop-color="#0053D0"/>
+</linearGradient>
+<linearGradient id="paint3_linear_651_6627" x1="79.2023" y1="179.093" x2="-16.149" y2="211.635" gradientUnits="userSpaceOnUse">
+<stop stop-color="#53C1FF"/>
+<stop offset="1" stop-color="#0053D0"/>
+</linearGradient>
+<linearGradient id="paint4_linear_651_6627" x1="299.334" y1="326.412" x2="222.184" y2="352.743" gradientUnits="userSpaceOnUse">
+<stop stop-color="#53C1FF"/>
+<stop offset="1" stop-color="#0053D0"/>
+</linearGradient>
+<linearGradient id="paint5_linear_651_6627" x1="306.707" y1="318.819" x2="211.356" y2="351.362" gradientUnits="userSpaceOnUse">
+<stop stop-color="#53C1FF"/>
+<stop offset="1" stop-color="#0053D0"/>
+</linearGradient>
+<linearGradient id="paint6_linear_651_6627" x1="530.421" y1="184.894" x2="453.272" y2="211.224" gradientUnits="userSpaceOnUse">
+<stop stop-color="#53C1FF"/>
+<stop offset="1" stop-color="#0053D0"/>
+</linearGradient>
+<linearGradient id="paint7_linear_651_6627" x1="537.794" y1="177.301" x2="442.443" y2="209.843" gradientUnits="userSpaceOnUse">
+<stop stop-color="#53C1FF"/>
+<stop offset="1" stop-color="#0053D0"/>
+</linearGradient>
+</defs>
+</svg>
@@ -409,6 +409,52 @@ window.addEventListener('scroll',changeHeaderBg);

        
        
+            <article class="w-full flex flex-col items-start md:flex-row rounded-[4px] overflow-hidden shadow-[0px_20px_30px_rgba(0,0,0,0.12)] dark:shadow-none bg-white dark:bg-[#11182F] mb-8">
+                <div class="min-h-[200px] h-[inherit] self-stretch md:w-[168px] bg-[#D9E7ED] dark:bg-[#17203D] flex items-center justify-center flex-[1] relative">
+                    <div class="min-h-[inherit] h-full w-full flex items-end px-4 pt-4 justify-center relative">
+                        
+                            
+                                <img class="mb-4 self-center w-full h-auto" src="images/simplex-explained.svg" alt="" srcset="">
+                            
+                        
+                    </div>
+                </div>
+                <div class="p-6 md:py-8 flex-[2.5] flex flex-col">
+                    <div>
+                        <h1 class="text-grey-black dark:text-white text-lg md:text-xl font-bold ">
+                            <a href="/blog/20240516-simplex-redefining-privacy-hard-choices.html">SimpleX: Redefining Privacy by Making Hard Choices</a>
+                        </h1>
+                        <p class="text-sm text-[#A8B0B4] font-medium mt-2 mb-4 tracking-[0.03em]">
+                            16 May 2024
+                        </p>
+                        
+                            <div class="mb-4 dark:text-white">
+                                <p class="mb-[12px]">When it comes to open source privacy tools, the status quo often dictates the limitations of
+    existing protocols and
+    structures. However, these norms need to be challenged to radically shift how we approach genuinely
+    private communication. This requires doing some uncomfortable things, like making hard choices as it relates to
+    funding, alternative decentralization models, doubling down on privacy over convenience, and more.
+</p>
+
+<p class="mb-[12px]">In this post we explain a bit more about why SimpleX operates and makes decisions the way it does:
+</p>
+
+<ul class="mb-[12px]">
+    <li>No user accounts.</li>
+    <li>Privacy over convenience.</li>
+    <li>Network decentralization.</li>
+    <li>Funding and profitability.</li>
+    <li>Company jurisdiction.</li>
+</ul>
+                            </div>
+                        
+                    </div>
+                    <a class="block text-primary-light dark:text-[#70F0F9] text-base font-medium tracking-[0.03em] mt-auto" href="/blog/20240516-simplex-redefining-privacy-hard-choices.html">Read More</a>
+                </div>
+            </article>
+        
+        
+        
            <article class="w-full flex flex-col items-start md:flex-row rounded-[4px] overflow-hidden shadow-[0px_20px_30px_rgba(0,0,0,0.12)] dark:shadow-none bg-white dark:bg-[#11182F] mb-8">
                <div class="min-h-[200px] h-[inherit] self-stretch md:w-[168px] bg-[#D9E7ED] dark:bg-[#17203D] flex items-center justify-center flex-[1] relative">
                    <div class="min-h-[inherit] h-full w-full flex items-end px-4 pt-4 justify-center relative">
@@ -1,5 +1,5 @@
 <h1 id="blog" tabindex="-1">Blog</h1>
-<p>4 févr. 2023 <a href="20230103-simplex-chat-v4.4-disappearing-messages.html">SimpleX Chat v4.5 publié</a></p>
+<p>4 févr. 2023 <a href="/blog/20230103-simplex-chat-v4.4-disappearing-messages.html">SimpleX Chat v4.5 publié</a></p>
 <ul>
 <li>profils de chat multiples.</li>
 <li>brouillon de message.</li>
@@ -8,7 +8,7 @@
 <li>noms de fichiers privés.</li>
 </ul>
 <p>Nous avons également ajouté <a href="#french-language-interface">l'interface en italien</a>, grâce à nos utilisateurs et à Weblate !</p>
-<p>3 janv. 2023 <a href="20230103-simplex-chat-v4.4-disappearing-messages.html">SimpleX Chat v4.4 publié</a></p>
+<p>3 janv. 2023 <a href="/blog/20230103-simplex-chat-v4.4-disappearing-messages.html">SimpleX Chat v4.4 publié</a></p>
 <ul>
 <li>messages éphèméres.</li>
 <li>messages &quot;en direct&quot; (dynamique).</li>
@@ -16,7 +16,7 @@
 <li>images animées et autocollants - maintenant aussi sur iOS.</li>
 </ul>
 <p>Nous avons également ajouté <a href="#french-language-interface">l'interface en français</a>, grâce à nos utilisateurs et à Weblate !</p>
-<p>6 déc. 2022 <a href="20221206-simplex-chat-v4.3-voice-messages.html">SimpleX Chat : révision et sortie de la v4.3</a></p>
+<p>6 déc. 2022 <a href="/blog/20221206-simplex-chat-v4.3-voice-messages.html">SimpleX Chat : révision et sortie de la v4.3</a></p>
 <p>Critiques de novembre :</p>
 <ul>
 <li>Recommandations de <a href="https://www.privacyguides.org/real-time-communication/#simplex-chat">Privacy Guides</a>.</li>
@@ -31,7 +31,7 @@
 <li>amélioration de la configuration du serveur SMP et du support des mots de passe du serveur</li>
 <li>améliorations de la confidentialité et de la sécurité : protection de l'écran de l'application, sécurité des liens SimpleX, etc.</li>
 </ul>
-<p>8 nov. 2022 <a href="20221108-simplex-chat-v4.2-security-audit-new-website.html">Audit de sécurité par Trail of Bits, nouveau site web et sortie de la v4.2</a></p>
+<p>8 nov. 2022 <a href="/blog/20221108-simplex-chat-v4.2-security-audit-new-website.html">Audit de sécurité par Trail of Bits, nouveau site web et sortie de la v4.2</a></p>
 <p><em>&quot;Avez-vous été audité ou devons-nous simplement vous ignorer ?&quot;</em></p>
 <p>SimpleX Chat a été audité par <a href="https://www.trailofbits.com/about">Trail of Bits</a>, 4 problèmes ont été identifiés, et 3 d'entre eux sont corrigés dans la version 4.2.</p>
 <p>Le nouveau site web est en ligne : <a href="https://simplex.chat">https://simplex.chat</a></p>
@@ -43,7 +43,7 @@
 <li>changer manuellement de contact ou de membre vers une autre adresse / serveur (BETA)</li>
 <li>recevoir des fichiers plus rapidement (BETA)</li>
 </ul>
-<p>28 sept. 2022 <a href="20220928-simplex-chat-v4-encrypted-database.html">v4 : chiffrement de la base de données locale</a></p>
+<p>28 sept. 2022 <a href="/blog/20220928-simplex-chat-v4-encrypted-database.html">v4 : chiffrement de la base de données locale</a></p>
 <ul>
 <li>base de données locale de chat chiffrée - si vous utilisez déjà l'application, vous pouvez chiffrer la base de données dans les paramètres de l'application.</li>
 <li>support pour les serveurs WebRTC ICE auto-hébergés</li>
@@ -53,7 +53,7 @@
 <li>support des images animées dans l'application Android</li>
 <li>Interface utilisateur en allemand pour les applications mobiles</li>
 </ul>
-<p>1 sept. 2022 <a href="20220901-simplex-chat-v3.2-incognito-mode.html">v3.2 : Mode Incognito</a></p>
+<p>1 sept. 2022 <a href="/blog/20220901-simplex-chat-v3.2-incognito-mode.html">v3.2 : Mode Incognito</a></p>
 <ul>
 <li>Mode Incognito - utiliser un nouveau nom de profil aléatoire pour chaque contact</li>
 <li>utiliser des adresses de serveur .onion avec Tor</li>
@@ -62,7 +62,7 @@
 <li>réduction de la taille des APK pour le téléchargement direct et dans le repo F-Droid de 200 à 46Mb !</li>
 </ul>
 <p>L'audit d'implémentation est prévu pour Octobre !</p>
-<p>8 août 2022 <a href="20220808-simplex-chat-v3.1-chat-groups.html">v3.1 : groupes de discussion</a></p>
+<p>8 août 2022 <a href="/blog/20220808-simplex-chat-v3.1-chat-groups.html">v3.1 : groupes de discussion</a></p>
 <ul>
 <li>enfin, des groupes de chat secrets - personne d'autre que les membres ne sait qu'ils existent !</li>
 <li>accès aux serveurs de messagerie via Tor sur toutes les plateformes</li>
@@ -70,27 +70,27 @@
 <li>protocole de chat publié</li>
 <li>nouvelles icônes d'application</li>
 </ul>
-<p>23 juil. 2022 <a href="20220723-simplex-chat-v3.1-tor-groups-efficiency.html">v3.1-beta : accès aux serveurs via Tor</a></p>
+<p>23 juil. 2022 <a href="/blog/20220723-simplex-chat-v3.1-tor-groups-efficiency.html">v3.1-beta : accès aux serveurs via Tor</a></p>
 <ul>
 <li>application terminale : accès aux serveurs de messagerie via un proxy SOCKS5 (par exemple, Tor).</li>
 <li>applications mobiles : rejoindre et quitter des groupes de discussion.</li>
 <li>utilisation optimisée de la batterie et du trafic - réduction jusqu'à 90x !</li>
 <li>deux configurations docker pour les serveurs SMP auto-hébergés.</li>
 </ul>
-<p>11 juil. 2022 <a href="20220711-simplex-chat-v3-released-ios-notifications-audio-video-calls-database-export-import-protocol-improvements.html">v3 : notifications push instantanées pour iOS et appels audio/vidéo</a> :</p>
+<p>11 juil. 2022 <a href="/blog/20220711-simplex-chat-v3-released-ios-notifications-audio-video-calls-database-export-import-protocol-improvements.html">v3 : notifications push instantanées pour iOS et appels audio/vidéo</a> :</p>
 <ul>
 <li>exportation et importation de la base de données de chat</li>
 <li>appels audio/vidéo chiffrés de bout en bout</li>
 <li>amélioration de la confidentialité du protocole et des performances</li>
 </ul>
-<p>4 juin 2022 <a href="20220604-simplex-chat-new-privacy-security-settings.html">v2.2 : nouveaux paramètres de confidentialité et de sécurité</a></p>
-<p>24 mai 2022 <a href="20220524-simplex-chat-better-privacy.html">v2.1 : effacement des messages pour une meilleure confidentialité des conversations</a></p>
-<p>11 mai 2022 <a href="20220511-simplex-chat-v2-images-files.html">Publication de la v2.0 - envoi d'images et de fichiers dans les applications mobiles</a></p>
-<p>04 avr. 2022 <a href="20220404-simplex-chat-instant-notifications.html">Notifications instantanées pour les applications mobiles SimpleX Chat</a></p>
-<p>08 mars 2022 <a href="20220308-simplex-chat-mobile-apps.html">Applications mobiles pour iOS et Android</a></p>
-<p>14 févr. 2022. <a href="20220214-simplex-chat-ios-public-beta.html">SimpleX Chat : rejoignez notre version bêta publique pour iOS</a></p>
-<p>12 janv. 2022. <a href="20220112-simplex-chat-v1-released.html">SimpleX Chat v1 : la plateforme de chat et d'application la plus privée et la plus sécurisée</a></p>
-<p>08 déc. 2021. <a href="20211208-simplex-chat-v0.5-released.html">Sortie de SimpleX Chat v0.5 : la première plateforme de chat 100% privée par définition - aucun accès à votre graphe de connexions</a></p>
-<p>14 septembre 2021. <a href="20210914-simplex-chat-v0.4-released.html">SimpleX Chat v0.4 publié : chat open-source qui utilise un protocole de routage de messages préservant la confidentialité</a></p>
-<p>12 mai 2021. <a href="20210512-simplex-chat-terminal-ui.html">Prototype de chat SimpleX</a></p>
-<p>22 oct. 2020. <a href="20201022-simplex-chat.html">SimpleX Chat</a></p>
+<p>4 juin 2022 <a href="/blog/20220604-simplex-chat-new-privacy-security-settings.html">v2.2 : nouveaux paramètres de confidentialité et de sécurité</a></p>
+<p>24 mai 2022 <a href="/blog/20220524-simplex-chat-better-privacy.html">v2.1 : effacement des messages pour une meilleure confidentialité des conversations</a></p>
+<p>11 mai 2022 <a href="/blog/20220511-simplex-chat-v2-images-files.html">Publication de la v2.0 - envoi d'images et de fichiers dans les applications mobiles</a></p>
+<p>04 avr. 2022 <a href="/blog/20220404-simplex-chat-instant-notifications.html">Notifications instantanées pour les applications mobiles SimpleX Chat</a></p>
+<p>08 mars 2022 <a href="/blog/20220308-simplex-chat-mobile-apps.html">Applications mobiles pour iOS et Android</a></p>
+<p>14 févr. 2022. <a href="/blog/20220214-simplex-chat-ios-public-beta.html">SimpleX Chat : rejoignez notre version bêta publique pour iOS</a></p>
+<p>12 janv. 2022. <a href="/blog/20220112-simplex-chat-v1-released.html">SimpleX Chat v1 : la plateforme de chat et d'application la plus privée et la plus sécurisée</a></p>
+<p>08 déc. 2021. <a href="/blog/20211208-simplex-chat-v0.5-released.html">Sortie de SimpleX Chat v0.5 : la première plateforme de chat 100% privée par définition - aucun accès à votre graphe de connexions</a></p>
+<p>14 septembre 2021. <a href="/blog/20210914-simplex-chat-v0.4-released.html">SimpleX Chat v0.4 publié : chat open-source qui utilise un protocole de routage de messages préservant la confidentialité</a></p>
+<p>12 mai 2021. <a href="/blog/20210512-simplex-chat-terminal-ui.html">Prototype de chat SimpleX</a></p>
+<p>22 oct. 2020. <a href="/blog/20201022-simplex-chat.html">SimpleX Chat</a></p>
@@ -940,7 +940,7 @@ git checkout stable
 DOCKER_BUILDKIT=1 docker build --output ~/.local/bin .
 </code></pre>
 <blockquote>
-<p><strong>Please note:</strong> If you encounter <code>version `GLIBC_2.28' not found</code> error, rebuild it with <code>haskell:8.10.7-stretch</code> base image (change it in your local <a href="Dockerfile">Dockerfile</a>).</p>
+<p><strong>Please note:</strong> If you encounter <code>version `GLIBC_2.28' not found</code> error, rebuild it with <code>haskell:8.10.7-stretch</code> base image (change it in your local <a href="https%3A//github.com/simplex-chat/simplex-chat/blob/stable/simplex-chat/Dockerfile">Dockerfile</a>).</p>
 </blockquote>
 <h4 id="in-any-os" tabindex="-1">In any OS</h4>
 <ol>
@@ -1015,20 +1015,20 @@ brew services start tor
 <p>Use <code>/help</code> in chat to see the list of available commands.</p>
 <h3 id="groups" tabindex="-1">Groups</h3>
 <p>To create a group use <code>/g &lt;group&gt;</code>, then add contacts to it with <code>/a &lt;group&gt; &lt;name&gt;</code>. You can then send messages to the group by entering <code>#&lt;group&gt; &lt;message&gt;</code>. Use <code>/help groups</code> for other commands.</p>
-<p><img src="../images/groups.gif" alt="simplex-chat"></p>
+<p><img src="images/groups.gif" alt="simplex-chat"></p>
 <blockquote>
 <p><strong>Please note</strong>: the groups are not stored on any server, they are maintained as a list of members in the app database to whom the messages will be sent.</p>
 </blockquote>
 <h3 id="sending-files" tabindex="-1">Sending files</h3>
 <p>You can send a file to your contact with <code>/f @&lt;contact&gt; &lt;file_path&gt;</code> - the recipient will have to accept it before it is sent. Use <code>/help files</code> for other commands.</p>
-<p><img src="../images/files.gif" alt="simplex-chat"></p>
+<p><img src="images/files.gif" alt="simplex-chat"></p>
 <p>You can send files to a group with <code>/f #&lt;group&gt; &lt;file_path&gt;</code>.</p>
 <h3 id="user-contact-addresses" tabindex="-1">User contact addresses</h3>
 <p>As an alternative to one-time invitation links, you can create a long-term address with <code>/ad</code> (for <code>/address</code>). The created address can then be shared via any channel, and used by other users as a link to make a contact request with <code>/c &lt;user_contact_address&gt;</code>.</p>
 <p>You can accept or reject incoming requests with <code>/ac &lt;name&gt;</code> and <code>/rc &lt;name&gt;</code> commands.</p>
 <p>User address is &quot;long-term&quot; in a sense that it is a multiple-use connection link - it can be used until it is deleted by the user, in which case all established connections would still remain active (unlike how it works with email, when changing the address results in people not being able to message you).</p>
 <p>Use <code>/help address</code> for other commands.</p>
-<p><img src="../images/user-addresses.gif" alt="simplex-chat"></p>
+<p><img src="images/user-addresses.gif" alt="simplex-chat"></p>
 </div>
                </article>
            </main>
@@ -739,7 +739,7 @@ window.addEventListener('scroll',changeHeaderBg);
 <p>You can use an experimental directory service to discover the groups created and registered by other users.</p>
 <h2 id="searching-for-groups" tabindex="-1">Searching for groups</h2>
 <p>Connect to the directory service via <a href="https://simplex.chat/contact#/?v=1-4&amp;smp=smp%3A%2F%2Fu2dS9sG8nMNURyZwqASV4yROM28Er0luVTx5X1CsMrU%3D%40smp4.simplex.im%2FeXSPwqTkKyDO3px4fLf1wx3MvPdjdLW3%23%2F%3Fv%3D1-2%26dh%3DMCowBQYDK2VuAyEAaiv6MkMH44L2TcYrt_CsX3ZvM11WgbMEUn0hkIKTOho%253D%26srv%3Do5vmywmrnaxalvz6wi3zicyftgio6psuvyniis6gco6bp6ekl4cqj4id.onion">this address</a> and send the message containing the words you want to find in the group name or welcome message. You will receive up to 10 groups with the largest number of members in the response, together with the links to join these groups.</p>
-<p>Please note that your search queries can be kept by the bot as the conversation history, but you can use incognito mode when connecting to the bot, to avoid correlation with any other communications. See <a href="/privacy">Privacy policy</a> for more details.</p>
+<p>Please note that your search queries can be kept by the bot as the conversation history, but you can use incognito mode when connecting to the bot, to avoid correlation with any other communications. See <a href="https%3A//github.com/simplex-chat/simplex-chat/blob/stable/simplex-chat/PRIVACY.md">Privacy policy</a> for more details.</p>
 <h2 id="adding-groups-to-the-directory" tabindex="-1">Adding groups to the directory</h2>
 <h3 id="how-to-add-a-group" tabindex="-1">How to add a group</h3>
 <p>To add a group you must be its owner. Once you connect to the directory service and send <code>/help</code>, the service will guide you through the process.</p>
@@ -822,7 +822,7 @@ window.addEventListener('scroll',changeHeaderBg);
 <p>In the context of SimpleX network, these are the identifiers generated by SMP relays to access anonymous messaging queues, with a separate identifier (and access credential) for each accessing party: recipient, sender and and optional notifications subscriber. The same approach is used by XFTP relays to access file chunks, with separate identifiers (and access credentials) for sender and each recipient.</p>
 <h2 id="peer-to-peer" tabindex="-1">Peer-to-peer</h2>
 <p>Peer-to-peer (P2P) is the network architecture when participants have equal rights and communicate directly via a general purpose transport or overlay network. Unlike client-server architecture, all peers in a P2P network both provide and consume the resources. In the context of messaging, P2P architecture usually means that the messages are sent between peers, without user accounts or messages being stored on any servers. Examples are Tox, Briar, Cwtch and many others.</p>
-<p>The advantage is that the participants do not depend on any servers. There are <a href="simplex.html#comparison-with-p2p9-messaging-protocols">multiple downsides</a> to that architecture, such as no asynchronous message delivery, the need for network-wide peer addresses, possibility of network-wide attacks, that are usually mitigated only by using a centralized authority. These disadvantages are avoided with <a href="#proxied-peer-to-peer">proxied P2P</a> architecture.</p>
+<p>The advantage is that the participants do not depend on any servers. There are <a href="/docs/simplex.html#comparison-with-p2p9-messaging-protocols">multiple downsides</a> to that architecture, such as no asynchronous message delivery, the need for network-wide peer addresses, possibility of network-wide attacks, that are usually mitigated only by using a centralized authority. These disadvantages are avoided with <a href="#proxied-peer-to-peer">proxied P2P</a> architecture.</p>
 <p><a href="https://en.wikipedia.org/wiki/Peer-to-peer">Wikipedia</a>.</p>
 <h2 id="perfect-forward-secrecy" tabindex="-1">Perfect forward secrecy</h2>
 <p><a href="#forward-secrecy">Forward secrecy</a>.</p>
@@ -747,10 +747,10 @@ window.addEventListener('scroll',changeHeaderBg);
 <p>This section is labelled <strong>&quot;You&quot;</strong> in the app settings.</p>
 <h3 id="your-active-profile" tabindex="-1">Your active profile</h3>
 <p>Tap on your avatar/name to update your current profile names and avatar.</p>
-<p>Display name cannot have any spaces and it is recommended to use latin characters and numbers to make it easier to type these names to the users who use <a href="cli.html">SimpleX Chat for the terminal</a> (CLI).</p>
+<p>Display name cannot have any spaces and it is recommended to use latin characters and numbers to make it easier to type these names to the users who use <a href="/docs/cli.html">SimpleX Chat for the terminal</a> (CLI).</p>
 <p><strong>Please note</strong>: When you save your profile, the update will be sent to all your contacts (excluding the contacts with whom your incognito profiles were shared). If you have a large number of contacts it can take several seconds.</p>
 <h3 id="your-chat-profiles" tabindex="-1">Your chat profiles</h3>
-<p>This page allows adding and configuring your chat profiles. Please see <a href="chat-profiles.html">Your chat profiles</a> for more details.</p>
+<p>This page allows adding and configuring your chat profiles. Please see <a href="/docs/guide/chat-profiles.html">Your chat profiles</a> for more details.</p>
 <h3 id="incognito" tabindex="-1">Incognito</h3>
 <p>This feature is unique to SimpleX Chat – it is independent from chat profiles.</p>
 <p>When &quot;Incognito” is turned on, your current profile name and image are NOT shared with your new contacts. It allows connections with other people without any shared data – when you make new connections or join groups via a link a new random profile name will be generated for each contact or group.</p>
@@ -760,7 +760,7 @@ window.addEventListener('scroll',changeHeaderBg);
 <p>This page allows you to create a long term address that can be used by other people to connect with you. Unlike 1-time invitation links, these addresses can be used many times, that makes them good to share online, e.g. on other social media platforms.</p>
 <p>When people connect to you via this address, you will receive a connection request that you can accept or reject. You can configure an automatic acceptance of connection request and an automatic welcome message that will be sent to the new contacts.</p>
 <p>If you start receiving too many requests via this address it is always safe to remove it – all the connections you created via this address will remain active, as this address is not used to deliver the messages.</p>
-<p>See the comparison with <a href="making-connections.html#comparison-of-1-time-invitation-links-and-simplex-contact-addresses">1-time invitation links</a>.</p>
+<p>See the comparison with <a href="/docs/guide/making-connections.html#comparison-of-1-time-invitation-links-and-simplex-contact-addresses">1-time invitation links</a>.</p>
 <p>Read more in <a href="/blog/20221108-simplex-chat-v4.2-security-audit-new-website.html#auto-accept-contact-requests">this post</a>.</p>
 <h3 id="chat-preferences" tabindex="-1">Chat preferences</h3>
 <p>This page allows to configure the chat preferences that would apply to all contacts - they can be changed separately for each contact:</p>
@@ -858,7 +858,7 @@ window.addEventListener('scroll',changeHeaderBg);
 </ul>
 <h3 id="database-passphrase-and-export" tabindex="-1">Database passphrase &amp; export</h3>
 <p>This page allows to change the database passphrase, export and import the database and configure the message retention period.</p>
-<p>Read more in <a href="managing-data.html">Managing Your Data</a> page.</p>
+<p>Read more in <a href="/docs/guide/managing-data.html">Managing Your Data</a> page.</p>
 <h2 id="help-and-feedback" tabindex="-1">Help &amp; feedback</h2>
 <p>This section has information on how to use the app and the links to connect to the team. Please use <a href="https://simplex.chat/contact#/?v=1&amp;smp=smp%3A%2F%2FPQUV2eL0t7OStZOoAsPEV2QYWt4-xilbakvGUGOItUo%3D%40smp6.simplex.im%2FK1rslx-m5bpXVIdMZg9NLUZ_8JBm8xTt%23%2F%3Fv%3D1%26dh%3DMCowBQYDK2VuAyEALDeVe-sG8mRY22LsXlPgiwTNs9dbiLrNuA7f3ZMAJ2w%253D%26srv%3Dbylepyau3ty4czmn77q4fglvperknl4bi2eb2fdy2bh4jxtf32kf73yd.onion">Send questions and ideas</a> to connect to us via the chat to ask any questions, make any suggestions and report any issues.</p>
 <h2 id="support-simplex-chat" tabindex="-1">Support SimpleX Chat</h2>
@@ -741,7 +741,7 @@ window.addEventListener('scroll',changeHeaderBg);
 <img src="../../blog/images/20230204-profiles2.png" width="288">
 <p>To create an additional SimpleX Chat profile:</p>
 <ul>
-<li><a href="app-settings.html#opening-the-app-settings">Open the app settings</a>.</li>
+<li><a href="/docs/guide/app-settings.html#opening-the-app-settings">Open the app settings</a>.</li>
 <li>Select &quot;Your chat profiles&quot;.</li>
 <li>Unlock option via fingerprint or PIN.</li>
 <li>Tap on &quot;+ Add profile”.</li>
@@ -766,14 +766,14 @@ window.addEventListener('scroll',changeHeaderBg);
 <p>When &quot;Incognito Mode” is turned on, your currently chosen profile name and image are hidden from your new contacts. It allows anonymous connections with other people without any shared data – when you make new connections or join groups via a link a new random profile name will be generated for each connection.</p>
 <p>To toggle the incognito mode on/off:</p>
 <ul>
-<li><a href="app-settings.html#opening-the-app-settings">Open the app settings</a>.</li>
+<li><a href="/docs/guide/app-settings.html#opening-the-app-settings">Open the app settings</a>.</li>
 <li>Turn on/off incognito mode by tapping on the switch on &quot;Incognito&quot;.</li>
 </ul>
 <p>Please read more in <a href="/blog/20220901-simplex-chat-v3.2-incognito-mode.html#incognito-mode">this post</a>.</p>
 <h2 id="edit-your-profile" tabindex="-1">Edit your profile</h2>
 <p>To edit your profile:</p>
 <ul>
-<li><a href="app-settings.html#opening-the-app-settings">Open the app settings</a>.</li>
+<li><a href="/docs/guide/app-settings.html#opening-the-app-settings">Open the app settings</a>.</li>
 <li>Select your profile.</li>
 <li>Tap on &quot;Edit&quot;.</li>
 <li>Input your desired profile name and/or update your full name.</li>
@@ -784,11 +784,11 @@ window.addEventListener('scroll',changeHeaderBg);
 <p>SimpleX Chat stores all user data only on client devices using a portable encrypted database format that can be exported and transferred to any supported device.</p>
 <p>To export your SimpleX Chat data:</p>
 <ul>
-<li><a href="app-settings.html#opening-the-app-settings">Open the app settings</a>.</li>
+<li><a href="/docs/guide/app-settings.html#opening-the-app-settings">Open the app settings</a>.</li>
 <li>Select &quot;Database passphrase &amp; export&quot;.</li>
 <li>Stop chat by toggling &quot;Chat is running&quot; (tap &quot;Stop” in the confirmation dialog).</li>
-<li>Confirm it with fingerprint or PIN, in case you have <a href="app-settings.html#simplex-lock">SimpleX Lock</a> enabled.</li>
-<li>If you didn't set it before, <a href="managing-data.html#database-passphrase">set a passphrase</a> in &quot;Database passphrase&quot;. Initially, the database is encrypted with a random passphrase that is stored in KeyChain (iOS) or with KeyStore (Android).</li>
+<li>Confirm it with fingerprint or PIN, in case you have <a href="/docs/guide/app-settings.html#simplex-lock">SimpleX Lock</a> enabled.</li>
+<li>If you didn't set it before, <a href="/docs/guide/managing-data.html#database-passphrase">set a passphrase</a> in &quot;Database passphrase&quot;. Initially, the database is encrypted with a random passphrase that is stored in KeyChain (iOS) or with KeyStore (Android).</li>
 <li>Tap on &quot;Export database&quot; - it won't allow exporting unless you have set a passphrase.</li>
 <li>Save the file on your device or share it via any available option.</li>
 </ul>
@@ -742,7 +742,7 @@ window.addEventListener('scroll',changeHeaderBg);
 <p>Private Connection — connect using an invitation link or QR code via video or in-person.</p>
 <p>Group Chat — Users have the option to create a secret group, share their contact link [which can be deleted later on], or generate a one-time invitation link.</p>
 <h2 id="your-simplex-contact-address" tabindex="-1">Your SimpleX contact address</h2>
-<p>You can <a href="app-settings.html#your-simplex-contact-address">create an optional long term address</a> for other people to connect with you. Unlike 1-time invitation links, these addresses can be used many times, that makes them good to share online, e.g. on social media platforms, or in email signatures. That helps more people discover SimpleX Chat, so please do it!</p>
+<p>You can <a href="/docs/guide/app-settings.html#your-simplex-contact-address">create an optional long term address</a> for other people to connect with you. Unlike 1-time invitation links, these addresses can be used many times, that makes them good to share online, e.g. on social media platforms, or in email signatures. That helps more people discover SimpleX Chat, so please do it!</p>
 <p>When people connect to you via this address, you will receive a connection request that you can accept or reject. You can configure an automatic acceptance of connection request and an automatic welcome message that will be sent to the new contacts. You can also share this address as part of your SimpleX profile, so group members can connect to you, and your contacts can share it with others - if this is something that you want.</p>
 <p>If you start receiving too many requests via this address it is always safe to remove it – all the connections you created via this address will remain active, as this address is not used to deliver the messages.</p>
 <h3 id="comparison-of-1-time-invitation-links-and-simplex-contact-addresses" tabindex="-1">Comparison of 1-time invitation links and SimpleX Contact addresses</h3>
@@ -742,7 +742,7 @@ window.addEventListener('scroll',changeHeaderBg);
 <h2 id="chat-database" tabindex="-1">Chat Database</h2>
 <p>To open your chat database settings:</p>
 <ul>
-<li><a href="app-settings.html#opening-the-app-settings">Open the app settings</a>.</li>
+<li><a href="/docs/guide/app-settings.html#opening-the-app-settings">Open the app settings</a>.</li>
 <li>Tap on &quot;Database passphrase &amp; export&quot; button.</li>
 </ul>
 <h3 id="database-passphrase" tabindex="-1">Database passphrase</h3>
@@ -739,7 +739,7 @@ window.addEventListener('scroll',changeHeaderBg);
 <p>SimpleX Chat default configuration aims to balance privacy, security and convenience. You may want to change the default options.</p>
 <p>This page lists all the features and options that affect privacy and security.</p>
 <h2 id="privacy-and-security-settings" tabindex="-1">Privacy and Security settings</h2>
-<p>These settings are available in the <a href="app-settings.html#privacy-and-security">Privacy &amp; Security settings</a>.</p>
+<p>These settings are available in the <a href="/docs/guide/app-settings.html#privacy-and-security">Privacy &amp; Security settings</a>.</p>
 <h2 id="security-code-verification" tabindex="-1">Security code verification</h2>
 <img src="../../blog/images/20230103-verification.png" width="288">
 <p>While SimpleX Chat always establishes connection via link passed via an independent channel, so it is already more protected than other apps, there are scenarios when the invitation links can be substituted in transit (MITM attack). To protect against such attacks, you should verify the security code with your contacts:</p>
@@ -758,19 +758,19 @@ window.addEventListener('scroll',changeHeaderBg);
 </ul>
 <p>Read more in <a href="/blog/20230103-simplex-chat-v4.4-disappearing-messages.html#connection-security-verification">this post</a></p>
 <h2 id="database-passphrase" tabindex="-1">Database passphrase</h2>
-<p>When installed, the app generates a random passphrase for the chat database and stores it securely in KeyChain (iOS) or using KeyStore (Android, TPM module is used when available). You can set your own passphrase and also remove it from the device, in which case you will need to enter it every time you start the app, and notifications may be limited, in the <a href="managing-data.html#database-passphrase">Database passphrase &amp; export</a> settings.</p>
+<p>When installed, the app generates a random passphrase for the chat database and stores it securely in KeyChain (iOS) or using KeyStore (Android, TPM module is used when available). You can set your own passphrase and also remove it from the device, in which case you will need to enter it every time you start the app, and notifications may be limited, in the <a href="/docs/guide/managing-data.html#database-passphrase">Database passphrase &amp; export</a> settings.</p>
 <h2 id="incognito-mode" tabindex="-1">Incognito mode</h2>
-<p>This feature generates a random profile name for each new contact. Read more in <a href="app-settings.html#incognito">Incognito mode</a>.</p>
+<p>This feature generates a random profile name for each new contact. Read more in <a href="/docs/guide/app-settings.html#incognito">Incognito mode</a>.</p>
 <h2 id="hidden-profiles" tabindex="-1">Hidden profiles</h2>
-<p>This feature allows to hide some of your chat profiles with the password. Read more in <a href="chat-profiles.html#hiding-and-muting-chat-profiles">Hiding and muting chat profiles</a>.</p>
+<p>This feature allows to hide some of your chat profiles with the password. Read more in <a href="/docs/guide/chat-profiles.html#hiding-and-muting-chat-profiles">Hiding and muting chat profiles</a>.</p>
 <h2 id="network-settings" tabindex="-1">Network settings</h2>
-<p><a href="app-settings.html#transport-isolation-beta">Transport isolation (BETA)</a> allows to isolate you traffic with each contact in a different TCP connection (and Tor circuit).</p>
+<p><a href="/docs/guide/app-settings.html#transport-isolation-beta">Transport isolation (BETA)</a> allows to isolate you traffic with each contact in a different TCP connection (and Tor circuit).</p>
 <h2 id="using-tor" tabindex="-1">Using Tor</h2>
 <p><img src="../../blog/images/20220808-tor1.png" width="330">   <img src="../../blog/images/20220808-tor2.png" width="330"></p>
 <p>To connect to SMP relays (messaging servers) via Tor you need to install Orbot app.</p>
-<p>Android: use Orbot app as SOCKS proxy on port 9050 (default) and enable <a href="app-settings.html#use-socks-proxy-android-only">Use SOCKS proxy</a>.</p>
+<p>Android: use Orbot app as SOCKS proxy on port 9050 (default) and enable <a href="/docs/guide/app-settings.html#use-socks-proxy-android-only">Use SOCKS proxy</a>.</p>
 <p>iOS: use Orbot app as VPN provider and enable VPN.</p>
-<p>You can also change which server addresses are used with <a href="app-settings.html#use-onion-hosts">Use .onion hosts option</a>.</p>
+<p>You can also change which server addresses are used with <a href="/docs/guide/app-settings.html#use-onion-hosts">Use .onion hosts option</a>.</p>
 </div>
                </article>
            </main>
@@ -740,13 +740,13 @@ window.addEventListener('scroll',changeHeaderBg);
 <h2 id="contents" tabindex="-1">Contents</h2>
 <ul>
 <li><a href="#quick-start">Quick start</a> - scroll down this page</li>
-<li><a href="send-messages.html">Sending messages</a></li>
-<li><a href="secret-groups.html">Secret groups</a></li>
-<li><a href="chat-profiles.html">Chat profiles</a></li>
-<li><a href="managing-data.html">Managing data</a></li>
-<li><a href="audio-video-calls.html">Audio &amp; video calls</a></li>
-<li><a href="privacy-security.html">Privacy &amp; security</a></li>
-<li><a href="app-settings.html">App settings</a></li>
+<li><a href="/docs/guide/send-messages.html">Sending messages</a></li>
+<li><a href="/docs/guide/secret-groups.html">Secret groups</a></li>
+<li><a href="/docs/guide/chat-profiles.html">Chat profiles</a></li>
+<li><a href="/docs/guide/managing-data.html">Managing data</a></li>
+<li><a href="/docs/guide/audio-video-calls.html">Audio &amp; video calls</a></li>
+<li><a href="/docs/guide/privacy-security.html">Privacy &amp; security</a></li>
+<li><a href="/docs/guide/app-settings.html">App settings</a></li>
 </ul>
 <h2 id="quick-start" tabindex="-1">Quick start</h2>
 <h3 id="create-your-first-chat-profile" tabindex="-1">Create your first chat profile</h3>
@@ -766,11 +766,11 @@ window.addEventListener('scroll',changeHeaderBg);
 <p>When you just start using the app, you can tap &quot;chat with the developers&quot; to ask any questions or just to test the app - feel free to send any test messages.</p>
 <p>This button will disappear once you make the first connection. To connect to the developers later:</p>
 <ul>
-<li><a href="app-settings.html#opening-the-app-settings">Open the app settings</a>.</li>
+<li><a href="/docs/guide/app-settings.html#opening-the-app-settings">Open the app settings</a>.</li>
 <li>Tap on &quot;Send questions and ideas&quot;.</li>
 </ul>
 <h3 id="join-some-user-groups" tabindex="-1">Join some user groups</h3>
-<p>There are links to join several <a href="readme.html#join-user-groups">user groups</a> on our GitHub page - join them to ask any questions and discuss ideas.</p>
+<p>There are links to join several <a href="https%3A//github.com/simplex-chat/simplex-chat/blob/stable/simplex-chat/README.md#join-user-groups">user groups</a> on our GitHub page - join them to ask any questions and discuss ideas.</p>
 <p>You can also find some other user-managed groups via online search.</p>
 <p>To join a group via a link:</p>
 <ul>
@@ -789,10 +789,10 @@ window.addEventListener('scroll',changeHeaderBg);
 <li>They can either scan QR code or paste the link. If they opened the link in the browser, they need to tap &quot;Open in mobile app&quot; button on the page.</li>
 </ul>
 <p>Watch the video on <a href="https://simplex.chat">the website</a> that shows how it works.</p>
-<p>You can also create a <a href="app-settings.html#your-simplex-contact-address">long-term contact address</a>.</p>
+<p>You can also create a <a href="/docs/guide/app-settings.html#your-simplex-contact-address">long-term contact address</a>.</p>
 <h3 id="explore-the-app" tabindex="-1">Explore the app</h3>
 <p>Most app settings are shared for all profiles, but some settings are specific to chat profile.</p>
-<p>Read more in <a href="app-settings.html">App settings</a> page.</p>
+<p>Read more in <a href="/docs/guide/app-settings.html">App settings</a> page.</p>
 <p>Many conversation actions are available via long-press or swipe – try them!</p>
 </div>
                </article>
@@ -908,7 +908,7 @@ git checkout stable
 DOCKER_BUILDKIT=1 docker build --output ~/.local/bin .
 </code></pre>
 <blockquote>
-<p><strong>Upozornění:</strong> Pokud narazíte na chybu <code>verze `GLIBC_2.28' nenalezena</code>, obnovte jej pomocí základního obrazu <code>haskell:8.10.7-stretch</code> (změňte jej ve svém lokálním <a href="Dockerfile">Dockerfile</a>).</p>
+<p><strong>Upozornění:</strong> Pokud narazíte na chybu <code>verze `GLIBC_2.28' nenalezena</code>, obnovte jej pomocí základního obrazu <code>haskell:8.10.7-stretch</code> (změňte jej ve svém lokálním <a href="https%3A//github.com/simplex-chat/simplex-chat/blob/stable/simplex-chat/Dockerfile">Dockerfile</a>).</p>
 </blockquote>
 <h4 id="v-libovolnem-operacnim-systemu" tabindex="-1">V libovolném operačním systému</h4>
 <ol>
@@ -831,7 +831,7 @@ window.addEventListener('scroll',changeHeaderBg);
 <h2 id="prehled" tabindex="-1">Přehled</h2>
 <p>SMP server je relay server používaný k předávání zpráv v síti SimpleX. Aplikace SimpleX Chat mají přednastavené servery (pro mobilní aplikace jsou to smp11, smp12 a <a href="http://smp14.simplex.im">smp14.simplex.im</a>), ale konfiguraci aplikace můžete snadno změnit a používat jiné servery.</p>
 <p>Klienti SimpleX pouze určují, který server bude použit pro příjem zpráv, a to pro každý kontakt (nebo spojení skupiny s členem skupiny) zvlášť, přičemž tyto servery jsou pouze dočasné, protože adresa pro doručování se může změnit.</p>
-<p><em>Upozornění</em>: když změníte servery v konfiguraci aplikace, ovlivní to pouze to, který server bude použit pro nové kontakty, stávající kontakty se na nové servery automaticky nepřesunou, ale můžete je přesunout ručně pomocí tlačítka <a href="blog/20221108-simplex-chat-v4.2-bezpecnostni-audit-novy-website.html#zmeny-dorucovani-adresy-beta">&quot;Změnit adresu příjmu&quot;</a> na stránkách s informacemi o kontaktech/členech - brzy bude automatizováno.</p>
+<p><em>Upozornění</em>: když změníte servery v konfiguraci aplikace, ovlivní to pouze to, který server bude použit pro nové kontakty, stávající kontakty se na nové servery automaticky nepřesunou, ale můžete je přesunout ručně pomocí tlačítka <a href="/blog/20221108-simplex-chat-v4.2-security-audit-new-website.html#change-your-delivery-address-beta">&quot;Změnit adresu příjmu&quot;</a> na stránkách s informacemi o kontaktech/členech - brzy bude automatizováno.</p>
 <h2 id="instalace" tabindex="-1">Instalace</h2>
 <ol start="0">
 <li>
@@ -908,7 +908,7 @@ git checkout stable
 DOCKER_BUILDKIT=1 docker build --output ~/.local/bin .
 </code></pre>
 <blockquote>
-<p><strong>Veuillez noter</strong> : Si vous rencontrez l'erreur <code>version `GLIBC_2.28' non trouvée</code>, reconstruisez-le avec l'image de base <code>haskell:8.10.7-stretch</code>(changez-la dans votre <a href="Dockerfile">Dockerfile</a> local).</p>
+<p><strong>Veuillez noter</strong> : Si vous rencontrez l'erreur <code>version `GLIBC_2.28' non trouvée</code>, reconstruisez-le avec l'image de base <code>haskell:8.10.7-stretch</code>(changez-la dans votre <a href="https%3A//github.com/simplex-chat/simplex-chat/blob/stable/simplex-chat/Dockerfile">Dockerfile</a> local).</p>
 </blockquote>
 <h4 id="utiliser-haskell-stack" tabindex="-1">Utiliser Haskell stack</h4>
 <p>(sur n'importe quel OS)</p>
@@ -907,7 +907,7 @@ git checkout stable
 DOCKER_BUILDKIT=1 docker build --output ~/.local/bin .
 </code></pre>
 <blockquote>
-<p><strong>Uwaga:</strong> Jeśli napotkasz błąd <code>version `GLIBC_2.28' not found</code>, przebuduj go z obrazem bazowym <code>haskell:8.10.7-stretch</code> (zmień go w Twoim lokalnym pliku <a href="Dockerfile">Dockerfile</a>).</p>
+<p><strong>Uwaga:</strong> Jeśli napotkasz błąd <code>version `GLIBC_2.28' not found</code>, przebuduj go z obrazem bazowym <code>haskell:8.10.7-stretch</code> (zmień go w Twoim lokalnym pliku <a href="https%3A//github.com/simplex-chat/simplex-chat/blob/stable/simplex-chat/Dockerfile">Dockerfile</a>).</p>
 </blockquote>
 <h4 id="uzywajac-haskella-na-dowolnym-systemie-operacyjnym" tabindex="-1">Używając Haskella na dowolnym systemie operacyjnym</h4>
 <ol>
@@ -972,7 +972,7 @@ brew services start tor
 <p>Po uruchomieniu czatu zostaniesz poproszony o podanie swojej &quot;nazwy wyświetlanej&quot; oraz opcjonalnej &quot;pełnej nazwy&quot; w celu utworzenia lokalnego profilu czatu. Nazwa wyświetlana jest aliasem, za pomocą którego kontakty mogą się do ciebie odnosić - nie jest ona unikalna i nie służy jako globalna tożsamość. Jeśli kilka kontaktów wybrało tę samą nazwę wyświetlaną, klient czatu dodaje numeryczną końcówkę (sufiks) do ich lokalnej nazwy wyświetlanej.</p>
 <p>Poniższy schemat przedstawia sposób łączenia się z kontaktem i wysyłania do niego wiadomości:</p>
 <div align="center">
-  <img align="center" src="../images/how-to-use-simplex.svg">
+  <img align="center" src="/images/how-to-use-simplex.svg">
 </div>
 <p>Gdy już skonfigurujesz swój profil lokalny, wpisz <code>/c</code> (oznaczające <code>/connect</code>), aby utworzyć nowe połączenie i wygenerować zaproszenie. Wyślij to zaproszenie do swojego kontaktu za pośrednictwem dowolnego innego kanału komunikacji.</p>
 <p>Możesz utworzyć wiele zaproszeń, kilkukrotnie wpisując <code>/connect</code> i wysłać te zaproszenia do kontaktów, z którymi chcesz się połączyć.</p>
@@ -982,20 +982,20 @@ brew services start tor
 <p>Użyj <code>/help</code> na czacie, by uzyskać listę pozostałych dostępnych komend.</p>
 <h3 id="grupy" tabindex="-1">Grupy</h3>
 <p>Aby utworzyć grupę, użyj <code>/g &lt;nazwa_grupy&gt;</code>, a następnie dodaj do niej kontakty za pomocą <code>/a &lt;nazwa_grupy&gt; &lt;nazwa_kontaktu&gt;</code>. Możesz wysyłać wiadomości do grupy wpisując <code>#&lt;nazwa_grupy&gt; &lt;wiadomość&gt;</code>. Użyj <code>/help groups</code>, by uzyskać listę pozostałych dostępnych komend.</p>
-<p><img src="../images/groups.gif" alt="simplex-chat"></p>
+<p><img src="/images/groups.gif" alt="simplex-chat"></p>
 <blockquote>
 <p><strong>Uwaga</strong>: informacje o grupach nie są przechowywane na żadnym serwerze, są one zapisywane jako lista członków w bazie danych aplikacji klientów, do których będą wysyłane wiadomości.</p>
 </blockquote>
 <h3 id="wysylanie-plikow" tabindex="-1">Wysyłanie plików</h3>
 <p>Możesz wysłać plik do kontaktu za pomocą <code>/f @&lt;nazwa_kontaktu&gt; &lt;ścieżka_do_pliku&gt;</code> - odbiorca będzie musiał go zaakceptować przed rozpoczęciem wysyłania. Użyj <code>/help files</code>, by uzyskać listę pozostałych dostępnych komend.</p>
-<p><img src="../images/files.gif" alt="simplex-chat"></p>
+<p><img src="/images/files.gif" alt="simplex-chat"></p>
 <p>Możesz wysyłać pliki do grupy za pomocą <code>/f #&lt;nazwa_grupy&gt; &lt;ścieżka_do_pliku&gt;</code>.</p>
 <h3 id="adresy-kontaktowe-uzytkownikow" tabindex="-1">Adresy kontaktowe użytkowników</h3>
 <p>Alternatywą dla jednorazowych linków zapraszających są adresy długoterminowe. Możesz je utworzyć za pomocą <code>/ad</code> (oznaczające <code>/address</code>). Utworzony adres może być następnie udostępniony za pośrednictwem dowolnego innego kanału komunikacji i użyty przez innych użytkowników jako link do prośby o kontakt używając <code>/c &lt;adres_kontaktowy_użytkownika&gt;</code>.</p>
 <p>Prośby o kontakt możesz przyjąć za pomocą komendy <code>/ac &lt;nazwa&gt;</code> oraz odrzucić za pomocą <code>/rc &lt;nazwa&gt;</code>.</p>
 <p>&quot;Długoterminowy&quot; adres użytkownika jest długoterminowy w tym sensie, że jest to link wielokrotnego użytku - może być używany do momentu usunięcia go przez użytkownika. Po usunięciu wszystkie nawiązane połączenia pozostaną aktywne (w przeciwieństwie do tego, jak działa to w przypadku poczty e-mail, gdy zmiana adresu powoduje, że ludzie nie mogą już wysyłać do siebie wiadomości).</p>
 <p>Użyj <code>/help address</code>, by uzyskać listę pozostałych dostępnych komend.</p>
-<p><img src="../images/user-addresses.gif" alt="simplex-chat"></p>
+<p><img src="/images/user-addresses.gif" alt="simplex-chat"></p>
 </div>
                </article>
            </main>
@@ -831,7 +831,7 @@ window.addEventListener('scroll',changeHeaderBg);
 <h2 id="informacje-ogolne" tabindex="-1">Informacje ogólne</h2>
 <p>Serwer SMP to serwer przekaźnikowy używany do przekazywania wiadomości w sieci SimpleX. Aplikacje SimpleX Chat mają wstępnie ustawione serwery (dla aplikacji mobilnych są to smp11, smp12 i <a href="http://smp14.simplex.im">smp14.simplex.im</a>), ale można łatwo zmienić konfigurację aplikacji, aby korzystać z innych serwerów.</p>
 <p>Klienty SimpleX określają tylko, który serwer jest używany do odbierania wiadomości, oddzielnie dla każdego kontaktu (lub połączenia grupowego z członkiem grupy), a serwery te są tylko tymczasowe, ponieważ adres dostawy może ulec zmianie.</p>
-<p><em>Uwaga</em>: gdy zmienisz serwery w ustawieniach aplikacji, wpłynie to tylko na to, który serwer będzie używany dla nowych kontaktów, istniejące kontakty nie zostaną automatycznie przeniesione na nowe serwery, ale możesz przenieść je ręcznie za pomocą przycisku <a href="blog/20221108-simplex-chat-v4.2-security-audit-new-website.html#change-your-delivery-address-beta">&quot;Zmień adres odbiorczy&quot;</a> na stronie z informacjami kontaktu/członka - wkrótce zostanie to zautomatyzowane.</p>
+<p><em>Uwaga</em>: gdy zmienisz serwery w ustawieniach aplikacji, wpłynie to tylko na to, który serwer będzie używany dla nowych kontaktów, istniejące kontakty nie zostaną automatycznie przeniesione na nowe serwery, ale możesz przenieść je ręcznie za pomocą przycisku <a href="/blog/20221108-simplex-chat-v4.2-security-audit-new-website.html#change-your-delivery-address-beta">&quot;Zmień adres odbiorczy&quot;</a> na stronie z informacjami kontaktu/członka - wkrótce zostanie to zautomatyzowane.</p>
 <h2 id="instalacja" tabindex="-1">Instalacja</h2>
 <ol>
 <li>
@@ -832,7 +832,7 @@ window.addEventListener('scroll',changeHeaderBg);
 <p>Istniejące komunikatory oraz protokoły borykają się ze wszystkimi lub kilkoma podanymi problemami:</p>
 <ul>
 <li>Brak zachowania prywatności profilu i kontaktów użytkownika (zachowanie poufności metadanych).</li>
-<li>Brak ochrony (lub jedynie opcjonalna ochrona) przed atakami MITM przez dostawcę usług przy użyciu szyfrowania <a href="1">end to end</a></li>
+<li>Brak ochrony (lub jedynie opcjonalna ochrona) przed atakami MITM przez dostawcę usług przy użyciu szyfrowania <a href="https://pl.wikipedia.org/wiki/Szyfrowanie_od_ko%C5%84ca_do_ko%C5%84ca">end to end</a></li>
 <li>Niechciane wiadomości (spam i nadużycia).</li>
 <li>Brak własności danych i ich ochrony.</li>
 <li>Dla nietechnicznych użytkowników używanie niescentralizowanych protokołów jest skomplikowane.</li>
@@ -790,7 +790,7 @@ window.addEventListener('scroll',changeHeaderBg);
 </code></pre>
 <p><code>msgId</code> property is a 12 bytes base64url-encoded random message ID that the clients can use to reference the message in the future, e.g. when editing, quoting or deleting it.</p>
 <p><code>event</code> property is the type of the message that defines the semantics of the message and the allowed format of <code>params</code> property.</p>
-<p><code>params</code> property includes message data, depending on <code>event</code>, as defined below and in <a href="./simplex-chat.schema.json">JTD schema</a>.</p>
+<p><code>params</code> property includes message data, depending on <code>event</code>, as defined below and in <a href="simplex-chat.schema.json">JTD schema</a>.</p>
 <h3 id="binary-format-for-sending-files" tabindex="-1">Binary format for sending files</h3>
 <p>SimpleX Chat clients use separate connections to send files using a binary format. File chunk size send in each message MUST NOT be bigger than 15,780 bytes to fit into 16kb (16384 bytes) transport block.</p>
 <p>The syntax of each message used to send files is defined by the following ABNF notation:</p>
@@ -822,7 +822,7 @@ eventWord = 1* ALPHA
 <li><code>x.call.*</code> - messages to invite to WebRTC calls and send signalling messages.</li>
 <li><code>x.ok</code> - message sent during connection handshake.</li>
 </ul>
-<p>JTD schema defining messages for all chat functions is available in <a href="./simplex-chat.schema.json">this file</a> – please refer to this document for all properties of the message <code>params</code>.</p>
+<p>JTD schema defining messages for all chat functions is available in <a href="simplex-chat.schema.json">this file</a> – please refer to this document for all properties of the message <code>params</code>.</p>
 <h2 id="xcontact-sending-connection-request" tabindex="-1">x.contact - sending connection request</h2>
 <p>The message is sent as part of the connection request to the long-term user address. <code>contactReqId</code> property is used to identify a duplicate contact request - the receiving client MAY put repeated request on top of the list in the UI.</p>
 <h2 id="sub-protocol-for-contact-profile" tabindex="-1">Sub-protocol for contact profile</h2>
@@ -835,7 +835,7 @@ eventWord = 1* ALPHA
 <h2 id="sub-protocol-for-content-messages" tabindex="-1">Sub-protocol for content messages</h2>
 <h3 id="xmsgnew-a-new-content-message" tabindex="-1">x.msg.new - a new content message</h3>
 <p>When chat clients receive or send this message, they MUST create a new chat item in the conversation. Top level <code>msgId</code> property is defined to allow referencing this chat item or message in the future, e.g. to delete, update or quote chat item, or to accept file.</p>
-<p>This message uses <code>params</code> property of the message as content message container, without any top level properties for the container. Message container (<code>params</code>) includes message <code>content</code> property, an optional &quot;invitation&quot; to receive file or image attachment in <code>file</code> property (that is interpreted depending on message content type) and optional indication whether this message is forwarded (<code>&quot;forward&quot;: true</code> property of container) or sent in reply to other message (<code>&quot;quote&quot;: {&lt;quoted message&gt;}</code>). See <code>/definition/msgContainer</code> in <a href="./simplex-chat.schema.json">JTD schema</a> for message container format.</p>
+<p>This message uses <code>params</code> property of the message as content message container, without any top level properties for the container. Message container (<code>params</code>) includes message <code>content</code> property, an optional &quot;invitation&quot; to receive file or image attachment in <code>file</code> property (that is interpreted depending on message content type) and optional indication whether this message is forwarded (<code>&quot;forward&quot;: true</code> property of container) or sent in reply to other message (<code>&quot;quote&quot;: {&lt;quoted message&gt;}</code>). See <code>/definition/msgContainer</code> in <a href="simplex-chat.schema.json">JTD schema</a> for message container format.</p>
 <p>Message content can be one of four types:</p>
 <ul>
 <li><code>text</code> - no file attachment is expected for this format, <code>text</code> property MUST be non-empty.</li>
@@ -843,7 +843,7 @@ eventWord = 1* ALPHA
 <li><code>image</code> - attached file is required, <code>text</code> property MAY be empty.</li>
 <li><code>link</code> - no file attachment is expected, <code>text</code> property MUST be non-empty. <code>preview</code> property contains information about link preview.</li>
 </ul>
-<p>See <code>/definition/msgContent</code> in <a href="./simplex-chat.schema.json">JTD schema</a> for message container format.</p>
+<p>See <code>/definition/msgContent</code> in <a href="simplex-chat.schema.json">JTD schema</a> for message container format.</p>
 <h3 id="xmsgupdate-update-of-the-previously-sent-message" tabindex="-1">x.msg.update - update of the previously sent message</h3>
 <p>This message is used to update previously created chat item. Its <code>params</code> property contains <code>msgId</code> of the previously sent message that this one is updating and <code>content</code> with the message content that the clients must use to replace the content of the original chat item.</p>
 <p>If the referenced message does not exist, the clients MUST create a new chat item with the ID of the referenced message. If the referenced message is not a content message, the clients MUST ignore this message.</p>
@@ -862,7 +862,7 @@ eventWord = 1* ALPHA
 <p>Clients are RECOMMENDED to indicate in the UI whether the connection to a group member or contact was made directly or via annother user.</p>
 <p>Each member in the group is identified by a group-wide unique identifier used by all members in the group. This is to allow referencing members in the messages and to allow group message integrity validation.</p>
 <p>The diagram below shows the sequence of messages sent between the users' clients to add the new member to the group.</p>
-<p><img src="./diagrams/group.svg" alt="Adding member to the group"></p>
+<p><img src="diagrams/group.svg" alt="Adding member to the group"></p>
 <h3 id="member-roles" tabindex="-1">Member roles</h3>
 <p>Currently members can have one of three roles - <code>owner</code>, <code>admin</code> and <code>member</code>. The user that created the group is self-assigned owner role, the new members are assigned role by the member who adds them - only <code>owner</code> and <code>admin</code> members can add new members; only <code>owner</code> members can add members with <code>owner</code> role.</p>
 <h3 id="messages-to-manage-groups-and-add-members" tabindex="-1">Messages to manage groups and add members</h3>
@@ -863,7 +863,7 @@ window.addEventListener('scroll',changeHeaderBg);
 <h2 id="overview" tabindex="-1">Overview</h2>
 <p>SMP server is the relay server used to pass messages in SimpleX network. SimpleX Chat apps have preset servers (for mobile apps these are smp11, smp12 and <a href="http://smp14.simplex.im">smp14.simplex.im</a>), but you can easily change app configuration to use other servers.</p>
 <p>SimpleX clients only determine which server is used to receive the messages, separately for each contact (or group connection with a group member), and these servers are only temporary, as the delivery address can change.</p>
-<p><em>Please note</em>: when you change the servers in the app configuration, it only affects which server will be used for the new contacts, the existing contacts will not automatically move to the new servers, but you can move them manually using <a href="blog/20221108-simplex-chat-v4.2-security-audit-new-website.html#change-your-delivery-address-beta">&quot;Change receiving address&quot;</a> button in contact/member information pages – it will be automated soon.</p>
+<p><em>Please note</em>: when you change the servers in the app configuration, it only affects which server will be used for the new contacts, the existing contacts will not automatically move to the new servers, but you can move them manually using <a href="/blog/20221108-simplex-chat-v4.2-security-audit-new-website.html#change-your-delivery-address-beta">&quot;Change receiving address&quot;</a> button in contact/member information pages – it will be automated soon.</p>
 <h2 id="installation" tabindex="-1">Installation</h2>
 <ol>
 <li>
@@ -744,7 +744,7 @@ window.addEventListener('scroll',changeHeaderBg);
 <p>Once you have configured your theme in the app, export it to a file and give it a descriptive name – e.g., <code>example.theme</code></p>
 </li>
 <li>
-<p>Export your app database, and import a <a href="./themes/simplex-chat.sample.zip">sample chat database</a> - the passphrase is <code>passphrase</code>.</p>
+<p>Export your app database, and import a <a href="themes/simplex-chat.sample.zip">sample chat database</a> - the passphrase is <code>passphrase</code>.</p>
 </li>
 <li>
 <p>Make three screenshots - the list of conversations with opened profile picker, conversation and privacy settings.</p>
@@ -758,7 +758,7 @@ window.addEventListener('scroll',changeHeaderBg);
 </ol>
 <h2 id="color-themes" tabindex="-1">Color themes</h2>
 <h3 id="simplex-included-dark-blue-theme" tabindex="-1">SimpleX - included dark blue theme</h3>
-<p>Download <a href="./themes/example.theme">SimpleX theme</a></p>
+<p>Download <a href="themes/example.theme">SimpleX theme</a></p>
 <p><img src="./themes/example-chats.png" width="240">    <img src="./themes/example-conversation.png" width="240">    <img src="./themes/example-settings.png" width="240">   </p>
 </div>
                </article>
@@ -1176,7 +1176,7 @@ allow_local_mode = true
 </li>
 </ul>
 <h3 id="configuring-the-app-to-use-the-server" tabindex="-1">Configuring the app to use the server</h3>
-<p>Please see: <a href="server.html#configuring-the-app-to-use-the-server">SMP Server: Configuring the app to use the server</a>.</p>
+<p>Please see: <a href="/docs/server.html#configuring-the-app-to-use-the-server">SMP Server: Configuring the app to use the server</a>.</p>
 </div>
                </article>
            </main>
@@ -881,20 +881,20 @@ window.addEventListener('scroll',changeHeaderBg);
 </ul>
 <h2 id="how-to-use-it" tabindex="-1">How to use it</h2>
 <h3 id="i-have-nobody-to-chat-with-where-can-i-find-any-groups" tabindex="-1">I have nobody to chat with! Where can I find any groups?</h3>
-<p>Please check our <a href="directory.html">Groups Directory</a> in the first place. You might find some interesting groups and meet even more interesting people.</p>
+<p>Please check our <a href="/docs/directory.html">Groups Directory</a> in the first place. You might find some interesting groups and meet even more interesting people.</p>
 <h3 id="what-is-database-what-can-i-do-with-it" tabindex="-1">What is database? What can I do with it?</h3>
-<p>Database is essential for SimpleX Chat to function properly. In comparison to centralized messaging providers, it is <em>the user</em> who is responsible for taking care of their data. On the other hand, user is sure that <em>nobody but them</em> has access to it. Please read more about it: <a href="guide/managing-data.html">Database</a>.</p>
+<p>Database is essential for SimpleX Chat to function properly. In comparison to centralized messaging providers, it is <em>the user</em> who is responsible for taking care of their data. On the other hand, user is sure that <em>nobody but them</em> has access to it. Please read more about it: <a href="/docs/guide/managing-data.html">Database</a>.</p>
 <h3 id="can-i-send-files-over-simplex" tabindex="-1">Can I send files over SimpleX?</h3>
-<p>Of course! While doing so, you are using a <em>state-of-the-art</em> protocol that greatly reduces metadata leaks. Please read more about it: <a href="blog/20230301-simplex-file-transfer-protocol.html">XFTP Protocol</a>.</p>
+<p>Of course! While doing so, you are using a <em>state-of-the-art</em> protocol that greatly reduces metadata leaks. Please read more about it: <a href="/blog/20230301-simplex-file-transfer-protocol.html">XFTP Protocol</a>.</p>
 <h3 id="whats-incognito-profile" tabindex="-1">What’s incognito profile?</h3>
 <p>This feature is unique to SimpleX Chat – it is independent from chat profiles.</p>
 <p>When &quot;Incognito Mode” is turned on, your currently chosen profile name and image are hidden from your new contacts. It allows anonymous connections with other people without any shared data – when you make new connections or join groups via a link a new random profile name will be generated for each connection.</p>
 <h3 id="how-do-invitations-work" tabindex="-1">How do invitations work?</h3>
 <p>It is quite a complex process, but fortunately all of this happens in the background, so it's simply to use.</p>
 <p>Whenever somebody connects to you via your address, they basically ask your client whether they want to establish connection. After that, you can either agree or disagree.<br>
-If interested, please read more: <a href="guide/making-connections.html">Addresses and invitations</a>.</p>
+If interested, please read more: <a href="/docs/guide/making-connections.html">Addresses and invitations</a>.</p>
 <h3 id="how-to-configure-and-delete-groups" tabindex="-1">How to configure and delete groups?</h3>
-<p>Please check: <a href="guide/secret-groups.html">Users guide</a>.</p>
+<p>Please check: <a href="/docs/guide/secret-groups.html">Users guide</a>.</p>
 <h3 id="are-there-any-reactions-to-messages-can-i-answer-specific-messages-directly" tabindex="-1">Are there any reactions to messages? Can I answer specific messages directly?</h3>
 <p>Yes! Currently, there are six emojis available. What's more, you can respond to specific message by holding it and selecting <em>Reply</em>.</p>
 <h3 id="what-do-checkmarks-mean" tabindex="-1">What do checkmarks mean?</h3>
@@ -906,7 +906,7 @@ If interested, please read more: <a href="guide/making-connections.html">Address
 </ul>
 <p>Also see <a href="#i-do-not-see-the-second-tick-on-the-messages-i-sent"> </a></p>
 <h3 id="can-i-use-the-same-profile-on-desktop-do-messages-sync-cross-platform" tabindex="-1">Can I use the same profile on desktop? Do messages sync cross-platform?</h3>
-<p>You can use your profile from mobile device on desktop. However, to do so you need to be on the same network, both on your mobile and desktop. More about it: <a href="blog/20231125-simplex-chat-v5-4-link-mobile-desktop-quantum-resistant-better-groups.html#link-mobile-and-desktop-apps-via-secure-quantum-resistant-protocol">Release info</a>.</p>
+<p>You can use your profile from mobile device on desktop. However, to do so you need to be on the same network, both on your mobile and desktop. More about it: <a href="/blog/20231125-simplex-chat-v5-4-link-mobile-desktop-quantum-resistant-better-groups.html#link-mobile-and-desktop-apps-via-secure-quantum-resistant-protocol">Release info</a>.</p>
 <h2 id="troubleshooting" tabindex="-1">Troubleshooting</h2>
 <h3 id="i-do-not-receive-messages-or-message-notifications" tabindex="-1">I do not receive messages or message notifications</h3>
 <p>There may be several reasons messages are not delivered to you from your contact:</p>
@@ -946,7 +946,7 @@ If interested, please read more: <a href="guide/making-connections.html">Address
 <p>Please check your network settings and make sure you use the latest version of the app.</p>
 <p>Please report such issues if you use v5.7 or newer.</p>
 <h3 id="audio-or-video-calls-do-not-connect" tabindex="-1">Audio or video calls do not connect</h3>
-<p>App uses WebRTC for calls. Please check that you can connect to the servers configured in the app: <a href="http://stun.simplex.im">stun.simplex.im</a> and <a href="http://turn.simplex.im">turn.simplex.im</a> - see <a href="webrtc.html#troubleshoot">troubleshooting WebRTC</a>.</p>
+<p>App uses WebRTC for calls. Please check that you can connect to the servers configured in the app: <a href="http://stun.simplex.im">stun.simplex.im</a> and <a href="http://turn.simplex.im">turn.simplex.im</a> - see <a href="/docs/webrtc.html#troubleshoot">troubleshooting WebRTC</a>.</p>
 <p>If you can connect to the server, please report this issue to us privately, including the following information:</p>
 <ul>
 <li>
@@ -981,22 +981,22 @@ If interested, please read more: <a href="guide/making-connections.html">Address
 <p>Once the connection is established you don't need to be online at the same time to send messages.</p>
 <h2 id="privacy-and-security" tabindex="-1">Privacy and security</h2>
 <h3 id="does-simplex-support-post-quantum-cryptography" tabindex="-1">Does SimpleX support post quantum cryptography?</h3>
-<p>Yes! Please read more about quantum resistant encryption is added to SimpleX Chat and about various properties of end-to-end encryption in <a href="blog/20240314-simplex-chat-v5-6-quantum-resistance-signal-double-ratchet-algorithm.html">this post</a>.</p>
+<p>Yes! Please read more about quantum resistant encryption is added to SimpleX Chat and about various properties of end-to-end encryption in <a href="/blog/20240314-simplex-chat-v5-6-quantum-resistance-signal-double-ratchet-algorithm.html">this post</a>.</p>
 <h3 id="what-user-data-can-be-provided-on-request" tabindex="-1">What user data can be provided on request?</h3>
 <p>Our objective is to consistently ensure that no user data and absolute minimum of the metadata required for the network to function is available for disclosure by any infrastructure operators, under any circumstances.</p>
-<p>Please see our <a href="/privacy">Privacy Policy</a> and <a href="transparency.html">Transparency Reports</a>.</p>
+<p>Please see our <a href="https%3A//github.com/simplex-chat/simplex-chat/blob/stable/simplex-chat/PRIVACY.md">Privacy Policy</a> and <a href="/transparency/index.html">Transparency Reports</a>.</p>
 <h3 id="does-simplex-protect-my-ip-address" tabindex="-1">Does SimpleX protect my IP address?</h3>
 <p>Not fully yet, it is a work in progress. While your device does not connect to your contacts' devices directly, as it happens in p2p networks, your contacts can self-host their relays, and you will connect to them when sending messages. A modified relay can record IP addresses connecting devices, as is the case with any other server, including Tor entry nodes, VPN providers, etc. - IP address is fundamental to Internet functioning, and there will always be some server that can observe your IP address.</p>
 <p>We are currently working on the next version of message routing protocol that will protect your IP address from the relays chosen by your contacts, so it will only be visible to the relays chosen by you. Read about technical details here: <a href="https://github.com/simplex-chat/simplexmq/blob/stable/rfcs/2023-09-12-second-relays.md">RFC</a>.</p>
 <h3 id="can-i-host-my-own-relays" tabindex="-1">Can I host my own relays?</h3>
-<p>Of course! Please check these tutorials: <a href="server.html">SMP server</a> and <a href="xftp-server.html">XFTP server</a>.</p>
+<p>Of course! Please check these tutorials: <a href="/docs/server.html">SMP server</a> and <a href="/docs/xftp-server.html">XFTP server</a>.</p>
 <h2 id="funding-and-business-model" tabindex="-1">Funding and business model</h2>
 <h3 id="how-are-you-funded" tabindex="-1">How are you funded?</h3>
-<p>SimpleX Chat Ltd is funded by private investors and venture capital. As an open-source project, it is also being generously supported by donations as well. Read <a href="blog/20230422-simplex-chat-vision-funding-v5-videos-files-passcode.html#how-is-it-funded-and-what-is-the-business-model">more details</a>.</p>
+<p>SimpleX Chat Ltd is funded by private investors and venture capital. As an open-source project, it is also being generously supported by donations as well. Read <a href="/blog/20230422-simplex-chat-vision-funding-v5-videos-files-passcode.html#how-is-it-funded-and-what-is-the-business-model">more details</a>.</p>
 <h3 id="why-vcs" tabindex="-1">Why VCs?</h3>
 <p>Here are some reflections on VC funding being a necessity for a project at this scale, as well as sustainability and profitability for longtime operations: <a href="https://www.poberezkin.com/posts/2023-10-31-why-privacy-impossible-without-venture-funding.html">https://www.poberezkin.com/posts/2023-10-31-why-privacy-impossible-without-venture-funding.html</a></p>
 <p>And another perspective from a team member on the delicate balance of venture-backed and nonprofit structures, and the plans for the SimpleX network protocols to evolve under the stewardship of nonprofit entities in various jurisdictions, so that its continued evolution aligns more closely with the vision of community-driven, independent and transparent governance:<br>
-<a href="blog/20240404-why-i-joined-simplex-chat-esraa-al-shafei.html">https://simplex.chat/blog/20240404-why-i-joined-simplex-chat-esraa-al-shafei.html</a>.</p>
+<a href="/blog/20240404-why-i-joined-simplex-chat-esraa-al-shafei.html">https://simplex.chat/blog/20240404-why-i-joined-simplex-chat-esraa-al-shafei.html</a>.</p>
 <h3 id="what-will-be-the-business-model" tabindex="-1">What will be the business model?</h3>
 <p>We are focusing on product-market fit, and as such the business model is still a work in progress. However, the app will have a freemium model with extra features or capabilities for paid users (taking into consideration a potential formula like 5% paying $5/month is $3/user/year - ~90% gross profit margin).</p>
 <p>The other income stream would be via business services, for entities needing direct and customized support to integrate with the SimpleX protocol or related resources. There will also be a revenue-sharing model from customers to network operators, to provide an incentive for them to continue running nodes, which will increase decentralization and reliability of the network.</p>
@@ -4,7 +4,7 @@
    <subtitle>It allows you to stay up to date with the latest Blogs from SimpleX Chat.</subtitle>
    <link href="https://simplex.chat/feed.atom" rel="self"/>
    <link href="https://simplex.chat/"/>
-    <updated>2024-04-26T00:00:00Z</updated>
+    <updated>2024-05-16T00:00:00Z</updated>
    <id>https://simplex.chat/</id>
    <author>
        <name>SimpleX Chat</name>
@@ -72,10 +72,10 @@
 &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/images/groups.gif&quot; alt=&quot;simplex-chat&quot; /&gt;&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;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/images/files.gif&quot; alt=&quot;simplex-chat&quot; /&gt;&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;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;
@@ -1523,7 +1523,7 @@ file ---&amp;gt; |   XFTP   | ------&amp;gt;           XFTP            ----&amp;
 &lt;h2 id=&quot;customize-and-share-color-themes&quot; tabindex=&quot;-1&quot;&gt;Customize and share color themes&lt;/h2&gt;
 &lt;img src=&quot;https://simplex.chat/blog/images/20230523-theme.png&quot; width=&quot;288&quot; class=&quot;float-to-left&quot; /&gt;
 &lt;p&gt;Android app now allows choosing between three color themes - Light, Dark and SimpleX (a dark blue theme). You can customize any theme by setting 9 different colors used in the app, including titles, menus, accent colors and colors for sent and received messages.&lt;/p&gt;
-&lt;p&gt;You can share your theme with other users by exporting it to a file and sending to them. You can also &lt;a href=&quot;https://simplex.chat/blog/docs/themes.html&quot;&gt;contribute your favorite themes&lt;/a&gt; to our GitHub repository.&lt;/p&gt;
+&lt;p&gt;You can share your theme with other users by exporting it to a file and sending to them. You can also &lt;a href=&quot;https://simplex.chat/docs/themes.html&quot;&gt;contribute your favorite themes&lt;/a&gt; to our GitHub repository.&lt;/p&gt;
 &lt;h2 id=&quot;self-destruct-passcode&quot; tabindex=&quot;-1&quot;&gt;Self-destruct passcode&lt;/h2&gt;
 &lt;img src=&quot;https://simplex.chat/blog/images/20230523-self-destruct.png&quot; width=&quot;288&quot; class=&quot;float-to-left&quot; /&gt;
 &lt;p&gt;This is something many of you asked before - when asked to enter the app passcode under duress, to be able to enter a special self-destruct code that would remove the app data. This feature is offered in many security tools, and now you can configure it in SimpleX Chat as well.&lt;/p&gt;
@@ -1623,8 +1623,8 @@ file ---&amp;gt; |   XFTP   | ------&amp;gt;           XFTP            ----&amp;
 &lt;p&gt;Please report the cases when messages are not delivered – delivery receipts should help with that.&lt;/p&gt;
 &lt;h4 id=&quot;messages-failed-to-decrypt-problem-solved&quot; tabindex=&quot;-1&quot;&gt;Messages failed to decrypt? Problem solved!&lt;/h4&gt;
 &lt;p&gt;Previously, a growing number of users had the issue when after restoring the chat database from backup, messages from some contacts failed to decrypt and were showing an error in the app.&lt;/p&gt;
-&lt;p&gt;This happens due to double ratchet protocol protecting the integrity of end-to-end encryption after the compromise - &lt;a href=&quot;https://simplex.chat/blog/docs/glossary.html#post-compromise-security&quot;&gt;post-compromise security&lt;/a&gt;. The protocol logic does not allow to use the old version of the database to decrypt the message.&lt;/p&gt;
-&lt;p&gt;v5.2 added the extension to the messaging protocol allowing to negotiate the new ratchet keys in such cases - both with the contacts and the group members. This requires a user action, and it resets the security code verification status for this contact or member – you need to verify it again to have the additional protection from &lt;a href=&quot;https://simplex.chat/blog/docs/glossary.html#man-in-the-middle-attack&quot;&gt;man-in-the-middle attacks&lt;/a&gt;.&lt;/p&gt;
+&lt;p&gt;This happens due to double ratchet protocol protecting the integrity of end-to-end encryption after the compromise - &lt;a href=&quot;https://simplex.chat/docs/glossary.html#post-compromise-security&quot;&gt;post-compromise security&lt;/a&gt;. The protocol logic does not allow to use the old version of the database to decrypt the message.&lt;/p&gt;
+&lt;p&gt;v5.2 added the extension to the messaging protocol allowing to negotiate the new ratchet keys in such cases - both with the contacts and the group members. This requires a user action, and it resets the security code verification status for this contact or member – you need to verify it again to have the additional protection from &lt;a href=&quot;https://simplex.chat/docs/glossary.html#man-in-the-middle-attack&quot;&gt;man-in-the-middle attacks&lt;/a&gt;.&lt;/p&gt;
 &lt;p&gt;The negotiation of the new ratchet keys still happens via the end-to-end encrypted messages, as the protocol has two layers of end-to-end encryption, so it cannot be compromised by the messaging relays.&lt;/p&gt;
 &lt;p&gt;You may still lose connection if you or your contact changed the receiving address after you made the backup, so make sure to make a new backup after any receiving address changes.&lt;/p&gt;
 &lt;h4 id=&quot;reconnect-the-servers&quot; tabindex=&quot;-1&quot;&gt;Reconnect the servers&lt;/h4&gt;
@@ -1644,12 +1644,12 @@ file ---&amp;gt; |   XFTP   | ------&amp;gt;           XFTP            ----&amp;
 &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/docs/rfcs/2023-05-02-groups.html&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://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;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/docs/rfcs/2023-05-22-groups-moderation.html&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://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;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;
@@ -1720,11 +1720,11 @@ file ---&amp;gt; |   XFTP   | ------&amp;gt;           XFTP            ----&amp;
 &lt;li&gt;you cannot send voice messages.&lt;/li&gt;
 &lt;li&gt;there is no support for calls yet.&lt;/li&gt;
 &lt;/ul&gt;
-&lt;p&gt;You can download the desktop app for Linux and Mac via &lt;a href=&quot;https://simplex.chat/downloads&quot;&gt;downloads page&lt;/a&gt;. Windows version will be available soon.&lt;/p&gt;
+&lt;p&gt;You can download the desktop app for Linux and Mac via &lt;a href=&quot;https://simplex.chat/downloads/index.html&quot;&gt;downloads page&lt;/a&gt;. Windows version will be available soon.&lt;/p&gt;
 &lt;h2 id=&quot;group-directory-service-and-other-group-improvements&quot; tabindex=&quot;-1&quot;&gt;Group directory service and other group improvements&lt;/h2&gt;
 &lt;img src=&quot;https://simplex.chat/blog/images/20230925-directory.png&quot; width=&quot;330&quot; class=&quot;float-to-left&quot; /&gt;
 &lt;p&gt;Directory service provides a way to search for public groups submitted by the users. To use it, you need to connect to it via SimpleX Chat, as you would connect to any other contact, and type some words to search.&lt;/p&gt;
-&lt;p&gt;You can also create and register your group, with some limitations explained &lt;a href=&quot;https://simplex.chat/blog/docs/directory.html&quot;&gt;here&lt;/a&gt;.&lt;/p&gt;
+&lt;p&gt;You can also create and register your group, with some limitations explained &lt;a href=&quot;https://simplex.chat/docs/directory.html&quot;&gt;here&lt;/a&gt;.&lt;/p&gt;
 &lt;p&gt;Other group improvements in this release:&lt;/p&gt;
 &lt;ul&gt;
 &lt;li&gt;
@@ -1815,7 +1815,7 @@ file ---&amp;gt; |   XFTP   | ------&amp;gt;           XFTP            ----&amp;
 &lt;p&gt;This is only possible when both devices are connected to the same local network. To send and receive messages mobile app has to be connected to the Internet.&lt;/p&gt;
 &lt;h3 id=&quot;quick-start-how-to-use-it&quot; tabindex=&quot;-1&quot;&gt;⚡️ Quick start - how to use it&lt;/h3&gt;
 &lt;p&gt;&lt;strong&gt;On desktop&lt;/strong&gt;&lt;/p&gt;
-&lt;p&gt;If you don&#39;t have desktop app installed yet, &lt;a href=&quot;https://simplex.chat/downloads/&quot;&gt;download it&lt;/a&gt; and create any chat profile - you don&#39;t need to use it, and when you create it there are no server requests sent and no accounts are created. Think about it as about user profile on your computer.&lt;/p&gt;
+&lt;p&gt;If you don&#39;t have desktop app installed yet, &lt;a href=&quot;https://simplex.chat/downloads/index.html&quot;&gt;download it&lt;/a&gt; and create any chat profile - you don&#39;t need to use it, and when you create it there are no server requests sent and no accounts are created. Think about it as about user profile on your computer.&lt;/p&gt;
 &lt;p&gt;Then in desktop app settings choose &lt;em&gt;Link a mobile&lt;/em&gt; - it will show a QR code.&lt;/p&gt;
 &lt;p&gt;&lt;img src=&quot;https://simplex.chat/blog/images/20231125-desktop1.png&quot; width=&quot;170&quot; /&gt; &lt;img src=&quot;https://simplex.chat/blog/images/arrow.png&quot; width=&quot;24&quot; /&gt; &lt;img src=&quot;https://simplex.chat/blog/images/20231125-desktop2.png&quot; width=&quot;170&quot; /&gt; &lt;img src=&quot;https://simplex.chat/blog/images/arrow.png&quot; width=&quot;24&quot; /&gt; &lt;img src=&quot;https://simplex.chat/blog/images/20231125-desktop3.png&quot; width=&quot;170&quot; /&gt; &lt;img src=&quot;https://simplex.chat/blog/images/arrow.png&quot; width=&quot;24&quot; /&gt; &lt;img src=&quot;https://simplex.chat/blog/images/20231125-desktop4.png&quot; width=&quot;510&quot; /&gt;&lt;/p&gt;
 &lt;p&gt;&lt;strong&gt;On mobile&lt;/strong&gt;&lt;/p&gt;
@@ -1825,7 +1825,7 @@ file ---&amp;gt; |   XFTP   | ------&amp;gt;           XFTP            ----&amp;
 &lt;p&gt;If it is an Android app, you can move the app to background, but iOS app has to remain open. In both cases, while you are using mobile profiles from desktop, you won&#39;t be able to use mobile app.&lt;/p&gt;
 &lt;p&gt;The subsequent connections happen much faster - by default, the desktop app broadcasts its session address to the network, in encrypted form, and mobile app connects to it once you choose &lt;em&gt;Use from desktop&lt;/em&gt; in mobile app settings.&lt;/p&gt;
 &lt;h3 id=&quot;how-does-it-work&quot; tabindex=&quot;-1&quot;&gt;How does it work?&lt;/h3&gt;
-&lt;p&gt;The way we designed this solution avoided any security compromises, and the end-to-end encryption remained as secure as it was - it uses &lt;a href=&quot;https://simplex.chat/blog/docs/glossary.html#double-ratchet-algorithm&quot;&gt;double-ratchet algorithm&lt;/a&gt;, with &lt;a href=&quot;https://simplex.chat/blog/docs/glossary.html#forward-secrecy&quot;&gt;perfect forward secrecy&lt;/a&gt;, &lt;a href=&quot;https://simplex.chat/blog/docs/glossary.html#post-compromise-security&quot;&gt;post-compromise security&lt;/a&gt; and deniability.&lt;/p&gt;
+&lt;p&gt;The way we designed this solution avoided any security compromises, and the end-to-end encryption remained as secure as it was - it uses &lt;a href=&quot;https://simplex.chat/docs/glossary.html#double-ratchet-algorithm&quot;&gt;double-ratchet algorithm&lt;/a&gt;, with &lt;a href=&quot;https://simplex.chat/docs/glossary.html#forward-secrecy&quot;&gt;perfect forward secrecy&lt;/a&gt;, &lt;a href=&quot;https://simplex.chat/docs/glossary.html#post-compromise-security&quot;&gt;post-compromise security&lt;/a&gt; and deniability.&lt;/p&gt;
 &lt;p&gt;This solution is similar to WhatsApp and WeChat. But unlike these apps, no server is involved in the connection between mobile and desktop. The connection itself uses a new SimpleX Remote Control Protocol (XRCP) based on secure TLS 1.3 and additional quantum-resistant encryption inside TLS. You can read XRCP protocol specification and threat model in &lt;a href=&quot;https://github.com/simplex-chat/simplexmq/blob/master/rfcs/2023-10-25-remote-control.md&quot;&gt;this document&lt;/a&gt;. We will soon be &lt;a href=&quot;https://github.com/simplex-chat/simplex-chat/blob/master/docs/rfcs/2023-09-30-pq-double-ratchet.md&quot;&gt;augmenting double ratchet&lt;/a&gt; to be resistant to quantum computers as well.&lt;/p&gt;
 &lt;p&gt;The downside of this approach is that mobile device has to be connected to the same local network as desktop. But the upside is that the connection is secure, and you do not need to have a copy of all your data on desktop, which usually has lower security than mobile.&lt;/p&gt;
 &lt;p&gt;Please note, that the files you send, save or play from desktop app, and also images you view are automatically saved on your desktop device (encrypted by default except videos). To remove all these files you can unlink the paired mobile device from the desktop app settings – there will be an option soon allowing to remove the files without unlinking the mobile.&lt;/p&gt;
@@ -1972,6 +1972,7 @@ file ---&amp;gt; |   XFTP   | ------&amp;gt;           XFTP            ----&amp;
            <updated>14 Mar 2024</updated>
            <id>https://simplex.chat/blog/20240314-simplex-chat-v5-6-quantum-resistance-signal-double-ratchet-algorithm.html</id>
            <content xml:lang="en" type="html">&lt;h1 id=&quot;simplex-chat-v56-beta-adding-quantum-resistance-to-signal-double-ratchet-algorithm&quot; tabindex=&quot;-1&quot;&gt;SimpleX Chat v5.6 beta: adding quantum resistance to Signal double ratchet algorithm&lt;/h1&gt;
+&lt;p&gt;&lt;strong&gt;Published:&lt;/strong&gt; Mar 14, 2024&lt;/p&gt;
 &lt;p&gt;This is a major upgrade for SimpleX messaging protocols, we are really proud to present the results of the hard work of our whole team on the &lt;a href=&quot;https://en.wikipedia.org/wiki/Pi_Day&quot;&gt;Pi day&lt;/a&gt;.&lt;/p&gt;
 &lt;p&gt;This post also covers various aspects of end-to-end encryption, compares different messengers, and explains why and how quantum-resistant encryption is added to SimpleX Chat:&lt;/p&gt;
 &lt;ul&gt;
@@ -2034,7 +2035,7 @@ file ---&amp;gt; |   XFTP   | ------&amp;gt;           XFTP            ----&amp;
 &lt;h3 id=&quot;4-compromised-long-term-or-session-mitigated-by-break-in-recovery&quot; tabindex=&quot;-1&quot;&gt;4. Compromised long-term or session - mitigated by break-in recovery&lt;/h3&gt;
 &lt;p&gt;This attack is much less understood by the users, and forward secrecy does not protect from it. Arguably, it&#39;s almost impossible to compromise individual message keys without compromising long-term or session keys. So the ability of the encryption to recover from break-in (attacker making a copy of the device data without retaining the ongoing access) is both very important and pragmatic - break-in attacks are simpler to execute on mobile devices during short-term device access than long-term ongoing compromise.&lt;/p&gt;
 &lt;p&gt;Out of all encryption algorithms known to us only &lt;em&gt;Signal double ratchet algorithm&lt;/em&gt; (also referred to as &lt;em&gt;Signal algorithm&lt;/em&gt; or &lt;em&gt;double ratchet algorithm&lt;/em&gt;, which is not the same as Signal messaging platform and protocols) provides the ability for the encryption security to recover after break-ins attacks. This recovery happens automatically and transparently to the users, without them doing anything special or even knowing about break-in, by simply sending messages. Every time one of the communication parties replies to another party message, new random keys are generated and previously stolen keys become useless.&lt;/p&gt;
-&lt;p&gt;Double ratchet algorithm is used in Signal, Cwtch and SimpleX Chat. This is why you cannot use SimpleX Chat profile on more than one device at the same time - the encryption scheme rotates the long term keys, randomly, and keys on another device become useless, as they would become useless for the attacker who stole them. Security always has some costs to the convenience.&lt;/p&gt;
+&lt;p&gt;Double ratchet algorithm is used in Signal, Cwtch and SimpleX Chat. But Signal app by allowing to use the same profile on multiple devices compromises the break-in recovery function of Signal algorithm, as explained in &lt;a href=&quot;https://eprint.iacr.org/2021/626.pdf&quot;&gt;this paper&lt;/a&gt;. Because of break-in recovery you cannot use SimpleX Chat profile on more than one device at the same time - the encryption scheme rotates the long term keys, randomly, and keys on another device become useless, as they would become useless for the attacker who stole them. Security always has some costs to the convenience.&lt;/p&gt;
 &lt;h3 id=&quot;5-man-in-the-middle-attack-mitigated-by-two-factor-key-exchange&quot; tabindex=&quot;-1&quot;&gt;5. Man-in-the-middle attack - mitigated by two-factor key exchange&lt;/h3&gt;
 &lt;p&gt;Many people incorrectly believe that security of end-to-end encryption cannot be broken by communication provider. But end-to-end encryption is only as secure as key exchange. While any intermediary passing the keys between senders and recipients cannot recover the private keys from the public keys, they can simply replace the passed public keys with their own and then proxy all communication between the users having full access to the original messages. So instead of having an end-to-end encrypted channel, users would have two half-way encrypted channels - between users and their communication intermediary.&lt;/p&gt;
 &lt;p&gt;Pictures below illustrate how this attack works for RSA encryption.&lt;/p&gt;
@@ -2312,6 +2313,7 @@ file ---&amp;gt; |   XFTP   | ------&amp;gt;           XFTP            ----&amp;
            <updated>26 Apr 2024</updated>
            <id>https://simplex.chat/blog/20240426-simplex-legally-binding-transparency-v5-7-better-user-experience.html</id>
            <content xml:lang="en" type="html">&lt;h1 id=&quot;simplex-network-legally-binding-transparency-v57-released-with-better-calls-and-messages&quot; tabindex=&quot;-1&quot;&gt;SimpleX network: legally binding transparency, v5.7 released with better calls and messages&lt;/h1&gt;
+&lt;p&gt;&lt;strong&gt;Published:&lt;/strong&gt; Apr 26, 2024&lt;/p&gt;
 &lt;p&gt;What&#39;s new in v5.7:&lt;/p&gt;
 &lt;ul&gt;
 &lt;li&gt;&lt;a href=&quot;https://simplex.chat/blog/20240426-simplex-legally-binding-transparency-v5-7-better-user-experience.html#quantum-resistant-end-to-end-encryption&quot;&gt;quantum resistant end-to-end encryption&lt;/a&gt; with all contacts.&lt;/li&gt;
@@ -2324,10 +2326,10 @@ file ---&amp;gt; |   XFTP   | ------&amp;gt;           XFTP            ----&amp;
 &lt;h2 id=&quot;legally-binding-transparency&quot; tabindex=&quot;-1&quot;&gt;Legally binding transparency&lt;/h2&gt;
 &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/&quot;&gt;Transparency Reports&lt;/a&gt; page.&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/&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/&quot;&gt;Security Policy&lt;/a&gt; – we welcome your feedback on it.&lt;/li&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 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;
 &lt;p&gt;What do we mean by “legally binding transparency?”. It includes these principles:&lt;/p&gt;
 &lt;ul&gt;
@@ -2366,7 +2368,7 @@ file ---&amp;gt; |   XFTP   | ------&amp;gt;           XFTP            ----&amp;
 &lt;p&gt;&lt;a href=&quot;https://simplex.chat/blog/20220511-simplex-chat-v2-images-files.html#the-first-messaging-platform-without-user-identifiers&quot;&gt;How can SimpleX deliver messages without user identifiers&lt;/a&gt;.&lt;/p&gt;
 &lt;p&gt;&lt;a href=&quot;https://simplex.chat/blog/20220711-simplex-chat-v3-released-ios-notifications-audio-video-calls-database-export-import-protocol-improvements.html#why-having-users-identifiers-is-bad-for-the-users&quot;&gt;What are the risks to have identifiers assigned to the users&lt;/a&gt;.&lt;/p&gt;
 &lt;p&gt;&lt;a href=&quot;https://github.com/simplex-chat/simplex-chat#privacy-technical-details-and-limitations&quot;&gt;Technical details and limitations&lt;/a&gt;.&lt;/p&gt;
-&lt;p&gt;&lt;a href=&quot;https://simplex.chat/blog/docs/faq.html&quot;&gt;Frequently asked questions&lt;/a&gt;.&lt;/p&gt;
+&lt;p&gt;&lt;a href=&quot;https://simplex.chat/faq/index.html&quot;&gt;Frequently asked questions&lt;/a&gt;.&lt;/p&gt;
 &lt;p&gt;Please also see our &lt;a href=&quot;https://simplex.chat/&quot;&gt;website&lt;/a&gt;.&lt;/p&gt;
 &lt;h2 id=&quot;help-us-with-donations&quot; tabindex=&quot;-1&quot;&gt;Help us with donations&lt;/h2&gt;
 &lt;p&gt;Huge thank you to everybody who donates to SimpleX Chat!&lt;/p&gt;
@@ -2378,6 +2380,50 @@ file ---&amp;gt; |   XFTP   | ------&amp;gt;           XFTP            ----&amp;
 &lt;p&gt;Thank you,&lt;/p&gt;
 &lt;p&gt;Evgeny&lt;/p&gt;
 &lt;p&gt;SimpleX Chat founder&lt;/p&gt;
+</content>
+            
+        </entry>
+        <entry>
+            <title>SimpleX: Redefining Privacy by Making Hard Choices</title>
+            <link href="https://simplex.chat/blog/20240516-simplex-redefining-privacy-hard-choices.html"/>
+            
+            <updated>16 May 2024</updated>
+            <id>https://simplex.chat/blog/20240516-simplex-redefining-privacy-hard-choices.html</id>
+            <content xml:lang="en" type="html">&lt;h1 id=&quot;simplex-redefining-privacy-by-making-hard-choices&quot; tabindex=&quot;-1&quot;&gt;SimpleX: Redefining Privacy by Making Hard Choices&lt;/h1&gt;
+&lt;p&gt;&lt;strong&gt;Published:&lt;/strong&gt; May 16, 2024&lt;/p&gt;
+&lt;p&gt;When it comes to open source privacy tools, the status quo often dictates the limitations of existing protocols and structures. However, these norms need to be challenged to radically shift how we approach genuinely private communication. This requires doing some uncomfortable things, like making hard choices as it relates to funding, alternative decentralization models, doubling down on privacy over convenience, and more.&lt;/p&gt;
+&lt;p&gt;There will always be questions on why the SimpleX Chat and network makes the choices it makes, and that’s good! It’s important to question us and to understand the reasoning behind each decision, whether it’s technical, structural, financial or any other.&lt;/p&gt;
+&lt;p&gt;In this post we explain a bit more about why SimpleX operates and makes decisions the way it does.&lt;/p&gt;
+&lt;h2 id=&quot;no-user-accounts&quot; tabindex=&quot;-1&quot;&gt;No user accounts&lt;/h2&gt;
+&lt;p&gt;Within SimpleX network there are no user accounts, and more importantly, no user profile identifiers whatsoever at the protocol level, not even random numbers or cryptographic keys used to identify the users. This means there is absolutely nothing that uniquely links users to their contacts or to the network relays. While it&#39;s accurate to say, &amp;quot;You need an address to send something,&amp;quot; it&#39;s crucial to understand that this &amp;quot;address&amp;quot; serves merely as a transient delivery destination, and not as a user profile identifier in any sense.&lt;/p&gt;
+&lt;p&gt;You can read more about how SimpleX works &lt;a href=&quot;https://simplex.chat/#how-simplex-works&quot;&gt;here&lt;/a&gt;.&lt;/p&gt;
+&lt;h2 id=&quot;privacy-over-convenience&quot; tabindex=&quot;-1&quot;&gt;Privacy over convenience&lt;/h2&gt;
+&lt;p&gt;One of the main considerations often ignored in security and privacy comparisons between messaging applications is multi-device access. For example, in Signal’s case, the Sesame protocol used to support multi-device access has the vulnerability that is &lt;a href=&quot;https://eprint.iacr.org/2021/626.pdf&quot;&gt;explained in detail here&lt;/a&gt;:&lt;/p&gt;
+&lt;p&gt;&lt;em&gt;&amp;quot;We present an attack on the post-compromise security of the Signal messenger that allows to stealthily register a new device via the Sesame protocol. [...] This new device can send and receive messages without raising any ‘Bad encrypted message’ errors. Our attack thus shows that the Signal messenger does not guarantee post-compromise security at all in the multi-device setting&amp;quot;&lt;/em&gt;.&lt;/p&gt;
+&lt;img src=&quot;https://simplex.chat/blog/images/20231125-mobile2.png&quot; width=&quot;170&quot; class=&quot;float-right&quot; /&gt;
+&lt;p&gt;Solutions are possible, and even the quoted paper proposes improvements, but they are not implemented in any existing communication solutions. Unfortunately this results in most communication systems, even those in the privacy space, having compromised security in multi-device settings due to these limitations. That&#39;s the reason we are not rushing a full multi-device support, and currently only provide &lt;a href=&quot;https://simplex.chat/blog/20231125-simplex-chat-v5-4-link-mobile-desktop-quantum-resistant-better-groups.html#link-mobile-and-desktop-apps-via-secure-quantum-resistant-protocol&quot;&gt;the ability to use mobile app profiles via the desktop app&lt;/a&gt;, while they are on the same network.&lt;/p&gt;
+&lt;p&gt;Another choice that compromises privacy for convenience and usability is 3rd party push notifications. At SimpleX, we take a slow path of optimizing the network and battery consumption in the app, rather than simply hiding inefficiencies behind the quick fix solution of 3rd party push notifications that &lt;a href=&quot;https://www.wired.com/story/apple-google-push-notification-surveillance/&quot;&gt;increases vulnerability&lt;/a&gt;, a path Signal and others chose. Like other choices, it has usability and optimization trade offs, but ultimately it’s the right thing to continue progressing towards a better solution as we explain &lt;a href=&quot;https://simplex.chat/blog/20220404-simplex-chat-instant-notifications.html&quot;&gt;here&lt;/a&gt;.&lt;/p&gt;
+&lt;p&gt;Whenever possible, we strive to achieve significantly higher levels of privacy and security. For example, unlike most, if not all, applications (including Signal), &lt;a href=&quot;https://simplex.chat/blog/20230925-simplex-chat-v5-3-desktop-app-local-file-encryption-directory-service.html#encrypted-local-files-and-media-with-forward-secrecy&quot;&gt;we encrypt application files with per-file unique key&lt;/a&gt;. Consequently, once a message is deleted, there&#39;s no means to open a file that someone may have stolen in hopes of acquiring the key later. Similarly, apps like Session have done away with forward secrecy, a decision which caused them &lt;a href=&quot;https://www.privacyguides.org/en/real-time-communication/#additional-options&quot;&gt;not to be recommended&lt;/a&gt; for &amp;quot;long-term or sensitive communications&amp;quot;. And &lt;a href=&quot;https://simplifiedprivacy.com/spain-has-banned-telegram-defending-session/&quot;&gt;misinformation&lt;/a&gt; around this makes it dangerous and irresponsible to recommend without such necessary disclosures for people’s awareness.&lt;/p&gt;
+&lt;p&gt;Session’s decision was based on &lt;a href=&quot;https://getsession.org/blog/session-protocol-explained&quot;&gt;the incorrect statements&lt;/a&gt; about double ratchet being impossible in decentralized networks, and underplayed importance of forward secrecy, break-in recovery and deniability - the absence of these crucial qualities makes Session a much weaker choice for private messaging. For transparency, this was something that was debated with their team &lt;a href=&quot;https://twitter.com/SimpleXChat/status/1755216356159414602&quot;&gt;here&lt;/a&gt;. We also made &lt;a href=&quot;https://simplex.chat/blog/20240314-simplex-chat-v5-6-quantum-resistance-signal-double-ratchet-algorithm.html#end-to-end-encryption-security-attacks-and-defense&quot;&gt;a separate post&lt;/a&gt; about these qualities of end-to-end encryption and their presence in different messengers, to show that not all end-to-end encrypted apps offer the same level of protections.&lt;/p&gt;
+&lt;h2 id=&quot;network-decentralization&quot; tabindex=&quot;-1&quot;&gt;Network decentralization&lt;/h2&gt;
+&lt;img src=&quot;https://simplex.chat/blog/images/simplex-explained.svg&quot; width=&quot;40%&quot; class=&quot;float-right&quot; /&gt;
+&lt;p&gt;It&#39;s important to recognize that a model of decentralization where all servers are openly known and accessible to all clients, that some users ask for, actually results in a less decentralized network, and as the network grows it often requires an introduction of a central authority to protect from bad actors with malicious intent. Therefore, we&#39;ve deliberately opted for a slower path towards achieving a higher degree of decentralization where there is no central server registry or network authority. For example, p2p designs may offer higher initial decentralization but often compromise on privacy and eventual decentralization. In essence, our approach prioritizes a balance between initial decentralization, privacy, and higher degree of decentralization down the line.&lt;/p&gt;
+&lt;p&gt;Additionally, while it&#39;s true that we haven&#39;t yet established a model to incentivize other network operators, it&#39;s certainly on the roadmap. We see the decentralization of network operators offered within the app as a top priority.&lt;/p&gt;
+&lt;p&gt;Where it stands today, users have the freedom to select their preferred servers within the SimpleX network by configuring the app, with thousands of self-hosted servers in operation. Moreover, numerous third-party applications rely on our code for their in-app communications, operating independently of our servers, many of which we may not even be aware of.&lt;/p&gt;
+&lt;p&gt;Decentralization is an ongoing journey, and we strive to proceed at a measured pace to ensure its proper implementation. While the immediate results may not always appear ideal, prioritizing a careful approach ensures that in the long run, the decisions made in this area align with our ultimate objectives of a private, efficient, reliable and fully decentralized network.&lt;/p&gt;
+&lt;h2 id=&quot;funding-and-profitability&quot; tabindex=&quot;-1&quot;&gt;Funding and profitability&lt;/h2&gt;
+&lt;p&gt;We explain our rationale for funding &lt;a href=&quot;https://simplex.chat/faq/index.html#funding-and-business-model&quot;&gt;here&lt;/a&gt;. Funding sources is always one of the most difficult choices to make, and it’s important to underline that VC models don’t necessarily translate to a quest for control, interference of any kind, or overall influence on product roadmap and strategy. The vast majority of investors seek profitability. Irrespective of the organization type profitability is essential for a sustainable operation, and it can and should be done while adhering to the highest possible standards for privacy. For-profit vs. nonprofit is also not an accurate metric to measure a commitment towards privacy and open standards, which is further explained &lt;a href=&quot;https://simplex.chat/blog/20240404-why-i-joined-simplex-chat-esraa-al-shafei.html&quot;&gt;here&lt;/a&gt;.&lt;/p&gt;
+&lt;p&gt;To make a profit, satisfying customers is the key. Unlike the many companies that profit from selling customer data, we put user privacy first. Doing this at scale requires investments. If the investors don’t own or control a company, their participation becomes merely about profit for them, and not about how this profit is obtained. With the investors we have, we are completely aligned on this - they are betting on the future where privacy is the norm. They do not dictate on anything related to our model. We build SimpleX chat, protocols and network the way Internet should have been built if we as developers always put the privacy and empowerment of users first.&lt;/p&gt;
+&lt;h2 id=&quot;company-jurisdiction&quot; tabindex=&quot;-1&quot;&gt;Company jurisdiction&lt;/h2&gt;
+&lt;img src=&quot;https://simplex.chat/blog/images/20240516-parliament.jpg&quot; width=&quot;40%&quot; class=&quot;float-right&quot; /&gt;
+&lt;p&gt;With regards to jurisdictions, nowhere is perfect. For that reason we plan to establish the foundations for protocol governance in &lt;a href=&quot;https://simplex.chat/blog/20240323-simplex-network-privacy-non-profit-v5-6-quantum-resistant-e2e-encryption-simple-migration.html#the-journey-to-the-decentralized-non-profit-protocol-governance&quot;&gt;various jurisdictions&lt;/a&gt;.&lt;/p&gt;
+&lt;p&gt;But we’d like to clarify some misconceptions about the UK, where SimpleX Chat Ltd. is registered, and the UK legislation.&lt;/p&gt;
+&lt;p&gt;For example, the Online Safety Act (OSA). Some people believe that it applies only to UK companies. But the OSA applicability isn’t determined by the company’s jurisdiction - it applies based on the nature and characteristics of the business and its services, as well as the number of its users in the UK. In case of SimpleX network, the OSA doesn’t apply for both of these reasons.&lt;/p&gt;
+&lt;p&gt;The UK’s position on communication encryption, and more specifically, on end-to-end encrypted messaging, remains the subject of political debates. But with the OSA, the legislative intent was to propose technical measures to block CSAM, and it was trying to explore ways to do this via client-side scanning, which of course would undermine the encryption. However, and thanks to the hard work of privacy experts, researchers, academics and rights organizations throughout the UK and the rest of the world, the Online Safety Bill did not prohibit end-to-end encrypted apps without such scanners. It is an open question whether such technology will ever be possible, and the UK government made a public commitment that client-side scanning won&#39;t be required until it is.&lt;/p&gt;
+&lt;p&gt;For now, strong end-to-end encryption remains permissible and protected, and we hope to also add to the privacy advocacy and debates as a UK-based company to keep it legally protected.&lt;/p&gt;
+&lt;p&gt;Overall, we view the UK as being better jurisdiction for privacy than many alternatives - there are some trade-offs everywhere.&lt;/p&gt;
+&lt;h2 id=&quot;looking-ahead&quot; tabindex=&quot;-1&quot;&gt;Looking ahead&lt;/h2&gt;
+&lt;p&gt;The future of the Internet should be based on decentralized infrastructure operated by commercially viable organizations. These operators need to possess minimal user data, so that users have genuine control over their identities, and free from lock-in by the operators, to support fair competition. This requires a drastic re-imagining of the current norms and newer, more privacy-minded protocols. All in all, private messaging is surrounded by very difficult challenges but it’s worth it to keep pushing the industry forward and not settle for the status quo and current trade offs, protocol limitations and vulnerabilities. The Internet deserves better standards, and so do users.&lt;/p&gt;
 </content>
            
        </entry>
@@ -6,10 +6,56 @@
        <atom:link href="https://simplex.chat/feed.rss" rel="self" type="application/rss+xml"/>
        <description>It allows you to stay up to date with the latest Blogs from SimpleX Chat.</description>
        <language>en</language>
+            <item>
+                <title>SimpleX: Redefining Privacy by Making Hard Choices</title>
+                <link>https://simplex.chat/blog/20240516-simplex-redefining-privacy-hard-choices.html</link>
+                <description>&lt;h1 id=&quot;simplex-redefining-privacy-by-making-hard-choices&quot; tabindex=&quot;-1&quot;&gt;SimpleX: Redefining Privacy by Making Hard Choices&lt;/h1&gt;
+&lt;p&gt;&lt;strong&gt;Published:&lt;/strong&gt; May 16, 2024&lt;/p&gt;
+&lt;p&gt;When it comes to open source privacy tools, the status quo often dictates the limitations of existing protocols and structures. However, these norms need to be challenged to radically shift how we approach genuinely private communication. This requires doing some uncomfortable things, like making hard choices as it relates to funding, alternative decentralization models, doubling down on privacy over convenience, and more.&lt;/p&gt;
+&lt;p&gt;There will always be questions on why the SimpleX Chat and network makes the choices it makes, and that’s good! It’s important to question us and to understand the reasoning behind each decision, whether it’s technical, structural, financial or any other.&lt;/p&gt;
+&lt;p&gt;In this post we explain a bit more about why SimpleX operates and makes decisions the way it does.&lt;/p&gt;
+&lt;h2 id=&quot;no-user-accounts&quot; tabindex=&quot;-1&quot;&gt;No user accounts&lt;/h2&gt;
+&lt;p&gt;Within SimpleX network there are no user accounts, and more importantly, no user profile identifiers whatsoever at the protocol level, not even random numbers or cryptographic keys used to identify the users. This means there is absolutely nothing that uniquely links users to their contacts or to the network relays. While it&#39;s accurate to say, &amp;quot;You need an address to send something,&amp;quot; it&#39;s crucial to understand that this &amp;quot;address&amp;quot; serves merely as a transient delivery destination, and not as a user profile identifier in any sense.&lt;/p&gt;
+&lt;p&gt;You can read more about how SimpleX works &lt;a href=&quot;https://simplex.chat/#how-simplex-works&quot;&gt;here&lt;/a&gt;.&lt;/p&gt;
+&lt;h2 id=&quot;privacy-over-convenience&quot; tabindex=&quot;-1&quot;&gt;Privacy over convenience&lt;/h2&gt;
+&lt;p&gt;One of the main considerations often ignored in security and privacy comparisons between messaging applications is multi-device access. For example, in Signal’s case, the Sesame protocol used to support multi-device access has the vulnerability that is &lt;a href=&quot;https://eprint.iacr.org/2021/626.pdf&quot;&gt;explained in detail here&lt;/a&gt;:&lt;/p&gt;
+&lt;p&gt;&lt;em&gt;&amp;quot;We present an attack on the post-compromise security of the Signal messenger that allows to stealthily register a new device via the Sesame protocol. [...] This new device can send and receive messages without raising any ‘Bad encrypted message’ errors. Our attack thus shows that the Signal messenger does not guarantee post-compromise security at all in the multi-device setting&amp;quot;&lt;/em&gt;.&lt;/p&gt;
+&lt;img src=&quot;https://simplex.chat/blog/images/20231125-mobile2.png&quot; width=&quot;170&quot; class=&quot;float-right&quot; /&gt;
+&lt;p&gt;Solutions are possible, and even the quoted paper proposes improvements, but they are not implemented in any existing communication solutions. Unfortunately this results in most communication systems, even those in the privacy space, having compromised security in multi-device settings due to these limitations. That&#39;s the reason we are not rushing a full multi-device support, and currently only provide &lt;a href=&quot;https://simplex.chat/blog/20231125-simplex-chat-v5-4-link-mobile-desktop-quantum-resistant-better-groups.html#link-mobile-and-desktop-apps-via-secure-quantum-resistant-protocol&quot;&gt;the ability to use mobile app profiles via the desktop app&lt;/a&gt;, while they are on the same network.&lt;/p&gt;
+&lt;p&gt;Another choice that compromises privacy for convenience and usability is 3rd party push notifications. At SimpleX, we take a slow path of optimizing the network and battery consumption in the app, rather than simply hiding inefficiencies behind the quick fix solution of 3rd party push notifications that &lt;a href=&quot;https://www.wired.com/story/apple-google-push-notification-surveillance/&quot;&gt;increases vulnerability&lt;/a&gt;, a path Signal and others chose. Like other choices, it has usability and optimization trade offs, but ultimately it’s the right thing to continue progressing towards a better solution as we explain &lt;a href=&quot;https://simplex.chat/blog/20220404-simplex-chat-instant-notifications.html&quot;&gt;here&lt;/a&gt;.&lt;/p&gt;
+&lt;p&gt;Whenever possible, we strive to achieve significantly higher levels of privacy and security. For example, unlike most, if not all, applications (including Signal), &lt;a href=&quot;https://simplex.chat/blog/20230925-simplex-chat-v5-3-desktop-app-local-file-encryption-directory-service.html#encrypted-local-files-and-media-with-forward-secrecy&quot;&gt;we encrypt application files with per-file unique key&lt;/a&gt;. Consequently, once a message is deleted, there&#39;s no means to open a file that someone may have stolen in hopes of acquiring the key later. Similarly, apps like Session have done away with forward secrecy, a decision which caused them &lt;a href=&quot;https://www.privacyguides.org/en/real-time-communication/#additional-options&quot;&gt;not to be recommended&lt;/a&gt; for &amp;quot;long-term or sensitive communications&amp;quot;. And &lt;a href=&quot;https://simplifiedprivacy.com/spain-has-banned-telegram-defending-session/&quot;&gt;misinformation&lt;/a&gt; around this makes it dangerous and irresponsible to recommend without such necessary disclosures for people’s awareness.&lt;/p&gt;
+&lt;p&gt;Session’s decision was based on &lt;a href=&quot;https://getsession.org/blog/session-protocol-explained&quot;&gt;the incorrect statements&lt;/a&gt; about double ratchet being impossible in decentralized networks, and underplayed importance of forward secrecy, break-in recovery and deniability - the absence of these crucial qualities makes Session a much weaker choice for private messaging. For transparency, this was something that was debated with their team &lt;a href=&quot;https://twitter.com/SimpleXChat/status/1755216356159414602&quot;&gt;here&lt;/a&gt;. We also made &lt;a href=&quot;https://simplex.chat/blog/20240314-simplex-chat-v5-6-quantum-resistance-signal-double-ratchet-algorithm.html#end-to-end-encryption-security-attacks-and-defense&quot;&gt;a separate post&lt;/a&gt; about these qualities of end-to-end encryption and their presence in different messengers, to show that not all end-to-end encrypted apps offer the same level of protections.&lt;/p&gt;
+&lt;h2 id=&quot;network-decentralization&quot; tabindex=&quot;-1&quot;&gt;Network decentralization&lt;/h2&gt;
+&lt;img src=&quot;https://simplex.chat/blog/images/simplex-explained.svg&quot; width=&quot;40%&quot; class=&quot;float-right&quot; /&gt;
+&lt;p&gt;It&#39;s important to recognize that a model of decentralization where all servers are openly known and accessible to all clients, that some users ask for, actually results in a less decentralized network, and as the network grows it often requires an introduction of a central authority to protect from bad actors with malicious intent. Therefore, we&#39;ve deliberately opted for a slower path towards achieving a higher degree of decentralization where there is no central server registry or network authority. For example, p2p designs may offer higher initial decentralization but often compromise on privacy and eventual decentralization. In essence, our approach prioritizes a balance between initial decentralization, privacy, and higher degree of decentralization down the line.&lt;/p&gt;
+&lt;p&gt;Additionally, while it&#39;s true that we haven&#39;t yet established a model to incentivize other network operators, it&#39;s certainly on the roadmap. We see the decentralization of network operators offered within the app as a top priority.&lt;/p&gt;
+&lt;p&gt;Where it stands today, users have the freedom to select their preferred servers within the SimpleX network by configuring the app, with thousands of self-hosted servers in operation. Moreover, numerous third-party applications rely on our code for their in-app communications, operating independently of our servers, many of which we may not even be aware of.&lt;/p&gt;
+&lt;p&gt;Decentralization is an ongoing journey, and we strive to proceed at a measured pace to ensure its proper implementation. While the immediate results may not always appear ideal, prioritizing a careful approach ensures that in the long run, the decisions made in this area align with our ultimate objectives of a private, efficient, reliable and fully decentralized network.&lt;/p&gt;
+&lt;h2 id=&quot;funding-and-profitability&quot; tabindex=&quot;-1&quot;&gt;Funding and profitability&lt;/h2&gt;
+&lt;p&gt;We explain our rationale for funding &lt;a href=&quot;https://simplex.chat/faq/index.html#funding-and-business-model&quot;&gt;here&lt;/a&gt;. Funding sources is always one of the most difficult choices to make, and it’s important to underline that VC models don’t necessarily translate to a quest for control, interference of any kind, or overall influence on product roadmap and strategy. The vast majority of investors seek profitability. Irrespective of the organization type profitability is essential for a sustainable operation, and it can and should be done while adhering to the highest possible standards for privacy. For-profit vs. nonprofit is also not an accurate metric to measure a commitment towards privacy and open standards, which is further explained &lt;a href=&quot;https://simplex.chat/blog/20240404-why-i-joined-simplex-chat-esraa-al-shafei.html&quot;&gt;here&lt;/a&gt;.&lt;/p&gt;
+&lt;p&gt;To make a profit, satisfying customers is the key. Unlike the many companies that profit from selling customer data, we put user privacy first. Doing this at scale requires investments. If the investors don’t own or control a company, their participation becomes merely about profit for them, and not about how this profit is obtained. With the investors we have, we are completely aligned on this - they are betting on the future where privacy is the norm. They do not dictate on anything related to our model. We build SimpleX chat, protocols and network the way Internet should have been built if we as developers always put the privacy and empowerment of users first.&lt;/p&gt;
+&lt;h2 id=&quot;company-jurisdiction&quot; tabindex=&quot;-1&quot;&gt;Company jurisdiction&lt;/h2&gt;
+&lt;img src=&quot;https://simplex.chat/blog/images/20240516-parliament.jpg&quot; width=&quot;40%&quot; class=&quot;float-right&quot; /&gt;
+&lt;p&gt;With regards to jurisdictions, nowhere is perfect. For that reason we plan to establish the foundations for protocol governance in &lt;a href=&quot;https://simplex.chat/blog/20240323-simplex-network-privacy-non-profit-v5-6-quantum-resistant-e2e-encryption-simple-migration.html#the-journey-to-the-decentralized-non-profit-protocol-governance&quot;&gt;various jurisdictions&lt;/a&gt;.&lt;/p&gt;
+&lt;p&gt;But we’d like to clarify some misconceptions about the UK, where SimpleX Chat Ltd. is registered, and the UK legislation.&lt;/p&gt;
+&lt;p&gt;For example, the Online Safety Act (OSA). Some people believe that it applies only to UK companies. But the OSA applicability isn’t determined by the company’s jurisdiction - it applies based on the nature and characteristics of the business and its services, as well as the number of its users in the UK. In case of SimpleX network, the OSA doesn’t apply for both of these reasons.&lt;/p&gt;
+&lt;p&gt;The UK’s position on communication encryption, and more specifically, on end-to-end encrypted messaging, remains the subject of political debates. But with the OSA, the legislative intent was to propose technical measures to block CSAM, and it was trying to explore ways to do this via client-side scanning, which of course would undermine the encryption. However, and thanks to the hard work of privacy experts, researchers, academics and rights organizations throughout the UK and the rest of the world, the Online Safety Bill did not prohibit end-to-end encrypted apps without such scanners. It is an open question whether such technology will ever be possible, and the UK government made a public commitment that client-side scanning won&#39;t be required until it is.&lt;/p&gt;
+&lt;p&gt;For now, strong end-to-end encryption remains permissible and protected, and we hope to also add to the privacy advocacy and debates as a UK-based company to keep it legally protected.&lt;/p&gt;
+&lt;p&gt;Overall, we view the UK as being better jurisdiction for privacy than many alternatives - there are some trade-offs everywhere.&lt;/p&gt;
+&lt;h2 id=&quot;looking-ahead&quot; tabindex=&quot;-1&quot;&gt;Looking ahead&lt;/h2&gt;
+&lt;p&gt;The future of the Internet should be based on decentralized infrastructure operated by commercially viable organizations. These operators need to possess minimal user data, so that users have genuine control over their identities, and free from lock-in by the operators, to support fair competition. This requires a drastic re-imagining of the current norms and newer, more privacy-minded protocols. All in all, private messaging is surrounded by very difficult challenges but it’s worth it to keep pushing the industry forward and not settle for the status quo and current trade offs, protocol limitations and vulnerabilities. The Internet deserves better standards, and so do users.&lt;/p&gt;
+</description>
+                
+                
+                <pubDate>16 May 2024</pubDate>
+                <dc:creator>SimpleX Chat</dc:creator>
+                <guid>https://simplex.chat/blog/20240516-simplex-redefining-privacy-hard-choices.html</guid>
+            </item>
            <item>
                <title>SimpleX network: legally binding transparency, v5.7 released with better calls and messages</title>
                <link>https://simplex.chat/blog/20240426-simplex-legally-binding-transparency-v5-7-better-user-experience.html</link>
                <description>&lt;h1 id=&quot;simplex-network-legally-binding-transparency-v57-released-with-better-calls-and-messages&quot; tabindex=&quot;-1&quot;&gt;SimpleX network: legally binding transparency, v5.7 released with better calls and messages&lt;/h1&gt;
+&lt;p&gt;&lt;strong&gt;Published:&lt;/strong&gt; Apr 26, 2024&lt;/p&gt;
 &lt;p&gt;What&#39;s new in v5.7:&lt;/p&gt;
 &lt;ul&gt;
 &lt;li&gt;&lt;a href=&quot;https://simplex.chat/blog/20240426-simplex-legally-binding-transparency-v5-7-better-user-experience.html#quantum-resistant-end-to-end-encryption&quot;&gt;quantum resistant end-to-end encryption&lt;/a&gt; with all contacts.&lt;/li&gt;
@@ -22,10 +68,10 @@
 &lt;h2 id=&quot;legally-binding-transparency&quot; tabindex=&quot;-1&quot;&gt;Legally binding transparency&lt;/h2&gt;
 &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/&quot;&gt;Transparency Reports&lt;/a&gt; page.&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/&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/&quot;&gt;Security Policy&lt;/a&gt; – we welcome your feedback on it.&lt;/li&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 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;
 &lt;p&gt;What do we mean by “legally binding transparency?”. It includes these principles:&lt;/p&gt;
 &lt;ul&gt;
@@ -64,7 +110,7 @@
 &lt;p&gt;&lt;a href=&quot;https://simplex.chat/blog/20220511-simplex-chat-v2-images-files.html#the-first-messaging-platform-without-user-identifiers&quot;&gt;How can SimpleX deliver messages without user identifiers&lt;/a&gt;.&lt;/p&gt;
 &lt;p&gt;&lt;a href=&quot;https://simplex.chat/blog/20220711-simplex-chat-v3-released-ios-notifications-audio-video-calls-database-export-import-protocol-improvements.html#why-having-users-identifiers-is-bad-for-the-users&quot;&gt;What are the risks to have identifiers assigned to the users&lt;/a&gt;.&lt;/p&gt;
 &lt;p&gt;&lt;a href=&quot;https://github.com/simplex-chat/simplex-chat#privacy-technical-details-and-limitations&quot;&gt;Technical details and limitations&lt;/a&gt;.&lt;/p&gt;
-&lt;p&gt;&lt;a href=&quot;https://simplex.chat/blog/docs/faq.html&quot;&gt;Frequently asked questions&lt;/a&gt;.&lt;/p&gt;
+&lt;p&gt;&lt;a href=&quot;https://simplex.chat/faq/index.html&quot;&gt;Frequently asked questions&lt;/a&gt;.&lt;/p&gt;
 &lt;p&gt;Please also see our &lt;a href=&quot;https://simplex.chat/&quot;&gt;website&lt;/a&gt;.&lt;/p&gt;
 &lt;h2 id=&quot;help-us-with-donations&quot; tabindex=&quot;-1&quot;&gt;Help us with donations&lt;/h2&gt;
 &lt;p&gt;Huge thank you to everybody who donates to SimpleX Chat!&lt;/p&gt;
@@ -260,6 +306,7 @@
                <title>SimpleX Chat v5.6 (beta): adding quantum resistance to Signal double ratchet algorithm</title>
                <link>https://simplex.chat/blog/20240314-simplex-chat-v5-6-quantum-resistance-signal-double-ratchet-algorithm.html</link>
                <description>&lt;h1 id=&quot;simplex-chat-v56-beta-adding-quantum-resistance-to-signal-double-ratchet-algorithm&quot; tabindex=&quot;-1&quot;&gt;SimpleX Chat v5.6 beta: adding quantum resistance to Signal double ratchet algorithm&lt;/h1&gt;
+&lt;p&gt;&lt;strong&gt;Published:&lt;/strong&gt; Mar 14, 2024&lt;/p&gt;
 &lt;p&gt;This is a major upgrade for SimpleX messaging protocols, we are really proud to present the results of the hard work of our whole team on the &lt;a href=&quot;https://en.wikipedia.org/wiki/Pi_Day&quot;&gt;Pi day&lt;/a&gt;.&lt;/p&gt;
 &lt;p&gt;This post also covers various aspects of end-to-end encryption, compares different messengers, and explains why and how quantum-resistant encryption is added to SimpleX Chat:&lt;/p&gt;
 &lt;ul&gt;
@@ -322,7 +369,7 @@
 &lt;h3 id=&quot;4-compromised-long-term-or-session-mitigated-by-break-in-recovery&quot; tabindex=&quot;-1&quot;&gt;4. Compromised long-term or session - mitigated by break-in recovery&lt;/h3&gt;
 &lt;p&gt;This attack is much less understood by the users, and forward secrecy does not protect from it. Arguably, it&#39;s almost impossible to compromise individual message keys without compromising long-term or session keys. So the ability of the encryption to recover from break-in (attacker making a copy of the device data without retaining the ongoing access) is both very important and pragmatic - break-in attacks are simpler to execute on mobile devices during short-term device access than long-term ongoing compromise.&lt;/p&gt;
 &lt;p&gt;Out of all encryption algorithms known to us only &lt;em&gt;Signal double ratchet algorithm&lt;/em&gt; (also referred to as &lt;em&gt;Signal algorithm&lt;/em&gt; or &lt;em&gt;double ratchet algorithm&lt;/em&gt;, which is not the same as Signal messaging platform and protocols) provides the ability for the encryption security to recover after break-ins attacks. This recovery happens automatically and transparently to the users, without them doing anything special or even knowing about break-in, by simply sending messages. Every time one of the communication parties replies to another party message, new random keys are generated and previously stolen keys become useless.&lt;/p&gt;
-&lt;p&gt;Double ratchet algorithm is used in Signal, Cwtch and SimpleX Chat. This is why you cannot use SimpleX Chat profile on more than one device at the same time - the encryption scheme rotates the long term keys, randomly, and keys on another device become useless, as they would become useless for the attacker who stole them. Security always has some costs to the convenience.&lt;/p&gt;
+&lt;p&gt;Double ratchet algorithm is used in Signal, Cwtch and SimpleX Chat. But Signal app by allowing to use the same profile on multiple devices compromises the break-in recovery function of Signal algorithm, as explained in &lt;a href=&quot;https://eprint.iacr.org/2021/626.pdf&quot;&gt;this paper&lt;/a&gt;. Because of break-in recovery you cannot use SimpleX Chat profile on more than one device at the same time - the encryption scheme rotates the long term keys, randomly, and keys on another device become useless, as they would become useless for the attacker who stole them. Security always has some costs to the convenience.&lt;/p&gt;
 &lt;h3 id=&quot;5-man-in-the-middle-attack-mitigated-by-two-factor-key-exchange&quot; tabindex=&quot;-1&quot;&gt;5. Man-in-the-middle attack - mitigated by two-factor key exchange&lt;/h3&gt;
 &lt;p&gt;Many people incorrectly believe that security of end-to-end encryption cannot be broken by communication provider. But end-to-end encryption is only as secure as key exchange. While any intermediary passing the keys between senders and recipients cannot recover the private keys from the public keys, they can simply replace the passed public keys with their own and then proxy all communication between the users having full access to the original messages. So instead of having an end-to-end encrypted channel, users would have two half-way encrypted channels - between users and their communication intermediary.&lt;/p&gt;
 &lt;p&gt;Pictures below illustrate how this attack works for RSA encryption.&lt;/p&gt;
@@ -551,7 +598,7 @@
 &lt;p&gt;This is only possible when both devices are connected to the same local network. To send and receive messages mobile app has to be connected to the Internet.&lt;/p&gt;
 &lt;h3 id=&quot;quick-start-how-to-use-it&quot; tabindex=&quot;-1&quot;&gt;⚡️ Quick start - how to use it&lt;/h3&gt;
 &lt;p&gt;&lt;strong&gt;On desktop&lt;/strong&gt;&lt;/p&gt;
-&lt;p&gt;If you don&#39;t have desktop app installed yet, &lt;a href=&quot;https://simplex.chat/downloads/&quot;&gt;download it&lt;/a&gt; and create any chat profile - you don&#39;t need to use it, and when you create it there are no server requests sent and no accounts are created. Think about it as about user profile on your computer.&lt;/p&gt;
+&lt;p&gt;If you don&#39;t have desktop app installed yet, &lt;a href=&quot;https://simplex.chat/downloads/index.html&quot;&gt;download it&lt;/a&gt; and create any chat profile - you don&#39;t need to use it, and when you create it there are no server requests sent and no accounts are created. Think about it as about user profile on your computer.&lt;/p&gt;
 &lt;p&gt;Then in desktop app settings choose &lt;em&gt;Link a mobile&lt;/em&gt; - it will show a QR code.&lt;/p&gt;
 &lt;p&gt;&lt;img src=&quot;https://simplex.chat/blog/images/20231125-desktop1.png&quot; width=&quot;170&quot; /&gt; &lt;img src=&quot;https://simplex.chat/blog/images/arrow.png&quot; width=&quot;24&quot; /&gt; &lt;img src=&quot;https://simplex.chat/blog/images/20231125-desktop2.png&quot; width=&quot;170&quot; /&gt; &lt;img src=&quot;https://simplex.chat/blog/images/arrow.png&quot; width=&quot;24&quot; /&gt; &lt;img src=&quot;https://simplex.chat/blog/images/20231125-desktop3.png&quot; width=&quot;170&quot; /&gt; &lt;img src=&quot;https://simplex.chat/blog/images/arrow.png&quot; width=&quot;24&quot; /&gt; &lt;img src=&quot;https://simplex.chat/blog/images/20231125-desktop4.png&quot; width=&quot;510&quot; /&gt;&lt;/p&gt;
 &lt;p&gt;&lt;strong&gt;On mobile&lt;/strong&gt;&lt;/p&gt;
@@ -561,7 +608,7 @@
 &lt;p&gt;If it is an Android app, you can move the app to background, but iOS app has to remain open. In both cases, while you are using mobile profiles from desktop, you won&#39;t be able to use mobile app.&lt;/p&gt;
 &lt;p&gt;The subsequent connections happen much faster - by default, the desktop app broadcasts its session address to the network, in encrypted form, and mobile app connects to it once you choose &lt;em&gt;Use from desktop&lt;/em&gt; in mobile app settings.&lt;/p&gt;
 &lt;h3 id=&quot;how-does-it-work&quot; tabindex=&quot;-1&quot;&gt;How does it work?&lt;/h3&gt;
-&lt;p&gt;The way we designed this solution avoided any security compromises, and the end-to-end encryption remained as secure as it was - it uses &lt;a href=&quot;https://simplex.chat/blog/docs/glossary.html#double-ratchet-algorithm&quot;&gt;double-ratchet algorithm&lt;/a&gt;, with &lt;a href=&quot;https://simplex.chat/blog/docs/glossary.html#forward-secrecy&quot;&gt;perfect forward secrecy&lt;/a&gt;, &lt;a href=&quot;https://simplex.chat/blog/docs/glossary.html#post-compromise-security&quot;&gt;post-compromise security&lt;/a&gt; and deniability.&lt;/p&gt;
+&lt;p&gt;The way we designed this solution avoided any security compromises, and the end-to-end encryption remained as secure as it was - it uses &lt;a href=&quot;https://simplex.chat/docs/glossary.html#double-ratchet-algorithm&quot;&gt;double-ratchet algorithm&lt;/a&gt;, with &lt;a href=&quot;https://simplex.chat/docs/glossary.html#forward-secrecy&quot;&gt;perfect forward secrecy&lt;/a&gt;, &lt;a href=&quot;https://simplex.chat/docs/glossary.html#post-compromise-security&quot;&gt;post-compromise security&lt;/a&gt; and deniability.&lt;/p&gt;
 &lt;p&gt;This solution is similar to WhatsApp and WeChat. But unlike these apps, no server is involved in the connection between mobile and desktop. The connection itself uses a new SimpleX Remote Control Protocol (XRCP) based on secure TLS 1.3 and additional quantum-resistant encryption inside TLS. You can read XRCP protocol specification and threat model in &lt;a href=&quot;https://github.com/simplex-chat/simplexmq/blob/master/rfcs/2023-10-25-remote-control.md&quot;&gt;this document&lt;/a&gt;. We will soon be &lt;a href=&quot;https://github.com/simplex-chat/simplex-chat/blob/master/docs/rfcs/2023-09-30-pq-double-ratchet.md&quot;&gt;augmenting double ratchet&lt;/a&gt; to be resistant to quantum computers as well.&lt;/p&gt;
 &lt;p&gt;The downside of this approach is that mobile device has to be connected to the same local network as desktop. But the upside is that the connection is secure, and you do not need to have a copy of all your data on desktop, which usually has lower security than mobile.&lt;/p&gt;
 &lt;p&gt;Please note, that the files you send, save or play from desktop app, and also images you view are automatically saved on your desktop device (encrypted by default except videos). To remove all these files you can unlink the paired mobile device from the desktop app settings – there will be an option soon allowing to remove the files without unlinking the mobile.&lt;/p&gt;
@@ -662,11 +709,11 @@
 &lt;li&gt;you cannot send voice messages.&lt;/li&gt;
 &lt;li&gt;there is no support for calls yet.&lt;/li&gt;
 &lt;/ul&gt;
-&lt;p&gt;You can download the desktop app for Linux and Mac via &lt;a href=&quot;https://simplex.chat/downloads&quot;&gt;downloads page&lt;/a&gt;. Windows version will be available soon.&lt;/p&gt;
+&lt;p&gt;You can download the desktop app for Linux and Mac via &lt;a href=&quot;https://simplex.chat/downloads/index.html&quot;&gt;downloads page&lt;/a&gt;. Windows version will be available soon.&lt;/p&gt;
 &lt;h2 id=&quot;group-directory-service-and-other-group-improvements&quot; tabindex=&quot;-1&quot;&gt;Group directory service and other group improvements&lt;/h2&gt;
 &lt;img src=&quot;https://simplex.chat/blog/images/20230925-directory.png&quot; width=&quot;330&quot; class=&quot;float-to-left&quot; /&gt;
 &lt;p&gt;Directory service provides a way to search for public groups submitted by the users. To use it, you need to connect to it via SimpleX Chat, as you would connect to any other contact, and type some words to search.&lt;/p&gt;
-&lt;p&gt;You can also create and register your group, with some limitations explained &lt;a href=&quot;https://simplex.chat/blog/docs/directory.html&quot;&gt;here&lt;/a&gt;.&lt;/p&gt;
+&lt;p&gt;You can also create and register your group, with some limitations explained &lt;a href=&quot;https://simplex.chat/docs/directory.html&quot;&gt;here&lt;/a&gt;.&lt;/p&gt;
 &lt;p&gt;Other group improvements in this release:&lt;/p&gt;
 &lt;ul&gt;
 &lt;li&gt;
@@ -784,8 +831,8 @@
 &lt;p&gt;Please report the cases when messages are not delivered – delivery receipts should help with that.&lt;/p&gt;
 &lt;h4 id=&quot;messages-failed-to-decrypt-problem-solved&quot; tabindex=&quot;-1&quot;&gt;Messages failed to decrypt? Problem solved!&lt;/h4&gt;
 &lt;p&gt;Previously, a growing number of users had the issue when after restoring the chat database from backup, messages from some contacts failed to decrypt and were showing an error in the app.&lt;/p&gt;
-&lt;p&gt;This happens due to double ratchet protocol protecting the integrity of end-to-end encryption after the compromise - &lt;a href=&quot;https://simplex.chat/blog/docs/glossary.html#post-compromise-security&quot;&gt;post-compromise security&lt;/a&gt;. The protocol logic does not allow to use the old version of the database to decrypt the message.&lt;/p&gt;
-&lt;p&gt;v5.2 added the extension to the messaging protocol allowing to negotiate the new ratchet keys in such cases - both with the contacts and the group members. This requires a user action, and it resets the security code verification status for this contact or member – you need to verify it again to have the additional protection from &lt;a href=&quot;https://simplex.chat/blog/docs/glossary.html#man-in-the-middle-attack&quot;&gt;man-in-the-middle attacks&lt;/a&gt;.&lt;/p&gt;
+&lt;p&gt;This happens due to double ratchet protocol protecting the integrity of end-to-end encryption after the compromise - &lt;a href=&quot;https://simplex.chat/docs/glossary.html#post-compromise-security&quot;&gt;post-compromise security&lt;/a&gt;. The protocol logic does not allow to use the old version of the database to decrypt the message.&lt;/p&gt;
+&lt;p&gt;v5.2 added the extension to the messaging protocol allowing to negotiate the new ratchet keys in such cases - both with the contacts and the group members. This requires a user action, and it resets the security code verification status for this contact or member – you need to verify it again to have the additional protection from &lt;a href=&quot;https://simplex.chat/docs/glossary.html#man-in-the-middle-attack&quot;&gt;man-in-the-middle attacks&lt;/a&gt;.&lt;/p&gt;
 &lt;p&gt;The negotiation of the new ratchet keys still happens via the end-to-end encrypted messages, as the protocol has two layers of end-to-end encryption, so it cannot be compromised by the messaging relays.&lt;/p&gt;
 &lt;p&gt;You may still lose connection if you or your contact changed the receiving address after you made the backup, so make sure to make a new backup after any receiving address changes.&lt;/p&gt;
 &lt;h4 id=&quot;reconnect-the-servers&quot; tabindex=&quot;-1&quot;&gt;Reconnect the servers&lt;/h4&gt;
@@ -805,12 +852,12 @@
 &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/docs/rfcs/2023-05-02-groups.html&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://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;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/docs/rfcs/2023-05-22-groups-moderation.html&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://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;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;
@@ -893,7 +940,7 @@
 &lt;h2 id=&quot;customize-and-share-color-themes&quot; tabindex=&quot;-1&quot;&gt;Customize and share color themes&lt;/h2&gt;
 &lt;img src=&quot;https://simplex.chat/blog/images/20230523-theme.png&quot; width=&quot;288&quot; class=&quot;float-to-left&quot; /&gt;
 &lt;p&gt;Android app now allows choosing between three color themes - Light, Dark and SimpleX (a dark blue theme). You can customize any theme by setting 9 different colors used in the app, including titles, menus, accent colors and colors for sent and received messages.&lt;/p&gt;
-&lt;p&gt;You can share your theme with other users by exporting it to a file and sending to them. You can also &lt;a href=&quot;https://simplex.chat/blog/docs/themes.html&quot;&gt;contribute your favorite themes&lt;/a&gt; to our GitHub repository.&lt;/p&gt;
+&lt;p&gt;You can share your theme with other users by exporting it to a file and sending to them. You can also &lt;a href=&quot;https://simplex.chat/docs/themes.html&quot;&gt;contribute your favorite themes&lt;/a&gt; to our GitHub repository.&lt;/p&gt;
 &lt;h2 id=&quot;self-destruct-passcode&quot; tabindex=&quot;-1&quot;&gt;Self-destruct passcode&lt;/h2&gt;
 &lt;img src=&quot;https://simplex.chat/blog/images/20230523-self-destruct.png&quot; width=&quot;288&quot; class=&quot;float-to-left&quot; /&gt;
 &lt;p&gt;This is something many of you asked before - when asked to enter the app passcode under duress, to be able to enter a special self-destruct code that would remove the app data. This feature is offered in many security tools, and now you can configure it in SimpleX Chat as well.&lt;/p&gt;
@@ -2348,10 +2395,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/images/groups.gif&quot; alt=&quot;simplex-chat&quot; /&gt;&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;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/images/files.gif&quot; alt=&quot;simplex-chat&quot; /&gt;&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;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;
@@ -40,8 +40,8 @@
    <meta name="viewport" content="width=device-width, initial-scale=1.0" />
    <title>SimpleX Privacy Policy</title>
    <meta name="Content-Type" content="text/html;charset=utf-8" />
-    <meta http-equiv="onion-location" content="http://isdb4l77sjqoy2qq7ipum6x3at6hyn3jmxfx4zdhc72ufbmuq4ilwkqd.onion" />
-    <meta property="og:url" content="https://simplex.chat" />
+    <meta http-equiv="onion-location" content="http://isdb4l77sjqoy2qq7ipum6x3at6hyn3jmxfx4zdhc72ufbmuq4ilwkqd.onion/privacy/index.html" />
+    <meta property="og:url" content="https://simplex.chat/privacy/index.html" />
    <meta property="og:type" content="article" />
    <meta property="og:title" content="" />
    
@@ -572,7 +572,7 @@ window.addEventListener('scroll',changeHeaderBg);
 <p>SimpleX Chat is the first communication network based on a new protocol stack that builds on the same ideas of complete openness and decentralization as email and web, with the focus on providing security and privacy of communications, and without compromising on usability.</p>
 <p>SimpleX Chat communication protocol is the first protocol that has no user profile IDs of any kind, not even random numbers, cryptographic keys or hashes that identify the users. SimpleX Chat apps allow their users to send messages and files via relay server infrastructure. Relay server owners and providers do not have any access to your messages, thanks to double-ratchet end-to-end encryption algorithm (also known as Signal algorithm - do not confuse with Signal protocols or platform) and additional encryption layers, and they also have no access to your profile and contacts - as they do not provide any user accounts.</p>
 <p>Double ratchet algorithm has such important properties as <a href="/docs/glossary.html#forward-secrecy">forward secrecy</a>, sender <a href="/docs/glossary.html#">repudiation</a> and break-in recovery (also known as <a href="/docs/glossary.html#post-compromise-security">post-compromise security</a>).</p>
-<p>If you believe that any part of this document is not aligned with our mission or values, please raise it with us via <a href="chat@simplex.chat">email</a> or <a href="https://simplex.chat/contact#/?v=1&amp;smp=smp%3A%2F%2FPQUV2eL0t7OStZOoAsPEV2QYWt4-xilbakvGUGOItUo%3D%40smp6.simplex.im%2FK1rslx-m5bpXVIdMZg9NLUZ_8JBm8xTt%23%2F%3Fv%3D1%26dh%3DMCowBQYDK2VuAyEALDeVe-sG8mRY22LsXlPgiwTNs9dbiLrNuA7f3ZMAJ2w%253D%26srv%3Dbylepyau3ty4czmn77q4fglvperknl4bi2eb2fdy2bh4jxtf32kf73yd.onion">chat</a>.</p>
+<p>If you believe that any part of this document is not aligned with our mission or values, please raise it with us via <a href="mailto:chat@simplex.chat">email</a> or <a href="https://simplex.chat/contact#/?v=1&amp;smp=smp%3A%2F%2FPQUV2eL0t7OStZOoAsPEV2QYWt4-xilbakvGUGOItUo%3D%40smp6.simplex.im%2FK1rslx-m5bpXVIdMZg9NLUZ_8JBm8xTt%23%2F%3Fv%3D1%26dh%3DMCowBQYDK2VuAyEALDeVe-sG8mRY22LsXlPgiwTNs9dbiLrNuA7f3ZMAJ2w%253D%26srv%3Dbylepyau3ty4czmn77q4fglvperknl4bi2eb2fdy2bh4jxtf32kf73yd.onion">chat</a>.</p>
 <h2 id="privacy-policy" tabindex="-1">Privacy Policy</h2>
 <p>SimpleX Chat Ltd uses the best industry practices for security and encryption to provide client and server software for secure <a href="/docs/glossary.html#end-to-end-encryption">end-to-end encrypted</a> messaging via private connections. This encryption cannot be compromised by the relays servers, even if they are modified or compromised, via <a href="/docs/glossary.html#man-in-the-middle-attack">man-in-the-middle attack</a>, unlike most other communication platforms, services and networks.</p>
 <p>SimpleX Chat software is built on top of SimpleX messaging and application protocols, based on a new message routing protocol allowing to establish private connections without having any kind of addresses or other identifiers assigned to its users - it does not use emails, phone numbers, usernames, identity keys or any other user profile identifiers to pass messages between the user applications.</p>
@@ -610,7 +610,7 @@ window.addEventListener('scroll',changeHeaderBg);
 <h4 id="ios-push-notifications" tabindex="-1">iOS Push Notifications</h4>
 <p>When you choose to use instant push notifications in SimpleX iOS app, because the design of push notifications requires storing the device token on notification server, the notifications server can observe how many messaging queues your device has notifications enabled for, and approximately how many messages are sent to each queue.</p>
 <p>Preset notification server cannot observe the actual addresses of these queues, as a separate address is used to subscribe to the notifications. It also cannot observe who sends messages to you. Apple push notifications servers can only observe how many notifications are sent to you, but not from how many contacts, or from which messaging relays, as notifications are delivered to your device end-to-end encrypted by one of the preset notification servers - these notifications only contain end-to-end encrypted metadata, not even encrypted message content, and they look completely random to Apple push notification servers.</p>
-<p>You can read more about the design of iOS push notifications <a href="https://simplex.chat/blog/20220404-simplex-chat-instant-notifications.html#our-ios-approach-has-one-trade-off">here</a>.</p>
+<p>You can read more about the design of iOS push notifications <a href="/blog/20220404-simplex-chat-instant-notifications.html#our-ios-approach-has-one-trade-off">here</a>.</p>
 <h4 id="another-information-stored-on-the-servers" tabindex="-1">Another information stored on the servers</h4>
 <p>Additional technical information can be stored on our servers, including randomly generated authentication tokens, keys, push tokens, and other material that is necessary to transmit messages. SimpleX Chat design limits this additional technical information to the minimum required to operate the software and servers. To prevent server overloading or attacks, the servers can temporarily store data that can link to particular users or devices, including IP addresses, geographic location, or information related to the transport sessions. This information is not stored for the absolute majority of the app users, even for those who use the servers very actively.</p>
 <h4 id="simplex-directory" tabindex="-1">SimpleX Directory</h4>
@@ -628,11 +628,11 @@ window.addEventListener('scroll',changeHeaderBg);
 <li>To protect against harm to the rights, property, or safety of software users, SimpleX Chat Ltd, or the public as required or permitted by law.</li>
 </ul>
 <p>At the time of updating this document, we have never provided or have been requested the access to the preset relay servers or any information from the servers by any third parties. If we are ever requested to provide such access or information, we will follow the due legal process to limit any information shared with the third parties to the minimally required by law.</p>
-<p>We will publish information we are legally allowed to share about such requests in the <a href="docs/transparency.html">Transparency reports</a>.</p>
+<p>We will publish information we are legally allowed to share about such requests in the <a href="/transparency/index.html">Transparency reports</a>.</p>
 <h3 id="updates" tabindex="-1">Updates</h3>
 <p>We will update this Privacy Policy as needed so that it is current, accurate, and as clear as possible. Your continued use of our software applications and preset relays infrastructure confirms your acceptance of our updated Privacy Policy.</p>
 <p>Please also read our Conditions of Use of Software and Infrastructure below.</p>
-<p>If you have questions about our Privacy Policy please contact us via <a href="chat@simplex.chat">email</a> or <a href="https://simplex.chat/contact#/?v=1&amp;smp=smp%3A%2F%2FPQUV2eL0t7OStZOoAsPEV2QYWt4-xilbakvGUGOItUo%3D%40smp6.simplex.im%2FK1rslx-m5bpXVIdMZg9NLUZ_8JBm8xTt%23%2F%3Fv%3D1%26dh%3DMCowBQYDK2VuAyEALDeVe-sG8mRY22LsXlPgiwTNs9dbiLrNuA7f3ZMAJ2w%253D%26srv%3Dbylepyau3ty4czmn77q4fglvperknl4bi2eb2fdy2bh4jxtf32kf73yd.onion">chat</a>.</p>
+<p>If you have questions about our Privacy Policy please contact us via <a href="mailto:chat@simplex.chat">email</a> or <a href="https://simplex.chat/contact#/?v=1&amp;smp=smp%3A%2F%2FPQUV2eL0t7OStZOoAsPEV2QYWt4-xilbakvGUGOItUo%3D%40smp6.simplex.im%2FK1rslx-m5bpXVIdMZg9NLUZ_8JBm8xTt%23%2F%3Fv%3D1%26dh%3DMCowBQYDK2VuAyEALDeVe-sG8mRY22LsXlPgiwTNs9dbiLrNuA7f3ZMAJ2w%253D%26srv%3Dbylepyau3ty4czmn77q4fglvperknl4bi2eb2fdy2bh4jxtf32kf73yd.onion">chat</a>.</p>
 <h2 id="conditions-of-use-of-software-and-infrastructure" tabindex="-1">Conditions of Use of Software and Infrastructure</h2>
 <p>You accept the Conditions of Use of Software and Infrastructure (&quot;Conditions&quot;) by installing or using any of our software or using any of our server infrastructure (collectively referred to as &quot;Applications&quot;), whether preset in the software or not.</p>
 <p><strong>Minimal age</strong>. You must be at least 13 years old to use our Applications. The minimum age to use our Applications without parental approval may be higher in your country.</p>
@@ -845,7 +845,7 @@ window.addEventListener('scroll',changeHeaderBg);
                    </div>
                    <div><h1 id="security-policy" tabindex="-1">Security Policy</h1>
 <p>While great care is taken to ensure the highest level of security and privacy in SimpleX network servers and clients, all software can have flaws, and we believe it is a critical part of an organization's social responsibility to minimize the impact of these flaws through continual vulnerability discovery efforts, defense in depth design, and prompt remediation and notification.</p>
-<p>The security assessment of SimpleX cryptography and networking was done by Trail of Bits in <a href="https://simplex.chat/blog/20221108-simplex-chat-v4.2-security-audit-new-website.html">November 2022</a>.</p>
+<p>The security assessment of SimpleX cryptography and networking was done by Trail of Bits in <a href="/blog/20221108-simplex-chat-v4.2-security-audit-new-website.html">November 2022</a>.</p>
 <p>We are planning design review of SimpleX protocols in July 2024 and implementation review in December 2024/January 2025.</p>
 <h2 id="reporting-security-issues" tabindex="-1">Reporting security issues</h2>
 <p>To report a security issue, please contact us directly via email <a href="mailto:chat@simplex.chat">chat@simplex.chat</a>. Please do NOT report security issues via GitHub issues or via any public channels.</p>
@@ -851,8 +851,8 @@ window.addEventListener('scroll',changeHeaderBg);
 <p>Our objective is to consistently ensure that no user data and absolute minimum of the metadata required for the network to function is available for disclosure by any infrastructure operators, under any circumstances.</p>
 <p><strong>Helpful resources</strong>:</p>
 <ul>
-<li><a href="/privacy">Privacy policy</a></li>
-<li><a href="readme.html#privacy-and-security-technical-details-and-limitations">Privacy and security: technical details and limitations</a></li>
+<li><a href="https%3A//github.com/simplex-chat/simplex-chat/blob/stable/simplex-chat/PRIVACY.md">Privacy policy</a></li>
+<li><a href="https%3A//github.com/simplex-chat/simplex-chat/blob/stable/simplex-chat/README.md#privacy-and-security-technical-details-and-limitations">Privacy and security: technical details and limitations</a></li>
 <li>Whitepaper:
 <ul>
 <li><a href="https://github.com/simplex-chat/simplexmq/blob/stable/protocol/overview-tjr.md#trust-in-servers">Trust in servers</a></li>