simplex
SimpleX Chat

https://github.com/simplex-chat/simplex-chat#readme

SimpleX - the first messaging platform operating without user identifiers of any kind - 100% private by design!

Public Key

npub1exv22uulqnmlluszc4yk92jhs2e5ajcs6mu3t00a6avzjcalj9csm7d828

NIP-05 Address

_@simplex.chat

NIP-57 Address

simplex@getalby.com

Profile Code

nprofile1qqsvnx99ww0sfall7gpv2jtz4ftc9v6wevgdd7g4hh7awkpfvwlezugpz3mhxue69uhhyetvv9ujumn0wd68ytnzvuq3gamnwvaz7tmwdaehgu3wdau8gu3wv3jhvxmuv00

Publishing to

relay.nostr.bg

nostr.oxtr.dev

Author Public Key

npub1exv22uulqnmlluszc4yk92jhs2e5ajcs6mu3t00a6avzjcalj9csm7d828

Show more details

Last Notes

2024-08-31 16:31:15

- reply

It is not the same. Build reproducibility means that every time you build the app from the source code you would get exactly the same result, identical byte by byte. It would allow independent parties to validate that the apps that we distribute via different channels are built from the source code we publish.
The problem is that to achieve this quality requires that the build process is deterministic, and in general case it is not:
- some libraries may embed timestamps during compilation.
- compilers my use random numbers for some identifiers.
- etc.
We plan to solve this problem, but it is much harder than it may seem.

2024-08-31 16:25:58

Answering your questions about "private message routing" in SimpleX network:
1. Does SimpleX protect IP addresses? Yes.
2. Doesn't private message routing reinvent Tor? No.
3. Why don't you embed Tor? Tor is great, but not for all.
Read more in FAQ: https://simplex.chat/faq/#does-simplex-protect-my-ip-address

2024-08-24 12:19:46

- reply

Thanks to our users who highlighted these inaccuracies to us!

2024-08-24 12:19:10

- reply

6. Is the design well documented? Somewhat
The design documentation was reviewed in preparation for design security audit in July 2024 - report is about to be published.

2024-08-24 12:18:40

- reply

5. Does the company log timestamps/IP addresses? Yes
This is incorrect, we never logged IP addresses and access timestamps of the users.
Further, the private message routing that is now enabled by default for all users prevents such logging by any 3rd party servers with modified code:
https://simplex.chat/blog/20240604-simplex-chat-v5.8-private-message-routing-chat-themes.html

2024-08-24 12:18:14

- reply

4. Directory service could be modified to enable a MITM attack? Yes
This is incorrect, as there is no user directory service at all (and no knowledge of even the number of users), and MITM by servers is not possible by design, even without optional security code verification (that exists to mitigate MITM by the channel you used to pass one-time invitation link, e.g. email).

2024-08-24 12:17:43

- reply

3. Cryptographic primitives. Curve25519 / XSalsa20 256 / Poly1305 (downgraded for the absence of PQ encryption).
We added PQ encryption in March this year: https://simplex.chat/blog/20240314-simplex-chat-v5-6-quantum-resistance-signal-double-ratchet-algorithm.html
This is done in the same way as Apple describes as PQ3 here: https://security.apple.com/blog/imessage-pq3/
it provides stronger protection than Signal design where PQ encryption only applies to the initial key exchange.

2024-08-24 12:16:34

- reply

2. Company jurisdiction: UK
We disagree that there are any jurisdictions that are particularly good for privacy.
Also, this might important for centralised services, like Threema, where the users can't host servers, and much less important for decentralized network, such as SimpleX, where there are hundreds (if not thousands) of servers that we don't control.

2024-08-24 12:15:59

- reply

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/

2024-08-24 12:15:01

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

2024-08-20 15:18:31

- reply

Opened now again - was limited to 100 responses

2024-08-20 10:48:16

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!

2024-08-14 14:03:15

- reply

Please upgrade desktop app to v6.0 as well.

2024-08-14 13:41:27

Announcing $1.3m pre-seed investment from @npub1sg6…f63m 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.

