generated from privacycg/template
-
Notifications
You must be signed in to change notification settings - Fork 14
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
Define navigational tracking as "without the user's knowledge"? #8
Comments
I made a pull request to start adding this into the document. IMO Tightly defining "good" and "bad" is an important next step. |
jyasskin
added
agenda+
Request to add this issue to the agenda of our next telcon or F2F
and removed
agenda+
Request to add this issue to the agenda of our next telcon or F2F
labels
Sep 20, 2021
jyasskin
added
the
agenda+
Request to add this issue to the agenda of our next telcon or F2F
label
Oct 13, 2021
jyasskin
removed
the
agenda+
Request to add this issue to the agenda of our next telcon or F2F
label
Oct 20, 2021
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
@johannhof pointed out that federated login intrinsically "identif[ies] that a user on one site is the
same person as a user on another site", which is how #2 defines navigational tracking. If we want to say that navigational tracking is always bad, we need some carve-out for cases where the user intentionally copies their identity using a navigation.
Alternatively, we could say that federated login is tracking, but a kind that's not bad. Then we might need yet another term to be the thing we think is bad.
The text was updated successfully, but these errors were encountered: