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.
Frustrated with excessive phone use, the creator developed "Touch Grass," an Android app designed to encourage breaks from screen time. The app uses GPS to confirm the user is physically outside and then starts a timer. Only after spending a user-defined amount of time outdoors will the app grant access to blocked apps, effectively locking the user out until they've "touched grass." This gamified approach aims to promote healthier digital habits and reconnect users with the real world.
Hacker News commenters generally found the "touch grass" app amusing, but impractical. Several questioned the effectiveness of physically touching grass through a phone screen, noting the inherent irony and missing the point of the idiom. Some suggested improvements like requiring a photo of actual grass or GPS verification of being outdoors. Others highlighted the performative nature of the app, comparing it to other avoidance techniques. A few commenters appreciated the humor and simple execution, viewing it as a lighthearted take on the problem of doomscrolling. Some pointed out the potential for addictive gamification of "touching grass" itself. Overall, the consensus leaned towards the app being a fun, albeit slightly absurd, commentary on internet overuse rather than a serious solution.
The author describes their struggle with doomscrolling, driven by a combination of FOMO (fear of missing out) and a desire to stay informed. They acknowledge the negative impact it has on their mental health, leading to increased anxiety, sleep disruption, and a distorted perception of reality. Despite recognizing the problem, they find it difficult to break the cycle due to the addictive nature of the constant information stream and the ease of access provided by smartphones. They express a desire to find strategies to manage their doomscrolling habit and reclaim control over their attention.
HN users largely agreed with the author's experience of doomscrolling, sharing their own struggles and coping mechanisms. Several suggested techniques like website blockers, strict time limits, and replacing the habit with other activities like reading physical books or exercising. Some pointed out the addictive nature of infinite scrolling and the algorithms designed to keep users engaged. A few commenters debated the definition of "doomscrolling," arguing that simply reading negative news isn't inherently bad if it leads to positive action. Others highlighted the importance of curating information sources and focusing on reliable, less sensationalized news. A recurring theme was the need for greater self-awareness and intentional effort to break free from the cycle.
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.