Surely a company that in their own docs suggests using "dangerouslySetInnerHTML" knows how important it is to be transparent about their downtime? This is shocking, thanks for sharing!
1) ButterCMS should have informed their customers/users about what they missed.
2) The way the issue was introduced could have led to a significant supply chain vulnerability.
3) I haven't found any analysis or communication from ButterCMS addressing the issue with their customers.
4) There’s still no downtime indicator on their website.
1) ButterCMS should have informed their customers/users about what they missed. 2) The way the issue was introduced could have led to a significant supply chain vulnerability. 3) I haven't found any analysis or communication from ButterCMS addressing the issue with their customers. 4) There’s still no downtime indicator on their website.