Just because the government defined it that way 60 years ago when software updates weren’t even a thing doesn’t mean it makes sense to call a user-applicable fix a recall. It’s literally in the name. Is it being re-called back to the manufacturer or not
“user-applicable fix” is hardly correct, they are installing a fix provided by the company that has the recall. The company just so happens to provide an over the air download to patch the issue instead of having owners go to a dealer.
Where is the car being recalled to? I get that that’s the word that stuck for ‘critical fix’ or whatever but if you don’t need to bring it back that’s not a recall. Call it something else.
they are installing a fix provided by the company
So the user is applying the fix? What else do you expect that to mean?
It could easily be written in a longer statement such as “recalled for service” which is still 💯 accurate but the service is being done remotely instead of at a shop.
There are just so many other things to give a shit about in even the realm of “words meaning what they mean” that it seems like a very random, stupid thing to get hot and bothered about.
You’re probably one of those guys who has Twitter threads where you’re quoting Webster as an argument aren’t you?
If it’s being done remotely it is not recalled, that’s my entire point.
Most of my bother comes from how people are reacting with kneejerk appeals to the status quo instead of actually responding to what I (and others) wrote, think of me what you will
It’s seems like you’re saying “we should change the legal term of art ‘payment intangible’ because it’s something that is general intangible under which the account debtor’s principal obligation is a monetary obligation.”
But that’s already what “payment intangible” means.
By your logic, the software bug in my Honda’s ECU would be called a recall because it required me going to a dealership and having them perform the software update. An owner can’t simply download and install ECU updates themselves in the vast majority of cases.
But then by your same logic the software update that Toyota mailed to me on a USB stick for my Prius shouldn’t be called a recall because I was able to plug the USB stick into the car myself. The only reason Toyota mailed that USB stick to me and thousands of other Prius owners is because they were legally required to fix a software bug identified by NHTSA in a recall notice. Toyota decided the USB approach was better than having all of us drive to dealers to have them apply it.
And the various over-the-air software updates that Tesla, Rivian, and others shouldn’t be called recalls either by your same logic.
Why cause confusion over calling software updates different things based solely on who installs it and/or how it’s installed? In all these cases NHTSA received reports about a safety issue, opened a formal investigation, and ultimately issued a legally binding directive to the manufacturer that required them, by law, to address it. That legally binding directive is a recall notice, and it can apply to software that you have to visit a dealer to install, or to software the owner can install, or to software the manufacturer can install automatically.
That entire process is what makes something a recall. Not how it’s addressed in the end.
Why cause confusion over calling software updates different things based solely on who installs it and/or how it’s installed?
Because they’re different things? For the user it doesn’t matter if they’re both same legally, in one case they need to bring their car somewhere, in the other one they don’t. If anything it’s confusing to call them both a recall.
The only thing that is different in this entire process is how the remedy is applied.
And that’s the thing that matters to the person who owns the car. Currently when a user sees that word they don’t know what they need to do to fix it. You can have some other name encompassing both (like ‘critical fix’), but if you keep recall for when that fix isn’t user applicable, (and furthermore have specific names for the fixes themselves if they’re user applicable) people would immediately understand
Lots of people here are disagreeing with me but I’m yet to see an argument about why that shouldn’t be the case other than that it currently isn’t. But even that’s an argument for why changing the term would be difficult, not for why calling every fix ‘recall’ makes sense.
Just because the government defined it that way 60 years ago when software updates weren’t even a thing doesn’t mean it makes sense to call a user-applicable fix a recall. It’s literally in the name. Is it being re-called back to the manufacturer or not
“user-applicable fix” is hardly correct, they are installing a fix provided by the company that has the recall. The company just so happens to provide an over the air download to patch the issue instead of having owners go to a dealer.
Where is the car being recalled to? I get that that’s the word that stuck for ‘critical fix’ or whatever but if you don’t need to bring it back that’s not a recall. Call it something else.
So the user is applying the fix? What else do you expect that to mean?
Why do you give such a shit about this word?
I’m sorry for wanting things to mean what they mean
It could easily be written in a longer statement such as “recalled for service” which is still 💯 accurate but the service is being done remotely instead of at a shop.
There are just so many other things to give a shit about in even the realm of “words meaning what they mean” that it seems like a very random, stupid thing to get hot and bothered about.
You’re probably one of those guys who has Twitter threads where you’re quoting Webster as an argument aren’t you?
If it’s being done remotely it is not recalled, that’s my entire point.
Most of my bother comes from how people are reacting with kneejerk appeals to the status quo instead of actually responding to what I (and others) wrote, think of me what you will
👍
It’s a legal term of art. Even over the air updates are literally recalls. It doesn’t need a new term.
Yes, and as I said it is inaccurate. Legalese can be updated to better match the meaning of the word. Why is that such an unacceptable concept?
Edit: I’m really worked up about this. Seriously, why is changing the term that unimaginable to you people?
It’s seems like you’re saying “we should change the legal term of art ‘payment intangible’ because it’s something that is general intangible under which the account debtor’s principal obligation is a monetary obligation.”
But that’s already what “payment intangible” means.
Wtf are talking about?
I’m talking about this specific word that means bringing the thing back from where it went in every context but cars.
By your logic, the software bug in my Honda’s ECU would be called a recall because it required me going to a dealership and having them perform the software update. An owner can’t simply download and install ECU updates themselves in the vast majority of cases.
But then by your same logic the software update that Toyota mailed to me on a USB stick for my Prius shouldn’t be called a recall because I was able to plug the USB stick into the car myself. The only reason Toyota mailed that USB stick to me and thousands of other Prius owners is because they were legally required to fix a software bug identified by NHTSA in a recall notice. Toyota decided the USB approach was better than having all of us drive to dealers to have them apply it.
And the various over-the-air software updates that Tesla, Rivian, and others shouldn’t be called recalls either by your same logic.
Why cause confusion over calling software updates different things based solely on who installs it and/or how it’s installed? In all these cases NHTSA received reports about a safety issue, opened a formal investigation, and ultimately issued a legally binding directive to the manufacturer that required them, by law, to address it. That legally binding directive is a recall notice, and it can apply to software that you have to visit a dealer to install, or to software the owner can install, or to software the manufacturer can install automatically.
That entire process is what makes something a recall. Not how it’s addressed in the end.
Because they’re different things? For the user it doesn’t matter if they’re both same legally, in one case they need to bring their car somewhere, in the other one they don’t. If anything it’s confusing to call them both a recall.
But they are NOT different things. In every one of these examples:
The only thing that is different in this entire process is how the remedy is applied. Every single step other than that is identical.
And that’s the thing that matters to the person who owns the car. Currently when a user sees that word they don’t know what they need to do to fix it. You can have some other name encompassing both (like ‘critical fix’), but if you keep recall for when that fix isn’t user applicable, (and furthermore have specific names for the fixes themselves if they’re user applicable) people would immediately understand
Lots of people here are disagreeing with me but I’m yet to see an argument about why that shouldn’t be the case other than that it currently isn’t. But even that’s an argument for why changing the term would be difficult, not for why calling every fix ‘recall’ makes sense.