Imagine you are in the situation faced by thousands every year: somebody has intimate images of you and they are threatening to spread them to your friends and family. They might be extorting you for money, more images, or just trying to cause you terrible harm.
-
Show this thread
-
What do you do? Having your images posted and then taken down hours later is not an acceptable solution, you want a way to prevent those images from spreading at all or making the jump to a major platform. You need a way to *preemptively* block images from being posted.
4 replies 1 retweet 14 likesShow this thread -
Replying to @alexstamos
Would it be possible to have a local software hash the pictures and then only upload the hashes? Purely technical question.
0 replies 0 retweets 1 like -
Not true; just do human review on match, facebook can prove they already have that image and therefore no additional exposure. They're already committed to paying for staff to review images, now they just review on match instead of submission.
1 reply 1 retweet 6 likes -
No, that's not it, I understand the problem. Facebook can store the hash forever until they get a match.
0 replies 0 retweets 5 likes -
Replying to @DitmarWendt @josephfcox and
No, that is precisely what domain specific hashes like PhotoDNA are designed to tolerate.
0 replies 0 retweets 0 likes
PhotoDNA is either what Facebook will use in their proposal, or very similar to what they'll use. You understand that they're not proposing a human compare every upload in realtime to every claimed abuse image? Images altered beyond recognition might survive in both proposals.
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.