Show HN: Timelinize – Privately organize your own data from everywhere, locally (timelinize.com)

Article summary

Timelinize is an open-source personal archival suite that organizes data from various sources into a unified timeline on a user's computer. It allows users to import data from sources like Google Photos, text messages, and social media, and provides features like semantic search, entity-aware processing, and customizable maps. The suite is designed to be self-contained and portable, with data stored in a folder on the user's disk. Timelinize aims to provide a private and permanent archive of a user's data, independent of cloud services.

Main themes

• Personal data archiving
• Data privacy
• Timeline organization
• Cloud independence
• Data import and export
• Entity-aware processing

What commenters say

• The process of updating data in Timelinize is cumbersome due to the need to manually download data from services like Google Takeout, and a more automated solution would be desirable.
• A companion app that streams data from a user's phone to their computer could provide a more convenient way to keep the timeline up to date.
• Some users are concerned about the cost and complexity of storing and backing up their data, and are looking for solutions that are easy to use and affordable.
• There is interest in integrating Timelinize with other services and tools, such as Nextcloud and Zotero, to provide a more comprehensive data management solution.
• Some users want more detailed data collection and tracking features, such as recording browser history and keystrokes, while others find this level of granularity unnecessary.
• The development of an extension system for arbitrary data collectors and filters could provide a way to balance the level of detail collected with user needs and preferences.
• There are differing opinions on the scope of Timelinize, with some seeing it as a tool for aggregating data from other services and others wanting it to replace services like Nextcloud.
• The use of a centralized database versus sidecar metadata files is a topic of discussion, with some users preferring the simplicity of a centralized database and others advocating for a more decentralized approach.