Transparency serves a bunch of different goals, as described in https://w3ctag.github.io/privacy-principles/#transparency, and the most valuable aren't always to give an end-user more information while they're trying to make a decision. I think the explainer is clear enough in saying that its goal is "providing transparency to the ecosystem" rather than to "provide information to users ... in real-time".
It sounds like the team is open to evolving toward showing information directly to end-users, but that decision should be based on something we expect the users to do with that information in real time, rather than on transparency in the abstract. Jeffrey On Fri, Sep 8, 2023 at 12:28 PM Tom Jones <thomasclinganjo...@gmail.com> wrote: > > so explain to me how you can claim transparency? > > ..tom > > > On Fri, Sep 8, 2023 at 12:26 PM Shivani Sharma <shivani...@chromium.org> > wrote: >> >> >> >> On Fri, Sep 8, 2023 at 2:51 PM Tom Jones <thomasclinganjo...@gmail.com> >> wrote: >>> >>> This statement is under non goals. So I think you need to change that or >>> remove the claim of transparency. >> >> This is specifically about whether the end user can see the result of >> attestation of a given site "in the browser", which at this time is not >> supported. >>> >>> >>> thx ..Tom (mobile) >>> >>> On Fri, Sep 8, 2023, 11:06 AM Shivani Sharma <shivani...@chromium.org> >>> wrote: >>>> >>>> >>>> >>>> On Fri, Sep 8, 2023 at 12:55 PM Tom Jones <thomasclinganjo...@gmail.com> >>>> wrote: >>>>> >>>>> I cannot understand how it is possible to claim transparency with the >>>>> following explanation. It seems completely misleading. >>>>> >>>>> Today, the attestation model does not seek to provide information to >>>>> users within the browser or device in real-time about a developer's >>>>> attestations >>>> >>>> >>>> Thanks for the question! The transparency for attestations is something >>>> that would be added in a future iteration and as mentioned in the earlier >>>> response, that will likely also include a public list of enrolled and >>>> attested sites. >>>>> >>>>> >>>>> >>>>> thx ..Tom (mobile) >>>>> >>>>> On Wed, Aug 30, 2023, 6:16 AM Shivani Sharma <shivani...@chromium.org> >>>>> wrote: >>>>>> >>>>>> Contact emails >>>>>> >>>>>> shivani...@chromium.org, georg...@google.com >>>>>> >>>>>> >>>>>> >>>>>> Explainer >>>>>> >>>>>> https://github.com/privacysandbox/attestation/blob/main/README.md >>>>>> >>>>>> >>>>>> Design document >>>>>> >>>>>> https://docs.google.com/document/d/16PYa6wBBGBbV4YMujkFzBab8s4a7N4PcvpY0Js1qN1k/edit?usp=sharing >>>>>> >>>>>> >>>>>> Specification >>>>>> >>>>>> While the enrollment process itself is not intended to be standardized, >>>>>> the impacted API specifications allow for a user agent defined gating >>>>>> mechanism such as enrollment and attestation. The spec changes for the >>>>>> gated APIs are linked below: >>>>>> >>>>>> >>>>>> Private aggregation (section with note on enrollment) >>>>>> >>>>>> Shared Storage (pull request) >>>>>> >>>>>> Topics (pull request) >>>>>> >>>>>> Attribution reporting API (pull request) >>>>>> >>>>>> Protected Audience (pull requests: 1, 2) >>>>>> >>>>>> >>>>>> >>>>>> Summary and Motivation >>>>>> >>>>>> As the Privacy Sandbox relevance and measurement APIs start ramping up >>>>>> for general availability, we want to make sure these technologies are >>>>>> used as intended and with transparency. The APIs include Attribution >>>>>> Reporting, the Protected Audience API, Topics, Private Aggregation and >>>>>> Shared Storage. As announced in a blog post, a new Developer Enrollment >>>>>> process for Privacy Sandbox relevance and measurement APIs is being >>>>>> introduced across Chrome and Android. This I2S refers to Chrome’s >>>>>> implementation of fetching the enrolled-sites list from the enrollment >>>>>> server (via component updater) and using it to gate access to the >>>>>> Privacy Sandbox APIs. >>>>>> >>>>>> >>>>>> Blink component >>>>>> >>>>>> Blink>PrivateAggregation >>>>>> >>>>>> Blink>Storage>SharedStorage >>>>>> >>>>>> Blink>TopicsAPI >>>>>> >>>>>> Internals > AttributionReporting >>>>>> >>>>>> Blink>InterestGroups >>>>>> >>>>>> >>>>>> Is this feature supported on all six Blink platforms (Windows, Mac, >>>>>> Linux, Chrome OS, Android, and Android WebView)? >>>>>> >>>>>> Supported on all the above platforms except Android WebView. >>>>>> >>>>>> In the initial version, no gated APIs are supported on WebView , with >>>>>> the caveat that the Attribution Reporting API delegates from WebView to >>>>>> Android and would be gated as part of Android’s attestation based gating. >>>>>> >>>>>> >>>>>> Debuggability >>>>>> >>>>>> Console errors: The API surfaces gated on enrollment and attestation >>>>>> will output relevant console error messages if a given site is not >>>>>> allowed to participate/invoke those API surfaces. (Private Aggregation >>>>>> API-related console messages are output during its consumer API >>>>>> enrollment checks e.g. Shared Storage, but could be made more specific >>>>>> in the future). >>>>>> >>>>>> >>>>>> Local override: For local testing, we are providing developer overrides >>>>>> with a Chrome flag and CLI switch: >>>>>> >>>>>> Flag: chrome://flags/#privacy-sandbox-enrollment-overrides >>>>>> >>>>>> CLI: >>>>>> --privacy-sandbox-enrollment-overrides=https://example.com,https://example.co.uk,... >>>>>> >>>>>> >>>>>> Initial public proposal >>>>>> >>>>>> https://github.com/privacysandbox/attestation/blob/main/README.md >>>>>> >>>>>> >>>>>> TAG review >>>>>> >>>>>> Private Aggregation (comment) >>>>>> >>>>>> Shared Storage (comment) >>>>>> >>>>>> Topics (comment) >>>>>> >>>>>> Attribution reporting API (comment) >>>>>> >>>>>> Protected Audience (comment) >>>>>> >>>>>> >>>>>> Risks >>>>>> >>>>>> Interoperability >>>>>> >>>>>> Initially the enrolled and attested sites list will only be available to >>>>>> Chrome browsers. The list is publicly available in the sense that it's >>>>>> shipped to Chrome browsers, but we don't have an official site currently >>>>>> where we post it. However, we could potentially do so in the future and >>>>>> that would enable other browsers to have a consistent gating mechanism. >>>>>> >>>>>> >>>>>> Compatibility >>>>>> >>>>>> No compatibility concerns. The existing APIs either return promises, and >>>>>> will reject for callers that are not enrolled (and they can already >>>>>> reject for other reasons today), or they don’t return anything and the >>>>>> script will not break. >>>>>> >>>>>> >>>>>> Is this feature fully tested by web-platform-tests? >>>>>> >>>>>> No, as there are no plans to standardize this behavior. >>>>>> >>>>>> >>>>>> Tracking bug >>>>>> >>>>>> crbug.com/1448875 >>>>>> >>>>>> >>>>>> Launch bug >>>>>> >>>>>> https://launch.corp.google.com/launch/4260778 >>>>>> >>>>>> >>>>>> Estimated milestones >>>>>> >>>>>> M118 >>>>>> >>>>>> >>>>>> Links to previous Intent discussions >>>>>> >>>>>> Intent to prototype: >>>>>> https://groups.google.com/a/chromium.org/g/blink-dev/c/Zy6uyaTdcJ8 >>>>>> >>>>>> >>>>>> -- >>>>>> You received this message because you are subscribed to the Google >>>>>> Groups "blink-dev" group. >>>>>> To unsubscribe from this group and stop receiving emails from it, send >>>>>> an email to blink-dev+unsubscr...@chromium.org. >>>>>> To view this discussion on the web visit >>>>>> https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CADAcp086BcDbQX%2B2ED-9eU06ZZPH6_MMpB0cr2F0Jf40H4EACw%40mail.gmail.com. > > -- > You received this message because you are subscribed to the Google Groups > "blink-dev" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to blink-dev+unsubscr...@chromium.org. > To view this discussion on the web visit > https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAK2Cwb5WAk215SzY%3DnKOgvhgXNH02TVn4NsOCKwFQoan5ZREjQ%40mail.gmail.com. -- You received this message because you are subscribed to the Google Groups "blink-dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to blink-dev+unsubscr...@chromium.org. To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CANh-dXmOfdAtEFx%2Bdq1oaacZsQefEXRLkSE2P1jOhAPj51FH%2Bw%40mail.gmail.com.
