-
Notifications
You must be signed in to change notification settings - Fork 2
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
Concentrate on use cases #26
base: main
Are you sure you want to change the base?
Conversation
Not solutions. We don't need to over-index on the solution part, particularly when we have just one solution that is really purpose-limited in the way we describe. I like CHIPS, but it is not an API that does purpose limitation.
I don't hate it, and if others agree I am happy to move it in this way. However, I think it's stronger to list some concrete examples of technologies that the TAG has reviewed positively (or which have positive consensus on) that are replacing functionality currently serviced by 3rd party cookies. |
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.
This seems like a net improvement to me, though I was skeptical of the idea of this change before seeing this PR. This text is actually stronger than the original, short list of examples, because it identifies a broader set of use cases that warrant investigation.
Coming to this late (thanks @torgo for the reminder of this PR, and to @martinthomson for the wording). I also think this is an improvement, and would be happy for it to be merged immediately. I also think that expanding it to a bulleted list of use cases, with links to existing or proposed solutions, and noting their level of maturity/adoption, would be a good thing to follow up with soon. |
Ref #30. |
Not solutions. We don't need to over-index on the solution part, particularly when we have just one solution that is really purpose-limited in the way we describe.
I like CHIPS, but it is not an API that does purpose limitation.