deploy: bf10f9d093

2026-05-28 11:35:24 +00:00 · 2022-08-08 09:40:44 +00:00
parent f75a6fa63f
commit bd1539da23
9 changed files with 28 additions and 28 deletions
@@ -62,7 +62,7 @@
 <h3>Changes in protocol encoding</h3>
 <p>We switched from inefficient text-based low level protocol encodings, that simplified early development, to space and performance efficient binary encodings, reducing protocol overhead from circa 15% to 3.7% of transmitted application message size.</p>
 <h2>Learn more about Simplex</h2>
-<p>Further details on platform objectives and technical design are available <a href="https://github.com/simplex-chat/simplexmq/blob/master/protocol/overview-tjr/">here</a>.</p>
+<p>Further details on platform objectives and technical design are available <a href="https://github.com/simplex-chat/simplexmq/blob/master/protocol/overview-tjr.md">here</a>.</p>
 <p>SimpleX Chat client can be used in the terminal on all major desktop platforms (Windows/Mac/Linux) and also on Android devices with <a href="https://github.com/termux">Termux</a>.</p>
 <p>SimpleX also allows people to host their own servers and own their own chat data. SimpleX servers are exceptionally lightweight and require a single process with the initial memory footprint of under 20 Mb, which grows as the server adds in-memory queues (even with 10,000 queues it uses less than 50Mb, not accounting for messages).</p>
 <h2>We look forward to you using it!</h2>
@@ -48,7 +48,7 @@
 <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="https://github.com/simplex-chat/simplex-chat/blob/stable/blog/20220112-simplex-chat-v1-released/">v1 announcement</a>.</p>
+<p>You can read more details in our recent <a href="https://github.com/simplex-chat/simplex-chat/blob/stable/blog/20220112-simplex-chat-v1-released.md">v1 announcement</a>.</p>
 <h2>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>
@@ -64,7 +64,7 @@
 <p>We aim to provide the best possible protection of messages and metadata. Today there is no messaging application that works without global user identities, so we believe we provide better metadata privacy than alternatives. SimpleX is designed to be truly distributed with no central server, and without any global user identities. This allows for high scalability at low cost, and also makes it virtually impossible to snoop on the network graph.</p>
 <p>The first application built on the platform is Simplex Chat, which is available for terminal (command line in Windows/Mac/Linux) and as iOS public beta - with Android app coming in a few weeks. The platform can easily support a private social network feed and a multitude of other services, which can be developed by the Simplex team or third party developers.</p>
 <p>SimpleX also allows people to host their own servers to have control of their chat data. SimpleX servers are exceptionally lightweight and require a single process with the initial memory footprint of under 20 Mb, which grows as the server adds in-memory queues (even with 10,000 queues it uses less than 50Mb, not accounting for messages). It should be considered though that while self-hosting the servers provides more control, it may reduce meta-data privacy, as it is easier to correlate the traffic of servers with small number of messages coming through.</p>
-<p>Further details on platform objectives and technical design are available <a href="https://github.com/simplex-chat/simplexmq/blob/master/protocol/overview-tjr/">in SimpleX platform overview</a>.</p>
+<p>Further details on platform objectives and technical design are available <a href="https://github.com/simplex-chat/simplexmq/blob/master/protocol/overview-tjr.md">in SimpleX platform overview</a>.</p>

        </div>
    </section>
@@ -46,7 +46,7 @@
 <p>We are building a new platform for distributed Internet applications where privacy of the messages <em>and</em> the network matter.</p>
 <p>We aim to provide the best possible protection of messages and metadata. Today there is no messaging application that works without global user identities, so we believe we provide better metadata privacy than alternatives. SimpleX is designed to be truly distributed with no central server, and without any global user identities. This allows for high scalability at low cost, and also makes it virtually impossible to snoop on the network graph.</p>
 <p>The first application built on the platform is Simplex Chat. The platform can easily support a private social network feed and a multitude of other services, which can be developed by the Simplex team or third party developers.</p>
