Earlier quoted context omitted.
How do you block it?
curious as well? How to block Floc?
Permissions-Policy: interest-cohort=()
41–50 of 249 posts
Earlier quoted context omitted.
How do you block it?
Blocking FLoC is as easy as adding this header to the HTTP response: Permissions-Policy: interest-cohort=() Source: https://www.drupal.org/project/drupal/issues/3209628
I'm curious, with third-party cookies being fased out, and alternatives like FLoC being met with resistance, could this drastically cut the size of Google's revenue's down? If the ads can no longer be accurately targeted, I imagine that would mean the main value of AdWords is no more, and that's the foundation that entire company is built on.
Earlier quoted context omitted.
That would annoy me less than seeing dish washer ads AFTER I bought the goddamned dish washer.
They are just trying to help you out. They know there are "if you find it cheaper in the next 30 days, we'll refund the difference" policies out there. So those ads are actually much more helpful than you are giving credit. They can't help it you chose poorly and used a site that did not have that policy. /s
Earlier quoted context omitted.
curious as well? How to block Floc?
We should make a darkUI along the lines of prohibitive cookie policy modals that detect Chrome, and forces the FLoC in user's faces. It'll get ignored and be as useful as the cookie policy windows, but it'll be funny. Maybe add to the window "Don't like this message? Try Firefox instead!"
If Firefox had larger market share, Chrome wouldn’t have been able to make this opt out for websites rather than opt in because it would have given them a bad public image. I don’t think it’s fair that some company gets to force every website maintainer (most aren’t extremely technical and just use Wordpress or something similar) on earth to muddle through documentation for their particular setups to 1) learn it exis…
This wording annoys me. The websites have nothing to do with it. Google choosing to turn it's browser into spyware that leaks information about what you used to do with it isn't the websites fault, the webserver doesn't do anything and doesn't have anything done to it, there is nothing for it to opt out of.
Google chose to give websites a way to request that the users browser doesn't include the fact that they visited this website in it's cohort calculation. That's fine, but the messaging around it is a transparent attempt at shifting the blame. It's not the website opting out or in, it's the website acting as an uninvolved third party bystander asking google to stop. Asking why a website didn't opt out is equivalent to a thief asking "well why didn't you stop me?" to the person looking on from the sidewalk.
We shouldn't accept this messaging. We should be very clear that Chrome is the entity spying on you, not the website, and that the website has no power to decide whether or not chrome spies on you, only the ability to make a polite request that it doesn't (or more accurately, does so less).
first world problems
I don't think so, and I'm actually happy that Amazon is blocking Google on this front. Amazon is always protective its customer data though. Their e-mails don't have details or invoices either.
Earlier quoted context omitted.
How do you block it?
Blocking FLoC is as easy as adding this header to the HTTP response: Permissions-Policy: interest-cohort=() Source: https://www.drupal.org/project/drupal/issues/3209628
Trying to block this is a losing battle. The whole privacy-first angle is so disingenuous, too. Is there a way we can just obfuscate / ruin our data with them? Like a tool or browser extension I can run that clicks / visits a bunch of random links and totally trashes which "cohort" Google thinks I belong in. I'd pay for this more than paying to opt-out. Then serve me all the ads you want.
Why do we believe the Googs will actually honor this flag? If it's just an HTTP header, the browser can be made to just act like it's not there. All of these "flags" are essentially honor policy level things (just like robots.txt), but if the thing is not even told to look for the flag, there's nothing stopping from doing exaclty what is being asked not to do.
We believe it because Google submitted the permissions-policy header / attribute (which allows a site owner to control the permissions for a lot of things apart from interest cohorts, such as geolocation, fullscreen etc) and because we have no choice. The organization controlling "the thing" is the entity that asked for the feature, so we believe the thing will both know about it and honor it.