The only thing I miss is the official API for the scheduled sending feature.
That's the only thing I would open the webpage app to do.
119 karma · joined November 2, 2022
The only thing I miss is the official API for the scheduled sending feature.
That's the only thing I would open the webpage app to do.
EDIT: thanks for people clarifying that pinning is done by Apps and not by IOS.
Fortunately, someone has created them!
Because I live in Emacs!
Use a low entropy things (I guess user's password would be not larger than 20 characters nowadays even using password managers) to encrypt a high entropy strings (PGP key).
Looks pretty weird to me.
Although they are open-source and can be scrutinized by anybody, it does not means that's what is run on the server side.
(Just say they have the capability; no accusation)
So at the end of the day, the question is whether you trust Proton or not. Encryption might not help in that case.
But for PGP? You should treat it seriously, considering your target customers.
If they cannot handle basic things like PGP correctly, how should I trust other part of their software. Especially they are a "Privacy-first" company.
"Privacy" becomes a marketing term nowadays.
Proton makes it hard for open-source software developer to send patches and they don't care.
https://git-send-email.io/#step-2
Some quote from it.
> Be advised that Protonmail is generally known to be a pretty bad email host. They will munge up your outgoing emails and your patches may fail to apply when received by the other end. Not to mention their mistreatment of open source and false promises of security! You should consider a different mail provider.
Glad that I jumped out the ship only after one week so I can get full refund lol
If they decide to use third party libraries, that's their responsibility to review those libraries and include them to their code base.
Not "it's not my fault; it's others fault"
I don't get it. Bridge is open source does not imply it should relies upon open-source components.
> Addressing this issue at the source requires replacing the core IMAP library.
Why building an IMAP library from scratch instead of fixing/forking go-imap? Even a temporary fix to go-imap when you are developing gluon? Another repetitive work which does not guarantee the mentioned issues will be resolved completely.
https://fastmail.blog/advanced/why-we-dont-offer-pgp/
I don't believe the encryption/key management from a company.
Besides, FastMail exists before Gmail and the people in FastMail are active standard protocol developers like IMAP and recently JMAP (a modern mail protocol will replace SMTP/IMAP, FastMail as a reference implementation), which is good because at least I know they understand the protocol and implement it by themselves.
However, bridge is a paid feature used to attract more users.
Also, I don't understand your point about e2ee.
Bridge to proton server is also e2ee.
The mail interface is just a implementation of e2ee in browser, isn't it?