-
The "Privacy" Sandbox & the "end" of 3rd-party cookies 🤔 "As part of the work on First-Party Sets, Chrome is implementing and extending the Storage Access API allowing a site to request access to their cookies in a third-party context" 😈 @ericlaw/1653931704514494465Permalink On twitter.com
♻️ 7 Retweets
❤️ 13 Favorites
Mood +1 🙂
-
Open bar for publishers cooperatives (multiple publishers belonging to different organizations, sharing your data) 😜 Self-declare the sets, Google lax approach will let you do whatever you want (and adtech people are imaginative) github.com/GoogleChrome/first-party-sets/blob/main/FPS-Submission_Guidelines.md#set-formation-requirements 👏Permalink On twitter.com
♻️ 1 Retweets
❤️ 1 Favorite
Mood +7 🙂
-
First-Party Sets: Tearing Down Privacy Defenses Just as They're Being Built brave.com/web-standards-at-brave/8-first-party-sets/ 👀On twitter.com
❤️ 1 Favorite
Mood 0
-
"We have decided to drop First-Party Sets as a Work Item in the group... with regards to the concerns about the privacy properties of First-Party Sets that were raised in issue 88" 🤔 lists.w3.org/Archives/Public/public-privacycg/2022Jun/0003.htmlPermalink On twitter.com
❤️ 1 Favorite
Mood -1 🙁
-
A privacy harming feature, rejected by most browser vendors, rejected from the W3C and... now shipped in Chrome as part of the "Privacy" Sandbox lists.w3.org/Archives/Public/public-privacycg/2022Jun/0003.html 🚀Permalink On twitter.com
❤️ 1 Favorite
Mood -2 🙁