| 4 Jul 2025 |
 Theuni | interestingly the doc is a bit outdated already, though ... | 10:30:34 |
 emily | well that is just reference material for ACME client developers from >half a decade ago | 11:09:15 |
| emily | most of it is still good, it's just OCSP stapling went away and ARI changed the renewal timing landscape a bit and so on | 11:09:40 |
| Theuni | yup | 12:12:06 |
| Theuni | as an outsider that just makes it hard to estimate which parts. i did understand it that way: ocsp and ari having changed. | 12:12:30 |
| emily | well, it's only really relevant for client developers, or comparing existing implementations but then you basically have to read code to see what they get right in some cases | 12:28:14 |
| emily | the fundamental issue with lego is that things like ARI don't fit great into a cron job type format if you want the best implementation of them | 12:29:00 |
| emily | and all the hashing etc. we have to do around it is just working around the model not being quite right | 12:29:20 |
| emily | (the end result does work well though at least at medium scale, it just takes a whole bunch of complexity to make the square peg fit the round hole) | 12:29:44 |
| Theuni | yup | 12:34:38 |
| Theuni | do you know what the list of supported DNS-01 provider APIs looks like in acmez compared to lego? | 12:35:05 |
| Theuni | so far that's been the reason why I decided to stick with lego for now. | 12:35:14 |
| Theuni | I got a green bar on the refactoring I demoed above. Trying to get the other tests clean again now. On disk formats are all compatible ... \o/ | 12:35:38 |
| Theuni | I need to explicitly praise the test coverage in the acme module. This helps a lot to find little glitches that I didn't properly catch. | 13:21:03 |
| Theuni | 🎉 | 13:21:06 |
