I'm sad to see a civil rights advocacy organization approach an issue of such impact with shallow snark. They clearly did not read the original post by my incredible colleague, Antigone Davis, nor comprehend the hard tradeoffs in dealing with revenge porn https://www.facebook.com/fbsafety/posts/1666174480087050 …https://twitter.com/fightfortheftr/status/999720271484350464 …
-
Show this thread
-
Antigone and her team have traveled around the world meeting with victims of NCII (the official term for revenge porn) and advocacy organizations, trying to answer a really tough question: how can we empower victims to stop the spread of nude images.
2 replies 5 retweets 20 likesShow this thread -
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.
1 reply 3 retweets 13 likesShow 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
Everyone is on board w/preventing abuse. It's the bit about having to share intimate pictures that's worrying. You're dismissive whenever someone says there are technical solutions, if you've got some convincing evidence, why not share? (eg. why not sgx+photodna+review on match?)
1 reply 1 retweet 12 likes -
Replying to @taviso @alexstamos
You mean? 1. submit hash/photo ID to block 2. When a hit happens, trigger manual review of the uploaded photo 3. If bad stuff, tell law enforcement about uploader. And inform victim 4. If good stuff, ask original submitter for proof the hash is for a bad photo
2 replies 0 retweets 0 likes -
Downside 1: this lets anyone force manual review of any photo by fake-reporting it. So e.g. the Turkish gov could make anyone wait $REVIEWTIME to post photos it didn't like
2 replies 0 retweets 1 like -
Replying to @katrielalex @mullender and
Downside of SGX: an SGX exploit could perma-break PhotoDNA (since an attacker who could fake running on a legit enclave could get access to the fingerprint algorithm and figure out how to work around it)
1 reply 0 retweets 1 like -
Replying to @katrielalex @mullender and
I mean I'm sure there are potentially technical solutions but are there ones you would comfortably support rolling out yesterday?
1 reply 0 retweets 0 likes
PhotoDNA could leak at anytime, do you really argue it's more likely to leak from an SGX defeat than leak/attack/etc of licensee network (not necessarily facebook, any licensee will do)? The latter seems way more likely to me.
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.