I added the floc prevention header to my website. It is something i was reluctant to do because of several reasons:
1) My website is served in a single request without any js and is only using images and css i have either inlined or i have full control over. But i have to include the header because i could include a tweet or a video or something that is calling the floc api and thus try to track my visitors. #wtf
2) We all are conditioned by Google to jump through the hoop every time they try to break or take control over the web.
3) Why is it my job to prevent Google Chrome users from hurting themselves? I understand that there are a few cases where a user has no control over the browser they use (likely in a company environment) but i would argue that they are the minority. #floc #fuckfloc #fuckgoogle
Why is it my job to prevent Google Chrome users from hurting themselves?
I’ve been considering setting up nginx to look at the user agent and direct chrome users to a “this site is unavailable on google chrome, here are reasons why” and just calling it a day. Also considering leaving HTTP for Gemini+FTP, since my site is pretty much just text and photos.
@mzumquadrat same here. I'm not going to babysit you for using a browser that will bite you. If you care about privacy you're not going to use any GAFAM software anyway.
Fosstodon is an English speaking Mastodon instance that is open to anyone who is interested in technology; particularly free & open source software.