It also possibly highlights the fact that algorithms are not immune to bias when they are designed by humans. Obviously I don’t think this bias is intentional, but so much of it isn’t and happens anyway.
It also possibly highlights the fact that algorithms are not immune to bias when they are designed by humans. Obviously I don’t think this bias is intentional, but so much of it isn’t and happens anyway.
I would wager "absolutely not" for the exact same issue as firearms or cars. The person who mis-applied the technology or a middle man vendor though? Unless they fall under qualified immunity, there's your fall guy.
Almost every engineering discipline has a code of ethics [0][1][2][3]. It's time software "engineering" grew up and did the same.
I rarely see ethics mentioned on HN, and granted, people's view differ. But it's weird we're not having that conversation at all.
[0] https://www.raeng.org.uk/policy/engineering-ethics/ethics
[1] https://www.ieee.org/about/corporate/governance/p7-8.html
So. Let's talk about ethics. I, personally, subscribe to the ACM code of ethics.
I think Rekognition, as built and presented, falls fully within that strict ethical code. It can be put to uses that are unethical, but that does not fall upon the people who made it. Certainly, an engineer creating a system such as the one the ACLU created would be acting unethically.
Will that slow things down and make them more expensive? Absolutely, but that’s the cost of safety.
In this case though what is probably most lacking is public knowledge about the shortcomings of such systems. The public needs to understand that 90% accuracy, while it sounds high, mean it’s wrong a lot, and the chances of it being wrong if it was continuously run all the time are actually quite high.
Car manufacturers are sued for incompetent use of their products.