mobilecoin VS session-desktop

On this day last month, v.4.1.0 of the protocol was released, enabling atomic swaps on the MobileCoin blockchain.

There is a distinction between "begin wrong" and "being so absolutely wrong that making a statement transparently communicates how small one's understanding is". The second applies here. He is absolutely wrong here. SGX is one aspect that has some beneficial contribution to the overall ideas in MobileCoin. It is not at all an elementary part. You can read here in detail what happens if SGX would be totally pwned: https://github.com/mobilecoinfoundation/mobilecoin/blob/master/fog-threat-model-2.1.0.md

General thoughts for a MobileCoin Fog Threat Model can be found here: https://github.com/mobilecoinfoundation/mobilecoin/blob/master/fog-threat-model-2.1.0.md E.g. you find a summary of what an 'SGX-compromising Adversary with root on Fog Infrastructure' can achieve.

Since you're passionate about the topic, it might make sense to read a bit about why Signal chose MobileCoin as well as MobileCoin's design goals.

You are welcome to audit the code yourself.

Link here: https://github.com/mobilecoinfoundation/mobilecoin#consensus

https://github.com/oxen-io/session-android https://github.com/oxen-io/session-desktop https://github.com/oxen-io/session-ios

This is the correct place to raise feature requests and bug reports: https://github.com/oxen-io/session-desktop/issues

We're at 1.10.8. Please update: https://github.com/oxen-io/session-desktop/releases

Session's reasoning seems much more... cagey. Telling people to recreate their identities themselves sounds a little like the Threema stopgap solution, but it's much sloppier (I can't imagine end users WANT to recreate their account and communicate this to all their contacts via a third party). They're talking about implementing this eventually, but the ticket for doing so was closed right after saying this.

Session F-Droid (version 1.15.4): Encrypted private messenger

Or Briar, Session, Tox, Element/Matrix, Jami...