A big biometric security company in the UK, Facewatch, is in hot water after their facial recognition system caused a major snafu - the system wrongly identified a 19-year-old girl as a shoplifter.
A big biometric security company in the UK, Facewatch, is in hot water after their facial recognition system caused a major snafu - the system wrongly identified a 19-year-old girl as a shoplifter.
The developers should be looking at jail time as they falsely accused someone of commiting a crime. This should be treated exactly like if I SWATed someone.
I get your point but totally disagree this is the same as SWATing. People can die from that. While this is bad, she was excluded from stores, not murdered
deleted by creator
That would then be an entirely different situation?
I mean, the article points out that the lady in the headline isn’t the only one who has been affected; A dude was falsely detained by cops after they parked a facial recognition van on a street corner, and grabbed anyone who was flagged.
That’s not very reassuring, we’re still only one computer bug away from that situation.
Presumably she wasn’t identified as a violent criminal because the facial recognition system didn’t associate her duplicate with that particular crime. The system would be capable of associating any set of crimes with a face. It’s not like you get a whole new face for each different possible crime. So, we’re still one computer bug away from seeing that outcome.
deleted by creator
This happens in the USA without face recognition
Mike judge calling it out again https://youtu.be/5d7SaO0JAHk?si=rieJnFE0YHd-_3lY
Here is an alternative Piped link(s):
https://piped.video/5d7SaO0JAHk?si=rieJnFE0YHd-_3lY
Piped is a privacy-respecting open-source alternative frontend to YouTube.
I’m open-source; check me out at GitHub.
People should be thrown in jail over a hypothetical?
In the UK at least a SWATing would be many many times more deadly and violent than a normal police interaction. Can’t make the same argument for the USA or Russia, though.
Difference in degree not kind
I’m not so sure the blame should solely be placed on the developers - unless you’re using that term colloquially.
Developers were probably the first people to say that it isn’t ready. Blame the sales people that will say anything for money.
It’s impossible to have a 0% false positive rate, it will never be ready and innocent people will always be affected. The only way to have a 0% false positive rate is with the following algorithm:
def is_shoplifter(face_scan):
return False
line 2 return False ^^^^^^ IndentationError: expected an indented block after function definition on line 1
In their defense, it didn’t return a false positive
Weird, for me the indentation renders correctly. Maybe because I used Jerboa and single ticks instead of triple ticks?
Interesting. This is certainly not the first time there have been markdown parsing inconsistencies between clients on Lemmy, the most obvious example being subscript and superscript, especially when ~multiple words~ ^get used^ or you use ^reddit ^style ^(superscript text).
But yeah, checking just now on Jerboa you’re right, it does display correctly the way you did it. I first saw it on the web in lemmy-ui, which doesn’t display it properly, unless you use the triple backticks.
They worked on it, they knew what could happen. I could face criminal charges if I do certain things at work that harm the public.
I have no idea where Facewatch got their software from. The developers of this software could’ve been told their software will be used to find missing kids. Not really fair to blame developers. Blame the people on top.
It says right on their webpage what they are about.
Developers don’t always work directly for companies. Companies pivot.
You can arrest their managers as well, good point.