Exactly. APPLE is calling in false alarms to 911. APPLE should be fined.Nah. How many people own an iPhone and don't even know this feature exists?
Exactly. APPLE is calling in false alarms to 911. APPLE should be fined.Nah. How many people own an iPhone and don't even know this feature exists?
During skiing in Switzerland I had a fall and watch started to beep asking if I needed help just touched no and that was that. I have no issues with thisIf Apple was billed a token amount, say $50, for every false alert that might help fix it.
Yup and after a while other people who see you just laying there will shout and ask if you’re ok 😂.idk man, sometimes when i crash out i just lay there and look up at the sky 😂
FWIW, many rural areas are understaffed on a per capita basis. Moreover, the distances that must be covered by services are also very large.![]()
Your logical fallacy is burden of proof
You said that the burden of proof lies not with the person making the claim, but with someone else to disprove.yourlogicalfallacyis.com
Oh, and you can tack a straw man on to that, because nobody has claimed that anybody has died yet - just that the false alarms are creating a risk (we do have crystal clear evidence that the false alarms are happening, and it's not rocket science to see that dealing with false calls can cause risky delays).
It's up to the people advocating crash detection to prove that the benefits outweigh the risks - preferably before rolling the product out to millions of users.
A good start would be to compare the number of people dying in car crashes because nobody called the emergency services in time, vs. people who died when the emergency were called promptly but arrived too late (where any sort of false alarm can be a factor). Now, I don't claim to have the data, but thinking about it, the first will be something that happens occasionally out in the sticks where there are no passers-by to raise the alarm, while the majority of fatalities are going to be occurring in heavily populated areas with plenty of eyeballs but overloaded emergency services.
A handful of self-selecting anecdotes where crash detection happened to work spectacularly (which often don't actually prove that people would have died without crash detection) don't really cut it.
Maybe another solution would be a message popping up on the device saying that crash detection is off while they are at a specific location.
Maybe they'll be able to geolocate and say "That car crash is on a ski slope, so nope."
If it makes the call and then were to cancel it, it still goes into 9-1-1 as a hang-up call. The call taker would then be required to call the person back. If the person didn't answer on several attempts back, depending on the situation, if location information was available, a police/fire response might still be sent to the location anyways. This wouldn't necessarily help.
Why would Apple be fined? Apple hasn't broken the law in regards to filing a false report to 911 etc....I'm a tad surprised Apple hasn't been fined for this?
I think I'd like to see them fined—not really punitively, but just to recoup the cost of those 911 calls, which I'm paying for in (very) small part as a taxpayer.
The problem may be that Apple may not have tested in every possible scenario where the watch is being triggered.AI is not so smart it seems …
As a fellow taxpayer I disagree. General public safety outweighs the thousandth of a penny you will ever be dinged for this specific feature over your lifetime.Agreed, but if the feature were off by default and they didn't know it existed, there's no chance of them triggering a false positive.
Bottom line for me is that this feature isn't something that I, as a tax payer, should have to subsidize. Apple clearly designed a flawed feature and the tax payer shouldn't be made to cover the costs associated with all of these false positives. Charge the user. Charge Apple. But don't pass it along to the public.
Apple’s PR statement and iOS messaging reads like crash detection was only tested with cars and that they didn’t consider the many, many other situations that might trigger it: snow machines, ATVs, driving a vehicle in rough terrain off-road, skiing, mountain biking, etc.
Decidedly OFF.
Well, who should be fined? Should it be the owner of the iPhone?Why would Apple be fined? Apple hasn't broken the law in regards to filing a false report to 911 etc.
Well, that’s pretty vague. Was it really an emergency? LolIt's not cringy or cringey. People hate on Apple for everything they do, but the Apple Watch has saved many lives. I'm sure the people that are here today because of their Apple Watch wouldn't think it's cringey. My Apple Watch alerted me to a medical condition where I needed emergency treatment. I can't say for sure it saved my life because I don't have an alternate person to test the other outcome but it sure helped me. I appreciate what Apple has done with the watch and I wear mine all the time!
I think you're underestimating the burden this places on these small EMS departments. They will need to hire additional personnel and that's not cheap. More to the point, it's not the public's responsibility to pay for Apple's crap code that doesn't do what it's supposed to. If Apple can't fix the problem, let them pay for all the false positives they are creating across the world. It's not the public's responsibility to subsidize a trillion dollar corporation that is flush with cash and enjoys a 40%+ margin.As a fellow taxpayer I disagree. General public safety outweighs the thousandth of a penny you will ever be dinged for this specific feature over your lifetime.
They absolutely should be billed. They've create a huge problem for EMS departments and all of these false positives will inevitably lead to real accidents not getting the immediate attention they require. EMS departments will have to hire additional staff and invest in additional resources to deal with all of the false positives and we, the tax payers, will have to cover the bill...while Apple continues to rake in the $$$. It's not the taxpayer's responsibility to pay for Apple's inability to fix their garbage code.If Apple was billed a token amount, say $50, for every false alert that might help fix it.
Yes, I overlooked GPS sensitive pause. Good idea. And no biggie taking your phone out, your gloves/mitts off for a sec at bottom or top of the run.That's a really good idea! Make an obvious setting to pause crash detection, and maybe fall detection as well. With GPS it could remind the user they're at a ski area and to do this, but that also depends on the user paying attention to notifications
A good start would be to compare the number of people dying in car crashes because nobody called the emergency services in time, vs. people who died when the emergency were called promptly but arrived too late (where any sort of false alarm can be a factor). Now, I don't claim to have the data, but thinking about it, the first will be something that happens occasionally out in the sticks where there are no passers-by to raise the alarm, while the majority of fatalities are going to be occurring in heavily populated areas with plenty of eyeballs but overloaded emergency services.