Post B66DWlF3PN4RLIho5Q by pikhq@social.treehouse.systems
 (DIR) More posts by pikhq@social.treehouse.systems
 (DIR) Post #B66BK7Q7RE0WSGj17o by ariadne@social.treehouse.systems
       0 likes, 0 repeats
       
       past me, which, while hating the certificate authority industry, warned about putting all of our eggs in a single basket with let's encrypt, is feeling quite vindicated now 😂
       
 (DIR) Post #B66Bw6l8LP7JPPfYKu by jakllsch@mastodon.sdf.org
       0 likes, 0 repeats
       
       @ariadne what happened?
       
 (DIR) Post #B66C3OGbeLGhjcrYVU by ariadne@social.treehouse.systems
       0 likes, 0 repeats
       
       @jakllsch they apparently had an incident rolling over from their old root to their new root, and issuance was suspended for quite some time today.
       
 (DIR) Post #B66DWlF3PN4RLIho5Q by pikhq@social.treehouse.systems
       0 likes, 0 repeats
       
       @ariadne it's a shame things can be both better than what came before and still have problems
       
 (DIR) Post #B66w5kyqlf8WeOck40 by icing@chaos.social
       0 likes, 0 repeats
       
       @ariadne unless you have an ACME client that can be configured with a fallback ACME provider.(but your point remains valid. the number of ACME CAs seems to be shrinking, LE being just too good)