Hacker News Reader

Comment by jng | Hacker News Reader

It would be nice if they included a TL;DR notice at the top saying: “1. If you are a user of let’s encrypt today, this announcement does not imply that you need to do anything at all, and, 2. The main thing is that new certificates are shorter and will take up less bandwidth, plus also safer.” In any case, thanks for the great, free service!

View on HN

I agree, I wish articles like this at the very least summarised their article first before going into a deep technical rabbit hole.

In hindsight, Let's Encrypt is good at backwards compatibility and actionable information. I suppose the target audience is technical.

LE is phrasing out their v1 API, and they email all users of v1 if they recently issued certificates with it. I suppose majority of non technical users of LE don't even visit the web site, apart from downloading the ToS PDF.

Side note: a TLDR at the top is called a BLUF = Bottom Line, Up Front.

https://en.m.wikipedia.org/wiki/BLUF_(communication)

A TLDR is traditionally at the bottom, but there's no rule against putting it at the top.

But no one knows what that means, so you would have to explain the whole thing every time you use it, defeating the purpose of a short acronym.

Say tl;dr in the first sentence and everyone knows what it means.

>But no one knows what that means

... anyone with writing experience in the military knows what that means.

So still relatively few people.

No, you don't label them you just follow good writing practice and put the important details first, details and data second

Interesting, seems pretty similar to an Executive Summary which also would have been very useful here.

Reply on news.ycombinator.com