this is a compelling idea (hash it locally after running a classifier in a trusted execution environment) and i think i missed this point in your original argument. is this practical yet? what needs to happen to make it so?
-
-
Replying to @saleemrash1d @alexstamos
I believe it's practical and that I could build it, Alex says it isn't but handwaves away anyone asking why not. So, who knows...
1 reply 0 retweets 0 likes -
Replying to @taviso @alexstamos
i think there are rough edges: - if your classifier mistakenly decides that a photo shouldn't be automatically blocked, what happens? - i guess you have to rate limit the classifier (depends on the limitations of your TEE); solved by making PoW an input to the classifier?
0 replies 0 retweets 0 likes -
I don't know if I'm convinced it's necessary, I think just standard procedures (require account, rate limiting, bans, etc) will prevent abuse and just proving you've seen it first and delaying until moderation is good enough. But if people disagree, the problems are solvable.
1 reply 0 retweets 0 likes -
Replying to @taviso @alexstamos
i don't know enough about the false positive/negative rates of these image hashing algorithms to draw a conclusion here. "seen it first" on its own is such a fickle metric because there's an entire Internet of content that Facebook hasn't "seen" yet.
1 reply 0 retweets 0 likes -
but it seems to me that, regardless of the pitfalls of this method, you could deploy both at once and collect at least some data on its effectiveness in practice (not comprehensive though, because people won't necessarily upload adversarial input while the old system is in place)
1 reply 0 retweets 0 likes -
Replying to @saleemrash1d @alexstamos
It's not blocking though, it's just temporarily delaying sharing while you're moderating it, with a pretty good signal that you own the image, and options for improving the signal. Is that really so bad that we should give up and say, "just mail facebook employees your nudes"?
1 reply 0 retweets 0 likes -
Replying to @taviso @alexstamos
Saleem Rashid Retweeted Saleem Rashid
so we're on the same page here, you started with the premise of "my solution is always >= Facebook's solution" and that therefore Alex's point made no sense. i was merely presenting the case where it did have merit.https://twitter.com/saleemrash1d/status/1196513128357515267 …
Saleem Rashid added,
2 replies 0 retweets 0 likes -
i don't think you necessarily need to decide which approach is more correct, most of the time; it'd be much better to empower the victim to choose between "this photo WILL be shared and i don't want it online a second longer than needed" and "this photo may or may not be shared"
1 reply 0 retweets 0 likes
Nonsense, I've already explained how you can prevent sharing without pre-emptively mailing all your nudes. Explain to me how the system I've described can delay the sharing for *longer* than Alex's system?
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.