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.

Sign up for GitHub

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

Jump to bottom

Enforcement entity viability #64

Open
jwrosewell opened this issue Sep 6, 2021 · 0 comments
Open

Enforcement entity viability #64

jwrosewell opened this issue Sep 6, 2021 · 0 comments

Comments

@jwrosewell
Copy link

Any enforcement entity will have the ability to severally disrupt businesses that operate First Party Sets that are are found to be in violation of the rules. Even if they exercise their role with care they are likely to face legal challenge at some point by the operator of a First Party Set that is found to be violating the rules. The enforcement entity will need a source of funds for legal costs and potential damages.

Consider a large trillion dollar market cap. corporation which operates First Party Sets and is ruled to be in violation of the rules. The damages associated with wrongful enforcement could run into hundreds of billions of dollars. The legal process is likely to take many years to complete and there will be issues over jurisdiction considering First Party Sets do not require entities to enter into contracts with the enforcement entity. Is such an enforcement entity viable in practice?
@jwrosewell jwrosewell mentioned this issue Sep 6, 2021
Closed
@NekR NekR mentioned this issue Sep 22, 2021
Open
dmarti added a commit to dmarti/first-party-sets that referenced this issue Jan 13, 2022
@dmarti
Checking user understanding of shared identity
5d1da86 
Add IEE role in surveys of users to check that they understand
common identity.

(It would be impractical to leave this to the browser and site
author, especially in cases where the browser and site author
have a business relationship that would be influenced by FPS
validity or invalidity.)

Refs WICG#43 WICG#48 WICG#64 WICG#76
@dmarti dmarti mentioned this issue Jan 13, 2022
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@jwrosewell