… well, I kinda like ACME. It's one of the few actually RESTful protocols out there, so it is quite straight-forward to navigate. The media types are well speci

… well, I kinda like ACME. It's one of the few actually RESTful protocols out there, so it is quite straight-forward to navigate. The media types are well specified compared to some HTTP APIs.¹ certbot (presuming that's the thing she's talking about the code quality of) can be a bit hard to interface with if you stray outside the default set of use cases, IMO. I don't know why it would be shelling out to openssl, though, when Python has cryptography, which is IMO one of the most pleasant libraries to work with if you need to build X.509 certs or CSRs etc. as it represents those things directly and plainly, and doesn't get in the way. … if the issuance limits on some random third party CA are a problem, … Let's Encrypt has generous limits. ¹my last experience was Github's API … which will happily have an attribute that's an enum, but not tell you what the variants are. Like … seriously? Azure's docs/data structs permit representing many illegal values easily, and don't document, e.g., when two things are mutually exclusive. The lack of REST in Azure's API means what could have easily been just a single attribute holding a URL gets broken out into 5 different attributes strewn across 3 different structs, a VM's initial image, I am looking at you.