Proton stores email subject lines unencrypted to facilitate search, Tuta does search client-side so everything can be completely encrypted. Both have access to unencrypted email when they receive it, so it’s not a huge difference, but given the cost difference, I figured I’d give Tuta a try first.
I don’t think that’s true. They can always do PGP on the client after decrypting the email (so double-encrypt). It’s also not particularly interesting because almost nobody uses PGP. It’s a design decision that I’m not a big fan of, but if they’re legally obligated to maintain my privacy, maybe I’m okay with it. I’ll give it some time and see how that pans out.
OpenPGP is actively supported by dozens of clients, they cannot and do not encrypt subjects, so Proton chose to be compatible with that. I think dismissing cross-compatibility because of a hand wave “nobody uses it” isn’t very productive either.
AFAIK, PGP is only automatically used in emails to other Proton users, you need to do it manually if you want to communicate with someone else with PGP (or use the secure email thing, which does it on Proton’s servers). So the PGP is largely just an implementation detail in how they store it, unless you’re communicating with a lot of other Proton users.
Then again, it’s been a couple years since I used Proton, so I don’t know if things have changed. But since nobody I contact uses Proton or Tuta, it’s irrelevant that Proton uses PGP. If I use PGP, I’d do it myself regardless.
How is it possible to have less data on your than Proton? I’m not aware of anything Proton has which isn’t fundamentally required.
Proton stores email subject lines unencrypted to facilitate search, Tuta does search client-side so everything can be completely encrypted. Both have access to unencrypted email when they receive it, so it’s not a huge difference, but given the cost difference, I figured I’d give Tuta a try first.
i wonder how is the experience of searching between millions of emails client side
Not great. I have a couple hundred or so, and it’s already a bit slow on my phone.
While it does help with search it was required to be compatible with OpenPGP.
I don’t think that’s true. They can always do PGP on the client after decrypting the email (so double-encrypt). It’s also not particularly interesting because almost nobody uses PGP. It’s a design decision that I’m not a big fan of, but if they’re legally obligated to maintain my privacy, maybe I’m okay with it. I’ll give it some time and see how that pans out.
OpenPGP is actively supported by dozens of clients, they cannot and do not encrypt subjects, so Proton chose to be compatible with that. I think dismissing cross-compatibility because of a hand wave “nobody uses it” isn’t very productive either.
AFAIK, PGP is only automatically used in emails to other Proton users, you need to do it manually if you want to communicate with someone else with PGP (or use the secure email thing, which does it on Proton’s servers). So the PGP is largely just an implementation detail in how they store it, unless you’re communicating with a lot of other Proton users.
Then again, it’s been a couple years since I used Proton, so I don’t know if things have changed. But since nobody I contact uses Proton or Tuta, it’s irrelevant that Proton uses PGP. If I use PGP, I’d do it myself regardless.