HN user

RobinUS2

57 karma
Posts3
Comments25
View on HN

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).

No Cheating Allowed 11 years ago

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.

BankAPI 12 years ago

Are there any banks actually using this? Or is it more like a suggested spec draft?

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.

Yes definitely. I personally see this as a key ingredient in order to make a project really work. Of course this doesn't work for things like an X-Ray machine, but for a SaaS company like CloudPelican it does.

We currently use it to investigate root-causes of disruptions, track down bugs in the development and staging environment, and most important: monitor our entire infrastructure. This is also in line with our company vision that should allow users to have a single overview on their entire stack of servers, websites and applications. This will reduce time spent on digging through log files, switching between lots of fragmented SaaS tools, et cetera.