Live data from Hacker News

Google failed to warn 10M of Turkey earthquake

bbc.com

21–30 of 30 posts

Re: Google failed to warn 10M of Turkey earthquake

#21
post #12
post #2

Can't say I like the tone of this article. Google is trying to do something good it is not in any way obligated to do. Painting this like they were responsible just encourages people not to try such things.

Google(and others) marketed these alerts as features of their product, as one of the reasons to upgrade a smartphone from a feature phone. Median price of phone went from couple of hundred in Nokia era to a thousand or more today, justified by all the features including this one , meaning they certainly made money of providing all these value added services. It’s no different from a fire or burglar alarm . Yes they a…

I had no idea.

https://blog.google/products/android/earthquake-detection-an...

Completely changed my perspective

Re: Google failed to warn 10M of Turkey earthquake

#24
post #12
post #2

Can't say I like the tone of this article. Google is trying to do something good it is not in any way obligated to do. Painting this like they were responsible just encourages people not to try such things.

Google(and others) marketed these alerts as features of their product, as one of the reasons to upgrade a smartphone from a feature phone. Median price of phone went from couple of hundred in Nokia era to a thousand or more today, justified by all the features including this one , meaning they certainly made money of providing all these value added services. It’s no different from a fire or burglar alarm . Yes they a…

True. That's why Apple does not attempt to have earthquake detection on China. https://iphonewired.com/news/684225/

Re: Google failed to warn 10M of Turkey earthquake

#25
I don't like this part:

"...sets off a loud alarm on a user's phone - overriding a Do Not Disturb setting - and covering their screen"

I'm already at war with my smartphone to make all the alerts stop buzzing and squelch the intrusive notifications (e.g. apps that think they're important, amber alerts that seem in most cases to be accidentally blanketed due to user-error, test alerts, false alarms, etc).

I'm fine if Google wants to experiment with it, and I even applaud the effort, but at the end of the day I want control of my device, thank you very much. That means this sort of thing should be opt-in, not foisted upon on me.

Re: Google failed to warn 10M of Turkey earthquake

#26
post #12

Earlier quoted context omitted.

Google(and others) marketed these alerts as features of their product, as one of the reasons to upgrade a smartphone from a feature phone. Median price of phone went from couple of hundred in Nokia era to a thousand or more today, justified by all the features including this one , meaning they certainly made money of providing all these value added services. It’s no different from a fire or burglar alarm . Yes they a…

I had no idea. https://blog.google/products/android/earthquake-detection-an... Completely changed my perspective

I think there's a reason you had no idea, and the reason is that Google didn't even try to use this for marketing. They also shipped it to existing phones, they didn't market it as a differentiating feature of new ones.

Re: Google failed to warn 10M of Turkey earthquake

#27
Science article: https://www.science.org/doi/10.1126/science.ads4779

IMO this is the most interesting part: Postevent analysis revealed several limitations to the detection algorithms that have since been improved. First, the duration of monitoring has increased. At the time of the event, the algorithm only allowed updates to earthquake parameters for 10 s after first detection. The number of allowed updates was limited because there was a trade-off between more updates providing additional information for larger earthquakes and more updates introducing outlying single-epic data causing a large overalert. We now allow updates for 30 s and use other checks on the rate of variation in earthquake parameters before updating an alert. Second, there were a large number of noisy phones in the monitoring pool at the time of the Türkiye earthquakes. These high-noise phones triggered late, particularly after the P wave for the M 7.8 event, which had a slow start and complex rupture (31–34). The AEA system is now more selective about which phones are included in the monitoring pool. Individual phones determine their noise level when they become available for monitoring, and this noise level is factored into the detection algorithm. Third, many phones were receiving a BeAware alert and vibrating, which prevented them from triggering on the earthquake ground motion. The alerts now issued by Android EEW no longer cause phones that are detecting to vibrate.

Re: Google failed to warn 10M of Turkey earthquake

#29

Feb 2023 was a while ago, and maybe I just didn’t pay attention at the time to the aftermath, even though I knew it was bad. But I wouldn’t have guessed that over 50,000 people were killed by that earthquake.

real number is way above 100K btw

Re: Google failed to warn 10M of Turkey earthquake

#30
Why doesn’t Google invest in existing solutions?

Why doesn’t Google invest in relay communications that doesn’t rely on a central server, like some on HN have done? One developer here had a really good implementation.

Not sure if Google is reinventing the wheel here?

Post reply on HN