diff --git a/package.yaml b/package.yaml index e34e924a2..889866307 100644 --- a/package.yaml +++ b/package.yaml @@ -13,7 +13,7 @@ extra-source-files: dependencies: - aeson == 1.5.* - - ansi-terminal >= 0.10 && < 0.12.0 + - ansi-terminal >= 0.10 && < 0.12 - attoparsec == 0.13.* - base >= 4.7 && < 5 - base64-bytestring >= 1.0 && < 1.3 diff --git a/simplex-chat.cabal b/simplex-chat.cabal index d30d63cc1..f7266a89c 100644 --- a/simplex-chat.cabal +++ b/simplex-chat.cabal @@ -40,7 +40,7 @@ library ghc-options: -Wall -Wcompat -Werror=incomplete-patterns -Wredundant-constraints -Wincomplete-record-updates -Wincomplete-uni-patterns -Wunused-type-patterns build-depends: aeson ==1.5.* - , ansi-terminal >=0.10 && <0.12.0 + , ansi-terminal >=0.10 && <0.12 , attoparsec ==0.13.* , base >=4.7 && <5 , base64-bytestring >=1.0 && <1.3 @@ -76,7 +76,7 @@ executable simplex-chat ghc-options: -Wall -Wcompat -Werror=incomplete-patterns -Wredundant-constraints -Wincomplete-record-updates -Wincomplete-uni-patterns -Wunused-type-patterns -threaded build-depends: aeson ==1.5.* - , ansi-terminal >=0.10 && <0.12.0 + , ansi-terminal >=0.10 && <0.12 , attoparsec ==0.13.* , base >=4.7 && <5 , base64-bytestring >=1.0 && <1.3 @@ -118,7 +118,7 @@ test-suite simplex-chat-test ghc-options: -Wall -Wcompat -Werror=incomplete-patterns -Wredundant-constraints -Wincomplete-record-updates -Wincomplete-uni-patterns -Wunused-type-patterns build-depends: aeson ==1.5.* - , ansi-terminal >=0.10 && <0.12.0 + , ansi-terminal >=0.10 && <0.12 , async ==2.2.* , attoparsec ==0.13.* , base >=4.7 && <5 diff --git a/simplex.md b/simplex.md index b39703e55..6dc22096d 100644 --- a/simplex.md +++ b/simplex.md @@ -4,8 +4,8 @@ Existing chat platforms and protocols have some or all of the following problems: -- Lack of privacy of the conversation, partially caused by [E2EE][1] implementations. -- Lack of privacy of the user profile and connections. +- Lack of privacy of the user profile and connections (meta-data privacy). +- No protection (or only optional protection) of [E2EE][1] implementations from MITM attacks. - Unsolicited messages (spam and abuse). - Lack of data ownership and protection. - Complexity of usage for all non-centralized protocols to non-technical users.