> It outlines an enrollment process by which I would signal to a WKD service that I have a key that I want to enroll into the process. The only problem is I nev

> It outlines an enrollment process by which I would signal to a WKD service that I have a key that I want to enroll into the process. The only problem is I never did that, or at least certainly can't remember doing that. I'm certainly not hosting a page with any key verification stuff. The post includes the above statement that this person never took the steps required for following the standard Proton states they are following. This communicates to me that Proton is not following any standard. This is something publicly visible and on a grander level fairly simple to discover compared to other issues related to E2E encryption. I don't trust Proton or really any organization to manage E2E for email, and among the biggest issues is that email just seems like the wrong tool for the job. Another issue I have with encrypted email is what to do about spam. If the server can't inspect the contents of the message, the probability of a "success" on the part of the spammer is significantly higher. Public keys can be published for addresses that have very high limitations (e.g., 1KB size limit, strict mail policy standards enforcement, whitelists, etc.). How Proton plans to deal with this an average person, I have no idea, but I imagine a lot of people will be scammed in their discovery process.