Comment by ziddoap
3 years ago
>Due diligence is expected among a mature population.
I wholly agree.
But we're quickly approaching (and in some cases, past) the point where proper due diligence requires a 4-year post-secondary education in a related CS field, if not more.
We're talking about products that take multiple domain experts several years of collaboration to create. How is it reasonable to expect my mechanic, accountant, etc. to do their due diligence on how that product processes their data, especially when it's processed in a black-box created by several other domain experts, and their only source of information is purposefully opaque terms written by lawyers?
> proper due diligence requires a 4-year post-secondary education
I don't think that's the case here or indeed very commonly. You don't necessarily have to understand implementation details if some core tenet of popular ethics is being violated. One key feature of the domain -- namely that you don't own "your data" and so you don't get to decide what happens with it -- is pretty clearly in violation of principles that the vast majority of Westerners would at least profess to hold. Beyond the motivating principle that third parties should be required to receive explicit whitelist access to use privately-owned data, "implementation details" refers mostly to policy and enforcement, not really technologies.