Whether you like it or not, Chrome’s ‘topic’ advertising system is here.

slack_justyb writes: after failure In Chrome’s user tracking system, called FLoC, Google has attempted to track topics as a replacement for third-party cookies (Chrome is still the only browser that supports it). fledge And the most recent release of Canary is a full-screen display for users and privacy advocates to dig deeper. This recent release shows Google’s hand in seeing user tracking as an integral part of internet usage, especially given the system’s prominent name “Privacy Sandbox” and the robustness of linking this new API directly to the browser. .

The new API allows you to build in the browser itself what your users think they’re interested in. Based on a wide range of topics created by Google. New topics and how they are placed on them are added to your browser’s database and indexing software via updates from Google. The point to subtract here is that the subject database is built using CPU time. You can now opt out of browsers that build this database of interest, saving you several cycles of use for that purpose. In the future, there will be no way to prevent browsers from using recursion to build databases. The only means is to constantly remove all interest from your personal database. There doesn’t seem to be a way to completely turn off the native API at this time. Websites expecting this API will always succeed in “some kind of response” as long as they use chrome. A response may be that you are not interested in anything, but nevertheless. Of course, someone would have to constantly clear the interest database in a timely manner to send a “I’m not interested in anything” response. Especially if the option to undeploy the database is later removed.

with 82% of Google’s empire based on advertising revenue, this latest development in Chrome shows that Google is not keen on any moves that threaten its main revenue stream. Google continues to insist that building user tracking and advertising systems into Chrome is essential, and, whatever the final solution, says it won’t block third-party cookies until it achieves it. The conclusion of the FLEDGE API via FLoC is that abuse of FLEDGE appears to produce less valuable results. And trying to use the API alone to select individual users via fingerprints or other methods used elsewhere seems rather daunting. But only time will tell if this is true or if Google is idealizing this new API. As for the current timeline, here’s what the company recently said: chrome blog post: “Starting today, developers will be able to globally test Topic, FLEDGE, and Attribution Reporting APIs on a canary version of Chrome. We’ll be rolling it out to a limited number of Chrome beta users as soon as possible. If things work smoothly, we will make API testing available in a stable version of Chrome to extend testing to more Chrome users.”

Whether you like it or not, Chrome’s ‘topic’ advertising system is here.

Source link Whether you like it or not, Chrome’s ‘topic’ advertising system is here.

Back to top button