Conversation

Everyone's talking about how to make your site request Chrome not do their FLoC tracking shit, but how about a bigger hammer: Apache, nginx, lightttpd, Caddy, etc.: make any request with FLoC headers in it reply with result code 400. Force Google to remove that shit entirely.

121

439

Daniel Micay

@DanielMicay

Replying to

@RichFelker

nginx literally includes a first party module for making tracking pixels more efficient: nginx.org/en/docs/http/n Their customers are web sites, advertising companies, etc. not the end users of those sites.

6:51 AM · Apr 19, 2021Twitter Web App

Replying to

and

I could see Caddy conservatively setting some privacy / security headers by default but nothing beyond that. I don't think any web server is going to break the web for a subset of users by default. The only way Chrome doesn't deploy FLOC is Google deciding it's not a good idea.

Replying to

An error message saying "you nerd to turn this off to proceed" wouldn't be breaking the web.

Show replies

Replying to

I don't expect them to do the right thing but that doesn't mean I can't challenge them to. The point is implicating them for their role in this if they don't.