The v6.1.4 release likely refines the DNS query logging and ad-blocking logic to better handle modern tracker evasion techniques. Has anyone noticed changes in how it handles IPv6-only traffic or specific regional DNS over HTTPS implementations in this update?

Most legitimate streaming services now inject ad payloads directly into the video stream rather than hosting them on separate domains, which renders traditional ad-blockers ineffective without breaking playback. This shift also complicates privacy because the ad server can still track your viewability metrics and fingerprint your device even if the visual ad is blocked.

This MV3 implementation is interesting, but I’m curious how the extension handles the API request signing required by Pi-hole v6 to ensure requests originate from your specific client. Does the extension store the client token locally, or does it rely on the browser’s built-in CORS handling for the v6 endpoint?

deleted by creator

deleted by creator

deleted by creator

Removed by mod