<isd>
Horray for having to write code to disable new browser anti-features? :(
<ocdtrekkie>
More hooray at it being done. I think it's good for us to also be in the group of platforms that take proactive action to prevent privacy abuses.
<ocdtrekkie>
I would hope that the code is deletable somewhat soon, if enough of the web can render it ineffective.
<isd>
I'm not super hopeful :/ configuring a header is enough of a pain for most web servers that we'd be outsandingly lucky to break 5% of sites. Still, we should do our part.
<isd>
(I would have done it on the spot when you reported the issue if it hadn't turned out to be a little non-trivial -- I kinda wish the gateway were written in something higher-level.
<ocdtrekkie>
Best bet is platforms doing it for people. If WordPress rolls out their fix by default... that's most nontechnical web owners in one go.
<ocdtrekkie>
But yeah, people asked in the FLoC repo why you can't opt out with a meta tag, and "because that'd be too easy" seems like the likely reason.
griff has quit [Quit: griff]
<isd>
Ok, yeah I guess wordpress covers a lot.
isd has quit [Write error: Connection reset by peer]
timmc[m] has quit [Remote host closed the connection]
ocdtrekkie has quit [Read error: Connection reset by peer]
jryans has quit [Read error: Connection reset by peer]