It will give so much power to Google. Aggregator service and ad-reporting service are probably going to be Google's service. IMO its rather better to be completely open with the world, than sharing all your secrets to one person whom you don't know.

@estercarvalho9703

3 ай бұрын

Invadiram minha conta !!!

@vuufke4327

Ай бұрын

literal conflict of interest

@manashmohanty7631

12 күн бұрын

😅😅😅​@@estercarvalho9703

And who's gonna be the Aggregation Service? Will Google Analytics servers be that?

What if the "adtech" provider is Google Ad Manager? Images can't be just uploaded into GAM without adding a script to deliver with the image?

Uhuuu. Parabéns Supla pela transição de carreira!

@giovaniortolanibarbosa

6 ай бұрын

papito!!!!

How it save privacy?

New Feature (suggestion/request): CSS Filter Hue rotation in different color spaces, please.

I understand the theory behind adding noise to this and other reporting in these new services that Google is rolling out but it feels clumsy and feels like it will undermine trust in the new system. I agree we need to retire 3rd party cookies to increase privacy but noising seems like a half-measure that doesn't fully address identifying most users for those trying to work around the privacy blocks and just adds distrust for those relying on accurate data in the reports.

This proposal is way way too complicated in my opinion. I really think it needs to be reconsidered.

@Ostap1974

7 ай бұрын

Don't worry, Google Ads service will implement the API properly.

It's amazing how much of Chrome's development is driven by initiatives from the ads division, meanwhile they deliberately deploy insecure APIs that ad networks routinely abuse for tracking -- such as the AudioContext API. Chrome developers implement insecure APIs, and then their friends in the ads division abuse it for tracking. Chrome is the antithesis of security and privacy, and should thusly receive antitrust scrutiny.

@Cookie_Wookie_7

7 ай бұрын

What's wrong with AudioContext?

@CastleMatch

7 ай бұрын

@@Cookie_Wookie_7 it leaks latency information that is regularly used in fingerprinting techniques. Given how recently this API was rolled out, it seems like there was absolutely zero considerations for privacy. In fact, there's evidence AudioContext exploitation happens in Google's own DoubleClick network by third parties.

@HiroaikiIzimi

3 ай бұрын

3:15 3:16 😅😅

@user-qi3hs9zu5q

26 күн бұрын

Ррр​@@Cookie_Wookie_7

I like thank to much 😂❤😂❤good

お