Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

> If each security guard has the entire database

What I meant was that each security guard has a certain subset of the database, so they're only responsible for scanning for those people. Say, instead of having 10 security guards each with a list of all 100 banned people, each security guard has a list of 10 people.

> Now you could invert the problem. You have the security guard take an image and distribute it to other guards who have their portion of their database that they're combing through and match against a subset of that. Still, that's a heck of a lot of extra man power that scales with the amount of bans you hand out and there's a natural backpressure for your business.

I think that's then an open problem of 1) how many people can one security guard reliably track, 2) how many people are on the ban list, 3) is it cheaper to hire that necessary number of security guards for each event than it is to invest in facial recognition tech? 4) How much cheaper or more expensive is it, exactly?

But my main question wasn't about the technical implementation, it was once again about what the actual argument is. Is it that businesses should be allowed to bar people as long as they don't use technology to do so? How would that account for different businesses having wildly different enforcement capabilities?



> Is it that businesses should be allowed to bar people as long as they don't use technology to do so? How would that account for different businesses having wildly different enforcement capabilities?

The issue is that the larger/cheaper the enforcement capabilities, the more likely frivolous bans are to be handed out.

Being able to implement small scale bans is reasonable including a "refuse the right to bar from service for any reason" type clause (which is obviously overridden by any protected groups legislation), but once implementing a permanent ban for large groups is a few clicks in a dashboard there's an issue.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: