Stefan Eissing on Nostr: nprofile1q…3jls8 nprofile1q…wz22s nprofile1q…9r3dp It's not "their" ...
nprofile1qy2hwumn8ghj7un9d3shjtnddaehgu3wwp6kyqpqvhxg88ey4h482zvf55edgayzzrfyay0adnvauka9xafqygphwpasy3jls8 (nprofile…jls8) nprofile1qy2hwumn8ghj7un9d3shjtnddaehgu3wwp6kyqpqdgsrtum45we57dd9zs6r9967fxxheqvruy86c2z0gy0ftv4ll6jqxwz22s (nprofile…z22s) nprofile1qy2hwumn8ghj7un9d3shjtnddaehgu3wwp6kyqpq8pp2kt3y3yduxpdkfqgrgvr4t9g2juj8dv37n0ntx89qlr2w68sqa9r3dp (nprofile…r3dp) It's not "their" certificates, they are "your" certificates.
You decide how much in advance you renew your certs to accomodate possible outages. It's not only Lets Encrypt that can fail. It could be your ISP or - gosh - your Comercial Firewall Vendor.
It's not the CA job to mitigate your unique risk setup and obligations.
You decide how much in advance you renew your certs to accomodate possible outages. It's not only Lets Encrypt that can fail. It could be your ISP or - gosh - your Comercial Firewall Vendor.
It's not the CA job to mitigate your unique risk setup and obligations.