@@ -75,7 +75,7 @@ While the content encryption is the most important, concealing the actual messag
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.
-To the best of our knowledge the only messenger other than SimpleX Chat that padded all messages to a fixed packet size was [Pond](https://github.com/agl/pond) - SimpleX design as an evolution of it.
+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 [Pond](https://github.com/agl/pond) - SimpleX design can be seen as an evolution of Pond design.
### 2. Compromised confidential messages - mitigated by repudiation (deniability)
@@ -97,15 +97,15 @@ This property is well understood by the users, and most messengers that focus on
### 4. Compromised long-term or session - mitigated by break-in recovery
-This attack is much less understood by the users, and forward secrecy does not protect from it. Arguably, it's almost impossible to compromise individual message keys without compromising long-term or session keys. So the ability of the encryption to recover from break-in (attacker making a copy of the device data without retaining the ongoing access) is both very and pragmatic - break-in attacks are simpler to execute on mobile devices during short-term device access than long-term ongoing compromise.
+This attack is much less understood by the users, and forward secrecy does not protect from it. Arguably, it's almost impossible to compromise individual message keys without compromising long-term or session keys. So the ability of the encryption to recover from break-in (attacker making a copy of the device data without retaining the ongoing access) is both very important and pragmatic - break-in attacks are simpler to execute on mobile devices during short-term device access than long-term ongoing compromise.
-Out of all encryption algorithms known to us only Signal double ratchet algorithm provides the ability to encryption security after break-ins. This recovery happens automatically and transparently to the users, without them doing anything special even knowing about break-in, by simply sending messages. Every time one of the communication parties replies to another party message, new random keys are generated and previously stolen keys become useless.
+Out of all encryption algorithms known to us only _Signal double ratchet algorithm_ (also referred to as _Signal algorithm_ or _double ratchet algorithm_, which is not the same as Signal messaging platform and protocols) provides the ability for the encryption security to recover after break-ins attacks. This recovery happens automatically and transparently to the users, without them doing anything special or even knowing about break-in, by simply sending messages. Every time one of the communication parties replies to another party message, new random keys are generated and previously stolen keys become useless.
-Signal double ratchet algorithm is used in Signal, Cwtch and SimpleX Chat. This is why you cannot use SimpleX Chat profile on more than one device at the same time - the encryption scheme rotates the long term keys, randomly, and keys on another device become useless, as they would become useless for the attacker who stole them. Security always has some costs to the convenience.
+Double ratchet algorithm is used in Signal, Cwtch and SimpleX Chat. This is why you cannot use SimpleX Chat profile on more than one device at the same time - the encryption scheme rotates the long term keys, randomly, and keys on another device become useless, as they would become useless for the attacker who stole them. Security always has some costs to the convenience.
### 5. Man-in-the-middle attack - mitigated by two-factor key exchange
-Many people incorrectly believe that security of end-to-end encryption cannot be broken by communication provider. But end-to-end encryption is as secure as key exchange. While any intermediary passing the keys between senders and recipients cannot recover the private keys from the public keys, they can simply replace the passed public keys with their own and then proxy all communication between the users having full access to the original messages. So instead of having an end-to-end encrypted channel, users would have two half-way encrypted channels - between users and their communication intermediary.
+Many people incorrectly believe that security of end-to-end encryption cannot be broken by communication provider. But end-to-end encryption is only as secure as key exchange. While any intermediary passing the keys between senders and recipients cannot recover the private keys from the public keys, they can simply replace the passed public keys with their own and then proxy all communication between the users having full access to the original messages. So instead of having an end-to-end encrypted channel, users would have two half-way encrypted channels - between users and their communication intermediary.
Pictures below illustrate how this attack works for RSA encryption.
@@ -143,7 +143,7 @@ Post-quantum cryptography, or encryption algorithms that are resistant to quantu
- many of post-quantum algorithms have known patent claims, so any system deploying them accepts the risks of patent litigation.
- the silver lining to these limitations is that the risk of appearance of commercially viable quantum computers in the next decade may be exaggerated.
-So, to put it bluntly and provocatively, post-quantum cryptography can be compared with a remedy against the illness that nobody has, without any guarantee that it will work. The closest analogy in the history of medicine is _snake oil_.
+So, to say it provocatively, post-quantum cryptography can be compared with a remedy against the illness that nobody has, without any guarantee that it will work. While there is a reasonable hope that it _might_ work, so it's not exactly a _snake oil_, these limitations and risks have to be much better communicated to the end users than they are.
@@ -164,8 +164,8 @@ The main objective here is to establish the framework for comparing the security
Some columns are marked with a yellow checkmark:
- when messages are padded, but not to a fixed size.
- when repudiation does not include client-server connection. In case of Cwtch it appears that the presence of cryptographic signatures compromises repudiation (deniability), but it needs to be clarified.
-- when 2-factor key exchange is optional, via security code verification.
-- when post-quantum cryptography is only added to the initial key agreement, does not protect break-in recovery.
+- when 2-factor key exchange is optional (via security code verification).
+- when post-quantum cryptography is only added to the initial key agreement and does not protect break-in recovery.
## Adding quantum resistance to Signal double ratchet algorithm
@@ -201,7 +201,7 @@ The reason it is released as opt-in is because once the conversation is upgraded
- enable _Show developer options_ toggle.
- now you will see _Post-quantum E2EE_ toggle - enable it as well.
-Now all new contacts you add to the app will use quantum resistant Signal double ratchet algorithm.
+Now all new contacts you add to the app will use quantum resistant double ratchet algorithm.
Once you have enabled it for the new contacts, you can also **enable it for some of the existing contacts**:
- open the chat with the contact you want to upgrade to be quantum resistant.
@@ -211,7 +211,7 @@ Once you have enabled it for the new contacts, you can also **enable it for some
## Next for post-quantum crypto - all direct chats, small groups and security audit
-We will be making quantum resistance default for all direct chats in v5.7, and they will be upgraded for all users without any action.
+We will be making quantum resistance default for all direct chats in v5.7, and we plan that all existing direct chats will be automatically upgraded when both contacts install v5.7.
We will also be adding quantum resistance to small groups up to 10-20 members. Computing cryptographic keys is much slower, in comparison, and it would be very inefficient (and completely unnecessary) for large public groups.
diff --git a/blog/20240323-simplex-network-privacy-non-profit-v5-6-quantum-resistant-e2e-encryption-simple-migration.md b/blog/20240323-simplex-network-privacy-non-profit-v5-6-quantum-resistant-e2e-encryption-simple-migration.md
index f036b95f1f..c017b9d1cc 100644
--- a/blog/20240323-simplex-network-privacy-non-profit-v5-6-quantum-resistant-e2e-encryption-simple-migration.md
+++ b/blog/20240323-simplex-network-privacy-non-profit-v5-6-quantum-resistant-e2e-encryption-simple-migration.md
@@ -1,20 +1,128 @@
---
layout: layouts/article.html
-title: "SimpleX network: real privacy and stable profits, non-profit protocol governance, v5.6 released with quantum resistant e2e encryption and simple profile migration"
+title: "SimpleX network: real privacy and stable profits, non-profits for protocols, v5.6 released with quantum resistant e2e encryption and simple profile migration"
date: 2024-03-23
-# previewBody: blog_previews/20240314.html
-preview: TODO
-draft: true
-# image: images/20240314-kem.jpg
-# imageWide: true
+previewBody: blog_previews/20240323.html
+image: images/20240323-post-preview.png
+imageBottom: true
permalink: "/blog/20240323-simplex-network-privacy-non-profit-v5-6-quantum-resistant-e2e-encryption-simple-migration.html"
---
-# SimpleX network: real privacy and stable profits, non-profit protocol governance, v5.6 released with quantum resistant e2e encryption and simple profile migration
+# SimpleX network: real privacy and stable profits, non-profits for protocols, v5.6 released with quantum resistant e2e encryption and simple profile migration
-This is a stub for release permalink
+**Published:** Mar 23, 2024
-TODO
+SimpleX network: deliver real privacy via a profitable business and non-profit protocol governance:
+- [community and business interests are aligned](#community-and-business-interests-are-aligned).
+- [the journey to the decentralized non-profit protocol governance](#the-journey-to-the-decentralized-non-profit-protocol-governance).
+- [welcome, Esra’a](#welcome-esraa)!
+
+What's new in v5.6:
+- [quantum resistant end-to-end encryption](#quantum-resistant-end-to-end-encryption-beta) (BETA) – enable it for the new contacts.
+- [use the app during the audio and video calls](#use-the-app-during-the-audio-and-video-calls).
+- [migrate all app data to another device via QR code](#migrate-all-app-data-to-another-device-via-qr-code).
+
+There are many other improvements and fixes in this release:
+- group admins can block a member for all other members.
+- filtering chats no longer includes muted chats with unread messages.
+- and more - see the [release notes](https://github.com/simplex-chat/simplex-chat/releases/tag/v5.6.0).
+
+## SimpleX network: deliver real privacy via a profitable business and non-profit protocol governance
+
+### Community and business interests are aligned
+
+Some people in our users' community believe that there is a conflict between the business and the community interests. This view fails to see a bigger picture of how these interests are aligned. I wrote a blog post about it [here](https://www.poberezkin.com/posts/2023-10-31-why-privacy-impossible-without-venture-funding.html). Our goal is to grow the network and the ecosystem while enriching all stakeholders involved, both the community and the business shareholders. This strategy relies on the strengths and opportunities of both the business and the decentralized network we build, with its vibrant community of individuals and organizations. It positions the business not as a controller but as a supporter of the community growth, resilience and sustainability.
+
+By leveraging access to investment resources, its ability to provide stock-based incentives beyond salaries, operating as a business will satisfy users' and community needs more effectively, ensuring the long-term viability and growth of the network, while remaining true to the mission. A purely nonprofit model with no avenue to sustain this growth is simply not possible. Sustainability requires profits, that is simply spending less than earning, as every responsible individual and organization should aim for, and these profits must be based on users' payments, and not on some other sources of revenue or funds. And building the software product that customers are willing to pay for requires substantial business investments. We will accomplish it while maintaining transparency and the commitment to keep SimpleX network and its protocols open and free to use.
+
+### The journey to the decentralized non-profit protocol governance
+
+At the current early stage of network growth the protocols will benefit most from the rapid evolution and centralized design. Many protocols that decentralized their evolution too early failed to evolve and to adapt to the product requirements of the majority of users, causing them to stall in growth. Even the open web became possible only thanks to Netscape, a venture funded company, that developed browsers and web server software taking it upon themselves to rapidly evolve web specification to make it into a robust application platform as we now know it. It is very unlikely that it would have happened if it was managed by a nonprofit or community, in a decentralized way.
+
+Once SimpleX network protocols stabilize and reach the required maturity, we plan to transition its governance to several new nonprofit entities, ensuring its continued evolution aligns more closely with our vision of community-driven, independent and transparent governance. We and our investors believe that this is a win-win strategy. It both maximizes the business value, by creating a product built on protecting privacy and users' trust - a model that we see as the only viable path forward. It also maximizes the value created for the user community.
+
+### Welcome, Esra’a!
+
+To help us deliver these goals, Esra’a Al Shafei joined SimpleX Chat team - we are excited to welcome her!
+
+Esra'a is a longtime privacy and human rights advocate from Bahrain. She is the founder of [Majal.org](http://majal.org), a network of platforms that amplify under-reported and marginalized voices in the Middle East and North Africa. She is also the co-founder of the [Numun Fund](https://numun.fund/), the first dedicated fund for women-led tech in the Global South. Esra’a is currently the Vice Chair of the Board at the [Wikimedia Foundation](https://wikimediafoundation.org/), the nonprofit which hosts Wikipedia. She is also on the Board of the [Tor Project](https://www.torproject.org/), developers of one of the world’s strongest tools for privacy and freedom online. Previously, she served on the Board of [Access Now](https://www.accessnow.org/), an international nonprofit dedicated to an open and free Internet.
+
+In her own words: *"Privacy and security have been the center of my work as a human rights advocate for the last 20 years in one of the most surveilled countries in the world where staying safe remains a burden. Our privacy is our dignity. It is something that belongs to us and something we should treasure - as people, as companies, as governments. Despite messaging being the most intimate aspect of our digital lives, the leading protocols in this space are centralized and we deserve a web that operates on the core principles of genuine privacy and security in a fully decentralized framework. SimpleX network will play a critical role towards that vision."*
+
+Executing the plan towards decentralized nonprofit protocol governance will be Esra’a’s primary responsibility. Our primary objective with this plan is to ensure that no single entity can control or have unrestricted ownership of the protocols, so it can maintain its integrity.
+
+## What's new in v5.6
+
+### Quantum resistant end-to-end encryption (BETA)
+
+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.
+
+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 [the most secure end-to-end encryption design](./20240314-simplex-chat-v5-6-quantum-resistance-signal-double-ratchet-algorithm.md#how-secure-is-end-to-end-encryption-in-different-messengers) against the present and future attacks.
+
+We plan to perform a security audit of this design and implementation later this year.
+
+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.
+
+
+
+**To enable quantum resistance for the new conversations**:
+- open the app settings (tap user avatar in the top left corner).
+- scroll down to _Developer tools_ and open them.
+- enable _Show developer options_ toggle.
+- now you will see _Post-quantum E2EE_ toggle - enable it as well.
+
+Now all new contacts you add to the app will use quantum resistant Signal double ratchet algorithm.
+
+Once you have enabled it for the new contacts, you can also **enable it for some of the existing contacts**:
+- open the chat with the contact you want to upgrade to be quantum resistant.
+- tap contact name above the chat.
+- tap Allow PQ encryption.
+- exchange several messages back and forth with that contact - the quantum resistant double ratchet will kick in after 3-5 messages (depending on how many messages you send in each direction), and you will see the notice in the chat once it enables.
+
+We will be making quantum resistance default for all direct chats in v5.7, and we plan that all existing direct chats will be automatically upgraded when both contacts install v5.7.
+
+### Use the app during the audio and video calls
+
+
+
+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.
+
+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.
+
+### Migrate all app data to another device via QR code
+
+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 [released in July 2022](./20220711-simplex-chat-v3-released-ios-notifications-audio-video-calls-database-export-import-protocol-improvements.md#database-export-and-import) 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.
+
+_"How can I migrate my data to another device?"_ was one of the most frequent user questions, but until this release this process was [quite complex](), requiring too many steps, and most non-technical users were not willing to try it, as even though it was reliable, it appeared risky.
+
+This release made the app data migration very simple, see the steps below.
+
+**Start the migration on the source device**
+
+
+
+On the device you migrate your app data from, follow these steps:
+- choose _Migrate to another device_,
+- if necessary, set the database passphrase (initially, the database is encrypted with a random passphrase), or, if it's already set, verify it - for security and to ensure that the archive will be usable on the new device,
+- tap _Archive and upload_ to and upload the app data in chunks to the XFTP servers configured in the app,
+- the app will show the QR code that should be scanned from the new device.
+
+**Migrate data to the target device**
+
+
+
+On the device you migrate your data to, follow these steps:
+- on the first app page choose _Migrate from another device_,
+- scan the QR code shown on the source device,
+- once the archive downloads, enter the database passphrase and tap _Open chat_,
+
+**Finalize migration on the source device**
+
+
+
+When the chat starts on the target device, make sure to tap _Finalize migration_ and then _Delete database_ on the source device.
+
+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.
## SimpleX network
diff --git a/blog/README.md b/blog/README.md
index 3b89628211..7f27c46c76 100644
--- a/blog/README.md
+++ b/blog/README.md
@@ -1,5 +1,19 @@
# Blog
+Mar 23, 2024 [SimpleX network: real privacy and stable profits, non-profits for protocols, v5.6 released with quantum resistant e2e encryption and simple profile migration](./20240323-simplex-network-privacy-non-profit-v5-6-quantum-resistant-e2e-encryption-simple-migration.md)
+
+SimpleX network: deliver real privacy via a profitable business and non-profit protocol governance:
+- community and business interests are aligned.
+- the journey to the decentralized non-profit protocol governance.
+- welcome, Esra’a!
+
+What's new in v5.6:
+- quantum resistant end-to-end encryption (BETA) – enable it for the new contacts.
+- use the app during the audio and video calls.
+- migrate all app data to another device via QR code.
+
+---
+
Mar 14, 2024 [SimpleX Chat v5.6 (beta): adding quantum resistance to Signal double ratchet algorithm](./20240314-simplex-chat-v5-6-quantum-resistance-signal-double-ratchet-algorithm.md)
This is a major upgrade for SimpleX Chat messaging protocol stack, I am really proud to present this work of the whole team.
diff --git a/blog/images/20240314-comparison.jpg b/blog/images/20240314-comparison.jpg
index 34027a43a7..579b2fd73c 100644
Binary files a/blog/images/20240314-comparison.jpg and b/blog/images/20240314-comparison.jpg differ
diff --git a/blog/images/20240323-call1.png b/blog/images/20240323-call1.png
new file mode 100644
index 0000000000..0cf954a07e
Binary files /dev/null and b/blog/images/20240323-call1.png differ
diff --git a/blog/images/20240323-call2.png b/blog/images/20240323-call2.png
new file mode 100644
index 0000000000..8a69d1891e
Binary files /dev/null and b/blog/images/20240323-call2.png differ
diff --git a/blog/images/20240323-migrate-from0.png b/blog/images/20240323-migrate-from0.png
new file mode 100644
index 0000000000..033ead3fd9
Binary files /dev/null and b/blog/images/20240323-migrate-from0.png differ
diff --git a/blog/images/20240323-migrate-from1.png b/blog/images/20240323-migrate-from1.png
new file mode 100644
index 0000000000..be016ada2c
Binary files /dev/null and b/blog/images/20240323-migrate-from1.png differ
diff --git a/blog/images/20240323-migrate-from2.png b/blog/images/20240323-migrate-from2.png
new file mode 100644
index 0000000000..2cee12e6f4
Binary files /dev/null and b/blog/images/20240323-migrate-from2.png differ
diff --git a/blog/images/20240323-migrate-from3.png b/blog/images/20240323-migrate-from3.png
new file mode 100644
index 0000000000..92d7bf19a6
Binary files /dev/null and b/blog/images/20240323-migrate-from3.png differ
diff --git a/blog/images/20240323-migrate-from4.png b/blog/images/20240323-migrate-from4.png
new file mode 100644
index 0000000000..9b96f9efd8
Binary files /dev/null and b/blog/images/20240323-migrate-from4.png differ
diff --git a/blog/images/20240323-migrate-from5.png b/blog/images/20240323-migrate-from5.png
new file mode 100644
index 0000000000..dfc22a3987
Binary files /dev/null and b/blog/images/20240323-migrate-from5.png differ
diff --git a/blog/images/20240323-migrate-from6.png b/blog/images/20240323-migrate-from6.png
new file mode 100644
index 0000000000..18d9c8b627
Binary files /dev/null and b/blog/images/20240323-migrate-from6.png differ
diff --git a/blog/images/20240323-migrate-to1.png b/blog/images/20240323-migrate-to1.png
new file mode 100644
index 0000000000..b3fb0e32f1
Binary files /dev/null and b/blog/images/20240323-migrate-to1.png differ
diff --git a/blog/images/20240323-migrate-to2.png b/blog/images/20240323-migrate-to2.png
new file mode 100644
index 0000000000..f64544cd9b
Binary files /dev/null and b/blog/images/20240323-migrate-to2.png differ
diff --git a/blog/images/20240323-migrate-to3.png b/blog/images/20240323-migrate-to3.png
new file mode 100644
index 0000000000..626032737b
Binary files /dev/null and b/blog/images/20240323-migrate-to3.png differ
diff --git a/blog/images/20240323-migrate-to4.png b/blog/images/20240323-migrate-to4.png
new file mode 100644
index 0000000000..59153a464c
Binary files /dev/null and b/blog/images/20240323-migrate-to4.png differ
diff --git a/blog/images/20240323-migrate-to5.png b/blog/images/20240323-migrate-to5.png
new file mode 100644
index 0000000000..b86f42b292
Binary files /dev/null and b/blog/images/20240323-migrate-to5.png differ
diff --git a/blog/images/20240323-post-preview.png b/blog/images/20240323-post-preview.png
new file mode 100644
index 0000000000..69c9908a1e
Binary files /dev/null and b/blog/images/20240323-post-preview.png differ
diff --git a/cabal.project b/cabal.project
index 547ec861e0..be58b64283 100644
--- a/cabal.project
+++ b/cabal.project
@@ -12,7 +12,7 @@ constraints: zip +disable-bzip2 +disable-zstd
source-repository-package
type: git
location: https://github.com/simplex-chat/simplexmq.git
- tag: 7b6b80cea21c7fbafffa118f1ed268411fcb79ca
+ tag: 8496884b42d76bd0d934e5ae481846d9c324d3c7
source-repository-package
type: git
diff --git a/docs/DOWNLOADS.md b/docs/DOWNLOADS.md
index 6726fa02fe..b394c9dd27 100644
--- a/docs/DOWNLOADS.md
+++ b/docs/DOWNLOADS.md
@@ -4,10 +4,10 @@ permalink: /downloads/index.html
revision: 11.02.2024
---
-| Updated 11.02.2024 | Languages: EN |
+| Updated 23.03.2024 | Languages: EN |
# Download SimpleX apps
-The latest stable version is v5.5.3.
+The latest stable version is v5.6.
You can get the latest beta releases from [GitHub](https://github.com/simplex-chat/simplex-chat/releases).
diff --git a/docs/rfcs/2024-03-22-communicating-reject.md b/docs/rfcs/2024-03-22-communicating-reject.md
new file mode 100644
index 0000000000..37bb4eab26
--- /dev/null
+++ b/docs/rfcs/2024-03-22-communicating-reject.md
@@ -0,0 +1,95 @@
+# Communicating rejection
+
+## Problem
+
+Many interactions support either approval, or silent rejection. From privacy perspective, rejection being silent is a correct default. However, for improved usability we could add optional communication of rejection, as many users don't mind sending such signals to their contacts.
+
+Features currently not supporting communicating rejection:
+- Rejecting contact request
+- Rejecting group join request
+- Rejecting call
+- Rejecting group invitation
+- TBC Other?
+
+## Solution
+
+## Rejection of contact / group join requests
+
+- Contact and group join requests are very similar between each other and different from other features as they both use mechanism of "contact connections".
+
+- Rejection can be made to the address proposed by requester in AgentInvitation message, where currently AgentConfirmation is sent in case of acceptance.
+
+ ``` haskell
+ data AgentMsgEnvelope
+ = ...
+ | AgentRejection
+ { e2eEncryption :: RcvE2ERatchetParams 'C.X448,
+ encRejectionInfo :: ByteString
+ }
+ ```
+
+- Unlike other AgentMsgEnvelope constructors, AgentRejection doesn't require agentVersion since connection will be deleted after sending this message.
+
+ - We may be able to re-use recently added mechanism of marking connection for deletion with deleted_at_wait_delivery field without much additional work.
+
+- e2eEncryption will be used to encrypt first message, same as for AgentConfirmation. (?)
+
+- Both sync and async versions of agent functions are required, as contact rejection will be user action, while group join rejection will be automated (in case, for example, if link host is no longer admin).
+
+ - Group requests non-automatic approval is a separate matter and requires UI consideration, but if it was added it would use sync function.
+
+ - For sync function either new API can be added, or rejectContact can be parameterized.
+
+- Chat protocol requires adding new messages to be sent in encRejectionInfo, to be processed on requester side based on connections' semantics.
+
+ ```haskell
+ -- / contact request rejection
+ XReject :: ChatMsgEvent 'Json
+ -- or
+ -- (contact can send reason for rejection; we don't even have welcome messages in XContact though)
+ XReject :: Maybe Text -> ChatMsgEvent 'Json
+
+ -- / group join request rejection
+ XGrpReject :: Maybe GrpRejectReason -> ChatMsgEvent 'Json
+
+ data GrpRejectReason
+ = GRRNone -- manual reject with no reason? use Nothing in GRRText instead?
+ | GRRCantInvite -- e.g., no longer admin
+ | GRRText {text :: Text} -- manual reject once supported? Maybe Text?
+
+ -- add similar type for contact request rejection?
+ -- minimal is to always send XReject without reasons
+ ```
+
+ - As a side note, it may have been a design mistake to mix both "connInfo" messages as well as regular chat messages in a single type for protocol messages, so it may be best to keep these as separate constructors.
+
+- Versioning considerations:
+ - Increase chat version.
+ - We already save peer chat version on contact_requests on initial REQ message. It can be used to differentiate UI whether contact supports rejection messages and not offer option to reject with notification.
+ - Increase agent version? Agent can prohibit sending AgentRejection based on version in AgentInvitation, though it shouldn't be reachable as chat should also prohibit it.
+
+## Rejecting calls
+
+- New chat protocol message is enough
+ - Based on user action in reply to XCallInv instead of XCallOffer.
+ - Send in APIRejectCall.
+
+ ```haskell
+ XCallReject :: CallId -> ChatMsgEvent 'Json
+ ```
+
+- Same chat versioning considerations as above.
+
+## Rejecting group invitation
+
+- Same, new protocol message.
+ - Based on user action in reply to XGrpInv instead of XGrpAcpt.
+ - Can't be sent as simple chat message since there's no group ID in invitation? (only optional groupLinkId)
+ - So, have to send as "conn info" via join, same as for XGrpAcpt.
+ - APIDeleteChat is already used for deleting group invitations, can re-use. In this case `notify` parameter in APIDeleteChat can be used to send rejection.
+
+ ```haskell
+ XGrpReject :: CallId -> ChatMsgEvent 'Json
+ ```
+
+- Same chat versioning considerations as above.
diff --git a/package.yaml b/package.yaml
index ed6bc96cb1..dbc75ddf9f 100644
--- a/package.yaml
+++ b/package.yaml
@@ -1,5 +1,5 @@
name: simplex-chat
-version: 5.6.0.3
+version: 5.6.0.4
#synopsis:
#description:
homepage: https://github.com/simplex-chat/simplex-chat#readme
@@ -104,16 +104,20 @@ executables:
- -threaded
simplex-broadcast-bot:
- source-dirs: apps/simplex-broadcast-bot/src
- main: ../Main.hs
+ source-dirs:
+ - apps/simplex-broadcast-bot
+ - apps/simplex-broadcast-bot/src
+ main: Main.hs
dependencies:
- simplex-chat
ghc-options:
- -threaded
simplex-directory-service:
- source-dirs: apps/simplex-directory-service/src
- main: ../Main.hs
+ source-dirs:
+ - apps/simplex-directory-service
+ - apps/simplex-directory-service/src
+ main: Main.hs
dependencies:
- simplex-chat
ghc-options:
diff --git a/scripts/nix/sha256map.nix b/scripts/nix/sha256map.nix
index b898978fcc..1fd783a1d3 100644
--- a/scripts/nix/sha256map.nix
+++ b/scripts/nix/sha256map.nix
@@ -1,5 +1,5 @@
{
- "https://github.com/simplex-chat/simplexmq.git"."7b6b80cea21c7fbafffa118f1ed268411fcb79ca" = "0a665v4v1ilm2j9cxkiwqq2xlp2732h95mqaywf7qrlk03qkasfi";
+ "https://github.com/simplex-chat/simplexmq.git"."8496884b42d76bd0d934e5ae481846d9c324d3c7" = "0c040s00zc1qg0ilsvpv54f01xz7flh8rsar2nplcs4a4gnp78qs";
"https://github.com/simplex-chat/hs-socks.git"."a30cc7a79a08d8108316094f8f2f82a0c5e1ac51" = "0yasvnr7g91k76mjkamvzab2kvlb1g5pspjyjn2fr6v83swjhj38";
"https://github.com/simplex-chat/direct-sqlcipher.git"."f814ee68b16a9447fbb467ccc8f29bdd3546bfd9" = "1ql13f4kfwkbaq7nygkxgw84213i0zm7c1a8hwvramayxl38dq5d";
"https://github.com/simplex-chat/sqlcipher-simple.git"."a46bd361a19376c5211f1058908fc0ae6bf42446" = "1z0r78d8f0812kxbgsm735qf6xx8lvaz27k1a0b4a2m0sshpd5gl";
diff --git a/simplex-chat.cabal b/simplex-chat.cabal
index 8361d3f55d..c9c7012102 100644
--- a/simplex-chat.cabal
+++ b/simplex-chat.cabal
@@ -5,7 +5,7 @@ cabal-version: 1.12
-- see: https://github.com/sol/hpack
name: simplex-chat
-version: 5.6.0.3
+version: 5.6.0.4
category: Web, System, Services, Cryptography
homepage: https://github.com/simplex-chat/simplex-chat#readme
author: simplex.chat
@@ -355,13 +355,14 @@ executable simplex-bot-advanced
, text >=1.2.3.0 && <1.3
executable simplex-broadcast-bot
- main-is: ../Main.hs
+ main-is: Main.hs
+ hs-source-dirs:
+ apps/simplex-broadcast-bot
+ apps/simplex-broadcast-bot/src
other-modules:
Broadcast.Bot
Broadcast.Options
Paths_simplex_chat
- hs-source-dirs:
- apps/simplex-broadcast-bot/src
ghc-options: -Wall -Wcompat -Werror=incomplete-patterns -Wredundant-constraints -Wincomplete-record-updates -Wincomplete-uni-patterns -Wunused-type-patterns -threaded
build-depends:
aeson ==2.2.*
@@ -481,7 +482,10 @@ executable simplex-chat
, text >=1.2.3.0 && <1.3
executable simplex-directory-service
- main-is: ../Main.hs
+ main-is: Main.hs
+ hs-source-dirs:
+ apps/simplex-directory-service
+ apps/simplex-directory-service/src
other-modules:
Directory.Events
Directory.Options
@@ -489,8 +493,6 @@ executable simplex-directory-service
Directory.Service
Directory.Store
Paths_simplex_chat
- hs-source-dirs:
- apps/simplex-directory-service/src
ghc-options: -Wall -Wcompat -Werror=incomplete-patterns -Wredundant-constraints -Wincomplete-record-updates -Wincomplete-uni-patterns -Wunused-type-patterns -threaded
build-depends:
aeson ==2.2.*
diff --git a/src/Simplex/Chat.hs b/src/Simplex/Chat.hs
index cdb6f90a98..959265141d 100644
--- a/src/Simplex/Chat.hs
+++ b/src/Simplex/Chat.hs
@@ -1563,19 +1563,40 @@ processChatCommand' vr = \case
processChatCommand . APISendMessage chatRef True Nothing $ ComposedMessage Nothing Nothing mc
SendMessageBroadcast msg -> withUser $ \user -> do
contacts <- withStore' $ \db -> getUserContacts db vr user
- let cts = filter (\ct -> contactReady ct && contactActive ct && directOrUsed ct) contacts
- ChatConfig {logLevel} <- asks config
withChatLock "sendMessageBroadcast" . procCmd $ do
- (successes, failures) <- foldM (sendAndCount user logLevel) (0, 0) cts
- timestamp <- liftIO getCurrentTime
- pure CRBroadcastSent {user, msgContent = mc, successes, failures, timestamp}
+ let ctConns_ = L.nonEmpty $ foldr addContactConn [] contacts
+ case ctConns_ of
+ Nothing -> do
+ timestamp <- liftIO getCurrentTime
+ pure CRBroadcastSent {user, msgContent = mc, successes = 0, failures = 0, timestamp}
+ Just (ctConns :: NonEmpty (Contact, Connection)) -> do
+ let idsEvts = L.map ctSndEvent ctConns
+ sndMsgs <- createSndMessages idsEvts
+ let msgReqs_ :: NonEmpty (Either ChatError MsgReq) = L.zipWith (fmap . ctMsgReq) ctConns sndMsgs
+ (errs, ctSndMsgs :: [(Contact, SndMessage)]) <-
+ partitionEithers . L.toList . zipWith3' combineResults ctConns sndMsgs <$> deliverMessagesB msgReqs_
+ timestamp <- liftIO getCurrentTime
+ void $ withStoreBatch' $ \db -> map (createCI db user timestamp) ctSndMsgs
+ pure CRBroadcastSent {user, msgContent = mc, successes = length ctSndMsgs, failures = length errs, timestamp}
where
mc = MCText msg
- sendAndCount user ll (s, f) ct =
- (sendToContact user ct $> (s + 1, f)) `catchChatError` \e -> when (ll <= CLLInfo) (toView $ CRChatError (Just user) e) $> (s, f + 1)
- sendToContact user ct = do
- (sndMsg, _) <- sendDirectContactMessage user ct (XMsgNew $ MCSimple (extMsgContent mc Nothing))
- void $ saveSndChatItem user (CDDirectSnd ct) sndMsg (CISndMsgContent mc)
+ addContactConn :: Contact -> [(Contact, Connection)] -> [(Contact, Connection)]
+ addContactConn ct ctConns = case contactSendConn_ ct of
+ Right conn | directOrUsed ct -> (ct, conn) : ctConns
+ _ -> ctConns
+ ctSndEvent :: (Contact, Connection) -> (ConnOrGroupId, PQSupport, ChatMsgEvent 'Json)
+ ctSndEvent (_, Connection {connId, pqSupport}) = (ConnectionId connId, pqSupport, XMsgNew $ MCSimple (extMsgContent mc Nothing))
+ ctMsgReq :: (Contact, Connection) -> SndMessage -> MsgReq
+ ctMsgReq (_, conn) SndMessage {msgId, msgBody} = (conn, MsgFlags {notification = hasNotification XMsgNew_}, msgBody, msgId)
+ zipWith3' :: (a -> b -> c -> d) -> NonEmpty a -> NonEmpty b -> NonEmpty c -> NonEmpty d
+ zipWith3' f ~(x :| xs) ~(y :| ys) ~(z :| zs) = f x y z :| zipWith3 f xs ys zs
+ combineResults :: (Contact, Connection) -> Either ChatError SndMessage -> Either ChatError (Int64, PQEncryption) -> Either ChatError (Contact, SndMessage)
+ combineResults (ct, _) (Right msg') (Right _) = Right (ct, msg')
+ combineResults _ (Left e) _ = Left e
+ combineResults _ _ (Left e) = Left e
+ createCI :: DB.Connection -> User -> UTCTime -> (Contact, SndMessage) -> IO ()
+ createCI db user createdAt (ct, sndMsg) =
+ void $ createNewSndChatItem db user (CDDirectSnd ct) sndMsg (CISndMsgContent mc) Nothing Nothing False createdAt
SendMessageQuote cName (AMsgDirection msgDir) quotedMsg msg -> withUser $ \user@User {userId} -> do
contactId <- withStore $ \db -> getContactIdByName db user cName
quotedItemId <- withStore $ \db -> getDirectChatItemIdByText db userId contactId msgDir quotedMsg
@@ -2221,7 +2242,7 @@ processChatCommand' vr = \case
summary <- case changedCts_ of
Nothing -> pure $ UserProfileUpdateSummary 0 0 []
Just changedCts -> do
- let idsEvts = L.map ctSndMsg changedCts
+ let idsEvts = L.map ctSndEvent changedCts
msgReqs_ <- L.zipWith ctMsgReq changedCts <$> createSndMessages idsEvts
(errs, cts) <- partitionEithers . L.toList . L.zipWith (second . const) changedCts <$> deliverMessagesB msgReqs_
unless (null errs) $ toView $ CRChatErrors (Just user) errs
@@ -2238,16 +2259,15 @@ processChatCommand' vr = \case
-- [incognito] filter out contacts with whom user has incognito connections
addChangedProfileContact :: User -> Contact -> [ChangedProfileContact] -> [ChangedProfileContact]
addChangedProfileContact user' ct changedCts = case contactSendConn_ ct' of
- Left _ -> changedCts
- Right conn
- | connIncognito conn || mergedProfile' == mergedProfile -> changedCts
- | otherwise -> ChangedProfileContact ct ct' mergedProfile' conn : changedCts
+ Right conn | not (connIncognito conn) && mergedProfile' /= mergedProfile ->
+ ChangedProfileContact ct ct' mergedProfile' conn : changedCts
+ _ -> changedCts
where
mergedProfile = userProfileToSend user Nothing (Just ct) False
ct' = updateMergedPreferences user' ct
mergedProfile' = userProfileToSend user' Nothing (Just ct') False
- ctSndMsg :: ChangedProfileContact -> (ConnOrGroupId, PQSupport, ChatMsgEvent 'Json)
- ctSndMsg ChangedProfileContact {mergedProfile', conn = Connection {connId, pqSupport}} = (ConnectionId connId, pqSupport, XInfo mergedProfile')
+ ctSndEvent :: ChangedProfileContact -> (ConnOrGroupId, PQSupport, ChatMsgEvent 'Json)
+ ctSndEvent ChangedProfileContact {mergedProfile', conn = Connection {connId, pqSupport}} = (ConnectionId connId, pqSupport, XInfo mergedProfile')
ctMsgReq :: ChangedProfileContact -> Either ChatError SndMessage -> Either ChatError MsgReq
ctMsgReq ChangedProfileContact {conn} =
fmap $ \SndMessage {msgId, msgBody} ->
diff --git a/tests/Bots/DirectoryTests.hs b/tests/Bots/DirectoryTests.hs
index 1054a1d8eb..b78d36f489 100644
--- a/tests/Bots/DirectoryTests.hs
+++ b/tests/Bots/DirectoryTests.hs
@@ -522,7 +522,7 @@ testNotApprovedBadRoles tmp =
let approve = "/approve 1:privacy 1"
superUser #> ("@SimpleX-Directory " <> approve)
superUser <# ("SimpleX-Directory> > " <> approve)
- superUser <## " Group is not approved: user is not an owner."
+ superUser <## " Group is not approved: SimpleX-Directory is not an admin."
groupNotFound cath "privacy"
bob ##> "/mr privacy SimpleX-Directory admin"
bob <## "#privacy: you changed the role of SimpleX-Directory from member to admin"
diff --git a/tests/ChatClient.hs b/tests/ChatClient.hs
index 409dd2bb3e..8e9d11d91f 100644
--- a/tests/ChatClient.hs
+++ b/tests/ChatClient.hs
@@ -37,10 +37,11 @@ import Simplex.Chat.Types
import Simplex.FileTransfer.Description (kb, mb)
import Simplex.FileTransfer.Server (runXFTPServerBlocking)
import Simplex.FileTransfer.Server.Env (XFTPServerConfig (..), defaultFileExpiration)
+import Simplex.Messaging.Agent (disposeAgentClient)
import Simplex.Messaging.Agent.Env.SQLite
import Simplex.Messaging.Agent.Protocol (currentSMPAgentVersion, duplexHandshakeSMPAgentVersion, pqdrSMPAgentVersion, supportedSMPAgentVRange)
import Simplex.Messaging.Agent.RetryInterval
-import Simplex.Messaging.Agent.Store.SQLite (MigrationConfirmation (..))
+import Simplex.Messaging.Agent.Store.SQLite (MigrationConfirmation (..), closeSQLiteStore)
import qualified Simplex.Messaging.Agent.Store.SQLite.DB as DB
import Simplex.Messaging.Client (ProtocolClientConfig (..), defaultNetworkConfig)
import Simplex.Messaging.Crypto.Ratchet (supportedE2EEncryptVRange, pattern PQSupportOff)
@@ -250,10 +251,12 @@ startTestChat_ db cfg opts user = do
pure TestCC {chatController = cc, virtualTerminal = t, chatAsync, termAsync, termQ, printOutput = False}
stopTestChat :: TestCC -> IO ()
-stopTestChat TestCC {chatController = cc, chatAsync, termAsync} = do
+stopTestChat TestCC {chatController = cc@ChatController {smpAgent, chatStore}, chatAsync, termAsync} = do
stopChatController cc
uninterruptibleCancel termAsync
uninterruptibleCancel chatAsync
+ liftIO $ disposeAgentClient smpAgent
+ closeSQLiteStore chatStore
threadDelay 200000
withNewTestChat :: HasCallStack => FilePath -> String -> Profile -> (HasCallStack => TestCC -> IO a) -> IO a
diff --git a/tests/ChatTests/Direct.hs b/tests/ChatTests/Direct.hs
index 4e06f68fb6..4b0389ab90 100644
--- a/tests/ChatTests/Direct.hs
+++ b/tests/ChatTests/Direct.hs
@@ -2997,10 +2997,15 @@ testPQEnableContactCompression =
bob ##> "/pq @alice on"
bob <## "alice: enable quantum resistant end-to-end encryption"
PQSupportOn <- bob `pqSupportForCt` 2
+ threadDelay 300000
(alice, "lrg 1", v) \:#> (bob, v')
+ threadDelay 300000
(bob, "lrg 2", v') \:#> (alice, v')
+ threadDelay 300000
(alice, "lrg 3", v') \:#> (bob, v')
+ threadDelay 300000
(bob, "lrg 4", v') \:#> (alice, v')
+ threadDelay 300000
(alice, "lrg 5", v') +:#> (bob, v')
PQEncOff <- alice `pqForContact` 2
PQEncOff <- bob `pqForContact` 2
diff --git a/tests/ChatTests/Groups.hs b/tests/ChatTests/Groups.hs
index bf9b445925..77bac11145 100644
--- a/tests/ChatTests/Groups.hs
+++ b/tests/ChatTests/Groups.hs
@@ -871,6 +871,9 @@ testGroupRemoveAdd =
testChatCfg3 testCfgCreateGroupDirect aliceProfile bobProfile cathProfile $
\alice bob cath -> do
createGroup3 "team" alice bob cath
+
+ threadDelay 100000
+
-- remove member
alice ##> "/rm team bob"
concurrentlyN_
@@ -880,6 +883,9 @@ testGroupRemoveAdd =
bob <## "use /d #team to delete the group",
cath <## "#team: alice removed bob from the group"
]
+
+ threadDelay 100000
+
alice ##> "/a team bob"
alice <## "invitation to join the group #team sent to bob"
bob <## "#team_1: alice invites you to join the group as member"
@@ -1916,6 +1922,8 @@ testGroupLink =
(alice <# "#team cath> hey team")
(bob <# "#team cath> hey team")
+ threadDelay 100000
+
-- leaving team removes link
alice ##> "/l team"
concurrentlyN_
diff --git a/website/langs/cs.json b/website/langs/cs.json
index d087fd5bec..6e2416e4a2 100644
--- a/website/langs/cs.json
+++ b/website/langs/cs.json
@@ -37,10 +37,10 @@
"hero-overlay-1-title": "Jak funguje SimpleX?",
"hero-overlay-2-title": "Proč jsou uživatelská ID špatná pro soukromí?",
"feature-1-title": "E2E šifrované zprávy s Markdown a editací",
- "feature-3-title": "Decentralizované tajné skupiny —pouze uživatelé vědí, že existují", + "feature-3-title": "E2E-šifrované decentralizované skupiny — pouze uživatelé vědí, že existují", "feature-4-title": "Hlasové zprávy šifrované E2E", "feature-6-title": "E2E šifrované
hlasové a videohovory", - "feature-7-title": "Přenosná šifrovaná databáze— přeneste svůj profil do jiného zařízení", + "feature-7-title": "Přenosné šifrované ůložiště aplikace — přeneste profil do jiného zařízení", "feature-8-title": "režim Inkognito —
Unikátní pro SimpleX Chat", "simplex-network-overlay-1-title": "Srovnání s protokoly zpráv P2P", "simplex-private-2-title": "Další vrstva
šifrování serveru", @@ -170,8 +170,8 @@ "comparison-section-list-point-1": "Založeném obvykle na telefonním čísle a v některých případech uživatelském jménu", "comparison-section-list-point-2": "Adresy založené na DNS", "comparison-section-list-point-3": "Veřejný klíč nebo jiné globálně jedinečné ID", - "comparison-section-list-point-4": "Pokud jsou servery operátora ohroženy", - "comparison-section-list-point-5": "Nechrání metadata uživatelů", + "comparison-section-list-point-4": "Pokud jsou servery operátora kompromitovány. Ověřte bezpečnostní kód v Signálu a nějaké jiné aplikaci ke zmírnění", + "comparison-section-list-point-5": "Nechrání soukromí metadat uživatelů", "comparison-section-list-point-6": "Zatímco P2P jsou distribuovány, nejsou federované – fungují jako jediná síť", "comparison-section-list-point-7": "P2P sítě mají buď centrální autoritu, nebo může být ohrožena celá síť", "see-here": "viz zde", @@ -195,7 +195,7 @@ "simplex-explained-tab-3-p-2": "Uživatelé mohou dále zlepšit soukromí metadat pomocí Tor pro přístup k serverům, což zabraňuje korelaci podle IP adresy.", "hero-p-1": "Jiné aplikace mají uživatelská ID: Signal, Matrix, Session, Briar, Jami, Cwtch atd.
SimpleX ne, ani náhodná čísla.
To radikálně zlepšuje vaše soukromí.", "hero-2-header-desc": "Video ukazuje, jak se spojit se svým přítelem prostřednictvím jeho jednorázového QR kódu, osobně nebo prostřednictvím QR kódu ve videu. Můžete se také připojit sdílením pozvánky.", - "feature-2-title": "Obrázky a soubory šifrované E2E
", + "feature-2-title": "E2E šifrované
obrázky, videa a soubory", "feature-5-title": "Mizící tajné konverzace", "simplex-private-1-title": "2-vrstvé
end-to-end šifrování", "simplex-private-8-title": "Smíchání zpráv
ke snížení korelace", @@ -232,5 +232,25 @@ "on-this-page": "Na této stránce", "back-to-top": "Zpět nahoru", "newer-version-of-eng-msg": "V angličtině je novější verze této stránky.", - "glossary": "Rejstřík" + "glossary": "Rejstřík", + "hero-overlay-3-title": "Posouzení bezpečnosti", + "hero-overlay-3-textlink": "Posouzení bezpečnosti", + "hero-overlay-card-3-p-1": "Trail of Bits je přední bezpečnostní a technologické poradenství, jejichž klienti zahrnují velké technologické firmy, vládní agentury a významné blockchainové projekty.", + "f-droid-page-simplex-chat-repo-section-text": "Chcete-li jej přidat do vašeho F-Droid clienta, použijte tuto adresu URL:", + "f-droid-page-f-droid-org-repo-section-text": "SimpleX Chat a F-Droid.org repozitáře jsou podepsané různými klíči. Chcete-li přepnout, prosím exportujte chat databázi a přeinstalujte aplikaci.", + "comparison-section-list-point-4a": "SimpleX relé nemůže ohrozit šifrování e2e. Ověřte bezpečnostní kód, který zmírňuje mimo pásmový útok na kanál", + "docs-dropdown-8": "Služba SimpleX Directory", + "please-enable-javascript": "Prosím, povolte JavaScript k zobrazení QR kódu.", + "please-use-link-in-mobile-app": "Prosím použijte odkaz v mobilní aplikaci", + "simplex-chat-via-f-droid": "SimpleX Chat přes F-Droid", + "simplex-chat-repo": "SimpleX Chat repozitář", + "stable-and-beta-versions-built-by-developers": "Stabilní a beta verze vytvořené vývojáři", + "signing-key-fingerprint": "Otisk podpisového klíče (SHA-256)", + "f-droid-org-repo": "F-Droid.org repozitář", + "stable-versions-built-by-f-droid-org": "Stabilní verze vytvořené F-Droid.org", + "releases-to-this-repo-are-done-1-2-days-later": "Vydání v tomto repozitáři se provádí o 1-2 dny později", + "jobs": "Připojit k týmu", + "hero-overlay-card-3-p-2": "Trail of Bits přezkoumala kryptografii a síťové komponenty SimpleX platformy v listopadu 2022.", + "hero-overlay-card-3-p-3": "Přečtěte si více v ohlášení.", + "docs-dropdown-9": "Ke stažení" } diff --git a/website/src/_includes/blog_previews/20240323.html b/website/src/_includes/blog_previews/20240323.html new file mode 100644 index 0000000000..7fe4c78179 --- /dev/null +++ b/website/src/_includes/blog_previews/20240323.html @@ -0,0 +1,16 @@ +
SimpleX network: deliver real privacy via a profitable business and non-profit protocol governance:
+ +-
+
- community and business interests are aligned. +
- the journey to the decentralized non-profit protocol governance. +
- welcome, Esra'a! +
v5.6 is released:
+ +-
+
- quantum resistant end-to-end encryption (BETA) - enable it for the new contacts. +
- use the app during the audio and video calls. +
- migrate all app data to another device via QR code. +
- blocking members and many other improvements. +