On Tuesday, February 4, 2025 at 9:20:37 PM UTC+1 Dan McArdle wrote:
Contact emailsdmcar...@chromium.org Explainerhttps://github.com/patcg-individual-drafts/private- aggregation-api#limiting-the-number-of-contributions-per-report Specificationhttps://github.com/patcg-individual-drafts/private- aggregation-api/pull/164/files Summary Enables Shared Storage callers to customize the number of contributions per Private Aggregation report. This feature enables Shared Storage callers to configure per-context contribution limits via a new field, `maxContributions`. Callers set this field to override the default number of contributions per report — larger and smaller numbers will both be permitted. Chrome will accept values of `maxContributions` between 1 and 1000 inclusive; larger values will be interpreted as 1000. Can you expand a bit on what this limit is protecting against, and why it's fine to remove it? What are the tradeoffs here? Also, why would developers want to reduce the limit? Due to padding, the size of each report's payload will be roughly proportional to the chosen number of contributions per report. We expect that opting into larger reports will increase the cost of operating the Aggregation Service. Protected Audience callers will not be affected by this feature. However, we are planning to add support for customizing the number of contributions for Protected Audience reports in future features. Blink componentBlink>PrivateAggregation <https://issues.chromium.org/issues?q=customfield1222907:%22Blink%3EPrivateAggregation%22> TAG reviewhttps://github.com/w3ctag/design-reviews/issues/846 TAG review statusDeclined Risks Interoperability and Compatibility None *Gecko*: No signal (https://github.com/mozilla/ standards-positions/issues/805) *WebKit*: No signal (https://github.com/WebKit/ standards-positions/issues/189) *Web developers*: Positive (https://github.com/patcg- individual-drafts/private-aggregation-api/issues/81) *Other signals*: WebView application risks Does this intent deprecate or change behavior of existing APIs, such that it has potentially high risk for Android WebView-based applications? None Debuggability No new debug capabilities beyond the existing internals page (chrome://private-aggregation-internals) and debug mode. These capabilities will reflect the variable number of contributions across payloads. Will this feature be supported on all six Blink platforms (Windows, Mac, Linux, ChromeOS, Android, and Android WebView)? All but WebView Is this feature fully tested by web-platform-tests <https://chromium.googlesource.com/chromium/src/+/main/docs/testing/web_platform_tests.md> ?Yes Flag name on about://flagsNone Finch feature namePrivateAggregationApiMaxContributions Requires code in //chrome?False Tracking bughttps://crbug.com/376707230 Launch bughttps://launch.corp.google.com/launch/4357940 Estimated milestonesShipping on desktop134Shipping on Android134 Anticipated spec changes Open questions about a feature may be a source of future web compat or interop issues. Please list open issues (e.g. links to known github issues in the project for the feature specification) whose resolution may introduce web compat/interop risk (e.g., changing to naming or structure of the API in a non-backward-compatible way). None Link to entry on the Chrome Platform Statushttps://chromestatus.com/ feature/5189366316793856?gate=5179705727385600 This intent message was generated by Chrome Platform Status <https://chromestatus.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 visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/07204796-80ab-48e8-9362-339ea8aefbc5n%40chromium.org.
