You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The current TURTLEDOVE states that the interest groups names may only be between 00-99. I propose that we allow a higher limit. It’s common practice for groups of publishers to work together to create large scale interest groups. These groups will be in taxonomies with tens of thousands of other groups. To support this use case, the limit to the number of interest groups should be at least 500,000.
The text was updated successfully, but these errors were encountered:
The mention of 00-99 in the current explainer is only one possibility for how to address a larger question: Ensuring that the interest groups used for ad targeting are not too small.
So as the explainer says, first "Browsers and the industry should reach some consensus on whether there should be a minimum threshold for ad audiences, and on what size any such threshold should be." Once we know what the goal is, we can try to figure out what the browser should do to enforce it.
I concur that limiting the number of interest groups per domain is a pretty crude way to force interest groups to be large, and I'd like us all to agree on something better.
Closing this issue as it represents past design discussion that predates more recent proposals. I believe some of this feedback was incorporated into the Protected Audience (formerly known as FLEDGE) proposal. If you feel further discussion is needed, please feel free to reopen this issue or file a new issue.
The current TURTLEDOVE states that the interest groups names may only be between 00-99. I propose that we allow a higher limit. It’s common practice for groups of publishers to work together to create large scale interest groups. These groups will be in taxonomies with tens of thousands of other groups. To support this use case, the limit to the number of interest groups should be at least 500,000.
The text was updated successfully, but these errors were encountered: