The whole point of associating an encryption key with your email address on a public keyserver is so that you get encrypted mail!
And PGP/GPG keys are used for more than just email, so just because you have a key on a keyserver doesn't necessarily mean you want your emails encrypted with it.
2. Keys have types. These keys were marked for use for encryption. You can upload keys for signing only if you wanted to.
I'm not surprised; these people think a lot more about these sort of things than I do.
One possible addition might be that maybe you could specify whether people should use the key to encrypt whenever possible, or only when security is absolutely vital. That's a setting that could pass the decision to encrypt to the sender (if clients support this).
You opt in by having an email address and by having a published key associated with that email address.
- It is necessary to upload a gpg public key to a keyserver in order to publish packages in some public repositories, such as maven central, or one of several linux distribution repositories
- They needed it in order to send or receive email from an entity that required using PGP, but don't use it normally.
- They tried using PGP for email, found out how painful it was to use, then decided it wasn't worth the effort and stopped.
I'm not familiar with any of this at all, but this sounds to me exactly how it should work: upload and verify the key, so people know they can use that key to send you encrypted email.
The thing protonmail might consider is to put an unencrypted standard message in the body that the message is encrypted because the recipient has published a key, so the recipient understands that it's encrypted and why it's encrypted.