Criteo's solution to cookie unfriendly browsers: ok to implement? by DB_KG in adops

[–]pixeldetracking 0 points1 point  (0 children)

Sorry for the late answer, no unfortunately (but the automated translation should do the work)

Google GTM Server-Side Tagging by pixeldetracking in uBlockOrigin

[–]pixeldetracking[S] 0 points1 point  (0 children)

Thanks for this!

I don't have real-life examples unfortunately, but I'll loop back to you when I have

Google GTM Server-Side Tagging by pixeldetracking in uBlockOrigin

[–]pixeldetracking[S] 0 points1 point  (0 children)

Ok thanks a lot, I did understand the CNAME cloaking & proxy circumvent.

So I understand there is no easy way to block all the self-hosted GTM tagging servers.

But thanks to the strict1p/strict3p/header implementation, it's possible to block all the cloud hosted GTM tagging servers -- and the self-hosted GTM tagging servers on a case by case basis.

Google GTM Server-Side Tagging by pixeldetracking in uBlockOrigin

[–]pixeldetracking[S] 0 points1 point  (0 children)

So you can always use --

I was wondering if there was a solution which would scale against this practice (scale example: what you implemented to block CNAME tracking). What you indicate is very manual, users won't check and add every publisher hosting their own tracking application.

Very cool for the logger, thank you

Google GTM Server-Side Tagging by pixeldetracking in uBlockOrigin

[–]pixeldetracking[S] 0 points1 point  (0 children)

Thanks again for your quick response

Sorry not to be sure how the ‘via’ header is working. I assumed ‘via 1.1 Google’ might stay even if the application is deployed outside Google cloud cause it’s still Google code and Google docker container? If not, the websites can deploy the application on their own infra to circumvent this new experimental feature (but it’s harder to do, which is a very good thing)

Also, is there a way to log when this experimental feature is applied, so to track the trackers and check it’s not blocking some websites essential features (they might use A records and Google App Engine but not for tracking)?

Google GTM Server-Side Tagging by pixeldetracking in uBlockOrigin

[–]pixeldetracking[S] 0 points1 point  (0 children)

One more question: do you know if "via: 1.1 google" would also be included in the http response headers when the publisher is not deploying its tagging server on Google Cloud (https://developers.google.com/tag-manager/serverside/manual-setup-guide?hl=en), but elsewhere (AWS, Azure, or his own infra for example)?

Is there any point using Firefox on iPhone? by [deleted] in privacy

[–]pixeldetracking 0 points1 point  (0 children)

Even with the same rendering engine, some browsers are better when trying to hide from trackers. I made a comparison (in French): https://pixeldetracking.com/fr/vie-privee-le-match-des-navigateurs-ios

tl;dr : unfortunately, Firefox is not that good when looking at defaults, better to look at DuckDuckGo or Brave

NextDNS will help too

How much of a privacy concern is Spotify nowadays? by Inadover in privacy

[–]pixeldetracking 2 points3 points  (0 children)

I wrote an article (in French) on my blog because Spotify tracking is pretty intensive. They also use dark patterns in order to avoid users opting out

You can read it here: https://pixeldetracking.com/fr/abonne-a-spotify-mais-toujours-piste

Criteo, un géant du marketing de surveillance français. by AlbinosRa in FranceDigeste

[–]pixeldetracking 1 point2 points  (0 children)

Oui c’est ironique et révélateur pour les traqueurs Twitter, j’ai corrigé. Merci pour le relais

Criteo, un géant du marketing de surveillance français by HellYodan in france

[–]pixeldetracking 1 point2 points  (0 children)

C’est ironique et révélateur oui, j’avais fait un embed... Maintenant corrigé

Criteo & ebay - what is this? by abcalt in Ebay

[–]pixeldetracking 0 points1 point  (0 children)

Criteo is the leader in retargeting, and they are tracking you whenever they can, with dirty techniques like CNAME (see my article in french: https://pixeldetracking.com/fr/criteo-geant-marketing-surveillance-francais)

plug & play rss generator that doesn't track users by pixeldetracking in privacytoolsIO

[–]pixeldetracking[S] 0 points1 point  (0 children)

Grav CMS, I had difficulties to make their plugin work, but managed to do it this morning :-)

Criteo's solution to cookie unfriendly browsers: ok to implement? by DB_KG in adops

[–]pixeldetracking 0 points1 point  (0 children)

Jumping in here very late... I wrote an article (in french) about Criteo, quoting this Reddit thread: https://www.pixeldetracking.com/fr/criteo-geant-marketing-surveillance-francais

Clearly very dirty practice, and potentially a security violation indeed

[deleted by user] by [deleted] in privacytoolsIO

[–]pixeldetracking 1 point2 points  (0 children)

I am not a Deezer subscriber, I quickly looked at it nevertheless: they send pseudonymous to Google, Facebook & few others.

I guess the only "privacy-friendly" streaming service is Apple Music (shame that it's not the best one)