Frustrated with the limitations and privacy concerns of mainstream calendar services, the author embarked on a journey to self-host their calendar data. They chose Radicale as their CalDAV server due to its simplicity and compatibility, and Thunderbird with the TbSync add-on as their client. The process involved setting up Radicale, configuring Thunderbird to connect securely, and migrating existing calendar data. While acknowledging potential challenges like maintaining the server and ensuring data backups, the author emphasizes the benefits of owning their data and controlling access to it. This shift empowers them to choose their preferred software and avoid the potential pitfalls of vendor lock-in and privacy compromises associated with commercial calendar platforms.
Tim investigated the precision of location data used for targeted advertising by requesting his own data from ad networks. He found that location information shared with these networks, often through apps on his phone, was remarkably precise, pinpointing his location to within a few meters. He successfully identified his own apartment and even specific rooms within it based on the location polygons provided by the ad networks. This highlighted the potential privacy implications of sharing location data with apps, demonstrating how easily and accurately individuals can be tracked even without explicit consent for precise location sharing. The experiment revealed a lack of transparency and control over how this granular location data is collected, used, and shared by advertising ecosystems.
HN commenters generally agreed with the article's premise that location tracking through in-app advertising is pervasive and concerning. Some highlighted the irony of privacy policies that claim not to share precise location while effectively doing so through ad requests containing latitude/longitude. Several discussed technical details, including the surprising precision achievable even without GPS and the potential misuse of background location data. Others pointed to the broader ecosystem issue, emphasizing the difficulty in assigning blame to any single actor and the collective responsibility of ad networks, app developers, and device manufacturers. A few commenters suggested potential mitigations like VPNs or disabling location services entirely, while others expressed resignation to the current state of surveillance. The effectiveness of "Limit Ad Tracking" settings was also questioned.
Summary of Comments ( 48 )
https://news.ycombinator.com/item?id=43643343
Hacker News commenters generally praised the author's approach to self-hosting a calendar, emphasizing the importance of data ownership and control. Some questioned the complexity and effort involved, suggesting simpler alternatives like using a privacy-focused calendar provider. A few pointed out potential downsides of self-hosting, including maintenance overhead and the risk of data loss. The discussion also touched on the trade-offs between convenience and control when choosing between self-hosting and third-party services, with some arguing that the benefits of self-hosting outweigh the added complexity. Several commenters shared their own experiences and recommended specific tools and services for self-hosting calendars and other personal data. There was a brief discussion on CalDAV and its limitations, along with alternative protocols.
The Hacker News post discussing self-hosting a calendar solution has generated several comments, primarily focusing on the practicality, security, and complexity of such an endeavor.
Some users express skepticism about the true ownership of data, even when self-hosting. They point out that reliance on third-party hardware and software components still introduces potential vulnerabilities and external dependencies. The discussion delves into the nuances of data ownership, acknowledging that complete control is difficult to achieve in the interconnected digital world.
A recurring theme is the trade-off between convenience and control. While self-hosting offers greater control over data, it often comes at the cost of increased complexity and maintenance. Commenters discuss the technical expertise required to set up and maintain a self-hosted calendar solution, highlighting the challenges of ensuring reliability, security, and accessibility. Several users suggest that for many individuals, the benefits of convenience offered by established calendar services outweigh the potential advantages of self-hosting.
The discussion also touches upon the importance of data backups and disaster recovery planning. Users emphasize the need for robust backup strategies to mitigate the risk of data loss in a self-hosted environment. The conversation highlights the responsibility that comes with self-hosting, as users become solely responsible for the security and integrity of their data.
Several commenters share their personal experiences with self-hosting calendars, offering insights into the challenges and rewards. Some users express satisfaction with their self-hosted setups, emphasizing the benefits of increased privacy and control. Others recount difficulties encountered during the setup and maintenance process, cautioning against undertaking such projects without sufficient technical expertise.
Finally, there's a thread discussing alternative approaches to data ownership and privacy, such as utilizing encrypted calendar services or employing privacy-focused email providers. The discussion explores the spectrum of options available to users concerned about data privacy, recognizing that self-hosting is not a one-size-fits-all solution.