Or just a cronjob that fetches the tls certs and look at the expiration date and then send a mail or X.

So it's even work if you don't have control about the le client.

Exactly this. Don't look at the renewal proces, look at its output. It'll work for all certificate sources and catch other potential errors too (eg the webserver reporting success but not presenting the new certificate)

That'll work too. The idea was to put your own infra in place if you really need that, and it's not very hard to do it, even with completely self-hosted stack.

TLD that are not accessable by everyone are useless.

And no free tls certs like letsencrypt is a huge step back.

Your second sentence’s lack of commas makes it ambiguous. To disagree with one possible interpretation:

Let’s Encrypt is a huge step forward. It provides end-to-end encryption for free, making it extremely abundant.

Fixed:

> And no free tls certs, like letsencrypt, is a huge step back.

They're saying that `.brave` domains are not capable of receiving Let's Encrypt certs. Which is bad.

And its underlying monaco editor.

What should I say with an iPod classic? 3!

why do I need to replace my devices every year?

Dont use soap down there. Water is enough normally.

Dont use soap on my hands. Water is enough normally.

You know that these are different areas with different skin types.

But yes too much soap on hands can also be bad.

I assure you that using soap once a day is not too much for that skin type.

Works On My Ass

Remind me to never toss your salad

Can similar technology be applied to other fields?

Children maybe every human

And systemd

"You do not need to change your passwords or phone numbers as a result of this event."

What a bad name for such app, as it has nothing to do with the actual git.

Funny to ship a web browser for a webserver.

I suppose that's why people run multi socket machines for "home labs".