namedpipe

The best mitigation strategy here is to engage your vendors with private contracts instead of depending on generic terms of service (ToS) alone.

Every company I've worked with has negotiated separate agreements with providers to reduce risk. Including contracts with both AWS and Azure.

If your business gets to a certain size and you are still on the generic ToS and paying by credit card you have a big risk on your hands. You could be terminated at any point.

With a private contract you can negotiate things like a termination notice. You can put in place a grace period before things are shut off. You can implement dispute procedures that are unique to your business needs so that when you and the vendor disagree it doesn't immediately disrupt your business.

None of this is easy. But if your business absolutely depends on public cloud hosting you'd be stupid not to call up your vendor and negotiate.

If you are unwilling to do that, then you need to make sure you diversify your cloud. It's much less likely that two competing cloud vendors would shut you off at exactly the same time.

The "Curator's Code" is an attempt to make things better on the web for sites that aggregate and curate content. It's definitely not perfect but Marco's complaint is pointless. His complaint amounts to "Sure, I try to drive the speed limit. BUT THERE ARE ALREADY SPEEDERS OUT THERE!!! So screw the speed limit."

Despite his throw-out-the-baby-and-bathwater approach, the discussion is worth having instead of dismissing the idea wholesale.

The NYT article he refers to covers the modest goals quite well. It's not a panacea that is just about using "via" and "hat tip" correctly. It's about making attribution clearer and putting in place some guidelines about attributing things to the original source.