IntenseFinance/simplex-chat
3
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

Merge branch 'master' into v1

Browse Source
This commit is contained in:
Evgeny Poberezkin 2022-01-11 21:25:18 +00:00 committed by GitHub
commit fcee108863
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
3 changed files with 6 additions and 6 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
package.yaml
View File

@ -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

6
simplex-chat.cabal
View File

@ -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

4
simplex.md
View File

@ -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.