From 3b958ea870f5d7e4ef8d5b24c9b85dab10017e63 Mon Sep 17 00:00:00 2001 From: groundcat <11240246+groundcat@users.noreply.github.com> Date: Sat, 14 Dec 2024 01:58:24 -0500 Subject: [PATCH 1/2] Update cookies documentation --- learn/index.html | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/learn/index.html b/learn/index.html index 040d2e7..256e229 100644 --- a/learn/index.html +++ b/learn/index.html @@ -45,7 +45,7 @@

Since there was and remains no algorithmic method of finding the highest level at which a domain may be registered for a particular top-level domain (the policies differ with each registry), the only method is to create a list. This is the aim of the Public Suffix List.

- Software using the Public Suffix List will be able to determine where cookies may and may not be set, protecting the user from being tracked across sites. + Software using the Public Suffix List will be able to determine cookie inheritance boundaries between domains, preventing cookies set on one domain from being accessible to other domains under the same public suffix. This protects users from cross-domain tracking while still allowing individual domains to set their own cookies.

As well as this, the Public Suffix List can also be used to support features such as site grouping in browsers. By knowing where the user-controlled section of the domain name begins and ends, browsers can group cookies and history entries by site in a way that couldn't easily be done before. From 2f5207afbfd1ab15cef141f78f10d0d535a1836a Mon Sep 17 00:00:00 2001 From: groundcat <11240246+groundcat@users.noreply.github.com> Date: Sat, 14 Dec 2024 11:37:58 -0500 Subject: [PATCH 2/2] Update index.html --- learn/index.html | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/learn/index.html b/learn/index.html index 256e229..2ffe101 100644 --- a/learn/index.html +++ b/learn/index.html @@ -45,7 +45,7 @@

Since there was and remains no algorithmic method of finding the highest level at which a domain may be registered for a particular top-level domain (the policies differ with each registry), the only method is to create a list. This is the aim of the Public Suffix List.

- Software using the Public Suffix List will be able to determine cookie inheritance boundaries between domains, preventing cookies set on one domain from being accessible to other domains under the same public suffix. This protects users from cross-domain tracking while still allowing individual domains to set their own cookies. + Software using the Public Suffix List will be able to determine cookie inheritance boundaries between domains, preventing cookies set on one domain from being accessible to other domains under the same public suffix. This protects users from cross-domain cookies setting while still allowing individual domains to set their own cookies.

As well as this, the Public Suffix List can also be used to support features such as site grouping in browsers. By knowing where the user-controlled section of the domain name begins and ends, browsers can group cookies and history entries by site in a way that couldn't easily be done before.