mirror of
https://github.com/simplex-chat/simplex-chat.git
synced 2025-06-28 20:29:53 +00:00
deploy: d993381d31
This commit is contained in:
parent
b4f2d46b18
commit
c444bc44eb
89 changed files with 1366 additions and 2302 deletions
File diff suppressed because one or more lines are too long
File diff suppressed because one or more lines are too long
File diff suppressed because one or more lines are too long
File diff suppressed because one or more lines are too long
File diff suppressed because one or more lines are too long
File diff suppressed because one or more lines are too long
File diff suppressed because one or more lines are too long
File diff suppressed because one or more lines are too long
File diff suppressed because one or more lines are too long
File diff suppressed because one or more lines are too long
File diff suppressed because one or more lines are too long
File diff suppressed because one or more lines are too long
File diff suppressed because one or more lines are too long
File diff suppressed because one or more lines are too long
File diff suppressed because one or more lines are too long
File diff suppressed because one or more lines are too long
File diff suppressed because one or more lines are too long
File diff suppressed because one or more lines are too long
File diff suppressed because one or more lines are too long
File diff suppressed because one or more lines are too long
File diff suppressed because one or more lines are too long
File diff suppressed because one or more lines are too long
File diff suppressed because one or more lines are too long
File diff suppressed because one or more lines are too long
File diff suppressed because one or more lines are too long
File diff suppressed because one or more lines are too long
File diff suppressed because one or more lines are too long
File diff suppressed because one or more lines are too long
File diff suppressed because one or more lines are too long
File diff suppressed because one or more lines are too long
File diff suppressed because one or more lines are too long
File diff suppressed because one or more lines are too long
File diff suppressed because one or more lines are too long
File diff suppressed because one or more lines are too long
File diff suppressed because one or more lines are too long
File diff suppressed because one or more lines are too long
|
@ -7,7 +7,7 @@
|
|||
<li>réduction de l'utilisation de la batterie.</li>
|
||||
<li>noms de fichiers privés.</li>
|
||||
</ul>
|
||||
<p>Nous avons également ajouté <a href="undefined">l'interface en italien</a>, grâce à nos utilisateurs et à Weblate !</p>
|
||||
<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="/blog/20230103-simplex-chat-v4.4-disappearing-messages.html">SimpleX Chat v4.4 publié</a></p>
|
||||
<ul>
|
||||
<li>messages éphèméres.</li>
|
||||
|
@ -15,7 +15,7 @@
|
|||
<li>vérification de la sécurité de la connexion.</li>
|
||||
<li>images animées et autocollants - maintenant aussi sur iOS.</li>
|
||||
</ul>
|
||||
<p>Nous avons également ajouté <a href="undefined">l'interface en français</a>, grâce à nos utilisateurs et à Weblate !</p>
|
||||
<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="/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>
|
||||
|
|
|
@ -217,10 +217,6 @@ h6 {
|
|||
float: right;
|
||||
margin-left: 3rem;
|
||||
}
|
||||
|
||||
#article .float-right{
|
||||
margin-left: 3rem;
|
||||
}
|
||||
}
|
||||
|
||||
@media (max-width:768px) {
|
||||
|
|
|
@ -764,15 +764,14 @@ p a{
|
|||
}
|
||||
|
||||
.tooltip-title{
|
||||
margin: 0 !important;
|
||||
margin-bottom: 0.5rem !important;
|
||||
color: #0197FF !important;
|
||||
font-weight: 600 !important;
|
||||
font-size: 1.1rem !important;
|
||||
margin-bottom: 0.5rem;
|
||||
color: #0197FF;
|
||||
font-weight: 600;
|
||||
font-size: 1.1rem;
|
||||
}
|
||||
|
||||
.dark .tooltip-title{
|
||||
color: #70F0F9 !important;
|
||||
color: #70F0F9;
|
||||
}
|
||||
|
||||
.glossary-tooltip .read-more-btn{
|
||||
|
@ -855,18 +854,13 @@ p a{
|
|||
}
|
||||
|
||||
.glossary-overlay .overlay-card .overlay-title{
|
||||
font-size: 1.875rem !important;
|
||||
line-height: 2.25rem !important;
|
||||
font-weight: 700 !important;
|
||||
margin: 0 !important;
|
||||
padding: 0 !important;
|
||||
margin-bottom: 1.5rem !important;
|
||||
--tw-text-opacity: 1 !important;
|
||||
color: rgb(1 151 255 / var(--tw-text-opacity)) !important;
|
||||
}
|
||||
|
||||
.glossary-overlay .overlay-card .overlay-title::after{
|
||||
background-color: transparent !important;
|
||||
font-size: 1.875rem;
|
||||
line-height: 2.25rem;
|
||||
font-weight: 700;
|
||||
margin-bottom: 1rem;
|
||||
margin-bottom: 1.5rem;
|
||||
--tw-text-opacity: 1;
|
||||
color: rgb(1 151 255 / var(--tw-text-opacity));
|
||||
}
|
||||
|
||||
.glossary-overlay .overlay-card .overlay-content{
|
||||
|
@ -882,10 +876,6 @@ p a{
|
|||
color: #fff;
|
||||
}
|
||||
|
||||
.glossary-overlay .overlay-card .overlay-content p{
|
||||
margin: 0 !important;
|
||||
}
|
||||
|
||||
.close-overlay-btn{
|
||||
fill: #3F484B;
|
||||
position: fixed;
|
||||
|
|
File diff suppressed because one or more lines are too long
File diff suppressed because one or more lines are too long
File diff suppressed because one or more lines are too long
File diff suppressed because one or more lines are too long
File diff suppressed because one or more lines are too long
File diff suppressed because one or more lines are too long
File diff suppressed because one or more lines are too long
File diff suppressed because one or more lines are too long
File diff suppressed because one or more lines are too long
File diff suppressed because one or more lines are too long
File diff suppressed because one or more lines are too long
File diff suppressed because one or more lines are too long
File diff suppressed because one or more lines are too long
File diff suppressed because one or more lines are too long
File diff suppressed because one or more lines are too long
File diff suppressed because one or more lines are too long
File diff suppressed because one or more lines are too long
File diff suppressed because one or more lines are too long
File diff suppressed because one or more lines are too long
File diff suppressed because one or more lines are too long
File diff suppressed because one or more lines are too long
File diff suppressed because one or more lines are too long
File diff suppressed because one or more lines are too long
File diff suppressed because one or more lines are too long
File diff suppressed because one or more lines are too long
File diff suppressed because one or more lines are too long
File diff suppressed because one or more lines are too long
File diff suppressed because one or more lines are too long
File diff suppressed because one or more lines are too long
File diff suppressed because one or more lines are too long
File diff suppressed because one or more lines are too long
File diff suppressed because one or more lines are too long
File diff suppressed because one or more lines are too long
File diff suppressed because one or more lines are too long
File diff suppressed because one or more lines are too long
File diff suppressed because one or more lines are too long
103
docs/server.html
103
docs/server.html
File diff suppressed because one or more lines are too long
File diff suppressed because one or more lines are too long
File diff suppressed because one or more lines are too long
File diff suppressed because one or more lines are too long
File diff suppressed because one or more lines are too long
File diff suppressed because one or more lines are too long
File diff suppressed because one or more lines are too long
File diff suppressed because one or more lines are too long
358
feed.atom
358
feed.atom
|
@ -78,10 +78,10 @@
|
|||
<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="https://simplex.chat/images/groups.gif" alt="simplex-chat" /></p>
|
||||
<p><img src="https://simplex.chat/blog/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="https://simplex.chat/images/files.gif" alt="simplex-chat" /></p>
|
||||
<p><img src="https://simplex.chat/blog/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>
|
||||
|
@ -464,13 +464,13 @@
|
|||
<p><strong>Published:</strong> Jul 11, 2022</p>
|
||||
<h2 id="new-in-version-3" tabindex="-1">New in version 3</h2>
|
||||
<ul>
|
||||
<li><a href="https://simplex.chat/blog/undefined">instant notifications for iOS</a></li>
|
||||
<li><a href="https://simplex.chat/blog/undefined">end-to-end encrypted audio/video calls</a></li>
|
||||
<li><a href="https://simplex.chat/blog/undefined">database export and import</a></li>
|
||||
<li><a href="https://simplex.chat/blog/undefined">protocol privacy and performance improvements</a></li>
|
||||
<li><a href="https://simplex.chat/blog/20220711-simplex-chat-v3-released-ios-notifications-audio-video-calls-database-export-import-protocol-improvements.html#instant-notifications-for-ios">instant notifications for iOS</a></li>
|
||||
<li><a href="https://simplex.chat/blog/20220711-simplex-chat-v3-released-ios-notifications-audio-video-calls-database-export-import-protocol-improvements.html#end-to-end-encrypted-audiovideo-calls">end-to-end encrypted audio/video calls</a></li>
|
||||
<li><a href="https://simplex.chat/blog/20220711-simplex-chat-v3-released-ios-notifications-audio-video-calls-database-export-import-protocol-improvements.html#database-export-and-import">database export and import</a></li>
|
||||
<li><a href="https://simplex.chat/blog/20220711-simplex-chat-v3-released-ios-notifications-audio-video-calls-database-export-import-protocol-improvements.html#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="https://simplex.chat/blog/20220404-simplex-chat-instant-notifications.html">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://simplex.chat/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>
|
||||
|
@ -500,7 +500,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="https://simplex.chat/blog/20220112-simplex-chat-v1-released.html">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://simplex.chat/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>
|
||||
|
@ -537,10 +537,10 @@
|
|||
<p><strong>Published:</strong> Jul 23, 2022</p>
|
||||
<h2 id="whats-new" tabindex="-1">What's new</h2>
|
||||
<ul>
|
||||
<li>terminal app: <a href="https://simplex.chat/blog/undefined">access to messaging servers via SOCKS5 proxy</a> (e.g., Tor).</li>
|
||||
<li>mobile apps: <a href="https://simplex.chat/blog/undefined">join and leave chat groups</a>.</li>
|
||||
<li><a href="https://simplex.chat/blog/undefined">optimized battery and traffic usage - up to 90x reduction!</a>.</li>
|
||||
<li><a href="https://simplex.chat/blog/undefined">two docker configurations for self-hosted SMP servers</a>.</li>
|
||||
<li>terminal app: <a href="https://simplex.chat/blog/20220723-simplex-chat-v3.1-tor-groups-efficiency.html#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://simplex.chat/blog/20220723-simplex-chat-v3.1-tor-groups-efficiency.html#mobile-apps-join-and-leave-chat-groups">join and leave chat groups</a>.</li>
|
||||
<li><a href="https://simplex.chat/blog/20220723-simplex-chat-v3.1-tor-groups-efficiency.html#optimized-battery-and-traffic-usage---up-to-90x-reduction">optimized battery and traffic usage - up to 90x reduction!</a>.</li>
|
||||
<li><a href="https://simplex.chat/blog/20220723-simplex-chat-v3.1-tor-groups-efficiency.html#docker-configuration-for-self-hosted-smp-servers">two docker configurations for self-hosted SMP servers</a>.</li>
|
||||
</ul>
|
||||
<h3 id="terminall-app-access-to-messaging-servers-via-socks5-proxy-tor" tabindex="-1">Terminall app: access to messaging servers via SOCKS5 proxy / Tor</h3>
|
||||
<img src="https://simplex.chat/blog/images/20220723-tor.jpg" width="480" />
|
||||
|
@ -575,7 +575,7 @@
|
|||
<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="https://simplex.chat/blog/20220711-simplex-chat-v3-released-ios-notifications-audio-video-calls-database-export-import-protocol-improvements.html">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://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">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="https://simplex.chat/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>
|
||||
|
@ -626,12 +626,12 @@
|
|||
<p><strong>Published:</strong> Aug 8, 2022</p>
|
||||
<h2 id="whats-new" tabindex="-1">What's new</h2>
|
||||
<ul>
|
||||
<li><a href="https://simplex.chat/blog/undefined">secret chat groups</a>!</li>
|
||||
<li><a href="https://simplex.chat/blog/undefined">access to messaging servers via Tor</a></li>
|
||||
<li><a href="https://simplex.chat/blog/undefined">advanced network settings</a></li>
|
||||
<li><a href="https://simplex.chat/blog/undefined">published chat protocol</a></li>
|
||||
<li><a href="https://simplex.chat/blog/undefined">new app icons</a></li>
|
||||
<li><a href="https://simplex.chat/blog/undefined">other changes since v3</a>:
|
||||
<li><a href="https://simplex.chat/blog/20220808-simplex-chat-v3.1-chat-groups.html#secret-chat-groups">secret chat groups</a>!</li>
|
||||
<li><a href="https://simplex.chat/blog/20220808-simplex-chat-v3.1-chat-groups.html#access-messaging-servers-via-tor">access to messaging servers via Tor</a></li>
|
||||
<li><a href="https://simplex.chat/blog/20220808-simplex-chat-v3.1-chat-groups.html#advanced-network-settings">advanced network settings</a></li>
|
||||
<li><a href="https://simplex.chat/blog/20220808-simplex-chat-v3.1-chat-groups.html#published-chat-protocol">published chat protocol</a></li>
|
||||
<li><a href="https://simplex.chat/blog/20220808-simplex-chat-v3.1-chat-groups.html#new-app-icons">new app icons</a></li>
|
||||
<li><a href="https://simplex.chat/blog/20220808-simplex-chat-v3.1-chat-groups.html#other-changes-since-v3">other changes since v3</a>:
|
||||
<ul>
|
||||
<li>optimized battery and traffic usage - up to 90x reduction!</li>
|
||||
<li>two docker configurations for self-hosted SMP servers</li>
|
||||
|
@ -679,9 +679,9 @@
|
|||
<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="https://simplex.chat/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="https://simplex.chat/blog/20220511-simplex-chat-v2-images-files.html">How can SimpleX deliver messages without user identifiers</a>.</p>
|
||||
<p><a href="https://simplex.chat/blog/20220711-simplex-chat-v3-released-ios-notifications-audio-video-calls-database-export-import-protocol-improvements.html">What are the risks to have identifiers assigned to the users</a>.</p>
|
||||
<p><a href="https://simplex.chat/blog/20220723-simplex-chat-v3.1-tor-groups-efficiency.html">Technical details and limitations</a>.</p>
|
||||
<p><a href="https://simplex.chat/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="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">What are the risks to have identifiers assigned to the users</a>.</p>
|
||||
<p><a href="https://simplex.chat/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>
|
||||
|
@ -714,11 +714,11 @@
|
|||
<p><strong>Published:</strong> Sep 1, 2022</p>
|
||||
<h2 id="whats-new" tabindex="-1">What's new</h2>
|
||||
<ul>
|
||||
<li><a href="https://simplex.chat/blog/undefined">Incognito mode</a></li>
|
||||
<li><a href="https://simplex.chat/blog/undefined">assign names to your contacts</a></li>
|
||||
<li><a href="https://simplex.chat/blog/undefined">use .onion server addresses with Tor</a></li>
|
||||
<li><a href="https://simplex.chat/blog/undefined">endless scrolling and search in chats</a></li>
|
||||
<li><a href="https://simplex.chat/blog/undefined">choose accent color and dark mode</a></li>
|
||||
<li><a href="https://simplex.chat/blog/20220901-simplex-chat-v3.2-incognito-mode.html#incognito-mode">Incognito mode</a></li>
|
||||
<li><a href="https://simplex.chat/blog/20220901-simplex-chat-v3.2-incognito-mode.html#assign-names-to-your-contacts">assign names to your contacts</a></li>
|
||||
<li><a href="https://simplex.chat/blog/20220901-simplex-chat-v3.2-incognito-mode.html#using-onion-server-addresses-with-tor">use .onion server addresses with Tor</a></li>
|
||||
<li><a href="https://simplex.chat/blog/20220901-simplex-chat-v3.2-incognito-mode.html#endless-scrolling-and-search-in-chats">endless scrolling and search in chats</a></li>
|
||||
<li><a href="https://simplex.chat/blog/20220901-simplex-chat-v3.2-incognito-mode.html#choose-accent-color-and-dark-mode">choose accent color and dark mode</a></li>
|
||||
<li>disable notifications per contact / group</li>
|
||||
<li>on Android:
|
||||
<ul>
|
||||
|
@ -727,7 +727,7 @@
|
|||
</ul>
|
||||
</li>
|
||||
</ul>
|
||||
<p><a href="https://simplex.chat/blog/undefined">Implementation audit is arranged for October</a>!</p>
|
||||
<p><a href="https://simplex.chat/blog/20220901-simplex-chat-v3.2-incognito-mode.html#we-ask-you-to-help-us-pay-for-3rd-party-security-audit">Implementation audit is arranged for October</a>!</p>
|
||||
<h3 id="incognito-mode" tabindex="-1">Incognito mode</h3>
|
||||
<p><img src="https://simplex.chat/blog/images/20220901-incognito1.png" width="330" /> <img src="https://simplex.chat/blog/images/20220901-incognito2.png" width="330" /> <img src="https://simplex.chat/blog/images/20220901-incognito3.png" width="330" /></p>
|
||||
<p><em>SimpleX is already private, so why do we need an incognito mode</em>, you may ask.</p>
|
||||
|
@ -758,9 +758,9 @@
|
|||
<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="https://simplex.chat/blog/20220511-simplex-chat-v2-images-files.html">How can SimpleX deliver messages without user identifiers</a>.</p>
|
||||
<p><a href="https://simplex.chat/blog/20220711-simplex-chat-v3-released-ios-notifications-audio-video-calls-database-export-import-protocol-improvements.html">What are the risks to have identifiers assigned to the users</a>.</p>
|
||||
<p><a href="https://simplex.chat/blog/20220723-simplex-chat-v3.1-tor-groups-efficiency.html">Technical details and limitations</a>.</p>
|
||||
<p><a href="https://simplex.chat/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="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">What are the risks to have identifiers assigned to the users</a>.</p>
|
||||
<p><a href="https://simplex.chat/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>
|
||||
|
@ -793,24 +793,24 @@
|
|||
<p><strong>Published:</strong> Sep 28, 2022</p>
|
||||
<h2 id="whats-new-in-v4" tabindex="-1">What's new in v4</h2>
|
||||
<ul>
|
||||
<li><a href="https://simplex.chat/blog/undefined">encrypted local chat database</a>.</li>
|
||||
<li><a href="https://simplex.chat/blog/undefined">support for self-hosted WebRTC ICE servers</a>.</li>
|
||||
<li><a href="https://simplex.chat/blog/undefined">improved stability of creating new connections: more reliable groups, files and contacts</a>.</li>
|
||||
<li><a href="https://simplex.chat/blog/undefined">deleting files and media</a>.</li>
|
||||
<li><a href="https://simplex.chat/blog/undefined">For developers - TypeScript SDK for integrating with SimpleX Chat</a> (e.g., chat bots or chat assistants).</li>
|
||||
<li><a href="https://simplex.chat/blog/20220928-simplex-chat-v4-encrypted-database.html#local-chat-database-encryption">encrypted local chat database</a>.</li>
|
||||
<li><a href="https://simplex.chat/blog/20220928-simplex-chat-v4-encrypted-database.html#self-hosted-webrtc-ice-servers">support for self-hosted WebRTC ICE servers</a>.</li>
|
||||
<li><a href="https://simplex.chat/blog/20220928-simplex-chat-v4-encrypted-database.html#improved-stability-of-creating-new-connections">improved stability of creating new connections: more reliable groups, files and contacts</a>.</li>
|
||||
<li><a href="https://simplex.chat/blog/20220928-simplex-chat-v4-encrypted-database.html#deleting-files-and-media">deleting files and media</a>.</li>
|
||||
<li><a href="https://simplex.chat/blog/20220928-simplex-chat-v4-encrypted-database.html#for-developers---typescript-sdk-for-integrating-with-simplex-chat">For developers - TypeScript SDK for integrating with SimpleX Chat</a> (e.g., chat bots or chat assistants).</li>
|
||||
<li>animated images in Android app.</li>
|
||||
<li>disable messages per contact / group in terminal app (it is already supported in mobile apps).</li>
|
||||
</ul>
|
||||
<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="https://simplex.chat/blog/20220808-simplex-chat-v3.1-chat-groups.html">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="https://simplex.chat/blog/20220808-simplex-chat-v3.1-chat-groups.html">v3.1</a> and <a href="https://simplex.chat/blog/20220901-simplex-chat-v3.2-incognito-mode.html">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="https://simplex.chat/blog/20220901-simplex-chat-v3.2-incognito-mode.html">v3.2</a> announcement).</li>
|
||||
<li>secret chat groups (see details in <a href="https://simplex.chat/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="https://simplex.chat/blog/20220808-simplex-chat-v3.1-chat-groups.html#access-messaging-servers-via-tor">v3.1</a> and <a href="https://simplex.chat/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="https://simplex.chat/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>
|
||||
<p><a href="https://simplex.chat/blog/undefined">Implementation audit is arranged for October</a>!</p>
|
||||
<p><a href="https://simplex.chat/blog/20220928-simplex-chat-v4-encrypted-database.html#we-ask-you-to-help-us-pay-for-3rd-party-security-audit">Implementation audit is arranged for October</a>!</p>
|
||||
<h3 id="local-chat-database-encryption" tabindex="-1">Local chat database encryption</h3>
|
||||
<img src="https://simplex.chat/blog/images/20220928-passphrase.png" width="330" />
|
||||
<p>SimpleX Chat focus has always been on protecting messages in delivery, not when they are stored on the device. This release changes it - now all messages that you receive and send are stored on the device encrypted with <a href="https://github.com/sqlcipher/sqlcipher">SQLCipher</a>.</p>
|
||||
|
@ -819,7 +819,7 @@
|
|||
<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="https://simplex.chat/blog/images/20220928-ice-servers.png" width="330" />
|
||||
<p>You could make audio and video calls via SimpleX Chat WebRTC servers since <a href="https://simplex.chat/blog/20220711-simplex-chat-v3-released-ios-notifications-audio-video-calls-database-export-import-protocol-improvements.html">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="https://simplex.chat/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>
|
||||
|
@ -859,9 +859,9 @@
|
|||
<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="https://simplex.chat/blog/20220511-simplex-chat-v2-images-files.html">How can SimpleX deliver messages without user identifiers</a>.</p>
|
||||
<p><a href="https://simplex.chat/blog/20220711-simplex-chat-v3-released-ios-notifications-audio-video-calls-database-export-import-protocol-improvements.html">What are the risks to have identifiers assigned to the users</a>.</p>
|
||||
<p><a href="https://simplex.chat/blog/20220723-simplex-chat-v3.1-tor-groups-efficiency.html">Technical details and limitations</a>.</p>
|
||||
<p><a href="https://simplex.chat/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="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">What are the risks to have identifiers assigned to the users</a>.</p>
|
||||
<p><a href="https://simplex.chat/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>
|
||||
|
@ -990,9 +990,9 @@
|
|||
<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="https://simplex.chat/blog/20220511-simplex-chat-v2-images-files.html">How can SimpleX deliver messages without user identifiers</a>.</p>
|
||||
<p><a href="https://simplex.chat/blog/20220711-simplex-chat-v3-released-ios-notifications-audio-video-calls-database-export-import-protocol-improvements.html">What are the risks to have identifiers assigned to the users</a>.</p>
|
||||
<p><a href="https://simplex.chat/blog/20220723-simplex-chat-v3.1-tor-groups-efficiency.html">Technical details and limitations</a>.</p>
|
||||
<p><a href="https://simplex.chat/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="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">What are the risks to have identifiers assigned to the users</a>.</p>
|
||||
<p><a href="https://simplex.chat/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>
|
||||
|
@ -1034,10 +1034,10 @@
|
|||
</ul>
|
||||
<h2 id="whats-new-in-v43" tabindex="-1">What's new in v4.3</h2>
|
||||
<ul>
|
||||
<li><a href="https://simplex.chat/blog/undefined">instant voice messages!</a></li>
|
||||
<li><a href="https://simplex.chat/blog/undefined">irreversible deletion of sent messages for all recipients</a></li>
|
||||
<li><a href="https://simplex.chat/blog/undefined">improved SMP server configuration and support for server passwords</a></li>
|
||||
<li><a href="https://simplex.chat/blog/undefined">privacy and security improvements</a>:
|
||||
<li><a href="https://simplex.chat/blog/20221206-simplex-chat-v4.3-voice-messages.html#instant-voice-messages">instant voice messages!</a></li>
|
||||
<li><a href="https://simplex.chat/blog/20221206-simplex-chat-v4.3-voice-messages.html#irreversible-message-deletion">irreversible deletion of sent messages for all recipients</a></li>
|
||||
<li><a href="https://simplex.chat/blog/20221206-simplex-chat-v4.3-voice-messages.html#smp-servers-configuration-and-password">improved SMP server configuration and support for server passwords</a></li>
|
||||
<li><a href="https://simplex.chat/blog/20221206-simplex-chat-v4.3-voice-messages.html#privacy-and-security-improvements">privacy and security improvements</a>:
|
||||
<ul>
|
||||
<li>protect app screen in recent apps and prevent screenshots</li>
|
||||
<li>improved privacy and security of SimpleX invitation links in the app</li>
|
||||
|
@ -1085,9 +1085,9 @@
|
|||
<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="https://simplex.chat/blog/20220511-simplex-chat-v2-images-files.html">How can SimpleX deliver messages without user identifiers</a>.</p>
|
||||
<p><a href="https://simplex.chat/blog/20220711-simplex-chat-v3-released-ios-notifications-audio-video-calls-database-export-import-protocol-improvements.html">What are the risks to have identifiers assigned to the users</a>.</p>
|
||||
<p><a href="https://simplex.chat/blog/20220723-simplex-chat-v3.1-tor-groups-efficiency.html">Technical details and limitations</a>.</p>
|
||||
<p><a href="https://simplex.chat/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="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">What are the risks to have identifiers assigned to the users</a>.</p>
|
||||
<p><a href="https://simplex.chat/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>
|
||||
|
@ -1123,16 +1123,16 @@
|
|||
<p><strong>Published:</strong> Jan 3, 2023</p>
|
||||
<h2 id="whats-new-in-v44" tabindex="-1">What's new in v4.4</h2>
|
||||
<ul>
|
||||
<li><a href="https://simplex.chat/blog/undefined">disappearing messages</a>.</li>
|
||||
<li><a href="https://simplex.chat/blog/undefined">&quot;live&quot; messages</a>.</li>
|
||||
<li><a href="https://simplex.chat/blog/undefined">connection security verification</a>.</li>
|
||||
<li><a href="https://simplex.chat/blog/undefined">animated images and stickers</a> – now on iOS too.</li>
|
||||
<li><a href="https://simplex.chat/blog/20230103-simplex-chat-v4.4-disappearing-messages.html#disappearing-messages">disappearing messages</a>.</li>
|
||||
<li><a href="https://simplex.chat/blog/20230103-simplex-chat-v4.4-disappearing-messages.html#live-messages">&quot;live&quot; messages</a>.</li>
|
||||
<li><a href="https://simplex.chat/blog/20230103-simplex-chat-v4.4-disappearing-messages.html#connection-security-verification">connection security verification</a>.</li>
|
||||
<li><a href="https://simplex.chat/blog/20230103-simplex-chat-v4.4-disappearing-messages.html#animated-images-and-stickers">animated images and stickers</a> – now on iOS too.</li>
|
||||
</ul>
|
||||
<p>Also, we added <a href="https://simplex.chat/blog/undefined">French language interface</a>, thanks to the users' community and Weblate!</p>
|
||||
<p>Also, we added <a href="https://simplex.chat/blog/20230103-simplex-chat-v4.4-disappearing-messages.html#french-language-interface">French language interface</a>, thanks to the users' community and Weblate!</p>
|
||||
<h3 id="disappearing-messages" tabindex="-1">Disappearing messages</h3>
|
||||
<p><img src="https://simplex.chat/blog/images/20230103-disappearing1.png" width="288" /> <img src="https://simplex.chat/blog/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="https://simplex.chat/blog/20221206-simplex-chat-v4.3-voice-messages.html">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="https://simplex.chat/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="https://simplex.chat/blog/images/20230103-live.png" width="288" />
|
||||
|
@ -1152,8 +1152,8 @@
|
|||
<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="https://simplex.chat/blog/20220511-simplex-chat-v2-images-files.html">How can SimpleX deliver messages without user identifiers</a>.</p>
|
||||
<p><a href="https://simplex.chat/blog/20220711-simplex-chat-v3-released-ios-notifications-audio-video-calls-database-export-import-protocol-improvements.html">What are the risks to have identifiers assigned to the users</a>.</p>
|
||||
<p><a href="https://simplex.chat/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="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">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>
|
||||
|
@ -1190,13 +1190,13 @@
|
|||
<p><strong>Published:</strong> Feb 4, 2023</p>
|
||||
<h2 id="whats-new-in-v45" tabindex="-1">What's new in v4.5</h2>
|
||||
<ul>
|
||||
<li><a href="https://simplex.chat/blog/undefined">multiple chat profiles</a>.</li>
|
||||
<li><a href="https://simplex.chat/blog/undefined">message draft</a>.</li>
|
||||
<li><a href="https://simplex.chat/blog/undefined">transport isolation</a>.</li>
|
||||
<li><a href="https://simplex.chat/blog/undefined">reduced battery usage</a>.</li>
|
||||
<li><a href="https://simplex.chat/blog/undefined">private filenames</a>.</li>
|
||||
<li><a href="https://simplex.chat/blog/20230204-simplex-chat-v4-5-user-chat-profiles.html#multiple-chat-profiles">multiple chat profiles</a>.</li>
|
||||
<li><a href="https://simplex.chat/blog/20230204-simplex-chat-v4-5-user-chat-profiles.html#message-draft">message draft</a>.</li>
|
||||
<li><a href="https://simplex.chat/blog/20230204-simplex-chat-v4-5-user-chat-profiles.html#transport-isolation">transport isolation</a>.</li>
|
||||
<li><a href="https://simplex.chat/blog/20230204-simplex-chat-v4-5-user-chat-profiles.html#reduced-battery-usage">reduced battery usage</a>.</li>
|
||||
<li><a href="https://simplex.chat/blog/20230204-simplex-chat-v4-5-user-chat-profiles.html#private-filenames">private filenames</a>.</li>
|
||||
</ul>
|
||||
<p>Also, we added <a href="https://simplex.chat/blog/undefined">Italian interface</a>, thanks to the users' community and Weblate!</p>
|
||||
<p>Also, we added <a href="https://simplex.chat/blog/20230204-simplex-chat-v4-5-user-chat-profiles.html#italian-interface">Italian interface</a>, thanks to the users' community and Weblate!</p>
|
||||
<h3 id="multiple-chat-profiles" tabindex="-1">Multiple chat profiles</h3>
|
||||
<p><img src="https://simplex.chat/blog/images/20230204-profiles1.png" width="288" /> <img src="https://simplex.chat/blog/images/20230204-profiles2.png" width="288" /></p>
|
||||
<p>Incognito mode added in v3.2 allows to share a random profile name with your new contacts. It is quite popular - more than half of users connecting to our support profile use it. In case when you just want a throw-away profile name that doesn't share any information about you it is more convenient that creating a new profile for each contact manually.</p>
|
||||
|
@ -1242,8 +1242,8 @@
|
|||
<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="https://simplex.chat/blog/20220511-simplex-chat-v2-images-files.html">How can SimpleX deliver messages without user identifiers</a>.</p>
|
||||
<p><a href="https://simplex.chat/blog/20220711-simplex-chat-v3-released-ios-notifications-audio-video-calls-database-export-import-protocol-improvements.html">What are the risks to have identifiers assigned to the users</a>.</p>
|
||||
<p><a href="https://simplex.chat/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="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">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>
|
||||
|
@ -1271,11 +1271,11 @@
|
|||
<content type="html"><h1 id="simplex-file-transfer-protocol-a-new-protocol-for-sending-large-files-efficiently-privately-and-securely" tabindex="-1">SimpleX File Transfer Protocol – a new protocol for sending large files efficiently, privately and securely.</h1>
|
||||
<p><strong>Published:</strong> Mar 1, 2023</p>
|
||||
<ul>
|
||||
<li><a href="https://simplex.chat/blog/undefined">Quick start: how to send a file using XFTP CLI</a></li>
|
||||
<li><a href="https://simplex.chat/blog/undefined">What's the problem</a></li>
|
||||
<li><a href="https://simplex.chat/blog/undefined">Why didn't we just use some existing solution?</a></li>
|
||||
<li><a href="https://simplex.chat/blog/undefined">What is XFTP and how does it work?</a></li>
|
||||
<li><a href="https://simplex.chat/blog/undefined">What is next?</a></li>
|
||||
<li><a href="https://simplex.chat/blog/20230301-simplex-file-transfer-protocol.html#%E2%9A%A1%EF%B8%8F-quick-start-send-a-file-with-xftp-cli-in-3-simple-steps">Quick start: how to send a file using XFTP CLI</a></li>
|
||||
<li><a href="https://simplex.chat/blog/20230301-simplex-file-transfer-protocol.html#whats-the-problem">What's the problem</a></li>
|
||||
<li><a href="https://simplex.chat/blog/20230301-simplex-file-transfer-protocol.html#why-didnt-we-just-use-some-existing-solution">Why didn't we just use some existing solution?</a></li>
|
||||
<li><a href="https://simplex.chat/blog/20230301-simplex-file-transfer-protocol.html#what-is-xftp-and-how-does-it-work">What is XFTP and how does it work?</a></li>
|
||||
<li><a href="https://simplex.chat/blog/20230301-simplex-file-transfer-protocol.html#what-is-next">What is next?</a></li>
|
||||
</ul>
|
||||
<h2 id="quick-start-send-a-file-with-xftp-cli-in-3-simple-steps" tabindex="-1">⚡️ Quick start: send a file with XFTP CLI in 3 simple steps</h2>
|
||||
<p>Download XFTP binary for Linux from <a href="https://github.com/simplex-chat/simplexmq/releases/tag/v5.0.0-beta.3">the release</a> – you need the file <code>xftp-ubuntu-20_04-x86-64</code> - rename it as <code>xftp</code>.</p>
|
||||
|
@ -1355,8 +1355,8 @@ file ---&gt; | XFTP | ------&gt; XFTP ----&
|
|||
<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="https://simplex.chat/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="https://simplex.chat/blog/20220511-simplex-chat-v2-images-files.html">How can SimpleX deliver messages without user identifiers</a>.</p>
|
||||
<p><a href="https://simplex.chat/blog/20220711-simplex-chat-v3-released-ios-notifications-audio-video-calls-database-export-import-protocol-improvements.html">What are the risks to have identifiers assigned to the users</a>.</p>
|
||||
<p><a href="https://simplex.chat/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="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">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>
|
||||
|
@ -1385,15 +1385,15 @@ file ---&gt; | XFTP | ------&gt; XFTP ----&
|
|||
<p><strong>Published:</strong> Mar 28, 2023</p>
|
||||
<h2 id="whats-new-in-v46" tabindex="-1">What's new in v4.6</h2>
|
||||
<ul>
|
||||
<li><a href="https://simplex.chat/blog/undefined">ARMv7a and Android 8+ support</a></li>
|
||||
<li><a href="https://simplex.chat/blog/undefined">hidden chat profiles</a></li>
|
||||
<li><a href="https://simplex.chat/blog/undefined">group / community moderation</a></li>
|
||||
<li><a href="https://simplex.chat/blog/undefined">group welcome message</a></li>
|
||||
<li><a href="https://simplex.chat/blog/undefined">improved audio/video calls</a></li>
|
||||
<li><a href="https://simplex.chat/blog/undefined">reduced battery usage</a>.</li>
|
||||
<li><a href="https://simplex.chat/blog/undefined">SMP server monitoring: status bot and page</a></li>
|
||||
<li><a href="https://simplex.chat/blog/20230328-simplex-chat-v4-6-hidden-profiles.html#armv7a-32-bit-and-android-8-support">ARMv7a and Android 8+ support</a></li>
|
||||
<li><a href="https://simplex.chat/blog/20230328-simplex-chat-v4-6-hidden-profiles.html#hidden-chat-profiles">hidden chat profiles</a></li>
|
||||
<li><a href="https://simplex.chat/blog/20230328-simplex-chat-v4-6-hidden-profiles.html#group--community-moderation">group / community moderation</a></li>
|
||||
<li><a href="https://simplex.chat/blog/20230328-simplex-chat-v4-6-hidden-profiles.html#group-welcome-message">group welcome message</a></li>
|
||||
<li><a href="https://simplex.chat/blog/20230328-simplex-chat-v4-6-hidden-profiles.html#improved-audiovideo-calls">improved audio/video calls</a></li>
|
||||
<li><a href="https://simplex.chat/blog/20230328-simplex-chat-v4-6-hidden-profiles.html#reduced-battery-usage">reduced battery usage</a>.</li>
|
||||
<li><a href="https://simplex.chat/blog/20230328-simplex-chat-v4-6-hidden-profiles.html#smp-server-monitoring">SMP server monitoring: status bot and page</a></li>
|
||||
</ul>
|
||||
<p>Also, we added <a href="https://simplex.chat/blog/undefined">Chinese and Spanish interface languages</a>, thanks to the users' community and Weblate!</p>
|
||||
<p>Also, we added <a href="https://simplex.chat/blog/20230328-simplex-chat-v4-6-hidden-profiles.html#chinese-and-spanish-interface---you-can-choose-the-language-via-the-app">Chinese and Spanish interface languages</a>, thanks to the users' community and Weblate!</p>
|
||||
<h3 id="armv7a-32-bit-and-android-8-support" tabindex="-1">ARMv7a (32 bit) and Android 8+ support!</h3>
|
||||
<p>It increases the number of supported Android devices twice - now most of your friends should be able to install SimpleX Chat. SimpleX Chat still doesn't support Android 7 and erlier versions.</p>
|
||||
<p>If you install the app from GitHub or F-Droid you need to choose the correct APK, Play Store will provide it automatically.</p>
|
||||
|
@ -1462,15 +1462,15 @@ file ---&gt; | XFTP | ------&gt; XFTP ----&
|
|||
<p><strong>Published:</strong> Apr 22, 2023</p>
|
||||
<p>SimpleX Chat vision and funding:</p>
|
||||
<ul>
|
||||
<li><a href="https://simplex.chat/blog/undefined">why is it a commercial company?</a></li>
|
||||
<li><a href="https://simplex.chat/blog/undefined">how is it funded and what is the business model?</a></li>
|
||||
<li><a href="https://simplex.chat/blog/undefined">what is next?</a></li>
|
||||
<li><a href="https://simplex.chat/blog/20230422-simplex-chat-vision-funding-v5-videos-files-passcode.html#why-is-it-a-commercial-company">why is it a commercial company?</a></li>
|
||||
<li><a href="https://simplex.chat/blog/20230422-simplex-chat-vision-funding-v5-videos-files-passcode.html#how-is-it-funded-and-what-is-the-business-model">how is it funded and what is the business model?</a></li>
|
||||
<li><a href="https://simplex.chat/blog/20230422-simplex-chat-vision-funding-v5-videos-files-passcode.html#what-is-next">what is next?</a></li>
|
||||
</ul>
|
||||
<p>What's new in v5.0:</p>
|
||||
<ul>
|
||||
<li><a href="https://simplex.chat/blog/undefined">send videos and files up to 1gb</a></li>
|
||||
<li><a href="https://simplex.chat/blog/undefined">app passcode independent from system authentication</a></li>
|
||||
<li><a href="https://simplex.chat/blog/undefined">networking improvements</a></li>
|
||||
<li><a href="https://simplex.chat/blog/20230422-simplex-chat-vision-funding-v5-videos-files-passcode.html#send-videos-and-files-up-to-1gb">send videos and files up to 1gb</a></li>
|
||||
<li><a href="https://simplex.chat/blog/20230422-simplex-chat-vision-funding-v5-videos-files-passcode.html#app-passcode">app passcode independent from system authentication</a></li>
|
||||
<li><a href="https://simplex.chat/blog/20230422-simplex-chat-vision-funding-v5-videos-files-passcode.html#networking-improvements">networking improvements</a></li>
|
||||
</ul>
|
||||
<p>Also, we added Polish interface language, thanks to <a href="https://github.com/simplex-chat/simplex-chat#help-translating-simplex-chat">the users' community and Weblate</a>.</p>
|
||||
<p>SimpleX Chat apps are now available in 10 languages!</p>
|
||||
|
@ -1490,7 +1490,7 @@ file ---&gt; | XFTP | ------&gt; XFTP ----&
|
|||
<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="https://simplex.chat/blog/20220901-simplex-chat-v3.2-incognito-mode.html">incognito mode</a>, <a href="https://simplex.chat/blog/20230103-simplex-chat-v4.4-disappearing-messages.html">live messages</a> and <a href="https://simplex.chat/blog/20230328-simplex-chat-v4-6-hidden-profiles.html">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="https://simplex.chat/blog/20220901-simplex-chat-v3.2-incognito-mode.html#incognito-mode">incognito mode</a>, <a href="https://simplex.chat/blog/20230103-simplex-chat-v4.4-disappearing-messages.html#live-messages">live messages</a> and <a href="https://simplex.chat/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>
|
||||
|
@ -1548,16 +1548,16 @@ file ---&gt; | XFTP | ------&gt; XFTP ----&
|
|||
<p><strong>Published:</strong> May 23, 2023</p>
|
||||
<p>What's new in v5.1:</p>
|
||||
<ul>
|
||||
<li><a href="https://simplex.chat/blog/undefined">message reactions</a> 🚀</li>
|
||||
<li><a href="https://simplex.chat/blog/undefined">improved messages</a>:
|
||||
<li><a href="https://simplex.chat/blog/20230523-simplex-chat-v5-1-message-reactions-self-destruct-passcode.html#message-reactions">message reactions</a> 🚀</li>
|
||||
<li><a href="https://simplex.chat/blog/20230523-simplex-chat-v5-1-message-reactions-self-destruct-passcode.html#improved-messages">improved messages</a>:
|
||||
<ul>
|
||||
<li><a href="https://simplex.chat/blog/undefined">voice messages up to 5 minutes</a>.</li>
|
||||
<li><a href="https://simplex.chat/blog/undefined">custom time to disappear</a>.</li>
|
||||
<li><a href="https://simplex.chat/blog/undefined">message editing history</a>.</li>
|
||||
<li><a href="https://simplex.chat/blog/20230523-simplex-chat-v5-1-message-reactions-self-destruct-passcode.html#voice-messages-up-to-5-minutes-better-quality-playback-control">voice messages up to 5 minutes</a>.</li>
|
||||
<li><a href="https://simplex.chat/blog/20230523-simplex-chat-v5-1-message-reactions-self-destruct-passcode.html#disappearing-messages-choose-any-time">custom time to disappear</a>.</li>
|
||||
<li><a href="https://simplex.chat/blog/20230523-simplex-chat-v5-1-message-reactions-self-destruct-passcode.html#message-editing-history">message editing history</a>.</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li>new design and <a href="https://simplex.chat/blog/undefined">customizable themes</a> that you can share!<sup>*</sup></li>
|
||||
<li><a href="https://simplex.chat/blog/undefined">self-destruct passcode</a></li>
|
||||
<li>new design and <a href="https://simplex.chat/blog/20230523-simplex-chat-v5-1-message-reactions-self-destruct-passcode.html#customize-and-share-color-themes">customizable themes</a> that you can share!<sup>*</sup></li>
|
||||
<li><a href="https://simplex.chat/blog/20230523-simplex-chat-v5-1-message-reactions-self-destruct-passcode.html#self-destruct-passcode">self-destruct passcode</a></li>
|
||||
</ul>
|
||||
<p>There are lots of small improvements and fixes in this release:</p>
|
||||
<ul>
|
||||
|
@ -1579,15 +1579,15 @@ file ---&gt; | XFTP | ------&gt; XFTP ----&
|
|||
<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="https://simplex.chat/blog/images/20230523-voice.png" width="288" class="float-to-left" />
|
||||
<p>Since <a href="https://simplex.chat/blog/20221206-simplex-chat-v4.3-voice-messages.html">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="https://simplex.chat/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="https://simplex.chat/blog/images/20230523-disappearing1.png" width="288" /> <img src="https://simplex.chat/blog/images/20230523-disappearing2.png" width="288" /></p>
|
||||
<p>Since <a href="https://simplex.chat/blog/20230103-simplex-chat-v4.4-disappearing-messages.html">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="https://simplex.chat/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="https://simplex.chat/blog/images/20230523-info.png" width="288" class="float-to-left" />
|
||||
<p>I <a href="https://simplex.chat/blog/20221206-simplex-chat-v4.3-voice-messages.html">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="https://simplex.chat/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="https://simplex.chat/blog/images/20230523-theme.png" width="288" class="float-to-left" />
|
||||
|
@ -1636,16 +1636,16 @@ file ---&gt; | XFTP | ------&gt; XFTP ----&
|
|||
<p><strong>Published:</strong> July 22, 2023</p>
|
||||
<p><strong>What's new in v5.2:</strong></p>
|
||||
<ul>
|
||||
<li><a href="https://simplex.chat/blog/undefined">message delivery receipts</a> – with opt-out per contact!</li>
|
||||
<li><a href="https://simplex.chat/blog/undefined">filter favorite and unread chats</a>.</li>
|
||||
<li><a href="https://simplex.chat/blog/undefined">more usable groups</a>:
|
||||
<li><a href="https://simplex.chat/blog/20230722-simplex-chat-v5-2-message-delivery-receipts.html#message-delivery-receipts">message delivery receipts</a> – with opt-out per contact!</li>
|
||||
<li><a href="https://simplex.chat/blog/20230722-simplex-chat-v5-2-message-delivery-receipts.html#filter-favorite-and-unread-chats">filter favorite and unread chats</a>.</li>
|
||||
<li><a href="https://simplex.chat/blog/20230722-simplex-chat-v5-2-message-delivery-receipts.html#more-usable-groups">more usable groups</a>:
|
||||
<ul>
|
||||
<li>view full original replied message in info.</li>
|
||||
<li>share your address with your contacts and group members via your chat profile.</li>
|
||||
<li>search new and existing members.</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li><a href="https://simplex.chat/blog/undefined">stability improvements</a>:
|
||||
<li><a href="https://simplex.chat/blog/20230722-simplex-chat-v5-2-message-delivery-receipts.html#stability-improvements">stability improvements</a>:
|
||||
<ul>
|
||||
<li>keep your connections working after restoring from backup.</li>
|
||||
<li>restart app (Android) or reconnect servers (iOS).</li>
|
||||
|
@ -1655,28 +1655,28 @@ file ---&gt; | XFTP | ------&gt; XFTP ----&
|
|||
</li>
|
||||
<li>other improvements:
|
||||
<ul>
|
||||
<li><a href="https://simplex.chat/blog/undefined">better disappearing messages</a>.</li>
|
||||
<li><a href="https://simplex.chat/blog/undefined">prohibit message reactions</a>.</li>
|
||||
<li><a href="https://simplex.chat/blog/20230722-simplex-chat-v5-2-message-delivery-receipts.html#better-disappearing-messages">better disappearing messages</a>.</li>
|
||||
<li><a href="https://simplex.chat/blog/20230722-simplex-chat-v5-2-message-delivery-receipts.html#prohibit-message-reactions">prohibit message reactions</a>.</li>
|
||||
</ul>
|
||||
</li>
|
||||
</ul>
|
||||
<p><strong>Platform evolution:</strong></p>
|
||||
<ul>
|
||||
<li><a href="https://simplex.chat/blog/undefined">problems of public groups</a>:
|
||||
<li><a href="https://simplex.chat/blog/20230722-simplex-chat-v5-2-message-delivery-receipts.html#problems-of-public-groups">problems of public groups</a>:
|
||||
<ul>
|
||||
<li>why not all messages are received.</li>
|
||||
<li>how to cope with these problems.</li>
|
||||
<li>when will public groups be more usable.</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li><a href="https://simplex.chat/blog/undefined">what about read receipts?</a></li>
|
||||
<li><a href="https://simplex.chat/blog/20230722-simplex-chat-v5-2-message-delivery-receipts.html#what-about-read-receipts">what about read receipts?</a></li>
|
||||
</ul>
|
||||
<h2 id="whats-new-in-v52" tabindex="-1">What's new in v5.2</h2>
|
||||
<h3 id="message-delivery-receipts" tabindex="-1">Message delivery receipts</h3>
|
||||
<img src="https://simplex.chat/blog/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="https://simplex.chat/blog/20230328-simplex-chat-v4-6-hidden-profiles.html">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="https://simplex.chat/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="https://simplex.chat/blog/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>
|
||||
|
@ -1695,8 +1695,8 @@ file ---&gt; | XFTP | ------&gt; XFTP ----&
|
|||
<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="https://simplex.chat/docs/glossary.html">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="https://simplex.chat/docs/glossary.html">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="https://simplex.chat/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="https://simplex.chat/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>
|
||||
|
@ -1716,12 +1716,12 @@ file ---&gt; | XFTP | ------&gt; XFTP ----&
|
|||
<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="https://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>
|
||||
<p>We also <a href="https://simplex.chat/blog/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="https://github.com/simplex-chat/simplex-chat/blob/stable/simplex-chat/docs/rfcs/2023-05-22-groups-moderation.md">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://simplex.chat/blog/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>
|
||||
|
@ -1762,10 +1762,10 @@ file ---&gt; | XFTP | ------&gt; XFTP ----&
|
|||
<p><strong>Published:</strong> September 25, 2023</p>
|
||||
<p><strong>What's new in v5.3:</strong></p>
|
||||
<ul>
|
||||
<li><a href="https://simplex.chat/blog/undefined">new desktop app!</a>!</li>
|
||||
<li><a href="https://simplex.chat/blog/undefined">directory service and other group improvements</a>.</li>
|
||||
<li><a href="https://simplex.chat/blog/undefined">encrypted local files and media with forward secrecy</a>.</li>
|
||||
<li><a href="https://simplex.chat/blog/undefined">simplified incognito mode</a>.</li>
|
||||
<li><a href="https://simplex.chat/blog/20230925-simplex-chat-v5-3-desktop-app-local-file-encryption-directory-service.html#multiplatform-desktop-app">new desktop app!</a>!</li>
|
||||
<li><a href="https://simplex.chat/blog/20230925-simplex-chat-v5-3-desktop-app-local-file-encryption-directory-service.html#group-directory-service-and-other-group-improvements">directory service and other group improvements</a>.</li>
|
||||
<li><a href="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">encrypted local files and media with forward secrecy</a>.</li>
|
||||
<li><a href="https://simplex.chat/blog/20230925-simplex-chat-v5-3-desktop-app-local-file-encryption-directory-service.html#simplified-incognito-mode">simplified incognito mode</a>.</li>
|
||||
</ul>
|
||||
<p>There are a lot of other improvements and fixes in this release:</p>
|
||||
<ul>
|
||||
|
@ -1860,17 +1860,17 @@ file ---&gt; | XFTP | ------&gt; XFTP ----&
|
|||
<p><strong>Published:</strong> Nov 25, 2023</p>
|
||||
<p><strong>What's new in v5.4:</strong></p>
|
||||
<ul>
|
||||
<li><a href="https://simplex.chat/blog/undefined">Link mobile and desktop apps via secure quantum-resistant protocol</a>.
|
||||
<li><a href="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">Link mobile and desktop apps via secure quantum-resistant protocol</a>.
|
||||
<ul>
|
||||
<li>⚡️ Quick start - how to use it.</li>
|
||||
<li>How does it work?</li>
|
||||
<li>🤖 Connecting to remote CLI.</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li><a href="https://simplex.chat/blog/undefined">Better groups</a>.
|
||||
<li><a href="https://simplex.chat/blog/20231125-simplex-chat-v5-4-link-mobile-desktop-quantum-resistant-better-groups.html#better-groups">Better groups</a>.
|
||||
<ul>
|
||||
<li><a href="https://simplex.chat/blog/undefined">Faster to join and more reliable</a>.</li>
|
||||
<li><a href="https://simplex.chat/blog/undefined">New group features</a>:
|
||||
<li><a href="https://simplex.chat/blog/20231125-simplex-chat-v5-4-link-mobile-desktop-quantum-resistant-better-groups.html#faster-to-join-with-more-reliable-message-delivery">Faster to join and more reliable</a>.</li>
|
||||
<li><a href="https://simplex.chat/blog/20231125-simplex-chat-v5-4-link-mobile-desktop-quantum-resistant-better-groups.html#new-group-features">New group features</a>:
|
||||
<ul>
|
||||
<li>create groups with incognito profile,</li>
|
||||
<li>block group members to reduce noise,</li>
|
||||
|
@ -1879,9 +1879,9 @@ file ---&gt; | XFTP | ------&gt; XFTP ----&
|
|||
</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li><a href="https://simplex.chat/blog/undefined">Better calls</a>: faster to connect, with screen sharing on desktop.</li>
|
||||
<li><a href="https://simplex.chat/blog/20231125-simplex-chat-v5-4-link-mobile-desktop-quantum-resistant-better-groups.html#better-calls">Better calls</a>: faster to connect, with screen sharing on desktop.</li>
|
||||
</ul>
|
||||
<p>There are many <a href="https://simplex.chat/blog/undefined">other improvements</a> and fixes in this release:</p>
|
||||
<p>There are many <a href="https://simplex.chat/blog/20231125-simplex-chat-v5-4-link-mobile-desktop-quantum-resistant-better-groups.html#other-improvements">other improvements</a> and fixes in this release:</p>
|
||||
<ul>
|
||||
<li>profile names now allow spaces.</li>
|
||||
<li>when you delete contacts, they are optionally notified.</li>
|
||||
|
@ -1903,7 +1903,7 @@ file ---&gt; | XFTP | ------&gt; XFTP ----&
|
|||
<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="https://simplex.chat/docs/glossary.html">double-ratchet algorithm</a>, with <a href="https://simplex.chat/docs/glossary.html">perfect forward secrecy</a>, <a href="https://simplex.chat/docs/glossary.html">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="https://simplex.chat/docs/glossary.html#double-ratchet-algorithm">double-ratchet algorithm</a>, with <a href="https://simplex.chat/docs/glossary.html#forward-secrecy">perfect forward secrecy</a>, <a href="https://simplex.chat/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>
|
||||
|
@ -1943,8 +1943,8 @@ file ---&gt; | XFTP | ------&gt; XFTP ----&
|
|||
<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="https://simplex.chat/blog/20220511-simplex-chat-v2-images-files.html">How can SimpleX deliver messages without user identifiers</a>.</p>
|
||||
<p><a href="https://simplex.chat/blog/20220711-simplex-chat-v3-released-ios-notifications-audio-video-calls-database-export-import-protocol-improvements.html">What are the risks to have identifiers assigned to the users</a>.</p>
|
||||
<p><a href="https://simplex.chat/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="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">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>
|
||||
|
@ -1971,7 +1971,7 @@ file ---&gt; | XFTP | ------&gt; XFTP ----&
|
|||
<title>SimpleX Chat: free infrastructure from Linode, v5.5 released with private notes, group history and a simpler UX to connect.</title>
|
||||
<content type="html"><h1 id="simplex-chat-free-infrastructure-from-linode-v55-released-with-private-notes-group-history-and-a-simpler-ux-to-connect" tabindex="-1">SimpleX Chat: free infrastructure from Linode, v5.5 released with private notes, group history and a simpler UX to connect.</h1>
|
||||
<p><strong>Published:</strong> Jan 24, 2024</p>
|
||||
<p><a href="https://simplex.chat/blog/undefined">SimpleX Chat infrastructure on Linode</a>:</p>
|
||||
<p><a href="https://simplex.chat/blog/20240124-simplex-chat-infrastructure-costs-v5-5-simplex-ux-private-notes-group-history.html#simplex-chat-infrastructure-on-linode">SimpleX Chat infrastructure on Linode</a>:</p>
|
||||
<ul>
|
||||
<li>Free infrastructure.</li>
|
||||
<li>SimpleX servers in Linode Marketplace.</li>
|
||||
|
@ -1979,10 +1979,10 @@ file ---&gt; | XFTP | ------&gt; XFTP ----&
|
|||
</ul>
|
||||
<p>What's new in v5.5:</p>
|
||||
<ul>
|
||||
<li><a href="https://simplex.chat/blog/undefined">private notes</a></li>
|
||||
<li><a href="https://simplex.chat/blog/undefined">group history</a></li>
|
||||
<li><a href="https://simplex.chat/blog/undefined">simpler UX to connect to other users</a></li>
|
||||
<li><a href="https://simplex.chat/blog/undefined">message delivery stability and other improvements</a></li>
|
||||
<li><a href="https://simplex.chat/blog/20240124-simplex-chat-infrastructure-costs-v5-5-simplex-ux-private-notes-group-history.html#private-notes">private notes</a></li>
|
||||
<li><a href="https://simplex.chat/blog/20240124-simplex-chat-infrastructure-costs-v5-5-simplex-ux-private-notes-group-history.html#group-history">group history</a></li>
|
||||
<li><a href="https://simplex.chat/blog/20240124-simplex-chat-infrastructure-costs-v5-5-simplex-ux-private-notes-group-history.html#simpler-ux-to-connect-to-other-users">simpler UX to connect to other users</a></li>
|
||||
<li><a href="https://simplex.chat/blog/20240124-simplex-chat-infrastructure-costs-v5-5-simplex-ux-private-notes-group-history.html#message-delivery-stability-and-other-improvements">message delivery stability and other improvements</a></li>
|
||||
</ul>
|
||||
<p>Also, we added Hungarian (only Android) and Turkish interface languages, thanks to <a href="https://github.com/simplex-chat/simplex-chat#help-translating-simplex-chat">our users and Weblate</a>.</p>
|
||||
<p>SimpleX Chat Android app is now available in 20 languages!</p>
|
||||
|
@ -2029,8 +2029,8 @@ file ---&gt; | XFTP | ------&gt; XFTP ----&
|
|||
</ul>
|
||||
<h2 id="simplex-platform" tabindex="-1">SimpleX platform</h2>
|
||||
<p>Some links to answer the most common questions:</p>
|
||||
<p><a href="https://simplex.chat/blog/20220511-simplex-chat-v2-images-files.html">How can SimpleX deliver messages without user identifiers</a>.</p>
|
||||
<p><a href="https://simplex.chat/blog/20220711-simplex-chat-v3-released-ios-notifications-audio-video-calls-database-export-import-protocol-improvements.html">What are the risks to have identifiers assigned to the users</a>.</p>
|
||||
<p><a href="https://simplex.chat/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="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">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>
|
||||
|
@ -2060,9 +2060,9 @@ file ---&gt; | XFTP | ------&gt; XFTP ----&
|
|||
<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>
|
||||
<li><a href="https://simplex.chat/blog/undefined">Why do we need end-to-end encryption?</a></li>
|
||||
<li><a href="https://simplex.chat/blog/undefined">Why is encryption even allowed?</a></li>
|
||||
<li><a href="https://simplex.chat/blog/undefined">End-to-end encryption security: attacks and defense.</a>
|
||||
<li><a href="https://simplex.chat/blog/20240314-simplex-chat-v5-6-quantum-resistance-signal-double-ratchet-algorithm.html#why-do-we-need-end-to-end-encryption">Why do we need end-to-end encryption?</a></li>
|
||||
<li><a href="https://simplex.chat/blog/20240314-simplex-chat-v5-6-quantum-resistance-signal-double-ratchet-algorithm.html#why-is-encryption-even-allowed">Why is encryption even allowed?</a></li>
|
||||
<li><a href="https://simplex.chat/blog/20240314-simplex-chat-v5-6-quantum-resistance-signal-double-ratchet-algorithm.html#end-to-end-encryption-security-attacks-and-defense">End-to-end encryption security: attacks and defense.</a>
|
||||
<ol>
|
||||
<li>Compromised message size - mitigated by padding messages to a fixed block size.</li>
|
||||
<li>Compromised confidentiality - mitigated by repudiation (deniability).</li>
|
||||
|
@ -2072,10 +2072,10 @@ file ---&gt; | XFTP | ------&gt; XFTP ----&
|
|||
<li>&quot;Record now, decrypt later&quot; attacks - mitigated by post-quantum cryptography.</li>
|
||||
</ol>
|
||||
</li>
|
||||
<li><a href="https://simplex.chat/blog/undefined">How secure is encryption in different messengers?</a></li>
|
||||
<li><a href="https://simplex.chat/blog/undefined">Adding quantum resistance to Signal double ratchet algorithm.</a></li>
|
||||
<li><a href="https://simplex.chat/blog/undefined">When can you start using quantum resistant chats?</a></li>
|
||||
<li><a href="https://simplex.chat/blog/undefined">Next for post-quantum crypto - all direct chats, small groups and security audit.</a></li>
|
||||
<li><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">How secure is encryption in different messengers?</a></li>
|
||||
<li><a href="https://simplex.chat/blog/20240314-simplex-chat-v5-6-quantum-resistance-signal-double-ratchet-algorithm.html#adding-quantum-resistance-to-signal-double-ratchet-algorithm">Adding quantum resistance to Signal double ratchet algorithm.</a></li>
|
||||
<li><a href="https://simplex.chat/blog/20240314-simplex-chat-v5-6-quantum-resistance-signal-double-ratchet-algorithm.html#when-can-you-start-using-quantum-resistant-chats">When can you start using quantum resistant chats?</a></li>
|
||||
<li><a href="https://simplex.chat/blog/20240314-simplex-chat-v5-6-quantum-resistance-signal-double-ratchet-algorithm.html#next-for-post-quantum-crypto---all-direct-chats-small-groups-and-security-audit">Next for post-quantum crypto - all direct chats, small groups and security audit.</a></li>
|
||||
</ul>
|
||||
<h2 id="why-do-we-need-end-to-end-encryption" tabindex="-1">Why do we need end-to-end encryption?</h2>
|
||||
<p>The objective of end-to-end encryption is to make any potential attackers, such as traffic observers or communication providers who pass the messages between senders and recipients, unable to recover <em>any</em> message content or meaningful information about the messages, even if these attackers possess very advanced computing and mathematical capabilities.</p>
|
||||
|
@ -2108,7 +2108,7 @@ file ---&gt; | XFTP | ------&gt; XFTP ----&
|
|||
<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="https://simplex.chat/blog/20230103-simplex-chat-v4.4-disappearing-messages.html">disappearing messages</a> and the ability to <a href="https://simplex.chat/blog/20221206-simplex-chat-v4.3-voice-messages.html">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="https://simplex.chat/blog/20230103-simplex-chat-v4.4-disappearing-messages.html#disappearing-messages">disappearing messages</a> and the ability to <a href="https://simplex.chat/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>
|
||||
|
@ -2202,8 +2202,8 @@ file ---&gt; | XFTP | ------&gt; XFTP ----&
|
|||
<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="https://simplex.chat/blog/20220511-simplex-chat-v2-images-files.html">How can SimpleX deliver messages without user identifiers</a>.</p>
|
||||
<p><a href="https://simplex.chat/blog/20220711-simplex-chat-v3-released-ios-notifications-audio-video-calls-database-export-import-protocol-improvements.html">What are the risks to have identifiers assigned to the users</a>.</p>
|
||||
<p><a href="https://simplex.chat/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="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">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>
|
||||
|
@ -2233,15 +2233,15 @@ file ---&gt; | XFTP | ------&gt; XFTP ----&
|
|||
<p><strong>Published:</strong> Mar 23, 2024</p>
|
||||
<p>SimpleX network: deliver real privacy via a profitable business and non-profit protocol governance:</p>
|
||||
<ul>
|
||||
<li><a href="https://simplex.chat/blog/undefined">community and business interests are aligned</a>.</li>
|
||||
<li><a href="https://simplex.chat/blog/undefined">the journey to the decentralized non-profit protocol governance</a>.</li>
|
||||
<li><a href="https://simplex.chat/blog/undefined">welcome, Esra’a</a>!</li>
|
||||
<li><a href="https://simplex.chat/blog/20240323-simplex-network-privacy-non-profit-v5-6-quantum-resistant-e2e-encryption-simple-migration.html#community-and-business-interests-are-aligned">community and business interests are aligned</a>.</li>
|
||||
<li><a href="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">the journey to the decentralized non-profit protocol governance</a>.</li>
|
||||
<li><a href="https://simplex.chat/blog/20240323-simplex-network-privacy-non-profit-v5-6-quantum-resistant-e2e-encryption-simple-migration.html#welcome-esraa">welcome, Esra’a</a>!</li>
|
||||
</ul>
|
||||
<p>What's new in v5.6:</p>
|
||||
<ul>
|
||||
<li><a href="https://simplex.chat/blog/undefined">quantum resistant end-to-end encryption</a> (BETA) – enable it for the new contacts.</li>
|
||||
<li><a href="https://simplex.chat/blog/undefined">use the app during the audio and video calls</a>.</li>
|
||||
<li><a href="https://simplex.chat/blog/undefined">migrate all app data to another device via QR code</a>.</li>
|
||||
<li><a href="https://simplex.chat/blog/20240323-simplex-network-privacy-non-profit-v5-6-quantum-resistant-e2e-encryption-simple-migration.html#quantum-resistant-end-to-end-encryption-beta">quantum resistant end-to-end encryption</a> (BETA) – enable it for the new contacts.</li>
|
||||
<li><a href="https://simplex.chat/blog/20240323-simplex-network-privacy-non-profit-v5-6-quantum-resistant-e2e-encryption-simple-migration.html#use-the-app-during-the-audio-and-video-calls">use the app during the audio and video calls</a>.</li>
|
||||
<li><a href="https://simplex.chat/blog/20240323-simplex-network-privacy-non-profit-v5-6-quantum-resistant-e2e-encryption-simple-migration.html#migrate-all-app-data-to-another-device-via-qr-code">migrate all app data to another device via QR code</a>.</li>
|
||||
</ul>
|
||||
<p>There are many other improvements and fixes in this release:</p>
|
||||
<ul>
|
||||
|
@ -2264,7 +2264,7 @@ file ---&gt; | XFTP | ------&gt; XFTP ----&
|
|||
<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="https://simplex.chat/blog/20240314-simplex-chat-v5-6-quantum-resistance-signal-double-ratchet-algorithm.html">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="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">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="https://simplex.chat/blog/images/20240314-pq1.png" width="288" /> <img src="https://simplex.chat/blog/images/20240314-pq2.png" width="288" /> <img src="https://simplex.chat/blog/images/20240314-pq3.png" width="288" /></p>
|
||||
|
@ -2289,8 +2289,8 @@ file ---&gt; | XFTP | ------&gt; XFTP ----&
|
|||
<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="https://simplex.chat/blog/20220711-simplex-chat-v3-released-ios-notifications-audio-video-calls-database-export-import-protocol-improvements.html">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="https://simplex.chat/blog/undefined">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>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="https://simplex.chat/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="https://simplex.chat/blog/20240323-simplex-network-privacy-non-profit-v5-6-quantum-resistant-e2e-encryption-simple-migration.html">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>
|
||||
<p><img src="https://simplex.chat/blog/images/20240323-migrate-from1.png" width="170" /> <img src="https://simplex.chat/blog/images/arrow.png" width="24" /> <img src="https://simplex.chat/blog/images/20240323-migrate-from2.png" width="170" /> <img src="https://simplex.chat/blog/images/arrow.png" width="24" /> <img src="https://simplex.chat/blog/images/20240323-migrate-from3.png" width="170" /> <img src="https://simplex.chat/blog/images/arrow.png" width="24" /> <img src="https://simplex.chat/blog/images/20240323-migrate-from4.png" width="170" /> <img src="https://simplex.chat/blog/images/arrow.png" width="24" /> <img src="https://simplex.chat/blog/images/20240323-migrate-from5.png" width="170" /></p>
|
||||
|
@ -2315,8 +2315,8 @@ file ---&gt; | XFTP | ------&gt; XFTP ----&
|
|||
<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="https://simplex.chat/blog/20220511-simplex-chat-v2-images-files.html">How can SimpleX deliver messages without user identifiers</a>.</p>
|
||||
<p><a href="https://simplex.chat/blog/20220711-simplex-chat-v3-released-ios-notifications-audio-video-calls-database-export-import-protocol-improvements.html">What are the risks to have identifiers assigned to the users</a>.</p>
|
||||
<p><a href="https://simplex.chat/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="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">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>
|
||||
|
@ -2387,7 +2387,7 @@ file ---&gt; | XFTP | ------&gt; XFTP ----&
|
|||
<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">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="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>
|
||||
<img src="https://simplex.chat/blog/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>
|
||||
|
@ -2412,18 +2412,18 @@ file ---&gt; | XFTP | ------&gt; XFTP ----&
|
|||
<p><strong>Published:</strong> Apr 26, 2024</p>
|
||||
<p>What's new in v5.7:</p>
|
||||
<ul>
|
||||
<li><a href="https://simplex.chat/blog/undefined">quantum resistant end-to-end encryption</a> with all contacts.</li>
|
||||
<li><a href="https://simplex.chat/blog/undefined">forward and save messages</a> without revealing the source.</li>
|
||||
<li><a href="https://simplex.chat/blog/undefined">in-call sounds and switching sound sources</a>.</li>
|
||||
<li><a href="https://simplex.chat/blog/undefined">better network connection management</a>.</li>
|
||||
<li><a href="https://simplex.chat/blog/undefined">customizable profile images</a></li>
|
||||
<li><a href="https://simplex.chat/blog/20240426-simplex-legally-binding-transparency-v5-7-better-user-experience.html#quantum-resistant-end-to-end-encryption">quantum resistant end-to-end encryption</a> with all contacts.</li>
|
||||
<li><a href="https://simplex.chat/blog/20240426-simplex-legally-binding-transparency-v5-7-better-user-experience.html#forward-and-save-messages">forward and save messages</a> without revealing the source.</li>
|
||||
<li><a href="https://simplex.chat/blog/20240426-simplex-legally-binding-transparency-v5-7-better-user-experience.html#in-call-sounds-and-switching-sound-sources">in-call sounds and switching sound sources</a>.</li>
|
||||
<li><a href="https://simplex.chat/blog/20240426-simplex-legally-binding-transparency-v5-7-better-user-experience.html#network-management">better network connection management</a>.</li>
|
||||
<li><a href="https://simplex.chat/blog/20240426-simplex-legally-binding-transparency-v5-7-better-user-experience.html#customizable-shape-of-profile-images">customizable profile images</a></li>
|
||||
</ul>
|
||||
<p>Also, we added Lithuanian interface language to the Android and desktop apps, thanks to <a href="https://github.com/simplex-chat/simplex-chat#help-translating-simplex-chat">our users and Weblate</a>.</p>
|
||||
<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/index.html">Transparency Reports</a> page.</li>
|
||||
<li>We updated our <a href="https://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 updated our <a href="https://simplex.chat/blog/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="https://simplex.chat/faq/index.html">Frequently Asked Questions</a>, thanks to the guidance from users.</li>
|
||||
<li>We also have a new <a href="https://simplex.chat/security/index.html">Security Policy</a> – we welcome your feedback on it.</li>
|
||||
</ul>
|
||||
|
@ -2461,8 +2461,8 @@ file ---&gt; | XFTP | ------&gt; XFTP ----&
|
|||
<p><img src="https://simplex.chat/blog/images/20240426-profile1.png" width="288" /> <img src="https://simplex.chat/blog/images/20240426-profile2.png" width="288" /> <img src="https://simplex.chat/blog/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="https://simplex.chat/blog/20220511-simplex-chat-v2-images-files.html">How can SimpleX deliver messages without user identifiers</a>.</p>
|
||||
<p><a href="https://simplex.chat/blog/20220711-simplex-chat-v3-released-ios-notifications-audio-video-calls-database-export-import-protocol-improvements.html">What are the risks to have identifiers assigned to the users</a>.</p>
|
||||
<p><a href="https://simplex.chat/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="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">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://simplex.chat/faq/index.html">Frequently asked questions</a>.</p>
|
||||
<p>Please also see our <a href="https://simplex.chat/">website</a>.</p>
|
||||
|
@ -2500,10 +2500,10 @@ file ---&gt; | XFTP | ------&gt; XFTP ----&
|
|||
<p>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 <a href="https://eprint.iacr.org/2021/626.pdf">explained in detail here</a>:</p>
|
||||
<p><em>&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&quot;</em>.</p>
|
||||
<img src="https://simplex.chat/blog/images/20231125-mobile2.png" width="170" class="float-right" />
|
||||
<p>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's the reason we are not rushing a full multi-device support, and currently only provide <a href="https://simplex.chat/blog/20231125-simplex-chat-v5-4-link-mobile-desktop-quantum-resistant-better-groups.html">the ability to use mobile app profiles via the desktop app</a>, while they are on the same network.</p>
|
||||
<p>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's the reason we are not rushing a full multi-device support, and currently only provide <a href="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">the ability to use mobile app profiles via the desktop app</a>, while they are on the same network.</p>
|
||||
<p>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 <a href="https://www.wired.com/story/apple-google-push-notification-surveillance/">increases vulnerability</a>, 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 <a href="https://simplex.chat/blog/20220404-simplex-chat-instant-notifications.html">here</a>.</p>
|
||||
<p>Whenever possible, we strive to achieve significantly higher levels of privacy and security. For example, unlike most, if not all, applications (including Signal), <a href="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">we encrypt application files with per-file unique key</a>. Consequently, once a message is deleted, there'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 <a href="https://www.privacyguides.org/en/real-time-communication/#additional-options">not to be recommended</a> for &quot;long-term or sensitive communications&quot;. And <a href="https://simplifiedprivacy.com/spain-has-banned-telegram-defending-session/">misinformation</a> around this makes it dangerous and irresponsible to recommend without such necessary disclosures for people’s awareness.</p>
|
||||
<p>Session’s decision was based on <a href="https://getsession.org/blog/session-protocol-explained">the incorrect statements</a> 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 <a href="https://twitter.com/SimpleXChat/status/1755216356159414602">here</a>. We also made <a href="https://simplex.chat/blog/20240314-simplex-chat-v5-6-quantum-resistance-signal-double-ratchet-algorithm.html">a separate post</a> 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.</p>
|
||||
<p>Session’s decision was based on <a href="https://getsession.org/blog/session-protocol-explained">the incorrect statements</a> 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 <a href="https://twitter.com/SimpleXChat/status/1755216356159414602">here</a>. We also made <a href="https://simplex.chat/blog/20240314-simplex-chat-v5-6-quantum-resistance-signal-double-ratchet-algorithm.html#end-to-end-encryption-security-attacks-and-defense">a separate post</a> 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.</p>
|
||||
<h2 id="network-decentralization" tabindex="-1">Network decentralization</h2>
|
||||
<img src="https://simplex.chat/blog/images/simplex-explained.svg" width="40%" class="float-right" />
|
||||
<p>It'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'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.</p>
|
||||
|
@ -2511,7 +2511,7 @@ file ---&gt; | XFTP | ------&gt; XFTP ----&
|
|||
<p>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.</p>
|
||||
<p>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.</p>
|
||||
<h2 id="funding-and-profitability" tabindex="-1">Funding and profitability</h2>
|
||||
<p>We explain our rationale for funding <a href="https://simplex.chat/faq/index.html">here</a>. 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 <a href="https://simplex.chat/blog/20240404-why-i-joined-simplex-chat-esraa-al-shafei.html">here</a>.</p>
|
||||
<p>We explain our rationale for funding <a href="https://simplex.chat/faq/index.html#funding-and-business-model">here</a>. 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 <a href="https://simplex.chat/blog/20240404-why-i-joined-simplex-chat-esraa-al-shafei.html">here</a>.</p>
|
||||
<p>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.</p>
|
||||
<h2 id="company-jurisdiction" tabindex="-1">Company jurisdiction</h2>
|
||||
<img src="https://simplex.chat/blog/images/20240516-parliament.jpg" width="40%" class="float-right" />
|
||||
|
@ -2563,11 +2563,11 @@ file ---&gt; | XFTP | ------&gt; XFTP ----&
|
|||
<p><strong>Published:</strong> June 4, 2024</p>
|
||||
<p>What's new in v5.8:</p>
|
||||
<ul>
|
||||
<li><a href="https://simplex.chat/blog/undefined">private message routing</a>.</li>
|
||||
<li><a href="https://simplex.chat/blog/undefined">server transparency</a>.</li>
|
||||
<li><a href="https://simplex.chat/blog/undefined">protect IP address when downloading files &amp; media</a>.</li>
|
||||
<li><a href="https://simplex.chat/blog/undefined">chat themes</a> for better conversation privacy - in Android and desktop apps.</li>
|
||||
<li><a href="https://simplex.chat/blog/undefined">group improvements</a> - reduced traffic and additional preferences.</li>
|
||||
<li><a href="https://simplex.chat/blog/20240604-simplex-chat-v5.8-private-message-routing-chat-themes.html#private-message-routing">private message routing</a>.</li>
|
||||
<li><a href="https://simplex.chat/blog/20240604-simplex-chat-v5.8-private-message-routing-chat-themes.html#server-transparency">server transparency</a>.</li>
|
||||
<li><a href="https://simplex.chat/blog/20240604-simplex-chat-v5.8-private-message-routing-chat-themes.html#protect-ip-address-when-downloading-files--media">protect IP address when downloading files &amp; media</a>.</li>
|
||||
<li><a href="https://simplex.chat/blog/20240604-simplex-chat-v5.8-private-message-routing-chat-themes.html#chat-themes">chat themes</a> for better conversation privacy - in Android and desktop apps.</li>
|
||||
<li><a href="https://simplex.chat/blog/20240604-simplex-chat-v5.8-private-message-routing-chat-themes.html#group-improvements">group improvements</a> - reduced traffic and additional preferences.</li>
|
||||
<li>improved networking, message and file delivery.</li>
|
||||
</ul>
|
||||
<p>Also, we added Persian interface language to the Android and desktop apps, thanks to <a href="https://github.com/simplex-chat/simplex-chat#help-translating-simplex-chat">our users and Weblate</a>.</p>
|
||||
|
@ -2581,12 +2581,12 @@ file ---&gt; | XFTP | ------&gt; XFTP ----&
|
|||
<p>Tor is the best transport overlay network in existence, and it provides network anonymity for millions of Internet users.</p>
|
||||
<p>SimpleX Chat has many integration points with Tor:</p>
|
||||
<ul>
|
||||
<li>it allows <a href="https://simplex.chat/blog/20220901-simplex-chat-v3.2-incognito-mode.html">dual server addresses</a>, when the same messaging relay can be reached both via Tor and via clearnet.</li>
|
||||
<li>it utilises Tor's SOCKS proxy &quot;isolate-by-auth&quot; feature to create a new Tor circuit for each user profile, and with an additional option - for each contact. Per-contact <a href="https://simplex.chat/blog/20230204-simplex-chat-v4-5-user-chat-profiles.html">transport isolation</a> is still experimental, as it doesn't work if you connect to groups with many members, and it's only available if you enable developer tools.</li>
|
||||
<li>it allows <a href="https://simplex.chat/blog/20220901-simplex-chat-v3.2-incognito-mode.html#using-onion-server-addresses-with-tor">dual server addresses</a>, when the same messaging relay can be reached both via Tor and via clearnet.</li>
|
||||
<li>it utilises Tor's SOCKS proxy &quot;isolate-by-auth&quot; feature to create a new Tor circuit for each user profile, and with an additional option - for each contact. Per-contact <a href="https://simplex.chat/blog/20230204-simplex-chat-v4-5-user-chat-profiles.html#transport-isolation">transport isolation</a> is still experimental, as it doesn't work if you connect to groups with many members, and it's only available if you enable developer tools.</li>
|
||||
</ul>
|
||||
<p>Many SimpleX network design ideas are borrowed from Tor network design:</p>
|
||||
<ul>
|
||||
<li>mitigation of <a href="https://simplex.chat/docs/glossary.html">MITM attack</a> on client-server connection is done in the same way as Tor relays do it - the fingerprint of offline certificate is included in server address and validated by the client.</li>
|
||||
<li>mitigation of <a href="https://simplex.chat/docs/glossary.html#man-in-the-middle-attack">MITM attack</a> on client-server connection is done in the same way as Tor relays do it - the fingerprint of offline certificate is included in server address and validated by the client.</li>
|
||||
<li>the private routing itself uses the approach similar to onion routing, by adding encryption layers on each hop.</li>
|
||||
<li>we are also considering to implement Tor's <a href="https://blog.torproject.org/introducing-proof-of-work-defense-for-onion-services/">Proof-of-work DoS defence</a> mechanism.</li>
|
||||
</ul>
|
||||
|
@ -2630,7 +2630,7 @@ file ---&gt; | XFTP | ------&gt; XFTP ----&
|
|||
<p>We <a href="https://github.com/simplex-chat/simplexmq/blob/master/rfcs/2024-03-20-server-metadata.md">wrote previously</a> that it is important that server operators commit to running unmodified server code or disclose any code modifications, and also disclose server ownership and any other relevant information.</p>
|
||||
<p>While we cannot require the operators of self-hosted and private servers to disclose any information about them (apart from which server code they use - this is the requirement of the AGPLv3 license to share this information with users connecting to the server), as we add other server operators to the app, it is important for the users to have all important information about these operators and servers location.</p>
|
||||
<p>This server release adds server information page where all this information can be made available to the users. For example, this is <a href="https://smp8.simplex.im/" target="_blank">the information</a> about one of the servers preset in the app.</p>
|
||||
<p>The updated server guide also includes <a href="https://simplex.chat/docs/server.html">the instruction</a> about how to host this page for your server. It is generated as a static page when the server starts. We recommend using Caddy webserver to serve it.</p>
|
||||
<p>The updated server guide also includes <a href="https://simplex.chat/docs/server.html#">the instruction</a> about how to host this page for your server. It is generated as a static page when the server starts. We recommend using Caddy webserver to serve it.</p>
|
||||
<h2 id="more-new-things-in-v58" tabindex="-1">More new things in v5.8</h2>
|
||||
<h3 id="protect-ip-address-when-downloading-files-and-media" tabindex="-1">Protect IP address when downloading files &amp; media</h3>
|
||||
<p>This version added the protection of your IP address when receiving files from unknown file servers without Tor. Images and voice messages won't automatically download from unknown servers too until you tap them, and confirm that you trust the file server where they were uploaded.</p>
|
||||
|
@ -2644,8 +2644,8 @@ file ---&gt; | XFTP | ------&gt; XFTP ----&
|
|||
<p>We also stopped unnecessary traffic caused by the members who became inactive without leaving the groups - it should substantially reduce traffic and battery consumption to the users who send messages in large groups.</p>
|
||||
<h2 id="simplex-network" tabindex="-1">SimpleX network</h2>
|
||||
<p>Some links to answer the most common questions:</p>
|
||||
<p><a href="https://simplex.chat/blog/20220511-simplex-chat-v2-images-files.html">How can SimpleX deliver messages without user identifiers</a>.</p>
|
||||
<p><a href="https://simplex.chat/blog/20220711-simplex-chat-v3-released-ios-notifications-audio-video-calls-database-export-import-protocol-improvements.html">What are the risks to have identifiers assigned to the users</a>.</p>
|
||||
<p><a href="https://simplex.chat/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="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">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://simplex.chat/faq/index.html">Frequently asked questions</a>.</p>
|
||||
<p>Please also see our <a href="https://simplex.chat/">website</a>.</p>
|
||||
|
|
358
feed.rss
358
feed.rss
|
@ -13,11 +13,11 @@
|
|||
<p><strong>Published:</strong> June 4, 2024</p>
|
||||
<p>What's new in v5.8:</p>
|
||||
<ul>
|
||||
<li><a href="https://simplex.chat/blog/undefined">private message routing</a>.</li>
|
||||
<li><a href="https://simplex.chat/blog/undefined">server transparency</a>.</li>
|
||||
<li><a href="https://simplex.chat/blog/undefined">protect IP address when downloading files &amp; media</a>.</li>
|
||||
<li><a href="https://simplex.chat/blog/undefined">chat themes</a> for better conversation privacy - in Android and desktop apps.</li>
|
||||
<li><a href="https://simplex.chat/blog/undefined">group improvements</a> - reduced traffic and additional preferences.</li>
|
||||
<li><a href="https://simplex.chat/blog/20240604-simplex-chat-v5.8-private-message-routing-chat-themes.html#private-message-routing">private message routing</a>.</li>
|
||||
<li><a href="https://simplex.chat/blog/20240604-simplex-chat-v5.8-private-message-routing-chat-themes.html#server-transparency">server transparency</a>.</li>
|
||||
<li><a href="https://simplex.chat/blog/20240604-simplex-chat-v5.8-private-message-routing-chat-themes.html#protect-ip-address-when-downloading-files--media">protect IP address when downloading files &amp; media</a>.</li>
|
||||
<li><a href="https://simplex.chat/blog/20240604-simplex-chat-v5.8-private-message-routing-chat-themes.html#chat-themes">chat themes</a> for better conversation privacy - in Android and desktop apps.</li>
|
||||
<li><a href="https://simplex.chat/blog/20240604-simplex-chat-v5.8-private-message-routing-chat-themes.html#group-improvements">group improvements</a> - reduced traffic and additional preferences.</li>
|
||||
<li>improved networking, message and file delivery.</li>
|
||||
</ul>
|
||||
<p>Also, we added Persian interface language to the Android and desktop apps, thanks to <a href="https://github.com/simplex-chat/simplex-chat#help-translating-simplex-chat">our users and Weblate</a>.</p>
|
||||
|
@ -31,12 +31,12 @@
|
|||
<p>Tor is the best transport overlay network in existence, and it provides network anonymity for millions of Internet users.</p>
|
||||
<p>SimpleX Chat has many integration points with Tor:</p>
|
||||
<ul>
|
||||
<li>it allows <a href="https://simplex.chat/blog/20220901-simplex-chat-v3.2-incognito-mode.html">dual server addresses</a>, when the same messaging relay can be reached both via Tor and via clearnet.</li>
|
||||
<li>it utilises Tor's SOCKS proxy &quot;isolate-by-auth&quot; feature to create a new Tor circuit for each user profile, and with an additional option - for each contact. Per-contact <a href="https://simplex.chat/blog/20230204-simplex-chat-v4-5-user-chat-profiles.html">transport isolation</a> is still experimental, as it doesn't work if you connect to groups with many members, and it's only available if you enable developer tools.</li>
|
||||
<li>it allows <a href="https://simplex.chat/blog/20220901-simplex-chat-v3.2-incognito-mode.html#using-onion-server-addresses-with-tor">dual server addresses</a>, when the same messaging relay can be reached both via Tor and via clearnet.</li>
|
||||
<li>it utilises Tor's SOCKS proxy &quot;isolate-by-auth&quot; feature to create a new Tor circuit for each user profile, and with an additional option - for each contact. Per-contact <a href="https://simplex.chat/blog/20230204-simplex-chat-v4-5-user-chat-profiles.html#transport-isolation">transport isolation</a> is still experimental, as it doesn't work if you connect to groups with many members, and it's only available if you enable developer tools.</li>
|
||||
</ul>
|
||||
<p>Many SimpleX network design ideas are borrowed from Tor network design:</p>
|
||||
<ul>
|
||||
<li>mitigation of <a href="https://simplex.chat/docs/glossary.html">MITM attack</a> on client-server connection is done in the same way as Tor relays do it - the fingerprint of offline certificate is included in server address and validated by the client.</li>
|
||||
<li>mitigation of <a href="https://simplex.chat/docs/glossary.html#man-in-the-middle-attack">MITM attack</a> on client-server connection is done in the same way as Tor relays do it - the fingerprint of offline certificate is included in server address and validated by the client.</li>
|
||||
<li>the private routing itself uses the approach similar to onion routing, by adding encryption layers on each hop.</li>
|
||||
<li>we are also considering to implement Tor's <a href="https://blog.torproject.org/introducing-proof-of-work-defense-for-onion-services/">Proof-of-work DoS defence</a> mechanism.</li>
|
||||
</ul>
|
||||
|
@ -80,7 +80,7 @@
|
|||
<p>We <a href="https://github.com/simplex-chat/simplexmq/blob/master/rfcs/2024-03-20-server-metadata.md">wrote previously</a> that it is important that server operators commit to running unmodified server code or disclose any code modifications, and also disclose server ownership and any other relevant information.</p>
|
||||
<p>While we cannot require the operators of self-hosted and private servers to disclose any information about them (apart from which server code they use - this is the requirement of the AGPLv3 license to share this information with users connecting to the server), as we add other server operators to the app, it is important for the users to have all important information about these operators and servers location.</p>
|
||||
<p>This server release adds server information page where all this information can be made available to the users. For example, this is <a href="https://smp8.simplex.im/" target="_blank">the information</a> about one of the servers preset in the app.</p>
|
||||
<p>The updated server guide also includes <a href="https://simplex.chat/docs/server.html">the instruction</a> about how to host this page for your server. It is generated as a static page when the server starts. We recommend using Caddy webserver to serve it.</p>
|
||||
<p>The updated server guide also includes <a href="https://simplex.chat/docs/server.html#">the instruction</a> about how to host this page for your server. It is generated as a static page when the server starts. We recommend using Caddy webserver to serve it.</p>
|
||||
<h2 id="more-new-things-in-v58" tabindex="-1">More new things in v5.8</h2>
|
||||
<h3 id="protect-ip-address-when-downloading-files-and-media" tabindex="-1">Protect IP address when downloading files &amp; media</h3>
|
||||
<p>This version added the protection of your IP address when receiving files from unknown file servers without Tor. Images and voice messages won't automatically download from unknown servers too until you tap them, and confirm that you trust the file server where they were uploaded.</p>
|
||||
|
@ -94,8 +94,8 @@
|
|||
<p>We also stopped unnecessary traffic caused by the members who became inactive without leaving the groups - it should substantially reduce traffic and battery consumption to the users who send messages in large groups.</p>
|
||||
<h2 id="simplex-network" tabindex="-1">SimpleX network</h2>
|
||||
<p>Some links to answer the most common questions:</p>
|
||||
<p><a href="https://simplex.chat/blog/20220511-simplex-chat-v2-images-files.html">How can SimpleX deliver messages without user identifiers</a>.</p>
|
||||
<p><a href="https://simplex.chat/blog/20220711-simplex-chat-v3-released-ios-notifications-audio-video-calls-database-export-import-protocol-improvements.html">What are the risks to have identifiers assigned to the users</a>.</p>
|
||||
<p><a href="https://simplex.chat/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="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">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://simplex.chat/faq/index.html">Frequently asked questions</a>.</p>
|
||||
<p>Please also see our <a href="https://simplex.chat/">website</a>.</p>
|
||||
|
@ -153,10 +153,10 @@
|
|||
<p>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 <a href="https://eprint.iacr.org/2021/626.pdf">explained in detail here</a>:</p>
|
||||
<p><em>&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&quot;</em>.</p>
|
||||
<img src="https://simplex.chat/blog/images/20231125-mobile2.png" width="170" class="float-right" />
|
||||
<p>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's the reason we are not rushing a full multi-device support, and currently only provide <a href="https://simplex.chat/blog/20231125-simplex-chat-v5-4-link-mobile-desktop-quantum-resistant-better-groups.html">the ability to use mobile app profiles via the desktop app</a>, while they are on the same network.</p>
|
||||
<p>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's the reason we are not rushing a full multi-device support, and currently only provide <a href="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">the ability to use mobile app profiles via the desktop app</a>, while they are on the same network.</p>
|
||||
<p>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 <a href="https://www.wired.com/story/apple-google-push-notification-surveillance/">increases vulnerability</a>, 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 <a href="https://simplex.chat/blog/20220404-simplex-chat-instant-notifications.html">here</a>.</p>
|
||||
<p>Whenever possible, we strive to achieve significantly higher levels of privacy and security. For example, unlike most, if not all, applications (including Signal), <a href="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">we encrypt application files with per-file unique key</a>. Consequently, once a message is deleted, there'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 <a href="https://www.privacyguides.org/en/real-time-communication/#additional-options">not to be recommended</a> for &quot;long-term or sensitive communications&quot;. And <a href="https://simplifiedprivacy.com/spain-has-banned-telegram-defending-session/">misinformation</a> around this makes it dangerous and irresponsible to recommend without such necessary disclosures for people’s awareness.</p>
|
||||
<p>Session’s decision was based on <a href="https://getsession.org/blog/session-protocol-explained">the incorrect statements</a> 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 <a href="https://twitter.com/SimpleXChat/status/1755216356159414602">here</a>. We also made <a href="https://simplex.chat/blog/20240314-simplex-chat-v5-6-quantum-resistance-signal-double-ratchet-algorithm.html">a separate post</a> 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.</p>
|
||||
<p>Session’s decision was based on <a href="https://getsession.org/blog/session-protocol-explained">the incorrect statements</a> 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 <a href="https://twitter.com/SimpleXChat/status/1755216356159414602">here</a>. We also made <a href="https://simplex.chat/blog/20240314-simplex-chat-v5-6-quantum-resistance-signal-double-ratchet-algorithm.html#end-to-end-encryption-security-attacks-and-defense">a separate post</a> 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.</p>
|
||||
<h2 id="network-decentralization" tabindex="-1">Network decentralization</h2>
|
||||
<img src="https://simplex.chat/blog/images/simplex-explained.svg" width="40%" class="float-right" />
|
||||
<p>It'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'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.</p>
|
||||
|
@ -164,7 +164,7 @@
|
|||
<p>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.</p>
|
||||
<p>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.</p>
|
||||
<h2 id="funding-and-profitability" tabindex="-1">Funding and profitability</h2>
|
||||
<p>We explain our rationale for funding <a href="https://simplex.chat/faq/index.html">here</a>. 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 <a href="https://simplex.chat/blog/20240404-why-i-joined-simplex-chat-esraa-al-shafei.html">here</a>.</p>
|
||||
<p>We explain our rationale for funding <a href="https://simplex.chat/faq/index.html#funding-and-business-model">here</a>. 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 <a href="https://simplex.chat/blog/20240404-why-i-joined-simplex-chat-esraa-al-shafei.html">here</a>.</p>
|
||||
<p>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.</p>
|
||||
<h2 id="company-jurisdiction" tabindex="-1">Company jurisdiction</h2>
|
||||
<img src="https://simplex.chat/blog/images/20240516-parliament.jpg" width="40%" class="float-right" />
|
||||
|
@ -190,18 +190,18 @@
|
|||
<p><strong>Published:</strong> Apr 26, 2024</p>
|
||||
<p>What's new in v5.7:</p>
|
||||
<ul>
|
||||
<li><a href="https://simplex.chat/blog/undefined">quantum resistant end-to-end encryption</a> with all contacts.</li>
|
||||
<li><a href="https://simplex.chat/blog/undefined">forward and save messages</a> without revealing the source.</li>
|
||||
<li><a href="https://simplex.chat/blog/undefined">in-call sounds and switching sound sources</a>.</li>
|
||||
<li><a href="https://simplex.chat/blog/undefined">better network connection management</a>.</li>
|
||||
<li><a href="https://simplex.chat/blog/undefined">customizable profile images</a></li>
|
||||
<li><a href="https://simplex.chat/blog/20240426-simplex-legally-binding-transparency-v5-7-better-user-experience.html#quantum-resistant-end-to-end-encryption">quantum resistant end-to-end encryption</a> with all contacts.</li>
|
||||
<li><a href="https://simplex.chat/blog/20240426-simplex-legally-binding-transparency-v5-7-better-user-experience.html#forward-and-save-messages">forward and save messages</a> without revealing the source.</li>
|
||||
<li><a href="https://simplex.chat/blog/20240426-simplex-legally-binding-transparency-v5-7-better-user-experience.html#in-call-sounds-and-switching-sound-sources">in-call sounds and switching sound sources</a>.</li>
|
||||
<li><a href="https://simplex.chat/blog/20240426-simplex-legally-binding-transparency-v5-7-better-user-experience.html#network-management">better network connection management</a>.</li>
|
||||
<li><a href="https://simplex.chat/blog/20240426-simplex-legally-binding-transparency-v5-7-better-user-experience.html#customizable-shape-of-profile-images">customizable profile images</a></li>
|
||||
</ul>
|
||||
<p>Also, we added Lithuanian interface language to the Android and desktop apps, thanks to <a href="https://github.com/simplex-chat/simplex-chat#help-translating-simplex-chat">our users and Weblate</a>.</p>
|
||||
<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/index.html">Transparency Reports</a> page.</li>
|
||||
<li>We updated our <a href="https://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 updated our <a href="https://simplex.chat/blog/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="https://simplex.chat/faq/index.html">Frequently Asked Questions</a>, thanks to the guidance from users.</li>
|
||||
<li>We also have a new <a href="https://simplex.chat/security/index.html">Security Policy</a> – we welcome your feedback on it.</li>
|
||||
</ul>
|
||||
|
@ -239,8 +239,8 @@
|
|||
<p><img src="https://simplex.chat/blog/images/20240426-profile1.png" width="288" /> <img src="https://simplex.chat/blog/images/20240426-profile2.png" width="288" /> <img src="https://simplex.chat/blog/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="https://simplex.chat/blog/20220511-simplex-chat-v2-images-files.html">How can SimpleX deliver messages without user identifiers</a>.</p>
|
||||
<p><a href="https://simplex.chat/blog/20220711-simplex-chat-v3-released-ios-notifications-audio-video-calls-database-export-import-protocol-improvements.html">What are the risks to have identifiers assigned to the users</a>.</p>
|
||||
<p><a href="https://simplex.chat/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="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">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://simplex.chat/faq/index.html">Frequently asked questions</a>.</p>
|
||||
<p>Please also see our <a href="https://simplex.chat/">website</a>.</p>
|
||||
|
@ -282,7 +282,7 @@
|
|||
<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">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="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>
|
||||
<img src="https://simplex.chat/blog/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>
|
||||
|
@ -330,15 +330,15 @@
|
|||
<p><strong>Published:</strong> Mar 23, 2024</p>
|
||||
<p>SimpleX network: deliver real privacy via a profitable business and non-profit protocol governance:</p>
|
||||
<ul>
|
||||
<li><a href="https://simplex.chat/blog/undefined">community and business interests are aligned</a>.</li>
|
||||
<li><a href="https://simplex.chat/blog/undefined">the journey to the decentralized non-profit protocol governance</a>.</li>
|
||||
<li><a href="https://simplex.chat/blog/undefined">welcome, Esra’a</a>!</li>
|
||||
<li><a href="https://simplex.chat/blog/20240323-simplex-network-privacy-non-profit-v5-6-quantum-resistant-e2e-encryption-simple-migration.html#community-and-business-interests-are-aligned">community and business interests are aligned</a>.</li>
|
||||
<li><a href="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">the journey to the decentralized non-profit protocol governance</a>.</li>
|
||||
<li><a href="https://simplex.chat/blog/20240323-simplex-network-privacy-non-profit-v5-6-quantum-resistant-e2e-encryption-simple-migration.html#welcome-esraa">welcome, Esra’a</a>!</li>
|
||||
</ul>
|
||||
<p>What's new in v5.6:</p>
|
||||
<ul>
|
||||
<li><a href="https://simplex.chat/blog/undefined">quantum resistant end-to-end encryption</a> (BETA) – enable it for the new contacts.</li>
|
||||
<li><a href="https://simplex.chat/blog/undefined">use the app during the audio and video calls</a>.</li>
|
||||
<li><a href="https://simplex.chat/blog/undefined">migrate all app data to another device via QR code</a>.</li>
|
||||
<li><a href="https://simplex.chat/blog/20240323-simplex-network-privacy-non-profit-v5-6-quantum-resistant-e2e-encryption-simple-migration.html#quantum-resistant-end-to-end-encryption-beta">quantum resistant end-to-end encryption</a> (BETA) – enable it for the new contacts.</li>
|
||||
<li><a href="https://simplex.chat/blog/20240323-simplex-network-privacy-non-profit-v5-6-quantum-resistant-e2e-encryption-simple-migration.html#use-the-app-during-the-audio-and-video-calls">use the app during the audio and video calls</a>.</li>
|
||||
<li><a href="https://simplex.chat/blog/20240323-simplex-network-privacy-non-profit-v5-6-quantum-resistant-e2e-encryption-simple-migration.html#migrate-all-app-data-to-another-device-via-qr-code">migrate all app data to another device via QR code</a>.</li>
|
||||
</ul>
|
||||
<p>There are many other improvements and fixes in this release:</p>
|
||||
<ul>
|
||||
|
@ -361,7 +361,7 @@
|
|||
<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="https://simplex.chat/blog/20240314-simplex-chat-v5-6-quantum-resistance-signal-double-ratchet-algorithm.html">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="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">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="https://simplex.chat/blog/images/20240314-pq1.png" width="288" /> <img src="https://simplex.chat/blog/images/20240314-pq2.png" width="288" /> <img src="https://simplex.chat/blog/images/20240314-pq3.png" width="288" /></p>
|
||||
|
@ -386,8 +386,8 @@
|
|||
<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="https://simplex.chat/blog/20220711-simplex-chat-v3-released-ios-notifications-audio-video-calls-database-export-import-protocol-improvements.html">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="https://simplex.chat/blog/undefined">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>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="https://simplex.chat/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="https://simplex.chat/blog/20240323-simplex-network-privacy-non-profit-v5-6-quantum-resistant-e2e-encryption-simple-migration.html">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>
|
||||
<p><img src="https://simplex.chat/blog/images/20240323-migrate-from1.png" width="170" /> <img src="https://simplex.chat/blog/images/arrow.png" width="24" /> <img src="https://simplex.chat/blog/images/20240323-migrate-from2.png" width="170" /> <img src="https://simplex.chat/blog/images/arrow.png" width="24" /> <img src="https://simplex.chat/blog/images/20240323-migrate-from3.png" width="170" /> <img src="https://simplex.chat/blog/images/arrow.png" width="24" /> <img src="https://simplex.chat/blog/images/20240323-migrate-from4.png" width="170" /> <img src="https://simplex.chat/blog/images/arrow.png" width="24" /> <img src="https://simplex.chat/blog/images/20240323-migrate-from5.png" width="170" /></p>
|
||||
|
@ -412,8 +412,8 @@
|
|||
<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="https://simplex.chat/blog/20220511-simplex-chat-v2-images-files.html">How can SimpleX deliver messages without user identifiers</a>.</p>
|
||||
<p><a href="https://simplex.chat/blog/20220711-simplex-chat-v3-released-ios-notifications-audio-video-calls-database-export-import-protocol-improvements.html">What are the risks to have identifiers assigned to the users</a>.</p>
|
||||
<p><a href="https://simplex.chat/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="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">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>
|
||||
|
@ -442,9 +442,9 @@
|
|||
<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>
|
||||
<li><a href="https://simplex.chat/blog/undefined">Why do we need end-to-end encryption?</a></li>
|
||||
<li><a href="https://simplex.chat/blog/undefined">Why is encryption even allowed?</a></li>
|
||||
<li><a href="https://simplex.chat/blog/undefined">End-to-end encryption security: attacks and defense.</a>
|
||||
<li><a href="https://simplex.chat/blog/20240314-simplex-chat-v5-6-quantum-resistance-signal-double-ratchet-algorithm.html#why-do-we-need-end-to-end-encryption">Why do we need end-to-end encryption?</a></li>
|
||||
<li><a href="https://simplex.chat/blog/20240314-simplex-chat-v5-6-quantum-resistance-signal-double-ratchet-algorithm.html#why-is-encryption-even-allowed">Why is encryption even allowed?</a></li>
|
||||
<li><a href="https://simplex.chat/blog/20240314-simplex-chat-v5-6-quantum-resistance-signal-double-ratchet-algorithm.html#end-to-end-encryption-security-attacks-and-defense">End-to-end encryption security: attacks and defense.</a>
|
||||
<ol>
|
||||
<li>Compromised message size - mitigated by padding messages to a fixed block size.</li>
|
||||
<li>Compromised confidentiality - mitigated by repudiation (deniability).</li>
|
||||
|
@ -454,10 +454,10 @@
|
|||
<li>&quot;Record now, decrypt later&quot; attacks - mitigated by post-quantum cryptography.</li>
|
||||
</ol>
|
||||
</li>
|
||||
<li><a href="https://simplex.chat/blog/undefined">How secure is encryption in different messengers?</a></li>
|
||||
<li><a href="https://simplex.chat/blog/undefined">Adding quantum resistance to Signal double ratchet algorithm.</a></li>
|
||||
<li><a href="https://simplex.chat/blog/undefined">When can you start using quantum resistant chats?</a></li>
|
||||
<li><a href="https://simplex.chat/blog/undefined">Next for post-quantum crypto - all direct chats, small groups and security audit.</a></li>
|
||||
<li><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">How secure is encryption in different messengers?</a></li>
|
||||
<li><a href="https://simplex.chat/blog/20240314-simplex-chat-v5-6-quantum-resistance-signal-double-ratchet-algorithm.html#adding-quantum-resistance-to-signal-double-ratchet-algorithm">Adding quantum resistance to Signal double ratchet algorithm.</a></li>
|
||||
<li><a href="https://simplex.chat/blog/20240314-simplex-chat-v5-6-quantum-resistance-signal-double-ratchet-algorithm.html#when-can-you-start-using-quantum-resistant-chats">When can you start using quantum resistant chats?</a></li>
|
||||
<li><a href="https://simplex.chat/blog/20240314-simplex-chat-v5-6-quantum-resistance-signal-double-ratchet-algorithm.html#next-for-post-quantum-crypto---all-direct-chats-small-groups-and-security-audit">Next for post-quantum crypto - all direct chats, small groups and security audit.</a></li>
|
||||
</ul>
|
||||
<h2 id="why-do-we-need-end-to-end-encryption" tabindex="-1">Why do we need end-to-end encryption?</h2>
|
||||
<p>The objective of end-to-end encryption is to make any potential attackers, such as traffic observers or communication providers who pass the messages between senders and recipients, unable to recover <em>any</em> message content or meaningful information about the messages, even if these attackers possess very advanced computing and mathematical capabilities.</p>
|
||||
|
@ -490,7 +490,7 @@
|
|||
<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="https://simplex.chat/blog/20230103-simplex-chat-v4.4-disappearing-messages.html">disappearing messages</a> and the ability to <a href="https://simplex.chat/blog/20221206-simplex-chat-v4.3-voice-messages.html">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="https://simplex.chat/blog/20230103-simplex-chat-v4.4-disappearing-messages.html#disappearing-messages">disappearing messages</a> and the ability to <a href="https://simplex.chat/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>
|
||||
|
@ -584,8 +584,8 @@
|
|||
<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="https://simplex.chat/blog/20220511-simplex-chat-v2-images-files.html">How can SimpleX deliver messages without user identifiers</a>.</p>
|
||||
<p><a href="https://simplex.chat/blog/20220711-simplex-chat-v3-released-ios-notifications-audio-video-calls-database-export-import-protocol-improvements.html">What are the risks to have identifiers assigned to the users</a>.</p>
|
||||
<p><a href="https://simplex.chat/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="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">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>
|
||||
|
@ -611,7 +611,7 @@
|
|||
<link>https://simplex.chat/blog/20240124-simplex-chat-infrastructure-costs-v5-5-simplex-ux-private-notes-group-history.html</link>
|
||||
<description><h1 id="simplex-chat-free-infrastructure-from-linode-v55-released-with-private-notes-group-history-and-a-simpler-ux-to-connect" tabindex="-1">SimpleX Chat: free infrastructure from Linode, v5.5 released with private notes, group history and a simpler UX to connect.</h1>
|
||||
<p><strong>Published:</strong> Jan 24, 2024</p>
|
||||
<p><a href="https://simplex.chat/blog/undefined">SimpleX Chat infrastructure on Linode</a>:</p>
|
||||
<p><a href="https://simplex.chat/blog/20240124-simplex-chat-infrastructure-costs-v5-5-simplex-ux-private-notes-group-history.html#simplex-chat-infrastructure-on-linode">SimpleX Chat infrastructure on Linode</a>:</p>
|
||||
<ul>
|
||||
<li>Free infrastructure.</li>
|
||||
<li>SimpleX servers in Linode Marketplace.</li>
|
||||
|
@ -619,10 +619,10 @@
|
|||
</ul>
|
||||
<p>What's new in v5.5:</p>
|
||||
<ul>
|
||||
<li><a href="https://simplex.chat/blog/undefined">private notes</a></li>
|
||||
<li><a href="https://simplex.chat/blog/undefined">group history</a></li>
|
||||
<li><a href="https://simplex.chat/blog/undefined">simpler UX to connect to other users</a></li>
|
||||
<li><a href="https://simplex.chat/blog/undefined">message delivery stability and other improvements</a></li>
|
||||
<li><a href="https://simplex.chat/blog/20240124-simplex-chat-infrastructure-costs-v5-5-simplex-ux-private-notes-group-history.html#private-notes">private notes</a></li>
|
||||
<li><a href="https://simplex.chat/blog/20240124-simplex-chat-infrastructure-costs-v5-5-simplex-ux-private-notes-group-history.html#group-history">group history</a></li>
|
||||
<li><a href="https://simplex.chat/blog/20240124-simplex-chat-infrastructure-costs-v5-5-simplex-ux-private-notes-group-history.html#simpler-ux-to-connect-to-other-users">simpler UX to connect to other users</a></li>
|
||||
<li><a href="https://simplex.chat/blog/20240124-simplex-chat-infrastructure-costs-v5-5-simplex-ux-private-notes-group-history.html#message-delivery-stability-and-other-improvements">message delivery stability and other improvements</a></li>
|
||||
</ul>
|
||||
<p>Also, we added Hungarian (only Android) and Turkish interface languages, thanks to <a href="https://github.com/simplex-chat/simplex-chat#help-translating-simplex-chat">our users and Weblate</a>.</p>
|
||||
<p>SimpleX Chat Android app is now available in 20 languages!</p>
|
||||
|
@ -669,8 +669,8 @@
|
|||
</ul>
|
||||
<h2 id="simplex-platform" tabindex="-1">SimpleX platform</h2>
|
||||
<p>Some links to answer the most common questions:</p>
|
||||
<p><a href="https://simplex.chat/blog/20220511-simplex-chat-v2-images-files.html">How can SimpleX deliver messages without user identifiers</a>.</p>
|
||||
<p><a href="https://simplex.chat/blog/20220711-simplex-chat-v3-released-ios-notifications-audio-video-calls-database-export-import-protocol-improvements.html">What are the risks to have identifiers assigned to the users</a>.</p>
|
||||
<p><a href="https://simplex.chat/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="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">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>
|
||||
|
@ -697,17 +697,17 @@
|
|||
<p><strong>Published:</strong> Nov 25, 2023</p>
|
||||
<p><strong>What's new in v5.4:</strong></p>
|
||||
<ul>
|
||||
<li><a href="https://simplex.chat/blog/undefined">Link mobile and desktop apps via secure quantum-resistant protocol</a>.
|
||||
<li><a href="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">Link mobile and desktop apps via secure quantum-resistant protocol</a>.
|
||||
<ul>
|
||||
<li>⚡️ Quick start - how to use it.</li>
|
||||
<li>How does it work?</li>
|
||||
<li>🤖 Connecting to remote CLI.</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li><a href="https://simplex.chat/blog/undefined">Better groups</a>.
|
||||
<li><a href="https://simplex.chat/blog/20231125-simplex-chat-v5-4-link-mobile-desktop-quantum-resistant-better-groups.html#better-groups">Better groups</a>.
|
||||
<ul>
|
||||
<li><a href="https://simplex.chat/blog/undefined">Faster to join and more reliable</a>.</li>
|
||||
<li><a href="https://simplex.chat/blog/undefined">New group features</a>:
|
||||
<li><a href="https://simplex.chat/blog/20231125-simplex-chat-v5-4-link-mobile-desktop-quantum-resistant-better-groups.html#faster-to-join-with-more-reliable-message-delivery">Faster to join and more reliable</a>.</li>
|
||||
<li><a href="https://simplex.chat/blog/20231125-simplex-chat-v5-4-link-mobile-desktop-quantum-resistant-better-groups.html#new-group-features">New group features</a>:
|
||||
<ul>
|
||||
<li>create groups with incognito profile,</li>
|
||||
<li>block group members to reduce noise,</li>
|
||||
|
@ -716,9 +716,9 @@
|
|||
</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li><a href="https://simplex.chat/blog/undefined">Better calls</a>: faster to connect, with screen sharing on desktop.</li>
|
||||
<li><a href="https://simplex.chat/blog/20231125-simplex-chat-v5-4-link-mobile-desktop-quantum-resistant-better-groups.html#better-calls">Better calls</a>: faster to connect, with screen sharing on desktop.</li>
|
||||
</ul>
|
||||
<p>There are many <a href="https://simplex.chat/blog/undefined">other improvements</a> and fixes in this release:</p>
|
||||
<p>There are many <a href="https://simplex.chat/blog/20231125-simplex-chat-v5-4-link-mobile-desktop-quantum-resistant-better-groups.html#other-improvements">other improvements</a> and fixes in this release:</p>
|
||||
<ul>
|
||||
<li>profile names now allow spaces.</li>
|
||||
<li>when you delete contacts, they are optionally notified.</li>
|
||||
|
@ -740,7 +740,7 @@
|
|||
<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="https://simplex.chat/docs/glossary.html">double-ratchet algorithm</a>, with <a href="https://simplex.chat/docs/glossary.html">perfect forward secrecy</a>, <a href="https://simplex.chat/docs/glossary.html">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="https://simplex.chat/docs/glossary.html#double-ratchet-algorithm">double-ratchet algorithm</a>, with <a href="https://simplex.chat/docs/glossary.html#forward-secrecy">perfect forward secrecy</a>, <a href="https://simplex.chat/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>
|
||||
|
@ -780,8 +780,8 @@
|
|||
<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="https://simplex.chat/blog/20220511-simplex-chat-v2-images-files.html">How can SimpleX deliver messages without user identifiers</a>.</p>
|
||||
<p><a href="https://simplex.chat/blog/20220711-simplex-chat-v3-released-ios-notifications-audio-video-calls-database-export-import-protocol-improvements.html">What are the risks to have identifiers assigned to the users</a>.</p>
|
||||
<p><a href="https://simplex.chat/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="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">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>
|
||||
|
@ -808,10 +808,10 @@
|
|||
<p><strong>Published:</strong> September 25, 2023</p>
|
||||
<p><strong>What's new in v5.3:</strong></p>
|
||||
<ul>
|
||||
<li><a href="https://simplex.chat/blog/undefined">new desktop app!</a>!</li>
|
||||
<li><a href="https://simplex.chat/blog/undefined">directory service and other group improvements</a>.</li>
|
||||
<li><a href="https://simplex.chat/blog/undefined">encrypted local files and media with forward secrecy</a>.</li>
|
||||
<li><a href="https://simplex.chat/blog/undefined">simplified incognito mode</a>.</li>
|
||||
<li><a href="https://simplex.chat/blog/20230925-simplex-chat-v5-3-desktop-app-local-file-encryption-directory-service.html#multiplatform-desktop-app">new desktop app!</a>!</li>
|
||||
<li><a href="https://simplex.chat/blog/20230925-simplex-chat-v5-3-desktop-app-local-file-encryption-directory-service.html#group-directory-service-and-other-group-improvements">directory service and other group improvements</a>.</li>
|
||||
<li><a href="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">encrypted local files and media with forward secrecy</a>.</li>
|
||||
<li><a href="https://simplex.chat/blog/20230925-simplex-chat-v5-3-desktop-app-local-file-encryption-directory-service.html#simplified-incognito-mode">simplified incognito mode</a>.</li>
|
||||
</ul>
|
||||
<p>There are a lot of other improvements and fixes in this release:</p>
|
||||
<ul>
|
||||
|
@ -904,16 +904,16 @@
|
|||
<p><strong>Published:</strong> July 22, 2023</p>
|
||||
<p><strong>What's new in v5.2:</strong></p>
|
||||
<ul>
|
||||
<li><a href="https://simplex.chat/blog/undefined">message delivery receipts</a> – with opt-out per contact!</li>
|
||||
<li><a href="https://simplex.chat/blog/undefined">filter favorite and unread chats</a>.</li>
|
||||
<li><a href="https://simplex.chat/blog/undefined">more usable groups</a>:
|
||||
<li><a href="https://simplex.chat/blog/20230722-simplex-chat-v5-2-message-delivery-receipts.html#message-delivery-receipts">message delivery receipts</a> – with opt-out per contact!</li>
|
||||
<li><a href="https://simplex.chat/blog/20230722-simplex-chat-v5-2-message-delivery-receipts.html#filter-favorite-and-unread-chats">filter favorite and unread chats</a>.</li>
|
||||
<li><a href="https://simplex.chat/blog/20230722-simplex-chat-v5-2-message-delivery-receipts.html#more-usable-groups">more usable groups</a>:
|
||||
<ul>
|
||||
<li>view full original replied message in info.</li>
|
||||
<li>share your address with your contacts and group members via your chat profile.</li>
|
||||
<li>search new and existing members.</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li><a href="https://simplex.chat/blog/undefined">stability improvements</a>:
|
||||
<li><a href="https://simplex.chat/blog/20230722-simplex-chat-v5-2-message-delivery-receipts.html#stability-improvements">stability improvements</a>:
|
||||
<ul>
|
||||
<li>keep your connections working after restoring from backup.</li>
|
||||
<li>restart app (Android) or reconnect servers (iOS).</li>
|
||||
|
@ -923,28 +923,28 @@
|
|||
</li>
|
||||
<li>other improvements:
|
||||
<ul>
|
||||
<li><a href="https://simplex.chat/blog/undefined">better disappearing messages</a>.</li>
|
||||
<li><a href="https://simplex.chat/blog/undefined">prohibit message reactions</a>.</li>
|
||||
<li><a href="https://simplex.chat/blog/20230722-simplex-chat-v5-2-message-delivery-receipts.html#better-disappearing-messages">better disappearing messages</a>.</li>
|
||||
<li><a href="https://simplex.chat/blog/20230722-simplex-chat-v5-2-message-delivery-receipts.html#prohibit-message-reactions">prohibit message reactions</a>.</li>
|
||||
</ul>
|
||||
</li>
|
||||
</ul>
|
||||
<p><strong>Platform evolution:</strong></p>
|
||||
<ul>
|
||||
<li><a href="https://simplex.chat/blog/undefined">problems of public groups</a>:
|
||||
<li><a href="https://simplex.chat/blog/20230722-simplex-chat-v5-2-message-delivery-receipts.html#problems-of-public-groups">problems of public groups</a>:
|
||||
<ul>
|
||||
<li>why not all messages are received.</li>
|
||||
<li>how to cope with these problems.</li>
|
||||
<li>when will public groups be more usable.</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li><a href="https://simplex.chat/blog/undefined">what about read receipts?</a></li>
|
||||
<li><a href="https://simplex.chat/blog/20230722-simplex-chat-v5-2-message-delivery-receipts.html#what-about-read-receipts">what about read receipts?</a></li>
|
||||
</ul>
|
||||
<h2 id="whats-new-in-v52" tabindex="-1">What's new in v5.2</h2>
|
||||
<h3 id="message-delivery-receipts" tabindex="-1">Message delivery receipts</h3>
|
||||
<img src="https://simplex.chat/blog/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="https://simplex.chat/blog/20230328-simplex-chat-v4-6-hidden-profiles.html">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="https://simplex.chat/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="https://simplex.chat/blog/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>
|
||||
|
@ -963,8 +963,8 @@
|
|||
<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="https://simplex.chat/docs/glossary.html">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="https://simplex.chat/docs/glossary.html">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="https://simplex.chat/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="https://simplex.chat/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>
|
||||
|
@ -984,12 +984,12 @@
|
|||
<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="https://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>
|
||||
<p>We also <a href="https://simplex.chat/blog/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="https://github.com/simplex-chat/simplex-chat/blob/stable/simplex-chat/docs/rfcs/2023-05-22-groups-moderation.md">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://simplex.chat/blog/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>
|
||||
|
@ -1028,16 +1028,16 @@
|
|||
<p><strong>Published:</strong> May 23, 2023</p>
|
||||
<p>What's new in v5.1:</p>
|
||||
<ul>
|
||||
<li><a href="https://simplex.chat/blog/undefined">message reactions</a> 🚀</li>
|
||||
<li><a href="https://simplex.chat/blog/undefined">improved messages</a>:
|
||||
<li><a href="https://simplex.chat/blog/20230523-simplex-chat-v5-1-message-reactions-self-destruct-passcode.html#message-reactions">message reactions</a> 🚀</li>
|
||||
<li><a href="https://simplex.chat/blog/20230523-simplex-chat-v5-1-message-reactions-self-destruct-passcode.html#improved-messages">improved messages</a>:
|
||||
<ul>
|
||||
<li><a href="https://simplex.chat/blog/undefined">voice messages up to 5 minutes</a>.</li>
|
||||
<li><a href="https://simplex.chat/blog/undefined">custom time to disappear</a>.</li>
|
||||
<li><a href="https://simplex.chat/blog/undefined">message editing history</a>.</li>
|
||||
<li><a href="https://simplex.chat/blog/20230523-simplex-chat-v5-1-message-reactions-self-destruct-passcode.html#voice-messages-up-to-5-minutes-better-quality-playback-control">voice messages up to 5 minutes</a>.</li>
|
||||
<li><a href="https://simplex.chat/blog/20230523-simplex-chat-v5-1-message-reactions-self-destruct-passcode.html#disappearing-messages-choose-any-time">custom time to disappear</a>.</li>
|
||||
<li><a href="https://simplex.chat/blog/20230523-simplex-chat-v5-1-message-reactions-self-destruct-passcode.html#message-editing-history">message editing history</a>.</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li>new design and <a href="https://simplex.chat/blog/undefined">customizable themes</a> that you can share!<sup>*</sup></li>
|
||||
<li><a href="https://simplex.chat/blog/undefined">self-destruct passcode</a></li>
|
||||
<li>new design and <a href="https://simplex.chat/blog/20230523-simplex-chat-v5-1-message-reactions-self-destruct-passcode.html#customize-and-share-color-themes">customizable themes</a> that you can share!<sup>*</sup></li>
|
||||
<li><a href="https://simplex.chat/blog/20230523-simplex-chat-v5-1-message-reactions-self-destruct-passcode.html#self-destruct-passcode">self-destruct passcode</a></li>
|
||||
</ul>
|
||||
<p>There are lots of small improvements and fixes in this release:</p>
|
||||
<ul>
|
||||
|
@ -1059,15 +1059,15 @@
|
|||
<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="https://simplex.chat/blog/images/20230523-voice.png" width="288" class="float-to-left" />
|
||||
<p>Since <a href="https://simplex.chat/blog/20221206-simplex-chat-v4.3-voice-messages.html">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="https://simplex.chat/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="https://simplex.chat/blog/images/20230523-disappearing1.png" width="288" /> <img src="https://simplex.chat/blog/images/20230523-disappearing2.png" width="288" /></p>
|
||||
<p>Since <a href="https://simplex.chat/blog/20230103-simplex-chat-v4.4-disappearing-messages.html">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="https://simplex.chat/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="https://simplex.chat/blog/images/20230523-info.png" width="288" class="float-to-left" />
|
||||
<p>I <a href="https://simplex.chat/blog/20221206-simplex-chat-v4.3-voice-messages.html">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="https://simplex.chat/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="https://simplex.chat/blog/images/20230523-theme.png" width="288" class="float-to-left" />
|
||||
|
@ -1114,15 +1114,15 @@
|
|||
<p><strong>Published:</strong> Apr 22, 2023</p>
|
||||
<p>SimpleX Chat vision and funding:</p>
|
||||
<ul>
|
||||
<li><a href="https://simplex.chat/blog/undefined">why is it a commercial company?</a></li>
|
||||
<li><a href="https://simplex.chat/blog/undefined">how is it funded and what is the business model?</a></li>
|
||||
<li><a href="https://simplex.chat/blog/undefined">what is next?</a></li>
|
||||
<li><a href="https://simplex.chat/blog/20230422-simplex-chat-vision-funding-v5-videos-files-passcode.html#why-is-it-a-commercial-company">why is it a commercial company?</a></li>
|
||||
<li><a href="https://simplex.chat/blog/20230422-simplex-chat-vision-funding-v5-videos-files-passcode.html#how-is-it-funded-and-what-is-the-business-model">how is it funded and what is the business model?</a></li>
|
||||
<li><a href="https://simplex.chat/blog/20230422-simplex-chat-vision-funding-v5-videos-files-passcode.html#what-is-next">what is next?</a></li>
|
||||
</ul>
|
||||
<p>What's new in v5.0:</p>
|
||||
<ul>
|
||||
<li><a href="https://simplex.chat/blog/undefined">send videos and files up to 1gb</a></li>
|
||||
<li><a href="https://simplex.chat/blog/undefined">app passcode independent from system authentication</a></li>
|
||||
<li><a href="https://simplex.chat/blog/undefined">networking improvements</a></li>
|
||||
<li><a href="https://simplex.chat/blog/20230422-simplex-chat-vision-funding-v5-videos-files-passcode.html#send-videos-and-files-up-to-1gb">send videos and files up to 1gb</a></li>
|
||||
<li><a href="https://simplex.chat/blog/20230422-simplex-chat-vision-funding-v5-videos-files-passcode.html#app-passcode">app passcode independent from system authentication</a></li>
|
||||
<li><a href="https://simplex.chat/blog/20230422-simplex-chat-vision-funding-v5-videos-files-passcode.html#networking-improvements">networking improvements</a></li>
|
||||
</ul>
|
||||
<p>Also, we added Polish interface language, thanks to <a href="https://github.com/simplex-chat/simplex-chat#help-translating-simplex-chat">the users' community and Weblate</a>.</p>
|
||||
<p>SimpleX Chat apps are now available in 10 languages!</p>
|
||||
|
@ -1142,7 +1142,7 @@
|
|||
<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="https://simplex.chat/blog/20220901-simplex-chat-v3.2-incognito-mode.html">incognito mode</a>, <a href="https://simplex.chat/blog/20230103-simplex-chat-v4.4-disappearing-messages.html">live messages</a> and <a href="https://simplex.chat/blog/20230328-simplex-chat-v4-6-hidden-profiles.html">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="https://simplex.chat/blog/20220901-simplex-chat-v3.2-incognito-mode.html#incognito-mode">incognito mode</a>, <a href="https://simplex.chat/blog/20230103-simplex-chat-v4.4-disappearing-messages.html#live-messages">live messages</a> and <a href="https://simplex.chat/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>
|
||||
|
@ -1198,15 +1198,15 @@
|
|||
<p><strong>Published:</strong> Mar 28, 2023</p>
|
||||
<h2 id="whats-new-in-v46" tabindex="-1">What's new in v4.6</h2>
|
||||
<ul>
|
||||
<li><a href="https://simplex.chat/blog/undefined">ARMv7a and Android 8+ support</a></li>
|
||||
<li><a href="https://simplex.chat/blog/undefined">hidden chat profiles</a></li>
|
||||
<li><a href="https://simplex.chat/blog/undefined">group / community moderation</a></li>
|
||||
<li><a href="https://simplex.chat/blog/undefined">group welcome message</a></li>
|
||||
<li><a href="https://simplex.chat/blog/undefined">improved audio/video calls</a></li>
|
||||
<li><a href="https://simplex.chat/blog/undefined">reduced battery usage</a>.</li>
|
||||
<li><a href="https://simplex.chat/blog/undefined">SMP server monitoring: status bot and page</a></li>
|
||||
<li><a href="https://simplex.chat/blog/20230328-simplex-chat-v4-6-hidden-profiles.html#armv7a-32-bit-and-android-8-support">ARMv7a and Android 8+ support</a></li>
|
||||
<li><a href="https://simplex.chat/blog/20230328-simplex-chat-v4-6-hidden-profiles.html#hidden-chat-profiles">hidden chat profiles</a></li>
|
||||
<li><a href="https://simplex.chat/blog/20230328-simplex-chat-v4-6-hidden-profiles.html#group--community-moderation">group / community moderation</a></li>
|
||||
<li><a href="https://simplex.chat/blog/20230328-simplex-chat-v4-6-hidden-profiles.html#group-welcome-message">group welcome message</a></li>
|
||||
<li><a href="https://simplex.chat/blog/20230328-simplex-chat-v4-6-hidden-profiles.html#improved-audiovideo-calls">improved audio/video calls</a></li>
|
||||
<li><a href="https://simplex.chat/blog/20230328-simplex-chat-v4-6-hidden-profiles.html#reduced-battery-usage">reduced battery usage</a>.</li>
|
||||
<li><a href="https://simplex.chat/blog/20230328-simplex-chat-v4-6-hidden-profiles.html#smp-server-monitoring">SMP server monitoring: status bot and page</a></li>
|
||||
</ul>
|
||||
<p>Also, we added <a href="https://simplex.chat/blog/undefined">Chinese and Spanish interface languages</a>, thanks to the users' community and Weblate!</p>
|
||||
<p>Also, we added <a href="https://simplex.chat/blog/20230328-simplex-chat-v4-6-hidden-profiles.html#chinese-and-spanish-interface---you-can-choose-the-language-via-the-app">Chinese and Spanish interface languages</a>, thanks to the users' community and Weblate!</p>
|
||||
<h3 id="armv7a-32-bit-and-android-8-support" tabindex="-1">ARMv7a (32 bit) and Android 8+ support!</h3>
|
||||
<p>It increases the number of supported Android devices twice - now most of your friends should be able to install SimpleX Chat. SimpleX Chat still doesn't support Android 7 and erlier versions.</p>
|
||||
<p>If you install the app from GitHub or F-Droid you need to choose the correct APK, Play Store will provide it automatically.</p>
|
||||
|
@ -1272,11 +1272,11 @@
|
|||
<description><h1 id="simplex-file-transfer-protocol-a-new-protocol-for-sending-large-files-efficiently-privately-and-securely" tabindex="-1">SimpleX File Transfer Protocol – a new protocol for sending large files efficiently, privately and securely.</h1>
|
||||
<p><strong>Published:</strong> Mar 1, 2023</p>
|
||||
<ul>
|
||||
<li><a href="https://simplex.chat/blog/undefined">Quick start: how to send a file using XFTP CLI</a></li>
|
||||
<li><a href="https://simplex.chat/blog/undefined">What's the problem</a></li>
|
||||
<li><a href="https://simplex.chat/blog/undefined">Why didn't we just use some existing solution?</a></li>
|
||||
<li><a href="https://simplex.chat/blog/undefined">What is XFTP and how does it work?</a></li>
|
||||
<li><a href="https://simplex.chat/blog/undefined">What is next?</a></li>
|
||||
<li><a href="https://simplex.chat/blog/20230301-simplex-file-transfer-protocol.html#%E2%9A%A1%EF%B8%8F-quick-start-send-a-file-with-xftp-cli-in-3-simple-steps">Quick start: how to send a file using XFTP CLI</a></li>
|
||||
<li><a href="https://simplex.chat/blog/20230301-simplex-file-transfer-protocol.html#whats-the-problem">What's the problem</a></li>
|
||||
<li><a href="https://simplex.chat/blog/20230301-simplex-file-transfer-protocol.html#why-didnt-we-just-use-some-existing-solution">Why didn't we just use some existing solution?</a></li>
|
||||
<li><a href="https://simplex.chat/blog/20230301-simplex-file-transfer-protocol.html#what-is-xftp-and-how-does-it-work">What is XFTP and how does it work?</a></li>
|
||||
<li><a href="https://simplex.chat/blog/20230301-simplex-file-transfer-protocol.html#what-is-next">What is next?</a></li>
|
||||
</ul>
|
||||
<h2 id="quick-start-send-a-file-with-xftp-cli-in-3-simple-steps" tabindex="-1">⚡️ Quick start: send a file with XFTP CLI in 3 simple steps</h2>
|
||||
<p>Download XFTP binary for Linux from <a href="https://github.com/simplex-chat/simplexmq/releases/tag/v5.0.0-beta.3">the release</a> – you need the file <code>xftp-ubuntu-20_04-x86-64</code> - rename it as <code>xftp</code>.</p>
|
||||
|
@ -1356,8 +1356,8 @@ file ---&gt; | XFTP | ------&gt; XFTP ----&
|
|||
<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="https://simplex.chat/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="https://simplex.chat/blog/20220511-simplex-chat-v2-images-files.html">How can SimpleX deliver messages without user identifiers</a>.</p>
|
||||
<p><a href="https://simplex.chat/blog/20220711-simplex-chat-v3-released-ios-notifications-audio-video-calls-database-export-import-protocol-improvements.html">What are the risks to have identifiers assigned to the users</a>.</p>
|
||||
<p><a href="https://simplex.chat/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="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">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>
|
||||
|
@ -1384,13 +1384,13 @@ file ---&gt; | XFTP | ------&gt; XFTP ----&
|
|||
<p><strong>Published:</strong> Feb 4, 2023</p>
|
||||
<h2 id="whats-new-in-v45" tabindex="-1">What's new in v4.5</h2>
|
||||
<ul>
|
||||
<li><a href="https://simplex.chat/blog/undefined">multiple chat profiles</a>.</li>
|
||||
<li><a href="https://simplex.chat/blog/undefined">message draft</a>.</li>
|
||||
<li><a href="https://simplex.chat/blog/undefined">transport isolation</a>.</li>
|
||||
<li><a href="https://simplex.chat/blog/undefined">reduced battery usage</a>.</li>
|
||||
<li><a href="https://simplex.chat/blog/undefined">private filenames</a>.</li>
|
||||
<li><a href="https://simplex.chat/blog/20230204-simplex-chat-v4-5-user-chat-profiles.html#multiple-chat-profiles">multiple chat profiles</a>.</li>
|
||||
<li><a href="https://simplex.chat/blog/20230204-simplex-chat-v4-5-user-chat-profiles.html#message-draft">message draft</a>.</li>
|
||||
<li><a href="https://simplex.chat/blog/20230204-simplex-chat-v4-5-user-chat-profiles.html#transport-isolation">transport isolation</a>.</li>
|
||||
<li><a href="https://simplex.chat/blog/20230204-simplex-chat-v4-5-user-chat-profiles.html#reduced-battery-usage">reduced battery usage</a>.</li>
|
||||
<li><a href="https://simplex.chat/blog/20230204-simplex-chat-v4-5-user-chat-profiles.html#private-filenames">private filenames</a>.</li>
|
||||
</ul>
|
||||
<p>Also, we added <a href="https://simplex.chat/blog/undefined">Italian interface</a>, thanks to the users' community and Weblate!</p>
|
||||
<p>Also, we added <a href="https://simplex.chat/blog/20230204-simplex-chat-v4-5-user-chat-profiles.html#italian-interface">Italian interface</a>, thanks to the users' community and Weblate!</p>
|
||||
<h3 id="multiple-chat-profiles" tabindex="-1">Multiple chat profiles</h3>
|
||||
<p><img src="https://simplex.chat/blog/images/20230204-profiles1.png" width="288" /> <img src="https://simplex.chat/blog/images/20230204-profiles2.png" width="288" /></p>
|
||||
<p>Incognito mode added in v3.2 allows to share a random profile name with your new contacts. It is quite popular - more than half of users connecting to our support profile use it. In case when you just want a throw-away profile name that doesn't share any information about you it is more convenient that creating a new profile for each contact manually.</p>
|
||||
|
@ -1436,8 +1436,8 @@ file ---&gt; | XFTP | ------&gt; XFTP ----&
|
|||
<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="https://simplex.chat/blog/20220511-simplex-chat-v2-images-files.html">How can SimpleX deliver messages without user identifiers</a>.</p>
|
||||
<p><a href="https://simplex.chat/blog/20220711-simplex-chat-v3-released-ios-notifications-audio-video-calls-database-export-import-protocol-improvements.html">What are the risks to have identifiers assigned to the users</a>.</p>
|
||||
<p><a href="https://simplex.chat/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="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">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>
|
||||
|
@ -1464,16 +1464,16 @@ file ---&gt; | XFTP | ------&gt; XFTP ----&
|
|||
<p><strong>Published:</strong> Jan 3, 2023</p>
|
||||
<h2 id="whats-new-in-v44" tabindex="-1">What's new in v4.4</h2>
|
||||
<ul>
|
||||
<li><a href="https://simplex.chat/blog/undefined">disappearing messages</a>.</li>
|
||||
<li><a href="https://simplex.chat/blog/undefined">&quot;live&quot; messages</a>.</li>
|
||||
<li><a href="https://simplex.chat/blog/undefined">connection security verification</a>.</li>
|
||||
<li><a href="https://simplex.chat/blog/undefined">animated images and stickers</a> – now on iOS too.</li>
|
||||
<li><a href="https://simplex.chat/blog/20230103-simplex-chat-v4.4-disappearing-messages.html#disappearing-messages">disappearing messages</a>.</li>
|
||||
<li><a href="https://simplex.chat/blog/20230103-simplex-chat-v4.4-disappearing-messages.html#live-messages">&quot;live&quot; messages</a>.</li>
|
||||
<li><a href="https://simplex.chat/blog/20230103-simplex-chat-v4.4-disappearing-messages.html#connection-security-verification">connection security verification</a>.</li>
|
||||
<li><a href="https://simplex.chat/blog/20230103-simplex-chat-v4.4-disappearing-messages.html#animated-images-and-stickers">animated images and stickers</a> – now on iOS too.</li>
|
||||
</ul>
|
||||
<p>Also, we added <a href="https://simplex.chat/blog/undefined">French language interface</a>, thanks to the users' community and Weblate!</p>
|
||||
<p>Also, we added <a href="https://simplex.chat/blog/20230103-simplex-chat-v4.4-disappearing-messages.html#french-language-interface">French language interface</a>, thanks to the users' community and Weblate!</p>
|
||||
<h3 id="disappearing-messages" tabindex="-1">Disappearing messages</h3>
|
||||
<p><img src="https://simplex.chat/blog/images/20230103-disappearing1.png" width="288" /> <img src="https://simplex.chat/blog/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="https://simplex.chat/blog/20221206-simplex-chat-v4.3-voice-messages.html">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="https://simplex.chat/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="https://simplex.chat/blog/images/20230103-live.png" width="288" />
|
||||
|
@ -1493,8 +1493,8 @@ file ---&gt; | XFTP | ------&gt; XFTP ----&
|
|||
<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="https://simplex.chat/blog/20220511-simplex-chat-v2-images-files.html">How can SimpleX deliver messages without user identifiers</a>.</p>
|
||||
<p><a href="https://simplex.chat/blog/20220711-simplex-chat-v3-released-ios-notifications-audio-video-calls-database-export-import-protocol-improvements.html">What are the risks to have identifiers assigned to the users</a>.</p>
|
||||
<p><a href="https://simplex.chat/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="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">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>
|
||||
|
@ -1536,10 +1536,10 @@ file ---&gt; | XFTP | ------&gt; XFTP ----&
|
|||
</ul>
|
||||
<h2 id="whats-new-in-v43" tabindex="-1">What's new in v4.3</h2>
|
||||
<ul>
|
||||
<li><a href="https://simplex.chat/blog/undefined">instant voice messages!</a></li>
|
||||
<li><a href="https://simplex.chat/blog/undefined">irreversible deletion of sent messages for all recipients</a></li>
|
||||
<li><a href="https://simplex.chat/blog/undefined">improved SMP server configuration and support for server passwords</a></li>
|
||||
<li><a href="https://simplex.chat/blog/undefined">privacy and security improvements</a>:
|
||||
<li><a href="https://simplex.chat/blog/20221206-simplex-chat-v4.3-voice-messages.html#instant-voice-messages">instant voice messages!</a></li>
|
||||
<li><a href="https://simplex.chat/blog/20221206-simplex-chat-v4.3-voice-messages.html#irreversible-message-deletion">irreversible deletion of sent messages for all recipients</a></li>
|
||||
<li><a href="https://simplex.chat/blog/20221206-simplex-chat-v4.3-voice-messages.html#smp-servers-configuration-and-password">improved SMP server configuration and support for server passwords</a></li>
|
||||
<li><a href="https://simplex.chat/blog/20221206-simplex-chat-v4.3-voice-messages.html#privacy-and-security-improvements">privacy and security improvements</a>:
|
||||
<ul>
|
||||
<li>protect app screen in recent apps and prevent screenshots</li>
|
||||
<li>improved privacy and security of SimpleX invitation links in the app</li>
|
||||
|
@ -1587,9 +1587,9 @@ file ---&gt; | XFTP | ------&gt; XFTP ----&
|
|||
<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="https://simplex.chat/blog/20220511-simplex-chat-v2-images-files.html">How can SimpleX deliver messages without user identifiers</a>.</p>
|
||||
<p><a href="https://simplex.chat/blog/20220711-simplex-chat-v3-released-ios-notifications-audio-video-calls-database-export-import-protocol-improvements.html">What are the risks to have identifiers assigned to the users</a>.</p>
|
||||
<p><a href="https://simplex.chat/blog/20220723-simplex-chat-v3.1-tor-groups-efficiency.html">Technical details and limitations</a>.</p>
|
||||
<p><a href="https://simplex.chat/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="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">What are the risks to have identifiers assigned to the users</a>.</p>
|
||||
<p><a href="https://simplex.chat/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>
|
||||
|
@ -1718,9 +1718,9 @@ file ---&gt; | XFTP | ------&gt; XFTP ----&
|
|||
<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="https://simplex.chat/blog/20220511-simplex-chat-v2-images-files.html">How can SimpleX deliver messages without user identifiers</a>.</p>
|
||||
<p><a href="https://simplex.chat/blog/20220711-simplex-chat-v3-released-ios-notifications-audio-video-calls-database-export-import-protocol-improvements.html">What are the risks to have identifiers assigned to the users</a>.</p>
|
||||
<p><a href="https://simplex.chat/blog/20220723-simplex-chat-v3.1-tor-groups-efficiency.html">Technical details and limitations</a>.</p>
|
||||
<p><a href="https://simplex.chat/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="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">What are the risks to have identifiers assigned to the users</a>.</p>
|
||||
<p><a href="https://simplex.chat/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>
|
||||
|
@ -1753,24 +1753,24 @@ file ---&gt; | XFTP | ------&gt; XFTP ----&
|
|||
<p><strong>Published:</strong> Sep 28, 2022</p>
|
||||
<h2 id="whats-new-in-v4" tabindex="-1">What's new in v4</h2>
|
||||
<ul>
|
||||
<li><a href="https://simplex.chat/blog/undefined">encrypted local chat database</a>.</li>
|
||||
<li><a href="https://simplex.chat/blog/undefined">support for self-hosted WebRTC ICE servers</a>.</li>
|
||||
<li><a href="https://simplex.chat/blog/undefined">improved stability of creating new connections: more reliable groups, files and contacts</a>.</li>
|
||||
<li><a href="https://simplex.chat/blog/undefined">deleting files and media</a>.</li>
|
||||
<li><a href="https://simplex.chat/blog/undefined">For developers - TypeScript SDK for integrating with SimpleX Chat</a> (e.g., chat bots or chat assistants).</li>
|
||||
<li><a href="https://simplex.chat/blog/20220928-simplex-chat-v4-encrypted-database.html#local-chat-database-encryption">encrypted local chat database</a>.</li>
|
||||
<li><a href="https://simplex.chat/blog/20220928-simplex-chat-v4-encrypted-database.html#self-hosted-webrtc-ice-servers">support for self-hosted WebRTC ICE servers</a>.</li>
|
||||
<li><a href="https://simplex.chat/blog/20220928-simplex-chat-v4-encrypted-database.html#improved-stability-of-creating-new-connections">improved stability of creating new connections: more reliable groups, files and contacts</a>.</li>
|
||||
<li><a href="https://simplex.chat/blog/20220928-simplex-chat-v4-encrypted-database.html#deleting-files-and-media">deleting files and media</a>.</li>
|
||||
<li><a href="https://simplex.chat/blog/20220928-simplex-chat-v4-encrypted-database.html#for-developers---typescript-sdk-for-integrating-with-simplex-chat">For developers - TypeScript SDK for integrating with SimpleX Chat</a> (e.g., chat bots or chat assistants).</li>
|
||||
<li>animated images in Android app.</li>
|
||||
<li>disable messages per contact / group in terminal app (it is already supported in mobile apps).</li>
|
||||
</ul>
|
||||
<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="https://simplex.chat/blog/20220808-simplex-chat-v3.1-chat-groups.html">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="https://simplex.chat/blog/20220808-simplex-chat-v3.1-chat-groups.html">v3.1</a> and <a href="https://simplex.chat/blog/20220901-simplex-chat-v3.2-incognito-mode.html">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="https://simplex.chat/blog/20220901-simplex-chat-v3.2-incognito-mode.html">v3.2</a> announcement).</li>
|
||||
<li>secret chat groups (see details in <a href="https://simplex.chat/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="https://simplex.chat/blog/20220808-simplex-chat-v3.1-chat-groups.html#access-messaging-servers-via-tor">v3.1</a> and <a href="https://simplex.chat/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="https://simplex.chat/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>
|
||||
<p><a href="https://simplex.chat/blog/undefined">Implementation audit is arranged for October</a>!</p>
|
||||
<p><a href="https://simplex.chat/blog/20220928-simplex-chat-v4-encrypted-database.html#we-ask-you-to-help-us-pay-for-3rd-party-security-audit">Implementation audit is arranged for October</a>!</p>
|
||||
<h3 id="local-chat-database-encryption" tabindex="-1">Local chat database encryption</h3>
|
||||
<img src="https://simplex.chat/blog/images/20220928-passphrase.png" width="330" />
|
||||
<p>SimpleX Chat focus has always been on protecting messages in delivery, not when they are stored on the device. This release changes it - now all messages that you receive and send are stored on the device encrypted with <a href="https://github.com/sqlcipher/sqlcipher">SQLCipher</a>.</p>
|
||||
|
@ -1779,7 +1779,7 @@ file ---&gt; | XFTP | ------&gt; XFTP ----&
|
|||
<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="https://simplex.chat/blog/images/20220928-ice-servers.png" width="330" />
|
||||
<p>You could make audio and video calls via SimpleX Chat WebRTC servers since <a href="https://simplex.chat/blog/20220711-simplex-chat-v3-released-ios-notifications-audio-video-calls-database-export-import-protocol-improvements.html">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="https://simplex.chat/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>
|
||||
|
@ -1819,9 +1819,9 @@ file ---&gt; | XFTP | ------&gt; XFTP ----&
|
|||
<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="https://simplex.chat/blog/20220511-simplex-chat-v2-images-files.html">How can SimpleX deliver messages without user identifiers</a>.</p>
|
||||
<p><a href="https://simplex.chat/blog/20220711-simplex-chat-v3-released-ios-notifications-audio-video-calls-database-export-import-protocol-improvements.html">What are the risks to have identifiers assigned to the users</a>.</p>
|
||||
<p><a href="https://simplex.chat/blog/20220723-simplex-chat-v3.1-tor-groups-efficiency.html">Technical details and limitations</a>.</p>
|
||||
<p><a href="https://simplex.chat/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="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">What are the risks to have identifiers assigned to the users</a>.</p>
|
||||
<p><a href="https://simplex.chat/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>
|
||||
|
@ -1853,11 +1853,11 @@ file ---&gt; | XFTP | ------&gt; XFTP ----&
|
|||
<p><strong>Published:</strong> Sep 1, 2022</p>
|
||||
<h2 id="whats-new" tabindex="-1">What's new</h2>
|
||||
<ul>
|
||||
<li><a href="https://simplex.chat/blog/undefined">Incognito mode</a></li>
|
||||
<li><a href="https://simplex.chat/blog/undefined">assign names to your contacts</a></li>
|
||||
<li><a href="https://simplex.chat/blog/undefined">use .onion server addresses with Tor</a></li>
|
||||
<li><a href="https://simplex.chat/blog/undefined">endless scrolling and search in chats</a></li>
|
||||
<li><a href="https://simplex.chat/blog/undefined">choose accent color and dark mode</a></li>
|
||||
<li><a href="https://simplex.chat/blog/20220901-simplex-chat-v3.2-incognito-mode.html#incognito-mode">Incognito mode</a></li>
|
||||
<li><a href="https://simplex.chat/blog/20220901-simplex-chat-v3.2-incognito-mode.html#assign-names-to-your-contacts">assign names to your contacts</a></li>
|
||||
<li><a href="https://simplex.chat/blog/20220901-simplex-chat-v3.2-incognito-mode.html#using-onion-server-addresses-with-tor">use .onion server addresses with Tor</a></li>
|
||||
<li><a href="https://simplex.chat/blog/20220901-simplex-chat-v3.2-incognito-mode.html#endless-scrolling-and-search-in-chats">endless scrolling and search in chats</a></li>
|
||||
<li><a href="https://simplex.chat/blog/20220901-simplex-chat-v3.2-incognito-mode.html#choose-accent-color-and-dark-mode">choose accent color and dark mode</a></li>
|
||||
<li>disable notifications per contact / group</li>
|
||||
<li>on Android:
|
||||
<ul>
|
||||
|
@ -1866,7 +1866,7 @@ file ---&gt; | XFTP | ------&gt; XFTP ----&
|
|||
</ul>
|
||||
</li>
|
||||
</ul>
|
||||
<p><a href="https://simplex.chat/blog/undefined">Implementation audit is arranged for October</a>!</p>
|
||||
<p><a href="https://simplex.chat/blog/20220901-simplex-chat-v3.2-incognito-mode.html#we-ask-you-to-help-us-pay-for-3rd-party-security-audit">Implementation audit is arranged for October</a>!</p>
|
||||
<h3 id="incognito-mode" tabindex="-1">Incognito mode</h3>
|
||||
<p><img src="https://simplex.chat/blog/images/20220901-incognito1.png" width="330" /> <img src="https://simplex.chat/blog/images/20220901-incognito2.png" width="330" /> <img src="https://simplex.chat/blog/images/20220901-incognito3.png" width="330" /></p>
|
||||
<p><em>SimpleX is already private, so why do we need an incognito mode</em>, you may ask.</p>
|
||||
|
@ -1897,9 +1897,9 @@ file ---&gt; | XFTP | ------&gt; XFTP ----&
|
|||
<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="https://simplex.chat/blog/20220511-simplex-chat-v2-images-files.html">How can SimpleX deliver messages without user identifiers</a>.</p>
|
||||
<p><a href="https://simplex.chat/blog/20220711-simplex-chat-v3-released-ios-notifications-audio-video-calls-database-export-import-protocol-improvements.html">What are the risks to have identifiers assigned to the users</a>.</p>
|
||||
<p><a href="https://simplex.chat/blog/20220723-simplex-chat-v3.1-tor-groups-efficiency.html">Technical details and limitations</a>.</p>
|
||||
<p><a href="https://simplex.chat/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="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">What are the risks to have identifiers assigned to the users</a>.</p>
|
||||
<p><a href="https://simplex.chat/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>
|
||||
|
@ -1930,12 +1930,12 @@ file ---&gt; | XFTP | ------&gt; XFTP ----&
|
|||
<p><strong>Published:</strong> Aug 8, 2022</p>
|
||||
<h2 id="whats-new" tabindex="-1">What's new</h2>
|
||||
<ul>
|
||||
<li><a href="https://simplex.chat/blog/undefined">secret chat groups</a>!</li>
|
||||
<li><a href="https://simplex.chat/blog/undefined">access to messaging servers via Tor</a></li>
|
||||
<li><a href="https://simplex.chat/blog/undefined">advanced network settings</a></li>
|
||||
<li><a href="https://simplex.chat/blog/undefined">published chat protocol</a></li>
|
||||
<li><a href="https://simplex.chat/blog/undefined">new app icons</a></li>
|
||||
<li><a href="https://simplex.chat/blog/undefined">other changes since v3</a>:
|
||||
<li><a href="https://simplex.chat/blog/20220808-simplex-chat-v3.1-chat-groups.html#secret-chat-groups">secret chat groups</a>!</li>
|
||||
<li><a href="https://simplex.chat/blog/20220808-simplex-chat-v3.1-chat-groups.html#access-messaging-servers-via-tor">access to messaging servers via Tor</a></li>
|
||||
<li><a href="https://simplex.chat/blog/20220808-simplex-chat-v3.1-chat-groups.html#advanced-network-settings">advanced network settings</a></li>
|
||||
<li><a href="https://simplex.chat/blog/20220808-simplex-chat-v3.1-chat-groups.html#published-chat-protocol">published chat protocol</a></li>
|
||||
<li><a href="https://simplex.chat/blog/20220808-simplex-chat-v3.1-chat-groups.html#new-app-icons">new app icons</a></li>
|
||||
<li><a href="https://simplex.chat/blog/20220808-simplex-chat-v3.1-chat-groups.html#other-changes-since-v3">other changes since v3</a>:
|
||||
<ul>
|
||||
<li>optimized battery and traffic usage - up to 90x reduction!</li>
|
||||
<li>two docker configurations for self-hosted SMP servers</li>
|
||||
|
@ -1983,9 +1983,9 @@ file ---&gt; | XFTP | ------&gt; XFTP ----&
|
|||
<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="https://simplex.chat/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="https://simplex.chat/blog/20220511-simplex-chat-v2-images-files.html">How can SimpleX deliver messages without user identifiers</a>.</p>
|
||||
<p><a href="https://simplex.chat/blog/20220711-simplex-chat-v3-released-ios-notifications-audio-video-calls-database-export-import-protocol-improvements.html">What are the risks to have identifiers assigned to the users</a>.</p>
|
||||
<p><a href="https://simplex.chat/blog/20220723-simplex-chat-v3.1-tor-groups-efficiency.html">Technical details and limitations</a>.</p>
|
||||
<p><a href="https://simplex.chat/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="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">What are the risks to have identifiers assigned to the users</a>.</p>
|
||||
<p><a href="https://simplex.chat/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>
|
||||
|
@ -2016,10 +2016,10 @@ file ---&gt; | XFTP | ------&gt; XFTP ----&
|
|||
<p><strong>Published:</strong> Jul 23, 2022</p>
|
||||
<h2 id="whats-new" tabindex="-1">What's new</h2>
|
||||
<ul>
|
||||
<li>terminal app: <a href="https://simplex.chat/blog/undefined">access to messaging servers via SOCKS5 proxy</a> (e.g., Tor).</li>
|
||||
<li>mobile apps: <a href="https://simplex.chat/blog/undefined">join and leave chat groups</a>.</li>
|
||||
<li><a href="https://simplex.chat/blog/undefined">optimized battery and traffic usage - up to 90x reduction!</a>.</li>
|
||||
<li><a href="https://simplex.chat/blog/undefined">two docker configurations for self-hosted SMP servers</a>.</li>
|
||||
<li>terminal app: <a href="https://simplex.chat/blog/20220723-simplex-chat-v3.1-tor-groups-efficiency.html#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://simplex.chat/blog/20220723-simplex-chat-v3.1-tor-groups-efficiency.html#mobile-apps-join-and-leave-chat-groups">join and leave chat groups</a>.</li>
|
||||
<li><a href="https://simplex.chat/blog/20220723-simplex-chat-v3.1-tor-groups-efficiency.html#optimized-battery-and-traffic-usage---up-to-90x-reduction">optimized battery and traffic usage - up to 90x reduction!</a>.</li>
|
||||
<li><a href="https://simplex.chat/blog/20220723-simplex-chat-v3.1-tor-groups-efficiency.html#docker-configuration-for-self-hosted-smp-servers">two docker configurations for self-hosted SMP servers</a>.</li>
|
||||
</ul>
|
||||
<h3 id="terminall-app-access-to-messaging-servers-via-socks5-proxy-tor" tabindex="-1">Terminall app: access to messaging servers via SOCKS5 proxy / Tor</h3>
|
||||
<img src="https://simplex.chat/blog/images/20220723-tor.jpg" width="480" />
|
||||
|
@ -2054,7 +2054,7 @@ file ---&gt; | XFTP | ------&gt; XFTP ----&
|
|||
<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="https://simplex.chat/blog/20220711-simplex-chat-v3-released-ios-notifications-audio-video-calls-database-export-import-protocol-improvements.html">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://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">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="https://simplex.chat/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>
|
||||
|
@ -2103,13 +2103,13 @@ file ---&gt; | XFTP | ------&gt; XFTP ----&
|
|||
<p><strong>Published:</strong> Jul 11, 2022</p>
|
||||
<h2 id="new-in-version-3" tabindex="-1">New in version 3</h2>
|
||||
<ul>
|
||||
<li><a href="https://simplex.chat/blog/undefined">instant notifications for iOS</a></li>
|
||||
<li><a href="https://simplex.chat/blog/undefined">end-to-end encrypted audio/video calls</a></li>
|
||||
<li><a href="https://simplex.chat/blog/undefined">database export and import</a></li>
|
||||
<li><a href="https://simplex.chat/blog/undefined">protocol privacy and performance improvements</a></li>
|
||||
<li><a href="https://simplex.chat/blog/20220711-simplex-chat-v3-released-ios-notifications-audio-video-calls-database-export-import-protocol-improvements.html#instant-notifications-for-ios">instant notifications for iOS</a></li>
|
||||
<li><a href="https://simplex.chat/blog/20220711-simplex-chat-v3-released-ios-notifications-audio-video-calls-database-export-import-protocol-improvements.html#end-to-end-encrypted-audiovideo-calls">end-to-end encrypted audio/video calls</a></li>
|
||||
<li><a href="https://simplex.chat/blog/20220711-simplex-chat-v3-released-ios-notifications-audio-video-calls-database-export-import-protocol-improvements.html#database-export-and-import">database export and import</a></li>
|
||||
<li><a href="https://simplex.chat/blog/20220711-simplex-chat-v3-released-ios-notifications-audio-video-calls-database-export-import-protocol-improvements.html#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="https://simplex.chat/blog/20220404-simplex-chat-instant-notifications.html">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://simplex.chat/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>
|
||||
|
@ -2139,7 +2139,7 @@ file ---&gt; | XFTP | ------&gt; XFTP ----&
|
|||
<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="https://simplex.chat/blog/20220112-simplex-chat-v1-released.html">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://simplex.chat/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>
|
||||
|
@ -2527,10 +2527,10 @@ file ---&gt; | XFTP | ------&gt; XFTP ----&
|
|||
<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="https://simplex.chat/images/groups.gif" alt="simplex-chat" /></p>
|
||||
<p><img src="https://simplex.chat/blog/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="https://simplex.chat/images/files.gif" alt="simplex-chat" /></p>
|
||||
<p><img src="https://simplex.chat/blog/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>
|
||||
|
|
|
@ -1,5 +1,3 @@
|
|||
const uniqueSwiperContainer = document.querySelector('.unique-swiper')
|
||||
if (uniqueSwiperContainer) {
|
||||
const uniqueSwiper = new Swiper('.unique-swiper', {
|
||||
slidesPerView: 1,
|
||||
spaceBetween: 80,
|
||||
|
@ -25,15 +23,12 @@ const uniqueSwiper = new Swiper('.unique-swiper', {
|
|||
prevEl: '.unique-swiper-button-prev',
|
||||
},
|
||||
});
|
||||
}
|
||||
|
||||
const isMobile = {
|
||||
Android: () => navigator.userAgent.match(/Android/i),
|
||||
iOS: () => navigator.userAgent.match(/iPhone|iPad|iPod/i)
|
||||
};
|
||||
|
||||
const privateSwiperContainer = document.querySelector('.private-swiper')
|
||||
if (privateSwiperContainer) {
|
||||
const privateSwiper = new Swiper('.private-swiper', {
|
||||
slidesPerView: 1,
|
||||
slidesPerGroup: 1,
|
||||
|
@ -84,10 +79,7 @@ const privateSwiper = new Swiper('.private-swiper', {
|
|||
}
|
||||
}
|
||||
});
|
||||
}
|
||||
|
||||
const simplexExplainedSwiperContainer = document.querySelector('.simplex-explained-swiper')
|
||||
if (simplexExplainedSwiperContainer){
|
||||
const simplexExplainedSwiper = new Swiper(".simplex-explained-swiper", {
|
||||
slidesPerView: 1,
|
||||
spaceBetween: 80,
|
||||
|
@ -120,7 +112,6 @@ const simplexExplainedSwiper = new Swiper(".simplex-explained-swiper", {
|
|||
}
|
||||
}
|
||||
});
|
||||
}
|
||||
|
||||
function closeOverlay(e) {
|
||||
e.target.closest('.overlay').classList.remove('flex');
|
||||
|
|
File diff suppressed because one or more lines are too long
File diff suppressed because one or more lines are too long
File diff suppressed because one or more lines are too long
Loading…
Add table
Add a link
Reference in a new issue