I am running the nachtalb fork (currently commit 082605c from this morning), which is actively implementing countermeasures, including HTML scraping. Right now, I can open posts. I don’t have to provide an account.

No, there is no fix released for this PHP vulnerability

In my current setup, I think my reverse proxy does not detect certificate updates (done by a different service), and I am just lucky that usually the service restarts because of some update before the old one expires.

Once that is solved, I am tempted to try the six-day expiration.

Did you consider the DNS-PERSIST-01 ACME challenge? You have to add a persistent TXT entry to your DNS, and then you are independent from provider support for renewals.

You have to carry a piece of paper in your wallet that contains a PIN. The piece of paper contains no further information, just a PIN. You decline to answer any questions regarding this piece of paper or your phone’s PIN.

This might not be a good idea, depending on your jurisdiction.