231–240 of 264 posts
I think I will just block Chrome users from my websites
I think I will just block Chrome users from my websites
if (document.interestCohort) {...
Ok, so let me see if I understand this correctly: I run a website with no trackers, no ads, nothing at all to do with Google or any other company in any way. You come along, with Google Chrome, and visit my site. Google adds the fact that you visited my site to their massive dataset (as well as who-knows-what-else) And to opt out of something I have never been asked to be involved with in any way, I need to contact G…
> I run a website with no trackers, no ads, nothing at all to do with Google or any other company in any way. Then your site will not be included in FLoC: "A page visit will be included in the browser's FLoC calculation if document.interestCohort() is used on the page. During the current FLoC origin trial, a page will also be included in the calculation if Chrome detects that the page load ads or ads-related resource…
caveat 1: extensions. And if one user runs an extension on your site, that triggers inclusion on FLoC, who knows how the domain will be classified in the near future or for other users without any extension?
caveat 2: google simply deciding to change the algo. Or running silent experiments, such as they one running now to try FLoC. Or would anyone here bet $1 on google keeping terms/services around?
caveat 3: the use of condescendingly misleading terms on the official FAQ. E.g. to define the item FLoC works on page/site "A page visit will be included" vs "Websites will have the ability to opt in or out" (no mention of accepted, non-ambiguous, factual terms like url, domain, origin, etc);
And yes, I am biased against FLoC because it is a very low effort to abuse browser monopoly to keep a business that nobody likes.
I will just end this rant with my favorite quote from google announcement: "FLoC service will evaluate whether a cohort may reveal sensitive information about users without learning why that cohort is sensitive".
Earlier quoted context omitted.
As noted by Consumer Reports: "When third-party cookies are replaced by FLoC, Google will have a way to track consumers that isn’t available to other companies, which could give Google a steep advantage in the advertising business." [1] According to the EFF, Google controls the algorithms, and will also be running its implementation and auditing its outputs, a task the EFF describes as "both orwellian and sisyphean".…
> that isn’t available to other companies Is there a proof for this claim? My understanding is that the cohort you belong to is available to any page. Is that not true?
Ok, so let me see if I understand this correctly: I run a website with no trackers, no ads, nothing at all to do with Google or any other company in any way. You come along, with Google Chrome, and visit my site. Google adds the fact that you visited my site to their massive dataset (as well as who-knows-what-else) And to opt out of something I have never been asked to be involved with in any way, I need to contact G…
> I run a website with no trackers, no ads, nothing at all to do with Google or any other company in any way. Then your site will not be included in FLoC: "A page visit will be included in the browser's FLoC calculation if document.interestCohort() is used on the page. During the current FLoC origin trial, a page will also be included in the calculation if Chrome detects that the page load ads or ads-related resource…
Ok, so let me see if I understand this correctly: I run a website with no trackers, no ads, nothing at all to do with Google or any other company in any way. You come along, with Google Chrome, and visit my site. Google adds the fact that you visited my site to their massive dataset (as well as who-knows-what-else) And to opt out of something I have never been asked to be involved with in any way, I need to contact G…
I think I will just block Chrome users from my websites
I looked into this, and it's way harder than you think. Several browsers report themselves as Chrome, Chrome itself is about to get rid of its user agent, and all the javascript feature detection methods I could find no longer work.
Earlier quoted context omitted.
I looked into this, and it's way harder than you think. Several browsers report themselves as Chrome, Chrome itself is about to get rid of its user agent, and all the javascript feature detection methods I could find no longer work.
A whitelist would work better than a blacklist, as with most other cases in dev ;)
Ok, so let me see if I understand this correctly: I run a website with no trackers, no ads, nothing at all to do with Google or any other company in any way. You come along, with Google Chrome, and visit my site. Google adds the fact that you visited my site to their massive dataset (as well as who-knows-what-else) And to opt out of something I have never been asked to be involved with in any way, I need to contact G…
Because Google has effectively embedded and interwoven itself so tightly into the fabric of the web, that simply having no association with them is impossible. Vint Cerf is their evangelist. The creator of The Internet is an evangelist for Google! Read more:
https://research.google/people/author32412/
> Vinton G. Cerf is vice president and Chief Internet Evangelist for Google. He contributes to global policy development and continued spread of the Internet.
Earlier quoted context omitted.
> I run a website with no trackers, no ads, nothing at all to do with Google or any other company in any way. Then your site will not be included in FLoC: "A page visit will be included in the browser's FLoC calculation if document.interestCohort() is used on the page. During the current FLoC origin trial, a page will also be included in the calculation if Chrome detects that the page load ads or ads-related resource…
That "During the current FLoC origin trial" bit scares me though. Why should I assume the scope of implicit inclusion in FLoC won't be expanded in the future? I don't exactly trust this opt-out header. The spec makes it sound like it's not so much a request to the user agent not to use cohorts in general. Rather it's a security-in-depth measure to prevent third-party scripts or injected spyware from exploiting certai…
It's the other way around: it's saying that normally "a page visit will be included in the browser's FLoC calculation if document.interestCohort() is used on the page" but to support this specific origin trial it will also include pages "if Chrome detects that the page load ads or ads-related resources". This is needed to avoid the chicken and egg problem that you would otherwise have in a proof-of-concept experiment.