Live data from Hacker News

A new path for Privacy Sandbox on the web

privacysandbox.com

61–70 of 71 posts

Re: A new path for Privacy Sandbox on the web

#61
"Privacy Sandbox" by Google.

See also:

1. Exxon's "Advanced Recycling"

2. Phillip Morris' "Smoke Free"

> The Ministry of Peace concerns itself with war, the Ministry of Truth with lies, the Ministry of Love with torture and the Ministry of Plenty with starvation. These contradictions are not accidental, nor do they result from ordinary hypocrisy: they are deliberate exercises in doublethink.

Re: A new path for Privacy Sandbox on the web

#62
post #20
post #18

A major problem with blocking third party cookies is that it kills any embeddable logged in experience. Think payment gateway widgets that would now require you to login every time you want to make a purchase, or youtube embeds that would no longer recognize your premium subscription and roll ads across the web if if you pay for none, etc.

That's what browsers are working on Federated Credential Management APIs for: https://developer.mozilla.org/docs/Web/API/FedCM_API

It would have been nice to have a replacement for it ready and shipped before they started getting removed.

Re: A new path for Privacy Sandbox on the web

#63

Earlier quoted context omitted.

In spite of Manifest V3 being a shit show, I continue to see all manners of evidence that Google wants genuine honest reform for user privacy. The attitude & negativity is at severely problematic levels, and Google actually gets that improvement & reform is necessary to keep going for another decade without some kind of boil over/explosion. I agree that Chrome in theory shouldnt be a part of Google. But generally I t…

> In spite of Manifest V3 being a shit show, I continue to see all manners of evidence that Google wants genuine honest reform for user privacy. The attitude & negativity is at severely problematic levels, and Google actually gets that improvement & reform is necessary to keep going for another decade without some kind of boil over/explosion. > I agree that Chrome in theory shouldnt be a part of Google. But generally…

Everyone else disable 3rd party cookies but has unspecified/undocumented workarounds & carve-outs that they've had to keep expanding on. It broke a ton of login and valid diagnostic systems.

Google's playing hard mode by trying to actually specify how the new world is going to work. A third the current explainers they are working on relate to trying to get login flows working again. https://github.com/orgs/explainers-by-googlers/repositories . Google's commitment to specifying & standards has made this much harder.

Meanwhile they also have vastly more scrutiny. I'm not sure if the UK's CMA or ICO have updated the public on what their concerns are, but the UK in particular has come out strongly saying that they get full say in what Google does here, in one of the strongest repudiations of the ideas of the Declaration of Independence of Cyberspace that the world has seen.

And meanwhile the slithering reptiles at the IAB are generating as much chaff nonsense and outcry as they can against Google, and putting forward proposals about making sure advertisers can tell what you had for breakfast & whether or not you flossed last night.

This is the least enviable spot to be in. The web has to change but trying to get the mandate for it to happen is neigh on impossible; giving users options & capabilities to pick seems like the only option at this stage.

Re: A new path for Privacy Sandbox on the web

#64

I can't tell from the announcement or official site. Is CHIPS still a thing? Do I still have to partition all my cookies I write on one domain I own to work on another domain I own? https://developers.google.com/privacy-sandbox/3pcd/chips

Yes CHIPS is still a thing. As far as I can tell, nothing changes except that Chrome will not disable third party cookies by default. It will remain a preference that users can choose.

Re: A new path for Privacy Sandbox on the web

#65
post #20

Earlier quoted context omitted.

That's what browsers are working on Federated Credential Management APIs for: https://developer.mozilla.org/docs/Web/API/FedCM_API

It would have been nice to have a replacement for it ready and shipped before they started getting removed.

They haven't gotten removed yet, just compartmentalised and some important existing ones grandfathered in, I believe. And none of that has happened in Chrome, as far as I know.

Re: A new path for Privacy Sandbox on the web

#66
So let me get this right...

Google introduces a lot of "privacy protecting" ideas like removing third party cookies, moving extensions to manifest v3, etc. Then they backtrack on removing third party cookies and keep the manifest v3 roadmap.

Essentially, they are getting their cookies and eating it too.

Re: A new path for Privacy Sandbox on the web

#67

Interesting timing for this. Chrome 127 (releases today) disables Manifest V2 extensions. When uBlock Lite runs out of rules, unwanted advertising will be back on the web. With all due respect to the Chrome team, where is the leadership, competence, or moral courage at Google? It looks like they are announcing to the world today that they care more about advertisers than users.

While I agree with you…

> It looks like they are announcing to the world today that they care more about advertisers than users.

Where does 78% of their revenue come from? I’m not sure why you’re surprised.

Re: A new path for Privacy Sandbox on the web

#69
post #44
post #43

Earlier quoted context omitted.

> ~20% reduction in ad revenue Why would they want a significant reduction in their main revenue source?

Increased demand for privacy, which has already led competing browsers to kill 3P cookies. Note that Google wasn't willing to kill 3P cookies without providing Privacy Sandbox an an alternative, less privacy-invasive, way for publishers to target ads. Without Privacy Sandbox, the reduction in revenue is even more severe: > we observed that removing third-party cookies without enabling Privacy Sandbox led to -34% prog…

> competing browsers

There's literally no competition: around 80% browsers market share belongs to Chromium-based ones. Whatever Google decides in Chromium will be delivered in the next update to rule 80% of the market.

What is 'programmatic revenue' here?

Post reply on HN