2024-08-12 18:41:39

- reply

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.

2024-08-12 16:24:50

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.

2024-08-11 20:22:18

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.

2024-08-08 22:07:00

- reply

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

2024-08-08 21:57:33

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.
https://m.primal.net/Jsqo.jpg

2024-07-04 20:48:03

The future of privacy depends on you!
https://simplex.chat/blog/20240704-future-of-privacy-enforcing-privacy-standards.html
To make privacy a non-negotiable obligation of technology providers:
- support noyb.eu legal actions.
- write to your elected representatives.
- explain the value privacy to your friends.

2024-06-30 13:20:30

- reply

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.

2024-06-09 08:05:27

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

2024-06-08 17:55:25

- reply

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.

2024-06-05 12:51:04

- reply

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

2024-05-16 19:03:53

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

2024-05-03 08:38:05

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.

2024-04-26 22:59:54

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

2024-03-23 20:53:23

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!

2024-02-24 21:42:43

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!

2024-02-12 21:10:17

- reply

Would be good to look at the spec.

2024-02-12 19:30:40

- reply

@npub1gcx…nj5z Thanks for the suggestions. We did indeed consider various ideas about how to reduce the persistence queue ID, but the to rotate the queues to another server periodically seemed simpler and providing better metadata protection. The current approach also allows some basic protection from resource exhaustion attacks.
What I don't quite follow - if the same key A is used to retrieve the messages how it is any better than having queue ID from the perspective of correlating messages to the users? Wouldn't it still identify the user any better, and now instead of mapping IP addresses to queues, the server could map IP addresses to the messages... Maybe I don't understand what you propose?
The ideas we considered were about trying to avoid any persistent IDs entirely, e.g. via some kind of DHT tables, and something like this might happen in "v3" of the protocols (we are currently still moving to "v2").

2024-02-12 18:51:19

- reply

Repudiation is the important quality for any private conversation - it gives digital conversation the same properties as face to face - you can plausibly deny it. And yes, non-repudiation can be added in the context where it is needed.

2024-02-12 18:49:47

- reply

Yes, but in Session it is sadly achieved it at a cost of compromising security - and the recovery phrase is just two taps away, to be copied unnoticeably even by technically incompetent attacker…

2024-02-07 13:06:37

