

How is Rust not problematic? Cargo has the same risks involved afaik


How is Rust not problematic? Cargo has the same risks involved afaik
Have you tried Stump?
I’m wondering how this compares and contrasts against something like the Mecha Comet. There seems to be a lot of similarities.


It could. The removal of “transparency” indicates to me that the clients might also stop being open source at some point and Vaultwarden doesn’t have its own clients.
Makes sense. Good luck. I’m trying to get a OnePlus 6T
You’re on an S23FE. As a fellow Samsung user, I think you’re pretty trapped.


Damn, WSJ really succeeded in their campaign


Are you talking about desktop use?
Yeah, all the Proton hate we’re seeing are overreactions. But life is easier when you can see everything as black and white when things are actually more nuanced.


Ooh, that’s promising. I guess I’ll try it once it matures a bit more then. Thanks for going through the trouble of reviewing it!


If you test it, can you let me know how it compares to Findroid?
Thanks for the explanation! I’ll try BetterBird
What is especially good about Betterbird in your opinion?


Use it but don’t rely on it. Celeste uses rclone. The rclone support was temporarily disabled from Proton’s end a while back and also, the rclone backend still has a bunch of bugs and the developer seems to have gone missing


I don’t think you understand how AIs work


One key aspect that you seem to be missing is that Proton encrypts every mail, including those sent by or sent to unencrypted providers using your pgp key before storing them on the server. This isn’t a case scenario that can be handled without using a bridge. Thunderbird or any other mail client won’t know how to handle that.
What you described only solves the end-to-end encryption portion of the problem Proton is trying to solve. Not zero access.
Yes, mail headers are unencrypted. They never claim otherwise and neither did I. If it were encrypted, it wouldn’t be interoperable, which is something you want it to be as well right? I’ve always been talking about the mail content itself. Unencrypted mail headers don’t make it “not zero access”.
I feel like you’re just not the target audience for Proton. I just use Proton because I’m fine with the web UI and Proton Unlimited is mostly good value for me. I do also pay for Purelymail as i have a few domains and they’ve been wonderful too.


The bridge does the decryption using credentials you give it locally. Sorry for mentioning “auth”. I should have mentioned encryption instead.
Regarding the rest, it comes down to the zero access mailbox encryption’s implementation details. In all described scenarios, you’re not really using your master password as the “key” for your mailbox. But in proton’s and similar services’ case like Tuta, this is true. Any “zero access” service provider offering IMAP access without a bridge is simply lying to you as IMAP (the protocol itself) requires server-side decryption of the content, even if SMTP doesn’t. (Btw, SMTP is really an artificial limitation. Just not IMAP. If they give you smtp access, it wouldn’t send encrypted mails unless specifically configured to do so but would otherwise be the same.)
What you described is encryption at rest, but not zero access encryption (which is what Purelymail does btw).
Whether all this is needed and all depends on your threat model. I think most tech-savvy folks would be happy with something like Purelymail or Migadu tbh…
Looks interesting