←back to thread

650 points clcaev | 1 comments | | HN request time: 0s | source
Show context
metaphor ◴[] No.45063162[source]
> Immediately after the wreck at 9:14 p.m. on April 25, 2019, the crucial data detailing how it unfolded was automatically uploaded to the company’s servers and stored in a vast central database, according to court documents. Tesla’s headquarters soon sent an automated message back to the car confirming that it had received the collision snapshot.

> Moments later, court records show, the data was just as automatically “unlinked” from the 2019 Tesla Model S at the scene, meaning the local copy was marked for deletion, a standard practice for Teslas in such incidents, according to court testimony.

Wow...just wow.

replies(5): >>45063302 #>>45063632 #>>45063687 #>>45063980 #>>45064115 #
raincole ◴[] No.45063632[source]
The 'wow' part is that they deleted data from server. The part you quoted sounds like nothing unusual to me.
replies(1): >>45063732 #
lexicality ◴[] No.45063732[source]
You don't think it's unusual that the software is designed to delete crash data from the crashed car?
replies(3): >>45063809 #>>45063911 #>>45064066 #
Thorrez ◴[] No.45063911{3}[source]
The question is whether this is code that's special for crashes, or code that runs the exact same way for all data uploads, regardless of whether there's a crash.

You're implying it's special for crashes, but we don't know that.

replies(3): >>45064033 #>>45064087 #>>45064288 #
1. sim7c00 ◴[] No.45064288{4}[source]
if its not special for crashes thats criminally bad design in a safety critical system.

u know if for instance u weld a gas pipeline and an xray machine reveal a crack in your work, you can go to jail.... but if you treat car software as an appstore item, totally fine??

stop defending ridiculously bad design and corporate practices.