The author describes creating a DNS sinkhole using an ESP32 microcontroller to combat doomscrolling. By intercepting DNS requests on their local network and redirecting specific domains (like social media sites) to a local web server, they effectively block access to these sites. The ESP32 runs a custom DNS server that returns a pre-defined IP address for targeted domains, leading devices to a blank webpage hosted on the ESP32 itself. This allows the author to curtail time spent on distracting websites without relying on browser extensions or more complex network configurations.
Cloudflare is reportedly blocking access to certain websites for users of Pale Moon and other less common browsers like Basilisk and Otter Browser. The issue seems to stem from Cloudflare's bot detection system incorrectly identifying these browsers as bots due to their unusual User-Agent strings. This leads to users being presented with a CAPTCHA challenge, which, in some cases, is unpassable, effectively denying access. The author of the post, a Pale Moon user, expresses frustration with this situation, especially since Cloudflare offers no apparent mechanism to report or resolve the issue for affected users of niche browsers.
Hacker News users discussed Cloudflare's blocking of Pale Moon and other less common browsers, primarily focusing on the reasons behind the block and its implications. Some speculated that the block stemmed from Pale Moon's outdated TLS/SSL protocols creating security risks or excessive load on Cloudflare's servers. Others criticized Cloudflare for what they perceived as anti-competitive behavior, harming browser diversity and unfairly impacting users of niche browsers. The lack of clear communication from Cloudflare about the block drew negative attention, with users expressing frustration over the lack of transparency and the difficulty in troubleshooting the issue. A few commenters offered potential workarounds, including using a VPN or adjusting browser settings, but there wasn't a universally effective solution. The overall sentiment reflected concern about the increasing centralization of internet infrastructure and the potential for large companies like Cloudflare to exert undue influence over web access.
Summary of Comments ( 9 )
https://news.ycombinator.com/item?id=43204091
Hacker News users generally praised the project's simplicity and effectiveness for blocking distracting websites. Several commenters suggested improvements, such as using a pre-built DNS sinkhole list or implementing a local DNS server for better performance. Some discussed the ethics and potential downsides of blocking websites, particularly for families or in situations where access is necessary. Others offered alternative solutions, like using Pi-hole or modifying the hosts file. A few pointed out potential issues with the ESP32's limited resources and the importance of using a reliable power supply. The overall sentiment was positive, viewing the project as a clever, albeit somewhat limited, solution to a common problem.
The Hacker News post "Turning my ESP32 into a DNS sinkhole to fight doomscrolling" generated a moderate number of comments, mostly focusing on the practicality and efficacy of the approach, as well as alternative solutions.
Several commenters questioned the effectiveness of using an ESP32 for this purpose, citing its limited resources and potential performance bottlenecks. One commenter pointed out that DNS queries are generally small and infrequent, suggesting the ESP32 might be sufficient for a home network. Another countered this by highlighting the ESP32's relatively slow processing speed and limited RAM, which could become problematic with more devices or complex DNS configurations. The potential for latency issues and single point of failure were also raised as concerns.
A prominent thread discussed alternative methods for achieving the same goal, such as using a Pi-hole, modifying the hosts file, or utilizing features built into existing routers. Pi-hole was frequently mentioned as a more robust and feature-rich solution, already designed for network-wide ad blocking and DNS sinkholing. Modifying the hosts file was suggested as a simpler, though potentially less manageable, alternative for individual devices. Some commenters highlighted the built-in DNS filtering options available in certain routers, offering a convenient solution without requiring additional hardware.
Some users discussed the broader implications of DNS sinkholing, including the ethical considerations of blocking content and the potential for inadvertently breaking legitimate websites. One commenter argued that while the author's intentions were understandable, blocking entire domains might be overly aggressive, suggesting a more targeted approach to filtering specific unwanted content.
While generally receptive to the author's ingenuity, the overall sentiment in the comments leans towards exploring alternative, more established solutions for DNS sinkholing and content filtering. The ESP32 approach is acknowledged as a functional proof-of-concept, but its limitations and potential drawbacks are highlighted, leading to recommendations for more robust and scalable alternatives. The discussion also extends to the ethical considerations surrounding content blocking and the importance of carefully considering the implications of such practices.