3 ms·
IP blocking still seems a thing, even with this new feature - the ads need to be served from _somewhere_. I am using pfblocker-ng on pfsense, which uses giant I
by Helmut10001 5y ago
IP blocking still seems a thing, even with this new feature - the ads need to be served from _somewhere_. I am using pfblocker-ng on pfsense, which uses giant IP blocklists to filter out all connections to spam and ad-servers. I haven't seen ads in 5 years and there is no need for client-side solutions (e.g. adblocker). The places where ads appear are just whitespace.
- josephcsible 5y agoThe idea is that this will be served from the same IP address that the site that you're trying to visit is.
- Helmut10001 5y agoThanks for the explanation - I understood this partly from the article and it is pretty worrying for the future.
- pixeldetracking 5y agoyes, i updated the french article but not this translation (no idea who did the translation btw), Google has a guide to host the container on your own infra: https://developers.google.com/tag-platform/tag-manager/server-side/manual-setup-guide https://developers.google.com/tag-platform/tag-manager/serve...