I&#x27;d prefer it but one you mention can be done upstream by library developer with secure defaults. Think NaCl. Client-side certificates might come with best practices or checklists that show proper use with optional data on the way. Neither issue requires understanding SSL in common deployments.<p>Note that I say this while agreeing with you that I prefer someone who knows what they&#x27;re doing. Especially as SSL support isn&#x27;t usually at the usability standard I&#x27;m describing. Yet, it&#x27;s not intrinsic to the problem: just crap UX.