How are we going to provide that evidence? And make sure that evidence is actually true, instead of AI generated? Send them a link to a wiki page that has been mutated by an AI bot updating it? ;-)
Reading a bit it seems to be potentially that the recommendations after the last big quake haven't been followed up properly. So basically stronger building requirements, with government validation was the plan; in reality not done (properly) and "checked" by paid companies.
I understand your point, but CloudFlare generally is very transparent, including root cause analysis and their CTO reaching out directly. It could also be a mistake or not so well thought about instead of assuming bad intentions.
generally lookup the IPs (dig <hostname>) and then attempt a host/whois on that IP. For PushBullet it's hidden by CloudFlare so hard to see easily, you should try and find an exposed endpoint (which they haven't if they've done well).
this one appears to be just global LBs, so a load balancer in AWS/Azure that hits the actual backends over a VPN or something would have worked, but that's just this case
Wouldn't it be an option to basically chain the "events" in the local storage queue with crytographic hashes (kind a like a block chain). You can then fairly easily verify modifications somewhere in the list of events.
It wouldn't make it entirely impossible, but much more complicated.
An autopilot can perform an instrument landing, however this does require some preparation of the flight crew (e.g. setting the right frequencies for ILS, reducing airspeed, deploy landing-gear, flaps, apply brakes + thrust reversers).
So simply guiding it to the nearest (suitable) airport would not make a big difference.
Located in The Netherlands, but mainly doing business with US/UK. I go on one holiday for an extend period (~ 14 days) and a couple (~ 2) of short 3-5 day trips.