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.
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 ( 6 )
https://news.ycombinator.com/item?id=43204406
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.
The Hacker News post for WebShield has several comments discussing its functionality, potential, and limitations.
One commenter expresses excitement about the project, specifically highlighting the ability to block cookie banners. They see this feature as a significant advantage and hope it works effectively. Another user echoes this sentiment, focusing on the annoyance of cookie banners and the desire for a reliable solution.
A discussion arises around the technical details of WebShield's implementation. One commenter inquires about the method used to block content, specifically asking whether it relies on a declarative approach with filter lists like uBlock Origin or employs a procedural method involving JavaScript. The developer of WebShield responds, clarifying that it uses a hybrid approach. While primarily declarative with filter lists, it also incorporates limited JavaScript execution within a sandboxed environment to handle more complex blocking scenarios. This exchange reveals a nuanced understanding of content blocking techniques within the commentariat.
Further technical discussion ensues regarding the performance implications of WebShield. One commenter raises concerns about potential slowdowns due to the use of JavaScript, referencing the performance impact observed with similar browser extensions. The developer acknowledges this valid concern and emphasizes their commitment to minimizing JavaScript usage to maintain optimal browser performance. They further explain that the careful and limited use of JavaScript is a deliberate design choice to balance functionality and performance.
A separate thread emerges comparing WebShield to existing content blockers. One commenter mentions uBlock Origin and its comprehensive features, questioning the need for a new solution. Another user counters this argument by pointing out the specific focus and potential advantages of WebShield, particularly in its approach to handling cookie banners and other targeted annoyances. This exchange highlights the diverse preferences and needs within the content blocking user base.
Finally, a commenter raises a question about the project's license. The developer promptly responds, confirming the use of the GPLv3 license, thereby addressing the inquiry about open-sourcing and community involvement.
Overall, the comments demonstrate a mix of enthusiasm for the potential of WebShield, particularly its cookie banner blocking capabilities, alongside pragmatic concerns about its technical implementation and performance. The developer actively engages with the commenters, providing insightful responses and clarifications, fostering a constructive discussion about the project's strengths and limitations.