My old boss had a fancy top of the line Audi with all the trimmings.
One day a fault developed with the seatbelt sensors on the rear seats. He kept getting the warning beeps to fasten the belts when no one was on those seats.
It was still in warranty so he took it get fixed. The dealer pulled his driving logs from the on board computer/data recorder and said his driving was too aggressive and that violated the warranty.
Truth be told his driving was terrible. I accepted a lift home from him once, and only once because his driving scared the bejeesus out of me. But that being said how could that affect the pressure sensors in the rear seats?
It took some solicitors letters to get the dealer to agree to a warranty repair.
I think its inevitable that manufacturers are going to use all this data to stop you claiming under your warranty. "Oh dear you slammed your door too hard one day, I'm afraid that invalidates your warranty". Insurers will demand this data in before giving you a quote. Its also likely that there will come a time when this data will be used to help price your car if you sell it or trade it in. And of course the government will want to use positioning data to automatically issue parking fines.
And this ignores all the obvious security risks that come along with this sort of stuff, for example all those BMW keyless car thefts.
Its also likely that there will come a time when this data will be used to help price your car if you sell it or trade it in.
That, at least, is potentially defensible. How the car is treated & how/where it was driven do have a big impact on long term reliability.
In fact, if you are a gentle driver who lives in a good location and operates the vehicle under optimal conditions, you could expect to get more for your vehicle- today, because the buyer cannot easily tell, they pay you somewhere in the middle.
Insurers will demand this data in before giving you a quote.
Same goes here, once it becomes commonplace, insurers will be able to reliability identify "golden goose" customers who, based on driving patterns, are exceptionally unlikely to get in an accident. They will fight eachother tooth and nail for these drivers.
I think its inevitable that manufacturers are going to use all this data to stop you claiming under your warranty. "Oh dear you slammed your door too hard one day, I'm afraid that invalidates your warranty".
Thankfully we have Magnuson-Moss, so while bad apples might give you the occasional runaround, the law is on your side.
> Same goes here, once it becomes commonplace, insurers will be able to reliability identify "golden goose" customers who, based on driving patterns, are exceptionally unlikely to get in an accident. They will fight eachother tooth and nail for these drivers.
I understand that this is what insurers are striving for, and same with good drivers, the problem with it is that personalizing prices to everyone essentially makes insurance useless, since you'll essentially end up paying how much damages would really cost if you had no insurance + extra premium, because insurance wants to make money
The whole idea of insurance is that you have a pool of people and there is probability that percentage of it will have an accident, the remaining group subsidizes essentially creating a safety net.
All of that is negated when insurance prices individually, since you'll always lose on it.
It doesn't make insurance useless, in fact it only makes insurance fair - yes, the whole idea of insurance is that you have a pool of people that covers the damage when a small percentage of them have an accident, but people who have twice as large likelihood to have an accident should justly pay twice as much in that pool.
The point of insurance is not to have some people cross-subsidize others on average, the point of insurance is that you might prefer to have 100% chance of paying ten bucks instead of 0.1% chance of having to pay ten thousand at a point when that would ruin you - and if you can afford the loss if it happens, then yes, there's no point in insurance for you, it's not a charity where you expect to get a net benefit from the insurance company.
Looking on the other side, from the driver that gets hit: I prefer to everyone having some insurance and paying me when I'm hit than relying that a "good driver had a bad luck".
Bad drivers hitting me and don't paying isn't useful, be it paying me directly or reimbursing my insurance company.
Only if the probability of a significant accident is 1 (or you have tons of free capital)
If your lifetime probability of a $10M accident is 0.01%, it is probably preferable to pool your risk with other drivers of equal risk, and pay $1,000 + small extra premium.
What I'm trying to say in that scenario, I would essentially pay what my damages would cost the insurance + extra premium to pay for insurance employees' salary.
In that case, why not just cut out the middle man and pay out of pocket when accident happen, it would be cheaper.
Essentially this tendency defeats the purpose of having insurance in the first place.
Actually, insurance premiums are designed to pay 100% of the losses the actuaries predict will occur over a large pool of people. There is a number commonly discussed by insurance companies called the "loss ratio." A loss ratio of 93% (i.e., $93 paid in claims for every $100 collected in premiums) for a year is very good. On the other hand, a loss ratio of 105% or even 110% in a year is not good, but not unheard of.
Insurers make their money on investments of premium dollars, not on loss ratios. Sure, they might have a good year or two with low loss ratios, but that means they're collecting too much premium compared to competitors and so may lose market share if the others lower premiums due to more accurate forecasts of losses (closer to 100%). This is one reason insurance marketing and advertising work so hard to drive customer loyalty and retention.
So your rates went up even though you didn't have an accident? Better look to see what the stock market has been doing lately.
It's a spectrum with that scenario at one end and at the other end: everyone paying exactly the same amount regardless of age, car, location gender, previous convictions etc.
I think that tailoring the premiums based on the driving style is fair, and would give bad drivers the option to improve to reduce their insurance, with the nice side affect of making the roads safer. It isn't going too far down the slope to do this.
In the extreme, it would mean everyone would need to become a safer driver or not drive at all, which is probably a good thing.
They will become safer drivers then pay a small premium to cover them for chance accidents like a collapsing bridge or a blown out tire.
>My old boss had a fancy top of the line Audi with all the trimmings.
I'd love to know how the dealer could justify saying a high-end Audi, a car (and company) with an established racing pedigree, was driven "too aggressively".
The "tracking" community embraces the fact that racing puts incredible strain on the car. Half of the hobby is the money and time you pour into service and repairs after every track day.
There are no illusions that this is something the warranty would or should cover.
>Insurers will demand this data in before giving you a quote.
This isn't obvious. Sure, some irresponsible driving behavior is evident in braking, acceleration, speed, etc. data.
I suspect the much larger pool of bad drivers is people who are braking and accelerating very gently because they are spaced out, drowsy, or on their phones.
I don't know the actual specifics, just that my boss came in to work one day raging about it. I suspect the dealer was just looking for excuses to not do the fix.
But just a cursory read around the web seems to imply that this is happening more and more and to be honest I think it would be unwise to assume that manufacturers wont make it an official policy at some point.
Dublin Ireland or Dublin Ohio? I live Ohio and know there's an Audi dealer in our Dublin. I have an Audi and would like to avoid that dealer if possible.
We have an infestation of middle aged men who drive mid to high end Audis (always painted black) with a set of gold clubs permanently stored in the boot.
he's probably referring to the dublin in the east bay area, ca. it looks like there's an audi right next door in livermore, ca which he was probably referring to.
My assumption would be that Audi told them this. The dealer is normally more than happy to perform repairs under warranty, as this is easy, guaranteed money for them. It's basically the same reason they love getting exclusive deals with insurance companies.
Sometimes perverse incentives are set up; for example, the manufacturer may offer a "bonus" payment if the number of warranty claims serviced by the dealer in a quarter is below a specified target.
Sometimes, "book time" to fix a particular defect is lower than the actual time, and manufacturers pay out on book time.
However you spin it, the dealer-manufacturer relationship ends up working in favor of the manufacturer, as they control the inventory and the bottom line of the dealer's balance sheet.
yes - also, some dealers refuse to perform warranty repairs with cars that have aftermarket parts... others are totally fine with it, and will even install aftermarket parts and perform warranty work afterwards.
I live a highly automated life and my database has when I woke up, where I drive, when I get home, what TV shows I watch, how long I spend on Hacker News and when, when I enter the house it is recorded... and then more benign stuff like how long my air conditioner has been on. And and I do this voluntarily.
Overall it's a gig of data a day.
The weird thing is my wife has access to this data too and I have access to her's (which is less extensive but still there... for example, if her code is used to disarm the alarm, it is stored that way).
I also might be crazy, most people would be disturbed with this level of data.
As a side note, I store the database on my own server and I am very comfortable with the security on said server. Firewalls, tripwires, multi-factor auth, encryption, the works. Even I wouldn't trust that database with a third party.
Have you done any analysis on the data? I'm wondering if you can find out if you're coming down with an illness before your body even exhibits the symptoms.
Here's the implication of why I say this: IoT companies who sell this data to third parties will then have this bit of leverage over you. The next time you browse Amazon/FB/News your browser, sans-adblock, will be just as infested with ads as your body is with the cold.
I often wonder if there is enough data to do that but I don't have a medical background so I wouldn't know how. Part of the dataset is my output from 23 and Me, as well as my steps, heart rate, weight, BMI, and caloric intake. I'd love to gather more but blood pressure, blood sugar, body temperature, and the like are semi-invasive to gather and I avoid gathering data I need to do daily manual work for.
The only exceptions I make are weight lifted and repetitions when working out and only because I haven't found a good way to do it and it... I've been playing with Arduinos and accelerometers and measurements (waist, chest, thighs, etc) which I only do once a month.
So in theory it is possible.
But in any case, per your motivation behind the question. I avoid devices that report data to a central server so advertisers using it would be hard pressed, but not all consumers are as careful. I can't avoid it entirely without making my own hardware. For example my Fitbit data goes to Fitbit, my treadmill data goes to iFit, and 23 and Me has my DNA sequence. But I think you'd need all the pieces to it all together and there is no third party that has them all.
>> "Being disturbed signals lack of touch with how reality works."
Could you explain what you mean by this? That level of data collection disturbs me for privacy reasons. I don't see how I lack touch with reality. It's interesting and I would like to have all that data on myself too but the privacy risks make it not worth it for me.
I was talking about being disturbed by existence/collectability of such data - not by collection by third parties, which is disturbing for privacy reasons. You radiate tons of data every second of your life. Your every interaction with every thing is recorded in the fabric of reality, and progress of technology gives us ways to access more and more of that information.
My point is - existence of such data should not be disturbing. How much of it is being collected by third parties - that's another story.
I agree completely. And the data certainly delights me.[1] I don't think most Hacker News users would be disturbed by it. I was generalizing (without evidence, mind you) the larger population.
[1] One nice thing about owning the database is if I want to, say, stick it in an R program and graph some stuff / make some models I can. Which as a software engineer is fun for days and has allowed me to see and correct and/or automate patterns. For example, my bank accounts and credit cards are also in this database and it has allowed me to see spending patterns that I needed to fix.
I'd be lying if I said this exact article wasn't behind some of the ideas I've used to build my own system. This was one of the first times I've heard the term Quantified Self.
Now I see "myself" as just a thing in the Internet of Things that I can track metrics on (and tell to do things) just like any other thing.
Don't take me philosophically or spiritually with that statement. As a human I am trained to think of myself as more than "just a thing" and to think otherwise would be a bit morbid :) but from an architectural standpoint I don't treat my own metrics different than the rest of the 200+ devices in my IoT network.
Home grown. Node.js running on a server in my basement. I do plan to open source it someday. It was a lot of work. Some devices I had to reverse engineer.[1]
[1] A little more detail on that because I'm sure they might find it interesting:
- If there is a phone, Linux, or Mac app I use Charles to try to intercept the traffic
- If that fails I use Wireshark
- If that fails I decompile their app
- If none of those work, I have to ditch the hardware and try new hardware.
Don't forget the possibility of data being repeated by your electric meter even if you don't provide WiFi. They're generally dual band, operating at WiFi frequencies for local interaction and with more power at a lower frequency for the networked traffic. While the protocols are not intended to be WiFi compatible, the already-proven-hackable devices are just a patch away from unexpected functionality. The local link is intended for things like telling your air conditioner not to run part of the time when the grid supply doesn't have much excess capacity.
What other data is sitting around? How about raster images of whatever your "copier" printer fax has handled? Even if you're using USB, if there's WiFi capability in there, assume it can be awakened. A link that's not compatible with your sniffer is a possibility too. Drag out a spectrum analyzer and directional antenna. While you're at it, check those new LED streetlights for bursts of r.f. too.
How have you implemented multi-factor? Near as I can tell there's no good open-source ways of managing it (i.e. something where I get Google-style app-passwords available via LDAP to connected applications + a UI for managing them).
Google Authenticator uses an open time-based algorithm that doesn't even require a server. Both sides just need to have the same seed and the same time on their clock (you can configure server-side how much clock drift to allow).
Authy supports the algorithm as well, they just don't advertise it because they want you to use their's.
To make myself more efficient. Automate things I have to do but that don't make me happy. Improve my physical health (I'm motivated by numbers... they get me to the gym). Make more informed decisions.
Basically I run my life like a business. I track KPIs[1] and use them to plan and act.
For example, right now my app is telling me I'm spending more than my average amount of time on Hacker News. And based on that, I can make the decision I should probably get some work done :)
Also, if I ever get murdered, unlikely for sure, the cops will have an easy job ;) (joking, this isn't a primary motivation but, certainly a side effect).
Edit: plus I think it is fun, it's a hobby. Everyone needs a hobby :)
No writeup and I haven't open sourced (yet) but the gist of it is:
For my software:
- Node.js
- MongoDB
- Ubuntu Server
- Docker
- Java for my mobile app
- Electron for the desktop app
For hardware:
- Galaxy Note 5 using the accelerometer and GPS
- Macbook Pro running custom monitoring software
- Fitbit smart scale
- A lot of Aurdinos
- A few Raspberry Pis
- A few Spark Photons
- A Vera for home automation and integration with household sensors
- A whole slew of Zwave and Wifi house sensors and switches
- The cameras and alarm are through ADT Pulse but to be honest I wish I had used a more open solution. Everything runs through their servers, I can't talk directly to the cameras.
- Some more home automation stuff that is not really quantified self (more IoT) so I'm not including (Nest thermostats, myQ garage door opener, etc)
For protocols (you'd be surprised at how many devices you can get data from knowing these three protocols):
- UPnP
- Bonjour
- HTTP
- IMAP
For APIs:
- Fitbit
- Facebook
- Twitter
- IMAP for email (not an API in the sense people think of APIs but still...)
- Nest
- A bunch of stuff that I had to reverse engineer because they don't offer public APIs
For analysis:
- R mostly
For reverse engineering hardware devices that don't open their APIs:
- Charles for a proxy to sniff traffic (if they have an app)
- Wireshark for devices that don't obey proxies
I'm sure I forgot something.
As you can see, it is a LOT of work. But it's a hobby so I enjoy it. I want to open source it one day but as you can imagine... none of this is unit tested or meets any of the criteria I would use for an open source project. It is, in effect, a "hack"... but it works.
Well, I chose Zwave because at the time Wifi lights were nonexistent and Hue wasn't available yet.
However, Zwave is pretty nice because it doesn't tie up my Wifi bandwidth, is quick to set up, and it forms a mesh network. Plus the devices are a fraction of the cost of the Wifi connected one.
All the improvements have been minor but they add up to large lifestyle improvements. Some examples:
- I never have to worry if I left the garage door open or the lights on.
- I can set my alarm (the intrusion detection kind not wake up kind) without leaving bed if I forget to set it.
- Controlling all my entertainment devices is now one click instead of messing with 5 different remotes. It's also easier for guests to understand.
- My sprinkler system adjusts watering based on the moisture level and the last time it rained. Which conserves water.
- My thermostat knows when I'm not home which also conserves energy and saves money.
- My exercise equipment turns on when I need it on schedule, which helps me to stay motivated. The TV with the workout DVD in it also turns on on schedule.
- Holliday lights turn on at dusk and turn off at 1 AM. Or when I tell them to with my phone.
- I can get woken up at the right time so I'm less tired throughout the day.
- If I have someone coming over to say, fix the plumbing, I can give them a temporary code that is only good during the time they are supposed to be there. Or they can call me and I can unlock the house from my office. And I can see them on video while they are there. Plus the alarm can set when they leave.
As I said, little things that add up.
The health and quantified self type stuff has helped me spend less time on stuff I shouldn't be doing and more time being healthy.
One of my favorite devices in terms of effect on my life, as weird as this sounds, is my Sonos system. I have speakers in every room in the house and I can use them to play music that sets the right mood whether I'm working out or eating. It's also nice to be able to pipe the TV audio to other rooms during, say, the presidential debates.
Have I considered machine learning? Yes. I actually use some to automate email. It deletes email I don't want to read and nags me about email I really should reply to (hence my previous post that mentions IMAP). But I'd love to find more uses of it.
One use I've been toying with is learning when I need to go places (like the grocery store) and alerting me when I'm driving near it so I can save an extra trip. Example: the milk will be gone in two days and you're right next to the store, you should get more now so you don't have to make a trip later.
None of this is important on its own and some of it is downright silly, but in aggregate it adds up.
Thanks for the insightful response. One use for machine learning could be to determine an optimal sleep/eating schedule. You'd probably need to log some mood/health data but should be doable. Similarly you could probably do something with diet data.
I laughed out loud on this one. This is great, especially since I just finished reading an Asimov book.
I guess I'd have to change my database to be built on blockchain technology so that it is cryptographically impossible to modify past state without detection. Then I'd just need to make sure the computer has append only access to the backups.
Since the company I co-founded at YC S11 (Automatic) was called out in the article, I want to share a few thoughts here.
It’s absolutely true that connected cars and the wider IoT space has miles to go in terms of security and privacy. Far too many companies treat security as an afterthought, and then we see everything from Jeeps to Barbie dolls being compromised. Those same firms then treat privacy as a winner-take-all game, where they expect the customers to give them maximum access with minimal accountability. And frankly, it pisses us off.
To get back to the article - car manufacturers that hide what they’re doing from consumers should knock it off. I don’t think they’re necessarily being nefarious, I just think they’re being foolish. In this age where consumers are waking up to the risks and rewards of connectivity, obscuring the data you’re collecting and how you’re using it is only going to become more untenable.
Edit: sorry, I extrapolated too much from my own experience. It's still not legally mandatory until 2018, however some manufacturers do indeed make it mandatory today.
Due to privacy protections I don't think marketers and insurers have access to driving data, but the security concerns remain. Their back-ends can be hacked, rogue employees could listen in, etc.
They've been talking about that technology for years, but that's a long way from not being able to buy a car without it.
In fact, the official site[1] says:
"On 28 April 2015 the European Parliament voted in favour of eCall regulation which requires all new cars be equipped with eCall technology from April 2018. eCall will be seamlessly functioning throughout Europe by that time."
And that's before the inevitable privacy lawsuits and so on.
I went for a test drive the other day, and the sales guy told me on his first test drive a couple of year ago, the customer actually rolled the BMW he was considering to buy. Upside down, airbags on.
He was so impressed by the automatic assistance call that he actually bought the car.
I hadn't heard of this. Just looking at the article you linked it seems it is only available in Slovenia and only since 2015. Is the tech still in all cars but just not being utilised?
eCall is weird. There are supposedly privacy protections, but I can't see how it can work without being always on the mobile network. Which tells you what cell the car is in.
Hardly anyone has heard of it and details seem vague.
I know for a fact that some manufacturers (check wikipedia) ship all cars with this system enabled. It might not be connected to the "real eCall" back-ends, but rather to the manufacturer back-ends, but it's there.
My current car has it. It used to be optional before 2015, but then they made it mandatory with the expectation that the law comes in effect.
"Once cars become fully driverless they will rely entirely on their outgoing and incoming data connection to function properly."
Not true. Chris Urmson, former head of Google's self-driving car project, before he left Google, made that point at a "connected car" conference. Google's self-driving cars don't rely on car-to-car communications. They rely on sensors. Lots of things a self-driving car needs to know about aren't "connected", and you can't trust the ones that are.
Google's own cars download their logs when they get back to the barn, but that's for debugging purposes. A production vehicle would not need that feature.
On the other hand, the Event Data Recorder in most cars isn't a big deal. It's a crash recorder. After a crash that caused airbag deployment, someone can dig into the wreckage, plug into the box, and look at the last 15 seconds before the crash. Useful for accident analysis, but not Big Brother. OnStar type systems are much more of a concern; they run all the time and have GPS inputs.
One can imagine a data connection being used to share routing-related information (traffic, road closures, etc. -- basically, the same thing a human driver would do with Waze/GMaps/etc.) for higher level planning, but, yeah, it makes little sense to rely on such a connection for basic operation rather than route optimization and cooperative traffic management.
The manufacturer will have bought a SIM for the lifetime of the car. You could potentially pull it and use it until they notice and shut you down, although it may (ought to!) be limited to a VPN tunnel.
I have a taste for the secret,
it clearly has to do with not-belonging;
I have an impulse or fear or terror in the
face of a political space, for example,
a public space that makes no room for the secret.
For me, the demand that everything be paraded in
the public square and that there be no internal
forum is a glaring sign of the totalitarianization
of democracy. [. . .] if a right to the secret is
not maintained, we are in a totalitarian space.
(Jacques Derrida, in Roudinesco, Jacques Lacan & Co., II, p. 599.)
Some of these sorts of issues are simply going to be standard and not so avoidable. I'm all for it if it means that we get autonomous cars everywhere, even better if it means that one public transportation option is to call up a pod to travel in. But regardless of the future, most of these things are still positives from a broad view.
Things such as improved emergency response (so long as equipment is upgraded), tips on how to improve your own driving (upon request) to make your car last longer, aggrevate data on different things to teach new drivers, and how common behavior x, y, and z are. I have little problem with the auto-ticketing, provided the state tests the system once a year or two to make sure it is functional (and when it is contested). This stuff makes the roads safer.
Though folks could hack into his brakes or disable his vehicle, right now that doesn't happen often to actually fear, and safeguards could be put on the vehicle to keep him safe.
The bigger threats he mentions are private firms and law enforcement.
The biggest factor with law enforcement is to have safeguards to check the honesty and things like that. Make sure the laws are fair and that law enforcement isn't tempted to bend them.
Private companies, such as insurance companies, are slightly different. While I believe this could be changed with legal protections, I believe there is very little hope of such legal protections being made with the current political climate. I don't think the information is bad per se, as we could learn quite a bit about normal driving habits, but the companies could decide to lobby for things like better enforcement of traffic violations, lower legal BAC levels, and other such things to gain the same sort of safety.
I predict a thriving market in grandfathered-in vehicles in the not-so-distant future. In many ways, I miss the '85 F150 I drove in high school. If there was a computer chip anywhere in it, it had shorted out long ago, but the thing just kept rolling along. It's become the truck of Theseus now, but it is still on the road, 300k+ miles later.
Not only is it impractical in rural areas of the US like others have said, but in most small-to-medium sized cities as well. Some places simply won't hire folks if they don't have access to a car. Some small cities have no taxi service, and the larger (30-80k) that do often charge too much to use on a regular basis.
Not to mention the same holds true for rural areas of other countries as well, as the bus system might not come often enough to work, let alone buy groceries. Or you might have to deal with weather which makes bike riding (let alone walking) inconceivable.
Where I live, the closest store is 5 miles, but it's just a very basic and small general store. To reach an actual store with fresh produce and more, it's a 100 mile round trip. That may be on the somewhat extreme end of things, but variations on that are a normal way of life for people in rural areas.
Cellphones may be popular, but they are not ubiquitous. Land lines (and equivalent) work fine for many purposes (including me).
Since humans are terrible at assessing risks that have probabilistic or delayed effects, most people - including some engineers that should know better - don't understand or underestimate how powerful patter-of-life analysis can be when it can utilize entire lifetimes of timestamped location data.
The point is you shouldn't assume everyone has a cellphone in their pocket. Therefor a car that broadcasts its location would compromise an existing expectation of privacy.
The rapidly growing use of ALPR devices is causing a similar compromise of privacy, but that's a separate problem.
My point is that it's not compromising an existing expectation of privacy if 1) you have the option to buy an older car, and 2) you are aware the new car you are considering buying is connected to the Internet.
Connected cars are going to create a much safer world .... the other month someone was in the news after a hit-and-run, the vehicle phoned the police and reported it itself. Eventually when all the cars have cameras, sensors, autonomous power to report to police things like speeding, reckless driving, hit and runs etc will go instinct as every vehicle around you is recording, reporting...
In terms of traffic control it's probably going to be mostly beneficial for people. Bad drivers will surely be annoyed, just as they were when running red lights and speeding became things that could be enforced 24/7.
If it spread to security cameras ... consequences could be a grave new world where a young Dennis Leary is caught in his very first act of subversion.
Bad drivers will surely be annoyed, just as they were when running red lights and speeding became things that could be enforced 24/7.
I like to consider myself a good driver, I'm mostly concerned about black-and-white application, where we had officer discretion in the past. (Discretion is hard to teach computers)
The traffic light I "ran" yesterday springs to mind. Second in line at stoplight (behind a cop no less). Light turns green, we roll into intersection. Light changes to yellow, then red, before either of us exit the intersection. An officer would not ticket me, but a computer that was not meticulously programmed probably would.
I don't know what the law is in your state, but in some states (like AZ), the law is that you only have to enter the intersection when it's green or yellow. If it turns red while you're still in the intersection, that's no problem for you, but other drivers have to wait for you to clear the intersection. So it's perfectly normal for turning drivers to enter the intersection and wait there, and then after the lights turn red and the straight-through drivers clear the way, the people turning will finish their turn, and the oncoming traffic with a green light has to wait for them to do this.
Situations like that won't always be easy and probably require manual arbitration which also creates work unfairly too.
But I'm much more interested in the egregious stuff in the rest of the world that goes largely unpoliced and kills millions a year - the Costa Rica version of your story is intersections routinely blocked by busses that are eager to cross when there's no space and an orange light!
All cars should come with the equivalent of an "airplane mode" switch--easily accessible to the owner--that disables all RF emissions and receptions. Since car companies are certainly not going to provide the switch voluntarily, it's probably going to require regulations to make it happen.
I had the same issue with my VW where it was activated without me signing the paperwork. The official line I got from VW was that it couldn't be removed or deactivated because it is 'safety equipment'.
One day a fault developed with the seatbelt sensors on the rear seats. He kept getting the warning beeps to fasten the belts when no one was on those seats.
It was still in warranty so he took it get fixed. The dealer pulled his driving logs from the on board computer/data recorder and said his driving was too aggressive and that violated the warranty.
Truth be told his driving was terrible. I accepted a lift home from him once, and only once because his driving scared the bejeesus out of me. But that being said how could that affect the pressure sensors in the rear seats?
It took some solicitors letters to get the dealer to agree to a warranty repair.
I think its inevitable that manufacturers are going to use all this data to stop you claiming under your warranty. "Oh dear you slammed your door too hard one day, I'm afraid that invalidates your warranty". Insurers will demand this data in before giving you a quote. Its also likely that there will come a time when this data will be used to help price your car if you sell it or trade it in. And of course the government will want to use positioning data to automatically issue parking fines.
And this ignores all the obvious security risks that come along with this sort of stuff, for example all those BMW keyless car thefts.