timelinize - Store your data from all your accounts and devices in a single cohesive timeline on your own computer

[ShellLM]

• timelinize/README.md at main · timelinize/timelinize

Organize your photos & videos, chats & messages, location history, social media content, contacts, and more into a single cohesive timeline on your own computer where you can keep them alive forever.

Timelinize lets you import your data from practically anywhere: your computer, phone, online accounts, GPS-enabled radios, various apps and programs, contact lists, cameras, and more.

Join our Discord to discuss!

Note

I am looking for a better name for this project. If you have an idea for a good name that is short, relevant, unique, and available, I'd love to hear it!

Screenshots

These were captured using a dev repository of mine filled with a subset of my real data, so I've run Timelinize in obfuscation mode: images and videos are blurred (except profile pictures---need to fix that); names, identifiers, and locations around sensitive areas are all randomized, and text has been replaced with random words so that the string is about the same length.

(I hope to make a video tour soon.)

Please remember this is an early alpha preview, and the software is very much evolving and improving. And you can help!

WIP dashboard. Very WIP. The bubble chart is particularly interesting as it shows you what kinds of data are most common at which times of day throughout the years.	The classic timeline view is a combination of all data grouped by types and time segments for reconstructing a day or other custom time period.
Viewing an item shows all the information about it, regardless of type: text, photo, live photo, video, location, etc.	I had to make a custom file picker since browser APIs are too limiting. This is how you'll import most of your data into your timeline, but this flow is being revised soon.
The large map view is capable of 3D exploration, showing your memories right where they happened with a color-coded path that represents time.	Because Timelinize is entity-aware and supports multiple data sources, it can show data on a map even if it doesn't have geolocation information. That's what the gray dots or pins represent. In this example, a text message was received while at church, even though it doesn't have any geolocation info associated with it directly.
Timelinize treats entities (people, pets/animals, organizations, etc.) as first-class data points which you can filter and organize.	Timelinize will automatically recognize the same entity across data sources with enough information, but if it isn't possible automatically, you can manually merge entities with a click.
Conversations are aggregated across data sources that have messaging capabilities. They become emergent from the database by querying relationships between items and entities.	In this conversation view, you can see messages exchanged with this person across both Facebook and SMS/text message are displayed together. Reactions are also supported.
A gallery displays photos and videos, but not just those in your photo library: it includes pictures and memes sent via messages, photos and videos uploaded to social media, and any other photos/videos in your data. You can always filter to drill down.

How it works

