SZsztanpet·Jan 8, 2017
No, that is a bad idea, see: https://github.com/rsc/letsencrypt/issues/15#issuecomment-25...
In Let’s Encrypt 2016 in Reviewrsc
letsencrypt
Go2016–2017
rsc / letsencrypt · Archived
letsencrypt
Manage TLS certificates automatically via LetsEncrypt.org
5Distinct people
5Mentions
0Explicit recommenders
455GitHub stars
What to know before exploring
What it is
Manage TLS certificates automatically via LetsEncrypt.org
GitHub
Where it is used
No documented product use has been verified yet.
What people are saying
No recommendation phrase was found in the indexed comments.
No classified warning is attached to this page. Read the discussions before treating silence as approval.
Also in these discussions
No other repository is repeatedly linked in the same discussions.
This week on Hacker News
Nov 7–Nov 14 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/14/2026, 12:54:37 PM UTC.
No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.
Mentions over time
HN mentions by week5 dated mentions
Observed mentions: 2016-09-20 13:57:44 UTC to 2017-01-08 11:16:53 UTC. Weeks start Monday, UTC.
Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.
View mention counts and date ranges
| Period | Start (UTC) | End (exclusive, UTC) | Mentions | Submissions | Comments |
|---|---|---|---|---|---|
| Sep 19 | 2016-09-19 00:00:00 UTC | 2016-09-26 00:00:00 UTC | 2 | 0 | 2 |
| Sep 26 | 2016-09-26 00:00:00 UTC | 2016-10-03 00:00:00 UTC | 0 | 0 | 0 |
| Oct 3 | 2016-10-03 00:00:00 UTC | 2016-10-10 00:00:00 UTC | 0 | 0 | 0 |
| Oct 10 | 2016-10-10 00:00:00 UTC | 2016-10-17 00:00:00 UTC | 1 | 0 | 1 |
| Oct 17 | 2016-10-17 00:00:00 UTC | 2016-10-24 00:00:00 UTC | 0 | 0 | 0 |
| Oct 24 | 2016-10-24 00:00:00 UTC | 2016-10-31 00:00:00 UTC | 0 | 0 | 0 |
| Oct 31 | 2016-10-31 00:00:00 UTC | 2016-11-07 00:00:00 UTC | 0 | 0 | 0 |
| Nov 7 | 2016-11-07 00:00:00 UTC | 2016-11-14 00:00:00 UTC | 0 | 0 | 0 |
| Nov 14 | 2016-11-14 00:00:00 UTC | 2016-11-21 00:00:00 UTC | 0 | 0 | 0 |
| Nov 21 | 2016-11-21 00:00:00 UTC | 2016-11-28 00:00:00 UTC | 0 | 0 | 0 |
| Nov 28 | 2016-11-28 00:00:00 UTC | 2016-12-05 00:00:00 UTC | 0 | 0 | 0 |
| Dec 5 | 2016-12-05 00:00:00 UTC | 2016-12-12 00:00:00 UTC | 0 | 0 | 0 |
| Dec 12 | 2016-12-12 00:00:00 UTC | 2016-12-19 00:00:00 UTC | 0 | 0 | 0 |
| Dec 19 | 2016-12-19 00:00:00 UTC | 2016-12-26 00:00:00 UTC | 0 | 0 | 0 |
| Dec 26 | 2016-12-26 00:00:00 UTC | 2017-01-02 00:00:00 UTC | 0 | 0 | 0 |
| Jan 2 | 2017-01-02 00:00:00 UTC | 2017-01-09 00:00:00 UTC | 2 | 0 | 2 |
What Hacker News says
5 sourcesYou can probably get pretty far with the package written by Russ Cox:
https://github.com/rsc/letsencrypt
In Let’s Encrypt 2016 in ReviewAlso worth mentioning if you want automatic HTTPS is Russ Cox's implementation that works with Go's built in HTTP server:
https://github.com/rsc/letsencrypt
I've used it. It's incredibly easy. It seems he now recommends this more official-looking package:
https://godoc.org/golang.org/x/crypto/acme/autocert
In Caddy – HTTP/2 Web Server with Automatic HTTPSwondering why not using `defer m.mu.Unlock()` right after line 279: https://github.com/rsc/letsencrypt/blob/a18c646c3d0772313b7b...
In GoDoc: package letsencryptHere is the package on RSC's github page: https://github.com/rsc/letsencrypt
In GoDoc: package letsencrypt