News for hackers. Stuff that matters.

A comment on Using the Topics API (Chrome Only, Opposed by Firefox/Safari). Parent comment

Re:Using the Topics API (Chrome Only, Opposed by Firefox/Saf... by afavour on Sunday September 15, 2024 @11:06PM (#41552380)
Narrator: Google was, in fact, not getting rid of third party cookies
[ Parent | on HN ]
Re:Using the Topics API (Chrome Only, Opposed by Firefox/Saf... by luckydata on Monday September 16, 2024 @01:32AM (#41553041)
Note the plan was abandoned to satiate UK regulators, not a decision made unilaterally by Google
[ Parent | on HN ]
Re:Using the Topics API (Chrome Only, Opposed by Firefox/Saf... by afavour on Monday September 16, 2024 @08:05AM (#41555192)
No. Lets be clear: Google absolutely could have continued in their plan. They’d be doing what Apple and Mozilla already do today, after all. The problem is that Google’s alternatives to allow tracking by ad providers have run afoul of regulators and Google isn’t prepared to lose that ad revenue.
[ Parent | on HN ]
Re:Using the Topics API (Chrome Only, Opposed by Firefox/Saf... by IshKebab on Monday September 16, 2024 @01:46PM (#41558581)
Apple and Mozilla can do it because they don't have as much browser market share as Google, and they don't run their own advertising businesses.
[ Parent | on HN ]
Re:Using the Topics API (Chrome Only, Opposed by Firefox/Saf... by afavour on Monday September 16, 2024 @04:11PM (#41560202)
Yeah it's almost like there's an inherent conflict in one company being the leading browser provider and advertising broker!
[ Parent | on HN ]
Re:Using the Topics API (Chrome Only, Opposed by Firefox/Saf... by magicalhippo on Monday September 16, 2024 @03:25AM (#41553598)
Now you made me want to play The Stanley Parable again...
[ Parent | on HN ]