1. Obtain your data. This usually involves exporting your data from apps, online accounts, or devices. For example, requesting an archive from Google Takeout. (Apple iCloud, Facebook, Twitter/X, Strava, Instagram, etc. all offer similar features for GDPR compliance.) Do this early/soon, because some services take days to provide your data.
2. Import your data using Timelinize. You don't need to extract or decompress .tar or .zip archives; Timelinize will attempt to recognize your data in its original format and folder structure. All the data you import is indexed in a SQLite database and stored on disk organized by date, without obfuscation or anything complicated.
3. Explore and organize! Timelinize has a UI that portrays data using various projections and filters. It can recall moments from your past and help you view your life more comprehensively. (It's a great living family history tool.)
4. Repeat steps 1-3 as often as desired. Timelinize will skip any existing data that is the same and only import new content. You could do this every few weeks or months for busy accounts that are most important to you.

Caution

Timelinize is in active development and is still considered unstable. The schema is still changing, necessitating starting over from a clean slate when updating. Always keep your original source data. Expect to delete and recreate your timelines as you upgrade during this alpha development period.

Download and run

From release binaries

Important

Please ensure you have the necessary dependencies installed or Timelinize will not function properly.

After you have the system requirements installed, you can download and run Timelinize from the latest Release action. Click the most recent job and then choose the artifact at the bottom of the page that matches your platform.

Because of limitations in GitHub Actions, all artifacts get downloaded as .zip files even though the artifact is already compressed, so you may have to double-extract the download.

While Timelinize is in development, it's a good idea to start over with a new timeline repository every time you upgrade your build. The schema is still changing!

I recommend running from the command line even if you can double-click to run, so that you can see the log/error output. Logs are also available in your browser dev tools console.

Using Docker images

Note

Docker images are not yet available. This section will be updated when they are.

docker run -p12002:12002 \
           -v /path/to/repo:/repo \
           -v /path/to/config:/app/.config/timelinize \
           ghcr.io/timelinize/timelinize

That will run Timelinize on port 12002, with the data repository mounted at /path/to/repo (change it to suite your needs) and the configuration directory mounted at /path/to/config (change it).
When using Docker bind mounts like above, make sure the directories exist on your host machine and that they belong to the user ID 1000.

Note

Because Timelinize is running inside a Docker container, it won't have access to your host's filesystem. You will need to mount the directories you want to access as volumes, to be able to load data into Timelinize.

Build from source

Timelinize compiles for Windows, Mac, and Linux.

Although Timelinize is written in Go, advanced media-related features such as video transcoding and thumbnail generation (and in the future, indexing with on-device machine learning) are best done with external dependencies. When building from source, you need to make sure the development packages/versions of those dependencies are installed! Also, the latest version of Go is required.

Dev dependencies

Note that, on some platforms, the compilation dependencies may be different from the dependencies needed to run an already-built binary (for example, on Ubuntu you need libvips-dev to compile, but on end user machines, you just need libvips).

• Go (latest version; do not use Debian or Ubuntu package managers)
• ffmpeg (executable must be in PATH)
• libvips-dev
  • Arch: sudo pacman -S libvips
  • Ubuntu: sudo apt install -y libvips-dev
  • macOS: brew install libvips
• libheif (I think libheif is sometimes automatically installed when you install libvips)
  • Ubuntu: sudo add-apt-repository ppa:vpa1977/libheif && sudo apt update && sudo apt install libheif-dev libheif1
  • Arch: sudo pacman -S libheif (if not already installed)

Installing dependencies on Windows

This is the easiest way I have found to get the project compiling on Windows, but let me know if there's a better way.

0. Make sure you don't already have MSYS2 installed and C:\msys64 does not exist.
1. Install MSYS2: https://www.msys2.org/ - don't run after installing, since it likely brings up the wrong shell (UCRT; we want MINGW64 - yes, UCRT is recommended as it's more modern, but I don't feel confident that our dependencies are available as UCRT packages yet).
2. Run the MSYS2 MINGW64 application (this is MSYS2's MINGW64 environment).
3. Install mingw64 with relevant tools, and libvips, and libheif:

   pacman -S --needed base-devel mingw-w64-x86_64-toolchain mingw-w64-x86_64-libvips mingw-w64-x86_64-libheif
   

4. Go to Windows environment variables setting for your account, and make sure:
   • Path has C:\msys64\mingw64\bin
   • PKG_CONFIG_PATH has C:\msys64\mingw64\lib\pkgconfig
5. Restart any running programs/terminals/shells, then run gcc --version to prove that gcc works. vips and heif-* commands should also work. It is likely that the libraries are also installed properly then too.
6. Running go build should then succeed, assuming the env variables above are set properly. You might need to set CGO_ENABLED=1 ($env:CGO_ENABLED = 1)

NOTE: Setting the CC env var to the path of MSYS's MINGW64 gcc isn't sufficient if a different gcc is in the PATH. You will need to prepend the correct gcc folder to the PATH!

For compilation targeting the same platform (OS and architecture) as your dev machine, go build should suffice.

Compile

Once you have the necessary dependencies installed, you can simply run go build from the project folder:

$ go build

and a binary will be placed in the current directory.

Or, to start the server and open a web browser diretly:

$ go run main.go

To only start the server and not open a web browser:

$ go run main.go serve

Cross-compile

The use of cgo makes cross-compilation a little tricky, but doable, thanks to zig.

Mac is the only platform I know of that can cross-compile to all the other major platforms.

Make sure zig is installed. This makes cross-compiling C/C++ a breeze.

To strip symbol tables and other debugging info, add -ldflags "-s -w" to these go build commands for a smaller binary. (This is not desirable for production builds.)

From Mac...

to Linux (amd64 / x86-64):

CGO_ENABLED=1 GOOS=linux GOARCH=amd64 CC="zig cc -target x86_64-linux" CXX="zig c++ -target x86_64-linux" go build

to Linux (arm64):

CGO_ENABLED=1 GOOS=linux GOARCH=arm64 CC="zig cc -target aarch64-linux" CXX="zig c++ -target aarch64-linux" go build

to Windows (amd64 / x86-64):

CGO_ENABLED=1 GOOS=windows GOARCH=amd64 CC="zig cc -target x86_64-windows" CXX="zig c++ -target x86_64-windows" go build

From Linux...

to Windows (amd64 / x86-64):

CGO_ENABLED=1 GOOS=windows CC="zig cc -target x86_64-windows" CXX="zig c++ -target x86_64-windows" go build

Command line interface

Timelinize has a symmetric HTTP API and CLI. When an HTTP API endpoint is created, it automatically adds to the command line as well.

Run timelinize help (or go run main.go help if you're running from source) to view the list of commands, which are also HTTP endpoints. JSON or form inputs are converted to command line args/flags that represent the JSON schema or form fields.

Motivation and vision

The motivation for this project is two-fold. Both press upon me with a sense of urgency, which is why I dedicated some nights and weekends to work on this.

1. Connecting with my family -- both living and deceased -- is important to me and my close relatives. But I wish we had more insights into the lives of those who came before us. What was important to them? Where did they live / travel / spend their time? What lessons did they learn? How did global and local events -- or heck, even the weather -- affect them? What hardships did they endure? What would they have wanted to remember? What would it be like to talk to them? A lot of this could not be known unless they wrote it all down. But these days, we have that data for ourselves. What better time than right now to start collecting personal histories from all available sources and develop a rich timeline of our life for our family, or even just for our own reference and nostalgia.

2. Our lives are better-documented than any before us, but the record of our life is more ephemeral than any before us, too. We lose control of our data by relying on

Suggested labels

None

[ShellLM]

Related content

#625 similarity score: 0.87
#754 similarity score: 0.86
#678 similarity score: 0.85
#848 similarity score: 0.85
#743 similarity score: 0.84
#748 similarity score: 0.84