383 karma · joined February 16, 2023
As far as "beating" Apple, I'm ready to bet that'll never happen (not just with this project but any really). A small open source project can't really compete with a $2T company
Also note there are some extra config steps for the preview app (initial run, cron job). See https://github.com/nextcloud/previewgenerator
I wrote a bit on why Nextcloud a while back, I'll link it here (see point 5 in FAQ): https://memories.gallery/faq/#faq
As such, Nextcloud doesn't really lock you in; it just provides a framework for the app. You can, theoretically, continue to use Syncthing to sync files while running Nextcloud on top of it (probably not ideal though)
I want to note though, the "no lock-in" philosophy refers more to being able to move out of Nextcloud/Memories at any point if you want. Nextcloud still just stores everything on your disk as folders and files, so you can just decide to nuke it one day and still have everything (not fully true yet, you'll still lose some things like tags and albums; exporting these out too is WIP)
Albums: partial support. You can share links to albums that are viewable or share albums with others with an account on your nextcloud instance. People who have an account can upload photos to the shared albums.
Minimum requirements are quite low. Mainly you need memory to get good performance (at least 4GB, say). CPU-wise it runs fine with massive libraries even on RPi.
I don't recommend S3 as external storage though; the Nextcloud implementation is quite finicky. Unless you can mount that and use it inside docker, that would work fine.
EDIT: features like AI are all optional.
In this case I was rather annoyed since the original comment was very offensively worded and the person obviously had zero intention of helping out. Their only goal was to stroke their own ego by shouting out how something they couldn't get to work is crap.
This is part of the reason for open source maintainer burnout -- useless comments about how something is broken with zero intention of helping to fix it. Hey, it's free -- if you don't like it then either help, or stop crying and move on to something else.
https://play.google.com/store/apps/details?id=gallery.memori...
The Nextcloud app is used for auto-upload, that does support background upload at least on Android.
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.
It's FOSS and I only work on this in my free time, so please keep the bug reports coming as you run into them! :)
The result: each request overall only takes a few milliseconds for the hardest part, the rest of the optimization is a game of caching.
EDIT: yeah, they edited that out too.
Ente is commercial, Memories is free
Ente is focused on E2EE, Memories is focused on self-hosting.
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.
Thumbnail caching exists (it's even highly configurable), there's absolutely zero buffering even with 100k photos+ on a raspberry pi. You obviously did not read the documentation or install the preview generator (which the docs clearly tell you to)
Your deployment skills are hot garbage
EDIT 3: ^the last line was in response to something that has been edited out of the original comment
EDIT: the comment this is in reply to was edited multiple times. This is pointless and a lot of it is just false.
EDIT 2: (at least currently the previous comment claims unnecessary PHP requests) this only happens if your configuration is incomplete; you didn't install preview generator as the docs say. Secondly it happens exactly once, the first time you see the image. All other requests are gracefully cancelled.