Improving repudiation (deniability) in SimpleX protocols
Please send any questions/comments!
We believe that repudiation (aka deniability) is very important for communications. See this discussion with Session CTO about it, for example:
https://twitter.com/JefferysKee/status/1754336020857029013
https://twitter.com/SimpleXChat/status/1754455524068720762
https://twitter.com/JefferysKee/status/1754762787119919587
https://twitter.com/SimpleXChat/status/1754840209936543977
Currently only a part of SimpleX protocol stack provides it – client-to-client e2e encryption, that includes double ratchet (aka Signal) algorithm in one of the layers.
Client-relay protocol, on another hand, does not provide it, and as relays are chosen by the recipients, a modified relay can provide non-repudiation for sent messages, which is undesirable in the context of private communications.
We believe there should be a possibility for digital off-the-record conversations, in the same way as it is possible for in-person meetings - while recipient can keep the memory and even transcript, it should not be a strong proof to a third party.
This proposal adds repudiation to client-relay protocol by replacing cryptographic signature with authenticator (see this WIP document for the details: https://github.com/simplex-chat/simplexmq/blob/ep/cmd-auth/rfcs/2024-02-03-deniability.md).
It is already mostly implemented and will be fully rolled out by v5.7.
A more detailed post about repudiation importance and its acceptance in society and legal systems is coming.

2024-01-31 14:23:07

- reply

I don’t think you can equate the amount of metadata available to Matrix and Signal servers with what is available to SimpleX servers - it’s actually less than what is available to Nostr relays users connect to. Putting them in one list, however flattering, implies a similar amount of metadata available, which is very far from reality and is misleading.

2024-01-31 12:53:57

The comments on comparisons of SimpleX with other platforms: https://www.reddit.com/r/SimpleXChat/comments/1afgrcj/comments_on_comparisons_of_simplex_with_other/

2024-01-24 20:57:42

SimpleX Chat v5.5 is released – with private notes and group history!
https://simplex.chat/blog/20240124-simplex-chat-infrastructure-costs-v5-5-simplex-ux-private-notes-group-history.html
Also in this release:
- simpler UX to connect - paste SimpleX links to search bar.
- improved message delivery and reduced battery usage.
- fully encrypted files and media in the app storage.
- reveal secrets in messages by tapping.
- many other improvements.
Downloads page: https://simplex.chat/downloads/
#privacy #security #messenger

2023-12-30 22:18:51

Thank you for all the support this year - it's been epic!
These are the last releases this year!
New in v5.4.2:
- faster sending messages to groups.
- lower CPU usage (except armv7 devices).
- on iOS: improved notifications and smaller video sizes
- many fixes!
In addition to that, v5.5-beta.0 has:
- new simpler UI for making connections.
- optional visible history in groups.
- reveal the secret texts by tapping.
Get them via our downloads page: https://simplex.chat/downloads/
Happy new year!

2023-12-03 09:50:58

A talk about SimpleX Chat at BornHack 2023 conference by Peter Stuge:
https://media.ccc.de/v/bornhack2023-56143-simplex-chat-simple-m (recently uploaded)
The talk was made when v5.2 was the latest, with lots of progress since:
- local file encryption
- desktop client
- using mobile from desktop
etc.
Thank you!

2023-11-25 20:30:04

Simplex Chat v5.4 is released – link mobile and desktop apps via secure quantum resistant protocol.
Also in v5.4:
- Many group improvements:
- faster to join and more reliable. Once you upgrade to v5.4, join the new users' group and find other groups in SimpleX directory.
- create groups with incognito profile.
- block group members to reduce noise.
- Better calls: faster to connect, with screen sharing on desktop.
- Many other fixes and improvements.
Read more in the post: https://simplex.chat/blog/20231125-simplex-chat-v5-4-link-mobile-desktop-quantum-resistant-better-groups.html
Install the apps via downloads page: https://simplex.chat/downloads/

2023-11-12 09:08:51

SimpleX Chat v5.4.0-beta.3!
Share screen/window in desktop video calls!
Lots of group improvements:
- create groups incognito.
- block some members just for you.
- etc.
Lots of fixes - more stable connections, more stable sending files, fixed file sharing and many crashes.
Get it from GitHub, our F-Droid repo, Play Store beta and TestFlight for iOS: https://simplex.chat/downloads/
Also, iOS and Android (aarch64 only for now – it didn't change for arvm7a devices) are built using the new version of the GHC compiler that should reduce the battery consumption a bit - please share how battery consumption changed for you, comparing with the previous version.

2023-10-27 16:42:37

RIP Chat Control?
https://european-pirateparty.eu/historic-agreement-on-chatcontrol-european-parliament-wants-to-safeguard-secure-encryption/ while I always believed that "Chat Control" as it was proposed would be dead on arrival, and unenforceable, it's always great to see common sense prevail. Some win for #privacy and #security of communications. The fight is far from over though.

2023-10-11 11:44:33

https://freedom.tech/simplex-chat-review/ - a fantastic review of SimpleX Chat by @npub1tr4…2y5g

2023-10-08 18:43:30

SimpleX Chat is now available via AppImage hub!
https://www.appimagehub.com/p/2093289

2023-10-01 19:06:17

SimpleX Chat desktop for Windows is released in v5.4-beta.0!
https://github.com/simplex-chat/simplex-chat/releases/tag/v5.4.0-beta.0

2023-09-28 13:02:01

- reply

I don’t think that marketing Session in competitor’s threads is a viable replacement for lost deniability and forward secrecy, and for the fact that whoever has passphrase can read user’s messages without them knowing. So no, I don’t think anybody needs to use session, even Signal seems a better trade off.

2023-09-27 20:21:40

- reply

Via export in database settings, but you can’t use one profile in both devices yet

2023-09-27 20:20:51

- reply

F-droid is always a bit behind, you can check our fdroid repo: https://simplex.chat/fdroid

2023-09-27 20:19:47

- reply

Working on it - this week seems likely!

2023-09-27 20:18:58

- reply

Yep, there was a broken M1 binary a the one uploaded now is fixed (in 5.3.1)

2023-09-25 19:59:32

SimpleX Chat v5.3 is released – with new desktop app and local file encryption!
Also in this release:
- group improvements.
- simplified incognito mode
- better app responsiveness, stability and 40% reduced memory usage.
- new privacy settings: show last messages & save draft.
Added 6 new interface languages thanks to our users - Arabic, Bulgarian, Finnish, Hebrew, Thai and Ukrainian.
Read more: https://simplex.chat/blog/20230925-simplex-chat-v5-3-desktop-app-local-file-encryption-directory-service.html
Downloads page: https://simplex.chat/downloads/
#privacy #security #messenger

2023-09-10 10:26:18

- reply

Verified!

2023-09-10 10:23:29

- reply

Thanks all - got it!

2023-09-10 10:13:33

Hm… where do I find my public key for NIP-05? npub address isn’t it, right?

2023-09-10 09:35:52

- reply

There is a desktop app beta via GitHub releases but it can only work with a separate profile for now - it’ll be announced soon!

2023-08-24 17:44:34

- reply

Join via link?

2023-08-19 18:16:59

SimpleX Directory Service and v5.3 public beta are released!
You can search for public groups via the experimental SimpleX Directory Service: connect to it via [this address](https://simplex.chat/contact#/?v=1-4&smp=smp%3A%2F%2Fu2dS9sG8nMNURyZwqASV4yROM28Er0luVTx5X1CsMrU%3D%40smp4.simplex.im%2FeXSPwqTkKyDO3px4fLf1wx3MvPdjdLW3%23%2F%3Fv%3D1-2%26dh%3DMCowBQYDK2VuAyEAaiv6MkMH44L2TcYrt_CsX3ZvM11WgbMEUn0hkIKTOho%253D%26srv%3Do5vmywmrnaxalvz6wi3zicyftgio6psuvyniis6gco6bp6ekl4cqj4id.onion).
Mobile apps public beta v5.3 are released:
- delivery receipts
- new layout in groups
- new UX for incognito mode
- etc.
Desktop app beta is now usable, please try it: https://github.com/simplex-chat/simplex-chat/releases/tag/v5.3.0-beta.5

2023-07-30 10:24:15

Please answer this short survey about SimpleX Chat!
https://gdlgeuc34xt.typeform.com/to/MNb0qLP9
It will take 5 minutes and will help us improve SimpleX Chat for you!
It is TypeForm – to avoid their cookies, use a private browser window.
Thank you!

2023-07-29 11:43:33

- reply

Can’t upload here it seems

2023-07-29 07:50:32

- reply

Any suggestion on the service to host?

2023-07-29 07:08:20

SimpleX Chat: The New Frontiers (livestream recording)
https://youtu.be/7yjQFmhAftE
- how does it work without user IDs
- desktop app demo (1:15) – you can already download beta version for Mac and Linux from GitHub
- how to set up your relay (3:51)
- how SimpleX Chat is funded (11:25)
- the problems and the future of groups (18:23)
- the demo of SimpleX Directory Service (25:20)
- Q&A (28:51)

2023-07-27 16:03:31

We are starting the livestream with the demo of SimpleX Chat desktop app and more in ~1 hour (see the previous post).
You can watch here https://stream.simplex.chat and ask any questions via the group (the QR code to join is on the page).

2023-07-26 22:02:50

- reply

Relays are decentralised of course

2023-07-26 22:02:21

- reply

What’s WINE?

2023-07-25 21:59:45

SimpleX Chat: New Frontiers – 7/27 at 17:00 UTC
Join us online on Thursday at 10am PT/1pm ET/6pm UK at https://stream.simplex.chat.
We will:
- demo the new desktop app.
- show how to set up SimpleX servers with dual address (public+onion).
- share the plan for SimpleX group and communities.
- possibly, show one more thing.
#OpenSource #Security #Privacy

2023-07-22 21:16:20

SimpleX Chat – #private and #secure #opensource messenger without user IDs of any kind (not even random numbers) – v5.2 with message delivery receipts and more stable message delivery is now released to App Store and Play Store!
https://simplex.chat/blog/20230722-simplex-chat-v5-2-message-delivery-receipts.html

2023-07-17 21:55:12

SimpleX Chat: v5.2-beta.2 with delivery receipts, favorite chats, and more is available! Also - join our event on July 27!
You can get the new version from GitHub, TestFlight, Play Store beta and our F-Droid repo - the links are here: https://github.com/simplex-chat/simplex-chat#readme
Full release and the release announcement are coming on Saturday July 22nd.
Also, we will host an online event on July 27 at 17:00 UTC (6pm UK, 10am PT) to talk about:
- what's new in v5.2, why we won't have read receipts and what is coming soon
- how we will solve the problem of groups and communities that are emerging on SimpleX platform
- we will demo how to host a server with dual address (both clearnet and onion) in linux VM, so that users who prefer to only connect to onion addresses can communicate with you via your self-hosted server even if you don't use Tor - it's much simpler than you think.
- we will answer all your questions too.
Online platform to connect to TBC, we'll make sure that it doesn't require any registration. You will be able to ask any questions in SimpleX group, you can already join it now via this link #SimpleX-Event-2023-07-27:
https://simplex.chat/contact#/?v=1-2&smp=smp%3A%2F%2FPQUV2eL0t7OStZOoAsPEV2QYWt4-xilbakvGUGOItUo%3D%40smp6.simplex.im%2FLDKQObOAkBcXZNtQIk5SXcZG4MDrCsc-%23%2F%3Fv%3D1-2%26dh%3DMCowBQYDK2VuAyEA6IE5fbkd0IXEbqp2FfwQubmBDxZIkpKJdt0ucGYBdBQ%253D%26srv%3Dbylepyau3ty4czmn77q4fglvperknl4bi2eb2fdy2bh4jxtf32kf73yd.onion&data=%7B%22type%22%3A%22group%22%2C%22groupLinkId%22%3A%22xVjXFRuTBuwOLieFa9FiIw%3D%3D%22%7D

2023-06-30 11:06:10

- reply

Yes, it’s a static page and it can be hosted on any domain - the app ignores domain part when processing the links. We didn’t split it from the website, but it’s trivial for anyone to split.

2023-06-30 11:00:16

We've just revived the demo of CLI from the old website:
https://simplex.chat/docs/cli.html
It's completely useless of course, purely a sentimental value, as this demo existed ~9 months before CLI was built, which was ~9 months before the mobile apps...
It's exactly how CLI looks today – that's feels really weird.
It all has to start somewhere, and journey is longer than it seems in the beginning.
#messenger #privacy #security

2023-06-30 10:59:00

- reply

You can use Orbot indeed

2023-06-30 10:58:41

- reply

That’s correct, simplex.chat domain doesn’t participate in the connection, and the only attack possible is via GitHub replacing page code - I don’t consider it a real threat for now.
Also, you can replace https://simplex.chat/ with simplex:/
It’s probably time we make it an option in the app…

2023-06-28 20:43:20

My talk at MoneroKon about SimpleX Chat current and future design https://youtu.be/0stN1SjZn0I?t=10572

2023-06-24 20:25:03

- reply

In any existing browser without changes I mean

2023-06-24 20:24:32

- reply

No web client for now, also it’s impossible to have the same security level in web browser

2023-06-15 19:28:04

SimpleX Chat v5.1.3 released:
- Fixed video calls on iOS!
- Much faster group deletion.
- New preset SMP servers - add them in server settings!
- Many small fixes.

2023-06-14 15:03:26

Incident with iOS notifications delivery (resolved)
During the server migration to a larger instance the certification authority file was not migrated and server failed to connect to Apple servers.
Our testing process was not properly followed during the migration, as the result notifications were not delivered for ~24 hours.
Really sorry for the inconvenience - we know how to improve it, this is not the level of service we want to operate. We are fully aware that some of you really depend on the service, however early stage it is, and it will be at a different level very soon.

2023-05-29 23:02:49

- reply

Thank you. Whenever users can’t receive messages I can’t think of anything until it’s fixed. The team feels this pain too. We do try to fix issue as soon as possible, and in general last week incident we see as not acceptable even for beta releases, leave alone production. So we’re improving the test coverage now, and we will prioritise delivery receipts for 5.2 or 5.3 - that would reduce users’ and our stress a lot.
The cadence of f-droid is indeed a pain, there are two problems:
1) the time it takes to build the app. Because there is no Nix cache that holds GHC cross compiler and the stack it has to be compiled every time we build the app - it takes ~12 hours. On our CI the build takes either 20-60 min, depending on the scope of changes. We need to figure out how to use Nix cache, but the problem is that it’s not a priority when exactly two apps in f-droid use Nix…
2) the time it takes to update the whole F-Droid repo - I don’t fully understand the design, so not sure if it can be improved to have f-droid updated per app…
Users can of course switch to another source, but the app would be signed with another key (as it’s not a solved problem doing reproducible builds with GHC), which means they would have to export db, reinstall the app, and import again.
I don’t have a simple solution here…

2023-05-27 21:34:32

SimpleX Chat v5.1.2 fixing message reception bug is released to GutHub, our F-Droid and on App Store. Play Store release is in review, and the main F-Droid will be updated in a couple of days.
Thanks for the patience and sorry for the trouble!

2023-05-27 16:03:11

Message delivery issue in v5.1, possible temporary workarounds until we fix.
We just confirmed that there is some message delivery bug in v5.1, working to diagnose the root cause and to fix it.
The symptom is that the messages are stopped being received by some contacts (and group members), and some users say it happens in 2 days after establishing the connection.
Possible temporary workarounds, until we fix (either of these works):
- downgrade the app to 5.0 (you will be asked to confirm downgrade on start, and reactions will be lost, but it will work) - all stuck messages are delivered. After upgrading back to v5.1 disrupted contacts continue to work - difficult to say for how long. It would be great if anybody could confirm that this worked for you, as we only could confirm it on one device so far.
- create a new connection with the same contact - it seems to work for 2 days.
Certainly do not install v5.1 if you have a choice, looking if it's possible to temporarily pull v5.1 from app stores.
Sorry for the inconvenience and thanks for all your support!

2023-05-27 08:21:45

- reply

Yes, that’s what we (= Moritz:) did to integrate the code we had working in the terminal into mobile apps in early 2022, as we also didn’t want to re-write, and now there is much more code to rewrite…
Haskell is very performant, and also very effective for concurrent programming (better than anything I used, including Erlang-based Elixir), and there is lots of potential to improve the performance with some code tweaks.
The binary size isn’t great. We will have to solve this problem eventually.
Compilation for web is getting stable in 9.6 though, so web client will become possible too (with some security compromises).
Android amrv7a support was done this year (Moritz did lots of fixes in GHC) - quite non trivial.

2023-05-26 21:16:06

- reply

iOS

2023-05-26 21:15:50

- reply

This is a classic UX fail, which I got trapped into even though I should now better not to tap again :))) We still have the same in “change address” button - everybody who finds it, taps 3 times (it seems a magic number we try something before concluding it’s broken), with a good probability disrupting the connection 🤦‍♂️

