You can configure the storage template for the photos and include an "album" part, so if a photo is in some album it'll get sorted into that folder. Then the file tree on disk is as you wish.
I haven't tested what it does when a photo is in multiple albums, but it does handle the no album case fine as well.
Ente looks interesting and worth looking into, thanks for mentioning it.
In the context of having a phone stolen, it's possible to at least limit the damage and revoke accesses via the Tailscale control server. Then the files on device are still vulnerable, but not everything in Immich (or whatever other service is running).
Why would you need Tailscale for revoking an access token in an unrelated service? Just kick the device out of the sessions list in Immich, or change your password if that's stored directly on the device
Very nice the author uses tailscale serve! It's an underrated, and unfortunately under documented, way to host a web service directly to Tailscale. With that you can run a docker compose stack with one extra tailscale container, and then it's immediately a self contained and reasonably portable web server in your tailnet.
Immich really is fantastic software, and their roadmap is promising. I hope they have enough funding to keep going.
Also it has a very rich ACL system. The Immich node can be locked out from accessing any other node in the network, but other nodes can be allowed to access it.
The sync really is quite good. On wifi it's basically seamless. If I had 30k new images though it would be much faster to use the immich-go tool mentioned in the blog post.
Offline support is alright, though I haven't worried about this much. I think it doesn't do any local deletion, so whatever stays in your DCIM folder is still on device.
The Nextcloud iOS app does it. For some reason it requires the location permission "all the time" for that, presumably as a way to "wake" the app from time to time?
I decided to try Nextcloud exactly because of this. My problem with it is more that the whole thing is a bit unreliable. Like once in a while the app will get into a state where the only way I found to recover is to just erase everything and re-sync everything. And the app will resend ALL the pictures, even though they are already on the server.
And I can't do that with my family members' phones. It doesn't matter to me if the app takes a month to sync the photos, but it has to require zero maintenance. I can deal with the server side, but I need it to "just work" on the smartphones.
Searching for "nextcloud ios background sync" shows a whole bunch of forum posts and bug reports about it not working well unless you have the application open.
For something that works well it seems like a ton of people have a lot of issues with it. Are you sure you're on the latest iOS version? Seems like people experience the issues when they're on a later version.
I don't know it for sure, but I think it wasn't working until a recent update (like 6 months ago). Also an unintuitive thing is that the location permission has to be given to the app "all the time", and I think I had to manually go into the settings to set it up.
I think that the forum posts may be old, and/or a bunch of them may come from users who did not know that they had to set the location permission this way (which admittedly is unintuitive for photo syncing).
Background support for non-Apple apps is best-effort at best, and explicitly discouraged in the docs. The rate of silent push notifications and other background mechanisms are intentionally not documented and you’re explicitly instructed you not to rely on any current behavior. They make some exceptions to support money makers like Uber and fitness tracking but generally they don’t like you using anything in the background.
Android is more relaxed but the vendors (like Samsung etc) will go around that and implement their own aggressive background killing bots. Sometimes, this causes alarm apps to stop and not wake you up etc.
The main reason is battery life. Tragically, this makes sense due to the cesspool of spam apps that plague their ”curated” app stores. If you’re an app developer who want to use it responsibly you’re in for a world of trouble. I know because I am one of them (well, I consider myself responsible at least).
The Nextcloud app has been running and syncing in the background on 3 iPhones for like 6 months, so they managed to make that work relatively well.
My issue is other bugs that make it painful, including the fact that I cannot trust that Nextcloud will eventually upload the whole photo gallery (it seems like some files regularly get "locked" w.r.t. "webdav", for some reason, and this never resolves).
Yeah, this and syncthing for keeping our shared password vault file in sync together were 2 of the 3 major reasons my wife's last phone upgrade was a swap from iOS to Android (went with a Pixel 8, which was new at the time).
Since then, Immich and Syncthing+Keepass have worked as well as or better than their proprietary equivalents for my decidedly-non-technical wife.
I did initial setup, and she never has to think about it again. It just works, which is more than I can say for paid cloud subscriptions and their constant nags over exceeded storage space.
I have the main volume for images in a zpool with two SSDs in a raid-1 configuration. I also have a daily cronjob that makes an encrypted off-site backup with Borg. I've also got healthchecks.io jobs setup so that if the zpool becomes unhealthy, the backups fail, or anything stops, then both me and my partner get alerted.
My partner isn't very technical, but having an Immich server we are both invested in has gotten her much more interested in self hosting and the skills to do it.
I think it's of course not so simple, and the abstract of the paper they refer to [0] seems to contradict the Business Insider article. Sure, inflation adjusted median income is up slightly. In addition to this educational costs have exploded, and to earn a median salary it has become necessary to buy in. People under 30 have greater inflation adjusted income, but this is because they rely more on their (boomer) parents. The overall wealth in society has increased dramatically, but the vast majority of gains are going to the outliers.
That is to say, the real conflict isn't between boomers and millennials, it's between billionaires and everyone else. But generational friction is not new, a more common experience, and easy to exploit in media.
I've used probably 15 or 20 web browsers in my lifetime and all of them had the same barely searchable table of URLs as their only history view. Why couldn't we have full text search of the pages, or a view that reflects tab histories as some kind of graph, or UIs that support any kind of sorting? Instead it's 2025 and the solution is to attach an LLM slot machine to the front and drive engagement.
I'd be very open to any Firefox extension suggestions (or standalone applications that can consume a Firefox history) that makes it more searchable. I don't often need to search my browser history, but when I do the answer is rarely easy to find.
All of the other features look like a high potential for abuse, but with lots of glitz to make it seem essential to laymen.
The Firefox Awesome Bar, since spring of 2008, has been quite better than anything else, you could search any fragment of the page title and the results showed up by frecency. Curiously, Chrome's omnibox came out later that year and is still worse.
There were many discussions about this in HN too, and the general conclusion was Google wanted to force more Google searches, and the large general users of Chrome were fine with it.
or when you go to chrome's history and it just lists the title of the page followed by simply the domain. It's like "some designer thought the pages feng shui wasn't in alignment and now the useful stuff is gone."
I have to assume they just hire artists that have never used a computer to make UX decisions and act as product dictators.
It's either that or empiricism by idiots: "We made the feature take 5x more time to use and got a 5x increase in engagement! Won't my boss be proud!?"
I think it's about improving the turnaround on planes. When a plane lands, the crew has to get everyone out, clean the cabin, then get the next flight's passengers in -- all as quickly as possible. The shorter this turnaround, the more flights the plane can fly, and the more money the airline can make.
Flexible seat back pockets are easy for people to stuff all kinds of trash in, so that's just one more task for the crew. Inflexible slots are harder to put trash in, and harder for passengers to notice there's trash in.
Counter offer... the turnaround time is locked in, cargo unloading and refueling, but fewer tasks mean fewer crew members needed to perform those tasks in the given time. So rather than 5 cleaners descending on an arriving plane, they can put 2 or 3 on it and pocket the 2 salaries they are no longer paying.
Just an offer, I don't actually know the airlines' historical cleaning crew requirement number trends.
I can imagine the large scale web scrapers just avoid processing comments entirely, so while they may unzip the bomb it could be they just discard the chunks that are inside of a comment. The same trick could be applied to other elements in the HTML though: semicolons in the style tag, some gigantic constant in inline JS, etc. If the HTML itself contained a gigantic tree of links to other zip bombs that could also have an amplifying effect on the bad scraper.
There is definitively improvements that can be made. The comment part is more about aesthetic as it is not needed actually, you could have just put the zip chunk in a `div`, I guess.
You can configure the storage template for the photos and include an "album" part, so if a photo is in some album it'll get sorted into that folder. Then the file tree on disk is as you wish.
I haven't tested what it does when a photo is in multiple albums, but it does handle the no album case fine as well.