kjodle/essays-ccs
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

update SimpleX in Why not signal (#131)

Browse Source
This commit is contained in:
Evgeny Poberezkin 2022-07-11 18:31:16 +01:00 committed by GitHub
parent 664b145302
commit 325a8c3f4d
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 4 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
why_not_signal.md
View File

@ -253,8 +253,10 @@ Briar is newer, and lacks too many features to be usable for large organizations
#### SimpleX Caveats
- The iOS and Android clients don't use the app store-run push notification system for privacy reasons; receiving messages can be delayed when the app isn't open.
- There isn't currently a web-based client because the SimpleX project assesses that web has too many attack vectors.
- The iOS client from v3.0 supports instant push notifications - it requires that users opt-in to using a central push notifications server. The project plans to add support for users to [self-host a part of notifications server functionality](https://github.com/simplex-chat/simplex-chat/blob/stable/blog/20220404-simplex-chat-instant-notifications.md#our-ios-approach-has-one-trade-off).
- The Android client supports fully private notification by running an optional always-on background service.
- There is no web-based client because of additional attack vectors.
- SimpleX messaging servers can see users IP addresses; the project plans to embed access via Tor into the apps.
## Conclusions