This blog post details a method for blocking YouTube ads on Apple TV by intercepting and manipulating encrypted traffic using pfSense, a firewall and router platform. The author leverages pfSense's ability to decrypt TLS/SSL traffic, then uses a custom Python script to parse and filter Google's Protocol Buffer (protobuf) messages, removing the components associated with advertisements before re-encrypting and forwarding the modified traffic to the Apple TV. This approach eliminates ads without relying on DNS blocking or other methods that YouTube might easily circumvent. The post provides a detailed explanation of the setup process, including installing necessary packages, configuring pfSense, and implementing the Python script.
WebShield is a new, free, and open-source content blocker for Safari designed to provide comprehensive protection against a wide range of online annoyances. Leveraging a constantly updated blocklist, it tackles intrusive ads, trackers, cryptocurrency miners, EU cookie banners, and other unwanted content, aiming for a cleaner and faster browsing experience. Users can customize their blocking preferences and add their own custom rules. Built using only native WebKit APIs, WebShield emphasizes performance and privacy by ensuring all processing is done locally on the device.
HN users generally expressed interest in WebShield, praising its open-source nature and potential effectiveness. Several commenters appreciated the developer's focus on privacy and the detailed explanation of the blocking process. Some raised concerns about the reliance on JavaScript and the potential for performance impact, suggesting native implementation would be preferable. Others questioned the long-term maintainability of the project and the feasibility of keeping the block lists updated. A few users mentioned existing content blockers and questioned WebShield's differentiation, while others welcomed it as a valuable addition to the Safari ecosystem. The developer actively engaged with the comments, addressing questions and clarifying the project's goals.
Pi-hole v6.0 is a significant update focusing on enhanced user experience and maintainability. It features a redesigned web interface with improved navigation, accessibility, and dark mode support. Under the hood, the admin console now uses Vue 3 and the API utilizes PHP 8.1, modernizing the codebase for future development. FTL, the DNS engine, also received updates improving performance and security, including DNSSEC validation enhancements and optimized memory management. While this version brings no major new features, the focus is on refining the existing Pi-hole experience and laying the groundwork for future innovation.
Hacker News users generally expressed excitement about Pi-hole v6, praising its improved interface and easier setup, particularly for IPv6. Some users questioned the necessity of blocking ads at the DNS level, citing browser-based solutions and the potential for breakage of legitimate content. Others discussed alternative solutions like NextDNS, highlighting its cloud-based nature and advanced features, while some defended Pi-hole's local control and privacy benefits. A few users raised technical points, including discussions of DHCPv6 and unique privacy addresses. Some expressed concerns about the increasing complexity of Pi-hole, hoping it wouldn't become bloated with features. Finally, there was some debate about the ethics and effectiveness of ad blocking in general.
Summary of Comments ( 385 )
https://news.ycombinator.com/item?id=43396735
Hacker News commenters generally express skepticism about the effectiveness and practicality of the described method for blocking YouTube ads on Apple TV. Some doubt the claim that all YouTube ads are served via protobuf, suggesting the method is likely to break frequently. Others point out the resource intensiveness of decrypting and re-encrypting TLS traffic on less powerful hardware like the Apple TV. Several commenters propose alternative ad-blocking solutions like Pi-hole or NextDNS, arguing these are simpler and more robust. The privacy implications of MITMing TLS traffic are also raised. While some acknowledge the cleverness of the approach, the consensus leans towards it being more of a proof-of-concept than a practical, long-term solution.
The Hacker News post discussing the blog post about blocking YouTube ads on AppleTV by decrypting and stripping ads from Protobuf has a moderate number of comments, sparking a discussion around the effectiveness, ethics, and technical aspects of the approach.
Several commenters express skepticism about the longevity of this method. They predict that Google will likely adapt and change its ad delivery system, rendering this specific decryption technique obsolete. This cat-and-mouse game between ad blockers and ad providers is a recurring theme. Some even suggest that Google might intentionally introduce breaking changes to specifically target this method, while others take a more neutral stance, viewing it as an inevitable evolution in the arms race between ad blockers and platforms.
The legality and ethical implications of bypassing ads are also debated. While some argue it's within the user's right to control their viewing experience, others point out that YouTube's terms of service likely prohibit such manipulation. This leads to a discussion about the broader issue of ad-supported content and the balance between user experience and content creator compensation.
Technical details of the implementation are discussed, with some questioning the efficiency and potential side effects of decrypting and re-encrypting the stream in real-time, particularly on less powerful devices like the AppleTV. The use of Protobuf for ad delivery is also mentioned, with some commenters expressing surprise or noting its prevalence in Google's infrastructure.
Alternative ad-blocking methods are suggested, including Pi-hole and other DNS-based solutions, which some commenters consider more robust and less prone to being circumvented. There's also a mention of using a custom DNS setup to block known ad servers.
Finally, some users share their personal experiences with ad blocking and express frustration with the increasing prevalence of ads on streaming platforms. This sentiment fuels the discussion about the ongoing struggle between users seeking an ad-free experience and platforms relying on advertising revenue.