timeliner

Heya! I'm the author of PhotoStructure, and my Google Photos account (before I started working on PhotoStructure) is about that size, too. I wrote up some tips here: https://photostructure.com/faq/takeout/ This is what I did: 1. First try to fetch all your Google Photos via Takeout in one archive. If it fails (like it did for me), try different-sized .tgz archives. I had to use the 10 Gb option (using 50gb caused an internal-to-google error). If that fails to work, the last resort is to manually create by-year albums, shove all photos from that year into that album, and do a takeout of just that album. Repeat as necessary for every year. Yes, this is a huge PITA--which is why I recommend the following: 2. Install an app on your phone to *directly* upload the original photos and videos from your phone to your NAS/home server. I have severa

Very cool. Some great ideas here as I build a visualizer for Timeliner [0] (effectively its successor, Timelinize [1]) in my spare time! Did you build the timeline UI yourself? Can it be used as a library? [0]: https://github.com/mholt/timeliner [1]: https://twitter.com/timelinize

Neat, and interesting that his conclusion is that it's too much effort to do for oneself. My take on this is Timelinize[0], which is capable of downloading all your data from various digital records like social media, your phone, arbitrary files and unstructured folders, your Google account, etc. So it can aggregate data from Google Photos, Location History, Twitter, Facebook, text messages, and more, onto your computer, organized into a single timeline. (It is the successor to Timeliner[1].) I suppose Timelinize can support personal body metrics from various devices, and it is planned to support manual entries as well like journals. Analyses like his would also be possible. Data can be automatically imported on a regular basis via APIs (like, backing up your new tweets every day). The arbitrary file importer can also be scheduled to watc

This is why I'm building Timelinize [1]. It's a follow-up to my open source Timeliner project [2], which has the potential to download all your digital life onto your own computer locally, and projects it all onto a single timeline, across all data sources (text messages, social media sites, photos, location history, and more). It's a little different from "self hosting" but it does have a similar effect of bringing all your data home and putting it in your control. We have to start somewhere, might as well start with bringing in all the data we've put out there. (It's not a replacement for self-hosted media servers, for example.) The backend and underlying processing engine is all functional and working very well; now I'm just getting the UI put together, so I hope to have something to share later this year. [1]: https://twitter.com/time

I wrote Timeliner [0] and am writing its successor, Timelinize [1], to download all my family's stuff to our own computer. [0]: https://github.com/mholt/Timeliner [1]: https://twitter.com/timelinize

Not a "big project/service" but a Go project that uses Sqlite is one of my own, Timeliner[1] and its successor, Timelinize[2] (still in development). Yeah the cgo dependency kinda sucks but you don't feel it in code, just compilation. And it easily manages Timeline databases of a million and more entries just fine. [1]: https://github.com/mholt/timeliner [2]: https://twitter.com/timelinize

Time to dust off my side project, Timeliner [1] which downloads your Google Photos (and other content from various services) and indexes them in a local SQLite DB. Then after backing them up locally, I won't feel bad about deleting them from the cloud later to free up space. I've been using Timeliner for a while but need to update it. New maintainers welcomed, if you're interested! (One major "oof" is that the Google Photos API strips geolocation data, so unfortunately coordinates are lost when using this method. There's discussion about using Takeout as a workaround, or even automating web browser interactions, but those have their own problems too.) [1]: https://github.com/mholt/timeliner

Note that Google Photos is not really a viable backup if you care about quality at all: photos and videos are recompressed into a blurry mess, and your metadata will be likely missing. That said, there are several approaches to downloading what you can from Google: 1. Schedule periodic Google Takeouts (this requires you to download them, though) 2. Set up rclone (https://rclone.org/) or timeliner (https://github.com/mholt/timeliner) to use the Photos API. Note that _many_ tags may be missing, scrambled, or wrong. GPS will be completely missing. A much better approach is to set up a server (either at home with just an RPi hooked up to an external drive, or a cheap VPS), and then use SyncThing or Resilio Sync to get your original files off your phone and some place that you control. And then set up automated backups for this server, of cour

I've never heard of Timeliner. It doesn't have good Google ranking, so it was a bit buried. I think this is it: https://github.com/mholt/timeliner Timeliner is a personal data aggregation utility. It collects all your digital things from pretty much anywhere and stores them on your own computer, indexes them, and projects them onto a single, unified timeline. Supported data sources * Google Location History * Google Photos

Hey karlicoss, I'm in love with your writeup. You should know about Timeliner; Matt Holt's attempt at solving some of the data sourcing / data silo problems. https://github.com/mholt/timeliner He also points out Perkeep: https://perkeep.org/ Anyway. Data liberation is a huge driver for me. Making it a primary goal of my next app (primarily for bookkeeping/financial data, but I want to allow users to connect to the third party services I integrate with, eg. Uber, Amazon, etc, and be able to download their own data / play with it via an API). Feel free to email me / tweet me (@Adys) if you ever want to chat.

Cool, that's similar to my project Timeliner: https://github.com/mholt/timeliner It downloads your data from social media (or other online sites) into a single sqlite database. It can even draw relations between various accounts/people. I use it to back up my Google Photos.

https://github.com/mholt/timeliner is the script I referenced, and it does incremental backups. It is limited by what Google's API exposes, though, so what you get back is not what you uploaded: it's got many tags stripped, including GPS. It's really best to back up the originals that are on your phone. SyncThing and Resilio will do that automatically to your NAS.

It's barely a year old, but I think Timeliner is kind of trying to be this, as something you run yourself to protect against disappearing cloud services: https://github.com/mholt/timeliner

For preserving at least your own data, check out one of my projects, Timeliner: https://github.com/mholt/timeliner It downloads your digital life and stores it locally on a single, unified timeline, for archival and family history purposes.

You can use https://github.com/mholt/timeliner (open source)