This action will delete this post on this instance and on all federated instances, and it cannot be undone. Are you certain you want to delete this post?
This action will delete this post on this instance and on all federated instances, and it cannot be undone. Are you certain you want to delete this post?
This action will block this actor and hide all of their past and future posts. Are you certain you want to block this actor?
This action will block this object. Are you certain you want to block this object?
Are you sure you want to delete the OAuth client [Client Name]? This action cannot be undone and will revoke all access tokens for this client.
Are you sure you want to revoke the OAuth token [Token ID]? This action cannot be undone and will immediately revoke access for this token.

this happened today:
https://letsencrypt.org/docs/dst-root-ca-x3-expiration-september-2021/
i don't disagree with their approach at all, but since the change was designed to just work for newer clients, and since older clients are, well, older, and since the change happens on servers but it impacts their clients, it was hard to see this coming until it hit.
in my case the fix was easy—upgrade openssl and rebuild—but reading the threads about this change highlights how disruptive the expiration of a root certificate can be, especially as older clients, which may not be as easy to upgrade, proliferate.