At least the error goes away immediately, for everyone, once you fix the cert.

.net seems to serve DS records with at least 18 hours TTL. so worst case it takes your monitoring up 18 hours to notice your record was broken, and then another 18 hours before your fixed record is server everywhere.

> but it is not the operational hazard it’s made out to be

Until you flip that DNSSEC toggle

Poll takes a timeout parameter. ‘Not polling’ is just a really long timeout

Don't forget about Bootcamp for the (soon) obsolete Intels .

With a debloated Windows 10 (which we're not going to connect to the internet anyway) they can live on for older games.

I think the 'K-thing' was a big and helpful part of getting early volunteers onboard to build apps for KDE. They really seemed to enjoy rebuilding existing applications into a K-version.

So I guess you just have to live with it, but consider it a way to honor the original contributors who build all the K(DE)-versions of the common apps

Except for infinite loops in JS. Firefox still handles those better.

How so? I don't remember ever having seen issues with this. If anything CSP steers you towards this (instead of inline scripts directly assigning to JS variables)

I thought I knew but it seems that the CSP story is unclear. I couldn't find an authoritative source for either position

CSP blocks execution/inclusion, but since json does not execute and any json mimetype will not do execution there is no problem.

Any CSP-allowed other script can read that application/json script tag and decode it, but it is no different than reading any other data it has access to like any other html element or attribute.

That makes sense, thank you

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)

Can't remove a certificate from the revocation lists until it's expired, leading to boundless growth of those lists.

Risk of private keys/certificates from old backup media being leaked (remembering the adobe password leak...) and then suddenly coming back online and working until someone figures out how to revoke them

They're not an April fool's joke. A 90's linux might have these services enabled by default. I assume they were built to make network debugging slightly less boring