3 ms·
> - The user uses a JS solution to hash the images on the client, without the image being uploaded You have to trust facebook in either case, each time you do
by the8472 9y ago
> - The user uses a JS solution to hash the images on the client, without the image being uploaded
You have to trust facebook in either case, each time you do it. Either to handle your nude pics properly or to serve you javascript that does what they claim it does, every single time.
On the other hand an open source desktop application only needs to be audited once and then can be validated based on a hash.
In browser crypto is not a solution if you want to minimize the needed trust.
- oh_sigh 9y agoNobody wants to run a desktop application given to them from facebook
- the8472 9y ago> only needs to be audited once and then can be validated based on a hash. I thought I covered that concern, but I neglected to mention that it should be open source so everyone can audit it.
- statictype 9y agoIt’s better than sending them NSFW photos for human review
- hnzix 9y agoBut it could force autoinstall from the website and autoscan your drives then preupload your nudie pics and tag them with your name. How convenient! If all your friends are using it then it must be safe right?
- zodiac 9y agoYou could examine network traffic to confirm that not enough data is sent to reconstitute the picture
- icebraining 9y agoYou'd have to check every single time, since the code can change at any time.
- the8472 9y agoThey could save it indexedb or localstorage and send it later. So now you have three things to inspect. They could even shunt it to a different domain within the browser through iframes and messaging. Now you have another thing to watch. There aren't even any devtools to watch that. The cheese is full of holes.