Google Photos is so 2020—welcome to the world of self-hosted photo management | Hacker News Reader

Google Photos is so 2020—welcome to the world of self-hosted photo management

arstechnica.com

37 pointsjdenning11 comments

I'm totally self hosted as well, I have a directory on a harddrive called "Pictures" and under that I have subdirectories.. It's about 3 tib, and I can find anything I need within a minute or two.

I would have expected Synology to be included.

What we need is something like iOS TimeCapsule. Let the Phone do the Photo Management on Devices, and have an on site ( Home ) DataBackup as well as offsite ( iCloud ) Data Backup.

Apple could even make iCloud Backup subscription a requirement for TimeCapsule to function.

What is the advantage over the iCloud photos service they already have?

I actually have a copy of Data I owned in my own physical property. Not in a cloud server and account. iCloud, still to this day have somehow a small chances of corrupted backup. Apple deleting iCloud Backup after 60 days ( I think extended to 180 days I am not too sure ) if your devices does not connect to it even if you are continuously paying. Fully encrypted iCloud Backup and Photos so Apple dont see any of it.

Numerous other things.

Apple does not delete iCloud photos if you don’t connect to it every 180 days, that’s for iCloud device backups only.

The solution to it supposedly being unreliable would be to make it reliable, not invent workarounds. You’d still be unhappy if the service allowed local storage and the cloud service was unreliable.

This is just not the kind of business Apple is in.

Howdy, I'm the author of PhotoStructure, and was interviewed for this article. AMA about photo metadata, deduping, asset management, or hierarchical folksonomies.

Piwigo has been working well for me. I've been looking at Nextcloud's capabilities, but like keeping public vs private on separate systems.

Nextcloud is pretty bad. I struggled to get it running and keep it running. Updates often caused catastrophic failures. The project is more focused on adding features than making them work.

I would avoid it completely.

I’ve been running and upgrading it for about four years now—so across about 11 different major versions. Prior to that I was actually on ownCloud and migrated straight from that to Nextcloud. Every upgrade or migration has taken like 5 minutes. I’ve yet to have a single problem and it’s required zero maintenance between upgrades. It’s actually one of the few pieces of software that I self host and don’t fear updating.

Many people have obviously had experiences different from yours given it’s popularity. Speaking in absolutes as you’ve done really isn’t helpful to anyone.

Anecdote, counter-anecdote.

So you agree it's worthless as evidence? So saying in absolute terms that Nextcloud is bad and should be avoided completely based solely on a single anecdote is kind of a useless contribution?

Reply on news.ycombinator.com