Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add Clearview AI to new Privacy Erosion category #38

Open
rhagenson opened this issue Jan 20, 2020 · 4 comments
Open

Add Clearview AI to new Privacy Erosion category #38

rhagenson opened this issue Jan 20, 2020 · 4 comments
Labels

Comments

@rhagenson
Copy link

Request to add Clearview as an Awful candidate?

This issue would have been a PR, but not sure this use of AI quite fits the current categories thus additional request to add a Privacy Erosion category?

@daviddao
Copy link
Owner

I've been following the news and creating a summary of Clearview.
I think it could fit into the existing 'surveillance' category?

@rhagenson
Copy link
Author

Sounds good on the summary. The current Surveillance entries felt more government/corporation + continuous monitoring to me, which my introduction to Clearview did not really fit into (saw it first from a person-to-person safety perspective). After reading more on Clearview, I agree that it fits within Surveillance.

@showengineer
Copy link
Contributor

Sounds like Clearview was a tool used by millionaires to identify normal people

@KOLANICH
Copy link

KOLANICH commented Mar 7, 2020

An app by a Russian company NTech Lab (now defunct, it was just an advertising campaign to allows strangers to use ther system) have allowed "normal" people (those *****s who have allowed the app to scan their VK (Russian largest social network website, originally created by Durov bros (who later have created Telegram)) profiles, I suppose to fill the DB with the private photos not available to accounts that are not "friend"s and probably other info) to identify "normal" people (those *****s who have put their photos on their VK profile, as prescribed by its ToS) in 2016.

daviddao added a commit that referenced this issue Jun 1, 2020
Thanks to thread #38 for all the additional information gathering
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

4 participants