4 ms·
I see where you're coming from, and this proposed law doesn't seem super useful in isolation. But consider: 1. Publishing the same data over OBD-2 ends up bein
by mindslight 6y ago
I see where you're coming from, and this proposed law doesn't seem super useful in isolation. But consider:
1. Publishing the same data over OBD-2 ends up being an afterthought. Without even looking at the specifics, I guarantee that there is data transmitted through telemetry that is not output through OBD-2. That's just how embedded development works - focus on making the main feature work, then forget about the rest. It seems quite hard to apply the law to the details of a technical system ("Sorry, when developing we didn't consider that type of data necessary for repairing the car, even though we are using it to diagnose. Anyway we'll fix it in the model year after next"). Whereas it's straightforward to say that no matter how many different interfaces automakers develop, independent auto repair has to be able to access all of them.
2. If we're concerned with privacy (and we should be), then we need an orthogonal privacy law that prohibits automakers from backhauling this information without consent, and selling this information without consent (eg to insurance companies). Letting them unilaterally collect and only make it accessible to their dealers, practically guarantees a terrible security implementation - something like one master login for each "trusted" dealer, that can access any car's data by VIN. Mandating access for third parties will actually result in the attack surface being properly designed and audited.
3. Once you're taking the privacy hit, then there is a stored history that won't be available over OBD-2. Imagine going to a repair shop and they tell you to borrow a dongle and drive around for two weeks, where a dealer can help you immediately. This ties into data ownership, in that you should be able to retrieve your own records.
4. Imagine a hypothetical service that keeps tabs on your car's metrics and alerts you to developing conditions. With mandated access, this can be done as a simple web service. Without that, you'll need a separate dongle, probably specific to your car if things advance beyond OBD-2. I'd personally rather have a dongle and a local service that I control (coupled with a privacy law or pulling the cell modem), but unfortunately that's not how the consumer market works.
- unholiness 6y agoThese are definitely valid points. Unfortunately your last example (3rd party web services easily discovering when I need an oil change, or what days I've been driving aggressively) is the kind of hypothetical I would want laws actively preventing. Arguably, it's not this law's job to introduce such a protection! But best I can tell, no other law covers it in MA. It is perfectly legal for 3rd parties to sell this and other data without my explicit consent or even an opportunity to opt out (I think only CA has such an opt-out [0]). Granted, manufacturers already have and can sell this data with no recourse. But at least manufacturers have national brands which could be hurt by selling or leaking massive amounts of data about their customers. Perhaps some brands could even make privacy a selling point. It seems like this law erodes that thin shell of protection. [0] http://leginfo.legislature.ca.gov/faces/billNavClient.xhtml?bill_id=201720180AB375 http://leginfo.legislature.ca.gov/faces/billNavClient.xhtml?...
- mindslight 6y ago> 3rd party web services easily discovering when I need an oil change, or what days I've been driving aggressively ... is the kind of hypothetical I would want laws actively preventing. But why, if it would still require your consent? Not faux consent based on click through or economic pressure, but real consent in the way the GDPR is getting at. > But at least manufacturers have national brands which could be hurt by selling or leaking massive amounts of data about their customers. Perhaps some brands could even make privacy a selling point. This doesn't seem to be playing out for any other industry, even ones with much lower barriers to switching (eg cell phones, supermarkets, credit cards). Privacy just does not seem to be a market differentiator. Car purchase timeframe is on the order of a decade (especially for the type of people concerned with autonomy that don't lease). So you buy a car from a brand that isn't selling your data, and a few years later they turn around and sell your data anyway. Then do you grin and bear it, or sell your car at a loss and go back to the market just to get screwed again? Until there is a privacy law, self help to prevent anyone getting your data in the first place is the only real option here. > But best I can tell, no other law covers it in MA. It is perfectly legal for 3rd parties to sell this and other data without my explicit consent or even an opportunity to opt out Yes, this is the root of our society's privacy/surveillance problem. The CCPA is relatively recent, and even that has been neutered to appease entrenched interests. Companies want to hold power over you by selling your data, and also by withholding your own data from you. Being hesitant to address the second problem because of unknown unknowns about the first problem seems like the path of self-defeat. I'd love to see another ballot initiative that addresses privacy by retaining control of our data, but this is orthogonal.