dcallies

5 ms·

1.
by dcallies 5y ago
Yup, you got it, the content itself will remain only in the device, the hashing is done in-browser, and the only part of the original content that makes it into the system is the hashes. Once a platform that is part of the program downloads
2.
by dcallies 5y ago
It’s somewhere in the FAQ at https://stopncii.org/faq/ , but It’s PDQ for photos ( https://github.com/facebook/ThreatExchange/tree/main/pdq ) and MD5 for videos. PDQ is resistant to so
3.
by dcallies 5y ago
Yup, PDQ ( https://github.com/facebook/ThreatExchange/tree/main/pdq ) and MD5- https://stopncii.org/faq/ . MD5 is a cryptographic hash, which means that even a single bit changed gives
4.
by dcallies 5y ago
It’s a real challenge - you can try and do more pre-processing on a submitter’s device to try and avoid mistakes or malicious use of the system. The big limitations are: 1. How much processing time can you put on what might be a mobile phon
5.
by dcallies 5y ago
Another commenter (“ahahahahah”) described it as the equivalent of a “report image” button, which I thought was apt - it preemptively reports on all the platforms that are participating with StopNCII. It comes down to each platform: Meta ha
6.
by dcallies 5y ago
I like the comparison of the program to hitting “report image” on a platform. Advantages of StopNCII is that you can report proactively, and to report it to all the participating platforms at the same time. Misuse of the StopNCII platform i
7.
by dcallies 5y ago
Hey everyone! I’m a software engineer at Meta, and I helped work on the program that the newsroom post is about. Sorry I’m late, I only just found the thread! I might be able to answer some questions about the technology - many of the build