Skip to content
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

Shared Storage #57

Closed
jkarlin opened this issue Jun 9, 2022 · 8 comments
Closed

Shared Storage #57

jkarlin opened this issue Jun 9, 2022 · 8 comments

Comments

@jkarlin
Copy link

jkarlin commented Jun 9, 2022

Introduction

In order to prevent cross-site user tracking, browsers are partitioning all forms of storage (cookies, localStorage, caches, etc). But, there are many legitimate use cases currently relying on unpartitioned storage that will vanish without the help of new web APIs. We’ve seen a number of APIs proposed to fill in these gaps (e.g., Conversion Measurement API, Private Click Measurement, Storage Access, Trust Tokens, TURTLEDOVE, FLoC) and some remain (including cross-origin A/B experiments and user measurement). We propose a general-purpose, low-level API that can serve a number of these use cases.

The idea is to provide a storage API (named Shared Storage) that is intended to be unpartitioned. Origins can write to it from their own contexts on any page. To prevent cross-site tracking of users, data in Shared Storage may only be read in a restricted environment that has carefully constructed output gates. Over time, we hope to design and add additional gates.

Read the complete explainer.

Feedback (Choose One)

I welcome feedback in this thread, but encourage you to file bugs against the explainer.

@SpaceGnome
Copy link

Definitely interested in Shared Storage API, including experimenting with it for addressing some anti-abuse use cases affected by the loss of 3P cookies.

@jonathanKingston
Copy link
Member

I think it's interesting enough to prototype (This isn't by any means an endorsement at all). I think it's a little unfortunate that it's coupled to fenced frames and the aggregation API

@supanate7
Copy link

I am also interested in the anti-abuse potential of the Shared Storage API .

@piwanczak
Copy link

piwanczak commented Jun 17, 2022

We're also interested in this proposal - frequency capping/measurement use case.
EDIT: just to clarify: statement is both personal and as a part of RTB House organization

@yoavweiss
Copy link
Collaborator

yoavweiss commented Jun 17, 2022

@jonathanKingston @supanate7 @piwanczak - Can you clarify if your support for exploring this use case is personal or in the name of an organization? (and if it's the latter, which organization)

@yoavweiss
Copy link
Collaborator

Thanks @piwanczak for clarifying. That seems like enough support to move the repo over to the WICG.

@yoavweiss
Copy link
Collaborator

The repo now lives under https://github.com/WICG/shared-storage
Happy incubation!!

@jonathanKingston
Copy link
Member

My views were personal, I think my organisation hasn't formed a concrete opinions yet.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

6 participants