-
Notifications
You must be signed in to change notification settings - Fork 16
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Remove the endorsement of exchanging personal data for content. #451
Conversation
This reverts commit 254a8d0.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm not sure if simply removing the text is the best approach, but I don't have alternative text to suggest. I can live with this change.
Hey @jyasskin I haven't been able to participate in this forum as much as I'd like so sorry if this is me wandering in out of my element...is the objection to this language a) that it belongs somewhere but just not here (like maybe it belongs in a Private Advertising Tech group but not the Privacy [no modifier] Group) or b) a more foundational objection? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
yes. re-reviewing this I'm not sure how this got in here in the first place. :/
@torgo This was a modified version of a general suggestion from the formal objection ( #431 #436 ) I tried to split out the really problematic case (where the power relationship between the user and the site does not allow for a meaningful choice to share data) from the case that is more like a subscription or paid download, but at a price of zero. |
@thegreatfatzby If I understand it correctly, it's a more foundational objection, wondering whether data access is so abusable that it should never be a valid thing to trade for access. I think we might be able to agree on something on this topic in a future version of this document, and if the objector wants to insist on this, the Council could always agree to reinstate this wording. As you suggest, it might be productive for an advertising group to propose the next iteration of wording, with an argument that the privacy impacts are reasonable. Seeing general consensus from the TAG, and remembering the sense that the task force would probably not have added this if I hadn't argued in favor of it, I'm going to merge this. |
SHA: c8a4709 Reason: push, by jyasskin Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
This reverts #436 and commit 254a8d0. Some folks on the TAG objected to the change.
Preview | Diff