Self-hosted photo and video backups directly from your mobile phone
211–220 of 354 posts
Re: Self-hosted photo and video backups directly from your mobile phone
#212The recommended spec is 4 cores and 6GB. Running this 24/7 for a year in US where the carbon intensity is about 400 gCO₂eq/kWh would produce about 150kg of CO2 per user per year. I appreciate the intent of this project, but it is not a sustainable approach. If you are taking a couple of pictures a day, you only need to run this service for a couple of minutes per day, the rest is wasted. With Google Photos, as a SaaS…
Honestly, that a simple file sync service needs that kind of specs is bewildering to me.
It has object and face detection. Metadata indexing / searching and multi user support.
Re: Self-hosted photo and video backups directly from your mobile phone
#213The recommended spec is 4 cores and 6GB. Running this 24/7 for a year in US where the carbon intensity is about 400 gCO₂eq/kWh would produce about 150kg of CO2 per user per year. I appreciate the intent of this project, but it is not a sustainable approach. If you are taking a couple of pictures a day, you only need to run this service for a couple of minutes per day, the rest is wasted. With Google Photos, as a SaaS…
Re: Self-hosted photo and video backups directly from your mobile phone
#214 The project is under very active development. Expect bugs and changes. Do not use it as the only way to store your photos and videos!
This is a bad thing for the average Joe.Re: Self-hosted photo and video backups directly from your mobile phone
#215The recommended spec is 4 cores and 6GB. Running this 24/7 for a year in US where the carbon intensity is about 400 gCO₂eq/kWh would produce about 150kg of CO2 per user per year. I appreciate the intent of this project, but it is not a sustainable approach. If you are taking a couple of pictures a day, you only need to run this service for a couple of minutes per day, the rest is wasted. With Google Photos, as a SaaS…
Honestly, that a simple file sync service needs that kind of specs is bewildering to me.
Re: Self-hosted photo and video backups directly from your mobile phone
#216I prefer SyncThing on both mobile and desktop devices. It's open source and mature, the server only makes devices findable between each other. It allows 1 or 2 way sync. And it has advanced settings for keeping removed files (e.g. trashbin that cleans anything older than X days.)
Re: Self-hosted photo and video backups directly from your mobile phone
#217I prefer SyncThing on both mobile and desktop devices. It's open source and mature, the server only makes devices findable between each other. It allows 1 or 2 way sync. And it has advanced settings for keeping removed files (e.g. trashbin that cleans anything older than X days.)
Can syncthing automatically upload photos?
Re: Self-hosted photo and video backups directly from your mobile phone
#218Earlier quoted context omitted.
Picasa could do that too 2014, single threaded. (And is probably still better)
It does feel like we keep going backwards for functionality while resource requirements keep increasing. Picasa had face recognition, basic editing, and a bunch of sorting features and ran on computers that had something like 1/50th the CPU performance. Meanwhile modern replacements like DigiKam, Lightroom, ON1, and so on are incredibly bloated with very slow UI response even on a very powerful desktop PC. Although I…
Darktable and ON1 feel decent snappy on my ~8 year old Desktop PC.
Though it was a looong time since I last tried Picasa.
Re: Self-hosted photo and video backups directly from your mobile phone
#219Earlier quoted context omitted.
Honestly, that a simple file sync service needs that kind of specs is bewildering to me.
It's not a simple file sync service. It has object and face detection. Metadata indexing / searching and multi user support.
The only computationally expensive thing here is face matching. Photoprism recommends two cores and 3G RAM and claims to be able to run on a NAS.
Re: Self-hosted photo and video backups directly from your mobile phone
#220The recommended spec is 4 cores and 6GB. Running this 24/7 for a year in US where the carbon intensity is about 400 gCO₂eq/kWh would produce about 150kg of CO2 per user per year. I appreciate the intent of this project, but it is not a sustainable approach. If you are taking a couple of pictures a day, you only need to run this service for a couple of minutes per day, the rest is wasted. With Google Photos, as a SaaS…
If you are running the machine anyway to do other tasks like backing up and running Jellyfish then it might be worth it. How did you get to 150kg of CO2 per user? I'm going to assume you mean each person has one instance rather than sharing an instance like a family would. So thats 375Kwh per year, which works out as drawing 42W. That seems rather high to me. I'm hoping to try and run this on my Pi4 which idles at un…
The link I shared has the details of the calculation. The calculation assumes 50% CPU load which is most likely too high for this use case.