Google Chrome coders really, truly, absolutely ready to cull third-party cookies from 2024Lee Duna@lemmy.nz to Technology@lemmy.world – 189 points – 8 months agotheregister.com48Post a CommentPreviewYou are viewing a single commentView all commentsShow the parent commentToday's dev call consisted of how iframes are tanking subresource integrity audit.Nah, no need for that. We'd just tell our customer to enable third-party cookies.A real conversation I had last week about ad blockers, Google vignette ads, and our sites becoming unresponsive. FMLReal shit. I spent like a week debugging until I was told "yeah make sure you enable that setting".
Today's dev call consisted of how iframes are tanking subresource integrity audit.Nah, no need for that. We'd just tell our customer to enable third-party cookies.A real conversation I had last week about ad blockers, Google vignette ads, and our sites becoming unresponsive. FMLReal shit. I spent like a week debugging until I was told "yeah make sure you enable that setting".
Nah, no need for that. We'd just tell our customer to enable third-party cookies.A real conversation I had last week about ad blockers, Google vignette ads, and our sites becoming unresponsive. FMLReal shit. I spent like a week debugging until I was told "yeah make sure you enable that setting".
A real conversation I had last week about ad blockers, Google vignette ads, and our sites becoming unresponsive. FMLReal shit. I spent like a week debugging until I was told "yeah make sure you enable that setting".
Today's dev call consisted of how iframes are tanking subresource integrity audit.
Nah, no need for that.
We'd just tell our customer to enable third-party cookies.
A real conversation I had last week about ad blockers, Google vignette ads, and our sites becoming unresponsive. FML
Real shit.
I spent like a week debugging until I was told "yeah make sure you enable that setting".