bloom-legacy VS backbone-python

Aside from library. Bloom was written in Go then ported to Rust. Maybe you can get some inspirations!

It's only impractical if you actually require end users to understand and apply all of these technologies. It's a lot more tractable if they're abstracted away.

The fact is that developers very (very) rarely have to interface directly with TLS or the Signal protocol, yet billions of non-technical users implicitly use them in our browsers and via Signal or WhatsApp.

In my view, the challenge in the adoption of secure/private-by-design tech is the simplicity and usability of the interfaces and the capabilities these tools provide.

We need secure tools to compete on capability in order to garner mass usage. Without (significant) feature superiority there's little reason for users to make the switch. I'm actively trying to solve some of these problems at Backbone [0]; aiming to build a usable, secure experience for end users and a simple, robust end-to-end-encryption interface for developers.

[0] https://backbone.dev/

> Data in our cloud is end to end encrypted so your credentials are never exposed to anyone but you.

A few comments:

1. You might want to avoid calling this zero-knowledge. While your docs suggest some use of E2EE, there seems to be a significant amount of metadata that remains both unencrypted and unauthenticated.

2. Having read your white paper, it appears your E2EE setup is vulnerable to various forms of forgery. In a simple case, an attacker that has compromised your infrastructure can easily substitute the credentials of arbitrary users in a way that is NOT tamper-evident.

3. There seems to be no post-compromise security. If your user private key is compromised (e.g. extracted from the extension's local storage), there seems to be no way to reset it.

4. The recovery flow is questionable. Do you really want to store critical cryptographic material in plaintext and in a third-party cloud?

When rolling out E2EE from scratch, it's very easy to give rise to issues like #2. At Backbone[1], we've built a framework for building end-to-end encrypted applications with building blocks designed to preserve confidentiality, integrity and nonrepudiatiability under a strict threat model.

Feel free to reach out if you might like to discuss how we're solving issues the above.

[1] https://backbone.dev/

Backbone is designed to reduce the need to trust third parties — it operates under a strict threat model, providing confidentiality, integrity and nonrepudiatiability even under the assumption that Backbone itself is pwned. We’re dedicated to operating transparently, leading us to build our open-source client on top of libsodium.