Related Website Sets - Revision history

Tom: /* Other Material */

2024-02-16T00:40:17Z

‎Other Material

Tom: /* Reference */

2024-02-16T00:39:23Z

‎Reference

Tom: /* Context */

2024-02-16T00:35:31Z

‎Context

Tom: /* Reference */

2023-10-09T17:57:17Z

‎Reference

Tom: /* Reference */

2023-10-09T17:56:45Z

‎Reference

Tom: /* Current OIDC Front Channel Flow */

2023-10-09T17:55:35Z

‎Current OIDC Front Channel Flow

Tom at 17:55, 9 October 2023

2023-10-09T17:55:15Z

Tom: /* Context */

2023-10-09T17:54:46Z

‎Context

Tom: /* Full Title or Meme */

2023-10-09T17:54:00Z

‎Full Title or Meme

Tom: Tom moved page First-Party Set to Related Website Sets: Google changed the name to be more representative

2023-09-29T18:28:23Z

Tom moved page First-Party Set to Related Website Sets: Google changed the name to be more representative

@@ Line 171: / Line 171: @@
 <references />
 ===Other Material===
-* The wiki page [[First-Party Set]] contains information on why [[Related Website Sets]] are useful.
 [[Category: Browser]]
 [[Category: User Agent]]
 [[Category: Privacy]]

@@ Line 169: / Line 169: @@
 We would welcome other browsers taking this same approach to cross-site cookie compatibility, instead of silently allowing cross-site cookies between select pairs of sites. But we don’t think such a list needs a site-controlled extension mechanism, and we don’t think it belongs in standards, since our goal is to drive the list to empty, as with any other site-specific compatibility quirk.
 ==Reference==
+<references />
 [[Category: Browser]]
 [[Category: User Agent]]
 [[Category: Privacy]]

@@ Line 3: / Line 3: @@
 ==Context==
-The [[First-Party Set]] (FPS) is a proposal in W3C to retain some of the advantages of this practice while limiting user tracking. That effort was renamed on 2023-08-31 to [[Related Website Sets]] as the APIs became more complex.<ref>Helen Cho, ''Related Website Sets - the new name for First-Party Sets in Chrome 11 ''</ref> At that time the domain limit was increased to 5 domains, which is small compared to the number of sites that are owned by the large corporations can be in the hundreds.<blockquote>RWS is designed to minimize disruptions to specific user-facing features once Chrome starts limiting access to third-party cookies by default. Our goal is to allow users to browse the web with minimal disruption while still upholding the privacy goals of the Privacy Sandbox. To strike this balance, RWS targets specific use cases related to website functionality.</blockquote>
+The [[First-Party Set]] (FPS) is a proposal in W3C to retain some of the advantages of this practice while limiting user tracking. That effort was renamed on 2023-08-31 to [[Related Website Sets]] as the APIs became more complex.<ref>Helen Cho, ''Related Website Sets - the new name for First-Party Sets in Chrome 11 ''</ref> At that time the domain limit was increased to 5 domains, which is small compared to the number of sites that are owned by the large corporations can be in the hundreds.<blockquote>RWS is designed to minimize disruptions to specific user-facing features once Chrome starts limiting access to third-party cookies by default. Our goal is to allow users to browse the web with minimal disruption while still upholding the privacy goals of the [[Privacy Sandbox]]. To strike this balance, RWS targets specific use cases related to website functionality.</blockquote>
-* Some privacy focused browsers, like Safari, Fire Fox and Brave, have started blocking access by Third-Parties in 2021. Google is more dependent on advertising revenue and so continues to look for an alternate way that will not result in massive revenue losses like the [https://www.businessinsider.com/facebook-blames-apple-10-billion-loss-ad-privacy-warning-2022-2 $10 billon loss experienced by FaceBook].
+* Some privacy focused browsers, like Safari, Fire Fox and Brave, have started blocking access by Third-Parties in 2021. Google is more dependent on advertising revenue and so continues to look for an alternate way that will not result in massive revenue losses like the [https://www.businessinsider.com/facebook-blames-apple-10-billion-loss-ad-privacy-warning-2022-2 $10 billion loss experienced by FaceBook].
 ===Current OIDC Front Channel Flow===
 * [[OpenID Connect]] was an enormously successful protocol because it allowed [[Front-Chanel]] communications of user sign-in information between a [[Identifier or Attribute Provider]] and a [[Relying Party]].

← Older revision		Revision as of 17:57, 9 October 2023
Line 172:		Line 172:
	[[Category: Browser]]		[[Category: Browser]]
	[[Category: User Agent]]		[[Category: User Agent]]
		+	[[Category: Privacy]]

← Older revision		Revision as of 17:56, 9 October 2023
Line 170:		Line 170:
	==Reference==		==Reference==

		+	[[Category: Browser]]
	[[Category: User Agent]]		[[Category: User Agent]]

@@ Line 1: / Line 1: @@
 ==Full Title or Meme==
-The [[Trusted First Party]] is typically the human user of a [[User Agent]] such as a [[Browser]]. While it has been the practice up to 2021 to allow [[Cookies]] stored by one party in a session to be read by a [[Third Party]], that has been explored but advertising and is scheduled to be shut down. The [[First-Party Set]] (FPS) is a proposal in W3C to retain some of the advantages of this practice while limiting user tracking.
+The [[Trusted First Party]] is typically the human user of a [[User Agent]] such as a [[Browser]]. While it has been the practice up to 2021 to allow [[Cookies]] stored by one party in a session to be read by a [[Third Party]], that has been exploited by advertising and is scheduled to be shut down.
 ==Context==

← Older revision	Revision as of 18:28, 29 September 2023
(No difference)