Jeff Waugh

I just started using acme, discovered renewal wasn't implemented, but then found this lovely pull request! What are the chances of a merge and release before my next renewal? 😉

Are these changes likely to land?

Hmm, that's odd, `acme cert` doesn't seem to renew as I'd expect. - `acme whoami` returns sensible information - `acme cert waugh.id.au -dns waugh.id.au www.waugh.id.au mail.waugh.id.au` responds with: `waugh.id.au: acme:...

Oh, *without* `-dns`. I thought I should tell it how it had been authorised. Unfortunately, that didn't seem to work either: ``` $ ls .config/acme/waugh.id.au.* -rw-r--r-- 1 jdub jdub 3.2K...

Yeah, the new authorisation theory makes sense. D'oh! I'll have to wait for the next renewal period to try it the right way. Thanks for your help! (I do think...

Three months later… unfortunately: ``` jdub@node:~$ acme cert waugh.id.au www.waugh.id.au mail.waugh.id.au waugh.id.au: acme: identifier authorization failed ```

Yeah – I have a destination that can't really handle structure (objects), but is totally fine with arrays of primitives. (I'd even argue that this is a nicer default, because...

Old `go get` only checks `go.mod` on the default branch. If the `module` line contains the version it expects, it will check out and use the default branch as if...

It's not a broken of Go, it's any (relatively recent) version of Go using non-modules resolution. (As you can see from the commit, they backported the change all the way...

I have come up with an alternative solution for non-modules users: use `gopkg.in/vmihailenco/msgpack.v4` as your import path instead, c.f. honeycombio/libhoney-go#79.