Update link to doc page about entr HOT 3 CLOSED

I was referring to the https://eradman.com/entrproject/ link which users will be going to for documentation. Even though there is no sensitive information to protect or any incentive for malicious actors to modify the documentation while in transit, HTTPS will provide the following:

• higher SEO ranking on Google
• confidentiality for user as traffic sniffing won't reveal exact url
• data integrity as MITM can't change the data

Since you already have a Lets Encrypt cert and https already enabled, I think it is just good practice to serve the documentation over https.

Anyway, I want to thank you for writing entr. I find it a very useful utility. I stumbled upon the http link when updating entr documentation on tldr. I raised a PR here

from entr.

Thanks for the explanation. I had not heard of the tldr project before. Thanks for your contribution!

I enabled HTTPS because people ask for it, but if it were not for Lets Encrypt I wouldn't do it. (As an aside, it's amazing that they have don't with such a small budget.) My view is that the entire chain of trust and the mechanism for renewing certificates is brittle, and I don't trust it to keep running if I am hit by a bus.

Closing, but I'll keep these points in mind.

from entr.

HTTPS is necessary in some cases, but isn't one of them. Is source code the concern? As far as I know, package builds rely on checksums, not encrypted transport.

from entr.