Episode #23 - Liu on Responsibility and Discrimination in Autonomous Weapons and Self-Driving Cars

Summary: In this episode I talk to Hin-Yan Liu. Hin-Yan is an Associate Professor of Law at the University of Copenhagen. His research interests lie at the frontiers of emerging technology governance, and in the law and policy of existential risks. His core agenda focuses upon the myriad challenges posed by artificial intelligence (AI) and robotics regulation. We talk about responsibility gaps in the deployment of autonomous weapons and crash optimisation algorithms for self-driving cars. You can download the episode here or listen below. You can also subscribe on Stitcher and iTunes (the RSS feed is here). Show Notes0:00 - Introduction1:03 - What is an autonomous weapon?4:14 - The responsibility gap in the autonomous weapons debate7:20 - The circumstantial responsibility gap13:44 - The conceptual responsibility gap21:00 - A tracing solution to the conceptual problem?27:47 - Should we use strict liability standards to plug the gap(s)?29:48 - What can we learn from the child soldiers debate33:02 - Crash optimisation algorithms for self-driving cars36:15 - Could self-driving cars give rise to structural discrimination?46:10 - Why it may not be easy to solve the structural discrimination problem49:35 - The Immunity Device Thought Experiment54:12 - Distinctions between the immunity device and other forms of insurance59:30 - What's missing from the self-driving car debate?  LinksHin-Yan's faculty webpageHin-Yan's academia.edu page'Autonomy in Weapons Systems' by Hin-Yan'Refining Responsibility: Differentiating Two Types of Responsibility Issues Raised by Autonomous Weapons Systems' by Hin-Yan'The Ethics of Crash Optimisation Algorithms' by John Danaher'The Ethics of Autonomous Cars' by Patrick LinInterview with Sven Nyholm about Trolley Problems and Self-Driving Cars #mc_embed_signup{background:#fff; clear:left; font:14px Helvetica,Arial,sans-serif; } /* Add your own MailChimp form style overrides in your site stylesheet or in this style block. We recommend moving this block and the preceding CSS link to the HEAD of your HTML file. */ Subscribe to the newsletter