1. Main reasons why the app isn't recommended: Provide a transparency report.

It is available online and updated at least quarterly, or if anything changes: https://simplex.chat/transparency/

https://securemessagingapps.com by is the great comparison of messaging apps, but there are several incorrect statements about @SimpleXChat there. Commenting in thread 🧵 below.

Opened now again - was limited to 100 responses

Please fill this survey about SimpleX Chat: https://gdlgeuc34xt.typeform.com/to/XAKc5N1l

It is a smaller version of the survey we did last year, please answer again if you answered then.

Thank you!

Please upgrade desktop app to v6.0 as well.

Announcing $1.3m pre-seed investment from nostr:npub1sg6plzptd64u62a878hep2kev88swjh3tw00gjsfl8f237lmu63q0uf63m and

Asymmetric VC in SimpleX Chat 🚀

https://simplex.chat/blog/20240814-simplex-chat-vision-funding-v6-private-routing-new-user-experience.html

Also SimpleX Chat v6.0 stable is now released with the new user experience and private message routing – details in the post.

If any applicable legislation were to be passed, then we will be getting a legal advice based on its final wording about what is the course of action that is both legal and also benefits our users most.

At this point it would be unprofessional to speculate about it.

In case you missed the news, #ChatControl is back on the agenda of the EU governments: https://www.patrick-breyer.de/en/take-action-to-stop-chat-control-now/

We wrote before that strong e2e encryption is the only way to protect children online: https://simplex.chat/blog/20240601-protecting-children-safety-requires-e2e-encryption.html

Write to the MPs you voted for – every single letter can change the outcome.

And huge thanks to Patrick Breyer for fighting this insanity.

Please note: we do NOT control the domain simplexchat.org

It might be a phishing site to collect the data (it has an exact copy of our website https://simplex.chat).

We submitted the complaint to the domain registrar (GNAME).

Do NOT download anything from simplexchat.org, obviously.

We love Nostr as a publishing platform that offers unparalleled censorship resistance. But NIP44 does NOT provide most of the important qualities of e2e encryption:

- break-in recovery.

- repudiation (deniability).

- visibility of connection graph to observers.

- fixed message sizes (although it can be provided by the specific app)

- resistance to Shore algorithm (PQ encryption).

It's unclear whether it provides forward secrecy, but the spec implies that it does not - I might be wrong here.

We wrote this post about the qualities of e2e encryption and why they are important: https://simplex.chat/blog/20240314-simplex-chat-v5-6-quantum-resistance-signal-double-ratchet-algorithm.html

SimpleX Chat v6.0-beta.4 is released!

It is stable to use, and please let us know any issues - any help testing it is really great!

You can get beta version for iOS from Apple TestFlight, and for Android from GitHub or from our F-Droid repo (it's still in review in Play Store beta channel): https://simplex.chat/downloads/

The final release will be published on 8/14, together with the announcements.

Because I specifically do not want to use any public currency blockchain - I want an accounting method, not money. There many useful legal differences when the flow of money is the opposite to the flow of cryptographic keys. Read the doc.

Talking at MoneroKon in 25 min! Watch the livestream here: https://youtube.monerokon.org/

No, not like Session at all.

We are not going to throw away double ratchet, and we are not going to create cryptocurrencies based on public blockchains. If we ever replace double ratchet with any other scheme, we would replace it with the more secure one, not with a less secure one like Session did.

We are moving to a very different direction from Session's: https://simplex.chat/blog/20240516-simplex-redefining-privacy-hard-choices.html

Also, the design of the private routing achieves the level of metadata privacy that onion routing in Session doesn’t provide - I can comment more on it, but here is the post: https://simplex.chat/blog/20240604-simplex-chat-v5.8-private-message-routing-chat-themes.html

I understand that Session fans might be angry about my criticism of Session, but its crisis is of their own doing - Session's decision to remove double ratchet was a wrong one - users who choose Session need double ratchet, at least.

The path for Session to regain users' trust would be:

1) get double ratchet back, with all its qualities, and figure out how to solve multidevice without compromising encryption security - I’d happily collaborate on that, as an acceptable solution doesn’t exist yet.

2) make node ownership optionally transparent and let clients choose nodes owned by known and different operators (to avoid unknown operators who potentially collude undermining onion routing promises - these promises only hold under the assumption that operators of nodes chosen for the circuit do not collude).

3) decentralise media storage in the same way messages are decentralised - Session may as well adopt XFTP protocol we designed - it's independent from messaging, and that can create some collaboration points too.

4) add a notification when another device access the same profile via recovery code.

5) protect access to recovery code in the app with PIN.

In its current state Session is simply dangerous to use for any scenarios requiring privacy and security.

Solving points 4 and 5 would remove Session from "dangerous" territory and make it simply “not too secure”. I don't understand why it wasn't already done after the public conversation with Keith several months ago, see the links here: https://x.com/SimpleXChat/status/1755216356159414602

Solving 1 would make it secure. Solving 2 and 3 would make it private.

It's correct to point out SimpleX network limitations, and we work on resolving them.

But by misleading the audience about Session level of privacy and security you are creating risks that may cost some people their lives or freedom - this is really bad for the community and detrimental for your reputation as well.

You’re ahead of us - thank you, reposted :)

Communication privacy and hard product choices: https://simplex.chat/blog/20240516-simplex-redefining-privacy-hard-choices.html

We are upgrading the preset SimpleX relays to the new version - it is compatible only with the apps starting from v5.5.3 (released early February) - please upgrade to the latest version and ask your friends to upgrade too.

SimpleX Chat v5.7 released:

- quantum resistant e2e encryption with contacts enabled by default.

- forward messages without revealing the source and save them to private notes.

- in-call sounds and switching sound sources.

- customizable profile images - from square to circle.

- better network connection management.

Also, we added Lithuanian interface language to Android and desktop apps - thanks to our users!

Read more: https://simplex.chat/blog/20240426-simplex-legally-binding-transparency-v5-7-better-user-experience.html

The post about SimpleX Chat v5.6 release with quantum resistant end-to-end encryption and also about how SimpleX network protocols will be moving to nonprofit governance:

https://

simplex.chat/blog/20240323-sim

plex-network-privacy-non-profit-v5-6-quantum-resistant-e2e-encryption-simple-migration.html

Esra'a Al Shafei has just joined SimpleX Chat team to help us deliver these goals - welcome!

Updated "SimpleX Chat Privacy Policy and Conditions of Use"

The updated document: https://github.com/simplex-chat/simplex-chat/blob/stable/PRIVACY.md

The changes: https://github.com/simplex-chat/simplex-chat/pull/3796/files

TL;DR:

- it clarifies that we develop software for communication network, and not a communication service.

- it highlights the requirement of AGPLv3 license to publish any code modifications, and our commitment to run unmodified code.

Let us know any comments / questions!