News for hackers. Stuff that matters.

A comment on Cruise is opening driverless cars to the public in San Francisco. Parent comment

Re:Cruise is opening driverless cars to the public in San Fr... by BurningFrog on Tuesday February 01, 2022 @10:54PM (#30173491)
I've given it some thought, and I think the SDC manufacturer must be liable for any accidents the SDC causes. Who else is there? The passengers certainly can't be responsible for any programming or manufacturing errors.

There are corner cases and exceptions, but that has to be the rule.

Which should mean that as and SDC owner, you don't have to pay car insurance.

[ Parent | on HN ]
Re:Cruise is opening driverless cars to the public in San Fr... by rfrey on Tuesday February 01, 2022 @11:40PM (#30173784)
>the SDC manufacturer must be liable for any accidents the SDC causes.

There's the rub... How do you seperate those from the rest?

[ Parent | on HN ]
Re:Cruise is opening driverless cars to the public in San Fr... by wutbrodo on Tuesday February 01, 2022 @11:50PM (#30173859)
We already have a system that relies on assigning fault among the multiple parties involved in an accident. This same approach applies just as well to SDC accidents. It would be even easier than the status quo, given the much richer data SDCs could be regulatorily mandated to provide.
[ Parent | on HN ]
Re:Cruise is opening driverless cars to the public in San Fr... by harpersealtako on Wednesday February 02, 2022 @01:34PM (#30181817)
If there is disagreement between the relevant parties, through the court system (or through insurance agreements).
[ Parent | on HN ]
Re:Cruise is opening driverless cars to the public in San Fr... by BurningFrog on Wednesday February 02, 2022 @07:00AM (#30176411)
The whole event will be recorded by at least the SDC vehicle.
[ Parent | on HN ]