BarbequedYeti t1_irsspmy wrote
Add geo-fenching around amusement parks to void all those by default, then you just have to deal with the traveling type fairs. You could probably even get a database with their setup addresses and geofence those off as well. It would take a bit of backend work, but would handle 99% of the false positives without user intervention.
MotelMonMurderMadnes t1_irw0phm wrote
Geofence is not the correct solution to this problem. It’s a bandaid to handle one failure case when the underlying system is broken. What happens when there’s a standalone roller coaster that isn’t in an amusement park? What happens when you crash your car on the outskirts of an amusement park?
Crash detection shouldn’t be going off for anything but a car crash. If you have to think about geofencing areas where phones are experiencing unusual forces, something is wrong with the feature.
Viewing a single comment thread. View all comments