Skip to content
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

PARAKEET adoption in Chrome #238

Open
drpaulfarrow opened this issue Nov 23, 2021 · 3 comments
Open

PARAKEET adoption in Chrome #238

drpaulfarrow opened this issue Nov 23, 2021 · 3 comments

Comments

@drpaulfarrow
Copy link

Where is the best place to discuss the adoption of PARAKEET in Chrome? It doesn't seem to fit in the FLEDGE meetings or the PARAKEET meetings neatly.

@michaelkleber
Copy link
Collaborator

Seems to me like a fine topic for discussion at PARAKEET meetings, where I and some other Chrome folks participate regularly.

But for a quick answer to the underlying question: In my view there is still a substantial open privacy question about the technique of proxying some user information to various non-trusted servers. This is the core subject of PARAKEET Issue #11 and came up again in 2021-08-25 PARAKEET meeting. Unfortunately, our (Chrome's) efforts to think about this problem have not landed on any approach that prevents joinability with a publisher's first-party notion of user identity.

@drpaulfarrow
Copy link
Author

Thanks for the quick response, Michael. I will bring it up in the next PARAKEET meeting if you're attending. :)

@drpaulfarrow
Copy link
Author

FYI: WICG/privacy-preserving-ads#42

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants