

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.


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


Wero is based on SEPA, the Single Euro Payments Area, which only covers countries in Europe. In order to use Wero, your bank (in a SEPA country) has to explicitly support it (not all of them do; I have checking accounts with 3 banks and only one of them has announced plans to support it). And to use it when shopping, the merchant also has to support it.
Apparently there are plans to link European and Canadian payment systems. But no way the US will do this.


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.
Oh, apparently it had to be revised and will take more time to be available. https://www.certkit.io/blog/whats-taking-dns-persist-01-so-long