mirror of
https://github.com/simplex-chat/simplex-chat.git
synced 2024-12-17 17:20:21 +01:00
deploy: 89782639c2
This commit is contained in:
epoberezkin
@@ -167,7 +167,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="./20220112-simplex-chat-v1-released.html">v1 announcement</a>.</p>
|
||||
<p>You can read more details in our recent <a href="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>
|
||||
|
||||
@@ -181,7 +181,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="./20220112-simplex-chat-v1-released.html">v1 announcement</a>.</p>
|
||||
<p>You can read more technical details in our recent <a href="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>
|
||||
|
||||
@@ -159,7 +159,7 @@
|
||||
<div class="bg-white py-6 sm:py-12 sm:px-8 md:px-16 lg:px-20"><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="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>
|
||||
@@ -198,7 +198,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="./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="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 "you have a new message", and the user will have to open the app to receive and see these messages. We are also investigating whether we can use "mutable-content" notifications that allow doing some processing when the notification arrives before showing it to the users.</p>
|
||||
|
||||
@@ -162,8 +162,8 @@
|
||||
<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="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>Read about SimpleX design in <a href="https://github.com/simplex-chat/simplexmq/blob/master/protocol/overview-tjr.md">whitepaper</a>.</p>
|
||||
</div>
|
||||
</section>
|
||||
|
||||
@@ -158,7 +158,7 @@
|
||||
<section class="container">
|
||||
<div class="bg-white py-6 sm:py-12 sm:px-8 md:px-16 lg:px-20"><h1 id="simplex-chat-v22-the-first-messaging-platform-without-user-identities-100percent-private-by-design" tabindex="-1">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="./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="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>
|
||||
@@ -181,7 +181,7 @@
|
||||
<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="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>
|
||||
|
||||
+3
-3
@@ -165,7 +165,7 @@
|
||||
<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="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>
|
||||
@@ -195,7 +195,7 @@
|
||||
<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="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>
|
||||
@@ -205,7 +205,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 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="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>
|
||||
|
||||
@@ -198,9 +198,9 @@
|
||||
<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="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="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 "defence in depth" security principles having multiple overlapping defensive mechanisms to protect users privacy and security:</p>
|
||||
<ul>
|
||||
|
||||
@@ -174,7 +174,7 @@
|
||||
</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&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="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&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>
|
||||
@@ -210,12 +210,12 @@
|
||||
<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="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="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="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>
|
||||
|
||||
@@ -204,10 +204,10 @@
|
||||
<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="../README.html#frequently-asked-questions">How SimpleX is different from Session, Matrix, Signal, etc.</a>.</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="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>
|
||||
<p>It is planned in October, and if there are no major issues we will publish this report straight away, otherwise - once we fix them.</p>
|
||||
|
||||
Binary file not shown.
|
After Width: | Height: | Size: 2.5 MiB |
Binary file not shown.
|
After Width: | Height: | Size: 320 KiB |
Binary file not shown.
|
After Width: | Height: | Size: 1016 KiB |
Binary file not shown.
|
After Width: | Height: | Size: 1.5 MiB |
File diff suppressed because one or more lines are too long
|
After Width: | Height: | Size: 332 KiB |
@@ -0,0 +1,12 @@
|
||||
<svg width="815" height="233" viewBox="0 0 815 233" fill="none" xmlns="http://www.w3.org/2000/svg">
|
||||
<g clip-path="url(#clip0)">
|
||||
<path fill-rule="evenodd" clip-rule="evenodd" d="M40.5683 66.9141C43.9954 66.9141 47.376 67.2323 50.7104 67.8687C54.0448 68.5051 57.2403 69.3234 60.2968 70.3235C63.3533 71.3236 66.2014 72.4601 68.8411 73.7329C71.4809 75.0058 73.9122 76.2786 76.1351 77.5515L66.132 96.0987L65.9952 95.9474C65.6001 95.5596 64.6732 94.9282 63.2144 94.0531C61.5472 93.053 59.4632 92.0074 56.9624 90.9164C54.4616 89.8254 51.7293 88.8708 48.7654 88.0525C45.8015 87.2342 42.8376 86.8251 39.8737 86.8251C31.723 86.8251 27.6476 89.5072 27.6476 94.8713C27.6476 96.5079 28.0876 97.8716 28.9675 98.9627C29.8474 100.054 31.1441 101.031 32.8576 101.895C34.5711 102.758 36.7245 103.554 39.318 104.281C41.9114 105.009 44.9216 105.827 48.3486 106.736C53.0723 108.009 57.3329 109.395 61.1304 110.896C64.9279 112.396 68.1465 114.26 70.7862 116.487C73.4259 118.715 75.4636 121.419 76.8993 124.602C78.3349 127.784 79.0527 131.602 79.0527 136.057C79.0527 141.512 78.0107 146.126 75.9267 149.899C73.8427 153.673 71.0872 156.718 67.6602 159.037C64.2332 161.355 60.2968 163.037 55.8509 164.083C51.4051 165.128 46.8203 165.651 42.0966 165.651C38.4844 165.651 34.7795 165.378 30.982 164.833C27.1845 164.287 23.4796 163.492 19.8674 162.446C16.2551 161.401 12.7587 160.15 9.37796 158.696C5.99726 157.241 2.87128 155.559 0 153.65L10.0032 134.148L10.1812 134.338C10.6877 134.825 11.8324 135.625 13.6154 136.739C15.6531 138.012 18.177 139.285 21.1872 140.558C24.1974 141.83 27.555 142.967 31.2599 143.967C34.9647 144.967 38.7159 145.467 42.5134 145.467C50.5715 145.467 54.6006 143.058 54.6006 138.239C54.6006 136.421 53.9985 134.921 52.7944 133.739C51.5903 132.557 49.9231 131.489 47.7928 130.534C45.6625 129.579 43.1386 128.693 40.221 127.875C37.3034 127.056 34.1311 126.147 30.7041 125.147C26.1657 123.783 22.2292 122.306 18.8948 120.715C15.5605 119.124 12.805 117.283 10.6284 115.192C8.45174 113.1 6.83086 110.691 5.76571 107.964C4.70056 105.236 4.16798 102.054 4.16798 98.4171C4.16798 93.3257 5.14051 88.8253 7.08557 84.9158C9.03063 81.0063 11.6703 77.7106 15.0047 75.0285C18.3391 72.3464 22.2061 70.3235 26.6056 68.9597C31.0051 67.5959 35.6594 66.9141 40.5683 66.9141ZM131.47 67.7323V164.56H108.685V67.7323H131.47ZM191.39 67.7323L216.954 118.328L242.657 67.7323H267.248V164.56H244.463V106.6L223.067 148.74H210.841L189.445 106.6V164.56H166.66V67.7323H191.39ZM419.925 67.7323V144.922H467.718V164.56H397.14V67.7323H419.925ZM560.072 67.7323V87.3706H514.78V106.191H553.681V124.329H514.78V144.922H561.323V164.56H491.995V67.7323H560.072ZM341.818 67.7323L343.378 67.7677C347.5 67.9563 351.31 68.8991 354.809 70.5962C358.745 72.5055 362.126 75.0058 364.951 78.097C367.776 81.1882 369.999 84.6885 371.62 88.598C373.24 92.5075 374.051 96.4624 374.051 100.463C374.051 104.736 373.287 108.827 371.758 112.737C370.23 116.646 368.1 120.147 365.368 123.238C362.635 126.329 359.324 128.784 355.434 130.602C351.976 132.218 348.189 133.116 344.072 133.296L342.513 133.33H322.507V164.56H299.722V67.7323H341.818ZM340.29 87.3706H322.507V113.828H341.124C343.81 113.828 346.125 112.691 348.07 110.418C350.016 108.145 350.988 104.827 350.988 100.463C350.988 98.1898 350.687 96.2351 350.085 94.5986C349.483 92.9621 348.672 91.5983 347.654 90.5073C346.635 89.4163 345.477 88.6207 344.18 88.1207C342.884 87.6206 341.587 87.3706 340.29 87.3706Z" fill="#062D56"/>
|
||||
<path fill-rule="evenodd" clip-rule="evenodd" d="M642.628 136.08L680.309 173.782L699.513 154.567L699.506 154.561L737.917 116.134L700.236 78.4367L700.243 78.4334L681.404 59.5826L642.993 98.014L642.99 98.0104L681.401 59.5829L643.725 21.881L662.929 2.6652L700.605 40.3673L739.016 1.93511L757.855 20.7859L719.443 59.2176L757.121 96.918L795.533 58.4875L814.373 77.3382L775.959 115.768L813.643 153.471L794.439 172.687L756.756 134.984L718.348 173.415L756.031 211.119L736.827 230.335L699.144 192.63L660.74 231.065L641.901 212.214L680.306 173.78L642.625 136.083L642.628 136.08Z" fill="#07B4B9"/>
|
||||
<path fill-rule="evenodd" clip-rule="evenodd" d="M604.77 59.7651L642.446 97.4664L680.856 59.035L699.696 77.8858L661.285 116.317L698.966 154.019L679.762 173.235L642.081 135.532L603.675 173.965L584.836 155.114L623.243 116.682L585.566 78.9809L604.77 59.7651Z" fill="#062D56"/>
|
||||
</g>
|
||||
<defs>
|
||||
<clipPath id="clip0">
|
||||
<rect width="815" height="233" fill="white"/>
|
||||
</clipPath>
|
||||
</defs>
|
||||
</svg>
|
||||
|
After Width: | Height: | Size: 4.3 KiB |
@@ -0,0 +1,16 @@
|
||||
<svg width="830" height="120" viewBox="0 0 830 120" fill="none" xmlns="http://www.w3.org/2000/svg">
|
||||
<rect width="830" height="120" fill="white"/>
|
||||
<path d="M491.857 60.3502C491.857 57.8277 492.323 55.3636 493.253 52.9576C494.222 50.5128 495.618 48.3008 497.44 46.3217C499.262 44.3426 501.472 42.7709 504.069 41.6067C506.706 40.4037 509.671 39.8022 512.967 39.8022C516.921 39.8022 520.371 40.6366 523.318 42.3053C526.264 43.9351 528.455 46.1083 529.889 48.8247L521.224 54.9949C520.72 53.6367 519.984 52.5889 519.015 51.8516C518.084 51.1143 517.057 50.6098 515.932 50.3381C514.847 50.0277 513.781 49.8725 512.734 49.8725C510.563 49.8725 508.78 50.4158 507.384 51.5023C506.027 52.5889 505.019 53.9665 504.36 55.6352C503.701 57.2651 503.372 58.9531 503.372 60.6994C503.372 62.6009 503.74 64.386 504.476 66.0547C505.252 67.7233 506.337 69.0816 507.733 70.1293C509.167 71.1383 510.873 71.6428 512.85 71.6428C513.897 71.6428 514.963 71.4875 516.049 71.1771C517.134 70.8278 518.123 70.2846 519.015 69.5472C519.906 68.8099 520.585 67.8204 521.05 66.5786L530.296 72.1084C529.482 74.1264 528.125 75.8533 526.225 77.2891C524.326 78.7249 522.174 79.8309 519.771 80.607C517.367 81.3443 514.983 81.713 512.618 81.713C509.555 81.713 506.744 81.1115 504.186 79.9085C501.666 78.6667 499.475 77.0368 497.615 75.0189C495.792 72.9622 494.377 70.6726 493.369 68.1502C492.361 65.589 491.857 62.989 491.857 60.3502Z" fill="#FFC513"/>
|
||||
<path d="M580.156 40.0351V81.3637H568.816V65.1815H554.976V81.3637H543.637V40.0351H554.976V55.2859H568.816V40.0351H580.156Z" fill="#FFC513"/>
|
||||
<path d="M606.092 40.0351H618.769L631.912 81.3637H620.397L617.897 73.2726H606.906L604.464 81.3637H592.891L606.092 40.0351ZM616.094 65.7054L612.431 51.1531L608.593 65.7054H616.094Z" fill="#FFC513"/>
|
||||
<path d="M673 49.9307H661.137V81.3637H649.797V49.9307H637.876V40.0351H673V49.9307Z" fill="#FFC513"/>
|
||||
<path fill-rule="evenodd" clip-rule="evenodd" d="M175.155 40.1228C176.604 40.1228 178.034 40.2546 179.444 40.5182C180.854 40.7818 182.205 41.1208 183.498 41.535C184.79 41.9493 185.994 42.42 187.111 42.9473C188.227 43.4745 189.255 44.0017 190.195 44.529L185.965 52.2115L185.907 52.1488C185.74 51.9882 185.348 51.7266 184.731 51.3642C184.026 50.9499 183.145 50.5168 182.088 50.0649C181.03 49.613 179.875 49.2176 178.621 48.8786C177.368 48.5397 176.115 48.3702 174.861 48.3702C171.415 48.3702 169.691 49.4812 169.691 51.7031C169.691 52.381 169.877 52.9459 170.249 53.3978C170.621 53.8497 171.17 54.2545 171.894 54.6123C172.619 54.9701 173.53 55.2996 174.626 55.6009C175.723 55.9021 176.996 56.2411 178.445 56.6177C180.443 57.1449 182.244 57.7192 183.85 58.3406C185.456 58.962 186.817 59.734 187.933 60.6567C189.049 61.5793 189.911 62.6997 190.518 64.0178C191.125 65.3358 191.429 66.9175 191.429 68.7629C191.429 71.0224 190.988 72.9337 190.107 74.4965C189.226 76.0594 188.06 77.321 186.611 78.2813C185.162 79.2416 183.498 79.9383 181.618 80.3714C179.738 80.8045 177.799 81.021 175.801 81.021C174.274 81.021 172.707 80.9081 171.101 80.6821C169.495 80.4561 167.929 80.1266 166.401 79.6935C164.874 79.2605 163.395 78.7426 161.966 78.1401C160.536 77.5375 159.214 76.8408 158 76.05L162.23 67.972L162.305 68.0506C162.519 68.2524 163.004 68.584 163.758 69.0453C164.619 69.5725 165.686 70.0998 166.959 70.627C168.232 71.1542 169.652 71.625 171.219 72.0392C172.785 72.4535 174.372 72.6606 175.978 72.6606C179.385 72.6606 181.089 71.6626 181.089 69.6667C181.089 68.9135 180.834 68.2921 180.325 67.8025C179.816 67.313 179.111 66.8705 178.21 66.475C177.309 66.0796 176.242 65.7124 175.008 65.3735C173.774 65.0346 172.433 64.658 170.984 64.2437C169.065 63.6788 167.4 63.0669 165.99 62.4078C164.58 61.7488 163.415 60.9862 162.494 60.12C161.574 59.2538 160.889 58.2559 160.438 57.1261C159.988 55.9963 159.763 54.6782 159.763 53.1718C159.763 51.0629 160.174 49.1987 160.996 47.5794C161.819 45.96 162.935 44.5949 164.345 43.4839C165.755 42.373 167.39 41.535 169.251 40.9701C171.111 40.4052 173.079 40.1228 175.155 40.1228ZM213.594 40.4617V80.5691H203.959V40.4617H213.594ZM238.933 40.4617L249.743 61.4193L260.611 40.4617H271.01V80.5691H261.375V56.5612L252.328 74.0164H247.158L238.11 56.5612V80.5691H228.475V40.4617H238.933ZM335.572 40.4617V72.4347H355.782V80.5691H325.937V40.4617H335.572ZM394.836 40.4617V48.5962H375.683V56.3917H392.133V63.9048H375.683V72.4347H395.365V80.5691H366.048V40.4617H394.836ZM302.544 40.4617L303.203 40.4764C304.946 40.5545 306.557 40.945 308.037 41.648C309.701 42.4389 311.131 43.4745 312.326 44.7549C313.52 46.0353 314.46 47.4852 315.146 49.1046C315.831 50.724 316.174 52.3621 316.174 54.0192C316.174 55.7892 315.851 57.4838 315.204 59.1032C314.558 60.7226 313.657 62.1724 312.502 63.4529C311.346 64.7333 309.946 65.7501 308.301 66.5033C306.839 67.1728 305.237 67.5447 303.497 67.6191L302.837 67.6331H294.377V80.5691H284.742V40.4617H302.544ZM301.897 48.5962H294.377V59.5551H302.25C303.386 59.5551 304.365 59.0844 305.187 58.1429C306.01 57.2014 306.421 55.8268 306.421 54.0192C306.421 53.0777 306.294 52.268 306.039 51.5901C305.785 50.9123 305.442 50.3474 305.011 49.8954C304.58 49.4435 304.091 49.114 303.542 48.9069C302.994 48.6998 302.446 48.5962 301.897 48.5962Z" fill="#030749"/>
|
||||
<path fill-rule="evenodd" clip-rule="evenodd" d="M412.851 40.4402L426.421 53.7412L440.37 40.0704L447.155 46.721L433.206 60.3915L446.778 73.6928L439.804 80.5282L426.232 67.2268L412.285 80.898L405.5 74.2475L419.447 60.5765L405.877 47.2756L412.851 40.4402Z" fill="#030749"/>
|
||||
<path fill-rule="evenodd" clip-rule="evenodd" d="M439.694 80.6528L446.614 73.8707L446.611 73.8687L460.452 60.3059L446.875 47.0009L446.877 46.9997L440.089 40.3464L426.513 27.0398L433.432 20.2577L447.007 33.5645L460.848 20L467.636 26.6533L453.795 40.2176L467.371 53.5238L481.212 39.9599L488 46.6132L474.159 60.1769L487.737 73.4841L480.818 80.2663L467.24 66.959L453.401 80.5231L466.978 93.8306L460.059 100.613L446.481 87.3051L432.643 100.87L425.855 94.2171L439.694 80.6528Z" fill="url(#paint0_linear_301_112)"/>
|
||||
<defs>
|
||||
<linearGradient id="paint0_linear_301_112" x1="436.651" y1="18.3496" x2="428.967" y2="94.7975" gradientUnits="userSpaceOnUse">
|
||||
<stop stop-color="#01F1FF"/>
|
||||
<stop offset="1" stop-color="#0197FF"/>
|
||||
</linearGradient>
|
||||
</defs>
|
||||
</svg>
|
||||
|
After Width: | Height: | Size: 6.0 KiB |
Binary file not shown.
|
After Width: | Height: | Size: 5.7 MiB |
Reference in New Issue
Block a user