@jack Do you feel that those orgs (#Google, #Twitter or #Facebook) are truly open, even if their license model is? It seems as though the #opensource APIs and SDKs they might have are doorways to a closed world. And that they are directly connected to losses of #privacy, which is often a reason to use open source software.
What are your thoughts on that?
Given that the OSI definition (criterion 6) and FSF software freedoms (freedom 0) grant people rights to use software for *any* reason, it follows that people may use (F)OSS for privacy-destroying reasons.
Obviously the fact that a (F)OSS project can be forked to remove privacy-destructive functionality is a big plus in its favour, but (F)OSS alone is not enough.
Of course, *all* developers should be aware of the privacy implications of using any code, just like they should be aware of the copyright license that code is under.
(And, in fact, the GDPR does place an obligation to write software that includes data protection by design and by default as one mechanism of ensuring this but enforcement of Art. 25 is not going to be exactly... robust)
@jack Thank you. And we do get that we are essentially arguing semantics, but feel it's necessary to understand the impact of going into Open Source projects with our eyes closed on privacy.
Appreciate you taking the time to comment.
My home on the Fediverse.