There is no problem with being located in sf but I would take issue with the idea its a job that 'requires' one to be located in sf or have access to the absout

There is no problem with being located in sf but I would take issue with the idea its a job that 'requires' one to be located in sf or have access to the absoute 'highest quality' of engineers. On the contrary there is a risk of adding complexity where none is needed because super high quality talent requires super high quality work and if the work of generating certs is not challenging enough, complexity is created, like Acme. I am not sure why generating a cert is so involved with letsencrypt. Does Dns validation, file validation or email validation require a new standard. Perhaps a simple rest api and web frontend would be better. Here is my domainname, my cert request and a file on my server or dns entry to verify, now can I have a cert please? This is the process. Why does it need a client, and one that can automatically update certs!! and an elaborate new standard? There is no way I am running this on a live server, so the automation is then moot. I would rather pay $20-40 a year than babysit my ssl every 90 days, and this is for a wildcard. The kind of folks who automate things spend hundreds of dollars a month on aws or gce, and willingly pay 10 times more for bandwidth than they would at do or vultr. Is $20 a year or $2 a month per wildcard domain in this context really an issue? So who does the automation target and benefit? For others a manual process would have been more accesible, there are tons of others things to do with one's time, le is automated but that is one more thing to monitor and that can go wrong. I can't help feeling the whole cert generation process could be simplified and artificial restrictions around 90 days and wildcards re-evaluated. That would be valuable to users, contribute to make running things simpler and money well spent.