2023-05-26 21:08:59

- reply

Yes. I suspect that I tapped post, nothing happened, so I tapped it again, and then again :). We had it too in SimpleX Chat. Solved by blocking the button while “post”
Is processed.

2023-05-26 21:07:14

- reply

It was sent three times 🤦‍♂️

2023-05-26 21:06:25

- reply

We don’t build the product for anonymity (although it can provide it), we build it for privacy of ordinary users from the operator and any observers.
Privacy means not just secrecy of my messages, by definition in includes the privacy of my associations.
I don’t need to hide my identity from people I talk to (=anonymity). But I absolutely don’t want my communication service provider observing my connections. Why is it so? Because apparently as this information is not private, and shared publicly, it can be further shared with the third parties - especially in the US.
And a lot of third parties having visibility of this connection graph doesn’t just create risks for freedom in oppressive regimes. It has a direct impact on the prices we pay online - targeted prices, aka price discrimination, becomes the norm for a growing number of online retailers. And if you think that it results in wealthier people paying more you are wrong - usually it works in the opposite direction, known as “poverty premium”.
So privacy doesn’t seem something only a niche market needs - it seems like something absolutely everybody needs, and that Signal, WhatsApp, Session etc. simply cannot provide whether they use phone numbers or not - any form of identification is good enough to reconstruct connection graph via correlation of communication patters with the existing public networks - it won’t be flawless but it will be precise enough for targeted pricing. So it’s just have to stop, and privacy of our associations from communication providers should become a norm, not an exception.

