Open wanderview opened 2 years ago
johannhof
commented
2 years ago I'm personally in favor of moving this work into PrivacyCG and I agree that it's separate from the nav-tracking effort (or at least that we need to have another conversation about how we can integrate them while avoiding the overhead for bounce tracking).
cc @jyasskin @pes10k
jyasskin
commented
2 years ago +1 that it makes sense to have a separate repo focused on iterating on bounce tracking mitigations specifically.
pes10k
commented
2 years ago Splitting the two sounds A+ to me too!
On Tue, Oct 4, 2022 at 5:23 PM Jeffrey Yasskin @.***> wrote:
+1 that it makes sense to have a separate repo focused on iterating on bounce tracking mitigations specifically.
— Reply to this email directly, view it on GitHub https://github.com/privacycg/proposals/issues/34#issuecomment-1267647350, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAASV3V7GSFXFCUJGDIOWPLWBSU7JANCNFSM6AAAAAAQYFBMZQ . You are receiving this because you were mentioned.Message ID: @.***>
At TPAC we presented chromium's proposal for bounce tracking mitigations in a number of meetings:
In general I think the feedback was positive and there was some interest from other browser vendors.
Does the privacycg want to host this proposal during incubation? Alternatively, we could host the proposal in WICG.
Note, while bounce tracking mitigations falls under the navigational tracking umbrella, I'm hoping it can be worked on as a separate item from the omnibus nav tracking report. That effort appears to cast a wide net trying to encompass the entire universe of navigational tracking.
If we move this into privacycg, would it be possible to keep bounce tracking as a separate repo and then point to it from the nav tracking report? I just want to avoid blocking bounce tracking on solving all of nav tracking.
Thank you.