Linux has davfs2, android has foldersync.
Apache2 is super streamlined for this, and has done dav stuff for at least 16 years.
And apache2 is a very well established implementation of it.
Clients handle partial snags.
I wouldn't rely upon anything that syncs like this, without backups. Any protocol at all.
Of course, the same may be said for anything at all. Backups are king.
I was able to recover a 13 year old photo I took with a D70s which was extremely noisy. By using what I learnt and state of the art software (which is Darktable), I was able to extract a very nice photo out of it.
Also, as your style improves and experience piles up, you look to your "bad" photos and say "Aha, there's a nice angle here. Let's process this".
You can see some of my "Remastered" photos at [0].
[0]: https://www.flickr.com/photos/zerocoder/albums/7215770242956...
https://www.dxo.com/fr/technology/deepprime/
I have a license for some older version, if you want to throw a .nef at me
Contributors send in calibrated RAW files per camera, taken at every ISO setting possible, so Darktable denoises your file according to your camera's profile at particular ISO. The result is pretty impressive.
I have uploaded that particular image to [0]. Taken in 2006 and processed in 2020, after 14 years!
[0]: https://www.flickr.com/photos/zerocoder/53363865806/in/datep...
Edit: EXIF says 2005, but it should be 2006.
Almost after every shoot, people come back "remember that one photo, where I smiled at sth? I'm very sentimental about that, cause it's [some important thing to them]", which necessitates the need to hold on to every photo taken on the session. So no real deletes here, even if it came out technically wrong (blurry, blown out, etc.).
Those requests lessen, but don't die down completely. Especially with cyclic events, organizers have this habit of a asking for things done exactly year ago.
Some just say: "hey, I remember you taking a photo of me then and then" for their dancing portfolio in my case.
Especially for videos, which can be a constant flow of editing requests, for supercuts and etc.
Now, if I were really smart, I'd just have some good way to archive after two years, and delete after - let's say three years. In practice though, there are so many unforseen circumstances that a habit of "never delete anything" forms really easily.
It's just a lot easier and cheaper to buy another drive instead of culling 10k of photos every once in a while, especially if external confirmation is involved.
[0] https://aws.amazon.com/s3/glacier/pricing/#Retrieval_request... <- under "Bulk"
I guess I could reinterpret your original comment as "Have fun paying a fortune if you need to get those files [out of AWS] again."
instead of my original interpretation "Have fun paying a fortune if you need to get those files [out of Glacier] again."
Agree!
Despite constantly crowing at researchers in my past life that they will lose all their data ... it only happened once or twice, and both times was related to theft and not drive failure.
I wonder if you could sell a type of "archive protection plan" as an add-on to your work. It's like $70 a year to store 500GB on Glacier. I am sort of assuming each shoot is 500GB? You could guarantee access for those customers who want it.
If we're being honest with each other, I would do the exact thing you're doing and focus more on my business. :)