From a05161c85ad62c9ddd317d4919127018a8b29108 Mon Sep 17 00:00:00 2001 From: Robin Berjon Date: Wed, 28 Jun 2023 11:31:55 -0400 Subject: [PATCH 1/2] 'encourage purpose-built APIs' --- index.html | 24 +++++++++++++++++------- 1 file changed, 17 insertions(+), 7 deletions(-) diff --git a/index.html b/index.html index e2aa6a53..c54d5502 100644 --- a/index.html +++ b/index.html @@ -421,7 +421,13 @@ authors: ['Salomé Viljoen'], href: 'https://www.yalelawjournal.org/feature/a-relational-theory-of-data-governance', publisher: 'Yale Law Journal', - } + }, + 'web-without-3p-cookies': { + title: 'Improving the web without third-party cookies', + authors: ['Amy Guy'], + href: 'https://www.w3.org/2001/tag/doc/web-without-3p-cookies/', + publisher: 'W3C', + }, }, }; @@ -1361,12 +1367,16 @@ the same events it would use to make the page interactive, so we can't block this information access either. - These principles don't describe exactly how to distinguish acceptable - information from information we'd rather not expose. API designers instead - need to balance the harm to users from exposing information against the harm - to users from blocking that exposure. When in doubt, designers should ensure - that different user agents can help their users balance the costs in - different ways. +These principles don't describe exactly how to distinguish acceptable information from information +we'd rather not expose. API designers instead need to balance the harm to users from exposing +information against the harm to users from blocking that exposure. When in doubt, designers should +ensure that different user agents can help their users balance the costs in different ways. + +Some functionality of the web has historically been provided using functional primitives (e.g. +third-party cookies) that can undermine people's privacy. As explained in Improving the web +without third-party cookies ([[?web-without-3p-cookies]]), "It is better to approach [these +use cases] with replacement technologies that are designed-for-purpose and built to respect user +privacy." The following subsections discuss how to review an API proposal that exposes data that provides a new way to infer each of the above categories of information. They explain how From e20567a14a86c6ffbd8bb48473d4c22690ddba23 Mon Sep 17 00:00:00 2001 From: Robin Berjon Date: Wed, 28 Jun 2023 13:00:21 -0400 Subject: [PATCH 2/2] 'lose graf' --- index.html | 5 ----- 1 file changed, 5 deletions(-) diff --git a/index.html b/index.html index c54d5502..84fc5089 100644 --- a/index.html +++ b/index.html @@ -1367,11 +1367,6 @@ the same events it would use to make the page interactive, so we can't block this information access either. -These principles don't describe exactly how to distinguish acceptable information from information -we'd rather not expose. API designers instead need to balance the harm to users from exposing -information against the harm to users from blocking that exposure. When in doubt, designers should -ensure that different user agents can help their users balance the costs in different ways. - Some functionality of the web has historically been provided using functional primitives (e.g. third-party cookies) that can undermine people's privacy. As explained in Improving the web without third-party cookies ([[?web-without-3p-cookies]]), "It is better to approach [these