-<p>Further details on platform objectives and technical design are available <a href="https://github.com/simplex-chat/simplexmq/blob/master/protocol/overview-tjr/">in SimpleX platform overview</a>.</p>
+<p>Further details on platform objectives and technical design are available <a href="https://github.com/simplex-chat/simplexmq/blob/master/protocol/overview-tjr.md">in SimpleX platform overview</a>.</p>
 <h2>Why we are building it</h2>
 <p>Evgeny (SimpleX Chat founder): I have been working on this platform for a long time to provide a place where all people can communicate freely with each other, without fear of persecution because of what they said and who they are connected with. Not sharing information about your connections is very important, particularly for people living in oppressive regimes. Because of the terrible conflict between Russia and Ukraine, people of both countries – I have friends and family there – could be at risk when sharing their opinions or just from being connected to people who were prosecuted. Every messenger app that knows who you are can end up sharing all of your connections with undesirable third parties, either as a result of a court order or as a result of attack - so even Signal, which has strong encryption, cannot protect your connection graph. I hope our messenger can help people living in the oppressive regimes to express their opinions without fear and risk of prosecution.</p>
 <h2>Huge thanks to our testers!</h2>
@@ -62,7 +62,7 @@
 <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="https://github.com/simplex-chat/simplex-chat/blob/stable/blog/20220112-simplex-chat-v1-released/">v1 announcement</a>.</p>
+<p>You can read more technical details in our recent <a href="https://github.com/simplex-chat/simplex-chat/blob/stable/blog/20220112-simplex-chat-v1-released.md">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>Install the apps and make a private connection!</h2>
 <p>Once you install the app, you can connect to anybody:</p>
@@ -40,7 +40,7 @@
            <h1>Instant notifications for SimpleX Chat mobile apps</h1>
 <p><strong>Published:</strong> April 04, 2022</p>
 <h2>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="https://github.com/simplex-chat/simplex-chat/blob/stable/blog/20220308-simplex-chat-mobile-apps/">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="https://github.com/simplex-chat/simplex-chat/blob/stable/blog/20220308-simplex-chat-mobile-apps.md">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>
@@ -79,7 +79,7 @@
 <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="https://github.com/simplex-chat/simplex-chat/blob/stable/blog/20220112-simplex-chat-v1-released/">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="https://github.com/simplex-chat/simplex-chat/blob/stable/blog/20220112-simplex-chat-v1-released.md">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>
@@ -50,7 +50,7 @@
 <p>To deliver mesages, instead of user IDs used by all other platforms, SimpleX has identifiers for message queues, separate for each of your contacts. In the current version of the protocol each queue is used until the contact is deleted. Later this year we plan to add queue rotation to the client protocol, so that even conversations don't have long term identifiers visible to the network. This design prevents leaking any users metadata on the application level.</p>
 <p>You define which server(s) to use <strong>to receive</strong> the messages, your contacts – the servers you use <strong>to send</strong> the messages to them. It means that every conversation is likely to use two different servers - one for each message direction.</p>
 <p>Only client devices store user profiles, contacts, groups, and messages sent with <strong>2-layer end-to-end encryption</strong>.</p>
-<p>Read more in <a href="https://github.com/simplex-chat/simplexmq/blob/master/protocol/overview-tjr/">SimpleX whitepaper</a>.</p>
+<p>Read more in <a href="https://github.com/simplex-chat/simplexmq/blob/master/protocol/overview-tjr.md">SimpleX whitepaper</a>.</p>
 <h2>How to connect with your contacts in SimpleX Chat</h2>
 <p>Once you install the app, you can connect to anybody:</p>
 <ol>
@@ -43,9 +43,9 @@
 <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="/img/images/20220524-clear-chat1.png" width="240"> <img src="/img/images/20220524-clear-chat2.png" width="240"></p>
-<p>See <a href="/blog/20220112-simplex-chat-v1-released/">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/">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/">whitepaper</a>.</p>
+<p>See <a href="https://github.com/simplex-chat/simplex-chat/blob/stable/blog/20220112-simplex-chat-v1-released.md">v1 announcement</a> for information on how SimpleX protects the security of the messages.</p>
+<p>See <a href="https://github.com/simplex-chat/simplex-chat/blob/stable/blog/20220511-simplex-chat-v2-images-files.md">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>
@@ -39,7 +39,7 @@
        <div class="bg-white py-12 px-6 sm:px-8 md:px-12 lg:px-16">
            <h1>SimpleX Chat v2.2 - the first messaging platform without user identities - 100% private by design!</h1>
 <p><strong>Published:</strong> June 4, 2022</p>
