I can’t believe I’m having to write this code in a fucking web server. What a mockery of the web, human rights, and the GDPR.
Fuck you, Google!
@aral as a site owner who doesn't care about Chrome users getting abused by their overlord: is there any reason for me to implement this?
@nanont Not everyone who uses the world’s most popular browser made the decision to use it or knows how to use a different one. So I’d say yes, if you care about people, you would. And fuck Google for making you do it.
@aral What bothers me is that tweaking my web server this way would essentially improve the privacy of Chrome, masking its abuse. I don't want that.
Plus, I don't think that Chrome will respect this header in the long run, should most servers choose to send it. Surely Google wouldn't be impressed by a non-binding header if it sits between them and piles of ad cash, no?
Maybe something less subtle like a call-out banner is a better idea? https://microblog.shivering-isles.com/@sheogorath/106072444241251745
@nanont Sure that’s one approach but that banner isn’t the way to do it. If you’re going to do that also write up detailed instructions on how to use another browser and, still, realise some folks may not be able to. So why not: put a banner to educate and also block it on your own site to show them you care?
@aral This sounds like a good idea. Thank you for taking the time to discuss this.
@nanont @aral Perhaps it would make sense to suggest #UngoogledChromium in that disclosure, assuming UC has fixed it.
