Hacker News new | ask | show | jobs
by menthe 822 days ago
Absolutely was using the AIO image, with thumbnail generation enabled for every formats of my library (another thing you need to manually edit in Nextcloud’s configuration as by default the format list is limited).

And it’s only “pre-optimized” if you are cool with PHP memory limit crashes, PHP operation timeouts, PHP request size limits, and the works.

Another joy associated with using Nextcloud sync is that uploads don’t even seem to support multi-part resumable uploads. So not only is it crazy slow, if there’s any error during the auto-upload of a 2G video clip, or the app is temporally backgrounded by iOS, it’ll go into an exponential back off (which you can force start), and eventually just start the upload for that/those file(s) over from scratch - good ways to waste days burning in your screen while in a trip and trying to ensure your medias are backed up in case you lose your phone on a trip. Try uploading raw images & 4k clips shot on iPhone to Nextcloud using the Nextcloud app + the AIO image from abroad.

I’m telling you, I’ve tried to use them for quite some time, and I’m far from DevOps-illiterate - I’ve been using k8s since it’s infancy, we wrote the original Operators at CoreOS way back.

1 comments

I don't know what to say if you think flipping a switch in the admin UI is "manually" configuring.

Otherwise, mostly all of this is just false. I routinely upload massive files (both RAW and 4K, yes) with almost default configuration and it just works. You also lied with "no thumbnail caching" in the first comment, no idea why.

Wow, your first comment was completely rude and unnecessary. Why do you feel the need to say, "you must be lying or you suck at deploying, because it works for me."

also, they meant that their SMB share didn't have thumbnail caching

Hmm I can reply now, strange. That comment was edited multiple times so this is pointless. Also the original commentor started the rude exchange with "hot garbage" (wonder if they'll edit that out too now)

EDIT: yeah, they edited that out too.

I understand now that you are the developer of this app.

I'm sure it doesn't feel very good to have someone criticize it, I get that. But, this person cared enough about the thing you made to use it, troubleshoot it, and post a comment about it on HN.

At the end of the day, it's valuable user feedback :)

No, just no.

Valuable user feedback (which I absolutely love) is someone pulling the server logs, filing a bug on GitHub and following through till it gets fixed. Or, even attempting to see what parts are slow and reporting it. Worse but still very helpful, providing a link to an affected instance that might help "see" what might be happening.

Spending a few hours trying random things and then complaining loudly like a know-it-all is NOT valuable feedback; it's bullshit. Nothing here is helpful, at all. There's absolutely zero indication of what could be fixed and why this particular person's deployment is broken while thousands of others on much slower hardware work just fine. None.

Yeah, you're right. You should say "please file a detailed bug report and consider contributing to the project", instead of being a dick about it.

The other comments you posted are also a bit odd without you disclosing you're the author. just saying

The day SMB supports server-side thumbnail generation/caching, kindly let me know :]