3 ms·
Sure, Triplebyte made a dumb move here. But “massively privacy violating” is hyperbole. It seems as if everything is considered “private” now. No, not everythi
by wildermuthn 6y ago
Sure, Triplebyte made a dumb move here. But “massively privacy violating” is hyperbole.
It seems as if everything is considered “private” now. No, not everything is private. You interviewing for a job isn’t private unless both parties make it private with a legally binding contract. It is a mistake to wishfully label public information as private simply because we don’t want it to be public. It also makes it harder to talk about true violations of privacy and distracts from understanding the real issues at stake.
What people ought to say, and have often said here, is that it is a violation of trust. People trusted Triplebyte to find them a new job, not lose their current job. That trust was violated not by an invasion of privacy — it is their data as much as it is ours — but a violation of using that data in a harmful way.
Privacy isn’t the problem here. The problem is with whatever broken processes led to this bad product and poor decision.
- stanleydrew 6y ago> You interviewing for a job isn’t private unless both parties make it private with a legally binding contract. I would gently suggest that you look into the idea of "reasonable expectation of privacy" which has a long history in the courts.