Chrome FLEDGE is here, whether you like it or not

After the failure of the Chrome's monitoring system called flock, Google's latest attempt to replace third-party cookies (Chrome is the only browser that still supports them) is FLEDGE.

spying google

The company the was released in the Canary channel allowing users and privacy advocates to search deeper.

This latest release shows that Google sees user tracking as a mandatory part of using the internet, and with a striking name "Privacy Sandbox" is trying to get us to link a new API directly to the browser. But there will be tightness, according to the name and that should make us happy.

The new API will allow the browser to record what it thinks we are interested in. However, the main point to note here is that the database will be created using our computer CPU.

google

At this time, it is possible to disable the feature from the browser, but in the future there may be no exception.

  Unsafe the HTTPS super-cookie

Note that at this time, there does not appear to be any way to completely disable the underlying API. A site that expects this API will always get "some sort of response" if you use Chrome.

The answer Chrome will send to the site may be that you are not interested in anything, but it is an answer nonetheless.

82% of Google's empire is based on ad revenue, and this latest development in Chrome shows that Google does not want to make any move that threatens the main way of financing.

Google continues to argue that it's mandatory to set up a user tracking and advertising system in Chrome, and says it will not block third-party cookies until it succeeds.

The result, if you can call it that, of the FLEDGE API versus FLOC, is that abusing the FLEDGE seems to yield less valuable results. And trying to use the API just to select a single user via fingerprinting or other methods used seems to be rather difficult to accomplish. Of course, time will tell if this remains the case or if Google is just trying to optimize this new API.

  Google announced additional security measures for Android apps

Regarding the schedule:

"From today, developers can start testing the Topics, FLEDGE, and Attribution Reporting APIs globally in the Canary version of Chrome. We will get to a limited number of users in Chrome Beta as soon as possible. "Once things work out in Beta, we'll make the API test available in the stable version of Chrome to extend the test to more Chrome users."

Registration in iGuRu.gr via email

Your email for sending each new post

Follow us on Google News iGuRu.gr at Google news

Leave a reply

Your email address Will not be published.

59 +    = 63

Previous Story

LibreOffice 7.3.2 stable has just been released

Next Story

How to left-click with your mouse