Which do get blocked since they're still trackers. The protection isn't just against 3rd party trackers.

And if you obfuscate your Matomo client script to get around the user's preference for trackers you're not being very ethical.

Seems like Firefox's built-in protection is mostly about 3rd-party trackers? Even the description for "Tracking content" (the not-obviously-3rd-party category) talks about "external ads, videos, and other content with tracking code from other companies. For example, a website may embed a video from a video platform". And this category is not blocked by default, only in strict mode.

> And if you obfuscate your Matomo client script to get around the user's preference for trackers you're not being very ethical.

I'm not sure I agree, but you made interesting point and I'm glad you brought it up!

Personally, I don't think I would classify that as unethical. Ethics need to be looked at with intent in mind, and if you are comfortable being honest about what you are doing, I _think_ I would be okay with this. Not sure, though–I do have doubt.

You can run self-hosted analytics without any client side JS. So no. You can't even block those (except if you disallowed any session cookies, but then the site might not work at all if it's login-based).

Theoretically you could use the same way to feed third-party analytics too though.

Even without cookies and without JS you can still get some data for analytics.