-<p>See <a href="/blog/20220511-simplex-chat-v2-images-files/">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 platfom, has no identity keys or any numbers that identify its users.</p>
+<p>See <a href="https://github.com/simplex-chat/simplex-chat/blob/stable/blog/20220511-simplex-chat-v2-images-files.md">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 platfom, has no identity keys or any numbers that identify its users.</p>
 <h2>New Privacy and Security settings in version 2.2</h2>
 <img src="/img/images/20220604-privacy-settings.png" width="480">
 <h3>Protect your chats</h3>
@@ -62,8 +62,8 @@
 <h3>There is more</h3>
 <p>You can discover additional features we are currently testing in Experimental Features - they will be announced later!</p>
 <h2>More information</h2>
-<p>See <a href="/blog/20220112-simplex-chat-v1-released/">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/">whitepaper</a>.</p>
+<p>See <a href="https://github.com/simplex-chat/simplex-chat/blob/stable/blog/20220112-simplex-chat-v1-released.md">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>
@@ -41,12 +41,12 @@
 <p><strong>Published:</strong> Jul 11, 2022</p>
 <h2>New in version 3</h2>
 <ul>
-<li><a href="#instant-notifications-for-ios">instant notifications for iOS</a></li>
-<li><a href="#database-export-and-import">database export and import</a></li>
-<li><a href="#protocol-privacy-and-performance-improvements">protocol privacy and performance improvements</a></li>
+<li><a href="https://github.com/simplex-chat/simplex-chat/blob/stable/blog/20220711-simplex-chat-v3-released-ios-notifications-audio-video-calls-database-export-import-protocol-improvements.md#instant-notifications-for-ios">instant notifications for iOS</a></li>
+<li><a href="https://github.com/simplex-chat/simplex-chat/blob/stable/blog/20220711-simplex-chat-v3-released-ios-notifications-audio-video-calls-database-export-import-protocol-improvements.md#database-export-and-import">database export and import</a></li>
+<li><a href="https://github.com/simplex-chat/simplex-chat/blob/stable/blog/20220711-simplex-chat-v3-released-ios-notifications-audio-video-calls-database-export-import-protocol-improvements.md#protocol-privacy-and-performance-improvements">protocol privacy and performance improvements</a></li>
 </ul>
 <h3>Instant notifications for iOS</h3>
-<p>I wrote previously about <a href="/blog/20220404-simplex-chat-instant-notifications/#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="https://github.com/simplex-chat/simplex-chat/blob/stable/blog/20220404-simplex-chat-instant-notifications.md#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>
@@ -76,7 +76,7 @@
 <h3>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="/blog/20220112-simplex-chat-v1-released/#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="https://github.com/simplex-chat/simplex-chat/blob/stable/blog/20220112-simplex-chat-v1-released.md#stable-protocol-implementation">since v1</a>, allowing us to evolve the protocols without any disruption to the users.</p>
 <h2>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>The first (and we believe the only) messaging platform without user identifiers of any kind - 100% private by design!</h3>
@@ -86,7 +86,7 @@
 <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>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="/blog/20220511-simplex-chat-v2-images-files/">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/">the whitepaper</a>.</p>
+<p>I wrote about it in <a href="https://github.com/simplex-chat/simplex-chat/blob/stable/blog/20220511-simplex-chat-v2-images-files.md">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>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>
@@ -41,16 +41,16 @@
 <p><strong>Published:</strong> Jul 23, 2022</p>
 <h2>What's new</h2>
 <ul>
