Re: [w3ctag/design-reviews] Shared Storage API (Issue #747)

Hi @jkarlin, thank you for the answers above. The following is hard to follow as we don't seem to have all the context you do. Can you try and answer the original question about _how this proposal fits into Privacy Sandbox_ more directly?

Shared Storage has three components. The first is the unpartitioned storage API (write data from anywhere, read it only in an isolated worklet). The other two components are the private ways in which data can leave the worklet. Private Aggregation API is a measurement API, allowing for measurement of things like ad reach, demographics, or cross-site debug reporting.

One of the main sections that's missing for me is about user needs. Can you elaborate and ideally add these to the explainer? See https://tag.w3.org/explainers/. The explainer talks about "including cross-origin A/B experiments and user measurement" – can you elaborate these in the form of user needs definition - from the user's perspective, how this benefits the end user.

The output gaiting of the API seems to be entirely based on budgeting. Can you confirm if this is the case or are we missing some other controls?


-- 
Reply to this email directly or view it on GitHub:
https://github.com/w3ctag/design-reviews/issues/747#issuecomment-1502037976
You are receiving this because you are subscribed to this thread.

Message ID: <w3ctag/design-reviews/issues/747/1502037976@github.com>