Well yeah, they’re just blocking known fingerprinting services. If you use a tool that they don’t recognize, it’ll still work, but their approach will still block the big companies that can do the most harm with that data.

The only alternative is probably to disable WebGL entirely, which isn’t a reasonable thing to do by default.

Just use git blame-someone-else.

https://github.com/jayphelps/git-blame-someone-else

Yeah, I manage the infrastructure for almost 150 WordPress sites, and I moved them all to ARM servers a while ago, because they’re 10% or 20% cheaper on AWS.

Websites are rarely bottlenecked by the CPU, so that power efficiency is very significant.