-<li>terminal app: <a href="#terminall-app-access-to-messaging-servers-via-socks5-proxy--tor">access to messaging servers via SOCKS5 proxy</a> (e.g., Tor).</li>
-<li>mobile apps: <a href="#mobile-apps-join-and-leave-chat-groups">join and leave chat groups</a>.</li>
-<li><a href="#optimized-battery-and-traffic-usage---up-to-90x-reduction">optimized battery and traffic usage - up to 90x reduction!</a>.</li>
-<li><a href="#docker-configuration-for-self-hosted-smp-servers">two docker configurations for self-hosted SMP servers</a>.</li>
+<li>terminal app: <a href="https://github.com/simplex-chat/simplex-chat/blob/stable/blog/20220723-simplex-chat-v3.1-tor-groups-efficiency.md#terminall-app-access-to-messaging-servers-via-socks5-proxy--tor">access to messaging servers via SOCKS5 proxy</a> (e.g., Tor).</li>
+<li>mobile apps: <a href="https://github.com/simplex-chat/simplex-chat/blob/stable/blog/20220723-simplex-chat-v3.1-tor-groups-efficiency.md#mobile-apps-join-and-leave-chat-groups">join and leave chat groups</a>.</li>
+<li><a href="https://github.com/simplex-chat/simplex-chat/blob/stable/blog/20220723-simplex-chat-v3.1-tor-groups-efficiency.md#optimized-battery-and-traffic-usage---up-to-90x-reduction">optimized battery and traffic usage - up to 90x reduction!</a>.</li>
+<li><a href="https://github.com/simplex-chat/simplex-chat/blob/stable/blog/20220723-simplex-chat-v3.1-tor-groups-efficiency.md#docker-configuration-for-self-hosted-smp-servers">two docker configurations for self-hosted SMP servers</a>.</li>
 </ul>
 <h3>Terminall app: access to messaging servers via SOCKS5 proxy / Tor</h3>
 <img src="/img/images/20220723-tor.jpg" width="480">
 <p>While SMP protocol is focussed on protecting application-level meta-data by using pairwise connection identifiers instead of user identifiers (that are used by all other messaging platforms), there are scenarios when it is important for the users to protect their IP addresses from the servers - quite a few users have been somewhat disappointed that we didn't add it earlier.</p>
 <p>This release of terminal app supports accessing the servers via Tor, but the servers themselves are still available on their usual addresses. We are planning to add .onion addresses (v3 hidden service) to all messaging servers we provide, and the users who self-host the servers will also be able to have dual servers addresses - so that one party in the conversation can access the servers via .onion address without necessarily requiring that the other party uses Tor as well.</p>
-<p>To access SimpleX servers via Tor you need to install Tor proxy and run simplex-chat with <code>-x</code> option. See <a href="../docs/CLI/#access-messaging-servers-via-tor-beta">terminal app docs</a> for more information.</p>
+<p>To access SimpleX servers via Tor you need to install Tor proxy and run simplex-chat with <code>-x</code> option. See <a href="https://github.com/simplex-chat/simplex-chat/blob/stable/docs/CLI.md#access-messaging-servers-via-tor-beta">terminal app docs</a> for more information.</p>
 <p>As this is a beta release, to install it you need to use this command:</p>
 <pre><code class="language-sh">curl -o- https://raw.githubusercontent.com/simplex-chat/simplex-chat/stable/install.sh | sh -s -- v3.1.0-beta.0
 </code></pre>
@@ -79,9 +79,9 @@
 <h2>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>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="/blog/20220711-simplex-chat-v3-released-ios-notifications-audio-video-calls-database-export-import-protocol-improvements/#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="https://github.com/simplex-chat/simplex-chat/blob/stable/blog/20220711-simplex-chat-v3-released-ios-notifications-audio-video-calls-database-export-import-protocol-improvements.md#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>If SimpleX has no user identifiers, how can it deliver messages?</h3>
-<p>I wrote about it in <a href="/blog/20220511-simplex-chat-v2-images-files/">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/">the whitepaper</a>.</p>
+<p>I wrote about it in <a href="https://github.com/simplex-chat/simplex-chat/blob/stable/blog/20220511-simplex-chat-v2-images-files.md">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>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>
@@ -103,7 +103,7 @@
 <li>using Tor v3 hidden service addresses for messaging servers.</li>
 <li>passphrase-based local database encryption.</li>
 </ul>
-<p>SimpleX Chat <a href="../README/#privacy-technical-details-and-limitations">README page</a> has more details about it.</p>
+<p>SimpleX Chat <a href="https://github.com/simplex-chat/simplex-chat/blob/stable/README.md#privacy-technical-details-and-limitations">README page</a> has more details about it.</p>
 <h2>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>