3 ms·
Regardless of the strengths of this, I can't read this slop. A third of the way in, and: > Instead of expecting the client to know the server's public key in a
by oasisbob 1y ago
Regardless of the strengths of this, I can't read this slop. A third of the way in, and:
> Instead of expecting the client to know the server's public key in advance, the server might just send its public key during the TLS handshake. But how does the client know that the public key actually belongs to the server? This is the job of a certificate.
Are you kidding me? You don't know your audience on an article at the nexus of certificate transparency and post-quantum cryptography well-enough to understand that this introduction to PKI isn't required?
Know your audience. Turning over your voice to an AI doesn't do that for you. It will waste everyone's time on thousands of words of vapid nonsense.
- jgrahamc 1y agoWhen I was the editor in chief of the Cloudflare blog we had a very, very strong mission to "educate, educate, educate" our readers. That often meant including details that someone versed in the field would skip over or find too basic. After all, we were writing for a general technical audience interested in learning about a topic. So, its natural that some readers would find parts over-explanatory but the hope was that they could read past those bits and the less educated reader would come away having learnt something new.
- oasisbob 11mo agoI can understand wanting to give background. There's still a place where it's too long and verbose. The pacing and verbosity makes me really doubt this underwent extensive editing.
- flufluflufluffy 1y agoI for one welcomed the refresher as I don’t often deal with the intricacies of the public key infrastructure, even though yes I am a programmer and make websites.