llmhm, i kinda am tempted to fork instant-acme crate
anville uses it, however it certainly has annoyances that i hate, such as AccountCredentials not supporting Clone (upstream rejected it for questionable reasons: github.com/djc/instant-acme/issues/61), and lack of policy banning llm usage (and considering the author of this crate overall is supportive of llms,,, they outright added a policy to quinn package saying "Using AI (LLMs) as tools for coding is welcome.")
my problem is, what should i call the fork? sweet-acme?
llmon sidenote, speaking of quinn, anville uses it
i don't exactly like that, it has slop commits (five of them), but ugh, the only alternatives are outright by ai companies (amazon, mozilla, tencent), so,,, well,,,
i don't have energy to like fork everything, and quinn is too big of a codebase for me
the same also applies to rustls for that matter (which is also by the same person who is working on instant-acme), which has the exact same ai policy as quinn, but like, what else i'm going to use? openssl? slopscan.ava.pet/repo/https://github.com/openssl/openssl
i hate the fact that there is no good option, quinn and rustls i believe are least bad for the functionality i need them for
1
1