2023-05-26 21:06:23

- reply

2023-05-26 21:06:21

- reply

2023-05-26 07:01:18

- reply

Let’s talk about it and brainstorm! :)

2023-05-26 07:00:28

- reply

Thanks for such a positive comment #[1] . User traffic almost tripled yesterday from your tweet, some people thought it’s your creation :)
Lots of work to do to improve it. Exciting times :)

2023-05-25 15:02:15

- reply

Interesting idea. I think redundancy support in the client is needed to make it reliable/useful… Re any queue - any sequential transport, e.g. there is implementation that wraps SMP into WebSocket frames, we just don’t use it yet, and it’s easy to wrap in any block transport - SMP uses fixed size blocks.
Happy to brainstorm it further.

2023-05-06 14:26:05

Talking at at RightsCon Costa Rica (June 5-8, 2023) about SimpleX Chat – the first messaging platform without user IDs – protecting participant identities!
Join me at the world's leading summit on human rights in the digital age.
https://www.rightscon.org/participate/

2023-04-26 07:39:27

Poll: Message expiration on SMP relays
When the messages are delivered they are instantly removed from the relay memory. If the messages are not delivered (e.g., the recipient never connects to the relay to receive the messages) they are kept up to 30 days.
Please vote in https://www.reddit.com/r/SimpleXChat/comments/12z9aey/poll_message_expiration_on_smp_relays/ or in https://mastodon.social/@simplex/110263817123280267
And looking forward for polls here :)

