3 ms·
If the system allowed users to send the hash, then yes, it would allow users the power to arbitrarily take down photos. The point of the users having to post th
by danso 9y ago
If the system allowed users to send the hash, then yes, it would allow users the power to arbitrarily take down photos. The point of the users having to post these images from their own account is so that a FB employee can confirm that the content breaks FB rules and that the content is associated with the user.
- zAy0LfpBZLC8mAC 9y agoIn other words: The solution to preventing strangers from looking at your nude photos is to have strangers look at your nude photos? Brilliant!
- danso 9y agoI've only read the posted article so I don't know if "revenge porn" is the primary or originating motivation for this initiative (as opposed to child porn victims, etc). But my perception is that victims of revenge porn -- the ones who feel the need to make a complaint (and risk drawing publicity to themselves) have had (or perceive) their images disseminated so widely to such psychologically devastating effect [0] that the thought of a FB employee seeing them is among the least of their worries. Probably because FB employees have already seen them if the user has submitted an abuse complaint. [0] https://www.theguardian.com/lifeandstyle/2015/feb/06/experience-i-was-victim-of-revenge-porn https://www.theguardian.com/lifeandstyle/2015/feb/06/experie...
- m_eiman 9y agoI'd assume that any matching photos would be manually verified to be of a nature possibly related to the subject at hand, "revenge porn", if the uploading user clicks the "hey, I should be allowed to post this" button?
- amelius 9y agoNo, it should probably work like this: 1. User submits hash. 2. Other user submits photo, which matches the hash, which is detected by the system. 3. Facebook employee is notified. Looks at photo. 4. Photo is removed. This way, the employee only looks at the photo if it was actually submitted. If (2) never happened, then (3) never happens.
- danso 9y agoI agree, that sounds like the better solution. Maybe it's not as user-friendly to have the user go through the hashing process client-side (I assume for the average user, it'd require providing a separately-downloaded application, which presents its own security risks), but Facebook hasn't had a spotless record when it comes to manual review workflow. Your suggestion would seem to at least greatly reduce the initial workload (assuming that many/most submitted hashes are matched only much later, if at all).