Just saw the edit, all clicked now. As described this is expected behavior. The entitieslist (can't link right now because Github is down but got a local copy for some experiments) contains exceptions for owners of tracking URLs, in this case as a resource for Cloudflare.com and others owned by them only. Basically, because they are the same entity, they are considered one. Whether that could be communicated better by upstream, that's worth a discussion. Anyone besides Cloudflare.com has cloudflareinsights blocked.
Here the specific entry for context from my local copy of ESR 153:
{
"entities": {
"Cloudflare": {
"properties": [
"cloudflare-quic.com",
"cloudflare.com",
"cloudflare.tv",
"cloudflarestatus.com",
"cloudflareworkers.com"
],
"resources": [
"cloudflare.com",
"cloudflareinsights.com",
"cloudflarestream.com"
]
}
}
On a side note, spent a while learning how upstream Firefox works in-depth over the last few months, if ETP didn't block cloudflareinsights on pages outside Cloudflare.com I'd have lost any confidence build up and my project would likely linger even longer. Might just add a setting that totally excludes such exceptions if I can properly test it before release, seems there might be demand. Admittedly more for UX and honest communication clarity reasons (top setting truly prevents everything) then privacy, not the main goal of Hominis as a project.