2023-04-25 19:54:32

Help us decide what's next in SimpleX Chat!
Please vote on the issues on the board in GitHub in "Prioritising" column (put thumbs up on exactly one of them, you'll need an account):
https://github.com/orgs/simplex-chat/projects/3/views/1
Thank you!

2023-04-22 18:39:19

SimpleX Chat v5.0 is released:
- send videos and files up to 1gb via fast and secure XFTP relays!
- passcode as an alternative to system authentication.
- support for IPv6 relay addresses.
- configurable SOCKS proxy in Android app.
We also added Polish interface language – thanks to the users!
Get the apps via the links here: https://github.com/simplex-chat/simplex-chat#readme
Read more details and also about SimpleX Chat vision and funding in this post: https://simplex.chat/blog/20230422-simplex-chat-vision-funding-v5-videos-files-passcode.html
#privacy #messenger

2023-04-10 19:41:53

The experimental support for SimpleX File Transfer Protocol to send videos and large files up to 1gb is now available!
See this post about XFTP: https://simplex.chat/blog/20230301-simplex-file-transfer-protocol.html
On my fast internet it takes 3 sec to send 25mb and 2 min to send 1gb.
Please note: currently the network settings are not used for sending files - it will be improved in the next version.
This version also fixes many bugs, in particular the bugs specific to ARMv7a 32bit devices.
#privacy #security #messenger

2023-03-30 18:09:44

Hello!