timeline VS PhotoPrism

My timeline thing. It gathers all my crap and puts in onto a timeline. It's a more fine-grained version of scrolling to a specific date on my photo stream.

https://github.com/nicbou/timeline

It serves no purpose, but somehow it attracted one contributor.

It's pointless on purpose. It's the thing I work on when I want to forget about work, and build purely for myself.

Google Drive as a first line of defence. It's been solid for a really long time.

I also run hourly rsync backups to my home server, and propagate them to a Hetzner file storage server. This is done by my timeline thing [0]. The timeline thing backs up files from multiple devices, but also geolocation, social media posts, and other data I consider valuable. It's extensible, so I can add new inputs/outputs as needed.

Whatever your backup strategy is, consider the following threats:

- Your files are held hostage by ransomware, and the damage spreads to your backup

- Your house is destroyed by fire

- You lose your 2FA device

- You are locked out of your Google/Apple/Microsoft account

- You are incapacitated, and someone needs to take over

I have 4 of those factors covered. I am working on the last point.

[0] https://github.com/nicbou/timeline

My own timeline thing.

It hosts all of my data plus my personal diary. I update it at least once a day. My photos, backups and geolocation are automatically uploaded to it.

https://github.com/nicbou/timeline

My home server gets a lot of use too. It's mostly my own code, plus Transmission.

https://github.com/nicbou/homeserver

I also have a few lines of code that take my browser's search queries and routes them according to keywords. Browsers do this natively now, but old habits die hard. Every search query goes through it.

I added RSS to my websites, because my timeline thing (https://github.com/nicbou/timeline) uses them to retrieve posts from my websites.

However, I see the death of RSS as the symptom of a larger problem: when platforms get big enough, they restrict access to their data. RSS feeds disappear, but so do other machine-readable endpoints. If it wasn't for GDPR, there would be no way to export that data. GDPR gave us clunky one-time exports, but even those are often incomplete.

The industry has a strong incentive to kill RSS, since the readers can strip the valuable bits (content or data) from the business bits (analytics, monetisation). RSS users are hard to count or monetise.

This is a battle worth fighting, but it's not one you should expect to win.

https://github.com/nicbou/timeline

It regroups my personal data, and displays it on a timeline. Sort of like if Google Photos also included reddit posts, personal journal entries, text messages and other slices of life.

I do it both as a way to back up files and photos, and as a way to keep an enhanced journal.

I have been using https://www.photoprism.app for a couple of years, and it works better than expected, with the latest updates it's actually quite fast and the face tagging works reasonably well.

For self-hosting, there's Photoprism[1] as well.

Ente's strength lies in end-to-end encryption[2] and its cloud[3] offering so you don't have to worry about reliability.

So if self-hosting is what you're after, Immich, Photoprism and Damselfly (TIL!) are perhaps better designed to serve your needs.

[1]: https://github.com/photoprism/photoprism

[2]: https://ente.io/architecture

[3]: https://ente.io/reliability

For quite a while I'm also in search for a solution which allows me to share galleries with my family, without having to ask them to jump through hoops in order to access them.

After some searching I'm now testing photoprism [1] which is a fantastic application, especially for self-hosting of photos. There's no mobile app for it (yet) and user-management is just starting to get implemented, but it shows alot of promise. Unfortunately not yet enough for putting it on the tablet of my granny but one can hope (and donate!)

Either way, I'm afraid that building a good mobile gallery app is an equally large task, after all the best solution would be to replace the users' native gallery-app with an equivalent that also supports custom Online-Galleries...

[1]: https://www.photoprism.app/

out of curiosity, why no sort-of-established pkg and internal dirs? What do you think of https://github.com/photoprism/photoprism structure?

Thank you!

Ente was first a piece of hardware, then a self-host-able project, but we had a hard time monetizing both, which lead to the E2EE pivot.

TIL about TagSpaces, thanks!

Our server can be open-sourced, but we're unsure of the value E2EE will provide, with services like Photoprism[1] and Immich[2] already doing a good job of serving customers who prefer to self host. In this context E2EE might become a constraint, rather than a feature.

[1]: https://github.com/photoprism/photoprism

[2]: https://github.com/immich-app/immich

Ive seen github issues like this one https://github.com/photoprism/photoprism/issues/907 in which it is implied that this is very very difficult.

Hi. I want to implement an image server similar to Photoprism using ImageAI to tag images based on objects and context. However I don't want to spend to much time working on the frontend, at first I were thinking about using Danbooru and use Flexbooru or the web interface on my phone. But it doesn't have any encryption or password protection (since the purpose of it is to be used as a public image board).

https://www.photoprism.app in Docker.

PhotoPrism[0] and some ugly plumbing[1] to semantically tag all images in the gallery.

0: https://github.com/photoprism/photoprism