Hacker News Reader

I'm very well aware, just because there's a history of people messing up doesn't mean the people that mess up shouldn't be held responsible.

I was responding specifically to your "trivial to implement" comment.

Policies to defend against these mistakes are trivial to implement. Testing of configs before deploying, live monitoring of newly deployed configs.

what makes you think it is trivial? how do I generate an accurate prefix list of who should be announcing what, when?

Surely YOU know what YOU should be announcing.