[pyre]

Assume for a moment that JS crypto is insecure. If you use a web client with JS crypto to bootstrap acceptance, then the majority of your clients will end up using JS crypto. If the majority of the clients on the 'network' are insecure, then what's really the point?

[mpowers]

A single client isn't weakened by other compromised clients.

If you run a hardened trustworthy client, your own public posts are still verifiable, and private posts meant for you are decodable only by you.

You would just need to make sure to send your private posts only to others that use trustworthy clients. But, because you're sending them a secret message in the first place, you already implicitly trust them.

[e12e]

> You would just need to make sure to send your private posts only to others that use trustworthy clients.

And how would you make sure of that? Is there a field in the user data that says: "419 I speak the protocol, but I don't give security grantees - fool you for talking with me?". Is there planned an easy UI for showing you which of your contacts are part of the secure network, and which ones are backdoors into the network?