Hacker News new | past | comments | ask | show | jobs | submit login

I installed Nextcloud twice and faced early bugs quickly as well. I'm certainly not moving my 15tb of client photos to it anytime soon



Just use apace2, its davfs implementation, and davfs clients.

Linux has davfs2, android has foldersync.

Apache2 is super streamlined for this, and has done dav stuff for at least 16 years.


I was thinking of trying out using something low level... Maybe that? Does it support lazy selective syncing? Updating only ranges of files? Does it handle broken connections gracefully and recovers without data loss?


davfs is a protcol, a standard. Read that standard uf you wonder, but many things used dav behind the scenes.

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.


What are you using for backup?


I always wondered why photographers held on to negatives/raw files for so long. How often does the need to return years later come up, and can that justify the cost of storing all that in a way that’s somewhat reliable? I’m not saying there aren’t valid reasons to do so, and throwing the pictures on a few externals drives isn’t terrible, but to do it “right” seems like it would be super expensive!


Oh, I'd throw them away in a blink, If I were not lazy:

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.


Totally understandable! As a service provider, you want to be able to fulfill those requests because it will make you their go-to person for life. Pretty cheap compared to the benefits you can get.

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. :)


You could also back up to something like AWS Glacier. The cheapest tier (access less than once a year) is $1/TB/month. Maybe if you kept thumbnails locally, you could push all the data up and only pull it as and when you needed it.


Have fun paying a fortune if you need to get those files again.


If you need all of them, and can wait 5-12 hours, that appears to be free to request and transfer? Or am I misreading[0]?

[0] https://aws.amazon.com/s3/glacier/pricing/#Retrieval_request... <- under "Bulk"


This does not include data transfer pricing: https://aws.amazon.com/de/s3/glacier/pricing/#Data_transfer_...


Free retrieval pricing, but not free transfer. Transfer is starting at $0.09 per GB :-)


Aaaah I see : - ) still, if it's only very occasional "do you remember that photo?" queries, that shouldn't add up to any significant cost. But a full retrieval - yeah. Interesting how the price ramps up!


For "expedited" retrieval it is $0.01 per request plus $0.03 per GB. Doesn't seem like a fortune. And there are retrieval options for 1/10th the cost.


Transfer is starting at $0.09 per GB.


The exact same as transfer out of normal S3? Don't get me wrong, I am as big of an AWS pessimist as one is likely to stumble across.

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!


Because better hardware gets cheaper, and one's technique and software improves over time.

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...


I wonder how would you react to the DeepPRIME* from DxO

https://www.dxo.com/fr/technology/deepprime/

I have a license for some older version, if you want to throw a .nef at me


That looks pretty nice. I'll try to find some noisy files to send to you. What's nice about Darktable is it has a feature called "profiled denoise".

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.


Have you tried Immich? I don't have much experience with it (installed yesterday evening) but it looks and run great.


I second immich - used it for some group sharing (non-registered users) and worked really smooth. had some random upload fails though on the app from iOS.


I spinned it up once and looked really good. Never got to thorougly testing for that case. Might take another look




Join us for AI Startup School this June 16-17 in San Francisco!

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: