3 ms·
Great idea, absolutely horrible implementation even as an MVP. Never in a million years would I trust that kind of data residing on Facebooks servers even flee
by lukejduncan 9y ago
Great idea, absolutely horrible implementation even as an MVP.
Never in a million years would I trust that kind of data residing on Facebooks servers even fleetingly. Years back, Facebook allowed you to have private profile photos. My then-girlfriend-now-wife has a picture of the two of us as hers which for cultural and religious reasons she had private since we hadn’t decided to tell her parents yet. Facebook decided without telling anyone one day that Facebook photos were now public. She hasn’t spoken to her father since that day. Facebook can and will do whatever they want with the data they have on you. Maybe permissions change on messenger (or there’s a bug) and data from this flow leaks. Maybe a year from now this flow still exists but messager makes all picture uploads a soft delete because they want to keep things as training data. Maybe the upload gets replicated to their CDNs in a way that is discoverable and recoverable. Maybe documentation for this manual process outlives the software, someone finds it, and uploads a picture only to find out they did it in the wrong place that now has no guarantees of even an effort for privacy.
That’s a lot of maybes for something so sensitive. Facebook doesn’t deserve your trust with this kind of data. They should come up with something where the hashing happens locally and the user never has to put faith in them to begin with.