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

Encourage purpose-built APIs, fix #175 #295

Merged
merged 2 commits into from
Jun 28, 2023
Merged

Encourage purpose-built APIs, fix #175 #295

Changes from 1 commit
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
a05161c
'encourage purpose-built APIs'
Jun 28, 2023
e20567a
'lose graf'
Jun 28, 2023
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
24 changes: 17 additions & 7 deletions index.html
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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',
},
},
};
</script>
Expand Down Expand Up @@ -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 <em>Improving the web
without third-party cookies</em> ([[?web-without-3p-cookies]]), "<em>It is better to approach [these
use cases] with replacement technologies that are designed-for-purpose and built to respect user
privacy.</em>"

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
Expand Down