|
Go.cam is something I've been really curious about, because I am very interested in their implementation since it's entirely in the browser, which means no images or data is uploaded to any centralized server. That kind of privacy could be a huge selling point for adult sites, since users are going to be very opposed to any kind of long-term recording of their information. My clients, who will want to employ this after purchase or after login, would absolutely prefer not to have a third party maintain data.
I read the open source code, so I know which libraries are being employed to do the age verification, but what methods are being used to ensure that malicious actors do not hijack the local verification data that generated and presumably sent to Go.cam or sent to the webmaster to record? Does anyone who uses Go.cam know?
|